patent_id
stringlengths 7
8
| description
stringlengths 125
2.47M
| length
int64 125
2.47M
|
|---|---|---|
11943679 | DETAILED DESCRIPTION OF THE DISCLOSURE Aspects of the present disclosure provide various techniques (e.g., methods, systems, devices, computer-readable media storing computer-executable instructions used to perform computing functions, etc.) for using image data captured via the cameras of a mobile device, as well as local map data (e.g., map tiles received from a map server or geoservices module), to determine an orientation and/or precise location for the mobile device. In some cases, the determined orientation data and location data may be used to update the previous device orientation readings or device location determinations made by the internal orientation or location/positioning systems of the device. The internal orientation or location/positioning systems of the mobile device also may be reconfigured or recalibrated in some cases based on the updated orientation and location readings. Additional aspects of the present disclosure provide techniques for generating and displaying map and navigation user interfaces on the mobile device, using the updated device orientation and/or location data. In some embodiments, an augmented reality (AR) navigation user interfaces may be generated and rendered by overlaying a set of navigation user interface components corresponding to the current location and orientation of the device, on to current image data captured by a device camera. FIG.1is a diagram illustrating a mobile device of a pedestrian displaying a navigation user interface according to certain embodiments of the present disclosure. In this example, a pedestrian user is holding a mobile device110which is currently displaying a user interface115of a mobile navigation application. Although a simplified user interface115is shown in this example for clarity, the mobile navigation application may display map and navigation graphical user interface components, such as a map of the general area near the user, including nearby streets, buildings, and landmarks, and an identification of the user's current location on the map. Embodiments described herein may apply both to map view user interfaces (e.g., showing the user's current location on a map) as well as to navigation user interfaces (e.g., showing the user's current location, a selected destination, and/or directions guiding the user to the location). Mobile map applications (which also may be referred to as mobile navigation applications when configured with navigation functionality) may retrieve map data from a map data store in a remote map server120. The mobile map and/or navigation application may display map elements (e.g., streets, buildings, landmarks, etc.) as graphical components and geometric shapes, and/or by using actual image data within the map displayed in the user interface. For example, the mobile navigation application may be configured to receive and display satellite image data or previously captured street view image data for the map rendering. In other examples, the mobile navigation application may be configured to display an augmented reality user interface, in which real-time image data is captured via a camera on the mobile device110, and is overlaid with labels and other graphical components to provide the navigation functionality to the user. The mobile navigation application also may support different user interface views for the user while being guided to a destination, such as an overhead (or bird's eye) view, a turn-by-turn navigation view, a street view, and an augmented reality view. In this example, the mobile navigation application shown inFIG.1may be configured as a pedestrian navigation system, which may differ from vehicle-based navigation systems in several ways. For example, certain vehicle-based navigation systems might not detect or use the orientation of the device to generate the user interface display. Instead, a vehicle-based GPS navigation system, or a smartphone executing a “vehicle mode” of a mobile navigation application, may assume that the orientation of the display should correspond to the direction of travel of the vehicle. Therefore, if a smartphone executing a “vehicle mode” of a mobile navigation application is turned around while the vehicle is moving forward, the user interface need not be rotated to reflect the change in orientation of the device. However, in the pedestrian navigation system shown inFIG.1, a change in orientation of the mobile device110may indicate that the pedestrian has turned or changed directions, and thus the user interface115should be changed to reflect the new device orientation. Additionally, unlike certain vehicle-based navigation systems, the current location of the mobile device110in a pedestrian navigation system cannot be assumed to be on a road or highway, or even on a sidewalk or path. Thus, a pedestrian navigation system may generate different displays for the user interface115based on even small difference in the location of the mobile device110. For instance, the pedestrian navigation system may display different data within the user interface115depending on which side of the street the user is walking, or when the user is cutting through a parking lot, path, or field, etc. Pedestrian navigation systems also might not assume that the user is at street level, but instead may detect when a user is below or above street level (e.g., in a subway tunnel, on a balcony or roof), when generating the user interface115. Thus, in certain embodiments, a pedestrian navigation system may determine whether the mobile device110is a street level, above street level, or below street level, and may generate the user interface115accordingly. FIG.2is a block diagram illustrating components of a mobile device navigation system according to one or more embodiments of the present disclosure. The mobile device navigation system200in this example may correspond to a pedestrian navigation system configured to provide location mapping and navigation functionality to a pedestrian user via the user's mobile device110. Navigation system200includes a map/navigation mobile application210, an augmented reality system220, a media system230, a map data store240, a location system (or mobile positioning) system)205, and a motion system260. The different components and systems210-260of the mobile device navigation system200may be implemented within a mobile device110, within a computer server120, and/or within one or more third-party systems as described herein. For example, in some embodiments, the mobile application210, augmented reality system220, media system230, location system250, and motion system260may be implemented within the user's mobile device110, and the map data store240may be provided by a server120. The map/navigation application210may correspond to a mobile application installed on the user's mobile device110. Application210may be configured to display map data and provide various location mapping and navigation functionality via a user interface115. For example, in response to application210being opened or started on the mobile device110, application210may display a map user interface with elements corresponding to the user's current location, and provide directions to selected destinations. In some embodiments, the map/navigation application210may be configured to provide an augmented reality (AR) user interface in which map/navigation components are generated and overlaid on real-time image data is captured via a camera on the mobile device110. Thus, application210may include a turn-by-turn routing engine, and an augmented reality overlay component as shown in this example. The augmented reality system220may include components configured to generate the map/navigation components to be overlaid within an AR navigation user interface on the mobile device110. In this example, the augmented reality system220includes a semantic image segmentation component, an image-based heading estimation component, a long-baseline Visual Inertial Odometry (VIO) component, and a georeferenced AR content provider. Media system230includes one or more device cameras that capture image data for use in the AR navigation user interface. The AR system220may transmit requests to the media system230to activate a front-facing camera of the mobile device110during time periods when the map/navigation application210is in use and configured to display an AR navigation interface. During these time periods, media system230may activate the front-facing camera continuously, and provide the captured image data to the AR system220for use in the AR navigation user interface. Map data store240, which may be implemented within a map server120separate from the mobile device110, includes a database of map tiles. Map tiles contain sets of object identifiers, properties, and geographic coordinates that represent physical objects (e.g., buildings, streets, natural landmarks, etc.) within a particular region. The AR system220may request the appropriate map tiles based from the map data store240based on the current position of the mobile device110when the map/navigation application210is in use. Location/positioning system250may be configured with one or more location subsystems configured to determine the location and orientation of the mobile device110. In this example, location/positioning system250includes a location estimator, a VIO-stabilized location component, a compass/camera heading arbitration component, a pedestrian map matching component. The location/positioning system250may be configured to provide device location data when requested by the map/navigation application210. In some cases, the device location system250may include a GPS receiver or other mobile positioning technology configured to detect current geographic coordinates for the mobile device110. Additionally or alternatively, the location/positioning system250may be configured to detect a wireless network, wireless access point, and/or other nearby devices (e.g., known Bluetooth devices, NFC tags, etc.) from which the location of the mobile device110may be determined. Location/positioning system250also may determine the current device orientation in response to requests from the map/navigation application210. In some cases, device orientation may be determined by an internal compass of the mobile device110. In other cases, device orientation may be calculated using triangulation, by detecting differences in arrival time of a signal at different antennas of mobile device110. Motion system260may include motion sensors such as an accelerometer and gyroscope. In some embodiments, motion system260may be configured to provide device motion data to the AR system220, and/or to the location/positioning system250. For example, motion data may be provided from the motion system260to the AR system220, to be used by the AR system220in generating the AR content. Additionally, the motion system260may be used to detect device location and/or device orientation, based on motion sensors such as an accelerometer and gyroscope within the mobile device110. For example, assuming that an initial location or orientation of the mobile device110is known, monitoring and tracking of device acceleration data and/or gyroscopic data in three dimensions may allow the mobile device110to compute an updated location or updated orientation. FIG.3is another block diagram illustrating interfaces and components of a mobile device navigation system according to embodiments of the present disclosure. The mobile device navigation system300shown in this example may be similar or identical to the navigation system200discussed above, with additional details showing further components and communication paths between the systems and components. In other embodiments, mobile device navigation system300may correspond to a separate implementation of a pedestrian navigation system, different from navigation system200. FIG.4is a flowchart illustrating an example process of generating and displaying a navigation user interface via a mobile computing device according to embodiments of the present disclosure. As described below, the steps in this process may be performed by a user device110, such as smartphone or other mobile device executing a mobile device navigation system. Accordingly, the features and functionality may be described with reference to the devices and systems described above inFIGS.1-3. However, it should be understood that processes of generating and displaying navigation user interfaces described herein are not limited to the specific computing environment and systems described above, but may be performed within various other computing environments and systems. In step401, the mobile device navigation system200receives imaged data captured by one or more cameras232of the mobile device100. In some embodiments, the capturing of image data in step401may be performed in response to the user launching or initiating the mobile navigation application210. For instance, the mobile application210or augmented reality system220may be configured to activate one or more device cameras in response to the mobile application210being opened or launched, or in response to a user action (e.g., a user initiating a pedestrian navigation mode) via the user interface of the mobile application210. In other examples, the device camera(s) may be configured to continuously capture data during the operation of the mobile device110, in which case a continuous stream of image data may be received by the AR system220, prior to mobile application210being opened or launched by the user. The image data received in step401may correspond to digital images and/or video data captured via one or more cameras of the mobile device. It may be advantageous in some cases to maximize the amount of image data received in step401. As discussed below, maximizing the amount of image data collected in step401may allow the objects represented in the image data to be more readily matched with corresponding map data, and also may provide more image data overall to analyze when determining device orientation and/or location. Accordingly, in some embodiments, receiving the image data in step401may include activating multiple cameras on the mobile device110, such as a front-facing camera, a user-facing camera, and/or any other available cameras to maximize the amount of image data collected. Wide-angle or panoramic camera modes also may be used in some cases, in order to increase the angles from which the image data collected in step401. Additionally, in some embodiments, the image data received in step401may be collected by one or more separate computing devices at the same location, and then transmitted to mobile device110. For example, a navigation system executing on a user's first mobile device110(e.g., a smartphone), may activate cameras on one or more of the user's other devices, such as a second smartphone, a smart watch, or other wearable device having a camera, etc. The other user devices thus may collect additional image data, and may transmit the image data back to the first mobile device110that is executing the navigation system. In step402, the mobile device navigation system200may receive and/or determine current location data for the mobile device110. In some embodiments, the mobile device110may activate an internal Standard Positioning Services (SPS) receiver, such as a GPS receiver or other mobile positioning system, in response to the user opening or activating the map/navigation mobile application210. One or more SPS receivers on the mobile device110may be capable of receiving signals from one or more SPS satellites using an SPS antenna. In various embodiments, an SPS receiver on the mobile device110may support measurement of signals from the space vehicles (SVs) of an SPS system, such as a Global Navigation Satellite System (GNSS) (e.g., Global Positioning System (GPS)), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, Beidou over China, or the like. Moreover, the an SPS receiver may be used with various augmentation systems (e.g., a Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global or regional navigation satellite systems. By way of example but not limitation, an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), or the like. Thus, as used herein an SPS may include any combination of one or more global or regional navigation satellite systems or augmentation systems, and SPS signals may include SPS, SPS-like, or other signals associated with such one or more SPS. Other techniques for receiving the current location of the mobile device110in step402may include determining a current device position based on the device's connections to one or more additional devices via short-range wireless communication protocols, including any wireless networks and/or wireless access points to which the mobile device110is currently connected. For instance, during use of the map/navigation mobile application, the mobile device110may be connected to one or more wireless networks through one or more wireless access points or other network components. Wireless access points may include devices such as wireless routers, modems, switches, mobile hotspots, set-top boxes, and the like, which allow mobile devices130to connect and communicate wirelessly to Local Area Networks (“LANs”), Wide Area Networks (WANs). Certain wireless networks and/or wireless access points may be associated with certain geographic locations (e.g., homes, workplaces, merchant-provided WiFi networks, etc.), and thus the mobile device110may determine its current geographic location based on the set of wireless networks and wireless access points that are currently available for connection by the mobile device110. The various techniques used in step402for determining the current location of the mobile device110may have different levels of accuracy and reliability. For example, GPS Standard Positioning Services (SPS) and GPS Precise Positioning Services (PPS) may provide different levels of accuracy, and the accuracy of receivers for either standard may be influenced by signal issues and satellite line-of-sight obstructions, measurement biases, and random errors. Additionally, determining a location of the mobile device110based on the wireless networks and wireless access points detected by the mobile device110may be less precise than using GPS in some embodiments. For example, a signal from a known wireless access point might only allow for positioning of the mobile device110within several hundred feet, depending on the transmission range of the wireless access point. Accordingly, it should be understood that the various steps below may be customized based on the accuracy and reliability of the location determination in step402. For example, larger geographic ranges of map information may be retrieved (step403) when the location determination in step402is less precise or more likely to be error prone. In step403, the mobile device navigation system200may receive map information for the region at or near the current location of the mobile device110. In some embodiments, a location/positioning system250of the mobile device110may request map information (e.g., one or more map tiles) from a map server120, corresponding to the current location and nearby areas of mobile device110. The map server120may include one or more map data stores240, storing a catalog of map tiles or other map data files/structures representing different map regions. In some cases, a single map tile may represent a one square kilometer area of land. In some cases, the map information (e.g., one or more map tiles) may be retrieved in step403in response to a user opening or initiating a map/navigation application210on the mobile device110. In other cases, the location system250may be configured to periodically or continuously track the current location of the mobile device110, and to request new surrounding map information from a map server120as needed. The map information received in step403may include map tiles, or other similar formats of map data files or structures, which include sets of geographic coordinates identifying the physical objects within the region covered by the map tile. For example, a map tile covering a particular region may include coordinate data that defines the precise size, shape, and boundaries for all streets, paths, buildings, natural or man-made landmarks, and other any fixed objects within the region. In addition to geographic coordinates, map tiles also may contain data identifying each unique object and its type (e.g., street, path, building, bodies of water, other natural landmarks, etc.), object names or labeling data, and other object properties. The map tiles or other map information received in step403may include any and all data needed by a map/navigation application210to render a map graphical user interface of the region. Additionally or alternatively, the map information received in step403may include image data for or near the current location of the mobile device110. For example, the location system250may retrieve satellite image data or previously captured street view image data, from one or more external servers120corresponding to the current location and surrounding areas. In another example, the map information received in step403may include catalog of physical object images (e.g., buildings, landmarks, etc.), along with the known geographic coordinates of the physical objects. As discussed below in more detail, the map information received in step403may be analyzed and compared to the image data captured at the mobile device110. Thus, when non-image map information (e.g., a map tile) is received in step403, the comparisons to the captured image data may be based comparison of object sizes, shapes, etc. However, when map image data is received in step403, the comparisons to the image data captured at the mobile device110may include image-matching, etc. In some embodiments, map information may be received from the map server120, without ever providing the map server120the precise location of the mobile device110. For example, the location/positioning system250of the mobile device110may request and receive one or more map tiles that cover a relatively large area, without ever transmitting the location coordinates of the mobile device110to the map server120. Such embodiments may provide technical advantages with respect to protecting privacy and security, including completely supporting the map/navigation functionality described herein (e.g., pedestrian navigation systems, AR-based map/navigation user interfaces, etc.) without requiring the mobile device110to transmit its location to any external server120. In step404, the mobile device navigation system200may determine a current orientation of the mobile device110, based on analyses of the image data captured at the mobile device110, the current location of the mobile device110, and/or the map information received for the current location of the mobile device110. In some embodiments, the orientation determination may be performed by an image-based heading estimation component222within an AR system220executing on the mobile device110. For example, the image-based heading estimation component222may initially plot the current location of the mobile device110within the map information received in step403. The heading estimation component222then may use the map information to determine one or more physical objects that are (or should be) currently nearby to the mobile device110. The heading estimation component222then may compare the image data captured at the mobile device110in step401, to the characteristics of the physical objects identified within the map data at or near the current location. In some embodiments, such comparisons may include analyzing the image data captured at the mobile device110to detect line segments, shapes, and other recognizable objects, and then comparing those objects to the nearby physical objects identified within the map data. As noted above, image-matching comparisons also may be performed, between the image data captured at the mobile device110and map data images (e.g., previous street view images, satellite images, image libraries, etc.) within the map information received from one or more map servers120. The analyses in step404may include detecting any discernable object within the image data captured at the mobile device110, determining the properties of such objects, and then attempting to match the objects to the nearby physical objects identified within the map data. In various examples, the object matching may be based on object shapes, sizes, colors, relationships between objects, or any other detectable patterns within the image data. In certain examples, the image-based heading estimation component222may analyze the image data captured by the mobile device110to detect a street, sidewalk, or walking/biking path within the capture image data. These objects may be detected by identifying parallel or near-parallel line segments corresponding to street boundaries, curbs, sidewalk lines or boundaries, and/or painted lines within streets. Based on the directions (or trajectories) of the line segments, the estimation component222may determine the orientation of the mobile device110with respect to a street, sidewalk, or path (or to a particular segment of a street, sidewalk, or path). Based on the angles or distances between the parallel or near-parallel line segments, the estimation component222also may determine the distance between the mobile device110and the street, sidewalk, or path, etc. The estimation component222then may identify the corresponding street, sidewalk, or path within from the map information, for example, comparing the location, direction, width, curve pattern, or other distinguishing characteristics of the street, sidewalk, or path. Finally, estimation component222may determine the current orientation of the mobile device110based on (1) the direction (or street vector) of the street, sidewalk, or path segment, which is stored within the map information, and (2) the relative orientation of the mobile device110to the street, sidewalk, or path segment, which may be determined by analysis of the captured image data. In some embodiments, the heading estimation component222also may analyze images to detect the vanishing point for parallel or near-parallel street boundaries, sidewalk lines, or railroad tracks, etc., may use the compare the direction of the vanishing point from the perspective of the mobile device110, to the direction of the street, path, railroad tracks, etc., within the map information to determine the current orientation of the mobile device110. In other examples, the image-based heading estimation component222may analyze the image data captured by the mobile device110to detect buildings or other landmarks, and may compare the buildings or landmarks to the corresponding objects in the map information to determine the current orientation of the mobile device110. For example, estimation component222may identify the characteristics of a nearby building or landmark (e.g., size, shape, location, or orientation), in order to match the building or landmark to the corresponding object within the map information. After matching the building or landmark to an object within the map information, the heading estimation component222may determine the current orientation of the mobile device110based on (1) the position and orientation of the object stored within the map information, and (2) the relative orientation of the mobile device110to the object (or at least one surface of the object) within captured image data. In addition to matching nearby buildings or other landmarks to corresponding objects within the map information, the heading estimation component222also may identify distant objects within the image data captured by the device, as long as the location and/or heading of those distant objects is known or can be determined. For instance, the heading estimation component222may identify the sun, moon, horizon line, or other distant landmarks (e.g., a mountain, body of water, radio tower, aircraft warning light tower, etc.) within the image data captured by the mobile device110, to determine the current orientation of the mobile device using similar techniques to those described above. Regardless of the type of physical object used to orient the mobile device110, the steps of the process may include matching the physical object within the image data captured by the mobile device110to a corresponding object in the received map information, determine the absolute orientation of the object from the received map information, and then determine the current orientation of the mobile device based on the absolute orientation of object and the relative orientation of the mobile device110with respect to the object. In some embodiments, data from an internal compass of the mobile device110also may be used in the device orientation determination in step404. As noted above, compass data from a mobile device110might be inaccurate or unreliable in some cases. However, heading estimation component222potentially may use the compass data in a limited manner, for example, to determine the general direction where the device is pointed (e.g., within a range of 90 degrees, or 180 degrees, etc.) which may be used as a starting point for the image analysis and object comparison processes. Although the above examples relate to determining the current orientation of the mobile device110, similar techniques may be used to determine the current location of the mobile device110. As noted above, the location data (or location information) received via the location/positioning system250of the mobile device110potentially may be inaccurate or imprecise. For instance, based on signal interference, erroneous readings, or design limitations of the location/positioning technologies, the current device location received in step402may be inaccurate by anywhere from a few feet to a half-mile or more. In these cases, the current location data determined in step402may be sufficiently accurate to allow the mobile device navigation system200to request the appropriate map tiles/map information, but might not be sufficiently accurate for the map/navigation mobile application210. Accordingly, step404also may include performing similar image processing and object comparison steps to determine the current location of the mobile device110. For example, a location estimator252within location/positioning system250and/or within the AR system220may match one or more physical objects within the image data captured by the mobile device110, to corresponding objects in the received map information. The location estimator252then may determine or estimate the distance between the mobile device110and one or more physical objects, for example, by using the size of an object and the angles between the object's edges to compute a straight line distance between the mobile device110and the object. The current location of the mobile device110may then be calculated using the absolute locations of the objects, which is stored in the map information, and the distances between the mobile device110and the same objects. For instance, the absolute location of the mobile device110may be determined by triangulation using distances to two or more objects, or based on a determined distance and orientation to one or more objects. In certain embodiments, the mobile device navigation system200may use techniques similar to determining device orientation and/or location discussed above, to determine when the mobile device110is at street-level, above street-level, or below street-level. For example, the analysis of the image data captured by the mobile device110may include detecting up-angles or down-angles with respect to the physical objects nearby. When the map information confirms that those physical objects are at street level, the pedestrian navigation system200may determine the vertical positioning of the mobile device110above or below street level. In step405, the components of the mobile device navigation system200may use the determinations of the device orientation and device location in step404, to select and positon the user interface elements to be presented via the map/navigation application210. In some embodiments, the generation of the user interface for the map/navigation application210may be performed wholly by the map/navigation application210itself. In other embodiments, for instance, an augmented reality (AR)-based pedestrian navigation system is provided via the map/navigation application210, then a separate AR system220may be used to select and positon the user interface elements to be presented via the AR-based interface. As noted above, when the map/navigation application210is a pedestrian navigation application, or may be configured to operate in a pedestrian navigation mode (unlike when operating in a driving navigation mode), the orientation of the mobile device110may determine the display generated for the user interface. For instance, if a pedestrian using the navigation application210turns the mobile device110while staying in the same location, the user interface may be updated to display the new set of streets, buildings, and other objects that are now in front of the mobile device110. Pedestrian navigation systems which update the display based on the orientation of the mobile device110may include both augmented reality (AR) navigation systems and graphical non-AR navigation systems. AR pedestrian navigation systems may display real-time image data captured from a front-facing camera of the mobile device110, overlaid with labels and other graphical components to provide the navigation functionality to the user. Both the selection of graphical components (e.g., graphical streets and objects, labels, direction windows, turn indicators, etc.) and the particular positioning of the graphical components may be based on the device orientation and/or location data determined in step404. Initially, based on the device location and orientation, the app/navigation mobile application210and/or the AR system220may determine which physical objects are directly in front of and in view of the mobile device110. For fully graphical (non-AR) user interfaces, these physical objects (e.g., streets, buildings, natural landmarks, etc.) the mobile application210may determine the size, location, and screen location of these components to correspond to the user's current perspective. For AR and non-AR user interfaces, labels may be generated for each physical object rendered in the user interface, and the size and placement of the labels may be selected to match the size and orientation of the rendered object. For AR-based pedestrian navigation applications, the camera image data displayed in the AR interface may analyzed to identify the particular physical objects currently shown in the image (e.g., streets, buildings, etc.), and the AR system220may generate object labels to be rendered onto the screen at the appropriate size, placement position, and orientation on the image of the object. In addition to labeling the physical objects shown in the interface, the map/navigation application210may provide map- or navigation-related functionality with additional components, including displaying the user's current location, the destination location and anticipated time of arrival, turn-by-turn navigation instructions, etc. In some embodiments, the mobile application210and/or the AR system220may determine the size and placement of the graphical user interface components, based on the representations of the physical objects within the user interface. For example, directional instruction windows, arrows, and the like, may be positioned on the screen and sized appropriately so as not to obscure street signs, traffic signals, oncoming moving objects, etc. Additionally, the AR system220also may select contrasting colors to be used for labeling objects and for other user interface components to be overlaid within the AR-based pedestrian navigation user interface. For example, street and building labels, arrows, and directional instructions may be rendered in a light color during nighttime use of the pedestrian navigation system, etc. In step406, the map/navigation user interface may be generated and rendered by the mobile application210onto a display screen of the mobile device110. As discussed above, various techniques described herein may be applied to location mapping only applications, as well as navigation applications, and for augmented reality user interfaces as well as graphical non-AR user interfaces. Accordingly, the map/navigation user interface generated and rendered in step406may include map-specific and/or navigation-specific user interface elements as appropriate, and may or may not be rendered as an augmented reality user interface. For instance, the techniques described herein also may be applied to any augmented reality application, to allow that application to provide geo-referenced augmented reality content. FIGS.5-7show three example display screens of a navigation user interface according to embodiments of the present disclosure. InFIG.5, a mobile device110is shown rendering an augmented reality user interface500generated by a pedestrian navigation system. In this example, the augmented reality user interface500includes an AR window510displaying the real-time image data captured via the mobile device's front-facing camera, and an overlay window515with graphical components displaying the current directional instruction516for the user, and an overhead map view517of the user's current position and route. As shown in this example, the current directional instruction (i.e., “Turn Around”) has been selected and displayed based on the user's current orientation and location. InFIG.6, the user has turned around and the user interface600has been updated based on the new orientation detected for the mobile device110. In this example, the overhead map view617has been updated to reflect the orientation, and the instruction to turn around has been replace with a separate graphical window616informing the user of the upcoming turn according to the current route. Finally, inFIG.7, the pedestrian is approaching the destination and both the overhead map view717and the directional instruction window716have been updated accordingly. FIG.8illustrates components of a pedestrian navigation system800according to at least one embodiment. System800may include user device802and/or service provider computer(s)804that may communicate with one another via network(s)806utilizing any suitable communications protocol. In some examples, the network(s)806may include any one or a combination of many different types of networks, such as cable networks, the Internet, wireless networks, cellular networks, and other private and/or public networks. While the illustrated example represents the user device802communicating with the service provider computer(s)804over the network(s)806, the described techniques may equally apply in instances where the user device802interacts with the service provider computer(s)804over a landline phone, via a kiosk, or in any other suitable manner. It should be appreciated that the described techniques may apply in other client/server arrangements, as well as in non-client/server arrangements (e.g., locally stored applications, etc.). For example, in some embodiments, the geoservices module854and/or navigation module856, discussed below in more detail, may operate in whole or in part on the user device802. Additionally, the user device802may access the functionality of the geoservices module854and/or navigation module856through components of the user device802(e.g., the map application module858), and/or the service provider computer(s)804via user interfaces and/or APIs provided by the geoservices module854and/or navigation module856. As noted above, the user device802may be configured to execute or otherwise manage applications or instructions for presenting a user interface (e.g., the user interfaces500,600, and700ofFIGS.5-7) for providing map data and pedestrian navigation data using an augmented reality overlay. The user device802may be any type of computing device such as, but not limited to, a mobile phone (e.g., a smartphone), a tablet computer, a personal digital assistant (PDA), a laptop computer, a desktop computer, a thin-client device, a smart watch, a wireless headset, or the like. In one illustrative configuration, the user device802may include at least one memory820and one or more processing units (or processor(s))822. The processor(s)822may be implemented as appropriate in hardware, computer-executable instructions, or combinations thereof. Computer-executable instruction or firmware implementations of the processor(s)822may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described. The memory820may store program instructions that are loadable and executable on the processor(s)822, as well as data generated during the execution of these programs. Depending on the configuration and type of the user device802, the memory820may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.). The user device802may also include additional removable storage and/or non-removable storage824including, but not limited to, magnetic storage, optical disks, and/or tape storage. The disk drives and their associated non-transitory computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computing devices. In some implementations, the memory820may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), or ROM. While the volatile memory described herein may be referred to as RAM, any volatile memory that would not maintain data stored therein once unplugged from a host and/or power would be appropriate. The memory820and the additional storage824, both removable and non-removable, are all examples of non-transitory computer-readable storage media. For example, non-transitory computer readable storage media may include volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. The memory820and the additional storage824are both examples of non-transitory computer storage media. Additional types of computer storage media that may be present in the user device802may include, but are not limited to, phase-change RAM (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital video disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the user device802. Combinations of any of the above should also be included within the scope of non-transitory computer-readable storage media. Alternatively, computer-readable communication media may include computer-readable instructions, program modules, or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, computer-readable storage media does not include computer-readable communication media. The user device802may also contain communications connection(s)826that allow the user device802to communicate with a data store, another computing device or server, user terminals and/or other devices via one or more networks. Such networks may include any one or a combination of many different types of networks, such as cable networks, the Internet, wireless networks, cellular networks, satellite networks, other private and/or public networks, or any combination thereof. The user device802may also include I/O Device(s)828, such as a touch input device, an image capture device, a video capture device, a keyboard, a mouse, a pen, a voice input device, a display, a speaker, a printer, etc. Turning to the contents of the memory820in more detail, the memory820may include an operating system830and/or one or more application programs or services for implementing the features disclosed herein. The memory820may include data store832which may be configured to store map data (e.g., map tiles) and/or navigation data (e.g., turn-by-turn directions) to be used by a map application module858providing vehicle and/or pedestrian navigation functionality on the user device802. In some examples, the map application module858may be configured to provide the user interfaces500,600, and700at the user device802(e.g., at a display of the I/O Device(s)828). As part of providing user interfaces500-700, the map application module858may be configured to retrieve map tiles and/or navigation data (e.g., from data store832), and to access an augmented reality module (e.g., AR Kit) for presenting an augmented reality overlay incorporating the map and/or navigation data within the user interfaces500-700. In some aspects, the service provider computer(s)804may be any suitable type of computing devices such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (PDA), a laptop computer, a desktop computer, a server computer, a thin-client device, a tablet PC, etc. Additionally, it should be noted that in some embodiments, the service provider computer(s)804are executed by one more virtual machines implemented in a hosted computing environment. The hosted computing environment may include one or more rapidly provisioned and released computing resources, which computing resources may include computing, networking and/or storage devices. A hosted computing environment may also be referred to as a cloud-computing environment. In some examples, the service provider computer(s)804may be in communication with the user device802via the network(s)806. The service provider computer(s)804may include one or more servers, perhaps arranged in a cluster, as a server farm, or as individual servers not associated with one another. These servers may be configured to implement the functionality described herein as part of an integrated, distributed computing environment. In one illustrative configuration, the service provider computer(s)804may include at least one memory840and one or more processing units (or processor(s))842. The processor(s)842may be implemented as appropriate in hardware, computer-executable instructions, firmware, or combinations thereof. Computer-executable instruction or firmware implementations of the processor(s)842may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described. The memory840may store program instructions that are loadable and executable on the processor(s)842, as well as data generated during the execution of these programs. Depending on the configuration and type of service provider computer(s)804, the memory840may be volatile (such as RAM) and/or non-volatile (such as ROM, flash memory, etc.). The service provider computer(s)804or servers may also include additional storage844, which may include removable storage and/or non-removable storage. The additional storage844may include, but is not limited to, magnetic storage, optical disks and/or tape storage. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computing devices. In some implementations, the memory840may include multiple different types of memory, such as SRAM, DRAM, or ROM. The memory840, the additional storage844, both removable and non-removable, are all examples of computer-readable storage media. For example, computer-readable storage media may include volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. The memory840and the additional storage844are all examples of computer storage media. Additional types of computer storage media that may be present in the service provider computer(s)804may include, but are not limited to, PRAM, SRAM, DRAM, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, DVD or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the service provider computer(s)804. Combinations of any of the above should also be included within the scope of computer-readable media. Alternatively, computer-readable communication media may include computer-readable instructions, program modules, or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, computer-readable storage media does not include computer-readable communication media. The service provider computer(s)804may also contain communications connection(s)846that allow the service provider computer(s)804to communicate with a stored database, another computing device (e.g., the user device802) or server, user terminals and/or other devices on the network(s)806. The service provider computer(s)804may also include I/O device(s)848, such as a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, speakers, a printer, etc. Turning to the contents of the memory840in more detail, the memory840may include an operating system850, one or more data stores852, and/or one or more application programs, modules, or services for implementing the features disclosed herein, such as the features provided by the geoservices module854and the navigation model856. In at least one embodiment, the geoservices module854may be configured to perform any operation described in connection with the geoservices models discussed above inFIGS.2-3, including receiving and responding to requests for map data (e.g., map tiles) and/or satellite image data corresponding to geographic locations or ranges. The navigation model856, which may be implemented within the geoservices module854or a separate module, may be configured to receive and respond to requests for point-to-point directions, using route optimization algorithms based on a mode of transportation (e.g., walking, bicycling, driving, etc.), map data (e.g., road segments, sidewalk, path, or trail data, etc.), current traffic conditions and historical traffic patterns, etc. The user device802may be configured with a map application module858and an augmented reality module860that provides the user with an augmented reality-based pedestrian navigation system. Although not illustrated inFIG.8, the user device802also may include additional underlying hardware and software components and modules to support the pedestrian navigation functionality, including locational components (e.g., GPS receiver), orientation components (e.g., compass), media components (e.g., one or more device cameras), and motion detection components (e.g., accelerometer, gyroscope, etc.). As described above, these components of the user device802may be used in conjunction with the map application module858and augmented reality module860to determine updated orientation data and/or location data to be used by the AR pedestrian navigation system. By way of example, a user may initiate a pedestrian navigation feature on a user device802(e.g., a smartphone, tablet, wearable device, etc.) with image capture functionality/hardware, location functionality/hardware, and orientation functionality/hardware. The user device802may capture image data, location data, and/or orientation data from these components, and analyze the data in conjunction with the map data received from the service provider computers804. Based on analyses techniques that may be performed within the various modules of the user device802, updated orientation data and/or location data may be determined for the user device802. The map application858may provide AR pedestrian navigation functionality which based on the updated orientation data and/or location data. In some embodiments, some or all of the operations described herein can be performed using an application executing on the user's device. Circuits, logic modules, processors, and/or other components may be configured to perform various operations described herein. Those skilled in the art will appreciate that, depending on implementation, such configuration can be accomplished through design, setup, interconnection, and/or programming of the particular components and that, again depending on implementation, a configured component might or might not be reconfigurable for a different operation. For example, a programmable processor can be configured by providing suitable executable code; a dedicated logic circuit can be configured by suitably connecting logic gates and other circuit elements; and so on. Any of the software components or functions described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C, C++, C#, Objective-C, Swift, or scripting language such as Perl or Python using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer readable medium for storage and/or transmission. A suitable non-transitory computer readable medium can include random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium, such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like. The computer readable medium may be any combination of such storage or transmission devices. Computer programs incorporating various features of the present disclosure may be encoded on various computer readable storage media; suitable media include magnetic disk or tape, optical storage media, such as compact disk (CD) or DVD (digital versatile disk), flash memory, and the like. Computer readable storage media encoded with the program code may be packaged with a compatible device or provided separately from other devices. In addition, program code may be encoded and transmitted via wired optical, and/or wireless networks conforming to a variety of protocols, including the Internet, thereby allowing distribution, e.g., via Internet download. Any such computer readable medium may reside on or within a single computer product (e.g. a solid state drive, a hard drive, a CD, or an entire computer system), and may be present on or within different computer products within a system or network. A computer system may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user. A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary. The use of “or” is intended to mean an “inclusive or,” and not an “exclusive or” unless specifically indicated to the contrary. Reference to a “first” component does not necessarily require that a second component be provided. Moreover reference to a “first” or a “second” component does not limit the referenced component to a particular location unless expressly stated. The term “based on” is intended to mean “based at least in part on.” All patents, patent applications, publications, and descriptions mentioned herein are incorporated by reference in their entirety for all purposes. None is admitted to be prior art Further, as described above, one aspect of the present technology is the gathering and use of data available from various sources to improve suggestions of applications and/or people to share content from a host application. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter ID's, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information. The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to determine application and people suggestions for sharing content that is of greater interest to the user. Accordingly, use of such personal information data enables users to more efficiently control sharing of content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals. The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of sharing of content objects, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users may select not to provide data corresponding to their previous interactions with various applications, along with their sharing preferences and/or historical user interactions. In yet another example, users can select to limit the length of time that previous application interactions and sharing data is maintained or entirely prohibit the collection and tracking of such data. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app. Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods. Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, suggestions for sharing applications and people may be selected and provided to users based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content sharing systems, or publicly available information. | 63,379 |
11943680 | The figures depict various embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein. DETAILED DESCRIPTION Environment Overview Embodiments described herein detail functionality associated with a tracking device. A user can attach a tracking device to or enclose the tracking device within an object, such as a wallet, keys, a car, a bike, a pet, or any other object that the user wants to track. The user can then use a mobile device (e.g., by way of a software application installed on the mobile device) or other device or service to track the tracking device and corresponding object. For example, the mobile device can perform a local search for a tracking device attached to a near-by object. However, in situations where the user is unable to locate the tracking device using their own mobile device (e.g., if the tracking device is beyond a distance within which the mobile device and the tracking device can communicate), the user can leverage the capabilities of a community of users of a tracking device system. In particular, a tracking system (also referred to herein as a “cloud server” or simply “server”) can maintain user profiles associated with a plurality of users of the tracking device system. The tracking system can associate each user within the system with one or more tracking devices associated the user (e.g., tracking devices that the user has purchased and is using to track objects owned by the user). If the user's object becomes lost or stolen, the user can send an indication that the tracking device is lost to the tracking system, which is in communication with one or more mobile devices associated with the community of users in communication with the system. The tracking system can set a flag indicating the tracking device is lost. When one of a community of mobile devices that are scanning for nearby tracking devices and providing updated locations to the tracking system identifies a flagged tracking device, the tracking system can associate the received location with the flagged tracking device, and relay the location to a user of the tracking device, thereby enabling the user to locate the lost tracking device. FIG.1illustrates an example tracking system environment in which a tracking device can operate, according to one embodiment. The environment ofFIG.1includes a tracking system100communicatively coupled to a mobile device102associated with the user103via a first network108. The tracking system100is also communicatively coupled to a plurality of community mobile devices104athrough104n(collectively referred to herein as “community mobile devices104”) associated with a plurality of users105athrough105nof the tracking system100(collectively referred to herein as “community users105”) via the first network108. As will be explained in more detail below, the tracking system100can allow the user103to manage and/or locate a tracking device106associated with the user103. In some embodiments, the tracking system100leverages the capabilities of community mobile devices104to locate the tracking device106if the location of the tracking device is unknown to the user103and beyond the capabilities of mobile device102to track. In some configurations, the user103may own and register multiple tracking devices106. AlthoughFIG.1illustrates a particular arrangement of the tracking system100, mobile device102, community mobile devices104, and tracking device106, various additional arrangements are possible.FIG.1also illustrates an external data source112that is communicatively coupled to the tracking system100to provide additional, external data to the tracking system100, as is discussed further below. Examples of external data sources include: social networking systems, messaging systems, calendaring systems, banking systems, budgeting systems, vendor systems, online retailers, parking regulation databases, weather service, travel agency, transportation services, ride-sharing systems, geo-locating systems, contact management systems, and the like. In some configurations, the user103may be part of the community of users105. Further, one or more users105may own and register one or more tracking devices106. Thus, any one of the users within the community of users105can communicate with tracking system100and leverage the capabilities of the community of users105in addition to the user103to locate a tracking device106that has been lost. The tracking system100, mobile device102, and plurality of community mobile devices104may communicate using any communication platforms and technologies suitable for transporting data and/or communication signals, including known communication technologies, devices, media, and protocols supportive of remote data communications. In certain embodiments, the tracking system100, mobile device102, and community mobile devices104may communicate via a network108, which may include one or more networks, including, but not limited to, wireless networks (e.g., wireless communication networks), mobile telephone networks (e.g., cellular telephone networks), closed communication networks, open communication networks, satellite networks, navigation networks, broadband networks, narrowband networks, the Internet, local area networks, and any other networks capable of carrying data and/or communications signals between the tracking system100, mobile device102, and community mobile devices104. The mobile device102and community of mobile devices104may also be in communication with a tracking device106via a second network110. The second network110may be a similar or different type of network as the first network108. In some embodiments, the second network110comprises a wireless network with a limited communication range, such as a Bluetooth or Bluetooth Low Energy (BLE) wireless network. In some configurations, the second network110is a point-to-point network including the tracking device106and one or more mobile devices that fall within a proximity of the tracking device106. In such embodiments, the mobile device102and community mobile devices104may only be able to communicate with the tracking device106if they are within a close proximity to the tracking device, though in other embodiments, the tracking device can use long-distance communication functionality (for instance, a GSM transceiver) to communicate with either a mobile device102/104or the tracking system100at any distance. In some configurations, the mobile device102and one or more community mobile devices104may each be associated with multiple tracking devices associated with various users. As mentioned above,FIG.1illustrates the mobile device102associated with the user103. The mobile device102can be configured to perform one or more functions described herein with respect to locating tracking devices (e.g., tracking device106). For example, the mobile device102can receive input from the user103representative of information about the user103and information about a tracking device106. The mobile device102may then provide the received user information, tracking device information, and/or information about the mobile device102to the tracking system100. Accordingly, the tracking system100is able to associate the mobile device102, the user103, and/or the tracking device106with one another. In some embodiments, the mobile device102can communicate with the tracking device106and provide information regarding the location of the tracking device to the user103. For example, the mobile device102can detect a communication signal from the tracking device106(e.g., by way of second network110) as well as a strength of the communication signal or other measure of proximity to determine an approximate distance (and/or a relative direction) between the mobile device102and the tracking device106. The mobile device102can then provide this information to the user103(e.g., by way of one or more graphical user interfaces) to assist the user103to locate the tracking device106. Accordingly, the user103can use the mobile device102to track and locate the tracking device106and a corresponding object associated with the tracking device106. If the mobile device102is located beyond the immediate range of communication with the tracking device106(e.g., beyond the second network110), the mobile device102can be configured to send an indication that a tracking device106is lost to the tracking system100, requesting assistance in finding the tracking device. The mobile device102can send an indication of a lost device in response to a command from the user103. For example, once the user103has determined that the tracking device106is lost, the user can provide user input to the mobile device102(e.g., by way of a graphical user interface), requesting that the mobile device102send an indication that the tracking device106is lost to the tracking system100. In some examples, the lost indication can include information identifying the user103(e.g., name, username, authentication information), information associated with the mobile device102(e.g., a mobile phone number), information associated with the tracking device (e.g., a unique tracking device identifier), or a location of the user (e.g., a GPS location of the mobile device102at the time the request is sent). The tracking system100can be configured to provide a number of features and services associated with the tracking and management of a plurality of tracking devices and/or users associated with the tracking devices. For example, the tracking system100can manage information and/or user profiles associated with user103and community users105. In particular, the tracking system100can manage information associated with the tracking device106and/or other tracking devices associated with the user103and/or the community users105. As mentioned above, the tracking system100can receive an indication that the tracking device106is lost from the mobile device102. The tracking system100can then process the indication in order to help the user103find the tracking device106. For example, the tracking system100can leverage the capabilities of the community mobile devices104to help find the tracking device106. In particular, the tracking system100may set a flag for a tracking device106to indicate that the tracking device106lost and monitor communications received from the community mobile devices104indicating the location of one or more tracking devices106within proximity of the community mobile devices104. The tracking system100can determine whether a specific location is associated with the lost tracking device106and provide any location updates associated with the tracking device106to the mobile device102. In one example, the tracking system may receive constant updates of tracking device106locations regardless of whether a tracking device106is lost and provide a most recent updated location of the tracking device106in response to receiving an indication that the tracking device106is lost. In some configurations, the tracking system100can send a location request associated with the tracking device106to each of the community mobile devices104. The location request can include any instructions and/or information necessary for the community mobile devices106to find the tracking device102. For example, the location request can include a unique identifier associated with the tracking device106that can be used by the community mobile devices104to identify the tracking device106. Accordingly, if one of the community mobile devices104detects a communication from the tracking device106(e.g., if the community mobile device104is within range or moves within range of the communication capabilities of the tracking device106and receives a signal from the tracking device106including or associated with the unique identifier associated with the tracking device106), the community mobile device104can inform the tracking system100. Using the information received from the community mobile devices104, the tracking system100can inform the user (e.g., by way of the mobile device102) of a potential location of the tracking device106. As shown inFIG.1and as mentioned above, the tracking system100can communicate with a plurality of community mobile devices104associated with corresponding community users105. For example, an implementation may include a first community mobile device104aassociated with a first community user105a, a second community mobile device104bassociated with a second community user105b, and additional communication mobile devices associated with additional community users up to an nth community mobile device104nassociated with an nth community user105n. The community mobile devices104may also include functionality that enables each community mobile device104to identify a tracking device106within a proximity of the community mobile device104. In one example, a first community mobile device104awithin proximity of a tracking device106can communicate with the tracking device106, identify the tracking device106(e.g., using a unique identifier associated with the tracking device106), and/or detect a location associated with the tracking device106(e.g., a location of the first mobile community device104aat the time of the communication with the tracking device106). This information can be used to provide updated locations and/or respond to a location request from the tracking system100regarding the tracking device106. In some embodiments, the steps performed by the first community mobile device104acan be hidden from the first community user105a. Accordingly, the first community mobile device104acan assist in locating the tracking device106without bother and without the knowledge of the first community user105a. As mentioned above, the tracking system100can assist a user103in locating a tracking device106. The tracking device may be a chip, tile, tag, or other device for housing circuitry and that may be attached to or enclosed within an object such as a wallet, keys, purse, car, or other object that the user103may track. Additionally, the tracking device106may include a speaker for emitting a sound and/or a transmitter for broadcasting a beacon. In one configuration, the tracking device106may periodically transmit a beacon signal that may be detected using a nearby mobile device102and/or community mobile device104. In some configurations, the tracking device106broadcasts a beacon at regular intervals (e.g., one second intervals) that may be detected from a nearby mobile device (e.g., community mobile device104). The strength of the signal emitted from the tracking device106may be used to determine a degree of proximity to the mobile device102or community mobile device104that detects the signal. For example, a higher strength signal would indicate a close proximity between the tracking device106and the mobile device102and a lower strength signal would indicate a more remote proximity between the tracking device106and the mobile device102, though in some embodiments, the tracking device106can intentionally vary the transmission strength of the beacon signal. In some cases, the strength of signal or absence of a signal may be used to indicate that a tracking device106is lost. System Overview FIG.2illustrates an example tracking system for use in a tracking system environment, according to one embodiment. As shown, the tracking system100may include, but is not limited to, an association manager204, a tracking device location manager206, a tracking device intervention manager207, and a data manager208, each of which may be in communication with one another using any suitable communication technologies. It will be recognized that although managers204-208are shown to be separate inFIG.2, any of the managers204-208may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment. The association manager204may be configured to receive, transmit, obtain, and/or update information about a user103and/or information about one or more specific tracking devices (e.g., tracking device106). In some configurations, the association manager204may associate information associated with a user103with information associated with a tracking device106. For example, user information and tracking information may be obtained by way of a mobile device102, and the association manager204may be used to link the user information and tracking information. The association between user103and tracking device106may be used for authentication purposes, or for storing user information, tracking device information, permissions, or other information about a user103and/or tracking device106in a database. The tracking system100also includes a tracking device location manager206. The tracking device location manager206may receive and process an indication that the tracking device106is lost from a mobile device (e.g., mobile device102or community mobile devices104). For example, the tracking system100may receive a lost indication from a mobile device102indicating that the tracking device106is lost. The tracking device location manager206may set a flag on a database (e.g., tracker database212) indicating that the tracking device106is lost. The tracking device location manager206may also query a database to determine tracking information corresponding to the associated user103and/or tracking device106. The tracking system100may obtain tracking device information and provide the tracking device information or other information associated with the tracking device106to a plurality of community mobile devices104to be on alert for the lost or unavailable tracking device106. The tracking device location manager206may also receive a location from one or more community mobile devices104that detect the tracking device106, for instance in response to the community mobile device receiving a beacon signal transmitted by the tracking device106, without the tracking device106having been previously marked as lost. In such embodiments, a user corresponding to the mobile device102can request a most recent location associated with the tracking device from the tracking system100, and the location manager206can provide the location received from the community mobile device for display by the mobile device102. In some embodiments, the location manager206provides the location of the tracking device106received from a community mobile device either automatically (for instance if the tracking device106is marked as lost) or at the request of a user of the mobile device102(for instance, via an application on the mobile device102). The location manager206can provide a location of a tracking device106to a mobile device102via a text message, push notification, application notification, automated voice message, or any other suitable form of communication. The tracking device location manager206may further manage providing indications about whether a tracking device106is lost or no longer lost. For example, as discussed above, the tracking device location manager206may provide a location request to the community of mobile devices104indicating that a tracking device106is lost. Additionally, upon location of the tracking device106by the user103or by one of the community of users105, the tracking device location manager206may provide an indication to the user103, community user105, or tracking system100that the tracking device106has been found, thus removing any flags associated with a tracking device and/or canceling any location request previously provided to the community of users105. For example, where a user103sends an indication that the tracking device106is lost to the tracking system100and later finds the tracking device106, the mobile device102may provide an indication to the tracking system100that the tracking device106has been found. In response, the tracking device location manager206may remove a flag indicating that the tracking device106is lost and/or provide an updated indication to the community of users105that the tracking device106has been found, thus canceling any instructions associated with the previously provided location request. In some configurations, the notification that the tracking device106has been found may be provided automatically upon the mobile device102detecting the tracking device106within a proximity of the mobile device102. Alternatively, the notification that the tracking device106has been found may be provided by the user103via user input on the mobile device102. In another example, a known user (e.g., a friend or family member) with whom the tracking device106has been shared may provide an indication that the tracking device106has been found. The tracking system100additionally includes a tracking device intervention manager207. The tracking device intervention manager207can identify whether a tracking device is lost or has been left behind, or can predict a state of the tracking device based on, for instance, the location of a tracking device relative to other tracking devices, the location of a tracking device relative to a user's phone, and the location of a tracking device relative to historical user data. When a device is determined to be lost or left behind, or when a state of the tracking device has been predicted, the tracking device intervention manager207can notify a user, for instance via a notification sent to and displayed by a mobile device102of the user. The tracking device intervention manager207is described below in greater detail. The tracking system100additionally includes a data manager208. The data manager208may store and manage information associated with users, mobile devices, tracking devices, permissions, location requests, and other data that may be stored and/or maintained in a database related to performing location services of tracking devices. As shown, the data manager208may include, but is not limited to, a user database210, a tracker database212, permissions data214, and location request data216. It will be recognized that although databases and data within the data manager208are shown to be separate inFIG.2, any of the user database210, tracker database212, permissions data214, and location request data216may be combined in a single database or manager, or divided into more databases or managers as may serve a particular embodiment. The data manager208may include the user database210. The user database210may be used to store data related to various users. For example, the user database210may include data about the user103as well as data about each user105in a community of users105. The community of users105may include any user that has provided user information to the tracking system100via a mobile device102,104or other electronic device. The user information may be associated with one or more respective tracking devices106, or may be stored without an association to a particular tracking device. For example, a community user105may provide user information and permit performance of tracking functions on the community mobile device104without owning or being associated with a tracking device106. The user database210may also include information about one or more mobile devices or other electronic devices associated with a particular user. The data manager208may also include a tracker database212. The tracker database212may be used to store data related to tracking devices. For example, the tracker database212may include tracking data for any tracking device106that has been registered with the tracking system100. Tracking data may include unique tracker identifications (IDs) associated with individual tracking devices106. Tracker IDs may be associated with a respective user103. Tracker IDs may also be associated with multiple users. Additionally, the tracker database212may include any flags or other indications associated with whether a specific tracking device106has been indicated as lost and whether any incoming communications with regard to that tracking device106should be processed based on the presence of a flag associated with the tracking device106. The data manager208may further include permissions data214and location request data216. Permissions data214may include levels of permissions associated with a particular user103and/or tracking device106. For example, permissions data214may include additional users that have been indicated as sharing a tracking device106, or who have been given permission to locate or receive a location of a tracking device106. Location request data216may include information related to a location request or a lost indication received from the user103via a mobile device102. FIG.3illustrates an example user mobile device for use in a tracking system environment, according to one embodiment. As shown, the mobile device102may include, but is not limited to, a user interface manager302, a location request manager304, a database manager306, a tracking manager308, and an intervention engine340, each of which may be in communication with one another using any suitable communication technologies. It will be recognized that although managers302-308are shown to be separate inFIG.3, any of the managers302-308may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment. As will be explained in more detail below, the mobile device102includes the user interface manager302. The user interface manager302may facilitate providing the user103access to data on a tracking system100and/or providing data to the tracking system100. Further, the user interface manager302provides a user interface by which the user103may communicate with tracking system100and/or tracking device106via mobile device102. For example, the user interface manager302can facilitate the providing of power settings to the tracking device106for power management on the tracking device106by the user103. The mobile device102may also include a location request manager304. The location request manager304may receive and process a request input to the mobile device102to send an indication that a tracking device106is lost to a tracking system100. For example, the user103may provide an indication that a tracking device106is lost, unreachable, or otherwise unavailable from the mobile device102via the user interface manager302, and the location request manager304may process the lost indication and provide any necessary data to the tracking system100for processing and relaying a location request to other users105over a network108. In some configurations, an indication that a tracking device106is lost is provided via user input. Alternatively, the indication may be transmitted automatically in response to the mobile device102determining that a tracking device106is lost. In addition, the location request manager304can request a location of the tracking device106without the tracking device106being identified as lost. For instance, a user can access a tracking device location feature of an application running on the mobile device102(for example, via the user interface manager302), and the location request manager304can request a most recent location of the tracking device106from the tracking system100. The location request manager304can receive the most recent location from the tracking system100, and can display the most recent location via the user interface manager302. The mobile device102may also include a database manager306. The database manager306may maintain data related to the user103, tracking device106, permissions, or other data that may be used for locating a tracking device106and/or providing a request to a tracking system100for locating one or more tracking devices106associated with the user103. Further, the database manager306may maintain any information that may be accessed using any other manager on the mobile device102. The mobile device102may further include a tracking manager308. The tracking manager308may include a tracking application (e.g., a software application) for communicating with and locating a tracking device106associated with the user103. For example, the tracking manager308may be one configuration of a tracking application installed on the mobile device102that provides the functionality for locating a tracking device106and/or requesting location of a tracking device106using a tracking system100and/or a plurality of community mobile devices104. As shown, the tracking manager308may include, but is not limited to, a Bluetooth Low Energy (BLE) manager310, a persistence manager312, a local files manager314, a motion manager316, a secure storage manager318, a settings manager320, a location manager322, a network manager324, a notification manager326, a sound manager328, a friends manager330, a photo manager332, an authentication manager334, and a device manager336. Thus, the tracking manager308may perform any of the functions associated with managers310-338, described in additional detail below. The BLE manager310may be used to manage communication with one or more tracking devices106. The persistence manager312may be used to store logical schema information that is relevant to the tracking manager308. The local files manager314may be responsible for managing all files that are input or output from the mobile device102. The motion manager316may be responsible for all motion management required by the tracking manager308. The secure storage manager318may be responsible for storage of secure data, including information such as passwords and private data that would be accessed through this sub-system. The settings manager320may be responsible for managing settings used by the tracking manager308. Such settings may be user controlled (e.g., user settings) or defined by the tracking manager308for internal use (e.g., application settings) by a mobile device102and/or the tracking system100. The location manager322may be responsible for all location tracking done by the tracking manager308. For example, the location manager322may manage access to the location services of the mobile device102and works in conjunction with other managers to persist data. The network manager324may be responsible for all Internet communications from the tracking manager308. For example, the network manager324may mediate all Internet API calls for the tracking manager308. The notification manager326may be responsible for managing local and push notifications required by the tracking manager308. The sound manager328may be responsible for playback of audio cues by the tracking manager308. The friends manager330may be responsible for managing access to contacts and the user's social graph. The photo manager332may be responsible for capturing and managing photos used by the tracking manager308. The authentication manager334may be responsible for handling the authentication (e.g., sign in or login) of users. The authentication manager334may also include registration (e.g., sign up) functionality. The authentication manager334further coordinates with other managers to achieve registration functionality. The device manager336may be responsible for managing the devices discovered by the tracking manager308. The device manager336may further store and/or maintain the logic for algorithms related to device discovery and update. The mobile device102may further include an intervention engine340. The intervention engine340is configured to, in response to a determination that a tracking device may be lost (or inadvertently left behind, misplaced, forgotten, stolen, etc.), notify a user that the tracking device may be lost or left behind. In some embodiments, the determination that the tracking device may be lost or left behind may be made by the tracking system100and communicated to the mobile device102, may be made by a different tracking device and communicated to the mobile device, or may be made by the intervention engine340. Likewise, the intervention engine340is configured to, in response to predicting a state of the tracking device, notify a user of the tracking device of the predicted state of the tracking device. The state of the tracking device can be predicted by the tracking system100and communicated to the mobile device102, or may be made by the intervention engine340. The intervention engine340can notify a user of the mobile device102that a tracking device may be lost or left behind, or can notify the user of the predicted state of the tracking device in a number of ways, for instance by displaying a notification within a graphical notification interface of the mobile device, by displaying a status or notification within an application interface of the mobile device, by emitting an alarm or notification audio, or the like. FIG.4illustrates an example community mobile device for use in a tracking system environment, according to one embodiment. As shown, the community mobile device104may include, but is not limited to, a user interface manager402, a tracking device manager404, a database manager406, and a tracking manager408, each of which may be in communication with one another using any suitable communication technologies. The user interface manager402, database manager406, and tracking manager408illustrated inFIG.4may include similar features and functionality as the user interface manager302, database manager306, and tracking manager308described above in connection withFIG.3. It will be recognized that although managers402-408are shown to be separate inFIG.4, any of the managers402-408may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment. The community mobile device104may include a tracking device manager404. The tracking device manager404may facilitate scanning for nearby tracking devices106. In some configurations, the tracking device manager404can continuously or periodically scan (e.g., once per second) for nearby tracking devices106. The tracking device manager404may determine whether to provide an updated location of the nearby tracking device106to the tracking system100. In some configurations, the tracking device manager404provides a location of a nearby tracking device106automatically. Alternatively, the tracking device manager404may determine whether the location of the tracking device106has been recently updated, and may determine whether to provide an updated location based on the last time a location of the tracking device106has been updated (e.g., by the community mobile device104). For example, where the community mobile device104has provided a recent update of the location of a tracking device106, the tracking device manager404may decide to wait a predetermined period of time (e.g., 5 minutes) before providing an updated location of the same tracking device106. In one configuration, the tracking device manager404may receive and process a location request or other information relayed to the community mobile device104by the tracking system100. For example, the tracking device manager404may receive an indication of a tracking device106that has been indicated as lost, and provide a location of the tracking device106if it comes within proximity of the community mobile device104. In some configurations, the community mobile device104is constantly scanning nearby areas to determine if there is a tracking device106within a proximity of the community mobile device104. Therefore, where a tracking device106that matches information provided by the tracking system100(e.g., from the location request) comes within proximity of the community mobile device104, the tracking device manager404may generate and transmit a response to the location request to the tracking system100, which may be provided to the user103associated with the tracking device106. Further, generating and transmitting the response to the tracking request may be conditioned on the status of the tracking device106being flagged as lost by the mobile device102and/or the tracking system100. The tracking device manager404may additionally provide other information to the tracking system100in response to receiving the tracking request. For example, in addition to providing a location of the community mobile device104, the tracking device manager may provide a signal strength associated with the location to indicate a level of proximity to the location of the community mobile device104provided to the user103. For example, if a signal strength is high, the location provided to the user103is likely to be more accurate than a location accompanied by a low signal strength. This may provide additional information that the user103may find useful in determining the precise location of tracking device106. As described above, the tracking device manager404may determine whether to send a location within the proximity of the tracking device106to the tracking system100. The determination of whether to send a location to the tracking system100may be based on a variety of factors. For example, a tracking device manager404may determine to send a location of the tracking device106to a tracking system100based on whether the detected tracking device106has been indicated as lost or if a tracking request has been provided to the community mobile device104for the particular tracking device106. In some configurations, the community mobile device104may send an update of a location of a tracking device106even if the tracking device106is not associated with a current tracking request or if the tracking device106is not indicated as lost. For example, where the location of a tracking device106has not been updated for a predetermined period of time, the community mobile device104may provide an update of a tracking device location to the tracking system100, regardless of whether a tracking request has been received. In some configurations, the community mobile device104may include additional features. For example, the community mobile device104may allow a tracking system100to snap and download a photo using photo functionality of the community mobile device104. In some configurations, this may be an opt-in feature by which a community user105permits a tracking system100to take a snap-shot and possibly provide a visual image of an area within a proximity of the tracking device106. FIG.5illustrates an example tracking device for use in a tracking system environment, according to one embodiment. The tracking device106ofFIG.5includes an interface502, a transceiver504, a controller506, and one or more sensors508. The transceiver504is a hardware circuit capable of both transmitting and receiving signals. It should be noted that in other embodiments, the tracking device106includes fewer, additional, or different components than those illustrated inFIG.5. The interface502provides a communicative interface between the tracking device106and one or more other devices, such as a mobile device102. For instance, the interface502can instruct the transceiver504to output beacon signals as described above (for example, periodically or in response to a triggering event, such as a detected movement of the tracking device106). The interface502can, in response to the receiving of signals by the transceiver504from, for instance, the mobile device102, manage a pairing protocol to establish a communicative connection between the tracking device106and the mobile device102. As noted above, the transceiver504can include a BLE receiver and transmitter, though in other embodiments, the transceiver504enables communications via other suitable wireless connection protocols (such as WiFi, Global System for Mobile Communications or “GSM”, LTE, and the like). It should be noted that while various examples herein describe the transceiver504as a GSM receiver and transmitter, this is done for the purposes of brevity, and it should be emphasized that the transceiver504can communicate over any other wireless communication protocol according to the embodiments described herein. The controller506is a hardware chip that configures the tracking device106to perform one or more functions or to operate in one or operating modes or states. For instance, the controller506can configure the interval at which the transceiver broadcasts beacon signals, can authorize or prevent particular devices from pairing with the tracking device106based on information received from the devices and permissions stored at the tracking device, can increase or decrease the transmission strength of signals broadcasted by the transceiver, can configure the interface to emit a ringtone or flash an LED light, can enable or disable various tracking device sensors, can enable or disable communicative functionality of the tracking device106, can configure the tracking device into a sleep mode or awake mode, can configure the tracking device into a power preservation mode, and the like. The controller506can configure the tracking device to perform functions or to operate in a particular operating mode based on information or signals received from a device paired with or attempting to pair with the tracking device106, based on an operating state or connection state of the tracking device106, based on user-selected settings, based on information stored at the tracking device106, based on a detected location of the tracking device106, based on historical behavior of the tracking device106(such as a previous length of time the tracking device was configured to operate in a particular mode), based on information received from the sensors508, or based on any other suitable criteria. The sensors508can include motion sensors (such as gyroscopes or accelerators), altimeters, GPS transceivers, orientation sensors, proximity sensors, communication sensors, light sensors, temperature sensors, pressure sensors, touch sensors, audio sensors, or any other suitable sensor configured to detect an environment of the tracking device106, a state of the tracking device106, a movement or location of the tracking device106, and the like. The sensors508are configured to provide information detected by the sensors to the controller506, which in turn can provide the information detected by the sensors to a mobile device102communicatively coupled to the tracking device106. Tracking Device Collection Overview Tracking devices can be organized into collections of tracking devices that are commonly co-located, that may move similarly, that are often kept close together, that are used similarly or for a common purpose, that are attached to related or similar objects, that are associated with a common subject matter, or that behave in a similar way. As used herein, a “collection” refers to a pre-determined set of tracking devices. Collections of tracking devices can include one, two, or more tracking devices, and the identities of each collection and the identities of the tracking devices within each collection can be stored within the tracker database212, within a mobile device102of a user associated with the collection, or any other suitable location. Tracking device collections can be defined by users. For instance, a user can create a collection via an application interface or other mobile device interface, via a web page interface associated with the tracking system100, or the like. The user can select a set of tracking devices owned or managed by the user, can associate with the selected tracking devices, and can name or otherwise identify the collection. For instance, the user can select tracking devices that are attached to objects needed by the user for the user's job, can create a collection of “work” tracking devices, and can name the collection, all via an application running on the user's mobile device102. The mobile device102can then communicate the defined collection to the tracking system100for storage. Alternatively, tracking device collections can be defined by the tracking system100, based on common historical behavior/usage patterns associated with a set of tracking devices. For instance, if a set of tracking devices (e.g., a first tracking device coupled to a user's wallet, a second to a user's ID badge, and a third to a user's briefcase) commonly accompanies a user from a home location to a work location weekday mornings, and likewise from the work location to the home location weekday evenings, the set of tracking devices can be grouped together in a tracking device collection. As described above, tracking devices are coupled to objects, and the user can identify to the tracking system100(for instance, via the mobile device102) the identity of the objects to which the tracking devices are attached. Accordingly, the tracking system100can define collections of tracking devices based on the identified types of objects to which a set of tracking devices are coupled. For example, if a user identifies an object to which a first tracking device is coupled as “luggage”, and identifies an object to which a second tracking device is coupled as “passport”, the tracking system100can define a “travel” tracking device collection based on a pre-determined likelihood that a user's luggage and passport are likely to be used together. In some embodiments, the tracking system100can identify a candidate tracking device collection (e.g., by identifying a set of tracking devices), and can present or suggest the candidate tracking device collection to a user (for instance, via the user's mobile device102). For example, the travel system100can identify a set of tracking devices that commonly move in conjunction with a user's car, and can suggest a candidate “car” tracking device collection to the user. If the user agrees to define a tracking device collection based on the presented candidate tracking device collection, the tracking system100can store the tracking device collection. In some embodiments, the tracking system100can identify a candidate tracking device likely to be related to a defined tracking device collection, and can present or suggest the candidate tracking device to the user to add to the tracking device collection. For example, if a user has defined a “travel” collection of tracking devices including a passport tracking device and luggage tracking device, and the tracking system100determines that a tracking device coupled to a camera bag is commonly co-located with the passport and luggage (or moves in conjunction with the passport and luggage), then the tracking system can suggest to the user (for instance, via the user's mobile device102) that the user add the camera bag to the travel tracking device collection. If the user accepts the suggestion and adds the suggested tracking device to the tracking device collection, the tracking system100can update the stored tracking device collection to include the suggested tracking device. In some embodiments, an interface of the user's mobile device (such as an application interface, a web page interface, and the like) can display one or more tracking device collections to the user. For instance, the mobile device can display a selectable icon, button, or display portion corresponding to the tracking device collection. When a user selects the tracking device collection, the mobile device can identify tracking devices within the selected tracking device collection, and can display information associated with the identified tracking devices within the collection (such as location information, status information, information about the object to which the tracking device is coupled, and the like). For instance, the user can select a “work” tracking device collection from an interface of the application associated with the tracking system100, and the application can display information associated with a first tracking device coupled to a user's keys, a second tracking device coupled to the user's ID badge, and a third tracking device coupled to the user's briefcase. Examples of tracking device collections include but are not limited to:Car accessory tracking devices: a wallet, glasses, spare tire, garage door remote control, parking pass, toll road/bridge payment sensor, keys, phone charger, jumper cables, car jack, auxiliary cableTravel tracking devices: luggage, phone charger, laptop charger, makeup/toiletry bag, passport, digital book/reader, computer, tablet, phone, camera, headphones, airpods, water bottle, jacket, pillowPurse tracking devices: purse, wallet, checkbook, keys, pillboxWork tracking devices: laptop, tablet, phone, ID badge, headphones, wallet, briefcaseSchool tracking devices: backpack, lunch bag, laptop, booksHome tracking devices: remote control, safe, jewelry box, tools, toolbox, artworkCamping tracking devices: tent, sleeping bags, headlamp, flashlight, lanterns, first aid kitSkiing/snowboarding tracking devices: skis, snowboard, coat, gloves, helmet, goggles, ski passGolf tracking devices: clubs, bag, shoes, hatSCUBA tracking devices: fins, mask, tank, wetsuit, flashlight, weight belt, buoyancy compensatorArt/antique tracking devices: tracking devices coupled to artwork or antiquesPhotography tracking devices: camera bag, camera, lenses, tripods, flash gearPublic tracking devices: tracking devices coupled to buses, food trucks, and the likeComputer/laptop accessories tracking devices: laptop, tablet, charger, dongle, mouse, keyboard, monitors, external hard drive, web cameraTool tracking devices: hammer, screwdriver, wrench, saw, safety glasses, tool boxEmergency supplies tracking devices: fire extinguisher, water containers, canned foods, flashlights, emergency radioBaby/child tracking devices: baby bag, diapers, toys, baby powder, baby wipes, books, car seat, stroller, clothesGym tracking devices: gym shoes, gym bag, extra clothes, towel, joint brace/supportBeach tracking devices: towel, sunscreen, beach umbrella, water bottle, surfboard, coolerRain-gear tracking devices: jacket, hat, poncho, umbrella, rain bootsSnow-gear tracking devices: jacket, hat, ear muffs, scarfWarm-weather tracking devices: sunscreen, sunglasses, sandals, water bottleValuable item tracking devices: Art, antique, television, jewelry/jewelry box, safe, monitor, computer Tracking Device Intervention Overview As used herein, a tracking device “intervention” can refer to notifying a user, owner, or manager of a tracking device that the tracking device may be lost, may be forgotten, or may be inadvertently left behind (collectively referred to as “potentially lost” hereinafter). In some embodiments, a tracking device intervention can refer to notifying a user of a predicted state or behavior of a tracking device (collectively referred to as “predicted state” hereinafter). In each case, a tracking device is either identified as potentially lost or a state of the tracking device is predicted, and in response, a notification is sent to a user of the tracking device. During the performance of a tracking device intervention, a user can be notified of the predicted state of the tracking device or that the tracking device is potentially lost via a mobile device102, for instance via a notification displayed within a mobile device or application interface, via an audio signal or vibration signal, and the like. As also noted above, any of the tracking system100, the mobile device102, or a tracking device106can identify a tracking device is potentially lost or can predict a state of the tracking device, though the remainder of the description will refer to the tracking system identifying a tracking device as potentially lost for the purposes of simplicity. A notification that a tracking device is potentially lost can include information about a last known location of the tracking device (for instance, displayed on a map displayed by a mobile device), can include information identifying the tracking device (such as a name of the tracking device, the identity of the object to which the tracking device is attached, or an icon corresponding to the tracking device), can include information identifying a tracking device collection to which the tracking device belongs (such as a name of the tracking device collection or an icon corresponding to the tracking device collection), and can include text indicating why the tracking device is thought to be lost or left behind (e.g., “you normally take your briefcase to work with you, and you left it behind today”). A notification of a predicted state of the tracking device can include information identifying the tracking device or a tracking device collection to which the tracking device belongs, can include information describing the predicted state of the tracking device (e.g., “you might want to bring this tracking device with you before you leave for work”), and can include information describing the circumstances under which the state of the tracking device is predicted (e.g., “it is warmer than normal outside today, don't forget to bring your water bottle”). In some embodiments, a notification of a predicted state of the tracking device or identifying a tracking device as potentially lost can include an option to disregard the notification. For instance, if the notification indicates that a tracking device is potentially lost, the user can select an option displayed by or associated with the notification to identify the tracking device as not lost. Likewise, if the notification indicates a predicted state of the tracking device reminding a user to bring an object coupled to a particular tracking device, the user can select an option displayed by or associated with the notification to disregard the reminder. Likewise, in some embodiments, a notification that a tracking device is identified as potentially lost can include an option to confirm the tracking device as lost. In response to the selection of such an option by a user, the tracking system100can affirmatively classify the tracking device as lost according to the principles described herein. The tracking system100can identify a tracking device106as potentially lost or can predict a future state of the tracking device based on a number of factors, including but not limited to: a proximity of a tracking device to one or more additional tracking devices, a proximity of a tracking device to a user's mobile device, a movement of a tracking device to more than a threshold distance away from a mobile device or one or more additional tracking devices, a location of a tracking device relative to a particular or pre-defined geographic location (such as GPS coordinates, a user's home, a user's place of employment, etc.), a location of a tracking device relative to particular or pre-defined geographic boundaries (such as boundaries within a map, property lines, and the like), based on a usage or movement behavior of the tracking device, based on a usage or movement behavior of a user or owner of a tracking device, based on information received from an external source (for instance, via an API corresponding to the API), based on information received from sensors within the tracking device or a user's mobile device (such as motion sensors), based on a current time or date, based on a low battery level, based on a malfunction of the tracking device or a tracking device component, or based on any other suitable factors. Circumstances in which the tracking system100can identify a tracking device106as potentially lost or can predict a state of the tracking device are described in greater detail below. Tracking device proximity: The tracking system100can identify a tracking device106as potentially lost in response to determining that the tracking device is not located within a threshold distance (such as a wireless communicative range, a selected threshold distance, or a pre-determined distance) of a target device (such as a user's mobile device or of one or more additional tracking devices). For instance, if a tracking device is commonly located within a threshold distance of a user's mobile device, the tracking system100can flag the tracking device as potentially lost in response to a determination that the tracking device is located outside the threshold distance of the user's mobile device. In addition, if a tracking device is commonly located within a threshold distance of a second tracking device, the tracking system can flag the tracking device as potentially lost in response to a determination that the tracking device is located more than a threshold distance away from the second tracking device. Likewise, if a tracking device is part of a tracking device collection, the tracking system100can flag the tracking device as potentially lost in response to a determination that the tracking device is located more than a threshold distance away from one or more additional tracking devices within the tracking device collection. It should be noted that the determination that a tracking device is potentially lost in response to proximity to another tracking device, a tracking device collection, or a user's mobile device can be based on time. For instance, if two tracking devices are commonly located within a threshold distance of each other during normal work hours for a user, but aren't commonly located within the threshold distance of each other outside of work hours, the tracking system100may flag a first of the tracking devices as potentially lost only if the first tracking device is located more than the threshold distance from the second tracking device during work hours, and may not flag the first tracking device as potentially lost if the first tracking device is located more than the threshold distance from the second tracking device outside of work hours. The tracking system100can determine that a tracking device106is not within a threshold proximity of a mobile device102by determining that the tracking device is outside of the transmission or communicative range of the mobile device. For instance, if the mobile device and the tracking device are configured to communicatively couple via the Bluetooth protocol, the tracking system100can determine that the tracking device106is outside of a threshold proximity of the mobile device102if the mobile device is unable to receive Bluetooth advertisements or communications from the tracking device. The tracking system100can determine that a first tracking device is not within a threshold proximity of one or more additional tracking devices by determining that the one or more additional tracking devices are within the transmission or communicative range of one or more mobile devices, and that the first tracking device is not within the transmission or communicative range of the one or more mobile devices. Likewise, the tracking system100can determine that a tracking device106is not within a threshold proximity of a mobile device102or one or more additional tracking devices by determining a location of the tracking device (e.g., from a community mobile device104different than the mobile device102, from a database storing a last known location of the tracking device, or from any other suitable source), and determining that the determined location of the tracking device is greater than a threshold distance away from the mobile device102or the one or more additional tracking devices. In some embodiments, the tracking system100can flag a tracking device106as potentially lost in response to the movement of the tracking device from within a threshold distance of a mobile device102to greater than a threshold distance of the mobile device. In some embodiments, the tracking system100can flag a tracking device106as potentially lost in response to the severing of a communicative connection between the tracking device and a mobile device102(for instance, as a result of the movement of the tracking device and the mobile device away from each other). In some embodiments, a user can select the threshold distance used by the tracking system100to trigger a determination that the tracking device106is potentially lost, for instance via an interface of the mobile device102. FIG.6illustrates a flowchart for a method of identifying a tracking device as potentially lost based on a threshold distance from a target device, according to one embodiment. Alternate embodiments may contain more, fewer, or different steps, or the steps may be performed in an order different from the one shown inFIG.6. The tracking system100receives600a location of a user's tracking device and receives610a location of a target device. In some embodiments, the tracking device location is received from a mobile device of a user different from the user to whom the tracking device belongs. The target device can be another tracking device, a user's mobile device, or any other suitable system. The tracking system100determines620whether the tracking device location is more than a threshold distance from the target device location. If the tracking device location is determined to be more than the threshold distance from the target device location, the tracking system identifies630the tracking device as potentially lost. The tracking system100generates640a notification identifying the tracking device and indicating that the tracking device is potentially lost, and provides650the generated notification to the user's mobile device. The user's mobile device can be configured to display the notification to the user. Examples: In some embodiments, the tracking system100notifies a user that a tracking device is potentially lost if the tracking device is not located with a threshold distance of the user's mobile device and if the tracking device is coupled with an object the user uses regularly. For example, the user may be notified as such if the tracking device is coupled to keys, a wallet, a phone, glasses, a watch, a laptop, a digital book/reader, or a tablet. The threshold distance can be selected by the user or the tracking system100such that the tracking device is on the user's person or within the user's immediate vicinity (e.g. <5 feet), or may be selected such that the user is reminded to bring the object when the user leaves an area (e.g. approximately 15 feet). In some embodiments, the user designates which tracking devices are coupled to objects the user uses regularly. The user may also designate time periods during which those designated tracking devices should be within a threshold distance of the user's mobile device. For example, the user may designate the user's work hours, workout hours, sleeping hours, dining hours, relaxation hours, traveling hours, class hours, or commuting hours. In some embodiments, the tracking system may notify a user that a tracking device is potentially lost if a tracking device was located within the threshold distance of the user's mobile device when the user left a geographic location and the tracking device is not located within the threshold distance of the user's mobile device before the user returns to that geographic location. For example, if the tracking device is coupled to a tablet, if the user leaves home with the tablet and the tracking system100determines that the tablet tracking device is not within a threshold distance of the user's mobile device before the user returns home, the tracking system100may notify the user that the tablet tracking device is potentially lost. The threshold distance may be selected such that if the tracking device is near the user or in the user's car (e.g. 2-5 feet), the tracking device is not identified as potentially lost. Example geographic locations include the user's home, work, school, gym, or car. In some embodiments, the tracking system100notifies the user that a tracking device coupled to car accessory may not be in the car based on whether the car accessory tracking device is located within a threshold distance of a tracking device coupled to the car. For example, if a tracking device coupled to the user's parking pass is not located within the threshold distance of a tracking device coupled to a car, the tracking system100may notify the user that the parking pass tracking device is not in the car. In such embodiments, the tracking system100may only notify the user if the user's mobile device is located within a threshold distance of the car tracking device. For example, the tracking system100may notify the user if a phone charger tracking device is not located within a first threshold distance of a car tracking device if the user is located within a second threshold distance of the car tracking device (e.g. if the user is in the car and about to leave). In some embodiments, the tracking system100provides notifications to the user's mobile device if the user is traveling and based on whether the travel tracking device is located within a threshold distance of the user's mobile device. For example, if the user is on an airplane, the user may be notified that a travel tracking device (e.g. a luggage tracking device, a laptop tracking device, a phone tracking device) is not on the user's airplane if the travel tracking device is not located within a threshold distance of the user's mobile device or a tracking device coupled to the airplane. Additionally, the tracking system100may notify the user of a travel tracking device that is potentially lost if the travel tracking device is within a threshold distance of an airplane tracking device and not within a threshold distance of the user's mobile device (e.g. the user left the travel tracking device on the airplane). In some embodiments, the tracking system100notifies the user that the user's luggage was sent to the wrong airport. The tracking system100can notify the user of such a state if the user's mobile device is located within a threshold distance of one airplane tracking device, and a luggage tracking device is located within a threshold distance of another airplane tracking device (or a community member's mobile device) that is at a different airport from the airport of the first airplane. In some embodiments, the tracking system100notifies the user if the user has potentially lost a tracking device coupled to the user's passport. If a passport tracking device is not located within a threshold distance of the user's mobile device or other travel tracking devices (such as a luggage tracking device, a travel bag tracking device, etc.) while the user's mobile device or the travel tracking devices are at a travel hub (e.g. airport, seaport, train station), the user may be notified that the passport tracking device is potentially lost. In some embodiments, the tracking system100notifies the user that a tracking device may have been stolen from the user's car if the tracking device is not located within a threshold distance of a car tracking device. For example, if the user leaves a tracking device coupled to a laptop in a car, and the laptop tracking device is not located within a threshold distance of the car tracking device, the user may be notified that the laptop tracking device has left the car. The tracking system100may only notify the user that a tracking device is potentially stolen if the user's mobile device is not detected within a threshold distance of the car tracking device during the time period in which the potentially stolen tracking device was determined to be outside the threshold distance from the car. For example, a user may have left a laptop tracking device in a car, and as a result, the laptop tracking device may be within a threshold distance of a car tracking device. If the laptop tracking device is determined to be outside the threshold distance from the car tracking device before the user returns to the car (e.g. when the user's mobile device is within a threshold distance of the car tracking device), the user can be notified that the laptop tracking device has been stolen. In some embodiments, the tracking system100notifies the user when a tracking device associated with a child is not located within a threshold distance of the user's mobile device. For example, a tracking device may be coupled to the child's phone, jacket, backpack, shoes, or toys. The user may configure the threshold distance of the child tracking device based on where the child is. For example, if the child is at the park, the threshold distance may be larger than if the child is at a theme park. In some embodiments, the user is notified when the child tracking device is not located within a threshold distance of another tracking device, such as a tracking device given to a baby sitter to locate the child tracking device. In these embodiments, if the child tracking device is not located within a threshold distance of the other tracking device, the tracking system100may notify the user through the user's mobile device that the child tracking device is outside the threshold distance of the user's mobile device or another tracking device. In some embodiments, the tracking system100will notify the user of a potentially lost tracking device when the user's mobile device is at a particular geographic location/within a geographic boundary and when the tracking device is not located within a threshold distance of the user's mobile device. For example, if the user's mobile device is at a store, the tracking system100may notify the user of a potentially lost wallet tracking device if the wallet tracking device is not located within a threshold distance of the user's mobile device while the user is at the store. The tracking system100may flag one or more tracking devices from a particular collection of tracking devices depending on which geographic location or geographic boundary the mobile device is in. For example, if the mobile device is at the airport, the tracking system100may notify the user if a travel tracking device is not located within a threshold distance of the mobile device or another travel tracking device. If the mobile device is at the gym, the tracking system100may notify the user if a gym bag tracking device is not located within a threshold distance of the mobile device or another workout tracking device. If the mobile device is at the beach, the tracking system100may notify the user if a beach gear tracking device is not located within a threshold distance of the mobile device or another beach tracking device. If the mobile device is at work, the tracking system100may notify the user if a work tracking device is not located within a threshold distance of the mobile device or another work tracking device. If the mobile device is at a campsite, the tracking system100may notify the user if a camping tracking device is not located within a threshold distance of the mobile device or another camping tracking device. Geographic location: The tracking system100can identify a tracking device106as potentially lost in response to determining that the tracking device is more than a threshold distance from a selected geographic location (for instance, defined by geographic coordinates), or outside of an area defined by a selected geographic boundary (for instance, boundaries associated with a house or building, boundaries associated with property lines or a property lot, and the like). The geographic location or geographic boundary can be defined or selected by a user, for instance, via an interface of the mobile device102or of the tracking system100. For example, a user can define a set of GPS coordinates as a selected location, or can draw a set of geographic boundaries within a map interface. In some embodiments, a user can select a threshold distance or can change a pre-set threshold distance for use in conjunction with a selected geographic location (such that tracking devices located more than the selected threshold distance are identified as potentially lost). The geographic location or geographic boundary can also be selected (for instance, by the tracking system100) based on historical location data associated with the tracking device106, a user, or a mobile device102associated with the user. For instance, if a tracking device106is commonly located within a geographic boundary associated with a user's work building during week day working hours, the geographic boundary can be selected by the tracking system100for use in determining if the tracking device is potentially lost. Likewise, if a tracking device106is commonly located within a threshold distance of a user's home on the weekend, a geographic location corresponding to the user's home (e.g., a set of GPS coordinates over which the user's home is located) can be selected by the tracking system100for use in determining if the tracking device is potentially lost. In some embodiments, the tracking system100can identify a potential geographic location or geographic boundary for use in determining if a tracking device106is potentially lost based on historical location data associated with the tracking device, a user, or a mobile device of the user, and can present the potential geographic location or geographic boundary to the user. For instance, an application associated with the tracking system100can display a set of selectable potential geographic locations or geographic boundaries to the user, and can display information associated with the historical location data upon which each potential geographic location or geographic boundary is identified (for instance, the application can display a potential geographic location in conjunction with the text “recommended based on the location of this tracking device during weekdays between the hours of 9 am and 5 pm”). If the user selects the potential geographic location or geographic boundary, the tracking system100can store the geographic location or geographic boundary for future use in determining if the tracking device106is lost. The tracking system100can determine that a tracking device106is not located within a threshold distance of a geographic location or is not located within a geographic boundary if 1) a location of the tracking device is received from a community mobile device104and 2) if the received location is more than a threshold distance away from the geographic location or is located outside of the geographic boundary. Alternatively, the tracking system100can determine that a tracking device106is located more than a threshold distance away from a geographic location or outside of a geographic boundary in response to 1) determining that a mobile device102of a user is located within the threshold distance of the geographic location or within the geographic boundary and 2) determining that the tracking device is not located within the communicative or transmission range of the mobile device (for instance, by determining that the mobile device cannot communicatively couple to the tracking device). In such embodiments, the communicative or transmission range of the mobile device102can be greater than the range defined by the geographic location and the threshold distance, and greater than the range defined by the geographic boundary. FIG.7illustrates a flowchart for a method of identifying a tracking device as potentially lost based on a threshold distance from a geographic location, according to one embodiment. Alternate embodiments may contain more, fewer, or different steps, or the steps may be performed in an order different from the one shown inFIG.7. The tracking system100receives700a location of a user's tracking device. In some embodiments, the tracking device location is received from a mobile device of a user different from the user to whom the tracking device belongs. The tracking system100determines710if the tracking device location is more than a threshold distance from a geographic location. As described above, in alternate embodiments, the tracking system determines if the tracking device location is outside of a geographic boundary. If the tracking system100determines that the tracking device location is more than the threshold distance from the geographic location (or outside the geographic boundary), the tracking system identifies720the tracking device as potentially lost. The tracking system100generates730a notification identifying the tracking device and indicating that the tracking device is potentially lost, and provides740the generated notification to the user's mobile device. The user's mobile device can be configured to display the notification to the user. Examples: In some embodiments, the tracking system100notifies the user when a tracking device coupled to a set of keys leaves a geographic boundary. For example, if a business provides a set of keys to a temporary employee or a contractor, the tracking system100may notify the user when a keys tracking device is not located within a threshold distance of a geographic location or within a geographic boundary associated with an office of the business. In some embodiments, a tracking device is coupled to a lifting weight or some other piece of exercise equipment and the tracking system100notifies the user when the lifting weight tracking device leaves a gym. Each lifting weight or piece of exercise equipment in a gym may be coupled to a tracking device and the notification to the mobile device may include information that identifies which lifting weight was not located within the gym. In some embodiments, if the mobile device is located near a tourist destination and a tracking device coupled to a camera is located within a threshold distance of the mobile device, the tracking system100may notify the user through the mobile device that they may want to take out their camera and take pictures of the tourist destination. In some embodiments, the tracking system100notifies the user that the user's car is potentially stolen if the car tracking device coupled to the user's car is located outside of a threshold distance from the geographic location where the user parked the car. The tracking system can determine a geographic location for where the user parked the car based on the geographic location of the car tracking device when the mobile device exceeded a threshold distance away from the car tracking device (e.g., when the user walked more than a threshold distance away from the car). If the car tracking device is located more than a threshold distance from the parking location, the tracking system100can notify the user that the car has potentially been stolen. In some embodiments, the tracking system100notifies a user if a tracking device is not located within a room or a house. For example, if a tracking device is coupled to an object that is not supposed to leave a room (e.g. a remote control, reading glasses), the tracking system100may notify the user if the tracking device leaves the room/is not located within the room. The tracking system100may also notify the user that a tracking device coupled to a valuable item (such as a safe, a jewelry box, artwork, a television, a computer, etc.) may have been stolen from a house if the tracking device coupled to the valuable item is not located within the house. In some embodiments, the tracking system100notifies the user if their child is not at a geographic location at which the child is supposed to be. If a tracking device associated with the child (e.g., a tracking device coupled to the child's bag or jacket) is not located within a threshold distance of a geographic location or within certain geographic boundaries (e.g. home, school, art/performance/music lessons, sport practice, friend's house), the user may be notified that the child is not located where they are supposed to be and may be provided with the location of the child tracking device. In some embodiments, the tracking system100notifies the user if a tracking device coupled to a pet is not located within a threshold distance of the user's home or within the geographic boundaries of the user's home. For example, if the user's pet escapes or is stolen, the tracking system100can notify the user that the pet tracking device is not located within the user's home and can provide the location of the pet tracking device. In some embodiments, the tracking system100notifies the user if the pet tracking device enters a particular part of the user's home. For example, if the pet is not supposed to be inside the house or not supposed to be in a particular room of the house, the tracking system can notify the user that the pet tracking device is not where it is supposed to be based on whether the pet tracking device is or is not located within a threshold distance of a geographic location or whether the pet is or is not located within a geographic boundary. Tracking device behavior: The tracking system100can identify a tracking device106as potentially lost in response to a comparison of current tracking device behavior and location and historical tracking device behavior and location. For instance, the tracking system100can determine that a tracking device106commonly accompanies a user on the user's way to work based on an analysis of historical location data associated with the tracking device, and can flag the tracking device as potentially lost in response to determining that the tracking device is not accompanying the user on the user's way to work. Likewise, the tracking system100can determine that the tracking device106typically does not move between the hours of 10 am and 4 pm on weekdays based on an analysis of historical movement data associated with the tracking device, and can flag the tracking device as potentially lost in response to a determination that the motion of the tracking device exceeds a pre-determined motion threshold during this time interval. In addition, the tracking system100can determine that the tracking device106commonly communicatively connects with a mobile device102of a user after 10 pm on weekends based on an analysis of historical communication data associated with the tracking device, and can flag the tracking device as potentially lost in response to a determination that the tracking device has not communicatively connected to the mobile device on a weekend day after 10 pm after the passage of a threshold amount of time. The tracking system100can predict a future state of the tracking device106based on a comparison of historical data associated with the tracking device. For instance, the tracking system100can determine that a tracking device106commonly travels between a first location and a second location between the hours of 5 pm and 6 pm, and can predict that the tracking device will be located at the second location after 6 pm in the event that the tracking device is outside the communicative range of a user's mobile device. Continuing with this example, the tracking system100can determine that the tracking device106commonly takes 30 minutes to reach the second location after leaving the first location, and can predict that the tracking device will reach the second location approximately 30 minutes after detecting that the tracking device has left the first location. Historical data analyzed by the tracking system100can include when, where, or how often the tracking device connects with the mobile device. In some embodiments, the tracking system100can analyze historical behavior of other tracking devices for use in predicting a state of the tracking device106. In such embodiments, historical location and movement patterns of other tracking devices can be used to predict a location and/or movement of the tracking device106in response to a determination that the tracking device is undergoing similar location and movement patterns. Examples: In some embodiments, the tracking system100identifies collections of tracking devices, as described above, for instance based on a history of the tracking devices tending to be located near each other or based on a collection definition from a user, and can notify the user that a tracking device of a collection is lost if the tracking device is not located near tracking devices in a collection. For example, the tracking system may determine that a keys tracking device and a wallet tracking device are typically located near each other, and thus may include the keys tracking device and the wallet tracking device in a collection. If the keys tracking device is subsequently not located near the wallet tracking device, the user may be notified that the keys tracking device or the wallet tracking device is potentially lost. In some embodiments, the tracking system100identifies tracking devices that are typically located near each other and may prompt the user to create a collection of the tracking devices or to add one or more of the tracking devices to an existing collection. For example, if the tracking system100determines that a toiletry bag tracking device is typically located near a suitcase tracking device, the tracking system100may prompt the user to add the toiletry bag tracking device to a travel tracking device collection. In some embodiments, the tracking system100can notify the user that a car tracking device is potentially stolen based on the behavior of the car tracking device. For example, if the car tracking device is typically parked within a threshold distance of a geographic location during particular hours (e.g. while the user is typically home or asleep), the tracking system100may notify the user if the car tracking device is not located within that threshold distance. The tracking system may also determine that a keys tracking device is typically located near the car tracking device when the car tracking device is moving, and may notify the user that the car tracking device is potentially stolen if the car tracking device is moving when not near the keys tracking device. In some embodiments, the tracking system100can notify the user that a car coupled to a tracking device has been in a car accident. The tracking system100may determine if the car tracking device stops suddenly or begins to move erratically and may identify that behavior as indicative of a car accident. The tracking system100may send a notification to the user about the potential car accident, and the notification may include an option to automatically send emergency assistance (e.g. an EMT, paramedic, fire fighters, the police) to the location of the car tracking device. If the mobile device is not located near the car tracking device, the notification may include the location of the car tracking device. If the mobile device is located near the car tracking device (e.g. within a threshold distance), the tracking system100may automatically notify an emergency assistance service (e.g.911) of the car accident and may transmit the location of the car tracking device or the mobile device to the emergency assistance service. In some embodiments, the tracking system100can notify the user with an estimate for how long it will take for the user's luggage to arrive at the luggage carousel from an airplane. The tracking system100may analyze the amount of time it takes luggage tracking devices of other users to arrive at the luggage carousel and provide an estimate based on those amounts of time. In some embodiments, the tracking system100determines an estimate for the amount of time will take for a luggage tracking device to arrive at the luggage carousel based on which airport the user has arrived at. The tracking system100may also analyze the paths luggage tracking devices take in an airport from an airplane to a luggage carousel and, based on those paths, provide a real-time time estimate to the user. For example, if the average wait time is 30 minutes and the luggage tracking device is half way to the luggage carousel from the airplane, the tracking system100may update the wait time estimate to 15 minutes. In some embodiments, the tracking system100notifies the user if a tracking device typically does not move and the tracking device suddenly begins to move. For example, a tracking device may be coupled to an object that typically does not move, such as a piece of art, a safe, an unused car, a desktop computer, a passport, or a file cabinet. If the tracking device moves (e.g. is located in a location different from where it was originally, or a motion-detection sensor of the tracking device, such as an accelerometer, detects movement), the tracking system100may notify the user that the tracking device is potentially lost or stolen. In some embodiments, the tracking system100only notifies the user that the tracking device has moved if the mobile device is not located within a threshold distance of the tracking device. In some embodiments, the tracking system100notifies the user if a pet coupled to a pet tracking device is taken for a walk. The tracking system100may determine if a pet is being taken out for a walk if the pet tracking device is following a path that the pet tracking device follows regularly (e.g. weekly, when a pet walker comes to walk the pet). If the pet tracking device deviates from paths the pet tracking device has taken in the past, the tracking system100may notify the user that the pet is potentially lost rather than that the pet is on a walk. Additionally, if the tracking system100determines that the pet is on a walk but that the path taken by the pet tracking device is different from a typical path of a walk (e.g. significantly longer or shorter), the tracking system100may provide a notification describing the difference to the user. User behavior: The tracking system100can identify a tracking device106as potentially lost in response to a comparison of current user location and behavior and historical user location and behavior. For instance, the tracking system100can determine that a user commonly brings a tracking device106with the user during particular times of the day (determined, for instance, based on historical communicative connections between the tracking device and a mobile device102of the user). In such instances, if the user is determined to not have the tracking device106during similar times of the day, the tracking system100can flag the tracking device as potentially lost. Likewise, the tracking system100can determine that when a mobile device102of a user is historically communicatively connected to a first tracking device in a collection of tracking devices, the user is historically commonly connected to the remaining tracking devices in the collection of tracking devices. In such instances, if the user's mobile device102is communicatively connected to the first tracking device in the collection but not the second tracking device in the collection, the tracking system100can flag the second tracking device as potentially lost. The tracking system100can predict a state of a tracking device106based on historical user location and behavior. For instance, the tracking system100can determine that users commonly bring a particular type of object coupled to a tracking device when the users move from a first location to a second location. In such instances, the tracking system100can determine that the user of a tracking device106coupled to the particular type of object is in the first location, and can predict that the user will want to bring the object to the second location. Likewise, the tracking system100can determine that a user commonly drives a particular vehicle on weekend mornings, and can predict that the user will need to bring the user's wallet coupled to a tracking device106before the user drives the vehicle. FIG.8illustrates a flowchart for a method of identifying a tracking device as potentially lost based on historical movement behavior, according to one embodiment. Alternate embodiments may contain more, fewer, or different steps, or the steps may be performed in an order different from the one shown inFIG.8. The tracking system100determines800a current movement behavior of a user's tracking device, and determines810a historical movement behavior. The historical movement behavior can be historical movement behavior of the tracking device, the user, or the user's mobile device. It should also be noted that in some embodiments, the tracking system100can determine a current movement behavior of a user, or of a user's mobile device. The tracking system100determines if the current movement behavior differs from the historical movement behavior. If the current movement behavior differs from the historical movement behavior (e.g. by more than a threshold amount), the tracking system identifies830the tracking device as potentially lost. The tracking system100generates730a notification identifying the tracking device and indicating that the tracking device is potentially lost, and provides740the generated notification to the user's mobile device. The user's mobile device can be configured to display the notification to the user. Examples: In some embodiments, the tracking system100notifies the user if the user has potentially dropped a tracking device. For example, if the tracking system100detects that the user may have dropped a tracking device coupled to the user's keys or wallet, the tracking system100may notify the user that the tracking device was potentially dropped and provide the location of the tracking device to the user in the notification. The tracking system100may detect a dropped tracking device if the tracking device is moving similarly to and in conjunction with the mobile device and the tracking device stops moving while the mobile device keeps moving, or the movement of the tracking device differs by more than a threshold from the movement of the mobile device. In some embodiments, the tracking system100provides notifications to the user based on the user's routine. If the user regularly visits a location during a particular time period and brings one or more tracking devices while visiting the location, the tracking system100may provide notifications to the user that remind the user to bring the tracking devices or notify the user that they potentially forgot to bring one or more of the tracking devices. For example, if the user visits a gym every week, the tracking system100may provide notifications to the user to bring gym tracking devices (e.g. a gym shoes tracking device or a gym bag tracking device) to the gym. Similarly, if the user travels regularly, the tracking system100may notify the user to bring travel tracking devices (e.g. a passport tracking device or a luggage tracking device) before the user travels to the airport. If the user is a student and goes to class regularly, the tracking system100can provide a notification to bring tracking devices coupled to class supplies (e.g. textbooks, a laptop, pencil case, notebook, homework/homework folder), or may notify the user if the user has potentially forgotten a class supply tracking device. In some embodiments, the user can specify routine activities for which the tracking system100should provide notifications or can specify time ranges during which the tracking system100should provide notifications. For example, if the user goes to the gym on Tuesdays, the user may specify to the tracking system100to provide reminder notifications about gym tracking devices on Tuesdays or when the user is going to or at the gym. In some embodiments, the tracking system100can provide reminder notifications to the user to use objects that the user needs to interact with regularly. The tracking system100may determine if the user is near a tracking device coupled to one of the objects and, if the user has not been near the tracking device within a certain time period, the tracking system100may notify the user to use the object coupled to the tracking device. For example, the user may be notified to use a pill box/medicine, a toothbrush, a mouth guard, or weights/exercise equipment. In some embodiments, the tracking device is coupled to an object that is related to a chore the user needs to perform on a regular basis, such as a pet food bowl, a mailbox, a washer/dryer, a dishwasher, a sink, or a trash can. External data: The tracking system100can identify a tracking device106as potentially lost or can predict a state of the tracking device based on data received from an external data source112. The external data source112can be an external database, a website, a digital or network service, an external device or system, a communication, or any other suitable source. In some embodiments, data can be requested from the external data source112by the tracking system100or a mobile device102, for instance via an API associated with the external source. The data can be requested from the external data source112at the explicit request of a user of the mobile device102, periodically, or in response to the occurrence of an event (for instance, the movement of a tracking device106, the communicative coupling of the tracking device to the mobile device, locating the tracking device, the movement or location of the user, or any other suitable criteria). FIG.9illustrates a flowchart for a method of identifying a tracking device as potentially useful to user based on external data, according to one embodiment. Alternate embodiments may contain more, fewer, or different steps, or the steps may be performed in an order different from the one shown inFIG.9. The tracking system100determines900a location of a user's tracking device, where the tracking device is coupled to an object. The tracking system100determines910a location of a user, and determines920whether the tracking device location is more than a threshold distance from the user's location. If the tracking device location is more than the threshold distance from the user location, the tracking system100accesses930external data from an external source, where the external data is associated with the object coupled to the tracking device. The tracking system100determines940that possession of the object is likely to be useful to the user based on the external data. The tracking system100generates950a notification identifying the tracking device and recommending that the user obtain the object, and provides960the generated notification to the user's mobile device. The user's mobile device can be configured to display the notification to the user. Examples: In some embodiments, the tracking system100receives financial transaction information from a bank or a budgeting system to detect fraudulent charges to the user's account. The tracking system100may receive information identifying transactions charged to the user's credit card and identifying where the transactions occurred. If a transaction occurred at a store that the wallet tracking device has not been in or was not in at the time of the transaction, the tracking system100may notify the user that the transaction at the store is potentially fraudulent. In some embodiments, the notification of the potential fraudulent charge may include an option to notify the credit card company of the fraudulent charge. In some embodiments, the tracking system100receives sales information from a vendor system regarding sales that are available near the user based on tracking devices near the user. If the tracking system100detects that a tracking device is near the user (e.g. within a threshold distance of the mobile device), and the tracking device is coupled to an object, the tracking system100may provide a notification with information about a sale that is relevant to the object. For example, if the user is carrying a gym bag tracking device and is walking through a store, the tracking system100may notify the user that there is a sale on energy drinks or water. In some embodiments, the tracking system100provides notifications with sales information based on a tracking device not being located near the user. For example, if the user is carrying a luggage tracking device, but a toiletry bag tracking device is not located near the user, the tracking system100may notify the user of sales to purchase toiletries in a nearby store. In some embodiments, the tracking system100receives parking regulation information from a database. The parking regulation information may describe where a user can park a car and for how long the user can park the car there. The tracking system100can provide notifications to a user if the user has parked their car in a spot for too long. For example, if a car tracking device is located in a parking spot that has a two-hour parking limit, the user may be notified after an hour and a half that the car tracking device needs to be moved soon. If the user paid a parking meter for the parking spot, the tracking system100may provide a notification to the user when the parking meter timer is getting low, and the notification may include an option to pay more money into the parking meter. In some embodiments, the tracking system100determines which parking meter is associated with the car tracking device based on the location of the car tracking device. Additionally, the tracking system100may notify the user if the car tracking device is potentially parked in a parking spot that the car is not allowed to be parked in. For example, if street parking on a street is restricted on Mondays and the car tracking device is located on the restricted street on a Monday, the user may be notified that their car is potentially parked illegally. In some embodiments, the tracking system100receives information about a user's schedule and provides notifications to the user based on the user's schedule. The schedule information can include information about a user's calendar from a calendaring system or a user's messages (e.g. emails, texts, instant messages) from a messaging system. The schedule information may describe events the user must attend, including what the events are, when they are, and where they are. The tracking system100may provide notifications to the user to remind the user to bring certain tracking devices to an event or to notify the user that they potentially left a tracking device behind. For example, the tracking system100may remind the user to bring a wallet tracking device, a keys tracking device, a watch tracking device, or a glasses tracking device to events on the user's schedule. In some embodiments, the tracking system100provides a notification to the user based on what event is on the user's schedule. For example, if the schedule information shows that the user is going to class and does not have a class tracking device (e.g. a textbook tracking device, pencil case tracking device, notebook tracking device), the tracking system100may notify the user that they potentially forgot the class tracking device. In some embodiments, the schedule information includes the type of the class (e.g., Biology, English, History) the user needs to attend, and the tracking system100may identify the class tracking device as potentially lost based on the type of the class. In some embodiments, the tracking system100receives travel information for the user from a travel agency or a transport service and provides notifications based on the travel information. The travel information can include the user's start location, destination, departure time, arrival time, or transportation hubs the user may be traveling through. In some embodiments, the travel information is determined based on the user's emails or calendar received by the tracking system100. The tracking system100may provide a notification to the user to pack certain objects based on the user's destination. For example, if the user is traveling to a cold place and a jacket tracking device is not located near a luggage tracking device, the tracking system100may notify the user that they should pack a jacket. The tracking system100can notify the user that their luggage is potentially lost if a luggage tracking device is not located at the correct transportation hub (determined based on information received from a travel system) when the user arrives at the transportation hub. For example, if a luggage tracking device is located at an airport that is different from the one the user arrived at, the user may be notified that the luggage tracking device is at the wrong airport. In some embodiments, the tracking system100can notify a travel hub or a transportation service if a user's luggage takes a long time to reach a luggage carousel or if the user's luggage was lost. The tracking system100can determine if a user's luggage took a long time to reach a luggage carousel or if the user's luggage was lost based on the location of a luggage tracking device. If the tracking system100notifies the travel hub or transportation service about delayed or lost luggage, the tracking system100may receive a coupon, gift card, offer, or the like for the user from the travel hub or transportation service. For example, the travel hub or transportation service may provide the user with an offer for a free coffee or a discount on a future trip. In some embodiments, the tracking system100receives weather information from a weather service and can provide notifications to the user based on the weather information. The weather information includes information about the weather in a geographic area, including high and low temperatures, rain/snow forecasts, wind forecasts, or humidity forecasts. The tracking system100may provide notifications to the user if the user is not located near a tracking device coupled to an object that will be necessary or helpful for the forecasted weather in the weather information. For example, if the weather information forecasts rain in the user's geographic area and a jacket tracking device is not located near the user, the tracking system100may notify the user that it will rain soon and that the user does not have their jacket. The user may receive a similar notification if the user is not located near an umbrella tracking device, a rain boot tracking device, or a hat tracking device. Similarly, if the weather information forecasts snow in the user's geographic area, the tracking system100may provide the user with a notification reminding them to bring a coat tracking device, an ear muff tracking device, or a scarf tracking device. If the weather information forecasts warm weather in the user's geographic area, the tracking system100may provide the user with a notification reminding them to bring a water bottle tracking device, a sunscreen tracking device. In some embodiments, the tracking system100receives information about natural disasters or emergency situations near the user and may notify the user of the locations of tracking devices coupled to emergency supplies. Examples of natural disasters can include flooding, hurricanes, tornados, earthquakes, and forest fires. Examples of emergency situations can include power outages, water outages, police activity, and building fires. The tracking system100can notify a user of the location of tracking supplies coupled to emergency supplies, including a fire extinguisher, extra water, extra food, and flashlights. In some embodiments, the tracking system100notifies the user of the location of a tracking device coupled to an object carried by the user's child if the tracking system receives information about a natural disaster or emergency situation. Sensor data: The tracking system100can identify a tracking device106as potentially lost or can predict a state of the tracking device based on data received from one or more tracking device sensors. The tracking device sensors can include one or more of: movement sensors (such as accelerators, gyroscopes, and the like), location determination sensors (such as a GPS transceiver, altimeters, and the like), orientation sensors, proximity sensors, communication sensors (such as a Bluetooth antenna or a Wifi antenna), temperature sensors, pressure sensors, light sensors, touch sensors (such as a capacitive touch screen), audio sensors (such as a microphone), or any other suitable sensor. The tracking device106can obtain sensor data in response to requesting sensor data from the sensors, automatically (as the sensors receive/generate the data), in response to a request from a mobile device102or a user of the mobile device, in response to a request from the tracking system100, and the like. The tracking device106can forward the sensor data to a mobile device102, which in turn can forward the sensor data to the tracking system100. The tracking system100can identify a tracking device106as potentially lost based on sensor data received from the tracking device. For instance, if a user leaves the tracking device106at home, and sensor data is received from the tracking device indicating that the tracking device has moved, the tracking system100can identify the tracking device as potentially lost (or in this case, potentially stolen). Likewise, if sensor data is received from a first tracking device indicating that a temperature has fallen below a particular threshold, the tracking system can predict that a user might need an object coupled to a second tracking device in order to stay warm. FIG.10illustrates a flowchart for a method of identifying a tracking device as potentially lost based on sensor data, according to one embodiment. Alternate embodiments may contain more, fewer, or different steps, or the steps may be performed in an order different from the one shown inFIG.10. The tracking system100determines1000a location of a user's tracking device that is coupled to an object. The tracking system100determines1010a location of a user, and determines1020whether the tracking device location is more than a threshold distance from the user's location. If the tracking device location is more than the threshold distance from the user location, the tracking system100accesses1030sensor data from one or more sensors within the tracking device. The tracking system100identifies1040identifies the tracking device as potentially lost based on the sensor data. The tracking system100generates1050a notification identifying the tracking device and identifying the tracking device as potentially lost, and provides1060the generated notification to the user's mobile device. The user's mobile device can be configured to display the notification to the user. Examples: In some embodiments, the tracking system100uses accelerometer data from an accelerometer in a tracking device to determine if the user has dropped the tracking device and may identify the tracking device as potentially lost. For example, if the accelerometer data describes a sudden downward acceleration of the tracking device and then a sudden deceleration as the tracking device reaches the ground, the tracking system100may notify the user that the user potentially dropped the tracking device. In some embodiments, the tracking system100only notifies the user that the tracking device is potentially lost if the tracking device is not located within a threshold distance of the user. In some embodiments, the tracking system100uses thermometer data from a thermometer in a tracking device to notify a user if an area is too warm or too cold for an object coupled to the tracking device or if the tracking device is outside when it should not be. The tracking system100may notify the user that the tracking device is potentially lost or that the tracking device is outside. For example, if the user leaves their pet outside on a cold day and thermometer data from a pet tracking device indicates that the temperature is below a threshold, the tracking system100may notify the user that it is potentially too cold outside for the pet. Similarly, if the user leaves a laptop tracking device outside, the tracking system100may notify the user that the laptop is potentially lost based on thermometer data from the tracking device that it is warm. Such a tracking device can be coupled to a laptop, a child, a pet, a book, a wallet, keys, or any other object a user may leave outside. In some embodiments, the tracking system100uses altimeter data from an altimeter in a water bottle tracking device to notify the user to drink water to keep hydrated. If the tracking system100determines that the water bottle tracking device is located near the user, and the altimeter data from the water bottle tracking device indicates that the water bottle tracking device is at a high altitude, the tracking system100may provide a notification to the user to drink from the water bottle to keep hydrated. Similarly, if the user is at a high altitude and a water bottle tracking device is not located near the user, the user may be notified that the water bottle tracking device is lost or that the water bottle tracking device should be brought with the user when the user goes outside. If the user is at a high altitude, the tracking system100also may notify the user to use or find a tracking device coupled to sunscreen, a hat, a jacket, a backpack, sunglasses, or any other object that may be helpful in a high-altitude environment. In some embodiments, the tracking system uses thermometer data from a thermometer in the water bottle tracking device to notify the user to drink water. In some embodiments, the tracking system100receives barometer data from a barometer in a tracking device to determine if it is about to rain. If the barometer data indicates that it is about to rain (e.g. the barometric pressure begins to drop) and a rain-gear tracking device (e.g. a jacket tracking device) is not located near the user, the tracking system100may notify the user that the rain-gear tracking device is lost or that the user should bring the rain-gear tracking device when going outside. In some embodiments, the tracking system100uses audio data from an audio sensor in a tracking device to determine if an object coupled to the tracking device is potentially being stolen. If the audio data from a tracking device indicates that a window or a door has been broken, the tracking system100may notify the user that someone may be breaking into their house and may identify the tracking device as potentially lost. The tracking system100also may use accelerometer data to determine if a tracking device coupled to an object has been stolen. For example, if audio data indicates that a window has been broken and/or accelerometer data indicates that the tracking device is moving, the tracking system100may notify the user that the tracking device has potentially been stolen and may identify the tracking device as potentially lost. It should be emphasized that in some embodiments, identifying a tracking device as lost or predicting a state of a tracking device can be based on any combination of the above circumstances. For example, a tracking device can be identified as potentially lost based on a proximity of the tracking device to other tracking devices and based on historical behavior of the tracking device. Likewise, a state of the tracking device can be predicted based on a combination of a movement of the tracking device and based on sensor data received from the tracking device. Examples: In some embodiments, the tracking system100uses audio data from an audio sensor in a tracking device and the tracking device's proximity to a geographic location to notify the user that the tracking device has potentially been stolen. If the audio data from a tracking device indicates that a window or a door has been broken, and the tracking device is not located within a threshold distance of a geographic location or within certain geographic boundaries (e.g. a user's home), the tracking system100may notify the user that the tracking device has potentially been stolen. In some embodiments, the tracking system100can notify the user of potential fraudulent financial transaction based on the behavior of a wallet tracking device. The tracking system100can receive financial transaction information from a bank or a budgeting system. If the financial transaction information describes a financial transaction at a store, but the historical behavior of the wallet tracking device suggests that the user has not been in the store, the tracking system100may notify the user of the potentially fraudulent financial transaction. For example, if the financial transaction information includes a credit card charge at a first restaurant on a Wednesday, however the wallet tracking device is typically located in another restaurant on Wednesdays, the tracking system100may notify the user of the potentially fraudulent charge at the first restaurant. The tracking device system100can prompt a user of a mobile device102to opt-in to one or more types of interventions, for instance via a mobile device interface. For example, the tracking system100can determine that a tracking device106is part of a tracking device collection, and can suggest to a user of a mobile device102that the mobile device receive intervention notifications when the distance between the tracking device and other tracking devices in the tracking device collection exceeds a threshold. If the user opts-in to a suggested intervention, the tracking system100stores the opt-in and provides notifications associated with the intervention in response to the circumstances associated with the intervention being trigger. If the user does not opt-in to a suggestion intervention, the tracking system100will not provide notifications associated with the intervention, even if the circumstances associated with the intervention are triggered. FIG.11illustrates a flowchart for a method of generating an opt-in notification for identifying a tracking device as potentially lost, according to one embodiment. Alternate embodiments may contain more, fewer, or different steps, or the steps may be performed in an order different from the one shown inFIG.11. The tracking system100accesses1100criteria for identifying a user's tracking device as potentially lost. The criteria can be associated with one or more properties of the tracking device. The tracking system100accesses1110information associated with the one or more properties of the tracking device, and identifies1120the tracking device as potentially lost based on the accessed criteria and the accessed information associated with the one or more properties of the tracking device. The tracking system100generates1130an interface including an option to opt-in to notifications identifying the tracking device as potentially lost in response to the accessed criteria being satisfied, and provides1140the generated interface to the user's mobile device. The mobile device can be configured to display the interface to the user. In response to the user opting-in to receiving the notifications, the tracking system100generates1150a notification that the tracking device is potentially lost and provides the generated notification to the mobile device for display to the user. In some embodiments, the tracking system100can prompt a user of a mobile device102, via a notification presented by the mobile device, to configure a tracking device106to operate in a particular mode based on a predicted state of the tracking device. For instance, if a tracking device106is predicted to be in motion or is predicted to move to an unfamiliar location, the tracking system100can instruct the mobile device102to display a notification including an option to configure the tracking device to operate in a high performance mode (e.g., the tracking device can increase a frequency of advertisements/communications broadcasted by the tracking device to increase the likelihood that the tracking device is able to communicatively couple to the mobile device or a community mobile device104). Likewise, if a tracking device106is predicted to be stationary for an interval of time, the tracking system100can instruct the mobile device102to display a notification including an option to configure the tracking device to operate in a power saving mode (e.g., the tracking device can decrease the frequency of advertisements/communications broadcasted by the tracking device in order to preserve power). If the user selects to reconfigure the tracking device106to operate in a particular mode as suggested by the notification (for instance, by selecting a selectable option displayed by the notification), the mobile device102can reconfigure the tracking device, and can inform the tracking system100that the user reconfigured the tracking device. In the future, if the tracking system100predicts a similar tracking device state, the tracking system can instruct the mobile device102to similarly configure the tracking device106without requiring the mobile device to display a similar notification and without requiring the user to affirmatively select to configure the tracking device to operate in the suggested mode. Examples: In some embodiments, the tracking system100prompts the user to opt into notifications about a luggage tracking device if the tracking system100determines the user is traveling. The user can select to receive notifications about whether the luggage tracking device is on the correct airplane, whether the luggage tracking device arrived at the correct airport, or an estimate for how long it will take for the luggage tracking device to arrive at a luggage carousel. In some embodiments, the tracking system100prompts the user to opt into or modify the circumstances under which the user is notified when a tracking device is not located within a threshold distance of the mobile device. For example, if the user leaves a wallet tracking device or a keys tracking device on a desk in the user's office and the user leaves the office without bringing the wallet tracking device or the keys tracking device, the user may not want a notification while the user is still within the office building. Thus, the tracking system100may prompt the user to adjust the threshold distance for which lost determinations are made for one or more tracking devices. Additionally, if the user does not want to receive notifications about a tracking device not being located within a threshold distance of the user, the user may be prompted to disable the notifications regarding that tracking device. For example, if a user lends their car to other people, the user may disable notifications about a car tracking device. In some embodiments, the tracking system100prompts the user to configure a tracking device to operate in a particular mode. For example, the user may configure a tracking device to operate in a power saving mode if the tracking device is coupled to an object that is predicted to be stationary for a period of time, such as a safe, artwork, a desktop computer, a jewelry box, or a television. The user may also configure a tracking device to operate in a power saving mode if the tracking device is coupled to an object (such as a television remote, a pet, or weights/exercise equipment) that is predicted to be located within a geographic area, such as a home, an office, or a store. The user may configure a tracking device to operate in a high-performance mode if the tracking device is coupled to an object that is predicted be in an unknown/unfamiliar area or is predicted to move, such as a car, luggage, a wallet, or keys. In some embodiments, the user may configure a tracking device to operate in different modes based on where the tracking device is located. For example, a pet tracking device may operate in a power saving mode when the pet tracking device is located within a home and may operate in a high-performance mode if the tracking device is located outside the home. The tracking device interventions described herein can beneficially enable a user to know that a tracking device is lost before the user even realizes the tracking device is lost. Likewise, a tracking device intervention can remind a user to bring an object coupled to a tracking device with the user when the user moves from a first location to a second location (e.g., on the way to work) before the user gets too far away from the first location. In addition, a tracking device intervention can suggest a user take an action (such as bringing an object coupled to a tracking device) based on a predicted state of the tracking device (e.g., the object coupled to the tracking device is likely to be useful to the user). In each of these circumstances, the user is provided with important or useful information before the user realizes that such information would be important or useful, thereby beneficially improving a user's experience with the tracking device and the tracking system100. Tracking Device Functions Based on User Presence A user's location, or a user's presence within a geofence or other predefined area, can be used to configure the operating mode or state of an electronic device. For instance, the movement of a user into a geographic area can be used to configure an electronic device within the area. Examples of such devices include home security systems, home heating and cooling systems, door locks, computers, routers, television set-top boxes, scanning devices (such as tracking device scanning devices), Bluetooth devices, and the like.FIGS.12A and12Billustrate an example of configuring an electronic device based on the entry of a user into an area defined by a geographic boundary, according to one embodiment. In particular,FIG.12Aillustrates a user1200outside an area defined by a geographic boundary1210, andFIG.12Billustrates the entry of the user into the geographic boundary. In this example, the geographic boundary1210encloses an area that contains the user's house1220. When the user1200is outside of the geographic boundary1210, an electronic device1230is configured to operate in a first mode. In the embodiment ofFIG.12A, the first mode is an “off” mode, but in other embodiments, the first mode can be an “on mode”, an “active mode” (e.g., for a security system), a temperature range (e.g., “between 60 and 65 degrees Fahrenheit”), or any other suitable mode of operation. When the user1200enters the geographic boundary1210, as illustrated inFIG.12B, the electronic device1230is configured to operate in a second mode (such as the “on” mode) in response to the presence of the user within the geographic boundary. In order to detect the absence or presence of a user1200within an area, a tracking system, such as the tracking system100, can detect the absence or presence of a tracking device often carried by or within a threshold distance of the user (for instance, a tracking device coupled to the user's keys, a handbag or backpack of the user, or the user's vehicle). As described above, a mobile device (such as a smartphone) of the user can receive a transmission from the tracking device and, in response, can detect a location of the mobile device (for instance, using location-detection functionality, such as a GPS receiver). The mobile device can then provide the detected location and an identity of the tracking device to the tracking system, and the tracking system can determine the presence or absence of the user based on the provided location and tracking device identity. The geographic boundary1210encloses a pre-defined geographic area. In one embodiment, the user defines the geographic boundary1210, for instance, by selecting a center of the boundary, a shape of the boundary, a radius of the boundary, the location for each boundary segment, and the like. For instance, a user can define a geographic boundary centered on the user's workplace and can specify that the geographic boundary covers the campus of the workplace. A user can also define the operating mode/function of a device being configured based on the presence or absence of the user in the geographic boundary. For instance, a user can define a geographic boundary, identify a device, define a first operating mode of the device when the user is within the geographic boundary, and define a second operating mode of the device when the user is outside the geographic boundary. In addition to the tracking system100configuring a device based on a user's absence/presence, a device can configure itself when it detects a user or a tracking device associated with the user, based on the user's observed daily routine. In an embodiment, the tracking system100can determine the geographic boundary1210based on the observed behavior and location of the user1200without direct input from the user. For example, the tracking system100can define geographic boundaries centered on the home of a first and second user, based on behavior of the first and second user each day after school. Continuing with this example, the first user can return directly home most days after school, and thus the tracking system can define a first geographic boundary of a first radius covering the property on which the home sits. Likewise, the second user can often go to a neighbor's house to study, and the tracking system can define a second geographic boundary of a second radius larger than the first radius for the second user to cover not just the property on which the house sits but to cover the neighbor's house as well. Accordingly, when either the first user returns home or the second user goes to the neighbor's house on a particular day, a furnace within the home can be activated in order to begin heating the home, as the tracking system100may observe the first user or second user doing routinely. The geographic boundary1210may be associated with a time range. In some embodiments, a user can define a geographic boundary and can define a time range in which the geographic boundary is active. For example, a user can define a geographic boundary associated with the user's home for the hours of 5 pm to 7 pm (when the user generally arrives home from work), and the tracking system100, in response to detecting the user arriving within the geographic boundary within the time range, can configure the operating mode of one or more electronic devices or home systems. In some embodiments, the tracking system100can define a geographic boundary without user input based on a user's historical behavior and can define the geographic boundary to be active only during a time period associated with the user's historical behavior. In some embodiments, a user1200may define multiple geographic boundaries1210, each associated with a different electronic device. For example, a user can define a first geographic boundary associated with a furnace of her house and can define a second, smaller geographic boundary associated with a security system of her house. Accordingly, because furnaces take some time to heat up a house, the furnace turns on as soon as the user crosses the first geographic boundary, and the security system is only de-activated when the user crosses the second, smaller geographic boundary. Such an embodiment both enables the furnace more time to heat the house, and reduces the period of time during which the security system is de-activated. A device can also configure itself when the user exits the region bounded by a geographic boundary. For example, because a user does not need a heated house when they are not home, the furnace may turn itself off when the user is not at their house. Therefore, the furnace can be configured to turn off if the user is exiting the geographic boundary instead of turning on when the user enters the geographic boundary. The same principle can be applied to modes of other devices, such as turning on a security system, turning off an oven, and the like if the user leaves their house. Although a user's house is the associated with the geographic boundary1210ofFIGS.12A and12B, in practice, a geographic boundary can be centered on or located at any suitable location or entity. For example, a geographic boundary can be defined based on a user's workplace, school, gym, church, family member's house, a park, and the like. The electronic device1230can be configured to operate in a particular mode based on the presence or absence of the user within a geographic boundary, or based on a location of the user more generally. In some embodiments, the electronic device1230is located within the geographic boundary itself, but in other embodiments, the electronic device is located outside the boundary. The electronic device1230can be a device configured to control temperature, configure a security system, send a notification, turn on/off lights, turn on/off music, scan for tracking devices, or perform any other suitable function. Some examples of an electronic device1230include a thermostat, a security system, a router, appliances, lights, a garage door opener, a television or set-top box, a computer, and any other suitable device configured to operate in one or more modes. In one embodiment, the electronic device1230is a mobile device102associated with the user1200(e.g., a mobile device configured to provide locations in association with a tracking device identity to a tracking system100in response to detecting the tracking device). For instance, a mobile device102can be configured to stop scanning for tracking devices when the user is at home (e.g., and another device can instead scan for tracking devices). Likewise, the mobile device102can be configured to operate in a silent or airplane mode after a particular time of day when the user is at home. Configuring an electronic device1230to operate in a particular mode based on the presence or absence of a user can include turning the device off or on, putting the device on silent, turning vibration on or off, or switching to airplane mode, changing the scanning frequency or transmission frequency or strength of the device, change the operation mode from “active” or “enabled” to “disabled”, and the like. The electronic device can be configured to perform a particular function based on the presence or absence of a user. For example, a thermostat can be configured to change temperatures, a door can be unlocked, a set-top box can be configured to record a television program, an application can be launched on a computer, and the like. A device can be configured to operate in different modes based on the presence or absence of the user during particular times of the day. For example, a user may only want a coffee maker to make coffee if she goes to her office in the morning and may want the coffee maker to remain idle if she goes in late to work. In some embodiments, the electronic device1230is a scanning device. A scanning device is a device configured to scan for tracking devices106in order to determine if a tracking device is within a proximity of the scanning device. Examples of scanning devices include computers, smartphones and other mobile devices, set-top boxes, and routers. A scanning device may also be a scanning hub or other specialty device built into a work station, home, or car. In embodiments in which a different scanning device is present (e.g., within a threshold proximity of a user), the scanning functionality of the user's smartphone can be disabled since the scanning device can perform the function of detecting tracking devices. Such a configuration beneficially saves mobile device battery power, since the mobile device is no longer required to scan for the tracking device. The tracking system100can configure a scanning device to operate in a first mode when the user1200is inside the geographic boundary and a second mode when the user1200is outside the geographic boundary. Configuring the scanning device can include changing the scanning frequency or duty cycle of the scanning device and enabling or disabling scanning functionality of the scanning device altogether. For instance, when a user is away from home, a scanning device can be configured to scan for tracking devices every 10 seconds, and when the user is at home, the scanning device can be configured to scan for tracking devices every 1 second while a smartphone can simultaneously be configured to halt scanning for tracking devices. FIG.13illustrates a flowchart for a method of configuring an electronic device based on a location of a user. A tracking system100receives1300a first location of a tracking device106from a mobile device102of a user at a first time. The mobile device102is configured to provide locations of the tracking device106to the central tracking device system in response to receiving communications from the tracking device106. The tracking system100then receives1310a second location of the tracking device106at a second time after the first time. The tracking system100accesses1320information describing a boundary associated with the user and corresponding to a geographic region. The user may define the location and contours of the geographic boundary for storage by the tracking system100. In response to determining that the first location is outside the boundary and the second location is inside the boundary, the tracking system100provides1330configuration instructions to an electronic device associated with the user. The configuration instructions can identify an operating mode that the electronic device can configure itself into or the function that the electronic device is supposed to perform. In response to the receiving the configuration instructions, the electronic device can configure itself to operate in the identified operating mode. In another embodiment, the configuration instructions can be provided to the electronic device in response to determining that the tracking device is within the geographic boundary at the first time and then later is outside the geographic boundary at the second time. Examples: In some embodiments, the tracking system100can send notifications to a first user based on a location of a second user. For example, the tracking system100may notify a user when their child gets to school, if their child gets to school on time, if their child does not arrive at school, when their child arrives home, and if their child does not arrive home based on the presence or absence of the child within a geographic boundary at a predetermined time. Additionally, the tracking system100may notify a user if a tracking device106leaves the geographic boundary unexpectedly, for instance a tracking device carried by a child leaving a boundary associated with school during school hours. In another example, when a user crosses a geographic boundary around their house, such that the user moves into the geographic boundary, the thermostat may turn on the heater or the air conditioner, the security system may be disabled, or the oven may turn on. Other examples include opening/closing the garage door, turning on/off lights in the house, turning on/off sprinklers, turning on/off outdoor lights, or locking/unlocking the door. In the case where a user crosses the geographic boundary, such that the user moves outside the geographic boundary, the thermostat may turn off the heater or air conditioner, the security system may be enabled, the outlets in the house may be disabled (i.e., to turn off any heating devices, like a hair straightener), the dog door may be locked/unlocked, or the oven may turn off. In a different example, when a user crosses a geographic boundary around their workplace or place of employment, the parking garage door may open, the elevator may move to the entrance level, or the user's computer monitors may turn on. Other examples include turning on/off the heater or air conditioner, turning on/off the lights in the office, or locking/unlocking the workplace door. In another example, when a user crosses a geographic boundary around their school, the attendance system may check the user in or the user's locker may unlock/lock. In other examples, the presence or absence of a user within a geographic boundary can configure a television or set-top box to record a certain television program or movie, can configure a pet food dispensing device to dispense pet food, can activate security cameras, or can turn off power switches/outlets. FIG.14illustrates a flowchart for a method of configuring a scanning device based on a location of a user. A tracking system100receives1400a location of a tracking device106associated with a user. The mobile device102is configured to provide locations of the tracking device106to the tracking system100in response to receiving communications from the tracking device106. The tracking system100accesses1410information describing a boundary corresponding to a geographic region, which, as noted above, may be defined by the user and stored by the tracking system. The tracking system100then determines1420if the location of the tracking device106is within the geographic boundary. If the device is within the boundary, the tracking system100provides1430a first configuration instruction to the scanning device associated with the user. If the device is not within the boundary, the tracking system100provides1440a second configuration instruction to the scanning device. For instance, if the user is within the boundary, the first configuration instruction can configure the scanning device to scan at a first frequency, and if the user is outside the boundary, the second configuration instruction can configure the scanning device to scan at a second frequency less than the first frequency. In some embodiments, the first instruction can configure the scanning device to operate in a scanning mode, and the second instruction can configure the scanning device to cease scanning altogether. Examples: In some embodiments, the tracking system100can be used to configure a scanning device related to a user. The scanning device may scan for tracking devices within a user's house, work, car, or other places associated with the user. In some embodiments, the scanning device takes over scanning for tracking devices from the user's mobile device when the mobile device is within a threshold proximity of the scanning device. For example, when the user enters the geographic boundary associated with the scanning device, the tracking system100configures the scanning device to scan for tracking devices and configures the mobile device to stop scanning for tracking devices to help save mobile device battery power. The scanning frequency, duty cycle, and scanning power/strength of the scanning device can be set by the tracking system100based on a user's presence or absence. For example, when a user comes home, the scanning device can be configured to scan every 15 minutes at a lower scanning power, and if the user leaves home, the scanning device can be configured to scan every 2 minutes at a high scanning power. In some embodiments, the scanning device can be configured to scan for particular behaviors based on the presence or absence of a user. For instance, if a user is not at home, the tracking system100can configure the scanning device to detect any movement of an object coupled to a tracking device. If an object moves when no one is at home, the scanning device can inform the tracking system, which in turn can inform the user that the user's house has potentially been broken into and burglarized. Likewise, when the user returns home, the user is likely to interact with (and thus move) objects coupled to tracking devices, and thus the tracking system can configure the scanning device to ignore detected object movement unless an object moves more than a threshold distance away from the home. Access Point Functionality in a Tracking Device Environment The tracking system100can make use of access points within an environment to identify the locations of tracking devices. The environment is bounded by a geographic boundary, such as a geofence, that may coincide with the range of the access points within the environment. Access points, such as Wi-Fi routers and range extenders, can communicate, over a network, with tracking devices as well as a tracking server of the tracking system100. An access point may couple with tracking devices, wherein the access point detects and/or couples to the tracking device over Bluetooth. An access point may also receive signals output by the tracking device, also via Bluetooth, while not being detected and/or coupled to the tracking device. In some embodiments, the access point may not couple to the tracking device, but rather simply detect the tracking device by receiving signals transmitted by the tracking device. Access points usually remain stationary in an environment, thereby facilitating the automated, immediate identification of tracking devices' locations. The tracking server may notify users of the tracking devices in real-time of their tracking devices' locations. Access point functionality in a tracking device environment may be used to alert a user of a tracking device's immediate location. A number of access points may try to communicate with the tracking device, increasing the likelihood of determining the tracking device's location. In addition, when a user enters and exits a geographic boundary associated with a location, access points may report the arrival and departure of the tracking device to the tracking server. Thus, due to the presence and prevalence of access points, the tracking server can immediately determine the location of the tracking device. FIGS.15A and15Billustrate an example of a tracking device left at a location defined by a geographic boundary. BothFIGS.15A and15Bshow a user1500and a geographic boundary1505associated with a location, i.e., a house1510of the user1500. The user's house1510, an access point1520, and a tracking device1530are located within the geographic boundary1505.FIGS.15A and15Balso show a mobile device1540of the user1500. The geographic boundary1505may be a geofence, as defined by a communicative range of at least one access point. The geographic boundary may also coincide with the communicative range of the mobile device1540and/or the tracking device. For example, inFIGS.15A and15B, the access point1520and the tracking device1530may each have a communicative range extending up to the geographic boundary1505. The access point1520may be a router or a similar device configured to communicate with and couple to the transceiver of the tracking device over Bluetooth. The location associated with the geographic boundary may be a place the user1500frequently visits, such as the user's house1510, or a workplace of the user, or a school of the user. Each time a user is at the frequently visited location, the tracking device1530couples to the access point1520. In some embodiments, the tracking device1530does not couple to the access point1520. Rather, the tracking device1530may transmit signals over Bluetooth that are detected and stored by the access point1520. A tracking server of the tracking system100is notified of the tracking device1530's proximity to the access point1520, wherein proximity is determined by coupling to and/or detecting the tracking device. It should be noted thatFIGS.15A-15Bshow one access point and one tracking device. In reality, a location within a geographic boundary may include a plurality of access points and a plurality of tracking devices. InFIG.15A, the user1500and the mobile device1540are within the geographic boundary1505. The mobile device1540detects and/or couples to the tracking device1530via Bluetooth, while the tracking device1530also detects and/or couples to the access point1520. InFIG.15B, the user1500exits the geographic boundary1505with the mobile device1540. The user1500leaves the tracking device1530within the geographic boundary1505, i.e., within the user's house1510. For example, the user1500may go for a run, taking the mobile device1540with them. The tracking device1530, left at the user's house1510, may be attached to a pair of keys. The mobile device1540no longer couples, via Bluetooth, to the tracking device1530, as the mobile device1540is beyond the communicative range of the tracking device1530. The mobile device1540determines that it is no longer coupled to the tracking device1520and subsequently notifies the tracking server of the tracking system100. The mobile device1540may wait until a threshold amount of time passes to receive a signal from the tracking device1530. After the threshold amount of time passes, the mobile device1540may determine that the mobile device is not coupled to the tracking device. In some embodiments, the mobile device1540may determine that the mobile device is not coupled to the tracking device1530by detecting that a strength of the signal from the tracking device1530is below a threshold value. The mobile device1540provides the tracking server with information about the mobile device1540's location (e.g., via GPS coordinates). The tracking server determines access points in proximity to the mobile device1540's location, including the access point1520. The tracking server queries one or more nearby access points, including the access point1520, to determine whether at least one of the queried access points is communicatively coupled to the tracking device1530. Querying nearby access points may include directly checking an access point for any coupled tracking devices and/or checking a tracking server for updates previously provided by an access point to the tracking server identifying recently coupled tracking devices. The access points may provide updates identifying recently detected and/or coupled tracking devices to the tracking server. The tracking server may receive these updates at a regular interval, such as every 2 minutes. Since the user1500left the tracking device1530within the geographic boundary1505, the tracking device1530remains communicatively coupled to the access point1520. The tracking server determines that the tracking device1530is coupled to the access point1520, and notifies the mobile device1540of the tracking device1530's location. In another embodiment, instead of receiving location data from the mobile device1540, the tracking server may query access points that the tracking device1530regularly couples to. Regularly coupled and/or detected access points may comprise access points at the user's house1510, including the access point1520, access points at the user's workplace, school, or gym. In some embodiments, the tracking server may identify recently provided updates from one or more access points1520that detected and/or coupled to the tracking device1530. If the tracking server has received an update from an access point1520within a previous threshold interval of time (e.g., within the last 5 seconds, within the last 10 seconds, etc.), the tracking server can determine that the tracking device1530is located within a threshold distance of the access point and can inform the mobile device1540accordingly. Once the tracking server notifies the mobile device1540of the tracking device1530's location, the mobile device1540may display a notification to the user1500informing them that the tracking device1530was left within the geographic boundary1505, at the user's house1510. In another embodiment, the mobile device1540does not notify the user1500of the tracking device1530's location, particularly if the location is regularly visited by the user, such as the user's house1510. The user1500may choose whether to be notified, via the mobile device1540, about instances in which the tracking device1530is left at a location. In some embodiments, the user1500may receive an initial notification, via the mobile device1540, indicating that the tracking device1530is left at the location. The user1500may provide an input to the mobile device1540choosing to prevent the subsequent display of notifications. This may be useful when the user1500wants to specify whether to be notified about certain tracking devices at certain locations. In line with the example above, when going on the run, the user1500may choose to not receive notifications when the tracking device1530, connected to the user1500's keys, is left within the geographic boundary1505corresponding to the user's house1510. However, the user1500may choose to receive notifications when another tracking device, such as one coupled to a laptop, is left within a geographic boundary corresponding to the user's workplace. In one embodiment, when notified that the tracking device1530is not communicatively coupled to the mobile device1540, the tracking server may determine that the tracking device1530is also not communicatively coupled with any queried access points. The tracking server may notify the mobile device1540and the mobile device1540may subsequently notify the user1500that the tracking device1530is lost. Following the above example, if the user1500took their keys with them on the run, but dropped them, the tracking device1530associated with the keys would no longer be detected by and/or coupled with the mobile device1540. The tracking device1530would no longer be in the communicative range of the mobile device1540. The tracking server would determine that the tracking device1530is not coupled to the access point1520or any other nearby access points, thus determining that the tracking device1530is not within the geographic boundary1505. The tracking server informs the mobile device1540, which immediately notifies the user1500that the keys are lost. In some embodiments, access points at particular locations (such as within a user's home) can be used to decrease the amount of time required to determine that a tracking device has been left behind as a user leaves a location. A user's mobile device can scan for a tracking device as the user leaves the location, and makes a determination that the tracking device has been left behind if no signals from the tracking device are received within a threshold amount of time (such as 2-4 minutes). However, waiting this amount of time can result in the user moving further away from the location, increasing the amount of time it takes for the user to return to the location to retrieve the tracking device. Using an access point located at the location can decrease this time interval, thereby decreasing the amount of time required to notify the user that the tracking device has been left behind. FIG.16illustrates a flowchart for a method1600of determining that a tracking device is located at a location that includes an access point. A mobile device (e.g., the mobile device1540) exits1610a geographic boundary (e.g., the geographic boundary1505) associated with a location (e.g., the user's house1510). The location includes at least one access point (e.g., the access point1520). The mobile device determines1620whether it is communicatively coupled, for instance via Bluetooth, to a tracking device (e.g., the tracking device1530). After determining that the mobile device is not communicatively coupled to the tracking device, the mobile device requests that a tracking system (e.g., the tracking system100) query the access point without waiting for the threshold period of time that might otherwise be required for the mobile device to determine that the tracking device is within range of the mobile device. A tracking server of the tracking system queries1630an access point within the location to determine if the tracking device is communicatively coupled to the access point. The access point may be a wireless access point or a Wi-Fi access point, such as a router, modem, range extender, or a television set-top box. In response to determining1640by the tracking server that the access point is communicatively coupled to the tracking device, the tracking server can determine that the tracking device is located at the location associated with the geographic boundary, and thus is not within range of the mobile device. The tracking server informs the mobile device of the tracking device's location. The mobile device notifies1650the user that the tracking device is not within range of the user and/or is at the location, for instance via a notification displayed by the mobile device. In some embodiments, the mobile device may not notify the user of the tracking device's location, for instance if the location corresponds to a pre-determined safe zone, or if the user has historically left the tracking device at the location (for instance within a particular time range). FIG.17illustrates an example of a set of access points within a geographic boundary. A geographic boundary1705encloses a number of access points1720A-F, designated as the set of access points1720, and a tracking device1730. The geographic boundary may correspond to a geofence surrounding a user's house or an airport, for example, and may coincide with the limits of the access points' communicative range. As noted above, a location associated with a geographic boundary may have a plurality of access points. A tracking server of the tracking system100may associate the access points1720A-F with the location corresponding to the geographic boundary1705. Each access point1720A-F is configured to detect the tracking device1730within a certain range of the access point. In the example ofFIG.17, at least one of the access points1720B-D may detect tracking device1730, since the tracking device1730is within a threshold distance of the access points1720B-D (not shown inFIG.17). The access points1720A and1720E-F, located farther away from the tracking device1730, may detect the tracking device1730as well, but with a lower likelihood than the access points1720B-D. After the tracking device1730has moved out of range of the access points1720A-F, the access points may be unable to detect the tracking device1730over an interval of time. The tracking server, after going a threshold amount of time without receiving a location of the tracking device1730from the set of access points1720, can determine that the tracking device1730is not in the location associated with the set of access points. The tracking server can provide a notification, for instance to a mobile device of the user, indicating that the tracking device1730is not at the location. The mobile device may also notify the user the tracking device1730is lost, for instance if the user is located at the location and the tracking device moves from within the location to outside of the location. In the case that at least one access point detects the tracking device over the interval of time, the access point notifies the tracking server of the location of the tracking device. The tracking server determines that the tracking device is located at the location and generates an instruction to provide to the tracking device1730, such as an instruction to ring the tracking device or to couple to a nearby access point1720C. The tracking server sends the identified instruction to the set of access points1720A-F, each of which is instructed or configured to send the instruction to the tracking device1730. With all of the access points1720A-F in the set of access points providing the instruction to the tracking device1730, there is a greater likelihood that the tracking device1730receives the instruction from at least one of the access points1720A-F. For example, in one embodiment, the access points1720A-F are all located within a geographic boundary1705that is associated with a convention center. The tracking device1730may be attached to a laptop of the user, which the user may unintentionally leave in a room in proximity to the access points1720B-C. The access points1720B-C may detect the tracking device1730for an interval of time, and inform the tracking server when the access points detect the tracking device. In response, the tracking server determines that the tracking device1730is located at the convention center, and notifies the user. The user may in turn request that the tracking server provide an instruction to ring the tracking device, and the tracking device can provide the instruction to all of the access points1720B-C. Accordingly, the likelihood that the tracking device will receive the instruction, and thus ring, increases, beneficially enabling the user to more easily identify the location of the laptop. While the tracking server provides the identified instruction to all of the access points1720A-F, each of which in turn is configured to transmit the instruction to the tracking device1730, in practice, the tracking device1730may receive the instruction only from the access points closest to it, such as the access points1720B-D. In some embodiments, when the tracking device1730receives the same instruction from multiple access points, the tracking device only performs the instruction once. In addition to ringing, the tracking server can provide other instructions to the set of access points1720to provide to the tracking device. For instance, the tracking server can instruct the tracking device1730to communicatively couple to the user's mobile device if it is within the communicative range of the tracking device1730, to configure the tracking device into a different operating mode (such as a lost mode or an increased transmission power mode), or to disable one or more features of the tracking device (or a device to or within which the tracking device is located or implemented). In some embodiments, the tracking server can notify the user (via the mobile device) to the areas within the geographic boundary1705in which access points nearest the tracking device are located. For instance, if one or more access points are coupled to the tracking device, or if the tracking device receives an instruction from one or more access points, the tracking server can identify a location of the access points, for instance within the geographic boundary. In some embodiments, the tracking server can indicate a location and/or communicative range of the access points within range of the tracking device within a map interface, beneficially enabling the user to retrieve the tracking device more easily. FIG.18illustrates a flowchart for a method1800of locating a tracking device using a set of access points. A tracking server of the tracking system100associates1810a plurality of access points (e.g., the access points1720A-F) as a pre-determined set of access points. Each access point is located within a geographic boundary (e.g., the geographic boundary1705) that is associated with a location. Examples of locations include a user of the tracking device's house, workplace, a conference center, and a school, among others. Each access point is configured to detect tracking devices (e.g., the tracking device1730) located within a proximity of the access point. For example, the access point may be able to detect tracking devices located within a communicative range of the access point. The tracking server determines1820whether at least one of the access points in the set of access points detects the tracking device within an interval of time. If none of the access points detect the tracking device over the interval of time, the tracking server determines1830that the tracking device is not at the location (or at least is not located within areas of the location within range of the set of access points). If at least one of the access points in the set of access points detects the tracking device within the interval of time, the tracking server determines1840that the tracking device is at the location. The tracking server identifies1850an instruction to send to the tracking device. The instruction may assist the user in locating the tracking device, relative to the locations of access points within the geographic boundary. For example, the instruction may instruct the tracking device to ring or to transmit beacon signals at a higher transmission power. In some embodiments, the instruction may instruct the tracking device to vibrate or emit a light. The tracking server provides1860the identified instruction to each access point in the set of access points. Each access point is in turn configured to transmit the instruction to the tracking device, increasing the likelihood that the tracking device receives the instruction from at least one access point, and thus increasing the likelihood that the tracking device executes the instruction. The tracking device may not receive the instruction from access points farther away from the tracking device, but may receive the instruction from those access points in proximity to the tracking device. FIG.19illustrates a flowchart for a method1900of reporting a location of a tracking device. An access point may detect signals transmitted by a tracking device in proximity to the access point. Once the tracking device has been detected, the access point reports the tracking device's presence to a tracking server of the tracking system100at a default transmission frequency (or “first frequency”). The tracking device may remain coupled to the access point over an interval of time, during which the access point repeatedly notifies the tracking server of the tracking device's presence. Instead of repeatedly providing the same information at the same first frequency, the access point may instead cache the tracking device's presence within the range of the access point in memory, and can either notify the tracking server of the tracking device's presence at a second, lower frequency, or can simply report the tracking device's arrival to (or coupling to) and departure from (or decoupling from) the access point's communicative range. By limiting the amount of redundant location information reported by the access point, the amount of transmission bandwidth and memory storage required by the tracking server can beneficially be reduced. An access point first detects1910a tracking device in proximity to the access point. The first detection of the tracking device's presence by the access point indicates that the tracking device has moved within the communicative range of the access point. The access point may be part of a set of access points, the collective range of which may constitute a geographic boundary, such as the geographic boundary1705. In some embodiments, the first detection of the tracking device by the access point indicates that the tracking device entered the geographic boundary corresponding to a set of access points. In response to detecting the tracking device, the access point provides1920the location of the access point (or a location corresponding to the geographic boundary) and the unique identifier of the tracking device to the tracking server. The access point determines1930whether it is coupled to the tracking device, for instance by determining if the access point is paired with the tracking device via Bluetooth. In some embodiments, the access point may not couple to the tracking device, but rather may simply detect the tracking device by receiving signals transmitted by the tracking device. After detecting the tracking device, but determining that the access point is not communicatively coupled to the tracking device, the access point provides1940its own location and the tracking device identifier to the tracking server at a first frequency, such as every minute. The first frequency may be operating default transmission frequency. In some embodiments, the access point provides the location of the tracking device to the tracking server if the access point detects the tracking device within a time period between transmissions at the first frequency. After detecting the tracking device, but determining that the access point is communicatively coupled to the tracking device, the access point can cache1950the tracking device's presence within the access point's local memory. Accordingly, the tracking server may determine the tracking device's location, which is associated with the access point's location, provided that the access point is stationary. While the access point remains coupled to the tracking device, the access point can subsequently provide1960the tracking device identifier and cached location to the tracking server at a second frequency. The second frequency may be slower than the first frequency and/or the default transmission frequency. For example, the access point may provide the tracking server with updates every three minutes, rather than every minute. The tracking server can also determine the frequency at which the access point provides updates while the access point is coupled to the tracking device. In some embodiments, while the tracking device remains communicatively coupled to the access point, the access point does not provide the tracking server with any location updates. In addition to reporting the tracking device's location at a reduced frequency, the access point reports the decoupling of the access point of the tracking device and the access point (or the departure of the tracking device from the access point's range). In response to the tracking device decoupling from the access point, the access point provides1980the location of the access point, the tracking device identifier, and the time of the tracking device's decoupling from the access point to the tracking server. In some embodiments, the tracking device decouples from the access point because the tracking device departs from the geographic boundary or from the collective communicative range of the set of access points, indicating that the tracking device is no longer in any access point's range at that location. The tracking server may notify the user's mobile device of the tracking device's departure from the location. Continuing with the previous example, the access points are within the geographic boundary are associated with a convention center, and the user unintentionally leaves the tracking device associated with a laptop near an access point. The laptop and the associated tracking device may be stolen. The access points may detect that the tracking device exited the geographic boundary and can provide a notification to the tracking server. The tracking server may notify the user's mobile device, which subsequently displays a notification to the user. The user may still be in the convention center and upon receiving the notification, may immediately realize that the laptop is stolen. The notification to the user may also include the location of the access point that detected the departure of the tracking device, such that the user can pursue the laptop thief as soon as possible. Additional Considerations The foregoing description of the embodiments of the invention has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure. Any of the devices or systems described herein can be implemented by one or more computing devices. A computing device can include a processor, a memory, a storage device, an I/O interface, and a communication interface, which may be communicatively coupled by way of communication infrastructure. Additional or alternative components may be used in other embodiments. In particular embodiments, a processor includes hardware for executing computer program instructions by retrieving the instructions from an internal register, an internal cache, or other memory or storage device, and decoding and executing them. The memory can be used for storing data or instructions for execution by the processor. The memory can be any suitable storage mechanism, such as RAM, ROM, flash memory, solid state memory, and the like. The storage device can store data or computer instructions, and can include a hard disk drive, flash memory, an optical disc, or any other suitable storage device. The I/O interface allows a user to interact with the computing device, and can include a mouse, keypad, keyboard, touch screen interface, and the like. The communication interface can include hardware, software, or a combination of both, and can provide one or more interfaces for communication with other devices or entities. Some portions of this description describe the embodiments of the invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combinations thereof. Any of the steps, operations, or processes described herein may be performed or implemented with one or more hardware or software modules, alone or in combination with other devices. In one embodiment, a software module is implemented with a computer program product comprising a computer-readable medium containing computer program code, which can be executed by a computer processor for performing any or all of the steps, operations, or processes described. Embodiments of the invention may also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, and/or it may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a non-transitory, tangible computer readable storage medium, or any type of media suitable for storing electronic instructions, which may be coupled to a computer system bus. Furthermore, any computing systems referred to in the specification may include a single processor or may be architectures employing multiple processor designs for increased computing capability. Embodiments of the invention may also relate to a product that is produced by a computing process described herein. Such a product may comprise information resulting from a computing process, where the information is stored on a non-transitory, tangible computer readable storage medium and may include any embodiment of a computer program product or other data combination described herein. Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims. | 175,584 |
11943681 | DETAILED DESCRIPTION OF THE INVENTION The present detailed description is intended to illustrate the invention in a non-limitative manner since any feature of an embodiment may be combined with any other feature of a different embodiment in an advantageous manner. In the method of the present invention, one first assumes a set of cell sites and towers distributed in a certain region and operating for a certain period of time giving support to a certain number of devices. Each device and each antenna are univocally identified. At each site, the metadata of every telecommunication events concurring at its coverage area along this period of time are collected, and all the data is centralized in a single or multiple set of data, the CDR. At this point, the method of the invention carries out three steps: The first step is a structuring step where CDR raw metadata is filtered so as to identify the fields of: device identification, cell site identification, date, and time. Once filtered, the data frame is generated and sorted by user, by date, and by time, preferably in this hierarchical order. The second step is a projecting step into an occupancy grid where locations are defined and univocally identified by groups of sites or towers, were groups are allowed to be composed of a single site, and time is divided in bins of arbitrary size. For each device, events are projected into a location vs. time-bin matrix which we will call the occupancy grid in the following description. In an occupancy grid G, the value of the entry G (time, location) is proportional to the certainty that the device was present at location at some point during the time-bin time, given the events registered. Since the sites and times can be grouped such that a device visits more than one location during a given time-bin, the values of the occupancy grid are in principle independent of each other. To project the events into this grid, one defines the network of conditional probabilities P=p(L|E) denoting the probability that the device visited the location L given that a series of events E is registered during that time bin. Given the events and the conditional probabilities P, a maximum likelihood analysis provides a closed-form for the values of the occupancy grid as G=11+exp(-∑i=0nsi)wheresi=log{p(L|Ei)}/log(1-p(L|Ei)}. In practice, the simplest implementation of this method consists of the following steps:1. Assign a positive number h>0 to the belief of a device being in a certain location if we have an event on that location.2. Assign a negative number m<0 to the belief of a device not being in a certain location if we have an event on another location. Typically, one wants |m|<|h|.3. Start a matrix S of size (num. of locations)×(num. of time-bins) with all the entries set to 0.4. For each event registered, add h to the entry of S corresponding to the location of that event, and subtract m from every other entry at that time-bin.5. Finally, compute the occupancy grid as G=1/(1+exp(−S)). The projection onto the occupancy grid generates a probabilistic map of a device's location in space and time as opposed to a single inferred trajectory. Thanks to this method, the projection is known to effectively provide an outlier filtering of the registered events, and is thus a first layer of automated, general, filter of CDR events. Also, it provides a measure of uncertainty in the information that traditional trajectory-filtering methods do not provide: if the events registered for a certain device switch erratically between locations the resulting occupancy grid will have very low values at all locations—signifying high uncertainty—that are easy to filter out in the third stage. The third step is a filtering step consisting in filtering devices and events for human mobility purposes where the method uses an analysis of the patterns observed in each user's occupancy grid to filter those that accurately represent human mobility from patterns that reflect errors, uncertainties, or patterns not related with real human mobility as machine-to-machine telecommunications, call centers, or technology-related false positives as changes on the connection to sites even if the device has not changed its position. The desired filters for discarding devices or events that do not contribute to the analysis of human mobility are defined at this stage and comprise the following: (i) Duplicated devices: if more than one person is using the same number or duplicated SIM cards, it is registered at the CDR as a single device but with overlapping events. Overlapping activity has a distinguishable imprint when projected to the occupancy grid. If that pattern is detected at the occupancy grid of a device, that device is rejected for next analysis. (ii) Machine-to-machine: if two devices (or a network of them) communicate each other in a regular basis and systematically from the same locations, the occupancy grid takes a distinguishable pattern. If this pattern is detected, those devices are rejected for mobility purposes. (iii) False mobility positives: in locations covered by several sites, the device may dynamically switch its connectivity between even if no movement is related with the event. This effect generates a characteristic “ping-pong” pattern in the occupancy grid for adjacent cells. When this pattern is detected, probabilities are uniformly corrected. (iv) False occupancy positives due to saturation of the network: when a cell is reaching its maximum capacity, nearby cells are assigned to handle the extra events. This effect generates a false positive in the occupancy grid. Probabilities are distributed assigning a higher probability to the saturated antenna, as potential real location of the device. The present invention provides several advantages among which an enhanced versatility because this method explicitly encodes the assumptions made about the nature of the data into the parameters of P, h and m. Therefore, it allows to formulate and test a large number of hypotheses about the mechanical working of the CDRs in particular areas of interest and compare the results by tuning P. Given enough data, this framework also allows to apply machine learning techniques to “train” the values of P. Also, it provides an improved scalability since the method is linear in time with respect to the number of registered events and linear in memory with respect to the number of locations considered. In contrast with traditional interpolation/filtering techniques, it only requires a single read of each event and does not need to store any temporary values other than the additive matrix S. As such, the algorithm fits into a map-reduce framework that is optimal to analyze large datasets. Finally, it is iterative. In fact, by storing the values of S described above, the occupancy grid can easily accommodate new data by just updating S as per point 4 in the algorithm. This also means that we can set up a feedback loop where the analysis of movement patterns using the occupancy grids of a large collection of devices can be included itself as new data points into the computation of the occupancy grid. When carrying out the above method it is also important that the calibration considers that mobile phone users do not use the device in a regular basis in time allowing for a continuous localization of the device. In order to improve this method, these activity gaps require to be filled with an educated guess to have a complete picture of the mobility patterns and consider cell sites and towers as accurate devices for this purpose. A preferred embodiment of the present invention uses physical concepts to describe, reproduce and predict collective human behavior. Using this framework, the preferred embodiment of the present invention can use quantum physics principles where a Hilbert space is used as representation of the underlying dynamics and the device's activity is represented as a superposition of eigenstates of a pseudo-Hamiltonian. The extrapolation of this superposition is assumed as an accurate representation of the missing information in the activity gaps. In this fashion, the reconstruction is self-consistent and data-driven as no external guesses or models are introduced. The reconstruction allows to use cell sites and towers as accurate devices for human tracking, obtaining a complete picture of mobility patterns. More particularly, described below is a procedure to fill these gaps self-consistently with the collected data without introducing external assumptions or modelizations. As mentioned, the method is based on social physics and described using bracket notation, as many of the concepts used in its derivation are borrowed from quantum physics (Hilbert spaces, superposition of states, density matrices, etc.). In analogy to quantum mechanics, one defines a state as the full set of amplitudes of probability of finding a device at a location at a time, represented as a vector in a high-dimensional vector space. A set of the most complete states is used first to define the Hilbert space describing the underlying dynamics from the diagonalization of the density matrix. Assuming a thermal equilibrium maximizing the entropy of the system, the eigenstates and occupation numbers obtained from the diagonalization of the density matrix are used in a second step to define the pseudo-Hamiltonian which is the generator of all dynamical states, and responsible of their evolution. Thus, any trajectory in space and time of any device is expressed as a superposition of the eigenstates of the pseudo-Hamiltonian. The superposition is assumed to accurately reproduce the dynamical state for all positions and time. Thus, its extrapolation to the gaps represents an accurate reconstruction of the missing information. Once the gaps are filled, one considers that the dataset is accurate enough to describe the full picture of human mobility in that region. In more details, one first assumes a set of Nccell sites and towers distributed in a certain region at positions ri(i=1, . . . Nc) and operating for a certain period of time T giving support to a certain number of devices N. Each device and each antenna are univocally identified with an integer α(α=1, . . . , N) and i respectively. At each site, the metadata of every telecommunication event concurring at its coverage area along this period of time are collected, and all the data is centralized in a single or multiple set of data, the CDR. One assumes that one can define from the data extracted from the CDR (or the occupancy matrix) the probability of finding device a at the area covered by site i at time t as pα(ri, t). This probability fulfills the normalization condition 1T∫τdt∑i=1Ncpα(ri,t)=1,(1) which is automatically fulfilled if ∑i=1Ncpα(ri,t)=1(2) or, in other words, if the probability of finding device a at any location at time t is equal to 1. One then introduces the bracket notation and define the state |ri,tas a vector containing all information about location (i) and time (t). More generally, one defines |αas the state of the device a as a vector which components are the amplitudes of probability for each location and time, defined as ❘"\[LeftBracketingBar]"α〉=1T∫Tdt∑i=1Ncϕα(ri,t)❘"\[LeftBracketingBar]"ri,t〉,where(3)ϕα(ri,t)=pα(ri,t)eisα(ri,t).(4) At this point, the value of the phase sα(ri,t) is arbitrary and undefined, so in lack of a better choice one sets sα(ri,t)=0 for all α, i and t. It can be proved with this definition thatα|α=1, fulfilling the normalization condition. Then one defines a pseudo-Hamiltonianas generator of the system's dynamics. The eigenstates |mofare orthonormal and define a complete Hilbert space able to describe any arbitrary dynamical state |αwhich is taking place in the system. In terms of the location-time states one writes ❘"\[LeftBracketingBar]"m〉=1T∫Tdt∑i=1Ncψm(ri,t)❘"\[LeftBracketingBar]"ri,t〉.(5) The system can be then univocally characterized by the density matrix ρ=∑m=1NNm❘"\[LeftBracketingBar]"m〉〈m❘"\[RightBracketingBar]"(6) where Nmare the occupancy of state m with Σm=1NNm=N (as shown below). The density matrix elements can be obtained in the empirical non-orthogonal basis set of states constructed from the CDRs as ραβ=〈α❘"\[RightBracketingBar]"1❘"\[LeftBracketingBar]"β〉=1T∫Tdt∑i=1Ncϕα(ri,t)ϕβ(ri,t).(7) It can be shown that ρ contains the same information in any base, meaning that this representation of ρ and the one expressed in terms of the eigenstates ofare univocally related. Thus, since the eigenstates |malso are eigenstates of ρ, they can be obtained from the diagonalization of ρ in its form in the empirical non-orthogonal basis. The eigenvalues obtained are the above-mentioned occupancy, representing the number of devices in each eigenstate |m. Indeed, it is a well-known property that the trace of ρ is conserved in any base, thus Trp=∑α=1N〈α❘α〉=∑m=1NNm=N(8) Assuming that the system is in a thermal equilibrium described by the maximum entropy principle, the occupancy numbers are related with the eigenvalues ∈mof the Hamiltonian as Nm=ce−∈m/k, where c=N/Σm=1Ne−∈m/kand k is an arbitrary thermal constant. The Hamiltonian can be reconstructed as ℋ/k=-∑m=1Nln(Nm)❘"\[LeftBracketingBar]"m〉〈m❘"\[RightBracketingBar]"+C(9) where C is a constant that does not affect the dynamics. Then one defines an uncomplete state |ωdefined oy in a subspace of time T′ contented in T. In order to use the eigenstates |mto describe |ω, siders the lack of orthonormality of the basis in the subspace defined by T′, writing ❘"\[LeftBracketingBar]"ω〉=∑m=1Nam❘"\[LeftBracketingBar]"m〉where(10)am=1T′∫T′dt∑i=1Ncϕω(ri,t)∑m′=1N(S-1)mm′ψm′*(ri,t)(11) being S−1the inverse of the overlap matrix defined as Smm′=1T′∫T′dt∑i=1Ncψm(ri,t)ψm′*(ri,t)(12) Once one obtains the set of coefficients αm, representing the overlap of state |ωwith the eigenstates of the pseudo-Hamiltonian, one extends the same coefficients beyond T′ to all period T. The final step to the reconstruction is to obtain the probabilities for times outside the domain of T′ as pω(ri,t)=❘"\[LeftBracketingBar]"∑m=1Namψm(ri,t)❘"\[RightBracketingBar]"2.(13) The fitness of the reconstruction can be easily obtained from the correlation between the set of components ϕω(ri,t) and Σm=1Namψm(ri,t) in T′. In summary, the gap filling/reconstructions method comprises the following steps:1. Represent the events registered at CDR as vectors which component are the amplitude of probabilities of occupation for each location and time, as in Eq. (3).2. Construct the density matrix from the most complete vectors set, as in Eq. (7).3. Diagonalize the density matrix obtaining a basis of orthonormal vectors, assuming that basis are also the eigenvectors of the underlying pseudo-Hamiltonian.4. For any incomplete vector, obtain the coefficients of this vector in the basis of the pseudo-Hamiltonian limited in the subspace where this vector is defined, as in Eq. (11).5. Extrapolate these coefficients to the subspace where the vector is not defined.6. Obtain the probabilities of occupation as the square of the obtained amplitudes as in Eq. (13). As explained above, cell sites are distributed in space with the goal of exhaustively covering all the surface of a region with potential human activity to provide signal to any device at any point. Because of the technological limitations of the cell's band width, more antennas are needed in populated areas to guarantee total coverage to all potential activity. This generates a distribution for the location of the cells that empirically mimics the density of population, with a denser grid in urban areas and a scattered one in rural areas. Assuming that the closest cell is the one providing a better signal for the device, the surface of the region can be divided by Voronoi cells following the locations of the sites. In this fashion, we can consider that a device is located at any point inside the Voronoi cell when an event is registered at that site. Thus, a sequence of events defines a path in the Voronoi grid, cell by cell. Even if this representation has some advantages for measuring human mobility over other technologies, it is still unsatisfactory for many applications as the location or exact path of the device along the roads and streets of the region is not defined, with the corresponding loosing of accuracy. Another embodiment of the invention relates to a method to accurately project the trajectories defined at the Voronoi grid defined by the sites and towers to the road and street grid. We make use of virtual agents moving randomly inside the road grid mimicking the movements of users in the real world, and select those which path and velocity are compatible with the events registered (or reconstructed) at the CDRs. We assign a probability or likelihood to each agent to represent the pattern that generates the observed events and aggregate all the agent's paths weighted by this likelihood to be used as a statistical measure of the empirical human mobility of the region. The procedure can be applied one-to-one (one agent to fit the events of one device) or all-to-all (the same number of agents as users to fit the aggregated set of events). The all-to-all procedure is applied when the anonymity and privacy of the users is required. The outcome of the procedure is a set of trajectories or paths at the level of roads and streets with attributes of time, path length and velocity. According to this method, one first assumes a set of Nccell sites and towers distributed in a certain region at positions ri(i=1, . . . Nc) and operating for a certain period of time T giving support to a certain number of devices N. Each device and each antenna are univocally identified (as much as technically possible) with an integer α (α=1, . . . , N) and i respectively. At each site, the metadata of every telecommunication event concurring at its coverage area along this period of time are collected, and all the data is centralized in a single or multiple set of data, the CDR. For each CDR labelled with j, we generate a pair (ijα,tjα) locating the event at site i at time tjfor user α. We define now the road graph as the network which nodes are crossings or junctions and vertex are the roads and streets of the region. We define Nv>N virtual agents or random walkers that will move from node to node following the rules defined by the grid (first neighbors, directions, velocities, etc). The procedure follows:1) Every walker x starts at a different random node of the road network, at a random initial time t0xinside the interval T.2) In a series of consecutive steps k=1, 2, 3 . . . , the walkers move to a random first neighboring node at each step, for a random maximum number of steps kmx. A velocity vkxis assigned randomly at each step, as the mean velocity of the walker along that vertex. We define a trajectory as the path followed by the walker along the graph in the series of steps. The final time of the path is obtained from the initial time t0xplus the time required to travel along each vertex in each step Δtkx=vkx/dkx, where dkxis the distance travelled at that same step along the vertex, as tfx=t0x+∑k=1kmxΔtkx. The average velocity of the full path for walker x is then 〈v〉=∑k=1kmxvkxtkx/T, where the time per step is considered. We now assign a likelihood for each walker as the probability that its path generates a sequence of events as those observed at the CDRs. For the one-to-one case (N=1), where we have a sequence in time of n events {(ijα,tjα)}j=1nfor user α, we apply the equation: Lx=∏j=1nP(rijα|rx(tjα))(1) where P(ri|rx) is the probability of generating an event in antenna i from a location rxand rx(t) is the position of walker x at time t. For the sake of simplicity, we consider for P a power law with quadratic decay in the distance for the intensity of the signal, which is normalized considering all the neighboring antennas as: P(ri|r)=❘"\[LeftBracketingBar]"ri-r❘"\[RightBracketingBar]"-2∑i′=1Nc❘"\[LeftBracketingBar]"ri′-r❘"\[RightBracketingBar]"-2(2) For the case of all-to-all (N>1), we extend eq. (1) to all antennas and all events as: Lx=∏α=1jN∏=1nP(rijα|rx(tjα))(3) for all walkers x. Next, we assign to each walker a weight according to his likelihood Lx. For a statistical representation of the real trajectories, we use this weight to select the N fittest walkers, or N′>N of the fittest walkers normalizing their contribution as wx=Lx/Σx′N′Lx′. In this fashion, w represents an estimation of the fraction of people—note that wxdoes not need to be 1 anymore—that has followed the path defined by walker x. However, since walkers are not fitted to individuals in the all-to-all case, it is important to notice that the meaningful statistical measures are those made at the level of aggregation of N walkers, as for instance the number of walkers crossing a preselected road, or the number of walkers with certain location for origin or destination of their trajectories. In this way, the final output in a set of paths along the road graph with attributes of time, distance, and velocity, with a real number representing the relative weight of the contribution of each path. While the embodiments have been described in conjunction with a number of embodiments, it is evident that many alternatives, modifications and variations would be or are apparent to those of ordinary skill in the applicable arts. Accordingly, this disclosure is intended to embrace all such alternatives, modifications, equivalents and variations that are within the scope of this disclosure. This for example particularly the case regarding the different apparatuses which can be used. | 21,828 |
11943682 | DETAILED DESCRIPTION OF THE EMBODIMENTS As mentioned, a list-based commissioning method (by a user with a device with a user interface) may be a tedious effort, e.g. in commissioning large networked wireless lighting system, because the process to populate nodes in said user interface may take too long, the scanning has to be repeated continuously, and/or the established list may provide an inaccurate representation of the nodes due to changes in the position of the user. Thereto, this application provides a mobile device, a system and a method according to the invention to overcome such drawbacks. FIG.1depicts schematically, by non-limiting example, a system100comprising a mobile device10according to the invention and a plurality of nodes20.FIG.2depicts schematically, by non-limiting example, details of the mobile device10. The plurality of nodes20are located within an area15. The plurality of nodes20comprises a first set of lighting devices21,22respectively consisting of a right luminaire21and a left luminaire22; a second set of lighting devices23,24respectively consisting of a right luminaire23and a left luminaire24; a first sensor device25; and a second sensor device26. All of said devices21,22,23,24,25,26are smart devices and have wireless connectivity. Here, the sensor devices25,26are microphones, but may alternatively be any other sensor such as e.g. motion sensor, light sensor, PIR sensor, camera sensor, tactile sensor, etc. Said lighting devices21,22,23,24, and said sensor devices25,26(that is: the plurality of nodes20) form a wireless network30. The wireless network30is a ZigBee network, but may alternatively be any other wireless modality. Here, the wireless network30requires commissioning the first set of lighting devices21,22and the left luminaire24of the second set of lighting devices23,24to the first sensor device25, thereby forming a first group; and only the right luminaire23of the second set of lighting devices23,24to the second sensor device26, thereby forming a second group. Consequently, the lighting devices21,22,23,24and/or the sensor devices25,26send out a wireless beacon and/or an advertisement (message). Said mobile device10is suitable for commissioning said devices21,22,23,24,25,26(i.e. the plurality of nodes20) by means of receiving an advertisement of said plurality of nodes20. Namely: A commissioning engineer17, using and/or holding said mobile device10, walks around in said area15along a path16and commissions each respective node of the plurality of nodes20(i.e. each of said respective devices) based on the beaconed advertisement message thereof. Thereby, the commissioning engineer17may stand still when commissioning the respective nearby nodes of the plurality of nodes20(i.e. said devices). In the present embodiment, only a limited number of nodes (i.e. six) is depicted for convenience, but in further examples said plurality of nodes may represent a large-scale network, e.g. with at least twenty or at least forty lighting devices and/or sensor devices. Referring toFIG.2as well, as partly mentioned, the mobile device10is arranged to receive such an advertisement (message). The mobile device10comprises a motion sensor11, a controller12, a radiofrequency transceiver13and a user interface14. The user interface14is a touchscreen display, which is configured to receive a user input, e.g. from the commissioning engineer17. The motion sensor11is an accelerometer, but may alternatively be a gyroscope or a camera. Thereby, the motion sensor11determines the motion of the mobile device10and outputs this motion to the controller12. For example, the motion of the mobile device10moving along the path16can be determined; it may further be detected whether the mobile device10is motionless (e.g. standing still), whether the mobile device10is changing orientation (e.g. turning, tilting the mobile device10), and/or whether the mobile device10is not moving away from a location on said path16. Hereby, said path does not have to be predetermined but may be established simultaneously. The controller12is configured to receive the motion of the mobile device10, as determined by the motion sensor11. The radiofrequency transceiver13receives an advertisement of the plurality of nodes. The transceiver13is a ZigBee transceiver, but may alternatively be e.g. a combo-chip for both ZigBee or Bluetooth. That is: the radiofrequency transceiver13receives the respective advertisement of each device within range. Here, at a first location18on the path16in the area15, the radiofrequency transceiver13receives the respective advertisement of the second set of lighting devices23,24and the second sensor26; but also receives the respective advertisement of the first set of lighting devices21,22and the first sensor25, albeit at a lower signal strength due to the larger distance thereto from the first location18. Here, at the second location19on the path16in the area15, the radiofrequency transceiver13receives the respective advertisement of the first set of lighting devices21,22and the first sensor25; but also receives the respective advertisement of the second set of lighting devices23,24and the second sensor26, albeit at a lower signal strength due to the larger distance thereto from the second location19. Thus, said range may be determined by the signal strength of the beaconing/advertisement signal, i.e. weak signals may e.g. not be received. Alternatively, said controller may disregard signals below a signal strength threshold. The controller12is configured to obtain each respective advertisement via the radiofrequency transceiver and parse said advertisement. All obtained parsed advertisements are displayed on a list144on the user interface14. Alternatively, or additionally, said advertisements may thereby be displayed as advertisement data indicative of the advertisement, thus not literally taking over the advertisement but having some processing in between to arrive at advertisement data suitable for display on the user interface14. Displaying a list comprising the parsed advertisement of the plurality of nodes20on the user interface14(i.e. the touchscreen display14) may however take an undesired long period of time (e.g. several seconds) in which a user (i.e. the commissioning engineer) of the mobile device10has to wait, and/or a previously established list may not be representative due to the movement of the user. This may have a negative influence on the user experience and/or commissioning process. Such a negative influence on the user experience may even be worse given that a user may have to perform the steps of such a commissioning procedure multiple times for a large networked wireless lighting system. The mobile device10according to the present invention therefore improves such commissioning. Namely, the controller12is configured to obtain and parse the advertisement of the plurality of nodes20, when the mobile device10is in a first motion. The first motion is the mobile device10moving along the path16. Thus, during the first motion of (the commissioning engineer17) moving along the path16, the controller12may continuously obtain and parse the advertisement of the plurality of nodes20in range in the background. Alternatively, the controller may be configured to parse said advertisement when the mobile device is moving along said path for at least a predetermined period of time, such as e.g. one second or two seconds, or alternatively at least four seconds. Moreover, the controller12is also configured to display a list144comprising the parsed advertisement of the plurality of nodes20on the user interface14, when the mobile device is in a second motion. The second motion is the mobile device10not moving away from a location on said path16, i.e. the first location18and/or the second location19. Not standing still may for example be standing still to perform the commissioning. Therefore, also referring toFIG.4in addition toFIG.1, the list144comprising the obtained and parsed advertisement of the plurality of nodes is displayed immediately on the user interface, when the commissioning engineer17is in the second motion (i.e. not moving away) at the first location18and/or second location19. Since displaying said list144merely requires a change of the displayed user interface14, because the advertisement of the plurality of nodes has already been parsed (in the background) when the mobile device10was in the first motion (i.e. moving along said path16), unnecessary periods of time waiting for the list to be ‘populated’ is avoided and a more representative list is provided for commissioning (e.g. the list order is always reflecting the distance from the current position of the commissioning engineer). Consequently, an accurate list144of the advertisement of the plurality of nodes20is displayed (or: provided) instantaneously on the user interface14. Therefore, the present invention advantageously improves the commissioning of at least one node of the plurality of nodes20and the ergonomics of displaying such a list144. Still referring to embodiment depicted inFIGS.1and2, but as additional and/or alternative features, the commissioning engineer17performs a commissioning step. Here, also referring toFIG.4in addition toFIG.1, the advertisement of the plurality of nodes20comprises their respective identity821,822,823,824,825,826. The list144therefore comprises the entries indicative of the parsed advertisement of the nodes on the user interface14. Moreover, based on the received advertisement of each respective node of the plurality of nodes20, the controller determines the RSSI value indicative of the distance between the respective node and the mobile device10. In alternative embodiments, not depicted, the RSSI value of the plurality of nodes may be a time-averaged RSSI value. Moreover, the advertisement of the plurality of nodes20comprises a respective commissioning status of the respective node. Here, none of the devices21,22,23,24,25,26is commissioned yet; hence their respective advertisement comprising a commissioning status of e.g. ‘to be commissioned’. This is not explicitly depicted inFIG.4. As a result, the user interface14displays the list144, wherein the list144comprises the identity and the commissioning status of each respective node of the plurality of nodes20. The list is also hierarchically ordered by RSSI value of the plurality of nodes20, depending whether the commissioning engineer17and the mobile device10the commissioning engineer is holding is at the first location18or the second location19. At the second location19, the list144is populated such that the first set of lighting devices21,22and the first sensor device25are on top of the list compared to the second set of lighting devices23,24and the second sensor device26; because first set of lighting devices21,22and the first sensor device25are closer to the second location19compared to the second set of lighting devices23,24and the second sensor device26. This hierarchy is not depicted in the figures. Furthermore, the commissioning engineer17, when being at the second location19, wants to commission the right luminaire23of the second set of lighting devices23,24to the second sensor device26. However, as the right luminaire23and the left luminaire24of the second set of lighting devices23,24is approximately at a similar further distance away compared to the first set of lighting devices21,22for example, the commissioning engineer17cannot clearly judge which advertisement and/or entry on the displayed list144is the left luminaire23or the right luminaire24of the second set of lighting devices23,24. Hereby noting that even though the identity may be known, said luminaires may still be switched when installing. Therefore, the commissioning engineer17selects with a user input to the touchscreen display14either one of the advertisements (i.e. e.g. entries) of the further away luminaires23,24of the second set of lighting devices21,22. The selection here is the entry and/or advertisement belonging to the right luminaire24of the second set of lighting devices23,24. This user input allows the controller to control the radiofrequency transceiver to send a control command to the right luminaire24of the second set of lighting device23,24to control this right luminaire24to emit a visual cue. Noting the visual cue, the commissioning engineer27knows which luminaire is the right luminaire23and which luminaire is the left luminaire24of the second set of lighting devices23,24. Such blink trials may therefore be advantageous in identifying luminaires during commissioning. As the list144of the present invention is more accurate and always reflecting the distance from the current position of the commissioning engineer, advantageously less blink trials are required. Furthermore, the commissioning engineer17, when being at the second location19, selects with a user input to the touchscreen display14the first set of lighting devices21,22, the first sensor device25and the left luminaire24of the second set of lighting devices23,24; and subsequently groups these nodes21,22,25,24together in the first group. Hence, a user input may comprise assigning a node indicated on the list144to a group. Similarly, the right luminaire23of the second set of lighting devices23,24is grouped with the second sensor device26. This completes the desired commissioning of the plurality of nodes20in terms of grouping devices. In an embodiment (not depicted), which is partly similar to the embodiment depicted inFIGS.1and2, but now the controller12is configured to provide alternative and/or additional features. Namely, the controller12is configured to run a first application related to positioning and output said application related to positioning on the user interface14when the device is in the first motion, i.e. when the mobile device10(hence the commissioning engineer17) is moving along said path16. Alternatively, said first application may be related to mapping and/or navigation. Yet alternatively, said first application may be related to communication, for example to allow the commissioning engineer to communicate with other commissioning engineers or a central command center. Since the first application relates to positioning and is run when the mobile device10(hence the commissioning engineer) is moving along said path16, the commissioning engineer17may advantageously orient himself/herself within the area15from e.g. the first location18to the second location19; whereas when not moving away from such a location18,19the controller displays the list144comprising the parsed advertisement of the plurality of nodes20on the user interface14. This facilitates the commissioning process and provides an intuitive user interface switch of functions. FIG.3depicts schematically, by non-limiting example, a method300of displaying a list suitable for commissioning at least one node with the mobile device according to the invention, e.g. the mobile device depicted inFIG.2. The method comprises the step301of determining a motion of the mobile device, the step302of receiving an advertisement of the at least one node, and step303of obtaining and parsing the advertisement of the at least one node, when the mobile device is in a first motion, the first motion being the mobile device is moving along a path. Similarly, to the embodiment depicted inFIG.1andFIG.2, said determining the motion may be performed by means of an accelerometer, said obtaining and parsing may be performed by means of a radiofrequency transceiver, and said obtaining and parsing of the advertisement by means of a controller of the mobile device. The at least one node may for example be a lighting device and/or a dedicated sensor device or actuator device. Furthermore, the method comprises the step304of displaying a list comprising the parsed advertisement of the at least one node on the user interface, when the mobile device is in a second motion, the second motion being the mobile device not moving away from a location on said path. Additionally, in further embodiments, when at said location on said path, the method further comprises step305of receiving a user input comprising selecting a node of the at least one node from said list; and step306of sending a control command to said node in response to said user input of selecting said node, wherein the control command is arranged for controlling said node of the at least one node to emit a visual cue; and step307of assigning said node of the at least one node to a group. FIG.5depicts schematically, by non-limiting example, a second example of a user interface of an embodiment (not depicted explicitly) according to the invention, which is partly similar to the embodiment depicted inFIG.1andFIG.2, but wherein the controller is configured to display an entry indicative of the parsed advertisement of only a first node921of the plurality of nodes on the user interface914, when the mobile device is in the second motion according to the invention. Thus, the mobile device according to the invention, e.g. according to the embodiment depicted inFIG.2, wherein the controller is configured to obtain and parse the advertisement of a plurality of nodes, when the mobile device is in a first motion being moving along a path as indicated above. The controller is further configured to establish said list comprising the parsed advertisement of the plurality of nodes, but only display said first node (of the plurality of nodes) (of said list) on the user interface, when the mobile device is in a second motion being not moving away from a location on said path. Here, the first node921is node with the highest RSSI value. The user interface914is a touch screen display. Here, the controller is configured to receive a user input, which is a touch-based selection of a button902to either go to the next node in the established list or a touch-based selection of a button901to go to the previous node in the established list. Connected lighting systems may be commissioned via a mobile device according to the present invention. The mobile device according to the invention may instead of a radiofrequency transmitter comprise a dongle which can convert a signal from the mobile device to an IR signal, so as to transmit commands for commissioning and/or configuring nodes of a connected lighting system. Communication between mobile device and such a dongle can be done via Bluetooth or via an audio output of the mobile device, e.g. when the mobile device may be a smartphone comprising such an audio output. Hence, in further aspects, the present application provides a device for and a method of converting an audio signal at an audio output of a mobile device to an IR signal. Said device may be suitable for commissioning and/or configuring a connected smart system, such as a connected lighting system. Namely: The device comprises an audio output and a dongle connected thereto. Both channels of an audio output, i.e. a ‘first’ channel LEFT and a ‘second’ channel RIGHT, as commonly known in the art, are used. That is, the first channel is used for a clock signal and the second channel for a data signal. The clock signal will always be present before the data signal is present and can therefore be used for waking up the dongle-circuit. The data signal will be used for creating an IR signal (i.e. e.g. a modulated signal). The device may be a smartphone. In some examples, the audio output may be inverted. This means that both the clock signal and the data signal will be inverted. An inverted data signal will result in an inverted IR signal, which may not be recognized by a node receiving said IR signal. Therefore, the dongle may be configured to detect its polarity by checking the clock signal and the data signal at any time, i.e.: at normal (correct) polarity, the transitions (High to Low′ or low to High′) of the data signal will take place at a positive edge of the clock signal; at not normal (inverted) polarity, the transitions of the data signal take place at a negative edge of the clock signal. This method works as long as there is a well-defined phase relation between the clock signal and the data signal, and the pulse period of the clock signal is equal to the smallest ‘high’ or ‘low’ interval in the data signal. Supposing the device being a smartphone: A different way to detect the polarity which only uses the second channel with the data signal is to make use of the fact that in some RC protocols (e.g. the Philips RC6 protocol) the first bit of the data signal is longer than the next one. This means that the length of the first ‘high’ period that is detected in the dongle depends on the polarity of the signal. For example, in case of a RC6 mode 1A payload, the first ‘high’ period that the dongle would see is 2.666 microseconds long if the polarity is not inverted, whereas it is 0.888 microseconds long in case the polarity was inverted by the smartphone audio output stage. By measuring the length of the first high bit it is therefore in this case also possible to find out whether the signal polarity was inverted or not. Though in this case the clock signal for detecting the polarity is not needed, it might still be preferential to send it on the other channel in order to use it as a ‘wake-up’ signal for the dongle in order to save battery power. Once the dongle has determined that the data signal is inverted, there are several ways to fix the problem: (i) Supposing the node to be commissioned being a lighting node, a visual feedback can be given by e.g. a LED of the lighting node blinking to indicate that the polarity is not correct. Based on this feedback, a commissioning engineer can select a function in the application software on the (smartphone) device to invert the signal. This will lead to an invert of the audio signals which results in a correct IR signal. (ii) The dongle can reconstruct the signal to a correct signal by inverting the incoming data signal and sending out the corresponding IR signal. (iii) Instruct an installed application on the device (e.g. smartphone) to invert the signals. A microcontroller in the dongle may recognize that the signals may not be not aligned in phase and replies with a signal on the microphone input of the audio connector to the e.g. smartphone. The installed app receives this audio feedback and inverts the output signals. As long as the signals are aligned, there will be no feedback on the microphone input of the audio connector, meaning that the installed app can continue. The advantage of this method is that there will be no ‘wrong’ IR message transmitted, the IR message is terminated right after the first not aligned detection and restarted in the correct phase. The commissioning engineer may not be aware of any smartphone audio output mismatch. | 22,935 |
11943683 | Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION Methods, systems, and computer readable media described herein can be operable to facilitate location determination, communications with an AFC system, configuring operational parameters in response to an identification of active 6 GHz paths, and timing distribution and low-latency services. Methods, systems, and computer readable media are described herein for implementing and improving use of automated frequency coordination (AFC), operational deployment of the 6 GHz band for unlicensed devices, and use of the 6 GHz band for low-latency services, timing distribution, and QoS. Automated Frequency Coordination (AFC) FIG.1shows an example network100operable to facilitate device management based upon a determination of proximity to one or more exclusion zones. In embodiments, operation of a device (e.g., an access device such as an access point (AP)105and/or one or more stations110associated with the AP105) may be dependent upon communications with an AFC system115. An AP105as described herein may include a RLAN (radio local area network) device, a WLAN (wireless local area network), and any other device configured to facilitate wireless communications with other devices. The AFC system115may include a database that contains pre-calculated exclusion zone data for one or more microwave paths. It should be understood that spectrum availability may be calculated upon request. The exclusion zone data may be updated at the database periodically (e.g., hourly, daily, etc.) or in response to an addition or deletion of data associated with a microwave path. Communications between a device and the AFC system115may be over wired or wireless links not in the 6 GHz band. The AFC system115and its database may be connected to a packet-based wide area network (e.g., wide area network (WAN)120), including but not limited to the Internet. Each of one or more devices (e.g., AP105) may register with the database. Initial registration and query may be made outside of the 6 GHz bands. In embodiments, each device (e.g., APs105) may also register devices that are associated with the device (e.g., STAs (stations)110, clients, etc.). Each device may query the database with location information (e.g., location information associated with a current location of the device), an identification of the device type, identifying information (e.g., unique identifiers), and/or other information associated with the device. Based upon the query received from each respective one device, the database may determine a proximity of the respective device to one or more exclusion zones. A device (e.g., AP105) may automatically determine a geographic location at which the device is currently positioned and/or a location at which the device has been installed. For example, GPS, cellular triangulation, or other systems may be utilized to determine a location of the device. A device may alternatively or additionally be proved using location information through a local user interface or remotely through a provisioning or status interface. In embodiments, the device may include an internal GPS through which the device may determine its current location. The internal GPS may be utilized by a device that is installed at an outdoor location. In embodiments, the device may communicate with a detached GPS receiver to determine a current location of the device. For example, the GPS receiver may be installed at an outdoor location while the device may be installed at an indoor location. With the location of the GPS receiver being known, the device may determine its own location using one or more Wi-Fi location determination features to map back from the GPS receiver's location. For example, the device may measure a signal strength and/or direction component associated with one or more wireless signals received at the device, and the measurements may be used to identify a location of the device relative to the GPS receiver. A STA (station)110(e.g., wireless extender, etc.) may determine its location by wirelessly communicating with the device (e.g., AP105). The STA110may determine its location relative to the device. For example, the wireless extender may use one or more Wi-Fi location determination features (e.g., signal strength, direction component associated with one or more received signals, etc.) to map its location relative to the device. It should be understood that cellular triangulation may be used in place of GPS. Other satellite-based location determination services may also be used in the place of GPS, such as Galileo. The device (e.g., AP105) may be manually configured with device location information. In embodiments, a technician (e.g., licensed technician or installer) may configure the device with location information once the device has been installed. For example, the device may be configured with a trusted certificate, blockchain, or other information to be used to authenticate a location of the device that is manually provided. The device (e.g., AP105) may be provided location information through a provisioning server or configuration server. In embodiments, a provisioning server may have information about the address of a customer deploying the device and may provide that address information to the device. In embodiments, the device (e.g., AP105), or an upstream device (e.g., controller of the AFC system115), may be configured to detect a movement of the device. The device, or upstream device, may be configured to determine a current location of the device in response to a triggering event. Triggering events may include, but are not limited to, the following: reboot of the device, detection of a loss or addition of a STA from which communications are received by the device, and others. In embodiments, a co-located device (e.g., AP (access point)) may determine that another co-located device has moved based upon a change in location that is indicated by one or more Wi-Fi location determination features. An outdoor GPS-AP may utilize an interlock to prevent it from being moved and continuing to operate. Such an interlock could cause the AP to reinitialize its GPS position and contact the AFC when it believes it has been moved. If the device had used a technician provided location, a physical interlock may be utilized. For example, if the AP lost power and had power restored, it could attempt to determine if it had been moved by querying other location-specific or at least location-indicating attributes. For example, if it was integrated with a cable modem, the cable modem could inform the AP whether or not it had been moved to a new HFC (hybrid fiber-coaxial) feed (new power levels, new CMTS (cable modem termination system) communication information, different cable group, etc.). Other location indications could be: DHCP server changes, DHCP Gateway changes, new clients/loss of old clients, new overlapping Wi-Fi Basic Service Sets (OBSSs). In embodiments, a 6 GHz AP may be collocated with a 5 GHz AP and/or a 2.4 GHz AP. If those collocated APs report new neighboring APs, one or more new clients, or the presence of other new wireless devices, the 6 GHz AP may refuse to transmit until its location is updated by a trusted source. In embodiments, the AFC system115may utilize location information from multiple sources to verify or otherwise improve the level of confidence in a determined location of a device (e.g., AP105). For example, the AFC system115may correlate location information of a device with GPS data with a physical address associated with a customer (e.g., an address recovered from billing data or subscriber information held at a subscriber information server125such as a service provider server or other server storing subscriber or account information). Location Determination Through RF Scans in 6 GHz Band A device needing to perform location determination, typically an AP105, initializes and comes up to scan available frequency bands. An AP may have access to 2.4 GHz, 5 GHz, and 6 GHz radios. The AP can scan 2.4, 5 and 6 GHz bands for Wi-Fi signals. The SSIDs obtainable from received Wi-Fi transmissions can contribute to an estimate of the AP's location. The signals of other 6 GHz APs may be detected from a 6 GHz scan or from analysis of information about 6 GHz SSIDs included in the 5 GHz or 2.4 GHz signals. For example, one or more signals received by an AP105through a 2.4 GHz or 5 GHz radio may indicate a presence or offering of a 6 GHz SSID by one or more other APs. A goal of 802.11 standards for the 6 GHz band is to restrict the amount of beaconing and similar activities to decrease the percentage of airtime given over to background or maintenance activities. An AP with 6 GHz capability may announce that capability in its 2.4 and/or 5 GHz transmissions. The AP105can also scan 6 GHz bands for the presence of non-Wi-Fi signals. The signals of fixed wireless or other non-Wi-Fi communications can be detected and, potentially, their directions recorded. Utilizing energy detection, an AP need not be able to demodulate or decode a fixed wireless or other non-Wi-Fi communications signal to detect its presence. In embodiments, further processing, beyond energy detection, is performed on the received signal spectrum. The characteristics of at least well-known signals such as fixed microwave signals can be applied to the received signal spectrum and energy signatures of potential interest marked for more processing. For instance, fixed microwave signals are typically 30 MHz wide and occur in pairs. These signals are also required to be registered with the FCC. In embodiments, a signal spectrum detected by an AP may be processed locally or sent to a controller130or cloud server for further processing. If the AP105is processing the spectrum locally, it may detect a certain combination of fixed microwave signals. With that information, the AP can consult a database containing 6 GHz registered signal sites. Fixed wireless assigned frequencies may be recorded in a database that also includes location information. When combined with the Wi-Fi signal information, the location of the AP may be ascertained with greater certainty or less uncertainty. An AP may develop a location estimate based on these sources of information, even if a GPS or similar location determination equipment is not available. If the AP sends a collected signal spectrum to a controller130or cloud server, those entities similarly may consult databases of known 6 GHz entities to develop a location estimate. Those entities may also consult databases of known 2.4 GHz and 5 GHz signal sources. That estimate may be returned to the AP for it to use in communication with an AFC system. Alternatively, the controller130or cloud server may forward the location estimate with information identifying the AP to an AFC. If the AP recognizes Wi-Fi signals within the 6 GHz scan, that information may also be used to aid with location determination. As mentioned earlier, additional sources of location information may include client devices such as smart phones that have associated with the AP's 2.4 or 5 GHz radios as well as GPS receivers or the like. Many smart phones have built-in GPS receivers and can provide an estimate of their current location by combining their GPS signals (if any) with other signals in the Wi-Fi bands and other indications as known in the art. The client devices may have an app installed that facilitates communication with the AP and indicates to the AP whether or not the client device will share its current location estimate. In embodiments, a user of a client device may be presented with an option to share its location with its associated AP or not. The AP may request a location estimate from the client device by communicating with the app. Alternatively, the controller may communicate with the client device's app on the AP's behalf to acquire the client's location estimate. The AP may use an algorithm itself to predict its most likely location based on the various inputs it received, or it may contact another device or server, provide the information and receive an estimated location with an estimated location error. An AP or a location server may use standard techniques of localization and triangulation to predict the AP's location from the gathered data. The AFC database (at the AFC system115) may utilize a buffer to compensate for potential inaccuracies with respect to the location information carried by a query. The AFC database may identify one or more frequencies available to the respective device (e.g., AP105), wherein the available frequencies are based upon the determination of whether the respective device is located within an exclusion zone. Further, the database may identify one or more operating requirements, such as transmit power level, based upon the determination of whether the respective device is located within an exclusion zone. The database may send a list of the available frequencies to the respective device, and the respective device may begin operating according to any operating requirements at an available frequency identified from the list. In embodiments, a device registered with the AFC database may send heartbeat messages to the database in order to ensure that exclusion zone data is current and to confirm that the device is active. A device may deregister from the AFC database when a determination is made that the device has been moved by more than a threshold distance (e.g., 50 m, 100 m, etc.), when a heartbeat message is not received for longer than a certain duration (e.g., 24 hours, etc.), or in response to another triggering event. If an AP is providing high reliability services, the AP may register with more than one AFC and retain records for the at least two different AFC responses providing channel availability and power levels. The AP may choose to use one AFC's response over another AFC's response if the responses differ, or it may choose to comply with the union of the two responses. FIG.2is a flowchart showing an example process for utilizing registration information from two AFC systems. At205, a connection failure between an AP and a first AFC system may be detected. For example, if the AP cannot contact one AFC for the daily heartbeat message and assignment confirmation, then the AP can continue to operate in compliance with an assignment given by a second AFC. At210, the AP may determine whether the operational parameters of the first AFC are the same as the operational parameters of a second AFC with which the AP has registered. If the operational parameters for the first AFC and the second AFC are not the same, the AP may initiate operation according to the operational parameters of the second AFC system at215. For example, if the AP chose to use an assignment from the first AFC that was not a part of the second AFC's assignment, then the AP will have to change channel and redirect its stations to the new assignment. If the operational parameters of the first AFC and the second AFC are the same, the AP may continue operating according to the operational parameters of the first AFC at220. For example, if the AP chose an assignment in compliance with both AFCs' allotments, then the AP need not make any changes in operation. The AP may choose to align its heartbeat messages to maximize its holdover operation time should it lose communication with all of its AFCs. For example, with one AP communicating with 2 AFCs, the AP may choose to space the heartbeat messages 12 hours apart, so that if the AP loses all communications with both AFCs, the most recent heartbeat message will be at most 12 hours old. A monitoring site already in position for CBRS may be enhanced to also collect signatures of radio traffic in various bands outside the CBRS band. It had been true that radios were fairly dedicated to specific frequency ranges, but as software defined radios (SDR) with flexible front ends have improved in performance and cost-effectiveness, that limitation is less accurate. If an SDR is being used for reception only, some of the concerns that attach to SDR are mitigated. One common concern is that the filtering for out-of-band emissions for SDR transmitters is difficult or expensive. If the SDR is only operating as a receiver, that concern is minimized. 6 GHz devices may also include 2.4 GHz and/or 5 GHz radios. This allows an AP, for example, to provide only minimal beaconing in its 6 GHz allotted channel because its 5 GHz beacon can include information about any 6 GHz interfaces. For example, the AP may advertise a 6 GHz SSID through a beacon provided by a 2.4 or 5 GHz radio of the AP. If a 6 GHz device, such as an AP or mesh station, does not include an LTE radio, one or more of its clients or associated devices may, such as a cell phone. In that case, an AP, for example, might ask its clients for information about networks seen over the air, even if it does not request an actual location determination from those devices. The AFC database may alternatively receive information such as 5 and 6 GHz signals received by the device seeking to register. The information about 5 and 6 GHz signals received may include SSIDs from Wi-Fi APs, as well as frequencies where energy was detected above a threshold in the 5 and 6 GHz bands. The information about 5 and 6 GHz signals received may include signal strengths associated with the received signals as well as angular directions. The database may correlate received energy signatures with known 6 GHz fixed microwave deployments to determine a device's probable location. Known 6 GHz microwave deployments may be registered with their frequency usage and locations. Detection of a certain pattern of 6 GHz signals can be matched against known deployments to allow the AFC database to estimate where a device would have to be to receive that pattern of 6 GHz signals. For example, fixed microwave links in the 6 GHz band are known to be 30 MHz wide and to exist in pairs. The database would consider not only the detected 6 GHz signal in making a frequency assignment for a requesting device that reports receiving at least one 30 MHz signal in its 6 GHz scan. Detection of one 30 MHz wide signal necessarily implies that the matching paired signal may also potentially be affected if the device begins transmissions in the frequencies assigned to the paired signal. As can be seen inFIG.3, the AFC database or a location determination proxy for the APs may correlate received energy signatures with known fixed microwave deployments to determine a probable location of an access point.FIG.3shows a range of possible device locations, A, B and C. A device at location A could report seeing frequency 1 and frequency 4. A device at location B might report seeing only frequency 1 and a device at location C might report seeing frequencies 1 and 2. For location C, the database could have confidence that any assignments must avoid frequency 1 and frequency 2. For location A, the database, knowing that A could see both frequency 1 and frequency 4, could estimate the location of A as probably being close enough to receiver 2 and receiver 3 that any assignment to the device at location A must avoid frequencies 2 and 3 as well as 1 and 4. When considering location B, the database would need to consider other information, such as if other 6 GHz signals were seen, or if any SSIDs were seen to determine whether to avoid frequency 2. Similarly, the database may correlate the received SSIDs with known SSID locations to determine a device's probable location. The database may combine the various estimations to form an estimate with greater confidence. If the estimates formed based on different information sources do not indicate the same location within a certain amount of uncertainty, then the database may choose which estimates to rely upon to make a registration decision, or it may reject the registration request entirely. The relative signal strengths and directions may be combined with the location estimation to determine if the information provided is credible. The database may also use the relative signal strengths and directions to determine the transmit power level allowed for a device as well as an allowed frequency block. For example, a device that reports very low signal levels for 5 and 6 GHz received signals may be within a building so that those other signals reach it only faintly. In this case, the database could allow that device to use a higher transmit power safely because its transmissions will also be attenuated heavily before they reach any 6 GHz fixed microwave operations. Location Awareness FIG.4is a flowchart showing an example process400for determining operational requirements and available frequencies for a device based upon a determination of a baseline location associated with the device. A baseline location associated with a device (e.g., AP105ofFIG.1) may be determined at405. For example, the device, or a related upstream device, may determine the baseline location of the device when the device is installed or in response to a triggering event (e.g., movement of the device, reboot of the device, etc.). The baseline location may be output to a database (e.g., database of an AFC system115ofFIG.1) at410. At415, the AFC system may determine whether the baseline location of the device is within one or more exclusion zones. If the baseline location of the device is within one or more exclusion zones, the AFC system may output to the device, available frequencies and one or more other operational requirements associated with the one or more exclusion zones at420. If the baseline location of the device is not within an exclusion zone, the AFC system may output to the device, available frequencies and operational requirements at425. At430, the device may initiate operation at the available frequencies according to the one or more operational requirements. The device, or a related upstream device, may be configured to determine that the device has moved by comparing a current location of the device to a baseline location of the device (e.g., the location information automatically determined or manually entered during an install or initial setup of the device). Additional description for comparing a current location of a device to a baseline location of the device to determine that the device has been moved may be found within U.S. application Ser. No. 15/131,693, entitled “Detecting Device Movement through Electronic Fingerprint Analysis,” filed on Apr. 18, 2016. The disclosure provided by U.S. application Ser. No. 15/131,693 is incorporated herein. The device may respond to a determination that a current location of the device differs from the baseline location of the device by initiating an action for ensuring compliance with regulatory requirements. The device may be configured to initiate an action for ensuring compliance with regulatory requirements only when the difference between the current location of the device and the baseline location of the device exceeds a certain threshold. Actions for ensuring compliance with regulatory requirements may include, but are not limited to, the following: halting AFC-regulated operation; reducing transmit power; changing channel to a channel that does not require AFC-regulated operation; powering down the device; and others. FIG.5is a block diagram illustrating an example network500that enables geo-location for mains-powered non-GNSS (global navigation satellite system) based devices, with multiple applications including SAS and AFC. Geo-location is becoming a basic requirement for many new applications. The expense for adding GNSS location hardware to certain devices may be cost prohibitive, thus ruling out these applications. Some new communication systems may require geo-location services in order to query a regulatory database to check if they are entitled to operate in a specific location. The need to include GNSS hardware with equipment providing these new communication systems may be burdensome and cost prohibitive. In the case of CBRS and the unlicensed use of 6 GHz, device location is essential to allow these services to operate. Both of these systems require location lookup to confirm if operation is allowed, and what constraints such operation is subject to. The deployed lookup system for CBRS is called Spectrum Access System (SAS), while the system for 6 GHz is called Automated Frequency Coordination (AFC). In the case of 6 GHz operation, basic operation at low power levels for indoor operation (also referred to as low power indoor operation (LPI)) may avoid the need to use AFC lookups before operating, however there is an advantage to using AFC to potentially enable standard indoor power levels, bringing 6 GHz operation up to existing UNII-2-Extended power levels (without worrying about Dynamic Frequency Selection (DFS)). In some instances, professional equipment may be able to absorb the cost of GNSS hardware, however, for mass residential deployments the additional cost of such hardware is prohibitive. The system described herein enables the use of adjacent connected technology to provide GNSS data to be used by a device when consulting SAS/AFC or similar systems, to confirm operation, without requiring additional GNSS hardware in the device. The AP505may include an adaptive movable access point (AMAP) system. Two broad interactions are described in a power on/off timeline. The first interaction describes how the AP505and a mobile application on an external device510(GNSS enabled mobile device/tablet/etc.) may be setup to communicate with each other over an authenticated link (e.g., Wi-Fi), and the external device510may securely exchange the GNSS information to the target device (e.g., AP505), which would in turn use this within the IAM (identity and access management) authenticated service link in order to retrieve SAS or AFC related information from an AFC system515(e.g., the AP505may communicate with the AFC system through a connection to a WAN525). For example, the external device510may be configured to retrieve location information from a GNSS520, the location information being associated with the physical location of the external device510. The GNSS data (e.g., location information) may remain within the target device (e.g., AP505) until a power off event. For example, when the AP505is powered on, the AMAP may initiate and the AP505may initiate 6 GHz communications at low power (e.g., 200 mW). The AP505may connect to a mobile application (e.g., application running at the external device510), and the AP505may receive location information (e.g., GPS data/coordinates) from the external device510. The AP505may output an AFC request to an AFC system515, wherein the AFC request includes the location information. The AP505may receive an AFC response from the AFC system515, wherein the response either approves or denies the AP request to operate within the 6 GHz band at high/normal power. If the AFC response approves the AP's use of the 6 GHz band, the AP505may switch to operating within the 6 GHz band at high/normal power levels (e.g., 1 W). When the AP505powers down, the AP505may lose the AFC details received from the AFC response. In the subsequent interaction (e.g., when the AP505returns to a power on state), the target device (e.g., the AP505) powers on and waits to have the external device510connect using the mobile application. If the AP505cannot connect to the external device510, the AP505will not receive the GNSS location information. For example, the AMAP system may be initiated, and the AP505may initiate 6 GHz communications at low power (e.g., 200 mW). The absence of a new connection to deliver GNSS information means that 6 GHz 1 W operation cannot be enabled. In embodiments, the system relies on an external device510with an existing embedded GNSS system to communicate GNSS data to the target device (e.g., AP505) that needs GNSS data, using a secure authenticated connection between the two devices, primarily based on a Wi-Fi connection offered by the target device. The target device is typically AC powered and may generally need to be powered down if it is moved to a new location. The system relies on the fact that a pre-authenticated device can provide authentic GNSS data when connected, and this information may be provided via a Wi-Fi connected device, operating on a logical Wi-Fi link connected to the target device. Once the GNSS information has been synchronized to the target device, the target device maintains this information in dynamic memory, losing all GNSS information upon power loss or reboot. While powered on, the target device can reuse the GNSS information to support any SAS/AFC related queries it may be required to perform. The proximity of the external device is proven through the Wi-Fi connectivity requirement, ensuring that both the external and target device are within a predetermined proximity to each other (e.g., <50 m). Another aspect of the system is to enable the target device to communicate with the AFC in a secure authenticated manner. One potential option, that is very cost effective for device authentication and basic information sharing is the utilization of a cloud-based platform (e.g., Google IAM service). This is useful for any large scale usage such as residential Wi-Fi AP deployments (either service provider or retail). Embodiments of the AFC service may provide a solution that is highly scalable, and may be able to offer daily lookup service for many devices (e.g., on the order of 100,000 s or 1,000,000 s). In embodiments, access may be gained to a database of AP SSIDs linked with locations. Such a database may be offered as a service where a device can survey the APs that it can hear and ask the database where the device is most likely physically located based upon a report of what it can hear. An AFC may offer similar services using a wider network of networks. An AFC may use data from its own sensors to gather information about locations. An AFC's own sensors' locations may be well known, allowing information from sensors with well-known locations and well-known antenna patterns to be trustworthy. An AFC may accept information from devices already having trustworthy accepted locations about 6 GHz signals, Wi-Fi APs (SSIDs and RSSI) and/or LTE or 5G base stations or microcells. Also available in some areas and from certain devices or sensors could be 900 MHz signals for Wi-Fi HaLow, Lora, SigFox or other such signals. The AFC may use that information, when the device is trusted, to enhance its mapping ability. It may also doublecheck location information from new devices seeking authorization by requesting information from that untrusted device about other signals it has detected. If the other information matches to within a certain degree of error the location information provided by the new device, then the AFC would have additional confidence that its reported location is correct. On the other hand, if the location information from the device does not agree with the wireless environmental information provided by that device, then the AFC may not choose to trust that device or provide it with a high power channel authorization. Alternatively, a device might use an available service to determine its location in lieu of having the ability to determine its location through access to a GPS or through the use of cellular location services. When the device reports its location to an AFC, it may provide a margin of error for that determination based on a factor returned by the location service. Database Management A controller or database may be utilized to store exclusion zone data associated with areas in which unlicensed band usage may impact microwave paths. The controller or database may include or may be a part of the AFC system. Updates to exclusion zone data may be pushed to the controller or database or may be pulled by the controller or database from one or more sources of exclusion zone data. Exclusion zone data may include one or more geographic locators (e.g., GPS coordinates, etc.) making up boundaries of exclusion zones or that are otherwise positioned within boundaries of exclusion zones. Exclusion zones may be areas that have been designated as areas in which unlicensed band usage may impact microwave paths. In embodiments, periodically or in response to certain triggers, the controller or database may identify one or more devices that are operating at a location that falls within a region that is the subject of an update which has been made to the exclusion zone data. For example, when an update to exclusion zone data is received, the controller or database may check location information associated with one or more devices to determine whether the location information of any of the one or more devices indicates that the device is located within an area that is affected by the update. As another example, the controller or database may periodically (e.g., hourly, daily, weekly, etc.) determine whether the location information of any of the one or more devices indicates that the device is located in an area that is affected by an update made to the exclusion zone data during the certain duration covered by the period. In response to a determination that a device is located within an area that is affected by an update to the exclusion zone data, the controller or database may output updated frequency information (e.g., AFC operational requirements) to the device. FIG.6is a flowchart showing an example process600for updating AP operating parameters based upon an update to exclusion zone data. At605, an update to exclusion zone data may be received, for example, at an AFC system. At610, a determination is made whether one or more APs are within an exclusion zone impacted by the update. If an AP is within an exclusion zone impacted by the update, the AFC system may output to the AP, updated operating parameters at615. If an AP is not within an exclusion zone impacted by the update, the decision may be made not to send updated operating parameters to AP(s) at620. In embodiments, the controller or database may include channel scanning functionality or secure and authenticated access to external channel scanning functionality.FIG.7is a flowchart showing an example process700for clearing or terminating usage of channels by one or more APs based upon a scan of channels utilized by a microwave path. At705, the controller or database may scan channels utilized by microwave systems to determine whether the microwave path associated with a microwave system is active at710. If the determination is made that the path is not active, the controller or database may clear one or more devices located within an area associated with the path to use the channel(s) associated with the microwave path at715. If the determination is made that the path is active, the controller or database may terminate usage of associated channels by one or more devices located within the area associated with the path at720. In embodiments, the controller or database may maintain a schedule of band usage by one or more microwave systems. The controller or database may clear or terminate channel usage at one or more devices based upon the schedule. In embodiments, the controller or database may generate a schedule of band usage by one or more microwave systems. The controller or database may monitor channel usage by the one or more microwave systems and may record times/days during which the microwave systems are active. Based upon the monitored channel usage, the controller or database may generate a schedule of daily/weekly/yearly use. The controller or database may clear or terminate channel usage at one or more devices based upon the schedule. In embodiments, the controller or database may direct one or more devices (e.g., one or more devices within an MDU (multiple dwelling unit), campus, etc.) to use certain frequencies based upon frequencies used by other devices. The controller may also direct other devices to alter their power levels or to use directed null forming to avoid causing interference. For example, the controller or database may allocate 6 GHz channels among a group of APs that are within a certain proximity of each other, wherein the allocations are made on a non-interference basis. In embodiments, a device (e.g., an AP) may receive communications indicating that a microwave path with which the device has been associated based upon a current location of the device has become active or inactive. For example, a beacon positioned in close proximity to a microwave system may determine a current state of the microwave system. When the state of the microwave system changes (e.g., when the corresponding microwave path becomes active/inactive), the beacon may output notifications indicating the state change to one or more devices that are located within an exclusion zone associated with the microwave path. For example, the notifications may include clearances or termination requests that notify the one or more devices that one or more frequencies have become available or unavailable. Further, the notifications may notify the one or more devices that operational requirements either may be temporarily ignored or should be adhered to based upon the identified state change. In embodiments, an AP may scan a channel to determine whether a 6 GHz band is available. For example, an AP operating at low power may carry out a scanning of the 6 GHz band as a background operation. If signals are detected on the 6 GHz band, the AP may refrain from using the 6 GHz band or may alternatively remain at low power until the 6 GHz band is clear. Operational Deployment In embodiments, an AP may have both a 6 GHz radio and another radio (e.g., 2.4 or 5 GHz radio). If a 6 GHz AP has a legacy band (2.4 or 5 GHz) and a 6 GHz STA also has legacy capabilities, then the AP may advertise in the legacy band its 6 GHz capabilities. In embodiments, a device may be configured with a 2+5+6 solution. In embodiments, a device may be configured with a 2+5+5/6, wherein one of the radio chains is switchable between 5 GHz and 6 GHz. If the units are a bookend solution and/or controlled by a home networking controller, a home networking controller may direct a STA/extender to a specific 5 or 6 GHz channel depending upon the STA's 5 GHz RSSI. The controller may consider the performance of similar stations already attached at 6 GHz to determine whether or not the STA should be directed to the higher band. If the higher channel has a very wide channel with little or no interference, then the controller may choose to move the STA. FIG.8is a flowchart showing an example process800for directing a STA to specific channel based upon potential operating performance at a 6 GHz channel. For the controller to make good decisions, it needs access to the AP's AFC channel/power assignments. The APs might handle the request process independently and keep the controller up to date on any assignments or refusals. As the controller decides which band to assign a station to, the controller may consider the STA's current RSSI as well as RSSI history, as well as the channel assignments and power level limits of the APs it controls. At805, the controller may determine a 5 GHz RSSI of a STA. At810, the controller may determine a breadth and level of interference of a 6 GHz channel. At815, the controller may determine whether the 6 GHz channel may offer better performance for the STA than the currently used 5 GHz channel. If the determination is made that the 6 GHz channel does not offer better performance for the STA, the controller may direct the STA to the 5 GHz channel at820. If the determination is made that the 6 GHz channel does offer better performance for the STA, the controller may direct the STA to the 6 GHz channel at825. FIG.9is a flowchart showing an example process900for scanning for a satisfactory 6 GHz channel. If the units are un-related, a STA may turn on and activate its 5 GHz radio and perform normal scanning at905. If a 6 GHz advertisement is not found at910, the STA may stay at the 5 GHz band at915. If an AP is found that also advertises a 6 GHz capability at910, the STA can consider which 6 GHz channel/band is included in the AP's information. For example, the STA may determine operational requirements associated with the 6 GHz band at920. Since the US current regulatory proposals indicate that the power level may be set by channel, the STA may take that into consideration. If the determination is made at925that the operational requirements of the 6 GHz band are satisfactory to the STA, the STA may activate a 6 GHz radio at930. If, at925, the STA determines that the operational requirements of the 6 GHz band are not satisfactory, the STA may continue scanning at935. For example, if the channel is a low power channel, the STA may preferentially keep looking until it finds an AFC/high power channel. In embodiments, multiple APs may coordinate to maximize efficiency of band usage between the multiple APs. For example, the APs may coordinate use of the large bands based upon the varying regulatory requirements associated with each of the bands. With the potentially lower power limits (at least for a while), spreading STAs across multiple APs may be helpful to use the wide bandwidth to bring up the data rate. A deployment constrained to a low power level, such as 250 mW, may require more APs to cover the same area compared to a standard 5 GHz AP (1 W). A collection of APs that are centrally coordinated can send in separate AFC requests and a central coordinator might choose how to distribute the STAs based on the responses. In embodiments, a controller may direct an AP to resend its request if the results are not acceptable. STAs may be directed to go from standard power to low power or to evacuate the band if an AFC withdraws the previously allowed channel(s) from an active AP. In embodiments, an AFC may withdraw a channel allocation at any time. If an AP receives a withdrawal notice from the AFC, the AP may notify all STAs that they must at least drop to low power. If the operational parameters do not allow the STAs to change their power level and remain on the channel, then the AP may direct the STAs to shift to a non-6 GHz band until the AP can obtain a new assignment from the AFC. Timing Distribution/Low Latency Services/QoS PTP (IEEE-1588) allows distribution of timing over Ethernet. DTP (DOCSIS Timing Protocol) from CableLabs extended this technology over DOCSIS. Motivation for 6 GHz Wi-Fi application: new unlicensed frequency band likely to have little interference for a while, especially if all four bands are opened. If only band 6 is open, that advantage will be short-lived. This disclosure applies to a cable modem GW that also has Wi-Fi including 6 GHz (but not required). The CM supports DTP as does its supporting CMTS. The CMTS/CM could provide several different timing sources. As different mobile providers advance their networks from 4G to 5G at different rates, there may be different timing feeds available for different small cell/pico cell uses. The timing feeds may also be of different qualities (4G vs 5G 1 ms). The AP can advertise its support for timing distribution or provide it later in a capabilities exchange. This notification could come via a field in the beacon or in a capabilities exchange after the STAs are associated. The notification could include multiple possible timing sources that the CM/AP may have available. The notification could also indicate the accuracy or quality of each potential timing source. A STA decides whether an AP can provide a timing feed that it needs. The STA can request the timing feed. If a STA wants to receive a timing distribution, it notifies the AP that that it wants to receive a timing distribution. That notification could indicate which timing source the STA is interested in and/or potentially a level of accuracy or quality that it needs to receive. The AP may evaluate whether it can provide the service that the STA has requested. The AP may need to communicate with the CM and/or the CMTS to ensure that the requested service and QoS level can be provided. The AP/CM passes that request back to the CMTS. If the CM/AP has to support multiple timing feeds then the CM may select which one to use for its internal systems, or it may not use any specific feed directly. If the AP can provide the STA with the service it requested, then it selects an OFDM/OFDMA downstream and upstream channel to carry the timing messages. For example, the timing messages may be carried over a selected 6 GHz channel. Note that the channel may actually be one or more resource units (RU) as known in11axwith limited bandwidth, but that can be dedicated to this purpose. The AP and STA begin communicating over that RU according to a schedule developed by the AP to accommodate the QoS requirements of the service level that the STA had requested. The AP may choose a limited set of MCS settings for the channel to ensure predictability and good performance. FIG.10is a flowchart showing an example process1000for establishing a timing distribution between an AP and STA. At1005, the AP may output an advertisement for support of timing distribution. At1010, the AP may receive a request from a STA to receive a timing feed, wherein the request is output from the STA in response to the STA recognizing the advertisement. At1015, a channel may be selected for carrying the timing messages. For example, the timing messages may be carried over a selected 6 GHz channel. At1020, a schedule for communicating the timing messages may be developed based upon a service level indicated by the request that is received from the STA. At1025, communications may be initiated between the AP and the STA over the selected channel according to the developed schedule. FIG.11is a flowchart showing an example process1100for establishing a timing distribution between an AP and STA, wherein the STA determines whether the AP offers the timing distribution from a certain source at a certain service level. At1105, a STA may receive, from an AP, an advertisement message carrying information associated with timing distribution that is offered by the AP. At110, the STA may identify sources and/or service levels offered by the AP. At115, the STA may determine whether a required timing service is offered by the AP. If the required timing service is not offered by the AP, the STA may evaluate other methods for receiving a timing distribution at1120. If the required timing service is offered by the AP, the STA may output a request to receive a timing feed from a specified source at a specified service level at1125. At1130, communications may be initiated between the AP and STA to receive the requested timing feed. FIG.12is a block diagram of a hardware configuration1200operable to facilitate location determination, communications with an AFC system, configuring operational parameters in response to an identification of active 6 GHz paths, and timing distribution and low-latency services. The hardware configuration1200can include a processor1210, a memory1220, a storage device1230, and an input/output device1240. Each of the components1210,1220,1230, and1240can, for example, be interconnected using a system bus1250. The processor1210can be capable of processing instructions for execution within the hardware configuration1200. In one implementation, the processor1210can be a single-threaded processor. In another implementation, the processor1210can be a multi-threaded processor. The processor1210can be capable of processing instructions stored in the memory1220or on the storage device1230. The memory1220can store information within the hardware configuration1200. In one implementation, the memory1220can be a computer-readable medium. In one implementation, the memory1220can be a volatile memory unit. In another implementation, the memory1220can be a non-volatile memory unit. In some implementations, the storage device1230can be capable of providing mass storage for the hardware configuration1200. In one implementation, the storage device1230can be a computer-readable medium. In various different implementations, the storage device1230can, for example, include a hard disk device, an optical disk device, flash memory or some other large capacity storage device. In other implementations, the storage device1230can be a device external to the hardware configuration1200. The input/output device1240provides input/output operations for the hardware configuration1200. In one implementation, the input/output device1240can include one or more of a network interface device (e.g., an Ethernet card), a serial communication device (e.g., an RS-232 port), one or more universal serial bus (USB) interfaces (e.g., a USB 2.0 port), one or more wireless interface devices (e.g., an 802.11 card), and/or one or more interfaces for outputting video and/or data services to a client device105ofFIG.1(e.g., television, STB, computer, mobile device, tablet, etc.) or display device associated with a client device105. In another implementation, the input/output device can include driver devices configured to send communications to, and receive communications from one or more networks (e.g., WAN115ofFIG.1, provider network120ofFIG.1, local network130ofFIG.1, etc.). The subject matter of this disclosure, and components thereof, can be realized by instructions that upon execution cause one or more processing devices to carry out the processes and functions described above. Such instructions can, for example, comprise interpreted instructions, such as script instructions, e.g., JavaScript or ECMAScript instructions, or executable code, or other instructions stored in a computer readable medium. Implementations of the subject matter and the functional operations described in this specification can be provided in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible program carrier for execution by, or to control the operation of, data processing apparatus. A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network. The processes and logic flows described in this specification are performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output thereby tying the process to a particular machine (e.g., a machine programmed to perform the processes described herein). The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable disks); magneto optical disks; and CD ROM and DVD ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry. While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination. Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Particular embodiments of the subject matter described in this specification have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results, unless expressly noted otherwise. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous. | 55,163 |
11943684 | Persons of ordinary skill in the art will appreciate that elements in the figures are illustrated for simplicity and clarity so not all connections and options have been shown to avoid obscuring the inventive aspects. For example, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are not often depicted in order to facilitate a less obstructed view of these various embodiments of the present disclosure. It will be further appreciated that certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. It will also be understood that the terms and expressions used herein are to be defined with respect to their corresponding respective areas of inquiry and study except where specific meaning have otherwise been set forth herein. DETAILED DESCRIPTION The present invention now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific exemplary embodiments by which the invention may be practiced. These illustrations and exemplary embodiments are presented with the understanding that the present disclosure is an exemplification of the principles of one or more inventions and is not intended to limit any one of the inventions to the embodiments illustrated. The invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Among other things, the present invention may be embodied as methods or devices. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense. Network operators or providers, such as entities providing cellular phone and data service, may use various hardware, software, or other tools and systems to review and manage network data and customer service. In some embodiments, network operators may provide systems and methods to access user data or data pertaining to a user's particular user equipment (UE) so that agents or applications of the network operator may access data or information, for example, while troubleshooting, assessing service quality, etc. In some embodiments, access to user or UE data may only be achieved by subscribing for updates to a particular user's or UE's data, waiting for updates to that data to be received from a database, system, or other source, then unsubscribing from the same updates to stop receiving that information. In some embodiments, traditionally, an entity seeking such user data may not simply obtain the current data for that user without going through the subscription process described above. For example, in 5G systems, a client system (e.g., network operator, troubleshooting, customer service entity, etc.) may need to retrieve user data from a control node for the 5G network, such as an access and mobility management function (AMF) or a short message service function (SMSF). In some embodiments, the SMSF may be accessed via a SMSF Representational State Transfer (REST) interface. In some embodiments, the SMSF specification related to the SMSF REST interface may be 3GPP TS 29 518 Release 16, but other specifications may be developed and implemented periodically that may work in a similar or equivalent manner. Traditionally, under the SMSF or AMF specification, a client system may subscribe to updates to user data on the SMSF or the AMF, but may not be able to obtain the current data directly without subscribing, receiving updates, and unsubscribing to that user's or user UE's updates. Similar restrictions may apply to accessing data of users in the LTE network domain, using a mobility management entity (MME) as a control node. The result may be slow, inefficient, and computer resources intensive access to user data, which may slow response to network problems, increase computing resources required to access the information, and generally reduce network efficiency, quality of service, and customer service efficiency. The disclosure describes a system and methods for improved access to user data that may provide increased efficiency, fewer computer resources, and faster user service troubleshooting, among other benefits and technical improvements. In some embodiments, a client system may obtain current data for a particular user or customer UE using manual steps via the SMSF REST interface for a SMSF. In some embodiments, the client system may be programmed to perform similar steps automatically based on inputs from a requesting entity. In some embodiments, the disclosure describes an application programming interface (API) that may receive input from a requesting entity, may interface with the SMSF REST interface for a SMSF, and may return user data for a particular user. In some embodiments, the system may allow any application or entity registered with a network repository function (NRF) (e.g., as an network function (NF)) to provide subscription, location, detailed registration information, etc., over the SMSF REST interface. In some embodiments, the system may provide access to this information without registering or subscribing for notification updates. In some embodiments, the system may provide access to user data in one of a variety of ways via the SMSF REST interface or other suitable interface. For example, in some embodiments, an application or entity may send an HTTP POST request to the client system or SMSF to initiate retrieval of user data. In some embodiments, the POST request may have a zero duration notification. In some embodiments, an application or entity may send a HTTP GET request to the client system or SMSF via the SMSF REST interface or other suitable means. In some embodiments, an application or other entity may request user data by sending a GET, POST, or other type of request to an API programed to retrieve the requested user data from the SMSF. In some embodiments, an application or other entity may use an API to request a particular user's registration data, and a user data API may include HTTP POST and/or HTTP GET requests. In such embodiments, the API may interface with the REST API and the SMSF, and may include a user interface or graphical user interface (GUI) that may receive identifying user information (e.g., international mobile subscriber information (IMSI), mobile station integrated services digital network (MSISDN), etc.) for the desired user. The system and method described herein may allow identification of subscriber registration in a 5G, LTE, or other network substantially close to the edge of the core network as possible. In some embodiments, the system and methods may also allow for the identification of the serving cell, current cell identification (CID), last CID, etc., that may be used in fault identification and triangulation, among other things. In some embodiments, the data sought and retrieved associated with a particular user or customer UE may be a UE context resource. In some embodiments, the UE context resource may include information to maintain network services for the customer's UE, such as UE state information, security information, UE capability information, identities of UE-associated connections, etc, and other information that may be useful for troubleshooting and other inquiries. FIG.1shows an embodiment of an example of a networking and computing architecture100in which the system and methods for improved access to UE context information may exist. The architecture100may include an AMF102that may connected to a session management function (SMF)104, a base station (e.g., g node B (gNB))106, user equipment (UE)108, authentication server function (AUSF)110, unified data management (UDM)112, policy control function (PCF)114, and short message service function (SMSF)132. The AMF102may be connected to and/or communicate with each part of the architecture via various interfaces and protocols, such as N1, N2, N12, N15, N8, N20, Nsmsf, etc. The SMF104may be connected to or interface with the AMF102, the UDM112, the PCF114, and the user plane function (UPF)116. The SMF104may connect or interface with the other nodes via one or more interfaces or protocols, such as N11, N10, N7, N4, etc. The gNB106may connect or interface with the AMF102, the UE108, and the UPF116via one or more protocols or interfaces such as N6, N2, N3, etc. The AUSF118may connect to or interface with the AMF102and the UDM112via protocols or interfaces such as N12, N13, etc. The PCF114may be connected to or interface with AMF102, the SMF104, and an application function (AF)120via protocols or interfaces such as N7, N8, N5, etc. The UPF116may be connected to or interface with the SMF104, the gNB106, and a data network (DN)122via protocols or interfaces such as N3, N4, N6, etc. The AMF102and other system elements may also communicate with or otherwise interface various other nodes via a message bus such as a serial bus interface (SBI) message bus124. For example, the AMF102and other elements may communicate with a network repository function (NRF)126, a network exposure function (NEF)128, a network slice selection function (NSSF)130, the AF120, the SMSF132, and the short message service center (SMSC)134via the SBI message bus124. In some embodiments, such as in some 5G networks, the SMF104may be a fundamental element of the service-based architecture (SBA). In some embodiments, the SMF104may be responsible for interacting with the decoupled data plane, creating, updating and removing Protocol Data Unit (PDU) sessions, and managing session context with the UPF116. Both the UE108and the gNB106may use next generation application protocol (NGAP) to carry non-access stratum (NAS) messages across N1 or N2 reference interfaces in order to request a new session. The AMF102may receive these requests and may handle connection or mobility management while forwarding session management requirements over the interface (e.g., N11) to the SMF104. The AMF102may determine which SMF104may be best suited to handle the connection request by querying the NRF126. The interface between the NRF126and the AMF102and the interface (e.g., N11) between the AMF and the specific SMF104assigned by the NRF may use the SBI message bus124, to which most or all of the system elements may be connected. In some embodiments, the SBI message bus124may employ RESTful API principles over HTTP/2. In some embodiments, the NRF126may maintain a repository of the 5G elements available in the operator's network along with services provided by each of the elements in the 5G core that are expected to be instantiated, scaled, and terminated with minimal manual intervention, if any. The NRF126may also support discovery mechanisms that may allow network elements to discover each other and get updated status of the desired elements. The NRF126may maintain the profiles of the available network function (NF) instances and supported services in the core network. The NRF126may also allow consumer NF instances to discover other providers NF instances in the core network (e.g., 5G core network). The NRF126may also allow NF instances to track the status of other NF instances. In some embodiments, the NRF126may interact with substantially every other element in the 5G core network and may support the above functions through management services and discovery services. In some embodiments, the SMSF132may support the transfer of short message service (SMS) messages over the NAS. In such embodiments, the SMSF132may conduct subscription checking and perform relay functions between the UE and the SMSC134, which may occur through interaction with the AMF102. In some embodiments, the SMSF132may interface with the AMF102via the Nsmsf service based interface. In some embodiments, the SMSC134may perform various tasks related to providing SMS delivery. For example, the SMSC134may receive SMS messages from wireless network users, store SMS messages, forward SMS messages to recipients, deliver SMS messages to wireless network users, maintain unique time stamps in SMS messages, store an SMS message until a recipient user is available to receive the message, etc. In some embodiments, the SMSF132and the SMSC134may be combined. In some embodiments, the SMSF132and the SMSC134may communicate via mobile application part (MAP) or Diameter protocols or other suitable protocols in other embodiments. In some embodiments, the SMSF132may communicate or interface with the UDM112using N21/Nudm protocols. In some embodiments, the SMSF132may support various services, such as allowing the AMF102to authorize, activate, deactivate, and update the SMS for network users. The SMSF132may also provide UplinkSMS services to the AMF102. Activating service may activate SMS service for a network user, which may result in creating or updating a UE context for SMS in the SMSF132. Deactivating service may deactivate service for a network user, which may result in deleting a UE context for SMS in the SMSF132. UplinkSMS service may send an SMS payload in the uplink direction to the SMSF132from the AMF102. FIG.2shows an embodiment of a computer environment200in which embodiments of the disclosed system for improved access to UE context information may operate. In some embodiments, the computing environment200may include at least one client system204that may be connected to or capable of connecting to one or more requesting entity computing devices202and/or one or more requesting entity servers206. In some embodiments, the client system204may be a server-type computing device specially configured to operate the system for improved access to UE context information and/or a UE context API configured to receive requests and return user data as disclosed herein. The requesting entity computing device202may be any type of suitable computing device capable of interfacing with the client system204via a data network such as the Internet, a local area network, a direct or wireless connection, using any suitable interface known to those skilled in the art, such as HTTP, simple object access protocol (SOAP), REST, etc. The requesting entity servers206may be any of a variety of servers hosting applications or other entities that may request UE context information from the client system204. In some embodiments, the UE context API may run on the requesting entity computer device202and/or the requesting entity server206and provide for sending requests to the client system204or AMF102. The client system204may interface with one or more AMFs, such as AMF102described in reference toFIG.1. In some embodiments, the client system204may interface with the AMF102via a REST interface and, more specifically, an AMF REST interface. The AMF102may be a traffic node in the system that may record any changes to UE context information. The AMF102may connect or otherwise interface with the UDM112, the SMSF132, and the SMSC134. Any time a user or network provider makes changes to the UE context associated with a user or UE, the changes may be updated on the SMSF132. In some embodiments, the UE context information may include substantially all information for a particular user registered on a particular node, particularly information associated with a user SMS subscription details and allowances. The SMSF132may, among other things, perform SMS management subscription data checking and conduct SMS delivery accordingly. Further details on example embodiments of these connections and associated interfaces are described in reference toFIG.1above. FIG.3shows an embodiment of data flow diagram300for example data traffic between the AMF102, the UE108, the SMSF132, and the UDM112. Those skilled in the art will understand that the data flow shown inFIG.2is merely an example and that other data flows consistent with the scope of the disclosure may be used as well. At302, an entity, such as a requesting entity, another entity associated with a network provider, or a network user using a UE, may transmit a registration request to the AMF102. In some embodiments, the registration request may include information identifying the user equipment of a user or the account or account information of a particular user for which SMS services are to be activated. In some embodiments, the identifying information may be a “International Mobile Subscriber Identity” (IMSI), which may be a unique number associated with the particular customer's UE or subscriber account. In some embodiments, the registration request may be submitted through an intermediary system, such as the client system204, via an API, user interface, or other interfacing protocol. At304, in some embodiments, the AMF102may request or otherwise access the network subscription information for the user or a particular UE associated with the user from the UDM112. In some embodiments, the UDM112may manage network user data or user data, provide authentication credentials, and be employed by the AMF102and SMF104to retrieve network customer/user or subscriber data and context. At305, the UDM may retrieve the subscription information for the user and, at306, transmit the subscription information back to the AMF102that requested it. Specifically, the subscription information may include SMS subscription information. At307, the AMF102may determine, based on the retrieved subscription information, whether the particular user and/or customer UE is authorized for SMS services. If so, the AMF102may discover and/or select an SMSF, such as SMSF132that may be used to provide SMS services to the customer UE. At308, in some embodiments, the AMF102may activate SMS service for the particular user or customer UE. In some embodiments, the activation may occur by the AMF102sending an HTTP PUT request to the SMSF132or, more specifically, to a resource in the SMSF representing the UE context for SMS. In some embodiments, the payload of the PUT request may include a representation of the individual UE context resource to be created or updated (e.g., UeSmsContextData). In some embodiments, if the designated UE context for SMS does not yet exist in the SMSF132, the SMSF may, at310, request subscription data for the particular customer UE from the UDM112. The UDM112may, at312, transmit the requested subscription data to the SMSF132, and the SMSF may perform service authorization for the customer UE and create the UE context resource for the particular customer UE. In some embodiments, at314, the SMSF132may transmit a success response (e.g., HTTP POST 201 Created) to the AMF102that may include a representation of the created UE context resource. Alternatively, if the designated context for SMS already exists, the SMSF132, at309, may update the UE context for SMS with parameters provided in the activation request and, at311, transmit a success response (e.g., HTTP POST 204 No Content) to the AMF102. If for some reason the activation or update may fail, in some embodiments, the SMSF132may return a failure response (e.g., HTTP POST 403 Forbidden) to the AMF102. Although not shown inFIG.3, in some embodiments, the AMF102may deactivate SMS service for the particular user or customer UE. In some embodiments, the deactivation may occur by the AMF102sending an HTTP DELETE request to the SMSF132or, more specifically, to the resource representing the UE context for SMS in the SMSF. In response, the SMSF132may deactivate SMS service for the user or customer UE and delete the UE context for SMS from the SMSF. If successful, the SMSF132may transmit a success response (e.g., HTTP 204 No Content) to the AMF102or, if unsuccessful, a failure message (e.g., HTTP 403 Forbidden). In some embodiments, an NF service consumer (e.g., AMF102) may use an HTTP POST in an UplinkSMS service operation to send an SMS on behalf of a customer UE. For example, the AMF102may transmit an HTTPS POST request to the SMSF132or, specifically, to the resource representing the UE context of the SMSF. The payload of the POST request may include the SMS message or record to be sent by the customer UE. In some embodiments, the SMSF132may then forward the SMS payload to another resource, such as an SMS router for transmission to a designated recipient. If successful, the SMSF132may return a success message (e.g., HTTP 200 OK) to the AMF102. In some embodiments, activation or deactivation may occur in response to a command from an entity, such as a requesting entity or other network entity. In some embodiments, the activation or deactivation may occur in response to a command received from a network entity through an interface or API (e.g., REST API) that may be associated with a client system, such as client system204. In some embodiments, a requesting entity using a requesting entity computing device, such as requesting entity computing device202, may query the request details for any UE context resource that has been created for a UE on the SMSF132. In some embodiments, such as at316inFIG.3, the requesting entity may transmit a request for a UE context resource from a computing device of the requesting entity202to the AMF102. In some embodiments, the request for the UE context resource may be sent directly to the SMSF132via an API or AMF API, or to the AMF via an interface with the client system204, such as via REST interface208between the client system204and the AMF. In some embodiments, the request for the UE context resource may include a user identifier of the user or user equipment, such as an IMSI or another account identifier. The UE context resource may include information relating to the customer's UE or the account associated with the UE. For example, the UE context may include. In some embodiments, the information in the UE context may include information to maintain network services for the customer's UE, such as UE state information, security information, UE capability information, identities of UE-associated connections, etc, and other information that may be useful for troubleshooting and other inquiries. In some embodiments, the AMF102or other traffic node may check whether the requesting entity is registered with the NRF126, such as before providing details relating to any UE context resource from the SMSF132. At318, the AMF102may query the SMSF132for a UE context resource associated with the user identifier provided by the requesting entity. In some embodiments, the UE context resource may be identified directly based on the user identifier, or in some embodiments, the AMF102may determine other identification information for the UE context resource based on the user identifier, such as by cross-checking a user identifier database. At319, the SMSF132may identify the particular UE context resource requested and, at320, the AMF102may receive the UE context resource from the SMSF in response to the query. In some embodiments, the AMF102may parse the UE context resource to identify particular information relevant to the requesting entity's query. In some embodiments, the AMF102may convert the received UE context resource to an API response. In some embodiments, the API response may be a REST API response. At322, the AMF102may transmit the UE context resource to the requesting entity computing device202. In some embodiments, the UE context resource transmitted to the requesting entity computing device202may be the parsed data from the UE context resource, and/or may be the converted UE context resource previously converted by the AMF102into an API response. In some embodiments, the requesting entity computing device202may receive the UE context resource via the REST interface or via a user data API, for example. In some embodiments, the user data API may provide access to information accessible via or stored directly on the AMF102via a client system. As mentioned above, in some embodiments, the request for a UE context resource from the requesting entity computing device202may be made via a REST API interface with the AMF102. In some embodiments, the request may include an HTTP POST message, or an HTTP POST message including a zero duration notification. In some embodiments, the request may include an HTTP GET request. In some embodiments, the request from the requesting entity computing device202for the UE context resource may be made directly to the SMSF132, or directly to the SMSF via the client system204, such as through the REST interface. In such embodiments, the SMSF132may check that the requesting entity may be registered with the NRF112as an NF and qualified to enable a request to the SMSF132to receive UE context resource details. In some embodiments, an application or other entity, such as via requesting entity server206, may use an API to request details for a particular UE or user, and a user data API may include HTTP POST and/or HTTP GET requests. In such embodiments, the API may interface with the REST API and the SMSF132and/or the AMF102, and may include a user interface or graphical user interface (GUI) that may receive identifying user information (e.g., international mobile subscriber information (IMSI), mobile station integrated services digital network (MSISDN), etc.) for the desired user and/or UE. In some embodiments, a client system may obtain current data for a particular UE context resource via the REST interface for an AMF or SMSF. The flow chart400inFIG.4illustrates an embodiment of a method to retrieve user data in accordance with the system and methods for accessing user data. In some embodiments, the user data may be retrieved via the user data API. At402, the method may include receiving, at a client system such as client system204, a request for user data from a requesting entity. In some embodiments, the request may come from a requesting entity computing device202or requesting entity server206, such as those shown and described with reference toFIG.2. In some embodiments, the request for user data may be in a REST API request format. In some embodiments, the request for user data may be a HTTP POST request, or an HTTP POST request with a zero duration notification. In some embodiments, the request for user data may be an HTTP GET request. At404, in response to receiving the request, the client system may execute a first login to the SMSF via an SMSF REST interface. In some embodiments, an AMF may instead perform authentication. In such embodiments, the client system may execute a first login to the AMF via an AMF REST interface. At406, the SMSF, such as SMSF132inFIG.2, may authenticate the first login from the client system. In some embodiments, the authentication process may include checking that the requesting entity is registered with an NRF, such as NRF126inFIG.2. In some embodiments, the authentication process may include determining whether the requesting entity may be registered with an NRF as a network function (NF). If the first login cannot be authenticated, the request may be denied. If the first login may be authenticated, the client system may logout of the SMSF REST interface at408and may execute a second login to the SMSF REST interface at410. Once logged in for the second time, the client system may submit query on a user identifier of a particular user or customer UE with the SMSF. Once again, in some embodiments, the login process may occur via the AMF instead. In some embodiments, the query may be made using man-machine language (MML). In some embodiments, the user identifier may be an IMSI, MSISDN, or other identification unique to the particular user, user account, or particular customer UE. Once the SMSF runs the query, the client system may, at414, receive a query response and parse the response to the query. At416, the client system may store the query response and/or parsed query response on the client system. At418, the client system may log out of the SMSF REST interface again, and at420, the client system may convert the stored query response to a REST API response. At422, the client system may send the REST API response to the requesting entity. In some embodiments, the REST API response may be in a format so as to provide the requested user data to the requesting entity. One example of the MML request that may be entered to query a particular user's data is shown in Example 1 below:Example 1: Show Subs Supi Imsi-310260173416064 Full where “imsi” may refer to International Mobile Subscriber Identity. The IMSI may be a unique number associated with the particular user's mobile phone or subscriber account. SUPI may refer to Subscription Permanent Identifier, which, in 5G network nomenclature, may be an abstraction of IMSI. Those skilled in the art will understand that, in some embodiments, other types of user identifiers may be used instead of or in addition to the IMSI. Additionally, those skilled in the art will understand that the MML request above is merely an example of one possible request, and that other requests in other programing languages may have a similar effect and still within the scope of the disclosure. Of course, those skilled in the art will recognize that this is merely an example of possible converted API format, and that many other query response formats may be used within the scope of the disclosure. In some embodiments, once the user data retrieved from the query has been converted to API format, the data may be requested and received at substantially any time to identify if there may be current registration. In some embodiments, the process described above may be automated so that the client system may receive an input of a particular user identifier and/or login credentials, query the SMSF or AMF via the SMSF or AMF REST interface based on the user identifier, and return user data for the particular user. In some embodiments, the process of requesting and receiving user data may be performed via the user data API. In some embodiments, the user data API may provide for a one-shot call of user data without subscribing to updates. In other words, a requesting entity may use the user data API to retrieve user data for a particular user or customer UE.FIG.5is a flow chart500illustrating an embodiment of a method of using the user data API to access user data. In some embodiments, at502, the client system or another computing entity hosting the user data API may receive login credentials for a requesting entity, such as from a requesting entity computing device202or requesting entity server206. At504, if the login credentials cannot be authenticated, the process may stop or the user data API may request the credentials again. If the login credentials may be authenticated, the user data API may request a user identifier for a user for which the requesting entity seeks user data. At506, the user data API may receive a user identifier for a particular user, such as an IMSI, MSISDN, or other identifying information. At508, the method may include executing the user data API to return the particular user or customer UE's data. In some embodiments, the user data API may query an SMSF to retrieve the requested data. In some embodiments, the user data API may be a REST API. In some embodiments, the user data API may use the SMSF REST interface to query information stored on the SMSF relating to users and customer UE. The user data API may include a HTTP GET request and/or an HTTP POST request, or other mechanisms to query and return user data or UE context resource data related to a UE. In some embodiments, the user data API may perform some or all of the steps shown and described in relation toFIG.4In some embodiments, the user data API may include code and response information similar to the commands and responses shown above with regard to Example 1, but other types of commands and responses may be used consistent with the teachings of the disclosure. Those of skill in the art will understand that the user data API may also operate in other ways consistent with the disclosure. At510, the user data API (e.g., via the client system) may transmit the retrieved user data to the requesting entity. The user data may include any of a variety of information. For example, the user data may UE context resource details, which may include information to maintain network services for the customer's UE, such as UE state information, security information, UE capability information, identities of UE-associated connections, and other information that may be useful for troubleshooting and other inquiries such as a general profile of the particular user's connection to the network, such as where the particular user may be identified in a cellular or data network, how the user may be registered, the internet protocol (IP) address of devices associated with a user, which systems in a network the user's device may be connected to (e.g., which AMF connected to which gNB, which SMSF, etc.), speed of the user device's connection to the network, etc. In some embodiments, the user data may also include a data network name (DNN), such as an access point name (APN). The user data API and systems and methods described herein may provide technical solutions to the technical problem of quickly and efficiently accessing user data, and particularly efficiently accessing UE context resource details for a particular UE. For example, if a customer service agent needs to perform troubleshooting activities, the agent traditionally may encounter problems identifying user data quickly and efficiently, such as while the user is waiting on the phone, because accessing the desired information may include taking several burdensome steps. Such agents and other entities may benefit from the systems and methods described herein by providing a technical solution to quickly and easily accessing user data for a particular user or customer UE. In some instances, the particular user may be waiting on the phone with a problem, or be otherwise expecting a problem to be addressed quickly. In such instances, a customer service agent may use the user data API described herein to quickly access the user data, identify the source of a user's problems, and potentially solve those problems or determine additional actions that may help solve those problems. Accordingly, the system and methods described herein have a practical application of providing for improved customer support solutions through technical solutions related to improved computer resource and time efficiency. Further the system and methods described herein may represent an improvement in customer service technology, networking technology, network access technology, and/or data access technology. FIG.6is a simplified illustration of the physical elements that make up an embodiment of a computing device, such as the requesting entity computing device202, andFIG.7is a simplified illustration of the physical elements that make up an embodiment of a server type computing device, such as the client system server204. Referring toFIG.6, a sample computing device is illustrated that is physically configured to be part of the systems and method for improved access to user data. The computing device202may have a processor1451that is physically configured according to computer executable instructions. In some embodiments, the processor may be specially designed or configured to optimize communication between a server such as client system server204and the computing device202relating to the system described herein. The computing device202may have a portable power supply1455such as a battery, which may be rechargeable. It may also have a sound and video module1461which assists in displaying video and sound and may turn off when not in use to conserve power and battery life. The computing device202may also have volatile memory1465and non-volatile memory1471. The computing device202may have GPS capabilities that may be a separate circuit or may be part of the processor1451. There also may be an input/output bus1475that shuttles data to and from the various user input/output devices such as a microphone, a camera, a display, or other input/output devices. The computing device202also may control communicating with networks either through wireless or wired devices. Of course, this is just one embodiment of a computing device202and the number and types of computing devices202is limited only by the imagination. The physical elements that make up an embodiment of a server, such as the client system server204, are further illustrated inFIG.7. In some embodiments, the client system server may be specially configured to run the system and methods for improved user data or the user data API as described herein. At a high level, the client system server304may include a digital storage such as a magnetic disk, an optical disk, flash storage, non-volatile storage, etc. Structured data may be stored in the digital storage a database. More specifically, the server304may have a processor1500that is physically configured according to computer executable instructions. In some embodiments, the processor1500can be specially designed or configured to optimize communication between a computing device, such as computing device202, and the server204relating to the system as described herein. The server204may also have a sound and video module1505which assists in displaying video and sound and may turn off when not in use to conserve power and battery life. The server204may also have volatile memory1510and non-volatile memory1515. A database1525for digitally storing structured data may be stored in the memory1510or1515or may be separate. The database1525may also be part of a cloud of servers and may be stored in a distributed manner across a plurality of servers. There also may be an input/output bus1520that shuttles data to and from the various user input devices such as a microphone, a camera, a display monitor or screen, etc. The input/output bus1520also may control communicating with networks either through wireless or wired devices. In some embodiments, a user data controller for running a user data API may be located on the computing device202. However, in other embodiments, the user data controller may be located on client system server204, or both the computing device202and the server204. Of course, this is just one embodiment of the client system server204and additional types of servers are contemplated herein. The figures depict preferred embodiments for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles described herein. Upon reading this disclosure, those of skill in the art will appreciate still additional alternative structural and functional designs for the systems and methods described herein through the disclosed principles herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those skilled in the art, may be made in the arrangement, operation and details of the systems and methods disclosed herein without departing from the spirit and scope defined in any appended claims. | 39,894 |
11943685 | A. First Embodiment A1. System Configuration: FIG.1is a schematic diagram depicting an embodiment of a server system. This system1000includes a DNS server60, a service server70, an administration terminal80, a plurality of terminal devices90A and90B, a user terminal95, and a server system100. These devices60,70,80,90A,90B,95, and100are connected to a network NT. The network NT may include the Internet. Further, the network NT may include local networks. In the first embodiment, the first terminal device90A is a printer having a printing execution part90PR. Illustration being omitted, the second terminal device90B has the same hardware configuration as the first terminal device90A. The service server70provides various services for using the plurality of terminal devices including the terminal devices90A and90B via the network NT. For example, the service server70causes the first terminal device90A to print images according to a request from the user terminal95(such a service is also referred to as remote printing). The server system100carries out various processes for always-on connection between the service server70and the plurality of terminal devices90A and90B. The server system100has a plurality of always-on connection processing parts10A,10B, and10C, an administration load balancer20, a cluster administration server30, a selection server40, and a control server50. The always-on connection processing parts10A,10B, and10C establish the always-on connection with a terminal device (such as the first terminal device90A), respectively (the always-on connection processing parts10A,10B, and10C will also be simply referred below as connection processing parts10A,10B, and10C). As will be described later on, the connection processing parts10A,10B, and10C have, respectively, node clusters12A,12B, and12C each having a plurality of nodes constructed in order to establish the always-on connection. The cluster administration server30carries out a process to allocate a node cluster to a terminal device. The administration load balancer20disperses the communication load on a plurality of node clusters by distributing the communication between the cluster administration server30and the node clusters to the node cluster of a communication target. The selection server40selects allocation label information to be assigned to the terminal device. As will be described later on, the label information is allocated in advance to each of the node clusters12A,12B, and12C. Then, the terminal device is allocated with the node cluster having the label information suitable for the allocation label information for the terminal device. The control server50controls the server system100. The first connection processing part10A has a first load balancer11A and a node cluster12A. The node cluster12A has a plurality of nodes (including nodes13A1to13A3). The plurality of nodes have the same hardware configuration. Hereinbelow, if there is no need to distinguish the individual nodes of the first node cluster12A, then those respective nodes will also be referred to as nodes13A. In the first embodiment, the nodes13A establish the always-on connection with the terminal device (such as the first terminal device90A) (the nodes13A are an example of the always-on connection execution part). Various methods are adoptable for establishing the always-on connection. In the first embodiment, the nodes13A establish a communication session for the always-on connection according to XMPP (Extensible Messaging and Presence Protocol). The service server70can communicate with the terminal device by using the nodes13A. The first load balancer11A disperses the load of the always-on connection on the plurality of nodes13A by distributing the always-on connection with a plurality of terminal devices to the plurality of nodes13A. Likewise, the other connection processing parts10B and10C have load balancers11B and11C, and node clusters12B and12C, respectively. The load balancers11B and11C each have the same hardware configuration as the first load balancer11A. The second node cluster12B has a plurality of nodes13B, and the third node cluster12C has a plurality of nodes13C. The nodes13B and13C each have the same hardware configuration as the node13A. Note that the server system100may include more than three connection processing parts. Hereinbelow, if there is no need to distinguish the individual connection processing parts, then those respective connection processing parts will also be referred to as connection processing parts10A. Then, those respective load balancers and the node clusters of the connection processing parts10A will also be referred to as load balancers11and the node clusters12, respectively. Those respective nodes included in the node clusters12will also be referred to as nodes13. The total number of nodes13included in one node cluster12may differ between the plurality of node clusters12. In the first embodiment, each of the devices11A,13A,20,30,40,50,60,70,80, and90A has a computer. In particular, the devices11A,13A,20,30,40,50,60,70,80, and90A have processing parts (such as CPUs)11p,13p,20p,30p,40p,50p,60p,70p,80p, and90p, volatile storage devices (such as DRAMs)11v,13v,20v,30v,40v,50v,60v,70v,80v, and90v, nonvolatile storage devices (such as flash memories)11n,13n,20n,30n,40n,50n,60n,70n,80n, and90n, and communication interfaces (such as wired LAN interfaces or wireless interfaces according to IEEE 802.11)11i,13i,20i,30i,40i,50i,60i,70i,80i, and90i, respectively. The nonvolatile storage devices11n,13n,20n,30n,40n,50n,60n,70n,80n, and90nstore beforehand programs11pg,13pg,20pg,30pg,40pg,50pg,60pg,70pg,80pg, and90pgfor operating the corresponding devices11,13,20,30,40,50,60,70,80, and90. The processing parts11p,13p,20p,30p,40p,50p,60p,70p,80p, and90pcarry out aftermentioned various processes according to the programs11pg,13pg,20pg,30pg,40pg,50pg,60pg,70pg,80pg, and90pg. The program for the terminal device (for example, the program90pgfor the first terminal device90A) is an example of firmware. The nonvolatile storage device of the load balancer11of the connection processing part10(such as the nonvolatile storage device11nof the first load balancer11A of the first connection processing part10A) stores dispersion data101indicating a corresponding relation between the terminal device and the node. The nonvolatile storage device30nof the cluster administration server30stores the cluster label data301and the cluster terminal data302. The nonvolatile storage device40nof the selection server40stores allocation label configuration data401. The nonvolatile storage device50nof the control server50stores API history data501, always-on connection history data502, and user corresponding relation data503. Those data101,301,302,401,501,502, and503will be described in detail later on. The nonvolatile storage device70nof the service server70stores service corresponding relation data701and history data702. The service corresponding relation data701indicate a corresponding relation between a user identifier for using the service and an identifier for the terminal device used in the service. This corresponding relation is preregistered by the user, and the service corresponding relation data701are predetermined. The history data702indicate a history of using the service. Whenever the service is used, the processing part70pof the service server70updates the history data702. The DNS server60carries out name resolution on the network NT. The nonvolatile storage device60nof the DNS server60stores record data RD indicating a corresponding relation between an IP address and a domain name. The record data RD indicate a plurality of corresponding relations including corresponding relations R1to R3. These corresponding relations R1to R3respectively indicate the load balancers11A to11C. Illustration being omitted, the record data RD also indicate a corresponding relation between the control server50and the service server70. The user terminal95is a terminal device operated by the user such as a smartphone, a tablet computer, a personal computer, or the like. The user can let the service server70carry out various processes by operating the user terminal95. FIG.2is a schematic diagram depicting an example of cluster label data301. The cluster label data301indicate a corresponding relation between a cluster identifier and label information. The cluster identifier serves to identify a node cluster12. The cluster identifier for each of a plurality of node clusters12is predetermined. InFIG.2, the cluster label data301depict the respective corresponding relations for a plurality of cluster identifiers including four cluster identifiers C1to C4. In the first embodiment, the label information indicates a combination of these two items: an area item GG and a model item GJ. The area item GG indicates the area where the terminal device is used (such as the destination, country, and the like for the terminal device). InFIG.2, the area item GG is selected from a plurality of areas including a first area GG1and a second area GG2. The model item GJ indicates the model of the terminal device. InFIG.2, the model item GJ is selected from a plurality of models including a first model GJ1and a second model GJ2. In this manner, in the first embodiment, each node cluster12is assigned beforehand with the label information for a plurality of node clusters12to disperse the load according to the combination of the area item GG and the model item GJ. A2. The Always-on Connection: FIG.3is a sequence diagram depicting an example of processing for establishing an always-on connection.FIG.3depicts an example of processing when the first terminal device90A establishes the always-on connection with the server system100. The processing part90pof the first terminal device90A starts the processing for establishing the always-on connection according to the first terminal device90A switching from the power off state to the power on state. Further, if the always-on connection breaks due to some communication error or the like, then the processing part90palso starts the processing for establishing the always-on connection. In the step S110, the processing part90psends a registration request of the terminal device to the control server50. The registration request includes terminal information data with terminal information related to the first terminal device90A. The terminal information may include any information related to the first terminal device90A (for example, the identifier, IP address, model name, firmware version and the like for the first terminal device90A). In the first embodiment, the terminal information includes the identifier and model name of the first terminal device90A. Further, in the first embodiment, the nonvolatile storage device90nstores data indicating the terminal information in advance (not depicted). The processing part90pcan acquire the terminal information by referring to the data. In the step S120, the processing part50pof the control server50sends to the selection server40a determination request for the allocation label information which is the label information to be allocated to the first terminal device90A. The determination request includes the terminal information data received in the step S110. In the step S130, the processing part40pof the selection server40determines the allocation label information.FIG.4is a flow chart depicting an example of processing for determining allocation label information. In the step S510, the processing part40pof the selection server40refers to the allocation label configuration data401(FIG.1), and acquires an allocation label configuration which is the configuration of the allocation label information. As depicted inFIG.2, in the first embodiment, the label information indicates the combination of the two items: the area item GG and the model item GJ. The allocation label configuration data401indicate that the combination of the area item GG and the model item GJ should be determined as the allocation label information. In the step S520, the processing part40pacquires information used in determining the allocation label information. In the first embodiment, the processing part40prefers to the terminal information data included in the determination request received in the step S120(FIG.3), and acquires the information. In the first embodiment, the processing part40pacquires the identifier and model name of the terminal device. In the step S530, the processing part40puses the information acquired in the step S520, and determines the allocation label information according to the allocation label configuration. In the first embodiment, the processing part40puses the identifier for the first terminal device90A to determine the area item GG of the allocation label information. For example, the area item GG is determined to be a first area GG1. A corresponding relation between the identifier and the area item GG for the terminal device is predetermined. Further, the processing part40puses the model name of the first terminal device90A to determine the model item GJ of the allocation label information. For example, the model item GJ is determined to be a first model GJ1. Then, the processing part40pends the process ofFIG.4, that is, the step S130ofFIG.3. Note that for a terminal device of some specific type, in some cases, it may be preferable to disperse the node cluster12to be allocated on a plurality of node clusters12, instead of allocating a specific node cluster12. For example, if there is little shipment of the terminal devices of a specific type corresponding to a specific model name, then the node cluster12to be allocated to those terminal devices of the specific type may be dispersed on a plurality of node clusters12. In the first embodiment, for the terminal devices of a specific type, the processing part40pdetermines empty allocation label information without determining any particular allocation label information. In the step S140(FIG.3), the processing part40pof the selection server40notifies the control server50of the determined allocation label information. The notification includes allocation label information data of the allocation label information. In the step S150, the processing part50pof the control server50sends to the cluster administration server30an allocation request of the node cluster12to the first terminal device90A. The allocation request includes the allocation label information data acquired in the step S140, and data indicating information about the first terminal device90A (such as the identifier, IP address, and the like). In the step S160, the processing part30pof the cluster administration server30allocates the node cluster12to the first terminal device90A. The node cluster12allocated is one node cluster12to establish the always-on connection with the first terminal device90A.FIG.5is a flow chart depicting an example of processing for allocation of a node cluster. In the step S610, the processing part30pacquires the allocation label information. In the first embodiment, the processing part30prefers to the allocation label information data acquired in the step S150(FIG.3), and acquires the allocation label information. In the step S620, the processing part30pdetermines whether or not the allocation label information is empty. If the allocation label information is empty (S620: Yes), then in the step S630, the processing part30pextracts all node clusters as candidate clusters, and the process shifts to the step S650. If the allocation label information is not empty (S620: No), then in the step S640, the processing part30prefers to the cluster label data301(FIG.2), and extracts the node clusters fitting for the allocation label information as the candidate clusters. In the first embodiment, the processing part30pextracts the node clusters assigned with the allocation label information as the candidate clusters. In particular, the processing part30pextracts the node clusters associated with the label information including the respective options for all items of the allocation label information, as the candidate clusters. For example, if the area item GG of the allocation label information is the first area GG1and the model item GJ is the first model GJ1, then the processing part30pextracts the first cluster identifier C1associated with the label information including the first area GG1and the first model GJ1. After the step S640, the processing part30plets the process proceed to the step S650. In the step S650, the processing part30pdetermines whether or not the total number N of candidate clusters is one. If N=1 (S650: Yes), then in the step S660, the processing part30pdetermines the candidate cluster to be the target node cluster (to be also referred to simply as target cluster) to be allocated to the terminal device. The processing part30padds to the cluster terminal data302(FIG.1) the data indicating the corresponding relation between the identifier for the terminal device and the identifier for the target cluster. FIG.6is a schematic diagram depicting an example of cluster terminal data302. The cluster terminal data302indicate a corresponding relation between the cluster identifier and the terminal device identifier. InFIG.6, the cluster terminal data302indicate the corresponding relation for each of a plurality of cluster identifiers including the four cluster identifiers C1to C4. Each of a plurality of terminal device identifiers including eight terminal device identifiers T1to T8is associated with a certain cluster identifier. In the step S660(FIG.5), the processing part30padds the terminal device identifier (such as the identifier for the first terminal device90A) indicated by the request of the step S150(FIG.3), to the terminal device identifiers associated with the cluster identifier for the target clusters. Then, the processing part30pends the process ofFIG.5, that is, the step S160(FIG.3). If the total number N of candidate clusters is not one (FIG.5: S650: No), then N>1 in the first embodiment. In this case, in the step S665, the processing part30pacquires status information from each of the N numbers of connection processing parts10(FIG.1) corresponding to the N numbers of candidate clusters. The communication between the cluster administration server30and the connection processing parts10is relayed by the administration load balancer20. The status information serves to indicate the state of the connection processing parts10and, in the first embodiment, to indicate the number of always-on connections. The number of always-on connections refers to the number of established always-on connections with the connection processing parts10. The processing part30pacquires the status information from the load balancer11of each connection processing part10. In the step S670, the processing part30pselects one connection processing part10(that is, one node cluster12) for reducing the bias in the number of always-on connections between the N numbers of candidate clusters. For example, the processing part30pselects the node cluster12having the minimum number of always-on connections from the N numbers of candidate clusters. Then, the processing part30pdetermines the selected node cluster12to be the target cluster. In the same manner as in the step S660, the processing part30padds the data indicating the corresponding relation between the identifier of the target cluster and the identifier of the terminal device to the cluster terminal data302(FIG.6). Then, the processing part30pends the process ofFIG.5, that is, the step S160(FIG.3). Hereinbelow, in the process for the first terminal device90A, let the first node cluster12A be extracted as a candidate cluster in the step S640ofFIG.5. Then, let the first node cluster12A of the first connection processing part10A be allocated to the first terminal device90A. The allocated node cluster12A is also referred to as the target node cluster12A. The connection processing part10A having the target node cluster12A is also referred to as the target connection processing part10A. In the step S170(FIG.3), the processing part30pof the cluster administration server30sends a notification to the control server50to notify the same of the completion of allocating the node cluster. The processing part90pof the first terminal device90A sends to the control server50a request for the destination to access the target node cluster12A, in the step S180after the step S110. This request includes data indicating the identifier for the first terminal device90A. In the first embodiment, URL (Uniform Resource Locator) is used as the destination. The destination will also be referred to below as cluster URL. Note that the timing for carrying out the step S180may vary. For example, the processing part90pmay carry out the step S180after a predetermined time has passed since the step S110. Instead of that, the processing part50pof the control server50may send the notification of the completion of allocating the node cluster to the first terminal device90A according to the completion notification of the step S170. Then, the processing part90pof the first terminal device90A may carry out the step S180according to that completion notification. In the step S190, the processing part50pof the control server50sends a request for the cluster URL to the cluster administration server30. This request includes data indicating the identifier for the first terminal device90A. In the step S200, the processing part30pof the cluster administration server30refers to the cluster terminal data302(FIG.6), and searches for the cluster identifier associated with the identifier of the first terminal device90A. The processing part30psends to the control server50a notification including destination data indicating the cluster URL associated with the searched cluster identifier. In the first embodiment, the cluster identifier is associated in advance with the URL of the load balancer11of the connection processing part10having the node cluster12indicated by the cluster identifier. For example, if the cluster identifier indicates the first node cluster12A (FIG.1), then the cluster identifier is associated with the URL of the first load balancer11A. In the step S210, the processing part50pof the control server50sends to the first terminal device90A a notification including the destination data indicating the cluster URL. In the step S220, the processing part90pof the first terminal device90A sends a request for establishing the always-on connection to the device indicated by the cluster URL. The DNS server60(FIG.1) provides the IP address of the destination device (the first load balancer11A in this case). The request for establishing the always-on connection includes data indicating information related to the first terminal device90A (including the IP address and the identifier for the terminal device). In the step S230, the processing part11pof the first load balancer11of the first connection processing part10A selects one node13A to be allocated to the source of sending the request of establishing the always-on connection (the first terminal device90A in this case) from the plurality of nodes13A of the first node cluster12A. The one node13A is selected for reducing the bias in the load between the plurality of nodes13A of the first node cluster12A or in the number of always-on connections. In the first embodiment, the node13A is selected for reducing the bias in the number of always-on connections. Hereinbelow, the selected node13A will also be referred to as target node13A. The processing part11pof the load balancer11A adds data indicating the corresponding relation between the terminal device and the target node to the dispersion data101(FIG.1). In the step S240, the processing part11pof the first load balancer11A of the first connection processing part10A supplies a request for establishing the always-on connection from the first terminal device90A to the target node13A of the first connection processing part10A. The processing part13pof the target node13A carries out processing for establishing the always-on connection by way of communication with the first terminal device90A according to the request for establishing the always-on connection. With the above steps, the always-on connection between the target node13A and the first terminal device90A is established. Then, the processing for establishing the always-on connection is ended. After establishing the always-on connection, a so-called Keep Alive communication is carried out to keep the always-on connection between the target node13A and the first terminal device90A (S250). For example, the processing part13pof the target node13A sends data of Keep Alive destined for the first terminal device90A according to a predetermined schedule (such as a predetermined time interval). The processing part90pof the first terminal device90A sends data indicating a response destined for the target node13A according to the received data of Keep Alive. By virtue of this, the communication session is kept between the target node13A and the first terminal device90A. Note that instead of the target node13A, the processing part90pof the first terminal device90A may send the data of Keep Alive destined for the target node13A according to the predetermined schedule. In the first embodiment, the load balancer11of the first connection processing part10A or the node13sends result data indicating a result of connection confirmation by the Keep Alive communication to the control server50(S255). The result data indicate the identifier for the terminal device, the IP address of the terminal device, the time and date, and a flag indicating whether or not the connection confirmation is successful. The processing part50pof the control server50adds the result data to the always-on connection history data502(FIG.1) (S260). In this manner, the always-on connection history data502is updated to show the history of the always-on connection of each terminal device. The steps S250to S260are carried out repetitively. Note that in the first embodiment, the communication between the first terminal device90A and the target node13A is relayed by the first load balancer11A. Instead of that, after the step S230, the target node13A and the first terminal device90A may directly communicate without the first load balancer11A staying therebetween. When another terminal device (such as the second terminal device90B) establishes the always-on connection with the server system100, in the same manner, the process ofFIG.3is also carried out. On this occasion, the first terminal device90A is replaced by the other terminal device, and the first connection processing part10A is replaced by the connection processing part10having the node cluster12allocated to the terminal device in the step S160. A3. Service: FIG.7is a flow chart depicting an example of processing for using a service with the service server70(FIG.1). In the step S310, the service server70receives a service request from an external device such as the user terminal95or the like. Hereinbelow, let the service request be a request for the first terminal device90A to print. In first embodiment, the service request includes the user identifier for using the service, data indicating that the requested service is remote printing, data indicating the identifier for the terminal device to be used in the service (the first terminal device90A in this case), and image data for the image to be printed. In the step S320, the processing part70pof the service server70sends to the control server50a request for association between the user identifier and the identifier for the first terminal device90A. In the step S330, the processing part50pof the control server50associates the user identifier with the identifier for the first terminal device90A, and adds data indicating this corresponding relation to the user corresponding relation data503(FIG.1). In this manner, the user corresponding relation data503indicate the corresponding relation between the user identifier and the identifier for the terminal device. In the step S340, the processing part50psends a completion notification to the service server70. In the step S350, the processing part70pof the service server70sends a request for printing destined for the first terminal device90A to the control server50. In the first embodiment, the processing part70puses image data for the image to be printed to generate print data for the first terminal device90A. The processing part70plets the nonvolatile storage device70nstore the print data, and generates URL of accessing the print data (to be also referred to as print URL). The request for printing includes print URL data indicating the print URL. In the step S360, the processing part50pof the control server50sends to the cluster administration server30a request for sending the request for printing destined for the first terminal device90A. In the step S370, the processing part30pof the cluster administration server30refers to the cluster terminal data302(FIG.6), and acquires the cluster identifier associated with the first terminal device90A. The processing part30psends a request for sending the printing request destined for the first terminal device90A, to the load balancer11of the connection processing part10having the node cluster12indicated by the acquired cluster identifier (to the first load balancer11A of the first connection processing part10A in this case). In the step S380, the processing part30psends a completion notification to the control server50. In the step S390, the processing part50psends a completion notification to the service server70. In the step S400, the processing part11pof the first load balancer11A of the first connection processing part10A refers to the dispersion data101, and searches for the target node13A associated with the first terminal device90A which is the destination of the printing request. The processing part11psends a request for sending the printing request destined for the first terminal device90A to the searched target node13A. The processing part13pof the target node13A sends the printing request to the first terminal device90A. This printing request includes print URL data. In the step S410, the processing part13pof the target node13A sends to the cluster administration server30, via the administration load balancer20, a result notification including result data indicating a result of the sent printing request. In the step S415, the processing part30pof the cluster administration server30sends the result notification to the control server50. In the step S420, the processing part50pof the control server50updates the API history data501. The API history data501indicates a history of using API (Application Programming Interface). The API for the history in question is released to the service server70by the server system100(the control server50in this case), including the API for making the request for service such as remote printing, remote scanning, and the like. The processing part50padds to the API history data501the data indicating, for example, the identifier of the user requesting for the service, the identifier for the terminal device, the time and date, and a flag indicating whether or not the communication is successful between the node13and the terminal device. In the step S430, the processing part50psends a result notification to the service server70. In the step S440, the processing part70pof the service server70updates the history data702(FIG.1). For example, the processing part70padds to the history data702the data indicating the user identifier, the identifier for the terminal device used in the service, printed pages, the time and date, and the flag indicating whether or not the communication is successful between the node13and the terminal device. In the step S450, the processing part90pof the first terminal device90A accesses the print URL indicated by the print URL data included in the printing request, and sends a print data request. In the first embodiment, the print URL indicates the print data stored in the nonvolatile storage device70nof the service server70. In the step S460, the processing part70pof the service server70sends the print data to the first terminal device90A according to the request. In the step S470, the processing part90pof the first terminal device90A causes the printing execution part90PR to print images by controlling the printing execution part90PR according to the print data. Then, the process ofFIG.7is ended. Note that if sending the request for printing in the step S400is not successful, then the steps S450to S470are omitted. In the above manner, in the first embodiment, the server system100(FIG.1) is configured to establish the always-on connection with the terminal devices90A and90B, and the like. The server system100has a plurality of connection processing parts10, an administration load balancer20, a cluster administration server30, a selection server40, and a control server50. As explained withFIG.3, the devices20to50share the processes for controlling the plurality of connection processing parts10. Hereinbelow, the devices20to50will also be referred to collectively as controller5. Each of the connection processing parts10includes a node cluster12constructed from a plurality of nodes13. The nodes13are an example of always-on connection execution parts configured to establish the always-on connection. In the step S110(FIG.3), the controller5(the control server50in this case) receives a registration request for the always-on connection from the first terminal device90A (the registration request will be also referred to as first request). In the steps S120to S160, the controller5(the devices30to50in this case) determines one target node cluster12A to establish the always-on connection with the terminal device among the plurality of node clusters12according to the first request. The target connection processing part10A having the target node cluster12A is an example of the target always-on connection processing part which is one always-on connection processing part to establish the always-on connection with the first terminal device90A. The steps S120to S160are an example of determination processing for determining the target connection processing part10A to establish the always-on connection with the first terminal device90A. In the steps S200and S210, the controller5(the devices30and50in this case) sends to the first terminal device90A the destination data indicating the target connection processing part10A and indicating the cluster URL, after determining the target connection processing part10A. The cluster URL is an example of destination of the request for establishment of the always-on connection. The target connection processing part10A is configured to establish the always-on connection between the first terminal device90A and one target node13A among the plurality of nodes13included in the first connection processing part10A (hereinbelow, the request for establishment will also be referred to as second request), according to the request for establishment from the first terminal device90A (S220). In this manner, the controller5of the server system100determines the target connection processing part10A to establish the always-on connection according to the first request from the first terminal device90A. Therefore, the server system100having the plurality of connection processing parts10can establish the always-on connection appropriately with the first terminal device90A. In the first embodiment, in the determining process by the target connection processing part10A (the steps S120to S160), the controller5uses one piece or more of information including the model item GJ for the first terminal device90A (the area item GG and the model item GJ (FIG.2) in the first embodiment), to determine the target connection processing part10A. The model item GJ is an example of terminal specification information related to the specifications of the first terminal device90A. The controller5can determine the target connection processing part10A suitable for the first terminal device90A by using such kind of terminal specification information. For example, as depicted inFIG.2, a first model GJ1and a second model GJ2are allocated with identifiers different from each other (that is, the connection processing parts10different from each other). In this manner, according to the model item GJ (more generally, the specification of the terminal device), it is possible to disperse the load of the always-on connection on a plurality of connection processing parts10. In the first embodiment, as depicted inFIG.2, the plurality of node clusters12(that is, the plurality of connection processing parts10) are each assigned with the label information. As depicted inFIG.3, the determining process by the target connection processing part10A (the steps S120to S160) includes the steps S130and S160. In the step S130, the controller5(the selection server40in this case) determines the allocation label information to be allocated to the first terminal device90A. The step S160includes the process ofFIG.5. As explained inFIG.5, the controller5(the cluster administration server30in this case) determines the node cluster12A assigned with the allocation label information to be the target cluster among the plurality of node clusters12. That is, the cluster administration server30determines the first connection processing part10A assigned with the allocation label information as the target connection processing part10A among the plurality of connection processing parts10. In this manner, the controller5determines the target connection processing part to be allocated to the terminal device via the label information. Therefore, the controller5can use the label information to determine a proper target connection processing part. Suppose that the controller5uses information of the terminal device to directly determine the target connection processing part without using the label information. Then, it is not easy to adjust the corresponding relation between the terminal device and the connection processing part (for example, the algorithm is changed for determining the target connection processing part from the information of the terminal device). In the first embodiment, it can be easy to adjust the corresponding relation between the terminal device and the connection processing part by changing the label information (FIG.2) assigned to the node cluster12(that is, to the connection processing part10). The cluster label data301(FIG.2) may associate the same label information with a plurality of cluster identifiers. For example, the cluster label data301may associate a combination of the first area GG1and the first model GJ1with a plurality of cluster identifiers. In the step S640ofFIG.5, if the allocation label information indicates the combination of the first area GG1and the first model GJ1, then the processing part30pof the cluster administration server30extracts the plurality of node clusters12as a plurality of candidate clusters, associated with the combination of the first area GG1and the first model GJ1. In this manner, the plurality of node clusters12may include a plurality of node clusters12assigned with the allocation label information. That is, the plurality of connection processing parts10may include a plurality of candidate processing parts being the plurality of connection processing parts assigned with the allocation label information. In the steps S665and S670, the processing part30pdetermines one target node cluster (that is, one target connection processing part) to reduce the bias in the number of always-on connections between the plurality of candidate clusters. In this manner, the server system100can reduce the bias in the number of always-on connections between a plurality of candidate processing parts. Therefore, there is a lower possibility of a concentrated load on some of the plurality of connection processing parts10. The cluster label data301(FIG.2) may associate specific label information with one cluster identifier only. For example, the cluster label data301may associate label information indicating the combination of the first area GG1and the first model GJ1with the first cluster identifier C1only (this label information will be referred to as single cluster label information). In the step S640ofFIG.5, if the allocation label information indicates the single cluster label information, then the processing part30pof the cluster administration server30extracts one cluster identifier only (for example, the first cluster identifier C1). If the allocation label information indicating the single cluster label information is allocated to a plurality of terminal devices, then the controller5determines the same connection processing part10associated with the first cluster identifier C1as the target connection processing part, for those plurality of terminal devices. In this manner, the controller5may determine the same connection processing part as the target connection processing part for the plurality of terminal devices satisfying a specific condition (for example, the condition of allocating the allocation label information indicating the single cluster label information). According to this configuration, a specific connection processing part10suitable for a plurality of terminal devices satisfying the specific condition can establish the always-on connection with those plurality of terminal devices. For example, the node cluster12of the specific connection processing part10may be configured to have a suitable number of nodes13for the number of shipments of a plurality of terminal devices satisfying the specific condition. As explained withFIG.1, the plurality of connection processing parts10each have a load balancer11. As explained for the steps S230and S240ofFIG.3, the load balancer11is configured to distribute the second condition received by the connection processing part10(that is, in the first embodiment, the request for establishing the always-on connection) to a plurality of nodes13. As explained for the step S200ofFIG.3, the destination data indicating the destination with the second request for the always-on connection indicate the load balancer11of the target connection processing part (the URL of the load balancer11in the first embodiment). Therefore, the connection processing part10including a load balancer11and a plurality of nodes13can establish the always-on connection appropriately with the terminal device. B. Second Embodiment FIGS.8to10are schematic diagrams depicting another embodiment of label information. The label information is not limited to the area item GG (FIG.2) and the model item GJ, but can use various other items.FIGS.8to10indicate eleven times GA to GK which are an example of usable items. Each figure indicates a corresponding relation between the type of information, item, method for acquirement, and rule for determining the cluster label data301(FIG.2). The items GA to GK are classified into the following five types: “service information”, “history information”, “connection source information”, “user information”, and “terminal specification information”. The method for acquirement is that used in determining each item in the step S520ofFIG.4. As will be described later on, as the label information, the items determined on the basis of the history about the terminal devices may use used (for example, the items GB, GC, GD, GE, GF, and GI). The power source for a terminal device can be switched by the user between the off state and the on state. If the power source is switched from the off state to the on state, then the terminal device starts the process for establishing the always-on connection (FIG.3). Further, if the always-on connection breaks due to some communication error or the like, then the terminal device also starts the process for establishing the always-on connection. On this occasion, a node cluster12suitable for the history related to the terminal device may be allocated to the terminal device. That, is, a node cluster12different from the node cluster12allocated in the past may be allocated to the terminal device. Hereinbelow, the items GA to GK will be explained one after another. B1. The Service Item GA: The service item GA (FIG.8) indicates the contents of the service of using the terminal device. The service item GA is selected, for example, from a plurality of services including a remote printing GA1, a remote scanning GA2, and an information acquiring GA3. In the service of the remote printing GA1, the service server70causes the terminal device to print images via the network NT (seeFIG.7). In the service of the remote scanning GA2, the service server70causes the terminal device having a reader device to read out from a target (such as a document sheet or the like) and to send the readout image data to a user terminal (such as the user terminal95) via the network NT. In the service of the information acquiring GA3, the service server70acquires information from the terminal device and uses the acquired information to carry out a specific process. For example, if the terminal device has a printing execution part, then the service server70acquires from the terminal device the residual information indicating the residual amount of office supplies (color materials (such as ink or toner), printing paper, and the like). Then, the service server70carries out an ordering process to place an order of the office supplies if the residual amount comes down to a threshold value or less. In the step S520ofFIG.4, the processing part40pof the selection server40acquires information used for determining the service item GA from the service server70.FIG.11Ais a flow chart depicting an example of acquirement process carried out in the step S520ofFIG.4. In the step S710, the processing part40pof the selection server40sends data indicating the identifier for the terminal device to the service server70. In the step S720, the processing part70pof the service server70sends to the selection server40the data indicating the service item GA associated in advance with the identifier for the terminal device. The processing part40pof the selection server40refers to the data from the service server70to determine the service item GA. Note that the nonvolatile storage device70nof the service server70stores beforehand the data indicating a corresponding relation between the identifier for the terminal device and the service (illustration omitted). The rule for determining the cluster label data301(FIG.2) related to the service item GA may be, for example, selected from two rules RA1and RA2. The first rule RA1is associated with a plurality of cluster identifiers with the specific service item GA. For example, since the remote printing GA1and the remote scanning GA2cannot be used under the condition of breaking of the always-on connection, it is preferable for those services to keep the always-on connection less likely to break. Therefore, the remote printing GA1and the remote scanning GA2may be each associated with a plurality of cluster identifiers. In such case, even if one connection processing part10falls into some situation of malfunction, the service server70can still carry out the services of the remote printing GA1and the remote scanning GA2for the terminal device connected to another connection processing part10. It is also preferable for the information acquiring GA3to be associated with a plurality of cluster identifiers. However, the service of the information acquiring GA3may be carried out after the always-on connection is restored if the always-on connection experienced a break. Therefore, the information acquiring GA3can be associated with one cluster identifier. The second rule RA2is to associate each service with a different cluster identifier. According to this configuration, influence is diminished on the other services due to some problem in the node cluster12caused by the load of one service. Between the plurality of connection processing parts10, the quality of the always-on connection may differ. In this case, according to the second rule RA2, the corresponding relation between the service and the cluster identifier may be determined as follows. The information acquiring GA3may be associated with the cluster identifier for the connection processing part10providing the always-on connection of a predetermined quality. The remote printing GA1and the remote scanning GA2may be each associated with the cluster identifier for the connection processing part10providing the always-on connection of a higher quality. According to this configuration, the remote printing GA1and the remote scanning GA2are less likely to break such that there is a lower possibility of stopping the services. Note that one service may be associated with any number (one or more) of cluster identifiers. Any method may be used to adjust the quality of the always-on connection. For example, illustration being omitted, the server system100is provided with a monitor monitoring the devices11and13included in the connection processing part10. Further, the connection processing part10has a substitution device for each of the devices11and13. The monitor periodically carries out a health check on each of the devices11and13. If some abnormity is detected in the health check, then the monitor lets the abnormal device be replaced by a substitution device. By virtue of this, the connection processing part10facilitates improving the quality of the always-on connection (for example, there is shortened time of interrupting the always-on connection due to some abnormity of the device). By increasing the frequency of the health check, the quality of the always-on connection is improved. Further, by adjusting the condition for abnormity detection in the health check for detecting the abnormity in a readier manner, the quality of the always-on connection is also improved. Further, by increasing the total number of nodes13of the node cluster12, the number of always-on connections is decreased per node13. By virtue of this, the possibility of malfunction of the nodes13is reduced such that the quality of the always-on connection is improved. Between the plurality of connection processing parts10, either or both of the frequency of the health check and the condition for abnormity detection may differ. Further, between the plurality of connection processing parts10, the number of always-on connections per node13may differ. B2. Printing Frequency Item GB The printing frequency item GB (FIG.8) indicates a group of printed pages NP per day via the remote printing. The printing frequency item GB is selected, for example, from a first group GB1(the printed pages NP per day are equal to or more than a predetermined threshold value NPth), and a second group GB2(the printed pages NP per day are less than the predetermined threshold value NPth). In the step S520ofFIG.4, the processing part40pof the selection server40acquires information used to determine the printing frequency item GB from the service server70according to the process ofFIG.11A. In the step S710, the processing part40pof the selection server40sends data indicating the identifier for the terminal device to the service server70. In the step S720, the processing part70pof the service server70refers to the history data702, and prepares information about the printing frequency item GB from the history of the remote printing associated with the identifier for the terminal device (for example, the total printing pages, and the days from starting use of the service to the present). The processing part70psends data indicating the prepared information to the selection server40. The processing part40pof the selection server40refers to the data from the service server70, calculates the printed pages NP per day, and determines the printing frequency item GB (For example, NP=the total printing pages/days). The rule for determining the cluster label data301(FIG.2) related to the printing frequency item GB may be, for example, selected from two rules RB1and RB2. The first rule RB1associates the first group GB1with a plurality of cluster identifiers. The first group GB1is a group of a high printing frequency, so that any terminal device of the first group GB1uses the always-on connection at a high frequency. If the first group GB1is associated with a plurality of cluster identifiers, then even in the case of one connection processing part10malfunctioning, the service server70can still carry out the remote printing with the terminal device connected to another connection processing part10. It is also preferable to associate the second group GB2to a plurality of cluster identifiers. However, any terminal device of the second group GB2uses the always-on connection at a low frequency. A temporary break of the always-on connection exerts a smaller influence on the second group GB2than that on the first group GB1. Therefore, the second group GB2may be associated with one cluster identifier. The second rule RB2associates a different cluster identifier with each group of the printing frequency item GB. The second rule RB2is a similar rule to the second rule RA2. The quality of the always-on connection may differ between the plurality of connection processing parts10. In this case, the second group GB2may be associated with the cluster identifier for a connection processing part10providing the always-on connection of a predetermined quality. The first group GB1may be associated with the cluster identifier for a connection processing part10providing the always-on connection of a higher quality. B3. Communication Frequency Item GC: The communication frequency item GC (FIG.8) indicates a group with an API usage frequency F1. The API of the API usage frequency F1is an API at which communication is brought by the node13, among the APIs released to the service server70by the server system100(the control server50in this case). In particular, the API of the API usage frequency F1serves for requesting services such as the remote printing, the remote scanning, and the like. The communication frequency item GC is selected, for example, from a first group GC1(the API usage frequency F1is equal to or more than a predetermined threshold value F1th), and a second group GC2(the API usage frequency F1is less than the predetermined threshold value F1th). In the step S520ofFIG.4, the processing part40pof the selection server40acquires the information used to determine the communication frequency item GC from the control server50.FIG.11Bis another flow chart depicting the example of acquirement process carried out in the step S520ofFIG.4. In the step S750, the processing part40pof the selection server40sends data indicating the identifier for the terminal device to the control server50. In the step S760, the processing part50pof the control server50refers to the API history data501(FIG.1), and prepares information about the API usage frequency F1from the history of using the API associated with the identifier for the terminal device (for example, the total number of usages, and the days from starting use of the service to the present). Then, the processing part50psends data indicating the prepared information to the selection server40. The processing part40pof the selection server40refers to the data from the control server50, calculates the API usage frequency F1, and determines the communication frequency item GC (For example, F1=the total number of usages/days). The rule for determining the cluster label data301(FIG.2) related to the communication frequency item GC may be, for example, selected from two rules RC1and RC2. The first rule RC1associates each of the groups GCB1and GC2with a plurality of cluster identifiers such that bias in the API usage frequency F1may be reduced. For example, the first group GC1and the second group GC2are associated with a plurality of common cluster identifiers. By virtue of this, the bias in the load is reduced between the plurality of node clusters12. The second rule RC2associates a different cluster identifier with each group of the communication frequency item GC. The second rule RC2is a similar rule to the second rule RA2. The quality of the always-on connection may differ between the plurality of connection processing parts10. In this case, the second group GC2may be associated with the cluster identifier for a connection processing part10providing the always-on connection of a predetermined quality. The first group GC1may be associated with the cluster identifier for a connection processing part10providing the always-on connection of a higher quality. B4. Error Frequency Item GD: The error frequency item GD (FIG.9) indicates a group with an API error frequency FE. The API of the API error frequency FE is the same as the API of the API usage frequency F1(FIG.8). The error frequency item GD is selected, for example, from a first group GD1(the API error frequency FE is equal to or more than a predetermined threshold value FEth), and a second group GD2(the API error frequency FE is less than the predetermined threshold value FEth). In the step S520ofFIG.4, the processing part40pof the selection server40acquires the information used to determine the error frequency item GD from the control server50, according to the process ofFIG.11B. In the step S750, the processing part40pof the selection server40sends data indicating the identifier for the terminal device to the control server50. In the step S760, the processing part50pof the control server50refers to the API history data501(FIG.1), and prepares information about the API error frequency FE from the history of using the API associated with the identifier for the terminal device (for example, the total number of errors, and the days from starting use of the service to the present). Then, the processing part50psends data indicating the prepared information to the selection server40. The processing part40pof the selection server40refers to the data from the control server50, calculates the API error frequency FE, and determines the error frequency item GD (For example, FE=the total number of errors/days). The rule for determining the cluster label data301(FIG.2) related to the error frequency item GD may be, for example, the following rule RD1. The rule RD1associates the first group GD1with one specific cluster identifier or more. According to this configuration, there is a higher possibility to allow a specific node cluster12corresponding to the specific cluster identifier to investigate the cause of the error clearly (for example, the cause may be made clear without investigating other node clusters12). The second group GD2may be associated with one cluster identifier or more different from the above one specific cluster identifier or more associated with the first group GD1. B5. Altogether Breaking Item GE: The altogether breaking item GE (FIG.9) is related to a group of a plurality of IP addresses where the always-on connections broke altogether in the past. If a network device malfunctions in processing communications from a plurality of IP addresses (such as a rooter, a gateway, or the like), then the always-on connections with the plurality of IP addresses will break altogether. Then, if the network device restores from the malfunction, then the server system100will receive all requests together for establishing the always-on connections from the plurality of IP addresses. The altogether breaking item GE is selected, for example, from a first group GE1and a second group GE2. The first group GE1is a group of the plurality of IP addresses where the always-on connections broke altogether in the past. The second group GE2is a group of the IP addresses not included in the first group GE1. The condition of the altogether breaking for the IP addresses to be included in the first group GE1may vary. For example, the condition of the altogether braking may be such that the always-on connections broke off a predetermined threshold number (100, for example) or more of the IP addresses in the past within a predetermined time period (such as 10 minutes). In the step S520ofFIG.4, the processing part40pof the selection server40acquires the information used to determine the altogether breaking item GE from the control server50, according to the process ofFIG.11B. In the step S750, the processing part40pof the selection server40sends data indicating the IP addresses of the terminal devices to the control server50. In the step S760, the processing part50pof the control server50refers to the always-on connection history data502(FIG.1), and generates a list of the plurality of IP addresses satisfying the condition of the altogether breaking. The processing part50psends data indicating whether or not the IP addresses of the terminal devices are included in the list to the selection server40. The processing part40pof the selection server40refers to the data from the control server50, and determines the altogether breaking item GE. The rule for determining the cluster label data301(FIG.2) related to the altogether breaking item GE may be, for example, the following rule RE1. The rule RE1associates the first group GE1with a plurality of cluster identifiers. The reason is stated as follows. The network device may malfunction again after a restoration. If the network device restores from the malfunction happening again, then then the server system100may receive all requests together for establishing the always-on connections from the plurality of IP addresses included in the first group GE1. If the cluster label data301is determined according to the rule RE1, then it is possible to disperse the requests for establishing the always-on connections from the plurality of IP addresses on a plurality of node clusters12. The second group GE2may be associated with one cluster identifier or more different from the cluster identifiers associated with the first group GE1. B6. Communication Failure Item GF: The communication failure item GF (FIG.9) is related to a group of a plurality of terminal devices where communication failure happened in the past. The plurality of terminal devices may be used in the same area. For example, the plurality of terminal devices may be used in the same destination. Further, the plurality of terminal devices may be provided by a seller and used in a business area of the seller. The plurality of terminal devices used in the same area may be more likely to undergo breaking of the always-on connections. For example, the network in the area of destination may be unstable. The network in the business area of the seller may be unstable. The communication failure item GF is selected, for example, from a first group GF1and a second group GF2. The first group GF1is a group where communication failure is more likely to happen. The second group GF2is a group of the terminal devices not included in the first group GF1. In the second embodiment, the identifiers for the plurality of terminal devices are divided in advance into a plurality of groups (also referred to as terminal groups). One terminal group is formed by an identifier for a plurality of terminal groups used in the same area. The areas differ from each other between the plurality of terminal groups. That is, their geographical places are different from each other. A failure group refers to a noticed terminal group included in the first group GF1. The condition of the failure group may vary in terms of indicating that the communication failure is more likely to happen. For example, the condition of the failure group may be such that the always-on connections broke in the past with a predetermined ratio (30%, for example) or more of terminal devices among the plurality of terminal devices included in the noticed terminal group within a predetermined time period (such as 10 minutes). In the step S520ofFIG.4, the processing part40pof the selection server40acquires the information used to determine the communication failure item GF from the control server50, according to the process ofFIG.11B. In the step S750, the processing part40pof the selection server40sends data indicating the identifiers for the terminal devices to the control server50. In the step S760, the processing part50pof the control server50refers to the always-on connection history data502(FIG.1), and extracts terminal groups satisfying the condition of the failure group from a predetermined plurality of terminal groups. The processing part50psends data indicating whether or not the identifiers for the terminal devices are included in the terminal groups satisfying the condition of the failure group to the selection server40. The processing part40pof the selection server40refers to the data from the control server50, and determines the communication failure item GF. The rule for determining the cluster label data301(FIG.2) related to the communication failure item GF may be selected, for example, from two rules RF1and RF2. The first rule RF1associates the first group GF1with a plurality of cluster identifiers. The reason is stated as follows. In an area where communication failure happens, the communication failure may happen again. If the system restores from the communication failure happening again, then the server system100may receive all requests together for establishing the always-on connections from the plurality of terminal devices of the terminal group included in the first group GF1. If the first rule RF1is adopted, then it is possible to disperse the requests for establishing the always-on connections from the plurality of terminal devices on a plurality of node clusters12. The second group GF2may be associated with one cluster identifier or more different from the cluster identifiers associated with the first group GF1. The second rule RF2associates a different cluster identifier with each group of the communication failure item GF. According to this configuration, if the communication failure happens in a terminal group included in the first group GF1, then the influence of the communication failure on the node cluster12associated with the second group GF2is eased. Note that the communication failure item GF may be determined by using the IP addresses instead of the identifiers for the terminal devices. B7. Area Item GG: The area item GG (FIG.9) was explained withFIG.3earlier on. The area item GG is related to connection sources of the always-on connection. The area item GG may be selected from a plurality of areas including a first area GG1, a second area GG2, and a third area GG3. In the step S520ofFIG.4, the processing part40pof the selection server40refers to the terminal information data included in the determination request received in the step S120(FIG.3), and acquires the information (the identifiers for the terminal devices in this case) used to determine the area item GG. Instead of that, the processing part40pmay acquire the information from the control server50according to the process ofFIG.11B. In the step S750, the processing part40pof the selection server40sends data indicating the information about the terminal devices (for example, the identifiers, IP addresses, and the like) to the control server50. In the step S760, the processing part50pof the control server50uses the information about the terminal devices to send data indicating the information of the areas associated with the terminal devices to the selection server40. The corresponding relation between the information about the terminal devices and the areas is predetermined. The processing part40pof the selection server40refers to the data from the control server50, and determines the area item GG. The rule for determining the cluster label data301(FIG.2) related to the area item GG may be, for example, the following rule RG1. The rule RG1associates each area of the area item GG with a different cluster identifier. According to this configuration, if the communication failure happens in one area, then the influence of the communication failure on the node cluster12associated with another area is eased. Note that the area item GG may be determined on the basis of various other kinds of information related to the area than the destination of the terminal devices, such as the IP addresses of the terminal devices, business area of the seller providing the terminal devices, and the like. B8. User Item GH: The user item (FIG.10) indicates a user associated with the terminal device. The user is, for example, the owner of the terminal device. The user item GH may be selected from a plurality of user identifiers including a first user identifier GH1and a second user identifier GH2. In the step S520ofFIG.4, the processing part40pof the selection server40acquires the information used to determine the user item GH from the control server50, according to the process ofFIG.11B. In the step S750, the processing part40pof the selection server40sends data indicating the identifier for the terminal device to the control server50. In the step S760, the processing part50pof the control server50refers to the user corresponding relation data503(FIG.1), and acquires the user identifier associated with the identifier for the terminal device. The processing part50psends data indicating the user identifier to the selection server40. The processing part40pof the selection server40refers to the data from the control server50, and determines the user item GH. The rule for determining the cluster label data301(FIG.2) related to the user item GH may be selected, for example, from two rules RH1and RH2. The first rule RH1associates each user identifier with one cluster identifier. If a plurality of terminal devices are associated with one user identifier, then the plurality of terminal devices are associated with the same one cluster identifier. According to this configuration, if some problem happens in one node cluster12, then it is possible to reduce the number of users influenced by the problem. Note that one cluster identifier may be associated with a plurality of user identifiers. The second rule RH2associates each user identifier with a plurality of cluster identifiers. If a plurality of terminal devices are associated with one user identifier, then the second rule RH2serves for dispersing the plurality of terminal devices on a plurality of node clusters12. In the step S670ofFIG.5, the processing part30pof the cluster administration server30determines one target node cluster (that is, one target connection processing part) by way of round-robin according to each user identifier. In this case, the step S665may be omitted. If the second rule RH2is used, then it is less possible that all terminal devices associated with one user identifier become not usable due to some problem of one node cluster12. B9. User Usage Frequency Item GI: The user usage frequency item GI (FIG.10) indicates the group of service usage frequency F3for each user identifier. The user usage frequency item GI is selected, for example, from a first group GI1(the service usage frequency F3is equal to or more than a predetermined threshold value F3th) and a second group GI2(the service usage frequency F3is less than the predetermined threshold value F3th). In the step S520ofFIG.4, the processing part40pof the selection server40acquires the information used to determine the user usage frequency item GI from the service server70, according to the process ofFIG.11A. In the step S710, the processing part40pof the selection server40sends data indicating the identifier for the terminal device to the service server70. In the step S720, the processing part70pof the service server70refers to the service corresponding relation data701, and acquires the user identifier associated with the identifier for the terminal device. The processing part70prefers to the history data702, and information about the user usage frequency item GI from the history of using the service associated with the identifier for the terminal device (for example, the total times of using all services, and the days from starting use of the first service to the present). Then, the processing part70psends data indicating the prepared information to the selection server40. The processing part40pof the selection server40refers to the data from the service server70, calculates the service usage frequency F3, and determines the user usage frequency item GI (For example, F3=the total times of usage/days). The rule for determining the cluster label data301(FIG.2) related to the user usage frequency item GI may be, for example, the following rule RI1. The rule RI1associates the first group GI1with one specific cluster identifier or more. The second group GI2is associated with one cluster identifier or more not included in the one specific cluster identifier or more associated with the first group GI1. The connection processing part10associated with the specific cluster identifier provides the always-on connection of a higher quality than the other connection processing parts10. According to this configuration, if a user having a high service usage frequency F3uses a new terminal device, then there is a lower possibility of causing a problem in the node cluster12due to the load of the always-on connection of that terminal device. B10. Model Item GJ The model item GJ (FIG.10) was that explained earlier on withFIG.3. The model item GJ may be selected, for example, from a plurality of models including the first model GJ1and the second model GJ2. In the step S520ofFIG.4, the processing part40pof the selection server40refers to the terminal information data included in the determination request received in the step S120(FIG.3), and acquires the information (the model name in this case) used to determine the model item GJ. Instead of that, the processing part40pmay acquire the information from the control server50according to the process ofFIG.11B. In the step S750, the processing part40pof the selection server40sends data indicating the information about the terminal devices (for example, the identifiers, IP addresses, and the like) to the control server50. In the step S760, the processing part50pof the control server50uses the information about the terminal devices to send data indicating the models of the terminal devices to the selection server40. The corresponding relation between the information about the terminal devices and the models is predetermined. The processing part40pof the selection server40refers to the data from the control server50, and determines the model item GJ. The rule for determining the cluster label data301(FIG.2) related to the model item GJ may be, for example, the following rule RJ1. The rule RJ1associates each model of the model item GJ with a different cluster identifier. Here, between the plurality of models, the functions of the terminal devices may differ (especially, the functions for the always-on connection). For example, the communication protocols for the always-on connection may differ between the plurality of models. In this case, each node cluster12is configured to have a function fitting the function of the terminal device of the corresponding model. In this manner, the plurality of node clusters12may have different functions from each other. Then, each model of the model item GJ may be associated with the node cluster12having the function fitting for the model. B11. Version Item GK: The version item GK (FIG.10) indicates a version of firmware of the terminal device. The version item GK may be selected, for example, from a plurality of versions including a first version GK1and a second version GK2. In the step S520ofFIG.4, the processing part40pof the selection server40refers to the terminal information data included in the determination request received in the step S120(FIG.3), and acquires the information (the version of firmware in this case) used to determine the version item GK. The rule for determining the cluster label data301(FIG.2) related to the version item GK may be, for example, the following rule RK1. The rule RK1associates each version of the version item GK with a different cluster identifier. Here, between the plurality of versions, the functions of the terminal devices may differ (especially, the functions for the always-on connection). For example, the communication protocols for the always-on connection may differ between the plurality of versions. In this case, each node cluster12is configured to have a function fitting the function of the terminal device of the corresponding version. In this manner, the plurality of node clusters12may have different functions from each other. Then, each version of the version item GK may be associated with the node cluster12having the function fitting for the version. Note that the label information may be a combination of any items more than one selected from the above items GA to GK. Here, the options for each item (such as the first group GB1, the second group GB2and the like of the printing frequency item GB (FIG.8)) may be associated with a cluster identifier according to the rule for the above corresponding item. The allocation label information401(FIG.1) may be predetermined to indicate the configuration of the label information (for example, the list of items included in the label information). However, the rules for determining the cluster label data301are not limited to those ofFIGS.8to10, but may be various other rules. For example, regardless of the item contents, each option for an item may be associated with a different cluster identifier. C. Third Embodiment The server system100(FIG.1) may reallocate a node cluster12to the terminal device.FIG.12is a flow chart depicting an example of allocation update process. In the step S780, the processing part50pof the control server50determines whether or not a reallocation condition is satisfied. The reallocation condition may be an arbitrary one indicating that it is preferable to reallocate the node cluster12. For example, the reallocation condition may be such that an elapsed time since the last reallocation reaches a predetermined temporal threshold value or more. If the reallocation condition is not satisfied (S780: No), then the processing part50prepeats the step S780and waits for the reallocation condition to be satisfied. If the reallocation condition is satisfied (S780: Yes), then the processing part50pcarries out a reallocation process in the step S790for the node cluster12. For example, the processing part50pmay send a command to acquire a cluster URL to the terminal device via the connection processing part10. The terminal device carries out the process of the step S180ofFIG.3according to the command. After the step S180, the process of the steps S190to S240is carried out. By virtue of this, the terminal device acquires a new cluster URL and uses the new cluster URL to reestablish the always-on connection. As a result, a new node cluster12is allocated to the terminal device. For example, based on the newest history about the terminal device, a node cluster12different from the node cluster12allocated in the past may be allocated to the terminal device. After the step S790, the process returns to the step S780. Note that in order to avoid too many requests for the establishment from reaching to the server system100, the processing part50pmay carry out the reallocation process (S790) at a different time for each terminal device. For example, the processing part50pmay repeat the reallocation process for one terminal device over a predetermined interval of time. Further, the processing part50pmay carry out the allocation update process for each terminal device. In this case, the condition for reallocation may differ for each terminal device. D. Fourth Embodiment It is allowable to change the configuration of the allocation label information to be allocated to the terminal device in the step S130ofFIG.3.FIG.13is a flow chart depicting an example of processing for changing the configuration of the allocation label information. In the step S810, the administrator of the server system100(FIG.1) operates on an undepicted operating unit (such as a touch panel, buttons, and the like) of the administration terminal80to input information indicating a new configuration. For example, the configuration of the allocation label information may combine items more than one selected arbitrarily from the items GA to GK ofFIGS.8to10. In the step S820, the processing part80pof the administration terminal80sends data indicating the new configuration to the selection server40. In the step S830, the processing part40pof the selection server40causes the nonvolatile storage device40nto store the allocation label configuration data401indicating the new configuration expressed by the received data. Then, the process ofFIG.13is ended. After updating the allocation label configuration data401, the processing part40prefers to the updated allocation label configuration data401in the step S130(FIG.3) to determine the allocation label information. In the fourth embodiment, the administrator can change the allocation label configuration data401according to the condition of using the server system100. For example, after starting operation of the server system100, there are cases where the frequency of errors of API becomes high. In such cases, the administrator may add the error frequency item GD (FIG.9) to the configuration of the allocation label information. The cluster label data301(FIG.2) may predetermine a corresponding relation between all usable items. Instead of that, the processing part30pof the cluster administration server30may allow the user to change the cluster label data301. The processing part30pmay change the cluster label data301, for example, by the same process as that ofFIG.13. The administrator inputs the label information of each of the plurality of cluster identifiers to the administration terminal80. The processing part80pof the administration terminal80sends to the cluster administration server30data indicating a corresponding relation between the label information and the cluster identifiers. The processing part30pof the cluster administration server30causes the nonvolatile storage device30nto store the cluster label data301indicating the corresponding relation expressed by the received data. Note that the administrator may add a new connection processing part10to the server system100. Then, the administrator may allocate the label information to the new connection processing part10by changing the cluster label data301. E. Modifications (1) The label information may include various kinds of information. For example, the label information may include terminal specification information related to the specifications of terminal devices. The model item GJ (FIG.10) and the version item GK are an example of the terminal specification information. Various other kinds of information may be adopted as the terminal specification information (such as the number of types of color materials usable for printing, resolution of reader devices, details of the function of terminal devices, and the like). The controller5can use one piece or more of the above information including the terminal specification information for determining a target node cluster (FIG.3: the steps S120to S160), to appropriately disperse a plurality of terminal devices on a plurality of connection processing parts10according to the specifications of each terminal device. The label information may include user information associated with the user of a terminal device. The user item GH (FIG.10) and the user usage frequency item GI are an example of the user information. Various other kinds of information may be adopted as the user information (such as the ages of users, the language setting for terminal devices, and the like). The controller5can use one piece or more of the above information including the user information for determining a target node cluster (FIG.3: the steps S120to S160), to appropriately disperse a plurality of terminal devices on a plurality of connection processing parts10according to the user attribution indicated by the user information. The label information may include service information related to the usable service for the terminal devices. The service item GA (FIG.8) and the printing frequency item GB are an example of the service information. Various other kinds of information may be adopted as the service information (such as the reading frequency of reader devices, and the like). The controller5can use one piece or more of the above information including the service information for determining a target node cluster (FIG.3: the steps S120to S160), to appropriately disperse a plurality of terminal devices on a plurality of connection processing parts10according to the usable service. The label information may include history information related to communication history of terminal devices. The communication frequency item GC (FIG.8), the error frequency item GD (FIG.9), the altogether breaking item GE, and the communication failure item GF are an example of the history information. Various other kinds of information may be adopted as the history information (such as the total number of breaks of the always-on connection, and the like). The controller5can use one piece or more of the above information including the history information for determining a target node cluster (FIG.3: the steps S120to S160), to appropriately disperse a plurality of terminal devices on a plurality of connection processing parts10according to the communication history. (2) In the step S520ofFIG.4, the process of acquiring the information used to determine the allocation label information may be various other processes instead of the process of referring to the terminal information data included in the determination request of the step S120(FIG.3), and the process ofFIGS.11A and11B. For example, the processing part40pof the selection server40may acquire information (such as information related to the terminal device) from the terminal device being the source of sending the registration request of the step S110(FIG.3). Further, the processing part40pmay acquire information (such as information related to communication history of the always-on connection) from the load balancer11of the connection processing part10. (3) The status information used in the steps S665and S670ofFIG.5is not limited to the number of always-on connections having established with the connection processing parts10, but may indicate various states of the connection processing parts10. For example, the status information may indicate the load of a connection processing part10. The load of the connection processing part10may be, for example, a combination of total usage rate of the CPU and total usage rate of the memory. The total usage rate of the CPU may take a variety of values calculated by using the usage rate of the CPU of each of the plurality of nodes13included in the node clusters12of the connection processing parts10. The total usage rate of the CPU may take, for example, a representative value (such as average value, a mode value, a median value, or the like). The total usage rate of the memory may take a variety of values calculated by using the usage rate of the memory of each of the plurality of nodes13included in the node clusters12of the connection processing parts10. The total usage rate of the memory may also take, for example, a representative value (such as an average value, a mode value, a median value, or the like). In the step S670, the processing part30pselects one connection processing part10(that is, one node cluster12) such that there may be less bias in the load between the N numbers of candidate clusters. For example, the processing part30pmay select from the N numbers of candidate clusters a candidate cluster having the minimum total usage rate of the CPU and the minimum total usage rate of the memory. If the candidate cluster having the minimum total usage rate of the CPU is different from the candidate cluster having the minimum total usage rate of the memory, then the candidate cluster having the minimum total usage rate of the memory may be selected. Likewise, in the step S230ofFIG.3, the processing part11pof the load balancer11may select one node13such that there may be less bias in the load between the plurality of nodes13of the node cluster12. For example, the processing part11pmay select from the plurality of nodes13a node13having the minimum usage rate of the CPU and the minimum usage rate of the memory. If the node13having the minimum usage rate of the CPU is different from the node13having the minimum usage rate of the memory, then the node13having the minimum usage rate of the memory may be selected. (4) The process for establishing the always-on connection may be any of various other processes instead of the process ofFIG.3. For example, the first request for determining one connection processing part10to establish the always-on connection with the terminal device may be any of various other requests instead of the registration request for the terminal device (FIG.3: S110). Further, the second request for establishing the always-on connection may be any of various other requests instead of the establishment request for the always-on connection (FIG.3: S220). The destination data may be sent at any timing after determining one connection processing part10to establish the always-on connection with the terminal device (FIG.3: S160). For example, the processing part30pof the cluster administration server30may send a notification including the destination data to the control server50. Then, the processing part50pof the control server50may send the notification including the destination data to the terminal device according to the receipt of the notification of the step S170. In this case, the steps S180to S210may be omitted, and the destination indicated by the destination data may be any information indicating the destination on the network such as an IP address or the like, instead of the URL. In the step S670ofFIG.5, the processing part30pof the cluster administration server30may select one node cluster12from the N numbers of candidate clusters by way of round-robin without using the status information. In this case, the step S665may be omitted. (5) In the above respective embodiments, the label information is used to determine one connection processing part10to establish the always-on connection with the terminal device (FIG.3: the steps S120to S160). In particular, in the process of determining the connection processing part10(the steps S120to S160), the allocation label information is used instead of detailed information about the terminal device. Therefore, compared to a case of using the detailed information about the terminal device, it is possible to configure the determining process readily. Further, by changing the allocation label information allocated to the terminal device or the label information assigned to the connection processing part10, it is possible to readily change the corresponding relation between the terminal device and the connection processing part10. Note that the allocation label information may be associated with a plurality of connection processing parts10. Instead of that, the allocation label information may also be associated with one connection processing part10. (6) It is possible to determine one connection processing part10to establish the always-on connection with the terminal device, without using the label information. For example, the step S160(FIG.3) may be configured to let the processing part30pof the cluster administration server30use detailed information about the terminal device to select the connection processing part10, without using the label information. Further, the processing part30pmay select a connection processing part10to reduce the bias in the load between a plurality of connection processing parts10or the bias in the number of always-on connections between the plurality of connection processing parts10, without using the information about the terminal device. For example, in the step S160(FIG.3), the processing part30pmay carry out the process of the steps of S665and S670(FIG.5). The steps S610to S660are omitted. Further, the steps S120to S140ofFIG.3are omitted. Further, the processing part30pmay select a connection processing part10by way of round-robin, without using the information about the terminal device, the load of the connection processing parts10, and the number of always-on connections of the connection processing parts10. Further, the processing part30pmay be configured to select in the step S160(FIG.3) the same connection processing part10for a plurality of terminal devices satisfying a predetermined specific condition. Here, the specific condition may be any condition such as, for example, a condition belonging to preselected options for the terminal device to preselect items from the aforementioned items GA to GK (FIGS.8to10). (7) The server system for the always-on connection may be configured in any other way than is the server system100ofFIG.1. For example, the load balancer11may be omitted from the connection processing part10. Here, in the step S230(FIG.3), one node13may be selected by any method. For example, among the plurality of nodes13included in the node cluster12, based on agreement, one node13may be selected for the always-on connection. The node13may be constructed of a dedicated hardware circuit such as an ASIC (Application Specific Integrated Circuit) or the like instead of a computer. Likewise, other devices of the server system100(such as the devices11,20,30,40, and50) may also be each constructed of a dedicated hardware circuit. The controller5controlling the plurality of connection processing parts10may be configured in any other way than is that ofFIG.1. For example, the cluster administration server30may have the function of the administration load balancer20, and the administration load balancer20may be omitted. Further, the control server50may have the function of the selection server40, and the selection server40may be omitted. Further, the controller5may be constructed from one server device or more. The controller5may include a plurality of devices (such as computers) capable of communication with each other via a network. In the above respective embodiments, part of the configuration realized by hardware may be replaced by software. Conversely, part of or the entire of the configuration realized by software may be replaced by hardware. Further, if part of or the entire of the function of the present teaching is realized by a computer program, then that program can be provided in the form of being stored in a computer readable recording medium (such as a non-temporary recording medium). The program may be used in a state of being stored in a recording medium (a computer readable recording medium) which is identical to or different from that on provision. The “computer readable recording medium” is not limited to portable recording media such as memory cards and CD-ROMs, but may include internal storage devices in a computer such as various ROMs and the like, external storage devices connected to a computer such as hard disk drives, and the like. Hereinabove, the present teaching was explained on the basis of the embodiments and modifications. However, the above embodiments and modifications of the present teaching are configured to facilitate comprehension of the present teaching but not to limit the present teaching. The present teaching may be changed and/or improved without departing from the true spirit thereof and, at the same time, the equivalences thereof are included in the present teaching. | 96,588 |
11943686 | DETAILED DESCRIPTION OF THE DRAWINGS FIG.1shows an information transmission system10for at least one commercial vehicle. Here, more commercial vehicles are present, i.e. one truck12as towing vehicle and two trailers14,16. In the shown embodiment, the vehicles, i.e. the truck12and two trailers14,16, are tethered and form a so-called road-train. All the vehicles, i.e. here the truck12as towing vehicle and being in the first position of the road-train, the first trailer14having the middle position of the road-train, and the second trailer16having the last position of the road-train, are each equipped with a wireless transceiver18,20,22. The wireless transceiver18is mounted on the truck12, the wireless transceiver20is mounted on the first trailer14and the wireless transceiver22is mounted on the second trailer16. In the truck, there is also an electronic control unit (ECU)19provided. All used transceivers within the system10are identical. This is also possible, when more vehicles are used and then each vehicle may be equipped with an identically made and specified transceiver. Each wireless transceiver18,20,22is capable of transmitting and receiving wireless signals W. The wireless transceivers18,20,22do not do the data processing itself, but forward the data to the processing ECU19via regular wired interface. The signal transmission between information sending module, here represented by (at least) one of the wireless transceivers18,20,22, and repeating module, here represented by (at least) one of the other wireless transceivers18,20,22, is established so as to be wireless. Also, the signal transmission between information repeating module, e.g. represented by the transceiver20on the first trailer14, and the receiving module, here represented by the transceiver22on the second trailer16, is wireless. The signal transmission between the transceivers18,20,22can be a WiFi connection. It is also possible that another standard is chosen, e.g. a standard such as Bluetooth, WAVE, ETSI ITS-G5, IEEE 802.15.4, C-V2X or the like. Furthermore, the information transmission system10comprises one or more directional antenna(s)18a,18b,20a,20b,22a,22b. The antennas18a,18b,20a,20b,22a,22bare integrated into the transceivers18,20,22. In the shown embodiment, each transceiver18,20,22has two integrated antennas18a,18b,20a,20b,22a,22b. All antennas18a,18b,20a,20b,22a,22bhave a gain of at least +5 dBi. Moreover, all antennas18a,18b,20a,20b,22a,22bhave a wired connection to the respective transceiver18,20,22. FIG.2shows the block diagram of a transceiver18,20,22according to the present invention, here with the “middle” transceiver20. The transceiver20has an antenna20aand an antenna20b. Furthermore, the transceiver20has a first wireless communication module24, a second wireless communication module26, a controller unit28, a power supply30, a wired connection32that carries the power voltage and a wired connection34that carries the signal of other sensors of the vehicle. The antenna20ais connected with a wired link21awith the first wireless communication module24. The antenna20bis connected with a wired link21bwith the second wireless communication module26. The controller unit28is connected via high speed communication links36,38to the communication module24,26. The functionality of the information transmission system10can be described as follows. The information transmission system10comprises with the first transceiver18as information sending module, with the middle transceiver20as repeating module and with the endmost transceiver22as receiving module. The first transceiver18sends signals defining a message to the middle transceiver20acting as repeating module, wherein the middle transceiver20enhances the signals and forwards the signals to the endmost transceiver22acting as receiving module. When the endmost trailer16wants to send messages to the truck12(or vice versa), this does not happen directly. Instead, the transceiver22of the endmost trailer16sends it to the middle transceiver20mounted on the trailer14in the middle via a wireless link L1. The middle transceiver20mounted on the trailer14in the middle enhances the signals and then forwards the message to the first transceiver18mounted on the truck12via another wireless link L2. The two wireless links L1, L2may operate on different channels or even use different wireless technologies. In one embodiment the used wireless technology is compliant with the Wi-Fi standards. The backwards facing radios R1are configured to behave as clients CL, while the forwards facing radios R2are configured as access points AP. The access points AP may work on different channels and therefore they do not have to share the bandwidth of the channel. Within the transceiver20, the controller unit28plays a gateway role between the two wireless communication modules24,26and its wired interface34. The controller unit28forwards the data from one wireless module24to the other wireless module26(or vice versa, as this is a bi-directional communication line) and sends the data of the sensor of the vehicle received via its wired interface34and wireless interfaces24,26. REFERENCES 10Information transmission system12Truck14Trailer16Trailer19Electronic control unit (ECU)18Information sending module18aDirectional antenna18bDirectional antenna20Repeating module20aDirectional antenna20bDirectional antenna21aWired link21bWired link22Receiving module22aDirectional antenna22bDirectional antenna24Wireless communication module26Wireless communication module28Controller unit30Power supply32Wired connection34Wired connection36Communication link38Communication linkAP Access PointCL ClientL1Wireless linkL2Wireless linkR1Facing RadioR2Facing RadioW Signals | 5,774 |
11943687 | DESCRIPTION OF THE EMBODIMENTS A data collection system according to the present disclosure is a system in which a server device collects data obtained by a plurality of vehicles (i.e., probe vehicles) traveling on a road. The date may be image data, sensor data or the like, as long as the data can be obtained by the vehicles. Each of the vehicles has a function of obtaining data during travel, and transmitting the data to the server device. In such a system, there may arise a case where a lot of duplicate data will be transmitted to the server device depending on the volume of passing traffic, thereby putting pressure on network resources. Accordingly, in the data collection system according to the present disclosure, the server device transmits to a vehicle a map showing a plurality of unit ranges in which data should be collected, and the vehicle decides, based on the information described in the map, the data to be transmitted to the server device among the data obtained. Specifically, the server device has stored a master map in which a necessity of data collection for each of a plurality of unit ranges included in a plurality of segments is represented by a binary value, wherein the server device extracts from the master map a segment corresponding to the position of a probe vehicle, and transmits it to the probe vehicle as a partial map. In addition, the probe vehicle identifies, based on the partial map received from the server device, a unit range requiring data collection, and transmits the data obtained in the unit range to the server device. According to such a configuration, each map indicating the necessity of data collection can be transmitted and received in units of segment, so it is possible to attain a reduction in the amount of data. In addition, a partial map can be replaced with another one in units of segment, version management of a map can be performed relatively easily. Moreover, the master map may be a map in which in cases where collection of data is necessary in any place within the unit range, a true value is associated with the unit range, but otherwise, a false value is associated with the unit range, and that in cases where one unit range is associated with a true value, the vehicle control unit may transmit the data obtained in this unit range to the server device. In this manner, compressibility can be improved by setting a bit according to the necessity of data collection. For example, as a compression method for a partial map, there can be adopted a well-known binary image compression method. Further, in cases where the vehicle control unit has not a partial map corresponding to at least one segment existing in the vicinity of a subject (own) vehicle, the vehicle control unit may request the partial map corresponding to this segment to the server device. According to such a configuration, only a necessary portion of the master map managed by the server device can be transmitted from the server device to the vehicle. The at least one segment existing in the vicinity of the subject vehicle may be only a segment to which the subject vehicle belongs, or may be a plurality of segments including a segment to which the subject vehicle belongs. In addition, the server device may further comprise an update unit configured to update the master map according to a collection situation of the data, wherein each time the master map is updated, the server control unit may apply a version number to each of the partial maps, and transmit both of the partial maps and their version numbers to the probe vehicle. In this manner, the master map may be updated according to the collection situation of the data. In this case, by applying a version number to a partial map, it becomes possible to grasp the latest data collection situation at the vehicle side. The version number can be, for example, a numerical value, which is incremented upon each occurrence of an update. Moreover, in cases where the vehicle control unit has a partial map corresponding to at least one segment existing in the vicinity of the subject vehicle, the vehicle control unit may transmit a version number of the partial map corresponding to this segment to the server device, and the server control unit may determine, based on the version number, whether the update of the partial map corresponding to the segment which the probe vehicle has is necessary. By transmitting the version number from the vehicle to the server device, the server device can detect whether the partial map which the vehicle has is old. When the vehicle is using the map of an old version, there is a fear of transmitting information already unnecessary for the server device, and hence, the server device may update the partial map based on the result of detection. Further, the vehicle control unit may perform the transmission of the version number at the timing of transmitting the data obtained to the server device. Hereinafter, specific embodiments of the present disclosure will be described based on the attached drawings. However, hardware configurations, module configurations, functional configurations and so on described in the respective embodiments are not intended to limit the technical scope of the present disclosure to these alone in particular as long as there are no specific statements. First Embodiment The configuration schematic of a data collection system according to a first embodiment of the present disclosure is illustrated inFIG.1. The data collection system according to this embodiment is composed of a plurality of vehicles10and a server device20. The server device20is a device that manages the plurality of vehicles10which are under the control of the server device20. Each of the vehicles10is a connected car (probe vehicle) that can communicate with the server device20and can perform a function to be described later. Here, note that inFIG.1, the one server device20is exemplified, but the server device20may be plural. In addition, the number of the vehicles10is also not limited to the number illustrated. Each of the vehicles10according to this embodiment has a function of obtaining an image outside the vehicle by using a camera mounted on the vehicle and storing it as image data, as well as a function of transmitting the image data thus obtained to the server device20. The server device20has a function of collecting the image data obtained by the vehicles10, and creating a road map by analyzing the image data. The transmission of the image data from the vehicles10to the server device20is controlled by the map created by the server device20. In the following description, the map managed by the server device20(i.e., a master map in the present disclosure) is referred to as a master partition table, and those which are obtained by dividing the master partition table into segments (i.e., partial maps in the present disclosure) are referred to as partial partition tables. Here, note that in this embodiment, the image data obtained by each of the vehicles10is transmitted to the server device20as it is, but the transmission is not necessarily limited to this mode. For example, the vehicles10may perform conversion from the image data to a characteristic quantity, and may also transmit the characteristic quantity thus converted to the server device20. In addition, sensor data obtained by sensing a road may also be transmitted to the server device20. In the description of this embodiment, “image data” and “data” are equivalent to each other. In the system in which the server device collects the data obtained by the plurality of vehicles10, it is necessary to perform control so as to prevent an excessive amount of data from being transmitted from the vehicles10. This is because in cases where such control is not performed, duplicate data (e.g., substantially the same data obtained at the same point or location) will be transmitted from the different vehicles10, whereby network resources may be strained. In the data collection system according to the first embodiment, in order to solve such a problem, the server device20stores a map (master partition table) for instructing data collection in a target area to the vehicles10and divides the master partition table into a plurality of segments, after which a partial partition table corresponding to a segment (or nearby segment) to which an optional vehicle10belongs is transmitted to the optional vehicle10. Based on the information described in the partial partition table received, the vehicle10decides image data to be transmitted to the server device20. In the data collection system according to this embodiment, the vehicles10and the server device20are mutually connected to one another through a network. For the network, there may be adopted a WAN (Wide Area Network), which is a public communication network on a worldwide scale such as for example the Internet, or other communication networks. In addition, the network may also include a telephone communication network such as a cellular or mobile phone network or the like, a radio or wireless communication network such as Wi-Fi (registered trademark) or the like. Next, the configuration of a vehicle10will be described.FIG.2is a view illustrating the system configuration of the vehicle10. The vehicle10is composed of including a control unit101, a storage unit102, a communication unit103, a vehicle-mounted camera104, and a position information obtaining unit105. The control unit101is an arithmetic unit that manages, among functions of the vehicle10, a function of obtaining and managing image data, and a function of transmitting the image data obtained. The control unit101can be achieved by an operation processing unit such as a CPU (Central Processing Unit). The control unit101is composed of including three functional modules, i.e., a partial partition table obtaining unit1011, a data management unit1012, and a transmission management unit1013. Each of these individual functional modules may be achieved by executing a program (s) stored in a storage unit102to be described later by the CPU. Before explaining each module of the control unit101, reference will be made to a master partition table managed by the server device20, and a partial partition table to be transmitted from the server device20to the vehicle10. FIG.3Ais a view visually illustrating a part of the master partition table. The master partition table is a map in which a target area for collecting image data is divided into a plurality of unit ranges. In this embodiment, a flag indicating the necessity of data collection (hereinafter, a necessity flag) is associated with each of the plurality of unit ranges. Each unit range can be defined, for example, by a mesh of50msquare, but it is not limited to this. Hereinafter, a unit range is referred to as a mesh. The master partition table is configured to be capable of being divided into a plurality of segments each having a predetermined size.FIG.3Bis a view explaining segments constituting the master partition table. Although a segment can be formed into a rectangular area of 10 km square, for example, the size and shape thereof are not limited to specific ones. The size of a segment should only be suitably set according to, for example, the capacity of a storage device mounted on the vehicle10, the frequency of communication with the server device, the speed of transmission, the speed of the movement of the vehicle10, etc. In cases where each segment is 10 km square and each mesh is 50 m square, one segment includes 40,000 meshes. In order to reduce data volume, the server device20according to this embodiment specifies one or more segments corresponding to the vehicle10from the master partition table, creates the data included in the segment as a partial partition table, and thereafter transmits it to the vehicle10. For example, in cases where the vehicle10exists in a segment E illustrated inFIG.3B, a partial partition table corresponding to the segment E is transmitted to the vehicle10. The one or more segments corresponding to the vehicle10may be, for example, a segment in which the vehicle10is located, or a plurality of segments which can be reached by the vehicle10within a predetermined period of time. The partial partition table thus transmitted is obtained by the partial partition table obtaining unit1011. In cases where it is necessary to obtain certain data in a corresponding mesh, the necessity flag is set to a true value (1), whereas in cases where it is not necessary to obtain data, the necessity flag is set to a false value (0). For example, in cases where the obtaining of data is performed in units of a road link (a road segment), and in cases where the obtaining of data is unnecessary in any point on the roads included in a mesh, the necessity flag is set to 0, whereas in other cases, the necessity flag is set to 1. The data management unit1012obtains image data, and manages the image data obtained. Specifically, at a predetermined period, the data management unit1012performs the processing of obtaining images outside the vehicle through the vehicle-mounted camera104, and storing them in the storage unit102, and also performs the processing of deleting unnecessary data among the image data stored in the storage unit102. The transmission management unit1013extracts image data stored in the storage unit102based on the received partial partition table, and performs the processing of transmitting the image date thus extracted to the server device20. A detailed method thereof will be described later. The storage unit102is composed of including a main memory or storage device and an auxiliary storage device. The main memory device is a memory in which control programs to be executed by the control unit101and data to be utilized by the control programs are developed. The auxiliary storage device is a device in which the programs to be executed in the control unit101and the data to be utilized by the control programs are stored. An operating system for executing the programs may be stored in the auxiliary storage device. The above-mentioned functions are achieved by the programs, which have been stored in the auxiliary storage device, being loaded to the main memory device and being executed by the control unit101. In addition, the storage unit102temporarily stores the image data obtained by the above-mentioned data management unit1012. In the following, a range of the storage unit102in which the image data is stored is referred to as an image storage. The communication unit103is a radio communication interface for connecting the vehicle10to the network. The communication unit103provides access to the network, for example, through a wireless LAN and/or a mobile communication service such as 3G, LTE, etc. The vehicle-mounted camera104is a camera capable of photographing the outside of the vehicle10. The vehicle-mounted camera may be arranged in any position or location, as long as it can photograph a road on which the vehicle10is running. The position information obtaining unit105is a unit that obtains the position information of the vehicle10. The position information obtaining unit105is composed of including a GPS module, for example, and obtains the position information (e.g., latitude and longitude) of the vehicle10. Here, note that the configuration illustrated inFIG.2is an example, and all or part of the illustrated functions may be carried out by using a circuit(s) designed for exclusive use. Also, the storage and/or execution of the programs may be carried out by a combination(s) of a main memory device and an auxiliary storage device(s) other than the one illustrated. Next, the configuration of the server device20will be described. FIG.4is a view illustrating a system configuration of the server device20. The server device20is composed of including a communication unit201, a storage unit202, and a control unit203. The server device20is composed by a general or common computer. That is, the server device20is a computer that includes a processor such as a CPU, a GPU or the like, a main memory device such as a RAM, a ROM or the like, and an auxiliary storage device such as an EPROM, a hard disk drive, a removable medium or the like. Here, note that the removable medium may be, for example, a USB memory or a disk recording medium such as a CD, a DVD, etc. An operating system (OS), various kinds of programs, various kinds of tables, etc., are stored in the auxiliary storage device, so that individual functions corresponding to predetermined purposes, respectively, which will be described later, can be achieved by loading the programs thus stored in the auxiliary storage device to a working area of the main memory device, executing them, and controlling the individual component units through the execution of the programs. However, a part or all of the functions may be achieved by a hardware circuit (s) such as an ASIC, an FPGA, or the like. Here, note that the server device20may be composed of a single computer, or may be composed of a plurality of computers that cooperate with one another. The communication unit201is a communication interface for connecting the server device20to the network. The communication unit201is composed of including a network interface board and/or a radio (wireless) communication circuit for radio (wireless) communication, for example. The storage unit202is composed including a main memory device and an auxiliary storage device. The main memory device is a memory in which control programs to be executed by the control unit203and data to be utilized by the control programs are developed. The auxiliary storage device is a device in which the programs to be executed in the control unit203and the data to be utilized by the control programs are stored. The main memory device and the auxiliary storage device of the storage unit202are the same as those in the storage unit102, so a detailed explanation thereof is omitted. Further, the storage unit202is composed of including an image database202A and a partition table data base202B. The image database202A is a database that stores image data collected from the vehicle10. The partition table data base202B is a database that stores a master partition table for creating partial partition tables to be distributed to the vehicle10. These databases are built by a program(s) of a database management system (DBMS) that is executed by the processor so as to manage the data stored in the storage devices. The databases used in this embodiment are relational databases, for example. The control unit203is an arithmetic unit that manages the control performed by the server device20. The control unit203can be achieved by an operation processing unit such as a CPU. The control unit203is composed of including two functional modules of an image management unit2031and a partition table management unit2032. Each of these functional modules may be achieved by executing programs stored in the auxiliary storage unit by the CPU. The image management unit2031collects image data from a plurality of vehicles10, and manages them using the image database202A. Based on the master partition table stored in the partition table data base202B, the partition table management unit2032creates and transmits partial partition tables to be distributed to the plurality of vehicles10. The specific processing thereof will be described later. Now, reference will be made to the outline of the processing in which the vehicle10collects image data. During traveling, the vehicle10(the data management unit1012) obtains image data through the vehicle-mounted camera in a periodic manner, and adds them to an obtained buffer in the storage unit102in a sequential manner. In this case, the data management unit1012associates an identifier for identifying a segment (hereinafter, a segment ID), an identifier for specifying a mesh in the segment (hereinafter, a mesh ID), and a data obtaining time point, with each piece of the image data. The segment ID and the mesh ID may be specified based on the data obtained beforehand from the server device20. For example, at the timing of receiving a partial partition table, a segment ID and data on meshes (the position, ID, etc., of each mesh) corresponding to the partial partition table may be obtained. The image data added to the obtained buffer are moved to the image storage in the storage unit102in a sequential manner. In this case, in cases where there is no space in the image storage, the image data therein may be organized or disposed according to a predetermined rule (e.g., deleted from older data, or deleted from less rare data, or the like). Next, reference will be made to the processing to be performed by a vehicle10and the server device20, while referring toFIG.5. This processing is divided into one processing in which the server device20transmits a partial partition table to the vehicle10, and another processing in which the vehicle10transmits image data stored in the image storage to the server device20based on the partial partition table thus received. The processing illustrated inFIG.5may be carried out at a predetermined interval, or may be carried out each time a predetermined event occurs, while the vehicle10is traveling. For example, it may be carried out each time the ignition of the vehicle10is turned on. Here, it is assumed that during traveling, the vehicle10obtains image data in a periodic manner, and stores them in the image storage by the data management unit1012. A segment ID and a mesh ID are associated with each piece of the image data stored, as mentioned above. First, at step S11, the vehicle10(the partial partition table obtaining unit1011) transmits a request for requesting a partial partition table to the server device20(the partition table management unit2032). This request includes a segment ID indicating a segment (hereinafter, a requested segment) for which the partial partition table is requested. The requested segment can be decided based on the position information of the vehicle10or a scheduled travel route thereof, for example. The requested segment may be a segment in which the vehicle10exists, or may be a set of segments which can be reached by the vehicle10within a predetermined period of time. The segment ID may be specified based on the data obtained beforehand from the server device20, as mentioned above. For example, a function or the like of converting latitude and longitude into a hash value or an address assigned in the master partition table may be obtained in advance and used. Subsequently, at step S12, the server device20(the partition table management unit2032) extracts from the master partition table a range (segment(s)) to be transmitted to the vehicle10based on the segment ID of the received requested segment, and creates a partial partition table. A necessity flag for each mesh is associated with the partial partition table, as illustrated inFIG.3A. It is preferable that the partial partition table to be transmitted to the vehicle10include only those segments to which the vehicle10can reach in a predetermined period of time (e.g., until the next update timing of the partial partition table). Such a range can be estimated based on the position information of the vehicle10or the scheduled travel route thereof, for example. Then, the server device20(the partition table management unit2032) transmits the created partial partition table to the vehicle10. In this step, the partial partition table is handled as an binary image, and the partial partition table is compressed by a well-known image compression method. As a method of compressing the binary image, there can be utilized ITU-T Rec.T. 6, for example, which is a data compression method for facsimile (G3), but methods other than this can also be used as long as they are data compression methods optimized for binary images. The partial partition table transmitted to the vehicle10is stored in the storage unit102(step S13). In this case, in cases where the partial partition table corresponding to the same segment is already stored, it is overwritten. Thereafter, by referring to one or more partial partition tables already stored, the transmission management unit1013determines whether image data obtained in a mesh for which data transmission is requested (i.e., a true value is set to a necessity flag thereof) has been stored (step S14). Here, in cases where an affirmative determination is made, then at step S15, corresponding image data is transmitted to the server device20(the image management unit2031). In cases where there exists no image data to be transmitted, processing returns to step S11. At step S15, the server device20stores the transmitted image data in the image database202A. In addition, it is determined whether a predetermined number of image data (the number of image data that should be collected by the server device20) have been collected for each mesh, and in cases where it is determined that the predetermined number of image data have been collected, the partition table management unit2032updates the master partition table. That is, a false value is set to a necessity flag for each corresponding mesh. Here, note that in this example, the update processing of the partial partition table and the transmission processing of the image data have been performed in succession, but the respective processings may be carried out at different timings. As described above, according to the first embodiment, in the system in which the vehicle10collects image data and transmits them to the server device20, a map indicating the necessity for transmission of the image data is transmitted to the vehicle, and the vehicle performs the transmission judgement (determination) of the image data based on the map. In particular, the necessity for transmission of the image data is represented by a binary value, so a high compressibility can be obtained. In addition, a target area is divided into segments, and only a necessary map is transmitted, so an amount of data can be reduced. Second Embodiment A second embodiment is an embodiment in which a version number is given to each partial partition table that is created and transmitted by the server device20, and the version management of each partial partition table stored in the vehicle10is performed. In the second embodiment, the partition table management unit2032does not update a master partition table stored in the partition table data base202B in real time, but performs write-ahead logging. Specifically, in cases where an update to the master partition table occurs, the content of the update is recorded in a log entry, and at the timing at which the number of log entries (i.e., the number of updates) has reached a fixed number, the log entries are reflected on the database.FIG.6Ais a view explaining the update sequence of a log. A different log entry is used for each segment.FIG.6Bis an example of log entries. A log entry is data that includes an LSN (Log Sequence Number, i.e., a version number), a mesh ID, and a necessity flag. The LSN is an integer value which is monotonously incremented each time an update occurs in a target segment. In cases where n segments are included in the master partition table (i.e., in cases where n partial partition tables exist), n LSNs exist. When the number of log entries (updates) exceeds a predetermined value in a certain segment, reflection processing (checkpoint) to the database is carried out, so that the data generated before the checkpoint will be deleted from the log entry. In the example ofFIG.6A, only a log entry is updated until the LSN reaches112, and a checkpoint (reflection to the database) occurs at a timing at which the LSN has become113. In the second embodiment, a partial partition table and an LSN are transmitted and received in a state where they are associated with each other. For example, when the server device20transmits a partial partition table to the vehicle10at step S12, the corresponding latest LSN is attached to the partial partition table. When storing the partial partition table, the vehicle10stores an LSN associated therewith at the same time.FIG.7is a schematic diagram illustrating a plurality of partial partition tables stored in the vehicle10and LSNs which are associated with the individual partial partition tables, respectively. Here, note that the plurality of partial partition tables are transmitted and received at different timings, and hence, as illustrated, the LSNs associated with the partial partition tables, respectively, become different numerical values. FIG.8is a flowchart illustrating, in detail, processing (i.e., processing carried out at step S11) in which the vehicle10requests a partial partition table to the server device20, in the second embodiment. First, at step S111, it is determined whether the vehicle10has a partial partition table corresponding to a requested segment. In cases where an affirmative determination is made here, processing shifts to step S112, and a target segment ID and an LSN associated with the segment are transmitted to the server device20. On the other hand, in cases where a negative determination is made, processing shifts to step S113, and only a segment ID is transmitted to the server device20, as in the first embodiment. FIG.9is a flowchart illustrating, in detail, processing (i.e., processing carried out at step S12) in which the server device20creates a partial partition table and transmits it to the vehicle10, in the second embodiment. First, at step S121, it is determined whether an LSN has been transmitted together with the ID of the requested segment from the vehicle10. Here, in cases where no LSN has been transmitted, processing shifts to step S122, where the latest partial partition table and a corresponding LSN are transmitted. In cases where the LSN is transmitted together with the ID of the requested segment, processing shifts to step S123A, where a comparison is made between the LSN at the time of the occurrence of the latest checkpoint and the received LSN. Here, in cases where the received LSN is smaller than the LSN at the latest checkpoint (YES at step S123A), it means that what is stored in the database is newer than the partial partition table held by the vehicle10, so processing shifts to step S122, where the latest partial partition table and a corresponding LSN are transmitted. In cases where the received LSN is larger than the LSN at the latest checkpoint (YES at step S123B), it means that what is stored in the database is older than the partial partition table held by the vehicle10. This means that there exists an update which has not yet been reflected in the database. In this case, processing shifts to step S124, where a log entry and an LSN corresponding to the partial partition table are transmitted. In cases where not the partial partition table itself but the log entry is transmitted to the vehicle10, then at step S13(FIG.5), the vehicle10updates the stored partial partition table based on the log entry. In cases where the values of both the LSNs are the same, processing shifts to step S125, where a message to the effect that there is no necessity for update is transmitted to the vehicle10. As described above, in the second embodiment, the version of each partial partition table stored in the vehicle10is managed by a numerical value indicating the version. According to such an embodiment, data update processing can be performed only in cases where a partial partition table stored in the vehicle10has become old, so unnecessary communication and processing can be reduced. (Modification) The above-mentioned embodiments are only some examples, and the present disclosure can be implemented while being changed or modified suitably without departing from the spirit and scope of the disclosure. For example, in the second embodiment, there has been mentioned the example in which only an LSN is attached to a partial partition table, but information other than this may be attached to a partial partition table. For example, information indicating the necessity of a pretreatment and/or the quality of compression (mode information) may be attached, so that the vehicle10may carry out processing according to the mode information thus attached. Here, note that the mode information and the necessity flag may be put together. That is, the necessity flag is not a binary value, but may be an integer value, so that the integer value may be utilized as the mode information. In addition, in the explanation of the above embodiments, each segment is divided into meshes in terms of geographical areas, but it may be further divided into highways and local streets, grade separations and side roads, or the like according to layers. In this case, based on the travel state of the vehicle, it may be specified to which layer a subject (own) vehicle belongs. Moreover, in the second embodiment, when a partial partition table is updated, an LSN is transmitted from the vehicle10to the server device20, but the transmission of the LSN may be performed at a timing at which image data is transmitted. According to such a configuration, it becomes possible for the server device20to quickly grasp that the received image data has been transmitted based on which version of the partial partition table. Here, note that the processings, units and devices explained in this disclosure can be implemented in various combinations thereof, as long as technical inconsistency does not occur. Moreover, the processing(s) explained as carried out by a single device may be carried out by a plurality of devices. Alternatively, the processing(s) explained as carried out by different devices may be carried out by a single device. In a computer system, whether each function of the disclosure is achieved by what kind of hardware configuration (server configuration) can be changed in a flexible manner. The present disclosure can also be achieved by supplying a computer program to a computer which implements the functions explained in the above-mentioned embodiments, and by reading out and executing the program by means of one or more processors of the computer. Such a computer program may be supplied to the computer by a non-transitory computer readable storage medium which can be connected with a system bus of the computer, or may be supplied to the computer through a network. The non-transitory computer readable storage medium includes, for example, any type of disk such as a magnetic disk (e.g., a floppy (registered trademark) disk, a hard disk drive (HDD), etc.), an optical disk (e.g., a CD-ROM, a DVD disk, a Blu-ray disk, etc.) or the like, a read-only memory (ROM), a random-access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, any type of medium suitable for storing electronic commands. | 35,151 |
11943688 | DETAILED DESCRIPTION The present disclosure may be understood more readily by reference to the following detailed description of the disclosure taken in connection with the accompanying drawing figures, which form a part of this disclosure. It is to be understood that this disclosure is not limited to the specific devices, methods, conditions or parameters described and/or shown herein, and that the terminology used herein is for the purpose of describing particular embodiments by way of example only and is not intended to be limiting of the claimed disclosure. Also, as used in the specification and including the appended claims, the singular forms “a,” “an,” and “the” include the plural, and reference to a particular numerical value includes at least that particular value, unless the context clearly dictates otherwise. Ranges may be expressed herein as from “about” or “approximately” one particular value and/or to “about” or “approximately” another particular value. When such a range is expressed, another embodiment includes from the one particular value and/or to the other particular value. The phrases “at least one”, “one or more”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together. FIG.1is a view illustrating a synchronization among a master node10and slave nodes20-1to20-N according to an embodiment of the present disclosure. Here, N is an integer equal to or more than one. The slave nodes20-1to20-N are synchronized to the master node10. Further, the nodes10and20-1to20-N are located in the same emergency vehicle (EV), or are located over different multiple EVs. The case where the nodes10and20-1to20-N are located in the same EV can be understood to mean a “synchronization between nodes in the same EV”. In this case, the master node10may include a main controller with one or more processor (not shown) and the slave nodes20-1to20-N may be peripheral devices (or peripherals) such as an emergency sound generation node (e.g., siren), an emergency light generation node (e.g., light bar), an I/O device, or the like. In this case, each of the nodes20-1to20-N is in communication with the master node10over e.g., a CAN bus network, so that synchronization messages each containing a timestamp are exchanged. For example, a modified CANOpen stack protocol, i.e., WeCANX, can be used to transmit the synchronization messages from the master node10to each of the slave nodes20-1to20-N for every predetermined time period (e.g., 1 second). However, embodiments of the present disclosure are not limited thereto; for example, any other point-to-point or multidrop communication schemes running a multitude of protocols can also be used for transmitting the synchronization messages. An internal timer (not shown) of the master node10generates a global time to which a local timer (not shown) of each slave node20-1to20-N is synchronized. In some embodiments, the global time can be provided with an accuracy of ˜100 nsec from an external global time source. The global time source may include a satellite based time source (150ofFIG.3A) such as a global navigation satellite system (GNSS), a global position system (GPS), or the like. In another embodiment, the global time can be provided using existing communication networks such as wireless cellular networks. For example, the GNSS transmitter transmits a global timestamp over a universal asynchronous receiver/transmitter (UART) signal (e.g.,3200ofFIG.3B) and a corresponding pulse-per-second (PPS) signal (e.g.,3100ofFIG.3B) to the master node10and/or each of the slave nodes20-1to20-N. In addition, the case where the nodes10and20-1to20-N are located over different EVs can be understood to mean a “synchronization between nodes in different EVs”. In this case, the master node10may correspond to a global time source, and the slave nodes20-1to20-N may correspond to peripherals located over different EVs. In the present disclosure, the term “node(s)” may mean a (network) device including a processor, memory, a communication module, an internal timer, and/or the like, and in some scenarios, the node(s) may be used interchangeably with the term “peripheral(s) except the case where a master node is described as a global time source, or a certain node may be understood as including a peripheral. The present disclosure will be described to address two technical issues as follows: (a) Synchronization between nodes located in the same EV; (b) Synchronization between nodes located in different EVs; and Synchronization Between Nodes Located in the Same EV In this section, a method or system for controlling time synchronization between nodes located in the same EV are described. FIG.2Ais a block diagram illustrating an example synchronization system according to an embodiment of the present disclosure.FIG.2Bis a view illustrating an example output sequence for generating a tone signal according to an embodiment of the present disclosure. InFIG.2A, the main controller210may include a processor (not shown), a memory (not shown) coupled to the processor, a communication device (not shown), and an optional master timer2100. Further, each peripheral such as an emergency sound generation node220(e.g., siren), an emergency light generation node230(e.g., a light bar), an10device240, or the like, may include a processor (not shown), a memory (not shown) coupled to the processor, a communication device (not shown), and a local timer2200. In some embodiments, the master timer2100which provides a global time used for the synchronization may not be a part of the master node10, instead the global time may be obtained using an external time source such as the satellite based time source. In one embodiment, the main controller210can be a microcontroller, a compact integrated circuit including a processor, memory and I/O devices on a single chip. While it is illustrated inFIG.2Athat each node has its own processor and memory for the sake of description, embodiments of the present disclosure are not limited thereto. For example, there may be a processor (not shown) and a memory (not shown), each of which is shared to control or perform processing jobs associated with each node210to240. Referring still toFIG.2A, the main controller210obtains a global time from either the master timer implemented therein or an external time source. The main controller210generates a first synchronization message and transmits the same to each peripheral220to240. Next, using the master timer2100, the main controller210determines a tx time at which the first synchronization message is transmitted and stores a tx timestamp corresponding to the determined tx time into the memory; for example, when a transmission interrupt signal, which is triggered upon transmission of the first synchronization message, is detected, the tx timestamp may be determined. Next, each peripheral220to240(e.g., processor thereof) receives the first synchronization message from the main controller210, determines a rx time (using the local timer2200) at which the first synchronization message is received and store a rx timestamp corresponding to the rx time into the memory; for example, when a reception interrupt signal, which triggered upon reception of the first synchronization message, is detected, the rx timestamp may be determined. After a predetermined period of time (e.g., Tp), the main controller210reads the tx timestamp from the memory, generates a second synchronization message containing the tx timestamp, and transmits the same to each peripheral220to240. Next, each peripheral220to240receives the second synchronization message and retrieves the tx timestamp from the received second synchronization message. Also, each peripheral220to240determines a current local time at which the second synchronization message is received. Next, each peripheral220to240compares the tx timestamp contained in the second synchronization message with the rx timestamp to determine a time difference ΔT between the tx timestamp and the rx timestamp. In addition, each peripheral220to240determines a global time by adding the time difference ΔT to the determined current local time, so that a local time of each peripheral220to240can be synchronized to the global time of the main controller210using the following equation: Global Time=Current Local Time+(txtimestamp−rxtimestamp) Equation 1, These two events regarding the tx timestamp and the rx timestamp determined and stored from a transmit side (e.g., main controller) and a receive side (e.g., each peripheral) both correspond to the same transmission which happened at one instance in time. Given that the main controller and the peripherals are located in the same EV, a delay, during the synchronization messages being transmitted, may be negligible, so that the only difference between the tx timestamp and rx timestamp can be contributed to a synchronization variance therebetween. The synchronization made based on Equation 1 may immediately bring the main controller210and each peripheral220to240to be synchronized within, e.g., 1 μsec. Even if the main controller210and each peripheral220to240are synchronized based on Equation 1, a further synchronization error may occur until the next round of synchronization due to inconsistent drifts between the master timer2100and the local timer2200which are caused by external factors such as temperature. This additional synchronization error occurs over the course of the next predetermined time period Tpwhere the local timer2200of each peripheral220to240may drift from the master timer2100of the main controller210due to differences in rate that their timers increment. The predetermined time period Tpis a period for which synchronization messages are transmitted and thus, the synchronization between nodes are performed. The maximum drift that can occur is equal to the maximum difference in the rate which the timers increment. For example, the drift can vary by up to 2% of the predetermined time period Tpwhich would result in a maximum of, e.g., 2 msec drift when Tp=1 sec, between the master timer and the local timer over the course of the predetermined time period Tp. The accuracy of the timers can be improved using external crystals up to 0.01% of the predetermined time period Tp. In this case, the maximum drift will be, e.g., 10 μsec when Tp=1 sec. Alternatively, a reload time of the internal timer (e.g., 80-microsecond timer) of the node can be reduced or increased to allow that node to catch up to or slow down and track the global time of the main node. For example, if each node is behind the global time of the main node by a predetermined time (e.g., a few milliseconds box), the reload time of the timer of that node can be reduced for the node to catch itself up smoothly by running the threads in the real-time operating system (RTOS) more often. Further, this can further be enhanced using a proportional-integral-derivative (PID) controller to catch up more quickly or slowly based on whether a local time of the node is far or close to the global time accordingly. In one embodiment, referring toFIG.2A, each peripheral220to240may further include a proportional-integral-derivative (PID) controller2300which acts to reduce the synchronization error occurring due to the drifts between the master and local timers2100and2200and eliminate the time jump in slave nodes upon the reception of synchronization messages. The PID controller2300is configured to compensate for the drift between the master and local timers2100and2200using Equation 2. The PID controller2300can be implemented using a hardware processor or based on a field-programmable gate array (FPGA) design, but in other embodiments, it may be implemented based on program codes which are stored in the memory or in the hardware processor, and executed by the hardware processor. u(t)=Kpe(t)+Ki∫0te(t′)dt′+Kdde(t)dt,Equation2 where u(t) is equal to the adjustment amount to a reload value of the local timer2200in each peripheral220to240. Kp, Ki, and Kdare all constants which are tuned in firmware to smooth out the drift between the master and local timers2100and2200over the predetermined period of time Tp. e(t) represents a time difference between the tx timestamp and the rx timestamp. In Equation 2, Kpacts as an immediate addition or subtraction of time to the local timer2200based on e(t) which is the difference between the local and master node, so that the timer2200can slow down or speed up to let it catch up with the master timer2100. Kiis multiplied by an accumulated error in drifts and is used to correct a small error that occurs over time where the local timer2200is running at the same rate as the master timer2100, but is just slightly ahead of or behind the master timer2100in time. Next, Kdis multiplied by the change in drifts between the last two calculated errors in order to resist the change of the element Kpe(t) of Equation 2 as the timers get closer and closer together to prevent overshoot, and the element Kdde(t)dt decreases as the local timer2200is altered to have the drift from the master timer2100to be zero. After tuning the rate of the local timer2200, the drift error will appear sinusoidal remaining centered around zero in drift as the local timer2200couples tightly to the master timer2100, as shown inFIG.2C. FIG.6is a view illustrating an example algorithm to be performed for synchronization according to another embodiment of the present disclosure. This embodiment is preferred for sirens to prevent audible jumps in tones, but is also applicable to other components requiring synchronization, e.g., lights. The PID controller can be further enhanced by allowing it to self-tune itself in real time rather than using stored PID values as well as preset maximums and minimums. This allows a single PID controller to be used across multiple devices in varying temperature ranges regardless of the accuracy of each devices clock source due to using an external or internal crystal etc. This is also disclosed in related U.S. application Ser. No. 16/815,988, filed Mar. 11, 2020, the entire contents of which are incorporated herein by reference. When syncing using a PID controller as opposed to just instantaneously jumping to a new timestamp using the method already specified above, three consecutive sync messages601/602/603are required as opposed to two (i.e.,601/602). This is due to the need for the PID controller to be tuned before use allowing for the same PID controller with different numbers to be used across varying temperature ranges and varying drifts between the main and external node. The first two sync messages and the processes performed are the same as those described using the instantaneous jump method. That is, the global time tg is calculated using two synch messages601/602, i.e., Global Time=Current Local Time+(tx timestamp−rx timestamp). Once this difference is added to the internal clock in node and the two devices10/20are in theory perfectly synced for that instance in time, slow drift is still occurring from the main node20based on the difference in running rates between the oscillators on the two nodes10/20. To prevent the need for further jumps, which is more perceptible in a siren jump, this variance in running rates must be eliminated which is where the PID controller is utilized. One more message is therefore needed in order to see the difference of how far the slave node was from the main node in time initially as compared to how far it is from the main nodes clock one sync message later. The main node20transmits a third sync message603to the node10. The third sync message603includes a third transmit time t3at which the main node20transmit completed for sync the previous sync message, i.e.,602. The third synch message603is received at the local node10and the receive time tr3is recorded. For example, if the time difference was initially 50 ms and it is now 55 ms one sync message later, this indicates that drift is occurring at a rate of 5 ms. The PID controller is not necessarily meant to eliminate the 55 ms difference, but adjust for the continuous 5 ms drift which is occurring after the jump. Thus, the P, I, and D values can be tuned based on a percentage of this drift and also set to slow down or speed up the clock in the local node to bring the devices into synchronization without an abrupt jump. In addition, a maximum allowable drift can be calculated as a percentage of this drift, which, if exceed, will trigger the need for a new jump and thereafter a new tuning will be needed in order to allow the PID controller the ability to compensate for the new drift, which is often caused by temperature variations or some other external factor. The PID controller and the values used for tuning can then be used to alter the auto reload register time of that clock in the local node as to what constitutes 1 ms for instance and speed it up or slow it down so that its 1 ms now happens at a slightly different rate as measured by external devices; but, the internal tasks to the local node still treat this time as if 1 ms has occurred slowing down or speeding up there tasks in real time to compensate. Thus, the PID controller2300allows for tuning the rate that the local timer2200increments by actively adjusting the reload value of its clock based on Equation 2. Among the peripherals220to240, the emergency sound generation node220generates an emergency sound based on an output sequence2000stored in a memory, as exemplary shown inFIG.2B. The output sequence is a sequence upon which the emergency sound generation node220is supposed to play the emergency sound. More particularly, a processor (not shown) of the emergency sound generation node220reads the output sequence2000from a memory (not shown) and generates a tone signal based on the output sequence2000. The tone signal may be amplified and played through a speaker (not shown). In this case, the tone signal may include volume level information and/or frequency information. In some embodiments, in case of the peripherals220to240includes another emergency sound generation node (not shown), the another emergency sound generation node can also be synchronized to the main controller210and thus, synchronized to the emergency sound generation node220. The another emergency sound generation node may also generate another tone signal based on another output sequence, and the another tone signal generated by the another emergency sound generation node can be synchronized to the tone signal generated by the emergency sound generation node220to generate a combined emergency sound, which make the sound more noticeable to drivers. The output sequence2000is repeated for every predetermined time period which, for example, is equal to the predetermined time period Tpfor which the synchronization messages are sent and the synchronizations are performed. A length of the output sequence2000is equal to that of the another output sequence. Examples of the output sequences, the tone signals and example embodiments as to how an emergency sound or a combined emergency sound is generated based on the synchronized global time are also described in Applicant's Provisional Application No. 62/816,958 filed on Mar. 12, 2019, the entire disclosure of which is incorporated by reference herein. In some embodiments, the emergency sound generation node220generates a tone signal based on the output sequence2000to generate an emergency sound, and a processor (not shown) of the emergency light generation node230generates another tone signal based on another output sequence (not shown) to generate an emergency flash light. In this case, the emergency light generation node230can also be synchronized to the main controller210and thus, synchronized to the emergency sound generation node220. The processor of the emergency light generation node230may also generate another tone signal based on another output sequence, and thus the another tone signal generated by the emergency light generation node230can be synchronized to the tone signal generated by the emergency sound generation node220to respectively generate an emergency flash light and an emergency sound which are played in a synchronization manner, which make the light and the sound more noticeable to drivers. The another tone signal generated by the emergency light generation node230may be amplified and played through a light bar (not shown). In this case, the another tone signal may include light intensity level information and/or frequency information. The aforementioned synchronization methods allow the system to resync the tone signals globally between the emergency sound generation nodes and/or the emergency light generation node to play that same pattern in the same phase, making them more noticeable to drivers. Synchronization Between Nodes Located Over Different Emergency Vehicles In this section, a method or system for controlling synchronization between nodes located over different EVs are described. FIG.3Ais a block diagram illustrating an example synchronization system according to an embodiment of the present disclosure.FIG.3Bis a view illustrating an example timing diagram of signals transmitted by a global time source and each emergency vehicle according to an embodiment of the present disclosure. Referring toFIG.3A, two different EVs200aand200bare illustrated only for the sake of simplicity. In the present disclosure, the number of EVs to be synchronized is not limited thereto. Similar to the EV200ofFIG.2A, each of the EVs200aand200bincludes one or more nodes (or peripherals) such as a main controller, an emergency sound generation node, an emergency light generation node, an I/O device, or the like and thus, duplicate description thereof will be omitted for the sake of simplicity. In this scenario, a node(s) of the EV200aand a node(s) of the EV200bis(are) synchronized to the global time source150, so that the node(s) of the EV200aand the node(s) of the EV200bis(are) all synchronized one to another, which allows for generating more noticeable emergency sound and/or light, as described in the previous section. In one embodiment, referring still toFIG.3A, the global time source can be a GNSS transmitter150. In this case, a GNSS receiver250for receiving signals from the GNSS transmitter150can be attached or included in each EV200aand200b, more particularly, e.g., a main controller. Referring further toFIG.3B, the GNSS transmitter150transmits a PPS signal3100as well as an UART signal3200containing a timestamp tPP Scorresponding to a transmission of the PPS signal3100(e.g., rising edge of the PPS signal) with an accuracy of 100 nsec to the main controller of each EV via the GNSS receiver250. In case of the global time source is implemented with any one other than the GNSS, the GNSS transmitter150and the GNSS receiver250can be replaced accordingly to transmit/receive corresponding signals. Referring toFIG.3B, illustrated are example timing diagrams of the UART signal3200and the PPS signal3100which show only a specific period for the sake of simplicity, but will be repeated periodically. For example, as shown inFIG.3B, at the GNSS transmitter150, the PPS signal3100has a rising peak at a first time tPPS, and the UART signal3200containing the timestamp which corresponds to the rising peak of the PPS signal3100is generated. After then, the PPS signal3100and the UART signal3200are transmitted. Upon the transmission of the PPS signal3100, a processor (not shown) of the GNSS transmitter150determines the first time tPPScorresponding to the rising edge of the PPS signal3100, and then transmits the UART signal3200containing the timestamp of the first time tPPSas a synchronization message. Each EV200aand200bincludes an internal timer (or input compare timer) (not shown) in the main controller (e.g.,210aor210b) or connected thereto. When the main controller receives the PPS signal3100, the internal timer is triggered upon the rising edge of the received PPS signal3100and stores a timestamp tLC_PPSof the internal timer into a memory. Next, when the main controller receives the UART signal3200, a current local time tCURRENT_LOCALof the internal timer upon the reception of the UART signal3200is determined and stored, and the timestamp tPPScontained in the UART signal3200is read and stored. Next, the main controller determines a global time by adding a time difference between the current local time tCURRENT_LOCALand the stored timestamp tLC_PPSto the determined timestamp tPPS, as shown with Equation 3, so that a local time of the main controller can be synchronized to the global time provided by the global time source150. Global Time=tPPS+(tCURRENT_LOCAL−tLC_PPS) Equation 3. Similar to what is described in the previous section, the UART signals3200are transmitted to each EV200aand200bevery a predetermined period (e.g., Tp), there will occur some drifts of the internal timer of each EV200aand200bwith respect to the global time source150over the course of the next predetermined time period. Because the global timer of the GNSS transmitter150has a max variance of 100 nsec, a difference between a time at which the PPS signal is transmitted and the corresponding timestamp (e.g., tPPS) contained in the UART signal3200may be relatively negligible with respect to the accuracy of the global time source and can thus be ignored. On the other hand, the internal timer of each EV200aand200bhas a relatively large variance (e.g., 1% of the predetermined time period Tp(e.g., 1 msec when Tp=1 sec) over the course of the next predetermined time for which the UART signals3200are transmitted. In one embodiment, this variance of the internal timer at each EV200aand200bcan be reduced to, e.g., approximately 0.005% of the predetermined time period Tp(or 5 μsec when Tp=1 sec) if an external oscillator is used for the internal timer. Similar to what is described in the previous section, the main controller may further include a PID controller (not shown) which acts to reduce the synchronization error occurring due to the drifts between the global time source150and the internal timer. Thus, duplicate of description will be omitted for the sake of simplicity. Although it is illustrated inFIG.3Athat the global time source150such as the satellite based time source is used for synchronization between vehicles. However, embodiments of the present disclosure are not limited thereto. For example, a precision time protocol demon (PTPd) stack as specified in IEEE 1588 can be used to establish any node(s) as a master node and leave it up to the peripherals to determine the most accurate source for synchronizing them. This leaves the instant synchronization method disclosed herein expandable in the future and free of and architectural requirements. Although currently all of systems using exclusively CAN to communicate between peripherals are limited to only one master, architectures more commonly seen in Ethernet applications containing multiple masters and a switch could also be used to synchronize devices in the future if higher data rates are required. The method for synchronization would still be the same regardless of communication scheme. The minimum parts needed to achieve synchronization using this method are two microcontrollers connected by a data line where the transmission and reception time of messages is determinant. To synchronize between vehicles there is needed a further addition of a global time source on the side of one of the microcontrollers. In one embodiment, once a corresponding main controller of each of the EV200aand200bis synchronized to the global time source150, peripherals in each EV200aand200bwill be synchronized to the main controller. In this case, the main controller210a(or210b) of each EV200aand200bofFIG.3Amay correspond to the main controller210ofFIG.2A, and the peripherals220ato240a(or220bto240b) of each EV200aand200bmay correspond to the peripherals210to240ofFIG.2A. Thus, for synchronization between the peripherals210ato240a(or the peripherals210bto240b), similar methods described with reference toFIG.2Acan be applied to the instant embodiment with reference toFIG.3A. Thus, duplicate description thereof will be omitted for the sake of simplicity. Further, it should be noted that once the peripherals210ato240aare synchronized in the EV200a, and the peripherals210bto240bare synchronized in the EV200b, it can be understood that the peripherals210ato240aof the EV200aand the peripherals210bto240bof the EV200bare all synchronized one to another. In addition, in order to make an emergency sound and/or an emergency light more noticeable, any combinations of the peripherals210ato240aand210bto240bcan be applied. For example, an emergency sound generation node220aof the EV200acan be synchronized to an emergency sound generation node220bof the EV200bto generate a combined emergency sound where their corresponding tone signals are synchronized each other to generate the same pattern of the emergency sound, similarly what is described in the previous section with reference toFIG.2A. In a further example, an emergency sound generation node220aof the EV200acan be synchronized to an emergency light generation node230bof the EV200bto generate an emergency sound and an emergency light where their tone signals are synchronized each other to have the emergency sound and the emergency light the same pattern as each other, similarly what is described in the previous section with reference toFIG.2A. Hereinafter, examples of how peripherals (e.g.,220to240ofFIG.2A or220ato240a,220bto240bofFIG.3A) located in the same EV or over different EVs will work after they are synchronized to the global time. In one embodiment, in order to generate a tone signal based on an output sequence (e.g.,2000ofFIG.2B), each of the peripherals will find out a certain point within an output sequence at which their actions are performed. For example, each peripheral is configured to calculate a start point in the output sequence at which the tone signal shall start to be generated. This start point is referred to as a TimeIntoSequence which represents the tone signal shall start to be generated in the sequence cycle that simulates its repetitive pattern. TimeIntoSequence can be calculated using the following Equation: TimeIntoSequence=((DegreeOfPhase/360)×TotalSequenceTime)+CurrentGlobalTime Mod Total SequenceTime Equation 4, where DegreeOfPhase represent a phase in degree where the playback of the sequence would have been. TotalSequenceTime is a predetermined time period where the sequence exists. CurrentGlobalTime represents a current global time determined at each peripheral. TimeIntoSequence to be determined using Equation 4 will tell the system exactly a certain time point in the output sequence at which the tone signal has to start rendering the sequence and repeated continuously since then. Because the global time of zero is the same for all peripherals using the aforementioned synchronization methods, all peripherals synchronized in either the same EV or different EVs, will begin a sequence of the same period and phase exactly in synchronization with one another regardless of when the sequences begin. FIG.4is a view illustrating an example timing diagram for determining a TimeIntoSequence according to an embodiment of the present disclosure. For example, referring toFIG.4, the sequence period (e.g., TotalSequenceTime) repeats for every 1000 msec, the sequence is played at degreeOfPhase of 0, at the global time zero, and the global time is 2600 msec. In one embodiment, the peripherals may calculate a certain point at which they should start in a sequence for every predetermined time period Tp and/or jump to the appropriate output state for that time as defined by the sequence definition. More particularly, if the peripherals use an internal PID controller or PTPD, it may allow the peripherals to continue playing their sequences normally the same as they would in an asynchronous system since they would exactly know where they should start. Further, the local timer of each peripheral will be updated in the background to keep its output synchronous in the overall system. In addition, the aforementioned synchronization method can be used for Cencom™ Core sirens and implementing hardware to achieve absolute synchronization between tone signals. This is done as by playing a sequence internally in one siren and then outputting it via a mux to an Auxillary-out connector on that board. A next siren in the system can then select to play a sequence at its Auxillary-in connected to an output of its main amplifier which receives a tone provided from the previous siren as well as pass the sequence through to another siren in the system. This allows the tone to be produced only once and played synchronously on every siren in the connected system. Because some users will not want sequences starting in the middle of a sequence but to still have all peripherals in a system synchronized with one another. In this case, a further calculation can be done to figure out what phase, according to a global time stamp of zero, would the sequence have to start so as to start at the beginning immediately using Equation 4. Once this is done, it can be remembered so that any sequence in the future of the same period or a multiple or division of that period and phase can be started in the same phase to achieve in vehicle synchronization between peripherals in a system as well as start from the beginning of a sequence. In addition, there is an option to play the sequence immediately without doing any calculation to make every peripheral in the vehicle run sequences asynchronously. FIG.5is a block diagram of a computing system4000according to an exemplary embodiment of the present disclosure. Referring toFIG.5, the computing system4000may be used as a platform for performing: the functions or operations described hereinabove with respect to at least one of the systems ofFIGS.2A and3A. Referring toFIG.8, the computing system4000may include a processor4010, I/O devices4020, a memory system4030, a display device4040, and/or a network adaptor4050. The processor4010may drive the I/O devices4020, the memory system4030, the display device4040, and/or the network adaptor4050through a bus4060. The computing system4000may include a program module for performing: the functions or operations described hereinabove with respect to at least one of the systems ofFIGS.2A and3A. For example, the program module may include routines, programs, objects, components, logic, data structures, or the like, for performing particular tasks or implement particular abstract data types. The processor (e.g.,4010) of the computing system4000may execute instructions written in the program module to perform: the functions or operations described hereinabove with respect to at least one of the systems ofFIGS.2A and3A. The program module may be programmed into the integrated circuits of the processor (e.g.,4010). In an exemplary embodiment, the program module may be stored in the memory system (e.g.,4030) or in a remote computer system storage media. The computing system4000may include a variety of computing system readable media. Such media may be any available media that is accessible by the computer system (e.g.,4000), and it may include both volatile and non-volatile media, removable and non-removable media. The memory system (e.g.,4030) can include computer system readable media in the form of volatile memory, such as RAM and/or cache memory or others. The computer system (e.g.,4000) may further include other removable/non-removable, volatile/non-volatile computer system storage media. The computer system (e.g.,4000) may communicate with one or more devices using the network adapter (e.g.,4050). The network adapter may support wired communications based on Internet, local area network (LAN), wide area network (WAN), or the like, or wireless communications based on code division multiple access (CDMA), global system for mobile communication (GSM), wideband CDMA, CDMA-2000, time division multiple access (TDMA), long term evolution (LTE), wireless LAN, Bluetooth, Zig Bee, or the like. Exemplary embodiments of the present disclosure may include a system, a method, and/or a non-transitory computer readable storage medium. The non-transitory computer readable storage medium (e.g., the memory system4030) has computer readable program instructions thereon for causing a processor to carry out aspects of the present disclosure. The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EEPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, or the like, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire. Computer readable program instructions described herein can be downloaded to the computing system4000from the computer readable storage medium or to an external computer or external storage device via a network. The network may include copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card (e.g.,4050) or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the computing system. Computer readable program instructions for carrying out operations of the present disclosure may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the computing system (e.g.,4000) through any type of network, including a LAN or a WAN, or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In an exemplary embodiment, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure. Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, system (or device), and computer program products (or computer readable medium). It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions. These computer readable program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks. The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks. The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions. The corresponding structures, materials, acts, and equivalents of all means or step plus function elements, if any, in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description but is not intended to be exhaustive or limited to the present disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present disclosure. The embodiment was chosen and described in order to best explain the principles of the present disclosure and the practical application, and to enable others of ordinary skill in the art to understand the present disclosure for various embodiments with various modifications as are suited to the particular use contemplated. While the present invention has been particularly shown and described with respect to preferred embodiments thereof, it will be understood by those skilled in the art that the foregoing and other changes in forms and details may be made without departing from the spirit and scope of the present invention. It is therefore intended that the present invention not be limited to the exact forms and details described and illustrated but fall within the scope of the appended claims. | 45,173 |
11943689 | DESCRIPTION OF EMBODIMENTS The following describes the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. In the descriptions of this application, “/” indicates an “or” relationship between associated objects unless otherwise specified. For example, A/B may indicate A or B. The term “and/or” in this application indicates only an association relationship for describing associated objects and indicates that three relationships may exist. For example, A and/or B may indicate the following three cases: Only A exists, both A and B exist, and only B exists, where A and B may be singular or plural. In addition, in the descriptions of this application, “a plurality of” means two or more unless otherwise specified. “At least one item (piece) of the following” or a similar expression thereof refers to any combination of these items, including any combination of singular items (pieces) or plural items (pieces). For example, at least one item (piece) of a, b, or c may indicate: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural. In addition, to clearly describe the technical solutions in the embodiments of this application, in the embodiments of this application, terms such as “first” and “second” are used to distinguish between same objects or similar objects whose functions and purposes are basically the same. A person skilled in the art may understand that the terms such as “first” and “second” do not limit a quantity and an execution sequence, and the terms such as “first” and “second” do not indicate a definite difference. Before the solutions of this application are described, terms in this application are first explained.(1) A service intent is used to describe a service requirement of a terminal device. For example, the service intent may be used to describe a service requirement of an unmanned aerial vehicle from a location A to a location B, a video backhaul service requirement of the unmanned aerial vehicle in a flight process, and the like.(2) Network intent information is used to describe a network requirement, that is, an effect that needs to be achieved during network configuration. For example, if a current network does not support a service intent, a network intent may be generated to express a requirement on the network. An operation such as extending a network range or narrowing a network range may be included.(3) A network management device is configured to: provide and manage a network, provide a service, and manage the provided service.(4) A requirement device is a device that uses a network or a service. The requirement device may propose a service intent based on a service requirement of a terminal device, and describe, by using the service intent, a service used by the terminal device. For example, the requirement device provides a service for an unmanned aerial vehicle enterprise user, and the requirement device may send a service intent to an intent management device based on a service requirement of the unmanned aerial vehicle user, to provide the service for the unmanned aerial vehicle user.(5) An intent management device is configured to configure, based on an intent proposed by a requirement device, a network or a service used by the requirement device. The intent management device may alternatively request a network management device to configure a corresponding network. Alternatively, the intent management device may determine a network intent based on a service intent proposed by a requirement device, and transfer the network intent to a network management device, so that the network management device configures a corresponding network based on the network intent. It should be noted that the intent management device may be independently deployed from a network provider device, or may be deployed in a network provider device. This is not specifically limited in the embodiments of this application. It should be noted that the foregoing devices may be function units, may be chip systems, or other devices. This is not specifically limited in the embodiments of this application. An intent-based network configuration method provided in the embodiments of this application may be applied to an intent hierarchical framework shown inFIG.1. As shown inFIG.1, the intent hierarchical framework includes a requirement device, an intent management device, a network management device, and a network. An interface between the requirement device and the intent management device is mainly used by the intent management device to receive a service subscription request and a service intent that are sent by the requirement device. An interface between the intent management device and the network management device is mainly used by the network management device to receive a network management request or a network device management request sent by the intent management device, for example, to request the network management device to modify a network configuration, to request the network management device to activate a network device, and to request the network management device to manage a life cycle of the network device. The management of the life cycle of the network device by the network management device may be creating a virtual machine on the network device, deleting a virtual machine deployed on the network device, modifying a virtual machine deployed on the network device, or the like. It should be noted that the requirement device may be a communication service consumer (CSC), and may provide a communication service for a terminal device. For example, the requirement device may be a device on which a user operation system is deployed. For example, the requirement device may provide an operation support for an unmanned aerial vehicle user, and may propose a service intent based on a service requirement of the unmanned aerial vehicle user, to implement a service of the unmanned aerial vehicle user based on the service intent. The intent management device may be a communication service provider (CSP), may provide a communication service for the requirement device, and is responsible for operation of the communication service, including management of a life cycle of the communication service, and the like. The intent management device may further convert a corresponding communication service requirement into a network requirement. For example, after receiving a service intent of the requirement device, the service intent may be converted into a network intent. For example, the service intent transferred by the requirement device is: An unmanned aerial vehicle A uses a service “from a school B to a school C”, and if the intent management device determines that a network that can be used cannot satisfy a flight mission of the unmanned aerial vehicle A, a network intent “extending a range of the network that can be used by the intent management device” is transferred to the network management device. Alternatively, the service intent transferred by the requirement device is: An unmanned aerial vehicle A uses a service “from a school B to a school C”, the intent management device converts the service intent into a network intent “a network slice of unmanned aerial vehicle flight is enabled in an area A”, and sends the network intent to the network management device. The network management device may be a device of a network operator (NOP), provides a network, including a sliced network, a non-sliced network, and a non-public network, for the intent management device, and is mainly responsible for management of a life cycle of the network. The network device is managed by a network element provider (NEP). The NEP provides the network device for the NOP, and is also responsible for management of a life cycle of a sub-network, management of a life cycle of a network element, and the like. In a current technology, the intent management device may allocate a network resource to a service of the terminal device based on a service subscription request message. Once the network resource is allocated to a corresponding service, even if the terminal device does not have the corresponding service at some moments, the corresponding resource is reserved. As a result, a waste of network resources is caused. For example, a maximum quantity of users in the service subscription request message is 100, and the intent management device reserves network resources to support services of the 100 terminal devices. Actually, some of the terminal devices may not always have a service requirement, and the waste of network resources is caused. An embodiment of the present application provides an intent-based network configuration method. An intent management device receives a service intent sent by a requirement device. The service intent is used to indicate service requirement information, and the service requirement information includes service access time information of at least one terminal device and service access location information of the at least one terminal device. Further, the intent management device configures a corresponding network based on the service intent, or indicates the network management device to configure a corresponding network. In some embodiments of the present application, the intent management device may allocate a network resource to a service of the terminal device based on the service access time information and the service access location information in the service requirement information, and a user only needs to pay for the network resource in a service access time, thereby implementing a pay-per-use network resource scheduling mode. In addition, in a period other than the service access time, the network resource may be allocated to another service, so that the network resource is properly used and network resources are not wasted. It should be noted that the intent management device or the requirement device in some embodiments of the present application may be implemented by one device, or may be jointly implemented by a plurality of devices, or may be a function module in a device, or may be a chip in a device. This is not specifically limited in this embodiment of this application. It may be understood that the foregoing functions may be network elements in a hardware device, or may be software functions running on special-purpose hardware, or may be virtualization functions instantiated on a platform (for example, a cloud platform). For example, the intent management device or the requirement device in some embodiments of the present application may be implemented by using a communication apparatus20inFIG.2.FIG.2is a schematic diagram of a hardware structure of the communication apparatus20according to an embodiment of this application. The communication apparatus20includes a processor201, a communication line202, a memory203, and at least one communication interface (where descriptions are provided inFIG.2merely by using an example in which the communication apparatus20includes the communication interface204). The processor201may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits that are configured to control execution of a program in the solutions of this application. The communication line202may include a path for transmitting information between the foregoing components. The communication interface204uses any apparatus such as a transceiver, to communicate with another device or a communication network, for example, the Ethernet, a radio access network (RAN), or a wireless local area network (WLAN). The memory203may be a read-only memory (ROM) or another type of static storage device capable of storing static information and instructions, or a random access memory (RAM) or another type of dynamic storage device capable of storing information and instructions, or may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or another compact disc storage, optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile optical disc, a Blu-ray optical disc, or the like), a magnetic disk storage medium or another magnetic storage device, or any other medium capable of carrying or storing expected program code in a form of instructions or a data structure and capable of being accessed by a computer, but is not limited thereto. The memory may exist independently, and is connected to the processor through the communication line202. The memory may alternatively be integrated with the processor. The memory203is configured to store computer-executable instructions for executing the solutions of this application, and the processor201controls the execution. The processor201is configured to execute the computer-executable instructions stored in the memory203, to implement the intent-based network configuration method provided in the following embodiments of this application. Optionally, the computer-executable instructions in some embodiments of this application may also be referred to as application program code. This is not specifically limited in some embodiments of this application. During specific implementation, in an embodiment, the processor201may include one or more CPUs, for example, a CPU0and a CPU1inFIG.2. During specific implementation, in an embodiment, the communication apparatus20may include a plurality of processors, for example, the processor201and a processor207inFIG.2. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and/or processing cores configured to process data (for example, computer program instructions). During specific implementation, in an embodiment, the communication apparatus20may further include an output device205and an input device206. The output device205communicates with the processor201, and may display information in a plurality of manners. For example, the output device205may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector). The input device206communicates with the processor201, and may receive input from a user in a plurality of manners. For example, the input device206may be a mouse, a keyboard, a touchscreen device, or a sensing device. The foregoing communication apparatus20may be a general-purpose device or a special-purpose device. During specific implementation, the communication apparatus20may be a desktop computer, a portable computer, a network server, a palmtop computer (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device having a structure similar to that inFIG.2. A type of the communication apparatus20is not limited in this embodiment of this application. In a possible implementation, when the communication apparatus20is used as the intent management device in an embodiment of the present application, the processor201of the communication apparatus20runs or executes a software program and/or a module that are/is stored in the memory203, and invokes data stored in the memory203, to perform the following functions. The intent management device receives a service intent sent by a requirement device, where the service intent includes service requirement information such as service access time information and service access location information. The intent management device may determine network configuration information based on the service intent, and further, the intent management device may configure a network based on the network configuration information, to support a service of a terminal device. Alternatively, the intent management device may send network configuration information to a network management device, to indicate the network management device to configure a network based on the network configuration information. Certainly, the intent management device may further generate network intent information based on the service intent, and transfer the network intent information to the network management device, and the network management device may configure the network based on the network intent information. In a possible implementation, when the communication apparatus20is used as the requirement device in an embodiment of the present disclosure, the processor201runs or executes a software program and/or a module that are/is stored in the memory203, and invokes data stored in the memory203, to perform the following functions. The requirement device receives a service intent template sent by an intent management device, where the service intent template is used to indicate at least one of format information of a service intent and constraint information of the service intent. The format information of the service intent is used to indicate service requirement information supported by the service intent, and the constraint information of the service intent is used to indicate a range of the service requirement information supported by the service intent. The requirement device may further generate the service intent based on a service requirement of a terminal device and with reference to the intent template, and send the generated service intent to the intent management device, to allocate a network resource to a service of the terminal device. The following describes in detail the solutions provided in the embodiments of this application with reference to accompanying drawings. It should be noted that, in the following embodiments of this application, names of messages or names of parameters in messages between devices are merely examples, and the messages or the parameters may have other names in specific implementations. This is not specifically limited in the embodiments of this application. An embodiment of the present application provides an intent-based network configuration method. As shown inFIG.3, the method includes the following steps.301: A requirement device generates a service intent based on a service intent template. It should be noted that the service intent template is used to indicate at least one of format information of the service intent and constraint information of the service intent. The format information of the service intent is used to indicate service requirement information supported by the service intent. For example, the service requirement information indicated by the format information of the service intent may be service access time information, service access location information, service type information, tenant information, an identifier of a terminal device, a quantity of terminal devices, and a service intent priority. The following describes the service requirement information with reference to examples.(1) The service access time information is used to indicate duration of a service described in the service intent. In a possible implementation, the service access time information includes at least one of the following: service access start time information, service access end time information, a service access periodicity, and service access duration. For example, service access time information in a service intent template of an unmanned aerial vehicle service may be a start time of the unmanned aerial vehicle service, for example, 2019.4.1.13:00. The service access time information may alternatively be an end time of the unmanned aerial vehicle service, for example, 2019.4.1.16:00. The service access time information may alternatively be duration of the unmanned aerial vehicle service, for example, 4 hours. The service access time information may alternatively be an access periodicity of the unmanned aerial vehicle service, for example, a flight service is used every two hours.(2) The service access location information is used to indicate a geographical range related to the service described in the service intent. In a possible implementation, the service access location information includes at least one of longitude and latitude information and service access area information that are/is related to a service access path. The longitude and latitude information related to the service access path may constitute longitude and latitude information of each node of the service access path, or may be longitude and latitude information of a start point of the service access path and longitude and latitude information of an end point of the service access path. For example, a flight mission of the unmanned aerial vehicle service is from a school A to a school B, passing through building D. The longitude and latitude information related to the service access path may be longitude and latitude information of the school A, longitude and latitude information of the school B, and longitude and latitude information of the building D. The longitude and latitude information related to the service access path may alternatively be longitude and latitude information of the school A and longitude and latitude information of the school B. The service access area information is used to indicate an area related to a service of the terminal device. For example, if a flight mission of the unmanned aerial vehicle service is performed in Haidian District, Beijing, the service access area information may be used to indicate “Haidian District, Beijing”.(3) The service type information is used to indicate a type of the service described in the service intent. For example, the type of the service indicated by the service type information may be an unmanned aerial vehicle service, an augmented reality (AR) service, a virtual reality (VR) service, or the like.(4) The tenant information is used to indicate a tenant (tenant) of the service described in the service intent. The tenant may be understood as an enterprise user, and the tenant information may be information about the enterprise user. For example, an unmanned aerial vehicle belongs to a tenant, the unmanned aerial vehicle may use a service provided by a network, and the tenant information may be information about an unmanned aerial vehicle enterprise user.(5) The identifier of the terminal device is used to indicate a terminal device that uses the service described in the service intent.(6) The quantity of terminal devices is used to indicate a quantity of terminal devices that use the service described in the service intent.(7) The service intent priority is used to indicate a priority of the service intent. The higher the priority of the service intent, a network resource is preferentially allocated to the service intent. Service intent templates of the same type of services can have different priorities. In addition, the constraint information of the service intent is used to indicate a range of the service requirement information supported by the service intent, and constraint information that is of the service intent and that corresponds to service requirement information is used to indicate a range of the service requirement information. For example, constraint information corresponding to the service access time information may be used to indicate a range of a service access time. For example, the service access time does not exceed two hours. FIG.4shows a possible service intent template. The service intent template shown inFIG.4is applicable to the unmanned aerial vehicle service. Specifically, the service requirement information included in the service intent template may be unmanned aerial vehicle enterprise user information, an identifier of the unmanned aerial vehicle service, duration of the unmanned aerial vehicle service, an identifier of the unmanned aerial vehicle, a quantity of unmanned aerial vehicles, and a service flight path. The unmanned aerial vehicle enterprise user information is the tenant information, and is used to indicate an enterprise user that uses the unmanned aerial vehicle service. The identifier of the unmanned aerial vehicle service is used to indicate that the service intent template is for the unmanned aerial vehicle service. The duration of the unmanned aerial vehicle service is the service access time information, the identifier of the unmanned aerial vehicle is the identifier of the terminal device, and the service flight path is the service access location information. Specifically, the service flight path may include longitude, latitude, and altitude of key nodes in the flight path. These key nodes may be nodes constituting the flight path. The service flight path may further include location information of a departure place of unmanned aerial vehicle flight, location information of a destination of the unmanned aerial vehicle flight, and flight altitude. FIG.5shows a possible service intent template. The service intent template shown inFIG.5is applicable to an AR service or a VR service. Specifically, the service requirement information included in the service intent template may be AR enterprise user information, an identifier of the AR service (an identifier of the VR service), duration of the AR service, a quantity of terminal devices, an identifier of a terminal device, and location information. The location information may be information about an area in the AR service or the VR service. For example, the “location information” may be area information of a library, area information of an administrative area, or the like. The identifier of the VR service in the service intent template is used to indicate that the service intent template is for the VR service. The identifier of the AR service in the service intent template is used to indicate that the service intent template is for the AR service. FIG.6shows a possible service intent template. The service intent template shown inFIG.6is applicable to an asset tracking (asset tracking) service. Specifically, the service requirement information included in the service intent template may be enterprise user information, an identifier of the asset tracking service, duration of the service, a quantity of terminal devices, an identifier of a terminal device, user speed information, and service coverage location information. The user speed information is moving speed information of the terminal device, for example, a low speed, a normal speed, or a fast speed. After obtaining the service intent template, the intent management device may determine a specific value of each piece of service requirement information in the service intent template based on a service requirement and with reference to the constraint information of the service requirement information. The service intent generated by the intent management device may include the specific value of each piece of service requirement information in the service intent template. The service intent template shown inFIG.4is used as an example. The intent management device describes, by using the service intent, a service to be used by the unmanned aerial vehicle.FIG.7shows a possible service intent. Referring toFIG.7, the service intent generated by the intent management device includes enterprise user information (SF Express), service type information (using the identifier of the unmanned aerial vehicle service as an example, the information may be “unmanned aerial vehicle flight”), service access time information (using the duration of the unmanned aerial vehicle service as an example, the information may be “20190109, 7:00 to 9:00”), longitude, latitude, and altitude of a flight path (a node A, longitude 40 degrees east and latitude 35 degrees north; a node B longitude 41 degrees east, latitude 34 degrees north, and flight altitude 200 m), and a departure place and a destination (Pudong, Shanghai and Puxi, Shanghai).302: The requirement device sends the service intent to the intent management device, where the service intent is used to indicate the service requirement information, and the service requirement information includes service access time information of at least one terminal device and service access location information of the at least one terminal device. It should be noted that the requirement device may send the service intent to the intent management device, to indicate the intent management device to configure a specific network. Alternatively, after receiving the service intent, the intent management device may not configure a network, but indicate the network management device to configure the network. Specifically, the requirement device may send the service intent to the intent management device by using an interface invocation address. The interface invocation address is an invocation address of an interface that is disposed on the intent management device and that is used to receive the service intent. For example, the interface invocation address may be a uniform resource identifier (uniform resource identifier, URI). It should be noted that the at least one terminal device is a terminal device configured to use the service described in the service intent. The service access time information of the at least one terminal device may be the same or different. In a possible implementation, the service requirement information may include service access time information of each terminal device, and the service access time information of each terminal device may be the same or different. For example, five terminal devices use the service described in the service intent, and the service access time information included in the service requirement information is 1 hour, 1 hour, 2 hours, 1.5 hours, and 0.5 hours. The five pieces of time information are in a one-to-one correspondence with the five terminal devices, and a correspondence between the service access time information in the service intent and the terminal device may be pre-specified. This is not limited in this embodiment of the present application. In a possible implementation, the service requirement information includes one piece of service access time information, and the service access time information of each terminal device is the same. For example, five terminal devices use the service described in the service intent, and service access time information included in the service requirement information is 1 hour. The time information included in the service requirement information corresponds to the five terminal devices, that is, service access time information of each of the five terminal devices is 1 hour. In some embodiments of the present application, the service access location information of the at least one terminal device may be the same or may be different. In a possible implementation, the service requirement information may include service access location information of each terminal device, and the service access location information of each terminal device may be the same or different. For example, five terminal devices use the service described in the service intent, and the service access location information included in the service requirement information is Haidian District, Chaoyang District, Dongcheng District, Xicheng District, and Changping District. The five pieces of location information are in a one-to-one correspondence with the five terminal devices, and a correspondence between the service access location information in the service intent and the terminal device may be pre-specified. This is not limited in this embodiment of the present application. In a possible implementation, the service requirement information includes one piece of service access location information, and the service access location information of each terminal device is the same. For example, five terminal devices use the service described in the service intent, and the service access location information included in the service requirement information is Chaoyang District. The location information included in the service requirement information corresponds to the five terminal devices, that is, service access location information of each of the five terminal devices is Chaoyang District.303: The intent management device receives the service intent from the requirement device. Specifically, the requirement device may send the service intent to the interface invocation address, and then the intent management device may receive the service intent sent by the requirement device. After receiving the service intent, the intent management device may perform step304to configure the network based on the service intent. Alternatively, step305may be performed to indicate the network management device to configure the network.304: The intent management device determines network configuration information based on the service intent, and configures the network based on the network configuration information. It should be noted that the network configuration information is used to indicate a radio resource configuration. In a possible implementation, the network configuration information includes at least one of the following: antenna configuration information, beam configuration information, cell configuration information, routing information, and status information of a network device. The antenna configuration information is used to adjust an antenna of the network device. For example, the antenna configuration information may be an antenna angle, and the intent management device may adjust the antenna angle based on the antenna configuration information. The beam configuration information is used to adjust a beam of the network device. For example, the beam configuration information may be an azimuth angle and a pitch angle of the beam of the network device, and the intent management device may adjust the beam of the network device based on the beam configuration information, to adjust a beam gain. The cell configuration information is used to adjust a cell covered by the network device. The cell configuration information may be a frequency of a cell, a radio resource management policy (RRM Policy) of the cell, neighboring cell information of the cell, slice selection assistance information, and the like. The slice selection assistance information may be single network slice selection assistance information (S-NSSAI). The intent management device may configure the cell based on the cell configuration information, to provide network coverage for the service described in the service intent. The routing information is used to adjust an interface endpoint of the network device. For example, the routing information may be an IP address of an Xn interface, an X2 interface, or an NG interface, or may be an ID of a virtual local area network (VLAN). The intent management device may adjust a route of the network device based on the routing information. The status information of the network device includes any one of an active state, an inactive state, an available state, and an unavailable state. The intent management device may adjust a status of the network device based on the status information of the network device in the network configuration information. For example, the network device is in the inactive state, and the status information of the network device is the active state. In step304, the intent management device may activate the network device based on the network configuration information.305: The intent management device determines first information based on the service intent, and sends the first information to the network management device, where the first information includes network configuration information or network intent information. In a possible implementation, the intent management device determines the network configuration information based on the service intent received from the requirement device, and sends the network configuration information to the network management device. The network management device receives the network configuration information, and configures the network based on the network configuration information. For information included in the network configuration information, refer to related descriptions in step303. For a specific implementation in which the network management device configures the network based on the network configuration information, refer to related configuration performed by the intent management device based on the network configuration information. Details are not described herein again. In a possible implementation, the intent management device determines the network intent information based on the service intent received from the requirement device, and sends the network intent information to the network management device. The network management device receives the network intent information, and configures the network based on the network intent information. The network intent information is used to describe an effect of a network configuration, and the network management device may configure a radio resource based on the network intent information, to achieve the effect of the network configuration described in the network intent information. For example, the service described in the service intent sent by the requirement device is a flight service of the unmanned aerial vehicle from a location A to a location B. If the intent management device determines that a currently available network cannot support the flight service of the unmanned aerial vehicle from the location A to the location B, the intent management device may generate the network intent information, to describe the effect of the network configuration as “extending a network range”. Optionally, the method shown inFIG.3further includes: Before step301, the intent management device sends the service intent template to the requirement device. Optionally, the method shown inFIG.3further includes: Before the intent management device sends the service intent template to the requirement device, the intent management device may further receive a service subscription request message. The service subscription request message may include at least one of a service type, a user rate, a latency, and a maximum quantity of users. The service type is used to describe a type of a subscribed service, including an enhanced mobile broadband (eMBB) service, a massive internet of things (mIoT) service, a URLLC service, a WTTx service, an unmanned aerial vehicle flight service, an AR/VR service, and a resource tracking service. The user rate is used to describe a network rate perceived by a user, including an uplink rate and a downlink rate, and may be a single-user rate or an average user rate. The latency is used to describe a latency of the network. The maximum quantity of users is used to describe a maximum quantity of terminal devices for accessing the network and using the service. Further, the intent management device determines the service intent template based on the service subscription request message. For example, the service type is the unmanned aerial vehicle flight service, and the intent management device determines the service intent template corresponding to the unmanned aerial vehicle service. Alternatively, the service type is the URLLC service, a traffic model is the unmanned aerial vehicle flight service, and the intent management device determines the service intent template corresponding to the unmanned aerial vehicle service. Optionally, the service subscription request message may further include second information, where the second information is used to indicate the intent management device to return the service intent template. In a current technology, after receiving the service subscription request message, the intent management device allocates a network resource to the service of the terminal device based on the service subscription request message. In some embodiments of the present application, after receiving the service subscription request message, the intent management device determines, based on the service subscription request message, the service intent template corresponding to the service of the terminal device, and may send the determined service intent template to the requirement device. In this way, the requirement device may report a real-time service requirement of the terminal device based on the service intent template, and the network resource is allocated based on the real-time service requirement. The user only needs to pay for the network resource in a service access time, thereby implementing a pay-per-use network resource scheduling mode. Optionally, the method shown inFIG.3further includes: The intent management device sends the interface invocation address to the requirement device, where the interface invocation address is used to indicate the requirement device to send the service intent to the requirement device by using the interface invocation address. In the method provided in an embodiment of the present application, the intent management device may allocate the network resource to the service of the terminal device based on the service access time information and the service access location information in the service requirement information, and the user only needs to pay for the network resource during the service access time, thereby implementing the pay-per-use network resource scheduling mode. In addition, in a period other than the service access time, the network resource may be allocated to another service, so that the network resource is properly used and network resources are not wasted. The following describes a network configuration method provided in an embodiment of the present application by using an unmanned aerial vehicle service as an example. Referring toFIG.8, the method includes the following steps.801: An intent management device deploys a network. The intent management device may be an operator management system. The intent management device may deploy, based on a feature of a service, a network supporting the service. The deployed network may include a base station, a core network, a transmission network, and the like. The transmission network may be a fixed network. The network deployed by the intent management device supports a service. For example, the network deployed by the intent management device only supports the unmanned aerial vehicle service. Certainly, the network deployed by the intent management device may also support a plurality of services. For example, the network deployed by the intent management device supports the unmanned aerial vehicle service, a VR service, and an AR service.802: The intent management device determines a service intent template of the unmanned aerial vehicle service based on a common service requirement of the unmanned aerial vehicle service. The service intent template of the unmanned aerial vehicle service includes service requirement information of the unmanned aerial vehicle service and constraint information of each item of service requirement information. Referring toFIG.4, the service requirement information included in the intent template of the unmanned aerial vehicle service may be unmanned aerial vehicle enterprise user information, an identifier of the unmanned aerial vehicle service, duration of the unmanned aerial vehicle service, an identifier of an unmanned aerial vehicle, and a service flight path.803: A requirement device sends a service subscription request message to the intent management device. The requirement device may be a service operation system of an enterprise user. For example, the requirement device may be an operation system of an unmanned aerial vehicle user, and may send the service subscription request message to the intent management device based on a service requirement of the unmanned aerial vehicle user. In an embodiment of the present application, the service subscription request message may include at least one of a service type, a user rate, a latency, and a maximum quantity of users. In a possible implementation, the service subscription request message may be an allocate network (allocate network) request, and a network may be allocated to a service of the unmanned aerial vehicle user based on the service subscription request message. Alternatively, the service subscription request message is an allocate network slice (allocate NSI), and the network slice may be allocated to the service of the unmanned aerial vehicle user based on the service subscription request message.804: The intent management device determines that a service indicated by the service subscription request message can be provided. In a specific implementation, if the intent management device determines that the network deployed in step801can satisfy information in the service subscription request message, the intent management device determines that the service indicated by the service subscription request message can be provided. Optionally, the intent management device may deploy an independent network slice instance on the network deployed in step801, to satisfy the service indicated by the service subscription request message. It should be noted that, after determining that the service indicated by the service subscription request message can be provided, the intent management device may determine the service intent template of the unmanned aerial vehicle service. That is, step802may be included in step804.805: The intent management device returns a service subscription response message to the requirement device. The service subscription response message carries the service intent template and an interface invocation address of the unmanned aerial vehicle service. The interface invocation address is used by the requirement device to send the service intent to the intent management device, and the intent management device may receive, by using the interface invocation address, a service requirement sent by the requirement device. In a possible implementation, the interface invocation address may be an IP address or a URI.806: The requirement device determines the service intent based on the service requirement of the unmanned aerial vehicle user and the obtained service intent template. In a specific implementation, the requirement device fills a specific value of the service intent template based on the service requirement of the unmanned aerial vehicle user and with reference to the constraint information of the service requirement information, to generate the service intent. For example, the service intent includes: enterprise user information (SF Express), service type information (unmanned aerial vehicle flight), service access time information (20190109, 7:00 to 9:00), longitude, latitude, and altitude of a flight path (a node A, longitude 40 degrees east and latitude 35 degrees north; a node B, longitude 41 degrees east, latitude 34 degrees north, and flight altitude 200 m), and a departure place and a destination (Pudong, Shanghai and Puxi, Shanghai).807: The requirement device sends the service intent to the intent management device. Specifically, the service intent is sent to the intent management device by using the interface invocation address.808: The intent management device receives the service intent from the requirement device, and determines, based on the received service intent, a network that supports the service intent and a network configuration parameter. Specifically, a core network function instance that supports the service intent may be determined, for example, a user plane function (user plane function, UPF) instance that can satisfy the service intent may be determined. Alternatively, an access network function that supports the service intent may be determined, for example, a base station, a cell, an antenna, and the like that support the service intent may be determined. Further, after the network that supports the service intent is determined, the network configuration parameter required for configuring the network may be further determined. The network configuration parameter may be a configuration parameter related to an antenna of the base station, for example, an angle of the antenna of the base station. The network configuration parameter may alternatively be a parameter related to a beam of the base station, and includes an azimuth angle of the beam, a pitch angle of the beam, transmit power of the beam, and the like. Optionally, in this step, the intent management device may also determine an access control policy of a corresponding terminal (for example, an unmanned aerial vehicle) that uses a service described in the service intent.809: The intent management device configures, based on the network configuration parameter, the network that is determined in step808and that supports the service intent. Specifically, the intent management device may activate or deactivate some network devices based on the network configuration parameter, or may adjust configurations of some network devices based on the network configuration parameter, for example, adjust an antenna angle of the base station, a pitch angle of a transmit/receive beam of the base station, an azimuth angle of the transmit/receive beam of the base station, and transmit power of a transmit beam of the base station. Optionally, the intent management device may also send the network configuration parameter to a network management device herein, to request the network management device to configure the network based on the network configuration parameter.810: The intent management device configures an access control policy of the unmanned aerial vehicle to a corresponding network device. The unmanned aerial vehicle is a terminal device configured to use the service described in the service intent. In a specific implementation, the intent management device may send the access control policy of the unmanned aerial vehicle to a policy control function (PCF) network element, or may send the access control policy of the unmanned aerial vehicle to a network slice selection function (NSSF) network element, or may send the access control policy of the unmanned aerial vehicle to a network data analytics function (NWDAF) network element. Optionally, the intent management device may alternatively request the network management device to configure a PCF/an NSSF/an NWDAF for the access control policy of the unmanned aerial vehicle. In the method provided in some embodiments of the present application, service intent templates for different services are provided, so that the operator management system can propose the service intent based on the intent template and a real-time service requirement of the enterprise user, the operator management system can adjust and schedule the network in real time to guarantee the service, and the enterprise user only needs to pay according to an actual traffic requirement. This improves user experience and reduces a waste of network resources to some extent. In a 5G communication system, a scenario in which different network slice instances share a network resource exists, and different network slice instances are used to support different types of services. It is assumed that a base station is shared by a URLLC network slice instance and an eMBB network slice instance. The URLLC network slice instance is used to support an unmanned aerial vehicle flight service, and the eMBB network slice instance is used to support an AR service. An embodiment of the present application further provides a network configuration method, to implement a pay-per-use network resource scheduling mode in this scenario. As shown inFIG.9, the method includes the following steps.901: A first requirement device obtains a service requirement template corresponding to an unmanned aerial vehicle, and a second requirement device obtains a service requirement template corresponding to an AR service. It should be noted that the first requirement device may be a service operation system of an unmanned aerial vehicle enterprise, and the second requirement device may be a service operation system of an AR enterprise. In addition, for a specific manner in which the first requirement device and the second requirement device obtain the service requirement template, refer to step801to step805. Details are not described herein again.902: The first requirement device sends a service intent of an unmanned aerial vehicle service to an intent management device, and the second requirement device sends a service intent of the AR service to the intent management device. In a specific implementation, the first requirement device fills a specific value of a service intent template of the unmanned aerial vehicle service based on a service requirement of an unmanned aerial vehicle user and with reference to constraint information of service requirement information, to generate the service intent of the unmanned aerial vehicle service. The second requirement device fills a specific value of a service intent template of the AR service based on a service requirement of an AR user and with reference to the constraint information of the service requirement information, to generate the service intent of the AR service. In addition, the intent management device may further send an interface invocation address to the first requirement device, and the first requirement device may send the service intent of the unmanned aerial vehicle service to the intent management device by using the interface invocation address. The intent management device may further send an interface invocation address to the second requirement device, and the second requirement device may send the service intent of the AR service to the intent management device by using the interface invocation address. It should be noted that the interface invocation addresses sent by the intent management device to the first requirement device and the second requirement device may be the same or may be different. This is not limited in this embodiment of the present application.903: The intent management device determines, based on the service intent of the unmanned aerial vehicle service and the service intent of the AR service, a base station that supports both the unmanned aerial vehicle service and the AR service, and determines a slice RRM policy of the base station. It should be noted that determining the slice RRM policy of the base station is determining, in network resources that can be used by the base station, a proportion of network resources that can be used by an eMBB slice instance to network resources that can be used by a URLLC slice instance. In addition, the intent management device may determine, based on the service intent of the unmanned aerial vehicle service and a proportion of network resources occupied by the URLLC slice instance, a network configuration parameter corresponding to the URLLC slice instance. For example, if 10 terminal devices need to use a service provided by the URLLC slice instance, and two terminal devices need to use a service provided by the eMBB slice instance, network resources need to be configured, that is, a large part of the network resources are allocated to the URLLC slice instance, and a small part of the network resources are allocated to the eMBB slice instance. The intent management device may further determine, based on the service intent of the AR service and a proportion of network resources occupied by the eMBB slice instance, a network configuration parameter corresponding to the eMBB slice instance.904: The intent management device configures a network based on the network configuration parameter of the eMBB slice instance and the network configuration parameter of the URLLC slice instance. In a specific implementation, the intent management device first activates the base station that is determined in step903and that supports both the unmanned aerial vehicle service and the AR service. Further, the network may be configured based on the network configuration parameter of the eMBB slice instance, for example, by adjusting an antenna parameter and a beam parameter of the base station. Certainly, the network may alternatively be configured based on the network configuration parameter of the URLLC slice instance, for example, by adjusting an antenna parameter and a beam parameter of the base station. It should be noted that an antenna adjusted based on the network configuration parameter of the eMBB slice instance and an antenna adjusted based on the network configuration parameter of the URLLC slice instance may be the same or may be different. This is not limited herein. For example, if there is only an unmanned aerial vehicle flight service at a moment, an antenna or a beam of the base station needs to be configured to be upward. If there is only the AR service at a moment, an antenna or a beam of the base station needs to be configured to be downward. Optionally, the intent management device may also request the network management device to activate a corresponding base station and configure a corresponding network. In the method provided in some embodiments of the present application, in a scenario in which different network slice instances share a network resource, the network can be adjusted and scheduled in real time based on service intents supported by different network slices to guarantee the service, and an enterprise user only needs to pay according to an actual traffic requirement, thereby improving user experience and reducing a waste of network resources to some extent. FIG.10is a possible schematic diagram of a structure of the apparatus in the foregoing embodiments. The apparatus shown inFIG.10may be the intent management device described in the embodiments of this application, or may be a component that implements the foregoing method and that is in the intent management device, or may be a chip used in the intent management device. The chip may be a system-on-a-chip (SOC), a baseband chip with a communication function, or the like. As shown inFIG.10, the apparatus includes a processing unit1001and a communication unit1002. The processing unit may be one or more processors, and the communication unit may be a transceiver. The processing unit1001is configured to support the apparatus in performing step303, step304, step801, step802, step804, step808, step809, step903, and step904, and/or another process of the technology described in this specification. The communication unit1002is configured to support communication between the apparatus and another apparatus, for example, support the apparatus in performing step302, step305, step803, step805, step807, step810, and step902in the foregoing embodiments, and/or another process of the technology described in this specification. The processing unit1001may send and receive information by using the communication unit1002. It should be noted that all related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again. FIG.11is a possible schematic diagram of a structure of the apparatus in the foregoing embodiments. The apparatus shown inFIG.11may be the requirement device described in the embodiments of this application, or may be a component that implements the foregoing method and that is in the requirement device, or may be a chip used in the requirement device. The chip may be a system-on-a-chip (SOC), a baseband chip with a communication function, or the like. As shown inFIG.11, the apparatus includes a processing unit1101and a communication unit1102. The processing unit may be one or more processors, and the communication unit may be a transceiver. The processing unit1101is configured to support the apparatus in performing step301, step806, and step901, and/or another process of the technology described in this specification. The communication unit1102is configured to support communication between the apparatus and another apparatus, for example, support the apparatus in performing step302, step803, step805, step807, and step902in the foregoing embodiments, and/or another process of the technology described in this specification. The processing unit1101may send and receive information by using the communication unit1102. It should be noted that all related content of the steps in the foregoing method embodiments may be cited in function descriptions of corresponding function modules. Details are not described herein again. The foregoing descriptions about implementations allow a person skilled in the art to understand that, for the purpose of convenient and brief description, division of the foregoing function modules is used as an example for illustration. In actual application, the foregoing functions can be allocated to different function modules and implemented according to a requirement, that is, an inner structure of a database access apparatus is divided into different function modules to implement all or some of the functions described above. In the several embodiments provided in this application, it should be understood that the disclosed database access apparatus and method may be implemented in other manners. For example, the described database access apparatus embodiment is merely an example. For example, the module or unit division is merely logical function division and may be other division during actual implementation. For example, a plurality of units or components may be combined or integrated into another apparatus, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the database access apparatuses or units may be implemented in electronic, mechanical, or other forms. The units described as separate components may or may not be physically separate, and components displayed as units may be one or more physical units, that is, may be located in one place, or may be distributed on a plurality of different places. Some or all of the units may be selected according to actual requirements to achieve the objectives of the solutions of the embodiments. In addition, function units in the embodiments of this application may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units may be integrated into one unit. The integrated unit may be implemented in a form of hardware, or may be implemented in a form of a software function unit. When the integrated unit is implemented in a form of a software function unit and sold or used as an independent product, the integrated unit may be stored in a readable storage medium. Based on such an understanding, the technical solutions of the embodiments of this application essentially, or the part contributing to the conventional technology, or all or some of the technical solutions may be implemented in the form of a software product. The software product is stored in a storage medium and includes several instructions for instructing a device (which may be a single-chip microcomputer, a chip, or the like) or a processor to perform all or some of the steps of the methods described in the embodiments of this application. The foregoing storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disc. The foregoing descriptions are merely specific implementations of this application, but are not intended to limit the protection scope of this application. Any variation or replacement within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims. | 64,429 |
11943690 | DETAILED DESCRIPTION The present disclosure provides systems, devices, and methods for dynamically adjusting a radio frequency (RF) amplifier based on link statistics corresponding to wireless transmissions between a first device (such as a hearing aid or earbud) and a second device (such as a smartphone). More specifically, the RF amplifier may be adjusted if the link statistics indicate the need for improved receiver sensitivity and/or transmission power, such as during outdoor cross-body transmissions. The RF amplifier may be arranged in the first device to improve receiver sensitivity, or in the second device to increase transmission power. Further, triggering the adjustment of the RF amplifier based on the link statistics limits the power consumption of the RF amplifier to periods when increased receiver sensitivity or transmission power is required. FIG.1shows a user U wearing a first device100, embodied by an audio device, such as a hearing aid, in their left ear. The user U is also holding a second device200, embodied by a smartphone, in their right hand near their right hip. Accordingly, the most direct wireless communication path between the first device100and the second device200is a cross-body transmission path300, as illustrated inFIG.1. In this example, wireless data106(seeFIGS.2-5) can be transmitted along the cross-body transmission path300in a bidirectional manner. For instance, the first device100may receive audio data transmitted by the second device200. This audio data may then be played back by an acoustic transducer130(seeFIG.5) of the first device100. The second device200may also transmit other types of data to the first device100, such as data to configure the software or firmware of the first device100. Similarly, the second device200may receive acknowledgement packets from the first device100acknowledging the reception of previously transmitted data. Further, the second device200may receive data describing the first device100, such as data regarding battery life, audio settings, performance, etc. Even further, the second device200may also receive data captured by the first device100, such as audio captured by one or more microphones. However, as described above, the cross-body transmission path300may experience losses due to the lossy impact of the human body on RF transmissions. In indoor situations, reflections off of walls and ceilings can compensate for losses in the cross-body transmission path300. However, in outdoor situations, these reflections are unavailable. Accordingly, additional steps must be taken to compensate for the losses in the cross-body transmission path300. In one example, the wireless data106is transmitted over the cross-body transmission path300via a Bluetooth protocol, such as Bluetooth Classic, Bluetooth Low Energy (BLE), Bluetooth LE Asynchronous Connection-Less (ACL), or LE Audio. In the example of LE Audio, the second device200and the first device100may form an LE Audio connection, such as a Connected Isochronous Stream (CIS). FIG.2illustrates a schematic of a first device100in communication with a second device200. The schematic representation of the first device100and the second device200in the foregoing figures are solely for explanatory purposes and omits certain aspects of each device100,200for clarity. The second device200is configured to transmit wireless data106via wireless transceiver202and antenna214. The second device200may be any type of device capable of transmitting wireless data106, such as a smartphone. The wireless data106transmitted by the second device200travels over the cross-body transmission path300, as shown inFIG.1, and is received by an antenna114of the first device100. The first device100may be any type of device capable of receiving wireless data106, such as a hearing aid, earbud, audio headset, audio eyeglasses, portable loudspeaker, etc. While the aforementioned first devices100include one or more audio components, in some examples the first device100is not necessarily an audio device. Further, while the wireless data106transmitted by the second device200may include audio data, the wireless data106does not necessarily need to include audio data. Indeed, the wireless data106may contain other types of data, such as data to control or configure aspects of the first device100. As shown inFIG.2, the first device100includes a wireless transceiver102, antenna114, memory175, processor150, and front-end module (FEM)122. The wireless transceiver102receives the wireless data106via the antenna114and the FEM122. The wireless transceiver102may be a smart Bluetooth transceiver. The wireless transceiver102is configured to determine a number of link statistics108corresponding to the transmission of the wireless data106. The link statistics108describe a number of important properties of the transmission used to evaluate whether compensation is required to offset losses in the cross-body transmission path300. In some examples, the wireless transceiver102may be divided into discrete transmitter and receiver components, each component corresponding to a unique antenna. The link statistics108may include a received signal strength indicator (RSSI)110, packet error ratio (PER)112, buffer level116, audio drop data118, and acknowledgement packet data120. RSSI110is an estimate measure of power level of the wireless signal carrying the wireless data106received by the first device100. PER112is the ratio of incorrectly received data packets to the total number of received packets. Buffer level116indicates the amount of data temporarily stored in a buffer during transmission or reception. Audio drop data118indicates drops in audio data when the first device100is an audio device. Acknowledgement packet data120indicates whether acknowledgements of received wireless data106were received. In one example, the first device100transmits acknowledgement packets to the second device200to confirm receipt of the wireless data106. Other types of link statistics106may also be evaluated depending on the application. Once generated by the wireless transceiver102, the link statistics108are stored in memory175for retrieval by the processor150. The processor150then analyzes the link statistics108to determine if the cross-body transmission path300requires compensation. Any combination of types of link statistics108and thresholds may be used. For instance, if the RSSI110decreases below a certain absolute threshold, compensation may be required. Further, if the current RSSI110measurement decreased a certain amount relative to the previous RSSI110measurement, compensation may be required. Even further, if the PER112decreases below a certain threshold, while, concurrently, the audio drop data120indicates one or more audio drops in a certain period, compensation may be required. These determinations may be made according to a wide variety of algorithms, which may be optimized using certain analysis techniques, such as machine learning. Based on the analysis of the link statistics108, the processor150generates a control signal144. As shown inFIG.2, the control signal144is provided to the FEM122. The FEM122ofFIG.2includes an RF amplifier104of the first device100, embodied as a low noise amplifier (LNA)104a.The FEM122also includes bypass circuitry124forming a signal path circumventing the LNA104a.The bypass circuitry124may include one or more switching elements, such as discrete switches, transistors, diodes, etc. to selectively activate or deactivate the signal path circumventing the LNA104a.In one example, the control signal144places the FEM122in active mode, which activates the LNA104aand deactivates the bypass circuitry124. Alternatively, the control signal144may place the FEM122in sleep mode, which deactivates the LNA104aand activates the bypass circuitry124. Notably, the power consumption of the FEM122in sleep mode is significantly lower than in active mode. Low noise amplifiers are generally used to amplify the power of received wireless signals, while limiting the amount of noise introduced during the amplification, thus improving the receiver sensitivity. However, this improved receiver sensitivity comes at the expense of increased power usage by the low noise amplifier. Compact wireless devices, such as earbuds and hearing aids, typically have very small batteries with low power capacity, thus making power conservation critical to the operation of the wireless device. The first device100ofFIG.2addresses this concern by using the processor150to selectively control the LNA104aof the FEM122based on the link statistics108. For example, if the processor150determines, based on the link statistics108, that increased receiver sensitivity is required due to losses in the cross-body transmission path300, the control signal144places the FEM122in active mode, which activates the LNA104a,and deactivates the bypass circuitry134. Alternatively, if the processor150determines that increased receiver sensitivity is no longer required, the control signal144places the FEM122into sleep mode, thus deactivating the LNA104a,and activating the bypass circuitry134. In this way, the processor150conserves power and battery life by only activating the FEM122when increased receiver sensitivity is required. In some examples, the processor150may also generate the control signal144to increase or decrease the gain of the LNA104abased on the link statistics108. In some examples, the processor150controls the LNA104adirectly, without a FEM122. In these examples, the first device100may also have bypass circuitry124selectively controlled by the processor150. In these examples, the LNA104aand/or the bypass circuitry124may receive the control signal144directly from the processor150. A variation of the arrangement ofFIG.2is shown inFIG.3directed to selectively increase the transmission power of the second device200, rather than increasing the receiver sensitivity of the first device100. InFIG.3, as withFIG.2, the wireless transceiver202of the second device200transmits, via antenna214and FEM222, wireless data106aacross the cross-body transmission path300. The wireless data106ais received by the wireless transceiver102, via antenna114, of the first device100. The first device100then responds by transmitting wireless data106bback to the second device200via the cross-body transmission path300. Similar to the first device100depicted inFIG.2, the second device200ofFIG.3, includes the wireless transceiver202, antenna214, memory275, processor250, and FEM222with an RF amplifier204and bypass circuitry224. However, rather than an LNA, the RF amplifier204is embodied as a power amplifier (PA). Power amplifiers are generally used to significantly amplify an RF signal immediately before transmission. Like the LNA104aofFIG.2, the processor250is configured to provide a control signal244to the FEM222. The processor250uses the control signal244to selectively place the FEM222in active mode (activating PA204aand deactivating bypass224) when increased transmission power is required to compensate for losses in the cross-body transmission path300. Similarly, the processor250is configured to place the FEM222in sleep mode (deactivating PA204aand activating bypass224) to conserve power and battery life when increase transmission power is not required. As withFIG.2, whether an increase in transmission power is required is determined based on link statistics108a,108b.In one example, and as described with respect toFIG.2, the link statistics108aare determined by the wireless transceiver102of the first device100, and transmitted to the second device200with wireless data106b.These link statistics108aare then received by the wireless transceiver202, and stored in memory275for retrieval by the processor250for analysis. Link statistics108bmay also be determined by the wireless transceiver202of the second device200. For example, these link statistics108bmay include acknowledgement packet data120based on the wireless transceiver202of the second device200receiving (or not receiving) acknowledgement packets transmitted by the wireless transceiver102of the first device100. These link statistics108bare also stored in the memory275for retrieval by the processor250for analysis. The processor250analyzes a combination of one or more link statistics108a,108bto generate the control signal244. In this way, the control signal244communicates to the FEM222whether or not increased transmission power is required. The processor250may use different combinations of types of link statistics108a,108band/or corresponding thresholds than the first device100uses to generate the control signal144. In some situations, rather than simply activating or deactivating PA204aand bypass circuitry224, the control signal144may increase or decrease the gain of the PA204a. A variation of the arrangements ofFIGS.2and3is shown inFIG.4directed to selectively increase the transmission power of the first device100. In this example, wireless transceiver102transmits, via antenna114, wireless data106bto second device200. As described above, this wireless data106bmay include acknowledgement packets and/or other information regarding or captured by the first device100. The acknowledgement packets show the second device200that the wireless data106atransmitted by the second device200were successfully received by the first device100. However, if losses in the cross-body transmission path300prevent the second device200from receiving the wireless data106bincluding the acknowledgement packets, the second device200responds as if the first device100never received the initially transmitted wireless data106a.Accordingly, the second device200may then unnecessarily retransmit portions of the wireless data106a,consuming extra power and delaying the transmission of other data. However, this situation may be avoided by using a PA104bof the first device100to increase the transmission power of the signal carrying wireless data106b. In the example ofFIG.4, and as inFIG.3, link statistics108amay be generated by the wireless transceiver102of the first device100, and link statistics108bmay be generated by the wireless transceiver202of the second device200. The link statistics108bmay be transmitted to the first device100with wireless data106a.The processor150evaluates the link statistics108a,108bto determine if increased transmission power (to transmit wireless data106b) is required. If so, the control signal144generated by the processor150selectively places the FEM122into active mode (activating PA104band deactivating bypass circuitry124) to increase transmission power to compensate for losses in the cross-body transmission path300. If not, the control signal144places the FEM122into sleep mode (deactivating PA104band activating bypass circuitry124) to conserve power and battery life when increase transmission power is not required. In some examples, activating the PA104bmay actually lead to an overall reduction in power consumption. As described above, lost acknowledgment packets may cause the second device200to unnecessarily retransmit portions of the previously transmitted wireless data106a. Retransmitting data and duplicative reception and processing consumes additional power. By successfully transmitting the acknowledgement packets to the second device200, this retransmission and processing is avoided. In some examples, the first device100includes both a selectively controllable LNA104a(as shown inFIG.2) and a selectively controllable PA104b.The LNA104aand PA104bmay be arranged in the same FEM122, or they may be arranged in discrete FEMs122. In further examples, either or both of the LNA104aand PA104bmay be arranged within the transceiver102. FIG.5depicts a further variation of the arrangement ofFIG.2. InFIG.2, the first device100further includes a sensor134. In some examples, the sensor134may be a motion sensor or an audio sensor. Other types of sensors may be used depending on the application. The sensor134captures sensor data136, and stores the sensor data136in the memory175. The processor150then retrieves the sensor data136from memory175and analyzes the sensor data136to determine one or more periodic patterns138. These periodic patterns138may be used to indicate outdoor user behavior, such as walking, running, or cycling. For instance, patterns in the motion data may indicate these certain types of movements. In further examples, these movements may also be determined based on the link statistics108. In another example, audio data corresponding to wind sounds may be indicative of outdoor behavior. The processor150may then use this sensor data136, either alone or in combination with the link statistics108, to generate the control signal144to activate or deactivate the LNA104a.The periodic patterns138may be determined using machine learning, artificial intelligence, or other algorithms and/or processes. Further, if the wireless transceiver102is a Bluetooth transceiver, the processor150may be configured to select one of a plurality of Bluetooth physical layers (PHY)126based on the link statistics. The plurality of PHY layers126may include a 1-Megabit per second layer (1 Mb layer)128, a 2-Megabits per second layer (2 Mb layer)140, and a coded layer142. Generally, transmission using the 2 MB layer140are less robust than the 1 Mb layer, and transmissions using the 1 Mb layer140are less robust than the coded layer142. However, robustness roughly correlates to power consumption, such that using the coded layer142may consume more power than using the 1 Mb layer140, and using the 1 Mb layer140may consume more than the 2 Mb layer128. Thus, in an analogous manner to the selectable RF amplifier104, the processor150may configure the wireless transceiver102to use the coded layer142or 1 Mb layer140when increased robustness over the cross-body transmission path300is required, and to then use the 2 Mb layer142when increased robustness is not required. Modifying the chosen PHY layer126may also correspond to activating or deactivating the RF amplifier104. Further, the first device100may further include an acoustic transducer130. The acoustic transducer130may be configured to generate audio132based on at least a portion of the wireless data106received by the first device100. As shown inFIG.5, the wireless transceiver102is configured to receive the output of the FEM122. The acoustic transducer130is electrically coupled to the wireless transceiver102via signal processing circuitry185. The signal processing circuitry185may include a combination of components (such as filters, switches, mixers, etc.) to process the output from the wireless transceiver102into an input audio signal of which the acoustic transducer130may translate into audio132. FIG.6illustrates a more detailed schematic of the first device100. InFIG.6, the first device100includes the wireless transceiver102, antenna114, processor150, memory175, FEM122, sensor134, and acoustic transducer130. The FEM122includes the RF amplifier104and the bypass circuitry124. The acoustic transducer130generates audio132. The memory stores wireless data106, link statistics108, sensor data136, periodic patterns138corresponding to the sensor data136, data related to the control signal144, and data related to the Bluetooth PHY126. FIG.7is a flowchart of a method500for dynamically adjusting an RF amplifier. The method500includes determining502one or more link statistics. The link statistics correspond to wireless data. The wireless data is transmitted by a second device and received by a first device. The method500further includes adjusting an RF amplifier of the first device or the second device. The adjusting is based on the one or more link statistics. According to an example, the adjusting includes increasing or decreasing506a gain of the RF amplifier. Alternatively, the adjusting may include activating or deactivating508the RF amplifier. FIG.8is a variation ofFIG.7.FIG.8is a flowchart of a method600for dynamically adjusting two or more RF amplifiers. The method600includes determining602one or more link statistics. The link statistics correspond to wireless data. The wireless data is transmitted by a second device and received by a first device. The method600further includes adjusting604an RF amplifier of the first device. The adjusting is based on the one or more link statistics. In this example, the first device may be a hearing aid or an earbud. The RF amplifier of the first device may be a LNA or a PA The method600further includes adjusting606an RF amplifier of the second device. The adjusting is based on the one or more link statistics. In this example, the first device may be a hearing aid or an earbud. The RF amplifier of the second device may be a PA. All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms. The indefinite articles “a” and “an,” as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean “at least one.” The phrase “and/or,” as used herein in the specification and in the claims, should be understood to mean “either or both” of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with “and/or” should be construed in the same fashion, i.e., “one or more” of the elements so conjoined. Other elements can optionally be present other than the elements specifically identified by the “and/or” clause, whether related or unrelated to those elements specifically identified. As used herein in the specification and in the claims, “or” should be understood to have the same meaning as “and/or” as defined above. For example, when separating items in a list, “or” or “and/or” shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as “only one of” or “exactly one of,” or, when used in the claims, “consisting of,” will refer to the inclusion of exactly one element of a number or list of elements. In general, the term “or” as used herein shall only be interpreted as indicating exclusive alternatives (i.e. “one or the other but not both”) when preceded by terms of exclusivity, such as “either,” “one of,” “only one of,” or “exactly one of.” As used herein in the specification and in the claims, the phrase “at least one,” in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements can optionally be present other than the elements specifically identified within the list of elements to which the phrase “at least one” refers, whether related or unrelated to those elements specifically identified. It should also be understood that, unless clearly indicated to the contrary, in any methods claimed herein that include more than one step or act, the order of the steps or acts of the method is not necessarily limited to the order in which the steps or acts of the method are recited. In the claims, as well as in the specification above, all transitional phrases such as “comprising,” “including,” “carrying,” “having,” “containing,” “involving,” “holding,” “composed of,” and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases “consisting of” and “consisting essentially of” shall be closed or semi-closed transitional phrases, respectively. The above-described examples of the described subject matter can be implemented in any of numerous ways. For example, some aspects can be implemented using hardware, software or a combination thereof. When any aspect is implemented at least in part in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single device or computer or distributed among multiple devices/computers. The present disclosure can be implemented as a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product can include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present disclosure. The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium can be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire. Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network can comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device. Computer readable program instructions for carrying out operations of the present disclosure can be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). In some examples, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure. Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to examples of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions. The computer readable program instructions can be provided to a processor of a, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions can also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram or blocks. The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks. The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various examples of the present disclosure. In this regard, each block in the flowchart or block diagrams can represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks can occur out of the order noted in the Figures. For example, two blocks shown in succession can, in fact, be executed substantially concurrently, or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions. Other implementations are within the scope of the following claims and other claims to which the applicant can be entitled. While various examples have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the examples described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific examples described herein. It is, therefore, to be understood that the foregoing examples are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, examples can be practiced otherwise than as specifically described and claimed. Examples of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the scope of the present disclosure. | 33,329 |
11943691 | The Figures depict preferred embodiments for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the systems and methods illustrated herein may be employed without departing from the principles of the invention described herein. DETAILED DESCRIPTION Auto insurance policies and premiums may be crafted based upon the insurers' quantification of insured drivers' risk. Insurance companies (i.e., insurers) utilize a variety of techniques to gauge a particular driver's or class of drivers' risk. These techniques may allow insurers to divide and subdivide insured drivers into various risk pools, where a given driver's risk pool impacts the auto insurance policies available and the premiums (and/or rates, discounts, rewards, points, etc.) at which those policies are available. The risk a given driver poses may be reduced if that driver is unable to use their mobile device while driving. Assuring the driver will not be distracted by voice calls and text messages improves the driver's focus on the road, and reduces the likelihood the driver is involved in a collision. Generally, voice calls and text messages originating from a remote user of a remote mobile device, or “user device,” are relayed to the destination mobile device by one or more base stations (e.g., cell towers). When the destination mobile device receives the communications, unless on “silent,” the mobile device alerts the user via some notification, such as a ringer, chime, chirp, vibration, or other observable notification. If the user is also operating a motor vehicle, any attention of the user drawn by the notification or communication itself, is attention drawn away from the road. It is realized herein that such communications may be blocked on the mobile device while the user is operating the motor vehicle. Various aspects of using a mobile device are distracting to drivers. Notifications for voice calls, text messages, emails, or other communications may cause drivers to look away from the road to or at least contemplate the origin of the communication, the type of communication, and the contents of the communication. Many drivers yield to the temptation to receive the communication and maybe even respond. This may include taking a voice call, reading a text message or email, or sending a responsive text message or email. It is realized herein that, in many cases, blocking of communications to the mobile device while the user is operating a motor vehicle should include complete suppression of even the notification of the incoming communication until the user is no longer operating the motor vehicle. Among the various methods of determining when a user is operating a motor vehicle, automatic methods tend to be more effective, as many users don't realize how distracted they become when using their mobile device while driving, and would likely prefer to disable or simply avoid enabling any feature that may block communications or suppress notifications. This is particularly true in younger, less-experienced drivers. It is realized herein that blocking of communications or suppression of notifications may be enabled and disabled on the mobile device itself, or remotely via a network interface. Enabling and disabling may also be password protected, akin to parental controls. One way to determine a motor vehicle is in operation is to collect and monitor telematics data for the motor vehicle. Simple speed and position data may be used to determine the motor vehicle is in operation. Alternatively, a driver's mobile device may connect to a BLUETOOTH device associated with the motor vehicle, such as the motor vehicle's native BLUETOOTH system (e.g., hands-free phone or info-tainment system). Upon establishing a BLUETOOTH connection between the mobile device and the BLUETOOTH device associated with the motor vehicle, an inference may be made that the user is embarking on a trip in the motor vehicle, the user will be driving, and that incoming communications should be blocked or notifications suppressed. Alternatively, a determination may be made based on a combination of the BLUETOOTH connection and the telematics data. Likewise, telematics data and the BLUETOOTH connection may indicate when the user is no longer operating the motor vehicle. For example, if the BLUETOOTH connection between the mobile device and the BLUETOOTH device associated with the motor vehicle is terminated, an inference may be made that the user's trip is complete, the user is no longer driving, and communications to and from the mobile device may resume. Any communications blocked or notifications suppressed may then be provided to the user on the mobile device. It is realized herein that blocking communications to a mobile device while the user of the mobile device is driving a motor vehicle may disrupt important communication bound for the user. Voice calls bound for the mobile device may be listed as missed calls upon completion of the user's trip. In certain embodiments, voice callers may be greeted with a voice or text message indicating the user is driving and the user will return their call at a more appropriate time. Similarly, automated text responses may be sent to originators of text messages indicating the user is driving and unable to receive or send text messages until their trip is complete. It is realized herein that emergencies may arise where blocking of communications and notifications to a mobile device is undesirable. Blocking or suppression of communications may be bypassed in certain circumstances. Such a bypass may be had by designated emergency contacts, or by some form of authentication of the emergency. For example, a voice caller may be presented a voice prompt to enter a bypass code in case of emergency. The technical effect achieved by this system may be at least one of: (a) recognizing when a user of a mobile device is operating a motor vehicle based on telematics and BLUETOOTH connectivity; (b) reducing distraction for operators of motor vehicles by blocking communications to their mobile device or suppressing notifications; (c) delaying notification of incoming communications on a user's mobile device while operating a motor vehicle; and (d) reducing drivers' risk of collision by improving their attention to the road. A technical effect of the systems and processes described herein may be achieved by performing at least one of the following steps: (i) establishing a BLUETOOTH connection between a mobile device and a BLUETOOTH device associated with a motor vehicle; (ii) recognizing the user is operating the motor vehicle based upon the BLUETOOTH connection; (iii) receiving a wireless communication from a remote device; and (iv) suppressing notification of receipt of the wireless communication to the user. As used herein, “user device” refers generally to any device capable of accessing the Internet including, but not limited to, a desktop computer, or a mobile device (e.g., a laptop computer, a personal digital assistant (PDA), a cellular phone, a smartphone, a tablet, a phablet, smart glasses, a smart watch or other wearable computing device, or netbook), or other mobile device or web-based connectable equipment. Exemplary System FIG.1depicts an exemplary system100for handling communications to a mobile device110while a user operates a motor vehicle120. Mobile device110is a user device capable of sending and receiving wireless communications130, including voice telephone calls and text messages. In certain embodiments, mobile device110may be a cellular phone with voice and text capability. In alternative embodiments, mobile device110may be a PDA or smartphone. Generally, mobile device110sends and receives wireless communications130to and from remote devices, such as remote device140. Wireless communications130between mobile device110and remote device140are typically indirect, being relayed by one or more wireless base stations, such as wireless base station150.FIG.1depicts a single wireless base station150, although system100may include multiple wireless base stations and wireless communications130are often relayed by multiple wireless base stations, the plurality of which are omitted inFIG.1for clarity. Generally, mobile device110receives wireless communications130from remote device140and provides a notification to a user of mobile device110. Such notification may include a ringer, tone, chime, or any other audible alert. The notification may also include a vibration, pulse, or other haptic alert. The notification may also include a visual alert, such as an incoming message indicator, an incoming call display or image, or a new message display or image. In certain cases, mobile device110may be in a “silent” mode, in which audible alerts are suppressed. In certain embodiments, the silent mode may further suppress haptic and visual alerts as well. In one embodiment, for example, mobile device110may be configured to provide a ringer for an incoming call. Mobile device110may be configured to execute a telephone application upon receipt of the incoming call. The telephone application may cause mobile device110to display an incoming call display, which may include the originating phone number and an identification of the originating user of remote device140. The incoming call display may facilitate the user's answering or ignoring the incoming call. Similarly, mobile device110may be configured to provide a chime upon receiving a new text message. Mobile device110may be further configured to display an incoming message icon. In certain embodiments, mobile device110may be configured to open the received text message and display its contents. Motor vehicle120is associated with a BLUETOOTH device160. BLUETOOTH device160may be a BLUETOOTH system native to motor vehicle120, such as a hands-free telephone system, or an info-tainment system. Alternatively, BLUETOOTH device160may include a BLUETOOTH beacon. Such a BLUETOOTH beacon may be configured to be powered by motor vehicle120. BLUETOOTH device160may be connected to mobile device110by a BLUETOOTH connection170. Exemplary Mobile Device FIG.2depicts a block diagram of an exemplary mobile device200. Mobile device200includes a processor210, a display220, a BLUETOOTH interface230, a wireless communication interface240, and telematics devices250. Processor210is coupled to display220such that, by executing program instructions, processor210controls display of images, icons, and application screens on display220. Processor210is further coupled to BLUETOOTH interface230such that, by executing program instructions, processor210sends and receives data over a BLUETOOTH connection between mobile device200and another BLUETOOTH device. Processor210is further coupled to wireless communication interface240such that, by executing program instructions, processor210sends and receives wireless communications to and from one or more remote devices, such as remote device140. Processor210is further coupled to telematics devices250such that processor210receives telematics data generated by telematics devices250. BLUETOOTH interface230may include a BLUETOOTH antenna, encoders, decoders, transceivers, or any other components necessary for carrying out BLUETOOTH communication. BLUETOOTH interface230establishes a BLUETOOTH connection with a BLUETOOTH device associated with a motor vehicle, such as BLUETOOTH device160associated with motor vehicle120. Processor210receives data indicating the status of the BLUETOOTH connection, including whether the BLUETOOTH connection is established, terminated, or in use. Based upon the BLUETOOTH connection, processor210determines whether the user of mobile device200is operating motor vehicle120. Once the BLUETOOTH connection is established, processor210determines the user has entered the vehicle and is embarking on a trip that will continue for a period of time. When the BLUETOOTH connection is terminated, processor210determines the user has completed the trip. In certain embodiments, processor210also receives telematics data for motor vehicle120from telematics devices250. Processor210may determine when the user embarks and completes a trip based upon the telematics data alone, or in combination with the BLUETOOTH connection. For example, processor210may determine the trip has begun based upon speed and position data collected by telematics devices250. In certain embodiments, processor210may determine the trip has begun based upon both the BLUETOOTH connection being established and the speed rising above a threshold. In certain embodiments, other telematics devices may be installed on motor vehicle120and send telematics data to mobile device200using BLUETOOTH Interface230or any other suitable communication channel, such as, for example, universal serial bus (USB). Telematics devices installed in motor vehicle120may be in addition to or in place of telematics devices250on mobile device200. Mobile device200sends and receives wireless communications using wireless communication interface240. Wireless communication interface240may include a radio frequency (RF) antenna, encoders, decoders, transceivers, and any other components necessary for carrying out wireless communications, including, for example, voice telephone calls and text messages. Wireless communications received over wireless communication interface240are further processed by processor210, which may include decoding, demodulating, translating, or any other suitable processes for receiving the wireless communication. Typically, when a wireless communication is received by mobile device200, processor210may generate a notification to the user to alert the user of receipt of the incoming wireless communication. The notification may include an audible alert, a haptic alert, or a visual alert. When processor210determines the user has begun a trip, processor210initiates suppression of notifications of the user of incoming wireless communications. Suppression of notifications may include suppression of audible, haptic, or visual alerts that the incoming wireless communications have been received. For example, a telephone ringer for an incoming voice call may be suppressed. Further, no visual alert of the incoming voice call is displayed. In certain embodiments, processor210initiates the suppression of notifications by instructing wireless base stations, such as wireless base station150, to delay delivery of wireless communications during the trip. Delaying delivery of wireless communications also delays processing by processor210that would generate typical notifications to the user. In other embodiments, processor210may provide information about the BLUETOOTH connection or telematics data to wireless base station150, which determines itself whether the user of mobile device200has begun a trip and is operating motor vehicle120. During the trip, processor210may initiate an automatic response to remote device140using wireless communication interface240. An automatic response may include an indication the user is operating the motor vehicle. In certain embodiments, processor210prompts the user for authorization to enable and disable suppression of notifications. The prompt may be displayed on display220. Processor210may, in certain embodiments, bypass suppression of notifications to the user. Bypass of suppression of notifications may be provided by voice or textual prompt of a user of the originating remote device for the wireless communication. For example, a second user of remote device140may be prompted during a voice call to mobile device200. Similarly, a text message prompt may be sent to the remote device requesting authorization for bypass. Authorization for bypass may be password protected. In alternative embodiments, bypass may be automatically authorized for emergency contacts. Exemplary Wireless Base Station FIG.3depicts a block diagram of an exemplary wireless base station300, such as wireless base station150, shown inFIG.1. Wireless base station300includes a processor310and a wireless communication interface320. Generally, wireless base station300relays wireless communication, such as wireless communications130, from tower-to-tower, or tower-to-mobile device. Wireless communications130are sent and received using wireless communication interface320. Processor310processes wireless communications130and controls how wireless communications130should be transmitted and received. In certain embodiments, processor310receives data from a mobile device, such as mobile device200, shown inFIG.2, indicating a BLUETOOTH connection has been established between mobile device200and a BLUETOOTH device associated with a motor vehicle, such as BLUETOOTH device160associated with motor vehicle120. Processor310determines the user of mobile device200is embarking on a trip in motor vehicle120and initiates suppression of notification of the user for incoming wireless communications. Processor310may delay delivery of incoming wireless communications to mobile device200, thus delaying the ordinary notifications generated by their receipt by mobile device200. When the trip is complete, processor310causes wireless communication interface320to deliver the wireless communications. When the delayed wireless communications are received, they may include notifications of missed calls or, for text messages, a queue of new text messages. Exemplary Methods FIG.4depicts flow diagrams of exemplary methods400,500, and600for handling communications to a mobile device, such as mobile device200, shown inFIG.2, while a user of mobile device200is operating a motor vehicle, such as motor vehicle120, shown inFIG.1. Method400begins at a start step410. At a BLUETOOTH connection step420, a BLUETOOTH connection is established between mobile device200and a BLUETOOTH device associated with motor vehicle120, such as BLUETOOTH device160. Based upon the BLUETOOTH connection, a determination is made, at determination step430, that the user of mobile device200is operating motor vehicle120. The determination may be made by a processor executing program instructions, such as processor210of mobile device200or processor310of wireless base station300. In certain embodiments, processor210may make the determination based upon telematics data collected by telematics devices, such as telematics devices250of mobile device200, or by other telematics devices on motor vehicle120. In certain other embodiments, processor310may receive the telematics data and BLUETOOTH connection data from mobile device200using wireless communications interface320and make the determination based upon one or more of the BLUETOOTH connection data and the telematics data. When the BLUETOOTH connection is established, the processor determines the user has entered and started motor vehicle120, and further infers that the user is embarking on a trip. In embodiments where telematics data is used, the processor makes further inferences that the trip has begun based upon, for example, speed and position data for motor vehicle120. For example, the processor may infer the trip has begun when the speed exceeds a threshold. Based upon the determination, communications to mobile device200are blocked or notifications of received wireless communications are suppressed. During the trip, at a receiving step440, a wireless communication is received from a remote device, such as remote device140, shown inFIG.1. The wireless communication is received using a wireless communications interface, such as wireless communications interface240of mobile device200or wireless communications interface320of wireless base station300. A notification of the user of receipt of the wireless communication is suppressed at a suppression step450. In one embodiment, at suppression step450, when the wireless communication is received at wireless communication interface240, processor210suppresses any audible, visual, haptic, or otherwise observable alerts that would ordinarily be provided to the user of mobile device200. When the trip is complete, processor210stops suppressing the notification and mobile device200resumes normal operation, which may include presenting the user a list of missed voice calls or a queue of text messages, for example. Method400ends at an end step460. The method may include additional, less, or alternate actions, including those discussed elsewhere herein. FIG.5depicts a flow diagram of an exemplary method500for handling communications to mobile device200at a wireless base station, such as wireless base station300, shown inFIG.3. Method500begins at a start step510. At a BLUETOOTH connection step520, a BLUETOOTH connection is established between mobile device200and BLUETOOTH device160associated with motor vehicle120. Based upon the BLUETOOTH connection, a determination is made, at a determination step530, that the user of mobile device200is operating motor vehicle120. The determination may be made by a processor executing program instructions, such as processor210of mobile device200or processor310of wireless base station300. In certain embodiments, processor210may make the determination based upon telematics data collected by telematics devices, such as telematics devices250of mobile device200, or by other telematics devices on motor vehicle120. In certain other embodiments, processor310may receive the telematics data and BLUETOOTH connection data from mobile device200using wireless communications interface320and make the determination based upon one or more of the BLUETOOTH connection data and the telematics data. When the BLUETOOTH connection is established, the processor determines the user has entered and started motor vehicle120, and further infers that the user is embarking on a trip. In embodiments where telematics data is used, the processor makes further inferences that the trip has begun based upon, for example, speed and position data for motor vehicle120. For example, the processor may infer the trip has begun when the speed exceeds a threshold. Based upon the determination, communications to mobile device200are blocked or notifications of received wireless communications are suppressed. During the trip, at a receiving step540, a wireless communication is received from remote device140. The wireless communication is received using wireless communication interface320of wireless base station300. Based upon the determination from determination step530, processor310delays delivery of the wireless communication to mobile device200at a delaying step550. Consequently, at delaying step550, notification of the user of receipt of the wireless communication is suppressed, because the wireless communication has not reached mobile device200or wireless communication interface240. When the trip is complete, processor310delivers the wireless communication to mobile device200and mobile device200may provide the user a list of missed voice calls or a queue of text messages, for example. Method500ends at an end step560. The method may include additional, less, or alternate actions, including those discussed elsewhere herein. FIG.6depicts a flow diagram of an exemplary method600for handling communications to mobile device200. Method600begins at a start step610. At a BLUETOOTH connection step620, a BLUETOOTH connection is established between mobile device200and BLUETOOTH device160associated with motor vehicle120. Based upon the BLUETOOTH connection, a determination is made, at a determination step630, that the user of mobile device200is operating motor vehicle120. The determination may be made by a processor executing program instructions, such as processor210of mobile device200or processor310of wireless base station300. In certain embodiments, processor210may make the determination based upon telematics data collected by telematics devices, such as telematics devices250of mobile device200, or by other telematics devices on motor vehicle120. In certain other embodiments, processor310may receive the telematics data and BLUETOOTH connection data from mobile device200using wireless communications interface320and make the determination based upon one or more of the BLUETOOTH connection data and the telematics data. When the BLUETOOTH connection is established, the processor determines the user has entered and started motor vehicle120, and further infers that the user is embarking on a trip. In embodiments where telematics data is used, the processor makes further inferences that the trip has begun based upon, for example, speed and position data for motor vehicle120. For example, the processor may infer the trip has begun when the speed exceeds a threshold. Based upon the determination, communications to mobile device200are blocked or notifications of received wireless communications are suppressed. During the trip, at a receiving step640, a wireless communication is received from remote device140. The wireless communication is received using wireless communication interface320of wireless base station300. At a delivery step650, the wireless communication is delivered to mobile device200using wireless communication interface320of wireless base station300and wireless communication interface240of mobile device200. Based upon the determination from determination step630, processor210, at delaying step660, delays notification of receipt of the wireless communication during the trip. In certain embodiments processor210may delay notification per instructions received from wireless base station300. Processor310of wireless base station300may generate such instructions based on the determination from determination step630. In such embodiments, the determination at step630may be carried out by processor210or processor310. Method600ends at an end step670. The method may include additional, less, or alternate actions, including those discussed elsewhere herein. Additional Considerations As will be appreciated based upon the foregoing specification, the above-described embodiments of the disclosure may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or any combination or subset thereof. Any such resulting program, having computer-readable code means, may be embodied or provided within one or more computer-readable media, thereby making a computer program product, i.e., an article of manufacture, according to the discussed embodiments of the disclosure. The computer-readable media may be, for example, but is not limited to, a fixed (hard) drive, diskette, optical disk, magnetic tape, semiconductor memory such as read-only memory (ROM), and/or any transmitting/receiving medium such as the Internet or other communication network or link. The article of manufacture containing the computer code may be made and/or used by executing the code directly from one medium, by copying the code from one medium to another medium, or by transmitting the code over a network. These computer programs (also known as programs, software, software applications, “apps”, or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms “machine-readable medium” “computer-readable medium” refers to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The “machine-readable medium” and “computer-readable medium,” however, do not include transitory signals. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor. As used herein, a processor may include any programmable system including systems using micro-controllers, reduced instruction set circuits (RISC), application specific integrated circuits (ASICs), logic circuits, and any other circuit or processor capable of executing the functions described herein. The above examples are example only, and are thus not intended to limit in any way the definition and/or meaning of the term “processor.” As used herein, the terms “software” and “firmware” are interchangeable, and include any computer program stored in memory for execution by a processor, including RAM memory, ROM memory, EPROM memory, EEPROM memory, and non-volatile RAM (NVRAM) memory. The above memory types are example only, and are thus not limiting as to the types of memory usable for storage of a computer program. In one embodiment, a computer program may be provided, and the program may be embodied on a computer readable medium. In an exemplary embodiment, the system may be executed on a single computer system, without requiring a connection to a sever computer. In a further embodiment, the system may be run in a Windows® environment (Windows is a registered trademark of Microsoft Corporation, Redmond, Washington). In yet another embodiment, the system may be run on a mainframe environment and a UNIX® server environment (UNIX is a registered trademark of X/Open Company Limited located in Reading, Berkshire, United Kingdom). The application is flexible and designed to run in various different environments without compromising any major functionality. In some embodiments, the system includes multiple components distributed among a plurality of computing devices. One or more components may be in the form of computer-executable instructions embodied in a computer-readable medium. The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independent and separate from other components and processes described herein. Each component and process may also be used in combination with other assembly packages and processes. As used herein, an element or step recited in the singular and preceded by the word “a” or “an” should be understood as not excluding plural elements or steps, unless such exclusion is explicitly recited. Furthermore, references to “exemplary embodiment” or “one embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. Telematics data collection may be started and stopped in response to trigger events (e.g., vehicle engine RPM, vehicle movement), such as disclosed by U.S. Pat. No. 8,930,231 (entitled “Methods Using a Mobile Device to Provide Data for Insurance Premiums to a Remote Computer”), which is incorporated herein by reference in its entirety. Collection of telematics data by a mobile device may be started and stopped based upon the mobile device being within BLUETOOTH, Near Field Communication, or other wireless communication technique range of a vehicle-mounted transceiver, such as disclosed by U.S. Pat. No. 8,666,789 (entitled “BLUETOOTH Device to Enable Data Collection for Insurance Rating Purposes”), which is incorporated herein by reference in its entirety. This written description uses examples to disclose the disclosure, including the best mode, and also to enable any person skilled in the art to practice the disclosure, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the disclosure is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims. | 32,085 |
11943692 | DETAILED DESCRIPTION In accordance with the principles described herein, emergency response is enabled by facilitating communication between an emergency communications center and user devices. Such user devices may be highly available without special training, such as cell phones. Furthermore, such communication is available even without the use of a cellular network. Thus, even in emergencies in which cellular communication is no longer possible, individuals can use prevalent devices to communicate their emergency needs and situation to an emergency communications center, allowing that center to gain a holistic, comprehensive, and fresh understanding of the needs of the community. The communication center can thereby coordinate with capable individuals and resources within the community to help address those needs. The enabled communication may be low-bandwidth since the amount of information needed for communication during emergencies is small, and include perhaps just simple messages that focus on the essentials. Furthermore, the communication protocol may require little power, thereby allowing the communication to continue for extended periods on battery power, which is particularly useful when the emergency has disrupted the power grid and that disruption is long-lasting. In accordance with the principles described herein, emergency communication hardware nodes intermediate communication between an emergency communications center and user devices. The emergency communication hardware node includes a long-range radio receiver configured to receive messages over a non-cellular long-range low-bandwidth radio channel (such as a LoRa channel). In addition, the hardware node also includes a long-range radio transmitter configured to transmit messages over the non-cellular long-range low-bandwidth radio channel, which may be a separate component or integrated with the receiver to form a transceiver. The channel may use an adaptive bitrate radio protocol that is low-bandwidth, such as LoRa. As an example, the channel may have a maximum bitrate of less than one megabit per second, and a minimum bitrate of less than a kilobit per second. In addition, the channel may be long distance, thereby enabling communication using a network of perhaps (but not necessarily) sparsely distributed nodes throughout the community. As an example, the channel may have a line-of-sight range of over a mile, as LoRa easily does. In addition to the capability to communicate with the emergency communications center over the long-range channel, the hardware node also has a wi-fi access point component configured to, when activated, enable a local wi-fi hotspot, which can be considered an emergency use wi-fi hotspot. The hardware node also includes an emergency response component configured to respond to an emergency message received over the long-range channel from an emergency communications center by activating the wi-fi access point component. The hardware node also responds to the emergency message by facilitating one or two-directional communication between the user device and the emergency communications center using the wi-fi hotspot and the long-range channel. In some embodiments, when the wi-fi access point component enables the local wi-fi hotspot, the wi-fi access point component may also provide a captive portal that is displayed at user devices within the local wi-fi hotspot once the user device connects to that hotspot. The captive portal provides an interface that permits low bandwidth communication (such as text and binary messages). As an example, the captive portal might provide a chat window, and/or buttons to report different types and levels of need during the emergency. Thus, the captive portal may be considered an emergency use captive portal. Thus, the principles described herein provide a robust emergency response mechanism that has the potential to save human life, reduce human injury, and alleviate human suffering in the event of an emergency. FIG.1illustrates a system100in accordance with the principles described herein. The system100includes hardware nodes101(1) through101(n) that are within long-range radio range of a base station120of an emergency communications center102. Each hardware node101has a capability to communicate over long range radio to the base station120as well as at least is selectively capable of communicating over wi-fi with respective user devices within a local wi-fi hotspot created by the hardware node101. Leveraging these two capabilities, the hardware nodes101each intermediates communications between the emergency communications center102and respective user devices that are within wi-fi range of the hardware node. InFIG.1, the user devices are represented with small circles, and the hardware nodes are represented as ovals. For example, inFIG.1, each hardware node101(1) through101(n) is illustrated as having an associated local wi-fi hotspot110(1) through110(n), respectively. The local wi-fi hotspots represent areas that are within wi-fi range of the corresponding hardware node when the wi-fi hotspot is enabled. When a user device is wi-fi enabled and within a wi-fi hotspot, the user device can discover and connect to a wi-fi network associated with the wi-fi hotspot, and thereafter communicate over the wi-fi network. Because the wi-fi hotspots can be turned on and off, the wi-fi hotspots110are each represented with dashed-lined borders. Although the wi-fi hotspots110are represented as circles, it will be appreciated that the actual wi-fi range of a wi-fi network may have a more complex and dynamic shape that depends on numerous factors such as obstacles, walls, interference, signal strength, and the like. However, a circle is used merely to represent the principle that each wi-fi network will have a particular range. The hardware nodes101each use one antenna (called herein a “wi-fi antenna”) for communicating over wi-fi with user devices within wi-fi range of the hardware node, and another antenna (called herein a “long-range radio antenna”) for communicating over longer ranges with the base station120of the emergency communications center102. For example, inFIG.1, each hardware node101(1) through101(n) has respective wi-fi antennas103(1) through103(n) for communicating with user devices within the corresponding wi-fi hotspot110(1) through110(n). Furthermore, each hardware node101(1) through101(n) has respective long-range radio antennas104(1) through104(n). As an example, the hardware node101(1) has associated wi-fi hotspot110(1), which encompasses two user devices111and112. Accordingly, the hardware node101(1) can selectively communicate with the user devices111and112using the wi-fi antenna103(1) as represented by respective connections131and132. InFIG.1, wi-fi connections are each represented as a jagged line. The hardware node101(1) also can communicate with the emergency communications center102as represented by the long-range radio connection105(1). Thus, when the wi-fi hotspot110(1) is enabled, the hardware node101(1) is capable of intermediating communication between the user device111and the emergency communications center102using wi-fi connection131and long-range radio connection105(1), and between the user device112and the emergency communications center102using wi-fi connection132and long-range radio connection105(1). Also, the hardware node101(2) can selectively communicate with the user devices113and114using the wi-fi antenna103(2) as represented by respective wi-fi connections133and134. The hardware node101(2) also can communicate with the emergency communications center102as represented by the long-range radio connection105(2). Thus, when the wi-fi hotspot110(2) is enabled, the hardware node101(2) is capable of intermediating communication between the user device113and the emergency communications center102using wi-fi connection133and long-range radio connection105(2), and between the user device114and the emergency communications center using wi-fi connection134and long-range radio connection105(2). Finally, the hardware node101(3) can selectively communicate with the user device115using the wi-fi antenna103(n) as represented by wi-fi connection135. The hardware node101(n) also can communicate with the emergency communications center102as represented by the long-range radio connection105(n). Thus, when the wi-fi hotspot110(n) is enabled, the hardware node101(2) is capable of intermediating communication between the user device115and the emergency communications center102using wi-fi connection135and long-range radio connection105(n). InFIG.1, there are some illustrated user devices116,117and118that are not within the local wi-fi hotspot of any of the hardware nodes. This is merely to demonstrate that the system100may not encompass every corner of a community. However, in order to facilitate as comprehensive of an emergency response as possible, the coverage of the system100is preferably as complete as feasible and viable. Nevertheless, even with less than complete coverage, the principles described herein provide the emergency communications center with a comprehensive view of the needs of the community. While each wi-fi hotspot110may always be active, even if not in case of emergency, in some embodiments described herein, the wi-fi hotspot is enabled by the respective hardware node in response to an emergency signal received by the hardware node from the emergency communications center. Thus, the emergency communications center102can cause all of the wi-fi hotspots to be enabled by broadcasting an emergency message. Once a local wi-fi hotspot is enabled, user devices within that hotspot can communicate with the hardware node providing that wi-fi hotspot. Thereafter, a given hardware node can intermediate communications between respective user devices with the corresponding local hotspot and the emergency communications center. That is, the hardware node can facilitate inbound communication from the user device to the emergency communications center by receiving a wi-fi communication from the user device over the corresponding wi-fi network, and transmitting the communication (or essential content of the communication) to the emergency communications center. Alternatively, or in addition, the hardware node can facilitate outbound communication from the emergency communications center to the user device by receiving a communication transmitted by a long-range radio base station120of the emergency communications center102, and then transmitting the communication (or essential content of the communication) to the user device over the wi-fi network. The system100ofFIG.1is a very simple example in order to explain the concepts herein without an unduly complex and more realistic example. For instance, the principles described herein do not restrict the number “n” of hardware nodes that can be within the system100. “n” can be any whole number, including one. If “n” is one, there would be but a single hardware node101(1) within the system100. On the other hand, “n” could be a very large number, which would be more suitable if the system spanned a larger and/or populous territory (such as a town or city). Accordingly, there may be a large number of hardware nodes within the system100. There may in fact be a variable number of hardware nodes within the system100, as hardware nodes are brought online or become in range of the emergency communications center102, or as hardware nodes are broad offline or fall out of range of the emergency communications center102. The ellipsis101(m) represents that the principles described herein are not limited to the number of hardware nodes within the system100, or the particular placement position of hardware nodes within the system100. Also, the example ofFIG.1is kept simple as there are only illustrated a small and static number of user devices shown within a given wi-fi hotspot. However, in reality, there may be more or less user devices (perhaps zero, perhaps many) within a given wi-fi hotspot. Furthermore, user devices tend to move around as their users wander. Thus, the number and position of user devices within a given wi-fi hotspot may dynamically change, without impacting the broader principles described herein. Prior to proceeding toFIG.2, this description mentions a brief note about nomenclature. InFIG.1, there are a number of elements that are referenced by numbers that use a suffix in parentheses. For instance, there are hardware nodes101(1) through101(n), wi-fi antennas103(1) through103(n), long-range radio antennas104(1) through104(n), long-range radio connections105(1) through105(n), and wi-fi hotspots110(1) through110(n). When such elements are referred to in their entirety, they may be referred to within the suffix. For example, the terms “hardware nodes101”, “each hardware node101”, or “any hardware node101”, may be used. The same may be said of the wi-fi antennas103, the long-range radio antennas104, the long-range radio connections105, and the wi-fi hotspots110. FIG.2illustrates an emergency communication hardware node200that represents an example of how each of the hardware nodes101ofFIG.1may be structured. The hardware node200includes a wi-fi radio201for communicating with user devices using the wi-fi antenna203. The wi-fi radio antenna203is an example of each of the wi-fi radio antennas103ofFIG.1. The hardware node200also includes a long-range radio202for communicating with the emergency communications center using the long-range radio antenna204. The long-range radio antenna204is an example of each of the long-range radio antennas104ofFIG.1. The wi-fi radio201handles communication at the wi-fi physical layer in that the wi-fi radio201generates the physical signals that are transmitted via the wi-fi antenna203to the user device, and receives physical signals that are received via the wi-fi antenna203from the user device. The long-range radio202also handles communication at the physical layer, but using a long-range radio channel, in that the long-range radio202generates the physical signals that are transmitted via the long-range radio antenna204to the base station of the emergency communications center, and receives the physical signals that are received via the long-range radio antenna204from the base station of the emergency communications center. The controller205handles logic performed above the physical layer for both the long-range radio channel and the wi-fi hotspot. As an example, the controller230activates and de-activates the respective wi-fi hotspot, and potentially also provides a captive portal for any user device that connects to the wi-fi hotspot. That captive portal may be a suitable portal that allows the user to enter simple messages to be sent inbound to the emergency communications center, and presents simple messages that were sent outbound from the emergency communications center to the user device. An input port221is provided for purposes of programming the controller205. The output port222is provided for purposes of performing diagnostics on the controller205. The input port221may also be a manual control that causes the hardware node to automatically send a message to the emergency communications center over the long-range radio channel. The hardware node200also has a power supply210that is configured to operate on external power211from the power grid when the power grid is available, and operate on battery power212when the power grid is not available. The long-range radio is not a cellular radio. In one embodiment, the long-range radio consumes low power, and thus when grid power is disrupted, the hardware node continues to operate long term (for weeks or months). This may be accomplished by using a non-cellular low bandwidth protocol, such as LoRa. However, any long-range low-power radio protocol will suffice. Example characteristics of a radio protocol that consumes low power is an adaptive bitrate radio protocol that has a low maximum bitrate (e.g., of less than one megabit per second), and a low minimum bitrate (e.g., of less than one kilobit per second). Another preferred characteristic is that the radio protocol is long-range (e.g., has a maximum line-of-sight range of over one mile). FIG.3illustrates a software architecture300that may be operated by the controller205in order to perform the various functions described herein for the controller. The software architecture comprises various components. Each of those components may be structured as described below for the executable component606ofFIG.6. As an example, the software architecture300includes an access point component310that is capable of activating and deactivating a corresponding local wi-fi hotspot, broadcast the associated wi-fi network identifier, and connect to user devices that request to connect to the wi-fi network. In addition, the access point component310is configured to present the captive portal311to those user devices that connect to the associated wi-fi network. The controller intermediates inbound messages by processing inbound messages received from user device over the wi-fi network, translates those inbound messages if appropriate, and initiates transmission of the respective inbound message to the emergency communications center using the long-range radio channel. Referring toFIG.3, the software architecture300includes inbound intermediation components320including an inbound message processor321that processes inbound messages received from a user device over the wi-fi hotspot, translates the inbound message if appropriate using the inbound translation component322, and initiates transmission of the inbound message to the emergency communications center using the inbound transmission component323. Alternatively, or in addition, the controller intermediates outbound messages by processing outbound messages received from emergency communications center over long-range radio, translates those outbound messages if appropriate, determines which user device (if not all) to send the outbound message to, and initiates transmission of the respective outbound message to the user device over the wi-fi network. Referring toFIG.3, the software architecture300includes outbound intermediation components330including an outbound message processor331that processes outbound messages received from the emergency communications center over the long-range radio channel, translates the outbound message if appropriate using the outbound translation component332, determines which user device (if not all) to send the outbound communication to using the router component333, and initiates transmission of the outbound message to the user device using the outbound transmission component334. The controller also includes an emergency response component340. The emergency response component340is configured to respond to an emergency message from the emergency communications center.FIG.4illustrates a flowchart of a method400for the emergency response component to respond to the emergency message from the emergency communications center, in accordance with the principles described herein. In an example referred to herein as the “subject example”, the method400is performed by an emergency response component within the hardware node101(1) ofFIG.1in order to facilitate communication between the user device111and the emergency communications center102. However, the method400may also be performed by any of the hardware nodes in order to facilitate communication between any of their respective user devices and the emergency communications center102. The method400includes receiving an emergency message from the emergency communications center (act401). This is what triggers the emergency response component340into emergency response mode. In response, the emergency response component340causes the wi-fi access point component310to activate the local wi-fi hotspot (act402) and connects to a user device within the hotspot (act403). In the subject example, the hardware node101(1) activates the wi-fi hotspot110(1) and forms the wi-fi connection131with the user device111. At this point, if the hardware node supports inbound messaging from the user device to the emergency communications center, the inbound intermediation components320operate as previously described to facilitate the inbound messages. If the hardware node supports outbound messaging from the emergency communications center to the user device, the outbound intermediation components330operate as previously described to facilitate outbound messages. Preferably, the hardware node supports both inbound messages and outbound messages. As previously mentioned, when the wi-fi network is enabled, those user devices within the wi-fi hotspot will see that emergency wi-fi network, and may choose to connect to that wi-fi network. The emergency wi-fi network may be named so as to make very clear that the wireless network is for facilitating emergency messages during times of emergency. In addition, as previously mentioned, when the user device connects to the emergency wi-fi network, a captive portal may be presented to allow the user to receive basic low-bandwidth data (e.g., text) about the nature of the emergency, and provide controls that may be used to report low-bandwidth information back to the emergency communications center. FIG.5illustrates a mere example of a captive portal user interface500that may be displayed on the user device once the user connects to the emergency wi-fi network. The user interface includes a portion510that includes text regarding the nature of the emergency. In addition, the user might use interface elements511through516to give the emergency communications center immediate information regarding what the user is reporting, whether it be an injury, fire, leak, death, and so forth. A chat window520may also be provided to allow the user to provide some text about further details. Thus, the captive portal encourages only small amounts of data to be communicated, which is appropriate since the long-range radio protocol is low bandwidth. Thus, the captive portal user interface can be used to render messages that are communicated as an outbound communication from the emergency communications center, and can be used to create inbound communication from the user device through the emergency communication hardware node to the emergency communications center. Accordingly, the principles described herein provide a robust emergency response system which allows for the efficient gathering of emergency information from throughout the community using prolific user devices, to allow the emergency communications center to quickly assess the needs of the community. The principles described herein also allow the emergency communications center to communicate basic information to those individuals that have needs, and to coordinate with resources within the community to meet those needs. Thus, the principles described herein have great potential to preserve life, health, and meet basic needs of the community in cases of emergency. Because the principles described herein may be performed in the context of a computing system (e.g., the controller205may, but need not, be implemented by a computing system), some introductory discussion of a computing system will be described with respect toFIG.6. Computing systems are now increasingly taking a wide variety of forms. Computing systems may, for example, be handheld devices, appliances, laptop computers, desktop computers, mainframes, distributed computing systems, data centers, or even devices that have not conventionally been considered a computing system, such as wearables (e.g., glasses). In this description and in the claims, the term “computing system” is defined broadly as including any device or system (or a combination thereof) that includes at least one physical and tangible processor, and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by a processor. The memory may take any form and may depend on the nature and form of the computing system. A computing system may be distributed over a network environment and may include multiple constituent computing systems. As illustrated inFIG.6, in its most basic configuration, a computing system600includes at least one hardware processing unit602and memory604. The processing unit602includes a general-purpose processor. Although not required, the processing unit602may also include a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other specialized circuit. In one embodiment, the memory604includes a physical system memory. That physical system memory may be volatile, non-volatile, or some combination of the two. In a second embodiment, the memory is non-volatile mass storage such as physical storage media. If the computing system is distributed, the processing, memory and/or storage capability may be distributed as well. The computing system600also has thereon multiple structures often referred to as an “executable component”. For instance, the memory604of the computing system600is illustrated as including executable component606. The term “executable component” is the name for a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof. For instance, when implemented in software, one of ordinary skill in the art would understand that the structure of an executable component may include software objects, routines, methods (and so forth) that may be executed on the computing system. Such an executable component exists in the heap of a computing system, in computer-readable storage media, or a combination. One of ordinary skill in the art will recognize that the structure of the executable component exists on a computer-readable medium such that, when interpreted by one or more processors of a computing system (e.g., by a processor thread), the computing system is caused to perform a function. Such structure may be computer readable directly by the processors (as is the case if the executable component were binary). Alternatively, the structure may be structured to be interpretable and/or compiled (whether in a single stage or in multiple stages) so as to generate such binary that is directly interpretable by the processors. Such an understanding of example structures of an executable component is well within the understanding of one of ordinary skill in the art of computing when using the term “executable component”. The term “executable component” is also well understood by one of ordinary skill as including structures, such as hard coded or hard wired logic gates, that are implemented exclusively or near-exclusively in hardware, such as within a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other specialized circuit. Accordingly, the term “executable component” is a term for a structure that is well understood by those of ordinary skill in the art of computing, whether implemented in software, hardware, or a combination. In this description, the terms “component”, “agent”, “manager”, “service”, “engine”, “module”, “virtual machine” or the like may also be used. As used in this description and in the case, these terms (whether expressed with or without a modifying clause) are also intended to be synonymous with the term “executable component”, and thus also have a structure that is well understood by those of ordinary skill in the art of computing. In the description that follows, embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors (of the associated computing system that performs the act) direct the operation of the computing system in response to having executed computer-executable instructions that constitute an executable component. For example, such computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product. An example of such an operation involves the manipulation of data. If such acts are implemented exclusively or near-exclusively in hardware, such as within a FPGA or an ASIC, the computer-executable instructions may be hard-coded or hard-wired logic gates. The computer-executable instructions (and the manipulated data) may be stored in the memory604of the computing system600. Computing system600may also contain communication channels608that allow the computing system600to communicate with other computing systems over, for example, network610. While not all computing systems require a user interface, in some embodiments, the computing system600includes a user interface system612for use in interfacing with a user. The user interface system612may include output mechanisms612A as well as input mechanisms612B. The principles described herein are not limited to the precise output mechanisms612A or input mechanisms612B as such will depend on the nature of the device. However, output mechanisms612A might include, for instance, speakers, displays, tactile output, virtual or augmented reality, holograms and so forth. Examples of input mechanisms612B might include, for instance, microphones, touchscreens, virtual or augmented reality, holograms, cameras, keyboards, mouse or other pointer input, sensors of any type, and so forth. Embodiments described herein may comprise or utilize a special-purpose or general-purpose computing system including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general-purpose or special-purpose computing system. Computer-readable media that store computer-executable instructions are physical storage media. Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: storage media and transmission media. Computer-readable storage media includes RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other physical and tangible storage medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general-purpose or special-purpose computing system. A “network” is defined as one or more data links that enable the transport of electronic data between computing systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computing system, the computing system properly views the connection as a transmission medium. Transmission media can include a network and/or data links which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general-purpose or special-purpose computing system. Combinations of the above should also be included within the scope of computer-readable media. Further, upon reaching various computing system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to storage media (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a “NIC”), and then be eventually transferred to computing system RAM and/or to less volatile storage media at a computing system. Thus, it should be understood that storage media can be included in computing system components that also (or even primarily) utilize transmission media. Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general-purpose computing system, special-purpose computing system, or special-purpose processing device to perform a certain function or group of functions. Alternatively, or in addition, the computer-executable instructions may configure the computing system to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries or even instructions that undergo some translation (such as compilation) before direct execution by the processors, such as intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims. Those skilled in the art will appreciate that the invention may be practiced in network computing environments with many types of computing system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, datacenters, wearables (such as glasses) and the like. The invention may also be practiced in distributed system environments where local and remote computing system, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices. Those skilled in the art will also appreciate that the invention may be practiced in a cloud computing environment. Cloud computing environments may be distributed, although this is not required. When distributed, cloud computing environments may be distributed internationally within an organization and/or have components possessed across multiple organizations. In this description and the following claims, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). The definition of “cloud computing” is not limited to any of the other numerous advantages that can be obtained from such a model when properly deployed. For the processes and methods disclosed herein, the operations performed in the processes and methods may be implemented in differing order. Furthermore, the outlined operations are only provided as examples, and some of the operations may be optional, combined into fewer steps and operations, supplemented with further operations, or expanded into additional operations without detracting from the essence of the disclosed embodiments. The present invention may be embodied in other specific forms without departing from its spirit or characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicate by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. | 36,160 |
11943693 | DETAILED DESCRIPTION OF THE INVENTION FIG.1is a schematic block diagram of an embodiment of a computing system10that includes a plurality of user devices12, a wireless location network14, a wireless communication network16, an application server18, a network20, an information server22, and a remote application server24. The wireless location network14includes one or more of a public wireless location system (e.g., global positioning satellite (GPS), a cellular network) and one or more private wireless location systems (e.g., wireless beacon, a wireless local area network (WLAN)). The wireless location network14sends wireless location signals26to the plurality of user devices12to enable determination of location information. The wireless communications network16includes one or more of a public wireless communications system and a private wireless communications system and may operate in accordance with one or more wireless industry standards including universal mobile telecommunications system (UMTS), global system for mobile communications (GSM), long term evolution (LTE), wideband code division multiplexing (WCDMA), IEEE 802.11, IEEE 802.16. The wireless communication network16sends wireless communications signals28to the plurality of user devices12and receives wireless communications signals28from the plurality of user devices12to communicate information and application messages30. Alternatively, or in addition to, the plurality of user devices12may send and receive the wireless communications signals28directly between two or more user devices12of the plurality of user devices12. The application server18includes a processing module and memory to support execution of one or more applications (e.g., an emergency preparedness application). The processing module may be a single processing device or a plurality of processing devices. Such a processing device may be implemented with one or more of a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module may have an associated memory and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module. The memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) when the processing module includes more than one processing device, or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). The memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry when the processing module implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry. The memory element stores hardcoded and/or operational instructions and the processing module executes the hardcoded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated inFIGS.1-21. The network20may include one or more of wireless and/or wireline communications systems, one or more private communications systems, and a public internet system. The application server18communicates information and application messages30via the wireless communication network16to the plurality of user devices12and via the network20to the information server22and the remote application server24. The information server22includes a processing module and memory to support storage and retrieval of information (e.g., emergency preparedness information) via information messages32. For example, the information server22streams emergency preparedness information via the network20and the wireless communication network16to one or more of the user devices12. As another example, information server22sends emergency preparedness information to user device12in response to receiving a request for emergency preparedness information from the user device12. The remote application server24includes a processing module and memory to support execution of one or more applications (e.g., the emergency preparedness application). For example, the remote application server24sends an application output response message as an application message34to the user device12in response to receiving an application request as the application message34from the user device12. The plurality of user devices12may be a portable computing device (e.g., a smart phone, a tablet computer, a laptop a handheld computer and/or any other portable device that includes a computing unit) and/or a fixed computing device (e.g., a desktop computer, a cable television set-top box, an application server, an internet television user interface and/or any other fixed device that includes a computing unit). Such a portable or fixed computing device includes one or more of a computing unit (e.g., providing processing module functionality), one or more wireless modems, sensors, and one or more user interfaces. An embodiment of the user device12will be described in greater detail with reference toFIG.2. In general and with respect to emergency preparedness, the system10supports three primary functions: emergency preparedness planning, emergency preparedness drilling, and response phase emergency communications. In accordance with these three primary functions, emergency preparedness plans can be created that are relevant in relationship to likely emergency scenarios and those affected, the emergency preparedness plans can be exercised by way of drilling and training to enable more efficient operations during an emergency response phase, and communications can be provided during an emergency response that is efficient in terms of mitigation resource utilization and relevant in terms of scope and nature of an associated emergency scenario. The first primary function includes the user device determining emergency preparedness planning information. In an example of operation, the user device12determines location information based on receiving the wireless location signals26. Next, the user device12sends a checklist request message that includes the location information to the application server18as wireless communications signals28via the wireless communications network16. The application server18determines recommended checklists based on the location information to produce recommended checklists (e.g., a hurricane checklist, a tornado checklist, etc.). For instance, the application server18determines the recommended checklists to include the hurricane checklist and the tornado checklist when the location information indicates that the user device is located in central Florida. As another instance, the application server18determines the recommended checklists to include an earthquake checklist and a wildfire checklist when the location information indicates that the user device is located in Southern California. The application server18sends the recommended checklists to the user device12. The user device12displays the recommended checklists and receives user input to produce a selected checklist. The user device12sends the selected checklist to the application server18. The application server18determines selected checklist information based on the selected checklist. The application server18sends the selected checklist information to the user device12. The user device12displays the selected checklist information and receives user input. The user device12modifies checklist item availability status to produce modified checklist item availability status. The user device12stores the modified checklist item availability status and may send the modified checklist item availability status to the application server18and/or the information server22. In addition, the user device12may produce a checklist item reminder (e.g., a visual and audible alert) in accordance with a checklist alert schedule when the modified checklist item availability status compares unfavorably to a checklist item availability template. The method of operation to determine emergency preparedness planning information is discussed in greater detail with reference toFIGS.3A-21. The second primary function includes the user device12participating in emergency preparedness drilling. In an example of operation, the user device12obtains location information and other context information (e.g., including a drill schedule) to produce a context bundle. The user device12sends a drill request message to the remote application server24that includes the context bundle. The remote application server24determines drill parameters (e.g., a drill scenario) and a drill identifier (ID) based on the drill request message. For instance, the remote application server24determines the drill scenario to be a hurricane drill based on the location information indicating that the user device12is near the Atlantic Ocean. As another instance, the remote application server24determines the drill scenario to be an earthquake drill based on the location information indicating that the user device12is near an earthquake fault line. The remote application server24sends the drill parameters and the drill ID to the user device12. The remote application server24initializes a drill application associated with the drill ID and in accordance with the drill parameters. The remote application server24sends a drill update message to the user device12that includes drill application output associated with the drill application. The user device12receives the drill update message and sends the drill application output to a display associated with the user device. The user device12receives user input to produce drill input information. The user device12sends a drill input message to the remote application server24that includes the drill input information. The remote application server24receives the drill input message and provides the drill application with the drill input information to produce updated drill application output. The remote application server24sends a second drill update message to the user device12that includes the updated drill application output. The process repeats until the application reaches an end point. The method of operation to participate in drilling is discussed in greater detail with reference toFIGS.3A-21. The third primary function includes the user device12communicating during an emergency response phase. In an example of operation, the user device12obtains location information and other context information (e.g., including a group ID affiliation) to produce the context bundle. The user device12obtains local status (e.g., ok, getting help, need help, etc.) via a user prompt. Next, the user device12sends a status request message to the application server18that includes the local status and the context bundle. The application server18receives the status request message and determines a status associated with each user device12affiliated with the group ID. For instance, the application server18sends a status request message to the other user devices12affiliated with the group ID and receives status response messages indicating status. The application server18sends a status response message that includes status information of the other user devices12affiliated with the group ID to the user device. The user device12receives the status response message and displays the status information in accordance with the context bundle. For instance, the user device12displays names associated with the other user devices12and utilizes a colored icon to indicate status of the other user device (e.g., red for not okay, green for okay). As another instance, the user device12displays names associated with the other user devices in a rank ordered list where the ranking is by relative distance away from the user device12as determined utilizing status information associated with the other user devices12. As another instance, the user device12displays the names associated with the other user devices12on a map where in the center of the map is a location associated with the user device12. The method of operation to communicate is discussed in greater detail with reference toFIGS.3A-21. FIG.2is a schematic block diagram of an embodiment of a user device12that includes a user interface output40, a user interface input42, a sensor44, a computing unit46, a wireless communications modem48, and a wireless location modem50. The user interface output40may be a single interface output device or a plurality of interface output devices. The interface output device40may include one or more of a display, a touch screen, a speaker, an earpiece, a motor, an indicator light, a transducer, and a digital indicator. For instance, the interface output device40includes a color touch screen display capable of rendering static images and/or full-motion video. The user interface input42may be a single interface input device or a plurality of interface input devices. The interface input device includes one or more of a touch screen sensor array, a keyboard, a microphone, a fingerprint reader, a trackball, a mouse sensor, a pushbutton, and a selector switch. For instance, the interface input device includes a touch screen sensor array associated with the color touch screen display. The sensor44may be a single sensor device or a plurality of sensor devices. The sensor device includes capabilities for sensing one or more of a magnetic field (e.g., a compass), motion, temperature, pressure, altitude, humidity, an image, a stream of images (e.g., capture video), biometrics, proximity, capacitance, gases, radiation, pathogens, light levels, and bio hazards. The wireless communications modem48may include a single wireless transceiver or a plurality of wireless transceivers. The wireless transceiver may operate in accordance with one or more wireless industry standards including universal mobile telecommunications system (UMTS), global system for mobile communications (GSM), long term evolution (LTE), wideband code division multiplexing (WCDMA), IEEE 802.11, IEEE 802.16. The wireless location modem50may include one or more of a single wireless location receiver, a single wireless location transceiver, a plurality of wireless location receivers, and a plurality of wireless location transceivers. The wireless location receiver and wireless location transceiver may operate in accordance with one or more wireless location technologies including GPS, Wi-Fi, angle of arrival, time difference of arrival, signal strength, and beaconing. The computing unit46includes an application processing module52, a memory54one or more interfaces to one or more of the user interface output40, user interface input42, the sensor44, the wireless communication modem48, and the wireless location modem50. The memory54may include a single memory device or a plurality of memory devices. The memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, cache memory, and/or any device that stores digital information. Memory device examples include static random access memory (SRAM), dynamic random access memory (DRAM), NAND flash memory, magnetic memory (e.g., a hard disk), and optical memory (e.g., an optical disc). The application processing module52may be a single processing device or a plurality of processing devices. The processing device may include one or more of a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The application processing module52may have an associated memory and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the application processing module. The memory device54include one or more of a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) when the application processing module includes more than one processing device, or the processing devices may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). The memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry) when the application processing module implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry. The memory element stores hard coded and/or operational instructions and the application processing module executes the hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated inFIGS.3A-21. FIG.3Ais a display rendering illustrating an example of a home screen62generated by an emergency preparedness application executing on an application processing module. The home screen62may be utilized to indicate emergency preparedness application options and to prompt for user input to execute one or more portions of the emergency preparedness application. The home screen62includes one or more of a set of soft keys and a user device status area60including one or more of a battery indicator level, a date, a time of day, a wireless location status indicator, and a wireless communication signal strength indicator. The set of soft keys includes one or more of a setup64, a plan66, information68, communicate70, and drill72. A method of operation of the application processing module is discussed in greater detail with reference toFIGS.4-21. FIG.3Bis a display rendering illustrating an example of a setup screen74generated by an emergency preparedness application executing on an application processing module. The setup screen74may be utilized to indicate emergency preparedness application options in regards to set up and to prompt for user input to gather setup information and to execute one or more portions of the emergency preparedness application. The setup screen74includes one or more of a set of soft keys and a user device status area60. The set of soft keys includes one or more of group76, individuals80, privacy82, credentials84, and feeds86. A method of operation of the application processing module is discussed in greater detail with reference toFIGS.4-7. FIG.3Cis a display rendering illustrating an example of a planning screen88generated by an emergency preparedness application executing on an application processing module. The planning screen88may be utilized to indicate emergency preparedness application options in regards to planning and to prompt for user input to gather planning information and to execute one or more portions of the emergency preparedness application. The planning screen88includes one or more of a set of soft keys and a user device status area60. The set of soft keys includes one or more of tutorials90, checklists92, resources94, scenarios96, and schedules98. A method of operation of the application processing module is discussed in greater detail with reference toFIGS.8-12. FIG.3Dis a display rendering illustrating an example of an information screen100generated by an emergency preparedness application executing on an application processing module. The information screen100may be utilized to indicate emergency preparedness application options in regards to information and to prompt for user input to gather information and to execute one or more portions of the emergency preparedness application. The information screen100includes one or more of a set of soft keys and a user device status area60. The set of soft keys includes one or more of environment102, local events104, national events106, live feeds108, and search110. A method of operation of the application processing module is discussed in greater detail with reference toFIGS.13-15. FIG.3Eis a display rendering illustrating an example of a communication screen112generated by an emergency preparedness application executing on an application processing module. The communication screen112may be utilized to indicate emergency preparedness application options in regards to communication and to prompt for user input to communicate and to execute one or more portions of the emergency preparedness application. The communication screen112includes one or more of a set of soft keys and a user device status area60. The set of soft keys includes one or more of top issues114, group status116, individual status118, messaging120, and send help122. A method of operation of the application processing module is discussed in greater detail with reference toFIGS.16-18. FIG.3Fis a display rendering illustrating an example of a drill screen124generated by an emergency preparedness application executing on an application processing module. The drill screen124may be utilized to indicate emergency preparedness application options in regards to drilling and to prompt for user input to drill and to execute one or more portions of the emergency preparedness application. The drill screen124includes one or more of a set of soft keys and a user device status area60. The set of soft keys includes one or more of schedules126, initiate128, participate130, monitor132, and tutorial134. A method of operation of the application processing module is discussed in greater detail with reference toFIGS.19-21. FIG.4is a flowchart illustrating an example of obtaining identification information. A method begins with step140where a processing module (e.g., an application processing module of a user device) obtains a temporary set of group information, wherein group information pertains to a group identifier (ID), and wherein the group ID is associated with a corresponding set of individual identifiers (IDs) of a plurality of individual IDs. The group information may include one or more of a group ID, a group name, a geographic region associated with a group ID, a context association with a group ID, and contact information. A group ID may be associated with a group type, wherein the group type may include one or more of a family, friends, a workgroup, a company a community organization, a neighborhood, a city, a region, a club, a common interest, and any other affiliating commonality. Each individual ID of the plurality of individual IDs may not be associated with at least one group ID. The obtaining the temporary set of group information further includes determining context information and identifying a set of group IDs of the temperate set of group information based on the context information. The context information includes one or more of location coordinates, current weather conditions, forecasted weather conditions, a sensor input, date information, time information, a current activity, a scheduled activity, a current event, and a scheduled event. The determining the context information includes at least one of querying an application server, receiving a message, a local memory lookup, receiving an input device output, receiving a user device sensor output, and decoding wireless location signals to produce location coordinates. For example, the processing module obtains the temporary set of group information to include group ID54when location coordinates associated with group ID54are substantially the same as location coordinates of the context information. Alternatively, or in addition to, the obtaining the temporary set of group information includes at least one of receiving at least some of the temporary set of group information from a user input and retrieving the temporary set of group information. The receiving includes facilitating outputting a user prompt that includes at least some of the context information and receiving a group ID selection in a user response. The retrieving includes generating a group ID request that includes at least some of the context information; sending the group ID request to at least one of an information server, an application server, and another user device; and receiving a group ID response that includes a group ID. The method continues at step142where the processing module obtains at least one set of individual information, wherein individual information pertains to an individual ID of the plurality of individual IDs. The individual information includes one or more of an individual ID, an individual ID that is not associated with the temporary set of group information, an individual name, a geographic region associated with an individual ID, and contact information. The contact information may include one or more of a voice telephone number, a short message service (SMS) telephone number, an internet protocol (IP) address, an email address, a uniform resource locator (URL), and a facsimile (FAX) telephone number. The obtaining the at least one set of individual information includes receiving at least some of the at least one set of individual information from a user input and retrieving the at least one set of individual information. Alternatively, or in addition to, the obtaining the at least one set of individual information further includes obtaining (e.g., retrieving, generating) context information and identifying (e.g., receiving, and retrieving) an individual ID of the at least one set of individual information based on the context information. The method continues at step144where the processing module obtains a set of group information associated with the at least one set of individual information based on the temporary set of group information. All individual IDs of the at least one set of individual information are associated with at least one group ID. The obtaining the set of group information associated with the at least one set of individual information includes at least one of outputting a user prompt that includes at least some of the temporary set of group information, extracting at least some of the temporary set of group information from a user input, and receiving a group ID selection user input that includes at least some of the temporary set of group information. Alternatively, or addition to, the obtaining the set of group information associated with the at least one set of individual information further includes generating a group information request based on the at least one set of individual information, facilitating outputting the group information request (e.g., to at least one of an information server, an application server, and another user device), and receiving a group information response that includes at least some of the temporary set of group information. The method continues at step146where the processing module facilitates storage of one or more of context information associated with the temporary set of group information, at least some of the temporary set of group information, at least some of the at least one set of individual information, and at least some of the group information. The method continues at step148where the processing module facilitates displaying one or more individual IDs of the at least one set of individual information. FIG.5is a flowchart illustrating an example of obtaining credential information. A method begins at step150where a processing module (e.g., an application processing module of a user device) sends a credentials request message. The processing module may send the credentials request message by one or more of sending the message to a user interface output (e.g., a display), sending a message to another user device, sending the message to a user device memory, sending a message to an information server, sending a message to an application server, and sending the message to a remote application server. The credentials may include one or more of a user name, user access rights, a user title, a user role, user responsibilities, a password, an encryption key, user attributes, user capabilities, user certifications, a user training list, a user history, user limitations, user device attributes, and a user geographic location affiliation. The method continues at step152where the processing module receives credentials information. The processing module may receive the credentials information from at least one of a user interface input (e.g., a touchscreen/keyboard), the user device memory, the another user device, the application server, the information server, and the remote application server. The method continues at step154where the processing module stores the credentials information (e.g., in the user device memory, by sending the credentials information to one or more of the application server, the information server, and the remote application server). The method continues at step156where the processing module selects credentials information to produce selected credentials information. The selection may be based on one or more of context information (e.g., location and a current event), a credentials type list, a desired credentials list, a credentials type, and a message. For example, the processing module selects the role credential when the role credential type substantially matches a credential list and wherein location information indicates a favorable proximal location to an event. The method continues at step158where the processing module transforms selected credentials information to produce registration information. The registration information may include one or more of an individual identifier (ID), the selected credentials information, and the desired credentials. The method continues at step160where the processing module determines a registration entity (e.g., a registration server, a registration application running on the application server, the registration application running on the remote application server, the registration application running on another user device). The determination may be based on one or more of the registration information, a registration entity list, and a registration entity ID associated with the desired credentials. The method continues at step162where the processing module sends the registration information to the registration entity. The method continues at step164where the processing module processes a registration response message from the registration entity. The processing module processes the registration response message by one or more of storing confirmation information in the user device memory, adding a new credential to a credential list, modifying an existing credential, storing a security signature, storing a new password, and storing a new encryption key. The above described extraction process may provide an efficiency improvement in an emergency response phase whereby an individual is automatically enabled to participate in a role acceptable to a group or authority associated with an emergency event. For instance, a volunteer certified in cardiopulmonary resuscitation (CPR) is automatically enabled to assist authorities at the scene of the emergency event. FIG.6is a flowchart illustrating an example of obtaining privacy information. A method begins with step166where a processing module (e.g., an application processing module of a user device) sends a privacy information request message. The processing module may send the privacy information request message by one or more of sending the message to a user interface output (e.g., a display), sending a message to another user device, sending the message to a user device memory, sending a message to an information server, sending a message to an application server, and sending the message to a remote application server. The privacy information may include one or more of which personal information to never disclose, which information to disclose to individuals affiliated with a plurality of groups, which information to disclose to selected individuals, and which information to disclose to anyone. The personal information may include one or more of a capability, a role, time availability, location availability, location sharing, group affiliations, user device attributes, encryption keys, passwords, signatures, and any other credentials information. The method continues at step168where the processing module receives the privacy information and sorts the privacy information to produce sorted privacy information. The sorting may be based on one or more of a sorting priority, a message, a command, a user input, and context information (e.g., location of an emergency event). For example, the processing module sorts the privacy information such that user capabilities are never shared when the processing module determines the context information does not include a location indicator of any emergency event within a location threshold of a current location indicator. As another example, the processing module sorts the privacy information such that user capabilities are shared when the processing module determines the context information does include a location indicator of an emergency event within the location threshold of the current location indicator. The method continues at step170where the processing module stores the sorted privacy information (e.g., in the user device memory, the application server, the information server, the remote application server). The method continues at step172where the processing module identifies shared information based on the sorted privacy information. For example, the processing module determines shared information when an information type associated with the shared information substantially matches an information type associated with the sorted privacy information. For instance, the processing module identifies location information when the sorted privacy information includes sharing the location information type. The method continues at step174where the processing module enables access to the shared information based on the identified shared information. The enabling may include one or more of updating a status indicator, setting a flag, and moving the shared information to a shared information memory. Subsequent requests for information contained within the shared information result in responses including the shared information. The method continues at step176where the processing module identifies non-shared information based on the sorted privacy information. For example, the processing module determines non-shared information when the information type associated with the shared information does not match the information type associated with the sorted privacy information. For instance, the processing module identifies certification information when the sorted privacy information does not include sharing the certification information type. The method continues at step178where the processing module disables access to the non-shared information based on the identified non-shared information. The disabling may include one or more of updating a status indicator, setting a flag, and moving the non-shared information to a non-shared information memory. Subsequent requests for information contained within the non-shared information result in responses that do not include the non-shared information. FIG.7is a flowchart illustrating an example of obtaining feeds information. A method begins with step180where a processing module (e.g., an application processing module of a user device) obtains context information, association information, and credentials information. Alternatively, the processing module may obtain the context information, the association information, and the credentials information by one or more of an application server query, and information server query, a remote application query, the user device query, and a user device memory lookup. The method continues at step182where the processing module determines available feeds. The available feeds includes feed identifiers (IDs) associated with one or more information streams (e.g., text streams, audio streams, picture streams, video streams, multimedia streams, etc.). For instance, a weather information stream is associated with a first feed ID. As another instance, an emergency event information stream associated with a second feed ID. The determination of available feeds may be based on one or more of an application server query, an information server query, a remote application server query, a feed stream, a list, and a message. The method continues at step184where the processing module determines recommended feeds based on the context information. The determination may be based on one or more of a favorable comparison of available feeds to one or more of the context information, the association information, and the credentials information. Recommended feeds include a subset of the available feeds, wherein recommended feeds may include a favorable relationship. As an example, the processing module determines a recommended feed to include a weather information stream when the context information indicates proximal location to a severe weather system. As another example, the processing module determines the recommended feed to include a train derailment emergency event information stream when the context information indicates proximal location to a train derailment and the credentials information indicates a favorable emergency response credential. The method continues at step186where the processing module sends a feeds information request message that includes the recommended feeds. For example, the processing module sends the information request message such that the recommended feeds are indicated on a user device display. Alternatively, or in addition to, the processing module sends the feeds information request message that includes the recommended feeds and the available feeds. The method continues at step188where the processing module receives selected feeds information (e.g., from a user interface input, from an application server, from an information server). For example, the processing module receives the selected feeds information via a user device touchscreen input. The method continues at step190where the processing module stores the selected feeds information (e.g., in a user device memory, in an application server, and an information server). The method continues at step192where the processing module facilitates receiving an information feed based on the selected feeds information. The facilitation may include one or more of sending a subscription request message to an information server, receiving a subscription response message from the information server, receiving an information stream, and extracting the information feed from the information stream. Alternatively, or in addition to, the processing module displays a portion of the information feed on a user interface output (e.g., a color display). The method continues at step194where the processing module facilitates storing information feed (e.g., in the user device memory, sending a storage message to an application server, sending the information feed to the information server). FIG.8is a flowchart illustrating an example of selecting a tutorial. A method begins with step196where a processing module (e.g., an application processing module of a user device) obtains context information, association information, credentials information, and an information feed. Alternatively, the processing module may obtain the information feed by one or more of an application server query, and information server query, a remote application query, the user device query, and a user device memory lookup. The method continues at step198where the processing module determines available tutorials. Available tutorials includes tutorial identifiers (IDs) associated with one or more tutorials. For instance, an earthquake tutorial is associated with a first tutorial ID. As another instance, a hurricane tutorial is associated with a second tutorial ID. The determination of available tutorials may be based on one or more of an application server query, an information server query, a remote application server query, a feed stream, a list, and a message. The method continues at step200where the processing module determines recommended tutorials based on the context information. The determination may be based on one or more of a favorable comparison of available tutorials to one or more of the context information, the association information, the credentials information, and information within the information feed (e.g., an earthquake alert, a hurricane alert). Recommended tutorials include a subset of the available tutorials, wherein recommended tutorials may include a favorable relationship. For example, the processing module determines a recommended tutorial to include the earthquake tutorial when the context information indicates proximal location to an earthquake fault line. As another example, the processing module determines the recommended tutorial to include the hurricane tutorial when the context information indicates proximal location to a hurricane event and the credentials information indicates a favorable emergency response credential. The method continues at step202where the processing module sends a selected tutorials request message that includes the recommended tutorials. For example, the processing module sends the selected tutorials request message such that the recommended tutorials are indicated on a user device display. Alternatively, or in addition to, the processing module sends the selected tutorials request message that includes the recommended tutorials and the available tutorials. The method continues at step204where the processing module receives selected tutorial information (e.g., from a user interface input, from an application server, from an information server). For example, the processing module receives the selected tutorial information via a user device touchscreen input. The method continues at step206where the processing module facilitates initializing a tutorial based on the selected tutorial information. The facilitation may include one or more of sending a tutorial request message to an information server, receiving a tutorial response message from the information server, extracting the tutorial from the response message, and initializing the tutorial. The processing module may display tutorial information of the tutorial on the user interface output. The method continues at step208where the processing module modifies the tutorial based on one or more of the context information, the association information, the credentials information, and the information feed. For example, the processing module skips portions of the tutorial plan location information of the context information compares unfavorably to a proximal location indicator. For instance, the processing module skips a portion of the tutorial affiliated with cooler climates when the proximal location indicates a warmer climate. As another example, the processing module adds a portion of the context information to the tutorial. For instance, the processing module adds the location information to the tutorial and calculates geographic relationships of one or more locations cited in the tutorial with the location information. FIG.9is a flowchart illustrating an example of selecting a checklist, which include similar steps toFIG.8. The method begins with step196ofFIG.8where a processing module (e.g., an application processing module of a user device) obtains context information, association information, credentials information, and an information feed. The method continues at step210where the processing module determines available checklists. The available checklists includes checklist identifiers (IDs) associated with one or more checklists. For example, a home checklist is associated with a first checklist ID. As another example, a workplace checklist is associated with a second checklist ID. The determination of available checklists may be based on one or more of an application server query, an information server query, a remote application server query, a feed stream, a list, and a message. The method continues at step212where the processing module determines recommended checklists based on the context information. The determination may be based on one or more of a favorable comparison of available checklists to one or more of the context information, the association information, the credentials information, and information within the information feed (e.g., a tornado alert, a wildfire alert). The recommended checklists include a subset of the available checklists, wherein recommended checklists may include a favorable relationship. For example, the processing module determines the recommended checklists to include a tornado checklist when the context information indicates proximal location to a geographic area with a history of frequent tornadoes. As another example, the processing module determines the recommended checklists to include a wildfire checklist when the information feed indicates a wildfire event within a proximal location threshold and the credentials information indicates a favorable emergency response credential. The method continues at step214where the processing module sends a selected checklists request message that includes the recommended checklists. For example, the processing module sends the selected checklists request message such that the recommended checklists are indicated on a user device display. Alternatively, or in addition to, the processing module sends the selected checklists request message that includes the recommended checklists and the available checklists. The method continues at step216where the processing module receives selected checklists information (e.g., from a user interface input, from an application server, from an information server). For example, the processing module receives the selected checklists information from a speech recognition algorithm utilizing a user device microphone input. The checklists information may include one or more of emergency preparedness items (e.g., food, water, clothing, tools, etc.), contacts, rally points, resources, associated tutorial IDs, and certification items. The method continues at step218where the processing module facilitates initializing a checklist session based on the selected checklists information. The facilitation may include one or more of sending a checklist request message to an information server, receiving a checklist response message from the information server, extracting a checklist from the response message, and initializing the checklist session. The processing module may display checklist information of the checklist on the user interface output. The method continues at step220where the processing module modifies the checklist based on one or more of the context information, the association information, the credentials information, and the information feed. For example, the processing module skips portions of the checklist session when the context information compares unfavorably to a proximal location indicator. For instance, the processing module skips a portion of the checklist affiliated with water emergencies when the proximal location indicates no water nearby. As another example, the processing module adds a portion of the context information to the checklist. For instance, the processing module adds the location information to the checklist and calculates geographic relationships of one or more locations (e.g., resource locales) cited in the checklist with the location information. FIG.10is a flowchart illustrating an example of selecting resources. A method begins with step222where a processing module (e.g., an application processing module of a user device) obtains context information, association information, credentials information, checklists, and an information feed. Alternatively, or in addition to, the processing module may retrieve checklists from one or more of a user device memory, an application server, and information server, and a remote application server. The method continues at step224where the processing module determines available resource lists. The available resource lists includes resource list identifiers (IDs) associated with one or more resource lists. For instance, a city resource list is associated with a first resource list ID. As another instance, a county resource list is associated with a second resource list ID. The determination of available resource lists may be based on one or more of a user device query, the application server query, the information server query, the remote application server query, a feed stream, a list, and a message. The method continues at step226where the processing module determines recommended resource lists based on the context information. The determination may be based on one or more of a favorable comparison of the available resource lists to one or more of the context information, the association information, the credentials information, content of the checklists, and information within the information feed (e.g., a winter storm alert, a high wind advisory). The recommended resource lists includes a subset of the available resource lists, wherein recommended resource lists may include a favorable relationship. For example, the processing module determines a recommended resource list to include a winter storm resource list when the context information indicates proximal location to a geographic area with a history of severe winter storms. As another example, the processing module determines the recommended resource lists to include a high wind resource list when the information feed indicates a high wind event within a proximal location threshold and the credentials information indicates a favorable emergency response credential. The method continues at step228where the processing module sends a selected resource list request message that includes the recommended resource lists. For example, the processing module sends the selected resource list request message such that the recommended resource lists are indicated on a user device display. Alternatively, or in addition to, the processing module sends the selected resource list request message that includes the recommended resource lists and the available resource lists. The method continues at step230where the processing module receives selected resource list information (e.g., from a user interface input, from the application server, from the information server). For example, the processing module receives the selected resource list information from an information server associated with location information. The resource list information may include one or more of emergency response phase assets and/or emergency recovery phase assets (e.g., heavy equipment, vehicles, construction materials, tools, etc.), leadership contacts, staging area locations, training drill sites, funding sources, federal government contacts, state government contacts, local government contacts, industry contacts, and phase assignment roles. The method continues at step232where the processing module facilitates initializing a resource list review session based on the selected resource list information. The facilitation may include one or more of sending a resource list request message to an information server, receiving a resource list response message from the information server, extracting a resource list from the response message, and initializing the resource list review session. The processing module may display resource list information of the resource list on the user interface output. The method continues at step234where the processing module modifies the resource list based on one or more of the context information, the association information, the credentials information, and the information feed. For example, the processing module skips portions of the resource list review session when the context information compares unfavorably to a proximal location indicator. For instance, the processing module skips a portion of the resource list review session affiliated with ice rescue emergencies when the proximal location indicates no freezing temperatures nearby. As another example, the processing module adds a portion of the context information to the resource list review session. For instance, the processing module adds the location information to the resource list and calculates geographic relationships of one or more locations (e.g., resource locales) cited in the resource list with the location information. Alternatively, or in addition to, the processing module may receive resource list modification inputs from a user device input and update the resource list accordingly. Next, the processing module sends the updated resource list to one or more of another user device (e.g., seeking and/or providing resources), the information server (e.g., to post resource needs), and the application processor (e.g., to modify a resource list and context association). FIG.11is a flowchart illustrating an example of determining scenarios information. A method begins with step236where a processing module (e.g., an application processing module of a user device) obtains context information, association information, credentials information, checklists, resource lists, and an information feed. Alternatively, or in addition to, the processing module may retrieve the resource lists from one or more of a user device memory, an application server, an information server, and a remote application server. The method continues at step238where the processing module determines a possible scenarios list. The possible scenarios list includes scenario identifiers (IDs) associated with one or more scenarios associated with the possible scenario list. For instance, a send help scenario is associated with a first scenario ID. As another instance, a severe weather scenario is associated with a second scenario ID. The determination of the possible scenarios list may be based on one or more of a user device query, the application server query, the information server query, the remote application server query, a feed stream, a list, and a message. The method continues at step240where the processing module determines recommended scenarios based on the context information. The determination may be based on one or more of a favorable comparison of the possible scenarios list to one or more of the context information, the association information, the credentials information, content of the checklists, resources of the resource list, and information within the information feed (e.g., a crime alert, a school lockdown). Recommended scenarios include a subset of the possible scenarios list, wherein recommended scenarios may include a favorable relationship. For example, the processing module determines the recommended scenarios to include a send help scenario when the context information indicates proximal location to a geographic area with a history of violent crime. As another example, the processing module determines the recommended scenarios to include a school lockdown scenario when the information feed indicates a school lockdown event within a proximal location threshold and the credentials information indicates a favorable school affinity. The method continues at step242where the processing module sends a selected scenarios information request message that includes the recommended scenarios. For example, the processing module sends the selected scenarios information request message such that the recommended scenarios are indicated on a user device display. Alternatively, or in addition to, the processing module sends the selected scenarios information request message that includes the recommended scenarios and the possible scenarios list. The method continues at step244where the processing module receives selected scenarios information (e.g., from a user interface input, from the application server, from the information server). For example, the processing module receives the selected scenarios information from an information server associated with location information. The selected scenarios information includes scenario references and/or scenario descriptions (e.g., during a planning phase, a response phase, a recovery phase), scenario triggers, and responsive actions. As an example, a send help scenario includes a user input scenario trigger and a responsive action that includes sending a help message to a list of help target IDs. As another example, an extreme weather scenario includes a weather service alert input scenario trigger and a responsive action that includes selecting a checklist and tutorial associated with a weather alert type of an associated weather service alert. As yet another example, an earthquake scenario includes a state government earthquake alert input scenario trigger and a responsive action that includes selecting a group ID (e.g., a family ID) to determine and share status and location information. The method continues at step246where the processing module facilitates initializing a scenarios review session based on the selected scenarios information. The facilitating may include one or more of sending a scenarios information request message to an information server, receiving a scenarios information response message from the information server, extracting scenarios information from the response message, and initializing the scenarios review session. The processing module may display scenarios information on the user interface output. The method continues at step248where the processing module modifies the scenarios information based on one or more of the context information, the association information, the credentials information, the resources information, and the information feed. For example, the processing module skips portions of the scenarios review session when the context information compares unfavorably to a proximal location indicator. For instance, the processing module skips a portion of the scenarios review session affiliated with earthquake emergencies when the proximal location indicates few or no earthquake fault lines nearby. As another example, the processing module adds a portion of the context information to the scenarios review session. For instance, the processing module adds the location information to the scenarios information and calculates geographic relationships of one or more locations (e.g., help resources) cited in a resource list associated with a scenario. Alternatively, or in addition to, the processing module may receive scenario information modification inputs from a user device input and update the scenario information accordingly. Next, the processing module sends the updated scenario information to one or more of another user device, the information server (e.g., to download later), and the application processor (e.g., to modify a scenario list and context association). FIG.12is a flowchart illustrating an example of determining schedules information. A method begins with step250where a processing module (e.g., an application processing module of a user device) obtains context information, association information, credentials information, checklists, resource lists, scenarios information, and an information feed. Alternatively, or in addition to, the processing module may retrieve the scenarios information from one or more of a user device memory, an application server, an information server, and a remote application server. The method continues at step252where the processing module determines a possible schedules list. The possible schedules list includes schedule identifiers (IDs) associated with one or more schedules associated with the possible schedules list. For instance, a drill schedule is associated with a first schedule ID. As another instance, a tutorial schedule is associated with a second schedule ID. As yet another instance, a checklist refresh schedule is associated with a third schedule ID. As a still further instance, a resource list refresh schedule is associated with a fourth schedule ID. The determining of the possible schedules list may be based on one or more of a user device query, the application server query, the information server query, the remote application server query, a feed stream, a list, and a message. The method continues at step254where the processing module determines recommended schedules to update based on the context information. The determining may be based on one or more of a favorable comparison of the possible schedules list to one or more of the context information, the association information, the credentials information, content of the checklists, resources of the resource list, scenarios of the scenarios information, and information within the information feed (e.g., a drill alert, a new tutorial announcement). The recommended schedules include a subset of the possible schedules list, wherein recommended schedules may include a favorable relationship. For example, the processing module determines the recommended schedules to include a drill schedule when the context information indicates proximal location to a government authority hosting an upcoming drill. As another example, the processing module determines the recommended schedules to include a scenarios update schedule when the information feed indicates an upcoming resource planning event within a proximal location threshold and the credentials information indicates a favorable credential with respect to the resource planning event. The method continues at step256where the processing module sends an update schedule information request message that includes the recommended schedules. For example, the processing module sends the update schedule information request message such that the recommended schedules are indicated on a user device display. Alternatively, or in addition to, the processing module sends the update schedule information request message that includes the recommended schedules and the possible schedules list. The method continues at step258where the processing module receives selected schedules information (e.g., from a user interface input, from the application server, from the information server). For example, the processing module receives the selected schedules information from an information server associated with drill schedules information. The selected schedules information includes schedule references and/or schedule descriptions (e.g., during a planning phase, a response phase, a recovery phase). As an example, the processing module receives the selected schedules information including a checklist update schedule reference. The method continues at step260where the processing module facilitates initializing a scheduling session based on the selected schedule information. The facilitating may include one or more of sending a schedules information request message to an information server, receiving a schedules information response message from the information server, extracting schedules information from the response message, and initializing the scheduling session. The processing module may display schedules information via the user interface output. The method continues at step262where the processing module modifies the schedules information based on one or more of the context information, the association information, the credentials information, the resources information, the scenarios information, and the information feed. For example, the processing module skips portions of the scheduling session when the context information compares unfavorably to a proximal location indicator. For instance, the processing module skips a portion of the scheduling session affiliated with drills when the proximal location indicates few or no earthquake fault lines nearby. As another example, the processing module adds a portion of the context information to the scheduling information. For instance, the processing module adds the location information to the scheduling information and calculates geographic relationships of one or more locations (e.g., participating drill authorities) cited in a drill schedule associated with a schedule. Alternatively, or in addition to, the processing module may receive schedule information modification inputs from a user device input and update the scheduling information accordingly. Next, the processing module sends the updated scheduling information to one or more of another user device, the information server (e.g., to download later), and the application processor (e.g., to modify a possible schedules list and context association). FIG.13is a flowchart illustrating an example of determining environmental information. A method begins with step264where a processing module (e.g., an application processing module of a user device) obtaining context information, association information, credentials information, checklists, resource lists, scenarios information, schedule information, and an information feed. Alternatively, or in addition to, the processing module may retrieve the schedule information from one or more of a user device memory, an application server, an information server, and a remote application server. The method continues at step266where the processing module determines a region based on group location. The region specifies a geographic area associated with a group. For example, the region is a circle wherein the circle is specified by coordinates (e.g., longitude and latitude) of a center location and a radius distance from the center location. As another example, the region is specified by an arbitrary boundary around the region (e.g., a continuum of longitude and latitude coordinates). As yet another example, the region is specified by a governmental jurisdiction (e.g., one or more city blocks, one or more neighborhoods, one or more cities, one or more counties, one or more states). The determining of the region may be based on one or more of determining individuals affiliated with the group, obtaining individual location information associated with at least some individuals affiliated with the group, and determining the region based on the individual location information. For example, the processing module determines the individuals associated with the group based on a group affiliation table lookup in a user device memory. Next, the processing module sends an individual location information request message to user devices associated with at least some of the individuals associated with the group. The processing module receives a plurality of individual location information response messages to produce a plurality of individual location information. The processing module determines the region such that the region encompasses the plurality of individual location information. The method continues at step268where the processing module determines weather information based on the region. The weather information may include one or more of current weather conditions, weather forecasts, weather alerts, weather advisories, weather history, and a weather dictionary. The determining may be based on one or more of the region, a query to one or more weather information servers, receiving an internet broadcast, receiving a wireless broadcast. For example, the processing module sends a weather information request message to the weather information server wherein the weather information request message includes the region. The processing module receives a weather information response message that includes the weather information. The method continues at step270where the processing module determines checklist highlights and resource needs based on the weather information. The checklist highlights includes selected checklist items with more relative importance than remaining checklist items with regards to the weather information. The resource needs includes selected resources with more relative importance than remaining resources with regards to the weather information. The determining may be based on one or more of the weather information, a checklist, a resource list, a checklist item to weather information correlation list, a resource item to weather information correlation list, and a favorable comparison of the weather information to one or more checklist items or to one or more resource list items. For example, the processing module determines the checklist highlights to include a raingear checklist item when the weather information indicates heavy rain in the region. As another example, the processing module determines the resource needs to include heavy snow removal machinery when the weather information indicates a high avalanche risk in the region. The method continues at step272where the processing module displays the weather information, the checklist highlights, and the resource needs. Alternatively, or in addition to, the processing module sends the weather information, the checklist highlights, and the resource needs to one or more of the user devices associated with individuals affiliated with the group. The method continues at step274where the processing module sends a resource needs message to one or more of another user device, the application server, information server, and the remote application server, wherein the resource needs message includes one or more of the resource needs, the weather information, an individual identifier (ID), and a group ID. FIG.14is a flowchart illustrating an example of determining event information. A method begins with step276where a processing module (e.g., an application processing module of a user device) obtaining a context bundle that includes context information, association information, credentials information, checklists, resource lists, scenarios information, schedule information, weather information, and an information feed. Alternatively, or in addition to, the processing module may retrieve the weather information from one or more of a user device memory, an application server, an information server, and a remote application server. The method continues at step278where the processing module sends an event information request message including at least a portion of the context bundle. For example, the processing module sends the event information request message to the information server, wherein the event information request message includes an individual identifier (ID), a group ID, location information, and a credential. The information server receives the event information request message and determines event information based on the event information request message and event information within the information server. For example, information server determines the event information to include events within a distance threshold of a location specified by the location information when the credential compares favorably to a credential authorization list for the individual ID. The event information may include one or more of an event ID, an event description, an event type, an event location, event resources required, event issues, event responsible individuals, event chain of command, and event timeline information. The event type may include one or more of a flood, a hailstorm, a rainstorm, a snowstorm, high winds, a tornado, a hurricane, an earthquake, a landslide, a wildfire, a forest fire, a building fire, an explosion, a train derailment, a traffic accident, a building collapse, a bombing, a hazardous substance, a chemical spill, a biological threat, and a nuclear threat. Next, the information server sends an event information response message to the processing module, wherein the event information response message includes the event information. The method continues at step280where the processing module receives the event information response message. The method continues at step282where the processing module displays the event information in accordance with the context bundle. For example, the processing module displays the event information in a ranked order with respect to distance from the location information. As another example, the processing module displays the event information in a ranked order with respect to an association with one or more credentials of the credentials information. For instance, the processing module ranks events associated with fire above other events when the credential information indicates a fire service association (e.g., a volunteer firefighter). As another example, the processing module displays the event information in a ranked order with respect to resources of the resource list. For instance, the processing module ranks events associated with resource needs for paramedics when a resource of the resource list indicates a paramedic capability. FIG.15is a flowchart illustrating an example of selecting live feed information, which includes similar steps toFIG.14. The method begins with step276ofFIG.14where a processing module (e.g., an application processing module of a user device) obtains a context bundle. The method continues at step284where the processing module sends a live feed list request message, wherein the live feed request message includes at least a portion of the context bundle. The live feed may include a real-time information flow from one or more of a federal government entity, a state government entity, a local government entity, and a private sector entity (e.g., an internet radio source, an internet information source, a broadcast network, etc.). A format of the live feed may include one or more of a text stream, an audio stream, a picture stream, a video stream, and a multimedia stream. For example, the processing module sends the live feed list request message to an application server, wherein the live feed list request message includes location information associated with a user device. As another example, the processing module sends the live feed list request message to an information server, wherein the live feed list request message includes credentials information associated with the user device. The application server and/or the information server receives the live feed list request message and determines a plurality of live feeds based on the at least the portion of the context bundle. For example, the application server determines the plurality of live feeds associated with at least a location within a distance threshold of location information of the context bundle. As another example, the information server determines the plurality of live feeds associated with a credential (e.g., a first aid relief worker) of the context bundle. The method continues at step286where the processing module receives a live feed list response message that includes identifiers (IDs) of the plurality of live feeds. The method continues at step288where the processing module prompts for live feed selections to produce selected live feeds. For example, the processing module displays live feed information (e.g., a live feed name, a live feed description) associated with the IDs of the plurality of live feeds rank ordered by relevance to the context bundle. For instance, the processing module rank orders live feeds that are associated with locations that compare more favorably (e.g., closer) to the location information of the context bundle before other live feeds. As another instance, the processing module rank orders live feeds that are associated with a group ID of association information of the context bundle before other live feeds. Next, the processing module receives selected live feed IDs (e.g., from an input user interface). The method continues at step300where the processing module sends the selected live feed IDs (e.g., to the application server and/or to the information server). The method continues at step302where the processing module receives live feed information (e.g., streaming information). The method continues at step304where the processing module displays the live feed information in accordance with the context bundle. For example, the processing module always displays the live feed information as a scroll of text across the bottom of a color display associated with a user device. As another example, the processing module only displays the live feed information on screens associated with higher priority context bundle information. For instance, the processing module displays drilling event associated live feed information when a currently active screen includes drill information and/or drill selection. As another instance, the processing module displays high priority weather alert associated live feed information on all screens. FIG.16is a flowchart illustrating an example of obtaining top issues information, which includes similar steps toFIG.14. The method begins with step276ofFIG.14where a processing module (e.g., an application processing module of a user device) obtaining a context bundle. The method continues at step306where the processing module obtains local top issues. The top issues include high-priority problems with respect to a user and/or a group. The obtaining may be based on one or more of a user input, a resource list, local environmental information, and local event information. For example, the processing module obtains local top issues via a user input that includes a need for medical attention. As another example, the processing module obtains local top issues by extracting the local environmental information from weather information and/or from one or more user device sensors (e.g., a barometer, a temperature sensor). For instance, the local environmental information indicates a temperature above 110° F. As another example, the processing module obtains local top issues by extracting a resource need from a resource list. For instance, the resource need indicates a need for more drinking water. The method continues at step308where the processing module sends a top issues request message that includes the local top issues. For example, the processing module sends the top issues request message to an information server. Next, the information server aggregates the top issues request message with other top issues request messages to produce aggregated top issues. The information server sends a top issues response message that includes the aggregated top issues to the processing module. The method continues at step310where the processing module receives the top issues response message. The method continues at step312where the processing module displays the aggregated top issues in accordance with the context bundle. For example, the processing module displays issues of the aggregated top issues in a rank order starting with issues that are associated with user capabilities of the context bundle. For instance, the processing module displays issues associated with a user capability of driving a truck first when the issues are associated with a need for a resource to drive a truck. As another example, the processing module displays issues of the aggregated top issues in a rank order starting with issues that are associated with events within a geographic distance threshold of location information of a group identifier (ID) of the context bundle. For instance, the processing module displays issues associated with events that are within 5 miles of individuals affiliated with group ID457first. FIG.17is a flowchart illustrating an example of obtaining status information, which includes similar steps toFIG.14. The method begins with step276ofFIG.14where a processing module (e.g., an application processing module of a user device) obtains a context bundle. The method continues at step314where the processing module obtains local status. The local status includes status of an individual and/or a group. The status may include an indicator of a status of a user of a user device including one or more of okay, not okay, need help, don't need help, online, and off-line. The obtaining may be based on one or more of a user input, local environmental information, a list, and local event information. For example, the processing module obtains local status information via a user input that includes the not okay indicator and text indicating a need for medical attention. As another example, the processing module obtains local status information by extracting the local environmental information from weather information and/or from one or more user device sensors (e.g., a barometer, a temperature sensor). For instance, the local environmental information indicates a barometric pressure sensor output within a predicted range of weather information. The method continues at step316where the processing module sends a status request message that includes the local status information. For example, the processing module sends the status request message to an information server. Next, the information server aggregates the status request message with other status request messages to produce aggregated status information. The information server sends a status response message that includes the aggregated status information to the processing module. The method continues at step318where the processing module receives the status response message. The method continues at step320where the processing module displays the aggregated status information in accordance with the context bundle. For example, the processing module displays individual status information for individuals affiliated with a group identifier (ID) associated with the processing module. For instance, the processing module displays names along with a colored icon wherein a color of the colored icon color represents a status condition (e.g., red or not okay, green for okay, yellow for getting help, flashing forward no recent status). Alternatively, or in addition to, the processing module displays the individual status information and a text message of an individual associated with the individual status information. For instance, the processing module displays a name with the red colored icon along with a short text message “need medical attention.” As another example, the processing module displays names with the colored icon in a rank order starting with names that are within a geographic distance threshold of location information of an individual ID of the context bundle (e.g., a user device associated with the processing module). For instance, the processing module displays names affiliated with group ID457that are within 5 miles of the user device. As yet another example, the processing module displays names with the colored icon on a map, wherein the icon is placed on the map at a location indicated by the status information associated with the corresponding name. FIG.18is a flowchart illustrating an example of selecting message targets, which includes similar steps toFIG.14. The method begins with step276ofFIG.14where a processing module (e.g., an application processing module of a user device) obtains a context bundle. The method continues at step322where the processing module displays received messages in accordance with the context bundle by routing received messages to at least one user interface output. The receive messages may include one or more of text messages, short message service (SMS) messages, data messages, telemetry messages, encrypted messages, email messages, voicemail messages, voice dispatch messages, broadcast messages, many-to-one messages, and one-to-many messages. For example, the processing module displays received text messages rank ordered by group identifiers (IDs) associated with a user device. In another example, the processing module displays received SMS messages rank ordered by distance proximity of a location associated with an event associated with each SMS message to location information of the user device. The method continues at step324where the processing module obtains target user device IDs in accordance with the context bundle. The target user device ID includes a user device ID associated with an intended recipient of a subsequent message. The obtaining may include one or more of receiving a user interface input (e.g., text entry), retrieving a list, utilizing a predetermination, looking up one or more individual IDs affiliated with a group ID of the context bundle, and receiving a user interface input in response to displaying recommended one or more individual IDs affiliated with the user device and/or event associated with the user device. The method continues at step326where the processing module obtains messaging user input. The obtaining may include or more of receiving a user interface input (e.g., free-form text), retrieving a predetermined message, selecting a message from a message list in accordance with a status of the context bundle, and selecting a message from the message list in accordance with location information of the context bundle. For example, the processing module obtains the messaging user input based on selecting a location message from the message list, wherein the messaging user input includes text of “I'm okay and at Main Street and Sixth Avenue” when the location information indicates global positioning satellite (GPS) data corresponding to a location at Main Street and Sixth Avenue and status information of the context bundle indicates an okay status. The method continues at step328where the processing module determines a user message in accordance with a context bundle that includes the messaging user input. For example, the processing module aggregates the messaging user input with at least some of the context bundle to produce the user message. For instance, the processing module aggregates the messaging user input text of “our family is to meet at the Church Street rally point as soon as possible”, the location information of the context bundle, and status information of the context bundle to produce the user message. The method continues at step330where the processing module sends the user message to the target user device IDs. For example, the processing module sends the user message to user device IDs affiliated with a family group ID. Alternatively, or in addition to, processing module sends the user message to the family group ID as a target ID. As another example, the processing module sends a message of the message list in accordance with a button push detection or sensor value detection of the context bundle. For instance, the processing module sends a text of “send help” along with location information when a send help button is activated. As another instance, the processing module sends the text of “send help” along with the location information when an accelerometer sensor of a user device detects an SOS Morse code pattern within a shaking sequence. Alternatively, or in addition to, the processing module sends location information and other portions of the context bundle to an application server from time to time. Next, the application server identifies messages and/or message streams associated with the location information. The application server sends the messages and/or message streams to the processing module. In an example of operation, the processing module sends the application server a public safety credential of the context bundle and location information every two minutes. Next, the application server verifies (e.g., via an access control list lookup) that the public safety credential authorizes a user device associated with the public safety credential to monitor public safety communications. The application server sends a public safety was communications message stream to the user device associated with the processing module. The processing module receives the message stream and routes the voice message stream to a speaker of the user device. FIG.19is a flowchart illustrating an example of initiating a drill sequence, which includes similar steps toFIG.14. The method begins with step276ofFIG.14where a processing module (e.g., an application processing module of a user device) obtains a context bundle. The method continues at step332where the processing module obtains drill parameters. The drill parameters may include one or more of individual identifiers (IDs), group IDs, a start time, an end time, a drill type, a drill location, drill constraints, and a drill template. The obtaining may be based on one or more of receiving a user input, a query, a list, and a message. The method continues at step334where the processing module sends a drill request message. The drill request message may include one or more of the drill parameters, an individual ID, a group ID, and at least a portion of the context bundle. For example, the processing module sends the drill request message to an application server. Next the application server processes the drill request message to produce a drill response message. The drill response message may include one or more of a drill ID, drill parameters, and an existing or new drill indicator. For instance, the application server produces the drill response message to include the new drill indicator when active drills include associated drill parameters that compare unfavorably to the drill parameters (e.g., requested by the processing module). As another instance, application server produces the drill response message to include an existing drill indicator and associated drill ID when an active drill includes associated drill parameters that compare favorably to the drill parameters. The application server sends the drill response message to the processing module. The method continues at step336for the processing module receives the drill response message. The method continues at step338where the processing module receives a drill update message wherein the drill update message includes one or more of a drill ID, drill parameters, a drill state, drill issue, a drill question, desired drill outcomes, and actual drill outcomes. Next, the processing module displays at least some of the drill update message. The processing module receives drill input in response to displaying at least some of the drill update message. For instance, a user interface input receives a text stream indicating a next move in the drill in response to the drill question. The method continues at step340where the processing module sends a drill input message when a drill engagement indicator indicates participation in the drill rather than monitoring the drill. The drill input message may include one or more of an individual ID, a group ID, a portion of the context bundle, drill question answers, comments, resource list, commands, instructions, requests, status, and other input. FIG.20is a flowchart illustrating an example of participating in a drill sequence, which includes similar steps toFIGS.14and19. The method begins with step276ofFIG.14where a processing module (e.g., an application processing module of a user device) obtains a context bundle. The method continues at step342where the processing module sends an identify drill request message that includes at least a portion of the context bundle. For example, the processing module sends the identify drill request message to an application server that includes an individual identifier (ID), a group ID, and an emergency medical team credential. Next, the application server identifies a plurality of drill IDs of active drills in progress that compare favorably to the identify drill request message. For instance, the application server identifies three drill IDs of active drills in progress that are associated with emergency medical team drills when the identify drill request message includes the emergency medical team credential. Next, the application server sends an identify drill response message that includes one or more of the plurality of drill IDs and drill descriptors associated with the plurality of drill IDs. The method continues at step344where the processing module receives the identify drill response message. The method continues at step346where the processing module selects a drill ID of the plurality of drill IDs extracted from the identify drill response message to produce a selected drill ID. The selecting may be based on one or more of displaying the plurality of drill IDs and drill descriptors in a rank order favorable with the context bundle (e.g., by closest location, by affiliation with association information, by affiliation with a credential) receiving a user interface input, the plurality of drill IDs, drill descriptors, a prioritization order, the context bundle a list, and a message. The method continues at step348where the processing module sends a join drill request message that includes the drill ID. For example, the processing module sends the join drill request message to the application server, wherein the join drill request message includes an individual ID, and the drill ID. Next, the application server adds the individual ID to a list of participants of a drill associated with the drill ID. The application server sends a join drill response message to the processing module that includes one or more of an indicator confirming that the individual ID is listed as a participant of the drill associated with the drill ID, the drill ID, and drill parameters. The method continues at step350where the processing module receives the join drill response message. The method continues at steps338-340ofFIG.19where the processing module receives a drill update message and sends a drill input message when participating. FIG.21is a flowchart illustrating an example of executing a drill tutorial, which includes similar steps toFIG.14. The method begins with step276ofFIG.14where a processing module (e.g., an application processing module of a user device) obtains a context bundle. The method continues at step352where the processing module selects a drill tutorial to produce a selected drill tutorial ID. The selecting may be based on one or more of a list of drill types, the context bundle, a list of drill tutorial IDs, a message, and receiving a user interface input. For example, the processing module displays the list of drill tutorial IDs and associated drill types rank ordering the top of the list with drill types that compare favorably to event information and/or location information of the context bundle. For instance, the processing module displays drill tutorial IDs at the top of the list that are associated with water rescue when a fast water rescue event is active within a distance threshold of location information of the context bundle. Next, the processing module receives the user interface input. The method continues at step354where the processing module displays tutorial instructions based on stored/and or received tutorial instructions. The tutorial instructions may include one or more of a drill descriptor, the drill ID, why drill, how the drill works, drill objectives, and drill participation guidance. The method continues at step356where the processing module displays a drill update message simulating a step of a drill. The drill update message includes elements as previously discussed with reference toFIG.19. The method continues at step358where the processing module obtains a drill input message, wherein the drill input message is as previously discussed with reference to FIG.19. The method continues at step360where the processing module determines whether the drill tutorial session is over based on last steps executed and the number of steps associated with the drill tutorial. For example, the processing module determines that the drill session is over when a last step executed is substantially the same as a last step of a number of steps of the drill tutorial. The method repeats back to step358when the processing module determines that the drill session is not over. The method continues to step362when the processing module determines that the drill session is over. The method continues at step362where the processing module determines and saves drill summary information. The drill summary information may include one or more of drill issues, drill solutions, an effectiveness rating, and an evaluation. The evaluation may be determined based on a comparison of drill results to desired drill results of a desired drill results list. The method continues at step364where the processing module displays at least some of the drill summary information As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “operable to” or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item. As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal1has a greater magnitude than signal2, a favorable comparison may be achieved when the magnitude of signal1is greater than that of signal2or when the magnitude of signal2is less than that of signal1. As may also be used herein, the terms “processing module”, “processing circuit”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture. The present invention has been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claimed invention. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof. The present invention may have also been described, at least in part, in terms of one or more embodiments. An embodiment of the present invention is used herein to illustrate the present invention, an aspect thereof, a feature thereof, a concept thereof, and/or an example thereof. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process that embodies the present invention may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones. While the transistors in the above described figure(s) is/are shown as field effect transistors (FETs), as one of ordinary skill in the art will appreciate, the transistors may be implemented using any type of transistor structure including, but not limited to, bipolar, metal oxide semiconductor field effect transistors (MOSFET), N-well transistors, P-well transistors, enhancement mode, depletion mode, and zero voltage threshold (VT) transistors. Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art. The term “module” is used in the description of the various embodiments of the present invention. A module includes a processing module, a functional block, hardware, and/or software stored on memory for performing one or more functions as may be described herein. Note that, if the module is implemented via hardware, the hardware may operate independently and/or in conjunction software and/or firmware. As used herein, a module may contain one or more sub-modules, each of which may be one or more modules. While particular combinations of various functions and features of the present invention have been expressly described herein, other combinations of these features and functions are likewise possible. The present invention is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. | 106,821 |
11943694 | DETAILED DESCRIPTION Briefly, the present disclosure provides an emergency data manager and method of operation. Among other features, the emergency data manager provides emergency network entities, such as various workstations, with a jurisdictional map view showing the geographic boundary of the emergency network to which a specific emergency network entity belongs. Each of the emergency network entities corresponds to an emergency network that has a given geographic boundary, and therefore the jurisdictional map view corresponds to a respective emergency network, and corresponding emergency network entity's, geographic boundary. The emergency data manager obtains emergency data from various sources and determines portions of emergency data corresponding to emergencies occurring within each respective emergency network's geographic boundary. The emergency network entities corresponding to the emergency network are thereby provided with respective jurisdictional map views that display their respective emergency network's geographic boundary. The emergency data manager provides location indicators within each respective jurisdictional map view, with each location indicator corresponding to an emergency. The emergency data manager also provides a regional jurisdictional map view to a regional emergency network entity where the regional emergency network entity corresponds to a given regional emergency network geographic boundary that incorporates subordinate emergency network geographic boundaries. For example, the regional jurisdictional map view may be a countrywide view, or a statewide view. One disclosed method includes: obtaining emergency data for multiple device types from a plurality of emergency data sources; providing a jurisdictional map view to a plurality of emergency network entities, where each emergency network entity corresponds to a given geographic boundary, and where the jurisdictional map view corresponds to a respective emergency network entity's geographic boundary; determining portions of the emergency data corresponding to emergencies occurring within each respective emergency network entity geographic boundary; and providing location indicators within each respective jurisdictional map view, with each location indicator corresponding to an emergency. The method may further include providing a regional jurisdictional map view to a regional emergency network entity, where the regional emergency network entity corresponds to a given regional geographic boundary that incorporates subordinate emergency network entity geographic boundaries. The method may further include determining at least one complex polygon as an emergency network entity's geographic boundary, and providing a buffer zone defining an expanded boundary within the jurisdictional map view. The method may further include: determining associations between portions of the emergency data and specific emergency network entities based on each emergency network entity's geographic boundary; and providing the location indicators based on the associations. Location indicators may also be provided within the expanded boundary defined by corresponding buffer zones. The method may further include: establishing a plurality of network connections with the plurality of emergency network entities; and sending determined portions of the emergency data to a respective associated emergency network entity based on the associations. Another disclosed method of operation includes: obtaining emergency data for multiple device types from a plurality of emergency data sources; establishing a plurality of network connections with a plurality of emergency network entities, each emergency network entity corresponding to a given geographic boundary; determining associations between portions of the emergency data and specific emergency network entities based on each emergency network entity's geographic boundary; and sending each determined portion of emergency data to a respective associated emergency network entity based on the determined associations. The method may further include providing a jurisdictional map view to each emergency network entity, where the jurisdictional map view corresponds to a respective emergency network entity's geographic boundary, and where a determined portion of emergency data corresponding to the respective emergency network entity is related to emergencies occurring within a displayed geographic boundary. The method may further include: providing a regional jurisdictional map view to a regional emergency network entity, where the regional emergency network entity corresponds to a given regional geographic boundary that incorporates subordinate emergency network entity geographic boundaries. The method may further include: showing location indicators within the jurisdictional map view, with each location indicator corresponding to an emergency. The method may further include: providing a selectable link corresponding to each location indicator within the jurisdictional map view; and providing emergency data related to an emergency at a location corresponding to the location indicator, in response to selection input via the selectable link. Determining associations between portions of the emergency data and specific emergency network entities based on each emergency network entity's geographic boundary, may include determining at least one complex polygon as an emergency network entity's geographic boundary. Establishing a plurality of network connections with a plurality of emergency network entities may include establishing a transport control protocol (TCP) connection with the plurality of emergency network entities. A disclosed apparatus includes: a network component, operative to connect to the Internet; and a processor, operatively coupled to the network component. The processor is operative to: obtain emergency data for multiple device types from a plurality of emergency data sources; provide a jurisdictional map view to a plurality of emergency network entities, where each emergency network entity corresponds to a given geographic boundary, and where the jurisdictional map view corresponds to a respective emergency network entity's geographic boundary; determine portions of the emergency data corresponding to emergencies occurring within each respective emergency network entity geographic boundary; and provide location indicators within each respective jurisdictional map view, with each location indicator corresponding to an emergency. The processor may be further operative to provide a regional jurisdictional map view to a regional emergency network entity, where the regional emergency network entity corresponds to a given regional geographic boundary that incorporates subordinate emergency network entity geographic boundaries. The processor may be further operative to determine at least one complex polygon as an emergency network entity's geographic boundary, and to provide a buffer zone defining an expanded boundary. The processor may be further operative to: determine associations between portions of the emergency data and specific emergency network entities based on each emergency network entity's geographic boundary; and provide the location indicators based on the associations. Location indicators may be provided within an expanded boundary defined by the buffer zones. The processor may be further operative to: establish a plurality of network connections with the plurality of emergency network entities; and send determined portions of the emergency data to a respective associated emergency network entity based on the associations. Another disclosed apparatus includes: a network component, operative to connect to the Internet; and a processor, operatively coupled to the network component. The processor is operative to: obtain emergency data for multiple device types from a plurality of emergency data sources; establish a plurality of network connections with a plurality of emergency network entities, each emergency network entity corresponding to a given geographic boundary; determine associations between portions of the emergency data and specific emergency network entities based on each emergency network entity's geographic boundary; and send each determined portion of emergency data to a respective associated emergency network entity based on the determined associations. The processor may be further operative to: provide a jurisdictional map view to each emergency network entity, where the jurisdictional map view corresponds to a respective emergency network entity's geographic boundary, and where a determined portion of emergency data corresponding to the respective emergency network entity is related to emergencies occurring within a displayed geographic boundary. The processor may be further operative to provide a regional jurisdictional map view to a regional emergency network entity, where the regional emergency network entity corresponds to a given regional geographic boundary that incorporates subordinate emergency network entity geographic boundaries. The processor may be further operative to: show location indicators within the jurisdictional map view, with each location indicator corresponding to an emergency. The processor may be further operative to: provide a selectable link corresponding to each location indicator within the jurisdictional map view; and provide emergency data related to an emergency at a location corresponding to the location indicator, in response to selection input via the selectable link. Another disclosed method of operation involves establishing a Web Socket connection between a public safety answering point (PSAP) and an emergency data manager; streaming location data to the PSAP from the emergency data manager via the Web Socket connection for a plurality of devices; and filtering the streaming location data to the PSAP based on the location data indicating location within a polygon defining a jurisdictional geofence for the PSAP. Filtering the streaming location data to the PSAP based on the location data indicating location within a polygon may include defining at least one complex polygon as the polygon defining the jurisdictional geofence for the PSAP. Streaming location data to the PSAP from the emergency data manager via the WebSocket connection for a plurality of devices, may include streaming location data along with a plurality of device identifiers in response to a plurality of devices each initiating an emergency session with the PSAP, prior to establishment of the emergency sessions. Streaming location data along with a device identifier in response to a device initiating an emergency session with the PSAP, may include streaming location data along with a device identifier in response to a device initiating an emergency session with the PSAP, where the emergency session is an emergency phone call. Streaming location data along with a device identifier in response to a device initiating an emergency session with the PSAP, may include streaming location data along with a device identifier in response to a device initiating an emergency session with the PSAP, where the emergency session is an emergency alert generated by the device. The method may further include pushing a plurality of device identifiers and associated location information, to the emergency data manager100in response to emergency sessions or emergency alerts being initiated by the plurality of devices. The method may further include establishing a call queue at the PSAP using the plurality of device identifiers, prior to establishment of the emergency sessions. The method may further include displaying the call queue on a PSAP graphical user interface (GUI); and displaying location information associated with each of the plurality of device identifiers on a map indicating the polygon boundary. The method may further include displaying the call queue on a PSAP graphical user interface (GUI) and providing each device identifier as a selectable link; receiving selection input for selection of a specific selectable link for a specific device identifier; and displaying location information associated with the specific device identifier on a map indicating the polygon boundary. The present disclosure also provides an emergency data manager operative to: establish a WebSocket connection with a PSAP; stream location data to the PSAP via the WebSocket connection for a plurality of devices; and filter the streaming location data to the PSAP based on the location data indicating location within a polygon defining a jurisdictional geofence for the PSAP. The emergency data manager may be further operative to filter the streaming location data to the PSAP based on the location data indicating location within a polygon by defining at least one complex polygon as the polygon defining the jurisdictional geofence for the PSAP. The emergency data manager may be further operative to stream location data along with a plurality of device identifiers in response to a plurality of devices each initiating an emergency session with the PSAP, prior to establishment of the emergency sessions. The emergency session may be an emergency phone call or may be an emergency alert generated by the device. The emergency data manager is further operative to receive a push a plurality of device identifiers and associated location information, in response to emergency sessions being initiated by the plurality of devices or in response to emergency alerts being generated by the plurality of devices. A PSAP may include an emergency response application that is operative to establish a call queue using the plurality of device identifiers, prior to establishment of the emergency sessions. The emergency response application may be further operative to: display the call queue on a PSAP graphical user interface (GUI); and display location information associated with each of the plurality of device identifiers on a map indicating the polygon boundary. The emergency response application may be further operative to: display the call queue on a PSAP graphical user interface (GUI) and provide each device identifier as a selectable link; receive selection input for selection of a specific selectable link for a specific device identifier; and display location information associated with the specific device identifier on a map indicating the polygon boundary. Another disclosed method includes establishing a WebSocket connection between an emergency service provider (ESP) and an emergency data emergency data manager; receiving a stream of emergency alerts from a plurality of devices, where each emergency alert includes location data; filtering the stream of emergency alerts to generate a filtered stream of emergency alerts for which the ESP is authorized to respond; and providing the filtered stream of emergency alerts to the ESP from the emergency data manager via the Web Socket connection. Filtering the stream of emergency alerts may include filtering the stream of emergency alerts based on a jurisdictional geofence defined as a polygonal boundary, or may include filtering the stream of emergency alerts based on location, type of emergency, ESP capabilities and ESP current status. Filtering the stream of emergency alerts based on a jurisdictional geofence defined as a polygonal boundary may include filtering the stream of emergency alerts based on a jurisdictional geofence that includes a complex polygon. The filtering may also include removing overlapping sections and protruding sections between the polygonal boundary and at least one adjacent polygon. Establishing a WebSocket connection between an emergency service provider (ESP) and an emergency data manager, may include establishing a WebSocket connection with a public safety answering point (PSAP) where the PSAP is the ESP. The method may further include streaming location data along with a plurality of device identifiers in response to a plurality of devices each initiating an emergency session with the ESP, prior to establishment of the emergency sessions. Among other advantages provided by the systems, servers, devices, methods, and media described in the present disclosure, is the ability to gather and deliver device-based hybrid locations (hereinafter, “enhanced locations”) and additional data that may be pertinent to emergency situations to public safety services (PSS; e.g., public safety answering points, fire departments, police departments, paramedics, police officers, etc.). An emergency network may be operatively coupled to an emergency data manager that functions to receive enhanced locations (e.g., global positioning systems location data, map data) and additional data (e.g., medical history, video feeds, emergency reports, media reports) from various sources (e.g., medical databases, mobile devices of public or first responders, public cameras, police systems, media outlets) and at various times before, during, or after emergency situations and distribute enhanced locations and additional data to ESPs to aid the ESP in responding to live emergency situations. The emergency data manager may be a separate network entity that communicates with the emergency network via an Internet connection or by some other appropriate network connection. The enhanced locations and additional data may be delivered by the emergency data manager to a public safety answering point (PSAP). The enhanced locations and additional data may be displayed within a PSAP display such as, but not limited to, an Automatic Location Identification (ALI) display. The enhanced locations and additional data may be displayed using a graphical user interface provided by an emergency response application GUI separate from other PSAP GUI displays. An emergency response application may also be separate from other PSAP applications. An emergency network entity, such as a PSAP workstation, may be provided with a device identifier, such as a phone number or IP address, etc., from an emergency caller through the emergency network. A PSAP operator may manually input the device identifier into an emergency response application to send a query to the emergency data manager and receive enhanced location and additional data from the emergency data manager in response to the query. However, in some implementations, a device identifier may be sent automatically for example, using a push operation to make an automatic query through a Web Socket connection between the emergency data manager and the emergency response application. In response to the device identifier push, the emergency data manager will provide the PSAP with enhanced location and additional data which will be received via the emergency response application, operating one or more PSAP workstations. The emergency response application may be integrated into an ESP system to form an integrated PSS system, such that the integrated ESP system may automatically receive enhanced location and additional data via a single, integrated GUI. Among other advantages provided by the present disclosure, the emergency response application provides an emergency network, such as a PSAP, with critical information to aid in the response to a given emergency. In the case of location data, a PSAP is enabled to verify the location of an emergency caller via technology, rather than relying on a distressed caller to generate the location data. Thus, a PSAP can initiate a response before the user provides any location information, saving seconds or minutes on emergency response time. The present disclosure provides for the communication of enhanced location data and additional data to the PSAP via, for example, an emergency response application accessible by PSAP personnel, or as a software integration of a data pipeline with other emergency network (i.e. emergency service provider “ESP” systems). Disclosed herein are systems, applications, servers, devices, methods, and media that automatically push data to the PSAP, which is particularly beneficial because it streamlines the emergency response without requiring active input from the PSAP personnel. Another advantage provided by the systems, servers, devices, methods, and media of the instant application is the ability to access an emergency response application provided to authorized emergency networks such as public safety services (PSAPs), for receiving and displaying emergency data, such as enhanced locations. The emergency response application is operative to verify public safety services, generate emergency data requests or queries, and display emergency data received from an emergency data manager. The emergency data manager and emergency response application are also operative to provide a graphical user interface to a computing device that is accessible by members of public safety services. The emergency response application may be integrated with one or more emergency networks/PSAP systems to provide a seamless and comprehensive emergency data delivery system. Another advantage provided by the systems, servers, devices, methods and media of the present disclosure is the ability to protect potentially sensitive emergency data using geospatial analysis. An emergency data manager and an emergency response application use geofences to limit the delivery of emergency data to authorized recipients based on authoritative jurisdictional boundaries. Geofences may be received from PSAP administrators through the emergency response application. A geofence may define a jurisdiction of a particular PSAP, and may be displayed as a geofence boundary on a map via a graphical user interface provided by the emergency response application. Geofences received from PSAP administrators must be verified by public safety officials before the geofences are applied by the emergency data manager and displayed with a GUI of the emergency response application. The emergency response application also provides an emergency management view in the graphical user interface (GUI). The emergency management view enables the PSAP staff to view ongoing recently received emergency calls within one or more geofenced jurisdictions displayed on the GUI. The emergency management view may display a call queue with numerous device identifiers associated with emergency caller devices, and the location of each caller. The caller's location may be updated in real time. The emergency management view may display the location of available emergency services within a variable proximity to one or more emergency callers, or within the jurisdictional geofence of one or more emergency callers. The PSAP may be enabled to coordinate the dispatch of emergency responders to emergency callers, so as to reduce response times and improve the allocation of resources. Described herein are various methods for delivering emergency data to emergency networks such as, but not limited to, a public safety answering point (PSAP). One method includes: a) receiving available emergency data associated with a device identifier from one or more emergency data databases, the emergency data comprising a current location; b) retrieving a geofence associated with the PSAP using the identifier of the PSAP, wherein the geofence encloses a region within a jurisdiction of the PSAP; c) determining if the current location is within the geofence associated with the PSAP; d) in response to determining that the current location is within the geofence associated with the PSAP, transmitting the emergency data to a PSAP computing device; and e) providing an emergency response application comprising a graphical user interface (GUI) accessible by the computing device at the PSAP, the GUI comprising an interactive map showing an incident associated with the device identifier within the jurisdiction of the PSAP and at least one data overlay displaying at least a subset of the emergency data. The method may further include accessing an Automatic Location Information (ALI) feed or a Computer Aided Dispatch (CAD) spill to identify the incident and the associated device identifier. The emergency data associated with the device identifier may include one or more historical locations. The method may further include: a) determining if the one or more historical locations are within the geofence associated with the PSAP; and b) in response to determining that the one or more historical locations are within the geofence associated with the PSAP, transmitting the one or more historical locations to the computing device for display within the interactive map. Determining if the current location is within the geofence associated with the PSAP may include applying a buffer that expands one or more boundaries of the geofence when comparing the current location to the geofence. The buffer may be kilometers beyond a boundary of the geofence. Determining if the current location is within the geofence associated with the PSAP may include shrinking one or more boundaries of the geofence when comparing the current location to the geofence. The geofence associated with the PSAP may be submitted through the GUI by an administrator of the PSAP. The geofence may be a rectangle defined by the administrator of the PSAP on a map within the GUI. The rectangle may be defined using two latitude-longitude coordinates. The geofence may include a shape defined by the administrator of the PSAP on a map provided by the GUI. The geofence may be a polygon defined by the administrator of the PSAP on a map provided by the GUI. The geofence may include a GIS file. The geofence may include a GIS shapefile. The geofence may include a plurality of polygons. The method may include PSAP registration steps comprising: a) receiving a registration request for access to the emergency response application from an administrator of the PSAP through the GUI, the registration request that includes a name of the PSAP and a non-emergency landline telephone number of the PSAP; b) receiving an administrator-designated definition of the geofence associated with the PSAP through an interactive map provided by the GUI; c) verifying the PSAP using the name of the PSAP, the non-emergency landline telephone number of the PSAP, and the geofence associated with the PSAP; and d) in response to verifying the PSAP, generating credentials associated with the PSAP and providing access to the emergency response application to the administrator of the PSAP. The PSAP may be authorized to receive the emergency data using a temporary access token. The temporary access token may be generated by a credential management system. The credentials may be associated with the PSAP are generated and stored within a credential management system. The method may include: a) receiving selection of a new user account for a PSAP member from an administrator of the PSAP, wherein the selection of a new user account includes an email address associated with the PSAP member; b) delivering an email comprising the login information to the email address associated with the PSAP member; c) generating the new user account within the credential management system; and d) linking the new user account with both the login information and the credentials associated with the PSAP. The temporary access token may be generated by steps that include, for example: a) identifying the new user account within the credential management system using the login information; b) identifying the PSAP using the new user account; c) retrieving the credentials associated with the PSAP; and d) deriving the temporary access token from the credentials associated with the PSAP. The method may include: a) wherein the selection of a new user account further includes a user type for the new user account; b) wherein the emergency data request further includes the user type; and c) further provides differentiating access to the emergency data based on the user type. The method may include: a) in response to receiving the login information from the member of the PSAP, checking an IP address of the computing device against a whitelist of IP addresses; b) in response to determining that the IP address of the computing device is not on the whitelist of IP addresses: i) denying the member of the PSAP access to the emergency response application; and ii) delivering an interactive call to a landline associated with the PSAP, wherein the interactive call audibly dictates an access code; c) receiving the access code from the member of the PSAP through the GUI; and d) providing access to the emergency response application to the member of the PSAP. The method may include: a) in response to receiving the login information from the member of the PSAP, checking an IP address of the computing device against a whitelist of IP addresses; b) in response to determining that the IP address of the computing device is not on the whitelist of IP addresses: i) denying the member of the PSAP access to the emergency response application; and ii) delivering an email to an administrator of the PSAP, the email that has a confirmation link; c) receiving selection of the confirmation link; and d) in response to receiving selection of the confirmation link, providing access to the emergency response application to the member of the PSAP. The device identifier may be associated with an electronic device used to make an emergency call to the PSAP. The device identifier may be a phone number or an email address, etc. The device identifier may be manually submitted to the emergency response application by a member of the PSAP through an entry field provided by the GUI. Alternatively, the device identifier may be automatically submitted to the emergency response application by call-taking software installed on the computing device. The emergency data request may be an API GET request. The emergency data may include, but is not limited to, at least one of caller information, sensor data, emergency contact information, emergency indication, and medical information. The at least one data overlay may include, but is not limited to, one or more Internet of Things (IoT) sensors graphically depicted on the interactive map. The IoT sensors may include, but are not limited to, a network-enabled camera, video camera, environmental sensor, or any combination thereof. The at least one data overlay may include one or more first responders graphically depicted on the interactive map. The at least one data overlay may include, but is not limited to, traffic data graphically depicted on the interactive map. The emergency response application may be configured to allow user adjustment of one or more filters for graphically depicting at least a subset of the emergency data on the interactive map. The incident shown on the interactive map may be configured to be user selectable and to display at least a subset of the emergency data associated with the incident upon user selection. The at least a subset of the emergency data may include, but is not limited to, user name, user address, emergency contact information, or any combination thereof. The emergency response application may be configured to automatically remove one or more incidents from the interactive map over time. The interactive map may be configured to show a plurality of nearby incidents located in proximity to the incident. The emergency response application may be configured to display a queue of ongoing or recent incidents. A disclosed method for delivering emergency data to a public safety answering point (PSAP), may include: a) providing an emergency response comprising a graphical user interface (GUI) accessible by a computing device at a public safety answering point; b) receiving login information for a member of the PSAP from the computing device; c) generating a temporary access token authorizing the member of the PSAP to access emergency data, wherein the temporary access token is derived from credentials associated with the PSAP; d) accessing a data feed of the PSAP to identify an emergency incident and an associated device identifier; e) associating the emergency incident with an identifier of the PSAP based on the temporary access token; f) receiving emergency data associated with the device identifier from one or more databases, the emergency data including a current location; and g) transmitting the emergency data to the computing device for display on the computing device through the GUI with an interactive map showing an incident associated with the device identifier within the jurisdiction of the PSAP and at least one data overlay displaying at least a subset of the emergency data. A disclosed system for delivering emergency data to a public safety answering point (PSAP), may include: a) an emergency response application communicatively coupled to a network server and including a graphical user interface (GUI) accessible by a PSAP computing device through the computing network, wherein the emergency response application is configured to: i) receive emergency data regarding an emergency incident, the emergency data including a device identifier and a current location; and ii) display an interactive map through the GUI showing the emergency incident within the jurisdiction of the PSAP and at least one data overlay displaying at least a subset of the emergency data; and b) an emergency data manager communicatively coupled to the network server and configured to: i) gather emergency data associated with the device identifier from one or more databases, the emergency data comprising a current location; ii) retrieve a geofence associated with the PSAP using an identifier of the PSAP, wherein a geofence encloses a region within a jurisdiction of the PSAP; iii) determining if the current location is within the geofence associated with the PSAP; and iv) in response to determining that the current location is within the geofence associated with the PSAP, transmitting the emergency data to the computing device for display through the GUI. The system may be further configured to access an Automatic Location Information (ALI) feed or a Computer Aided Dispatch (CAD) spill to identify the incident and the associated device identifier. The emergency data associated with the device identifier may include, but is not limited to, one or more historical locations. The system may be further configured to: a) determine if the one or more historical locations are within the geofence associated with the PSAP; and b) in response to determining that the one or more historical locations are within the geofence associated with the PSAP, transmit the one or more historical locations to the computing device for display within the interactive map. Determining if the current location is within the geofence associated with the PSAP may further include applying a buffer that expands one or more boundaries of the geofence when comparing the current location to the geofence. The buffer may be kilometers beyond a boundary of the geofence. Determining if the current location is within the geofence associated with the PSAP may further include shrinking one or more boundaries of the geofence when comparing the current location to the geofence. The geofence associated with the PSAP may be submitted through the GUI by an administrator of the PSAP. The geofence may be a rectangle defined by the administrator of the PSAP on a map within the GUI. The rectangle may be defined using two latitude-longitude coordinates. The geofence may include a shape defined by the administrator of the PSAP on a map provided by the GUI. The geofence may be a polygon defined by the administrator of the PSAP on a map provided by the GUI. The geofence may include, but is not limited to, a GIS file such as a GIS shapefile. The geofence may include a plurality of polygons. The system may be further configured to receive a PSAP registration, the PSAP registration comprising: a) a registration request for access to the emergency response application from an administrator of the PSAP through the GUI, the registration request comprising a name of the PSAP and a non-emergency landline telephone number of the PSAP; b) an administrator-designated definition of the geofence associated with the PSAP through an interactive map provided by the GUI; c) verification of the PSAP using the name of the PSAP, the non-emergency landline telephone number of the PSAP, and the geofence associated with the PSAP; and d) credentials associated with the PSAP and providing access to the emergency response application to the administrator of the PSAP. The PSAP may be authorized to receive the emergency data using a temporary access token. The temporary access token may be generated by a credential management system. The credentials associated with the PSAP may be generated and stored within a credential management system. The system may be further configured to: a) receive a selection of a new user account for a PSAP member from an administrator of the PSAP, wherein the selection of a new user account includes an email address associated with the PSAP member; b) deliver an email that has the login information to the email address associated with the PSAP member; c) generate the new user account within the credential management system; and d) link the new user account with both the login information and the credentials associated with the PSAP. The temporary access token may be generated by steps including, for example: a) identifying the new user account within the credential management system using the login information; b) identifying the PSAP using the new user account; c) retrieving the credentials associated with the PSAP; and d) deriving the temporary access token from the credentials associated with the PSAP. The system may also include: a) wherein the selection of a new user account further includes a user type for the new user account; b) wherein the emergency data request further includes the user type; and c) further configured to differentiate access to the emergency data based on the user type. The system may be further configured to: a) in response to receiving the login information from the member of the PSAP, check an IP address of the computing device against a whitelist of IP addresses; b) in response to determining that the IP address of the computing device is not on the whitelist of IP addresses: i) deny the member of the PSAP access to the emergency response application; and ii) deliver an interactive call to a landline associated with the PSAP, wherein the interactive call audibly dictates an access code; c) receive the access code from the member of the PSAP through the GUI; and d) provide access to the emergency response application to the member of the PSAP. The system may be further configured to: a) in response to receiving the login information from the member of the PSAP, check an IP address of the computing device against a whitelist of IP addresses; b) in response to determining that the IP address of the computing device is not on the whitelist of IP addresses: i) deny the member of the PSAP access to the emergency response application; and ii) deliver an email to an administrator of the PSAP with a confirmation link; c) receive selection of the confirmation link; and d) in response to receiving selection of the confirmation link, provide access to the emergency response application to the member of the PSAP. The device identifier may be associated with an electronic device used to make an emergency call to the PSAP, and may be, but is not limited to, a phone number or an email address. The device identifier may be manually submitted to the emergency response application by a member of the PSAP through an entry field provided by the GUI. Alternatively, the device identifier may be automatically submitted to the emergency response application by call-taking software installed on the workstation/computing device. The emergency data request may be an API GET request. The emergency data may include, but is not limited to, at least one of caller information, sensor data, emergency contact information, emergency indication, and medical information. The at least one data overlay may include, but is not limited to, one or more Internet of Things (IoT) sensors graphically depicted on the interactive map. The IoT sensors may include, but are not limited to, a network-enabled camera, video camera, environmental sensor, or any combination thereof. The at least one data overlay may include, but is not limited to, one or more first responders graphically depicted on the interactive map. The at least one data overlay may include, but is not limited to, traffic data graphically depicted on the interactive map. The emergency response application may be configured to allow user adjustment of one or more filters for graphically depicting at least a subset of the emergency data on the interactive map. The incident shown on the interactive map may be configured to be user selectable and to display at least a subset of the emergency data associated with the incident upon user selection. The at least a subset of the emergency data may include, but is not limited to, user name, user address, emergency contact information, or any combination thereof. The emergency response application may be configured to automatically remove one or more incidents from the interactive map over time. The interactive map may be configured to show a plurality of nearby incidents located in proximity to the incident. The emergency response application may be configured to display a queue of ongoing or recent incidents. A disclosed system for delivering emergency data to a public safety answering point (PSAP), the system configured to: a) provide an emergency response application that includes a graphical user interface (GUI) accessible by a workstation/computing device at a public safety answering point; b) receive login information for a member of the PSAP from the workstation/computing device; c) generate temporary access token authorizing the member of the PSAP to access emergency data, wherein the temporary access token is derived from credentials associated with the PSAP; d) access a data feed of the PSAP to identify an emergency incident and an associated device identifier; e) associate the emergency incident with an identifier of the PSAP based on the temporary access token; f) receive emergency data associated with the device identifier from one or more databases that includes, but is not limited to, a current location; and g) transmit the emergency data to the computing device for display on the workstation/computing device through the GUI on an interactive map showing an incident associated with the device identifier within the jurisdiction of the PSAP and at least one data overlay displaying at least a subset of the emergency data. A disclosed non-transitory, non-volatile, computer readable storage media encoded with a computer program includes instructions executable by at least one processor, that when executed cause the processor to: a) receive available emergency data associated with a device identifier from one or more databases, the emergency data including, but not limited to, a current location; b) retrieve a geofence associated with the PSAP using the identifier of the PSAP, wherein the geofence encloses a region within the jurisdiction of the PSAP; c) determine if the current location is within the geofence associated with the PSAP; d) in response to determining that the current location is within the geofence associated with the PSAP, transmit the emergency data to a PSAP computing device; and e) provide an emergency response application with a graphical user interface (GUI) accessible by the computing device at the PSAP, where the GUI provides an interactive map showing an incident associated with the device identifier within the jurisdiction of the PSAP and at least one data overlay displaying at least a subset of the emergency data. The non-transitory, non-volatile, computer readable storage media executable instructions, when executed, may further cause the processor to access an Automatic Location Information (ALI) feed or a Computer Aided Dispatch (CAD) spill to identify the incident and the associated device identifier. The emergency data associated with the device identifier may include, but is not limited to, one or more historical locations. The non-transitory, non-volatile, computer readable storage media executable instructions, when executed, may further cause the processor to: a) determine if the one or more historical locations are within the geofence associated with the PSAP; and b) in response to determining that the one or more historical locations are within the geofence associated with the PSAP, transmit the one or more historical locations to the computing device for display within the interactive map. Determining if the current location is within the geofence associated with the PSAP may include applying a buffer that expands one or more boundaries of the geofence when comparing the current location to the geofence. The buffer may be kilometers beyond a boundary of the geofence. Determining if the current location is within the geofence associated with the PSAP may include shrinking one or more boundaries of the geofence when comparing the current location to the geofence. The geofence associated with the PSAP may be submitted through the GUI by an administrator of the PSAP. The geofence may be a rectangle defined by the administrator of the PSAP on a map within the GUI, and may be defined using two latitude-longitude coordinates. The geofence may include a shape defined by the administrator of the PSAP on a map provided by the GUI. The geofence may be, but is not limited to, a polygon defined by the administrator of the PSAP on a map provided by the GUI. The geofence may include a GIS file such as, but not limited to, a GIS shapefile. The geofence may include, but is not limited to, a plurality of polygons. The non-transitory, non-volatile, computer readable storage media executable instructions, when executed, may further cause the processor to perform PSAP registration steps that include, for example: a) receiving a registration request for access to the emergency response application from an administrator of the PSAP through the GUI, where the registration request includes a name of the PSAP and a non-emergency landline telephone number of the PSAP; b) receiving an administrator-designated definition of the geofence associated with the PSAP through an interactive map provided by the GUI; c) verifying the PSAP using the name of the PSAP, the non-emergency landline telephone number of the PSAP, and the geofence associated with the PSAP; and d) in response to verifying the PSAP, generating credentials associated with the PSAP and providing access to the emergency response application to the administrator of the PSAP. The PSAP may be authorized to receive the emergency data using a temporary access token. The temporary access token may be generated by a credential management system. The credentials associated with the PSAP may be generated and stored within a credential management system. The non-transitory, non-volatile, computer readable storage media executable instructions, when executed, may further cause the processor to: a) receive selection of a new user account for a PSAP member from an administrator of the PSAP, where the selection of a new user account includes an email address associated with the PSAP member; b) deliver an email with the login information to the email address associated with the PSAP member; c) generate the new user account within the credential management system; and d) link the new user account with both the login information and the credentials associated with the PSAP. The temporary access token may be generated by steps including, for example: a) identifying the new user account within the credential management system using the login information; b) identifying the PSAP using the new user account; c) retrieving the credentials associated with the PSAP; and d) deriving the temporary access token from the credentials associated with the PSAP. The non-transitory, non-volatile, computer readable storage media executable instructions, when executed, may further cause the processor to: a) select a new user account including a user type for the new user account; b) wherein the emergency data request may further include the user type; and c) may further include differentiating access to the emergency data based on the user type. The non-transitory, non-volatile, computer readable storage media executable instructions, when executed, may further cause the processor to: a) in response to receiving the login information from the member of the PSAP, check an IP address of the computing device against a whitelist of IP addresses; b) in response to determining that the IP address of the computing device is not on the whitelist of IP addresses: i) deny the member of the PSAP access to the emergency response application; and ii) deliver an interactive call to a landline associated with the PSAP, where the interactive call audibly dictates an access code; c) receive the access code from the member of the PSAP through the GUI; and d) provide access to the emergency response application to the member of the PSAP. The non-transitory, non-volatile, computer readable storage media executable instructions, when executed, may further cause the processor to: a) in response to receiving the login information from the member of the PSAP, check an IP address of the workstation/computing device against a whitelist of IP addresses; b) in response to determining that the IP address of the computing device is not on the whitelist of IP addresses: i) deny the member of the PSAP access to the emergency response application; and ii) deliver an email to an administrator of the PSAP with a confirmation link; c) receive selection of the confirmation link; and d) in response to receiving selection of the confirmation link, provide access to the emergency response application to the member of the PSAP. The device identifier may be associated with an electronic device used to make an emergency call to the PSAP, and may be, but is not limited to, a phone number or an email address. The device identifier may be manually submitted to the emergency response application by a member of the PSAP through an entry field provided by the GUI. The device identifier may be automatically submitted to the emergency response application by call-taking software installed on the computing device. The emergency data request may be an API GET request. The emergency data may include, but is not limited to, at least one of caller information, sensor data, emergency contact information, emergency indication, and medical information. The at least one data overlay may include, but is not limited to, one or more Internet of Things (IoT) sensors graphically depicted on the interactive map. The IoT sensors may include, but are not limited to, a network-enabled camera, video camera, environmental sensor, or any combination thereof. The at least one data overlay may include, but is not limited to, one or more first responders graphically depicted on the interactive map. The at least one data overlay may include, but is not limited to, traffic data graphically depicted on the interactive map. The emergency response application may be configured to allow user adjustment of one or more filters for graphically depicting at least a subset of the emergency data on the interactive map. The incident shown on the interactive map may be configured to be user selectable and to display at least a subset of the emergency data associated with the incident upon user selection. The at least a subset of the emergency data may include, but is not limited to, user name, user address, emergency contact information, or any combination thereof. The emergency response application may be configured to automatically remove one or more incidents from the interactive map over time. The interactive map may be configured to show a plurality of nearby incidents located in proximity to the incident. The emergency response application may be configured to display a queue of ongoing or recent incidents. A disclosed non-transitory, non-volatile, computer readable storage media encoded with a computer program includes instructions executable by at least one processor, that when executed cause the processor to: a) provide an emergency response comprising a graphical user interface (GUI) accessible by a computing device at a public safety answering point; b) receive login information for a member of the PSAP from the computing device; c) generate a temporary access token authorizing the member of the PSAP to access emergency data, wherein the temporary access token is derived from credentials associated with the PSAP; d) access a data feed of the PSAP to identify an emergency incident and an associated device identifier; e) associate the emergency incident with an identifier of the PSAP based on the temporary access token; f) receive emergency data associated with the device identifier from one or more databases with a current location; and g) transmit the emergency data to the computing device for display on the computing device through the GUI, on an interactive map showing an incident associated with the device identifier within the jurisdiction of the PSAP and at least one data overlay displaying at least a subset of the emergency data. A disclosed method for delivering emergency data to an emergency service provider (ESP), may include: a) receiving an emergency alert associated with a device identifier and a current location; b) determining a ESP for responding at the current location by retrieving a geofence associated with the ESP, and determining if the current location is within the geofence associated with the ESP; c) in response to determining that the current location is within the geofence associated with the ESP, transmitting the emergency data to an ESP computing device; and d) providing an emergency response application with a graphical user interface (GUI) accessible by the computing device at the ESP, showing a list of emergency alerts and an interactive map with an incident location associated with the device identifier. The list of emergency alerts may include a list of emergency calls located within the geofence of the ESP. The list of emergency alerts may be ordered by the time the emergency call was received. The emergency alert may include an emergency notification indicating an on-going emergency call. The emergency alert may be initiated by user input on a user device associated with the device identifier. The emergency alert may be initiated by one or more sensor readings from a user device associate with the device identifier. The method may include identifying two or more emergency alerts associated with an incident. The GUI may include a section providing emergency data regarding the selected emergency alert. The emergency data associated with the device identifier may include one or more historical locations. The device identifier may be, but is not limited to, a phone number, an email address, or an IP address. The emergency data may include, but is not limited to, caller information, sensor data, emergency contact information, emergency indication, and medical information. The at least one data overlay may include, but is not limited to, one or more Internet of Things (IoT) sensors graphically depicted on the interactive map. The IoT sensors may include, but are not limited to, a network-enabled camera, video camera, environmental sensor, or any combination thereof. The at least one data overlay may include, but is not limited to, one or more first responders graphically depicted on the interactive map. The at least one data overlay may include, but is not limited to, traffic data graphically depicted on the interactive map. The emergency response application may be configured to allow user adjustment of one or more filters for graphically depicting at least a subset of the emergency data on the interactive map. The incident shown on the interactive map may be configured to be user selectable and displays at least a subset of the emergency data associated with the incident upon user selection. The at least a subset of the emergency data may include, but is not limited to, user name, user address, emergency contact information, or any combination thereof. The emergency response application may be configured to automatically remove one or more incidents from the interactive map over time. A disclosed method for presenting emergency data at a workstation/computing system of an emergency network (i.e. emergency service provider (ESP)), may include a) receiving, emergency data sourced from one or more databases, including a current location and an associated device identifier; b) detecting, an emergency alert associated with the device identifier; c) linking the emergency alert to the emergency data; and d) providing a graphical user interface (GUI) with: i) an interactive map showing a geographic representation of a jurisdiction of the ESP and graphically depicting one or more emergency alerts within the jurisdiction, wherein the one or more emergency alerts includes the emergency alert associated with the device identifier; and ii) a list of one or more emergency alerts showing at least a subset of the emergency data associated with the one or more emergency alerts. A disclosed computer-implemented system for presenting emergency data at an emergency network (emergency service provider (ESP)) workstation/computing system, may include: an emergency response application communicatively coupled to a network server with a graphical user interface (GUI) accessible by a PSAP workstation/computing device through a network, where the emergency response application is configured to: a) receive emergency data sourced from one or more databases, including a current location and an associated device identifier; b) detect an emergency alert associated with the device identifier; c) link the emergency alert to the emergency data; and d) provide a graphical user interface (GUI) with: i) an interactive map showing a geographic representation of a jurisdiction of the ESP and graphically depicting one or more emergency alerts within the jurisdiction, wherein the one or more emergency alerts includes the emergency alert associated with the device identifier; and ii) a list of one or more emergency alerts showing at least a subset of the emergency data associated with the one or more emergency alerts. A disclosed method for presenting emergency data at an emergency network (emergency service provider (ESP)) workstation/computing system, may include: a) receiving emergency data sourced from one or more databases, including a current location and an associated device identifier; b) detecting an emergency alert associated with the device identifier; c) linking the emergency alert to the emergency data; and d) providing a graphical user interface (GUI) with: i) an interactive map showing a geographic representation of a jurisdiction of the ESP and graphically depicting one or more emergency alerts within the jurisdiction, wherein the one or more emergency alerts includes the emergency alert associated with the device identifier; and ii) a list of one or more emergency alerts showing at least a subset of the emergency data associated with the one or more emergency alerts. A disclosed method for delivering emergency data to a public safety answering point (PSAP), may include: a) receiving available emergency data associated with a device identifier from one or more databases, including a current location; b) retrieving a geofence associated with the PSAP using the identifier of the PSAP, wherein the geofence encloses a region within a jurisdiction of the PSAP; c) determining if the current location is within the geofence associated with the PSAP; d) in response to determining that the current location is within the geofence associated with the PSAP, transmitting the emergency data to a PSAP workstation/computing device; and e) providing an emergency response application with a graphical user interface (GUI) accessible by the workstation/computing device at the PSAP, the GUI including: i) an interactive map showing a geographic representation of a jurisdiction of the ESP and graphically depicting one or more incidents within the jurisdiction; and ii) a list of one or more incidents showing at least a subset of the emergency data that is associated with the one or more incidents. A disclosed method for delivering emergency data to a public safety answering point (PSAP), may include: a) providing an emergency response application with a graphical user interface (GUI) accessible by a computing device at a public safety answering point; b) receiving login information for a member of the PSAP from a workstation/computing device; c) generating a temporary access token authorizing the member of the PSAP to access emergency data, wherein the temporary access token is derived from credentials associated with the PSAP; d) accessing a data feed of the PSAP to identify an emergency incident and an associated device identifier; e) associating the emergency incident with an identifier of the PSAP based on the temporary access token; f) receiving emergency data associated with the device identifier from one or more databases, including a current location; and g) transmitting the emergency data to the workstation/computing device for display on the a GUI with: i) an interactive map showing a geographic representation of a jurisdiction of the ESP and graphically depicting one or more incidents within the jurisdiction; and ii) a list of one or more incidents showing at least a subset of the emergency data that is associated with the one or more incidents. A disclosed computer-implemented system for delivering emergency data to an emergency network such as a public safety answering point (PSAP) workstation/computing system, includes: a) an emergency response application communicatively coupled to a network server with a graphical user interface (GUI) accessible by a PSAP workstation/computing device through the emergency network, wherein the emergency response application is configured to: i) receive emergency data regarding an emergency incident with a device identifier and a current location; and ii) an interactive map showing a geographic representation of a jurisdiction of the emergency network and graphically depicting one or more incidents within the jurisdiction, wherein the one or more incidents includes the emergency incident; and iii) a list of one or more incidents showing at least a subset of the emergency data associated with the one or more incidents; and b) an emergency data manager communicatively coupled to a network server and configured to: i) gather emergency data associated with the device identifier from one or more databases, including a current location; ii) retrieve a geofence associated with the PSAP using an identifier of the PSAP, wherein a geofence encloses a region within a jurisdiction of the PSAP; iii) determining if the current location is within the geofence associated with the PSAP; and iv) in response to determining that the current location is within the geofence associated with the PSAP, transmitting the emergency data to the computing device for display through the GUI. A disclosed computer-implemented system for delivering emergency data to an emergency network such as a public safety answering point (PSAP) workstation/computing system, the system configured to: a) provide an emergency response application with a graphical user interface (GUI) accessible by a workstation/computing device at a PSAP; b) receive login information for a member of the PSAP from the computing device; c) generate temporary access token authorizing the member of the PSAP to access emergency data, wherein the temporary access token is derived from credentials associated with the PSAP; d) access a data feed of the PSAP to identify an emergency incident and an associated device identifier; e) associate the emergency incident with an identifier of the PSAP based on the temporary access token; f) receive emergency data associated with the device identifier from one or more databases, with a current location; and g) transmit the emergency data to the computing device for display on the computing device through the GUI with: i) an interactive map showing a geographic representation of a jurisdiction of the ESP and graphically depicting one or more incidents within the jurisdiction, wherein the one or more incidents includes the emergency incident associated with the device identifier; and ii) a list of one or more incidents showing at least a subset of the emergency data associated with the one or more incidents. A disclosed non-transitory, non-volatile, computer readable storage media encoded with a computer program includes instructions executable by at least one processor, that when executed cause the processor to: a) receive available emergency data associated with a device identifier from one or more databases with a current location; b) retrieve a geofence associated with the PSAP using the identifier of the PSAP, wherein the geofence encloses a region within the jurisdiction of the PSAP; c) determine if the current location is within the geofence associated with the PSAP; d) in response to determining that the current location is within the geofence associated with the PSAP, transmit the emergency data to a PSAP computing device; and e) provide an emergency response application with a graphical user interface (GUI) accessible by the workstation/computing device at the PSAP. The GUI includes: i) an interactive map showing a geographic representation of a jurisdiction of the PSAP and graphically depicts one or more incidents within the jurisdiction, wherein the one or more incidents includes the emergency incident associated with the device identifier; and ii) a list of one or more incidents showing at least a subset of the emergency data associated with the one or more incidents. Another disclosed method is for displaying information to emergency response providers on a spatial map. The method includes: displaying a location of an emergency on a map; displaying one or more emergency assets proximal to the location of the emergency; and displaying one or more data layers around the location of the emergency, wherein the data layers may include weather, traffic, and hazards. Emergency assets may include, but are not limited to, medical (for example ambulances, defibrillators, etc.), fire (for example, fire trucks, fire extinguishers, fire hydrants, etc.), police and safety assets, etc. Turning now to the drawings wherein like numerals represent like components,FIG.1illustrates an emergency data manager100which is operative to communicate with various multiple Enhanced 9-1-1 (E911) or Next Generation 9-1-1 (NG911) emergency networks170via network connections175. E911 and NG911 emergency networks are defined according to the National Emergency Number Association (NENA) standards which define applicable network architectures and protocols for communication between various network entities within the network architectures. An emergency network may also be referred to as an emergency service provider (ESP) and includes various public and private emergency service providers such as a public safety answering point (PSAP), a public safety services (PSS) as well as private emergency service providers. Put another way, an ESP is an organization that owns and operates an emergency network where the emergency network includes the infrastructure, network entities, communication devices and other equipment required to provide the emergency services. InFIG.1, double arrowed lines represent operative coupling which may be implemented as backhaul connections between network entities, or as wireless connections between network entities and devices. Curved, dotted lines inFIG.1represent network connections or data connections over which data may be sent and received by respective devices, network entities or by combinations of devices and network entities sending data to, and receiving data from, each other, accordingly. The network connections may be Internet connections and may further include Virtual Private Network (VPN) pathways or other secure connections. The emergency data manager100is operatively coupled to emergency networks170via operative coupling178, which may be implemented as network connections175through the Internet190. The network connections175may include an Internet protocol (IP) connection between each of the emergency networks170and the emergency data manager100and may be connection oriented or connectionless. For example, the network connections175may include IP connections which may include a TCP (Transmission Control Protocol, also referred to as Transport Control Protocol) connection, a UDP (User Datagram Protocol) connection or a combination of both such as UDP over TCP, etc., or a combination of TCP and UDP connections, etc. An IP connection may further employ one or more TCP sockets or one or more WebSocket connections. The emergency networks may have backhaul connections173to the Internet190and backhaul connections176to national or regional emergency networks180. The emergency data manager100may operate as an interface between the emergency networks170, databases120and devices160, to provide emergency data to the emergency networks170. The emergency data manager100is operative to retrieve various types of emergency data such as location data, medical data, sensor data, camera data and other data, etc., determine the appropriate emergency network170authorized to receive specific emergency data, and provide that specific emergency data to the authorized emergency network. The emergency data manager100may, under some circumstances and for certain types of emergency data, store obtained emergency data in one or more databases which may be distributed databases. The emergency data manager100may communicate with, and retrieve and obtain data from, the various databases120, and may also receive and store emergency data from the devices160. The emergency data manager100determines the authorized emergency network using a geofence database101which includes boundary information for all of the emergency networks170and also for national or regional emergency networks180. The various emergency networks170may include various public safety answering points (PSAPs). Each emergency network may include an emergency dispatch center and employ a computer aided dispatch (CAD) system. Each emergency network170includes at least one workstation140, which may be a CAD system, a call handling system or some other type of workstation, and which provides various graphical user interfaces (GUIs) on a display141for use by emergency network personnel. Each individual emergency network170may include an emergency call handling system which is operatively coupled to a PSTN (public switched telephone network) and various wireless networks110via appropriate backhaul connections171. The various emergency networks170are each operative to receive emergency calls103from a variety of devices160and a variety of device types. Each individual emergency network170may also receive emergency alerts105and establish emergency sessions108from the various devices160over the Internet190. An emergency alert105may be sent as, for example, short message service (SMS) messages, SMS data messages, instant messages (IM), multi-media messages (MMS), email, or other formats of messages sent as Internet Protocol (IP) messages. For example, IP based messages may be sent using TCP, UDP, SIP, HTTP, or other mechanisms, etc. Emergency sessions108may also be established using these same, or other, IP protocols. An emergency session108refers to communication over an Internet connection between any the various types of devices160and an emergency network, where there is bi-directional communication between one of the devices160and a particular emergency network of the emergency networks170. One example of an emergency session108is a Voice-over-IP (VoIP) call using Session Initiation Protocol (SIP). Another example is an IP call using H.323 protocol, or some other communication protocol, etc. An emergency alert105may be, but is not limited to, data sent from a device160to a given one of the emergency networks170. Because the emergency alert105will contain information that identifies the specific device160that sent the alert, the specific emergency network that received the emergency alert105may be able to respond to the device160by sending a response or acknowledgement message, or by making a call-back if the device160is for example, a mobile telephone such as a smartphone107. The information that identifies a specific device160is referred to herein as a “device identifier.” The various types of devices160that may communicate with an emergency network include, but are not limited to, desktop computers, laptop computers, tablets, mobile phones, smartphones107, smartwatches111(or other health and medical tracking devices), medical bracelets109, and various wired devices which may be Internet-of-Things (IoT) devices113which are operative to send and receive data from a wireless network such as, but not limited to, a 5thgeneration mobile network (5G network). A medical bracelet109may be a type of IoT device in some instances. The medical bracelet109may be operative to transmit an emergency alert105to an emergency network. Emergency calls may also be made from landline phones connected to a PSTN and medical bracelet109and/or health monitoring device, such as a medical bracelet109, may use a wireless access point connected to the PSTN to place an emergency call103or send emergency alert105. Each of the devices160may also be operative to send data updates106to various databases120. The databases120may contain protected data in that the data is subject to various statutorily defined protections, such as, but not limited to, HIPPA, GDPR, or other statutorily defined data protection and data privacy requirements. The databases120may include location databases121, medical databases123and other databases125with various personally identifiable data related to device160users. The data contained in the databases120is referred to as “emergency data” and may be retrieved by the emergency data manager100via an IP connection161. In each emergency network170, at least one workstation140includes one or more processors that are operative to execute one or more emergency services related applications such as an emergency response application144. The workstation140includes a display141operative to display one or more graphical user interfaces (GUIs), such as GUI142and GUI143, which are related to, and provided by, the emergency response application144. The emergency response application144is operative to communicate with the emergency data manager100. The emergency data manager100is included within an emergency data management network102which may include one or more servers, and one or more databases such as geofence database101. The emergency data manager100may be implemented as a server having at least one processor, or may be implemented as a distributed system with multiple servers, processors, memory and databases, and may further provide cloud-based, software-as-a-service (SaaS) features and functions. The GUI142and GUI143, in conjunction with the emergency response application144, are operative to retrieve and display emergency data provided by the emergency data manager100. The GUI142and GUI143provide communication between the workstation140and the emergency data manager100. The GUIs may each be provided as a web browser interface, such as a cloud-based application interface (i.e. a software-as-a-service SaaS interface), or via a web browser plug-in, or may be associated with applications running as executable instructions, executed by one or more processors on the machine/workstation on which the GUIs are displayed, or by any other software implementation mechanism. Emergency services personnel may receive appropriate emergency services information and view emergency data via the GUI142, GUI143and other GUIs, and place dispatch calls to emergency responders who receive the dispatch calls and emergency data on various emergency responder devices150accordingly. Emergency responders, also referred to as emergency service providers (ESPs) may utilize a variety of emergency responder devices150which may include, but are not limited to, desktop computers, laptop computers, tablets, mobile phones, smartphones, radios (i.e. walkie-talkies), in-vehicle computers, etc., all of which are operative to display emergency data to the emergency responders. The devices150may be operative to send emergency data requests to a respective emergency network170and also authentication data. The devices150communicate with the emergency networks170over a combination of wireless networks110and proprietary wireless networks that provide wireless communications links177. Each of the devices150may include a mobile emergency response application, that provides a GUI155and that is operative to communicate with the emergency response application144and the emergency data manager100. An emergency data request from an ESP device150, may be sent by an appropriate one of the emergency networks170to the emergency data manager100such that the emergency data manager100may identify the emergency and any emergency data pertaining to the emergency stored by the emergency data manager100or contained within the various databases120, and transmits the pertinent emergency data to the requesting ESP device150. In other words, in some implementations, the emergency data manager100may serve as a data pipeline for ESP devices150through which the ESP devices150may request and retrieve reliable emergency data through secure pathways using defined protocols and formats. The emergency data may be, but is not limited to, accurate location data, that is critical for responding to an emergency. The emergency data manager100is operative to obtain emergency data from various sources including other servers, databases and devices160. In one example of operation, an emergency alert105may be triggered by a device160in any of various ways such as, but not limited to, device fall detection, by the user pressing a soft button or a physical button (i.e. a “panic button”), a voice command, a gesture, or autonomously based on other sensor data such as via a smoke, carbon-monoxide, burglar alarm, or some other alarm, etc. In some situations, the user may confirm the emergency or provide authorization for sending the emergency alert105. Emergency data, such as enhanced location data, medical data, or other data, may be sent by the device160to an appropriate one of the emergency networks170as part of the emergency alert105, or may be sent as data updates106to a specific database of the various databases120. The emergency data manager100may interact with the given emergency network to access and obtain the emergency data, or the emergency network may send an emergency data request to the emergency data manager100such that the emergency data manager100may search or query the various databases120in response to receiving an emergency alert105. In some implementations, an emergency data request may be sent by the emergency data manager100, over the IP connections161, to the various databases120in response to an emergency alert105received by an emergency network. The emergency data manager100or the emergency network may format stored emergency data or any received emergency data into a format that is compatible with industry standards for storing and sharing emergency data. For example, the emergency data may be formatted to be compatible with National Emergency Number Association (NENA) standards. Where emergency data is stored by the emergency data manager100, emergency data requests may be sent to the emergency data manager100by an emergency network, such as via an HTTP GET request. Therefore, emergency data requests may be sent from any one of the emergency networks170to the emergency data manager100. The emergency data requests may utilize Location Information Server (LIS) protocol. For emergency data related to location, the data may include, but is not limited to, device generated location data (such as device160GPS chipset data), location information such as Location-by-Reference, Location-by-Value, etc. from, for example a, Location Information Server (LIS) or from other sources. Each of the emergency networks170may be operatively coupled, via appropriate backhaul connections176, to one or more national or regional emergency networks180. The national or regional networks180each include an emergency event application181which is operative to, among other things, display emergency events for a hierarchical view of emergencies being handled by one or more of the emergency networks170. FIG.2provides an example implementation of the emergency data manager100shown inFIG.1. The emergency data manager100includes a set of data ingestion modules258and a set of retrieval modules259. The set of data ingestion modules258are operative to communicate with the various databases120to obtain emergency data and may include a location ingestion module251, an additional data ingestion module252, and one or more multimedia ingestion modules253. The location ingestion module251is an emergency location service ingestion interface which is operative to post or receive emergency locations. The location ingestion module251may be a REST API that is operative to receive an HTTP POST including location data when an emergency alert105is generated or when an emergency call103is received from a device160. The location data may include a location generated concurrently or in response to the generation of the emergency alert105, which may initiate an emergency call103or emergency session for requesting emergency assistance. This generated location data may be, for example, location data from a device160GPS chipset, such as GPS coordinates. This data may also include data from a device160inertial-measurement-unit (IMU). The location data may be generated before an emergency alert105such as, for example, when a medical bracelet IMU detects that a patient has fallen. In another example, when an emergency call103is made from a device160, the location ingestion module251may receive a location recently generated by the device160GPS chipset, or by a device160triangulation algorithm, or other device160location mechanism, thereby ensuring that a location for the emergency is available as quickly as possible. The location data may include a device-based hybrid location generated by a device160which has sent an emergency alert105. A GPS chipset within the device160may generate the location data. The location data may also include a location data generated by a second device160that is communicatively coupled to the device160that sent the emergency alert105. For example, a wearable device such as a medical bracelet or smartwatch, that does not include location capabilities, may use the location services location from a mobile phone with which it is paired. The location ingestion module251may communicate with a device160via a mobile application installed on the device160or via firmware or an operating system of the device160. The location data generated by a device160prior to an emergency occurrence may be accessible by an authorized one (based on device160location) of the emergency networks170during an emergency. For example, a taxi company may have software that transmits the location of its cars or assets to the emergency data manager100, or another server, preemptively. Thus, when an emergency arises, the location of the affected taxi can be made accessible quickly to send for help. Further, location data generated by a device160after an emergency has commenced may be made accessible to one of the emergency networks170during the on-going emergency. For example, updated location data of a hijacked taxi may be periodically transmitted to the emergency data manager100and made accessible to one or more of the emergency networks170. The additional data ingestion module252may be an interface for posting or receiving static or dynamic emergency profile data. Such additional data may include, but is not limited to, medical data, personal data, demographic data, and health data, which may be obtained from the various databases120. For example, medical data may include information relating to a person's medical history, such as medications the person is currently taking, past surgeries or preexisting conditions. Personal data may include a person's name, date of birth, height, weight, occupation, addresses such as home address and work address, spoken languages, etc. Demographic data may include a person's gender, ethnicity, age, etc. Health data may include information such as a person's blood type or biometrics such as heart rate, blood pressure or temperature. Additional data may further include data received from connected devices such as vehicles, IoT devices113, and wearable devices such as medical bracelet109, smartwatch111or other devices, etc. For example, intelligent vehicle systems may generate and send data regarding a crash, such as the speed at which the vehicle was moving just before the collision, where the vehicle was struck, the number of occupants, etc. The additional data ingestion module252may be a REST API, for example using JSON (JavaScript Object Notation). In another example of operation, if an emergency call103is made from a mobile phone, or if an emergency alert105is sent, the mobile phone may receive a heart rate of the person who made the emergency call from a smartwatch111worn by the person and communicatively coupled to the cell phone via a Wi-Fi™ or Bluetooth™ connection or some other wireless connection. The mobile phone may therefore send the heart rate to the additional data ingestion module252, along with any other additional data, in an HTTP POST. The additional data ingestion module252may communicate with a device160via a mobile application installed on the device160or integrated into the firmware or operating system of the device160. Additional data may also be sent to the additional data ingestion module252from a network server. The additional data ingestion module252may be accessed by any connected platform that receives data that might be relevant in an emergency. Connected platforms, such as the various databases120, may therefore send additional data to the additional data ingestion module252at any time. A website, web application, or mobile application may communicate with the additional data ingestion module252and may allow device160users to create profiles to send additional data included in the profiles to the additional data ingestion module252every time a profile is created or updated. A third ingestion module, multimedia ingestion module253, may provide an interface for posting or receiving data relevant to emergencies that is not received by the location ingestion module251or the additional data ingestion module252, such as audio or video streams obtained during an emergency from a device160that is proximal to the emergency. In one example of operation, if an emergency alert105is generated by an intelligent vehicle system installed in a vehicle in response to the vehicle experiencing a collision, the emergency alert105is sent to one of the emergency networks170by the intelligent vehicle system or by another device160communicatively coupled to the intelligent vehicle system, such as a mobile phone coupled to the intelligent vehicle system via Bluetooth™. In response to generating the emergency alert105, the intelligent vehicle system may additionally begin streaming audio and video from microphones and cameras installed inside or outside of the vehicle to the emergency data manager100through the multimedia ingestion modules253. A mobile phone communicatively coupled to the intelligent vehicle system may additionally or alternatively stream audio or video from microphones and cameras integrated into the mobile phone to the emergency data manager100through the multimedia ingestion modules253. The one or more multimedia ingestion modules253may be REST APIs that are accessed with an HTTP POST. After receiving the relevant data, the set of data ingestion modules258can store the data in one or more databases257. The emergency data manager100, databases257may include a location database, the geofence database101, and one or more other additional data databases. The emergency data manager100databases257are operatively coupled to, or otherwise accessible by, one of the emergency networks170. The set of data ingestion modules258tags or otherwise associates the data received by the modules with an identifier of a user or specific device160associated with the data. For example, the set of data ingestion modules258may tag the data received by the data ingestion modules258with a user ID number, an email address, or a phone number (i.e. caller ID), a MAC address, or other device or user identification information, etc. The data ingestion modules258may also tag the data received by the emergency data manager100based on the data source using, for example, a device name or type, an application name, user name, phone number, corporate account, or etc. An individual or group of individuals may be associated with multiple identifiers. In an example of operation, if the location ingestion module251receives a location generated by a phone associated with the phone number +1-555-555-5555, associated with John Doe, the additional data ingestion module252may also receive a heart rate from a smartwatch associated with the email address [email protected], which is an identifier that is also associated with John Doe. In this example, the set of data ingestion modules258tag the location with the phone number “+1-555-555-5555,” and tag the heart rate with the email address “[email protected],” thereby associating both the location and the heart rate with John Doe in the emergency data manager100databases257. Ingestion data that enters the emergency data manager100may include various data fields and associated data entries within the data fields. The emergency data manager100maintains a list of expected data fields so that the data entries can be entered within a specific data field. The emergency data manager100may include a set of retrieval modules259such as a location retrieval module254, an additional data retrieval module255, and one or more multimedia retrieval modules256. The location retrieval module254may be an interface for retrieving location data from the emergency data manager100databases257. The location retrieval module254may be a JSON REST API operative to receive a query or request such as, but not limited to, an HTTP GET request, from the emergency networks170or an ESP device150. The location retrieval module254may provide a single GET endpoint for retrieving either the latest or paginated list of locations for a specific caller ID. For example, a phone number associated with a device160from which a location was received may be included in a header, body, or metadata of a request sent to the location retrieval module254. The emergency data manager100may then retrieve a location or set of locations from the emergency data manager100databases257and deliver the location or set of locations to the relevant authorize emergency network170or to an ESP device150associated with the authorized emergency network. The location retrieval module254may be a location information server (LIS), in which the LIS may further be a NG911 standards-based XML API for the retrieval of location data from the emergency data manager100databases257. The location retrieval module254may be operative to accept HELD requests from the emergency networks170or from ESP devices150and to return location data for a specific caller ID or anonymous reference. The set of retrieval modules259may also include an additional data retrieval module255, which may be implemented as a JSON REST API for the retrieval of emergency or additional data. Additional data may include, but is not limited to, medical data, personal data, demographic data, health data or other data which may be protected data. Additional data may also include data received from connected devices160such as, but not limited to, vehicles, IoT devices, and wearable devices. The additional data retrieval module255is operative to receive a query or request, such as an HTTP GET request, from an emergency network170or ESP device150. The additional data retrieval module255may then, in response to a request, retrieve additional data associated with a specific or particular identifier of a user or a device160associated with the user, such as a phone number, and return the data to the emergency network170or ESP device150. The set of retrieval modules259further includes one or more multimedia retrieval modules256, which function similarly to the location retrieval module254and additional data retrieval module255, for the retrieval of data stored in the emergency data manager100databases257not retrieved by the location retrieval module254or additional data retrieval module255. The emergency data manager100determines which of the emergency networks170and associated ESP devices150have authorization to receive particular types of emergency data. For example, a given emergency network or ESP device150may, in certain circumstances, be granted access only to a particular subset of emergency data. For example, a police officer may only be given access to the location emergency data, while an EMT (emergency medical technician) may only be given access to an additional data emergency data. However, a given emergency network such as a national or regional emergency network180, or associated ESP device150, may be given differential access to the entirety of the emergency data, or to particular emergency data categories within the databases257based on any factor or set of factors. A management portal may be provided to determine which emergency data categories are returned from one of the emergency networks170to a particular emergency network or ESP device150. Other data services corresponding to the various databases120may also be coordinated with respect to granting access to protected data. FIG.3provides an example emergency data manager100. The emergency data manager100includes network components302, at least one processor310, and at least one non-volatile, non-transitory memory330in addition to RAM. The network components302may include one or more network transceivers for Ethernet connectivity to other network entities and an Internet connection. The memory330stores executable instructions and data such as executable instructions for an operating system331and various applications332. The memory330also stores data333which may provide a location and geofence data cache and other data. The processor310may be implemented as one or more microprocessors, ASICs, FPGAs, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or devices that manipulate signals based on operational instructions. Among other capabilities, the processor310is configured and operative to fetch and execute computer-readable instructions (i.e. executable instructions) stored in the memory330. For example, the operating system331executable instructions, when executed by the at least one processor310, may provide a kernel351, libraries353(i.e. application programming interfaces or “APIs”), an application layer350or “user space” within which the various applications are executed, and an IP protocol stack355. The applications332executable instructions, when executed by the at least one processor310, also provide data retrieval modules371, data ingestion modules373, a geofence module375, a mapping module377and one or more emergency network managers379. Emergency network profiles335, stored in memory330, may be accessed by the various modules and the emergency network managers379to access information needed to communicate with various emergency networks. The emergency network managers379communicate with the other modules of application370via a set of APIs378. The processor310may further execute a set of application agents357which facilitate communication between the IP protocol stack355and the application370via various APIs358. The application agents357are operative to, among other things, provide API communication between the various applications332and the kernel351. The emergency data manager100may be implemented as a cloud server. The term “cloud server” as used herein, refers to a server, accessible by an Internet connection, that is operative to host one or more applications that may be accessed by a computing device using a Web browser or an application resident on the computing device. The emergency data manager100is operative to provide a cloud-based application such as a software-as-a-service (SaaS) accessible remotely using a computer or workstation connected to the Internet and operatively coupled to the emergency data manager100. All of the components of the emergency data manager100are operatively coupled by an internal communication bus301. As used herein, components may be “operatively coupled” when information can be sent between two such components, even though there may be one or more intermediate or intervening components between, or along the connection path. Therefore, any of the various components with the emergency data manager100, and in other example network entities and devices described herein, may be understood herein to be operatively coupled to each other where appropriate, and to be executing on one or more processors that are further operatively coupled to a memory that stores executable instructions (also referred to as “software code” or “code”) for implementing the various components. Operative coupling may also exist between engines, system interfaces or components implemented as software or firmware executing on a processor and such “software coupling” may be implemented using libraries (i.e. application programming interfaces (APIs)) or other software interfacing techniques as appropriate. Such libraries or APIs provide operative coupling between various software implemented components ofFIG.3. A “module” as used herein may be a software component. All of the components and modules described herein may be implemented as software or firmware (or as a combination of software and firmware) executing on one or more processors, and may also include, or may be implemented independently, using hardware such as, but not limited to, ASICs (application specific integrated circuits), DSPs (digital signal processors), hardwired circuitry (logic circuitry), or combinations thereof. That is, any of the components or modules disclosed herein may be implemented using an ASIC, DSP, executable instructions executing on a processor, logic circuitry, or combinations thereof. In other words, the components and modules may be implemented as hardware, software or by combinations thereof. Therefore, each of the components and modules disclosed herein may be considered a type of apparatus that may be implemented and operate independently from the other components in the system. The various embodiments also include computer readable memory that may contain executable instructions, for execution by at least one processor, that when executed, cause the at least one processor to operate in accordance with the emergency data manager100and other functionality herein described. The computer readable memory may be any suitable non-volatile, non-transitory, memory such as, but not limited to, programmable chips such as EEPROMS, flash ROM (thumb drives), compact discs (CDs) digital video disks (DVDs), etc., that may be used to load executable instructions or program code to other processing devices or electronic devices such as those that may benefit from the features and methods of operation herein described. The executable instructions may also include the various operating system environments and the kernel. The emergency data manager100is operatively coupled to a geofence database101which stores jurisdictional boundary data for various emergency networks170as well as for the national or regional emergency networks180. The emergency data manager100is operative to store and retrieve emergency data from the various databases120, and may function as an interface between emergency networks, the various databases120and devices160to receive and store emergency data. The stored emergency data can be transmitted or distributed to emergency networks and emergency responder devices150before, during, or after emergencies. The data retrieval modules371, and data ingestion modules373operate similarly to the data retrieval and ingestion modules described with respect toFIG.2. The emergency data manager100may receive emergency data from any of the devices160and such data may include, but is not limited to, locations, medical history, personal information, or contact information. During an emergency, the emergency data manager100is operative to detect the emergency and/or otherwise identify the need to provide emergency data pertaining to the emergency. In response to detecting an emergency, the emergency data manager100is operative to identify any emergency data pertaining to the emergency stored within the databases120, retrieve and transmit the pertinent emergency data to the appropriate emergency network170. The emergency data manager100may act as a data pipeline that automatically pushes emergency data to emergency networks that would otherwise be without access to emergency data that is critical to most effectively and efficiently respond to an emergency. Location data stored within, and/or obtained and provided by, the emergency data manager100, enables emergency responders to arrive at the scene of an emergency faster, and the additional emergency data stored within, and/or obtained and provided by, the emergency data manager100enables emergency responders to be better prepared for the emergencies they face. The emergency data manager100is operative to provide a cloud-based application to multiple emergency networks by establishing network connections via the IP protocol stack355, with various emergency network entities such as a call handling workstation, CAD workstation etc. Other examples of emergency network entities include, but are not limited to, servers, desktop computers, laptops, routers, switches, etc. that are operative to send and receive data. The network connections may be transport control protocol (TCP) connections and may utilize Web Socket connections between the emergency data manager100and an emergency network entity. The geofence module375is operative to determine emergency network jurisdictional boundaries and to show the jurisdictional boundaries on a graphical user interface as a jurisdictional map view. The mapping module377is operative to generate the jurisdictional map view and to also post emergency data locations as location indicators on the map. For example, location indicators may show the location of incoming emergency calls that the emergency network has received, or is receiving. The emergency network managers379provide authentication and login capabilities for the various emergency networks and enable APIs378for communication between the emergency network entities and the geofence module375and mapping module377. Emergency networks and their corresponding emergency network entities are associated with a given geographic boundary. Based on the geographic boundary for a respective emergency network, a jurisdictional map view customized for the respective emergency network may be generated and provided to emergency network entities such as workstations for display. Within the jurisdictional map view for the emergency network, location indicators for emergencies occurring within its geographic boundary may be displayed. The jurisdictional map view for a given emergency network may include one or more geofences associated with the respective emergency network and surrounding areas. A jurisdictional map view for a given emergency network may also include a buffer zone as described below with respect toFIG.17. The jurisdictional map view may include location indicators with various symbols and colors to denote different types of emergencies, data sources, status of emergency call, status of emergency response, etc. A data entry field may also be provided in the GUI143such that a user may input data about a location indicator. An emergency network may customize its jurisdictional map view based on its operational requirements or preferences. In an example use case, an emergency alert may be triggered by a given device160, for example by a user pressing a soft button, a physical button, initiating a voice command, or gesture, or autonomously based on sensor data such as from a smoke alarm. In this example use case, the user may be prompted to confirm the emergency or otherwise provide authorization for sending the emergency alert. Emergency data, such as an enhanced location and additional data regarding the user, such as the user's medical history, may then be delivered by the device160to the emergency data manager100and stored in a database. The emergency data manager100may format the emergency data into a format that is compatible with industry standards for storing and sharing emergency data. For example, the emergency data may be formatted to be compatible with National Emergency Number Association (NENA) standards. The emergency data manager100performs a push operation to push the emergency data to an emergency network entity. Alternatively, an emergency network, such as a PSAP responding to an emergency alert, may query the emergency data manager100with an emergency data request which may be, for example, an HTTP GET request. The emergency data request may be in the form required by the Location Information Server (LIS) protocol. In response to the emergency data request, the emergency data manager100sends an appropriate response including relevant emergency data to the requesting party via an encrypted pathway. The emergency data request may be in the form of an HTTP-Enabled Location Delivery (HELD) and the response from the emergency data manager100may be in the form of a Presence Information Data Format Location Object (PIDF-LO) as defined by the Internet Engineering Task Force (IETF). An example PIDF-LO is shown inFIG.6. The emergency data request includes an authorization code, also referred to as an “authorization token”, in the body, header, or metadata of the request, and the emergency data manager100checks that the authorization code is active before providing a response to the requesting party. Authorization may be provided in the “Authorization” header of the emergency data request using HTTP Basic Authentication. For example, authorization may be a base64-encoded user name and password for an account associated with the requesting party. Emergency data requests are sent over public networks using API access keys or credentials. Transport Layer Security (TLS) may be used in the requests and responses from the emergency data manager100for encryption security. FIG.4provides an example emergency network workstation140which may be a call handling workstation, a CAD workstation, etc., which are examples of emergency network entities. An emergency network may be implemented with multiple emergency network entities of various kinds and therefore may have multiple workstations for example one or more call handling workstations, one or more CAD workstations, etc., in addition to routers, switches, hubs, access points, and other emergency network entities, etc. The example workstation140may include a display403, a user interface405, audio equipment407, network transceiver/s402, at least one processor410, and at least one non-volatile, non-transitory memory430in addition to RAM. The network components may include one or more network transceivers for Ethernet connectivity to other workstations and devices and an Internet connection. The memory430stores executable instructions and data such as executable instructions for an operating system431and various applications432. The memory430also stores data433which may provide data caching. The processor410may be implemented as one or more microprocessors, ASICs, FPGAs, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or devices that manipulate signals based on operational instructions. Among other capabilities, the processor410is configured and operative to fetch and execute computer-readable instructions (i.e. executable instructions) stored in the memory430. For example, the applications432executable instructions, when executed by the at least one processor410, may provide an operating system, a dialer application451, a short-message-service (SMS) application452, an instant message (IM) application453, a web browser455, an email client456and one or more IM and voice applications which may each provide IM and voice call capability separately or in combination. The operating system may include a kernel485, libraries483(also referred to as “application programming interfaces” or APIs) and an application layer450or user space within which the various applications are executed, and an IP protocol stack481. The applications432executable instructions, when executed by the at least one processor410, may also provide the emergency response application144, and an associated GUI, and various emergency network applications479such as, a call handling application, dispatching application, ALI module and an emergency alert module. In some implementations, the emergency response application144may have a component that communicates with the emergency data manager100. However, in other implementations, the Web browser455may provide the GUI142and GUI143enabling communication with a cloud-based application resident on the emergency data manager100. In that case, the Web browser455communicates with the emergency data manager100. In either implementation, communication is established between the workstation140and the emergency data manager100using the IP protocol stack481and a network connection is established which may be a TCP connection and which may include one or more WebSocket connections. The emergency response application144may include geofence434executable instructions and mapping435executable instructions to implement a geofence module473and a mapping module475. The data retrieval module471may communicate with the emergency data manager100to retrieve emergency data. The emergency data may be received by the workstation140via push operations from the emergency data manager100or may receive the emergency data as streaming data over a streaming connection. Application agents457may use APIs458to establish operative coupling between the emergency response application144, the web browser455, the IP protocol stack481and the various emergency network applications479and other applications executed by the at least one processor410. The geofence module473is for managing geofence data for the emergency network including assigning geofences to one or more responders or ESP members, etc. An ALI module provides location information, and a mapping module475displays information on a map on the display403. The geofence module473is operative to provide an interface, such as a GUI, for an ESP user to manage and input geofences including shape files, such as GIS shape files, and other GIS data. The workstation140may also include a dispatch module for communication with emergency responders. An emergency network may include one or more emergency network databases, one or more servers, and one or more workstations. The emergency network may also include a database of emergency responders, such as medical assets, police assets, fire response assets, rescue assets, safety assets, etc. All of the components of the workstation140are operatively coupled by an internal communication bus401. The display403is operatively coupled to the user interface405or may be considered a part of the user interface405such as in the case of a touchscreen which is both a display and a user interface in that it provides an interface to receive user input or user interactions. The user interface405includes a mouse and keyboard and the audio equipment407may include a microphone and a speaker. The call handling module may include a call-handling application that emergency network personnel, such as PSAP personnel, may interact with to send an emergency data request to the emergency data manager100. The response from the emergency data manager100is displayed at the display403. Emergency data may include locations and additional data. Emergency data may further include one or more emergency data categories, also referred to as “data categories”. The emergency data categories may include, for example: service data reference, full name, email, emergency contacts, addresses, language, occupation, phone numbers, websites, gender, height, weight, ethnicity, profile picture, allergies, medical conditions, medications, disabilities, blood type, medical notes, birthday, and additional comments. Emergency data categories may be tagged with tags for specific types of data such as “demographics” or “medical data.” For example, gender, height, weight, ethnicity, profile picture (image-url) may be tagged as demographic data. Medical data protected under HIPAA and other laws may be tagged as “HIPAA” or “private.” Medical data may include information on one or more of allergies, medical conditions or illnesses, medications, disabilities, blood type, medical notes, and other medical information. Medical information protected under HIPAA are encrypted and/or anonymized. Some data are tagged as “general” or another similar tag, wherein access is not specifically restricted. User profiles437stored in memory430contain data that determines which staff members can access the workstation140as well as certain applications. Subscription Model The various emergency networks170or regional emergency networks180may subscribe to the emergency data manager100for a particular device identifier, and thereby receive updates for that particular device identifier. A device identifier may be, but is not limited to, a phone number, an email address, an IP address, a MAC address, or some other identifier etc. When an emergency network receives an emergency alert105for a phone number, the emergency data manager100, or an emergency response application144resident on the emergency network workstation, will check the current location of the emergency alert105and run the current location through geofencing analysis. The emergency network may identify at least one geofence that encompasses the current location of the emergency. If the encompassing geofence is associated with the specific emergency network (i.e. emergency service provider (ESP) or PSAP, then the emergency network may subscribe that device identifier. The emergency alert may be then added to the alert queue or call queue at the workstation140display and include that emergency alert as an incident on an interactive map provided by the emergency data manager100in a cloud-based Web browser-based GUI, or via an emergency response application144GUI. Subscribing to a device identifier provides updated emergency data without need for user queries. Thus, the relevant emergency data for an emergency is available to the emergency network workstation user without requiring any user input thereby saving precious minutes during emergency response. In addition, the credentialing system for ESPs and the geofencing analysis balances the need for quick and accurate emergency data (particularly accurate location) with the need to protect the privacy and security of user data. Updated data may be provided periodically (e.g., every 1 minute, 5 minutes, 10 minutes, 20 minutes, etc.), or alternatively may be updated data only when there is a change, such as when the current location has changed significantly. Initiating a subscription may involve establishing one or more connections between the ESP system and the emergency data manager100. These connections may be TCP and may include WebSocket connections. For example, when a PSAP user (e.g., a call taker, a dispatcher, a supervisor) from the PSAP logs in to a computer terminal within the PSAP system, one or more WebSocket connection may be initiated. The Web Socket connections may be maintained for the duration of the PSAP user's log-in session. In some non-emergency situations, there is a need to access location data, user data, emergency data or sensor data. For example, a user of an electronic device160may grant authorization to family members to access location data for the user. Accordingly, when a family member requests location data for a user, access is granted if there is proper authorization. As another example, a taxi operations company may request and obtain location data of one or more fleet members to keep track of its vehicles (e.g., via onboard vehicle console or terminal). Push to Emergency Network Entity (ESP or PSAP Workstation/Computing Device) An emergency alert105may be generated and sent to an emergency network by any type of device160without an associated emergency call103. Thus, an emergency network workstation140user may see the emergency alert105related incident on the interactive map of the GUI143, but not be assigned to take a call. A PSAP supervisor may review the emergency alert105and may determine that an emergency response is warranted. In such situations, a “push to PSAP” is initiated by sending the emergency alert105from the user device160to the emergency network. The emergency network workstation140user may accept the “push to PSAP” by creating an incident in CAD. This “push to PSAP” capability can be critical because there are currently limited pathways into the PSAP in some jurisdictions. That is, some jurisdictions can currently only accept emergency calls or texts. Using the push-to-PSAP feature, users and user devices can get access to emergency response through alternate pathways. Geofence Determinations When one or more emergencies are determined to be within the jurisdictional boundaries (i.e. within a geofence) of an emergency network, the emergency data manager100may determine whether one or more emergency network users are ready to accept pushed emergency data. Portions of emergency data (e.g. emergency alerts located within a jurisdictional boundary of an emergency network) are determined by the emergency data manager100to be associated with a given emergency network jurisdictional boundary if an emergency call or emergency alert was originated by a device160located within the respective emergency network's jurisdictional boundary. The jurisdictional boundary is defined by one or more geofences. For example, location data of an emergency alert may be filtered to find locations within the geofence of an emergency network. That is, the location data within obtained emergency data may be filtered for locations that are within the jurisdictional boundary defined by one or more geofences for a respective emergency network. If there is no match, the location data of the emergency alert will be filtered for locations within the geofence of another emergency network. After there is a match, the emergency alert is associated with that emergency network and the process is halted. An emergency alert may be associated with one emergency network. Once a portion of obtained emergency data is determined to be associated with a given emergency network, it is likewise associated with emergency network entities, such as workstations, of the given network emergency network, and emergency data is then pushed or streamed to one or more network entities of the corresponding emergency network. In some situations, an emergency alert may be matched with two or more emergency networks. For example, one matches may be to a primary agency (e.g., a PSAP) and one or more secondary agencies (e.g., a regional agency). In some implementations, a regional jurisdictional map view may be provided to regional emergency network, where the regional map view includes one or more jurisdictional boundaries of one or more emergency network. After there is a match, the emergency alert is checked against additional geofences that are available (e.g., additional geofences within a geofence database). The emergency data manager100may establish and maintain one or more persistent connections (e.g., WebSocket, TCP/IP connections, REST, HTTP polling, HTTP streaming, SSE connection, HTTP/2 server push, web hooks, etc.) for various network entities of the emergency network such as a workstation140. In some cases, there may be only one persistent connection associated with a user at the emergency network. In other cases, there may be multiple persistent connections with several users at the emergency network logged-in to various workstations. The emergency data associated with an emergency incident may be pushed to one or more persistent connections. The emergency data manager100is operative to probe the nature and quality of the persistent connection with the appropriate emergency network. For example, the emergency data manager100may check whether the persistent connection is active or inactive or whether the user has been inactive for a set period of time. The emergency data manager100may also check the quality of the connection such as the processing speed, time delay, etc. A member of an emergency network, for example a PSAP staff member, may log into the emergency response application at an emergency network workstation140. The emergency response application may be provided as a cloud-based software application GUI143which may be accessed using the web browser455. The PSAP staff member may submit login information through the GUI143of the emergency response application. When the staff member logs in to the emergency response application by submitting their login information, the emergency data manager100then determines an emergency network account ID associated with the staff member's account and establishes a persistent communication link with the workstation140, automatically subscribing the workstation140to the account ID for the duration of the login session. If the emergency data manager100receives an emergency alert105including a location (e.g., when a panic button is pressed, or an emergency call is made from a device160that sends an emergency alert105to the emergency data manager100including a location generated by the device160and a device identifier), the emergency data manager100retrieves geofences from the geofence database101, and determines if the location falls within any of the geofences which correspond to emergency network jurisdictional boundaries. In response to determining that the location falls within a jurisdictional boundary as defined by a geofence associated with the emergency network, and with the staff member's account ID, the emergency data manager100associates the location with the account ID, and determines if there are any active persistent communication links between the emergency data manager100and any workstations/computing devices subscribed to the emergency network account ID. For example, if a workstation140is subscribed to the account ID and actively linked to the emergency data manager100through the persistent communication link, the emergency data manager100automatically pushes the emergency alert105or emergency data associated with the emergency alert105to the workstation140for display within the emergency response application GUI143. Emergency alerts105or emergency data associated with an emergency alert105that has been pushed to an emergency network are displayed within a GUI143which may include a jurisdictional map view. In response to determining that the location of a device160falls within the jurisdictional boundary defined by a geofence associated with the specific emergency network and identifying at least one persistent communication link between the workstation140(by way of the web browser455) and the emergency data manager100, the emergency data manager100transmits the location and identifier of the device160to the workstation140for display within the GUI143. For example, two different workstations may be associated with a first emergency network and a third workstation may be associated with a second emergency network. When staff members of the two emergency networks log in to the emergency response application provided by the emergency data manager100, each of the three workstations have a separate persistent communication link. In this example, each of the three workstations will be automatically subscribed by the emergency data manager100to the appropriate emergency network account IDs. Assuming each of the two emergency networks have jurisdictional boundaries defined by separate geofences that do not overlap, the respective geofences will have been tagged by the emergency data manager100with the respective emergency network account IDs during the registration process for the emergency response application. In an example of operation, an emergency call103may be made by a device160, which causes the device160to generate a first emergency alert105including a first location of the device160and transmit the first emergency alert105to the emergency data manager100. When the emergency data manager100receives the first emergency alert105, it determines that the first location of the device160falls within one of the geofences stored in the geofence database101associated with a jurisdictional boundary for PSAP A. In response, the emergency data manager100tags the first location with the emergency network account ID associated with PSAP A and the associated jurisdictional boundary defined by the geofence. The emergency data manager100then determines if there are any active persistent communication links between the emergency data manager100and any emergency network consoles subscribed to emergency network account ID for PSAP A and automatically pushes the first emergency alert105to those emergency network workstations. If more than one workstation at PSAP A is logged in, the emergency data manager100will push the first emergency alert105to all emergency network workstations of PSAP A for display within the GUI143in a jurisdictional map view. Any other workstations logged in that are not associated with PSAP A and it's corresponding jurisdictional boundary will not receive the emergency alert105. If the device160that generated the first emergency alert105has changed locations, and a subsequent emergency call is made thereby generating a second emergency alert105including a second location, again the emergency data manager100will, in response to receiving the second emergency alert105, determine whether the device160is located within a jurisdictional boundary defined by a geofence stored in the geofence database101. For example, the emergency data manager100may determine that the device160is now located within a second jurisdictional boundary defined by a second geofence associated with PSAP B. The emergency data manager100will therefore tag the second location within the emergency network account associated with PSAP B and geofence B, and will push the second emergency alert105to any workstations logged in for PSAP B. Using the subscription model, the emergency data manager100can push emergency data to appropriate emergency networks without receiving an emergency data request or query. As a result, the emergency data manager100can use a jurisdictional map view within the emergency response application GUI143to display emergency alerts and emergency data associated with emergency alerts to appropriate emergency networks as the emergency alerts are received by the emergency data manager100in real-time. Using the subscription system to push emergency data from the emergency data manager100to emergency networks provides numerous advantages. For example, the GUI143allows members of an emergency network to see and be aware of all emergencies in their jurisdiction whether or not they are handling or responding to a particular emergency and whether or not an emergency call actually gets connected to the emergency network (e.g., a call that doesn't connect, a dropped call). Additionally, even if a member of the emergency network is not immediately able to respond to an emergency alert, they are still able to see where the emergency is located and when the emergency alert was received. Various emergency responses may be initiated when an emergency call103is dropped, such as for example sending a message to the user, calling back the number, or sending patrols to the location, etc. The emergency response may be automated, such as, dispatch of surveillance drones to the emergency location. The emergency response may be initiated by an emergency network user after reviewing the emergency data. Electronic Devices FIG.5provides an example device160which may be used as an emergency caller device160or as a responder device150. It is to be understood thatFIG.5is an example only, and that a given emergency caller device160or a given responder device150may have more components, less components, or different components than shown, depending on the specific function and type of device. Further, depending on the type of device, there may be hardware only, hardware and firmware, hardware and software, etc. and may therefore be implemented in various ways not limited by the components shown in theFIG.5example. The example device160may be, but is not limited to: a mobile or cellular phone such as a smartphone; a wearable device such as a medical information bracelet, a fitness tracker or a smartwatch; a computer, laptop, or tablet; a vehicle console; an Internet of Things (IoT) device, such as a home assistant (e.g., a connected speaker) or a connected sensor such as a connected smoke and carbon monoxide alarm, a burglar alarm, etc.; or a walkie-talkie or two-way radio; etc. The example device160may include a display503, a user interface505, audio equipment507, network transceiver/s509, antennas511, location components515, sensors517, at least one processor520, and at least one non-volatile, non-transitory memory530in addition to RAM. Network components may include one or more wireless network transceivers for wireless communication such as for cellular communication, Wi-Fi™, Bluetooth™, etc. The memory530stores executable instructions and data such as executable instructions for an operating system531, various applications532and an emergency alert application535in some implementations. The memory530also stores data533which may provide a location data cache and a user data cache. The device160may, in the case of mobile telephones, include a SIM card or other removable, replaceable memory components in addition to memory530. The location data cache be used to store locations generated by the one or more location components515which may include a GPS chipset, triangulation processing, or other location determination technology, etc. User profiles534stored in memory530may contain information related to specific devices user configuration preferences, data sharing permissions, etc. The processor520may be implemented as one or more microprocessors, ASICs, FPGAs, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or devices that manipulate signals based on operational instructions. Among other capabilities, the processor520is configured and operative to fetch and execute computer-readable instructions (i.e. executable instructions) stored in the memory530. For example, the applications532executable instructions, when executed by the at least one processor520, may provide, a dialer application541, a short-message-service (SMS) application542, an instant message (IM) application543, a web browser545, an email client546and one or more IM and voice applications544which may each provide IM and voice call capability separately or in combination. The IM and voice applications544are referred to as “over-the-top” applications because the operate within the application layer of a mobile operating system. The operating system531executable instructions, when executed by the at least one processor520, may provide a kernel521, libraries523(also referred to as “application programming interfaces” or APIs) and an application layer540or user space within which the various applications are executed. All of the components of the device160are operatively coupled by an internal communication bus501. The display503is operatively coupled to the user interface505or may be considered a part of the user interface505such as in the case of a touchscreen which is both a display and a user interface in that it provides an interface to receive user input or user interactions. In some devices, the display503may not include a touchscreen, but may include one or more lights, indicators, lighted buttons, or combinations of these. The user interface505may also include physical buttons such as an on/off button or volume buttons, and the audio equipment507may include a microphone and a speaker. The example device160may also include various accessories that allow for additional functionality. Such accessories (not shown) may include one or more of the following: a microphone, a camera, speaker, a fingerprint scanner/reader, health or environmental sensors, a USB or micro-USB port, a headphone jack, a card reader, a SIM card slot, or any combination thereof. The one or more sensors may include, but are not limited to: a gyroscope, and an accelerometer which may be incorporated into an Inertial Measurement Unit (IMU); a thermometer; a heart rate sensor; a barometer; or a hematology analyzer, or some other type of biometric sensor. An emergency alert component513may be an ASIC or may be implement as, or in conjunction with, an emergency alert application547where the emergency alert application535executable instructions are stored in memory530and executed by the processor520. The emergency alert component513may be configured and operative to record user data, such as a name, address, or medical data of a user associated with the device160. The emergency alert component513may also detect an emergency using features of the device160for example, when a user places an emergency call on a device that has phone call capabilities. The emergency alert component513may also work in conjunction with “fall detection” such as in a medical bracelet which uses the sensors517, such as an IMU (inertial-measurement-unit), to detect if the wearer of the bracelet has fallen and to initiate an emergency call or emergency alert accordingly. The emergency alert component513may also work in conjunction with sensors517such as biometric sensors to detect for example, a cardiac event or some other critical health or safety event and to initiate an emergency call or emergency alert accordingly. A device160user may initiate an emergency alert105by interacting with the user interface505, or the emergency may be detected by sensors517. In response to detecting an emergency alert or a request for assistance, such as a via native dial 9-1-1 call via the dialer application541(which is the phone's native dialer), which may be generated or sent by the device160, the emergency alert component513may send a notification to the emergency network. The notification may be sent as an HTTP post containing information regarding the emergency request for assistance. The notification may include a location (e. g., a device-based hybrid location) generated by or for the electronic device. In response to detecting an emergency request generated or sent by the device, the emergency alert component513may send user data to the emergency network. Regarding emergency responder devices150, responder devices150may include a mapping application for displaying an interactive map of incidents. Responder devices are designed to display incidents within authoritative, administrative or assigned jurisdiction of the specific responder. The credentials of the responders may be matched to one or more geofences and incidents with current location within the geofences are displayed. Responder devices may display incidents based on a proximity radius on the interactive map. For example, a proximity radius may be within 10 meters to 5 kms, between 50 meters to 1000 meters, for example 500 meters. As the responder moves towards an area, new incidents within the proximity radius may be “unlocked” and viewed. Access to Emergency Data After an emergency network user (e.g., a PSAP administrator or PSAP staff member) successfully logs into the emergency response application and a temporary access token is generated for the user, the user can use an emergency response application via the emergency network workstation to display data from the emergency data manager100via, for example, a query process or a WebSocket subscription. Depending on various types of integration, the emergency data may be provided to the emergency network user in various ways. The call-taker can prompt the emergency response application to generate a request for emergency data by submitting an identifier of the electronic device (i.e., a device identifier), such as the phone number of the electronic device, IMEI number, SIM number, name of the user, account ID, user ID, etc. The emergency response application can automatically retrieve the device identifier from a call-handing application installed on the workstation and automatically generate an emergency data request without requiring input from the call-taker. The device identifier may be communicated from the call-handling application to the emergency response application through a Web Socket connection. The Web Socket may couple to the emergency response application at the emergency data manager100. The emergency response application may also be integrated into the call-handling application installed in a PSAP workstation, and may automatically be provided with location data and additional data within a GUI of the call-handling application. The emergency data manager100inFIG.3includes a geofence module375that is operative to protect potentially sensitive emergency data using geospatial analysis. As described above with respect toFIG.2, the emergency data manager100includes data ingestion modules373and data retrieval modules371. The set of data ingestion modules373are operative to receive emergency data or other information that can be useful in responding to an emergency, from a variety of data sources such as various databases120, multiple types of devices160, etc. For example, a smartphone107may send emergency data to the emergency data manager100in the form of an HTTP POST API call in response to a user of the smartphone107initiating a 911 emergency call103. When emergency data (e.g., an emergency location or additional emergency data) is sent from a device160to the emergency data manager100, the emergency data is first processed by the geofence module375before being received by the set of data ingestion modules373. Similarly, when an emergency data request is sent from a requesting party, such as from an emergency response application144or from a responder device150, the emergency data request is processed by the geofence module375before being received by the set of data retrieval modules371for display on a GUI143of the requesting emergency network workstation140. Emergency Response Application As discussed above, a requesting emergency network such as a PSAP may initiate a query or request for emergency data using an emergency response application, which in turn generates the query and transmits the query to the emergency data manager100. The emergency data manager100includes an emergency network manager379for each emergency network to which it is connected. The emergency data manager100has emergency network profiles335which may include credentials for authorizing logins and data acquisitions by the emergency networks. Emergency network users interact with the emergency response application using the GUI143which may be accessed using the web browser455. Alternatively, the workstation140may include a desktop application version as emergency response application144which is operative to provide secure communication with the emergency data manager100. Thus, the GUI143may be a webpage accessible through a web browser, or the GUI143may be is accessed through a desktop application such as emergency response application144. The GUI143may include one or more pages each with their own plurality of interactive elements, such as, but not limited to, entry fields, soft buttons, sliders, maps, images, and videos. The interactive elements of the GUI143may be configured to perform various operations. As an example, a soft button (e.g., a “next” button) instructs the GUI143to navigate from one page to another. Another soft button (e.g., a “submit” button) instructs the GUI143to navigate from one page to another while concurrently instructing the application to store or process information submitted by a user into an entry field elsewhere within the GUI143. An example of the GUI143is shown inFIG.8. Emergency data send to the GUI143by the emergency data manager100may include additional data or information displayed in the GUI143. Additional information can include, but is not limited to: service data reference, full name, email, emergency contacts, addresses, language, occupation, phone numbers, websites, gender, height, weight, ethnicity, profile picture, allergies, medical conditions, medications, disabilities, blood type, medical notes, birthday, and additional comments. The emergency response application GUI143displays additional information included in the emergency data associated with a device identifier as depicted byFIG.8. A user can access the page displaying the additional information by selecting an additional information button or tab within the GUI143. InFIG.8, the GUI143displays emergency data returned from the emergency data manager100within discrete categories of emergency data categories in separate data fields. For example, the GUI143may include a location field801, a demographics field807, a contact Information field809, an addresses field811, and a medical information field813. The “Demographics,” “Contact Information,” and “Addresses” groups of emergency data categories (as described above) are displayed sequentially under a “Personal Information” (as described above) section of the GUI. A Medical Information field813is displayed below the Personal Information section. The GUI143may include one or more tabs to filter emergency data categories. For example, as depicted inFIG.8, GUI143can include a “Caller Information” tab803, and a menu805including a “Location” tab, a “Caller-Provided Locations” tab, a “Devices” tab, and a “Directions” tab. A “Directions” tab can be selected within the GUI143to render a map displaying directions from a PSAP to a location of an emergency situation. The map is capable of providing real-time or near real-time traffic updates. FIG.9depicts a GUI143provided by the emergency response application and including a jurisdictional map view. The page shown provides interactive elements that allow a user to generate an emergency data request using, for example, data entry field901through which a user can submit a device identifier, such as by typing or pasting the device identifier into the entry field901. After submitting a device identifier through the entry field901, the user can prompt the emergency response application to generate and send an emergency data request by selecting a search button. In response to a user submitting a device identifier into the entry field901and selecting the search button, the emergency response application generates an emergency data request including the device identifier and a temporary access token to the emergency data manager100. After receiving an emergency data request including a device identifier, the emergency data manager100retrieves or gathers emergency data associated with the device identifier from one or more databases which may include one or more locations, and a current location. Location indicators are provided on the GUI143to show the various locations. For example, the current location indicator915shows the current location of the caller, and historic location indicator909and historic location indicator913show past locations as the caller has traveled. By moving the cursor over a historic location indicator909, emergency data907is displayed in an overlay showing time, date, and the phone number (i.e. device identifier) of the caller's device. A call queue905is also displayed and a use may select any call from the call queue905to display further information. The field903shows that calls in the call queue905are for a specific jurisdictional boundary910which corresponds to a geofence and which is also displayed on the GUI143. The emergency data907textual description of a current or historical location may include an indoor location, an amount of time elapsed since the current or historical location was received, and an amount of time elapsed since the current or historical location was generated. FIG.10illustrates a GUI143view after selection of a device identifier1001in the call queue to enter the single caller view. The single caller view enlarges or moves the user's map to detail the environment around the selected single caller location1007. In theFIG.10example, call1001has been selected, resulting in the single caller view that shows the single caller location1007. Enhanced location data1003and additional data1009may be available in the single caller view. The single caller view enables the viewing of past location data through the use of a historic locations toggle button1005or historic locations menu1011.FIG.10also illustrates the use of a past location data feature. Toggling the historic locations button1005allows the user to view the past locations, of a particular device identifier in the call queue. Date and time may be displayed when the user selects or moves a cursor over a past location indicator. Past location indicators and the current location indicators may be displayed. Past location indicators are automatically denoted or visibly distinct from current location indicators. For example, past location indicators may be denoted as shades of color, wherein more distant location indicators may be lighter shades, while the current location indicator may be the darkest shade of the color, or a different color.FIG.11provides an example GUI143view where the use has selected to view historic locations using the historic locations toggle button1101for a device identifier associated with the selected call1105in the call queue. Based on the selection to view historic locations, the GUI143displays the last twenty-five historic locations marked by historic location indicators1103. FIG.12shows a zoomed out jurisdictional map view of the GUI143. A device identifier may be entered in the search field1205or a call may be selected from the call queue. A current location field1207provides emergency data for the current location and a historic location field1209provides emergency data for past locations. A jurisdictional boundary1201is displayed that corresponds to a geofence for the specific emergency network and a location indicator1203shows the current location associated with the jurisdictional boundary and the device identifier. FIG.13illustrates non-limiting examples of geofence approximations that can be submitted as jurisdictional boundaries or an “authoritative jurisdiction” for an emergency network such as a PSAP. One or more geofences enclose the geofenced region which is under the authoritative jurisdiction of a PSAP. These jurisdictional boundaries can be displayed in the GUI143by a national or regional emergency network180that has subordinate jurisdictions. In some cases, a geofenced region may be a complex polygon, and is optionally approximated using an appropriate simpler shape. For example, a rectangle (A)1301, two disjointed rectangles, rectangle B1307and rectangle B′1309, a complex polygon C1303with several sides, and a triangle D1305, may each represent different jurisdictional boundaries which are geofenced regions defined by one or more geofences. An administrator of an emergency network, such as a PSAP, may submit the complex jurisdictional boundaries as one or more approximate geofences by specifying points. For example, the PSAP administrator can submit geofenced region A1301by specifying two points—the north-west corner and the south-east corner using a drawing tool provided by the GUI143of the emergency response application. In this example, the two points of the geofenced region are set using two latitude-longitude coordinates. In another example, the multiple-sided polygon C1303may be submitted by specifying the five corners. A PSAP administrator may approximate a geofence for a PSAP by drawing one or more polygons using a drawing tool provided by the GUI143of the emergency response application. A geofence is generated using a series of points that are connected, for example by entering three longitude-latitude points on a map to form a triangular geofence. Approximating a complex geofenced region has several advantages. The geofences are simple and the calculations can be quicker and less cumbersome for applications where exact calculations are not needed. A PSAP administrator can submit a GIS file (e.g., a shapefile) that represents the actual authoritative jurisdiction of the PSAP, which may then be provisioned in the geofence database101. It is appreciated that a GIS file defining the authoritative jurisdiction may be saved in one or more industry-acceptable formats such as a shapefile, a GeoJSON file, KML file, etc. The GIS file includes one or more features such as points, lines, polygons, density, and other shapes. A GeoJSON is open standard GIS file representing geographical features and non-spatial attributes based on JavaScript Object Notation. Features can include points (such as addresses and locations), line strings (streets, highways and boundaries), polygons (countries, provinces, tracts of land), and multi-part collections of these types. A Keyhole Markup Language (KML) file includes geographic annotations and visualization on internet-based maps on Earth browsers. A shapefile is a vector data format for storing the location, shape, and attributes of geographic features. A shapefile is stored in a set of related files, each of which may contain one feature class (e.g., lines, points, polygons, etc.). The shapefile is a file with extension .SHP in ESRI file format where SHP is the feature geometry, SHX is the shape index position and DBF is the attribute data. The geofence database101may be implemented in various ways. One or more databases are searchable using a PSAP identifier, credentials, or other information. An emergency location is searched through several geofences in the geofence database. In some cases, the geofenced region is shrunk for ease of storage and to simplify calculations. FIG.14illustrates examples of geofenced regions defined by one or more geofences within the United States and which may be displayed on a GUI1400for a national emergency network. In this case, an overall jurisdictional boundary1401may be the entire United States. As shown, subordinate jurisdictions defined by geofenced regions (e.g., an authoritative jurisdiction) may cover an entire state (P), a complex shape within a state (Q), and a simple (rectangle) shape (R)1405. Location indicator1403may be related to a specific device identifier within the jurisdictional boundary R1405. However, on a location indicator1407may be related to a cluster of related events and not related to a single device identifier. In other words, national and regional jurisdiction views, as well as for individual emergency networks, may also display location indicators for clusters of related emergencies. These cluster location indicators are visually distinguishable from single device identifier location indicators by, for example, different, size, shape, color, or shading etc. Geofences may be defined on a grid mesh including equal-sized rectangles or grids, for example, on the entire United States. In such scenarios, the grid-lines are used as geofences to define geofenced region comprising each grid. Such grid-geofences may be used as other geofences for filtering, reporting and monitoring emergency data. On an emergency network jurisdictional map view for a specific emergency network, the emergency data manager100obtains emergency data and determines portions of the emergency data that correspond to emergencies occurring within the respective emergency network's geographic boundaries which are defined by geofences. The network entities of that emergency network can therefore display the corresponding jurisdictional map view with location indicators for emergencies occurring within the respective jurisdictional boundary. On a jurisdictional map view that provides a regional view, such as of the entire United States, location indicators may indicate emergencies, or clusters of emergencies, occurring within the jurisdictional boundaries of multiple different emergency networks. Additionally, the GUI143may also provide for sharing of emergency data between emergency networks and enables the viewing of emergencies occurring within neighboring jurisdictional boundaries. To determine the appropriate emergency network for sharing emergency data, the authoritative jurisdiction, as defined by one or more geofences, of an emergency network (e.g. primary agency) has to be evaluated. In case of irregularities (e.g. overlaps, islands, or other irregular features), steps may be taken to check with respective agency, geographical boundaries (national and international borders, county lines, rivers, hills, etc.), or other authority. Call routing data may be analyzed to see which emergency network is answering the emergency call. Raw geofences may be pre-processed to generate processed geofences using a variety of techniques. For removing irregularities, a geofence may be processed to resolve overlaps, remove islands and projections, smooth boundaries, modifying the file format or size, etc. Geographical features (rivers, hills, etc.), administrative features (national borders, county/state lines, etc.) can be compared to geofence boundaries. The geofence boundaries can be processed to match with geographical and administrative features. The geofence boundaries are processed to match with geofence boundaries of adjacent emergency networks, or overseeing emergency networks. For example, a regional emergency network (i.e., a secondary agency) may include one or more primary agencies (e.g., PSAPs). If the geofence boundary of the regional emergency network is known, the geofence boundary of the constituent primary agencies can be matched to remove inconsistencies. In some cases, there may be overlap between geofence of two or more adjacent emergency networks. The emergency data may be shared with the two or more emergency networks to err on the side of making mission critical information to all entities that may be involved in the emergency response. Sometimes, the two or more emergency networks are primary agencies (e.g. PSAPs) and the emergency data has to be shared with one appropriate emergency network. To determine the appropriate emergency networks for sharing emergency data, the authoritative jurisdiction (defined by one or more geofences) of the overlapping emergency networks must be checked with the respective agency, geographical boundaries (national and international borders, county lines, rivers, hills, etc.), sample routing data, etc. In contrast, if the overlapping emergency networks include one or more secondary emergency networks, the overlap may be retained and emergency data may be shared with one or more emergency networks (e.g. one primary agency and two secondary agencies). Referring toFIG.15, two adjacent geofence are shown; a first geofence1507representing a first jurisdictional boundary and a second geofence1509representing a second jurisdictional boundary, for two respective primary agencies (e.g. PSAPs). When the raw polygonal geofence1507is projected on the map, there is an overlap1501and a sliver1503that appears. To process geofence1507to remove overlaps, the overlap1501and sliver1503may be removed and the western boundary of geofence1507will be aligned with the eastern boundary of geofence1509. A buffer zone (e.g., +10 km) is added to one or both of the geofences such that query results within the buffer zone are also returned or such that portions of emergency data may be determined, by the emergency data manager100, to correspond to emergencies occurring within each respective emergency network's geographic jurisdictional boundary as well as an expanded boundary defined by a buffer zone. That is, a buffer zone defines an expanded boundary that is larger than an emergency network's geographic boundary as defined by a geofence. Put another way, the “buffer zone” defines an “expanded polygonal geofence” for a particular emergency network. In many cases, emergency networks have discretion and incentive to respond to emergencies that are proximal to their authoritative jurisdiction. A specific network entity of an emergency network may therefore display a jurisdictional map view that includes a buffer zone that defines an expanded boundary for its specific emergency network. As an example, a geofence that is a circular area with a radius of 10 km would have an area of 100π or ˜314 km2, whereas the same area with a 10 km buffer around its circumference would have yield a combined radius of 20 km and a combined area of 400π or 1256 km2. The buffer is from 0.5 km to 5 km, from 0.5 km to 10 km, from 0.5 km to 15 km, from 0.5 km to 20 km, from 0.5 km to 25 km, or from 0.5 km to 30 km. The buffer is from 1 km to 5 km, from 1 km to 10 km, from 1 km to 15 km, from 1 km to 20 km, or from 1 km to 30 km. The buffer is at least 0.1 km, at least 0.2 km, at least 0.3 km, at least 0.4 km, at least 0.5 km, at least 0.6 km, at least 0.7 km, at least 0.8 km, at least 0.9 km, at least 1 km, at least 2 km, at least 3 km, at least 4 km, at least 5 km, at least 6 km, at least 7 km, at least 8 km, at least 9 km, at least 10 km, at least 11 km, at least 12 km, at least 9 km, at least 14 km, at least 15 km, at least 16 km, at least 17 km, at least 18 km, at least 19 km, at least 20 km, at least 25 km, or at least 30 km. The buffer is no more than 0.1 km, no more than 0.2 km, no more than 0.3 km, no more than 0.4 km, no more than 0.5 km, no more than 0.6 km, no more than 0.7 km, no more than 0.8 km, no more than 0.9 km, no more than 1 km, no more than 2 km, no more than 3 km, no more than 4 km, no more than 5 km, no more than 6 km, no more than 7 km, no more than 8 km, no more than 9 km, no more than 10 km, no more than 11 km, no more than 12 km, no more than 9 km, no more than 14 km, no more than 15 km, no more than 16 km, no more than 17 km, no more than 18 km, no more than 19 km, no more than 20 km, no more than 25 km, or no more than 30 km. Geofences can be used by emergency networks and by the emergency data manager100for reporting results for internal metrics and monitoring the system. For example, the number of emergency data requests, locations provided, “no location found” etc., can be obtained for one or more geofences associated with a PSAP. Using single or combined geofences, the emergency data can be obtained on county-wide, city-wide, postal code, course grid (rectangle overlay), state-wide, or country-wide basis. Ingress and egress counters (e.g., percent of emergency sessions where the location data was received, but not queried) and other similar metrics can be calculated and analyzed to identify problems and spikes. Different geofences are used for retrieval and for reporting. A given incident may be determined to fall within a two or more geofences. Emergency data for the incident is pushed to each PSAP having a geofence that the incident falls within. Emergency data for the incident is pushed to a subset of PSAPs having a geofence that encloses the incident. The location data of an individual device identifier is not pushed to more than one PSAP at one time. In situations where a device identifier egresses a geofence in which communication began and ingresses into a neighboring geofence, the location data is pushed to the neighboring PSAP with jurisdiction over the ingressed geofence. When a device identifier egresses or ingresses a geofence, the location indicator is preserved with a notation regard the time of egress or ingress. The location indicator is preserved for a configured time or manually removed. Returning briefly toFIG.3, the emergency data manager100applies the geofence module375to the data retrieval modules371and data ingestion modules373. Emergency data obtained from a device160can be provided to an emergency network such as a PSAP. The geofence module375may perform upstream filtering to restrict sending of data from devices160to an emergency network from geographical areas that are not covered by the emergency network's jurisdictional boundaries as defined by one or more geofences in the geofence database101. The geofence module375may restrict the data ingestion modules373from obtaining any emergency data that could result in accidental breaches of privacy. The data ingestion modules373of the emergency data manager100therefore drops location payloads that do fall within the geographical region covered by the jurisdictional boundaries of emergency networks that the emergency data manager100services. The emergency data manager100may include or access databases for storing emergency data. For example, the data retrieval modules371may obtain emergency data relating to one or more emergency incidents from a database to send to a PSAP. The emergency data is sent to the PSAP automatically without requiring a request for the data from the PSAP. The geofence module375is applied at the data retrieval modules371for retrieved emergency data to protect against abuse and limit the scope of security breaches in cases where credentials have been compromised. One or more geofences are associated with one or more credentials associated with an emergency network agency or organization. The credentials associated with an emergency network agency or organization confers authorization to access data such as emergency data from the emergency data manager100. Specific authorization to access data may be granted individually to members of a PSAP through tokens derived from the credentials for that PSAP. When the data retrieval modules371check the coordinates of current location data (within retrieved emergency data) associated with a device identifier with the geofence or geofences associated with the credentials in an emergency data request. If the current location is within the geofence region, then the current location is returned to the emergency response application and displayed within the GUI143. If not, the data retrieval modules371will return a “not found” message (as opposed to the retrieved location is outside the geofence) to protect privacy. FIG.16depicts an emergency dispatch center routing and dispatching in City A in a map view1600. City A may be serviced by an emergency service provider (e.g., a PSAP), which may have authoritative jurisdiction over a geofence and a jurisdictional boundary1601. City A may be serviced by an emergency network (e.g., a hospital) with an administrative jurisdiction over a geofence. City A may be serviced by an emergency network (e.g., a crisis management center) with an assigned jurisdiction over a geofence. As shown, a PSAP1602may have an authoritative jurisdictional boundary1610defined by a circular geofence. In an operational example, if an emergency alert with a location is received, the emergency alert may be determined to be in the jurisdiction of PSAP1602because the device sending the emergency alert is located with the jurisdictional boundary1610. The location associated with the emergency alert may be searched within one or more geofences to determine a geofence that encompasses the location. Once the PSAP1602is identified, the PSAP1602is subscribed to the device identifier associated with the emergency alert (e.g., a phone number). A buffer region may be defined around the boundary of the geofence and the locations falling within the buffer region can be treated as locations falling within the geofence. The buffer region may be 1 meter to 10 km, or between 200 meters to 5 km, preferably 2 km. AlthoughFIG.13shows circular geofences (also referred to as proximity jurisdictions), it is understood that geofences may of any regular shape (e.g., square, rectangle, polygon) or irregular shapes. For emergency response, an emergency service provider (public or private entities) may be given jurisdictional authority to a certain geographical region or jurisdiction (also referred to as “authoritative jurisdiction”). However, in many cases, an emergency network may have an area of administration not based on authority, but based on various factors such as capacity, resources, funding requirements, or practical limitations (also referred to as an “administration jurisdiction”). In some cases, an area or region is assigned to an emergency network or responder for planning and resource allocation, although the emergency network or responder may respond to emergencies outside the area (e.g., a police beat) (also referred to as an “assigned jurisdiction”). For example, the geofences1606may define assigned jurisdiction of police officers1604a,1604band1604cwithin the authoritative jurisdiction1610of a PSAP1602which is operated by a police station. In another example, authoritative jurisdictions, administrative jurisdictions and assigned jurisdiction may be treated differently. For example, the smaller circular geofences may define assigned jurisdictions1606of emergency responders1604a,1604band1604c(e.g., police patrols) within a larger authoritative jurisdiction1610of police department PSAP1602. When an emergency alert with a location is received, the emergency data manager100may allow emergency responders (e.g., a police patrol in1604a) access to emergency data even if it does not fall within its assigned jurisdiction1606a, but within the larger authoritative region1610. Here, current location1608aand current location1608bare depicted as a circle including the location accuracy radius. A current location may fall within the geofence of only one emergency network (e.g., PSAP). However, an emergency location may fall within geofences of more than one emergency network or within buffer regions. For example, an emergency alert with current location1608afalls within two geofences—the larger geofence1610and the subset geofence (sub-geofence)1606b. The emergency data manager100provides a subscription to both the emergency network PSAP1602(e.g., a police department) and the emergency network1604b(e.g., a police patrol) and makes the emergency data available to both emergency networks. Providing access to emergency data is advantageous when the emergency network1604has an assigned jurisdiction (sub-geofence) within the authoritative jurisdiction of the larger geofence. The emergency data manager100may choose the appropriate emergency network to provide subscription to. For example, the emergency data manager100may send the subscription to the authoritative emergency network (e.g., the police department) and allow the emergency network to manage resources and assign the incident to appropriate emergency network for the emergency response (e.g., a different police patrol1604awhen police patrol1604bis occupied). Additionally, different types of responders may have different or overlapping jurisdictional boundaries and therefore different or overlapping geofences. For example, police may have a different geofence than a fire department, state troopers may have a different geofence than local police, etc. Emergency alerts may be associated with an emergency type by the emergency data manager100, such as, but not limited to, medical, fire, police, etc. The emergency data manager100may therefore subscribe the emergency network (i.e. medical, fire, police, etc.) based on the associated emergency type and a geofence corresponding to the jurisdictional boundary of a corresponding emergency network. In other words, for a fire emergency, the fire department emergency network, if different from police but having an overlapping geofence, only the fire department emergency network would be subscribed to the emergency data and the police emergency network would not be subscribed to the data. The jurisdictional map view that may be displayed on the GUI143of an emergency network workstation140may also, in addition to displaying a location of an emergency on the map, display other useful information using data layers or data overlays that can be configured to be shown on the display as needed. For example, the GUI143may be configured to display the locations of one or more emergency assets proximal to the location of the emergency. One or more data layers (i.e. data overlays) may also be displayed around the location of the emergency, such as but not limited to, data overlays showing weather, traffic, and hazards. Displayed emergency assets may include, but are not limited to, medical (for example ambulances, defibrillators, etc.), fire (for example, fire trucks, fire extinguishers, fire hydrants, etc.), police and safety assets, etc. Displayed safety assets may include, but are not limited to, police, private security personnel, fire extinguishers, fire hydrants, chemical showers, etc., responders such as EMTs, paramedics, etc., and volunteers (fire marshals, etc.). The GUI143may be configured to display geographical data layers, or overlays, including “police assets”, “fire response assets”, “safety assets”, “vehicle rescue assets”, “pet rescue assets”, “water rescue assets” or other data overlays, etc. In other words, the jurisdictional map view may be configured to display data layers useful for gaining situational awareness about an emergency and response. For example, the location of nearby safety assets such as a tow truck, medical assets such as a hospital, an urgent care center, etc. and fire assets like the fire station can be displayed. Various other types of data layers including, but not limited to, weather (e.g. a storm system), traffic (e.g. gridlock and congestion) and safety hazards (e.g. icy bridge) can also be displayed on a map proximal to an emergency location. In another example, a data layer with weather conditions may be displayed when there are emergencies related to flooding in an area. Medical assets such as urgent care units may be displayed during a medical emergency. Thus, the GUI143may be configured to display relevant data layers based on type of emergency, severity of the emergency, type of response, etc. The emergency response application GUI143is also customizable and configurable in other ways. For example, the GUI143may be configured to display information relevant to the individual authority, or to restrict information from being accessed by an individual authority. For example, the GUI143available to a PSAP administrator may display options to access sensor data, traffic data, video data and historical and live location data while a GUI155used by a first responder may display live location data, personal medical data, and traffic data. The individual features of the GUI143are customizable, such that a user can enable or disable functionalities and/or data streams. For example, a user may enable or disable a historic location overlay. In another example a user may enable or disable personal medical information associated with the device identifier. The individual features of GUI143may be able to be arranged by the user according to the user's preferences. Features of the GUI143are made available based on a user's proximity to an emergency. For example, a first responder may gain access to a medical data associated with a device identifier when the first responder is 5000, 2000, 1000, or 500 meters or less from the emergency. The GUI includes a functionality to enable and disable a WebSocket connections that, when enabled, automatically push device identifier data (e.g., phone number, IP address) to the emergency response application. As mentioned above, the emergency response application may be a cloud-based application accessed via webpage that can be accessed through an Internet or web browser. The emergency response application can thus be quickly and easily integrated into the systems used by public safety services, such as public safety answering points (PSAPs), because accessing and using emergency response application144requires no additional software or hardware outside of standard computing devices and networks. As previously discussed, one of the greatest hinderances that PSAPs face in providing emergency assistance to people experiencing emergency situations is in acquiring accurate locations of the emergencies and the people involved, because PSAPs are currently typically limited to verbally asking for and verbally receiving locations from callers. The emergency data manager100is capable of receiving accurate locations (as well as additional emergency data) from electronic devices160such as smartphones and delivering the accurate locations to the appropriate PSAPs during emergency situations. Therefore, it is advantageous to provide the emergency response application to PSAPs in the form of a webpage accessible through a standard web browser, in order to provide the potentially life-saving information stored within the emergency data manager100to those capable of providing emergency assistance as quickly and easily as possible. In providing the emergency response application to emergency networks such as PSAPs (and the potentially sensitive emergency data obtained and stored within the emergency data manager100, by extension) in the most accessible way possible, it is advantageous to provide rigorous security precautions and functions specifically created and suited for the emergency response application. If a PSAP desires to access the emergency data stored within the emergency data manager100, an administrator of the PSAP (hereinafter, “PSAP administrator” or “PSAP admin”) can navigate to the emergency response application using a URL in a standard web browser. The PSAP administrator can then use interactive elements of the GUI143to request access to the emergency data manager100using the emergency response application. Upon selecting to request access to the emergency response application, the emergency response application prompts the PSAP administrator to submit information about the PSAP through the GUI143. FIG.17is another example GUI143showing a jurisdictional map view1790which includes a map1720showing a jurisdictional boundary1710a, and a call queue1705. In the example jurisdictional map view1790, an emergency network such as a PSAP can view two or more ongoing or recently received emergency calls within one or more geofenced jurisdictions. The locations from which each of the emergency calls or emergency alerts received in the call queue1705as shown on the map1720using location indicators. The jurisdictional map view1790includes an alert queue or call queue1705that is populated by device identifiers (e.g., phone numbers, IP addresses) and the location of each emergency or device in use. The map1720may also show location indicators for emergencies occurring outside of the jurisdictional boundary1710a, but within a buffer zone. In the example ofFIG.17, the dotted line indicates a buffer zone boundary1735that is some arbitrary distance away from a complex polygon border that defines the jurisdictional boundary1710a. The location indicator1727shows an emergency call or emergency alert received originated from a device located with the defined buffer zone. Buffer zone distances may be defined by the jurisdictional authority (i.e. an ESP) operating the given emergency network and may be based on agreements with neighboring jurisdictional authorities or based on other criteria. The call queue1705may be displayed or ordered in any manner for clarity and efficiency. The alert queue (e.g., call queue1705) is ordered sequentially based on the time that the alert was received. The alert queue is prioritized based on type of emergency, severity of the emergency or other appropriate factors. The emergency network user is required to respond to emergency alerts in the alert queue sequentially. The emergency network user may select any emergency alert in the queue in any order. The call queue1705is populated by device identifiers that correspond to emergency locations, and may display a call start time associated with each device identifier, a call end time associated with each device identifier, and a call date associated with each device identifier. The information displayed for the device identifier is in the user's time zone or in the caller's time zone. The call queue1705may be ordered with respect to the start time of the call. The terminated calls may be automatically removed from the call queue1705or may be removed by the user. For example, the terminated calls may be removed from the call queue1705after a variable delay, or if the user does not manually remove the terminated call. The delay may be set at any arbitrary time interval, for example, from seconds to minutes to hour intervals. The call queue includes a search box1730that allows the user to quickly find device identifiers within the current call queue1705or for terminated calls. A user can also review the history of a device identifier with respect to previous emergency calls. Each location indicator may be customizable by the user. The shape and/or color of each location indicator is customizable. The shape and color of the location indicator is denoted in the call queue. The user is enabled to annotate text next to or within a text box associated with a particular location indicator. The user is enabled to annotate text next to or below each device identifier within the call queue. For example, a user may customize three ongoing emergency location indicators by changing the indicators to a “yellow star”, and the associated device identifiers in the call queue are automatically denoted with a “yellow star” adjacent to the device identifier. Each location indicator may be automatically updated or changed to reflect response status of secondary response agencies, such as the fire department or police department, or to reflect response status at a PSAP. For example, the location indicator may be flashing to indicate that no user at the PSAP has attended to the incoming call. In another example, the location indicator may automatically change color to indicate that a first responder has been dispatched to the emergency location. In another example, a location indicator may automatically change to reflect that an emergency call is no longer active, or the caller has egressed the jurisdictional geofence of the PSAP. The user is enabled to display device identifier data (e.g., phone numbers) adjacent to the map indicator. The user is enabled to toggle on and off map indicator customization preferences. The jurisdictional map view may allow an emergency network user (e.g., a PSAP call taker) to mark one or more incidents as “Cancel”, “Duplicate”, “Push to CAD”, etc. For example, a PSAP call taker can cancel inadvertent calls (e.g., butt dials), prank calls, and other non-emergency calls. For example, a fire that is being reported in two incidents1725aand1725bmay be reporting the same fire. The emergency network user (e.g., PSAP call taker, supervisor, emergency responder) may mark one of these incidents as a duplicate. The emergency network user may link the two incidents1725aand1725bas related. The emergency network user may also consolidate the two incidents into one incident. By allowing identification of redundant emergency alerts, the jurisdictional map view improves efficiency and efficacy of the emergency response. In addition, a PSAP call taker may initiate a CAD incident based on an emergency alert in the alert queue. For example, an emergency alert may have been triggered by smoke alarms in a home and there may not be an associated emergency call. By creating a CAD incident, the PSAP call taker could initiate dispatch and emergency response for to the home. A PSAP call taker may characterize an emergency within the GUI143by indicating an emergency type, emergency severity, priority, dispatch notes, response status, etc. The user initiates the emergency response application to find the jurisdictional map view of the PSAP geofence. The jurisdictional map view is populated with previous and ongoing calls being attended to by the PSAP. Upon initiation of the emergency response application, the jurisdictional map view may not be populated with previous and on-going calls, but becomes populated with each incoming call following the initiation of the emergency response application. When a call is added to the call queue, a corresponding location indicator may be added. When a call is removed from the call queue, the corresponding location indicator may be removed. Wherein the user hovers or selects the location indicator, the device identifier (e.g., phone number) may be displayed adjacent to the location indicator. Selection of a device identifier in the call queue, will cause a corresponding location indicator to be displayed. Multiple device identifiers can be selected in the call queue to display information adjacent to the corresponding location indicator. When a device is a mobile device and relocating in real time, the device's location may be updated in the emergency response application GUI in real time. The emergency response application GUI displays the location of all device identifiers in the call queue, and tracks the location of each emergency or device in real time simultaneously. The jurisdictional map view1790may also display one or more data overlays. A data overlay may include an additional source of information. Examples of such information sources include IoT sensors (e.g., temperature sensor, camera/video camera), first responder devices (e.g., police vehicle console), wearable sensors (e.g., heart monitor), third party databases, and other relevant sources. The emergency management view is configured to be customizable to show one or more data overlays (or none) based on user configured settings. The jurisdictional map view displays the location of available emergency services within a variable proximity to one or more callers, or within the jurisdictional boundaries, as defined by a geofence, of one or more callers. The jurisdictional map view displays the location of one or more first responders. The location of a first responder that is assigned to and/or actively responding to an emergency incident may be displayed in real-time. An estimated time to arrival and/or distance to arrival may also be displayed (e.g., calculated using the shortest or fastest path between the first responder and the incident location). The PSAP is enabled to coordinate the dispatch of emergency responders to emergency callers, so as to reduce response times and improve the allocation of resources. The emergency response application is updated in response to the dispatch of a first responder to an emergency location. The emergency response application is updated manually or automatically. The jurisdictional map view may display one or more sensors within a variable proximity to one or more callers (e.g., as determined using emergency data based on the locations of the callers or associated emergency incidents). The one or more sensors may include, but are not limited to, physiological sensors, environmental sensors, etc. that are operative to sense environmental and health/physiological parameters. Environmental parameters may include, but are not limited to, light, motion, temperature, pressure, humidity, vibration, magnetic field, sound, smoke, carbon monoxide, radiation, hazardous chemicals, acid, base, reactive compounds, volatile organic compounds, and smog. Health parameters may include, but are not limited to, heart rate, pulse, electric signals from the heart, blood oxygen levels, blood pressure, blood sugar level, and other health parameters. A sensor may be an Internet of Things (IoT) device such as a home thermostat, vehicle console, a pacemaker implant, etc. As used herein, IoT refers to the ever-growing network of physical devices, buildings, vehicles, and other objects that feature an IP address for Internet network connectivity for exchanging data. In many cases, IoT devices are embedded with electronics, software, sensors, network connectivity, or a combination thereof. IoT devices may feature an IP address for internet connectivity. In addition to an IP address, an IoT device is optionally associated with a MAC address or an SSID. It is understood that, IoT devices are connected with one or more other devices through Bluetooth®, Wi-Fi, or other wired and/or wireless technologies which allow for transfer of data. An IoT device may also be in a network of sensors. As an example, IoT networks, wireless sensor networks (WSN) or wireless sensor and actuator networks (WSAN) monitor environmental parameters such as temperature, pressure, sound, etc., using a network of sensors or devices. When one sensor or device detects a sensed value outside of the identified range indicating a likely emergency, it will pass the data to other devices in the network. The sensor network is a Wi-Fi, WiMAX, or LTE MESH network. The sensor or IoT devices form nodes in the sensor network. The sensor network includes a central node for controlling the network. The sensor network has a distributed architecture to reduce the impact of a failed node. The jurisdictional view is used improve the coordination of first responder resources during large scale emergencies such as natural disasters, industrial accidents, and acts of terror. The user of the emergency response application is enabled to access a single caller view from the jurisdictional awareness view. The single caller view is accessed by the user selecting a location indicator or a device identifier on the call queue. FIG.18provides another example of a GUI1800showing a jurisdictional map view for a jurisdictional boundary1801. The GUI1800provides an example of a view into adjacent jurisdictions and buffer regions. In the example illustrated byFIG.18, an emergency network can facilitate the transmission of emergency data from to another emergency network. The emergency network GUI1800includes a list of incidents, i.e. call queue1810corresponding to emergency alerts received by an emergency network. A map1820displays emergency locations via location indicators corresponding to alerts on the list of alerts shown in call queue1810. In this example, the emergency response application may be being accessed by a public safety answering point (PSAP A) with a jurisdictional boundary defined by polygonal geofence1810A. As depicted, emergency data for all the emergency alerts within the geofences1810A (incident1802A,1824A,1824B,1824C, etc.) are displayed. In addition, an emergency alert1827that falls outside the geofence1810A is also depicted as it falls within the buffer boundary1835(+10 km) or within expanded polygonal geofence region. As such, emergency data for the emergency alert1827is not pushed through the WebSocket connection to the emergency network GUI1800, but the alert1827is available via emergency network query using the search field1830. As depicted inFIG.18, the emergency network display1800includes the call queue1810corresponding to emergency calls received by an emergency network and map1820that displays emergency locations1824corresponding to incidents1812(1812A through1812E) on the list of incidents. In this example, the emergency response application GUI1800is being accessed and used by a public safety answering point (PSAP A) at emergency network location1802A, which has an emergency network geofence1810A. PSAP A has received three emergency calls, represented by incidents1812A,1812B, and1812C. PSAP A has received emergency locations for each of the three emergency calls, emergency locations1824A,1824B, and1824C, respectively. In this example, PSAP A is neighbored by a second public safety answering point (PSAP B) at emergency network location1802B, which has an emergency network geofence1810B. PSAP B has also received three emergency calls and an emergency location for reach of the three emergency calls, emergency locations1824D,1824E, and1824F. In this example, both PSAP A and PSAP B have integrated with the emergency network such that both emergency networks transmit an emergency communication including a user identifier (e.g., a phone number) and an emergency location for each emergency call that the emergency networks receive. The emergency network can then share relevant emergency data from one of the emergency networks to the other. In this example, the emergency network has determined that emergency locations1824D and1824E (received in separate emergency communications from PSAP B) are within a threshold distance (e.g., one mile, five miles, ten miles, etc.) of PSAP A's associated geofence, emergency network geofence1810A. In response to making this determination, the emergency network can transmit emergency data regarding the two emergencies represented by emergency location1824D and1824E (e.g., associated user identifiers and the time at which the respective emergency calls were received) to PSAP A and display the emergency data within the emergency response application1890. In this example, emergency data regarding the emergencies represented by emergency location1824D and1824E are displayed within the list of incidents in call queue1810under “Neighboring Calls”1827. The emergency network may share any and all relevant emergency data between emergency networks, including, but not limited to, user identifiers, emergency location, emergency day and time, emergency type, contact info, demographic data, and medical data. The user of the emergency response application can disable the jurisdictional awareness view by selecting a location indicator or a device identifier on the call queue1810. The user of the emergency response application can disable the jurisdictional awareness view by way of a toggle button or a menu selection. Authentication, Credentials & Roles To ensure the security, privacy and integrity of the data provided to the emergency network, proper authentication may be required at various steps. In addition, differential access may be provided to different users using various methods of access controls. The authorization process may require the emergency network member or user of the enhanced data display to verify their identity through the use of credentials such as log-in password, config file (e.g., a configuration created in a third-party system), etc. The emergency network member provides fingerprint, voice command, etc. to log-in, which can be verified. Various types of credentials may be utilized as a part of the authentication process. Credentials may be generated, stored, verified and validated by the emergency network. For example, the credentials may be generated, but must be verified (e.g., phone verification) before use. The credentials are valid for a specific duration of time (e.g., 1 minute, 5 minutes, 1 hour, 24 hours). Some examples of credentials that may be used are access keys, admin credentials, time-limited tokens, etc. Credentials may be transmitted through secure pathways (e.g., using encryption). Access controls may allow differential access to emergency data depending on user consent and/or requesting party. For example, geofencing check allows the system to give access to data from within the jurisdiction of the emergency network (and buffer region, where applicable). In addition, sensitive data such as medical or location data may be restricted to individuals with a specific level of authorization (e.g., emergency network users with specific training, or supervisory roles). Thus, medical data may be restricted when a call taker answers the call, where additional data can be overwhelming and unnecessary if it is not a medical emergency. On the other hand, medical data may be accessed by an emergency responder with medical training. The user profiles437stored in memory430of an emergency network entity such as example workstation140may contain the staff member access credentials and restrictions for one or more staff member users. Credentials may be used in a two-step authentication process. For example, the authentication may require: (i) a log-in and password for the emergency network member to log-in the emergency network system and (ii) a time-limited token to be generated based on an authentication request. A role (as described above) may be combined with to create a three-step authentication process. For example, an administrator of the emergency network could have designated roles for various emergency network members and selected specific data categories to be made accessible for each role. In contrast to system-generated credentials which must be created, stored and managed in specific ways, roles can be assigned by the admin to each member of the emergency network. For example, roles can include admin, agent, call taker, supervisor, manager, etc. In contrast to credentials, roles do not need to be verified by system as they are usually admin-defined. In addition, the admin can update the role of an emergency network member to accurately reflect changes in jobs, positions and responsibilities. In this way, the use of the roles allows the admin to customize the management portal to reflect the organizations under their supervision. An emergency network member may have multiple admin-defined roles. The authentication of the data request may be through the use of a credential, which is included in the data request (e.g., in the header of the request). When the emergency data manager100receives the request, the credential (e.g., a token) is verified to ensure that it is valid and has not expired. The data request may also include an identifier for the admin-defined role for the emergency network member. The emergency network member or user may be subscribed to the emergency data received within the emergency network jurisdiction. In this way, the credential system ensures that emergency data that is relevant for the emergency network member is accessible and updates are available quickly and efficiently. Due to the diversity of emergency network members (e.g., call dispatcher, PSAP manager, police, paramedic) and the need for accurate and relevant data, there are specific challenges for emergency response. Although system-defined credentials may also be used to restrict access to emergency data, admin-defined roles were incorporated to allow the customization needed for different emergency network members. In this way, the present system allows for both secure authentication and significant customizations for managing access to emergency data for various members of the organization. Credential Management System & User Database As previously discussed, it is advantageous to provide rigorous security precautions and functions specifically created and suited for the emergency response application in which the emergency response application is accessible as a webpage through standard web browsers. As mentioned above, the emergency response application may include a user database and is communicatively coupled to a credential management system. The user database and the credential management system may function cooperatively to secure the emergency response application and the emergency data stored within the emergency data manager100. Unlike the emergency response application, which can be accessed through public networks and servers, the credential management system can be securely connected to the emergency data manager100through private networks and servers. In this sense, the credential management system can serve as a protective barrier between the emergency response application and the emergency data manager100, as described below. When an emergency network administrator (e.g., a PSAP administrator) requests access to the emergency response application on behalf of a PSAP, an organization (also referred to as an “org”) is created for the PSAP within the credential management system. Concurrently, an organization identifier (also referred to as an “org ID”) is created for the organization (e.g., the PSAP) within the credential management system. When the request is granted, a long-lived credential (hereinafter, “credential”) is created for the PSAP within the credential management system. The credential may never expire, or may expire after an extended period of time, such as a year. Multiple credentials may be created for a single organization. As an example, in the event that a credential is compromised, the credential is deactivated, and a new credential is created for the organization. Alternatively, multiple credentials are created for a single organization, and the credential management system periodically cycles through the credentials by activating one and deactivating the others to provide an additional layer of security. Whenever an account is created within the emergency response application, the account may be stored within the user database and populated with information regarding the account, such as a name of the PSAP member for which the account was created, an email address, and the name of the PSAP. A temporary password may be created for and stored with the account in the user database. Concurrently with storing the account within the user database, an account node is created within the credential management system and a system ID is generated for the account node. The emergency response application then stores the system ID in the account stored within the user database. In this way, the system ID serves as a link between an account stored within the user database and a correlated account node stored within the credential management system. The emergency response application then requests information regarding an account node stored within the credential management system using the system ID associated with the account node, as described below. Organizations, organization IDs, users, and system IDs, and credentials may be stored within a credential management system database. The credential management system may be a software module included in the emergency network. The credential management system may be a credential management service. As an example, an API management service, such as Apigee, is used as a credential management system. Login Flow Once a request for access to the emergency response application from a PSAP administrator has been approved, the PSAP administrator and any account created by the PSAP administrator may be able to log into the emergency response application and request emergency data from the emergency data manager100through the emergency response application. To log into the emergency response application, any account holder (e.g., registered user) can navigate to a login page within the GUI143of the emergency response application, and submit the email address and password associated with their account (e.g., “login information”). If the login information is correct, the emergency response application can grant the account holder access to the emergency response application and display the dashboard within the GUI143. Alternate information may be used as login information. For example, login information may include a username, employee ID, or other suitable identifying information for an account holder. The emergency response application or emergency network may maintain an authorized list (also referred to as a “whitelist”) of internet protocol addresses (hereinafter, “IP addresses”). In that case, only login attempts from IP addresses listed on the whitelist are granted access to the emergency response application. When a PSAP administrator requests access to the emergency response application and the request is approved, as described above, the IP address from which the PSAP administrator submitted the request may be automatically added to the whitelist. The whitelisted IP address from which the PSAP administrator submitted the request may be associated with the PSAP administrator within the PSAP administrator's account stored in the user database. Each additional account created by a PSAP administrator (e.g., another PSAP admin account or a PSAP staff account) may be associated by default with the whitelisted IP address from which the PSAP administrator submitted the request to access the emergency response application within the user database. When a user (e.g., a PSAP admin or PSAP staff member) attempts to log into the emergency response application by submitting the email address and password for their account, the emergency response application may identify the IP address of the computing device from which the user is attempting to login and cross-references the IP address with the whitelist of IP addresses. If the IP address is found on the whitelist of IP addresses, in addition to the email address and password being correct, the emergency response application can grant the user access to the emergency response application. However, if the IP address is not found on the whitelist of IP addresses, the emergency response application can deny the user access to the emergency response application. In addition to denying the user access to the emergency response application, the emergency response application may disable or deactivate the account with which the user attempted to login. When a user attempts to log into the emergency response application by submitting the email address and password for their account, the emergency response application identifies the IP address of the computing device from which the user is attempting to login and cross-references the IP address with one or more IP addresses listed with the account. If the IP address is found within the one or more IP addresses listed with the account, in addition to the email address and password being correct, the emergency response application can grant the user access to the emergency response application. However, if the IP address is not found within the one or more IP addresses listed with the account, the emergency response application can deny the user access to the emergency response application and/or disable or deactivate the account with which the user attempted to login. If an account is disabled or deactivated by the emergency response application in response to receiving a login attempt from an unrecognized IP address (e.g., an IP address that is not found within the whitelist of IP addresses or an IP address that is not found within one or more IP addresses listed with the account), the account must be reactivated by the emergency response application but the account can be used to access the emergency response application. After disabling or deactivating an account, the emergency response application presents options for requesting an access (or reactivation) code through the GUI143. The access code can be used to reactivate the disabled account. For example, the emergency response application presents an option to request an access code by receiving a phone call (e.g., an interactive voice response (IVR) call) to a non-emergency number associated with the PSAP associated with the disabled account. As such the GUI143can present an entry field through which the non-emergency number can be submitted. After receiving a non-emergency number and confirming that the submitted non-emergency number is indeed associated with the proper PSAP, the emergency response application or emergency network can deliver an IVR call to the non-emergency number of the associated PSAP and playback an access code through the IVR call. This method ensures and confirms that whoever is attempting to log into the emergency response application from the unrecognized IP address is truly affiliated with the associated PSAP, because to receive the access they must be physically present at the PSAP or receive the access code from another person who is physically present at the PSAP. The IVR call may be delivered using voice over internet protocol (VoIP). Once the access code is submitted to the emergency response application (e.g., through an entry field), the emergency response application can reactivate the disabled account. After reactivating the disabled account, the emergency response application can add the formerly unrecognized IP address to the whitelist of IP addresses. After reactivating the disabled account, the emergency response application can associate the formerly unrecognized IP address with the account within the user database. The emergency response application can present an option to request an access code by delivering an email containing the access code to a PSAP administrator associated with the disabled account. As such, the GUI143can present an entry field through which a PSAP name can be submitted. After receiving a PSAP name through the entry field, the emergency response application can identify a PSAP administrator associated with the PSAP name within the user database and retrieve an email address of the PSAP administrator from the PSAP administrator's account. If the emergency response application is unable to identify a PSAP administrator associated with the PSAP name within the user database, the emergency response application can display an error message within the GUI143. If the emergency response application is able to identify to a PSAP administrator associated with the PSAP name within the user database, the emergency response application can then deliver an email containing an access code to the PSAP administrator's email address. This method similarly ensures and confirms that whoever is attempting to log into the emergency response application from the unrecognized IP address is truly affiliated with the associated PSAP, because they must receive the access code from the PSAP administrator, who has been previously verified. As described above, the access code can then be used to reactivate the disabled account. The email sent to the email address of the PSAP administrator additionally or alternatively includes a confirmation link that is selectable by the recipient of the email (e.g., the PSAP administrator) to automatically reactivate the disabled account. Once the account has been reactivated, the emergency response application can grant the account holder access to the emergency response application and display the dashboard within the GUI143and the user can use the emergency response application to request emergency data from the emergency data manager100. Emergency Data Retrieval A user may log into the emergency response application and uses the emergency response application to access emergency data pushed from the emergency data manager100. A user must log into the emergency response application using an authorized and/or active account, as described above, to access the emergency response application. When a user successfully logs into the emergency response application, such as by navigating to the emergency response application within a web browser and submitting their login information through the GUI143, the emergency response application retrieves the system ID associated with the user's account and sends an account information request including the system ID to the credential management system. In response to receiving the account information request from the emergency response application, the credential management system can identify an account node correlated with the account and return information regarding the account node to the emergency response application. The information regarding the account node includes the org ID associated with the organization to which the account node is linked. An example of an account node is shown inFIG.7. After receiving the information regarding the account node (such as the example account node information illustrated inFIG.7) from the credential management system, the emergency response application then sends a temporary access token request including the org ID to the credential management system. In response to receiving the temporary access token request, the credential management system can identify a credential associated with the organization to which the org ID refers and generate a temporary access token based on the credential. After receiving the information regarding the account node from the credential management system, the emergency response application sends a credential request including the org ID to the credential management system. In response to receiving the credential request, the credential management system can identify a credential associated with the organization to which the org ID refers and return the credential to the emergency response application. As such, the emergency response application can then send a temporary access token request including the credential to the credential management system, which can in turn generate the temporary access token based on the credential and return the temporary access token to the emergency response application. The emergency response application sends the temporary access token request to the credential management system only after the user navigates to the dashboard. The credential management system generates the temporary access token by deriving the temporary access token from the credential. The temporary access token expires after a predetermined duration of time, such as 24 or 48 hours. The temporary access token expires when the user logs out of the emergency response application. The temporary access token is a short-lived access token created under the OAuth 2.0 authorization protocol. After generating the temporary access token, the credential management system can then return the temporary access token to the emergency response application. The temporary access token is generated automatically upon the successful login of a user without requiring input from the user. The user must manually request that the temporary access token be generated, such as by selecting a generate access token button after the successful login of the user. However, a temporary access token may be generated in any other way. After a user (e.g., a PSAP administrator or PSAP staff member) successfully logs into the emergency response application and a temporary access token is generated for the user, the user can use the emergency response application to visualize data provided by the emergency data manager100on a GUI such as an interactive map with one or more data overlays. A call-taker (e.g., a PSAP staff member) at a PSAP successfully logs into the emergency response application by navigating to the emergency response application and submitting their login information through the GUI143. When an emergency call is made from an electronic device to the PSAP, the call-taker answers the emergency call and begins to respond to the emergency. The call-taker can then prompt the emergency response application to visualize the emergency data (which can correspond to an identifier of the electronic device, such as the phone number of the electronic device). For example, the call-taker can submit the device identifier by copying and pasting the device identifier or typing the device identifier into an entry field and selecting a search button. The emergency response application automatically retrieves the device identifier from a call-handling application installed at the PSAP, and the call-taker can prompt the emergency response application to obtain emergency data by selecting an emergency data button, such as the search button. The emergency response application can automatically retrieve the device identifier from a call-handing application installed at the PSAP and automatically generate an emergency data request without requiring input from the call-taker. The device identifier is communicated from the call-handling application to the emergency response application through a WebSocket. The WebSocket is coupled to the emergency response application. The emergency response application is integrated into the call-handling application installed at the PSAP, and automatically provides location data and additional data to the call-handling application installed at the PSAP. The emergency response application receives emergency data corresponding to the device identifier and/or the temporary access token. After the emergency response application obtains authorization to receive emergency data from the emergency data manager100via the credential management system. The credential management system can identify the appropriate organization using the temporary access token and communicate with the emergency data manager100to authorize the emergency response application to access emergency data (e.g., receiving automatically pushed emergency data from the emergency data manager100). Although the emergency response application can communicate with the credential management system over a public network, the org ID is not sent over a public network because the org ID is only sent from the credential management system to the emergency data manager100, and the credential management system communicates with the emergency data manager100over an encrypted or private network. This method provides critical security provisions to the publicly available emergency response application. In order to access emergency data stored within the emergency data manager100, a requesting party must provide both a valid and matching org ID and temporary access token. The interplay between the emergency response application and the credential management system described above limits the possibility of an unauthorized party acquiring both a valid and matching org ID and temporary access token. The emergency data request is an HTTP GET request, as described above. The emergency data request includes an address of an emergency network server and the device identifier in the URL of the emergency data request in the form of https://[emergency network_Server]?[Alert_ID] (e.g., https://api.rapidsos.com?caller_id={0}, wherein [emergency network_Server] (emergency network Server)=api.rapidsos.com and [Alert_ID] (device identifier)=caller_id={0}). The device identifier is an 11-digit phone number (also referred to as a CPN) (e.g., caller_id=72743767911, wherein 72743767911 is the 11-digit phone number). The emergency data request is an HTTP request that includes the following parameters or information in the headers or metadata of the request: Authorization—temporary access token; and X-RapidSOS-Role—the account type assigned to the requesting account. When processing authorization to access emergency data for the emergency response application, the emergency network or emergency data manager100verifies the temporary access token and account type of the application or its associated organization. As described herein, the emergency data manager100receives emergency data from one or more third party data sources. After retrieving the emergency data associated with a particular device identifier and/or emergency identifier, the emergency data manager100pushes the associated emergency data to the emergency response application, which can in turn display the emergency data associated with the device identifier through the GUI provided by the emergency response application. The emergency data associated with the device identifier includes one or more locations (e.g., enhanced locations). The emergency data associated with the device identifier includes a current location. The current location is received by the emergency data manager100by the electronic device to which the device identifier refers. The current location is received by the emergency data manager100from a second electronic device associated with the electronic device. The current location is received from a second electronic device communicatively coupled to the electronic device. The emergency data associated with the device identifier includes one or more historical locations. Before returning emergency data associated with a device identifier to the emergency response application, the emergency data manager100or emergency network determines if a current location included in the emergency data is within one or more geofences associated with the PSAP (and/or at least one adjacent PSAP or other emergency network) of the requesting user, as described below. The emergency data manager100only provides the emergency data associated with the device identifier if the current location included in the emergency data is determined to be within the geofence associated with the PSAP of the requesting user. A geofence is associated with the PSAP if it defines a location or area that falls within the jurisdiction of the PSAP. Emergency Data Geofencing As mentioned above with respect toFIG.3, a geofence module is applied to the emergency data manager100to protect potentially sensitive emergency data using geofences. Generally, a geofence is a virtual perimeter for a real-world geographic area. For example, a geofence perimeter may define a boundary for a relatively small geographic area such as a city block, or may define a relatively large geographic boundary such as for an entire country. A geofence can be dynamically generated—as in a radius around a point location—or a geofence can be a predefined set of boundaries (such as school zones or neighborhood boundaries). The use of a geofence is called geofencing, and one example of usage involves a location-aware device of a location-based service (LBS) user entering or exiting a geofence. Entry or exit from a geofence could trigger an alert to the device's user as well as messaging to the geofence operator. The geofence information, which could contain the location of the device, could be sent to a mobile telephone or an email account. For emergency response, an emergency service provider (public or private entities) may be given jurisdictional authority to a certain geographical region or jurisdiction (also referred to as “authoritative regions”). In the context of emergency services, one or more geofences may correspond to the authoritative region of an emergency network. In many cases, the emergency network is a public entity such as a public safety answering points (“PSAP), a PSS (e.g., a police department, a fire department, a federal disaster management agency, national highway police, etc.), which have jurisdiction over a designated area (sometimes, overlapping areas). Geofences are used to define the jurisdictional authority by various methods and in various Geographic Information System (GIS) formats. An emergency network may be a private call center. For example, an emergency network may be a university police or corporate police. There may be different types of emergency networks (e.g., primary agencies, secondary agencies, public safety agencies, private agencies, etc.). Primary agencies may have authoritative responsibility to respond to emergencies within its geofence, while secondary agencies may be assigned to respond to emergencies by primary agencies. For example, the primary agency is a PSAP, while a secondary agency is a local medical service provider. In another example, the primary agency is a PSAP, while a secondary agency is a regional authority, where the jurisdiction of the secondary agency may overlap with the jurisdiction of the PSAP. Geofences can be defined in various ways. For example, a geofence may include one or more of the following: a county boundary, a state boundary, a collection of postal/zip codes, a collection of cell sectors, simple shapes, complex polygons, or other shapes or areas. Geofences comprise approximations where the “approximated” geofence encloses an approximation of the authoritative region. Updates to geofences may be required over time because the authoritative regions may change over time. Geofences may change over time (e.g., a new sub-division has cropped up) and require updates. The systems and methods described herein allow geofences to be updated (e.g., a PSAP administrator can upload updated geofence GIS shapefiles). For maintaining the privacy, security and integrity of the data, geofencing may be applied to emergency data. For example, applying geofence filters to the emergency data allows additional avenues for monitoring, both visibility and control, over the emergency data manager100to detect anomalies/spikes and reduce the risk of security breaches. Digital Processing Device The platforms, media, methods and applications described herein include a digital processing device, a processor, or use of the same. The digital processing device may include one or more hardware central processing units (CPU) that carry out the device's functions. The digital processing device further may include an operating system configured to perform executable instructions. The digital processing device is optionally connected a computer network. The digital processing device may be optionally connected to the Internet such that it accesses the World Wide Web. The digital processing device may be optionally connected to a cloud computing infrastructure. The digital processing dice may be optionally connected to an intranet and may be optionally connected to a data storage device. In accordance with the description herein, suitable digital processing devices include, by way of non-limiting examples, server computers, desktop computers, laptop computers, notebook computers, sub-notebook computers, netbook computers, netpad computers, set-top computers, handheld computers, Internet appliances, mobile smartphones, tablet computers, personal digital assistants, video game consoles, and vehicles. Those of skill in the art will recognize that many smartphones are suitable for use in the system described herein. Those of skill in the art will also recognize that select televisions, video players, and digital music players with optional computer network connectivity are suitable for use in the system described herein. Suitable tablet computers include those with booklet, slate, and convertible configurations, known to those of skill in the art. The digital processing device includes an operating system configured to perform executable instructions. The operating system is, for example, software, including programs and data, which manages the device's hardware and provides services for execution of applications. Those of skill in the art will recognize that suitable server operating systems include, by way of non-limiting examples, FreeBSD, OpenBSD, NetBSD®, Linux, Apple® Mac OS X Server®, Oracle® Solaris®, Windows Server®, and Novell® NetWare®. Those of skill in the art will recognize that suitable personal computer operating systems include, by way of non-limiting examples, Microsoft® Windows®, Apple® Mac OS X®, UNIX®, and UNIX-like operating systems such as GNU/Linux®. The operating system is provided by cloud computing. Those of skill in the art will also recognize that suitable mobile smart phone operating systems include, by way of non-limiting examples, Nokia® Symbian® OS, Apple® iOS®, Research In Motion® BlackBerry OS®, Google® Android®, Microsoft® Windows Phone® OS, Microsoft® Windows Mobile® OS, Linux®, Ubuntu® and Palm® WebOS®. The device includes a storage and/or memory device. The storage and/or memory device is one or more physical apparatuses used to store data or programs on a temporary or permanent basis. The device is volatile memory and requires power to maintain stored information. The device is non-volatile memory and retains stored information when the digital processing device is not powered. The non-volatile memory may include flash memory. The non-volatile memory may include dynamic random-access memory (DRAM). The non-volatile memory may include ferroelectric random-access memory (FRAM). The non-volatile memory may include phase-change random access memory (PRAM). The non-volatile memory may include magneto resistive random-access memory (MRAM). The device may be a storage device including, by way of non-limiting examples, CD-ROMs, DVDs, flash memory devices, magnetic disk drives, magnetic tapes drives, optical disk drives, and cloud computing-based storage. The storage and/or memory device may be a combination of devices such as those disclosed herein. The digital processing device includes a display to send visual information to a subject. The display is a cathode ray tube (CRT). The display is a liquid crystal display (LCD). The display may be a thin film transistor liquid crystal display (TFT-LCD). The display is an organic light emitting diode (OLED) display. An OLED display may be a passive-matrix OLED (PMOLED) or active-matrix OLED (AMOLED) display. The display is a plasma display. The display is E-paper or E ink. The display may be a video projector. The display may be a combination of devices such as those disclosed herein. The digital processing device may include an input device to receive information from a subject. The input device may be a keyboard. The input device is a pointing device including, by way of non-limiting examples, a mouse, trackball, track pad, joystick, game controller, or stylus. The input device is a touch screen or a multi-touch screen. The input device may be a microphone to capture voice or other sound input. The input device may be a video camera or other sensor to capture motion or visual input. The input device may be a Kinect, Leap Motion, or the like. The input device may be a combination of devices such as those disclosed herein. Non-Transitory, Non-Volatile, Computer Readable Storage Medium The platforms, media, methods and applications described herein include one or more non-transitory, non-volatile, computer readable storage media encoded with a program including instructions executable by the operating system of an optionally networked digital processing device. A computer readable storage medium may be a tangible component of a digital processing device. A computer readable storage medium may be optionally removable from a digital processing device. A computer readable storage medium includes, by way of non-limiting examples, CD-ROMs, DVDs, flash memory devices, solid state memory, magnetic disk drives, magnetic tape drives, optical disk drives, cloud computing systems and services, and the like. In some cases, the program and instructions are permanently, substantially permanently, semi-permanently, or non-transitorily encoded on the media. Computer Program The platforms, media, methods and applications described herein include at least one computer program, or use of the same. A computer program includes a sequence of instructions, executable in the digital processing device's CPU, written to perform a specified task. Computer readable instructions may be implemented as program modules, such as functions, objects, Application Programming Interfaces (APIs), data structures, and the like, that perform particular tasks or implement particular abstract data types. In light of the disclosure provided herein, those of skill in the art will recognize that a computer program may be written in various versions of various languages. The functionality of the computer readable instructions may be combined or distributed as desired in various environments. A computer program may include one sequence of instructions. A computer program may include a plurality of sequences of instructions. A computer program is provided from one location. A computer program may be provided from a plurality of locations. A computer program may include one or more software modules. A computer program may include, in part or in whole, one or more web applications, one or more mobile applications, one or more standalone applications, one or more web browser plug-ins, extensions, add-ins, or add-ons, or combinations thereof. Web Application A computer program includes a web application. In light of the disclosure provided herein, those of skill in the art will recognize that a web application, may utilize one or more software frameworks and one or more database systems. A web application may be created upon a software framework such as Microsoft® .NET or Ruby on Rails (RoR). A web application utilizes one or more database systems including, by way of non-limiting examples, relational, non-relational, object oriented, associative, and XML database systems. Suitable relational database systems may include, by way of non-limiting examples, Microsoft® SQL Server, mySQL™, and Oracle®. Those of skill in the art will also recognize that a web application may be written in one or more versions of one or more languages. A web application may be written in one or more markup languages, presentation definition languages, client-side scripting languages, server-side coding languages, database query languages, or combinations thereof. A web application is written to some extent in a markup language such as Hypertext Markup Language (HTML), Extensible Hypertext Markup Language (XHTML), or eXtensible Markup Language (XML). A web application is written to some extent in a presentation definition language such as Cascading Style Sheets (CSS). A web application is written to some extent in a client-side scripting language such as Asynchronous Javascript and XML (AJAX), Flash® Actionscript, Javascript, or Silverlight®. A web application is written to some extent in a server-side coding language such as Active Server Pages (ASP), ColdFusion®, Perl, Java™, JavaServer Pages (JSP), Hypertext Preprocessor (PHP), Python™, Ruby, Tcl, Smalltalk, WebDNA®, or Groovy. A web application is written to some extent in a database query language such as Structured Query Language (SQL). A web application integrates enterprise server products such as IBM® Lotus Domino®. A web application includes a media player element. A media player element may utilize one or more of many suitable multimedia technologies including, by way of non-limiting examples, Adobe® Flash®, HTML 5, Apple® QuickTime®, Microsoft® Silverlight®, Java™, and Unity®. Mobile Application A computer program includes a mobile application provided to a mobile digital processing device. The mobile application is provided to a mobile digital processing device at the time it is manufactured. The mobile application may be provided to a mobile digital processing device via the computer network described herein. In view of the disclosure provided herein, a mobile application is created by techniques known to those of skill in the art using hardware, languages, and development environments known to the art. Those of skill in the art will recognize that mobile applications are written in several languages. Suitable programming languages include, by way of non-limiting examples, C, C++, C#, Objective-C, Java™, Javascript, Pascal, Object Pascal, Python™, Ruby, VB.NET, WML, and XHTML/HTML with or without CSS, or combinations thereof. Suitable mobile application development environments are available from several sources. Commercially available development environments include, by way of non-limiting examples, AirplaySDK, alcheMo, Appcelerator®, Celsius, Bedrock, Flash Lite, .NET Compact Framework, Rhomobile, and WorkLight Mobile Platform. Other development environments are available without cost including, by way of non-limiting examples, Lazarus, MobiFlex, MoSync, and Phonegap. Also, mobile device manufacturers distribute software developer kits including, by way of non-limiting examples, iPhone and iPad (iOS) SDK, Android™ SDK, BlackBerry® SDK, BREW SDK, Palm® OS SDK, Symbian SDK, webOS SDK, and Windows® Mobile SDK. Other cloud and IoT development platforms that may be used for, but not limited to, Ubuntu® include, but are not limited to, GCC, CLANG, Go, Python, Ruby, Node.js, Deb, snap, charm, etc. Those of skill in the art will recognize that several commercial forums are available for distribution of mobile applications including, by way of non-limiting examples, Apple® App Store, Android™ Market, BlackBerry® App World, App Store for Palm devices, App Catalog for webOS, Windows® Marketplace for Mobile, Ovi Store for Nokia® devices, Samsung® Apps, and Nintendo® DSi Shop. Standalone Application A computer program includes a standalone application, which is a program that is run as an independent computer process, not an add-on to an existing process, e.g., not a plug-in. Those of skill in the art will recognize that standalone applications are often compiled. A compiler is a computer program(s) that transforms source code written in a programming language into binary object code such as assembly language or machine code. Suitable compiled programming languages include, by way of non-limiting examples, C, C++, Objective-C, COBOL, Delphi, Eiffel, Java™, Lisp, Python™, Visual Basic, and VB .NET, or combinations thereof. Compilation is often performed, at least in part, to create an executable program. A computer program includes one or more executable complied applications. Software Modules The platforms, media, methods and applications described herein include software, server, and/or database modules, or use of the same. In view of the disclosure provided herein, software modules are created by techniques known to those of skill in the art using machines, software, and languages known to the art. The software modules disclosed herein are implemented in a multitude of ways. A software module may include a file, a section of code, a programming object, a programming structure, or combinations thereof. A software module may include a plurality of files, a plurality of sections of code, a plurality of programming objects, a plurality of programming structures, or combinations thereof. The one or more software modules may include, by way of non-limiting examples, a web application, a mobile application, and a standalone application. Software modules may be in one computer program or application or may be in more than one computer program or application. Software modules may be hosted on one machine or may be hosted on more than one machine in a distributed architecture. Software modules may be hosted on cloud computing platforms. Software modules may be hosted on one or more machines in one location, or may be hosted on one or more machines in more than one location. Databases The platforms, systems, media, and methods disclosed herein include one or more databases, or use of the same. In view of the disclosure provided herein, those of skill in the art will recognize that many databases are suitable for storage and retrieval of barcode, route, parcel, subject, or network information. Suitable databases may include, but are not limited to, by way of non-limiting examples, relational databases, non-relational databases, object-oriented databases, object databases, entity-relationship model databases, associative databases, and XML databases. A database is internet-based. A database may be web-based, cloud computing-based, or database based on one or more local computer storage devices. Web Browser Plug-In The computer program includes a web browser plug-in. In computing, a plug-in is one or more software components that add specific functionality to a larger software application. Makers of software applications support plug-ins to enable third-party developers to create abilities which extend an application, to support easily adding new features, and to reduce the size of an application. When supported, plug-ins enable customizing the functionality of a software application. For example, plug-ins are commonly used in web browsers to play video, generate interactivity, scan for viruses, and display particular file types. Those of skill in the art will be familiar with several web browser plug-ins including, Adobe® Flash® Player, Microsoft® Silverlight®, and Apple® QuickTime®. The toolbar may include one or more web browser extensions, add-ins, or add-ons. The toolbar may include one or more explorer bars, tool bands, or desk bands. In view of the disclosure provided herein, those of skill in the art will recognize that several plug-in frameworks are available that enable development of plug-ins in various programming languages, including, by way of non-limiting examples, C++, Delphi, Java™, PHP, Python™, and VB .NET, or combinations thereof. Web browsers (also called Internet browsers) are software applications, designed for use with network-connected digital processing devices, for retrieving, presenting, and traversing information resources on the World Wide Web. Suitable web browsers include, by way of non-limiting examples, Microsoft® Internet Explorer®, Mozilla® Firefox®, Google® Chrome, Apple® Safari®, Opera Software® Opera®, and KDE Konqueror. The web browser is a mobile web browser. Mobile web browsers (also called microbrowsers, mini-browsers, and wireless browsers) are designed for use on mobile digital processing devices including, by way of non-limiting examples, handheld computers, tablet computers, netbook computers, subnotebook computers, smartphones, music players, personal digital assistants (PDAs), and handheld video game systems. Suitable mobile web browsers include, by way of non-limiting examples, Google® Android® browser, RIM BlackBerry® Browser, Apple® Safari®, Palm® Blazer, Palm® WebOS® Browser, Mozilla® Firefox® for mobile, Microsoft® Internet Explorer® Mobile, Amazon® Kindle® Basic Web, Nokia® Browser, Opera Software® Opera® Mobile, and Sony® PSP™ browser. Certain Terminologies Unless otherwise defined, all technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural references unless otherwise stated. Any reference to “or” herein is not an exclusive disjunction and is, in other words, intended to refer to a “non-exclusive or” that encompasses “and/or” unless otherwise stated. As used herein, “emergency data sources” refers to devices that internally generate data such as, but not limited to, hybrid location data, sensor data, etc.; sensors such as but not limited to IoT sensors, fire alarms, carbon monoxide detectors, etc. without limitation; multimedia sources including cameras; databases (including, but not limited to, medical databases, locations databases, law enforcement databases, etc.) As used herein, “emergency network entity” refers to a hardware apparatus used to access or implement an emergency network such as, but not limited to, workstations, servers, routers, switches, laptops, desktop computers, etc. As used herein “jurisdictional boundary” refers to a geographic area defined by one or more geofences within which a given emergency network provides emergency services. As used herein “jurisdictional map view” refers to a map displayed on a GUI showing a “jurisdictional boundary” of at least one emergency network. As used herein “emergency data” is “associated” with an emergency network when it correlates to a “jurisdictional boundary” by having with been generated by a device originating an emergency call or emergency alert from a location within the jurisdictional boundary, or by way of being related to an emergency occurring within the “jurisdictional boundary” for example, a camera feed showing a building that is on fire is emergency data associated with an emergency network that serves the geographic area in which the building is located, etc. When emergency data is associated with an emergency network it is also associated with any emergency network entity such as a workstation operating within that emergency network. A “complex polygon” refers to the standard geometric definition of a complex polygon and where the complex polygon may be represented on a two-dimensional map by way of lines having vertices and, in some cases, intersecting lines. As used herein, the “device identifier” refers to information allowing identification of the device or a user of the device, such as for example, a phone number associated with a user of a producing device. A “device identifier” may include but is not limited to, a phone number, email address, physical address, coordinates, IMEI number, IMSI, TMSI, IP address, BSSID, SSID or MAC address. As used herein, an “emergency alert” refers to a communication relating to an emergency or non-emergency situation. An emergency alert is an emergency request for assistance (e.g., the request is associated with an emergency situation). An emergency alert is a phone call. An emergency alert may include an emergency indication. An emergency indication may be selected from one or more of the group consisting of traffic accident, police emergency, medical emergency, and fire emergency. An emergency alert is associated with a non-emergency situation (e.g., request for a tow truck after car breaks down). An emergency alert is associated with a device sending the alert. An emergency alert may be associated with a device not sending the alert (e.g., a proxy request on behalf of a second device and/or a member device in a group of devices). As used herein, an emergency alert is “associated” with a device or user when the emergency alert relates to an emergency or non-emergency situation involving the device or user. An emergency alert may include data associated with a device (or user thereof). An emergency alert may include data associated with an electronic device sending the alert or another device. For example, an emergency alert may include data associated with a device, wherein the data set may include current and/or past location data. In another example, the data set may include current and/or past health data associated with the user of an electronic device. An emergency alert may be sent and/or received separately from data associated with a device. An emergency alert may be associated with an ESP after making a geofencing determination. As used herein, an emergency service provider (ESP) refers to an agency or institution that provides safety, security, or medical services. An ESP can be a public safety service which refers to a local, state, or federal government agency or institution that is responsible for providing safety, security, or medical services to members of the public. Examples of ESPs that are public safety services include fire departments, police departments, and hospitals. Public safety services additionally include public safety answering points (PSAPs). An ESP can also be a private safety service, which refers to a private agency or institution that is responsible for providing safety, security, or medical services to clients. Examples of ESPs that are private safety services include private call centers, security companies, and private police, such as university or corporate campus police. Various ESPs may have geofences that overlap and therefore, even though multiple ESPs may cover identical or overlapping geographic area, a specific ESP may be selected based on the type of emergency. Additionally, an ESP may be selected based on various other factors such as the severity of emergency, proximity to public lands (e.g., state or national highways, military installments), proximity to private areas (e.g., a corporate campus, university campus), and other factors. There may be different types of ESPs (e.g., primary agencies, secondary agencies, public safety agencies, private agencies, etc.). Primary agencies may have authoritative responsibility to respond to emergencies within its geofence, while secondary agencies do not have primary authority to respond to emergencies with the primary agencies geofence. In some cases, the secondary agency may be assigned to respond to emergencies by primary agencies. As an illustrative example, a primary agency may be a PSAP, while a secondary agency may be a local medical service provider. In another example, a primary agency may be a PSAP, while a secondary agency may be a regional authority, where the jurisdiction of the secondary agency may overlap with the jurisdiction of the PSAP. An ESP may operate a PSAP. A PSAP refers to a call center responsible for answering calls to an emergency telephone number for police, firefighting, and ambulance services. Trained telephone operators (also referred to as call-takers) are also usually responsible for dispatching these emergency services. The Federal Communications Commission (FCC) of the United States government maintains a PSAP registry. The registry lists PSAPs by an FCC assigned identification number, PSAP Name, State, County, City, and provides information on any type of record change and the reason for updating the record. The FCC updates the registry periodically as it receives additional information. The ESP identifier or PSAP identifier may include the FCC identification of the agency. As used herein, a “emergency authority” refers entities or organizations that have been given authority by the government to service emergency calls (911, 112 or other emergency numbers) within a specific area (the “authoritative region”). These emergency authorities operate emergency networks. Non-limiting examples of emergency authorities that operate emergency networks include various types of ESPs such as emergency command centers and PSAPs. “User data” refers to general information associated with a user of a device, such as, but not limited to: user identity, user name, height, weight, eye color, hair color, ethnicity, national origin, religion, language(s) spoken, vision (e.g., whether user needs corrective lenses), home address, work address, occupation, family information, user contact information, emergency contact information, social security number, alien registration number, driver's license number, vehicle VIN, organ donor (e.g., whether user is an organ donor), or any combination thereof. As used herein, “emergency data” refers to data pertaining to an on-going or historical emergency. The emergency data may be generated at the time of the emergency, or before the emergency occurs, and may be made accessible when the emergency occurs. Emergency data may include, but is not limited to, location data, particularly the current location of the emergency which may often times be based on the location of the user device from which an emergency call was made, or that sent an emergency alert. Because of privacy and security concerns, emergency data must be stored, accessed, transmitted using security and privacy measures. Emergency data may include, but is not limited to, at least one of user data, sensor data, health data, etc. As used herein, “sensor data” refers to information obtained or provided by one or more sensors. In some instances, a sensor is associated with a device (e.g., user has a communication device with a data link via Bluetooth with a wearable sensor, such as, for example, a heart rate monitor or a pedometer). Accordingly, a device may obtain sensor data from various sensors (e.g., heart rate from the heart rate monitor or distance traveled from the pedometer). In some instances, sensor data may be relevant to an emergency situation (e.g., heart rate during a cardiac emergency event). Sensors and/or sensor devices may include, but are not limited to, an acoustic sensor, a breathalyzer, a carbon dioxide sensor, a carbon monoxide sensor, an infrared sensor, an oxygen sensor, an ozone monitor, a pH sensor, a smoke detector, a current sensor (e.g., detects electric current in a wire), a magnetometer, a metal detector, a radio direction finder, a voltage detector, an air flow meter, an anemometer, a flow sensor, a gas meter, a water meter, a Geiger counter, an altimeter, an air speed indicator, a depth gauge, a gyroscope, a compass, an odometer, a shock detector (e.g., on a football helmet to measure impact), a barometer, a pressure gauge, a thermometer, a proximity sensor, a motion detector (e.g., in a home security system), an occupancy sensor, or any combination thereof. Sensor data may include, but is not limited to, information obtained from any of the preceding sensors. One or more sensors may be physically separate from a user device. One or more sensors may authorize the user device to obtain sensor data. One or more sensors may provide or send sensor data to the user device autonomously. A user device and one or more sensors that may belong to the same group of devices, where member devices are authorized to share data. A user device may include one or more sensors (e.g., user device is a wearable device having a sensor or sensing component). FIG.19is a flowchart illustrating the method of operation. The method of operation begins, and in operation block1901an IP connection is established between an emergency network entity, such as a workstation, and an emergency data manager100. The IP connection may include WebSocket connections and may create a subscription between the emergency service provider and the emergency data manager100such that emergency data from various devices is pushed or streamed to the emergency service provider as emergency alerts or emergency sessions are initiated from the various devices to the emergency service provider. In operation block1903, the emergency data manager100begins to send, by push operations or by data streaming, location data and other emergency data to the emergency service provider using the IP connection. In operation block1905, the emergency data manager100filters the data based on determining that the location of any device sending emergency data is located within a polygon that defines the jurisdictional boundary as defined by one or more geofences for the specific emergency network. The method of operation then terminates as shown. FIG.20is a flowchart of another method of operation. The method of operation begins, and in operation block2001an IP connection, which may include WebSocket connections, is established between an emergency network entity, such as a workstation, and an emergency data manager100. In operation block2003, the emergency data manager100begins to send location data, via push operations or data streaming, to the emergency network entity for a plurality of devices in response to each device initiating an emergency session and prior to establishment the emergency session between the emergency service provider and the emergency data manager100. In other words, there is a delay that occurs during establishment of an emergency session such as a phone call placed from a mobile telephone to an emergency service provider. However, the emergency data manager100may receive location data and emergency data from a mobile telephone or other device during an interval or delay during which the emergency session is being established. Therefore, the emergency service provider may have access to emergency data concerning an emergency prior to receiving a 911 phone call or prior to establishment of some other type of emergency session. In operation block2005, the emergency data manager100filters the location data as well as other emergency data to the emergency service provider based on a jurisdictional boundary which may be a polygon defining a jurisdictional geofence that defines the emergency response area for which the emergency service provider is authorized. The method of operation then terminates as shown. FIG.21is a flowchart illustrating another method of operation. The method of operation begins, and in operation block2101, an IP connection, which may include Web Socket connections, is established between an emergency network entity and an emergency data manager100. In operation block2103, the emergency services provider receives an emergency alerts with location from a plurality of devices. In operation block2105, the emergency data manager100filters the stream of emergency alerts for only those for which the emergency service provider is authorized to respond. The method of operation then terminates as shown. FIG.22is a flowchart illustrating another method of operation. The method of operation begins, and in operation block2201an emergency data manager creates a jurisdictional map view in a graphical user interface of an emergency response application. In operation block2203, a polygonal boundary is defined within the jurisdictional map view where the polygonal boundary is the jurisdictional authority area of the associated emergency service provider. In operation block2205, emergency data is received from a plurality of devices for each device sends a device identifier and location data, as well as possibly other emergency data. In decision block2207, the emergency data manager checks to determine whether the any specific received emergency data is associated with location data such that the device sending the emergency data is located within the polygonal boundary. If not, then in operation block2211the emergency data manager will search for an emergency service provider at the location, and in operation block2213will initiate streaming data for a located authorized emergency service provider at the location of the device. The method of operation then terminates as shown. If in decision block2207, the location data is determined to be within the polygonal boundary for the emergency service provider, then the method of operation proceeds to operation block2209. In operation block2209, the emergency data is included in the streaming data sent to the emergency service provider. The method of operation then terminates as shown. FIG.23is a flowchart illustrating another method of operation. The method of operation begins, and in operation block2301an emergency data manager obtains emergency data for multiple device types from a plurality of emergency data sources. In operation block2303, the emergency data manager provides a jurisdictional map view to a plurality of emergency network entities, where each emergency network entity corresponds to a given geographic boundary, and where the jurisdictional map view corresponds to a respective emergency network entity's geographic boundary. In operation block2305, the emergency data manager determines portions of the emergency data corresponding to emergencies occurring within each respective emergency network entity geographic boundary. In operation block2307, the emergency data manager provides location indicators within each respective jurisdictional map view, with each location indicators corresponding to an emergency. The method of operation then terminates as shown. FIG.24is a flowchart illustrating another method of operation. The method of operation begins, and in operation block2401an emergency data manager obtains emergency data for multiple device types from a plurality of emergency data sources. In operation block2403, the emergency data manager establishes a plurality of network connections with a plurality of emergency network entities, where each emergency network entity corresponds to a given geographic boundary. In operation block2405, the emergency data manager determines associations between portions of the emergency data and specific emergency network entities based on each emergency network entity's geographic boundary. In operation block2407, the emergency data manager sends each determined portion of emergency data to a respective associated emergency network entity based on the determined associations. The method of operation then terminates as shown. Various jurisdictional authorities may be represented by complex polygonal boundaries which may be displayed on a graphical user interface of an emergency services application. Emergency response logic, which may be implemented as hardware, firmware, software code, or by any combination thereof, or which may be implemented as the emergency services application, or which may be supplemental to and interacting with an emergency services application, is operative to determine complex polygonal boundaries for a plurality of emergency service providers. For example, a national system which may be displayed on the national map, may display various complex polygonal boundaries for governmental or private emergency service providers and may show the overlap of the various complex polygonal boundaries. Additionally, some emergency service providers may exist within the boundaries of other emergency service providers. For example, a private emergency service provider may have a complex polygonal boundary within another complex polygonal boundary for a governmental emergency service provider. A graphical user interface may display a map view showing all of these relationships between the complex polygonal boundaries of the various emergency service provider jurisdictions. Additionally, the emergency service logic is operative to make decisions as to where emergency data incoming to an emergency data manager100, should be routed based on a hierarchy or other criteria and using the complex polygonal boundaries of the various emergency service provider jurisdictions. For example, an emergency occurring in a private area such as a corporate campus or university may be routed initially to a private emergency service provider authorized to handle such emergencies within their specific polygonal boundary. However, the emergency service logic may determine that the nature of the emergency is such that a governmental emergency service provider should handle the emergency rather than the private emergency service provider. In that case, emergency data may be routed initially to the governmental provider to facilitate timely handling of the emergency. In addition, the private emergency service provider may also be notified that the emergency is occurring and that the governmental emergency service provider having jurisdiction over the location has been contacted. As one would understand, many different options may exist for how specific emergency service providers are notified regarding emergencies occurring within their jurisdictional authority defined by the polygonal boundary specific to their emergency handling area. OPERATIONAL EXAMPLES AND USE CASES The following operational examples are representative of various use cases that may be implemented using the various apparatuses, systems and methods disclosed herein. Example 1 Jurisdiction View “Just-in-Time,” a hypothetical emergency response company, aids ESPs (e.g. public safety answering points, or “PSAPs”) by gathering emergency data from a variety of sources and delivering the data directly to the public safety services. Traditionally, PSAPs are only technologically capable of receiving telephone calls (e.g., 9-1-1 emergency calls) with no additional data. Thus, when an emergency all is made to a PSAP from a mobile phone, with a dynamic and uncertain location, PSAP operators or call-takers must speak directly to the caller to determine the person's location. Unfortunately, many people involved in emergency situations are unable to articulate their location or may not even know—and even if they do, the time spent articulating their location to the PSAP operator can often be the difference between life and death. Similarly, PSAP operators are forced to respond to emergencies with little or no information about the persons involved (e.g., health data or medical histories) or context of the emergencies (e.g., type of emergency, audio/video of the surroundings, etc.). Just-in-Time understands how critical it is to quickly and accurately provide locations and situational/contextual information during emergencies to public safety services. To aid ESPs, Just-in-Time maintains and provides an emergency data manager100(hereinafter, “emergency data manager100”) that receives and stores data and information from a plurality of sources, such as mobile phones and mobile applications, internet of things (IoT) devices, intelligent vehicles systems, and other electronic devices. During an emergency, the emergency data manager100can gather information stored within the emergency data manager100regarding the emergency and deliver the information to ESPs. In order to provide access to the information stored within the emergency data manager100to ESPs as quickly and easily as possible, Just-in-Time develops and provides an emergency response application (also referred to as jurisdiction view). The administrator of a ESP in Georgia, Joe, learns of the helpful and potentially life-saving information stored within Just-in-Time's emergency data manager100—such as accurate emergency locations and medical histories (hereinafter, “emergency data”)—and that is automatically pushed to registered ESPs (which has authoritative jurisdiction to respond to emergencies). Accordingly, Joe registers his ESP and a set of credentials are created and activated. Joe also, uploads a shapefile containing a polygonal geofence of the authoritative jurisdiction of the ESP. The polygonal geofence is processed by determining and removing overlaps with adjacent geofences and saved as a processed GeoJSON file in a geofencing database. Once registered, Joe then creates Nick-of-Time accounts for any number of other members of the ESP-1 to use to access the Nick-of-Time emergency response application. For example, Joe creates an account for one of the Georgia ESP call-takers, Jane. Just-in-Time then sends Jane an email including a temporary password for her to use to access the Nick-of-Time emergency response application. When Jane attempts to log into the Nick-of-Time emergency response application, in addition to checking the credentials, the Nick-of-Time emergency response application checks the IP address that Jane's login attempt was received from, and determines that the IP address is different from the IP address Joe used to register the ESP (e.g., Jane attempted to log in from a different computer within the ESP). In response, Jane's login attempt is blocked and her account is disabled. The Nick-of-Time emergency response application presents Jane with two options for requesting an access code to reactivate her account: a phone call to the ESP's non-emergency telephone number that will audibly relay the access code; or an email sent to Joe. This security method ensures that Jane is legitimately associated with the Georgia ESP, as she must either be physically present at the PSAP, receive the access code from someone who is physically present at the ESP, or receive the access code from Joe, who has been previously vetted. Since Jane is physically present at the ESP, she chooses to receive the phone call and records the access code that is dictated by the call. She submits the access code into the Nick-of-Time emergency response application, which reactivates her account and adds her IP address to a list of authorized IP addresses. The Nick-of-Time emergency response application then presents a jurisdiction view on a computer display to Jane through the Nick-of-Time emergency response application GUI, where Jane can view a master list and/or an interactive map showing one or more ongoing and recent incidents within the jurisdiction. Jane soon receives an emergency call from a man named Eric, whose phone number is (555) 444-6666. Upon making the emergency call, Eric's smartphone automatically sends a current location (determined using the phone's hybrid location rather than just cell tower triangulation) to a third-party database, which then relays the information to the emergency data manager100. In addition, the emergency data manager100searches its records for additional information including Eric's home and work addresses, Eric's medical history, and a phone number for Eric's mother, who is listed as Eric's emergency contact. The emergency data manager100then uses the identifier of the Georgia ESP to retrieve the processed geofence. The emergency data manager100then determines whether or not Eric's current location is within the geofence. For security purposes, the emergency data manager100does not return emergency data to requesting parties if a current location included in the emergency data is not within a geofence associated with the requesting party. However, the emergency data manager100determines that Eric's current location is within the geofence provided by Joe. The emergency data manager100also accesses the ALI feed or CAD spill of the PSAP to locate the phone identifier corresponding to the current location for Eric's phone. Once the location has been successfully matched to the phone identifier, the emergency data manager100automatically pushes all of the emergency data associated with Eric's phone number to Jane to be visualized using the jurisdiction view. The jurisdiction view displays a graphical representation of Eric's current location within a map view on the GUI along with a textual description of Eric's current location (e.g., latitude and longitude) within a text box. The emergency data is already available when Jane accesses the jurisdiction view, and Jane immediately dispatches emergency help to Eric's current location. To access the emergency data, Jane opens the jurisdiction view on the GUI which shows the interactive map. Medical data may be excluded depending on Jane's authorization to view medical information. In this example use case, Jane has received basic EMT training and is authorized to view medical data. The graphical representation of Eric's current location is user selectable and configured to provide any additional information upon selection. Moreover, the map view is operative to show one or more data overlays visualizing additional sources of information. In this example use case, Jane has modified the settings to display the IoT sensor overlay showing sensors within a 200-meter radius of a current incident's location. Accordingly, IoT sensors within the 200-meter proximity to Eric's current location are graphically shown as an IoT sensor overlay on the interactive map. Eric communicates to Jane that the emergency is for a fire in his apartment building. Jane selects the emergency alert from the IoT sensor and marks it as a “duplicate.” Jane selects a traffic camera at an intersection close to Eric's location and accesses the data feed to assess the fire. She also selects IoT temperature sensors located near Eric's location to access temperature readings. Jane then relays the information to the first responder (fire department) that has been assigned to respond to the emergency incident. Example 2 No Emergency Call John, a resident of southwest side of City A, which falls within the jurisdiction of an Emergency Dispatch Center, i.e. ESP-1, is driving north on Highway 49. On the way, an ice storm hits and John's car skids, goes through a barrier into a ditch. John is injured and cannot locate his phone. Fortunately, John's car is equipped with telematics with motion sensors to detect collision by a vehicular computer. The vehicular computer has a communication system, which may be a cellular connection, a satellite connection or other wireless connection, etc., through which the alarm signal reaches a central monitoring station. The location of the car from a built-in GPS chip was also sent to the central monitoring system. The location of the car appears to be with the jurisdictional boundary of ESP-1. A service request was sent to ESP-1, which is a primary agency with a polygonal geofence A. The dispatchers at ESP-1 are monitoring the jurisdictional view of the ESP-1 when an alert appears with the account phone number for John. By 9:15 PM, all dispatch lines are busy responding to calls from various residents in the area including reports of patchy cellular phone coverage. From the jurisdictional display, the ESP-1 manager proactively calls John's number to see if he is an emergency. When the phone rings, John finds that the phone has fallen under the seat. He picks up the phone and confirms that he needs emergency assistance. The location of the car is available in jurisdictional view of the ESP-1, when the ESP manager clicks on the alert. First responders and a toy truck are dispatched to the exact location and John is rescued. Example 3 ESP Update Jane, an IT professional, is driving back home from work. On the way, she passes through the authoritative jurisdiction of two ESPs—ESP-1 (with geofence A) and ESP-2 (with geofence B). As she is about to leave geofence A, Jane sees a vehicle on fire. Jane calls 911, which routes her call to ESP-2 as she is now in geofence B. When the call taker, Susan picks up the call, she realizes that the location of the emergency might be in the jurisdiction of ESP-1 or within the buffer region. Susan zooms in and finds that the location is within geofence A. Susan chooses an option to “share data with ESP-1” and transfers the call to ESP-1. Example 4 Small Geofence XYZ school has taken security measures, which includes an App that the school principal and other officials have installed on their mobile phones through which an emergency notification procedure can be initiated. The location of the school including the playing fields are represented by a rectangular geofence. Two corners (latitude/longitude) are specified and saved in a GIS file. When an emergency call is made by a student within the school, an emergency notification is received by the emergency network. The emergency network checks the location of the emergency and determines that it is within the XYZ school premises. The notification procedure for XYZ school is initiated and automated SMS notification messages are sent to specific school officials. On receiving the notification, the school principal opens up the security App and presses a button to initiate school lockdown. A belligerent student with a gun is contained within the second floor and the security officer is able to diffuse the emergency. Example 5 Emergency Call Data Routing “Just-in-Time,” the hypothetical emergency response company from Example 1, aids ESPs (e.g. public safety answering points, or “PSAPs”) by gathering emergency data from a variety of sources and delivering the data directly to the public safety services. A plurality of dispatch operators at various PSAP located across the country are logged into their respective emergency response applications on their computing workstations. Each emergency response application presents a jurisdiction view on a computer display to its operator through the emergency response application GUI, where the operator can view a master list and/or an interactive map showing one or more ongoing and recent incidents within the jurisdiction. A number of emergency calls are made from smartphones located in different PSAP jurisdictions. The smartphones send their respective GPS locations to the emergency response company server (referred to as an “emergency data manager”) which associates the locations with the smartphone identifiers (e.g., their phone numbers), respectively, and stores them temporarily. Specifically, the smartphones automatically send their current locations (determined using the phone's hybrid location rather than just cell tower triangulation) to a location database, which then relays the information to the emergency data manager100. Each emergency call is routed to the PSAP that corresponds to the geographic boundary delineating the PSAP's jurisdiction or area of responsibility for emergency services. For each emergency call, the emergency data manager100searches its records for additional information including the caller's home and work addresses, medical history, and a phone number for the caller's emergency contact. The emergency data manager100then uses the identifier of the PSAP to retrieve the processed geofence having the geographic boundary delineating the PSAP's area of responsibility. The emergency data manager100then determines whether or not the caller's current location is within the geofence. When the emergency data manager100determines that the caller's current location is within the processed geofence. The emergency data manager100also accesses the ALI feed or CAD spill of the PSAP to locate the phone identifier corresponding to the current location for Eric's phone. Once the location has been successfully matched to the phone identifier, the emergency data manager100automatically pushes all of the emergency data associated with Eric's phone number to the operator to be visualized using the jurisdiction view. The jurisdiction view displays a graphical representation of the caller's current location within a map view on the GUI along with a textual description of the caller's current location (e.g., latitude and longitude) within a text box. The emergency data is already available when the operator accesses the jurisdiction view, allowing the operator to immediately dispatch emergency help to the caller's current location. In addition, the jurisdiction view optionally shows information for other emergencies in the PSAP's jurisdiction. The jurisdiction view shows a historical list of emergency calls within the past 20 minutes sorted by time of the call. The map view shows ongoing emergencies on the map with graphical representations of the current locations of the callers. This graphical view allows the operator to determine when multiple emergency calls may be related to the same emergency, e.g., when the map shows multiple ongoing emergency calls clustered close together. Example 6 Emergency Type Determination “Just-in-Time,” emergency data manager may be used to determine the appropriate ESP to respond to an emergency, and determine a specific geofence for a specific emergency where a single ESP may have multiple geofences. For example, specific emergency data (e.g., health sensor data, etc.) obtained by the emergency data manager may indicate a medical emergency. The emergency data manager will determine the specific geofence that will be used by the ESP for the response. For example, the ESP may have a defined geofence specifically for medical emergencies. Additionally, other factors such as, but not limited to, the proximity of the accident to the national highway etc. may also be used by the emergency data manager to determine which specific geofence should apply. Various other use cases may be contemplated by one of ordinary skill in light of the various embodiments and various examples disclosed herein. While various embodiments have been illustrated and described, it is to be understood that the invention is not so limited. Numerous modifications, changes, variations, substitutions and equivalents will occur to those skilled in the art without departing from the scope of the present invention as defined by the appended claims. | 277,898 |
11943695 | DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure will be further described in detail with reference to the drawings and embodiments. It will be understood that the specific embodiments described herein are only used to explain rather than limit the present disclosure. It should be also noted that for convenience of description, only some, but not all, of the structures relating to the present disclosure are shown in the drawings. Before describing the embodiments of the present disclosure, the application scenarios of the embodiments of the present disclosure will be explained. The network channel switching method, apparatus, device, and storage medium in the embodiments of the present disclosure may be applied to channel migration of wireless mesh networks (e.g., mesh networks). A mesh network may be composed of a router and a plurality of node devices. Such a mesh network may be constructed by a point-to-point or point-to-multipoint topology among node devices. As shown inFIG.1, the mesh network includes a router10, a root node device11, intermediate node devices12-13, and leaf node devices14-16. The intermediate node device13is connected to the leaf node device16in a point-to-point manner, the root node device11is connected to the intermediate node device12and the intermediate node device13in a point-to-multipoint manner, and the intermediate node device12is connected to the leaf node device14and the leaf node device15in a point-to-multipoint manner. The node devices in a wireless mesh network may be divided into levels according to a direct or indirect connection relationship among the node devices and the router: the node devices directly connected to the router may be regarded as first-level node devices, such as the root node device11inFIG.1; the node devices indirectly connected to the router through one node device may be regarded as second-level node devices, such as the intermediate node devices12-13inFIG.1; and the node devices indirectly connected to the router through two node devices may be regarded as third-level node devices, such as the leaf node devices14-16inFIG.1, and so on. In embodiments of the present disclosure, taking the mesh network shown inFIG.1as an example, a channel switching method in a wireless mesh network according to embodiments of the present disclosure is further explained in detail. It can be understood that the mesh network inFIG.1described herein is only used for explaining rather than limiting the present disclosure. The network applicable to the network channel switching method provided in embodiments of the present disclosure may include any network that is composed of a plurality of node devices having parent-child node connection relationships. It should be also noted that for convenience of description, only some, but not all, of the structures relating to the present disclosure are shown in the drawings. First Embodiment FIG.2is a flow chart of a network channel switching method provided in the first embodiment of the present disclosure. This embodiment may be applicable to implement channel switching in a network that is composed of a plurality of node devices having parent-child node connection relationships, such as to implement channel switching in a mesh network. The method may be performed by a network channel switching apparatus provided in an embodiment of the present disclosure, which may be implemented in hardware and/or software, for example, may be configured in any node device in the mesh network. The node devices in the wireless mesh network may include smart phones, smart TVs, smart stereos, tablet computers, or wearable devices. As shown inFIG.2, the method specifically includes the following steps: In S201, network channel switching information sent by an upper-level parent node device having a connection relationship therewith is obtained, and the network channel switching information is sent to at least a lower-level child node device having a connection relationship therewith. The network channel switching information may be information related to a Channel Switch Announcement (CSA) defined in Wireless-Fidelity (Wi-Fi) protocols, which may be used as information for instructing each node device in the network to perform channel switching. The network channel switching information may include, but not limited to, information such as a channel switching latency value (csa_count), a target channel to be switched to (csa_newchan), and a node state. Specifically, the channel switching latency value may be used to represent the number of beacons that each node device has to wait from receiving the network channel switching information to performing a channel switching. The timing for each node device to perform channel switching may be determined from the channel switching latency value. The target channel to be switched to may refer to a channel to be switched to by the current node device, i.e., the channel to be switched to by the mesh network, which is also the channel that the router in the mesh network has been switched to. The node state may be the state of the node device sending the network channel switching information, such as a connectable state (i.e., AP state) and a unconnectable state (i.e., station state). It should be noted that the embodiments of the present disclosure may be performed by any node device in the mesh network. Every node device in the mesh network may perform the operations described in the embodiments of the present disclosure; that is, the channel switching of the entire mesh network may be completed while connections of every node device in the network may be maintained. In the present embodiment, the current node device may be an arbitrary node device in the mesh network, and the current node device performing the method in the embodiments of the present disclosure will be described hereinafter as an example. An upper-level parent node device having a connection relationship therewith may be a node device in the mesh network that is connected to the current node device and at an upper level of the current node device. As shown inFIG.1, if the current node device is the intermediate node device12, the upper-level parent node device having a connection relationship with the intermediate node device12may be the root node device11. Optionally, if the current node device is the root node device11, the upper-level parent node device having a connection relationship with the root node device11may be the router10. The at least a lower-level child node device having a connection relationship therewith may be a node device in the mesh network that is connected to the current node device and is at a lower level of the current node device. As shown inFIG.1, if the current node device is the intermediate node device12, the lower-level child node devices having a connection relationship with the intermediate node device may be the leaf node device14and the leaf node device15. Optionally, in the embodiments of the present disclosure, the current node device may receive network channel switching information sent by an upper-level parent node device connected with it, and then send the network channel switching information to the lower-level child node devices connected with it. Specifically, the receiving and sending process may include the following three steps. A) The network channel switching information broadcasted via a beacon of the upper-level parent node device having a connection relationship therewith is received. A beacon may be a way for sending and receiving messages between node devices in a mesh network, and each node device has its own beacon. In the present embodiment, each node device may send the network channel switching information to at least a lower-level child node device via its own beacon. For example, when a node device is to send information to another node device in the network, the node device may add the information to be sent to its own beacon, and then send the information to be sent to the entire network via the beacon through a network-wide broadcast. Exemplarily, the upper-level parent node device of the current node device adds the network channel switching information to a beacon of the parent node device and sends the network channel switching information to the wireless mesh network through a network-wide broadcast. The current node device monitors and receives the information sent via the beacon of the upper-level parent node; that is, the network channel switching information sent by the upper-level parent node device of the current node device is obtained. Optionally, in addition to the network channel switching information, the information broadcasted via the beacon of the upper-level parent node device may also include an identifier of the parent node device and/or an identifier of a lower-level child node device of the parent node device (i.e., the current node device), so as to determine the receiver to which the information is sent. B) The received network channel switching information is added to a beacon of the node device itself. Optionally, in an embodiment of the present disclosure, the process of the node device adding the obtained network channel switching information to a beacon of the node device itself may be as follows: directly adding the network channel switching information obtained from the upper-level parent node device to the beacon of the node device itself, or encrypting the network channel switching information obtained from the upper-level parent node device and then adding it to the beacon of the node device itself, so as to ensure the security of information transmission and prevent the information from being monitored by other node device. In the present embodiment, the specific encryption algorithm is not limited, which may be, for example, public-private key encryption algorithm, hash encryption algorithm, digital signature algorithm, and so on. Accordingly, if the network channel switching information that is added to the beacon by the parent node device connected to the child node device for receiving the network channel switching information is unencrypted, the information may be directly obtained; if the network channel switching information that is added to the beacon is encrypted, the obtained information may be decrypted according to a preset algorithm to obtain the network channel switching information. Optionally, different node devices in the mesh network may encrypt the network channel switching information and decrypt the received data information broadcasted via the beacon with a same encryption algorithm; or, each node device may have its own beacon encryption algorithm, and only the node device and its lower-level child node devices know the encryption and decryption algorithm of the beacon data of the node device, which is used by the node device to encrypt the network channel switching information and decrypt the data information of the obtained beacon broadcast of the parent node. C) The network channel switching information in the beacon of the node device itself is sent to the at least a lower-level child node device having a connection relationship therewith through a network-wide broadcast. Exemplarily, when a current node device sends a beacon to the lower-level child node devices connected with it, the current node device may send the network channel switching information in its own beacon to the lower-level child node devices through a network-wide broadcast. Optionally, the current node device may send the network channel switching information in its own beacon to all node devices in the wireless mesh network through a network-wide broadcast, but only the lower-level child node devices in the wireless mesh network that have a connection relationship with the current node device will receive the network channel switching information sent by the current node device. It should be noted that, in the embodiment of the present disclosure, if the node device in the mesh network is a root node device, the network channel switching information sent by a router will be obtained, and the network channel switching information will be sent to lower-level child node devices having a connection relationship with the root node device. If the node device in the wireless mesh network is not a root node device, the network channel switching information sent by an upper-level parent node having a connection relationship therewith will be obtained, and the network channel switching information will be sent to the lower-level child node devices having a connection relationship therewith. If the node device in the mesh network is a bottom-level node device and does not have a lower-level child node device having a connection relationship therewith, the bottom-level node device will only obtain the network channel switching information sent by the upper-level parent node device having a connection relationship therewith and will not proceed to send the network channel switching information. Optionally, if the network quality is poor or there are interferences among devices, in order to ensure that the node devices in the wireless mesh network can still receive the network channel switching information, the current node device may send the network channel switching information to the lower-level child node devices connected with it according to a preset beacon interval for multiple times. Specifically, it is possible that the number of times a current node device sends the network channel switching information to its lower-level child node devices may be the same as the number of times the current node device receives the network channel switching messages sent from the upper-level parent node device. The number of times a root node device connected to a router in the wireless mesh network sends the network channel switching information to its lower-level child node devices may be determined according to the channel switching information sent from the router and/or a preset rule. In S202, switching from a current channel to a target channel according to the received network channel switching information is performed. The current channel may be the channel where the current node device is currently in, i.e., the channel where the mesh network was in before the switching of the channel. The target channel may be the channel that the current node device will switch to, i.e., the channel that the mesh network will switch to, or the channel that the router in the mesh network has switched to. Optionally, in an embodiment of the present disclosure, the specific process of switching from a current channel to a target channel according to the received network channel switching information may include the following three steps. A) A channel switching latency value and a target channel to be switched in the network channel switching information are obtained. For example, the channel switching latency value and the target channel to be switched to may be contained in the network channel switching information in an unencrypted or encrypted form. Accordingly, obtaining the channel switching latency value and the target channel to be switched to in the network channel switching information may include obtaining the channel switching latency value and the target channel to be switched to directly from the network channel switching information, or decrypting the network channel switching information to obtain the channel switching latency value and the target channel to be switched to. B) A latency time period to perform the network channel switching is determined according to the channel switching latency value. For example, the specific manner for determining a latency time period to perform the network channel switching according to the channel switching latency value may include multiplying the channel switching latency value with a preset beacon interval to obtain the latency time period to perform the network channel switching. Optionally, the preset beacon interval may be a preset beacon interval that is set for the mesh network according to the current network quality, information transmission rate and etc. and which may be the default for the node devices in the network. Alternatively, the preset beacon interval may be a preset beacon interval that is set by each node device according to its own characteristics. In this regard, there is no any limit thereto imposed by the present embodiment. C) The switching from the current channel to the target channel is performed when the latency time period is lapsed. For example, a timer in the current node device may start timing when the current node device receives the network channel switching information sent by its parent node device or when the current node device sends the network channel switching information to its lower-level child node devices for the first time. When the latency time period is lapsed, the timer will trigger to control the current node device to switch from the current channel to the target channel. It should be noted that there is a router in the mesh network and the root node device obtains the network channel switching information from the router, according to an embodiment of the present disclosure. However, the source of the network channel switching information is not limited to the router, and may also include other sources. For example, after the root node device in the mesh network is disconnected from the router, the root node device may trigger all-channel scanning, search for the historically connected router, obtain the channel switching latency value of the router (the channel switching latency value may also be generated according to its own network quality) and the target channel to be switched to, and generate the network channel switching information. Alternatively, after another node device other than the root node device in the mesh network is disconnected from the parent node device having a connection relationship therewith, the another node device may trigger all-channel scanning, search for a previous upper-level parent node device or a new upper-level parent node device having a connection relationship therewith, and obtain the channel switching latency value (the channel switching latency value can also be generated according to its own network quality) and the target channel to be switched to from the previous upper-level parent node device or the new upper-level parent node device having a connection relationship therewith, and generate the network channel switching information. Further, in a scenario that there is no router included in the mesh network, the network channel switching information may be generated according to a channel to be switched to and a channel switching latency value, in which the channel to be switched to is set by the user and the channel switching latency value is generated based on its own network quality. In this regard, there is no any limit thereto imposed by the present embodiment. In the present embodiment, a network channel switching method is provided, in which each node device in the mesh network obtains network channel switching information sent by an upper-level parent node device, then sends the network channel switching information to lower-level child node devices, and performs a channel switching according to the received network channel switching information. In this manner, a success rate of each node device in the mesh network receiving network channel switching information may be greatly improved, such that the channel switching of the entire mesh network may be completed while connections of every node device in the network may be maintained, and the efficiency of channel switching in the mesh network may be improved. Further, since the network channel switching information sent to the mesh network by different routers may be different, the channel switching latency value in each network channel switching information may also be different. If the channel switching latency value is relatively small, the upper-level parent node device may switch to the target channel before the node devices in the whole network all receive the information. Due to this, the node devices that have not received the information may be disconnected from the upper-level parent node device and then exit the mesh network. In an embodiment of the present disclosure, in order to avoid such a problem, after the root node device in the mesh network obtains the network channel switching information sent by the router, the method further includes: adjusting the channel switching latency value in the network channel switching information according to the current network quality, in which the channel switching latency value may be used to determine a latency time period for each node device to perform a network channel switching. Specifically, when the root node device adds the received network channel switching information to its own beacon, the root node device may appropriately increase the channel switching latency value in the network channel switching information according to the current network conditions (e.g., long beacon transmission period or significant interference). Therefore, the time that the entire network completes channel migration is not dependent on the configuration of the router anymore, but on the state of the network itself. As such, the channel switching of the entire network may be completed while the connections of every node device in the network may be maintained, and the efficiency of the network channel switching is improved. Second Embodiment FIG.3is a flow chart of a network channel switching method provided in the second embodiment of the present disclosure. The network channel switching method is further optimized on the basis of the above embodiments, and specifically provides a preferred embodiment of a channel switching method in a mesh network with two levels of child node devices. In conjunction with the schematic structural diagram of the mesh network shown inFIG.1, the network channel switching method shown inFIG.3is described, and the method includes the following steps. In S301, a root node device obtains network channel switching information sent by a router, and sends the network channel switching information to at least a first-level child node device having a connection relationship with the root node device. The first-level child node device may refer to one or more child node devices having a connection relationship with the first-level node device (i.e., the root node device). As an example, the root node device11in the mesh network receives the network channel switching information sent by the router10, adds the network channel switching information to its own root node beacon, and sends the network channel switching information to first-level child node devices (i.e., the intermediate node device12and the intermediate node device13) connected to it in the wireless mesh network through a network-wide broadcast. Optionally, the root node device11may send the network channel switching information to the intermediate node device12and the intermediate node device13according to a preset beacon interval for multiple times, i.e., once every preset bacon interval. For example, the network channel switching information may be added to ten beacons and sent to the intermediate node device12and the intermediate node device13for ten times according to the preset beacon interval. In S302, the root node device switches from a current channel to a target channel according to the received network channel switching information. As an example, the root node device11obtains the channel switching latency value and the target channel to be switched to from the received network channel switching information. A latency time period to perform a network channel switching is determined according to the channel switching latency value. For example, the latency time period to perform a channel switching may be calculated according to the formula of T=csa_count×TBTT, where T is the latency time period to perform the channel switching, csa_count is the channel switching latency value, and TBTT (Target Beacon Transmission Time) is the preset beacon interval. Then, a timer in the root node device11performs a timing operation, and the switching from a current channel to a target channel is preformed when the calculated channel switching latency time period is lapsed. In S303, the first-level child node device obtains the network channel switching information sent by the root node device, and sends the network channel switching information to at least a second-level child node device having a connection relationship with the first-level child node device. The second-level child node device may refer to at least a child node device having a connection relationship with the second-level node device (e.g., intermediate node device). As an example, the intermediate node device12of the first-level child node devices in the mesh network receives the network channel switching information sent by the root node device11, adds the network channel switching information to its own beacon, and sends the network channel switching information to second-level child node devices connected to it in the mesh network through a network-wide broadcast, i.e., the leaf node device14and the leaf node device15. Optionally, the number of times the intermediate node device12sends network channel switching information to the leaf node devices14and15may be dependent on the number of times the intermediate node device12receives the network channel switching information sent by the root node device11. For example, if the intermediate node device12receives the network beacon sent by the root node device11for eight times, the intermediate node device12may send the network channel switching information to the leaf node device14and the leaf node device15for eight times. It should be noted that the first-level child node devices shown inFIG.1include the intermediate node device12and the intermediate node device13. The present step is described by taking the intermediate node device12as an example here. The process that the intermediate node device13receives the network channel switching information sent by the root node device11and sends the network channel switching information to the leaf node device16connected with it is the similar to the above process, and will not be repeated here. In S304, the first-level child node device switches from a current channel to a target channel according to the received network channel switching information. As an example, the intermediate node device12and the intermediate node device13among the first-level child node devices obtain the channel switching latency value and the target channel to be switched to from the received network channel switching information. The latency time period to perform the network channel switching is determined according to the channel switching latency value. For example, the latency time period to perform the channel switching may be calculated according to the formula of T=csa_count×TBTT, where T is the channel switching latency time period, csa_count is the channel switching latency value, and TBTT is the preset beacon interval. Then, the timers in the intermediate node device12and the intermediate node device13perform timing operations respectively, and the switching from a current channel to a target channel is performed when the corresponding calculated channel switching latency time period is lapsed. Optionally, the intermediate node device12and the intermediate node device13may receive the network channel switching information more than once; hence, when the timing for the switching waiting time period is performed, for example after the network channel switching information is received for the first time, a switching latency time is determined, and the timing operation is started. In S305, the second-level child node device switches from a current channel to a target channel according to the received network channel switching information. As an example, the leaf node devices14to16among the second-level child node devices obtain the channel switching latency value and the target channel to be switched to from the received network channel switching information. The latency time period to perform the network channel switching is determined according to the channel switching latency value. For example, the latency time period to perform the channel switching may be calculated according to the formula of T=csa_count×TBTT, where T is the channel switching latency time period, csa_count is the channel switching latency value, and TBTT is the preset beacon interval. Then, the timers in the leaf node devices14to16perform the timing operations respectively, and the switching from a current channel to a target channel is performed when the corresponding calculated channel switching latency time period is lapsed. Similarly, the leaf node devices14to16may receive the network channel switching information more than once; hence, when the timing for the switching latency time period is performed, for example after the network channel switching information is received for the first time, a switching latency time is determined, and the timing operation is started. In the present embodiment, a network channel switching method is provided. According to the network channel switching method provided in present disclosure, the channel switching in the entire mesh network is completed while the connection of each node device in the entire mesh network (composed of three levels of node devices) is maintained, and the efficiency of the channel switching of the mesh network is improved. Third Embodiment FIG.4is a flow chart of a network channel switching method provided in the third embodiment of the present disclosure. The network channel switching method is further optimized on the basis of the above embodiments, and specifically describes the specific situation of network channel switching when the node device in the mesh network has lost the network channel switching information. As shown inFIG.4, the method includes the following steps. In S401, if the network channel switching information is lost, an all-channel scanning is triggered to search for the upper-level parent node device having a connection relationship therewith. As an example, since the network channel switching information is added to a beacon and sent through a broadcast, and there are interferences among the node devices in the mesh network, some node devices in the network may have lost the network channel switching information. Optionally, in the process of obtaining the network channel switching information sent by the upper-level node device having a connection relationship therewith, the loss of the network channel switching information happens at least in the following two situations: (1) the node device obtains and checks the network channel switching information (e.g., performs a CRC check on the network channel switching information); if the check fails, the node device may discard the received network channel switching information, and thus the network channel switching information is lost by the node device; (2) due to poor network quality, interferences among the node devices, insufficient memory of the node devices, or other reasons, the network channel switching information is never obtained in the process of obtaining the network channel switching information. At this time, some node devices in the mesh network may exit the network because these node devices have lost the network channel switching information and have not completed the channel migration. To solve the above problems, when the current node device has lost the network channel switching information and the upper-level parent node device has finished channel switching, that is, the current node device and the upper-level parent node device are in two different channels, the current node device may trigger an all-channel scanning to search for the upper-level parent node device having a connection relationship with the current node from all channels. Optionally, if a root node device in the wireless mesh network loses the network channel switching information, the root node device may trigger an all-channel scanning to search for a historically connected router. For example, according to the identification information of the historically connected router, the root node device may scan out the router with the identification information from all channels. If a non-root node device in the mesh network loses the network channel switching information, the non-root node device may trigger the all-channel scanning in the mesh network to search for the upper-level parent node device having a connection relationship with the current node device in the mesh network. For example, the current node device may scan all channels in the mesh network according to the identification of the upper-level parent node device having a connection relationship therewith to search for the node device with the identification of the upper-level parent node device. Optionally, in order to improve the channel switching efficiency of the entire mesh network, a preset time period (e.g., one minute) may be set when searching for the upper-level parent node device for the node device that has lost the network channel switching information, and the search range may be expanded if the upper-level node device is not found within the preset time period. Optionally, if the node device that has lost the network channel switching information in the mesh network is a root node device, the entire mesh network cannot carry out channel migration. In this case, when the root node device does not scan out a router historically connected with the root node device within the preset time period, a router failure may have happened. Therefore, in order to ensure the normal networking of the entire mesh network, the root node may search for other standby routers in the mesh network and take one of the other standby routers identified from the search as the upper-level parent node device having a connection relationship therewith. Specifically, the root node device in the mesh network stores not only the identification information of the historically connected router but also the identification information of at least one standby router. At this time, all-channel scanning may be performed according to the identification information of at least one standby router and the identification information of the historically connected router. When a router with a same identification information is scanned out, the router may be taken as the upper-level parent node device having a connection relationship with the root node device. If the node device losing the network channel switching information in the mesh network is a non-root node device and the non-root node device fails to scan out an upper-level parent node device having a connection relationship therewith within the preset time period, another node device in the mesh network may be searched for; and the another node device identified from the search may be taken as the upper-level parent node device having a connection relationship therewith. The process of searching for the another node device in the mesh network may include scanning out the another node device that also stores the mesh network identification according to a wireless mesh network identification stored in advance; when a node device that stores the identification is scanned out, the node device may be taken as the upper-level parent node device having a connection relationship therewith. In S402, the channel switching latency value and the target channel to be switched to are obtained from the upper-level parent node device, and the network channel switching information is generated. Optionally, in the present embodiment, the channel switching latency value and the target channel to be switched to may be obtained from an upper-level parent node device in various ways. For example, the channel switching latency value and the target channel to be switched to may be obtained by communicating with the upper-level node device and requesting the upper-level node device to send the channel switching latency value and the target channel to be switched to. Alternatively, the channel switching latency value may be determined according to the current network quality and a preset rule by taking the channel where the scanned out upper-level parent node device is in as the target channel to be switched to. In this regard, there is no any limit thereto imposed by the present embodiment. Optionally, in the present embodiment, the process of generating the network channel switching information after the channel switching latency value and the target channel to be switched to are obtained by the current node device may include combining and/or encrypting the channel switching latency value, the target channel to be switched to and the state information of the current node to generate the network channel switching information. Other ways can also be adopted to generate the network channel switching information according to the channel switching latency value and the target channel to be switched to. In this regard, there is no any limit in the present embodiment. Optionally, if a root node device in the mesh network lost the network channel switching information, the root node device may trigger an all-channel scanning to search for the historically connected router, and then obtains the channel switching latency value and the target channel to be switched to from a historically connected router and generates the network channel switching information. If a non-root node device in the wireless mesh network lost the network channel switching information, the non-root node device may trigger an all-channel scanning to search for the upper-level parent node device having a connection relationship therewith, and then obtains the channel switching latency value and the target channel to be switched to from the upper-level parent node device having a connection relationship therewith, and generates the network channel switching information. If there is no router in the mesh network, the node device in the mesh network may generate the network channel switching information according to the channel to be switched to set by the user and the channel switching latency value generated according to the network quality. In S403, the network channel switching information is sent to the at least a lower-level child node device having a connection relationship therewith. As an example, after regenerating the network channel switching information, the node device that has lost the network channel switching information in the mesh network may not immediately perform a channel switching, but instead send the channel switching information to the lower-level child node devices having a connection relationship therewith so as to ensure that the lower-level child node devices can perform a channel switching according to the channel switching information, and then proceed to step S404to switch from the current channel to the target channel according to the generated network channel switching information, that is, to establish a connection relationship with another node device that has been identified from the searched(the previous or new upper-level parent node device having a connection relationship therewith). In S404, the switching from a current channel to a target channel is performed according to the generated network channel switching information. In the present embodiment, a network channel switching method is provided. According to this method, when a node device in the network lost network channel switching information, the node device may search for an upper-level parent node device by triggering an entire network scanning, obtain the channel switching latency value and the target channel to be switched to, generate the network channel switching information, then proceed to send the network channel switching information to at least a lower-level child node device, and switch channel according to the generated network channel switching information. Accordingly, in the case that the node device is disconnected from the mesh network or the router due to the loss of the network channel switching information, the network channel switching information may still be determined quickly, so as to complete the channel switching of the entire network, thereby avoiding the situation that node devices in the mesh network are lost in the channel switching process and ensuring the integrity of network channel switching. Fourth Embodiment FIG.5is a schematic structural diagram of a network channel switching apparatus provided in the fourth embodiment of the present disclosure. The network channel switching device may be configured in a node device in a wireless mesh network, can perform the network channel switching method provided in any embodiment of the present disclosure, and has corresponding functional modules for and advantageous effects from performing the method. As shown inFIG.5, the apparatus may include: an information transceiving module501, configured to obtain network channel switching information sent by an upper-level parent node device having a connection relationship therewith and send the network channel switching information to at least a lower-level child node device having a connection relationship therewith; and a channel switching module502, configured to switch from a current channel to a target channel according to the received network channel switching information. The present embodiment provides a network channel switching apparatus, in which each node device in the mesh network may obtain network channel switching information sent by an upper-level parent node device, then sends the network channel switching information to at least a lower-level child node device, and performs a channel switching according to the received network channel switching information, by means of which a success rate of each node device in a mesh network receiving network channel switching information may be greatly improved, such that the channel switching of the entire mesh network may be completed while the connections of every node device in the network may be maintained, and the efficiency of channel switching in the mesh network may be improved. Further, the information transceiving module501is specifically configured to: receive the network channel switching information broadcasted via a beacon of the upper-level parent node device having a connection relationship therewith; adding the received network channel switching information to a beacon of the node device itself; and sending the network channel switching information in the beacon of the node device itself to the at least a lower-level child node device having a connection relationship therewith through a network-wide broadcast. Further, the information receiving and sending module501is specifically configured to: if the node device in the wireless mesh network is a root node device, obtain network channel switching information sent by a router, and send the network channel switching information to the at least a lower-level child node device having a connection relationship with the root node device. Further, the device may also include: a latency value adjustment module, configured to adjust a channel switching latency value in the network channel switching information according to the current network quality, in which the channel switching latency value is used to determine a latency time period for each node device to perform a network channel switching. Further, the channel switching module502may be configured to: obtain a channel switching latency value and a target channel to be switched to in the network channel switching information; determine a latency time period to perform a network channel switching according to the channel switching latency value; and switch from a current channel to a target channel when the latency time period is lapsed. Further, the device may also include: a channel scanning module, configured to trigger an all-channel scanning to search for the upper-level parent node device having a connection relationship therewith if the network channel switching information is lost; and an information generation module, configured to obtain the channel switching latency value and the target channel to be switched to from the upper-level parent node device, and generate network channel switching information. Further, the channel scanning module may specifically be configured to: if a root node device in the wireless mesh network lost the network channel switching information, trigger the all-channel scanning to search for a historically connected router; Accordingly, the information generation module may specifically be configured to: obtain the channel switching latency value and the target channel to be switched to from the historically connected router, and generate the network channel switching information. Further, the channel scanning module may also be configured to: if the node device in the wireless mesh network is a non-root node device and the non-root node device fails to scan out an upper-level parent node device having a connection relationship therewith within a preset time period, search for another node device in the wireless mesh network; and taking the another node device identified from the searching as the upper-level parent node devices having a connection relationship therewith. Fifth Embodiment FIG.6is a schematic structural diagram of a device provided in the fifth embodiment of the present disclosure.FIG.6illustrates a block diagram of an exemplary device60suitable for implementing the embodiments of the present disclosure. The device60shown inFIG.6is only an example, and should not be constructed as limiting in anyway the functions and application scope of the embodiments of the present disclosure. As shown inFIG.6, the device60is embodied in the form of a general-purpose computing device. The device60may be a node device in a network for channel switching. Components of the device60may include, but not limited to, one or more processors or processing units601, a system memory602, and a bus603connecting different system components (including the system memory602and the processing unit601). The bus603represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of a plurality of bus structures. For example, these architectures include, but not limited to, an Industry Standard Architecture (ISA) bus, a Microchannel Architecture (MAC) bus, an Enhanced ISA bus, a video electronics standards association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus. The device60typically includes a plurality of computer system readable media that may be any available media accessed by the device60, including volatile and non-volatile media, removable and non-removable media. The system memory602may include computer system readable media in the form of a volatile memory, such as random-access memory (RAM)604and/or cache memory605. The device60may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, the storage system606may be used for reading and writing non-removable, non-volatile magnetic media (not shown inFIG.6, which is commonly referred to as a “hard disk drive”). Although not shown inFIG.6, a disk drive for reading and writing a removable non-volatile disk (e.g., “floppy disk”) and an optical disk drive for reading and writing a removable non-volatile disk (e.g., CD-ROM, DVD-ROM or other optical media) may be provided. In these cases, each drive may be connected to the bus603through one or more data medium interfaces. The system memory602may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of embodiments of the present disclosure. A program/utility608having a set of (at least one) program modules607may be stored in, for example, the system memory602. The program modules607may include, but not limited to, an operating system, one or more application programs, other program modules, and program data, and each or some combination of these embodiments may include an implementation of a network environment. The program module607typically performs the functions and/or methods in the embodiments described in the present disclosure. The device60may also communicate with one or more external devices609(e.g., a keyboard, a pointing device, and a display610), and may also communicate with one or more devices that enable a user to interact with the device, and/or with any device that enables the device60to communicate with one or more other computing devices (e.g., a network card and a modem). This communication may be performed through an input/output (I/O) interface611. Furthermore, the device60can also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN) and/or a public network including the internet) through the network adapter612. As shown inFIG.6, the network adapter612communicates with other modules of the device60through the bus603. It should be understood that although not shown in the figure, other hardware and/or software modules may be used in conjunction with the device60, including, but not limited to, a microcode, a device driver, a redundant processing unit, an external disk drive array, a RAID system, a tape drive, and a data backup storage system. The processing unit601executes various functional applications and processes data by running programs stored in the system memory602, for example, implementing the network channel switching method provided in embodiments of the present disclosure. Sixth Embodiment The sixth embodiment of the present disclosure also provides a computer readable storage medium with a computer program stored thereon. When the program is executed by one or more processors, the network channel switching method described in the above embodiment may be achieved. The computer storage medium of embodiments of the present disclosure may be any combination of one or more computer readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (as a non-exhaustive list) of computer readable storage media may include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any combination thereof. In the present disclosure, a computer readable storage medium may be any tangible medium containing or storing a program, and the program may be used by or in combination with an instruction execution system, an apparatus or a device. The computer readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, in which a computer readable program code is carried. The propagated data signal may take various forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer readable signal medium may also be any computer readable medium other than the computer readable storage medium, which can send, propagate or transmit a program used by or in connection with an instruction execution system, an apparatus, or a device. The program code contained on the computer readable medium may be transmitted by any suitable medium, including but not limited to wireless, electric wire, optical cable and RF, or any suitable combination thereof. A computer program code for executing the operations of the present disclosure may be written in one or more programming languages or a combination thereof, including an object-oriented programming language such as Java, Smalltalk, C++, and a conventional procedural programming language such as “C” language or a similar programming language. The program code may be completely executed on a user computer, partially executed on a user computer, executed as an independent software package, partially executed on a user computer and partially executed on a remote computer, or completely executed on a remote computer or server. In a case involving a remote computer, the remote computer may be connected to a user computer through any kind of network including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., connected through the Internet provided by an Internet service provider). The numbering of the above embodiments are only for description, and do not represent the pros and cons of the embodiments. It should be understood by those of ordinary skill in the art that the modules or operations of the above embodiments of the present disclosure may be achieved by a general computing device, concentrated on a single computing device or distributed on a network including multiple computing devices, and alternatively achieved by a program code executed by a computer device, so that the modules or operations may be stored in a storage device and executed by the computing device, or made into various integrated circuit modules respectively, or multiple modules or operations among the modules or operations may be made into a single integrated circuit module. Thus, the present disclosure is not limited to any specific combination of hardware and software. The embodiments in the specification have been described in a progressive manner. What are emphasized in each embodiment are directed to the differences from other embodiments. Identical or similar features among the embodiments may be identified by mutual reference. The preferred embodiments described herein are for illustration of the present disclosure only but not a limit thereto. For a person of ordinary skill in the art, various modifications or changes may be made to the present disclosure. Any modifications, equivalent substitutions and improvements made within the spirit and principle of the present disclosure should be incorporated in the scope of protection of the present disclosure. | 55,394 |
11943696 | The present disclosure will be described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left most digit(s) of a reference number identifies the drawing in which the reference number first appears. DETAILED DESCRIPTION Advances in communications technology have opened avenues for inmates to circumvent more traditional forms of monitoring that are typically available in correctional facilities. Maintaining the ability to ensure control and/or monitoring of communications from or to a controlled facility is, therefore, an important aspect to the security of the correctional facilities. With the advances in cellular communications technology, maintaining security becomes more difficult due to such issues as the smuggling of prohibited equipment into a monitored facility. Due to the small size of certain of the more recently-developed devices, such may avoid detection by more conventional search techniques including, but not limited to, walk through and manual metal detectors and even physical “pat-down” searches. Therefore, correctional facilities have the need to detect and control the use of the smuggling or “contraband” wireless and cellular devices. Due to the small size of certain of the more recently developed devices and the ingenuity of violating parties, such contraband devices become very hard to detect or control by conventional searching techniques. The correctional facilities may choose to install a fixed detection system to detect and monitor the usage of the contraband devices within the facilities. However, such systems usually require a large upfront cost for the installation, hardware and infrastructure, and initial training of the staff. Due to their complexity and delicacy, such systems usually require regular maintenances. In addition, with the rapid advancement of communication technologies, such systems need to be upgraded frequently to keep up with the most advanced technologies utilized by the contraband devices. The cost of maintenance and upgrade further increases the total cost of operation of such fixed systems. Moreover, once a fixed detection system is installed, the system is stationed within one facility/location. Without knowing the severity of the contraband device situation in a correctional facility, it may not be economical to invest a large amount of funding to install a fixed detection system before evaluating the need for such a system. Further, inmates may gain access to the detection system that is fixed in one location within the correctional facility and cause damage to the system or interrupt the operations of the system. Such potential risks may also greatly impact the utilization and security of the detection system. In light of the above, the present disclosure provides details of a system and method for detecting, locating and disrupting a contraband device by utilizing a portable detection and control system. The portable detection and control system is configured to detect and locate contraband devices within a correctional facility. The portable detection and control system is also configured to actively disrupt the communication of the contraband devices to block the communications, intercept the communication information, and gain control of the contraband devices. The portable detection and control system can be self-contained and fully enclosed in a transportable casing, so that it can be moved from one location to another. More features of such as portable detection and control system are to be discussed in detail. FIG.1illustrates a block diagram of a correctional facility and detection and control scheme100for a correctional facility, according to some embodiments of the present disclosure. The detection and control scheme comprises a detection and control system110, a correctional facility140, a communication center150. The correctional facility140comprises a contraband device130. In some embodiments, there are more than one contraband device in the correctional facility140. In one embodiment, there is another contraband device131in the correctional facility140. The detection and control unit110can be placed at location A outside the correctional facility140to detect the contraband device130in a “detection mode”. The contraband device130is used by the inmates to communicate with outside network illegally. In some embodiments, the communication is carried out between the contraband device130and a communication center150outside the correctional facility140. The communication center150, in some embodiments, is a nearby telecommunication tower for the wireless network carrier of the contraband device. The communication between the communication150and the contraband device130can be carried out with different communication technologies such as, but not limited to, GSM, 2G-5G technologies, WCDMA, CDMA, TDMA, UMTS, WIMAX, WIFI, IBEACON, Bluetooth, LTE, 700 MHz to 2200 MHz or other frequency band communication technologies. The detection and control unit110is configured to detect the transmission of signals of the contraband device130using some or all the technologies described above. In some embodiments, the contraband device130can also communicate with another communication center (e.g. communication center151). In some embodiments, the detection and control system110is also configured to intercept the transmitted data from the detected contraband device130and extract information from the detected contraband device130based on the transmitted data. Such information includes, but is not limited to, hardware information, data usage information, and location information of the contraband device130when the contraband device is detected. In some embodiments, the hardware information further includes a hardware identification number of the contraband device130(e.g. an international mobile subscriber identity number (IMSI), an electronic serial number (ESN), a mobile device ID, etc.), a phone number of the contraband device, and a phone number that is communicating with the contraband device. In some embodiments, the data usage information includes the duration of data transmission conducted by the contraband device and the volume of the data transmitted by the contraband devices. In some embodiments, the location information of the contraband device130is extracted by the detection and control system110by locating the contraband device130with a number of different positioning techniques. The positioning techniques include, but are not limited to, lateration (e.g. trilateration) and angulation (e.g. triangulation). Lateration is a process of estimating the location a contraband device given the distance measurements of the contraband device to a set of detection devices with known location. The location of the contraband device can be calculated and estimated by solving a set of equations based on the measured distances for each of the detection devices. Trilateration is a lateration process when a set of three detection devices with known locations are used to estimate the contraband device location. Angulation is a process of estimating the location of a contraband device given the measured angles between detecting devices at known locations and the contraband devices. The location of the contraband device can be calculated and estimated by solving a set of equations based on the measured angles for each of the detection devices. Triangulation is an angulation process when a set of three detection devices with known locations are used to estimate the contraband device location. In some embodiments, the distance of the contraband device to a detection device can be estimated by the Received Signal Strength Indicator (RSSI) of the detected signal, and the measured angle can be estimated by the Direction of Arrival (DOA) of the detected signal. Further, the detection and control system110can be configured to capture the motion of the contraband device130based on motion detection techniques. One example of such techniques is Doppler effect. In some embodiments, the detection and control system110is further able to track the location of the contraband device130during the time period when the contraband device is transmitting signal or is powered on. In some embodiments, the detection and control system110is configured to generate detection event information for each detection event when the contraband device (e.g. contraband device130) was detected. Such detection event information includes, but is not limited to, the date/time when the contraband device was detected, the duration of the contraband device being detected, and the location of the detection and control system110when the contraband device was detected. In some embodiments, the detection and control system110is configured to record the detection information (e.g. hardware information, location information, data usage information, and detection event information, etc.) in a memory. In some embodiments, the detection and control system110is also configured to analyze the recorded detection information in a given period of time (i.e. all the detection event information, all the hardware information of the detected contraband devices, all the data usage information of the detected contraband devices, and all the location information of the detected contraband devices in the period of time) to generate a collection of detection parameters. In some embodiments, the detection parameters include, but are not limited to, the total number of contraband device detection events, the total number of detected contraband devices, the total time of contraband device usage, the total volume of the data transmitted by the contraband devices, the location and distribution of the contraband devices, and the time and frequency of the data transmission made by the contraband devices. In some embodiments, the detection and control system110is also configured to generate a report for the detection of the contraband devices (e.g. the contraband device130) in a given period of time. In some embodiments, the report for the detection of the contraband devices in a given period of time includes all the detection event information, all the hardware information of the detected contraband devices, all the data usage information of the detected contraband devices, and all the location information of the detected contraband devices in the period of time. In some embodiments, the report for the detection of the contraband devices includes the collection of detection parameters such as, but not limited to, the total number of contraband device detection events, the total number of detected contraband devices, the total time of contraband device usage, the total volume of the data transmitted by the contraband devices, the location and distribution of the contraband devices, and the time and frequency of the data transmission made by the contraband devices. In some embodiments, the detection and control system110further includes a degree of severity (DOS) in the report for the detection of the contraband devices. In some embodiments, the degree of severity gives guidance to the jurisdiction on the severity of the contraband device usage. In some embodiments, the degree of severity is calculated based on the collection of detection parameters. In some embodiments, the degree of severity is a numerical number from 0 to 9, with 0 meaning no contraband device usage and 9 meaning the most severe contraband device usage. In some embodiments, the calculation of a degree of severity is based on a predetermined rule defined by the jurisdiction officers or the system administrator. In some embodiments, the predetermined rule defines a selection of detection parameters such as “p1” for the number of detected contraband devices, “p2” for the number of detection events, and “p3” for the total time of contraband device usage. The predetermined rule further defines a coefficient for each detection parameter (e.g. “c1” for “p1”, “c2” for “p2”, and “c3” for “p3”). The predetermined rule defines the relationship between the degree of severity (DAS) and the detection parameters by an specific algorithm (e.g. DAS=c1×p1+c2×p2+c3×p3). In some embodiments, the number of DAS is rounded to the nearest integer to give the final number of the degree of severity. A person of ordinary skill in the art would understand that the algorithm described in the current disclosure is only for illustration purpose and a different algorithm can be chosen or defined as needed. In some embodiments, the jurisdiction officer and/or the system administrator refers to the report of the detection of the contraband devices with or without a DOS before taking further actions in fighting the contraband device usage. Such actions include, but are not limited to, extending the detection period, locating the detected contraband devices physically, instructing the detection and control system110to take disruption actions, and deciding whether to install a fixed detection system inside the correctional facility. In some embodiments, the detection and control system110is also configured to actively disrupt the operation of the detected contraband device130in a “control mode”. A number of methods can be used by the detection and control system110to disrupt the operation of contraband device130in the control mode. In one embodiment, the detection and control system110transmits a wideband jamming signal to the contraband device130to block the contraband device130from successfully communicating with the communication center150. In one embodiment, the detection and control system110transmits a managed access request to the contraband device130and force the contraband device130to connect with the detection and control system110. Upon a successful setup of a managed access with the contraband device130, the detection and control system110is able to manage the contraband device130and applies usage rules determined by the jurisdiction offices. In one embodiment, the detection and control system110listens and records the communication transmitted to and from the contraband device130. Such communication can include, but is not limited to, phone calls, emails, voice messages and text messages. In some embodiments, the detection and control system110is fully enclosed in a transportable casing so that the system is portable. In some embodiments, the detection and control system110is carried around by human hand-holding. In some other embodiments, the detection and control system110can also be mounted on powered vehicles with or without human control. In yet some other embodiments, the detection and control system110can be mounted on unmanned aerial vehicles (UAVs). In some embodiments, the detection and control system110is placed at location A outside the correctional facility104for the duration of a detection. In some embodiments, the location A is a location between the correctional facility and the communication center150. In some other embodiments, the detection and control system110moves around from one location to another location for the duration of a detection. The detection and control system110collects detection information from multiple locations to improve the accuracy of the detection and cover a larger area of the correctional facility. In some embodiments, the location information of the detected contraband devices collected at multiple locations by the detection and control system110is analyzed using positioning technologies, such as triangulation, to improve the accuracy of the location of the detected contraband devices. In yet some other embodiments, the detection and control system110is moved to a location closer to the contraband device to improve the accuracy of the detection, and/or improve the efficiency for the disruption. In some embodiments, the detection and control scheme100further comprises a detection and control system120. In some embodiments, the detection and control system120is configured the same way as the detection and control system110. Referring toFIG.1, the detection and control system120is placed at location B outside the correctional facility140. Location B is remote to location A. In some other embodiments, the detection and control scheme comprises more detection and control systems than the detection and control systems110and120. In some embodiments, the detection and control system120is configured to detect the contraband devices (e.g. the contraband device130) within the correctional facility140independently from the detection and control system110. In some other embodiments, the detection and control systems110and120communicate with each other before, during, and/or after the detection to share the detection information of each detected contraband device. In yet some other embodiments, there are more detection and control systems than systems110and120. The sharing of detection information between multiple detection and control systems can be used for a variety of applications including, but not limited to, confirming detection events when more than one detection and control systems detect the same contraband device, locating the contraband device when location information for the contraband device are obtained from more than one detection and control system and used for lateration or angulation, and enhancing detection coverage when different detection and control systems are located in different locations around the correction facility. In some embodiments, the detection and control systems110and120communicate with each other to disrupt the communication of the detected contraband devices (e.g. the contraband device130). In one embodiment, the detection and control systems110and120located in different locations (i.e. location A and location B) send out jamming signals to the same detected contraband device and boost the strength of the jamming signals, therefore enhancing the disruption efficiency. Referring toFIG.1, in some embodiments, the detection and control scheme100further comprises a detachable detection and control unit180. In some embodiments, the detachable detection and control unit180is part of the detection and control system110and is detachable from the casing of the detection and control system110. The detachable detection and control unit180is configured to communicate with the detection and control system110wirelessly using technologies including, but not limited to, Bluetooth, WIFI, and radio frequency communication technologies. The detachable detection and control unit180is further configured to detect the transmission of signals from the contraband device130. The detachable and control detection unit180is able to detect signals using technologies such as, but not limited to, GSM, 2G-5G technologies, WCDMA, CDMA, TDMA, UMTS, WIMAX, WIFI, IBEACON, Bluetooth, LTE, 700 MHz to 2200 MHz or other frequency band communication technologies. In some embodiments, the detachable and control detection unit180is placed at location C outside the correctional facility140and location C is remote to location A. The detachable and control detection unit180detects transmission signals from the contraband device130and communicates the detection information of the detected contraband device with the detection and control system110. The communication of data between the detachable detection and control unit180and the detection and control system110can be used for a variety of applications including, but not limited to: confirming detection events when both the detection and control system110and the detachable detection and control unit180detect the same contraband device; locating the contraband device when the contraband device location information from both the detection and control system110and the detachable detection and control unit180are used for positioning; and enhancing the detection coverage when the detachable detection and control unit180is placed at a different location than the detection and control system110around the correction facility140. In some embodiments, the detection and control systems110and the detachable detection and control unit180communicate with each other to disrupt the communication of the detected contraband devices (e.g. the contraband device130). In one embodiment, the detection and control system110and the detachable detection and control unit180are located in different locations (i.e. location A and location C). Both the detection and control system110and the detachable detection and control unit180send out jamming signals to the same detected contraband device, which boosts the strength of the jamming signals received by the detected contraband device, therefore enhancing the disruption efficiency. Referring toFIG.1, in some embodiments, the correctional facility140further comprises a facility control center160. In some embodiments, the facility control center160is configured to communicate with the detection and control system130wirelessly to receive the updated detection information of the detected contraband devices. In some embodiments, whenever the detection and control system130detects a contraband device usage, the detection and control system130sends an alert to the facility control center160and notify the facility administrators of the detection event. The alert includes information such as, but not limited to, the date/time of the detection event, the location of the detected contraband device, and other information of the detected contraband devices. In some embodiments, the facility control center160is configured to take instructions from the facility administrators and transmit the instructions to the detection and control system130. Such instructions include, but are not limited to, initiate the control mode of the detection and control system130to disrupt the detected contraband devices, extend the detection period, relocate to the next target location for detection/disruption, pause the detection, generate a report of the detection, and terminate the detection. In some embodiments, the correctional facility140further comprises a facility mobile device170. The facility mobile device170can be carried around by the jurisdiction officers in the facility. In some embodiments, the facility mobile device170is configured to communicate with the facility control center160. The communication between the facility control center160and the facility mobile device170includes, but is not limited to, voice messages, text messages, phone calls, emails, and video calls. In some embodiments, the facility mobile device170is configured to receive alerts from the facility control center160whenever a detection event occurs. The alerts include information such as, but not limited to, the date/time of the detection event, the location of the detected contraband device, and other information of the detected contraband devices. The facility mobile device170is also configured to receive instructions from the facility control center160, such as, but not limited, conducting a physical search at a target location, patrolling a target region, and isolating a certain area of the facility. The facility mobile device170is further configured to send instructions or requests to the facility control center160, such as, but not limited to, continuing detection of the contraband device, sending updated location of the detected contraband devices, initiating the disruption of the contraband devices, and improving the location accuracy to narrow down the search area. In some embodiments, the facility mobile device170is further configured to directly communicate with the detection and control system110to obtain information and send out instructions. FIG.2illustrates a block diagram of an exemplary detection and control system200, according to some embodiments of the present disclosure. The detection and control system200is an exemplary embodiment of the detection and control system110and the detection and control system120inFIG.1. The detection and control system comprises a memory201, an application server202, a communication interface203, a power unit204, a plurality of input means205, a plurality of output means206, a plurality of sensors207, and an antenna unit208. In some embodiments, the memory201stores the information and instructions necessary for the operations of the detection and control system200. The information stored in memory201includes, but is not limited to, the detection event information for each detection event, the information extracted from the contraband devices in each detection event, the transmitted data intercepted by the communication interface203from the detected contraband devices, the reports generated by the detection and control system200for the detection of the contraband devices in a given period of time, the instructions received for the application server202, the instructions generated by the application server202, the data to be transmitted and the data received by the communication interface203, the data received by the plurality of input means205, and the data to be output by the plurality of output means206. In some embodiments, the application server202is the main processing unit for the detection and control system200. The application server202is configured to execute a variety of tasks, such as, but not limited to, instructing the communication interface203to detect the contraband devices, generating detection event information whenever a detection event occurs (e.g. a contraband device is detected), instructing the communication interface to intercept transmitted data from the detected contraband device (e.g. contraband device130), analyzing the transmitted data intercepted from the detected contraband device to extract the hardware information, data usage information, and location information of the detected contraband devices, recording the intercepted data from the detected contraband device in the memory201, recording the detection event information and the information extracted from the detected contraband devices in the memory201, performing positioning actions using positioning techniques to locate the contraband devices, generating instructions to perform disruption actions to disrupt the detected contraband devices, analyzing all the detection information (e.g. detection event information, hardware information, location information, data usage information, etc.) stored in the memory201to generate a report of the detection of the contraband devices, and executing instructions received from the plurality of input means206. In some embodiments, the application server202is further configured to generate alerts for the facility control center160and/or the facility mobile device170, generate location information of the detection and control system200, and execute instructions received from the facility control center160, the facility mobile device170, and/or other detection and control system communicating with the detection and control system200. In some embodiments, the communication interface203includes one or more transceivers, transmitters, and/or receivers that communicate via the antenna unit208. The communication interface203is configured to detect transmissions by the contraband device130. Detection of the contraband device130transmissions includes reception of a transmission signal from an unauthorized communication via the antenna unit208. For example, to detect an unauthorized communication, a receiver of the communication interface203may cycle through different frequencies bands and/or radio access technologies. In some embodiments, the communication interface203is further configured to output an RF signal during disruption operations. For example, a transmitter of the communication interface203can be configured to transmit an interference signal based on the received unauthorized communication. In some embodiments, the communication interface203is further configured to communicate with another detection and control system120, the detachable detection and control unit180, the facility control center160, and the facility mobile device170to provide or receive information and/or instructions. In some embodiments, the antenna unit208includes one or more antennas. The antenna unit208can include a distributed antenna system (DAS), in which a number of antenna elements are spaced apart from each other. The usage of a DAS can increase the detection accuracy and reliability by detecting the same area with multiple units that are spaced apart. The antenna unit208can also include one or more directional antennas which radiate or receive greater power in specific directions allowing for increased performance and reduced interference from unwanted sources. The usage of directional antennas can direct the detection and disruption to the target area (e.g. the correctional facility140) without detecting or interfering unwanted areas (e.g. public areas). In some embodiments, the power unit204provides power to the detection and control system200for its operations. In one embodiment, the power unit204is an A/C power adapter that directly connects to A/C power outlets outside the correctional facility140. In another embodiment, the power unit204includes a battery that can be charged. In another embodiment, the power unit204includes a power generator that generates power from a number of sources such as, but not limited to, propane, diesel, gas, and solar energy. In yet another embodiment, the power unit204is a wireless charging adapter that receives power remotely from a charging base station. In some embodiments, the plurality of input means include different input interfaces for the detection and control system200including, but not limited to, a keyboard, a touch screen, a microphone, and a camera. In some embodiments, the administrator of the detection and control system200can input information and/or instructions to the detection and control system200to complete specific tasks. In some embodiments, the plurality of output means include different output interfaces for the detection and control system200including, but not limited to, a display for video, photo, and text output, and a loudspeaker for sound output. In some embodiments, the plurality of sensors207include a biometric sensor and a position and motion sensor. The biometric sensor can be a fingerprint sensor that validates the identity of the user before granting the user an access to the detection and control system110. In one embodiment, the biometric sensor communicates with the application server202and the memory201to verify the identity of the user. The biometric sensor obtains the biometric information of a requesting user, and sends the data to the application server202. The application server202receives the biometric data from the biometric sensor207, and compare the data from the biometric information database of all the authorized users stored in memory201. If the biometric data from the requesting user matches one of the authorized users' biometric data, the application server grants access to the requesting user. In some embodiments, the position and motion sensor includes devices such as, but not limited to, Global Positioning System (GPS) devices, indoor positioning systems (IPS) devices, accelerometers, and/or gyroscopes to determine position and motion. The position and motion data obtained by the position and motion sensor207for the detection and control system is sent to the application server202as part of the detection information for a detection event. The position and motion data is further used by the application server during the positioning process (e.g. triangulation) for the current location of the contraband device130. FIG.3illustrates a block diagram of an exemplary detection and control system300, according to some embodiments of the present disclosure. The detection and control system300is another exemplary embodiment of the detection and control system110and the detection and control system120inFIG.1. The detection and control system includes a detection and control unit310and a mobility unit320. In some embodiments, the detection and control unit310further includes a memory311, an application server312, a communication interface313, a power unit314, a plurality of input means315, a plurality of output means316, a plurality of sensors317, and an antenna unit318. In some embodiments, the memory311stores the information and instructions necessary for the operations of the detection and control system300. The information stored in memory311includes, but is not limited to, the detection event information for each detection event, the information extracted from the contraband devices in each detection event, the transmitted data intercepted by the communication interface313from the detected contraband devices, the reports generated by the detection and control system300for the detection of the contraband devices in a given period of time, the instructions received for the application server312, the instructions generated by the application server312, the data to be transmitted and the data received by the communication interface313, the data received by the plurality of input means315, and the data to be output by the plurality of output means316. In some embodiments, the application server312is the main processing unit for the detection and control system300. The application server312is configured to execute a variety of tasks, such as, but not limited to, instructing the communication interface313to detect the contraband devices, generating detection event information whenever a detection event occurs (e.g. a contraband device is detected), instructing the communication interface to intercept transmitted data from the detected contraband device (e.g. contraband device130), analyzing the transmitted data intercepted from the detected contraband device to extract the hardware information, data usage information, and location information of the detected contraband devices, recording the intercepted data from the detected contraband device in the memory311, recording the detection event information and the information extracted from the detected contraband devices in the memory311, performing positioning actions using positioning techniques to locate the contraband devices, generating instructions to perform disruption actions for the detected contraband devices, analyzing all the detection information (e.g. detection event information, hardware information, location information, data usage information, etc.) stored in the memory311to generate a report of the detection of the contraband devices, and executing instructions received from the plurality of input means206. In some embodiments, the application server312is further configured to generate alerts for the facility control center160and/or the facility mobile device170, generate location information of the detection and control system300, and execute instructions received from the facility control center160, the facility mobile device170, and/or other detection and control system communicating with the detection and control system300. In some embodiments, the communication interface313includes one or more transceivers, transmitters, and/or receivers that communicate via the antenna unit318. The communication interface313is configured to detect transmissions by the contraband device130. Detection of the contraband device130transmissions includes reception of a transmission signal of an unauthorized communication via the antenna unit318. For example, to detect an unauthorized communication, a receiver of the communication interface313may cycle through different frequencies bands and/or radio access technologies. The communication interface313is further configured to output an RF signal during disruption operations. For example, a transmitter of the communication interface313can be configured to transmit an interference signal based on the received unauthorized communication. In some embodiments, the communication interface313is further configured to communicate with another detection and control system120, the detachable detection and control unit180, the facility control center160, and the facility mobile device170to provide or receive information and/or instructions. In some embodiments, the antenna unit318includes one or more antennas. In one embodiment, the antenna unit318is a distributed antenna system (DAS), in which a number of antenna elements are spaced apart from each other. The usage of a DAS can increase the detection accuracy and reliability by detecting the same area with multiple units that are spaced apart. In another embodiment, the antenna unit318can be one or more directional antennas which radiate or receive greater power in specific directions allowing for increased performance and reduced interference from unwanted sources. The usage of directional antennas can direct the detection and disruption to the target area (e.g. the correctional facility140) without detecting or interfering unwanted areas (e.g. public areas). In some embodiments, a part or all of the antenna unit318can be located on the mobility unit320. In some embodiments, the power unit314provides power to the detection and control system300for its operations. In one embodiment, the power unit314is an A/C power adapter that directly connects to A/C power outlets outside the correctional facility140. In another embodiment, the power unit314includes a battery that can be charged. In another embodiment, the power unit314includes a power generator that generates power from a number of sources such as, but not limited to, propane, diesel, gas, and solar energy. In yet another embodiment, the power unit314is a wireless charging adapter that receives power remotely from a charging base station. In a further embodiment, the power unit314receives the power from the mobility unit320. In a further embodiment, the mobility unit320directly provides power for the operation of the detection and control system300, and the power unit314is not necessary. In some embodiments, the plurality of input means include different input interfaces for the detection and control system300including, but not limited to, a keyboard, a touch screen, a microphone, and a camera. In some embodiments, the administrator of the detection and control system300can input information and/or instructions to the detection and control system300to complete specific tasks. In some embodiments, the plurality of output means include different output interfaces for the detection and control system300including, but not limited to, a display for video, photo, and text output, and a loudspeaker for sound output. In some embodiments, the plurality of sensors317include a biometric sensor and a position and motion sensor. The biometric sensor can be a fingerprint sensor that validates the identity of the user before granting the user an access to the detection and control system110. In one embodiment, the biometric sensor communicates with the application server312and the memory311to verify the identity of the user. The biometric sensor obtains the biometric information of a requesting user, and sends the data to the application server312. The application server312receives the biometric data from the biometric sensor317, and compare the data from the biometric information database of all the authorized users stored in memory311. If the biometric data from the requesting user matches one of the authorized users' biometric data, the application server grants access to the requesting user. In some embodiments, the position and motion sensor includes devices such as, but not limited to, Global Positioning System (GPS) devices, indoor positioning systems (IPS) devices, accelerometers, and/or gyroscopes to determine position and motion. The position and motion data obtained by the position and motion sensor317for the detection and control system is sent to the application server312as part of the detection information for a detection event. The position and motion data is further used by the application server during the positioning process (e.g. triangulation) for the current location of the contraband device130. In some embodiments, the mobility unit320is a manned vehicle, an unmanned vehicle, or a drone or unmanned aerial vehicles (UAVs). In some embodiments, the detection and control unit310is mounted on the mobility unit320. In some embodiments, the control unit310is detachable from the mobility unit320. In some other embodiments, a part of the detection and control unit310can be mounted on the mobility unit320. In some embodiments, the mobility unit320provide power to the detection and control unit310through wired electrical connection or wireless charging technology. In some embodiments, the mobility unit320is a self-driving vehicle with its own processing unit, input/output means, communication interface, sensors, and memory unit. The mobility unit320can be configured to communicate with the detection and control unit310and transmit/receive information including, but not limited to, location of the mobility unit320and/or the detection and control unit310, detection information of all the detection events, target location for detection and disruption, instructions for the mobility unit320to move to the target location, and instructions for the operations of the detection and control unit310. In some embodiments, the mobility unit320works with the detection and control unit310in accordance to detect contraband devices, locate contraband devices from conducting detection at different locations, move to the detected contraband devices, and disrupt the operation of the detected contraband devices. In some embodiments, the operation of the detection and control system300is fully automated. FIG.4illustrates a block diagram of an exemplary application server400, according to some embodiments of the present disclosure. The application server400is an exemplary embodiment of the application server202inFIG.2and the application server312inFIG.3. Application server400consists of any number of servers, and functions as the primary logic processing center in the detection and control system200and the detection and control system300. Application server400is configured to execute a variety of tasks, such as, but not limited to, initiating and coordinating the detection of the contraband devices, analyzing the data received from the detected contraband devices to obtain the information of the detected contraband devices, recording information into and fetching information from the memory of the detection and control system, performing positioning actions using positioning techniques to locate the contraband devices, generating instructions to perform disruption actions for the detected contraband devices, analyzing the detection information stored in the memory of the detection and control system, generating a report of the detection of the contraband devices, and executing instructions received from different sources. In some embodiments, the application server400is further configured to generate alerts for the facility control center160and/or the facility mobile device170, generate location information of the detection and control system, and execute instructions received from the facility control center160, the facility mobile device170, and/or other detection and control system communicating with the detection and control system. Application server400includes one or more central processing units (CPU)410connected via a bus401to several other components. One of such components can be an internal data storage420. This data storage420is non-volatile storage, such as one or more magnetic hard disk drives (HDDs) and/or one or more solid state drives (SSDs). Data storage420is used to store a variety of important files, documents, or other digital information, such as operating system files, application files, and/or temporary recording space. Application server400also includes system memory430. System memory430is preferably faster and more efficient than Data storage420, and is configured as random access memory (RAM) in an embodiment. System memory430contains the runtime environment of application server400, storing temporary data for any of operating system432, java virtual machine434, java application server436, and detection and monitoring control logic438. In some embodiments, referring toFIG.4, the application server400can have its own input and output methods. For example, the input method can be a keyboard and/or mouse440, and the output method can be a monitor442. FIG.5illustrates a block diagram of an exemplary detachable detection and control unit500, according to some embodiments of the present disclosure. The detachable detection and control unit500is an exemplary embodiment of the detachable detection and control unit180inFIG.1. In some embodiments, the detachable detection and control unit500is part of the detection and control system110and is detachable from the casing of the detection and control system. The detachable detection and control unit500is configured to communicate with the detection and control system110wirelessly using technologies including, but not limited to, Bluetooth, WIFI, and radio frequency communication technologies. The detachable detection and control unit500is further configured to detect the transmission of signals from the contraband devices (e.g. contraband device130). The detachable detection and control unit500is able to detect signals using technologies such as, but not limited to, GSM, 2G-5G technologies, WCDMA, CDMA, TDMA, UMTS, WIMAX, WIFI, IBEACON, Bluetooth, LTE, 700 MHz to 2200 MHz or other frequency band communication technologies. The detachable detection and control unit500is further configured to perform disruption actions to the detected contraband devices upon receiving instructions from the application server400, according to some embodiments. In some embodiments, the detachable detection and control unit500includes a communication interface502, a plurality of sensors503, and an antenna unit506. In some embodiments, the detachable detection and control unit500further includes a memory501and a power unit504. In some embodiments, the detachable detection and control unit500further includes a mobility unit505. The communication interface502includes one or more transceivers, transmitters, and/or receivers that communicate via the antenna unit506. The communication interface502is configured to detect transmissions by the contraband device130. Detection of the contraband device130transmissions includes reception of a transmission signal of an unauthorized communication via the antenna unit506. For example, to detect an unauthorized communication, a receiver of the communication interface502may cycle through different frequencies bands and/or radio access technologies. In some embodiments, the communication interface502is further configured to output an RF signal during disruption operations. For example, a transmitter of the communication interface502can be configured to transmit an interference signal based on the received unauthorized communication. The communication interface502is further configured to communicate with the detection and control system110to transmit information and/or instructions. In some embodiments, the antenna unit506includes one or more antennas. In one embodiment, the antenna unit506is a distributed antenna system (DAS), in which a number of antenna elements are spaced apart from each other. The usage of a DAS can increase the detection accuracy and reliability by detecting the same area with multiple units that are spaced apart. In another embodiment, the antenna unit506includes one or more directional antennas which radiate or receive greater power in specific directions allowing for increased performance and reduced interference from unwanted sources. The usage of directional antennas can direct the detection and disruption to the target area (e.g. the correctional facility140) without detecting or interfering unwanted areas (e.g. public areas). In some embodiments, the plurality of sensors503include a position and motion sensor. The position and motion sensor includes devices such as, but not limited to, Global Positioning System (GPS) devices, indoor positioning systems (IPS) devices, accelerometers, and/or gyroscopes to determine position and motion. The position and motion data obtained by the position and motion sensor503for the detachable detection and control unit500is sent to the application server400as part of the detection information for a detection event. The position and motion data is further used by the application server400during the positioning process (e.g. triangulation) for the current location of the detected contraband device130. In some embodiments, the power unit504provides power to the detachable detection and control unit500for its operations. In one embodiment, the power unit504is an A/C power adapter that directly connects to A/C power outlets outside the correctional facility140. In another embodiment, the power unit504includes a battery that can be charged. In another embodiment, the power unit504is a wireless charging adapter that receives power remotely from a charging base station. In a further embodiment, the power unit504receives the power from the mobility unit505. In a further embodiment, the mobility unit505directly provides power for the operation of the detachable detection and control unit500, and the power unit504is not necessary. In some embodiments, the mobility unit505is a self-driving vehicle or an unmanned aerial vehicle with its own processing unit, input/output means, communication interface, sensors, and memory unit. The mobility unit505can be configured to communicate with the detection and control unit310and transmit information including, but not limited to, location of the mobility unit505and/or the detachable detection and control unit500, detection information of all the detection events, target location for detection and disruption, instructions for the mobility unit505to move to the target location, and instructions for the operations of the detachable detection and control unit500. In some embodiments, the mobility unit505cooperates with the detection and control unit310or the detection and control system200to detect contraband devices, locate contraband devices from conducting detection at different locations, move to the detected contraband devices, and disrupt the operation of the detected contraband devices. FIG.6illustrates a flow chart for an exemplary method600to operate the detection and control system110, according to some embodiments. At step602, the detection and control system110is placed at a first location outside the correctional facility140. Referring toFIG.1, in some embodiments, the first location (e.g. Location A) is between the correctional facility140and a nearby communication center150. Such a location set up is favorable in detecting the signal transmission between the contraband device (e.g. contraband device130) and the correctional facility, because the detection and control system110is located close to the signal transmission pathway between the contraband device130and the communication center150. At step604, the detection and control system110detects communication signals from the contraband devices in the correctional facility. In some embodiments, the detection is done by the communication interface and the antenna unit of the detection and control system. In some embodiments, the antenna unit is a DAS system to improve the detection accuracy and reliability. In some other embodiments, the antenna unit includes one or more directional antennas directed to the correctional facility140to avoid detecting unwanted areas. When searching for a contraband device, the detection and control system110enables a receiver to receive transmissions from contraband devices. The detection and control system110may focus on specific types of transmissions such as GSM, CDMA, LTE, or other cellular transmissions and/or may rotate through a variety of frequencies and transmission types including, for example, cellular transmissions and WIFI signals of a specific type. At step606, the detection and control system110conducts the detection until a contraband device is detected, or when a pre-determined time period for detection ends. If a contraband device is not detected within the pre-determined time period, the system operation jumps to step618to determine if the operation needs to continue. If a contraband device is detected, the system proceeds to step608. At step608, the detection and control system110perform actions to extract information of the detected contraband device (e.g. contraband device130). The information of the contraband device130to be extracted includes, but is not limited to, hardware information, data usage information, and location information of the contraband device130when the contraband device is detected. In some embodiments, the hardware information further includes a hardware identification number of the contraband device130(e.g. an international mobile subscriber identity number (IMSI), an electronic serial number (ESN), a mobile device ID, etc.), a phone number of the contraband device, and a phone number that is communicating with the contraband device. In some embodiments, the data usage information includes the duration of data transmission conducted by the contraband device and the volume of the data transmitted by the contraband devices. In some embodiments, the detection and control system110utilizes one or more positioning techniques (e.g. lateration and angulation) to obtain the location of the detected contraband devices. In some embodiments, at step608, the detection and control system110further intercepts the communication transmitted from and to the detected contraband device. In some embodiments, the detection and control system110sends an alert to the facility control center160to inform the correctional facility140of the detection event. In some embodiments, the detection and control system110further generates detection event information for the detected contraband device. Such detection event information includes, but is not limited to, the date/time when the contraband device was detected, the duration of the contraband device being detected, and the location of the detection and control system110when the contraband device was detected. At step610, the detection and control system110records the extracted information for the detected contraband device at step608to a memory. In addition to the information extracted at step608, the detection and control system110can also record information such as, but not limited to, the date/time when the contraband device was detected, the duration of the contraband device being detected, and the location of the detection and control system110when the contraband device was detected. At step612, the detection and control system110generates a report for all the detection events and all the detected contraband device during a given period of time. In some embodiments, the report contains information such as, but not limited to the total number of contraband device detection events, the total number of detected contraband devices, the total time of contraband device usage, the total volume of the data transmitted by the contraband devices, the location and distribution of the contraband devices, and the time and frequency of the data transmission made by the contraband devices. In some embodiments, based on the extracted data from all the detected contraband devices and the detection event information for all the detected devices, the detection and control system110generates a degree of severity in the report to give guidance to the facility administrators on the severity of the contraband device usage in the correctional facility. At step614, the detection and control system110listens for input or instruction to activate control mode and perform disruption to the contraband devices. If the disruption is needed, the detection and control system110jumps to step616. If no disruption is needed, the detection and control system110jumps to step618. In one embodiment, the input and/or instruction comes from the detection and control system110administrator via one of the input method. In one embodiment, the input and/or instruction comes from the facility administrator via the facility control center160, or from the facility officer via the facility mobility device170. In some embodiments, at step614, the detection and control system110have pre-determined instructions to automatically activate control mode and perform disruption to the contraband devices. In these embodiment, the detection and control system110can automatically activate control mode when the total number of detection events exceeds a pre-determined number, or the total number of detected contraband devices exceeds a pre-determined number, or the total data transmitted by the contraband devices exceeds a pre-determined amount. At step618, the detection and control system110listens for input or instruction on whether to continue the detection at the current location. If continued detection is needed, the detection and control system110jumps back to step604to continue the detection. If continued detection at current location is not needed, the detection and control system110jumps to step620. In one embodiment, the input and/or instruction comes from the detection and control system110administrator via one of the input method. In one embodiment, the input and/or instruction comes from the facility administrator via the facility control center160, or from the facility officer via the facility mobility device170. In some embodiments, at step618, the detection and control system110have pre-determined instructions to automatically determine whether continued detection is needed at the current step. In these embodiment, the detection and control system110can automatically continue the detection when the total number of detection events exceeds a pre-determined number, or the total number of detected contraband devices exceeds a pre-determined number, or the total data transmitted by the contraband devices exceeds a pre-determined amount. In these embodiments, the detection and control system110can still listen for input and/or instructions and alter its operations based on the input and/or instructions. At step620, the detection and control system110listens for input or instructions on whether to relocate to another location. If relocation is needed, the detection and control system110jumps to step622. If relocation is not needed, the detection and control system110jumps to step624. In one embodiment, the input and/or instruction comes from the detection and control system110administrator via one of the input method. In one embodiment, the input and/or instruction comes from the facility administrator via the facility control center160, or from the facility officer via the facility mobility device170. In some embodiments, at step620, the detection and control system110have pre-determined instructions to automatically determine whether a relocation is needed. At step622, the detection and control system110is moved to the next location for detection and disruption. In some embodiments, the detection and control system110is carried to the next location by human, manned vehicles, unmanned vehicles, and/or unmanned aerial vehicles. After relocation, the detection and control system110can jump back to step604for more detection and/or disruption. At step624, the detection and control system110is in a standby or power off state, waiting for input and/or instructions to wake up or power on for operations. In one embodiment, the input and/or instruction comes from the detection and control system110administrator via one of the input method. In one embodiment, the input and/or instruction comes from the facility administrator via the facility control center160, or from the facility officer via the facility mobility device170. In some embodiments, at step624, the detection and control system110have pre-determined instructions to automatically wake up or power on. In one embodiment, the detection and control system110automatically wakes up or powers on when a pre-determined standby or power off time period ends. FIG.7illustrates a flow chart for an exemplary method700to operate the detection and control system110for detecting and locating contraband devices, according to some embodiments. At step702, the detection and control system110is placed at a first location outside the correctional facility140. Referring toFIG.1, in some embodiments, the first location (e.g. Location A) is between the correctional facility140and a nearby communication center150. Such a location set up is favorable in detecting the signal transmission between the contraband device (e.g. contraband device130) and the correctional facility, because the detection and control system110is located close to the signal transmission pathway between the contraband device130and the communication center150. At step704, the detection and control system110detects communication signals from the contraband devices in the correctional facility. In some embodiments, the detection is done by the communication interface and the antenna unit of the detection and control system. In some embodiments, the antenna unit is a DAS system to improve the detection accuracy and reliability. In some other embodiments, the antenna unit includes one or more directional antennas directed to the correctional facility140to avoid detecting unwanted areas. When searching for a contraband device, the detection and control system110enables a receiver to receive transmissions. The detection and control system110may focus on specific types of transmissions such as GSM, CDMA, LTE, or other cellular transmissions and/or may rotate through a variety of frequencies and transmission types including, for example, cellular transmissions and WIFI signals of a specific type. In some embodiments, at step704, a detachable detection and control unit180is detached from the detection and control system110and placed to another location (e.g. location C) that is outside the correctional facility and remote to location A. This detachable detection and control unit180can detect communication signals from the contraband devices in the correctional facility. In some embodiments, the detection is done by the communication interface and the antenna unit of the detachable detection and control unit180. In some embodiments, the detachable detection and control unit180communicates with the detection and control system110and transmits information and/or instructions. At step706, the detection and control system110conducts the detection until a contraband device is detected, or when a pre-determined time period for detection ends. If a contraband device is not detected within the pre-determined time period, the system operation jumps to step724to determine if the operation needs to continue. If a contraband device is detected, the system proceeds to step708. At step708, referring toFIG.1, the detection and control system110finds out whether another detection and control system (e.g. detection and control system120) is in operation for the correctional facility140. If another detection and control system is in operation, the detection and control system110jumps to step710. If another detection and control system is not available or not in operation, the detection and control system110jumps to step712. In some embodiments, the additional detection and control system120is located at a location B outside the correctional facility140but remote to location A where the detection and control system110is located. At step710, the detection and control system110communicates with the additional detection and control system120to transmit information and/or instructions. In some embodiments, such information includes, but is not limited to, the detection information for all detection events, the information obtained from all the detected contraband devices, the location and motion information for the detection and control system, and the reports generated during the detection period. In some embodiments, there are more detection and control systems than the detection and control system110and120. The sharing of detection information between multiple detection and control systems can be used for a variety of applications including, but not limited to, confirming detection events when more than one detection and control systems detect the same contraband device, locating the contraband device when location information for the contraband device are obtained from more than one detection and control system and used for lateration and/or angulation, and enhancing detection coverage when different detection and control systems are located in different locations around the correction facility. At step712, the detection and control system110estimates the location of the detected contraband devices based on one or more positioning techniques, such as, but not limited to, lateration and angulation. Depending on different factors such as, but not limited to, the detection ability of the detection and control system110, the relative distance between the contraband device and the detection and control system110, and the positioning technique used to for locating the contraband device, the estimated location of the contraband device can have a certain degree of accuracy. Due to the different degrees of accuracy, the estimated location of the contraband device can be a big region that can be narrowed down. At step720, the detection and control system110determines whether relocation is needed. If a relocation is needed, the detection and control system110jumps to step714. If a relocation is not needed, the detection and control system110jumps to step724. In some embodiments, whether relocation is needed is determined by input and/or instructions received by the detection and control system110. In some embodiments, the input and/or instruction comes from the detection and control system110administrator via one of the input method. In one embodiment, the input and/or instruction comes from the facility administrator via the facility control center160, or from the facility officer via the facility mobility device170. In some embodiments, the detection and control system110have pre-determined instructions to automatically determine whether a relocation is needed. At step714, the detection and control system110determines the next desirable detection location or locations. In some embodiments, the determination of the next desirable detection location or locations is conducted automatically by the detection and control system110based on the detection information of the contraband devices. The next desirable detection location or locations can be determined based on a variety of reasons such as, but not limited to, the need to improve the estimation accuracy of the contraband device location, the need to improve the coverage of detection within the correctional facility, and the need to focus the detection on a certain area of the correctional facility. In some embodiments, the next desirable locations can be input manually from the detection and control system110administrator via one of the input method. In one embodiment, the next desirable locations can be input manually from the facility administrator via the facility control center160, or from the facility officer via the facility mobility device170. At step716, the detection and control system110determines if one or more detachable detection and control unit180is available or in operation. If there are one or more detachable detection and control unit180available or in operation, the detection and control system110jumps to step722. If there is no detachable detection and control unit180available or in operation, the detection and control system110jumps to step718. At step722, the detachable detection and control unit180is moved to the next desirable locations for the detachable detection and control unit180determined at step714. In some embodiments, the detachable detection and control unit180is moved by human, manned vehicles, unmanned vehicles, and/or UAV. In some embodiments, the detachable detection and control unit180is moved by its own mobility unit. In some embodiments, the mobility unit of the detachable detection and control unit180has an autonomous mobility unit (e.g. an autonomous car, a drone or an UAV) that receives instructions directly from the detection and control system110and move to the next desirable location. Advantages of having a drone or an UAV to move the detachable detection and control unit180include, but are not limited to, the degree of freedom in the whole space and the speed of movement for fast response. At step718, the detection and control system110is moved to the next desirable location. In some embodiments, the detection and control system110is moved by human, manned vehicles, unmanned vehicles, and/or UAVs. In some embodiments, the detection and control system110is moved by its own mobility unit. In some embodiments, the detection and control system110has an autonomous mobility unit (e.g. an autonomous car, a drone or an UAV) that receives instructions directly from the detection and control system110and move the detection and control system110to the next desirable location. The advantages of having an autonomous moving vehicle as the mobility unit includes, but not limited to, the speed of movement for fast response and the fully automatic process without requiring human intervention. At step724, the detection and control system110determines whether to continue the operation. If the operation needs to continue, the detection and control system110jumps back to step704to continue detecting the contraband devices. If the operation does not need to continue, the detection and control system jumps to step726. In some embodiments, whether the operation needs to continue is determined by input and/or instructions received by the detection and control system110. In some embodiments, the input and/or instruction comes from the detection and control system110administrator via one of the input method. In one embodiment, the input and/or instruction comes from the facility administrator via the facility control center160, or from the facility officer via the facility mobility device170. In some embodiments, the detection and control system110have pre-determined instructions to automatically determine whether a continued operation is needed. It will be apparent to persons skilled in the relevant art(s) that various elements and features of the present disclosure, as described herein, can be implemented in hardware using analog and/or digital circuits, in software, through the execution of computer instructions by one or more general purpose or special-purpose processors, or as a combination of hardware and software. The following description of a general purpose computer system is provided for the sake of completeness. Embodiments of the present disclosure can be implemented in hardware, or as a combination of software and hardware. Consequently, embodiments of the disclosure are implemented in the environment of a computer system or other processing system. For example, the detection and control system200, the detection and control system300, the application server400, and the methods described inFIG.6andFIG.7can be implemented in the environment of one or more computer systems or other processing systems. An example of such a computer system800is shown inFIG.8. One or more of the modules depicted in the previous figures can be at least partially implemented on one or more distinct computer systems800. Computer system800includes one or more processors, such as processor804. Processor804can be a special purpose or a general purpose digital signal processor. Processor804is connected to a communication infrastructure802(for example, a bus or network). Various software implementations are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement the disclosure using other computer systems and/or computer architectures. Computer system800also includes a main memory806, preferably random access memory (RAM), and may also include a secondary memory808. Secondary memory808may include, for example, a hard disk drive810and/or a removable storage drive812, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, or the like. Removable storage drive812reads from and/or writes to a removable storage unit816in a well-known manner. Removable storage unit816represents a floppy disk, magnetic tape, optical disk, or the like, which is read by and written to by removable storage drive812. As will be appreciated by persons skilled in the relevant art(s), removable storage unit816includes a computer usable storage medium having stored therein computer software and/or data. In alternative implementations, secondary memory808may include other similar means for allowing computer programs or other instructions to be loaded into computer system800. Such means may include, for example, a removable storage unit818and an interface814. Examples of such means may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, a thumb drive and USB port, and other removable storage units818and interfaces814which allow software and data to be transferred from removable storage unit818to computer system800. Computer system800may also include a communications interface820. Communications interface820allows software and data to be transferred between computer system800and external devices. Examples of communications interface820may include a modem, a network interface (such as an Ethernet card), a communications port, a PCMCIA slot and card, etc. Software and data transferred via communications interface820are in the form of signals which may be electronic, electromagnetic, optical, or other signals capable of being received by communications interface820. These signals are provided to communications interface820via a communications path822. Communications path822carries signals and may be implemented using wire or cable, fiber optics, a phone line, a cellular phone link, an RF link and other communications channels. As used herein, the terms “computer program medium” and “computer readable medium” are used to generally refer to tangible storage media such as removable storage units816and818or a hard disk installed in hard disk drive810. These computer program products are means for providing software to computer system800. Computer programs (also called computer control logic) are stored in main memory806and/or secondary memory808. Computer programs may also be received via communications interface820. Such computer programs, when executed, enable the computer system800to implement the present disclosure as discussed herein. In particular, the computer programs, when executed, enable processor804to implement the processes of the present disclosure, such as any of the methods described herein. Accordingly, such computer programs represent controllers of the computer system800. Where the disclosure is implemented using software, the software may be stored in a computer program product and loaded into computer system800using removable storage drive812, interface814, or communications interface820. In another embodiment, features of the disclosure are implemented primarily in hardware using, for example, hardware components such as application-specific integrated circuits (ASICs) and gate arrays. Implementation of a hardware state machine so as to perform the functions described herein will also be apparent to persons skilled in the relevant art(s). It is to be appreciated that the Detailed Description section, and not the Abstract section, is intended to be used to interpret the claims. The Abstract section may set forth one or more, but not all exemplary embodiments, and thus, is not intended to limit the disclosure and the appended claims in any way. The disclosure has been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries may be defined so long as the specified functions and relationships thereof are appropriately performed. It will be apparent to those skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus, the disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. | 77,794 |
11943697 | DETAILED DESCRIPTION The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multicarrier frequency division multiple access (MC-FDMA) system. CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is a part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. LTE-advanced (LTE-A) is an evolved version of 3GPP LTE. For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems. For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced. In the present disclosure, “A or B” may mean “only A”, “only B”, or “both A and B”. In other words, “A or B” in the present disclosure may be interpreted as “A and/or B”. For example, “A, B or C” in the present disclosure may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. In the present disclosure, slash (/) or comma (,) may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B or C”. In the present disclosure, “at least one of A and B” may mean “only A”, “only B” or “both A and B”. In addition, the expression “at least one of A or B” or “at least one of A and/or B” in the present disclosure may be interpreted as same as “at least one of A and B”. In addition, in the present disclosure, “at least one of A, B and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. In addition, “at least one of A, B or C” or “at least one of A, B and/or C” may mean “at least one of A, B and C”. Also, parentheses used in the present disclosure may mean “for example”. In detail, when it is shown as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” in the present disclosure is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of “control information”. In addition, even when shown as “control information (i.e., PDCCH)”, “PDCCH” may be proposed as an example of “control information”. Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously. Throughout the disclosure, the terms ‘radio access network (RAN) node’, ‘base station’, ‘eNB’, ‘gNB’ and ‘cell’ may be used interchangeably. Further, a UE may be a kind of a wireless device, and throughout the disclosure, the terms ‘UE’ and ‘wireless device’ may be used interchangeably. Throughout the disclosure, the terms ‘cell quality’, ‘signal strength’, ‘signal quality’, ‘channel state’, ‘channel quality’, ‘channel state/reference signal received power (RSRP)’ and ‘reference signal received quality (RSRQ)’ may be used interchangeably. Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and/or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and/or connection (e.g., 5G) between devices. Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and/or descriptions may refer to the same and/or corresponding hardware blocks, software blocks, and/or functional blocks unless otherwise indicated. FIG.1shows an example of a communication system to which implementations of the present disclosure is applied. The 5G usage scenarios shown inFIG.1are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown inFIG.1. Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC). Partial use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI). 5G supports such various use cases using a flexible and reliable method. eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality. Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application program using data connection provided by a communication system. Main causes for increased traffic volume are due to an increase in the size of content and an increase in the number of applications requiring high data transmission rate. A streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet. These many application programs require connectivity of an always turned-on state in order to push real-time information and alarm for users. Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment. The cloud storage is a special use case which accelerates growth of uplink data transmission rate. 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience. Entertainment, for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane. Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume. In addition, one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach 204 hundred million up to the year of 2020. An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G. URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable/available low-latency link such as a self-driving vehicle. A level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone. 5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. A specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency. Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds. Another use case of an automotive field is an AR dashboard. The AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver. In the future, a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver may drive more safely drive, thereby lowering the danger of an accident. The next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify. Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being. A smart city and a smart home/building mentioned as a smart society will be embedded in a high-density wireless sensor network. A distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring. Consumption and distribution of energy including heat or gas is distributed at a higher level so that automated control of the distribution sensor network is demanded. The smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviors of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation. The smart grid may also be regarded as another sensor network having low latency. Mission critical application (e.g., e-health) is one of 5G use scenarios. A health part contains many application programs capable of enjoying benefit of mobile communication. A communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation. The wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure. Wireless and mobile communication gradually becomes important in the field of an industrial application. Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with reconstructible wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed. Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system. The use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability. Referring toFIG.1, the communication system1includes wireless devices100ato100f, base stations (BSs)200, and a network300. AlthoughFIG.1illustrates a 5G network as an example of the network of the communication system1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system. The BSs200and the network300may be implemented as wireless devices and a specific wireless device may operate as a BS/network node with respect to other wireless devices. The wireless devices100ato100frepresent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication/radio/5G devices. The wireless devices100ato100fmay include, without being limited to, a robot100a, vehicles100b-1and100b-2, an extended reality (XR) device100c, a hand-held device100d, a home appliance100e, an IoT device100f, and an artificial intelligence (AI) device/server400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR/VR/Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. In the present disclosure, the wireless devices100ato100fmay be called user equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather/environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field. The UAV may be, for example, an aircraft aviated by a wireless control signal without a human being onboard. The VR device may include, for example, a device for implementing an object or a background of the virtual world. The AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world. The MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world. The hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet. The public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user. The MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors. Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and/or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and/or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate personal area networks (PANs) associated with small/low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names. The medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment. For example, the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device may be a device used for the purpose of adjusting pregnancy. For example, the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure. The security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety. For example, the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box. The FinTech device may be, for example, a device capable of providing a financial service such as mobile payment. For example, the FinTech device may include a payment device or a point of sales (POS) system. The weather/environment device may include, for example, a device for monitoring or predicting a weather/environment. The wireless devices100ato100fmay be connected to the network300via the BSs200. An AI technology may be applied to the wireless devices100ato100fand the wireless devices100ato100fmay be connected to the AI server400via the network300. The network300may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices100ato100fmay communicate with each other through the BSs200/network300, the wireless devices100ato100fmay perform direct communication (e.g., sidelink communication) with each other without passing through the BSs200/network300. For example, the vehicles100b-1and100b-2may perform direct communication (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices100ato100f. Wireless communication/connections150a,150band150cmay be established between the wireless devices100ato100fand/or between wireless device100ato100fand BS200and/or between BSs200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication150a, sidelink communication (or device-to-device (D2D) communication)150b, inter-base station communication150c(e.g., relay, integrated access and backhaul (JAB)), etc. The wireless devices100ato100fand the BSs200/the wireless devices100ato100fmay transmit/receive radio signals to/from each other through the wireless communication/connections150a,150band150c. For example, the wireless communication/connections150a,150band150cmay transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/de-mapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure. FIG.2shows an example of wireless devices to which implementations of the present disclosure is applied. Referring toFIG.2, a first wireless device100and a second wireless device200may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR). InFIG.2, {the first wireless device100and the second wireless device200} may correspond to at least one of {the wireless device100ato100fand the BS200}, {the wireless device100ato100fand the wireless device100ato100f} and/or {the BS200and the BS200} ofFIG.1. The first wireless device100may include one or more processors102and one or more memories104and additionally further include one or more transceivers106and/or one or more antennas108. The processor(s)102may control the memory(s)104and/or the transceiver(s)106and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s)102may process information within the memory(s)104to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s)106. The processor(s)102may receive radio signals including second information/signals through the transceiver(s)106and then store information obtained by processing the second information/signals in the memory(s)104. The memory(s)104may be connected to the processor(s)102and may store a variety of information related to operations of the processor(s)102. For example, the memory(s)104may store software code including commands for performing a part or the entirety of processes controlled by the processor(s)102or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s)102and the memory(s)104may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)106may be connected to the processor(s)102and transmit and/or receive radio signals through one or more antennas108. Each of the transceiver(s)106may include a transmitter and/or a receiver. The transceiver(s)106may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the first wireless device100may represent a communication modem/circuit/chip. The second wireless device200may include one or more processors202and one or more memories204and additionally further include one or more transceivers206and/or one or more antennas208. The processor(s)202may control the memory(s)204and/or the transceiver(s)206and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s)202may process information within the memory(s)204to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s)206. The processor(s)202may receive radio signals including fourth information/signals through the transceiver(s)106and then store information obtained by processing the fourth information/signals in the memory(s)204. The memory(s)204may be connected to the processor(s)202and may store a variety of information related to operations of the processor(s)202. For example, the memory(s)204may store software code including commands for performing a part or the entirety of processes controlled by the processor(s)202or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s)202and the memory(s)204may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)206may be connected to the processor(s)202and transmit and/or receive radio signals through one or more antennas208. Each of the transceiver(s)206may include a transmitter and/or a receiver. The transceiver(s)206may be interchangeably used with RF unit(s). In the present disclosure, the second wireless device200may represent a communication modem/circuit/chip. Hereinafter, hardware elements of the wireless devices100and200will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors102and202. For example, the one or more processors102and202may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). The one or more processors102and202may generate one or more protocol data units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors102and202may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors102and202may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers106and206. The one or more processors102and202may receive the signals (e.g., baseband signals) from the one or more transceivers106and206and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors102and202may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors102and202may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors102and202. descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors102and202or stored in the one or more memories104and204so as to be driven by the one or more processors102and202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands. The one or more memories104and204may be connected to the one or more processors102and202and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories104and204may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories104and204may be located at the interior and/or exterior of the one or more processors102and202. The one or more memories104and204may be connected to the one or more processors102and202through various technologies such as wired or wireless connection. The one or more transceivers106and206may transmit user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers106and206may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers106and206may be connected to the one or more processors102and202and transmit and receive radio signals. For example, the one or more processors102and202may perform control so that the one or more transceivers106and206may transmit user data, control information, or radio signals to one or more other devices. The one or more processors102and202may perform control so that the one or more transceivers106and206may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers106and206may be connected to the one or more antennas108and208and the one or more transceivers106and206may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or more antennas108and208. In the present disclosure, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers106and206may convert received radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors102and202. The one or more transceivers106and206may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors102and202from the base band signals into the RF band signals. To this end, the one or more transceivers106and206may include (analog) oscillators and/or filters. For example, the transceivers106and206can up-convert OFDM baseband signals to a carrier frequency by their (analog) oscillators and/or filters under the control of the processors102and202and transmit the up-converted OFDM signals at the carrier frequency. The transceivers106and206may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the transceivers102and202. In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device100acts as the UE, and the second wireless device200acts as the BS. For example, the processor(s)102connected to, mounted on or launched in the first wireless device100may be configured to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s)106to perform the UE behavior according to an implementation of the present disclosure. The processor(s)202connected to, mounted on or launched in the second wireless device200may be configured to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s)206to perform the BS behavior according to an implementation of the present disclosure. In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB. FIG.3shows an example of a wireless device to which implementations of the present disclosure is applied. The wireless device may be implemented in various forms according to a use-case/service (refer toFIG.1). Referring toFIG.3, wireless devices100and200may correspond to the wireless devices100and200ofFIG.2and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices100and200may include a communication unit110, a control unit120, a memory unit130, and additional components140. The communication unit110may include a communication circuit112and transceiver(s)114. For example, the communication circuit112may include the one or more processors102and202ofFIG.2and/or the one or more memories104and204ofFIG.2. For example, the transceiver(s)114may include the one or more transceivers106and206ofFIG.2and/or the one or more antennas108and208ofFIG.2. The control unit120is electrically connected to the communication unit110, the memory130, and the additional components140and controls overall operation of each of the wireless devices100and200. For example, the control unit120may control an electric/mechanical operation of each of the wireless devices100and200based on programs/code/commands/information stored in the memory unit130. The control unit120may transmit the information stored in the memory unit130to the exterior (e.g., other communication devices) via the communication unit110through a wireless/wired interface or store, in the memory unit130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit110. The additional components140may be variously configured according to types of the wireless devices100and200. For example, the additional components140may include at least one of a power unit/battery, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit. The wireless devices100and200may be implemented in the form of, without being limited to, the robot (100aofFIG.1), the vehicles (100b-1and100b-2ofFIG.1), the XR device (100cofFIG.1), the hand-held device (100dofFIG.1), the home appliance (100eofFIG.1), the IoT device (100fofFIG.1), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400ofFIG.1), the BSs (200ofFIG.1), a network node, etc. The wireless devices100and200may be used in a mobile or fixed place according to a use-example/service. InFIG.3, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices100and200may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit110. For example, in each of the wireless devices100and200, the control unit120and the communication unit110may be connected by wire and the control unit120and first units (e.g.,130and140) may be wirelessly connected through the communication unit110. Each element, component, unit/portion, and/or module within the wireless devices100and200may further include one or more elements. For example, the control unit120may be configured by a set of one or more processors. As an example, the control unit120may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory130may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof. FIG.4shows another example of wireless devices to which implementations of the present disclosure is applied. Referring toFIG.4, wireless devices100and200may correspond to the wireless devices100and200ofFIG.2and may be configured by various elements, components, units/portions, and/or modules. The first wireless device100may include at least one transceiver, such as a transceiver106, and at least one processing chip, such as a processing chip101. The processing chip101may include at least one processor, such a processor102, and at least one memory, such as a memory104. The memory104may be operably connectable to the processor102. The memory104may store various types of information and/or instructions. The memory104may store a software code105which implements instructions that, when executed by the processor102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code105may implement instructions that, when executed by the processor102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code105may control the processor102to perform one or more protocols. For example, the software code105may control the processor102may perform one or more layers of the radio interface protocol. The second wireless device200may include at least one transceiver, such as a transceiver206, and at least one processing chip, such as a processing chip201. The processing chip201may include at least one processor, such a processor202, and at least one memory, such as a memory204. The memory204may be operably connectable to the processor202. The memory204may store various types of information and/or instructions. The memory204may store a software code205which implements instructions that, when executed by the processor202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code205may implement instructions that, when executed by the processor202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code205may control the processor202to perform one or more protocols. For example, the software code205may control the processor202may perform one or more layers of the radio interface protocol. FIG.5shows an example of UE to which implementations of the present disclosure is applied. Referring toFIG.5, a UE100may correspond to the first wireless device100ofFIG.2and/or the first wireless device100ofFIG.4. A UE100includes a processor102, a memory104, a transceiver106, one or more antennas108, a power management module110, a battery1112, a display114, a keypad116, a subscriber identification module (SIM) card118, a speaker120, and a microphone122. The processor102may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The processor102may be configured to control one or more other components of the UE100to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor102. The processor102may include ASIC, other chipset, logic circuit and/or data processing device. The processor102may be an application processor. The processor102may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor102may be found in SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or a corresponding next generation processor. The memory104is operatively coupled with the processor102and stores a variety of information to operate the processor102. The memory104may include ROM, RAM, flash memory, memory card, storage medium and/or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory104and executed by the processor102. The memory104can be implemented within the processor102or external to the processor102in which case those can be communicatively coupled to the processor102via various means as is known in the art. The transceiver106is operatively coupled with the processor102, and transmits and/or receives a radio signal. The transceiver106includes a transmitter and a receiver. The transceiver106may include baseband circuitry to process radio frequency signals. The transceiver106controls the one or more antennas108to transmit and/or receive a radio signal. The power management module110manages power for the processor102and/or the transceiver106. The battery112supplies power to the power management module110. The display114outputs results processed by the processor102. The keypad116receives inputs to be used by the processor102. The keypad16may be shown on the display114. The SIM card118is an integrated circuit that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices (such as mobile phones and computers). It is also possible to store contact information on many SIM cards. The speaker120outputs sound-related results processed by the processor102. The microphone122receives sound-related inputs to be used by the processor102. FIGS.6and7show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied. In particular,FIG.6illustrates an example of a radio interface user plane protocol stack between a UE and a BS andFIG.7illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring toFIG.6, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring toFIG.7, the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a non-access stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an access stratum (AS). In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network quality of service (QoS) flows. In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing/de-multiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use. Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, paging control channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing public warning service (PWS) broadcasts, common control channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and dedicated control channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated traffic channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH. The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM). The RLC configuration is per logical channel with no dependency on numerologies and/or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only). In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers. In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session. In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to/from NAS from/to UE. FIG.8shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied. The frame structure shown inFIG.8is purely exemplary and the number of subframes, the number of slots, and/or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols). Referring toFIG.8, downlink and uplink transmissions are organized into frames. Each frame has Tf=10 ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5 ms duration. Each half-frame consists of 5 subframes, where the duration Tsfper subframe is 1 ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing βf=2u*15 kHz. Table 1 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframeslotfor the normal CP, according to the subcarrier spacing βf=2u*15 kHz. TABLE 1uNsymbslotNslotfame,uNslotsubframe,u01410111420221440431480841416016 Table 2 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frame Nframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the extended CP, according to the subcarrier spacing βf=2u*15 kHz. TABLE 2uNsymbslotNslotfame,uNslotsubframe,u212404 A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid of Nsize,ugrid,x*NRBscsubcarriers and Nsubframe,usymbOFDM symbols is defined, starting at common resource block (CRB) Nstart,ugridindicated by higher-layer signaling (e.g., RRC signaling), where Nsize,ugrid,xis the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. NRBscis the number of subcarriers per RB. In the 3GPP based wireless communication system, NRBscis 12 generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth Nsize,ugridfor subcarrier spacing configuration u is given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is referred to as a resource element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with ‘point A’ which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from 0 to NsizeBWP,i−1, where i is the number of the bandwidth part. The relation between the physical resource block nPRBin the bandwidth part i and the common resource block nCRBis as follows: nPRB=nCRB+NsizeBWP,i, where NsizeBWP,iis the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth. The NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2. The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 3 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean “sub 6 GHz range”, FR2 may mean “above 6 GHz range,” and may be referred to as millimeter wave (mmW). TABLE 3FrequencyRangeCorrespondingSubcarrierdesignationfrequency rangeSpacingFR1450 MHz-6000 MHz15, 30, 60 kHzFR224250 MHz-52600 MHz60, 120, 240 kHz As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving). TABLE 4FrequencyRangeCorrespondingSubcarrierdesignationfrequency rangeSpacingFR1410 MHz-7125 MHz15, 30, 60 kHzFR224250 MHz-52600 MHz60, 120, 240 kHz In the present disclosure, the term “cell” may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A “cell” as a geographic area may be understood as coverage within which a node can provide service using a carrier and a “cell” as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The “cell” associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the “cell” of radio resources used by the node. Accordingly, the term “cell” may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times. In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the primary cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, secondary cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of special cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA/DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA/DC, the term “serving cells” is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG. FIG.9shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied. Referring toFIG.9, “RB” denotes a radio bearer, and “H” denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted/received using radio resources through the PHY layer to/from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block. In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels physical uplink shared channel (PUSCH) and physical random access channel (PRACH), respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to physical downlink shared channel (PDSCH), physical broadcast channel (PBCH) and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to physical uplink control channel (PUCCH), and downlink control information (DCI) is mapped to physical downlink control channel (PDCCH). A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment. Hereinafter, contents regarding a non-public network (NPN) are described. An NPN is a 5GS deployed for non-public use. Non-public networks are intended for the sole use of a private entity such as an enterprise, and may be deployed in a variety of configurations, utilising both virtual and physical elements. Specifically, they may be deployed as completely standalone networks, they may be hosted by a PLMN, or they may be offered as a slice of a PLMN. In any of these deployment options, it is expected that unauthorized UEs, those that are not associated with the enterprise, will not attempt to access the non-public network, which could result in resources being used to reject that UE and thereby not be available for the UEs of the enterprise. It is also expected that UEs of the enterprise will not attempt to access a network they are not authorized to access. For example, some enterprise UEs may be restricted to only access the non-public network of the enterprise, even if PLMN coverage is available in the same geographic area. Other enterprise UEs may be able to access both a non-public network and a PLMN where specifically allowed. An NPN is either a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN), as illustrated inFIG.10. FIG.10shows an example of SNPN and PNI-NPN according to an embodiment of the present disclosure. Referring toFIG.10, the SNPN may be operated by an NPN operator and not relying on network functions provided by a PLMN. The PNI-NPN may be an NPN with the support of a PLMN. An NPN and a PLMN can share NG-RAN. SNPN 5GS deployments are based on the architecture for 5GC with untrusted non-3GPP access for access to SNPN services via a PLMN (and vice versa). Alternatively, a Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the Credentials Holder. In the disclosure, direct access to SNPN is specified for 3GPP access only. Interworking with EPS is not supported for SNPN. Also, emergency services are not supported for SNPN. Furthermore, roaming is not supported for SNPN, e.g. roaming between SNPNs. Handover between SNPNs, between SNPN and PLMN or PNI NPN are not supported. CIoT 5GS optimizations are not supported in SNPNs. PNI-NPNs are NPNs made available via PLMNs e.g. by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN. The existing network slicing functionalities may apply. When a PNI-NPN is made available via a PLMN, then the UE shall have a subscription for the PLMN in order to access PNI-NPN. As network slicing does not enable the possibility to prevent UEs from trying to access the network in areas where the UE is not allowed to use the Network Slice allocated for the NPN, Closed Access Groups (CAGs) may optionally be used to apply access control. A Closed Access Group identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). CAG is used for access control e.g. authorization at cell selection and configured in the subscription as part of the Mobility Restrictions i.e. independent from any S-NSSAI. CAG is not used as input to AMF selection nor Network Slice selection. If NPN isolation is desired, operator can better support NPN isolation by deploying network slicing for PNI-NPN, configuring dedicated S-NSSAI(s) for the given NPN and restricting NPN's UE subscriptions to these dedicated S-NSSAI(s). Hereinafter, details of the SNPN are described. 1. Identifiers The combination of a PLMN ID and Network identifier (NID) identifies an SNPN. The PLMN ID used for SNPNs is not required to be unique. PLMN IDs reserved for use by private networks can be used for non-public networks, e.g. based on mobile country code (MCC) 999 as assigned by ITU. Alternatively, a PLMN operator can use its own PLMN IDs for SNPN(s) along with NID(s), but registration in a PLMN and mobility between a PLMN and an SNPN are not supported using an SNPN subscription given that the SNPNs are not relying on network functions provided by the PLMN. The NID shall support two assignment models:Self-assignment: NIDs are chosen individually by SNPNs at deployment time (and may therefore not be unique) but use a different numbering space than the coordinated assignment NIDs.Coordinated assignment: NIDs are assigned using one of the following two options:1) The NID is assigned such that it is globally unique independent of the PLMN ID used; or2) The NID is assigned such that the combination of the NID and the PLMN ID is globally unique. An optional human-readable network name helps to identify an SNPN during manual SNPN selection. 2. Broadcast System Information NG-RAN nodes which provide access to SNPNs broadcast the following information:One or multiple PLMN IDs; and/orList of NIDs per PLMN ID identifying the non-public networks NG-RAN provides access to. It is assumed that an NG-RAN node supports broadcasting a total of twelve NIDs. The presence of a list of NIDs for a PLMN ID indicates that the related PLMN ID and NIDs identify SNPNs. Further, the NG-RAN nodes which provide access to SNPNs broadcast optionally the following information:A human-readable network name per SNPN. The human-readable network name per SNPN is only used for manual SNPN selection;Information to prevent UEs not supporting SNPNs from accessing the cell, e.g. if the cell only provides access to non-public networks;An indication per SNPN of whether access using credentials from a Credentials Holder is supported;List of supported Group IDs for Network Selection (GINs or GIDs) per SNPN. GIN reuses the NID encoding and can be self-managed or globally unique. GIN may be represented/expressed by a pair (or, combination) of PLMN ID and NID; and/orAn indication per SNPN of whether the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. UEs that do not have any PLMN ID and NID nor GIN broadcast by the SNPN in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs. 3. UE Configuration and Subscription Aspects An SNPN-enabled UE is configured with the following information for each subscribed SNPN:PLMN ID and NID of the SNPN;Subscriber identifier (SUPI) and credentials;Optionally, an N3IWF FQDN and an identifier of the country where the configured N3IWF is located;Optionally, if the UE supports access to an SNPN using credentials from a Credentials Holder:User controlled prioritized list of preferred SNPNs;Credentials Holder controlled prioritized list of preferred SNPNs;Credentials Holder controlled prioritized list of GINs. The Credentials Holder controlled prioritized lists of preferred SNPNs and GINs can be updated by the Credentials Holder. A subscriber of an SNPN is either:identified by a SUPI containing a network-specific identifier that takes the form of a Network Access Identifier (NAI) using the NAI RFC based user identification. The realm part of the NAI may include the NID of the SNPN; oridentified by a SUPI containing an IMSI. In the case of access to an SNPN using credentials owned by a Credentials Holder, the SUPI shall also contain identification for the Credentials Holder (i.e., the realm in the case of Network Specific Identifier based SUPI or the MCC and MNC in the case of an IMSI based SUPI). When Credentials Holder is an SNPN, and the MCC and MNC of the SNPN is not unique, then IMSI based SUPI is not supported as the MCC and MNC need not be unique always; instead USIM credentials are supported using Network Specific Identifier based SUPI. Network Specific Identifier are not supported for the case the Credentials Holder is provided by a PLMN. An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription may additionally be configured with the following information for SNPN selection and registration using the PLMN subscription in SNPN access mode:User controlled prioritized list of preferred SNPNs;Credentials Holder controlled prioritized list of preferred SNPNs;Credentials Holder controlled prioritized list of preferred GINs. The Credentials Holder controlled prioritized lists of preferred SNPNs and GINs can be updated by the Credentials Holder. 4. Network Selection in SNPN Access Mode An SNPN-enabled UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode the UE only selects and registers with SNPNs over Uu. Emergency services are not supported in SNPN access mode. If a UE is not set to operate in SNPN access mode, even if it is SNPN-enabled, the UE does not select and register with SNPNs. A UE not set to operate in SNPN access mode performs PLMN selection procedures. For a UE capable of simultaneously connecting to an SNPN and a PLMN, the setting for operation in SNPN access mode is applied only to the Uu interface for connection to the SNPN. An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription needs to first enter SNPN access mode to be able to select SNPNs. Once the UE has entered SNPN access mode, SNPN selection is performed. Once an SNPN has been selected, the UE attempts registration in the SNPN using the PLMN credentials. Details of activation and deactivation of SNPN access mode are up to UE implementation. When a UE is set to operate in SNPN access mode, the UE does not perform normal PLMN selection procedures. UEs operating in SNPN access mode read the information from the broadcast system information and take them into account during network selection. 4-1. Automatic Network Selection If the UE has multiple SNPN subscriptions, it is assumed that the subscription to use for automatic selection is determined by implementation specific means prior to network selection. For automatic network selection, the UE selects and attempts registration on available and allowable SNPNs in the following order:the SNPN the UE was last registered with (if available);the SNPN identified by the PLMN ID and NID for which the UE has SUPI and credentials;If the UE supports access to an SNPN using credentials from a Credentials Holder, then the UE continues by selecting and attempting registration on available and allowable SNPNs which broadcast the indication that access using credentials from a Credentials Holder is supported in the following order:1> SNPNs in the user controlled prioritized list of preferred SNPNs (in priority order);2> SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs (in priority order);3> SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs (in priority order). If multiple SNPNs are available that broadcast the same GIN, the order in which the UE selects and attempts a registration with those SNPNs is implementation specific.4> SNPNs, which additionally broadcast an indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. the broadcasted NID or GIN is not present in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs in the UE. If multiple SNPNs are available that broadcast the indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, the order in which the UE selects and attempts a registration with those SNPNs is implementation specific. When a UE performs Initial Registration to an SNPN, the UE shall indicate the PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID. 4-2. Manual Network Selection For manual network selection UEs operating in SNPN access mode provide to the user the list of SNPNs (each is identified by a PLMN ID and NID) and related human-readable names (if available) of the available SNPNs the UE has respective SUPI and credentials for. If the UEs supports access to an SNPN using credentials from a Credentials Holder, the UE also presents available SNPNs which broadcast the “access using credentials from a Credentials Holder is supported” indication. The UE indicates to the user any available SNPNs which meet the criteria specified in bullets a) and b). If the UE does not support access to an SNPN using credentials from a credentials holder, this includes SNPNs in the list of “permanently forbidden SNPNs”, and the list of “temporarily forbidden SNPNs”. The UE may indicate to the user whether the available SNPNs are present in the list of “temporarily forbidden SNPNs” or the list of “permanently forbidden SNPNs”. If the UE supports access to an SNPN using credentials from a credentials holder, this includes SNPNs in the lists of “permanently forbidden SNPNs”, and the lists of “temporarily forbidden SNPNs” associated with each entry of the “list of subscriber data” or the PLMN subscription. The UE may indicate to the user whether the available SNPNs are present in a list of “temporarily forbidden SNPNs” or a list of “permanently forbidden SNPNs” for an entry of the “list of subscriber data” or the PLMN subscription.a) SNPNs identified by an SNPN identity in an entry of the “list of subscriber data” in the ME, if any. The order in which those SNPNs are indicated is UE implementation specific;b) if the UE supports access to an SNPN using credentials from a credentials holder, for the SNPNs which broadcast the indication that access using credentials from a credentials holder is supported:b-1) each SNPN which is identified by an SNPN identity contained in one of the user controlled prioritized lists of preferred SNPNs configured in the ME. SNPNs included in the same list are indicated in the order in which they are included in the list. Prioritization between the different lists is UE implementation specific;b-2) each SNPN which is identified by an SNPN identity contained in one of the credentials holder controlled prioritized lists of preferred SNPNs configured in the ME. SNPNs included in the same list are indicated in the order in which they are included in the list. Prioritization between the different lists is UE implementation specific;b-3) each SNPN which broadcasts a GIN contained in one of the credentials holder controlled prioritized lists of GINs configured in the ME. SNPNs broadcasting a GIN included in the same list are indicated in the order in which the GIN is included in the list. Prioritization between the different lists is UE implementation specific. If more than one SNPN broadcast the same GIN, the order in which those SNPNs are indicated is UE implementation specific; andb-4) each SNPN identified by an SNPN identity which is included neither in the SNPN selection parameters of the entries of the “list of subscriber data” nor in the SNPN selection parameters associated with the PLMN subscription and which does not broadcast a GIN which is included in one of the credentials holder controlled prioritized lists of GINs configured in the ME. The order in which those SNPNs are indicated is UE implementation specific. For each of the SNPNs indicated to the user, the UE shall forward a human-readable network name along with the SNPN identity to the upper layers if the system information broadcasted for the SNPN includes the human-readable network name for the SNPN. The UE shall limit its search for the SNPN to the NG-RAN access technology. The user may select an SNPN and the UE then initiates registration on this SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from the selected entry of the “list of subscriber data” or from USIM, if the PLMN subscription is selected, determined as follows:for bullet a) above, the entry of the “list of subscriber data”, with the SNPN identity matching the selected SNPN (this may take place at any time during the presentation of SNPNs), shall be considered as selected;for bullet b-1) above:i) the entry of the “list of subscriber data” which contains the user controlled prioritized lists of preferred SNPNs that includes the SNPN identity of the selected SNPN shall be considered as selected, if the user controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN is included in the entry of the “list of subscriber data”; orii) the PLMN subscription shall be considered as selected, if the user controlled prioritized list of preferred SNPNs associated with the PLMN subscription includes the SNPN identity of the selected SNPN;for bullet b-2) above:i) the entry of the “list of subscriber data” which contains the credentials holder controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN shall be considered as selected, if the credentials holder controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN is included in the entry of the “list of subscriber data”; orii) the PLMN subscription shall be considered as selected, if the credentials holder controlled prioritized list of preferred SNPNs associated with the PLMN subscription includes the SNPN identity of the selected SNPN;for bullet b-3) above:i) the entry of the “list of subscriber data” which contains the credentials holder controlled prioritized list of GINs that includes the GIN broadcast by the selected SNPN shall be considered as selected, if the credentials holder controlled prioritized list of GINs that includes the GIN broadcast by the selected SNPN is included in the entry of the “list of subscriber data”; orii) the PLMN subscription shall be considered as selected, if the credentials holder controlled prioritized list of GINs associated with the PLMN subscription includes the GIN broadcast by the selected SNPN; andfor bullet b-4) above, the entry of the “list of subscriber data” or the PLMN subscription shall be selected by UE implementation specific means. If the SNPN identity of the selected SNPN is included in more than one of the following: one or more user controlled prioritized list(s) of preferred SNPNs configured in the ME, one or more credentials holder controlled prioritized list(s) of preferred SNPNs configured in the ME or the list of SNPNs which are broadcasting a GIN included in one or more credentials holder controlled prioritized list(s) of GINs configured in the ME, which subscription is selected is MS implementation specific. Once the UE has registered on an SNPN selected by the user, the UE shall not automatically register on a different SNPN unless the user selects automatic SNPN selection mode. If the user does not select an SNPN, the selected SNPN shall be the one that was selected either automatically or manually before the SNPN selection procedure started. If no such SNPN was selected or that SNPN is no longer available, then the UE shall attempt to camp on any acceptable cell and enter the limited service state. When a UE performs Initial Registration to an SNPN, the UE shall indicate the selected PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID. 5. Network Access Control If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a self-assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to temporarily prevent the UE from automatically selecting and registering with the same SNPN. If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a coordinated assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to permanently prevent the UE from automatically selecting and registering with the same SNPN. In order to prevent access to SNPNs for authorized UE(s) in the case of network congestion/overload, Unified Access Control information is configured per SNPN (i.e. as part of the subscription information that the UE has for a given SNPN) and provided to the. 6. Cell (Re-)Selection in SNPN Access Mode UEs operating in SNPN access mode only select cells and networks broadcasting both PLMN ID and NID of the selected SNPN. 7. Access to PLMN Services Via Stand-Alone Non-Public Networks To access PLMN services, a UE in SNPN access mode that has successfully registered with an SNPN may perform another registration via the SNPN User Plane with a PLMN (using the credentials of that PLMN) following architectural principles including the optional support for PDU Session continuity between PLMN and SNPN using the Handover of a PDU Session procedures and the SNPN taking the role of “Untrusted non-3GPP access”. QoS differentiation in the SNPN can be provided on per-IPsec Child Security Association basis by using the UE or network requested PDU Session Modification procedure. In the PLMN, N3IWF determines the IPsec child SAs. The N3IWF is preconfigured by PLMN to allocate different IPsec child SAs for QoS Flows with different QoS profiles. To support QoS differentiation in the SNPN with network-initiated QoS, the mapping rules between the SNPN and the PLMN are assumed to be governed by an SLA including: 1) mapping between the DSCP markings for the IPsec child SAs on NWu and the corresponding QoS, which is the QoS requirement of the PLMN and is expected to be provided by the SNPN, and 2) N3IWF IP address(es) in the PLMN. The non-alteration of the DSCP field on NWu is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters in the SNPN can be based on the N3IWF IP address and the DSCP markings on NWu. To support QoS differentiation in the SNPN with UE-requested QoS, the UE can request for an IPsec SA the same 5QI from the SNPN as the 5QI provided by the PLMN. It is assumed that UE-requested QoS is used only when the 5QIs used by the PLMN are from the range of standardized 5QIs. The packet filters in the requested QoS rule can be based on the N3IWF IP address and the SPI associated with the IPsec SA. When the UE accesses the PLMN over NWu via a SNPN, the AMF in the serving PLMN shall send an indication toward the UE during the Registration procedure to indicate whether an IMS voice over PS session is supported or not. 8. Access to Stand-Alone Non-Public Network Services Via PLMN To access SNPN services, a UE that has successfully registered with a PLMN over 3GPP access may perform another registration via the PLMN User Plane with an SNPN (using the credentials of that SNPN) following the architectural principles including the optional support for PDU Session continuity between PLMN and SNPN using the Handover of a PDU Session procedures and the PLMN taking the role of “Untrusted non-3GPP access” of the SNPN, i.e. using the procedures for Untrusted non-3GPP access. QoS differentiation in the PLMN can be provided on per-IPsec Child Security Association basis by using the UE or network requested PDU Session Modification procedure. In the SNPN, N31WF determines the IPsec child SAs. The N3IWF is preconfigured by SNPN to allocate different IPsec child SAs for QoS Flows with different QoS profiles. To support QoS differentiation in the PLMN with network-initiated QoS, the mapping rules between the PLMN and the SNPN are assumed to be governed by an SLA including: 1) mapping between the DSCP markings for the IPsec child SAs on NWu and the corresponding QoS, which is the QoS requirement of the SNPN and is expected to be provided by the PLMN, and 2) N31WF IP address(es) in the SNPN. The non-alteration of the DSCP field on NWu is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters in the PLMN can be based on the N3IWF IP address and the DSCP markings on NWu. To support QoS differentiation in the PLMN with UE-requested QoS, the UE can request for an IPsec SA the same 5QI from the PLMN as the 5QI provided by the SNPN. It is assumed that UE-requested QoS is used only when the 5QIs used by the SNPN are from the range of standardized 5QIs. The packet filters in the requested QoS rule can be based on the N3IWF IP address and the SPI associated with the IPsec SA. When the UE accesses the SNPN over Nwu via a PLMN, the AMF in the serving SNPN shall send an indication toward the UE during the Registration procedure to indicate whether an IMS voice over PS session is supported or not. Emergency services are not supported when the UE accesses the SNPN over NWu via a PLMN. Hereinafter, SNPN connectivity for UEs with credentials owned by an external credential holder is described. SNPNs may support UE access using credentials owned by a Credentials Holder separate from the SNPN. In this case the Session Management procedures (i.e. PDU Sessions) terminate in an SMF in the SNPN. When an SNPN supports UE access using credentials assigned by a Credentials Holder separate from the SNPN, it is assumed that is supported homogeneously within the whole SNPN. FIG.11shows an example of an SNPN connectivity for UEs with credentials owned by an external credential holder according to an embodiment of the present disclosure. In the disclosure, entities separate from the SNPN holding credentials (e.g., external credential holders) may comprise a home service provider (SP). Referring toFIG.11, a visited-SNPN (V-SNPN) may broadcast information that enables a UE to determine whether the UE can access the V-SNPN using any of the home SP credentials that the UE is configured with. In particular, a V-SNPN may broadcast identities of home SPs that the V-SNPN has an agreement with, i.e., which supports access to the V-SNPN using the credentials of those home SPs. The V-SNPN may also broadcast the identities of home SP groups that the V-SNPN has an agreement with for access to the V-SNPN using the credentials of any of the home SPs that are part of the home SP group. The UE may be assumed to be configured by the home SP with one or more home SP groups that the home SP is part of so that the UE can select a V-SNPN that supports one of the home SP groups the UE is configured with. One benefit of the home SP group is that the V-SNPN does not need to broadcast the identities of all the home SPs that are part of the home SP group but only needs to broadcast the home SP group ID instead. In the disclosure, the home SP group ID is an example of GIN/GID. For example, home SP group may include:National operating companies of a multi-national operator. By broadcasting the home SP group ID assigned to the multi-national operator, a V-SNPN can enable the UEs from all the national operating companies of the multi-national operator to select the V-SNPN (instead of having to broadcast the home SP IDs of each of the national operating companies, which may also exceed the number of home SP IDs supported by SIB);Home SPs that are connected to an interconnection provider. Typically mobile operators have direct interconnections and agreements only with large partner networks. For the large amount of small partner networks, mobile operators typically use the services of an interconnection provider that provides interconnection with a large amount of partner networks while avoiding the need for bilateral agreements and interconnections. By broadcasting the home SP group ID assigned to the interconnection provider, a V-SNPN can enable the UEs from all the home SPs connected to the interconnection provider to select the V-SNPN (instead of having to broadcast the IDs of each of the home SPs, which may also exceed the number of home SP IDs supported by SIB) while also avoiding the need for the home SPs to maintain an accurate list of all the supported V-SNPNs. The home SP group ID is assumed to be globally unique or self-managed. Home SP group ID can be based on private enterprise number issued to e.g., a multi-national operator group or to an interconnection provider by internet assigned numbers authority (IANA) in its capacity as the private enterprise number administrator. If the UE's home SP network is not available, then the UE discovers and selects an SNPN as follows (the UE ignores SNPNs that do not broadcast the indication that access using Home SP credentials is supported):1> If the UE is configured with a user-controlled prioritized list of preferred SNPNs then the UE evaluates the list in priority order. That is, if a PLMN ID and NID in the list matches the PLMN ID and NID of an available SNPN, then the UE selects that SNPN;1> If the UE has not been able to select a network based on the above and the UE is configured with a home SP-controlled prioritized list of preferred SNPNs and home SP groups then the UE evaluates the list in priority order as follows:if a PLMN ID and NID in the list matches the PLMN ID and NID of an available SNPN, then the UE selects that SNPN;if a home SP group ID in the list matches a home SP group ID broadcast by an available SNPN, then the UE selects that SNPN. Which SNPN to select if multiple SNPNs support access using the same home SP group ID is up to UE implementation. 1> If the UE has not been able to select a network based on the above but if an available SNPN broadcasts a supported home SP ID that matches the UE's home SP subscription, then the UE selects that SNPN. Which SNPN to select if multiple SNPNs broadcast the UE's home SP ID is up to UE implementation. 1> If the UE has not been able to select a network based on the above, then the UE selects an available SNPN. Once the UE has selected an SNPN according to the procedure above, the UE performs the Registration procedure. The UE provides the SUCI of the home SP subscription. The UE is authenticated by the home SP. If the UE's RPLMN or (E) HPLMN is not available, then the UE discovers and selects an SNPN or PLMN as follows (it is assumed that the UE ignores SNPNs that do not broadcast the indication that access using Home SP credentials is supported): 1> If the UE is configured with a user-controlled prioritized list of preferred SNPNs and PLMNs then the UE evaluates the list in priority order as follows:if a PLMN ID and NID in the list matches the PLMN ID and NID of an available SNPN, then the UE selects that SNPN.if a PLMN ID in the list matches the PLMN ID of an available PLMN, then the UE selects that PLMN. 1> If the UE has not been able to select a network based on the above and the UE is configured with a Home SP-controlled prioritized list of preferred SNPNs, Home SP Groups and PLMNs then the UE evaluates the list in priority order as follows:if a PLMN ID and NID in the list matches the PLMN ID and NID of an available SNPN, then the UE selects that SNPN;if a PLMN ID in the list matches the PLMN ID of an available PLMN, then the UE selects that PLMN;if a Home SP Group ID in the list matches a Home SP Group ID broadcast by an available SNPN, then the UE selects that SNPN. Which SNPN to select if multiple SNPNs support access using the same Home SP Group ID is up to UE implementation. 1> If the UE has not been able to select a network based on the above and the UE is configured with a Visited Network Type Preference indicating “SNPN preferred” or “SNPN only” and an available SNPN broadcasts a supported Home SP ID that matches the UE's Home SP subscription then the UE selects that SNPN. Which SNPN to select if multiple SNPNs broadcast the UE's Home SP ID is up to UE implementation. In the disclosure, the term “selecting an available SNPN” assumes the same selection for SNPNs as currently defined for PLMNs. 1> If the UE has not been able to select a network based on the above: 2> If the UE has been configured with a Visited Network Type Preference, then the UE selects a network as follows:If the Visited Network Type Preference indicates “PLMN only” then the UE ignores available SNPNs and selects an available PLMN.If the Visited Network Type Preference indicates “PLMN preferred” then the UE tries to first select an available PLMN before trying to select an available SNPN.If the Visited Network Type Preference indicates “SNPN only” then the UE tries to select an available SNPN and ignores the PLMNs.If the Visited Network Type Preference indicates “SNPN preferred” then the UE tries to first select an available SNPN before trying to select a PLMN. 2> If the UE has not been configured with a Visited Network Type Preference, then the UE selects an available PLMN. Once the UE has selected an SNPN or PLMN according to the procedure above, the UE performs the Registration procedure. The UE provides the SUCI of the Home SP subscription. The UE is authenticated by the Home SP. Hereinafter, onboarding of UEs for SNPNs is described. Onboarding of UEs for SNPNs allows the UE to access an Onboarding Network (ONN) for the purpose of provisioning the UE with SNPN credentials for primary authentication and other information to enable access to a desired SNPN, i.e. (re-)select and (re-)register with SNPN. To provision SNPN credentials in a UE that is configured with Default UE credentials, the UE selects an SNPN as ONN and establishes a secure connection with that SNPN referred to as Onboarding SNPN (ON-SNPN). If the UE is already provisioned with a set of CH credentials and needs to be provisioned with an additional set of SNPN credentials, the UE can request PVS address information and leverage the User Plane connection enabled by the available set of CH credentials to get access to a PVS. To provision SNPN credentials in a UE that is equipped with a USIM configured with PLMN credentials, the UE selects a PLMN as ONN and establishes a secure connection with that PLMN. After the secure connection is established, the UE is provisioned with SNPN credentials and possibly other data to enable discovery, (re-)selection and (re-)registration for a desired SNPN. ON-SNPN and subscription owner-SNPN (SON-SNPN) can be roles taken by either an SNPN or different SNPNs. It is possible for the same network to be in both roles with respect to a specific UE. FIG.12shows an example of onboarding of UEs for SNPNs according to an embodiment of the present disclosure. When the UEs are deployed without provisioned subscription, UE onboarding and provisioning for an SNPN may provide a solution on how UE subscription/credentials are afterward provisioned to the UEs. The solution enables UEs to get network connectivity to an ON-SNPN so that it can be provisioned with necessary subscription credentials and configuration for the SON-SNPN that will own the UE's subscription. Regarding UE onboarding in non-public network:The UE is provisioned with some default UE credentials and a unique UE identifier and ON Group IDs (e.g., GIN/GID). The unique UE identifier is assumed to be unique within the DCS. It takes the form of a Network Access Identifier (NAI) which is composed of the user part and the realm part which may identify the domain name of the DCS.The UE is not provisioned with subscription credentials that grant access to a SO-PLMN or to an SON-SNPN.As part of the onboarding process the UE shall get access granted to an ON-SNPN based on e.g. default UE credentials.The Onboarding SNPN (ON-SNPN) that is used by the UE in the onboarding process is not necessarily the same as the SON-SNPN (Subscription Owner SNPN) for which subscription credentials will be provisioned in the UE.The ON-SNPN operator has access to a Default Credential Server (DCS), which is used to verify that UE is subject to onboarding based on UE identifier and the associated default UE credentials. The DCS is used for 5GS-level UE authentication/authorization during registration to ON-SNPN for onboarding purpose. The owner of the DCS is out of scope of this document and can be inside or outside of the ON-SNPN e.g. DCS can be owned by the device manufacturer, by a PLMN, by a SNPN other than the ON-SNPN or by a 3rd party. The DCS has the business relationship with the ON-SNPN if the DCS is outside of the ON-SNPN.The ON-SNPN operator provides the UE with connectivity to a Provisioning Server that allows UEs to retrieve their subscription credentials and other personalized configuration. In some deployments the DCS and the Provisioning Server can be the same entity. In deployments where the DCS and the Provisioning Server are different entities, it is expected that they communicate with each other to share the security based on the default UE credentials for UE authentication in the Provisioning Server via an interface.The SON-SNPN owning the subscription (SON-SNPN) is provisioned to its UDM/UDR from the Provisioning Server the corresponding UE's subscription credentials and provides the Provisioning Server with the corresponding UE's configuration data to be provisioned using the UE onboarding procedure, where default UE credentials is used to identify the corresponding data to be provisioned to the UE.The DCS makes a contract with the SON-SNPNs owning the subscription for provisioning the subscriptions to the UE and provides the SON-SNPN with the list of UE identifiers.The ON-SNPN broadcasts system information including an identity of ON-SNPN, a Support for Onboarding Indication and optionally a list of ON Group IDs. Selection of ON-SNPN in case of multiple ON-SNPNs supporting UE Onboarding for the UE is up to UE implementation. UE which is not initially provisioned with subscription credentials may access an Onboarding SNPN (ON-SNPN) and obtain subscription credentials and configuration for an SON-SNPN which can be the same as or different from the ON-SNPN. The UE selects the ON-SNPN based on information broadcasted by the ON-SNPN and registers to it for onboarding service to obtain connectivity to the Provisioning Server. If the UE is not configured with network selection parameters for ON-SNPN, the ON-SNPN may be manually selected, or the UE may randomly select a network that's available and supports onboarding functionalities. If the UE fails to complete the remote provisioning through the selected ON-SNPN (e.g. the UE fails the authentication by the DCS), the UE may select another ON-SNPN to try the process again. During the registration procedure the ON-SNPN may authenticate the UE with the Default Credential Server (DCS) to determine whether the UE is a genuine device subject to onboarding and authorized to access a Provisioning Server via a Configuration PDU Session. Upon establishment of connectivity to the Provisioning Server, the UE is provisioned with the subscription credentials for the SON-SNPN (i.e. SNPN that will own the UE's subscription) and additional configuration data. Then the UE de-registers from the ON-SNPN, performs a new network selection, and registers the SON-SNPN using the provisioned subscription credentials and configuration data. When the UE is in SNPN access mode and the UE wants to perform UE onboarding via an SNPN, the UE shall perform ON-SNPN selection as described below, where the ON-SNPN is an SNPN providing access to the UE for UE onboarding. The trigger for the UE to initiate the UE Onboarding procedure is UE implementation dependent (e.g. the trigger can be a power-on event in the UE, or an input by the user). For automatic or manual selection, the UE may select and attempt to register to an ON-SNPN which broadcast the Onboarding enabled indication and matches the pre-configured ON-SNPN selection information such as SNPN network identifier and/or GIN(s) (if available) according to the UE implementation-specific logic. If the registration fails, the UE may select and attempt to register to a different ON-SNPN. When the UE is not in SNPN access mode and the UE is using PLMN credentials for accessing a PLMN as the onboarding network (ONN), then regular network selection and regular initial registration procedures apply. After successfully registering to the ON-PLMN, the UE is provisioned with the SON-SNPN credentials via User Plane. When Onboarding network is a PLMN and the UE's subscription only allows for Remote Provisioning, then based on PLMN policies, the AMF can start an implementation specific timer once the UE has registered to the PLMN. Expiry of this timer triggers the AMF to deregister the UE from the PLMN. This specific timer is used to prevent registered UEs that are only allowed for Remote Provisioning from staying at the PLMN indefinitely. Meanwhile, as shown inFIGS.11and12, GIDs may be associated with SNPN broadcast by a cell. Given that a cell can support K SNPNs (e.g., K=12) for RAN sharing, if N GIDs per SNPN is explicitly broadcast in the cell, it requires up to N*K GIDs signalling space. Given the maximum SI message size restriction and the signalling size of a GID, the amount of signalling to broadcast N*K GIDs is already considered big even for a small N. If the association exceeds the maximum SI message size, the association needs to be signalled in multiple SIBs. Then UE may need to read SIB1 and those SIB(s), causing delay in network identification and selection. To address this issue, the present disclosure provides a method for efficient signalling of GIDs such that the GID-related information can be efficiently expressed and hence possibly included in the minimum number of SIB(s) (e.g., SIB1 and/or SIB x). In the disclosure, a cell may broadcast/signal, in SIB x which may be SIB1 or SIB other than the SIB1, a set/list of GIDs and a linkage between the GID set and SNPN. For example, it may be signalling-efficient to express the linkage with bitmap. In this case, the SIB x may comprise information as illustrated in table 5 below: TABLE 5-- ASN1START-- TAG-SIBXY-STARTSIBXY-rl7 ::= SEQUENCE{ gin-ElementList-rl7 SEQUENCE (SIZE (1..maxGIN-r17)) OF GIN-Element-rl7 OPTIONAL, -- Need R ginsPerSNPN-List-r17SEQUENCE (SIZE (1..maxNPN-r16)) OF GINs-perSNPN-rl7 OPTIONAL,-- Need R lateNonCriticalExtension OCTET STRINGOPTIONAL, ...}GIN-Element-r17 ::= SEQUENCE { plmn-Identity-r17PLMN-Identity, nid-List-r17 SEQUENCE (SIZE (1..maxGIN-r17))OF NID-r16}GINs-perSNPN-r17 ::= SEQUENCE { supportedGINs-r17BIT STRING (SIZE (1..maxGIN-r17)) OPTIONAL -- Need R}-- TAG-SIBXY-STOP-- ASN1STOP The SIB x may contain group IDs for network selection (GINs) to support access using credentials from a credentials holder or to enable UE onboarding. The SIB x may be present if there is at least one SNPN that supports either access using credentials from a credentials holder or UE onboarding. In table 5, the GIN-ElementList (e.g., set/list of GIDs) may contain one or more GIN elements. Each GIN element may contain either one GIN, which is identified by a PLMN ID and a NID, or multiple GINs that share the same PLMN ID. The GIN index m (i.e., m-th GID among GIDs related to the set/list of GIDs) may be defined as d1+d2++d(n−1)+i for the GIN/GID included in the n-th entry of the gin-ElementList and the i-th entry of its corresponding GIN-Element, where d(k) is the number of GIN index values used in the k-th gin-ElementList entry. The ginsPerSNPN-List (e.g., list of bitmaps) may indicate the supported GINs for each SNPN. The network may include the same number of entries as the number of SNPNs (e.g., maxNPN) in snpn-AccessInfoList (e.g., list of SNPN identifiers) in provided in SIB1, and the n-th entry in this list may correspond to the n-th SNPN listed in snpn-AccessInfoList provided in SIB1. It is not present if there is only a single SNPN in snpn-AccessInfoList in SIB1, as in that case all GINs in this SIB is associated with that SNPN. The supportedGINs (e.g., ginsPerSNPN and/or bitmap) may indicate the GINs which are supported by the given SNPN. The first/leftmost bit may correspond to the GIN with GIN index 0, the second bit may correspond to the GIN with GIN index 1 and so on. A bit set to 1 may indicate that the GIN is supported by the SNPN. If the field is not present, then the corresponding SNPN does not support any GINs. The length/size of the bitmap may be the number of GIDs signalled in the set/list of GIDs (e.g., maxGIN, the number of GIN indexes and/or the number of GIDs related to the set/list of GIDs) broadcast by the cell. The leftmost bit of the bitmap of the associated SNPN may correspond to a first entry of the set/list of GIDs, and the second leftmost bit of the bitmap of the associated SNPN may correspond to a second entry of the set/list of GIDs, etc (or, the reverse correspondence may also be possible). That is, k-th bit from left side in each bitmap may correspond to k-th GID among GIDs related to the set/list of GIDs. Or, the first/leftmost bit may correspond to the GIN with GIN index 0, the second bit may correspond to the GIN with GIN index 1, and so on. A bit with positive indication may indicate that the associated SNPN supports the corresponding GID. That is, a bit set to a positive indication in a bitmap informs that a corresponding GID is supported by an SNPN corresponding to the bitmap. Or, a bit set to positive indication may indicate that the GIN is supported by the SNPN. In an example, bit with positive indication may be bit 1, and bit with negative indication may be bit 0. In another example, bit with positive indication may be bit 0, and bit with negative indication may be bit 1. For signalling of bitmaps for SNPNs, the cell may signal a pair of {SNPN ID, bitmap} for each SNPN. Or, the cell may signal a list of bitmaps, where each bitmap is associated with a SNPN in the SNPN list (i.e., list of SNPN identifiers) in order that is supported and signalled by the cell (the first bitmap of the bitmap list corresponds to the first SNPN identified in the SNPN list, etc). That is, the n-th entry in the list of bitmaps may correspond to n-th SNPN identified in the list of SNPN identifiers. This example is illustrated inFIG.13. For signalling of bitmaps for GIDs, the cell may signal a pair of {GID ID, bitmap} for each SNPN. Or, the cell may signal a list of bitmaps, where each bitmap is associated with a GID in the GID list (i.e., list of GIDs) in order that is supported and signalled by the cell (the first bitmap of the bitmap list corresponds to the first GID in the GID list, etc). That is, the n-th entry in the list of bitmaps may correspond to n-th group identifier among group identifiers related to the list of group identifiers. This example is illustrated inFIG.14. With this efficient signalling of GIDs and association between GIDs and SNPN, network can signal the association between GIDs and SNPNs in a minimum number of SIBs. For example, if signalling of GIDs and association between GIDs and SNPN is all included in SIB1, the UE can immediately check upon only reading SIB1 whether the cell can be accessible by onboarding or using credentials owned by a credential holder separate from SNPN (i.e., using external subscription and credential). if signalling of GIDs and association between GIDs and SNPN is all included in other SIB (e.g., SIB x) dedicated for the association between GINs and SNPNs, the UE can check whether the cell is accessible only upon reading SIB1 and SIB x. With this efficient signalling of GIDs and association between GIDs and SNPN, one SI message or SIB1 message can indicate more number of GINs per SNPN within a given SIB, compared to explicit signaling of associated GINs in RAN sharing cases. A cell may want to signal the GID information (i.e., list of SNPN identifiers, list of GIDs and association between GID(s) and SNPN(s)) in SIB1 for some SNPNs and in other SIB for other SNPNs. In this case, if GID information in SIB1 is available for a concerned SNPN, the UE may only consider the GID information in SIB1 even if other SIB including GID information is available so that the UE can avoid additional SIB reading. If GID information in SIB1 is not available for a concerned SNPN but other SIB including GID information is scheduled, UE may read additional SIB and check if the cell is accessible by onboarding or using credentials owned by a credential holder separate from SNPN (i.e., using external subscription and credential). FIG.13shows an example of a signal flow for signalling a linkage between each SNPN and a GID set for each SNPN according to an embodiment of the present disclosure. Referring toFIG.13, association between SNPN and GID(s) is assumed as:SNPN #1 is associated with GID #A, #B, #C;SNPN #2 is associated with GID #B, #C;SNPN #3 is associated with GID #A, #D, #E;SNPN #4 is associated with GID #A, #D;SNPN #5 is associated with GID #B, #C; andSNPN #6 is associated with GID #A, #D. In step S1301, UE may receive, from a network node, a SIB, e.g., SIB1 including a list of SNPN identifiers. The list of SNPN identifiers may comprise SNPN #1, SNPN #2, SNPN #3, SNPN #4, SNPN #5 and SNPN #6. In step S1303, the UE may receive, from the network node, a SIB (e.g., SIB x) including a list of GIDs and information indicating associated GIDs for each SNPN in SIB1. The SIB including the GID information may be different from SIB1. The list of GIDs may comprise GID #A, GID #B, GID #C, GID #D and GID #E. The information indicating associated GIDs for each SNPN may comprise a list of bitmaps. The n-th entry in the list of bitmaps may correspond to n-th SNPN identified in the list of SNPN identifiers, where a SNPN is identified by a combination of PLMN ID and NID. For example, the 1stentry in the list of bitmaps (e.g., 11100) may correspond to 1stidentified SNPN (e.g., SNPN #1) in the list of SNPN identifiers. The 2ndentry in the list of bitmaps (e.g., 01100) may correspond to 2ndidentified SNPN (e.g., SNPN #2) in the list of SNPN identifiers. The 3rdentry in the list of bitmaps (e.g., 10011) may correspond to 3rdidentified SNPN (e.g., SNPN #3) in the list of SNPN identifiers. The 4thentry in the list of bitmaps (e.g., 10010) may correspond to 4thidentified SNPN (e.g., SNPN #4) in the list of SNPN identifiers. The 5thentry in the list of bitmaps (e.g., 01100) may correspond to 5thidentified SNPN (e.g., SNPN #5) in the list of SNPN identifiers. The 6thentry in the list of bitmaps (e.g., 10010) may correspond to 6thSNPN (e.g., SNPN #6) in the list of SNPN identifiers. The k-th bit from left side in each bitmap correspond to k-th group identifier among group identifiers related to the list of group identifiers. For example, 1stbit from left side in each bitmap correspond to 1stgroup identifier (e.g., GID #A) among group identifiers related to the list of group identifiers. The 2ndbit from left side in each bitmap correspond to 2ndgroup identifier (e.g., GID #B) among group identifiers related to the list of group identifiers. The 3rdbit from left side in each bitmap correspond to 3rdgroup identifier (e.g., GID #C) among group identifiers related to the list of group identifiers. The 4thbit from left side in each bitmap correspond to 4thgroup identifier (e.g., GID #D) among group identifiers related to the list of group identifiers. The 5thbit from left side in each bitmap correspond to 5thgroup identifier (e.g., GID #E) among group identifiers related to the list of group identifiers. A bit set to a positive indication in a bitmap may inform that a corresponding group identifier is supported by a SNPN corresponding to the bitmap. For example, since 1st, 2ndand 3rdbits are set to a positive indication in the 1stbitmap (e.g., 11100), corresponding group identifiers GID #A, GID #B and GID #3 are supported by a SNPN corresponding to the 1stbitmap (e.g., SNPN #1). Since 2ndand 3rdbits are set to a positive indication in the 2ndbitmap (e.g., 01100), corresponding group identifiers GID #B and GID #3 are supported by a SNPN corresponding to the 2ndbitmap (e.g., SNPN #2). Since 1, 4thand 5thbits are set to a positive indication in the 3rdbitmap (e.g., 10011), corresponding group identifiers GID #A, GID #D and GID #E are supported by a SNPN corresponding to the 3rdbitmap (e.g., SNPN #3). Since 1stand 4thbits are set to a positive indication in the 4thbitmap (e.g., 10010), corresponding group identifiers GID #A and GID #D are supported by a SNPN corresponding to the 4thbitmap (e.g., SNPN #4). Since 2ndand 3rdbits are set to a positive indication in the 5thbitmap (e.g., 01100), corresponding group identifiers GID #B and GID #3 are supported by a SNPN corresponding to the 5thbitmap (e.g., SNPN #5). Since 1stand 4thbits are set to a positive indication in the 6thbitmap (e.g., 10010), corresponding group identifiers GID #A and GID #D are supported by a SNPN corresponding to the 6thbitmap (e.g., SNPN #6). FIG.14shows an example of a signal flow for signalling a linkage between each GID and a SNPN set for each GID according to an embodiment of the present disclosure. Referring toFIG.14, association between SNPN and GID(s) is assumed as:GID #A is associated with SNPN #1, #3, #4, #6;GID #B is associated with SNPN #1, #2, #5;GID #C is associated with SNPN #1, #2, #5;GID #D is associated with SNPN #3, #4, #6; andGID #E is associated with SNPN #3. In step S1401, UE may receive, from a network node, SIB1 including a list of SNPN identifiers. The list of SNPN identifiers may comprise SNPN #1, SNPN #2, SNPN #3, SNPN #4, SNPN #5 and SNPN #6. In step S1303, the UE may receive, from the network node, SIB x including a list of GIDs and associated SNPNs for each GID. The list of GIDs may comprise GID #A, GID #B, GID #C, GID #D and GID #E. The associated SNPNs for each GID may comprise a list of bitmap. The n-th entry in the list of bitmaps may correspond to n-th group identifier among group identifiers related to the list of group identifiers. For example, the 1stentry in the list of bitmaps (e.g., 101101) may correspond to 1stGID (e.g., GID #A) among group identifiers related to the list of group identifiers. The 2ndentry in the list of bitmaps (e.g., 110010) may correspond to 2ndGID (e.g., GID #B) among group identifiers related to the list of group identifiers. The 3rdentry in the list of bitmaps (e.g., 110010) may correspond to 3rdGID (e.g., GID #C) among group identifiers related to the list of group identifiers. The 4thentry in the list of bitmaps (e.g., 001101) may correspond to 4thGID (e.g., GID #D) among group identifiers related to the list of group identifiers. The 5thentry in the list of bitmaps (e.g., 001000) may correspond to 5thGID (e.g., GID #E) among group identifiers related to the list of group identifiers. The k-th bit from left side in each bitmap correspond to k-th SNPN in the list of SNPN identifiers. For example, 1stbit from left side in each bitmap correspond to 1stSNPN (e.g., SNPN #1) in the list of SNPN identifiers. The 2ndbit from left side in each bitmap correspond to 2ndSNPN (e.g., SNPN #2) in the list of SNPN identifiers. The 3rdbit from left side in each bitmap correspond to 3rdSNPN (e.g., SNPN #3) in the list of SNPN identifiers. The 4thbit from left side in each bitmap correspond to 4thSNPN (e.g., SNPN #4) in the list of SNPN identifiers. The 5thbit from left side in each bitmap correspond to 5thSNPN (e.g., SNPN #5) in the list of SNPN identifiers. The 6thbit from left side in each bitmap correspond to 6thSNPN (e.g., SNPN #6) in the list of SNPN identifiers. A bit set to a positive indication in a bitmap may inform that a corresponding SNPN supports a GID corresponding to the bitmap. For example, since 1st, 3rd, 4thand 6thbits are set to a positive indication in the 1stbitmap (e.g., 101101), corresponding SNPNs SNPN #1, SNPN #3, SNPN #4 and SNPN #6 support a GID corresponding to the 1stbitmap (e.g., GID #A). Since 1st, 2ndand 5thbits are set to a positive indication in the 2ndbitmap (e.g., 110010), corresponding SNPNs SNPN #1, SNPN #2 and SNPN #5 support a GID corresponding to the 2ndbitmap (e.g., GID #B). Since 1, 2ndand 5thbits are set to a positive indication in the 3rdbitmap (e.g., 110010), corresponding SNPNs SNPN #1, SNPN #2 and SNPN #5 support a GID corresponding to the 3rdbitmap (e.g., GID #C). Since 3rd, 4rdand 6thbits are set to a positive indication in the 4thbitmap (e.g., 001101), corresponding SNPNs SNPN #3, SNPN #4 and SNPN #6 support a GID corresponding to the 4thbitmap (e.g., GID #D). Since 3rdbit is set to a positive indication in the 5thbitmap (e.g., 001000), corresponding SNPN #3 supports a GID corresponding to the 5thbitmap (e.g., GID #E). FIG.15shows an example of a method performed by a UE according to an embodiment of the present disclosure. The method may also be performed by a wireless device. Referring toFIG.15, in step S1501, the UE may receive, from a network, first system information (e.g., SIB1) for a list of stand-alone non-public networks (SNPN) identifiers (e.g., snpn-AccessInfoList). In step S1503, the UE may receive, from the network, second system information (e.g., SIB x) comprising information for a list of group identifiers of network (e.g., gin-ElementList) and information for a list of bitmaps (e.g., ginsPerSNPN-List). According to various embodiments, n-th entry (e.g., n-th ginsPerSNPN and/or n-th supportedGINs) in the list of bitmaps may correspond to n-th identified SNPN (e.g., n-th snpn-AccessInfo) in the list of SNPN identifiers of SIB1. According to various embodiments, k-th bit from left side in each bitmap (e.g., supportedGINs) may correspond to k-th group identifier (e.g., GIN index k) among group identifiers (e.g., GIN indexes) related to the list of group identifiers. According to various embodiments, a bit set to a positive indication in a bitmap informs that a corresponding group identifier is supported by a SNPN corresponding to the bitmap. In step S1505, the UE may identify one or more group identifiers (e.g., one or more GINs) supported by each SNPN in the list of SNPN identifiers based on the first system information and the second system information. In step S1507, the UE may select an SNPN based on the list of SNPN identifiers and one or more group identifiers of network supported by the SNPN. In step S1509, the UE may select a cell of the selected SNPN to camp on the cell. Once the UE has selected a SNPN, the cell selection procedure shall be performed in order to select a suitable cell of that SNPN to camp on. According to various embodiments, each of the group identifiers related to the list of group identifiers may be represented by a pair or combination of a public land mobile network (PLMN) identifier (ID) and a network identifier (NID). According to various embodiments, a size of each bitmap may be identical to a number of the group identifiers related to the list of group identifiers. According to various embodiments, a number of bitmaps in the list of bitmaps may be identical to a number of SNPNs in the list of SNPN identifiers. According to various embodiments, each element in the list of group identifiers may comprise a group identifier (ID) for network selection (GIN) element. The GIN element may comprise a public land mobile network (PLMN) ID and a list of one or more network IDs (NIDs). According to various embodiments, a pair or combination of the PLMN ID and each of the one or more NIDs may represent a GIN among one or more GINs in the GIN element. The GIN may correspond to each of the group identifiers related to the list of group identifiers. According to various embodiments, the k-th group identifier among the group identifiers related to the list of group identifiers may comprise a GIN index k. According to various embodiments, the first system information may be included in a system information block type 1 (SIB1). The second system information may be included in an SIB other than the SIB1 and received after the SIB1 is received. According to various embodiments, the first system information and the second system information may be included in a system information block type 1 (SIB1). According to various embodiments, the bit set to positive indication may comprise a bit set to 1. According to various embodiments, the UE may perform an access to the selected SNPN. According to various embodiments, the group identifiers may be used for the UE to access to an SNPN with credentials owned by a credential holder separate from the SNPN. According to various embodiments, the group identifiers may be used for onboarding of the UE to an SNPN. The onboarding of the UE to the SNPN may comprise allowing the UE to access an onboarding network (ONN) for providing the UE with SNPN credentials for a primary authentication and information to select and register with the SNPN. FIG.16shows an example of a method performed by a network node according to an embodiment of the present disclosure. The network may comprise a base station (BS). Referring toFIG.16, in step S1601, the network node may transmit, to a UE, first system information (e.g., SIB1) for a list of stand-alone non-public networks (SNPN) identifiers (e.g., snpn-AccessInfoList). In step S1603, the network node may transmit, to the UE, second system information (e.g., SIB x) comprising information for a list of group identifiers of network (e.g., gin-ElementList) and information for a list of bitmaps (e.g., ginsPerSNPN-List). According to various embodiments, n-th entry (e.g., n-th ginsPerSNPN and/or n-th supportedGINs) in the list of bitmaps may correspond to n-th SNPN (e.g., n-th snpn-AccessInfo) in the list of SNPN identifiers. According to various embodiments, k-th bit from left side in each bitmap (e.g., supportedGINs) may correspond to k-th group identifier (e.g., GIN index k) among group identifiers (e.g., GIN indexes) related to the list of group identifiers. According to various embodiments, a bit set to a positive indication in a bitmap informs that a corresponding group identifier is supported by a SNPN corresponding to the bitmap. In step S1605, the UE may receive, from the UE, a signalling to access to an SNPN selected based on the list of SNPN identifiers and one or more group identifiers of network supported by the SNPN. For example, one or more group identifiers supported by each SNPN in the list of SNPN identifiers may be identified based on the first system information and the second system information. Furthermore, the method in perspective of the wireless device described above inFIG.12may be performed by first wireless device100shown inFIG.2, the wireless device100shown inFIG.3, the first wireless device100shown inFIG.4and/or the UE100shown inFIG.5. More specifically, the wireless device comprises at least one transceiver, at least processor, and at least one computer memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations. The operations may comprise: receiving, from a network, first system information for a list of stand-alone non-public networks (SNPN) identifiers; receiving, from the network, second system information comprising information for a list of group identifiers of network and information for a list of bitmaps; identifying one or more group identifiers supported by each SNPN in the list of SNPN identifiers based on the first system information and the second system information; selecting a SNPN based on the list of SNPN identifiers and one or more group identifiers of network supported by the SNPN; and selecting a cell of the selected SNPN to camp on the cell. The n-th entry in the list of bitmaps corresponds to n-th SNPN in the list of SNPN identifiers. The k-th bit from left side in each bitmap corresponds to k-th group identifier among group identifiers related to the list of group identifiers. A bit set to positive indication in a bitmap informs that a corresponding group identifier is supported by a SNPN corresponding to the bitmap. Furthermore, the method in perspective of the wireless device described above inFIG.12may be performed by a software code105stored in the memory104included in the first wireless device100shown inFIG.4. More specifically, at least one computer readable medium (CRM) stores instructions that, based on being executed by at least one processor, perform operations comprising: receiving, from a network, first system information for a list of stand-alone non-public networks (SNPN) identifiers; receiving, from the network, second system information comprising information for a list of group identifiers of network and information for a list of bitmaps; identifying one or more group identifiers supported by each SNPN in the list of SNPN identifiers based on the first system information and the second system information; selecting a SNPN based on the list of SNPN identifiers and one or more group identifiers of network supported by the SNPN; and selecting a cell of the selected SNPN to camp on the cell. The n-th entry in the list of bitmaps corresponds to n-th SNPN in the list of SNPN identifiers. The k-th bit from left side in each bitmap corresponds to k-th group identifier among group identifiers related to the list of group identifiers. A bit set to positive indication in a bitmap informs that a corresponding group identifier is supported by a SNPN corresponding to the bitmap. Furthermore, the method in perspective of the wireless device described above inFIG.12may be performed by control of the processor102included in the first wireless device100shown inFIG.2, by control of the communication unit110and/or the control unit120included in the wireless device100shown inFIG.3, by control of the processor102included in the first wireless device100shown inFIG.4and/or by control of the processor102included in the UE100shown inFIG.5. More specifically, an apparatus for configured to operate in a wireless communication system (e.g., wireless device) comprises at least processor, and at least one computer memory operably connectable to the at least one processor. The at least one processor is configured to perform operations comprising receiving, from a network, first system information for a list of stand-alone non-public networks (SNPN) identifiers; receiving, from the network, second system information comprising information for a list of group identifiers of network and information for a list of bitmaps; identifying one or more group identifiers supported by each SNPN in the list of SNPN identifiers based on the first system information and the second system information; selecting a SNPN based on the list of SNPN identifiers and one or more group identifiers of network supported by the SNPN; and selecting a cell of the selected SNPN to camp on the cell. The n-th entry in the list of bitmaps corresponds to n-th SNPN in the list of SNPN identifiers. The k-th bit from left side in each bitmap corresponds to k-th group identifier among group identifiers related to the list of group identifiers. A bit set to positive indication in a bitmap informs that a corresponding group identifier is supported by a SNPN corresponding to the bitmap. Furthermore, the method in perspective of the network node described above may be performed by second wireless device100shown inFIG.2, the device100shown inFIG.3, and/or the second wireless device200shown inFIG.4. More specifically, the network node comprises at least one transceiver, at least processor, and at least one computer memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations. The operations may comprise: transmitting, to a user equipment (UE), first system information for a list of stand-alone non-public networks (SNPN) identifiers; transmitting, to the UE, second system information comprising information for a list of group identifiers of network and information for a list of bitmaps; and receiving, from the UE, a signalling to access to an SNPN selected based on the list of SNPN identifiers and one or more group identifiers of network supported by the SNPN. One or more group identifiers supported by each SNPN in the list of SNPN identifiers are identified based on the first system information and the second system information. The n-th entry in the list of bitmaps corresponds to n-th SNPN in the list of SNPN identifiers. The k-th bit from left side in each bitmap corresponds to k-th group identifier among group identifiers related to the list of group identifiers. A bit set to positive indication in a bitmap informs that a corresponding group identifier is supported by a SNPN corresponding to the bitmap. The present disclosure can have various advantageous effects. For example, signalling overhead required for signalling a GIN list associated with each SNPN may be dramatically reduced. Therefore, the maximum number of GINs that can be signalled can be increased (that is, more GIN signalling space can be guaranteed). For example, network can configure/apply GINs more flexibly. Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure. Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims. | 132,095 |
11943698 | DETAILED DESCRIPTION Hereinafter, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. Furthermore, in describing the present disclosure, a detailed description of a related known function or configuration will be omitted if it is deemed to make the gist of the present disclosure unnecessarily vague. Furthermore, terms to be described hereinafter have been defined by taking into consideration functions in the present disclosure, and may be different depending on a user, an operator's intention or practice. Accordingly, each term should be defined based on contents over the entire specification. Advantages and characteristics of the present disclosure and a method of achieving advantages and characteristics will become more apparent from the embodiments described in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the disclosed embodiments, but may be implemented in various different ways. The embodiments are provided to only complete the present disclosure and to allow those skilled in the art to fully understand the category of the present disclosure. The present disclosure is defined by the category of the claims. The same reference numerals will be used to refer to the same or similar elements throughout the specification. FIG.1is a diagram illustrating private communication network architecture having a public NW integrated NPN (PNI-NPN, a PNI non-public network) form. Referring toFIG.1, the private communication network architecture having a public NW integrated NPN form has a form in which some of a public cellular network consisting of a data network name (DNN) or network slice instance(s) of the public cellular network is used for an NPN. Accordingly, as in a public network, when accessing a private cellular network having the public NW integrated NPN form, a UE110transmits information of single-network slice selection assistance information (S-NSSAI(s)) to a core network (CN) in order to access a network slice instance(s), and selects an access and mobility management function (AMF)120capable of serving the S-NSSAI(s) transmitted by the UE110. The selected AMF120selects a session management function (SMF)130corresponding to the S-NSSAI(s) information. The SMF provides a corresponding NPN service, such as by selecting a user plane function (UPF)140corresponding to the network slice instance(s) or a DNN. Meanwhile, in order to control the access of the UE in a specific area or cell, an RAN105may use a method of broadcasting information of closed access group (CAG) IDs served by the RAN and accessing an RAN that broadcasts the CAG ID to only a UE that has subscribed to the CAG ID. The CN includes entities, such as the AMF120responsible for mobility management and registration management of a UE, an authentication server function (AUSF) (not illustrated) responsible for authenticating a UE, unified data management (UDM)150managing subscription, a unified data repository (UDR) storing subscription data, an SMF130responsible for session management, a UPF140forwarding user data, an application function (AF)180that is an application server operated by a service provider for providing an NPN service outside the CN, and a network exposure function (NEF)170responsible for a role for exposing information of the CN to the outside of a network and providing information necessary for the CN by the AF. FIG.2is a diagram illustrating private communication network architecture having a standalone NPN (SNPN) form. Referring toFIG.2, there is a cellular network having a standalone NPN form, which is autonomously operated by a private cellular network without association with a public cellular network. Alternatively, there may be a cellular network having a standalone NPN form, which is operated by a public cellular network operator. InFIG.2, a standalone NPN #3230is a cellular network having standalone NPN form which is autonomously operated by a private cellular network without association with a public cellular network. Each of standalone NPN #1210and NPN #2220is a cellular network having a standalone NPN form which is operated by a public cellular network operator. Like the standalone NPN #3230, a standalone NPN autonomously operated by a private cellular network without association with a public cellular network has the same communication network architecture as a public cellular network. In this case, a 5G-RAN235may broadcast MCC information of a PLMN ID along with an NPN ID of the standalone NPN by setting the MCC information as a specific value. For example, an MCC 999 value is used. In contrast, like the standalone NPN #1210and NPN #2220, in the case of a cellular network having a standalone NPN form which is operated by a public cellular network operator, UDM205and an AUSF (not illustrated) uses an entity within a public cellular network. Furthermore, if a standalone NPN wants to have its own UDR or NEF according to circumstances, a UDR211,221or an NEF212,222may be located in the standalone NPN. In addition to the entities, the standalone NPN autonomously consists of separate independent entities as the same architecture as a public cellular network. In this case, a 5G-RAN broadcasts a PLMN ID of a corresponding public cellular network along with an NPN ID of the standalone NPN. Meanwhile, an AF208, that is, an application server operated by a service provider for providing an NPN service outside the CN, may provide information necessary for an NPN through an NEF or may be provided with information within an NPN. According to an embodiment of the disclosure, NPN subscription data for a UE may include different information depending on a form of an NPN to be accessed by the UE. That is, as inFIG.1, in the case of an NPN having a public NW integrated NPN form, the contents of some or all of the following items are included in the NPN subscription data.A subscription permanent identifier (SUPI) of a UEA generic public subscription identifier (GPSI) of a UEAn allowed closed access group (CAG) list or a list of allowed CAG IDs which may be accessed by a UE. In this case, a PLMN ID may also be included.Indication indicating whether a UE can be accessed only in an allowed CAG cell.A list of single network slice selection assistance information (S-NSSAI) available for an NPN by a UEA data network name (DNN) available for an NPN by a UEA human readable network name available for an NPN by a UE. For example, a human readable network name corresponding to each S-NSSAI or each DNN, or mapping information between S-NSSAI and a human readable network name, or mapping information between a DNN and a human readable network nameA period in which the NPN subscription data is valid: For example, the period may indicate information on a period in which NPN subscription data is available (a hour or a day or a week or a month or a year), timing at which NPN subscription data expires, etc. For example, this value may be indicated to be always valid or to be not always valid by being inputted as 0 or a specific value, such as null. The valid period may be given with respect to all of NPN subscription data or may be given for each item of NPN subscription data. For example, the valid period may be set for each allowed CAG ID or for each DNN or for each S-NSSAI or for each Human readable network name.An NPN subscription data change indicator. That is, the indicator indicates that NPN subscription data for a serving AMF or a UE needs to be updated because the NPN subscription data has been changed. As inFIG.2, in the case of an NPN having a standalone NPN form, the contents of some or all of the following items are included in the NPN subscription data.A subscription permanent identifier (SUPI) of a UEA generic public subscription identifier (GPSI) of a UEA NPN ID list accessible to a UE. In this case, a PLMN ID may also be included.Subscription credentials to be used for authentication upon access of a UE in a corresponding NPN for each NPN (or for each NPN ID).A human readable network name of an NPN available for a UE.A period in which the NPN subscription data is valid: For example, the period may indicate information on a period in which NPN subscription data is available (a hour or a day or a week or a month or a year), timing at which NPN subscription data expires, etc. For example, this value may be indicated to be always valid or to be not always valid by being inputted as 0 or a specific value, such as null. The valid period may be given with respect to all of NPN subscription data or may be given for each item of NPN subscription data. For example, the valid period may be set for each NPN ID or for each PLMN ID+NPN ID or for each human readable network name.An NPN subscription data change indicator. That is, the indicator indicates that NPN subscription data for a UE needs to be updated because the NPN subscription data has been changed. In this document, NPN subscription data mentioned in describing embodiments means NPN subscription data for an NPN having a public NW integrated NPN form or a standalone NPN form. FIG.3is a diagram illustrating a procedure of adding NPN subscription data to the UDM and the UDR according to an embodiment of the present disclosure. If NPN subscription data of a UE is to be added or modified with respect to NPNs to be accessed by an AF operated by an NPN service provider, a smart factory operator, etc., in step 1, the AF transmits NPN subscription data to the NEF of a PLMN or the NEF of a corresponding NPN that operates a corresponding NPN. In this case, the AF may use an Nnef_ParameterProvision_Update request message (301). In this case, the Nnef_ParameterProvision_Update request message may include a GPSI or SUPI for providing notification that the message is for which UE in addition to the NPN subscription data, and may include an AF ID for indicating a source that provides the NPN subscription data or an AF-Service-Identifier indicating that the NPN subscription data is provisioned and may include a transaction reference ID previously shared between the AF and the NEF. In step 2, the NEF that has received the Nnef_ParameterProvision_Update request message transmits the NPN subscription data to the UDM in order to update NPN subscription data information. In this case, the NEF may use a Nudm_ParameterProvision_Update request message may be used (302). In this case, the Nudm_ParameterProvision_Update request message may include a GPSI or SUPI for providing notification that the message is for which UE in addition to the NPN subscription data, and may include an AF ID for indicating a source that provides the NPN subscription data or an AF-Service-Identifier indicating that the NPN subscription data is provisioned and may include a transaction reference ID previously shared between the NEF and the UDM. In step 3, the UDM that has received the Nudm_ParameterProvision_Update request message transmits an Nudr_DM_Query request message to the UDR in order to check whether it is necessary to update the UDR with respect to the received NPN subscription data (303). In this case, the Nudr_DM_Query request message may have a data set identifier set as “NPN subscription data” or corresponding information including a data set identifier(s) including NPN subscription data may be received from the UDR. In step 4, the UDM identifies whether the NPN subscription data of the UDR needs to be updated (304). For example, when the NPN subscription data received from the UDR through step 3 is different from the NPN subscription data received from the NEF, the UDM identifies that the UDR is to be updated or does no perform step 3 or identifies that the UDR is updated with the NPN subscription data received from the NEF regardless of information received in step 3. In step 5, the UDM transmits an Nudr_DM_Update request message to the UDR in order to update NPN subscription data (305). In this case, the Nudr_DM_Update request message has a data set identifier set as “NPN subscription data”, includes a data set identifier(s) including the NPN subscription data, and includes information corresponding to NPN subscription data to be updated or a data set identifier. Thereafter, the AF is notified of the results indicating that the update of the NPN subscription data has been successfully performed through steps 6 and 7 (306and307). Meanwhile, the NPN subscription data stored in the UDM or the UDR is automatically destroyed when a valid period included in the information elapses. Alternatively, in order to destroy the NPN subscription data, the AF may notify the UDM of the deletion of the corresponding NPN subscription data by using a method of setting the contents of the NPN subscription data as “null” or indicating that a valid period included in the NPN subscription data is not always valid in steps 1 and 2. The UDM may set an Nudr_DM_Delete request message as a data set identifier=“NPN subscription data” instead of the Nudr_DM_Update request message in step 5, and may transmit the Nudr_DM_Delete request message to the UDR so that the UDR deletes the NPN subscription data. FIG.4is a diagram illustrating a procedure of adding NPN subscription data to the UDR according to an embodiment of the present disclosure. If NPN subscription data of a UE is to be added or modified with respect to NPNs to be accessed by an AF operated in an NPN service provider, a smart factory operator, etc., in step 1, the AF transmits NPN subscription data to the NEF of a PLMN or the NEF of a corresponding NPN that operates a corresponding NPN (401). In this case, NPN subscription data may be newly added using an Nnef_ServiceParameter_Create request message or the existing NPN subscription data may be updated using an Nnef_ServiceParameter_Update request message. In this case, the Nnef_ServiceParameter_Create request or the Nnef_ServiceParameter_Update request message may include a GPSI or SUPI for providing notification that the message is for which UE in addition to the NPN subscription data, may include an AF ID for indicating a source that provides the NPN subscription data or include an AF-Service-Identifier indicating that the NPN subscription data is provisioned, and may include a transaction reference ID previously shared between the AF and the NEF in the case of the Nnef_ServiceParameter_Create request message. In step 2, the NEF that has received the Nnef_ServiceParameter_Create request message or the Nnef_ServiceParameter_Update request message directly transmits the NPN subscription data to the UDR in order to update NPN subscription data information. In this case, the NEF may use an Nudr_DM_Create request message or an Nudr_DM_Update request message (402). In this case, if NPN subscription data is newly added, the Nudr_DM_Create request message has a data set identifier set as “NPN subscription data” or includes a data set identifier(s) including the NPN subscription data or includes the NPN subscription data to be updated or information corresponding to a data set identifier. If the existing NPN subscription data is updated, the Nudr_DM_Update request message has a data set identifier set as “NPN subscription data” or includes a data set identifier(s) including the NPN subscription data or includes the NPN subscription data to be updated or information corresponding to a data set identifier. Thereafter, the AF is notified of the results indicating whether the update of the NPN subscription data has been successfully performed through step 3 and 4 (403and404).FIG.5is a diagram illustrating a procedure of provisioning NPN subscription data to a UE according to an embodiment of the present disclosure. According to the embodiments described with reference toFIGS.3and4, in the case of a UE registered with a network of a public network, that is, a PLMN, in the case that NPN subscription data of the UDM for the UE has been changed or NPN subscription data of the UDR has been changed and resultantly NPN subscription data of the UDM has been changed, if newly changed NPN subscription data is applied to the subscription of a corresponding PLMN, UE context of the AMF is updated with the corresponding NPN subscription data, and is provisioned to the UE. NPN subscription data for an NPN having a public NW integrated NPN form corresponds to such a case. Alternatively, NPN subscription data for an NPN having a standalone NPN form which is operated by a public network, that is, a PLMN operator, may correspond to such a case. In step 0, if NPN subscription data has been updated, the AMF may request, from the UDM, a subscription service that requests notification (500). To this end, an Nudm_SDM_Subscribe request message includes SUPI in order to notify the UDM that the message corresponds to subscription for information of which UE. In order to request notification when NPN subscription data is changed, a subscription data type(s) including a subscription data type=“NPN subscription data” or NPN subscription data may be included in the message. As another method of recognizing, by the UDM, that NPN subscription data has been updated, if an NPN subscription data change indicator is included in subscription data of the UE, the UDM may recognize that the NPN subscription data has been updated. According to the embodiments described with reference toFIGS.3and4, when NPN subscription data of the UDM for a corresponding UE is changed, in step 1, the UDM notifies the AMF that NPN subscription data has been changed and transmits an Nudm_SDM_Notification Notify message in order to transmit the changed NPN subscription data (501). The Nudm_SDM_Notification Notify message includes SUPI in order to indicate that the message corresponds to subscription data for which UE. In order to provide notification that the NPN subscription data is included, updated NPN subscription data may be included in the message along with the subscription data type=“NPN subscription data” or a subscription data type(s) including the NPN subscription data. In step 2, the AMF that has received the updated NPN subscription data recognizes that a UE configuration needs to be updated (502), and transmits a UE configuration update command message to the UE as in step 3 when a state of the UE is a connected state (503). Alternatively, the AMF changes a state of the UE into the connected state through paging when the state of the UE is an idle state, or transmits the UE configuration update command message to the UE as in step 3 when the state of the UE is changed into the connected state in the case of a MICO mode UE. The UE configuration update command message includes the NPN subscription data. In step 4, the UE notifies the AMF that the NPN subscription data has been successfully delivered through a UE configuration update complete message (504). Furthermore, in step 5, the AMF notifies the UDM that the NPN subscription data has been successfully delivered to the UE through an Nudm_SDM_Info service message (505). The Nudm_SDM_Info service message includes acknowledgement providing notification that the SUPI and NPN subscription data of the corresponding UE have been successfully delivered. Meanwhile, in step 6, for a case where the UE applies newly changed NPN subscription data, the AMF transmits required updated information to an (R)AN being accessed by the UE (506). For example, in the case of NPN subscription data for an NPN having a public NW integrated NPN form, mobility restriction information in which allowed CAG list information, etc. has been updated may be included and delivered as updated information. FIG.6is a diagram illustrating a procedure of provisioning NPN subscription data to a UE according to an embodiment of the present disclosure. According to the embodiments described with reference toFIGS.3and4, in the case of a UE registered with a network of a public network, that is, a PLMN, in the case that NPN subscription data of the UDM for the UE has been changed or that NPN subscription data of the UDM has been changed because NPN subscription data of the UDR has been changed, if newly changed NPN subscription data is not applied to the subscription of the corresponding PLMN, the corresponding NPN subscription data is provisioned to the UE. NPN subscription data for an NPN having a standalone NPN form operated by a public network, that is, an operator of a PLMN, may correspond to the corresponding NPN subscription data. In step 0, the AMF may request, from the UDM, a subscription service that requests notification when NPN subscription data is updated in the UDM (600). To this end, an Nudm_SDM_Subscribe request message includes SUPI in order to notify the UDM that the message corresponds to subscription for information of which UE. In order to indicate a request for notification when the NPN subscription data is changed, a subscription data type=“NPN subscription data” or a subscription data type(s) including the NPN subscription data may be included in the message. As another method of recognizing, by the UDM, that NPN subscription data has been updated, if an NPN subscription data change indicator has been included in subscription data of a UE, the UDM may recognize that the NPN subscription data has been updated. According to the embodiments described with reference toFIGS.3and4, when NPN subscription data of the UDM for the corresponding UE is changed, in step 1, the UDM notifies the AMF that the NPN subscription data has been changed in order to provision the UE with the NPN subscription data, and transmits an Nudm_SDM_Notification Notify message in order to transmit the changed NPN subscription data (601). The Nudm_SDM_Notification Notify message includes SUPI in order to indicate that the NPN subscription data is subscription data for which UE. Furthermore, the UDM transmits the Nudm_SDM_Notification Notify message to the AMF along with the SUPI by inserting updated NPN subscription data into a transparent container for transmitting the NPN subscription data to the UE along with a subscription data type=“NPN subscription data” or a subscription data type(s) including NPN subscription data. In step 2, the AMF that has received the Nudm_SDM_Notification Notify message recognizes that the information included in the transparent container needs to be delivered to the corresponding UE. When a state of the UE is a connected state, the AMF transmits a DL NAS Transport message to the UE by carrying, on the DL NAS Transport message, the transparent container including the NPN subscription data (602). Alternatively, the AMF changes a state of the UE into the connected state through paging when the state of the UE is an idle state, or transmits the DL NAS Transport message to the UE when a state of the UE is changed into the connected state in the case of a MICO mode UE. In step 3, the UE notifies the AMF that the transparent container including the NPN subscription data has been successfully delivered through an UL NAS Transport message (603). Furthermore, in step 4, the AMF notifies the UDM that the transparent container including the NPN subscription data has been successfully delivered to the UE through an Nudm_SDM_Info service message (604). The Nudm_SDM_Info service message includes acknowledgement providing notification that the transparent container including the SUPI and NPN subscription data of the corresponding UE has been successfully delivered. FIG.7is a diagram illustrating a procedure of obtaining, by a UE, updated NPN subscription data when the UE accesses a standalone NPN autonomously operated by a private cellular network without association with a public cellular network according to an embodiment of the present disclosure. According to the embodiments described with reference toFIGS.3and4, when NPN subscription data of which UE is changed in the UDM or UDR of a standalone NPN autonomously operated by a private cellular network without association with a public cellular network, if the UE has subscription to the standalone NPN, the UE may obtain the changed NPN subscription data in a registration process or through the method ofFIG.5after registration. However, if the UE does not have subscription to the standalone NPN, but the standalone NPN supports non-authentication access, the UE may obtain NPN subscription data by accessing the standalone NPN through non-authentication access according to the procedure ofFIG.7. In step 0a, according to the embodiments described with reference toFIGS.3and4, the AF provides changed NPN subscription data of a UE to the UDM or UDR of a standalone NPN autonomously operated by a private cellular network without association with a public cellular network (700a). Meanwhile, the standalone NPN may support non-authenticated registration, that is, non-authentication network registration, in order to provide a method for obtaining, by a UE that has not yet obtained NPN subscription, the required NPN subscription by accessing the standalone NPN. In step 0b, the RAN of the standalone NPN (SNPN) broadcasts a PLMN ID (MCC=999) and an NPN ID in order to notify UEs of the NW identification of the SNPN. The broadcasting may include indication (or restricted local operator services (RLOS) indication) indicating that the SNPN supports non-authentication network registration (700b). If the UE does not have a credential and subscription for the SNPN, when the UE wants access to the SNPN and recognizes that the SNPN supports non-authentication network registration, the UE NW-selects the SNPN (701). The UE may find out whether the SNPN supports non-authentication network registration from the “indication indicating that the SNPN supports non-authentication network registration” broadcasted by the RAN of the SNPN or may always identify that the SNPN supports non-authentication network registration in the case of MCC=999. The UE selects the SNPN. In step 2, for the non-authentication network registration with the SNPN, the UE includes RLOS indication in a registration request message, transmits the registration request message to the AMF, and completes the non-authentication network registration (702). In step 3, the UE requests a PDU session. In this case, a request message may include the RLOS indication (703). Meanwhile, the AMF that has received the PDU session request message selects an SMF supporting secondary authentication and forwards the message to the selected SMF. When recognizing that secondary authentication is necessary, the SMF that has received the PDU session request message discovers a data network authentication authorization accounting (DN AAA) server and starts an authentication process along with the discovered DN AAA server. As a method of recognizing that the secondary authentication is necessary, the SMF refers to the RLOS indication included in the PDU session request message or indicates that the secondary authentication is necessary for the PDU session by including that a state of the UE is an RLOS indication or un-authenticated state when the AMF transmits, to the SMF, an Nsmf_PDUSession_CreateSMContext Request message by including the PDU session request message received from the non-authentication network-registered UE in the Nsmf_PDUSession_CreateSMContext Request message. In step 4, the UE performs an extensible authentication protocol (EAP) authentication process along with the DN AAA server through the SMF (704). When the EAP authentication is successfully finished, in step 5, the UE terminates the establishment of the PDU session (705). In the EAP authentication step of step 4, the UE previously shares a credential by which an SNPN operator that operates the DN AAA server and a smart factory can be mutually authenticated. For example, the SNPN operator and the smart factory may be authenticated using an ID/Password or a certificate. In step 6, the UE accesses an AF or application server from which the SNPN subscription data and credential of the UE can be downloaded through the generated PDU session, downloads the SNPN subscription data and credential of the UE, and installs the SNPN subscription data and the credential therein (706). In step 7, the UE in which the new SNPN subscription data and the credential have been installed performs de-registration on an SNPN that is now accessed in order to access the SNPN by using the newly downloaded SNPN subscription data and credential (707). In step 8, the UE access the SNPN again by using the newly assigned SNPN subscription data and credential (708). FIG.8is a diagram illustrating a structure of a UE according to an embodiment of the present disclosure. Referring toFIG.8, the UE may include a transceiver810, a controller820, and a storage unit830. In the present disclosure, the controller820may be defined as a circuit or an application-specific integrated circuit or at least one processor. The transceiver810may transmit and receive signals to and from another network entity. The transceiver810may receive system information from a base station, for example, and may receive a synchronization signal or a reference signal. The controller820may control an overall operation of the UE according to an embodiment proposed in the present disclosure. For example, the controller820may control a signal flow between the blocks so that an operation according to the described flowchart is performed. The storage unit830may store at least one of information transmitted and received through the transceiver810and information generated through the controller830. FIG.9is a diagram illustrating a structure of a network entity according to an embodiment of the present disclosure. The network entity illustrated inFIG.9means any one of the network entities illustrated inFIGS.1to7. Referring toFIG.9, the network entity may include a transceiver910, a controller920, and a storage unit930. In the present disclosure, the controller920may be defined as a circuit or an application-specific integrated circuit or at least one processor. The transceiver910may transmit and receive signals to and from a UE or another network entity. The transceiver910may transmit system information to a UE, for example, and may transmit a synchronization signal or a reference signal. The controller920may control an overall operation of the network entity according to the embodiment proposed in the present disclosure. For example, the controller920may control a signal flow between the blocks so that an operation according to the described flowchart is performed. The storage unit930may store at least one of information transmitted and received through the transceiver910and information generated through the controller920. | 30,883 |
11943699 | While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION In certain wireless communications scenarios, component carriers may be associated with a specific PDCCH span pattern and starting span. Monitoring for a PDCCH message on a component carrier occurs on a defined schedule. For example, PDCCH monitoring occasions may be based on a span pattern for a particular time interval. As a more detailed example, an orthogonal frequency-division modulation (OFDM) frame may be divided into a set of spans of a set number of consecutive OFDM symbols. The PDCCH span pattern may then be defined for a set number and location of spans for each set of spans. For example, a PDCCH span pattern may be in a form of (X,Y), where X represents a gap between a first span of a PDCCH monitoring occasion and another PDCCH monitoring occasion, and Y represents a number of spans to monitoring for the PDCCH monitoring occasion. Thus, a PDCCH span pattern of (4,3), e.g., would indicate that the PDCCH monitoring occasion will last for three spans, with no monitoring in a fourth span. This span pattern then repeats for the set of spans. In addition to the span pattern, a starting span indicates in which span, of the set of spans, a particular span pattern starts. Components carriers may thus be categorized as “aligned” or “unaligned.” For two or more component carriers to be aligned, the component carriers have the same span pattern and starting span. Component carriers with different span patterns or different starting spans are unaligned. It may be understood that, in the carrier alignment context, the component carriers implement at least a common time interval. For example, where a UE is configured with a mix of common carriers, a first set of which having OFDM frames divided into a set of spans, such as fourteen spans, and a second set of which have OFDM frames divided into two slots per frame, whether a set of component carriers are aligned or not would not refer to whether a first component carrier from the first set is aligned or not aligned with a second component carrier from the second set. In accordance with aspects of the present disclosure, different techniques for allocating the PDCCH monitoring ability of a UE may be implemented based on component carrier alignment. There are three basic scenarios for component carrier alignment. The first scenario is that all of the component carriers are aligned. The second scenario is that some of the component carriers are not aligned. The first scenario applies if, for any span that starts from a symbol on a downlink component carrier from the Ncells,r16DL,(XY),μdownlink component carriers, there is a span on every other downlink component carrier from the Ncells,r16DL,(XY),μdownlink component carriers that starts from the symbol. (Note: μ, in this context, simply refers to an index into possible SCS configurations, e.g., 30 kHz, 60 kHz, . . . 240 kHz, in the cases of Rel-15 and Rel-16.) The number of serving component carriers configured with a common time interval, such as a set of spans (e.g., in Rel-16), PDCCH monitoring capability with an associated PDCCH span pattern (X, Y) with a common subcarrier spacing (SCS) may be referred to as Ncells,r16DL,(XY),μ. In certain cases, a UE may have a maximum capability to monitor PDCCH for a particular span patterns (X, Y), represented by CPDCCHmax,(X,Y),μ, if the UE indicates a capability to monitor PDCCH according to multiple (X, Y) combinations and a configuration of search space sets to the UE results in a separation of any two consecutive PDCCH monitoring spans that is equal to or larger than the value of X for two or more of the (X, Y) combinations. If a UE is configured with Ncells,r16DL,(XY),μdownlink component carriers with an combination (X, Y) and SCS configuration μ, and where Σμ=01=Ncells,r16DL,μ>Ncellscap-r16, the UE is not required to monitor more than CPDCCHtotal,(X,Y),μnon-overlapping control channel elements (CCEs) per span on the active downlink bandwidth parts (BWPs) of the scheduling component carriers from the Ncells,r16DL,(XY),μdownlink component carriers. In this aligned case, the total number of non-overlapping CCEs per span to be monitored is given by Equation 1, CPDCCHtotal,(X,Y),μ=└Ncellscap-r16·CPDCCHmax,(X,Y),μ·(Ncells,r16DL,(XY),μ)/Σj=01=(Ncells,r16D,j┘. Here, Ncellscap-r16resents the UE's capability on the number of CCs/cells, with Rel-16 PDCCH monitoring capability. In the aforementioned second scenario, at least two component carriers are non-aligned. That is, the second scenario applies if, for any span that starts from a symbol on a downlink component carrier from the Ncells,r16DL,(XY),μdownlink component carriers, all of the spans on at least one other downlink component carrier from the Ncells,r16DL,(XY),μdownlink component carriers do not start from the same symbol. If a UE is configured with Ncells,r16DL,(XY),μdownlink component carriers with an combination (X, Y) and SCS configuration μ, and where Σμ=01Ncells,r16DL,μ>Ncellscap-r16, the UE is not required to monitor more than CPDCCHtotal,(X,Y)μnon-overlapping control channel elements for any set of spans across the active Downlink Bandwidth Parts (DL BWPs) of scheduling of the scheduling component carriers from the Ncells,r16DL,(XY),μdownlink component carriers if the spans on different downlink component carriers from the Ncells,r16DL,(XY),μdownlink component carriers are not aligned, with at most one span per scheduling component carrier for each set. In this non-aligned case, the total number of non-overlapping CCEs per span to be monitored may also be defined by Equation 1, CPDCCHtotal,(X,Y)μ=└Ncellscap-r16·CPDCCHmax,(X,Y)μ·(Ncells,r16DL,(X,Y),μ)/Σj=01(Ncells,r16DL,j)┘, where j is an index into the available subcarrier spacing configurations (e.g., only 30 kHz and 60 kHz are considered in this example). The following is a glossary of terms that may be used in this disclosure: Memory Medium—Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors. Carrier Medium—a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals. Programmable Hardware Element—includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as “reconfigurable logic.” Computer System—any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term “computer system” can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium. User Equipment (UE) (or “UE Device”)—any of various types of computer systems or devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, music players, data storage devices, or other handheld devices, etc. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication. Wireless Device—any of various types of computer systems or devices that perform wireless communications. A wireless device can be portable (or mobile) or may be stationary or fixed at a certain location. A UE is an example of a wireless device. Communication Device—any of various types of computer systems or devices that perform communications, where the communications can be wired or wireless. A communication device can be portable (or mobile) or may be stationary or fixed at a certain location. A wireless device is an example of a communication device. A UE is another example of a communication device. Base Station—The term “Base Station” has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system. Processing Element (or Processor)—refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, individual processors, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above. Channel—a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide while Bluetooth channels may be 1 Mhz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and/or different channels for different uses such as data, control information, etc. Band—The term “band” has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose. Automatically—refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus the term “automatically” is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system must update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed in response to actions the user has taken. Approximately—refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as required by the particular application. Concurrent—refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads. Configured to—Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits. Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component. Turning now toFIG.1, a simplified example of a wireless communication system is illustrated, according to some embodiments. It is noted that the system ofFIG.1is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired. As shown, the example wireless communication system includes a base station102A, which communicates over a transmission medium with one or more user devices106A,106B, etc., through106N. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the user devices106are referred to as UEs or UE devices. The base station (BS)102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs106A through106N. The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station102A and the UEs106may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately be referred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station102A is implemented in the context of 5G NR, it may alternately be referred to as a ‘gNodeB’ or ‘gNB’. As shown, the base station102A may also be equipped to communicate with a network100(e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station102A may facilitate communication between the user devices and/or between the user devices and the network100. In particular, the cellular base station102A may provide UEs106with various telecommunication capabilities, such as voice, SMS and/or data services. Base station102A and other similar base stations (such as base stations102B . . .102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or more cellular communication standards. Thus, while base station102A may act as a “serving cell” for UEs106A-N as illustrated inFIG.1, each UE106may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations102B-N and/or any other base stations), which may be referred to as “neighboring cells.” Such cells may also be capable of facilitating communication between user devices and/or between user devices and the network100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and/or cells which provide any of various other granularities of service area size. For example, base stations102A-B illustrated inFIG.1might be macro cells, while base station102N might be a micro cell. Other configurations are also possible. In some embodiments, base station102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB.” In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC)/5G core (5GC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs. For example, it may be possible that that the base station102A and one or more other base stations102support joint transmission, such that UE106may be able to receive transmissions from multiple base stations (and/or multiple TRPs provided by the same base station). For example, as illustrated inFIG.1, both base station102A and base station102C are shown as serving UE106A. Note that a UE106may be capable of communicating using multiple wireless communication standards. For example, the UE106may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE106may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M/H), and/or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible. FIG.2illustrates user equipment106(e.g., one of the devices106A through106N) in communication with a base station102, according to some embodiments. The UE106may be a device with cellular communication capability such as a mobile phone, a hand-held device, a computer, a laptop, a tablet, a smart watch or other wearable device, or virtually any type of wireless device. The UE106may include a processor (processing element) that is configured to execute program instructions stored in memory. The UE106may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE106may include a programmable hardware element such as an FPGA (field-programmable gate array), an integrated circuit, and/or any of various other possible hardware components that are configured to perform (e.g., individually or in combination) any of the method embodiments described herein, or any portion of any of the method embodiments described herein. The UE106may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE106may be configured to communicate using, for example, NR or LTE using at least some shared radio components. As additional possibilities, the UE106could be configured to communicate using CDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD) or LTE using a single shared radio and/or GSM or LTE using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE106may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above. In some embodiments, the UE106may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE106may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE106might include a shared radio for communicating using either of LTE or 5G NR (or either of LTE or 1×RTT, or either of LTE or GSM, among various possibilities), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible. FIG.3illustrates an example simplified block diagram of a communication device106, according to some embodiments. It is noted that the block diagram of the communication device ofFIG.3is only one example of a possible communication device. According to embodiments, communication device106may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and/or a combination of devices, among other devices. As shown, the communication device106may include a set of components300configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components300may be implemented as separate components or groups of components for the various purposes. The set of components300may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device106. For example, the communication device106may include various types of memory (e.g., including NAND flash310), an input/output interface such as connector I/F320(e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display360, which may be integrated with or external to the communication device106, and wireless communication circuitry330(e.g., for LTE, LTE-A, NR, UMTS, GSM, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.). In some embodiments, communication device106may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet. The wireless communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antenna(s)335as shown. The wireless communication circuitry330may include cellular communication circuitry and/or short to medium range wireless communication circuitry, and may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration. In some embodiments, as further described below, cellular communication circuitry330may include one or more receive chains (including and/or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some embodiments, cellular communication circuitry330may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with a second radio. The second radio may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain. The communication device106may also include and/or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display360(which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display), a mouse, a microphone and/or speakers, one or more cameras, one or more buttons, and/or any of various other elements capable of providing information to a user and/or receiving or interpreting user input. The communication device106may further include one or more smart cards345that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards345. As shown, the SOC300may include processor(s)302, which may execute program instructions for the communication device106and display circuitry304, which may perform graphics processing and provide display signals to the display360. The processor(s)302may also be coupled to memory management unit (MMU)340, which may be configured to receive addresses from the processor(s)302and translate those addresses to locations in memory (e.g., memory306, read only memory (ROM)350, NAND flash memory310) and/or to other circuits or devices, such as the display circuitry304, wireless communication circuitry330, connector I/F320, and/or display360. The MMU340may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU340may be included as a portion of the processor(s)302. As noted above, the communication device106may be configured to communicate using wireless and/or wired communication circuitry. As described herein, the communication device106may include hardware and software components for implementing any of the various features and techniques described herein. The processor302of the communication device106may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor302may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor302of the communication device106, in conjunction with one or more of the other components300,304,306,310,320,330,340,345,350,360may be configured to implement part or all of the features described herein. In addition, as described herein, processor302may include one or more processing elements. Thus, processor302may include one or more integrated circuits (ICs) that are configured to perform the functions of processor302. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)302. Further, as described herein, wireless communication circuitry330may include one or more processing elements. In other words, one or more processing elements may be included in wireless communication circuitry330. Thus, wireless communication circuitry330may include one or more integrated circuits (ICs) that are configured to perform the functions of wireless communication circuitry330. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of wireless communication circuitry330. FIG.4illustrates an example block diagram of a base station102, according to some embodiments. It is noted that the base station ofFIG.4is merely one example of a possible base station. As shown, the base station102may include processor(s)404which may execute program instructions for the base station102. The processor(s)404may also be coupled to memory management unit (MMU)440, which may be configured to receive addresses from the processor(s)404and translate those addresses to locations in memory (e.g., memory460and read only memory (ROM)450) or to other circuits or devices. The base station102may include at least one network port470. The network port470may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices106, access to the telephone network as described above inFIGS.1and2. The network port470(or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices106. In some cases, the network port470may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider). In some embodiments, base station102may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB.” In such embodiments, base station102may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC)/5G core (5GC) network. In addition, base station102may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs. The base station102may include at least one antenna434, and possibly multiple antennas. The at least one antenna434may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices106via radio430. The antenna434communicates with the radio430via communication chain432. Communication chain432may be a receive chain, a transmit chain or both. The radio430may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc. The base station102may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station102may include multiple radios, which may enable the base station102to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station102may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station102may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station102may include a multi-mode radio, which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and LTE, 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.). As described further subsequently herein, the BS102may include hardware and software components for implementing or supporting implementation of features described herein. The processor404of the base station102may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer readable memory medium). Alternatively, the processor404may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor404of the BS102, in conjunction with one or more of the other components430,432,434,440,450,460,470may be configured to implement or support implementation of part or all of the features described herein. In addition, as described herein, processor(s)404may include one or more processing elements. Thus, processor(s)404may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s)404. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)404. Further, as described herein, radio430may include one or more processing elements. Thus, radio430may include one or more integrated circuits (ICs) that are configured to perform the functions of radio430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio430. FIG.5illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry ofFIG.5is only one example of a possible cellular communication circuit; other circuits, such as circuits including or coupled to sufficient antennas for different RATs to perform uplink activities using separate antennas, or circuits including or coupled to fewer antennas, e.g., that may be shared among multiple RATs, are also possible. According to some embodiments, cellular communication circuitry330may be included in a communication device, such as communication device106described above. As noted above, communication device106may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices. The cellular communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas335a-band336as shown. In some embodiments, cellular communication circuitry330may include dedicated receive chains (including and/or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown inFIG.5, cellular communication circuitry330may include a first modem510and a second modem520. The first modem510may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and the second modem520may be configured for communications according to a second RAT, e.g., such as 5G NR. As shown, the first modem510may include one or more processors512and a memory516in communication with processors512. Modem510may be in communication with a radio frequency (RF) front end530. RF front end530may include circuitry for transmitting and receiving radio signals. For example, RF front end530may include receive circuitry (RX)532and transmit circuitry (TX)534. In some embodiments, receive circuitry532may be in communication with downlink (DL) front end550, which may include circuitry for receiving radio signals via antenna335a. Similarly, the second modem520may include one or more processors522and a memory526in communication with processors522. Modem520may be in communication with an RF front end540. RF front end540may include circuitry for transmitting and receiving radio signals. For example, RF front end540may include receive circuitry542and transmit circuitry544. In some embodiments, receive circuitry542may be in communication with DL front end560, which may include circuitry for receiving radio signals via antenna335b. In some embodiments, a switch570may couple transmit circuitry534to uplink (UL) front end572. In addition, switch570may couple transmit circuitry544to UL front end572. UL front end572may include circuitry for transmitting radio signals via antenna336. Thus, when cellular communication circuitry330receives instructions to transmit according to the first RAT (e.g., as supported via the first modem510), switch570may be switched to a first state that allows the first modem510to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry534and UL front end572). Similarly, when cellular communication circuitry330receives instructions to transmit according to the second RAT (e.g., as supported via the second modem520), switch570may be switched to a second state that allows the second modem520to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry544and UL front end572). As described herein, the first modem510and/or the second modem520may include hardware and software components for implementing any of the various features and techniques described herein. The processors512,522may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processors512,522may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processors512,522, in conjunction with one or more of the other components530,532,534,540,542,544,550,570,572,335and336may be configured to implement part or all of the features described herein. In addition, as described herein, processors512,522may include one or more processing elements. Thus, processors512,522may include one or more integrated circuits (ICs) that are configured to perform the functions of processors512,522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors512,522. In some embodiments, the cellular communication circuitry330may include only one transmit/receive chain. For example, the cellular communication circuitry330may not include the modem520, the RF front end540, the DL front end560, and/or the antenna335b. As another example, the cellular communication circuitry330may not include the modem510, the RF front end530, the DL front end550, and/or the antenna335a. In some embodiments, the cellular communication circuitry330may also not include the switch570, and the RF front end530or the RF front end540may be in communication, e.g., directly, with the UL front end572. FIG.6illustrates an exemplary block diagram of a network element600, according to some embodiments. According to some embodiments, the network element600may implement one or more logical functions/entities of a cellular core network, such as a mobility management entity (MME), serving gateway (S-GW), access and management function (AMF), session management function (SMF), network slice quota management (NSQM) function, etc. It is noted that the network element600ofFIG.6is merely one example of a possible network element600. As shown, the core network element600may include processor(s)604which may execute program instructions for the core network element600. The processor(s)604may also be coupled to memory management unit (MMU)640, which may be configured to receive addresses from the processor(s)604and translate those addresses to locations in memory (e.g., memory660and read only memory (ROM)650) or to other circuits or devices. The network element600may include at least one network port670. The network port670may be configured to couple to one or more base stations and/or other cellular network entities and/or devices. The network element600may communicate with base stations (e.g., eNBs/gNBs) and/or other network entities/devices by means of any of various communication protocols and/or interfaces. As described further subsequently herein, the network element600may include hardware and software components for implementing and/or supporting implementation of features described herein. The processor(s)604of the core network element600may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a nontransitory computer-readable memory medium). Alternatively, the processor604may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Turning now toFIG.7, an example distribution of PDCCH monitoring occasions for a set of component carriers700is illustrated, in accordance with aspects of the present disclosure. As shown, the set of component carriers700includes six component carriers, CC1-CC6, all utilizing a fixed SCS. For this example, a total number of component carriers aggregated is represented by the parameter N=6. Component carriers CC1 and CC2 utilize a (2,2) PDCCH span pattern. In this example, a number of component carriers with a (2,2) span pattern is represented by the parameter N_DL(2,2)=2. The other four component carriers CC3-CC6 utilize a (4,3) PDCCH span pattern with various starting spans. In this example, a number of component carriers with a (4,3) span pattern is represented by the parameter N_DL(4,3)=4. As shown, component carriers CC3 and CC4 both have the same span patterns and starting spans, and thus are aligned. Similarly, CC1 and CC2 are also aligned. However, as there is at least one span where not all of the spans of the component carriers have a monitoring period, the set of component carriers overall is non-aligned. In this example, the parameters C_max(2,2)=16 and C_max(4,3)=36 indicate a maximum non-overlapping CCEs per span that the UE can monitor for a given PDCCH span pattern. In certain cases, to help reduce the PDCCH monitoring complexity, the UE may estimate the total limit for non-overlapping CCE monitoring for spans with a same span pattern and SCS and then perform a “hard split” of the number of non-overlapping CCEs required to be monitored across all of the spans, such that each component carrier is allocated a fixed number of non-overlapped CCEs per span for monitoring by sharing the limited resources equally between the component carriers. For a scheduled component carrier, the number of non-overlapped CCEs a UE may monitor on the active downlink BWP with a span configuration (X,Y) for SCS μ, of the scheduling component carrier from the downlink component carriers may be total,(X,Y) defined by Equation 2, min (CPDCCHmax,(X,Y)μ,CPDCCHtotal,(X,Y)μ/Ncells,0DL,(X,Y),μ). In this example, for the component carriers with a span pattern of (2,2) using equation 1 to find a total number of non-overlapping CCEs per span to be monitored with the example parameters is CPDCCHtotal,(2,2)=⌊2·16·26⌋=10. Plugging CPDCCHtotal,(2,2)into Equation 2 above, indicates that the monitoring limit for non-overlapped CCEs per span pattern span for span pattern (2,2) is Limit=min(16, 10)=10 for CC1 and CC2. Thus, UE monitoring capability for the (2,2) span pattern is split across the component carriers with the monitoring pattern. Solving Equation 1 for span pattern (4,3) can be shown as CPDCCHtotal,(4,3)=⌊2·36·46⌋=48. Plugging CPDCCHtotal,(4,3)into Equation 2 above, indicates that the monitoring limit for non-overlapped CCEs per span for span pattern (4,3) is Limit=min(36,484)=12 for CC3-CC6. Thus, the monitoring limit for non-overlapped CCEs per span pattern span for span pattern (4,3) is 12, and UE monitoring capability for the span pattern is split across the component carriers with the span pattern. In certain cases, the above calculations may be repeated for each SCS configuration. In certain cases, to allocate C_total between CCs in the unaligned case, assume that C(x,y) is the limit for span y within CC x, where x=1, . . . ,X, then C(x,y)=C(x) for all spans y within CC x, and the sum of all C(x,y)=C_total, for x=1, . . . ,X. In this case, the CCE values may be unevenly distributed across the component carriers but remain constant within each component carrier, and the sum of any set of spans selected across component carriers is equal to C_total. In accordance with aspects of the present disclosure, reducing the PDCCH monitoring complexity can further be enhanced in the second scenario where the component carriers overall are non-aligned, but some of component carriers are aligned. For example, grouping may be performed into aligned and unaligned groups with the same SCS. Here, the UE may estimate the total number of non-overlapping CCEs per span to be monitored for the spans with the same configuration and SCS. Here, again, a total number of non-overlapping CCEs per span to be monitored for a given span pattern (CPDCCHtotal,(X,Y)μ) is determined based on equation 1. In addition, a hard split of C_total between the different groups (e.g., aligned and non-aligned) may be performed for a given span pattern, as defined by Equation 3, CPDCCHtotal,(X,Y),μ,groupi=CPDCCHtotal,(X,Y),μ·Ncells,r16DL,(X,Y),μ,groupi∑kNcells,r16DL,(X,Y),μ,k, wherein i represents an index into the number of groups in (X,Y), μ, and wherein k is an index that sums across all groups. Then, for a scheduled component carrier, the UE can monitor on the active downlink BWP with a span pattern (X,Y) for SCS μ, of the scheduling component carrier from the non-aligned downlink component carriers, a number=min(CPDCCHmax,(X,Y),μ, CPDCCHtotal,(X,Y),μgroupnon-aligned/Ncells,0DL,(X,Y),μ,groupnon-aligned) of non-overlapped CCEs per span. In the non-aligned case, the UE can split the maximum number of non-overlapped CCEs equally between component carriers. For aligned groups, for a scheduled component carrier, the UE can monitor on the active downlink BWP with a span configuration (X,Y) for SCS μ, of the scheduling component carrier from the non-aligned downlink component carriers, a number=min(CPDCCHmax,(X,Y),μ, CPDCCHtotal,(X,Y),μgroupaligned,kof non-overlapped CCEs per span. In the aligned case, the UE may allocate a component carrier, such as a Primary cell (Pcell), more non-overlapped CCEs than a secondary cell (Scell), so long as the total number does not exceed the limit. In certain cases, the above calculations may be repeated for each SCS configuration. In certain cases, to allocate C_total between CCs in the unaligned case, assume that C(x,y) is the limit for span y within CC x, where x=1, . . . ,X, then C(x,y)=C(x) for all spans y within CC x, and the sum of all C(x,y)=C_total, for x=1, . . . ,X. In this case, the CCE values may be unevenly distributed across the component carrier groups but remain constant within each component carrier group, and the sum of any set of spans selected across component carriers is equal to C_total. Note that, within a component carrier group, the values of C(x,y) may be different. FIG.8illustrates an example distribution of PDCCH monitoring occasions for a set of component carriers800, in accordance with aspects of the present disclosure. As shown, the set of component carriers800once again includes six component carriers, CC1-CC6, all utilizing a fixed SCS with the same parameters as the example fromFIG.7. In this example the UE may split each span pattern and SCS into sets of aligned groups and a single non-aligned group and then estimate C_total for each group. This may be described by Equation 4, CPDCCHtotal,(X,Y),μ,groupi=⌊Ncellscap-r16·CPDCCHmax,(X,Y,)μ·(Ncells,r16DL,(X,Y),μ,groupi)/∑j=0J∑k(Ncells,r16DL,j,groupk)⌋ In this example, the UE performs a hard split within the non-aligned groups of available monitoring occasions. For non-aligned downlink component carriers of a scheduled component carrier, the UE may monitor, on the active downlink DWP with a span pattern (X,Y) for SCS μ, a number of non-overlapped CCEs per span based on Equation 5, min(CPDCCHmax,(X,Y),μ, CPDCCHtotal,(X,Y),μgroupnon-aligned/Ncells,0DL,(X,Y),μ,groupnon-aligned). For non-aligned component carriers, the UE may split the maximum number of non-overlapped CCEs equally between component carriers. For aligned span groups, the UE can pool the monitoring limits across all the spans of the aligned groups. For aligned downlink component carriers of a scheduled component carrier, the UE may monitor, on the active downlink BWP with a span pattern (X,Y) for SCS μ, a number of non-overlapped CCEs per span based on Equation 6, min(CPDCCHmax,(X,Y),μ, CPDCCHtotal,(X,Y),μgroupaligned,k. For aligned component carriers, the UE may allocate a component carrier, such as a Pcell, more non-overlapped CCEs than a Scell, so long as the total number does not exceed the limit. Applying the parameters of this example to solve for Equation 4 for the (2,2) span pattern of CC1 and CC2 may be shown as: CPDCCHtotal,(2,2)=⌊(16·2·26)⌋=10. As CC1 and CC2 are aligned component carriers, solving for Equation 6 may be shown as Limit=min(16,10)=10.]. Thus, the monitoring limit for non-overlapped CCEs per span pattern span for aligned component carriers having a span pattern (2,2) is 10, as shown inFIG.8for CC1 and CC2. In certain cases, to allocate C_total between CCs in the unaligned case, assume that C(x,y) is the limit for span y within CC x, where x=1, . . . ,X, then C(x,y)=C(x) for all spans y within CC x, and the sum of all C(x,y)=C_total, for x=1, . . . ,X. In this case, the CCE values may be unevenly distributed across the component carrier groups but remain constant within each component carrier group, and the sum of any set of spans selected across component carriers is equal to C_total. Note that, within a component carrier group, the values of C(x,y) may be different. In this example, CC3 and CC4 are also aligned component carriers and solving for Equation 4 may be shown as: CPDCCHtotal(4,3),groupaligned=⌊(36·2·26)⌋=24, and solving for Equation 6 may be shown as Limit=min(36, 24)=24. As the UE may allocate up to all of the monitoring resources to a single component carrier of the aligned component carriers, CC3 here is allocated all 24 monitoring instances. Thus, the monitoring limit for non-overlapped CCEs per span pattern span for aligned component carriers having a span pattern (4,3) is 24, as shown inFIG.8for CC3 and CC4. In this example, CC5 and CC6 are non-aligned component carriers and solving for Equation 4 may be shown as CPDCCHtotal,(4,3),groupnon-aligned=⌊(36·2·26)⌋=24, and solving for Equation 5 may be shown as Limit=min(36,242)=12. Thus, the monitoring limit for non-overlapped CCEs per span pattern span for span pattern (4,3) is 12. Thus, the monitoring limit for non-overlapped CCEs per span pattern span for non-aligned component carriers having a span pattern (4,3) is 12, as shown inFIG.8for CC5 and CC6. In certain cases, the above calculations may be repeated for each SCS configuration. In certain cases, the determined PDCCH monitoring limit for component carriers with a shared span pattern remains constant within each component carrier. In some such cases, determining the PDCCH monitoring limit for a group of component carriers comprises determining a minimum of a predetermined maximum number of non-overlapping CCEs for a monitoring pattern and a total number of non-overlapping CCEs of the group shared by a number of component carriers with a shared span pattern. In certain cases, “overbooking” limits, i.e., the practice of a wireless station (e.g., a gNB) configuring more non-overlapping CCEs than is allowed, based on the per-cell or carrier aggregation (CA) limits, may depend on what type of group a Pcell is located in. For example, if the Pcell is in an aligned group, then C_limit for the Pcell (C_limit(Pcell)) may be described as min(Ctotal_aligned, C_span), and C_limit for the corresponding Scell (C_limit(Scell)) may be described as Ctotal_{aligned}-C_limit (Pcell). If the Pcell is in an unaligned group, then C_limit(Pcell) may equal min (Ctotal_{non-aligned}/number(non-aligned), C_max_span). For the corresponding SCell, C_limit(Scell) may equal min (Ctotal_{non-aligned}/number(non-aligned), C_max_span). In accordance with aspects of the present disclosure, monitoring gap and span capability may be reported by a UE. For example, the UE may report gap and span capability to the network element by reporting a supported Ncap-r16 estimation method. As another example, a UE may receive a PDCCH configuration, the configuration indicated expected gap and span capability using the Ncap-r16 estimation method. Based on this indication, the UE may either treat all component carriers as unaligned or perform grouping as described above. In certain cases, the UE may estimate applicable gap and span configurations based on a received PDCCH configuration. The UE may also receive an Ncap-r16 estimation method, or use a stored estimation method. In certain cases, a gNB cell may include one or more transmission and reception points (TRPs), and a UE may be configured to connect via multiple component carriers, where some component carriers are served by a single TRP, while other component carriers are served by multiple TRPs. When monitoring a component carrier operating in a multi-TRP mode, the UE may have to monitor for multiple downlink control information (DCI) from the multiple TRPs. Here, Ncell,0DLmay represent a number of cells in a single DCI or single TRP mode and Ncell,1DLmay represent the number of cell in a multi-DCI mode. If a UE is configured with Ncell,0DL+Ncell,1DLdownlink component carriers, for the UE to determine UE capability, PDCCH-BlindDetectionCA, the number of supported serving components carriers for PDCCH monitoring per slot is Ncell,0DL+γ×Ncell,1DL, where γ is derived from a UE capability, R. In certain cases, R may be predefined for a UE, for example, as a constant stored on the UE. With multi-TRPs, a maximum number of total PDCCH candidates and non-overlapped CCEs are scaled by r times in Rel-16, as compared to Rel-15. If the UE does not report to a network element pdcch-BlindDetectionCA, or the UE is not provided with BDFactorR, r is equal to 2. Otherwise, r is configured by BDFactorR, which is either 1 or R. For Rel-15 behavior, r=1. For r>1, the sets associated with the CORESET with CORESETPoolIndex=0 if CORESETPoolIndex is configured and on the primary cell. A CORESET is a set of physical resources, such as a downlink resource grid, and a set of parameters used to carry the PDCCH/DCI. Where a UE is configured with Ncell,0DL+Ncell,1DLdownlink component carriers, if ∑j=03(Ncells,0DL,j+γ·Ncells,1DL,j)>4, then the UE may be configured to process CPSCCHtotal,slot,μnon-overlapped CCEs per slot on the active downlink DWP of the scheduling cell, where, per Equation 7, CPDCCHtotal,slot,μ=⌊Ncellscap·CPDCCHmax,slot,μ(Ncells,0DL,j+γ·Ncells,1DL,j)·/∑j=03(Ncells,0DL,j+γ·Ncells,1DL,j)⌋ In such a configuration, C_total may be estimated where if a UE is configured with ∑j=01(Ncells,0DL,(X,Y),j+γ·Ncells,1DL,(X,Y),j)>Z, where Z is pre-defined limit, such as 4, with an associated monitoring patter (X,Y) and SCS configuration p the UE may monitor CPSCCHtotal,slot,μnon-overlapping CCEs per span on the active downlink BWP of the scheduling cells from the downlink cells. Here, per Equation 8, CPDCCHtotal,(X,Y),μ=⌊Ncellscap-r16·CPDCCHmax,(X,Y),μ(Ncells,0DL,(X,y),μ+γ·Ncells,1DL,(X,Y),μ)·/∑j=01(Ncells,0DL,(X,Y),j+γ·Ncells,1DL,(X,Y),j)⌋. For a scheduled cell, for the aligned component carriers, the UE may monitor, per Equation 9, min(γ·CPDCCHmax,(X,Y),μ·CPDCCHtotal,(X,Y),μ) non-overlapped CCEs per span and may monitor min(CPDCCHmax,(X,Y),μ·CPDCCHtotal,(X,Y),μ) non-overlapped CCEs per span for CORESETS with the same CORESETPoolIndex value. For non-aligned component carriers, the UE may monitor, per Equation 10, min(γ·CPDCCHmax(X,Y),μ,CPDCCHtotal,(X,Y),μ/Ncells,0DL,(X,Y),μ,non-aligned+γ·Ncells,1DL,(X,Y),μ,non-aligned) non-overlapped CCEs per span and may monitor min(CPDCCHmax(X,Y),μ,CPDCCHtotal,(X,Y),μ/Ncells,0DL,(X,Y),μ,non-aligned+γ·Ncells,1DL,(X,Y),μ,non-aligned) non-overlapped CCEs per span for CORESETS with the same CORESETPoolIndex value. In certain cases, for any (X,Y) span pattern for a specific SCS may be treated as unaligned for a multi-TRP component carrier. FIG.9illustrates an example distribution of PDCCH monitoring occasions for a set of component carriers900, in accordance with aspects of the present disclosure. In the set of component carriers900, CC3 is configured for multi-TRP operation with TRP1 and TRP2. In this example, the parameter γ=2 and all other parameters are the same as the examples discussed with respect toFIGS.7and8. Solving for Equation 8 for the (2,2) span pattern can be shown as CPDCCHtotal,(2,2)=⌊(16·2·27)⌋=9, and for the (4,3) span pattern, CPDCCHtotal,(4,3)=⌊(36·2·57)⌋=51. As the (2,2) span pattern is aligned, Equation 9 is applied as Limit=min(16, 9)=9. Thus, each (2,2) span may include 9 scheduled monitoring instances for CC1 and CC2. In this example, the (4,3) span pattern may be treated as unaligned as there is a multi-TRP component carrier with the (4,3) span pattern and Equation 10 may be applies as shown as Limit=min(36,515)=11. Thus, each (4,3) span may include 11 monitoring instances for CC3-CC6. In other cases, a UE may implement certain procedures to determine whether a multi-DCI/multi-TRP configuration is aligned. This determination may be made in two steps. In the first step, the UE may define an intra-TRP alignment and an inter-TRP alignment. The intra-TRP alignment may be determined if there is a span on every downlink component carrier from the downlink component carriers which start from the symbol with a single TRP. Inter-TRP alignment may be determined if there is a span on every other TRP from all the TRPs that starts from the symbol within a single downlink component carrier, and the UE can process the PDCCHs from the different TRPs substantially simultaneously, e.g., where the difference in the timing advance to the two TRPs is less than a threshold, such as a threshold processing limit. This threshold may be defined as a UE capability or otherwise predefined. In the second step, the UE may classify a transmission as aligned or non-aligned based on the intra-TRP or inter-TRP alignment. This classification may be based on four scenarios. The first is where there is intra-TRP alignment and inter-TRP alignment. In such case, the UE may classification the transmission as aligned. In this scenario, a single group may be used to estimate C_total, based on the aligned span technique described above. In the second scenario, there may be an intra-TRP alignment, but inter-TRP is non-aligned. In this scenario, the UE may create two groups, the first group including intra-TRP component carriers without multi-DCI mode which are aligned, and a second group including intra-TRP component carriers with multi-DCI mode, which are non-aligned. Alternatively, in this second scenario, the UE may assume R=1 and fall back to basic Rel-15 behavior, i.e., PDCCH monitoring based on a single TRP and its associated limits. In the third scenario, intra-TRP may be non-aligned with inter-TRP alignment. In this scenario, the system may be considered non-aligned with R set to the configured value. In a fourth scenario, intra-TRP may be non-aligned and inter-TRP may also be non-aligned. In this scenario, the UE may assume R=1 and fall back to basic Rel-15 limits. FIG.10illustrates a technique for wireless communications1000, in accordance with aspects of the present disclosure. At block1010, a wireless device is configured to access a wireless network using a set of at least three component carriers (CCs). At block1020, the at least three CCs are divided into groups of CCs based on whether the CCs share a monitoring pattern and a starting span for monitoring a Physical Downlink Control Channel (PDCCH) of each CC. At block1030, a number of non-overlapping control channel elements (CCE) are determined to monitor for each group of CCs. At block1040, the wireless device is configured to monitor the non-overlapping CCEs based on the determined number to monitor for each group. In certain cases, the dividing is further based on subcarrier spacings of the CCs. FIG.11illustrates a technique for wireless communications1100, in accordance with aspects of the present disclosure. At block1110, a wireless device is configured to access a wireless network using a set of at least three CCs. At block1120, the at least three CCs are divided into groups of CCs based on whether the CCs share a monitoring pattern and a starting span for monitoring a PDCCH of each CC. At block1130, a number of non-overlapping CCEs are determined to monitor for each group of CCs. At block1132, a PDCCH monitoring limit for a group of component carriers is determined. At block1134, the determined PDCCH monitoring limit is split across the spans of the component carriers of the group of component carriers. At block1140, the wireless device is configured to monitor the non-overlapping CCEs based on the determined number to monitor for each group. FIG.12illustrates a technique for wireless communications1200, in accordance with aspects of the present disclosure. At block1210, a wireless device is configured to access a wireless network using a set of at least three CCs. At block1220, the at least three CCs are divided into groups of CCs by grouping the component carriers with both a shared span pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group for monitoring a PDCCH of each CC. At block1230, a number of non-overlapping CCEs are determined to monitor for each group of CCs. At block1232, a PDCCH monitoring limit is determined for component carriers with a shared span pattern. At block1234, the determined PDCCH monitoring limit is split for component carriers of the first group based on the shared span pattern. At block1236the determined PDCCH monitoring limit is split for component carriers of the second group across spans of the component carriers of the second group. At block1240, the wireless device is configured to monitor the non-overlapping CCEs based on the determined number to monitor for each group. FIG.13illustrates a technique for wireless communications1300, in accordance with aspects of the present disclosure. At block1310, a wireless device is configured to access a wireless network using a set of at least three CCs. At block1320, the at least three CCs are divided into groups of CCs by grouping the component carriers with both a shared span pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group for monitoring a PDCCH of each CC. At block1330, a number of non-overlapping CCEs are determined to monitor for each group of CCs. At block1332, a PDDCH monitoring limit for component carriers is determined based on the grouped component carriers. At block1340, the wireless device is configured to monitor the non-overlapping CCEs based on the determined number to monitor for each group. FIG.14illustrates a technique for wireless communications1400, in accordance with aspects of the present disclosure. At block1410, a wireless device is configured to access a wireless network using a set of at least three CCs. At block1420, the at least three CCs are divided into groups of CCs by grouping the component carriers with both a shared span pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group for monitoring PDCCH of each CC. At block1430, a number of non-overlapping CCEs are determined to monitor for each group of CCs. At block1432, an overbooking limit is determined for each CC, wherein the overbooking limit is based on the group an overbooked CC is in. At block1440, the wireless device is configured to monitor the non-overlapping CCEs based on the determined number to monitor for each group. FIG.15illustrates a technique for or wireless communications1500, in accordance with aspects of the present disclosure. At block1510, a wireless device is configured to access a wireless network using a set of at least three CCs, where at least one of the CCs is received from multiple transmission points. At block1520, the at least three CCs are divided into groups of CCs by grouping the component carriers with both a shared span pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group for monitoring a PDCCH of each CC, wherein the at least one CC received from a multiple transmission point is divided into the second group. At block1530, a number of non-overlapping CCEs are determined to monitor for each group of CCs. At block1540, the wireless device is configured to monitor the non-overlapping CCEs based on the determined number to monitor for each group. FIG.16illustrates a technique for wireless communications1400, in accordance with aspects of the present disclosure. At block1510, a wireless device is configured to access a wireless network using a set of at least CCs, where at least one of the CCs is received from multiple transmission points. At block1520, the at least three CCs are divided into groups of CCs by grouping the component carriers with both a shared span pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group for monitoring a PDCCH of each CC, wherein the at least one of the CCs received from a multiple transmission point are grouped based on an alignment of the multiple transmission points. At block1630, a number of non-overlapping CCEs are determined to monitor for each group of CCs. At block1640, the wireless device is configured to monitor the non-overlapping CCEs based on the determined number to monitor for each group. It is noted that, while the examples and embodiments above focus primarily on methods to calculate the maximum number of non-overlapping CCEs in a carrier aggregation scenario, similar methodologies and formulae may also be applied for calculating the maximum number of PDCCH Candidates (i.e., M) in a wireless communication scenario. Similarly, while the examples and embodiments above focus primarily methods to calculate the maximum number of non-overlapping CCEs in a carrier aggregation scenario, similar methodologies and formulae may also be applied for calculating limits on the number of blind decodes (BDs) that may be attempted by a UE in a carrier aggregation scenario, as well. EXAMPLES In the following sections, further exemplary embodiments are provided. According to Example 1, a method is disclosed, comprising: configuring a wireless device to access a wireless network using a set of at least three components carriers (CCs); dividing the at least three component carriers into groups of component carriers based on whether the component carriers share a span pattern and a starting span for monitoring a Physical Downlink Control Channel (PDCCH) of each component carrier; determining a number of non-overlapping control channel elements (CCE) to monitor for each group of component carriers; and configuring the wireless device to monitor the non-overlapping CCEs based on the determined number to monitor for each group. Example 2 comprises the subject matter of Example 1, wherein the dividing is further based on subcarrier spacing of the component carriers. Example 3 comprises the subject matter of Example 1, wherein the determined number of non-overlapping CCEs to monitor is a predetermined number. Example 4 comprises the subject matter of Example 1, wherein the dividing comprises grouping the component carriers based on a shared span pattern; and wherein determining the number of non-overlapping CCEs to monitor comprises: determining a PDCCH monitoring limit for a group of component carriers, and splitting the determined PDCCH monitoring limit across spans of the component carriers of the group of component carriers. Example 5 comprises the subject matter of Example 1, wherein the dividing comprises grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein determining the number of non-overlapping CCEs to monitor for the second group comprises: determining a PDCCH monitoring limit for component carriers with a shared span pattern, splitting the determined PDCCH monitoring limit for component carriers of the first group based on the shared span pattern; and splitting the determined PDCCH monitoring limit for component carriers of the second group across spans of the component carriers of the second group. Example 6 comprises the subject matter of Example 5, wherein determining a PDCCH monitoring limit for component carriers of the second group comprises determining a minimum of a predetermined maximum number of spans for a monitoring pattern and a total number of component carriers of the second group divided by a number of component carriers with a shared span pattern. Example 7 comprises the subject matter of Example 6, wherein the determined PDCCH monitoring limit for component carriers with a shared span pattern remains constant within each component carrier. Example 8 comprises the subject matter of Example 5, wherein determining a PDCCH monitoring limit for component carriers of the second group comprises determining a minimum of a predetermined maximum number of non-overlapping CCEs for a monitoring pattern and a total number of non-overlapping CCEs of the second group shared by a number of component carriers with a shared span pattern. Example 9 comprises the subject matter of Example 8, wherein the determined PDCCH monitoring limit for component carriers with a shared span pattern remains constant within each component carrier. Example 10 comprises the subject matter of Example 1, wherein the dividing comprises grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein determining the number of non-overlapping CCEs to monitor comprises: determining a PDCCH monitoring limit for component carriers based on the grouped component carriers. Example 11 comprises the subject matter of Example 1, wherein the dividing comprises grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein an overbooking limit is based on the group an overbooked CC is in. Example 12 comprises the subject matter of Example 1, further comprising transmitting the determined non-overlapping CCE to monitor to a wireless station. Example 13 comprises the subject matter of Example 1, wherein the determined non-overlapping CCE to monitor is based on configuration information received from the wireless station. Example 14 comprises the subject matter of Example 1, wherein at least one CC of the set of CCs is received from multiple transmission points. Example 15 comprises the subject matter of Example 14, wherein the dividing comprises grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group, and wherein the at least one CC received from multiple transmission point is divided into the second group. Example 16 comprises the subject matter of Example 14, further comprising grouping CCs received from multiple transmission points based on an alignment of the multiple transmission points. According to Example 17, a wireless device is disclosed, comprising: an antenna; a radio operably coupled to the antenna; and a processor operably coupled to the radio; wherein the wireless device is configured to: access a wireless network using at least three components carriers (CCs); divide the at least three component carriers into groups of component carriers based on whether the component carriers share a monitoring pattern for monitoring a Physical Downlink Control Channel (PDCCH) of each component carrier; determine a number of non-overlapping control channel elements (CCE) to monitor for each group of component carriers; and monitor the non-overlapping CCEs based on the determined number to monitor for each group. Example 18 comprises the subject matter of Example 17, wherein the wireless device is configured to divide the at least three component carriers by grouping the component carriers based on a shared span pattern; and wherein determining the number of non-overlapping CCEs to monitor comprises: determining a PDCCH monitoring limit for a group of component carriers, and splitting the determined PDCCH monitoring limit across spans of the component carriers of the group of component carriers. Example 19 comprises the subject matter of Example 17, wherein the wireless device is configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein the wireless device is configured to determine the number of non-overlapping CCEs to monitor for the second group by: determining a PDCCH monitoring limit for component carriers with a shared span pattern, splitting the determined PDCCH monitoring limit for component carriers of the first group based on the shared span pattern; and splitting the determined PDCCH monitoring limit for component carriers of the second group across spans of the component carriers of the second group. Example 20 comprises the subject matter of Example 17, wherein the wireless device is configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein the wireless device is configured to determine the number of non-overlapping CCEs to monitor by: determining a PDCCH monitoring limit for component carriers based on the grouped component carriers. Example 21 comprises the subject matter of Example 17, wherein the wireless device is configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein an overbooking limit is based on the group an overbooked CC is in. Example 22 comprises the subject matter of Example 17, wherein at least one CC of the set of CCs is received from multiple transmission points. According to Example 23 an apparatus is disclosed, comprising: a processor configured to: configure a wireless device to access a wireless network using at least three components carriers (CCs); divide the at least three component carriers into groups of component carriers based on whether the component carriers share a monitoring pattern for monitoring a Physical Downlink Control Channel (PDCCH) of each component carrier; determine a number of non-overlapping control channel elements (CCE) to monitor for each group of component carriers; and configuring the wireless device to monitor the non-overlapping CCEs based on the determined number to monitor for each group. Example 24 comprises the subject matter of Example 23, wherein the processor is further configured to divide the at least three component carriers by grouping the component carriers based on a shared span pattern; and wherein determining the number of non-overlapping CCEs to monitor comprises: determining a PDCCH monitoring limit for a group of component carriers, and splitting the determined PDCCH monitoring limit across spans of the component carriers of the group of component carriers. Example 25 comprises the subject matter of Example 23, wherein the processor is further configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein the processor is further configured to configure the wireless device to determine the number of non-overlapping CCEs to monitor for the second group by: determining a PDCCH monitoring limit for component carriers with a shared span pattern, splitting the determined PDCCH monitoring limit for component carriers of the first group based on the shared span pattern; and splitting the determined PDCCH monitoring limit for component carriers of the second group across spans of the component carriers of the second group. Example 26 comprises the subject matter of Example 23, wherein the processor is further configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein the processor is further configured to configure the wireless device to determine the number of non-overlapping CCE to monitor by: determining a PDCCH monitoring limit for component carriers based on the grouped component carriers. Example 27 comprises the subject matter of Example 23, wherein the processor is further configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group; and wherein an overbooking limit is based on the group an overbooked CC is in. Example 28 comprises the subject matter of Example 23, wherein the apparatus is configured to transmit at least one CC of the set of CCs from multiple transmission points. Example 29 comprises a method that includes any action or combination of actions as substantially described herein in the Detailed Description. Example 30 comprises a method as substantially described herein with reference to each or any combination of the Figures included herein or with reference to each or any combination of paragraphs in the Detailed Description. Example 31 comprises a wireless device configured to perform any action or combination of actions as substantially described herein in the Detailed Description as included in the wireless device. Example 32 comprises a wireless station configured to perform any action or combination of actions as substantially described herein in the Detailed Description as included in the wireless station. Example 33 comprises a non-volatile computer-readable medium that stores instructions that, when executed, cause the performance of any action or combination of actions as substantially described herein in the Detailed Description. Example 34 comprises an integrated circuit configured to perform any action or combination of actions as substantially described herein in the Detailed Description. Example 35 comprises the subject matter of Example 17, wherein the dividing is further based on subcarrier spacing of the component carriers. Example 36 comprises the subject matter of Example 17, wherein the determined number of non-overlapping CCEs to monitor is a predetermined number. Example 37 comprises the subject matter of Example 19, wherein determining a PDCCH monitoring limit for component carriers of the second group comprises determining a minimum of a predetermined maximum number of spans for a monitoring pattern and a total number of component carriers of the second group divided by a number of component carriers with a shared span pattern. Example 38 comprises the subject matter of Example 37, wherein the determined PDCCH monitoring limit for component carriers with a shared span pattern remains constant within each component carrier. Example 39 comprises the subject matter of Example 37, wherein determining a PDCCH monitoring limit for component carriers of the second group comprises determining a minimum of a predetermined maximum number of non-overlapping CCEs for a monitoring pattern and a total number of non-overlapping CCEs of the second group shared by a number of component carriers with a shared span pattern. Example 40 comprises the subject matter of Example 39, wherein the determined PDCCH monitoring limit for component carriers with a shared span pattern remains constant within each component carrier. Example 41 comprises the subject matter of Example 17, wherein the wireless device is further configured to transmit the determined non-overlapping CCE to monitor to a wireless station. Example 42 comprises the subject matter of Example 17, wherein the determined non-overlapping CCE to monitor is based on configuration information received from the wireless station. Example 43 comprises the subject matter of Example 22, wherein the wireless device is further configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group, and wherein the at least one CC received from multiple transmission point is divided into the second group. Example 44 comprises the subject matter of Example 22, wherein the wireless device is further configured to group CCs received from multiple transmission points based on an alignment of the multiple transmission points. Example 45 comprises the subject matter of Example 23, wherein the dividing is further based on subcarrier spacing of the component carriers. Example 46 comprises the subject matter of Example 23, wherein the determined number of non-overlapping CCEs to monitor is a predetermined number. Example 47 comprises the subject matter of Example 25, wherein determining a PDCCH monitoring limit for component carriers of the second group comprises determining a minimum of a predetermined maximum number of spans for a monitoring pattern and a total number of component carriers of the second group divided by a number of component carriers with a shared span pattern. Example 48 comprises the subject matter of Example 23, wherein the wireless device is further configured to transmit the determined non-overlapping CCE to monitor to a wireless station. Example 49 comprises the subject matter of Example 23, wherein the determined non-overlapping CCE to monitor is based on configuration information received from the wireless station. Example 50 comprises the subject matter of Example 28, wherein the wireless device is further configured to divide the at least three component carriers by grouping the component carriers with both a shared monitoring pattern and a shared starting span into a first set of one or more groups and the other component carriers into a second group, and wherein the at least one CC received from multiple transmission point is divided into the second group. Example 51 comprises the subject matter of Example 28, wherein the wireless device is further configured to group CCs received from multiple transmission points based on an alignment of the multiple transmission points. According to Example 52, a method is disclosed, comprising: configuring a wireless device to access a wireless network using a set of components carriers (CCs); dividing the set of CCs into groups of component carriers based on whether the component carriers share a span pattern and a starting span for monitoring a Physical Downlink Control Channel (PDCCH) of each component carrier; determining a number of non-overlapping control channel elements (CCE) to monitor for each group of component carriers; and configuring the wireless device to monitor the non-overlapping CCEs based on the determined number to monitor for each group. Example 53 comprises the subject matter of Example 49, wherein the set of CCs includes at least three CCs. According to Example 54, a wireless device is disclosed, comprising: an antenna; a radio operably coupled to the antenna; and a processor operably coupled to the radio; wherein the wireless device is configured to: access a wireless network using a set of components carriers (CCs); divide the set of CCs into groups of CCs based on whether the CCs share a monitoring pattern for monitoring a Physical Downlink Control Channel (PDCCH) of each component carrier; determine a number of non-overlapping control channel elements (CCE) to monitor for each group of component carriers; and monitor the non-overlapping CCEs based on the determined number to monitor for each group. Example 55 comprises the subject matter of Example 51, wherein the set of CCs includes at least three CCs. According to Example 56 an apparatus is disclosed, comprising: a processor configured to: configure a wireless device to access a wireless network using a set of components carriers (CCs); divide the set of CCs into groups of CCs based on whether the CCs share a monitoring pattern for monitoring a Physical Downlink Control Channel (PDCCH) of each CC; determine a number of non-overlapping control channel elements (CCE) to monitor for each group of CCs; and configuring the wireless device to monitor the non-overlapping CCEs based on the determined number to monitor for each group. Example 57 comprises the subject matter of Example 52, wherein the set of CCs includes at least three CCs. Yet another exemplary embodiment may include a method, comprising, by a device, performing any or all parts of the preceding Examples. A yet further exemplary embodiment may include a non-transitory computer-accessible memory medium comprising program instructions which, when executed at a device, cause the device to implement any or all parts of any of the preceding Examples. A still further exemplary embodiment may include a computer program comprising instructions for performing any or all parts of any of the preceding Examples. Yet another exemplary embodiment may include an apparatus comprising means for performing any or all of the elements of any of the preceding Examples. Still another exemplary embodiment may include an apparatus comprising a processor configured to cause a device to perform any or all of the elements of any of the preceding Examples. It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users. Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer-readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs. In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of a method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets. In some embodiments, a device (e.g., a UE106, a BS102, a network element600) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms. Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. | 92,416 |
11943700 | DESCRIPTION OF EMBODIMENTS Exemplary embodiments of the present invention are explained below with reference to the accompanying drawings. Furthermore, in the drawings, structural elements having the same function or configuration are indicated by the same or similar reference numerals and the explanation thereof is appropriately omitted. (1) Overall Structural Configuration of Radio Communication System FIG.1is an overall structural diagram of a radio communication system10according to the present embodiment. The radio communication system10includes a user device100(hereinafter, the OF100), 5G system200and 4G system300that support an IP multimedia subsystem (IMS) type communication service, 3G system400that supports a circuit switching (CS) type communication service, IMS500, and CS600. The 5G system200, for example, is a mobile communication system according to New Radio (NR), and includes 5GRAN210and 5G core network220that is connected to the 5GRAN210. The 5GRAN210is a network constituted by a radio base station (gNB) and the like, and for example, executes connection processing with the UE100. The radio base station of the 5GRAN210controls the radio communication with the LIE100in 5G cell230. Note that, even if only one radio base station is shown inFIG.1, the 5GRAN210includes a plurality of the radio base stations and these radio base stations form a plural of the 5G cells. The 5G core network220is a network constituted by a switching station and the like, and, for example, executes an attach processing with the UE100. In addition to the 5GRAN210, the 5G core network220is also connected to 4GRAN310explained later. Note that it can be assumed that the 5G core network220does not support the IMS-type communication service because of the architecture of the network. The 4G system300, for example, is a mobile communication system according to LTE specifications, and includes the 4GRAN (E-UTRAN)310and 4G core network (EPC)320that is connected to the 4GRAN310. The 4GRAN310is a network constituted by a radio base station (eNodeB) and the like, and, for example, executes connection processing with the UE100. The radio base station of the 4GRAN310controls the radio communication with the UE100in 4G cell330. Note that, even if only one radio base station is shown inFIG.1, the 4GRAN310includes a plurality of the radio base stations and these radio base stations form a plurality of the 4G cells. The 4G core network320is a network constituted by a switching station (MME) and the like, and, for example, executes the attach processing with the UE100. The 3G system400includes 3GRAN (UTRAN)410and 3G core network420that is connected to the 3GRAN410. The 3GRAN410is a network constituted by a radio base station (NodeB), a radio network control device (RNC), and the like, and, for example, executes connection processing with the UE100. The radio base station of the 3GRAN410controls the radio communication with the UE100in 3G cell430. Note that, even if only one radio base station is shown inFIG.1, the 3GRAN410includes a plurality of the radio base stations and these radio base stations form a plurality of the 3G cells. The 3G core network420is a network constituted by a switching station (MSC/VLR) and the like, and, for example, executes the attach processing with the UE100. The IMS500is connected to the 5G core network220, and provides the IMS-type communication service to the UE100via the 5GRAN210and the 5G core network220or via the 4GRAN310and the 5G core network220. Similarly, the IMS500is connected to the 4G core network320, and provides the IMS-type communication service to the UE100via the 4GRAN310and the 4G core network320. The CS600is connected to the 3G core network420, and provides the CS-type communication service to the UE100via the 3GRAN410and the 3G core network420. (2) Functional Block Configuration of Radio Communication System A functional block configuration of the radio communication system10is explained below. Specifically, a functional block configuration of the UE100is explained below. A hardware configuration of the UE100will be explained later. FIG.2is a functional block diagram of the UE100. As shown inFIG.2, the UE100includes a radio communication unit110, a connection processing unit120, an attach processing unit130, IMS incoming/outgoing communication processing unit140, a system state detecting unit150, and a cell selecting unit160. The radio communication unit110transmits various signals based on requests received from the connection processing unit120, the attach processing unit130, and the IMS incoming/outgoing communication processing unit140. The radio communication unit110receives various signals from the 5G system200, the 4G system300, or the 3G system400, and transmits the received signals to the connection processing unit120, the attach processing unit130, the IMS incoming/outgoing communication processing unit140, or the system state detecting unit150. The connection processing unit120requests the radio communication unit110to transmit the radio signal so as to transmit a connection request signal to RAN (for example, the 5GRAN210or the 4GRAN310) of a target generation system when the UE100attempts to connect to the target generation system (for example, the 5G system200or the 4G system300) to perform emergency call communication, voice communication, or video call communication via IP packet. In other words, the connection processing unit120transmits the connection request signal to the RAN of the target generation system via the radio communication unit110. The radio communication unit110transmits, based on the received request, the radio signal to the RAN of the target generation system. As it will be explained later, upon instructed by the cell selecting unit160to attempt to connect to the 4G cell330that is selected as the target cell for connection, the connection processing unit120requests the radio communication unit110to transmit the radio signal so as to only transmit the connection request signal for the IMS-type communication service to the target cell for connection. In other words, the connection processing unit120transmits the connection request signal for the IMS-type communication service to the target cell for connection via the radio communication unit110. The radio communication unit110transmits, based on the received request, the radio signal to the 4GRAN310. As an example of the connection request signal, RRC CONNECTION REQUEST can be cited. Upon receiving a connection setup signal from the target generation system via the radio communication unit110, the connection processing unit120establishes radio connection with the target generation system. On the other hand, upon receiving a connection rejection signal or a fallback instruction from the target generation system via the radio communication unit110, the connection processing unit120does not establish the radio connection with the target generation system. As an example of the connection setup signal, RRC CONNECTION SETUP can be cited. As an example of the connection rejection signal, RRC CONNECTION REJECTION can be cited. The attach processing unit130requests the radio communication unit110to transmit the radio signal so as to transmit an attach request signal to a core network (for example, the 5G core network220or the 4G core network320) of the target generation system when the UE100attempts to attach to the target generation system after the radio connection has been established with the target generation system. In other words, the attach processing unit130transmits the attach request signal to the core network of the target generation system via the radio communication unit110. The radio communication unit110transmits, based on the received request, the radio signal to the core network of the target generation system. Upon receiving an attach complete response signal from the target generation system via the radio communication unit110, the attach processing unit130completes the attach processing with the target generation system. On the other hand, upon receiving a non-IMS support notification or the fallback instruction from the target generation system via the radio communication unit110, the attach processing unit130stops executing the attach processing with the target generation system. The IMS incoming/outgoing communication processing unit140requests the radio communication unit110to transmit the radio signal so as to transmit the IMS registration request signal to the IMS500that is connected to the target generation system, when the UE100attempts to execute the IMS registration procedure after the attach processing with the target generation system is completed and before performing the IMS incoming/outgoing communication. In other words, the IMS incoming/outgoing communication processing unit140transmits, via the radio communication unit110, the IMS registration request signal to the IMS500that is connected to the target generation system. The radio communication unit110transmits, based on the received request, the radio signal to the IMS500that is connected to the target generation system. Upon receiving the IMS registration completion signal from the IMS500via the radio communication unit110, the IMS incoming/outgoing communication processing unit140completes the IMS registration procedure. Subsequently, the IMS incoming/outgoing communication processing unit140requests the radio communication unit110to transmit the radio signal so as to transmit an INVITE signal to the IMS500that is connected to the target generation system, when the IMS incoming/outgoing communication is attempted. In other words, the IMS incoming/outgoing communication processing unit140transmits, via the radio communication unit110, the INVITE signal to the IMS500that is connected to the target generation system. The radio communication unit110transmits, based on the received request, the radio signal to the IMS500that is connected to the target generation system, and performs the IMS incoming/outgoing communication via the target generation system. However, in addition to the 4G core network320, the 4GRAN310of the 4G system300is also connected to the 5G core network220. Therefore, the IMS incoming/outgoing communication processing unit140can also execute the IMS registration procedure and IMS incoming/outgoing communication explained above with the IMS500via the 4GRAN310and the 5G core network220. Upon being notified from the connection processing unit120that the connection rejection signal from the 5G system200is received, based on the notification, the system state detecting unit150detects that access to the 5G system200is barred, and transmits a detection signal to the cell selecting unit160. Upon being notified from the attach processing unit130that the non-IMS support notification is received from the 5G system200, based on the notification, the system state detesting unit150detects that the 5G core network220of the 5G system200does not support the IMS-type communication service and transmits the detection signal to the cell selecting unit160. Upon being notified from the connection processing unit120or the attach processing unit130that the fallback instruction is received from the 5G system200, based on the received notification, the system state detecting unit150detects the instruction to perform fallback to the 4G system300and transmits the detection signal to the cell selecting unit160. Upon being notified from the connection processing unit120or the attach processing unit130that the response signal is not received from the 5G system200even after a predetermined time has elapsed, based on the notification, the system state detecting unit150detects that the 5G system200is congested and transmits the detection signal to the cell selecting unit160. The system state detecting unit150receives broadcast information from the 5G system200via the radio communication unit110. Upon detecting that the received broadcast information includes access restriction information, congestion information, non-IMS support information, or fallback instruction information, the system state detecting unit150transmits the detection signal to the cell selecting unit160. As an example of the broadcast information, System Information Block (SIB) can be cited. The system state detecting unit150receives a paging signal from the 5G system200via the radio communication unit110. Upon detecting that the received paging signal includes the access restriction information, the congestion information, the non-IMS support information, or the fallback instruction information, the system state detecting unit150transmits the detection signal to the cell selecting unit160. The access restriction information is the information, via which it is notified that the access to the 5G system200is barred. By using the access restriction information, the 5G system200notifies the UE100that emergency call communication, voice communication, or video call communication via IP packet is restricted in the entire 5G system200or a specific 5G cell. As an example of the access restriction information, Access Class Barring (ACB), Service Specific Access Control (SSAC) Barring, Access Control for general Data Connectivity (ACDC), and User Access Control (UAC) can be cited. The congestion information is the information via which it is notified that the 5G system200is congested. By using the congestion information, the 5G system200notifies the UE100that congestion has occurred in the 5GRAN210, in the 5G core network220, or between the 5GRAN210and the 5G core network220. The non-IMS support information is the information via which it is notified that the 5G core network220of the 5G system200does not support the IMS-type communication service. By using the non-IMS support information, the 5G system200notifies the UE100that the 5G core network220does not support the IMS-type communication service. The fallback instruction information is the information via which fallback to the 4G system300is instructed. By using the fallback instruction information, the 5G system200instructs the UE100to perform fallback to the 4G system300. When the received broadcast information or the paging signal includes frequency information having information on a plurality of the frequencies used by the plurality of the 4G cells in the 4G system300that supports the IMS-type communication service, the system state detecting unit150notifies the cell selecting unit160of the frequency information. When the received broadcast information or the paging signal includes cell information having information on the plurality of the 4G cells that are formed near the 5G cell230of the 5G system200in which the UE100resides, in the 4G system300that supports the IMS-type communication service, the system state detecting unit150notifies the cell selecting unit160of the cell information. Upon receiving the detection signal from the system state detecting unit150, the cell selecting unit160selects, as the target cell for connection, the 4G cell330of the 4G system300that supports the IMS-type communication service. Specifically, the cell selecting unit160selects, the target cell for connection, the 4G cell330in the 4G system300that uses a different frequency than that used by the 5G cell230of the 5G system200in which the UE100resides. Upon receiving the detection signal from the system state detecting unit150when the frequency information is notified from the system state detecting unit150, the cell selecting unit160selects, as the target cell for connection, the 4G cell330that uses a different frequency than that used by the 5G cell230, based on the frequencies included in the frequency information. Upon selecting the 4G cell330as the target cell for connection, the cell selecting unit160instructs the connection processing unit120to attempt to connect to the 4G system300. Alternatively, upon receiving the detection signal from the system state detecting unit150, in the 4G system300, the cell selecting unit160can select, as the target cell for connection, the 4G cell330formed near the 5G cell230of the 5G system200in which the UE100resides. In such a case, a part or an entire area of the 4G cell330of the 4G system300that is formed near the 5G cell230of the 5G system200can overlap with that of the 5G cell230. Upon receiving a detection signal from the system state detecting unit150when the cell information is notified from the system state detecting unit150, the cell selecting unit160selects the target cell for connection from among the plurality of the 4G cells of the 4G system300included in the cell information. (3) Operation of Radio Communication System Operation of the radio communication system10is explained below. Specifically, operations related to the processing performed by the UE100to fall back from the 5G system200to the 4G system300will be explained. (3.1) Fallback Processing FIG.3shows a processing flow of fallback performed by the UE100. As shown inFIG.3, the UE100determines whether fallback from the 5G system200to the 4G system300is to be started (Step S10). Specifically, in the 5G cell230of the 5G system200, the UE100determines whether the access restriction to the 5G system200, congestion of the 5G system200, non-support for the IMS by the 5G core network220, or fallback instruction is detected. More specifically, upon detecting that at least one of the following conditions is fulfilled, the UE100determines to perform fallback to the 4G system300: (1) the system state detecting unit150is notified from the connection processing unit120that the connection rejection signal is received from the 5G system200; (2) the system state detecting unit150is notified from the attach processing unit130that the non-IMS support notification is received from the 5G system200; (3) the system state detecting unit150is notified from the connection processing unit120or the attach processing unit130that the response signal is not received from the 5G system even after the predetermined time has elapsed; (4) the system state detecting unit150is notified from the connection processing unit120or the attach processing unit130that the fallback instruction is received from the 5G system200; and (5) the system state detecting unit150detects that the broadcast information or the paging signal received from the 5G system200via the radio communication unit110includes the access restriction information, the congestion information, the non-IMS support information, or the fallback instruction information. Upon determining that fallback to the 4G system300is to be started, the UE100selects the 4G cell330of the 4G system300as the target cell for connection (Step S20). Specifically, upon receiving from the system state detecting unit150the detection signal that indicates that at least one of the conditions explained above is fulfilled, the cell selecting unit160selects, as the target cell for connection, the 4G cell330of the 4G system300that uses a different frequency than that used by the 5G cell230of the 5G system200in which the UE100resides. When the frequency information included in the broadcast information or the paging signal received from the 5G system200is notified from the system state detecting unit150, the cell selecting unit160selects, as the target cell for connection, the 4G cell330that uses a different frequency than that used by the 5G cell230, based on the frequencies included in the frequency information. However, even if the 3G system400that supports the CS-type communication service is available for fallback, the UE100avoids selecting the 3G cell430of the 3G system400as the target cell for connection. Specifically, when the system state detecting unit150receives via the radio communication unit110the information that indicates whether fallback from the 5G system200to the 4G system300that supports the IMS-type communication service or the 3G system400that supports the CS-type communication services is allowed, the UE100can avoid selecting the 3G cell430of the 3G system400as the get cell for connection. The UE100transmits the connection request signal to the 4G cell330that is selected as the target cell for connection (Step S30). Specifically, the connection processing unit120requests the radio communication unit110to transmit the radio signal so as to transmit the connection request signal to the 4G system330. The radio communication unit110transmits, based on the received request, the radio signal to the 4GRAN310of the 4G system300. Upon connecting to the 4G system300, the UE100executes IMS incoming/outgoing communication with the IMS500via the 4GRAN310and the 4G core network320(Step S40). Specifically, upon receiving the connection setup signal from the 4GRAN310via the radio communication unit110, the connection processing unit120establishes the radio connection with the 4G system300. The attach processing unit130requests the radio communication unit110to transmit the radio signal so as to transmit the attach request signal after the UE100has established the radio connection with the 4G system300. The radio communication unit110transmits, based on the received request, the radio signal to the 4G core network320of the 4G system300. Upon receiving the attach complete response signal from the 4G core network320via the radio communication unit110, the attach processing unit130completes the attach processing with the 4G system300. The IMS incoming/outgoing communication processing unit140execute an IMS registration procedure with the IMS500via the 4GRAN310and the 4G core network320after the UE100has completed the attach processing with the 4G system300, and requests the radio communication unit110to transmit the radio signal so as to transmit the INVITE signal. The radio communication unit110transmits, based on the received request, the radio signal to the IMS500and performs the IMS incoming/outgoing communication with the IMS500via the 4GRAN310and the 4G core network320. In addition, when the 5G core network220supports the IMS-type communication service, the UE100can execute the IMS incoming/outgoing communication with the IMS500via the 4GRAN310and the 5G core network220. Moreover, when the UE100is unable to connect to the 4G system300, the UE100avoids selecting the30cell430of the 3G system400as the target cell for connection even when the 3G system400that supports the CS-type communication service is available for fallback. Specifically, when the system state detecting unit150receives via the radio communication unit110the information that indicates whether fallback from the 5G system200or the 4G system300to the 3G system400that supports the CS-type communication service is allowed, the UE100can avoid selecting the 3G cell430of the 3G system400as the target cell for connection. On the other hand, upon determining that fallback to the 4G system300is not to be started, the UE100performs the IMS incoming/outgoing communication with the IMS500via the 5GRAN210and the 5G core network220(Step S50). (3.1.1) Operation Example 1 FIG.4shows a processing sequence of fallback from the 5G system200to the 4G system300according to Operation Example 1. In the present operation example, when the UE100receives RRC CONNECTION REJECTION or the fallback instruction from the 5GRAN210, or does not receive the response signal from the 5GRAN210even after the predetermined time has elapsed, the UE100performs fallback to the 4G system300. When a connection request for performing emergency call communication, voice communication, or video call communication via IP packet occurs in the application layer of the UE100in a state in which the UE100has not established the radio connection with the 5G system200(for example, IDLE state or RRC Inactivity state), the UE100attempts to connect to the 5G system200. Specifically, in the 5G cell230of the 5G system200, the UE100transmits RRC CONNECTION REQUEST to the 5GRAN210(Step S100). When emergency call communication, voice communication, or video call communication via IP packet is restricted in the entire 5G system200or the 5G cell230, the UE100receives RRC CONNECTION REJECTION from the 5GRAN210(Step S110-a). Moreover, when the 5G system200instructs the UE100to perform fallback to the 4G system300, the UE100receives the fallback instruction from the 5GRAN210(Step S110-a) Alternatively, when congestion has occurred in, the 5GRAN210, the UE100does not receive the response signal from the 5GRAN210even after the predetermined timed has elapsed (Step S110-b) When the UE100receives RRC CONNECTION REJECTION or the fallback instruction from the 5GRAN210or does not receive the response signal from the 5GRAN210even after the predetermined time has elapsed, the UE100starts to perform fallback to the 4G system300. Specifically, the UE100selects, as the target cell for connection, the 4G cell330of the 4G system300that uses a different frequency than that used by the 5G cell230(Step S120). In the 4G cell330that is selected as the target cell for connection, the UE100transmits RRC CONNECTION REQUEST to the 4GRAN310(Step S130). Upon receiving RRC CONNECTION SETUP from the 4GRAN310(Step S140), the UE100establishes the radio connection with the 4G system300. Subsequently, the UE100transmits the attach request signal to the 4G core network320(Step S150), and after a communication bearer is configured in the 4G core network320(Step S160), the UE100receives the attach complete response signal from the 4G core network320(Step S170). Once the attach processing with the 4G core network320is completed, the UE100executes the IMS registration procedure with the IMS500via the 4GRAN310and the 4G core network320(Step S180). Subsequently, the UE100transmits the INVITE signal to the IMS500via the 4GRAN310and the 4G core network320(Step S190), and performs the IMS incoming/outgoing communication. (3.1.2) Operation Example 2 FIG.5shows a processing sequence of fallback from the 5G system200to the 4G system300according to Operation Example 2. In the present operation example, when the UE100receives the non-IMS support notification or the fallback instruction from the 5G core network220, or does not receive the response signal from the 5G core network220even after the predetermined time has elapsed, the UE100performs fallback to the 4G system300. When the connection request for performing emergency call communication, voice communication, or video call communication via IP packet occurs in the application layer of the UE100in the state in which the UE100has not established the radio connection with the 5G system200(for example, IDLE state or RRC Inactivity state), the UE100attempts to connect to the 5G system200. Specifically, in the 5G cell230of the 5G system200, the UE100transmits RRC CONNECTION REQUEST to the 5GRAN210(Step S200). Upon receiving RRC CONNECTION SETUP from the 5GRAN210(Step S210), the UE100establishes the radio connection with the 5G system200. Subsequently, the UE100transmits the attach request signal to the 5G core network220(Step S220). When the 5G core network220does not support the IMS-type communication service, the UE100receives the non-IMS support notification from the SG core network220(Step S230-a). Moreover, when the 5G system200instructs the UE100to perform fallback to the 4G system300, the UE100receives the fallback instruction from the 5G core network220(Step S230-a). Alternatively, when congestion has occurred in the 5G core network220, the UE100does not receive the response signal from the 5G core network220even after the predetermined timed has elapsed (Step S230-b) In a response to a location registration request in a location registration procedure with a network that is performed based on the reception of the attach request signal, if the network notifies that the 5G core network220does not support the IMS-type communication service, the 5G core network220can transmit the non-IMS support notification to the UE100. When the UE100receives the non-IMS support notification or the fallback instruction from the 5G core network220or does not receive the response signal from the 5G core network220even after the predetermined time has elapsed, the UE100starts to perform fallback to the 4G system300. Specifically, the UE100selects, as the target cell for connection, the 4G cell330of the 4G system300that uses a different frequency than that used by the 5G cell230(Step S240). In the present operation example, because the processing performed at Steps S250to S310is the same as that performed at Steps S130to S190of Operation Example 1, explanation thereof is omitted. (3.1.3) Operation Example 3 FIG.6shows a processing sequence of fallback from the 5G system200to the 4G system300according to Operation Example 3. In the present operation example, the UE100receives the broadcast information or the paging signal from the 5GRAN210, and performs fallback to the 4G system300when the access restriction information, the congestion information, the non-IMS support information, or the fallback instruction information is included in the received broadcast information or the paging signal. Before and after the timing at which the connection request for performing emergency call communication, voice communication, or video call communication via IP packet occurs in the application layer of the UE100in a state in which the UE100has not established the radio connection with the 5G system200(for example, the IDLE state or the RRC Inactivity state), the UE100receives the broadcast information or the paging signal from the 5G system200. Specifically, in the 5G cell230of the 5G system200, the UE100receives the broadcast information or the paging signal from the 5GRAN210(Step S400). When emergency call communication, voice communication, or video call communication via IP packet is restricted in the entire 5G system200or the 5G cell230, the 5GRAN210includes the access restriction information in the broadcast information or the paging signal. When the congestion has occurred in the 5GRAN210, in the 5G core network220, or between the 5GRAN210and 5G core network220, the 5GRAN210includes the congestion information in the broadcast information or the paging signal. When the 5G core network220does not support the IMS-type communication service, the 5GRAN210includes the non-IMS support information in the broadcast information or the paging signal. When the 5G system200instructs the UE100to perform fallback to the 4G system300, the 5GRAN210includes the fallback instruction information in the broadcast information or the paging signal. Upon detecting that the access restriction information, the congestion information, the non-IMS support information, or the fallback instruction information is included in the received broadcast information or the paging signal (Step S410), the UE100starts performing fallback to the 4G system300. Specifically, the UE100selects, as the target cell for connection, the 4G cell330of the 4G system300that uses a different frequency than that used by the 5G cell230(Step S420). When the frequency information is included in the received broadcast information or the paging signal, the UE100selects, as the target cell for connection, the 4G cell330that uses a different frequency than that used by the 5G cell230, based on the frequencies included in the frequency information. In the present operation example, because the processes performed at Steps S430to S490are the same as that performed at Steps S130to S190of Operation Example 1, the explanation thereof is omitted. (3.1.4) Operation Example 4 FIG.7shows a processing sequence of fallback from the 5G system200to the 4G system300according to Operation Example 4. In the present operation example, when the 5G core network220supports the IMS-type communication service, the UE100executes the IMS registration procedure and the IMS incoming/outgoing communication with the IMS500via the 4GRAN310and the 5G core network220. Because the processes performed at Steps S500to S520shown inFIG.7are the same as those performed at Steps S120to S140shown inFIG.4, those performed at Steps S240to S260shown inFIG.5, and those performed at Steps S420to S440shown inFIG.6, the explanation thereof is omitted. Upon establishing the radio connection with the 4G system300, the UE100transmits the attach request signal to the 5G core network220(Step S530), and after the communication bearer is configured in the 5G core network220(Step S540), the UE100receives the attach complete response signal from the 5G core network220(Step S550). Once the attach processing with the 5G core network220is completed, the UE100executes the IMS registration procedure with the IMS500via the 4GRAN310and the 5G core network220(Step S560). Subsequently, the UE100transmits the INVITE signal to the IMS SOO via the 4GRAN310and the 5G core network220(Step S570), and performs the IMS incoming/outgoing communication. (3.2) Modifications of Fallback Processing FIG.8shows a modification of the flow of fallback processing performed by the UE100. Specifically,FIG.8shows a transition of a core network performed by the UE100in a configuration in which the 4GRAN310is connected to the 4G core network320and the 5G core network220. As shown inFIG.8, the UE100determines whether the transition from the 5G core network220to the 4G core network320is to be started (Step S610). Specifically, the system state detecting unit150of the UE100determines whether the congestion in the 5G core network220or the non-support for IMS in the 5G core network220is detected in the 4G cell330. In addition, when the system state detecting unit150detects that the congestion information or the non-IMS support information is included in the broadcast information or the paging signal received from the 4GRAN310via the radio communication unit110in the 4G cell330, the UE100can determine that the transition from the 5G core network220to the 4G core network320is to be started. Upon determining that the transition to the 4G core network320is to be started, the UE100selects, as the target cell for connection, the 4G cell330in which the UE100resides (Step S620). Specifically, upon receiving from the system state detecting unit150the detection signal that indicates that the 5G core network220is congested or the 5G core network220does not support IMS, the cell selecting unit160selects, as the target cell for connection, the 4G cell330in which the UE100resides. The UE100transmits the connection request signal to the 4G cell330that is selected as the target cell for connection (Step S630). Specifically, the connection processing unit120requests the radio communication unit110to transmit the radio signal, so a to transmit the connection request signal to the 4G cell330. The radio communication unit110transmits, based on the received request, the radio signal to the 4GRAN310. Upon connecting to the 4GRAN310, the UE100performs the IMS incoming/outgoing communication with the IMS500via the 4GRAN310and the 4G core network320(Step S640). Specifically, upon receiving the connection setup signal from be 4GRAN310via the radio communication unit110, the connection processing unit120establishes the radio connection with the 4GRAN310. The attach processing unit130request the radio communication unit110to transmit the radio signal so as to transmit the attach request signal after the UE100has established the radio connection with the 4GRAN310. The radio communication unit110transmits, based on the received request, the radio signal to the 4G core network 4G. Upon receiving the attach complete response signal from the 4G core network320via the radio communication unit110, the attach processing unit130completes the attach processing with the 4G core network320. After the UE100has completed the attach processing with the 4G core network320, the IMS incoming/outgoing communication processing unit140executes the IMS registration procedure with the IMS500via the 4GRAN310and the 4G core network320, and requests the radio communication unit110to transmit the radio signal so as to transmit the INVITE signal. The radio communication unit110transmits, based on the received request, the radio signal to the IMS500and performs the IMS incoming/outgoing communication with the IMS500via the 4GRAN310and the 4G core network320. On the other hand, upon determining that the transition to the 4G core network320is not to be started, the UE100performs the IMS incoming/outgoing communication with the IMS500via the 4GRAN310and the 5G core network220(Step S650). (4) Effects and Advantages According to the embodiments explained above, upon transmitting the connection request signal to the 5GRAN210in the 5G cell230of the 5GRAN210and receiving a connection rejection signal from the 5GRAN210, the UE100selects the 4G cell330of the 4G system300as the target cell for connection and starts the processing for fallback to the 4G system300. In this manner, when the connection to the 5G system200is rejected, instead of performing fallback to the 3G system400, the UE100autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300. Therefore, because, in the embodiments explained above, even when the connection to the 5G system200is rejected, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. Upon transmitting the connection request signal to the 5GRAN210in the 5G cell230of the 5GRAN210and receiving the fallback instruction from the 5GRAN210, the UE100selects the 4G cell330of the 4G system300as the target cell for connection and starts the processing for fallback to the 4G system300. In this manner, when fallback to the 4G system300is instructed, instead of performing fallback, to the 3G system400, the UE100autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300. Therefore, because, in the embodiments explained above, when fallback to the 4G system300is instructed, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. Upon transmitting the connection request signal to the 5GRAN210in the 5G cell230of the 5GRAN210and not receiving a response signal from the 5GRAN210after the predetermined time has elapsed, the UE100selects the 4G cell330of the 4G system300as the target cell for connection and starts the processing for fallback to the 4G system300. In this manner, when the 5G system200is congested, instead of performing fallback to the 3G system400, the UE100autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300. Therefore, because, in the embodiments explained above, even when the 5G system200is congested, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. Upon transmitting the attach request signal to the 5G core network220in the 5G cell230of the 5GRAN210and receiving the non-IMS support notification from the 5G core network220, the UE100selects the 4G cell330of the 4G system300as the target cell for connection and starts the processing for fallback to the 4G system300. In this manner, when the 5G core network220does not support the IMS-type communication service, instead of performing fallback to the 3G system400, the UE100autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300. Therefore, because, in the embodiments explained above, even when the 5G core network220does not support the IMS-type communication service, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. Upon transmitting the attach request signal to the 5G core network220in the 5G cell230of the SGRAN210and receiving the fallback instruction from the 5G tore network220, the UE100selects the 4G cell330of the 4G system300as the target cell for connection and starts the processing for fallback to the 4G system300. In this manner, when fallback to the 4G system300is instructed, instead of performing fallback to the 3G system400, the UE100autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300. Therefore, because, in the embodiments explained above, when fallback to the 4G system300is instructed, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. Upon transmitting the attach request signal to the 5G core network220in the 5G cell230of the 5GRAN210and not receiving the response signal from the 5G core network220even after the predetermined time has elapsed, the UE100selects the 4G cell330of the 4G system300as the target cell for connection and starts the processing for fallback to the 4G system300. In this manner, when the 5G system200is congested, instead of performing fallback to the 3G system400, the UE100autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300. Therefore, because, in the embodiments explained above, even when the 5G system200is congested, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. Upon receiving broadcast information or the paging signal that, includes the access restriction information, the congestion information, the non-IMS support information, or the fallback instruction in the 5G cell230of the 5GRAN210, the UE100selects the 4G cell330of the 4G system300as the target cell for connection and starts the processing for fallback to the 4G system300. In this manner, when the access to the 5G system200is barred, the 5G system200is congested, the 5G core network220does not support the IMS-type communication service, or fallback to the 4G system300is instructed, instead of performing fallback to the 3G system400, the UE100does not attempt to connect to the 5G system200, and autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300. Therefore, because, in the embodiments explained above, even when the access to the 5G system200is barred, the 5G system200is congested, the 5G core network220does not support the IMS-type communication service, or when fallback to the 4G system300is instructed, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to CS-type service change communication service from the IMS-type service to CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. Moreover, when the broadcast information or the paging signal received in the 5G cell230of the 5GRAN210includes the frequency information, the DE100selects, based on the frequencies included in the frequency information, the 4G cell330that uses a different frequency than that used by the 5G cell230as the target cell for connection. Therefore, time required for selecting the target cell for connection can be shortened, and as a result, time required for performing fallback can be further shortened. In a configuration in which the 4GRAN310is connected to the 4G core network320and the 5G core network220, upon detecting in the 4G cell330that the 5G core network220is congested or the 5G core network220does not support the IMS, the UE100selects, as the target cell for connection, the 4G cell330in which the UE100resides, and starts the transition from the 5G core network220to the 4G core network320. In this manner, when the 5G core network220is congested or the 5G core network220does not support the IMS-type communication service, instead of performing fallback to the 3G system400, the UE100autonomously selects the 4G cell330of the 4G system300that supports the IMS-type communication service and performs fallback to the 4G system300to perform incoming/outgoing communication of the IMS-type communication service via the 4GRAN310and the 4G core network320that is connected to the 4GRAN310. Therefore, because, in the embodiments explained above, even when the 5G core network220is congested or the SG core network220does not support the IMS-type communication service, it is not necessary to perform fallback to the 4G system300at the initiative of the 5G system200and change communication service from the IMS-type service to the CS-type service, time required to perform fallback can be shortened. As a result, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. (5) Other Embodiments The present invention has been explained in detail by using the above mentioned embodiments; however, it is self-evident to a person skilled in the art that the present invention is not limited to the embodiments explained herein and that the embodiments can be modified or improved in various ways. For example, even if fallback to the 4G system300is explained in Operation Examples 1 to 4 explained above, the fallback destination system is not limited to the 4G system300. As long as the UE100can autonomously select the target cell for connection and perform fallback while retaining the IMS-type communication service as the communication service, fallback can be performed to other systems. Moreover, the block diagram used for explaining the embodiments (FIG.2) shows a functional block diagram. Those functional blocks (structural components) can be realized by a desired combination of hardware and/or software. Means for realizing each functional block is not particularly limited. That is, each functional block may be realized by one device combined physically and/or logically. Alternatively, two or more devices separated physically and/or logically may be directly and/or indirectly connected (for example, wired and/or wireless) to each other, and each functional block may be realized by these plural devices. Furthermore, the UE100explained above can function as a computer that performs the fallback processing of the present invention.FIG.9is a diagram showing an example of a hardware configuration of the UE100. As shown inFIG.9, the UE100can be configured as a computer device including a processor1001, a memory1002, a storage1003, a communication device1004, an input device1005, an output device1006, and a bus1007. The functional blocks of the UE100(seeFIG.2) can be realized by any of hardware elements of the computer device or a desired combination of the hardware elements. The processor1001, for example, operates operating system to control the entire computer processor1001can be configured with a central processing unit (CPU) including an interface with a peripheral device, a control device, a computing device, a register, and the like. The memory1002is a computer readable recording medium and is configured, for example, with at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. The memory1002can be called register, cache, main memory (main memory), and the like. The memory1002can store therein a computer program (computer program codes), software modules, and, the like that can execute the method according to the above embodiments. The storage1003is a computer readable recording medium. Examples of the storage1003include at least one of an optical disk such as CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray (Registered Trademark) disk), a smart card, a flash memory (for example, a card, a stick, a key drive), a floppy (Registered Trademark) disk, a magnetic strip, and the like. The storage1003can be called an auxiliary storage device. The recording medium can be, for example, a database including the memory1002and/or the storage1003, a server, or other appropriate medium. The communication device1004is hardware (transmission/reception device) capable of performing communication between computers via a wired and/or wireless network. The communication device1004is also called, for example, a network device, a network controller, a network card, a communication module, and the like. The input device1005is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, and the like) that accepts input from the outside. The output device1006is an output device (for example, a display, a speaker, an LED lamp, and the like) that outputs data to the outside. Note that, the input device1005and the output device1006may be integrated (for example, a touch screen). In addition, the respective devices, such as the processor1001and the memory1002, are connected to each other with the bus1007for communicating information there among. The bus1007can be constituted by a single bus or can be constituted by separate buses between the devices. In addition, the manner of notification of information is not limited to the one explained in the embodiments, and the notification may be performed in other manner. For example, the notification of information can be performed by physical layer signaling (for example, DCI (Downlink Control information), UCI (Uplink Control Information)), upper layer signaling (for example, RRC signaling, MAC (Medium Access Control) signaling, broadcast information (NIB (Master Information Block), SIB (System information Block)), other signals, or a combination thereof. In addition, the RRC signaling can be called an RRC message, and the RRC signaling can be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, and the like. Furthermore, the input/output information can be stored in a specific location (for example, a memory) or can be managed in a management table. The information to be input/output can be overwritten, updated, or added. The information can be deleted after outputting. The inputted information can be transmitted to another device. The order of the sequences, flowcharts, and the like in the embodiments can be rearranged unless there is a contradiction. Moreover, in the embodiments explained above, the specific operations performed by the target generation RAN and the core network can be performed by another network node (device). Moreover, functions of the target gene ration RAN and the core network can be provided by combining a plurality of other network nodes. Moreover, the terms used in this specification and/or the terms necessary for understanding the present specification can be replaced with terms having the same or similar meanings. For example, a channel and/or a symbol can be replaced with a signal (signal) if that is stated. Also, the signal can be replaced with a message. Moreover, the terms “system” and “network” can be used interchangeably. Furthermore, the used parameter and the like can be represented by an absolute value, can be expressed as a relative value from a predetermined value, or can be represented by corresponding other information. For example, the radio resource can be indicated by an index. The target generation base station can accommodate one or more (for example, three) cells (also called sectors) In a configuration in which the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas. In each such a smaller area, communication service can be provided by a base station subsystem (for example, a small base station for indoor use Remote Radio Head). The term “cell” or “sector” refers to a part or all of the coverage area of a base station and/or a base station subsystem that performs communication service in this coverage. In addition, the terms “base station”, “cell”, and “sector” can be used interchangeably in the present specification. The base station can also be referred to as a fixed station, NodeB, eNodeB (eNB), an access point, a femtocell, a small cell, and the like. The UE100is called by the persons skilled in the art as a subscriber station, a mobile unit, a subscriber unit, a radio unit, a remote unit, a mobile device, a radio device, a radio communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a radio terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or with some other suitable term. As used herein, the phrase “based on” does not mean “based only on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on”. Furthermore, the terms “including”, “comprising”, and variants thereof are intended to be inclusive in a manner similar to “having”. Furthermore, the term “or” used in the specification or claims is intended not to be an exclusive disjunction. Any reference to an element using a designation such as “first”, “second”, and the like used in the present specification generally does not limit the amount or order of those elements. Such designations can be used in the present specification as a convenient way to distinguish between two or more elements. Thus, the reference to the first and second elements does not imply that only two elements can be adopted, or that the first element must precede the second element in some or the other manner. Throughout the present specification, for example, during translation, if articles such as “a”, “an”, and “the” in English are added, these articles shall include plurality, unless it is clearly indicated that it is not so according to the context. As described above, the details of the present invention have been disclosed by using the embodiments of the present invention. However, the description and drawings which constitute part of this disclosure should not be interpreted so as to limit the present invention. From this disclosure, various alternative embodiments, examples, and operation techniques will be apparent to a person skilled in the art. For example, the present invention can be applied. to a radio communication system in which a first system and a second system that support the IMS-type communication service respectively correspond to the 4G system300and the 5G system200. Specifically, in the 4G cell330of the 4G system300, upon detecting that the 4G core network320is congested, the UE100selects the 5G cell230of the 5G system200as the target cell for connection. Upon selecting the target cell for connection, the UE100transmits the connection request signal for the IMS-type communication service to the selected 5G cell230. Alternatively, in the 4G cell330of the 4G system300, when the UE100detects that the 4G core network320is congested, in a state in which the UE100is connected to the 4G cell330, the UE100can transmit a request to the 4GRAN310to perform communication with the IMS500via the 5G core network220that is connected to the 4GRAN310, INDUSTRIAL APPLICABILITY According to the user device explained above, the present invention is useful in that, even when performing fallback from a first system to a system other than the first system, service quality of communication that requires real time performance such as emergency calls, voice communication, and video calling can be maintained. EXPLANATION OF REFERENCE NUMERALS 10radio communication system100UE120connection processing unit150system state detecting unit160cell selecting unit2005G system2105GRAN2205G core network2305G cell3004G system3104GRAN3204G core network3304G cell500IMS | 57,940 |
11943701 | DETAILED DESCRIPTION The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims. Some embodiments are directed to access point (AP) station (STA) (AP STA) that may be part of an AP multi-link device (MLD). The AP MLD may comprise one or more other AP stations (STAs) (AP STAs). In these embodiments, the AP STA may be configured as a reporting AP. When configured as reporting AP, the AP STA may encode a BSS Transition Management (BTM) request frame for transmission to one or more associated non-AP stations (STAs). The BTM request frame may include a neighbor report element encoded to include information about one or more neighbor APs. In some embodiments, the neighbor report element may indicate whether the one or more neighbor APs identified in the neighbor report element are part of an AP MLD and, when a neighbor AP is indicated to be part of an AP MLD whether the reporting AP is part of the indicated AP MLD (i.e., whether the AP MLD is the same AP MLD that the reporting AP is part of). In some embodiments, the AP STA may decode a reassociation frame from one of the non-AP STAs for transition from one of the AP STAs of the AP MLD to one of the neighbor APs. These embodiments are described in more detail below. In some embodiments, the one or more associated non-AP STAs may be associated with one of the AP STAs of the AP MLD. In some embodiments, some of the one or more associated non-AP STAs may be part of a non-AP MLD, the AP MLD and the non-AP MLD comprising logical entities. These embodiments are described in more detail below. In some embodiments, the AP MLD is configured for multi-link operation. In these embodiments, two or more links with the non-AP MLD may be aggregated in which each of the aggregated links use a same traffic identify (TID). In some embodiments, the reassociation frame may be to initiate a fast BSS transition protocol. In some embodiments, the reassociation frame may be received from one of the non-AP STAs for transition to one of the neighbor APs that are indicated to be part of the same AP MLD as the reporting AP. These embodiments are described in more detail below. In some embodiments, the BTM frame is a BTM request frame. In some embodiments, the BTM frame may be a BTM query frame. In some embodiments, the BTM frame may be a BTM response frame. These embodiments are described in more detail below. In some embodiments, when the reporting AP is an extremely high throughput (EHT) AP, the AP STA may set an EHT BSSID information field in the neighbor report element to indicate that the AP is an EHT AP and part of an AP MLD. In some of these embodiments, all EHT APs may be part of a AP MLD. Some embodiments are directed to a non-access point (AP) station (STA) (non-AP STA) that may be part of STA multi-link device (MLD). In these embodiments, the non-AP STA may decode a BSS Transition Management (BTM) request frame from an AP STA of an AP MLD comprising one or more APs. The BTM request frame may include a neighbor report element that includes information about one or more neighbor APs. In these embodiments, the neighbor report element may indicate whether the one or more neighbor APs identified in the neighbor report element are part of an AP MLD and, when a neighbor AP is indicated to be part of an AP MLD whether the reporting AP is part of the indicated AP MLD (i.e., whether the AP MLD is the same AP MLD that the reporting AP is part of). In these embodiments, the non-AP STA may encode a reassociation frame for transmission to one of the AP STAs of the AP MLD identified in the neighbor report element for reassociation. These embodiments are described in more detail below. Some embodiments are directed to a mechanism for multi-band flow control. One of the main features in the scope of EHT is to enable Multi-band data aggregation. A typical scenario for MAC aggregation is shown inFIG.1A, where AP and STA have multiple interfaces to exchange data simultaneously. For example, AP and STA can negotiated frames related to TID1, such as MU-BAR, BAR, data frame, to be transmitted simultaneously across different interfaces. An example at a specific time frame is shown inFIG.1B. To enable Multi-band Aggregation operation, we have suggested the following: Allow shared transmit buffer control on transmitter side and receive reordering buffer control on receiver side for a TID across the interfaces Allow BA Bitmap size of a TID across interfaces different from the shared buffer size In IEEE 802.11ad, a common problem for receiver to process packets is that the PHY data rate is much higher than the speed of MAC to pass up data. As a result, 11ad introduces flow control as described below and illustrated inFIGS.2A and2B. Rx side has additional received reordering buffer pointer WinTailB to record the value of the Sequence Number field (SN) of the first (in order of ascending sequence number) MSDU or A-MSDU that has not yet been delivered to the next MAC process Rx side has record of the highest SN received in the current reception range (WinHeadB) Rx side signals to Tx side about the remaining buffer space (WinCapacityB=WinTailB+BufSizeB−WinHeadB) Tx side controls the number of packets sending to the receiver (Not beyond WinLimitO=MostSuccSN+WinCapacityO), where MostSuccSN is the highest SN of positively acknowledged MPDUs For details, see IEEE 802.11ad 10.24.11.4 Receive Reordering Buffer with flow control operation. Processing Delay Consideration in Multi-Band Implementation: Due to various implementation choices that may exist to realize the MAC aggregation feature, there may be a processing delay for an AP or a STA to process frames coming in different interfaces. For example, for a STA, the delay to process the frames from interface 1 may have delay 0, and the delay to process the frames from interface 2 may be 3 ms. The various embodiments address the following two issues: Issue 1: Since AP and STA can certainly negotiate more than two interfaces to transmit, the sum data rate that can arrive at a specific amount of time is huge. In this case, the STA may have slower speed of passing up received MSDU or A-MSDU to the next MAC process than the speed of arriving data. Issue 2: In legacy Wi-Fi Operation, the order of processing the frames is the same as the order of the arriving time of the frames. In multi-band operation, due to different processing delay in different interfaces, the order of processing the frames is then not the same as the order of the arriving time of the frames. We provide various examples below to demonstrate the potential problems due to these processing time difference. Assume that AP and STA negotiate TID1 to be aggregated across two interfaces. Assume that the buffer size is 512, and BA bitmap size is 256 for each interface. Assume that the sequence number for data transmission starts with 0. Assume that the processing delay of interface 1 is 0, and the processing delay of interface 2 is 3 ms to 10 ms. (Note that it is basically impossible to get a rough idea about the value of processing time at this point.) It is however expected that the value will be bounded. Example 1 Assume that somehow, data with sequence number 1 to 511 is received, but data with sequence number 0 is not received. Assume that AP sends data with SN 0 in interface 2 and sends data with SN 512 in interface 1 as shown inFIG.3. Note that although data with SN 0 arrives earlier in interface 2 than data with SN 512 in interface 1, data with SN 0 is processed later than data with SN 512 in interface 2. When STA processed data with SN 512 in interfaces 2, the buffer is required to move one space to drop the reception of data with SN 0. As a result, when data with SN 0 is processed later, the data with SN 0 is going to be dropped. Example 2 Assume that somehow, data with sequence number 1 to 511 is received, but data with sequence number 0 is not received. Assume that AP sends data with SN 0 in interface 2 and sends BAR with SN 1 in interface 1 as shown inFIG.4. Note that although data with SN 0 arrives earlier in interface 2 than BAR with SN 1 in interface 1, data with SN 0 is processed later than BAR with SN 1 in interface 2. When STA processed BAR with SN 1 in interfaces 2, the buffer is required to move one space to drop the reception of data with SN 0. As a result, when data with SN 0 is processed later, the data with SN 0 is going to be dropped. Example 3 Assume that AP sends data with SN 0 to 255 in interface 2 and sends data with SN 256 to 511 in interface 1 as shown inFIG.5Note that although data with SN 0 to 255 arrives the same time in interface 2 as data with SN 256 to 511 in interface 1, data with SN 0 to 255 is processed later than data with SN 256 to 511 in interface 2. Now, if data with SN 512 to 767 are sent right after data with SN 256 to 511 in interface 1. When STA processed data with SN 512 to 767 in interface 1, the buffer is required to move 512 spaces. As a result, when data with SN 0 to 255 are processed later, all of them will be dropped. For issue 1, 11ad has proposed flow control to address the issue. For issue 2, there is no existing solutions. For both issue 1, 11ad flow control may not work under the EHT context due to the following consideration: It is possible that for multi-band context, the total SN space may be larger. As a result, the rule needs to be changed to accommodate the consideration of larger SN space. Multi-band BAR operation may change, and we need to accommodate for that IEEE 802.11ad has the flow control signaling in 11ad acknowledgement frame. EHT is likely to have its own acknowledgement frame with signaling to accommodate EHT consideration. For issue 2, 11ad flow control rule requires the following change to work. 11ad assumes that the BuffSizeB for reception window and receiver memory are the same. To resolve issue 2, multi-band context will need to relax the requirement to allow higher speed under the constraint of processing delay. 11ad flow control does not allow the data before WinStartB to come. For issue 2, we will have to allow this case. We need to revise the meaning of passing up. Specifically, receiver should be allowed to delay passing up a SN, even when the SN does not have any received MSDU or A-MSDU Embodiments described herein provide a solution from the perspective of Tx side and Rx side for both issue 1 and issue 2. Essentially, what we propose is a generalized multi-band flow control operation. From the perspective of Rx side, allow STA to delay the passing up of stored MSDU or A-MSDU to the next MAC process, or delaying the drop of reception of a MSDU or A-MSDU and passing the gaps to the next MAC process Have a pointer PassStartB to indicate the SN to be passed up to the next MAC address with stored MSDU or A-MSUD or without any MSDU or A-MSDU. Have STA maintain a total buffer space (TotalBufferSizeB) that can be larger than WinSizeB, the size of the reception window. The total buffer size represents the sum of the space waiting to be passed up. Have STA maintain the highest acknowledged SN, PassEndB. This represents the highest SN that maybe passed up to the next MAC address with stored MSDU or A-MSUD or without any MSDU or A-MSDU. The receiver can indicate to the transmitter about total buffer size, TotalBufferSizeB, which includes the exact capacity to store packets. The receiver can indicate the remaining capacity of the MSDU/A-MSDU, WinCapacityB to be transmitted in the new variant of block acknowledgement frame. Define corresponding rule for the update based on the above consideration. From the perspective of Tx side, the transmitter transmits MSDU/A-MSDU based on the remaining capability indicated by the receiver. These embodiment help resolve issue 1 and problem in multi-band context: Accommodate the processing delay of each interface, which may happen for various implementation choices. Prevent possible data loss based on solution on receiver side or transmitter side. Resolve the problem of higher arriving data rate than internal processing speed. In these embodiments, from receiver side. We start with the definition of new parameters. Allow STA to delay the passing up of stored MSDU or A-MSDU to the next MAC process or delay the drop of the reception of a MSDU or A-MSDU and passing the gaps to the next MAC process. Have a pointer PassStartB to indicate the SN to be passed up to the next MAC address with stored MSDU or A-MSUD or without any MSDU or A-MSDU. If PassStartB=WinStartB, it represents stopping passing up to the next MAC address. Have STA maintain a total buffer space (TotalBufferSizeB) that can be larger than WinSizeB, the size of the reception window. Have STA maintain the highest SN, PassEndB, which represents the potential SN that maybe passed up to the next MAC address with stored MSDU or A-MSUD or without any MSDU or A-MSDU We continue with the setup of these parameters. STA on the receiver (RX) side indicates the capability to do multi-band flow control in receiver side. The indication can be in EHT capability element. STA on the RX side indicates TotalBufferSizeB to the transmitter, the indication can be in ADDBA request/response or an element in ADDBA request/response. Assume that TotalBufferSizeB>=reception window size WinSizeB STA on the rx side indicates WinCapacityB to the transmitter the indication can be in a new variant of EHT BA the indication can be in a new variant of EHT acknowledgement STA on the rx side indicates to the transmitter the processing delay of each interface The indication can be in an element of ADDBA request/response The transmitter indicates if support of multi-band flow control in transmitter side The indication can be in EHT capability element We continue with the discussion of initializing parameters at rx side as follows: WinStartB, WinEndB, and WinSizeB follow the design of Multi-band data operation for initialization WinStartB=SSN from the ADDBA Request frame that elicited the ADDBA Response frame WindEndB=WinStartB+WinSizeB−1 PassStartB=WinStartB PassEndB=WinStartB WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB+1 In the following, we describe the rules for updating the parameters on the rx side. The receiver shall continue to pass SN with stored MSDUs or A-MSDUs or without stored MSDUs or A-MSDUs to the next MAC process order of increasing value of the SN based on implementation specific consideration, starting with the MSDU or A-MSDU that has SN=PassStartB and proceeding sequentially until there is no ready for the next sequential value of the SN or PassStartB hits WinStartB. Gaps may exist in the Sequence Number subfield values of the MSDUs or A-MSDUs that are passed up to the next MAC process. Set PassStartB to the value of latest SN that was passed up to the next MAC process plus one. We describe two general principles before we continue to describe the update rule. Make sure that PassEndB−PassStartB+1<=TotalBufferSizeB Total space occupied to be passed up is smaller than the total size used for storing passing up. Make sure that WinEndB−PassStartB+1<=2{circumflex over ( )}(log 2(max SN+1)−1) We continue with the detailed rules: For a received MSDU or A-MSDU with SN, If PassStartB<=SN<WinStartB Store the received MPDU in the buffer if the MPDU is not yet received If WinStartB<=SN<=WinEndB Store the received MPDU in the buffer if the MPDU is not yet received, and have the following operation if the MPDU is not yet received If SN>PassEndB, Set PassEndB=SN. If PassEndB>PassStartB+TotalBufferSizeB−1, All MSDU buffers with sequence numbers from PassStartB to PassEndB−TotalBufferSizeB that were received correctly are passed to the next MAC process. Set PassStartB=PassEndB−TotalBufferSizeB+1. Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB Set WinStartB to the value of the Sequence Number field of the first MSDU or A-MSDU that is missing to allow in-order delivery to the next MAC process. Set WinEndB=WinStartB+WinSizeB−1. If WinEndB-PassStartB+1>2{circumflex over ( )}(log 2(max SN+1)−1) All MSDU buffers with sequence numbers from PassStartB to WinEndB−2{circumflex over ( )}(log 2(max SN+1)−1) that were received correctly are passed to the next MAC process. Set PassStartB=WinEndB−2{circumflex over ( )}(log 2(max SN+1)−1)+1. If PassStartB>PassEndB, set PassEndB=PassStartB. Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB+1 if PassEndB=WinStartB Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB if PassEndB is not equal to WinStartB If WinEndB<SN<PassStartB+2{circumflex over ( )}(log 2(max SN+1)−1), Store the received MPDU in the buffer. Set WinEndB=SN. Set WinStartB=WinEndB−WinSizeB+1. Update WinStartB to the value of the Sequence Number field of the first MSDU or A-MSDU that is missing to allow in-order delivery to the next MAC process. Set WinEndB=WinStartB+WinSizeB−1 Set PassEndB=SN. If PassEndB>PassStartB+TotalBufferSizeB−1 All MSDU buffers with sequence numbers from PassStartB to PassEndB−TotalBufferSizeB that were received correctly are passed to the next MAC process. Set PassStartB=PassEndB−TotalBufferSizeB+1. Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB. If WinEndB-PassStartB+1>2{circumflex over ( )}(log 2(max SN+1)−1) All MSDU buffers with sequence numbers from PassStartB to WinEndB−2{circumflex over ( )}(log 2(max SN+1)−1) that were received correctly are passed to the next MAC process. Set PassStartB=WinEndB−2{circumflex over ( )}(log 2(max SN+1)−1)+1. If PassStartB>PassEndB, set PassEndB=PassStartB. Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB+1 if PassEndB=WinStartB Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]-PassEndB if PassEndB is not equal to WinStartB If PassStartB+2{circumflex over ( )}(log 2(max SN+1)−1)<=SN<PassStartB, discard the MPDU (do not store the MPDU in the buffer, do not pass the MSDU or A-MSDU up to the next MAC process). For each received BlockAckReq frame or any BAR variant the block acknowledgment record that changes WinStartB by indicated SSN is modified as follows, where SSN is the value from the Starting Sequence Number field of the received BlockAckReq frame or any BAR variant: If PassStartB<=SSN<WinStartB make no changes to the record If WinStartB<SSN<=WinEndB Set WinStartB=SSN. Set WinEndB=WinStartB+BufferSizeB−1. Update WinStartB to the value of the Sequence Number field of the first MSDU or A-MSDU that is missing to allow in-order delivery to the next MAC process. Set WinEndB=WinStartB+WinSizeB−1 If SSN>PassEndB, set PassEndB=SSN−1. If PassEndB>(PassStarttB+TotalBufferSizeB−1), All MSDU buffers with sequence numbers from PssStartB to PassEnd−TotalBufferSizeB, are discarded from the buffer. Set PassStartB=PassEnd−TotalBufferSizeB+1. Set WinCapacityB=min[PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB. If WinEndB-PassStartB+1>2{circumflex over ( )}(log 2(max SN+1)−1) All MSDU buffers with sequence numbers from PassStartB to WinEndB−2{circumflex over ( )}(log 2(max SN+1)−1) that were received correctly are passed to the next MAC process. Set PassStartB=WinEndB−2{circumflex over ( )}(log 2(max SN+1)−1)+1. If PassStartB>PassEndB, set PassEndB=PassStartB. Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB+1 if PassEndB=WinStartB Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB if PassEndB is not equal to WinStartB If WinEndB<SSN<PassStartB+2{circumflex over ( )}(log 2(max SN+1)−1) Set WinStartB=SSN. Set WinEndB=WinStartB+WinSizeB−1. Set PassEndB=SSN−1. If PassEndB>(PassStartB+TotalBufferSizeB−1), All MSDU buffers with sequence numbers from PassStartB to PassEndB−TotalBufferSizeB, are discarded from the buffer. Set PassStartB=PassEndB−TotalBufferSizeB+1. Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB+1 if PassEndB=WinStartB Set WinCapacityB=min [PassStartB+TotalBufferSizeB−1,WinEndB]−PassEndB if PassEndB is not equal to WinStartB If PassStartB+2{circumflex over ( )}(log 2(max SN+1)−1)<=SSN<PassStartB, make no changes to the record. We continue with our proposal from transmitter side. If transmitter can be controlled by WinCapacityB, the transmitter shall not transmit an MPDU with a SN that is beyond the current recipient's buffer capacity (WinLimitO=MostSuccSN+WinCapacityO), where WinCapacityO to the received value of WinCapacityB indicated in the BlockAck frame. MostSuccSN to the highest of the following two values: (SN of positively acknowledged MPDUs or the SSN−1, where SSN is in any BAR variant that moves WinStartB on the receiver side and is acknowledged). The transmitter will consider the processing delay when transmitting frames across the interfaces to avoid packet loss Some embodiments are directed to a neighbor report for an AP MLD. There are two multi-link logical entities on either side which includes multiple STAs that can setup link with each other. The detailed definition is shown inFIG.6and described in more detail below. Multi-link logical entity: A logical entity that contains one or more STAs. The logical entity has one MAC data service interface and primitives to the LLC and a single address associated with the interface, which can be used to communicate on the DSM. NOTE—A Multi-link logical entity allows STAs within the multi-link logical entity to have the same MAC address. NOTE—The exact name can be changed For infrastructure framework, we have Multi-link AP logical entity, which includes APs on one side, and Multi-link non-AP logical entity, which includes non-APs on the other side. The detailed definition is illustrated inFIG.6and described in more detail below. Multi-link AP device (AP MLD): A multi-link logical entity, where each STA within the multi-link logical entity is an EHT AP. Multi-link non-AP device (non-AP MLD): A multi-link logical entity, where each STA within the multi-link logical entity is a non-AP EHT STA. Note that this framework is a natural extension from the one link operation between two STAs, which are AP and non-AP STA under infrastructure framework. Background: Discovery of an AP Through Neighbor Report Neighbor report element is used in order for a reporting AP to provide information about another AP (usually from the same ESS). It is mainly used when included in a BSS Transition Management (BTM) request/response/query frame, where the objective is for an AP to inform an associated STA about neighboring APs that the STA could associate to, and to recommend or force the STA to roam/associate to. It is also used to provide information about APs for unassociated STAs using the ANQP query protocol. One issue is that the neighbor report allows to discover APs, and not AP MLDs. Embodiments described herein modify the neighbor report element in order to allow to discover AP MLDs. Some embodiments modify the Neighbor Report element describing an AP, in order to provide the information that this AP is part of an AP MLD. To achieve this, we can simply add a field in the BSSID information field called for instance: “part of an AP MLD”. This field would be set to 1 if the AP is part of an AP MLD If we mandate that an EHT AP is always part of an AP MLD, to achieve this, we can simply add a field in the BSSID information field called “Extremely High Throughput”. This field would be set to 1 if the AP is an EHT AP and would therefore be part of an AP MLD. We can also include another field describing the number of APs that are part of the same MLD. Some embodiments modify the Neighbor Report element describing an AP, in order to be able in a frame to send multiple Neighbor Report elements describing multiple or all APs of an AP MLD. To achieve this, we can add a field in the BSSID information field called for instance: “part of same MLD as reporting AP”. In this case, we would simply indicate that the reported AP is part of the same MLD as the reporting AP. To achieve this, we can add a field in the BSSID information field called for instance: “part of same MLD as AP reported in following neighbor report element”. In this case, we would simply indicate that the reported AP is part of the same MLD as the reported AP that is reported in the neighbor report element that is sent right after this neighbor report element in the frame. In order to report 3 APs of an AP MLD, the reporting AP would then transmit 3 neighbor report elements (one after the others) and set this new field to 1 for the 2 first neighbor report elements. The receiver would then make the connection between the 3 APs and know that they are part of the same AP MLD. To achieve this, we can also define a new element, which contains an AP MLD address (which can be the upper MAC address of the AP MLD and which is unique in the AP MLD), and possibly could then include also the linkID, which would be the ID of the reported AP, within the AP MLD. To achieve this, we can also use a multi-link element, which is meant to describe an AP MLD. This Multi-link element would have the structure of the multiple BSSID element, with a subelement for each AP, identified by their linkID. The subelement of one AP can contains multiple elements to describe the AP. We could then here include in the frame a multi-link element, which includes 3 (in our example) linkID subelements (one for each AP of the AP MLD), and each subelement containing a neighbor report describing the AP. In some embodiments, the protocol for BSS transition management, as defined currently in the 802.11 specification for the transition between one AP to another AP, is modified for an EHT STA to enable the transition between one AP MLD to another AP MLD, by making the changes as follows: Neighbor report(s) included in the BTM request frame describes the AP MLD (as described above) or one or more AP that are part of the AP MLD, with an indication that it is part of an AP MLD. A non-AP MLD would then use reassociation frame to one of the reported neighbor AP that is part of the target neighbor AP MLD to perform a multi-link setup with the new AP MLD. If the FT (Fast BSS Transition protocol) is used, it would be use at the AP MLD level and not at the AP level. These embodiments allow for discovery of an AP MLD. These embodiments also allow the use of BSS transition management protocol between AP MLDs. In some embodiments, a physical layer protocol data unit may be a physical layer conformance procedure (PLCP) protocol data unit (PPDU). In some embodiments, the AP and STAs may communicate in accordance with one of the IEEE 802.11 standards. IEEE draft specification IEEE P802.11ax/D4.0, February 2019, and IEEE Std 802.11ad-2012 are incorporated herein by reference. In one embodiment,FIG.7illustrates a functional block diagram of a communication station that may be suitable for use as an AP, a STA or other user device in accordance with some embodiments. The communication station700may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device. The communication station700may include communications circuitry702and a transceiver710for transmitting and receiving signals to and from other communication stations using one or more antennas701. The communications circuitry702may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station700may also include processing circuitry706and memory708arranged to perform the operations described herein. In some embodiments, the communications circuitry702and the processing circuitry706may be configured to perform operations detailed in the above figures, diagrams, and flows. In accordance with some embodiments, the communications circuitry702may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry702may be arranged to transmit and receive signals. The communications circuitry702may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry706of the communication station700may include one or more processors. In other embodiments, two or more antennas701may be coupled to the communications circuitry702arranged for sending and receiving signals. The memory708may store information for configuring the processing circuitry706to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory708may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory708may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media. In some embodiments, the communication station700may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly. In some embodiments, the communication station700may include one or more antennas701. The antennas701may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station. In some embodiments, the communication station700may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen. Although the communication station700is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station700may refer to one or more processes operating on one or more processing elements. The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment. | 32,740 |
11943702 | DETAILED DESCRIPTION In the present disclosure, a “base station” can include a RAN Node such as an 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), and/or a 5G Node, new radio (NR) node or g Node B (gNB), which communicate with a wireless communication device, also known as user equipment (UE). Although some examples may be described with reference to any of E-UTRAN Node B, an eNB, an RNC and/or a gNB, such devices may be replaced with any type of base station. In wireless communication systems, if the UE uses a reference cell on a earlier frequency subject to Clear Channel Assessment (CCA) for deriving the UE transmit timing, then the UE shall meet the requirement for an initial transmission provided that at least one (Synchronization Signal Block) SSB is available at the UE during the last 160 ms. The UE shall determine the reference cell (or, reference timing) availability first and then the above UE behavior could be applied based on the availability of reference cell (or, reference timing). For serving cell(s) in Primary Timing Advance Group (pTAG), UE shall use the Special Cell (SpCell) as the reference cell for deriving the UE transmit timing for cells in the pTAG. If a reference cell on a carrier frequency belonging to the pTAG, which is subject to CCA, is unavailable at the UE for more than 160 ms then the UE is allowed to use any of available activated Secondary Cell(s) (SCell(s)) at the UE in pTAG as a new reference cell. If the SCell used as reference cell is deactivated, or becomes unavailable for more than 160 ms, the UE is allowed to use another active serving cell in pTAG as new reference cell. For serving cell(s) in Secondary Timing Advance Group (sTAG), UE shall use any of the activated SCell(s) as the reference cell for deriving the UE transmit timing for the cells in the sTAG. If a reference cell on a carrier frequency belonging to the sTAG, which is subject to CCA is unavailable at the UE for more than 160 ms then the UE is allowed to use any of available activated SCell(s) at the UE in sTAG as a new reference cell. FIG.1illustrates a wireless network100, in accordance with some embodiments. The wireless network100includes a UE101and a base station150connected via an air interface190. The UE101and any other UE in the system may be, for example, laptop computers, smartphones, tablet computers, printers, machine-type devices such as smart meters or specialized devices for healthcare monitoring, remote security surveillance, an intelligent transportation system, or any other wireless devices with or without a user interface. The base station150provides network connectivity to a broader network (not shown) to the UE101via the air interface190in a base station service area provided by the base station150. In some embodiments, such a broader network may be a wide area network operated by a cellular network provider, or may be the Internet. Each base station service area associated with the base station150is supported by antennas integrated with the base station150. The service areas are divided into a number of sectors associated with certain antennas. Such sectors may be physically associated with fixed antennas or may be assigned to a physical area with tunable antennas or antenna settings adjustable in a beamforming process used to direct a signal to a particular sector. One embodiment of the base station150, for example, includes three sectors each covering a 120 degree area with an array of antennas directed to each sector to provide 360 degree coverage around the base station150. The UE101includes control circuitry105coupled with transmit circuitry110and receive circuitry115. The transmit circuitry110and receive circuitry115may each be coupled with one or more antennas. The control circuitry105may be adapted to perform operations associated with MTC. In some embodiments, the control circuitry105of the UE101may perform calculations or may initiate measurements associated with the air interface190to determine a channel quality of the available connection to the base station150. These calculations may be performed in conjunction with control circuitry155of the base station150. The transmit circuitry110and receive circuitry115may be adapted to transmit and receive data, respectively. The control circuitry105may be adapted or configured to perform various operations such as those described elsewhere in this disclosure related to a UE. The transmit circuitry110may transmit a plurality of multiplexed uplink physical channels. The plurality of uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM). The transmit circuity110may be configured to receive block data from the control circuitry105for transmission across the air interface190. Similarly, the receive circuitry115may receive a plurality of multiplexed downlink physical channels from the air interface190and relay the physical channels to the control circuitry105. The uplink and downlink physical channels may be multiplexed according to TDM or FDM. The transmit circuitry110and the receive circuitry115may transmit and receive both control data and content data (e.g. messages, images, video, et cetera) structured within data blocks that are carried by the physical channels. FIG.1also illustrates the base station150, in accordance with various embodiments. The base station150circuitry may include control circuitry155coupled with transmit circuitry160and receive circuitry165. The transmit circuitry160and receive circuitry165may each be coupled with one or more antennas that may be used to enable communications via the air interface190. The control circuitry155may be adapted to perform operations associated with MTC. The transmit circuitry160and receive circuitry165may be adapted to transmit and receive data, respectively, within a narrow system bandwidth that is narrower than a standard bandwidth structured for person to person communication. In some embodiments, for example, a transmission bandwidth may be set at or near 1.4 MHz. In other embodiments, other bandwidths may be used. The control circuitry155may perform various operations such as those described elsewhere in this disclosure related to a base station. Within the narrow system bandwidth, the transmit circuitry160may transmit a plurality of multiplexed downlink physical channels. The plurality of downlink physical channels may be multiplexed according to TDM or FDM. The transmit circuitry160may transmit the plurality of multiplexed downlink physical channels in a downlink super-frame that is comprised of a plurality of downlink subframes. Within the narrow system bandwidth, the receive circuitry165may receive a plurality of multiplexed uplink physical channels. The plurality of uplink physical channels may be multiplexed according to TDM or FDM. The receive circuitry165may receive the plurality of multiplexed uplink physical channels in an uplink super-frame that is comprised of a plurality of uplink subframes. As described further below, the control circuitry105and155may be involved with measurement of a channel quality for the air interface190. The channel quality may, for example, be based on physical obstructions between the UE101and the base station150, electromagnetic signal interference from other sources, reflections or indirect paths between the UE101and the base station150, or other such sources of signal noise. Based on the channel quality, a block of data may be scheduled to be retransmitted multiple times, such that the transmit circuitry110may transmit copies of the same data multiple times and the receive circuitry115may receive multiple copies of the same data multiple times. FIG.2illustrates a flowchart for an exemplary method for a user equipment in accordance with some embodiments. The method200illustrated inFIG.2may be implemented by the UE101described inFIG.1. The method200may begin at step S201, where the UE may determine a first time period for the UE, based on whether the UE uses Discontinuous Reception (DRX) and whether the UE uses Measurement Gap (MG). The first time period indicates a respective timing criterion for the UE to determine a time period of maintaining available downlink timing for a reference cell. In some embodiments, the first time period may relate to a sampling rate at the physical layer, in other words, the first time period may be based on the physical layer measurement time interval for the reference cell. At step S202, the UE may determine, based on the first time period, a first time threshold for the UE to determine reference cell availability. The reference cell availability is determined by above two steps taking into account timing criteria for UE to determine DL timing availability. The availability criteria for UE are determined and then the UE behavior could be applied based on the availability of reference. In some embodiments, the UE may do not use DRX. The first time period is determined based on a synchronization signal and physical broadcast channel block (SSB)-based measurement timing configuration (SMTC) periodicity of the UE. In some embodiments, the UE do not use DRX and does not use MG, for instance, the reference cell SSB is inside active Bandwidth Part (BWP) and the reference cell SSB time tracking can be performed without MG. The first time period is determined as a product of a first factor and the SMTC periodicity. As shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. In some embodiments, the first factor may have a predefined value which is greater than or equal to 1. For example, when the second time threshold is defined as 160 ms, the first time threshold may be determined by: X=max{M1×SMTC periodicity, 160 ms},M1≥1 Wherein X and M1are the first time threshold and the first factor, respectively. In some embodiments, the first factor may be a measurement resource sharing factor. In some embodiments, the measurement resource sharing factor may be a carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0. For example, when the second time threshold is defined as 160 ms, and the first time threshold may be determined by: X=max{SMTC periodicity×CSSFintra, 160 ms} Wherein, X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0, respectively. In some embodiments, the first factor may be a product of a second factor and a measurement resource sharing factor. The second factor is based on how intra-frequency SMTC is overlapped with MGs; in other word, the second factor is based on MG overlapping condition. In some embodiments, the measurement resource sharing factor is a carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0. For example, when the second time threshold is defined as 160 ms, the first time threshold may be determined by: X=max{(Kpor ceiling (Kp))×SMTC periodicity×CSSFintra, 160 ms} Wherein X, and CSSFintraare the first time threshold and the carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0, respectively. In some embodiments, the second factor may be Kp. In other embodiments, the second factor may be ceiling (Kp). Even though the UE does not use MGs, the second factor may be determined based on MGs since there are always MGs which are configured by the base station no matter whether the UE use them or not. When intra-frequency SMTC is fully non overlapping with MGs or intra-frequency SMTC is fully overlapping with MGs, Kp=1. When intra-frequency SMTC is partially overlapping with MGs, Kp=1/(1−(SMTC periodicity/MGRP)), where SMTC period<MGRP and MGRP means a measurement gap repetition periodicity. Kpis as defined in section 9.2A.5.1 in TS 38.133 V16.6.0. UE determines the reference cell or reference timing on a carrier frequency subject to CCA is not available at the UE refers to when at least one SSB is configured by gNB, but the first two successive candidate SSB positions for the same SSB index within the discovery burst transmission window are not available at the UE due to DL CCA failures at gNB during the last X otherwise the reference cell or reference timing on the carrier frequency subject to CCA is considered as available at the UE. When the UE do not use DRX, in some embodiments where the UE uses MG, the reference cell SSB is outside active BWP and the reference cell SSB time tracking needs MG. The first time period is determined based on the larger one between the SMTC periodicity and a measurement gap repetition (MGRP). In some embodiments, the first time threshold is determined as a product of a third factor and the larger one between the SMTC periodicity and the MGRP, the third factor having a predefined value which is greater than or equal to 1. For example, the first time threshold may be determined by: X=N3×max{MGRP, SMTC periodicity},N3≥1 Wherein X and N3are the first time threshold and the third factor, respectively. In some embodiments, the first time period is determined as a product of a fourth factor and the larger one between the SMTC periodicity and the MGRP, the fourth factor having a predefined value which is greater than or equal to 1. Again, as shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. For example, when the second time threshold is defined as 160 ms, the first time threshold may be determined by: X=max{M4×max{MGRP, SMTC periodicity}, 160 ms},M4≥1 Wherein X and M4are the first time threshold and the fourth factor, respectively. In some embodiments, the first time period is determined as a product of a measurement resource sharing factor and the larger one between the SMTC periodicity and the MGRP. Again, as shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. In some embodiments, the measurement resource sharing factor is a carrier-specific scaling factor CSSF defined in the section 9.1.5.2 of 3GPP TS 38.133 V16.6.0. For example, when the second time threshold is defined as 160 ms, and the first time threshold may be determined by: X=max{max{MGRP, SMTC periodicity}×CSSFintra, 160 ms} Wherein X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.2 of 3GPP TS 38.133 V16.6.0., respectively. In some embodiments, the first time threshold is determined as a predefined fixed value larger than or equal to the second time threshold such as 160 ms. UE determines the reference cell or reference timing on a carrier frequency subject to CCA is not available at the UE refers to when at least one SSB is configured by gNB, but the first two successive candidate SSB positions for the same SSB index within the discovery burst transmission window are not available at the UE due to DL CCA failures at gNB during the last X ms; otherwise the reference cell or reference timing on the carrier frequency subject to CCA is considered as available at the UE. In some embodiments, the UE may use DRX but does not use MG, where the reference cell SSB is inside active BWP and the reference cell SSB time tracking can be performed without MG. The first time period is determined based on a synchronization signal and physical broadcast channel block (SSB)-based measurement timing configuration (SMTC) periodicity and a DRX cycle of the UE. In some embodiments, the first time threshold is determined as a product of a fifth factor and the larger one between the SMTC periodicity and the DRX cycle, the fifth factor having a predefined value which is greater than or equal to 1. For example, the first time threshold may be determined by: X=N5×max{SMTC periodicity, DRX cycle},N5≥1 Wherein X and N5are the first time threshold and the fifth factor, respectively. In some embodiments, wherein the first time period is determined as a product of a sixth factor and the larger one between the SMTC periodicity and the DRX cycle, the sixth factor having a predefined value which is greater than or equal to 1. Again, as shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. For example, when the second time threshold is defined as 160 ms, the first time threshold may be determined by: X=max{M6×max{SMTC periodicity, DRX cycle}, 160 ms},M6≥1 Wherein X and M6are the first time threshold and the sixth factor, respectively. When the UE uses DRX but does not use MG, in some embodiments where the DRX cycle may be greater than a third time threshold, the first time threshold is determined as a product of a measurement resource sharing factor and the DRX cycle. In some embodiments, the measurement resource sharing factor may be a carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0. For example, when the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=DRX cycle×CSSFintra, DRX cycle>320 ms Wherein X is the first time threshold and CSSFintrais the carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0. When the UE uses DRX but does not use MG, in some embodiments where the DRX cycle may be not greater than the third time threshold, the first time period is determined as a product of the following: a seventh factor, a measurement resource sharing factor and the larger one between the SMTC periodicity and the DRX cycle, the seventh factor being greater than or equal to 1. Again, as shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. In some embodiments, the measurement resource sharing factor is a carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0. For example, when the second time threshold is defined as 160 ms and the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=max{max{SMTC periodicity, DRX cycle}×CSSFintra, 160 ms}, DRX cycle≤320 ms Wherein X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0, respectively. The seventh factor is equal to 1. For example, when the second time threshold is defined as 160 ms and the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=max{(1.5 or 2)×max{SMTC periodicity, DRX cycle}×CSSFintra, 160 ms}, DRX cycle≤320 ms Wherein X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0, respectively. The seventh factor is equal to 1.5 or 2. When the UE uses DRX but does not use MG, in some embodiments where the DRX cycle is greater than a third time threshold, the first time threshold is determined as a product of the following: an eighth factor, a measurement resource sharing actor and the DRX cycle, wherein the eighth factor is based on how intra-frequency SMTC is overlapped with MGs. In some embodiments, the measurement resource sharing factor is a carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0. For example, when the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=(Kpor ceiling (Kp))×DRX cycle×CSSFintra, DRX cycle>320 ms Wherein X, and CSSFintraare the first time threshold and the carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0, respectively. In some embodiments, the eighth factor may be Kp. In other embodiments, the eighth factor may be ceiling (Kp). When the UE uses DRX but does not use MG, in some embodiments where the DRX cycle may be not greater than a third time threshold, the first time period is determined as a product of the following: a ninth factor, a measurement resource sharing factor, the larger one between the SMTC periodicity and the DRX cycle, and wherein the ninth factor based on how intra-frequency SMTC is overlapped with MGs. Again, as shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. In some embodiments, the ninth factor may be based on Kp. For example, the ninth factor may be equal to Kpor ceiling(Kp). In other embodiments, the ninth factor may be further based on a relaxation due to DRX mode. As a result, for instance, the ninth factor may be (1.5×Kp) or ceiling (1.5×Kp). In some embodiments, the measurement resource sharing factor is a carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0. For example, when the second time threshold is defined as 160 ms and the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=max{(Kpor ceiling (Kp))×max{SMTC periodicity, DRX cycle}×CSSFintra, 160 ms}, DRX cycle≤320 ms Or X=max{((1.5×Kp) or ceiling (1.5×Kp))×max{SMTC periodicity, DRX cycle}×CSSFintra, 160 ms}, DRX cycle≤320 ms Wherein X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.1 of 3GPP TS 38.133 V16.6.0, respectively. Even though the UE does not use MGs, the ninth factor may be determined based on MGs since there are always MGs which are configured by the base station no matter whether the UE use them or not. When intra-frequency SMTC is fully non overlapping with MGs or intra-frequency SMTC is fully overlapping with MGs, Kp=1. When intra-frequency SMTC is partially overlapping with MGs, Kp=1/(1−(SMTC periodicity/MGRP)), where SMTC period<MGRP and MGRP means a measurement gap repetition. Kpis as defined in section 9.2A.5.1 in TS 38.133 V16.6.0 In some embodiments, the first time threshold is determined as a predefined fixed value larger than or equal to the second time threshold such as 160 ms. In some embodiments, the predefined fixed values are different among different DRX cycles. UE determine the reference cell or reference timing on a carrier frequency subject to CCA is not available at the UE refers to when at least one SSB is configured by gNB, but the first two successive candidate SSB positions for the same SSB index within the discovery burst transmission window are not available at the UE due to DL CCA failures at gNB during the last X ms; otherwise the reference cell or reference timing on the carrier frequency subject to CCA is considered as available at the UE. In some embodiments, the UE may use DRX and MG, where the reference cell SSB is outside active BWP and the reference cell SSB time tracking needs MG. The first time period is determined based on a synchronization signal and physical broadcast channel block (SSB)-based measurement timing configuration (SMTC) periodicity, a DRX cycle and a measurement gap repetition (MGRP) of the UE. In some embodiments, the first time threshold is determined as a product of a tenth factor and the largest one among the SMTC periodicity, the DRX cycle and the MGRP, the tenth factor having a predefined value which is greater than or equal to 1. For example, the first time threshold may be determined by: X=N10×max{MGRP, SMTC periodicity, DRX cycle},N10≥1 Wherein X and N10are the first time threshold and the tenth factor, respectively. In some embodiments, wherein the first time period is determined as a product of an eleventh factor and the largest one among the SMTC periodicity, the DRX cycle and the MGRP, the eleventh factor having a predefined value which is greater than or equal to 1. Again, as shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. For example, when the second time threshold is defined as 160 ms, the first time threshold may be determined by: X=max{M11×max{MGRP, SMTC periodicity, DRX cycle}, 160 ms},M11≥1 Wherein, X and M11are the first time threshold and the eleventh factor, respectively. When the UE uses DRX and MG, in some embodiments where the DRX cycle may be greater than a third time threshold, the first time threshold is determined as a product of the DRX cycle and a measurement resource sharing factor. In some embodiments, the measurement resource sharing factor is a carrier-specific scaling factor CSSF defined in the section 9.1.5.2 of 3GPP TS 38.133 V16.6.0. For example, when the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=DRX cycle×CSSFintra, DRX cycle>320 ms Wherein X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.2 of 3GPP TS 38.133 V16.6.0, respectively. When the UE uses DRX and MG, in some embodiments where the DRX cycle may be not greater than the third time threshold, the first time period is determined as a product of the following: a twelfth factor, a measurement resource sharing factor, the largest one among the SMTC periodicity, the DRX cycle and the MGRP, the twelfth factor having a predefined value which is greater than or equal to 1. Again, as shown inFIG.3, the step S202, determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: step S2021, comparing a second time threshold for the UE to maintain local DL timing with the first time period; step S2022, determining the larger one between the second time threshold and the first time period as the first time threshold. In some embodiments, the measurement resource sharing factor is a carrier-specific scaling factor CSSF defined in the section 9.1.5.2 of 3GPP TS 38.133 V16.6.0. For example, when the second time threshold is defined as 160 ms and the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=max{max{MGRP, SMTC periodicity, DRX cycle}×CSSFintra, 160 ms}, DRX cycle≤320 ms Wherein X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.2 of 3GPP TS 38.133 V16.6.0, respectively. The twelfth factor is equal to 1. For example, when the second time threshold is defined as 160 ms and the third time threshold is defined as 320 ms, the first time threshold may be determined by: X=max{(1.5 or 2)×max{MGRP, SMTC periodicity, DRX cycle}×CSSFintra, 160 ms}, DRX cycle≤320 ms Wherein X and CSSFintraare the first time threshold and carrier-specific scaling factor CSSF defined in the section 9.1.5.2 of 3GPP TS 38.133 V16.6.0., respectively. The twelfth factor is equal to 1.5 or 2. In some embodiments, the first time threshold is determined as a predefined fixed value larger than or equal to the second time threshold such as 160 ms. In some embodiments, the predefined fixed values are different among different DRX cycles. UE determine the reference cell or reference timing on a carrier frequency subject to CCA is not available at the UE refers to when at least one SSB is configured by gNB, but the first two successive candidate SSB positions for the same SSB index within the discovery burst transmission window are not available at the UE due to DL CCA failures at gNB during the last X ms; otherwise the reference cell or reference timing on the carrier frequency subject to CCA is considered as available at the UE. FIG.4illustrates an exemplary block diagram of an apparatus for a user equipment (UE) in accordance with some embodiments. The apparatus400illustrated inFIG.4may be used to implement the method200as illustrated in combination withFIG.2 As illustrated inFIG.4, the apparatus400includes a first determination unit410and a second determination unit420. The first determination unit410may be configured to determine a first time period for the UE, based on whether the UE uses Discontinuous Reception (DRX) and whether the UE uses Measurement Gap (MG), wherein the first time period indicates a respective timing criterion for the UE to determine a time period of maintaining available downlink timing for a reference cell. The second determination unit420may be configured to determining, based on the first time period, a first time threshold for the UE to determine reference cell availability. According to the embodiments of the present application, by performing reference signal measurement in a relaxation mode based on the mobility of the UE, whether the reference cell or reference timing on a carrier frequency subject to CCA is available or not at the UE is determined, and then the UE behavior could be applied based on the availability of reference cell. FIG.5illustrates example components of a device500in accordance with some embodiments. In some embodiments, the device500may include application circuitry502, baseband circuitry504, Radio Frequency (RF) circuitry (shown as RF circuitry520), front-end module (FEM) circuitry (shown as FEM circuitry530), one or more antennas532, and power management circuitry (PMC) (shown as PMC534) coupled together at least as shown. The components of the illustrated device500may be included in a UE or a RAN node. In some embodiments, the device500may include fewer elements (e.g., a RAN node may not utilize application circuitry502, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device500may 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). The application circuitry502may include one or more application processors. For example, the application circuitry502may 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 device500. In some embodiments, processors of application circuitry502may process IP data packets received from an EPC. The baseband circuitry504may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry504may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry520and to generate baseband signals for a transmit signal path of the RF circuitry520. The baseband circuitry504may interface with the application circuitry502for generation and processing of the baseband signals and for controlling operations of the RF circuitry520. For example, in some embodiments, the baseband circuitry504may include a third generation (3G) baseband processor (3G baseband processor506), a fourth generation (4G) baseband processor (4G baseband processor508), a fifth generation (5G) baseband processor (5G baseband processor510), or other baseband processor(s)512for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry504(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 circuitry520. In other embodiments, some or all of the functionality of the illustrated baseband processors may be included in modules stored in the memory518and executed via a Central Processing ETnit (CPET514). 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 circuitry504may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry504may 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. In some embodiments, the baseband circuitry504may include a digital signal processor (DSP), such as one or more audio DSP(s)516. The one or more audio DSP(S)516may be 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 circuitry504and the application circuitry502may be implemented together such as, for example, on a system on a chip (SOC). In some embodiments, the baseband circuitry504may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry504may 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 circuitry504is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. The RF circuitry520may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry520may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. The RF circuitry520may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry530and provide baseband signals to the baseband circuitry504. The RF circuitry520may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry504and provide RF output signals to the FEM circuitry530for transmission. In some embodiments, the receive signal path of the RF circuitry520may include mixer circuitry522, amplifier circuitry524and filter circuitry526. In some embodiments, the transmit signal path of the RF circuitry520may include filter circuitry526and mixer circuitry522. The RF circuitry520may also include synthesizer circuitry528for synthesizing a frequency for use by the mixer circuitry522of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry522of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry530based on the synthesized frequency provided by synthesizer circuitry528. The amplifier circuitry524may be configured to amplify the down-converted signals and the filter circuitry526may 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 circuitry504for 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 circuitry522of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect. In some embodiments, the mixer circuitry522of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry528to generate RF output signals for the FEM circuitry530. The baseband signals may be provided by the baseband circuitry504and may be filtered by the filter circuitry526. In some embodiments, the mixer circuitry522of the receive signal path and the mixer circuitry522of 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 circuitry522of the receive signal path and the mixer circuitry522of 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 circuitry522of the receive signal path and the mixer circuitry522may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry522of the receive signal path and the mixer circuitry522of the transmit signal path may be configured for super-heterodyne operation. 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 circuitry520may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry504may include a digital baseband interface to communicate with the RF circuitry520. 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. In some embodiments, the synthesizer circuitry528may be a fractional-N synthesizer or a fractional N/N+1 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 circuitry528may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. The synthesizer circuitry528may be configured to synthesize an output frequency for use by the mixer circuitry522of the RF circuitry520based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry528may be a fractional N/N+1 synthesizer. 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 circuitry504or the application circuitry502(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 circuitry502. Synthesizer circuitry528of the RF circuitry520may 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 (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (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. In some embodiments, the synthesizer circuitry528may 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 circuitry520may include an IQ/polar converter. The FEM circuitry530may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas532, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry520for further processing. The FEM circuitry530may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry520for transmission by one or more of the one or more antennas532. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry520, solely in the FEM circuitry530, or in both the RF circuitry520and the FEM circuitry530. In some embodiments, the FEM circuitry530may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry530may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry530may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry520). The transmit signal path of the FEM circuitry530may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry520), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas532). In some embodiments, the PMC534may manage power provided to the baseband circuitry504. In particular, the PMC534may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC534may often be included when the device500is capable of being powered by a battery, for example, when the device500is included in a EGE. The PMC534may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics. FIG.5shows the PMC534coupled only with the baseband circuitry504. However, in other embodiments, the PMC534may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry502, the RF circuitry520, or the FEM circuitry530. In some embodiments, the PMC534may control, or otherwise be part of, various power saving mechanisms of the device500. For example, if the device500is 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 brown as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device500may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the device500may 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 device500goes 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 device500may not receive data in this state, and in order to receive data, it transitions back to an RRC Connected state. 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. Processors of the application circuitry502and processors of the baseband circuitry504may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry504, alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry502may 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. FIG.6illustrates example interfaces600of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry504ofFIG.5may comprise 3G baseband processor506, 4G baseband processor508, 5G baseband processor510, other baseband processor(s)512, CPU514, and a memory518utilized by said processors. As illustrated, each of the processors may include a respective memory interface602to send/receive data to/from the memory518. The baseband circuitry504may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface604(e.g., an interface to send/receive data to/from memory external to the baseband circuitry504), an application circuitry interface606(e.g., an interface to send/receive data to/from the application circuitry502ofFIG.5), an RF circuitry interface608(e.g., an interface to send/receive data to/from RF circuitry520ofFIG.5), a wireless hardware connectivity interface610(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 interface612(e.g., an interface to send/receive power or control signals to/from the PMC534. FIG.7is a block diagram illustrating components700, 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.7shows a diagrammatic representation of hardware resources702including one or more processors712(or processor cores), one or more memory/storage devices718, and one or more communication resources720, each of which may be communicatively coupled via a bus722. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor704may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources702. The processors712(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 processor714and a processor716. The memory/storage devices718may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices718may 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. The communication resources720may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices706or one or more databases708via a network710. For example, the communication resources720may 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. Instructions724may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors712to perform any one or more of the methodologies discussed herein. The instructions724may reside, completely or partially, within at least one of the processors712(e.g., within the processor's cache memory), the memory/storage devices718, or any suitable combination thereof. Furthermore, any portion of the instructions724may be transferred to the hardware resources702from any combination of the peripheral devices706or the databases708. Accordingly, the memory of the processors712, the memory/storage devices718, the peripheral devices706, and the databases708are examples of computer-readable and machine-readable media. 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. FIG.8illustrates an architecture of a system800of a network in accordance with some embodiments. The system800includes one or more user equipment (UE), shown in this example as a UE802and a UE804. The UE802and the UE804are illustrated as smartphones handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface. In some embodiments, any of the UE802and the UE804can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network. The UE802and the UE804may be configured to connect, e.g., communicatively couple, with a radio access network (RAN), shown as RAN806. The RAN806may be, for example, an Evolved ETniversal Mobile Telecommunications System (ETMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UE802and the UE804utilize connection808and connection810, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connection808and the connection810are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like. In this embodiment, the UE802and the UE804may further directly exchange communication data via a ProSe interface812. The ProSe interface812may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH). The UE804is shown to be configured to access an access point (AP), shown as AP814, via connection816. The connection816can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP814would comprise a wireless fidelity (WiFi®) router. In this example, the AP814may be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). The RAN806can include one or more access nodes that enable the connection808and the connection810. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN806may include one or more RAN nodes for providing macrocells, e.g., macro RAN node818, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., a low power (LP) RAN node such as LP RAN node820. Any of the macro RAN node818and the LP RAN node820can terminate the air interface protocol and can be the first point of contact for the UE802and the UE804. In some embodiments, any of the macro RAN node818and the LP RAN node820can fulfill various logical functions for the RAN806including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In accordance with some embodiments, the EGE802and the EGE804can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the macro RAN node818and the LP RAN node820over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal sub carriers. In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the macro RAN node818and the LP RAN node820to the UE802and the UE804, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks. The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UE802and the UE804. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UE802and the UE804about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE804within a cell) may be performed at any of the macro RAN node818and the LP RAN node820based on channel quality information fed back from any of the UE802and UE804. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UE802and the HE804. The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8). Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations. The RAN806is communicatively coupled to a core network (CN), shown as CN828—via an S1 interface822. In embodiments, the CN828may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface822is split into two parts: the S1-U interface1124, which carries traffic data between the macro RAN node818and the LP RAN node820and a serving gateway (S-GW), shown as S-GW1132, and an S1-mobility management entity (MME) interface, shown as S1-MME interface826, which is a signaling interface between the macro RAN node818and LP RAN node820and the MME(s)830. In this embodiment, the CN828comprises the MME(s)830, the S-GW832, a Packet Data Network (PDN) Gateway (P-GW) (shown as P-GW834), and a home subscriber server (HSS) (shown as HSS836). The MME(s)830may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MME(s)830may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS836may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN828may comprise one or several HSS836, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS836can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. The S-GW832may terminate the S1 interface822towards the RAN806, and routes data packets between the RAN806and the CN828. In addition, the S-GW832may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The P-GW834may terminate an SGi interface toward a PDN. The P-GW834may route data packets between the CN828(e.g., an EPC network) and external networks such as a network including the application server842(alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface (shown as IP communications interface838). Generally, an application server842may be an element offering applications that use IP bearer resources with the core network (e.g., ETMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW834is shown to be communicatively coupled to an application server842via an IP communications interface838. The application server842can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE802and the UE804via the CN828. The P-GW834may further be a node for policy enforcement and charging data collection. A Policy and Charging Enforcement Function (PCRF) (shown as PCRF840) is the policy and charging control element of the CN828. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a ETE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF840may be communicatively coupled to the application server842via the P-GW834. The application server842may signal the PCRF840to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF840may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server842. ADDITIONAL EXAMPLES 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. The following examples pertain to further embodiments. Example 1 is a method for a user equipment (UE), comprising:determining a first time period for the UE, based on whether the UE uses Discontinuous Reception (DRX) and whether the UE uses Measurement Gap (MG), wherein the first time period indicates a respective timing criterion for the UE to determine a time period of maintaining available downlink timing for a reference cell; anddetermining, based on the first time period, a first time threshold for the UE to determine reference cell availability. Example 2 is the method of Example 1, wherein, when the UE does not use DRX, the first time period is determined based on a synchronization signal and physical broadcast channel block (SSB)-based measurement timing configuration (SMTC) periodicity of the UE. Example 3 is the method of Example 2, wherein, when the UE does not use MG, the first time period is determined as a product of a first factor and the SMTC periodicity, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL timing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 4 is the method of Example 3, wherein the first actor has a predefined value which is greater than or equal to 1. Example 5 is the method of Example 3, wherein the first factor is a measurement resource sharing factor. Example 6 is the method of Example 3, wherein the first factor is a product of a second factor and a measurement resource sharing factor, and wherein the second factor is based on how intra-frequency SMTC is overlapped with MGs. Example 7 is the method of Example 5 or 6, wherein the measurement resource sharing factor is a carrier-specific scaling factor CSSF. Example 8 is the method of Example 2, wherein, when the UE uses MG, the first time period is determined based on the larger one between the SMTC periodicity and a measurement gap repetition (MGRP). Example 9 is the method of Example 8, wherein the first time threshold is determined as a product of a third factor and the larger one between the SMTC periodicity and the MGRP, the third factor having a predefined value which is greater than or equal to 1. Example 10 is the method of Example 8, wherein the first time period is determined as a product of a fourth factor and the larger one between the SMTC periodicity and the MGRP, the fourth factor having a predefined value which is greater than or equal to 1, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL timing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 11 is the method of Example 8, wherein the first time period is determined as a product of a measurement resource sharing factor and the larger one between the SMTC periodicity and the MGRP, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL timing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 12 is the method of Example 11, wherein the measurement resource sharing factor is a carrier-specific scaling factor CSSF. Example 13 is the method of Example 1, wherein, when the UE uses DRX but does not use MG, the first time period is determined based on a synchronization signal and physical broadcast channel block (SSB)-based measurement timing configuration (SMTC) periodicity and a DRX cycle of the UE. Example 14 is the method of Example 13, wherein the first tune threshold is determined as a product of a fifth factor and the larger one between the SMTC periodicity and the DRX cycle, the fifth factor having a predefined value which is greater than or equal to 1. Example 15 is the method of Example 13, wherein the first time period is determined as a product of a sixth factor and the larger one between the SMTC periodicity and the DRX cycle, the sixth factor having a predefined value which is greater than or equal to 1, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL timing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 16 is the method of Example 13, wherein, when the DRY cycle is greater than a third time threshold, the first time period is determined as a product of the following: a measurement resource sharing factor and the DRX cycle. Example 17 is the method of Example 16, wherein, when the DRX cycle is not greater than the third time threshold, the first time period is determined as a product of the following: a seventh factor, a measurement resource sharing factor and the larger one between the SMTC periodicity and the DRX cycle, the seventh factor being greater than or equal to 1, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL tithing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 18 is the method of Example 17, wherein the measurement resource sharing factor is a carrier-specific scaling factor CSSF. Example 19 is the method of Example 13, wherein, when the DRX cycle is greater than a third time threshold, the first time threshold is determined as a product of the following: an eighth factor, a measurement resource sharing factor and the DRX cycle, wherein the eighth factor is based on how intra-frequency SMTC is overlapped with MGs. Example 20 is the method of Example 19, wherein, when the DRX cycle is not greater than the third time threshold, the first time period is determined as a product of the following: a ninth factor, a measurement resource sharing factor, the larger one between the SMTC periodicity and the DRX cycle, and wherein the ninth factor based on how intra-frequency SMTC is overlapped with MGs, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL timing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 21 is the method of Example 19 or 20, wherein the measurement resource sharing factor is a carrier-specific scaling factor CSSF. Example 22 is the method of Example 1, wherein, when the UE uses DRX and MG, the first time period is determined based on a synchronization signal and physical broadcast channel block (SSB)-based measurement timing configuration (SMTC) periodicity, a DRX cycle and a measurement gap repetition (MGRP) of the UE. Example 23 is the method of Example 22, wherein the first time threshold is determined as a product of a tenth factor and the largest one among the SMTC periodicity, the DRX cycle and the MGRP, the tenth factor having a predefined value which is greater than or equal to 1. Example 24 is the method of Example 22, wherein the first time period is determined as a product of an eleventh factor and the largest one among the SMTC periodicity, the DRX cycle and the MGRP, the eleventh factor having a predefined value which is greater than or equal to 1, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL timing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 25 is the method of Example 22, wherein, when the DRX cycle is greater than a third time threshold, the first time threshold is determined as a product of the DRX cycle and a measurement resource sharing factor. Example 26 is the method of Example 25, wherein the measurement resource sharing factor is a carrier-specific scaling factor CSSF. Example 27 is the method of Example 25, wherein, when the DRX cycle is not greater than the third time threshold, the first time period is determined as a product of the following: a twelfth factor, a measurement resource sharing factor, the largest one among the SMTC periodicity, the DRX cycle and the MGRP, the twelfth factor having a predefined value which is greater than or equal to 1, and wherein the determining, based on the first time period, a first time threshold for the UE to determine reference cell availability comprises: comparing a second time threshold for the UE to maintain local DL timing with the first time period; and determining the larger one between the second time threshold and the first time period as the first time threshold. Example 28 is the method of Example 27, wherein the measurement resource sharing factor is a carrier-specific sealing factor CSSF. Example 29 is an apparatus for a user equipment (UE), the apparatus comprising: one or more processors configured to perform steps of the method according to any of examples 1-28. Example 30 is a computer readable medium having computer programs stored thereon which, when executed by one or more processors, cause an apparatus to perform steps of the method according to any of examples 1-28. Example 31 is an apparatus for a communication device, comprising means for performing steps of the method according to any of examples 1-28. Example 32 is a computer program product comprising computer programs which, when executed by one or more processors, cause an apparatus to perform steps of the method according to any of examples 1-28. 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. 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. It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users. 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. | 78,824 |
11943703 | Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements. The figures are not necessarily to scale, and the size of some parts may be exaggerated to more clearly illustrate the example shown. Moreover, the drawings provide examples and/or implementations consistent with the description; however, the description is not limited to the examples and/or implementations provided in the drawings. DETAILED DESCRIPTION In the present disclosure, use of the term “a,” “an”, or “the” is intended to include the plural forms as well, unless the context clearly indicates otherwise. Also, the term “includes,” “including,” “comprises,” “comprising,” “have,” or “having” when used in this disclosure specifies the presence of the stated elements, but do not preclude the presence or addition of other elements. In a wireless local area network (WLAN), a wireless device may communicate with one or multiple wireless access points (APs). A wireless AP (or more simply, an AP) can refer to a communication device to which a wireless device can establish a wireless connection to communicate with other endpoint devices. WLANs can include wireless networks that operate according to the Institute of Electrical and Electronic Engineers (IEEE) 802.11 or Wi-Fi Alliance Specifications. In other examples, wireless networks can operate according to other protocols. More generally, techniques or mechanisms according to some implementations of the present disclosure can be used with various types of wireless networks, such as WLANs, cellular networks, or other wireless networks. In a cellular network, an AP can refer to a wireless access network node, such as a base station or enhanced node B (eNodeB) in a cellular network that operates according to the Global System for Mobile communications (GSM), Universal Mobile Telecommunications Service (UNTS) or Long-Term Evolution (LTE) standards as provided by the Third Generation Partnership Project (3GPP). The LTE standards are also referred to as the Evolved Universal Terrestrial Radio Access (E-UTRA) standards. An AP can also refer to a fifth generation (5G) wireless access network node, or another type of wireless access network node. Examples of wireless devices include computers (e.g., tablet computers, notebook computers, desktop computers, etc.), handheld devices (e.g. smart phones, personal digital assistants, etc.), wearable devices (smart watches, electronic eyeglasses, head-mounted devices, etc.), game appliances, health monitors, vehicles (or equipment in vehicles), cargo transportation units (e.g., trailers, containers, etc.), Internet of Things (IoT) devices, or other types of endpoint or user devices that are able to communicate wirelessly. Wireless devices can include mobile devices and/or fixed position devices. More generally, a wireless device can refer to an electronic device that is able to communicate wirelessly. In the ensuing discussion, reference is made to communications and operations that are according to the IEEE 802.11 standards. It is noted that techniques or mechanisms according to some implementations of the present disclosure can be applied to communications and operations according to other standards. According to the IEEE 802.11 standards, a wireless device can operate in one of several connection states: State 1: initial start state, unauthenticated, un-associated. State 2: authenticated, not associated. State 3: authenticated and associated (pending Robust Security Network or RSN authentication). State 4: authenticated and associated. In accordance with some examples, reference is made to a pre-associated state of a wireless device. In the context of IEEE 802.11, the pre-associated state of a wireless device refers to State 1 noted above. More generally, a pre-associated state of a wireless device refers to a state before the wireless device has established a connection (e.g., association in the terminology of the IEEE 802.11 standards) with a network, and before the wireless device has been authenticated. This state can also be referred to as prior to association. When operating in the pre-associated state, a wireless device that operates according to IEEE 802.11 is unable to automatically configure its WLAN interface to adhere to a network policy of a selected network (WLAN). The WLAN interface has to be configured on the wireless device out-of-band (for example, by a non-WLAN communication exchange, such as over a cellular network, a Bluetooth link, etc.) by a network administrator that manages the WLAN. The IEEE 802c-2017 Specification has introduced new requirements for usage of Medium Access Control (MAC) addresses in a local address space. A “local address space” refers to a range of MAC address values used by a particular wireless network that is distinct from another address range used by another wireless network. In some examples, MAC addresses can be defined as 48-bit values, and the 48-bit address range is divided into broadcast/multicast, globally unique, and locally administered. In other examples, MAC addresses can be values with a different number of bits. The requirements of the IEEE 802c-2017 Specification are generally targeted towards wired networks, to allow network administrators to use the range of locally administered MAC addresses to support virtual network interfaces in data centers. IEEE 802c-2017 defines a Structured Local Address Plan (SLAP) that divides the local address space into four quadrants and assigns the range of MAC addresses in each quadrant to a specific purpose. If a wireless device using a random MAC address joins a WLAN and has traffic bridged to a same wired local area network (LAN) segment as the data center devices operating with MAC addresses assigned from the SLAP, there is a chance that the wireless device's MAC address may conflict with the addresses of other equipment operating on the wired network. Reference to SLAP herein refers to the SLAP as defined original IEEE 802c-2017 Specification or any subsequent updates to SLAP requirements based on the original IEEE 802c-2017 Specification. Note that the IEEE 802c-2017 standard may subsequently be combined with another standard, such as the IEEE 802-2014, to become a new standard. The term “IEEE 802c-2017” includes any subsequent standard that includes at least a portion of the content of the IEEE 802c-2017 standard. In some cases, a wireless device that operates according to IEEE 802.11 in a pre-associated state may be allowed by a network administrator of a WLAN to choose its own MAC Address. In this situation, the wireless device may choose a MAC address that is already in use in the WLAN. This can result in frames from the wireless device and another device with the duplicate MAC address being confused in the WLAN. In accordance with some implementations of the present disclosure, a wireless device in a pre-associated state is able to receive, from a wireless network, information including a network address policy of the wireless network. The network address policy included in the received information can specify any of a number of different network address policies used in the wireless network. In some examples, the network address policy included in the received information can indicate use of an address (e.g., a network address such as a MAC address) with at least a portion of the address assigned according to the SLAP. FIG.1is a block diagram of an example network arrangement100that includes a wireless local area network (WLAN)102. The WLAN includes an AP106with which a wireless device104is able to wirelessly communicate. Although just one AP is shown inFIG.1, it is noted that in some examples, the WLAN102may include multiple APs. Also, there may be multiple wireless devices to communicate with the one or more APs of the WLAN102. In some examples, the wireless device104is able to transmit and receive layer 2 frames (or more specifically, Medium Access Control (MAC) frames) over the air interface with the AP106. Communications of layer 2 frames can occur while the wireless device104is in the pre-associated state (e.g., State 1 of IEEE 802.11), as well as in other states (e.g., including States 2, 3, and 4 of IEEE 802.11 noted above). In accordance with some implementations of the present disclosure, the network arrangement100further includes a server108, which includes a network address policy notification engine110that can provide an indication of a network address policy used by the WLAN102to the wireless device104. The network address policy notification engine110can also act as a proxy or relay of policy from an external network116. As used here, an “engine” can refer to a hardware processing circuit, such as any or some combination of a microprocessor, a core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit device, a programmable gate array, or any other hardware processing circuit. In other examples, an “engine” can refer to a combination of a hardware processing circuit and machine-readable instructions (software and/or firmware) executable on the hardware processing circuit. The server108can be implemented as part of the AP106, or alternatively, as a computing node or an arrangement of computing nodes separate from the AP106. The wireless device104includes a network address policy determination and application engine112, which is able to receive information114including a network address policy of the WLAN102from the network address policy notification engine110of the server108. In some examples, the information114including the network address policy is in the form of a WLAN discovery message. Examples of WLAN discovery messages include any or some combination of the following: a beacon, a probe response, an Access Network Query Protocol (ANQP) message, or an IEEE 802.11 management frame (which can be a newly defined IEEE 802.11 management frame), and so forth. A beacon is broadcast by the AP106for receipt by multiple wireless devices104within a wireless communication range of the AP106. A broadcast beacon from the AP106can include a Service Set Identifier (SSID) of the AP106. The SSID identifies the WLAN102. The beacon can also include other information, which according to some implementations of the present disclosure includes the network address policy information114. A beacon is a type of an IEEE 802.11 management frame. In other examples, another type of an IEEE 802.11 management frame can be used to carry the network address policy information114. A probe response according to IEEE 802.11 is in response to a probe request sent by the wireless device104. The probe request can be broadcast by the wireless device104for receipt by one or more APs within the range of the wireless device104. The probe request is used by the wireless device104to discover AP(s) within the wireless communication range of the wireless device104. In further examples, the information114can be provided by the server108that implements an advertisement protocol. For example, the server108can use a Generic Advertisement Service (GAS) as a transport mechanism for an advertisement protocol. The advertisement protocol allows the bidirectional transmission of frames between the wireless device104and the server108prior to network connectivity, so that the wireless device104is effectively in a pre-associated state. This means that a device is connected to the layer 2 radio service, but has not exchanged any authentication parameters and does not have a recognized session (e.g. no session keys are established and no IP address is assigned). One example of an advertisement protocol is ANQP. ANQP operates as a simple query and response protocol that is used by a device to discover a range of information from an “Access Network Information” (ANI) server. This ANI server is either co-located with an AP or is located within a LAN, which is the layer 2 network to which the AP is connected. ANQP allows a device to determine the properties of the LAN before starting an association procedure. Information obtained through ANQP can include: network identifiers, roaming relationships, supported security methods (IEEE 802.1X or web-based authentication), emergency services capability, available service providers, etc. This enables ANQP to be a useful protocol enabling discovery of information about WLANs, prior to the device establishing network connectivity. In examples implementing ANQP, the server108can be an ANQP server that is used to convey ANQP information. The ANQP server is an advertisement server in the network that can receive ANQP requests and respond with ANQP responses. This server can also be referred to as an Access Network (AN) server. FIG.2is a message flow diagram of a process performed among the wireless device104, the AP106, and the server108, according to further examples. The wireless device104receives (at202) network address policy information, such as in a beacon or a probe response, for example. In response, the wireless device104sends (at204) a request for further information regarding the network address policy. For example, the network address policy information received (at202) can include an indication that the WLAN102has a local network policy that the wireless device104is to conform to. However, the network address policy information received (at202) may not include further detail regarding what the network address policy is. The request that is sent (at204) can include an ANQP request or another request, for example. In some embodiments, the wireless device104does not need to receive network address policy information (at202) before sending the request for further information (at204). In response to the request sent (at204), the server108sends (at206) a response that includes the requested further information regarding the network address policy. For example, the requested further information can include a value (selected from among multiple possible values) that indicates the specific network address policy to used. The multiple possible values indicate respective different network address policies. A further explanation of the different network address policies is provided later in this description. Based on the further information regarding the network address policy, the wireless device104decides (at208) whether or not to connect to the WLAN102, as part of a network selection algorithm used by the wireless device104. If the wireless device104decides (at208) to select the WLAN102, the wireless device104obtains (at210) an address of the wireless device according to the network address policy. Depending on the specific network address policy used, the address can be obtained in one of several different ways. The address can be obtained in any of the following ways: (1) locally generating the address in the wireless device104, or (2) obtaining the address from the AP106or another network node, or (3) obtaining a portion of the address from the AP106or another network node, and (4) generating a second portion of the address in the wireless device104. The wireless devices104establishes (at212) a network connection with the WLAN102, and uses the obtained address to perform communications over the WLAN102. If the wireless device104decides (at208) to not select the WLAN102, then the wireless device104performs (at214) another action, which can include selecting another WLAN for connection. Specifying a Local MAC Address Policy in an ANQP Element The following describes an example of using an ANQP-element to specify a local MAC address policy. FIG.3shows an example of a Local MAC Address Policy ANQP-element300. The Local MAC Address Policy ANQP-element300includes the following example fields: Info ID field302(which is set to a value to identify the ANQP-element as a Local MAC Address Policy ANQP element), a Length field304(which is set to a value to indicate a length of a combination of a Policy field306and a Company Identifier (CID) field308, if present), the Policy field306(which is settable to any of various different values to advertise specific policy information supported by the transmitting device, such as the AP106), and the optional CID field308(discussed further below). FIG.3shows the size (in terms of a number of octets) of each of the fields302,304,306, and308. In other examples, the fields of the ANQP-element300can have different sizes. Table 1 below shows an example of possible values to which the Policy field306can be set. TABLE 1Policy Field 306 valueDescription of MAC Address policy0Allow a random MAC address within thefull range of the local space. Therandom MAC address can be generatedby a wireless device or by a networknode in the WLAN.1Use only a globally assigned MACaddress of the WLAN interface for thewireless device.2Use a MAC address within the SLAPAdministratively Assigned Identifier (AAI)Space. The complete MAC addressincludes the 2 bits of the AAI StructuredLocal Address Plan (SLAP) quadrantplus the local/global bit and theunicast/multicast bit and then the rest ofthe bits of the MAC address are random.3Use a MAC address within the SLAPExtended Local Identifier (ELI) space.The complete MAC address includes the2 bits of the ELI SLAP quadrant plus thelocal/global bit and the unicast/multicastbit and then the rest of the bits of theMAC address include a specific CID withthe remaining bits being a randomnumber.4Use a MAC address within the SLAPStandard Assigned Identifier (SAI)space. The complete MAC addressincludes the 2 bits of the SAI SLAPquadrant plus the local/global bit and theunicast/multicast bit and then the rest ofthe bits of the MAC address include anumber generated by a protocolspecified within various IEEE 802standards.5Use a MAC address within the SLAPquadrant “10” space. The completeMAC address includes the 2 bits of the“10” SLAP quadrant plus the local/globalbit and the unicast/multicast bit and thenthe rest of the bits of the MAC addressinclude a number generated by anadministrator.6The local administrator will configure theMAC address.7-255Reserved If the Policy field306is set to value 0, then the MAC address of the wireless device104can be randomly assigned, either by the wireless device104itself or by the WLAN102. If the Policy field306is set to value 1, then the MAC address of the IEEE 802.11 interface of the wireless device104is set to a globally assigned MAC address. If the Policy field306is set to value 2, 3, 4, or 5, then a portion of the MAC address of the wireless device104is assigned according to the IEEE 802c-2017 standard, while another portion(s) of the MAC address is (are) assigned in a different manner, such as randomly assigned (Policy field306set to value 2 or 3), assigned according to another standard (Policy field306set to value 4), or assigned by a network administrator (Policy field306set to value 5). Table 2 below shows an example where the Policy field306can have a number of bits (eight bits0-7in the example shown). Each bit can be set between a logical low value (“0”) and a logical high value (“1”) to indicate whether or not the corresponding policy applies (as indicated by the second column of Table 2). In other words, each bit of the Policy field206is set to “1” when the indicated MAC Address policy is supported and “0” when it is not. Simultaneous policies supported by the transmitting STA can therefore be advertised. TABLE 2Policy Field bitsDescription of MAC Address policy0Allow a random MAC address within thefull range of the local space. Therandom MAC address can be generatedby a wireless device or by a networknode in the WLAN.1Use only a globally assigned MACaddress of the WLAN interface for thewireless device.2Use a MAC address within the SLAPAdministratively Assigned Identifier (AAI)Space. The complete MAC addressincludes the 2 bits of the AAI StructuredLocal Address Plan (SLAP) quadrantplus the local/global bit and theunicast/multicast bit and then the rest ofthe bits of the MAC address are random.3Use a MAC address within SLAPExtended Local Identifier (ELI) space.The complete MAC address includes the2 bits of the ELI SLAP quadrant plus thelocal/global bit and the unicast/multicastbit and then the rest of the bits of theMAC address include a specific CID withthe remaining bits being a randomnumber.4Use a MAC address within the SLAPStandard Assigned Identifier (SAI)space. The complete MAC addressincludes the 2 bits of the SAI SLAPquadrant plus the local/global bit and theunicast/multicast bit and then the rest ofthe bits of the MAC address include anumber generated by a protocolspecified within various IEEE 802standards.5Use a MAC address within SLAPquadrant “10” space. The completeMAC address includes the 2 bits of the“10” SLAP quadrant plus the local/globalbit and the unicast/multicast bit and thenthe rest of the bits of the MAC addressinclude a number generated by anadministrator.6The local administrator will configure theMAC address.7Reserved The CID field308can be provided by the transmitting station (STA) to assist the receiving STA in a case where the Policy field306is set to the value 3 (Table 1 implementation) or bit3of the Policy field308is set to “1” (Table 2 implementation). If the CID field is not used for this option, then the CID may already be known to the receiving STA. For example, the receiving STA can be provisioned with the CID out of band or the receiving STA can also read the CID from the AP's Basic Service Set (BSS) Identifier (BSSID). The advertised values of the Policy field206may change if the MAC address policy in both the transmitting and receiving STAs is dynamic. For example, the MAC address policy may only be used when the transmitting STA (or WLAN) is heavy loaded with traffic and devices. With the Table 1 implementation, the Policy field106is set to value 1 to indicate that the MAC address policy is turned off—i.e., a global MAC address is used. Similarly, with the Table 2 implementation, bit1of the Policy field106is set to “1” to indicate that the MAC address policy is turned off. Alternatively, the receiving STA can ignore any advertisements and use a global MAC address instead of an address indicated by any of the MAC address policies (for backwards compatibility). The choice to ignore or follow the advertised policy may be based on a user setting or based on data stored in the network profile for that particular wireless network. Local MAC Address Policy in Another Message In other examples, the local MAC address policy can be specified using a different element, such as within a beacon or a probe response. FIG.4shows an example of an MAC Address Policy element400that can be included in a beacon or a probe response. The MAC Address Policy element400includes the following example fields: an Element ID field402and an Element ID Extension field406(which when combined provides a value to identify the element as a MAC Address Policy element), a Length field404(to indicate a length of a combination of an Element ID Extension field406, a Policy field408, and a CID field410, if present). The Policy field408can be set to any of various different values to indicate corresponding different local MAC address policies (such as according to Tables 1 and 2 above). MAC Address Duplication Detection In further examples, MAC address duplication can be detected. MAC address duplication detection includes detecting that multiple wireless devices have been assigned or are using the same MAC address. FIG.5shows an example arrangement for MAC address duplication detection. The wireless device104is wirelessly connected to a wireless port502of an infrastructure unit504, which can include an AP and/or a switch, that is part of a WLAN505. A “wireless port” can refer to the circuitry and machine-readable instructions (e.g., physical layer and other layers above the physical layer of a protocol stack) that enable communication over a wireless link. The infrastructure unit504further includes a wired port506that is connected to a wired local area network (LAN)508. A “wired port” can refer to the circuitry and machine-readable instructions (e.g., physical layer and other layers above the physical layer of a protocol stack) that enable communication over a wired link. A device510connected to the wired LAN508can be assigned a MAC address, and the wireless device104can also be assigned a MAC address. The infrastructure unit504includes a duplicate network address detection engine512that is able to monitor MAC addresses of associated devices, including the devices104and510. The duplicate network address detection engine512monitors and maps the MAC addresses associated with the ports (including502and506) of the infrastructure unit504. Each port provides a logical interface to the infrastructure unit504. At the switching level, the infrastructure unit504checks both wireless and wired ports to ensure that there is no duplication of MAC addresses assigned to wireless and wired devices. If the duplicate network address detection engine512detects network address duplication (for example, the wireless port502and the wired port506on the infrastructure unit504have the same MAC address assigned to respective different devices), then the infrastructure unit504can de-authenticate either the wireless device104or the wired device510with an error indication (e.g., “duplicate MAC address detected”). The error indication indicates that the address of the de-authenticated device is a duplicate of another address already used in another device within the WLAN505, the wired LAN508or an external network to which the WLAN505and/or wired LAN508are connected. Additionally, the infrastructure unit504can provide an instruction to the de-authenticated device to assist the de-authenticated device to circumvent MAC address duplication in the future. The error indication and the instruction can be sent as an update to an existing error message or in a new error message from the infrastructure unit504to the de-authenticated device. If two wireless devices are detected as having duplicate MAC addresses (e.g., due to almost simultaneous MAC address assignment), either the most recent device detected is sent the error indication, or both wireless devices are sent the error indication. In other examples, the duplicate network address detection engine512can be provided in a server514that is separate from the infrastructure unit504. For example, the server514can include an Authentication, Authorization, and Accounting (AAA) server. An identity (e.g., MAC address) of the wireless device104can be passed in a message, such as a Remote Authentication Dial-In User Service (RADIUS) message, to the AAA server514for authentication. If the AAA server514detects that the MAC address assigned to the wireless device104is a duplicate of a MAC address assigned to another device (e.g.,510), the AAA server514can instruct the infrastructure unit504to transmit an error indication as noted above. System Arrangement FIG.6is a block diagram of a device or system600, which can be a wireless device, a computer, or an arrangement of multiple computers. The computer or arrangement of computers can implement an AP, a server, or another network node. The device or system600includes a processor602(or multiple processors). A processor can include a microprocessor, a core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, or another hardware processing circuit. The processor(s)602can be coupled to a non-transitory machine-readable or computer-readable storage medium604, which stores network address policy related instructions606executable on the processor602to perform various tasks discussed above, including wireless devices, APs, servers, network nodes, and so forth. Machine-readable instructions executable on a processor can refer to the instructions executable on a single processor or the instructions executable on multiple processors. The device or system600further includes a communication interface608that includes a transceiver (e.g., a radio frequency (RF) transceiver to transmit and receive RF signals) and layers of a protocol stack. The communication interface608can communicate over a wired or wireless medium. The storage medium604can include any or some combination of the following: a semiconductor memory device such as a dynamic or static random access memory (a DRAM or SRAM), an erasable and programmable read-only memory (EPROM), an electrically erasable and programmable read-only memory (EEPROM) and flash memory; a magnetic disk such as a fixed, floppy and removable disk; another magnetic medium including tape; an optical medium such as a compact disk (CD) or a digital video disk (DVD); or another type of storage device. Note that the instructions discussed above can be provided on one computer-readable or machine-readable storage medium, or alternatively, can be provided on multiple computer-readable or machine-readable storage media distributed in a large system having possibly plural nodes. Such computer-readable or machine-readable storage medium or media is (are) considered to be part of an article (or article of manufacture). An article or article of manufacture can refer to any manufactured single component or multiple components. The storage medium or media can be located either in the machine running the machine-readable instructions, or located at a remote site (e.g., a cloud) from which machine-readable instructions can be downloaded over a network for execution. In the foregoing description, numerous details are set forth to provide an understanding of the subject disclosed herein. However, implementations may be practiced without some of these details. Other implementations may include modifications and variations from the details discussed above. It is intended that the appended claims cover such modifications and variations. | 30,100 |
11943704 | DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. As communication networks and services increase in size, complexity, and number of users, management of the communication networks have become increasingly more complex. One way in which wireless access networks are continuing to become more complicated is by incorporating various aspects of next generation networks, such as Fifth Generation (5G) mobile networks, utilizing high frequency bands (e.g., 24 Gigahertz (GHz), 39 GHz, etc.), and/or lower frequency bands such as Sub 6 GHz, and a large number of antennas. 5G New Radio (NR) millimeter (mm) wave technology may provide significant improvements in bandwidth and/or latency over other wireless network technology. Furthermore, coverage and signal quality may be improved using multiple-input and multiple-output (MIMO) adaptive antenna arrays. Additionally, user equipment (UE) devices may also include multiple antennas to improve spectral efficiency. Moreover, improvements in the core networks of 5G wireless access networks provide new functionality, such as, for example, network slicing. Network slicing is a form of virtual network architecture that enables multiple logical networks to be implemented on top of a common shared physical infrastructure using software defined networking (SDN) and/or network function virtualization (NFV). Each logical network, referred to as a “network slice,” may encompass an end-to-end virtual network with dedicated storage and/or computation resources, configured to implement a different set of requirements and/or priorities, and/or may be associated with a particular Quality of Service (QoS) class, type of service, and/or particular enterprise customer associated with a set of UE devices. Examples of network slices that may be implemented in a 5G network may include a default network slice used for sessions not associated with a particular network slice; an enhanced Mobile Broadband (eMBB) network slice for Voice over Internet Protocol (VoIP) telephone calls and/or data sessions for accessing Internet websites; a massive Internet of Things (mIoT) network slice for IoT devices; an Ultra-Reliable Low Latency Communication (URLLC) network slice for URLLC communication, such as medical monitoring devices, autonomous vehicles, industrial automation, etc.; and/or other types of network slices. For example, a Mobile Private Network (MPN) for a particular enterprise may be associated with an MPN network slice. When a UE device is configured and activated by a wireless network, the UE device may be configured to connect to one or more particular network slices. The allowed slices for the UE device may be configured using a Network Slice Selection Function (NSSF) device and stored in a subscription profile, associated with the UE device, in a Unified Data Management (UDM) device. When the UE device requests a connection to a particular network slice, the UE may send a request to the Access and Mobility Function (AMF) device and the AMF device may provide a list of allowed network slices to the UE device. The UE device may then request a Packet Data Unit (PDU) connection with one or more of the allowed network slices. Therefore, the slice selection for a UE device may be performed statically during the initial configuration of the UE device. Furthermore, a UE device may connect to multiple network slices even though the UE device may not use each of the multiple network slices at any particular time. Implementations described herein relate to application driven dynamic network slice selection. A 5G network may be configured to dynamically select a particular network slice for a UE device based on the type of service or connection required by the UE device. For example, the particular network slice may be selected based on a request from an Application Function (AF) device for a particular type of session for the UE device. The AF device may be associated with an application on the UE device. For example, the UE device may run a medical monitoring application and the AF device may correspond to, or interface with, a server device associated with the medical monitoring application. The AF device may send the request in response to the AF device selecting to communicate with the UE device or in response to the UE device sending an application request to the AF device (e.g., via a default network slice). The AF device may send the request to a 5G Network Exposure Function (NEF) device configured to interface the 5G core network with AF devices. The NEF device may be configured to include a slice manager that selects a network slice for the UE device based on the request received from the AF device. The NEF device may include a slice database (DB) that stores information relating network slices to AF devices. The NEF device may receive information relating to available network slices from a NSSF device, including information identifying any newly added slices to the network. In some implementations, the NEF device may send an update relating to available network slices to AF devices based on information received from the NSSF device relating to the available network slices, including the information identifying any newly added slices to the network. For example, the NEF device may be configured to receive a session request from an AF device for a UE device; select a network slice based on AF device; send an updated allowed slices list for the UE device to a Unified Data Management (UDM) device based on the selected network slice; and send a slice selection trigger to an AMF device for the UE device in response to selecting the network slice. The slice selection trigger may include an instruction to the UE device to request the selected network slice. In some implementations, the session request received from the AF device may be received via a Representational State Transfer (REST) Application Programming Interface (API). The NEF may be further configured to receive a notification, from a User Plane Function (UPF) device associated with the selected slice, which identifies a PDU session between the UPF device and the UE device, and instruct the AF device to start a session with the UE device via the identified PDU session between the UPF device and the UE device. In some implementations, the 5G core network may include a signaling network slice that is used for sending management plane and/or control plane messages to devices in the 5G core network, to base stations, and/or to UE devices. For example, the signaling network slice may be used to send instructions to UE devices to request a particular network slice. Thus, the slice selection trigger may be sent by the NEF device to a signaling slice AMF associated with the signaling network slice. After the UE device receives the instruction from the signaling slice AMF, the UE device may send a PDU connection request to another AMF associated with the selected network slice and the NEF device may receive a notification from the selected slice AMF device indicating that the UE device has requested a session using the selected network slice. The terms “NEF device,” “NSSF device,” “AF device,” “UPF device,” and/or other network devices described herein, may refer to a dedicated hardware component implementing a network function instance via software, or to a hardware component that is part of a common shared physical infrastructure used to implement virtualized network function instances using SDN or another type of virtualization technique. Thus, the network device may be configured to implement a particular network function instance as a Virtual Network Function (VNF) (e.g., in a virtual machine), as a Cloud-native Network Function (CNF) (e.g., in a container), as a serverless architecture event handler, and/or using a different type of virtualization. The common shared physical infrastructure may be implemented using one or more computer devices in a cloud computing center, a Multi-Access Edge Computing (MEC) system associated with a base station, and/or in another type of computer system. FIG.1is a diagram of an exemplary environment100in which the systems and/or methods, described herein, may be implemented. As shown inFIG.1, environment100may include UE devices110-AA to110-NY (referred to herein collectively as “UE devices110” and individually as “UE device110”), a radio access network120, a core network130, and data networks140-A to140-N. UE device110may include any device with wireless communication functionality (e.g., using a cellular or mobile wireless network). For example, UE device110may include a handheld wireless communication device (e.g., a mobile phone, a smart phone, a tablet device, etc.); a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, etc.); a laptop computer, a tablet computer, or another type of portable computer; a desktop computer; a customer premises equipment (CPE) device, such as a set-top box or a digital media player (e.g., Apple TV, Google Chromecast, Amazon Fire TV, etc.), a WiFi access point, a smart television, etc.; a portable gaming system; a global positioning system (GPS) device; a home appliance device; a home monitoring device; and/or any other type of computer device with wireless communication capabilities and a user interface. UE device110may include capabilities for voice communication, mobile broadband services (e.g., video streaming, real-time gaming, premium Internet access etc.), best effort data traffic, and/or other types of applications. In some implementations, UE device110may communicate using machine-to-machine (M2M) communication, such as machine-type communication (MTC), and/or another type of M2M communication. For example, UE device110may include a health monitoring device (e.g., a blood pressure monitoring device, a blood glucose monitoring device, etc.), an asset tracking device (e.g., a system monitoring the geographic location of a fleet of vehicles, etc.), a traffic management device (e.g., a traffic light, traffic camera, road sensor, road illumination light, etc.), a climate controlling device (e.g., a thermostat, a ventilation system, etc.), a device controlling an electronic sign (e.g., an electronic billboard, etc.), a device controlling a manufacturing system (e.g., a robot arm, an assembly line, etc.), a device controlling a security system (e.g., a camera, a motion sensor, a window sensor, etc.), a device controlling a power system (e.g., a smart grid monitoring device, a utility meter, a fault diagnostics device, etc.), a device controlling a financial transaction system (e.g., a point-of-sale terminal, a vending machine, a parking meter, etc.), an autonomous or semi-autonomous vehicle, an unmanned aerial drone, and/or another type of electronic device. Radio access network120may enable UE devices110to connect to core network130for mobile telephone service, Short Message Service (SMS) message service, Multimedia Message Service (MMS) message service, Internet access, cloud computing, and/or other types of data services. Radio access network120may include base stations125-A to125-N (referred to herein collectively as “base stations125” and individually as “base station125”). Each base station125may service a set of UE devices110. For example, base station125-A may service UE devices110-AA to110-AX, etc., and base station125-N may service UE devices110-NA to110-NY. In other words, UE devices110-AA to110-AX may be located within the geographic area serviced by base station125-A, and other UE devices110may be serviced by another base station125. Base station125may include a 4G LTE base station (e.g., an evolved Node B (eNodeB)) or a 5G NR base station (e.g., a next generation Node B (gNodeB)). Base station125may include one or more radio frequency (RF) transceivers (also referred to as “cells” and/or “base station sectors”) facing particular directions. For example, base station125may include three RF transceivers and each RF transceiver may service a 120° sector of a 360° field of view. If base station125includes a 5G NR base station, each RF transceiver may include an antenna array. The antenna array may include an array of controllable antenna elements configured to send and receive 5G NR wireless signals via one or more antenna beams. The antenna elements may be digitally controllable to electronically tilt, or adjust the orientation of, an antenna beam in a vertical direction and/or horizontal direction. In some implementations, the antenna elements may additionally be controllable via mechanical steering using one or more motors associated with each antenna element. The antenna array may serve k UE devices110, and may simultaneously generate up to k antenna beams. A particular antenna beam may service multiple UE devices110. In some implementations, base station125may also include a 4G base station (e.g., an eNodeB). Furthermore, in some implementations, base station125may include a MEC system that performs processing services for UE devices110. Core network130may manage communication sessions for UE devices110. For example, core network130may establish an Internet Protocol (IP) connection between UE device110and a particular data network140. Furthermore, core network130may enable UE device110to communicate with an application server, and/or another type of device, located in a particular data network140using a communication method that may not require the establishment of an IP connection between UE device110and data network140, such as, for example, Data over Non-Access Stratum (DoNAS). In some implementations, core network130may include a 4G LTE core network (e.g., an evolved packet core (EPC) network). In other implementations, core network130may include a Code Division Multiple Access (CDMA) network. For example, the CDMA network may include a CDMA enhanced High Rate Packet Data (eHRPD) network (which may provide access to an LTE network). Furthermore, core network130may include an LTE Advanced (LTE-A) network and/or a 5G core network or other advanced network that includes functionality such as management of 5G NR base stations in radio access network120, which may implement carrier aggregation; advanced or massive multiple-input and multiple-output (MIMO) configurations (e.g., an 8×8 antenna configuration, a 16×16 antenna configuration, a 256×256 antenna configuration, etc.); cooperative MIMO (CO-MIMO); relay stations; Heterogeneous Networks (HetNets) of overlapping small cells and macrocells; Self-Organizing Network (SON) functionality; MTC functionality, such as 1.4 MHz wide enhanced MTC (eMTC) channels (also referred to as category Cat-M1), Low Power Wide Area (LPWA) technology such as Narrow Band IoT (NB-IoT) technology, and/or other types of MTC technology; and/or other types of LTE-A and/or 5G functionality. Data networks140-A to140-N (referred to herein collectively as “data networks140” and individually as “data network140”) may each include a packet data network. A particular data network140may include, and/or be connected to and enable communication with, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), an optical network, a cable television network, a satellite network, a wireless network (e.g., a CDMA network, a general packet radio service (GPRS) network, and/or an LTE network), an ad hoc network, a telephone network (e.g., the Public Switched Telephone Network (PSTN) or a cellular network), an intranet, or a combination of networks. Some or all of a particular data network140may be managed by a communication services provider that also manages core network130, radio access network120, and/or particular UE devices110. In some implementations, a particular data network140may include an IP Multimedia Subsystem (IMS) network (not shown inFIG.1). An IMS network may include a network for delivering IP multimedia services and may provide media flows between two different UE devices110, and/or between a particular UE device110and external IP networks or external circuit-switched networks (not shown inFIG.1). AlthoughFIG.1shows exemplary components of environment100, in other implementations, environment100may include fewer components, different components, differently arranged components, or additional components than depicted inFIG.1. Additionally or alternatively, one or more components of environment100may perform functions described as being performed by one or more other components of environment100. FIG.2illustrates a system200that includes exemplary components of core network130in the context of environment100according to an implementation described herein. As shown inFIG.2, system200may include UE device110, gNodeB210, core network130, and data network140. gNodeB210may correspond to base station125. gNodeB210may include one or more devices (e.g., base stations) and other components and functionality that enable UE device110to wirelessly connect to core network130using 5G NR Radio Access Technology (RAT). For example, gNodeB210may service one or more cells, with each cell being served by a wireless transceiver with an antenna array configured for mm-wave wireless communication, and/or for lower frequency bands such as Sub 6 GHz. gNodeB210may communicate with AMF220using an N2 interface212and communicate with UPF230using an N3 interface214. Core network130may include an Access and Mobility Function (AMF)220, a User Plane Function (UPF)230, a Session Management Function (SMF)240, an Application Function (AF)250, a Unified Data Management (UDM)252, a Policy Control Function (PCF)254, a Charging Function (CHF)256, a Network Repository Function (NRF)258, a Network Exposure Function (NEF)260, a Network Slice Selection Function (NSSF)262, an Authentication Server Function (AUSF)264, a 5G Equipment Identity Register (EIR)266, a Network Data Analytics Function (NWDAF)268, a Short Message Service Function (SMSF)270, a Security Edge Protection Proxy (SEPP)272, and a Non-3GPP Inter-Working Function (N3IWF)274. WhileFIG.2depicts a single AMF220, UPF230, SMF240, AF250, UDM252, PCF254, CHF256, NRF258, NEF260, NSSF262, AUSF264, EIR266, NWDAF268, SMSF270, SEPP272, and N3IWF274for illustration purposes, in practice, core network130may include multiple AMFs220, UPFs230, SMFs240, AFs250, UDMs252, PCFs254, CHFs256, NRFs258, NEFs260, NSSFs262, AUSFs264, EIRs266, NWDAFs268, SMSFs270, SEPPs272, and/or N3IWFs274. The components depicted inFIG.2may be implemented as dedicated hardware components or as virtualized functions implemented on top of a common shared physical infrastructure using SDN. For example, an SDN controller may implement one or more of the components ofFIG.2using an adapter implementing a VNF virtual machine, a CNF container, an event driven serverless architecture interface, and/or another type of SDN architecture. The common shared physical infrastructure may be implemented using one or more devices400described below with reference toFIG.4in a cloud computing center associated with core network130. Additionally, or alternatively, some, or all, of the common shared physical infrastructure may be implemented using one or more devices400described below with reference toFIG.4using a MEC system associated with base stations125. AMF220may perform registration management, connection management, reachability management, mobility management, lawful intercepts, Short Message Service (SMS) transport between UE device110and SMSF270, session management messages transport between UE device110and SMF240, access authentication and authorization, location services management, functionality to support non-3GPP access networks, and/or other types of management processes. AMF220may be accessible by other function nodes via an Namf interface222. UPF230may maintain an anchor point for intra/inter-RAT mobility, maintain an external Packet Data Unit (PDU) point of interconnect to a particular data network140(e.g., an IMS network, a MPN, etc.), perform packet routing and forwarding, perform the user plane part of policy rule enforcement, perform packet inspection, perform lawful intercept, perform traffic usage reporting, perform QoS handling in the user plane, perform uplink traffic verification, perform transport level packet marking, perform downlink packet buffering, forward an “end marker” to a Radio Access Network node (e.g., gNodeB210), and/or perform other types of user plane processes. UPF230may communicate with SMF240using an N4 interface232and connect to data network140using an N6 interface234. SMF240may perform session establishment, session modification, and/or session release, perform IP address allocation and management, perform Dynamic Host Configuration Protocol (DHCP) functions, perform selection and control of UPF230, configure traffic steering at UPF230to guide the traffic to the correct destinations, terminate interfaces toward PCF254, perform lawful intercepts, charge data collection, support charging interfaces, control and coordinate of charging data collection, terminate session management parts of NAS messages, perform downlink data notification, manage roaming functionality, and/or perform other types of control plane processes for managing user plane data. SMF240may be accessible via an Nsmf interface242. AF250may provide services associated with a particular application, such as, for example, an application for influencing traffic routing, an application for accessing NEF260, an application for interacting with a policy framework for policy control, a third-party application running on server device280in a particular data network140, and/or other types of applications. AF250may be accessible via an Naf interface251, also referred to as an NG5 interface. For example, server device280may be configured to communicate with, or to function as, a particular AF250(shown as the dotted line connecting AF250and server device280inFIG.2). UDM252may maintain subscription information for UE devices110, manage subscriptions, generate authentication credentials, handle user identification, perform access authorization based on subscription data, perform network function registration management, maintain service and/or session continuity by maintaining assignment of SMF240for ongoing sessions, support SMS delivery, support lawful intercept functionality, and/or perform other processes associated with managing user data. UDM252may store, in a subscription profile associated with a particular UE device110, a list of network slices which the particular UE device110is allowed to access. UDM252may be accessible via a Nudm interface253. PCF254may support policies to control network behavior, provide policy rules to control plane functions (e.g., to SMF240), access subscription information relevant to policy decisions, perform policy decisions, and/or perform other types of processes associated with policy enforcement. PCF254may be accessible via Npcf interface255. CHF256may perform charging and/or billing functions for core network130. CHF256may be accessible via Nchf interface257. NRF258may support a service discovery function and maintain profiles of available network function (NF) instances and their supported services. An NF profile may include an NF instance identifier (ID), an NF type, a Public Land Mobile Network (PLMN) ID associated with the NF, network slice IDs associated with the NF, capacity information for the NF, service authorization information for the NF, supported services associated with the NF, endpoint information for each supported service associated with the NF, and/or other types of NF information. Additionally, NRF258may include one or more transport network Key Performance Indicators (KPIs) associated with the NF instance. NRF258may be accessible via an Nnrf interface259. NEF260may expose capabilities and events to other NFs, including third party NFs, AFs, edge computing NFs, and/or other types of NFs. Furthermore, NEF260may secure provisioning of information from external applications to core network130, translate information between core network130and devices/networks external to core network130, support a Packet Flow Description (PFD) function, and/or perform other types of network exposure functions. NEF260may include a slice manager that selects a network slice for a particular UE device110based on a request received from a particular AF250, as described herein. NEF260may be accessible via Nnef interface261. NSSF262may select a set of network slice instances to serve a particular UE device110, determine network slice selection assistance information (NSSAI), determine a particular AMF220to serve a particular UE device110, and/or perform other types of processing associated with network slice selection or management. NSSF262may provide a list of allowed slices for a particular UE device110to UDM252to store in a subscription profile associated with the particular UE device110. NSSF262may be accessible via Nnssf interface263. AUSF264may perform authentication. For example, AUSF264may implement an Extensible Authentication Protocol (EAP) authentication server and may store authentication keys for UE devices110. AUSF264may be accessible via Nausf interface265. EIR266may authenticate a particular UE device110based on UE device identity, such as a Permanent Equipment Identifier (PEI). For example, EIR266may check to see if a PEI has been blacklisted. EIR266may be accessible via Neir interface267. NWDAF268may collect analytics information associated with radio access network120and/or core network130. For example, NWDAF268may collect accessibility KPIs (e.g., an Radio Resource Control (RRC) setup success rate, a Radio Access Bearer (RAB) setup success rate, etc.), retainability KPIs (e.g., a call drop rate, etc.), mobility KPIs (e.g., a handover success rate, etc.), service integrity KPIs (e.g., downlink average throughput, downlink maximum throughput, uplink average throughput, uplink maximum throughput, etc.), utilization KPIs (e.g., resource block utilization rate, average processor load, etc.), availability KPIs (e.g., radio network unavailability rate, etc.), traffic KPIs (e.g., downlink traffic volume, uplink traffic volume, average number of users, maximum number of users, a number of voice bearers, a number of video bearers, etc.), response time KPIs (e.g., latency, packet arrival time, etc.), and/or other types of wireless network KPIs. SMSF270may perform SMS services for UE devices110. SMSF270may be accessible via Nsmsf interface271. SEPP272may implement application layer security for all layer information exchanged between two NFs across two different PLMNs. N3IWF274may interconnect to a non-3GPP access device, such as, for example, a WiFi access point (not shown inFIG.2). N3IWF274may facilitate handovers for UE device110between radio access network120and the non-3GPP access device. N3IWF274maybe accessible via Nn3iwf interface275. AlthoughFIG.2shows exemplary components of core network130, in other implementations, core network130may include fewer components, different components, differently arranged components, or additional components than depicted inFIG.2. Additionally or alternatively, one or more components of core network130may perform functions described as being performed by one or more other components of core network130. For example, core network130may include additional function nodes not shown inFIG.2, such as a Unified Data Repository (UDR), an Unstructured Data Storage Network Function (UDSF), a Location Management Function (LMF), a Lawful Intercept Function (LIF), a Binding Session Function (BSF), and/or other types of functions. Furthermore, while particular interfaces have been described with respect to particular function nodes inFIG.2, additionally, or alternatively, core network130may include a reference point architecture that includes point-to-point interfaces between particular function nodes. FIG.3is a diagram of a system300illustrating exemplary components of different slices of core network130. As shown inFIG.3, system300may include core network130and data networks140-A to140-N. Core network130may include a set of network functions common to all network slices, a signaling network slice310, and network slices320-B to320-N (referred to herein collectively as “network slices320” and individually as “network slice320”). For example, network functions that are common to all network slices may include AF250, UDM252, NRF258, NEF260, NSSF262, AUSF264, EIR266, NWDAF268, SMSF270, and SEPP272. In other implementations, a different set of network functions may be common to all the network slices. Furthermore, some network functions may be shared by two or more network slices, while other network slices may include separate instances of those network functions. Signaling network slice310may be configured to send management plane and/or control plane messages to UE devices110, base stations125, and/or network functions in core network130. For example, signaling network slice310may be used to send instructions to UE devices110to request a particular network slice from network slices320-B to320-N. Furthermore, signaling network slice310may monitor the reachability of particular UE devices110. Signaling network slice310may include a RAN315, AMF220-A, UPF230-A, SMF240-A, and PCF254-A. RAN315may include one or more gNodeBs210that are associated with signaling network slice310. While a single AMF220-A, UPF230-A, SMF240-A, and PCF254-A are shown in signaling network slice310for illustrative purposes, in practice, signaling network slice310network may include multiple AMFs220-A, UPFs230-A, SMFs240-A, and/or PCFs254-A. Each of network slices320may be configured to communicate with a particular one of data networks140. Network slice320may include a RAN325, AMF220, UPF230, SMF240, and PCF254. RAN325may include one or more gNodeBs210that are associated with network slice320. While a single AMF220, UPF230, SMF240, and PCF254are shown in network slice320for illustrative purposes, in practice, signaling network slice310network may include multiple AMFs220, UPFs230, SMFs240, and/or PCFs254. Network slices320may include a default network slice used when a particular network slice is not selected by UE device110, an eMBB network slice320, an mIoT network slice320, a URLLC network slice320, and/or one or more MPN network slices320associated with particular enterprises. AlthoughFIG.3shows exemplary components of system300, in other implementations, system300may include fewer components, different components, differently arranged components, or additional components than depicted inFIG.3. Additionally, or alternatively, one or more components of system300may perform functions described as being performed by one or more other components of system300. FIG.4illustrates example components of a device400according to an implementation described herein. UE device110, gNodeB210, AMF220, UPF230, SMF240, AF250, UDM252, PCF254, CHF256, NRF258, NEF260, NSSF262, AUSF264, EIR266, NWDAF268, SMSF270, SEPP272, N3IWF274, server device280, and/or other components of core network130and/or data network140, may each include one or more devices400. As shown inFIG.4, device400may include a bus410, a processor420, a memory430, an input device440, an output device450, and a communication interface460. Bus410may include a path that permits communication among the components of device400. Processor420may include any type of single-core processor, multi-core processor, microprocessor, latch-based processor, and/or processing logic (or families of processors, microprocessors, and/or processing logics) that interprets and executes instructions. In other embodiments, processor420may include an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and/or another type of integrated circuit or processing logic. Memory430may include any type of dynamic storage device that may store information and/or instructions, for execution by processor420, and/or any type of non-volatile storage device that may store information for use by processor420. For example, memory430may include a random access memory (RAM) or another type of dynamic storage device, a read-only memory (ROM) device or another type of static storage device, a content addressable memory (CAM), a magnetic and/or optical recording memory device and its corresponding drive (e.g., a hard disk drive, optical drive, etc.), and/or a removable form of memory, such as a flash memory. Input device440may allow an operator to input information into device400. Input device440may include, for example, a keyboard, a mouse, a pen, a microphone, a remote control, an audio capture device, an image and/or video capture device, a touch-screen display, and/or another type of input device. In some embodiments, device400may be managed remotely and may not include input device440. In other words, device400may be “headless” and may not include a keyboard, for example. Output device450may output information to an operator of device400. Output device450may include a display, a printer, a speaker, and/or another type of output device. For example, device400may include a display, which may include a liquid-crystal display (LCD) for displaying content to the user. In some embodiments, device400may be managed remotely and may not include output device450. In other words, device400may be “headless” and may not include a display, for example. Communication interface460may include a transceiver that enables device400to communicate with other devices and/or systems via wireless communications (e.g., radio frequency, infrared, and/or visual optics, etc.), wired communications (e.g., conductive wire, twisted pair cable, coaxial cable, transmission line, fiber optic cable, and/or waveguide, etc.), or a combination of wireless and wired communications. Communication interface460may include a transmitter that converts baseband signals to radio frequency (RF) signals and/or a receiver that converts RF signals to baseband signals. Communication interface460may be coupled to one or more antennas/antenna arrays for transmitting and receiving RF signals. Communication interface460may include a logical component that includes input and/or output ports, input and/or output systems, and/or other input and output components that facilitate the transmission of data to other devices. For example, communication interface460may include a network interface card (e.g., Ethernet card) for wired communications and/or a wireless network interface (e.g., a WiFi) card for wireless communications. Communication interface460may also include a universal serial bus (USB) port for communications over a cable, a Bluetooth™ wireless interface, a radio-frequency identification (RFID) interface, a near-field communications (NFC) wireless interface, and/or any other type of interface that converts data from one form to another form. As will be described in detail below, device400may perform certain operations relating to selection of a network slice. Device400may perform these operations in response to processor420executing software instructions contained in a computer-readable medium, such as memory430. A computer-readable medium may be defined as a non-transitory memory device. A memory device may be implemented within a single physical memory device or spread across multiple physical memory devices. The software instructions may be read into memory430from another computer-readable medium or from another device. The software instructions contained in memory430may cause processor420to perform processes described herein. Alternatively, hardwired circuitry may be used in place of, or in combination with, software instructions to implement processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software. AlthoughFIG.4shows exemplary components of device400, in other implementations, device400may include fewer components, different components, additional components, or differently arranged components than depicted inFIG.4. Additionally, or alternatively, one or more components of device400may perform one or more tasks described as being performed by one or more other components of device400. FIG.5illustrates exemplary components of NEF260. The components of NEF260may be implemented, for example, via processor420executing instructions from memory430. Alternatively, some or all of the components of NEF260may be implemented via hard-wired circuitry. As shown inFIG.5, NEF260may include s slice manager510, a slice DB520, an NSSF interface530, an AF interface540, a UDM interface550, an AMF interface560, and a SMF interface570. Slice manager510may select a particular network slice320for a particular UE device110based on a request received from AF250using information stored in slice DB520. Exemplary information that may be stored in slice DB520is described below with reference toFIG.6. NSSF interface530may be configured to communicate with NSSF262. For example, NSSF interface530may receive from NSSF262a list of network slices320present in core network130and/or a list of allowed network slices320for a particular UE device110. Slice manager510may store the information received via NSSF interface530in slice DB520. AF interface540may be configured to communicate with AF250. In some implementations, AF interface540may implement a REST API that AF250may use to communicate with NEF260. For example, AF250may use the REST API to send a service request for a particular UE device110, to receive a notification when a PDU session for the particular UE device110has been established, and/or to request that a particular network slice320be added to the allowed slice list for the particular UE device110. Furthermore, AF250may use the REST API to subscribe to network slice updates to be notified when there is a change in the network slices320available in core network130. UDM interface550may be configured to communicate with UDM252. For example, slice manager510may send an updated list of allowed network slices320for a particular UE device110to UDM252based on information received from AF250and stored in slice DB520. AMF interface560may be configured to communicate with AMF220. For example, slice manager510may send a slice selection trigger to signaling AMF220-A to instruct UE device110to select a particular network slice320and may receive an acknowledgment from signaling AMF220-A that UE device110has successfully received the slice selection trigger. Furthermore, AMF interface560may receive a notification from AMF220in the selected network slice320that UE device110has requested a PDU session connection using the selected network slice320. SMF interface570may be configured to communicate with SMF240. For example, SMF interface570may receive a notification from SMF240in the selected network slice320that UE device110has established a PDU session with UPF230. Slice manager510may send information relating to the established PDU session to AF250via AF interface540. AlthoughFIG.5shows exemplary components of NEF260, in other implementations, NEF260may include fewer components, different components, additional components, or differently arranged components than depicted inFIG.5. Additionally, or alternatively, one or more components of NEF260may perform one or more tasks described as being performed by one or more other components of NEF260. For example, in some implementations, slice DB520may be stored and/or maintained by UDM252, rather than by NEF260. FIG.6illustrates exemplary components of slice DB520. As shown inFIG.6, slice DB520may include one or more slice records600. Each slice record600may store information relating to a particular network slice320. Slice record600may include a slice identifier (ID) field610, a service type field620, and one or more AF records630. Slice ID field610may include a slice ID associated with a particular network slice320. Service type field620may store information identifying one or more service types associated with the particular network slice320. For example, service type field620may identify a Quality of Service (QoS) class (e.g., VoIP, real-time video, live gaming, URLLC, MTC, priority data, best effort data, etc.), a type of traffic associated with the particular network slice320, whether the particular network slice320is associated with an MPN, and/or other types of information used to identify the types of services associated with the particular network slice320. Each AF record630may store information relating to a particular AF250associated with the particular network slice320. AF record630may include an AF ID field640and one or more UE device records650. AF ID field640may store information identifying a particular AF250. Each UE device record650may store information identifying a particular UE device110associated with the particular AF250. UE device record650may include a UE device ID field660, a Network Slice Subnet Instance (NSSI) field670, a Data Network Name (DNN) field680, and a PDU session field690. UE device ID field660may store one or more IDs associated with the particular UE device110. For example, UE device ID field660may store an International Mobile Equipment Identity (IMEI), an International Mobile Subscriber Identity (IMSI), a Mobile Directory Number (MDN), a Mobile Station International Subscriber Directory Number (MSISDN), a Globally Unique Temporary Identity (GUTI), a Cell Radio Network Temporary Identity (CRTNI), an IP address, a Media Access Control (MAC) address, and/or another type of identifier associated with UE device110. NSSI field670may store one or more NSSIs associated with the particular UE device110. Each NSSI may correspond to an ID for a particular network slice320and may identify that the particular UE device110is allowed to access the particular network slice320. DNN field680may identify one or more DNNs associated with the particular UE device110. Each DNN may identify a particular data network140to which UE device110is allowed to connect. For example, a particular DNN may correspond to a particular NSSI associated with the particular UE device110. PDU session field690may identify a PDU session associated with the particular UE device110. For example, after the particular UE device110connects to data network140using UPF230in a selected slice, SMF240may provide information identifying the PDU session associated with the particular UE device110to slice manager510and slice manager510may store the information identifying the PDU session in PDU session field690. AlthoughFIG.6shows exemplary components/fields of slice DB520, in other implementations, slice DB520may store fewer components/fields, different components/fields, additional components/fields, or differently arranged components/fields than depicted inFIG.6. Additionally, or alternatively, one or more components/fields of slice DB520may store information described as being stored by one or more other components/fields of slice DB520. For example, whileFIG.6shows slice DB520organized based on network slices320, in other implementations, slice DB520may be organized based on AFs250, based on UE devices110, and/or based on another organization scheme. FIG.7is a flowchart700of a first network slice selection process according to an implementation described herein. In some implementations, the process ofFIG.7may be performed by NEF260. In other implementations, some or all of the process ofFIG.7may be performed by another device or a group of devices separate from NEF260. The process ofFIG.7may include receiving network slice information from an NSSF262(block710). For example, NSSF262may, at particular intervals, send information identifying the available network slices320in core network130to NEF260. NEF260may store the network slice information in slice DB520. A session request may be received from AF250for one or more UE devices110(block720). For example, AF250may send a session request to NEF260to start a session with one or more UE devices110. The session request may be initiated in response to AF250(or server device280) receiving an application session request from UE device110or in response to AF250selecting to communicate with UE device110(e.g., to perform an application update, etc.). The session request may include information identifying one or more UE devices110, information identifying an application associated with the session request, information identifying a particular network slice320associated with the session request, information identifying a service type associated with the session request, and/or other types of information associated with the session request. A network slice may be selected for the session request based on AF250and/or the one or more UE devices (block730). Slice manager510of NEF260may identify a network slice320associated with the session request based on information included in the session request and/or based on information stored in slice DB520. For example, slice manager510may identify a particular network slice record600that includes the particular AF250from which the session request was received. An update relating to allowed slices for the one or more UE devices110may be sent to UDM252(block740). For example, NEF260may send an updated network slice list for UE device110to UDM252. The updated network slice list may include information identifying UE device110and a list of network slice IDs that UE device110is allowed to access. UDM252may update the subscription profile for UE device110with the received network slice list. Furthermore, UDM252may inform signaling slice AMF220-A that the allowed slice list for UE device110has been updated. A slice selection trigger may be sent to a signaling slice AMF220for a particular UE device110of the one or more UE devices (block750) and a notification from the signaling slice AMF220may be received relating to the particular UE device110(block760). For example, NEF260may send a slice selection trigger to signaling slice AMF220-A to be sent to the particular UE device110. The slice selection trigger may include a UE device ID for the particular UE device110, an NSSID identifying the selected network slice320, a DNN identifying a particular data network140associated with the selected network slice320, and a PDU type identifying the type of PDU connection (e.g., a particular QoS class, etc.) to be requested by the particular UE device110. If the signaling slice AMF220-A is able to reach the particular UE device110and successfully send the slice selection trigger to the particular UE device110, the signaling slice AMF220-A may send a notification back to NEF260indicating that the slice selection trigger was successfully sent to the particular UE device110. If the signaling slice AMF220-A is unable to reach the particular UE device110, signaling slice AMF220-A may send an AMF notification to NEF260informing NEF260that the particular UE device110is not reachable and NEF260may notify AF250that the particular UE device110is not reachable. An AMF notification may be received from a selected slice AMF220relating to the particular UE device110(block770). After the particular UE device110requests a PDU session connection with a selected slice AMF220in the selected network slice, the selected slice AMF may send an AMF notification to NEF260indicating the particular UE device110has requested the PDU session connection. A PDU session notification may be received from a selected slice SMF240relating to the particular UE device110(block780). For example, after the particular UE device110establishes a PDU session with a selected slice UPF230, a selected slice SMF240, which manages the selected slice UPF230, may send a PDU session notification to NEF260. The PDU session notification may include a UE device ID, an ID associated with UPF230(e.g., an IP address for UPF230, etc.), a PDU session ID, a DNN, and/or other types of IDs that may be used by AF250to identify the PDU session. In some implementations, NEF260may generate a slice selection trigger ID and include the slice selection trigger ID in the slice selection trigger sent to the signaling slice AMF220-A. The slice selection trigger ID may subsequently be included in the AMF notification received from the selected slice AMF220, and/or in the PDU session notification received from the selected slice SMF240, and used by NEF260to associate the requested AMF notification and/or PDU session notification with the session request received from AF250. AF250may be instruction to start a session with the particular UE device110using the selected slice UPF230identified in the PDU session notification (block790). For example, after NEF260receives the PDU session notification from the selected slice SMF240, NEF260may send a message to AF250, instructing AF250to start the session with the particular UE device110using the established PDU session. The message may include a UE device ID, a PDU session ID, and/or a UPF ID identifying the particular UPF230associated with the PDU session (e.g., an IP address for UPF230, etc.). FIG.8is a flowchart800of a second network slice selection process according to an implementation described herein. In some implementations, the process ofFIG.8may be performed by UE device110. In other implementations, some or all of the process ofFIG.8may be performed by another device or a group of devices separate from UE device110. The process ofFIG.8may include receiving an instruction to connect to a selected network slice associated with AF250from a signaling slice AMF220-A (block810). For example, UE device110may receive a slice selection trigger from the signaling slice AMF220-A to request a connection via a particular network slice320. The slice selection trigger may include an NSSID identifying the selected network slice320, a DNN identifying a particular data network140associated with the selected network slice320, and a PDU type identifying the type of PDU connection (e.g., a particular QoS class, etc.) to be requested by UE device110. An allowed slice list from the signaling AMF220-A may be requested (block820) and the allowed slice list may be received from the signaling AMF220(block830). For example, UE device110may request an allowed slice list from the signaling AMF220-A. AMF220-A may obtain the allowed slice list from UDM252and provide the allowed slice list to UE device110. UE device110may then update the list of network slices UE device110is configured to access. The allowed slice list may include an ID for a network slice AMF220for each of the allowed network slices. A confirmation may be made that the selected network slice is allowed (block840) and a session establishment request may be sent to the selected slice AMF220(block850). UE device110may confirm that the selected network slice identified in the received slice selection trigger is included in the allowed slice list and may send a PDU session establishment request to a particular AMF220, via gNodeB210, identified in the allowed network slice list as being associated with the selected network slice320. A PDU session may be established with a selected slice UPF230(block860) and a communication may be made with AF250or server device280via the selected slice UPF230(block870). For example, the selected slice AMF220may send a PDU session request to a selected slice SMF240. The selected slice SMF240may establish a PDU session with a selected slice UPF230and send a response to the selected slice AMF220. The selected slice AMF220may then send a PDU session establishment accept message to gNodeB210and gNodeB210may send a Radio Resource Control (RRC) reconfiguration message to UE device110, indicating the PDU session has been established. UE device110may then communicate with AF250(or server device280) via the established PDU session. FIG.9is a diagram of an exemplary signal flow900according to an implementation described herein. As shown inFIG.9, signal flow900may include NSSF262sending network slice information to NEF260(signal910). For example, each time a new network slice320is configured in core network130, NSSF262may send a slice update to NEF260and NEF260may update slice DB520based on the information received from NSSF262. AF250may send a session request for UE device110to NEF260(signal920). For example, UE device110may send an application session request to server device280and server device280may respond by sending the session request to AF250. The session request may include a UE device ID, information identifying an application associated with the session request, information identifying a particular network slice320associated with the session request, information identifying a service type associated with the session request, and/or other types of information associated with the session request. In response, NEF260may send an updated allowed slices list to UDM252for UE device110(signal922). The updated allowed slices list may include information identifying the particular network slice320associated with the session request. Furthermore, NEF260may select the particular network slice320for UE device110and may send a slice selection trigger to signaling slice AMF220-A (signal924). The slice selection trigger may include a UE device ID for UE device110, an NSSID identifying the selected network slice320, a DNN identifying a particular data network140associated with the selected network slice320, and/or a PDU type identifying the type of PDU connection (e.g., a particular QoS class, etc.) to be requested by UE device110. Furthermore, in some implementations, the slice selection trigger may include a slice selection trigger ID. The signaling slice AMF220-A may forward the slice selection trigger to UE device110(signal926). UE device110may send a slice selection request to the signaling slice AMF220-A (signal930) and the signaling slice AMF220-A may request a list of the allowed slices for UE device110from UDM252(signal932). UDM252may provide the requested allowed slices list to the signaling slice AMF220-A (signal934) and the signaling slice AMF220-A may forward the allowed slices list to UE device110(signal936). Furthermore, the signaling slice AMF220-A may send an AMF notification to NEF260, indicating that UE device110has received the slice selection trigger (signal938). UE device110may confirm that selected network slice320is on the allowed slices list, identify a selected slice AMF220-B based on information included in the allowed slices list, and send a PDU session establishment request to the selected slice AMF220-B (signal940). The selected slice AMF220-B may send an AMF notification to NEF260indicating that UE device110has requested a PDU session establishment (signal942). Furthermore, the selected slice AMF220-B may send a PDU session request to a selected slice SMF240-B (signal944) and the selected slice SMF240-B may establish a PDU session between a selected slice UPF230-B (not shown inFIG.9) and UE device110. The selected slice SMF240-B may then send a PDU session notification to NEF260(signal946). The PDU session notification may include a UE device ID for UE device110, an ID associated with the selected slice UPF230-B, a PDU session ID, a DNN, and/or other types of IDs that may be used by AF250to identify the PDU session. NEF260may then send a message instructing AF250to establish a session with UE device110using the selected slice UPF230-B (signal950). The message may include a UE device ID for UE device110, a PDU session ID, and/or a UPF ID identifying the selected slice UPF230-B (e.g., an IP address for selected slice UPF230-B, etc.). AF250, or server device280, may then communicate with UE device110using the established PDU session via the selected slice UPF230-B managed by the selected slice SMF240-B (signals960and962). In the preceding specification, various preferred embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense. For example, while a series of blocks have been described with respect toFIGS.7and8, and a series of signals with respect toFIG.9, the order of the blocks and/or signals may be modified in other implementations. Further, non-dependent blocks and/or signals may be performed in parallel. It will be apparent that systems and/or methods, as described above, may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the embodiments. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code-it being understood that software and control hardware can be designed to implement the systems and methods based on the description herein. Further, certain portions, described above, may be implemented as a component that performs one or more functions. A component, as used herein, may include hardware, such as a processor, an ASIC, or a FPGA, or a combination of hardware and software (e.g., a processor executing software). It should be emphasized that the terms “comprises”/“comprising” when used in this specification are taken to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. The term “logic,” as used herein, may refer to a combination of one or more processors configured to execute instructions stored in one or more memory devices, may refer to hardwired circuitry, and/or may refer to a combination thereof. Furthermore, a logic may be included in a single device or may be distributed across multiple, and possibly remote, devices. For the purposes of describing and defining the present invention, it is additionally noted that the term “substantially” is utilized herein to represent the inherent degree of uncertainty that may be attributed to any quantitative comparison, value, measurement, or other representation. The term “substantially” is also utilized herein to represent the degree by which a quantitative representation may vary from a stated reference without resulting in a change in the basic function of the subject matter at issue. To the extent the aforementioned embodiments collect, store, or employ personal information of individuals, it should be understood that such information shall be collected, stored, and used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage and use of such information may be subject to consent of the individual to such activity, for example, through well known “opt-in” or “opt-out” processes as may be appropriate for the situation and type of information. Storage and use of personal information may be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information. No element, act, or instruction used in the present application should be construed as critical or essential to the embodiments unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. | 60,280 |
11943705 | DETAILED DESCRIPTION The embodiments described include methods, apparatuses, and systems for a radio frequency (RF) virtualization architecture. FIG.1shows a block diagram of a radio frequency (RF) virtualization architecture of a radio access technology (RAT)110and multiple radios130,140, according to an embodiment. The radio access technology (RAT)110interfaces with a virtual hardware enhancement layer (VHEL)120, allowing the RAT110to utilize at least one of a plurality of radios130,140for wireless communication. The RAT110is an underlying physical connection method for a radio-based communication network. Many modern mobile devices support several RATs in one device such as Bluetooth, Wi-Fi, and GSM, UMTS, LTE or 5G NR. The radios130,140are elements that radiate (when transmitting) a signal generated from radio access technologies (RATs) and often include baseband converters, amplifiers, other RF frontend elements, and antennas. In many mobile devices, multiple RATs may share a single radio, as is commonly found with Bluetooth and Wi-Fi. The VHEL120is an abstraction layer that facilitates interfacing the RAT110with the radios130,140over time. For an embodiment, the VHEL120pairs a standard set of control interfaces to the specific capabilities of a selected radio in which the control interfaces of the VHEL manage control, configuration, and data transfer of the RAT/radio system. RF virtualization refers to the abstraction of RF and associated baseband/IF signal processing chain from the Radio Access Technology (RAT) protocol stack. RF virtualization allows for improved software defined radio and RF operations that are leveraged by the VHEL120. Furthermore, RF virtualization converges several similar or different radios130,140, which may be co-located or geographically distributed, into one virtual pool of resources (time, frequency, space, code, power . . . ) which can be shared by one or more RAT systems (such as, RAT110). For an embodiment, the RF virtualization architecture is designed to work with several types of RF units through the adaptation layer, or VHEL120(virtual hardware enhancement layer). The VHEL120is an abstraction layer which defines common APIs (application program interfaces) needed to be used by the controller150and a BB (baseband) unit of the RAT110to interact with the RF subsystem (radios130,140). The controller150works with any plug-in (a plugin is a software component of the VHEL120on the side of the radio which can be located inside the radio or the VHEL API that connects the specific hardware features of the radio to the VHEL standard APIs) which implements VHEL APIs. Plug-ins hide hardware drivers and their internal communication protocol from the RF server. This way different radios (such as SDRs (Software Defined Radios), eCPRI (enhanced common public radio interface) radios or other radios) work together seamlessly. An embodiment includes a controller150receiving a standard set of interfaces and capabilities from a plurality of radios130,140through the abstraction layer (VHEL120), wherein the abstraction layer (VHEL120) provides an interface to connect the radio access technology (RAT110) to a corresponding one of the plurality of radios130,140. For an embodiment, a CNTRL (control)125of the VHEL120provides (step 1 ofFIG.1) the controller150with radio capabilities162. That is, each of the radios130,140have varying radio wireless communication capabilities, such as, a wireless communication transmit power, a wireless communication bandwidth, a wireless communication transmission frequency, coverage area, location, allowed transmit/receive times, etc. As stated, these capabilities are provided to the controller150. The radio capabilities162are used by the controller150to aid in matching the available radio capabilities with radio capabilities desired, needed, or required by the RAT110. An embodiment includes the controller150receiving a request from the radio access technology (RAT110) for a radio of the plurality of radios (130,140). Additional request can be made over time, such as, on a per frame basis, wherein each frame defines a structure of the wireless communication of the RAT110. For an embodiment, a VHEL client126provides (step 2 ofFIG.1) the controller150with radio resources164requested by the RAT110. For an embodiment, the VHEL client126is an adaption layer connecting the bespoke RAT capabilities to standard VHEL interfaces that can connect to the controller150. The request can include, for example, a requested bandwidth, duration, start time, cell site, a number of antennas, a transmission power, etc. For an embodiment, the controller150, allocates and connects a one of a plurality of radios that satisfies specifications of the request of the radio access technology (RAT110) as a function of time (for example, a per frame basis). Based on the radio capabilities provided to the controller150, the controller150responds to the radio resources request of the VHEL client126. The response includes a grant (step 3 ofFIG.1) that authorizes the RAT110to initiate a data connection with the assigned radio and to update the configuration of the radio based upon the authorized grant. The VHEL client126then communicates data and control information166to a VHEL server123through a data interface124and the CNTRL125interface (step 4 ofFIG.1). The VHEL server123manages the routing and configuration of pairing RATs to radios. For example, the VHEL server123can be responsible for multiplexing requests from multiple RATs to a single radio. The VHEL API122provides an interface between the VHEL server123and the radios130,140through a data link and a control link. For an embodiment, the VHEL API122connects standard control interfaces to the capabilities of the radio enabled through the radio plugin. The VHEL API122may provide an interface to send and receive I/Q samples, control the RF gain of the transmitters, or steer the antenna to a different coverage area. FIG.2shows a block diagram of a radio frequency (RF) virtualization architecture of multiple radio access technologies (RATs)210,212, and multiple radios230,240, according to another embodiment. For this embodiment, the VHEL220provides an interface to connect the radio access technologies (RAT211, RAT212) to a corresponding one of the plurality of radios230,240. For an embodiment, the multiple RATs210,212(VHEL clients226,286) send their granted (authorized) data and control requests (control information266) to the Data224interface and the CNTRL225interface of the VHEL220. The VHEL server223then routes the requests to the correct radio API and multiplexes the data and configuration requests when the RATs210,212share a radio. The VHEL API222provides an interface between the VHEL server223and the radios230,240through a data link and a control link. For an embodiment, when the RATs210,212share a radio, the VHEL server223multiplexes the data and configuration requests. The multiplexing of the shared radio with the multiple RATs210,212can be facilitated through one or more of various multiplexing configurations290, such as, frequency division multiple access (FDMA), time division multiple access (TDMA), space division multiple access (SDMA, and/or power division multiple access (PDMA). FIG.3shows a timing diagram of communication between a virtual client, a virtual server, and a controller, according to an embodiment. For an embodiment, the communication initially starts with the VHEL client310submitting a resource request to the controller330. The controller330initiates a configuration update to the VHEL server320which includes a request for updated configurations of the radios available for use by the RAT(s). The VHEL server320responds with a complete configuration update that provides the control330with the current configuration of the available radios. Based on the current configuration and the resource request, the controller330provides the VHEL client310with a resource grant which provides the VHEL client310with the resources available to the VHEL client310. The VHEL client310submits a command request to the VHEL server320, and the VHEL server320responds with a command response. For an embodiment, the command request contains the request to send or receive data, or the command request contains a request to update the configuration of the radio. For an embodiment, the command response contains the response code to the request which may include, acknowledgement, timeout, error or other control information. DL data frames and UL data frames are then exchanged between the VHEL client310and the VHEL server320as downlink and uplink communication through the radio(s) is performed. For an embodiment, the VHEL server synchronizes the timing of transmit and receive frames between disparate radios (due to different RF path lengths) to provide frame continuity and ordering for the RAT. That is, frames of data may be provided to the VHEL server from one or more radio access technologies (RATs) in which the data is organized within each successive frame of data. However, as described, different radios may be used to transmit the frames of data over time. The different radios have different propagation channels that have varying transmission propagation delays. Accordingly, the reception of data by the different radios can vary as the propagation delays through the different propagation channels varies. As described, for an embodiment, the VHEL server re-synchronizes the data received back from the different radios over time. The re-synchronized receive data is organized back into data frames that the RAT(s) are able to process. After the DL and UL communication has been performed, either the VHEL client310or the controller330initiates a resource release, which is followed by a resource release complete by the other of the VHEL client310or the controller330. The released resource is then returned to the pool of controller330allocatable resources. The controller330can then be updated with the current configuration of the available radio(s) through another exchange of configuration update and configuration update complete. FIG.4shows a block diagram of a radio frequency (RF) virtualization architecture of a radio access technology (RAT) and multiple radios that further includes a network management controller490providing policy control568, according to an embodiment. For an embodiment, the network management control490provides the controller150policies568that further control operation of the radios130,140. The policies568can influence the grants provided by the controller150to the RAT110. For different embodiments, the policies can be static, or change as a function of time. For different embodiments, the policies can be adapted or changed as a function of network performance or loading characteristics. For example, for an embodiment, a policy can define the maximum configurable transmit power from a radio as a function of location or time. For an embodiment, a policy may define the allocable frequency bands over a location of the wireless device that is communicating with one of more of the radios. For an embodiment, a policy may throttle (adjust), or limit RAT allocation of radios based upon current network traffic, RAT priority, and/or RAT radio resource usage. For an embodiment, the policy may define the required link margin/SNR/BER and enforce a desired link margin through MCS selection, radio selection and radio configuration. FIG.5shows a radio access technology (RAT)511performing operating selections and configuration management based on a response received from a controller550, according to an embodiment. For an embodiment, the RAT511selects an MCS (modulation and coding scheme) of wireless communication utilizing a selected radio based on the response of the controller550. For an embodiment, the RAT511selects frame scheduling of wireless communication utilizing a selected radio based on the response of the controller550. For an embodiment, the RAT511selects an IQ data format of wireless communication utilizing a selected radio based on the response of the controller550. As previously described, the RAT511has an associated VHEL client525that interfaces with the controller550. For an embodiment, a wireless system must maintain a prescribed bit error rate. However, the allocated radio from the controller550may not be capable of transmitting at the required output power. Therefore, for an embodiment, the RAT511updates its MCS configuration based upon the controller550response to ensure the prescribed bit error rate is maintained. FIG.6is a flow chart that includes steps of a method of operating a radio frequency (RF) virtualization architecture, according to an embodiment. A first step610includes receiving, by a controller, a standard set of interfaces and capabilities from a plurality of radios through an abstraction layer, wherein the abstraction layer provides an interface to connect a radio access technology to a corresponding one of the plurality of radios. A second step620includes receiving, by the controller, a request from the radio access technology for a radio of the plurality of radios. A third step630includes allocating and connecting, by the controller, a one of a plurality of radios that satisfies specifications of the request of the radio access technology, wherein the one of the plurality of radios that is allocated and connected to the radio access technology changes over time. For an embodiment, the request from the radio access technology for the radio of the plurality of radios occurs as frequently as once per frame, wherein the frame is defined by a frame structure of wireless communication transmitted and received by the plurality of radios. For an embodiment, the allocating and connecting, by the controller, the one of a plurality of radios that satisfies specifications of the request of the radio access technology changes from one frame to a next frame. The changes do not need to occur from one frame to the next but can occur as frequently as from one frame to another. For an embodiment, the radio access technology changes over time such that the changes are aligned with the RAT protocol framing structure. For an embodiment, the controller sets a configuration of the plurality of radios. For a least some embodiments, the configuration of the radio includes one or more of a maximum transmit power, bandwidth, etc. For at least some embodiments, the controller receives the request from the radio access technology for the radio of the plurality of radios from a VHEL (virtual hardware enhancement layer) client of the abstraction layer. For an embodiment, the VHEL client adapts an interface of the radio access technology to a standard interface used by the controller. For an embodiment, the request from the radio access technology for the radio of the plurality of radios is based on a type of data to be transmitted, wherein the type of data includes at least control data and user data. For an embodiment, the request from the radio access technology changes as a function of the type of data transmitted (for example, control versus user data). For an embodiment, the request from the radio access technology includes switching between wide beams for control data and narrow beams for user data. As will be described, for an embodiment, a switch from a wide beam to a narrow beam can be interpreted as two different radios or configuring a single radio differently. For an embodiment, the request from the radio access technology for the radio of the plurality of radios is based on transmission (downlink) and reception (uplink) request for wireless communication through the radio. For an embodiment, the radio requests by the radio access technology changes as a function of uplink versus downlink requests. For an embodiment, the request from the radio access technology for the radio of the plurality of radios is based on a signal strength of wireless devices connected to the plurality of radios. For an embodiment, the radio requested by the radio access technology changes as a function of signal strength with connected devices. For an embodiment, the request from the radio access technology for the radio of the plurality of radios is based on a location of a device the radio is to wirelessly communicate with, and/or a coverage area of the radio. For an embodiment, the radio requested by the radio access technology changes as a function of the location of the connected device and/or the coverage area of the radio. For an embodiment, the radios allocated by the controller changes as a function of the temporal capabilities of the radios. That is, different radios may have different coverage at different times. Accordingly, the radio allocated may change according to the coverage available at the different times. For at least some embodiments, the radio access technology is one of a plurality of radio access technologies. Further, the controller receives requests from each of the plurality of the radio access technologies for a radio of the plurality of radios on a per frame basis. Further, the controller allocates and connects a one of a plurality of radios that satisfies specifications of each request of the plurality of radio access technologies on the per frame basis. At least some embodiments further include multiplexing between connections of multiple of the plurality of radio access technologies to a single one of the plurality of radios. As previously stated, the multiplexing may be facilitated by one or more of various multiplexing configurations including FDMA, TDMA, SDMA, PDMA, etc. For at least some embodiments, the allocating and connecting, by the controller, the one of the plurality of radios that satisfies specifications of each request of the plurality of radio access technologies includes the one of the plurality of radios transmitting data packets provided by the radio access technology. Further, for at least some embodiments, the allocating and connecting, by the controller, the one of the plurality of radios that satisfies specifications of each request of the plurality of radio access technologies includes the one of the plurality of radios receiving data packets which are provided to the radio access technology. For at least some embodiments, the allocating and connecting, by the controller, further includes satisfying a policy control provided by a network management server. For an embodiment, the network manager creates policies for the allocating and connecting based upon network traffic & congestions. For example, for an embodiment, the policy of the network manager may include allocating and connecting the radio access technology to a single broad beam radio at night, and the allocating and connecting the radio access technology to several narrow beam radios at day. Further, for an embodiment, the policy of the network manage includes enabling/disabling radios available for allocation and connection based upon time, coverage, and spectral coordination/cohabitation. For at least some embodiments, the controller setting a configuration of the plurality of radios includes configuring the plurality of radios to satisfying a policy control provided by a network management server. For an embodiment, the network manager sets a configuration of the plurality of radios based upon network traffic & congestions. For example, for an embodiment, the policy of the network manager may include the controller setting a configuration of the plurality of radios to a single broad beam radio at night, and the setting a configuration of the plurality of radios to several narrow beam radios at day. Further, for an embodiment, the policy of the network manage includes enabling/disabling radios available for allocation and connection based upon time, coverage, and spectral coordination/cohabitation. FIG.7shows a radio frequency (RF) virtualization architecture adapted for at least satellite communication, according to an embodiment. For this embodiment, at least one of the radios700includes a frequency conversion device740communicating with Hubs710,720through a satellite791. For an embodiment, the frequency conversion device740operates to receive a baseband communication signal that is frequency upconverted before being transmitted to a hub710,720through the satellite791, and further, receives a wireless communication signal from at least one of the hubs710,720, frequency down-converts the received wireless communication signal to a baseband communication signal. For at least some embodiments, the hubs710,720are wireless devices that operates to sense or receive sensed information from sensors, and communicate the sensed information through the satellite791, the frequency conversion device740, through the VHEL120, to one or more of the RAT instances730. For an embodiment, the radio(s) formed by the frequency conversion device740and the satellite791includes multiple antennas located at the satellite791, and accordingly, wireless links715,716formed by the multiple antennas of the satellite791can include beamforming. The beamformed wireless signals of the links715,716focus the electromagnetic energy of the wireless links715,716over coverage areas, such as, coverage areal725and coverage area 2726. It is to be observed that the two different wireless links715,716have two different beam directions and have two different coverage areas725,726. Different instances of RATs730can be matched with the different radio configurations of radios700formed by the different beamforming selections. For an embodiment, different beam directions and/or different coverage area can define different selectable radios700. That is, a first radio access technology can be selectively matched to a first beam direction and a second radio access technology can be selectively matched to a second beam direction. Further, the first radio access technology can be selectively matched to a first beam coverage area and a second radio access technology can be selectively matched to a second beam coverage area. For an embodiment, different RAT instances730can request for radio resources based on a current location of one of the Hubs710,720and a location of the beam coverage area. Further, for an embodiment, a network manager (such as, network manager790) operates to control at which time a particular beam can be enabled (of a radio700), which influences the selection and time of allocation of radios700to the RAT instances730. For an embodiment, a location of a Hub710,720can be determined based on the last signal received from Hub710,720. If the last location of the hub is not available, then the Hub location is determined by other means. For an embodiment, the location of a Hub can be shared between different RAT instances when available. If hub moves from one coverage area to another coverage area, the Hub connects to a different RAT instance, wherein the different RAT instance was assigned to the same or a different radio. For an embodiment, communication occurs between RAT instances. For example, different RATs can share network related information (network characteristics, congestion, etc.) which can help RAT in requesting radio resources as well as selecting control parameters for radio (for example, MCS, frame scheduling, IQ data format, etc. as shown inFIG.5). For an embodiment, when a RAT is overloaded with data traffic, the controller150can help in balancing the radio resources assigned to the RAT and divert data traffic to other lightly loaded RAT instances. Sharing the information between RATs can influence the request of the RAT which therefore can influence the balancing provided by the controller. Although specific embodiments have been described and illustrated, the embodiments are not to be limited to the specific forms or arrangements of parts so described and illustrated. The described embodiments are to only be limited by the claims. | 24,094 |
11943706 | DETAILED DESCRIPTION Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment. The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter. FIG.2is a block diagram illustrating elements of a wireless device200(also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless terminal, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Wireless device200may be provided, for example, as discussed below with respect to wireless device4110ofFIG.17.) As shown, wireless device UE may include an antenna207(e.g., corresponding to antenna4111ofFIG.17), and transceiver circuitry201(also referred to as a transceiver, e.g., corresponding to interface4114ofFIG.17) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node4160ofFIG.17) of a radio access network. Wireless device UE may also include processing circuitry203(also referred to as a processor, e.g., corresponding to processing circuitry4120ofFIG.17) coupled to the transceiver circuitry, and memory circuitry205(also referred to as memory, e.g., corresponding to device readable medium4130ofFIG.17) coupled to the processing circuitry. The memory circuitry205may include computer readable program code that when executed by the processing circuitry203causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry203may be defined to include memory so that separate memory circuitry is not required. Wireless device UE may also include an interface (such as a user interface) coupled with processing circuitry203, and/or wireless device UE may be incorporated in a vehicle. As discussed herein, operations of wireless device UE may be performed by processing circuitry203and/or transceiver circuitry201. For example, processing circuitry203may control transceiver circuitry201to transmit communications through transceiver circuitry201over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry201from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry205, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry203, processing circuitry203performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless devices). FIG.3is a block diagram illustrating elements of a radio access network RAN node300(also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node300may be provided, for example, as discussed below with respect to network node4160ofFIG.17.) As shown, the RAN node may include transceiver circuitry301(also referred to as a transceiver, e.g., corresponding to portions of interface4190ofFIG.17) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry307(also referred to as a network interface, e.g., corresponding to portions of interface4190ofFIG.17) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include a processing circuitry303(also referred to as a processor, e.g., corresponding to processing circuitry4170) coupled to the transceiver circuitry, and a memory circuitry305(also referred to as memory, e.g., corresponding to device readable medium4180ofFIG.17) coupled to the processing circuitry. The memory circuitry305may include computer readable program code that when executed by the processing circuitry303causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry303may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the RAN node may be performed by processing circuitry303, network interface307, and/or transceiver301. For example, processing circuitry303may control transceiver301to transmit downlink communications through transceiver301over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver301from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry303may control network interface307to transmit communications through network interface307to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory305, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry303, processing circuitry303performs respective operations such as providing to the wireless device200(also referred to as UE in the description below) the thresholds to use for measurements as described below. According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless device UE may be initiated by the network node so that transmission to the wireless device is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver. FIG.4is a block diagram illustrating elements of a core network CN node (e.g., an SMF node, an AMF node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the CN node may include network interface circuitry407(also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry403(also referred to as a processor) coupled to the network interface circuitry, and memory circuitry405(also referred to as memory) coupled to the processing circuitry. The memory circuitry405may include computer readable program code that when executed by the processing circuitry403causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry403may be defined to include memory so that a separate memory circuitry is not required. As discussed herein, operations of the CN node may be performed by processing circuitry403and/or network interface circuitry407. For example, processing circuitry403may control network interface circuitry407to transmit communications through network interface circuitry407to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry403, processing circuitry403performs respective operations such as communicating with the UE over the NAS layer. PLMN Selection In current specifications, the access stratum (AS) layer in the UE may scan all radio frequency (RF) bands to find available public land mobile networks (PLMNs). The scanning may include finding the strongest cell on each carrier and reading the system information. The AS layer in the UE shall report the found PLMNs and their associated measured RSRP (reference signal received power) value to the NAS layer, which selects a PLMN to camp on according to 3GPP TS 23.122. If the UE finds that the measured RSRP value is larger than a specific value, then the UE shall report these PLMNs as “high quality signal” to the NAS layer that makes the selection among the available PLMNs. One problem identified is that the current PLMN selection criterion for determining the PLMNs may not be suitable for non-terrestrial network (NTN) cells due the different propagation in an NTN compared to a terrestrial network. One example of why this may not be suitable is that a satellite may not be suitable to select if the satellite is too close to the horizon, i.e. if the angle of elevation between the UE and the satellite (seeFIG.5) is too low. A small elevation in associated with large doppler frequency offsets and large round-trip times (RTTs) which both are aspects that impairs the link quality of service (QoS). A second problem that may occur is that the current NAS PLMN selection according to 3GPP TS 23.122 does not take any NTN specifics into consideration. Due to the significant delays, path loss and Doppler frequency offsets associated with an NTN, the NTN may not be able to offer the same QoS as a terrestrial NW. These delays, path loss, and offsets are currently not accounted for in the PLMN selection. This second problem may cause the UE to connect to a PLMN where the propagation delay is much larger than what the radio technology operating the PLMN supports, making establishing connection to a cell in the PLMN difficult or even impossible, which further on might cause large amount of interference. A set of basic mechanisms for preparing PLMN selection for NTN is described below. The mechanisms may ensure that a UE selects a suitable PLMN based on relevant NTN aspects. In one embodiment the existing PLMN selection, i.e. to determine the “high quality signal” is enhanced, in addition to RSRP, based on one or more of the following measurements performed by a UE: RSRQ (reference signal received quality), or another signal quality metric such as SINR (signal-to-interference-plus-noise ratio); RTT (round trip time); differential delay, i.e. the delay between the measured RTT and a broadcasted cell or PLMN specific RTT; UE geographical position; satellite elevation angle; satellite orbital height; and/or satellite ephemeris data In some embodiments a UE may be capable of only performing one of the above measurements. In additional or alternative embodiments, A UE may be capable of performing a few of the above listed measurements. In additional or alternative embodiments, a UE may be capable of performing all of the above measurements. The above measured metrics may be compared to corresponding thresholds that may be signalled by the network via a network node or be fixed in the 3GPP specifications. The signalling may be done by radio resource control (RRC) or NAS. The UE may signal the measured values to the NAS together with a high signal quality indicator when applicable, as exemplified in the embodiments illustrated inFIGS.6-8. Operations of the wireless device200(implemented using the structure of the block diagram ofFIG.2) will now be discussed with reference to the flow chart ofFIG.6according to some embodiments of inventive concepts. For example, modules may be stored in memory205ofFIG.2, and these modules may provide instructions so that when the instructions of a module are executed by respective wireless device processing circuitry203, processing circuitry203performs respective operations of the flow chart. Turning toFIG.6, the additional measured value specified shall be RTT to describe this embodiment. Other measurements may be used, such as one of the measurements described above. In operation600, the processing circuitry203may measure the RSRP and RTT on the frequency associated to a PLMN. In operation602, the processing circuitry203may determine whether the RSRP is greater than an RSRP threshold and whether the RTT is less than an RTT threshold. Responsive to the RSRP being greater than the RSRP threshold and the RTT being less than the RTT threshold, the processing circuitry203may forward the identification of the PLMN and a high-quality indication to the NAS in operation604. Responsive to either the RSRP being less than the RSRP threshold or the RTT being greater than the RTT threshold, the processing circuitry203may forward the identification of the PLMN and the measured RSRP and RTT values to the NAS in operation606. FIG.7illustrates an embodiment where multiple additional measurements may be taken. In operation700, the processing circuitry203may receive satellite positioning information and/or a list of a plurality of measurements to perform to find a PLMN to select. The plurality of measurements may include a plurality of different types of measurements. In some embodiments, one of the plurality of different types of measurements includes an RSRP measurement. In additional or alternative embodiments, the list of the plurality of different types of measurements may include at least one of a reference signal received quality, RSRQ, measurement a signal-to-interference-plus-noise ratio, SINR, measurement a round trip time, RTT, measurement and a differential delay measurement. In some examples, a differential delay is a difference in propagation delay of UEs in the cell. In additional or alternative examples, a differential delay is the difference in distance between the UE and a satellite. The satellite positioning information may include at least one of a UE geographical position, a satellite elevation angle, a satellite orbital height, and satellite ephemeris data. The list may also provide the threshold to use in which to compare the measurement results for each of the plurality of different types of measurements. For example, the threshold for a measurement result may indicate whether the measurement result should be above or below the specified threshold value. The one or more measurements may depend on the capability of the UE as described above. When a specified measurement is satellite specific, a default comparison result may be specified for terrestrial based PLMNs. For example, if satellite elevation angle is specified and the threshold specified is being greater than or equal to a specified angle, the default comparison result for terrestrial based PLMNs is an indication of a “yes.” Alternatively, the comparison result may indicate that it is not applicable. In operation702, the processing circuitry203may perform the plurality of measurements on a frequency associated with a found PLMN to generate a plurality of measurement results. For example, a RSRP may be measured and the additional specified measurement results in the plurality of measurement results may be generated (i.e., measured) from the frequency associated to the found PLMN. In operation704, the processing circuitry203may determine based on the plurality of measurement results whether a high-quality indication should be provided to the NAS. For example, if the RSRP is greater than an RSRP threshold and if the additional measurement results are above or below the thresholds as specified, the indication should be provided. An example of the additional plurality of measurement results may be RTT and RSRQ, and the thresholds may be RTT<RTTTHand RSRQ≥RSRQTH. Turning toFIG.8, in one embodiment, determining (704) based on the plurality of measurement results whether the high-quality indication should be provided to the NAS includes receiving, in operation800, a plurality of thresholds, each of the plurality of thresholds corresponding to one of the plurality of measurement results and indicating whether the measurement result should be above or below a threshold value. For each of the plurality of measurement results, the measurement result is compared to a corresponding threshold of the plurality of thresholds in operation802and a determination is made as to whether the measurement result is above or below the corresponding threshold in accordance with the indication of the corresponding threshold in operation804. In operation806, responsive to the measurement result being above or below the threshold in accordance with the indication for all of the plurality of measurement results, a determination is made that the high-quality indication should be provided. Returning toFIG.7, in operation706, responsive to determining that the high-quality indication should be provided, the high quality indication and an identification of the found PLMN is provided to the NAS. For example, responsive to the RSRP being greater than the RSRP threshold and the additional specified measurement results are above or below the thresholds as specified, the processing circuitry203may forward the identification of the PLMN and the high-quality indication to the NAS. Responsive to either the RSRP being less than the RSRP threshold or any of the additional specified measurement results are not above or below the thresholds as specified, the processing circuitry203may forward the identification of the PLMN and the measured RSRP and additional measurement value(s) to the NAS in operation708. In one embodiment the existing RSRP based “high quality signal” decision is complemented by a second NTN specific “high quality signal” decision that is based on the measured values for one or more of the above metrics. A combined determination of a “high quality signal” is based on both metrics, and the signaling of the measured metrics is based on the metrics and the measured values as exemplified in the below figure. If the NTN specific criteria is not met a high quality indication based on RSRP may still apply. FIG.9illustrates aspects of this embodiment. Turning toFIG.9, the additional measurement result specified is RTT. In operation900, the processing circuitry203may measure the RSRP and RTT on the frequency associated to a PLMN. In operation902, the processing circuitry203may determine whether the RSRP is greater than the specified RSRP threshold. Responsive to the RSRP not being greater than the RSRP threshold, the processing circuitry203may forward the identification of the PLMN and the measured RSRP to the NAS in operation904. Responsive to the RSRP being greater than the RSRP threshold, the processing circuitry203may determine whether the RTT is less than the RTT threshold in operation906. Responsive to the RTT being less than the RTT threshold, the processing circuitry203may forward the identification of the PLMN and a high-quality indication to the NAS in operation908. Responsive to the RTT not being less than the RTT threshold, the processing circuitry203may forward the identification of the PLMN and a high-quality RSRP indication to the NAS and the measured RTT value to the NAS in operation910. FIG.10illustrates an embodiment where multiple additional measurements may be taken. In operation1000, the processing circuitry203may receive satellite positioning information and/or a list of a plurality of measurements to perform to find a PLMN to select. The plurality of measurements may include a plurality of different types of measurements. In some embodiments, one of the plurality of different types of measurements includes an RSRP measurement. IN additional or alternative embodiments, the list of the plurality of different types of measurements may include at least one of a reference signal received quality, RSRQ, measurement a signal-to-interference-plus-noise ratio, SINR, measurement a round trip time, RTT, measurement and a differential delay measurement. In some examples, a differential delay is a difference in propagation delay of UEs in the cell. In additional or alternative examples, a differential delay is the difference in distance between the UE and a satellite. The satellite positioning information may include at least one of a UE geographical position, a satellite elevation angle, a satellite orbital height, and satellite ephemeris data. The list may also provide the threshold to use in which to compare the measurement results for each of the plurality of different types of measurements. For example, the threshold for a measurement result may indicate whether the measurement result should be above or below the specified threshold value. The one or more measurements may depend on the capability of the UE as described above. When a specified measurement is satellite specific, a default comparison result may be specified for terrestrial based PLMNs. For example, if satellite elevation angle is specified and the threshold specified is being greater than or equal to a specified angle, the default comparison result for terrestrial based PLMNs is an indication of a “yes.” Alternatively, the comparison result may indicate that it is not applicable. In operation1002, the processing circuitry203may perform the plurality of measurements on a frequency associated with a found PLMN. For example, a measurement of the RSRP and the additional specified measurements on the frequency associated with a found PLMN may be performed. In operation1004, the processing circuitry203may determine whether the RSRP is greater than the specified RSRP threshold. Responsive to the RSRP not being greater than the RSRP threshold, the processing circuitry203may forward the identification of the PLMN and the measured RSRP to the NAS in operation1006. Responsive to the RSRP being greater than the RSRP threshold, the processing circuitry203may determine whether every additional measurement result in the plurality of measurement results is above or below the corresponding threshold as specified in operation1008. For example, if the additional specified measurement results are RTT and RSRQ, the thresholds may be RTT<RTTTHand RSRQ≥RSRQTH. Determining whether every additional measurement result in the plurality of measurement results is above or below the corresponding threshold as specified is determined when RTT<RTTTHand RSRQ≥RSRQTH. Turning toFIG.11, in one embodiment, determine whether every additional measurement result in the plurality of measurement results is above or below the corresponding threshold as specified includes receiving, in operation1100, a plurality of thresholds, each of the plurality of thresholds corresponding to one of the plurality of measurement results and indicating whether the measurement result should be above or below a threshold value. For each of the plurality of measurement results, the measurement result is compared to a corresponding threshold of the plurality of thresholds in operation1102and a determination is made as to whether the measurement result is above or below the corresponding threshold in accordance with the indication of the corresponding threshold in operation1104. In operation1106, responsive to the measurement result being above or below the threshold in accordance with the indication for all of the plurality of measurement results, a determination is made that every additional measurement in the plurality of measurement results is above or below the corresponding threshold as specified. In operation1108, responsive to any measurement result not being above or below the threshold in accordance with the indication for the measurement, a determination is made that not every additional measurement result is above/below the threshold as specified. Returning toFIG.10, responsive to every of the additional specified measurement results being above or below the thresholds as specified, the processing circuitry203may forward the identification of the found PLMN and a high-quality indication to the NAS in operation1010. Responsive to any of the additional specified measurement results not being above or below the thresholds as specified, the processing circuitry203may forward the identification of the found PLMN with the high quality RSRP indication and the additional measurement results to the NAS in operation1012. For example, if RTT>RTTTHor RSRQ<RSRQTH, then the RTT and the RSRQ are not above or below the thresholds as specified. In one embodiment a UE may be required to receive the NTN PLMN system information to acquire NTN specific information specified in the NTN PLMN system information such as satellite ephemeris data, satellite orbit altitude, NTN type (e.g., LEO, MEO, GEO), constellation size (e.g., number of satellites in the constellation), maximum supported RTT, and/or number of tracking areas supported by the PLMN. The UE AS may pass this information to the NAS together with the PLMN ID. In one embodiment the UE NAS logic may rank and prioritize selection of a PLMN that qualifies as a high quality PLMN based on the AS measurements and information conveyed to NAS as described above. The NAS may also use the signalled AS information for ranking the PLMNs in case no high quality PLMN is identified. FIG.12illustrates an embodiment where the UE NAS logic may prioritize PLMNs and select a PLMN based on the prioritization. In operation1200, the processing circuitry203may receive, from an access stratum layer, for each of a plurality of public land mobile networks, PLMNs, an identification of the PLMN and one of a plurality of measurements for the PLMN or a high-quality indication for the PLMN, the PLMN being one of a terrestrial PLMN or a non-terrestrial network, NTN, PLMN. The NTN PLMN may be a type of radio access technology (RAT) that is different from terrestrial PLMNs. In operation1202, the processing circuitry203may prioritize the plurality of PLMNs based on the high-quality indication and the plurality of measurements. For example, if there are high-quality indications, the PLMNs associated with the high-quality indications may be prioritized over the PLMNs that are not associated with a high-quality indication. The PLMNs that are not associated with a high-quality indication are prioritized based on the measurements. In another embodiment the PLMN selection may support a distinction between terrestrial and non-terrestrial networks. In one embodiment, the prioritizing may include prioritizing PLMNs based on PLMN type. Turning toFIG.13, in one embodiment, the processing circuitry203may, in operation1300, prioritize terrestrial PLMNs in the plurality of PLMNs to provide a terrestrial prioritization. In operation1302, the processing circuitry203may prioritize the NTN PLMNs in the plurality of PLMNs in a NTN prioritization separate from the terrestrial prioritization. Returning toFIG.12, in operation1204, the processing circuitry203may select a PLMN to camp on from the plurality of PLMNs based on the prioritization. For example, if there are PLMNs having a high-quality indication, one of these PLMNs may be selected before a PLMN not having a high-quality indication may be selected. If there are no high-quality indications, then the selection may be based on the prioritization of the measurements. In one embodiment, the prioritization of the measurements may prioritize one type of measurement over another type of measurement. For example, an RTT measurement may take priority over a differential delay measurement such that a PLMN is selected based on the PLMN having a lower RTT measurement than other PLMNs. In one embodiment the PLMN selection may support a distinction between terrestrial and non-terrestrial networks. PLMN selection can then be based on this distinction and whether the UE supports one or the other. This is illustrated inFIG.14. Turning toFIG.14, in operation1400, the processing circuitry203may obtain an indication of whether to prioritize the terrestrial PLMNs over the NTN PLMNs. In operation1402, responsive to the indication indicating to prioritize the terrestrial PLMNs over the NTN PLMNs, the processing circuitry203selects a PLMN having a high-quality indication from the terrestrial prioritization. In operation1404, responsive to the indication indicating to prioritize the NTN PLMNs over the terrestrial PLMNs, the processing circuitry203selects a PLMN having a high-quality indication from the NTN prioritization. Returning toFIG.12, in operation1206, the processing circuitry203may perform an action to camp on the selected PLMN. In a further embodiment, the PLMN selection may support a distinction between different types of non-terrestrial networks, such as LEO, MEO and GEO. The PLMN selection from the plurality of PLMNs can then be based on this distinction. For example, the NTN PLMNs in the plurality of PLMNs may be prioritized based on a type of the NTN PLMN, wherein the type of the NTN PLMN comprises one of a low earth orbit, LEO, NTN, a medium earth orbit, MEO, NTN, or a geostationary orbit, GEO, NTN. An indication of a priority of which of the LEO PLMN, the MEO PLMN, and the GEO PLMN to select before selecting other PLMNs of the LEO PLMN, the MEO PLMN, and the GEO PLMN may be obtained and the selection of the PLMN to camp on may be in accordance with the priority. For example, responsive to receiving an indication of a PLMN for each of the LEO PLMN type, the MEO PLMN type, and the GEO PLMN type having a high-quality indication, the PLMN may be selected to camp on in accordance with the priority. The different type can also be based on satellite constellation size, orbit altitude, and/or RTT. In another embodiment an NTN PLMN may be identified as a separate type of PLMN, known as, for example, a “N-PLMN”. The NTN PLMN applies to any existing type of PLMNs such as HPLMN (“N-HPLMN”). This new PLMN type may be used to refine the PLMN selection based on PLMN type. In a further embodiment, the NTN may be identified as a separate access technology in 3GPP TS 23.122. Existing PLMN selection functionality based on access technology may then include NTN. Different types of NTNs, i.e. LEO, MEO, GEO, may be identified as separate access technologies to refine the PLMN selection based on access technology. In another embodiment the PLMN selection may be based on the RTT. In another embodiment the PLMN selection may be complemented with a set of requirements based on NTN characteristics such as orbit height, RTT or satellite ephemeris data. This information can be signalled from the AS as outlined above. One requirement may be that a UE with guaranteed bit rate, low latency requirements or high reliability requirements should ignore NTN PLMNs. In other words, the NTN PLMN is not prioritized. Another example is that UE with high requirements on battery life may deprioritize a PLMN with many tracking areas since this may be associated with heavy tracking area update signalling. Explanations are provided below for various abbreviations/acronyms used in the present disclosure. AbbreviationExplanationASAccess StratumBSBase StationBL/CEBandwidth Limited/Coverage ExtendedDRBData Radio BearerGEOGeostationary OrbitGPSGlobal Positioning SystemGWGatewayLEOLow Earth OrbitMEOMedium Earth OrbitMsg1Message 1Msg2Message 2Msg3Message 3Msg4Message 4NASNon-Access StratumNGSONon-Geostationary OrbitNWNetworkNTNNon-terrestrial NetworkRFRadio FrequencyRLCRadio Link ControlRTTRound-Trip TimeRRCRadio Resource ControlSINRSignal to Interference Noise RatioTATiming AdvanceTAUTracking Area UpdateQoSQuality of Service References are Identified Below.[1] TR 38.811, Study on New Radio (NR) to support non-terrestrial networks[2] RP-181370, Study on solutions evaluation for NR to support non-terrestrial Network Additional explanation is provided below. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. ABBREVIATIONS At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).1×RTT CDMA2000 1× Radio Transmission Technology3GPP 3rd Generation Partnership Project5G 5th GenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplexing AccessCGI Cell Global IdentifierCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCPICH Ec/No CPICH Received energy per chipdivided by the power density in the bandCQI Channel Quality informationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)E-SMLC Evolved-Serving Mobile Location CentreECGI Evolved CGIeNB E-UTRAN NodeBePDCCH enhanced Physical Downlink Control ChannelE-SMLC evolved Serving Mobile Location CenterE-UTRA Evolved UTRAE-UTRAN Evolved UTRANFDD Frequency Division DuplexFFS For Further StudyGERAN GSM EDGE Radio Access NetworkgNB Base station in NRGNSS Global Navigation Satellite SystemGSM Global System for Mobile communicationHARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionMAC Medium Access ControlMBMS Multimedia Broadcast Multicast ServicesMBSFN Multimedia Broadcast multicast service Single Frequency NetworkMBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDP Profile Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoder Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyRLM Radio Link ManagementRNC Radio Network ControllerRNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power ORReference Signal Received PowerRSRQ Reference Signal Received Quality ORReference Symbol Received QualityRSSI Received Signal Strength IndicatorRSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self Optimized NetworkSS Synchronization SignalSSS Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunication SystemUSIM Universal Subscriber Identity ModuleUTDOA Uplink Time Difference of ArrivalUTRA Universal Terrestrial Radio AccessUTRAN Universal Terrestrial Radio Access NetworkWCDMA Wide CDMAWLAN Wide Local Area Network Further definitions and embodiments are discussed below. In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” includes any and all combinations of one or more of the associated listed items. It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification. As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation. Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s). These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof. It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows. Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description. | 45,640 |
11943707 | DETAILED DESCRIPTION A core provider predicts that a device (e.g., an Internet of things (IoT) device) will enter an area of poor coverage by a wireless network provider (also referred to as a wireless network carrier). Based on the prediction, one or more rules are applied to prioritize data traffic to be received prior to entering the area of poor coverage. For example, the device may be a car and, prior to entering the area of poor coverage, map data is prioritized to be downloaded to the car over other data, such as streaming music. As a result, the map data will be available locally to the device in the area of poor coverage, though the streaming music may become unavailable prior to entering the area of poor coverage due to being deprioritized, while connectivity exists. The prediction that the device will enter the area of poor coverage may be based on cell coverage data received from the wireless network provider, connection quality data received from other devices, a location of the device, a speed of the device, a direction of the device, or any suitable combination thereof. The location of the device may be based on the base station to which the device is connected. The speed, direction, or both of the device may be based on a rate of handovers between base stations by the device. In addition to or instead of prioritizing data before entering an area of poor coverage, a route of the device may be changed to avoid or minimize an amount of time in the area of poor coverage. For example, a route selection algorithm may treat the area of poor coverage as impassable, causing a route that avoids the area to be selected. As another example, a route selection algorithm may treat the area of poor coverage as being slower to traverse (e.g., by doubling the predicted travel time through the area of poor coverage) when generating a route, causing a route that passes through the area to be selected only if a substantial time savings results. In some example embodiments, an area of poor coverage on one wireless network is also an area of adequate coverage on another wireless network. Thus, a prediction of poor coverage on a current wireless network of a device may be the basis for switching to another wireless network. A cost function may be assigned to the switch and used as part of a pathing algorithm for the device. Thus, a first path that passes through an area of poor coverage may be compared with a second path that avoids the area of poor coverage and a third path that passes through the area of poor coverage but switches wireless networks to compensate. Based on the cost functions of the physical paths, the time spent in an area of low coverage, and the switching of the wireless network, an optimal path is selected for the device. FIG.1is an architecture diagram100showing communication paths between a user endpoint (UE)110and a home public land mobile network (HPLMN)150, according to some example embodiments. The UE connects to a visited public land mobile network (VPLMN)115. The VPLMN115connects to the HPLMN150. When a user is not in their home area (generally referred to as “roaming), the VPLMN115is a network to which the UE110connects but is distinct from the HPLMN150to which the UE110is subscribed. When the user105is not roaming, the UE110connects directly to the HPLMN150, without connecting to a separate VPLMN115. In this case, the devices and services described as being in the VPLMN115are instead performed by the HPLMN150. The HPLMN150has information about the UE110such as which services are associated with the UE110, which networks around the world the device is allowed to roam over, whether the account is currently paid up, or any suitable combination thereof. The HPLMN150may, based on local policy, deny access to the network over which the UE110is roaming. When the UE110comes online, it registers with the HPLMN150. The registration data includes information such as the network over which the device is connecting (e.g., AT&T North America or Telefonica Spain), the radio access technology used (e.g., 3G or 4G), and information about the hardware (e.g., the international mobile equipment identity (IMEI) of the UE110). An IMEI uniquely identifies the hardware of the UE110and thus can be used to lookup characteristics of the UE110in a database. The VPLMN115includes a visitor location register (VLR)120. The VLR120is a database associated with a mobile switching center (MSC)125. The VLR120stores the location of the mobile devices in the service area of the MSC125. Typically, each MSC has its own VLR. Thus,FIG.1shows the MSC125to which the UE110is connected, but the VPLMN115typically comprises multiple MSCs and their corresponding VLRs. The signal transfer point (STP)140receives data from the MSC125and communicates with the STP155of the HPLMN150to achieve inter-network communication. The STP140serves as a load balancer for 2G and 3G connections. The VPLMN115also includes a mobility management entity (MME)130connected to a serving gateway (SGW)/serving general packet radio service (GPRS) support node (SGSN)135. The SGW/SGSN135connects to the packet serving gateway (PGW)180(e.g., via a direct cable connection between servers on a rack in a colocation facility, via an IP exchange (IPX) connection, via a VPN connection, or any suitable combination thereof). The MME130also connects to the Diameter routing agent (DRA)170and a domain name server (DNS)160of the HPLMN150. The VLR120, MSC125, and STP140service 2G and 3G connections from the UE110. The MME130, SGW/SGSN135, and DRA145service 4G and long-term evolution (LTE) connections from the UE110. The MME130is responsible for UE paging and transmission procedures. The MME130selects the SGW for a UE at the time the UE attaches to the VPLMN115. The130also provides the control plane function for mobility between LTE and 2G/3G access networks. The DRAs145and170are functional elements in a 3G or 4G network that provide real-time routing capabilities to ensure that messages are routed correctly. The DRAs145and170serve as load balancers for connections using the Diameter protocol (e.g., 4G and LTE connections). A home subscriber server (HSS)/home location register (HLR)175is also part of the HPLMN150. The HSS/HLR175comprises a database that contains information about each device that is authorized to use the global system for mobile communications (GSM) core network. The HSS/HLR175stores data for each subscriber identity module (SIM) card issued by the HPLMN150. Each SIM card has a unique international mobile subscriber identity (IMSI) that is used as a primary key to retrieve data for a device. In some example embodiments, the UE110(e.g., a phone) sends an attach request to a base station, which will, usually through configuration, connect to the MME130. The MME130identifies the IMSI of the UE110. The UE110may send a temporary mobile subscriber identity (TMSI) or a globally unique temporary identifier (GUTI) instead of an IMSI. In that case, the MME130determines the IMSI based on the received IMSI/GUTI or requests the IMSI from the UE110. Once the IMSI has been obtained, the MME130may have to clean up any old sessions if this was a re-attachment. Then, the MME130contacts the subscriber's HSS/HLR175in order to perform authentication. The HSS may be configured directly in the MME130. After authentication, the MME130sends an Update Location Request (ULR). This request will typically go through several DRAs and Diameter edge agents (DEAs)) on the way to the final destination. For example, the VPLMN115may have the MME130connect through the DRA145, which has a peer connection with the DRA170of the HPLMN150. The request will arrive at the DRA170of the HPLMN150, which is configured to route requests (e.g., through a VPN tunnel or an IPX connection) to the destination. Voice over IP (VoIP) traffic can be carried over the public internet or private IPX networks. By using a private network, service is unaffected by unrelated congestion on the internet, helping service providers meet quality of service (QoS) guarantees. Some providers dynamically determine whether to connect using a VPN over the internet or to connect using an IPX connection based on latency or throughput of one or more both connections. For example, a higher cost associated with an IPX connection may be incurred only when the performance gain (compared with using the internet) exceeds a predetermined threshold. The ULR will eventually arrive at the HSS/HLR175, being run by the HPLMN150. In response to receiving the ULR, the HSS/HLR175may optionally allocate the PGW180for the GPRS tunneling protocol (GTP) traffic and, if so, that information will be included in the Update Location Answer (ULA) sent back to the UE110. The PGW address may be included in the public data network (PDN) context sent back as part of the ULA. After handling the ULR, the HSS/HLR175sends back a ULA. The ULA is routed back through the DRAs145and170. The ULA includes the IMSI and the access point name (APN) of the ULR, the identifier of the PGW180through which the GTP tunnels will go, and a QoS profile for the connection. The ULA will be processed by the MME130, which will select the PGW180(or another PGW). The MME130will also choose the SGW/SGSN135, which will be the same SGW for all hearers that will be allocated for the UE. This is unlike PGW where different bearers for different APNs may go through different PGWs. The ULA contains a set of APNs that the IMSI is allowed to use. The MME130compares the set of APNs in the ULA with a set of APNs received from the UE. If there is an intersection between the two sets, the MME130selects an APN from the intersection. If there is no intersection between the two sets, the MME130rejects a request to connect using 4G and instead creates a 3G connection. Finally, the MME130will construct a Create Session Request and send it to the SGW/SGSN135. The Create Session Request includes any one or more of the IMSI of the UE110, an evolved packet system (EPS) bearer id, the APN the user is subscribing to, the IP address of the PGW180that the MME130selected for this EPS Session, a QoS profile, an evolved universal terrestrial radio access network (E-UTRAN) cell global identifier (EGCI) for the cell in which the UE110is located, and a tracking area identity (TAI) for the tracking area in which the UE110is located. The SGW/SGSN135will process the Create Session request, create a tunnel endpoint identifier (TEID) for the downlink tunnel, and send a Create Session Request to the PGW180whose IP was selected by the MME130and is part of the request the SGW/SGSN135received from the MME130. If a PGW has not already been selected (e.g., by the HSS/HLR175), the MME130selects a PGW by resolving the APN. The Create Session Request includes: the IMSI, the EPS bearer ID, the downlink TEID, the APN, the QoS profile, the ECGI, and the TAI. In response to the Create Session Request, the PGW180allocates an IP address for the UE110and notifies the policy and charging rules function (PCRF), which will look up the user access profile, verify that the user is allowed to create a new bearer and if all is well, return that policy to the PGW180. When the PGW180receives the access policy from the PCRF, it will apply those policies to the UE110. The PGW180will also allocate a TEID for the downlink tunnel back to the SGW/SGSN135. Finally, the PGW180will send back a Create Session Response, which will include: the IP address for the UE110, the EPS Bearer ID, the uplink TEID, and the authorized QoS profile. The Create Session Response will then propagate back to the MME130, which then will allocate a TEID for the uplink, which goes to the base station, which will talk to the UE110and eventually the attach completes whereby a Modify Bearer Request happens between the MME130and SGW/SGSN135to setup the downlink tunnel and finally, the GTP user (GTP-U) tunnels have been established. After the UE110is registered, additional signaling data is used for establishing and maintaining data connections (e.g., a PDN for a 4G connection or a packet data protocol (PDP) context for a 3G connection). The signaling data for establishing these data “tunnels” includes information about the cell information (e.g., a tracking area, a cell identifier, or both), which gives a rough estimate of where the device is in the physical world. The signaling data also, in some example embodiments, includes the radio access technology used (e.g., whether the connection is 3G, 4G, or 5G). As the device moves from one base station to the next, it's session will be handed over to the next base station and, typically, a request to modify the session will be sent to the HPLMN150. The request contains the updated information (new cell identifier, etc.). Since each cell identifier can be mapped to a physical location, the rate at which these updates occur can provide an indication of the speed and direction of the device. FIG.2is an architecture diagram200showing communication paths between a user endpoint110and a wireless network core provider260, according to some example embodiments. The architecture diagram200is similar to the architecture diagram100, but shows multiple HPLMNs210A and210B and a core provider260, to which both HPLMNs210route traffic. The HPLMNs210A-210B may be referred to generically as an HPLMN210, or in the aggregate as HPLMNs210. Though two HPLMNs210are shown inFIG.2, the VPLMN115connects to more or fewer HPLMNs210in various example embodiments. The UE110connects to the VPLMN115. The VPLMN115connects to the HPLMN210A or the HPLMN210B, selecting between then based on the IMSI (or a portion thereof) of the UE110. The first three digits of an IMSI indicate the country of the subscriber (e.g.,310for USA or460for China). The following two or three digits indicate the subscriber's service provider (e.g.,310for AT&T Mobility in the USA or00for CMCC in China). Thus, by using the first five or six digits of the IMSI of the UE110, the particular HPLMN for the subscriber is identified and the traffic for the UE110is routed appropriately by the VPLMN115. The HPLMN210either processes the connection itself (as shown inFIG.1) or routes the traffic for the UE110to the core provider260(e.g., via a VPN tunnel to the router250). The user105, the UE110, and the VPLMN115(including the VLR120, the MSC125, the MME130, the SGW/SGSN135, the STP140, and the DRA145) are described above with respect toFIG.1. The core provider260comprises the PGW285, the HSS/HLR275, the GGSN280, the DRA265, and the STP270. The core provider260communicates with the HPLMNs210using the router250, processes data using one or more of a DRA265, an STP270, an HSS/HLR275, a GGSN280, and a PGW285. The DRA265and the STP270in the core provider260allows the core provider260to alter the routing of communications. As a result, the core provider260may direct traffic according to a user- or customer-specific algorithm. For example, a call-redirection service may be provided by the core provider260, such that when a first phone number is dialed, the call is instead received at a device having a second phone number. The connection between the core provider260and the other end of the connection being established by the UE110may be via an IPX290, a VPN, or any suitable combination thereof. User data is all the data that the modem (e.g., as directed by an application running on the UE110) is pushing across the data connections. Some or all of the user data is transparent data. The HPLMN210and the core provider260do not access the content of transparent data. Nonetheless, just by observing the data, the quality of the connection can be measured and calculated. The maximum bandwidth assigned to this “channel” is known from the establishing of this tunnel and the actual bandwidth can be calculated by measuring the packets across the tunnel. Furthermore, the stream may contain information regarding retransmissions, which is an indication of whether there is packet loss and also, the latency can be calculated, both indicators of the quality of the channel. Additionally, a portion of the user data may be telemetry data. By providing the client (the UE110) means of communicating metrics only it can collect, the network can gain insight into statistics that it otherwise cannot obtain. For example, signaling strength is a data point that only the modem knows. As another example, the global positioning system (GPS) coordinates of the device may be sent from the device to get absolute accuracy of the physical location of the device. By enabling the client to push those metrics to the HPLMN210or the core provider260, an even more accurate heat map of the connectivity state can be achieved. There are several ways of providing the client with means of exchanging telemetry with the HPLMN210. An easy way is to provide a hypertext transport protocol (HTTP) endpoint and allow the client to push data straight to it. However, this would be, to the VPLMN115, regular data and if a prioritization has to be made, that data may also be throttled or dropped when it is needed the most. Another way is to establish a separate bearer with a higher priority and push the telemetry data across that channel. A PGW of the HPLMNs210can take those packets and push them onto a connection (such as Apache Kafka or AWS Kinesis) without inspecting the actual payload, thus offloading the processing of those packets to another system (e.g., the core provider260). This ensures that the PGW, a scarce resource within the HPLMN210, is not wasting cycles on tasks that, to it, is irrelevant. The UE110may be associated with multiple IMSIs and be able to select which IMSI to present to the VPLMN115. Thus, the UE110is able to determine which HPLMN210its connections should be forwarded to. The core provider260, in communication with the UE110and both HPLMNS210A and210B, can determine which HPLMN210the UE110should use. For example, based on a roaming cost or latency of each available HPLMN210, the core provider260may instruct the UE110to switch IMSIs. FIG.3is a coverage map300showing wireless networking coverage by a wireless networking provider, according to some example embodiments. The coverage map300includes areas310,320,330,340,350,360,370, and380, connected by routes. The coverage map300may be considered as a graph or a digraph, with nodes corresponding to the areas310-380and edges corresponding to the routes. Each edge may have a cost that corresponds to a distance or time to travel from one area to another. In a digraph, the cost between two areas may differ depending on the direction. Each of the areas310-380is associated with QoS information. InFIG.3, the area360is associated with a poor QoS, which is indicated by different shading from the areas310-350and370-380. The QoS may be measured by latency, packet loss, data transmission rate, or any suitable combination thereof. In some example embodiments, cost is factored into the QoS value. For example, the area360may have equivalent network quality to the other areas, but incur roaming charges. In some example embodiments, the out-of-network (or high cost) areas are removed from the coverage map300entirely. Additionally or alternatively, the QoS value of an area may be factored into the cost of edges connecting to the area. For example, each edge connecting two high-QoS regions may be set to a value of 1. Thus, a least-cost path from one region to another will be a path that minimizes the number of regions, which, assuming that each region is approximately the same size, will correspond to a shortest path. Each edge connecting from a high-QoS region to a low-QoS region may be set to a value of 100. Accordingly, the least-cost path will minimize the number of high-QoS regions encountered, even at the cost of increasing the total number of regions by up to 100. Furthermore, the edge value may be set as a continuous function of QoS rather than as a step function, allowing for finer gradation of the tradeoff between distance and QoS. The coverage map300may be created by the network map module1260ofFIG.12. For example, the network map module1260may access, over a network, statistics data for a wireless carrier. In some example embodiments, the statistics data are provided by the core provider260. For example, the statistics data may be generated by monitoring traffic that passes through the core provider260in providing services to a plurality of UEs (e.g., hundreds or thousands of UEs). The monitoring of the traffic for a particular UE may be controlled by a user setting (also referred to as a user preference) for an account associated with the UE. Based on the statistics data, regions of high and low QoS are identified and the coverage map300is created accordingly. In some example embodiments, the statistics data comprises network bandwidth associated with a location, packet loss associated with a location, a number of connected devices associated with a location, or any suitable combination thereof. In some example embodiments, the core provider260receives, for each device connection, a QoS profile for the base station. Additionally, the core provider260measures the bandwidth of established connections. Some customers may provide additional statistics to the core provider260. By correlating the data received from many devices, a very accurate, near real-time map of connectivity heuristics are generated for a given geographical area. The data may be further enriched by taking IP connectivity, border gateway protocol (BGP) route change data, real-time transport protocol (RTP) data, simple messaging service (SMS), session initiation protocol (SIP), and voice over LTE (VoLTE) data into account. For example, VoLTE is a service in which voice packets are delivered using IP all the way to the UE110over an LIE access network. Thus, the VPLMN115does not translate the digital data to a wireless audio transmission before sending the voice packets to the UE110, reducing latency and processing by the VPLMN115. Since the VoLTE data from the UE110is destined for the core provider260, analysis of this data may be performed by the core provider260. Each of the nodes310-380has a certain set of characteristics. Some characteristics are static and others are calculated dynamically. The characteristics of a node can be divided into two main categories: 1) physical capabilities and properties and 2) key performance indicators (KPIs). Physical capabilities and properties include the radio access technologies supported by a cell tower of a region corresponding to the node. For example, a particular cell tower may support 3G and 4G, but not 2G. Also, despite identifying as supporting 4G, it may not support all available bands. These properties are important to track and assign to each node since modern that does not support the same radio access technologies as the cell tower will experience a complete lack of coverage in the region. The geographic area of a node is fairly static and can be looked up, even though it will change as operators deploy/remove cell towers. Also, the technologies supported by a cell are also quite static. For example, the radio access technology supported by the cell does not change frequently since that requires a physical change to the cell towers. This static information can be updated, based on information received from the UE110as it scans areas for available cells and radio access technologies. Also, as a device registers with the network and creates “data channels,” the radio access technology will be made available to the HPLMN210and the core provider260. Together, these data points can be used to calculate the physical capabilities and properties of a particular cell. For each radio access technology the cell is supporting, the KPIs are measured. These KPIs are very dynamic in nature and may change quickly. The KPIs may include: the current and historical bandwidth, the current packet loss, the number of connected devices, or any suitable combination thereof. For each device that is currently connected within a cell, the HPLMN210and the core provider260is enabled to determine the average throughput of the devices, the access technology it is using and based on that, calculate a value for a corresponding KPI. For example, if the bandwidth suddenly drops, or if the packet loss suddenly increases, that could be an indication that the cell area is having an issue, or perhaps the area is now servicing too many devices and is now running over capacity. Under any of these circumstances, the KPI would go down. If an area is very busy, it could also be that a device may not even be able to attach. Devices that are static, such as a traffic light, and normally would be attached to the network but no longer is, could be an indication that the area is unusually busy (or having other types of issues). If a single device drops off, it will not affect the model, but if many do, combined they will perhaps score this cell to be “busy” or “degraded.” Thus, for each node, some or all of the following may be tracked: operator name, operator mobile country code (MCC), operation mobile network code (MNC), geographic location (e.g., GPS coordinates), TAI, cell global identifier (CGI), and radio access technologies supported. For each supported radio technology, some or all of the following may be tracked: supported frequency bands, current KPI values, and moving average KPI values. The KPIs may include bandwidth, packet loss, number of connected devices, number of statically connected devices (e.g., immobile devices such as traffic lights), or any suitable combination thereof. FIG.4is a coverage map400showing wireless networking coverage by another wireless networking provider, according to some example embodiments. The coverage map400includes areas410,420,430,440,450,460,340, and480, connected by routes. The coverage map400may be considered as a graph or a digraph, with nodes corresponding to the areas410-480and edges corresponding to the routes. Each of the areas410-480is associated with QoS information. InFIG.4, the areas420and450are associated with a poor QoS, which is indicated by different shading from the areas410,430-440, and460-480. As can be seen by comparison ofFIG.3withFIG.4, the two wireless networking providers have different areas with poor QoS. As a result, redirecting network traffic from a UE to different network providers as the UE travels between areas may result in improved QoS for the UE. The coverage map400may be created by the network map module1260ofFIG.12, based on statistics data gathered from the core provider260. FIG.5is a map500of a physical region including an origin location510and a destination location520, according to some example embodiments. A path from the origin location510to the destination location520along the map may be determined by minimizing a cost function (e.g., a cost function based on distance, time, toll roads, or any suitable combination thereof). In this example, the lowest-cost route is a straight line along Hammer Lane. The map500indicates physical paths among the second map further indicates physical paths among the plurality of regions of the coverage map300, the coverage map400, other coverage maps of other wireless carriers, or any suitable combination thereof. Thus, by considering the map500and one or more coverage maps, a path from the origin location510to the destination520may be determined while taking into account the wireless coverage provided by each network carrier. FIG.6shows the area360of poor coverage by a wireless networking provider superimposed on the map500of the physical region.FIG.6also shows the origin location510and the destination location520. The straight-line path along Hammer Lane goes through the area360. Accordingly, an alternate route using March Lane may be taken to avoid the low QoS area360or the networking provider may be switched from the provider ofFIG.3to the provider ofFIG.4that does not have a low QoS area along the path from the origin location510to the destination location520. Though not shown inFIG.6, in this example, the portions of the map500not covered by the area360are covered by one or more of the areas310-350and370-380. Thus, the coverage map300combined with the map500shows that the network provider ofFIG.3has adequate overage of all of the area of the map500except for the portion shown covered by area360inFIG.6. FIG.7is a flowchart of a method700to select a physical path from an origin location to a destination location, according to some example embodiments. The method700includes operations710,720, and730. By way of example and not limitation, the method700is described as being performed by the systems and devices ofFIG.2(implemented in whole or in part as a computer1200as shown inFIG.12), using the data structures ofFIGS.3-6. In operation710, the network map module1260accesses a first map that indicates wireless network connectivity in each of a plurality of regions. For example, the UE110or a server of the core provider260may access the coverage map300for wireless network connectivity of a first HPLMN210A. The route map module1270, in operation720, accesses a second map that indicates physical paths among the plurality of regions. For example, the UE110or a server of the core provider260may access the map500of a physical region. As is discussed above with respect toFIG.6, the map500shows physical paths in an area covered by the regions of the coverage map300, with varying QoS in each region. In operation730, the planning module1280selects a physical path from an origin location to a destination location based on the first map and the second map. For example, if the QoS of the area360is poor as shown inFIG.6, the planning module1280may select a path from the origin510to the destination520along March Lane, staying within areas of high QoS. As another example, if the QoS of the area360is adequate, the planning module1280may select a path from the origin510to the destination520along Hammer Lane, minimizing the travel time without sacrificing QoS. As a result of the application of the method700, the user105of the UE110is enabled to take an optimal (e.g., a shortest, fastest, least cost, or any suitable combination thereof) path from an origin location to a destination location without sacrificing wireless connectivity quality. This enables the UE110to provide connectivity that would be lost had a route been selected without taking into account the wireless connectivity quality, improving the performance of the UE110. FIG.8is a flowchart of a method800to change from one wireless network to another while following a physical path from an origin location to a destination location, according to some example embodiments. The method800includes operations810,820,830, and840. By way of example and not limitation, the method800is described as being performed by the systems and devices ofFIG.2(implemented in whole or in part as a computer1200as shown inFIG.12), using the data structures ofFIGS.3-6. The method800may be performed instead of the method700when a request for a path is generated from the UE110. In operation810, the planning module1280determines that a current wireless network carrier has a connectivity issue on a current path. For example, the current path may be the shortest route from the origin location510to the destination location520and, as shown inFIG.6, the current wireless network carrier has a connectivity issue (in this example, a poor QoS area360) on the current path. The planning module1280determines, in operation820, that an alternative wireless network carrier has better connectivity on the current path. For example, the coverage map400for an alternative wireless network carrier shows adequate QoS in the area460, corresponding to the same physical area as the area360. In operation830, the planning module1280determines a time or a location at which to switch from the current wireless network carrier to the alternative wireless network carrier. For example, the planning module1280may determine to switch network carriers immediately before or after entering the area360, to switch networks at a time predicted to coincide with entering the area360, to switch networks at a time in which use of the wireless network traffic is below a predetermined threshold, or any suitable combination thereof. Switching carriers may be accomplished by changing the IMSI of the UE110, by changing prioritization of carriers, or any suitable combination thereof. The UE110, in operation840, follows the current path to a destination, switching network carriers at the determined time or location. For example, the UE110may be a self-driving car that drives to the destination location520, switching from the wireless service provider ofFIG.3to the wireless service provider ofFIG.4at the location or time determined in operation830. In some example embodiments, the core provider260instructs the UE110to change its IMSI to connect to a different HPLMN210without any other change in behavior by the UE110, the VPLMN115, or the HPLMNs210A-210B. As a result, the US110enjoys improved network connectivity on the path from the origin location510to the destination location520without consuming additional processing resources to perform the method800or requiring modification of the VPLMN115or the HPLMNs210A-210B. FIG.9is a flowchart of a method900to change from one physical path to another while travelling from an origin location to a destination location, according to some example embodiments. The method900includes operations910,920,930, and940. By way of example and not limitation, the method900is described as being performed by the systems and devices ofFIG.2(implemented in whole or in part as a computer1200as shown inFIG.12), using the data structures ofFIGS.3-6. The method900may be performed in combination with or instead of the methods700and800when a request for a path is generated from the UE110. In operation910, the planning module1280determines that a current wireless network carrier has a connectivity issue on a current path (e.g., as in the operation810, described above with respect toFIG.8). The planning module1280determines, in operation920, that an alternative wireless network carrier does not have better connectivity on the current path. Thus, in this example, the path from the origin location510to the destination location520encounters the area360with a connectivity issue but the area460(contrary to the way it is shown inFIG.4) also has poor wireless network connectivity. In operation930, the planning module1280determines an alternative path that avoids the connectivity issue. For example, the planning module1280select a path from the origin510to the destination520along March Lane, staying within areas of high QoS of the current wireless network. The selecting of the physical path may be based on a speed of a vehicle. For example, the speed of the vehicle and the size of the low QoS region may be used to estimate an amount of time that will be spent in the low QoS region. Based on the amount of time and a predetermined threshold (e.g., 1 minute), the planning module1280may determine to continue through the low QoS region or go around it. Additionally or alternatively, the selecting of the physical path may be based on modem capabilities of the UE110. For example, for one UE110, the method800may be performed; for another UE110with modem capabilities that preclude connection to the alternative wireless carrier of operation830, the method900may be performed. The UE110, in operation940, follows the alternative path to the destination. As a result of performing the method900, the UE110is enabled to maintain high wireless connectivity along a current path if an alternative network carrier is available and to change paths to maintain high wireless connectivity if no alternative network carrier is available. This improves the functionality of the UE110over prior art systems that would simply endure the low network connectivity when passing through the area360. FIG.10is a flowchart of a method1000to download additional data while travelling from an origin location to a destination location, according to some example embodiments. The method1000includes operations1010and1020. By way of example and not limitation, the method1000is described as being performed by the systems and devices ofFIG.2(implemented in whole or in part as a computer1200as shown inFIG.12), using the data structures ofFIGS.3-6. The method1000may be performed in combination with or instead of the methods700,800, and900when a request for a path is generated from the UE110. In operation1010, the planning module1280, based on a current path and a network connectivity map, determines an amount of time remaining before entering an area with poor wireless network connectivity. For example, the current path may be the straight-line path from the origin510to the destination520as shown inFIG.6, with the area360having poor wireless network connectivity. Based on a current rate of travel (e.g., a speed of a vehicle) and other information (e.g., a speed limit, an average rate of travel, a distance from a current location to an edge of the area360, or any suitable combination thereof), the amount of time remaining before the QoS decreases is determined. The UE110, in operation1020, based on the determined amount of time and a predetermined threshold, downloads additional data prior to entering the area with poor wireless connectivity. For example, when five minutes or less of high QoS remains, additional map data may be downloaded to decrease the probability of being unable to access a plotted route stored on a server while in the area of poor wireless connectivity. In some example embodiments, other network traffic is deprioritized while the additional data is being downloaded. For example, streaming music or video may be halted to free up bandwidth for downloading more critical information that will be used during the predicted period of low QoS. As another example, streaming music or video may be the additional data that is downloaded, such that the increased buffering of the streamed data allows for uninterrupted play while traversing the low QoS region. The prioritization of traffic for downloading may be controlled based on customer-specified rules. For example, maps may be prioritized over streaming music based on a user preference. In some example embodiments, operation1020is replaced or supplemented with a notification message presented to the user105by the UE110. The user is enabled to respond to the notification message by selecting which traffic to prioritize for download prior to entering the area with poor wireless connectivity. FIG.11is a flowchart of a method1100to maintain a connection to a current wireless network while following a physical path from an origin location to a destination location, according to some example embodiments. The method1100includes operations1110,1120,1130, and1140. By way of example and not limitation, the method1100is described as being performed by the systems and devices ofFIG.2(implemented in whole or in part as a computer1200as shown inFIG.12), using the data structures ofFIGS.3-6. The method1100may be performed in combination with or instead of the methods700,800,900, and1000when a request for a path is generated from the UE110. In operation1110, the planning module1280determines that a current wireless network carrier has a connectivity issue in a region on a current path. For example, the UE110may be a smart car travelling near a border region wherein different wireless network carriers provide connectivity on either side of the border. The current path may take the smart car back and forth across the border, such that the planning module1280detects the next border crossing and the corresponding connectivity issue for the current wireless network carrier. The planning module1280determines, in operation1120, that an alternative wireless network carrier has better connectivity on the current path. For example, the wireless network carrier that provides connectivity on the other side of the border has better connectivity during the portion of the current path that takes place on that side of the border. In operation1130, the planning module1280determines a predicted amount of time that will be spent in the region that the current wireless network carrier has a connectivity issue. For example, the planning module1280may determine, based on a current speed of the smart car, an average speed of vehicles traversing the region, or any suitable combination thereof, an amount of time expected to take to traverse the region. Thus, if the current path will simply to cross the border and maintain a heading farther into the area served by the other wireless network carrier, the predicted amount of time will be large or unbounded (e.g., hours or days). However, if the current path will cross the border only momentarily, the predicted amount of time will be small (e.g., minutes or seconds). The planning module1280, in operation1140, based on the predicted amount of time, a cost associated with switching network carriers, and a predetermined threshold, maintains connection with the current wireless carrier. The cost associated with switching network carriers may be measured in time, currency, or any suitable combination thereof. The predetermined threshold may be defined in time, currency, or any suitable combination thereof. If the cost and threshold are measured in currency, a conversion function may be used to convert them to time or to convert the predicted amount of time to currency. For example, if the predicted time minus the cost is less than the threshold, the connection with the current wireless carrier is maintained. Thus, if the predicted time is low, the cost high, or the threshold is high, the connection is more likely to be maintained and if the predicted time is high, the cost of switching is low, or the threshold is low, the wireless carrier is more likely to be switched. If the wireless carrier is switched, the operations830and840may be performed. The method1100may be used to allow a smart car or other mobile EU104to tolerate brief losses of wireless connectivity instead of incurring high costs to maintain the connectivity. Alternatively, if the predicted loss of wireless connectivity is substantial, the cost of switching mobile network providers is incurred, allowing the UE110to maintain wireless connectivity. FIG.12is a schematic diagram of a computing system1200suitable for performing one or more methods described herein, according to some example embodiments. All components need not be used in various embodiments. For example, clients (e.g., the UE110), servers (e.g., the HSS/HLR260), autonomous systems, and cloud-based network resources (e.g., the DRAs145,170,240A,240B, and265) may each be use a different set of components, or, in the case of servers for example, larger storage devices. The computer system1200includes a processor1205, a computer-storage medium1210, removable storage1215, and non-removable storage1220, all connected by a bus1240. Although the example computing device is illustrated and described as the computer system1200, the computing device may be in different forms in different embodiments. For example, the computing device1200may instead be a smartphone, a tablet, a smartwatch, or another computing device including elements the same as or similar to those illustrated and described with regard toFIG.12. Devices such as smartphones, tablets, and smartwatches are collectively referred to as “mobile devices.” Further, although the various data storage elements are illustrated as part of the computer1200, the storage may also or alternatively include cloud-based storage accessible via a network, such as the Internet, or server-based storage. The processor1205may be a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. AlthoughFIG.12shows a single processor1205, the computer system1200may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof. The computer-storage medium1210includes volatile memory1245and non-volatile memory1250. The volatile memory1245or the non-volatile memory1250stores a program1255. The computer1200may include, or have access to, a computing environment that includes a variety of computer-readable media, such as the volatile memory1245, the non-volatile memory1250, the removable storage1215, and the non-removable storage1220. Computer storage includes random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) and electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD ROM), digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium capable of storing computer-readable instructions embodying any one or more of the methodologies or functions described herein. The instructions may also reside, completely or partially, within the processor1205(e.g., within the processor's cache memory) during execution thereof by the computer system1200. The computer system1200includes or has access to a computing environment that includes an input interface1225, an output interface1230, and a communication interface1235. The output interface1230interfaces to or includes a display device, such as a touchscreen, that also may serve as an input device. The input interface1225interfaces to or includes one or more of a touchscreen, a touchpad, a mouse, a keyboard, a camera, one or more device-specific buttons, one or more sensors integrated within or coupled via wired or wireless data connections to the computer system1200, and other input devices. The computer system1200may operate in a networked environment using the communication interface1235to connect to one or more remote computers, such as database servers. The remote computer may include a personal computer (PC), server, router, network PC, peer device or other common network node, or the like. The communication interface1235may connect to a local-area network (LAN), a wide-area network (WAN), a cellular network, a WiFi network, a Bluetooth network, or other networks. Computer instructions stored on a computer-storage medium (e.g., the program1255stored in the computer-storage medium1210) are executable by the processor1205of the computer system1200. As used herein, the terms “machine-storage medium,” “device-storage medium,” and “computer-storage medium” (referred to collectively as “machine-storage medium”) mean the same thing and may be used interchangeably. The terms refer to a single or multiple storage devices and/or media (e.g., a centralized or distributed key-value store, and/or associated caches and servers) that store executable instructions and/or data, as well as cloud-based storage systems or storage networks that include multiple storage apparatus or devices. The terms shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors1205. Specific examples of machine-storage media, computer-storage media, and/or device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), field-programmable gate array (FPGA), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such transitory media, at least some of which are covered under the term “signal medium” discussed below. The term “signal medium” or “transmission medium” shall be taken to include any form of modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The terms “machine-readable medium,” “computer-readable medium,” and “device-readable medium” mean the same thing and may be used interchangeably in this disclosure. The terms are defined to include both machine-storage media and signal media. Thus, the terms include both storage devices/media and carrier waves/modulated data signals. The program1255may further be transmitted or received over a network using a transmission medium via the communication interface1235and utilizing any one of a number of well-known transfer protocols (e.g., HTTP). Examples networks include a local area network (LAN), a wide area network (WAN), the Internet, mobile telephone networks, plain old telephone service (POTS) networks, and wireless data networks (e.g., WiFi, LTE, and WiMAX networks). The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the computer system1200, and includes digital or analog communications signals or other intangible media to facilitate communication of such software. The program1255is shown as including a network map module1260, a route map module1270, and a planning module1280. Any one or more of the modules described herein may be implemented using hardware (e.g., a processor of a machine, an application-specific integrated circuit (ASIC), an FPGA, or any suitable combination thereof). Moreover, any two or more of these modules may be combined into a single module, and the functions described herein for a single module may be subdivided among multiple modules. Furthermore, according to various example embodiments, modules described herein as being implemented within a single machine, database, or device may be distributed across multiple machines, databases, or devices. The network map module1260accesses, creates, stores, or transmits data indicating QoS of one or more wireless networks. For example, data structures in a database corresponding to the maps300and400may be accessed, created, stored, or transmitted. The route map module1270accesses, creates, stores, or transmits geographic maps and routes. For example, data representing the map500may be accessed, created stored, or transmitted. The planning module1280plans, based on network map and route map data, a route from one location to another. The route may include a transition from one wireless network to another. In alternative embodiments, the computer system1200operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the computer system1200may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The computer system1200may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a smart phone, a mobile device, a network router, a network switch, a network bridge, or any machine capable of executing instructions of the program1255, sequentially or otherwise, that specify actions to be taken by the computer system1200. Further, while only a single computer system1200is illustrated, the term “machine” shall also be taken to include a collection of computer systems1200that individually or jointly execute the instructions to perform any one or more of the methodologies discussed herein. The input interface1225and the output interface1230include components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific input/output (“I/O”) components that are included in a particular computer system1200will depend on the type of computer system. For example, portable devices such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components may include many other components that are not shown inFIG.12. The input interface1225may interface with visual components (e.g., a display such as a plasma display panel, a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), other signal generators, and so forth. The input interface1225may interface with alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like. The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of the methods700,800,900,1000, and1100may be performed by one or more processors. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but also deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment, or a server farm), while in other embodiments the processors may be distributed across a number of locations. Although the embodiments of the present disclosure have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the inventive subject matter. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent, to those of skill in the art, upon reviewing the above description. In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended; that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim is still deemed to fall within the scope of that claim. | 57,888 |
11943708 | DETAILED DESCRIPTION Embodiments herein and the various features and advantageous details thereof are explained more fully with reference to non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not obscure embodiments herein. Also, embodiments described herein are not mutually exclusive, as embodiments can be combined to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which embodiments herein can be practiced and to further enable those skilled in the art to practice embodiments herein. Accordingly, the examples should not be construed as limiting the scope of embodiments herein. As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware and software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block may be physically separated into two or more interacting and discrete blocks without departing from the scope of embodiments. Likewise, the blocks may be physically combined into more complex blocks without departing from the scope of embodiments. The accompanying drawings are used to help easily understand various technical features and it should be understood that embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another. As used herein, the term “preferred” refers to a selection, an order of priority, etc., and should not be interpreted as a preference for particular embodiments. Accordingly, embodiments herein achieve a method for selecting a public land mobile network (PLMN) in a wireless communication system comprising a Global System for Mobile (GSM) network, a Code Division Multiple Access (CDMA) network and a User Equipment (UE). The method includes detecting, by the UE, that the UE is operating in an interworking mode. Further, the method includes triggering, by the UE, a manual scan in the interworking mode for acquiring a list of available GSM network based PLMNs in the wireless communication system. Furthermore, the method includes causing to display, by the UE, the list of available GSM network based PLMNs in response to triggering the manual scan in the interworking mode. Referring now to the drawings, and more particularly toFIGS.1A through4, there are shown embodiments. FIG.1Ashows various hardware components of a UE (100) for selecting a PLMN in a wireless communication system comprising a GSM network, a CDMA network and the UE (100), according to embodiments as disclosed herein. The UE (100) may be, for example, but is not limited to a cellular phone, a smart phone, a Personal Digital Assistant (PDA), a wireless modem, a tablet computer, a laptop computer, an Internet of Things (IoT) or the like. In embodiments, the UE (100) comprises a processor (110), a communicator (120), a memory (130), a timer (140), and/or a display (150). The processor (110) may be coupled with the communicator (120), the memory (130), the timer (140), and/or the display (150). The timer may be a Manual high priority service recovery (MHPSR) timer. The value of the timer (140) may be implementation dependant. The processor (110) may be configured to detect whether the UE (100) is operating in an interworking mode. The interworking mode may be a 3rd Generation Partnership Project (3GPP) and 3GPP2 interworking mode which is defined in 3GPP 23.122. In an example, based on a SIM card used, the processor (110) may determine whether the UE (100) may operate in the interworking mode or not. According to embodiments, the processor (110) may detect whether the UE (100) is operating in the interworking mode based on the SIM card being used. According to embodiments, the processor (110) may be configured to detect whether the UE (100) is operating in the interworking mode using data at, or obtainable by, the UE (100) using methods and/or implementations that would be known to a person of ordinary skill in the art. The UE (100) may support access technologies (e.g., Radio Access Technologies) defined both by 3GPP and 3GPP2 and may consider all supported access technologies in all supported bands when performing PLMN selection. During the PLMN selection process, the UE (100) may find the highest priority PLMN and to attempt to register to it. The UE (100) may follow PLMN selection procedures across both 3GPP and 3GPP2 access technologies based on the methods described herein. Further, the processor (110) may be configured to trigger a manual scan in the interworking mode for acquiring a list of available GSM network based PLMNs (also referred to as GSM network-based PLMNs herein) in the wireless communication system. In embodiments, the processor (110) may be configured to perform the manual scan in the interworking mode for acquiring the list of available GSM network based PLMNs. After triggering the manual scan in the interworking mode, the processor (110) may be configured to display (e.g., output) the list of available GSM network based PLMNs on the display (150). In embodiments, the processor (110) may be configured to display the list of available GSM network based PLMNs on the display (150) grouped according to network class PLMN. Further, the processor (110) may be configured to receive a selection of at least one PLMN from the displayed list of available GSM network based PLMNs by a user of the UE (100). In embodiments, the processor (110) may be configured to receive a selection of a preferred network class (e.g., from the displayed list of available GSM network based PLMNs) by the user of the UE (100). Based on the selection(s), the processor (110) may be configured to determine whether the UE (100) is to be registered with a selected PLMN based on one of the user selection of the at least one PLMN and/or a user selected preferred network class PLMN (also referred to herein as a selected network class and/or a preferred network class). In response to determining that the UE (100) is to be registered with the selected PLMN based on the user selection, the processor (110) may be configured to perform the UE selection on the user selected PLMN, or a PLMN equal or similar to the user selected PLMN. In an example, the network class is derived for a particular PLMN based on a below configuration in a SIM card. Preferred class3GPP SIM Preferred listHOMEHOME PLMN list (EHPLMN list/HomePLMN from IMSI)PREFOPERATOR PLMN ListANYAny available PLMNs including randomPLMNs Consider an example of an Operator PLMN list (PREF Network class) configured as below: 1) PLMN A 2) PLMN B 3) PLMN C If the user of the UE (100) selects PREF network class option in the manual selection then, the processor (110) may select and attempt registration on any of the above PLMN's in an operator PLMN list. Scenario-1 (PREF Class is selected): Consider, the UE (100) registered on PLMN B after PREF class is selected. PLMN D and PLMN E may be Equivalent PLMNs (EPLMNS) with respect to PLMN B. As per the proposed method, the UE (100) may select EPLMN's (PLMN D, PLMN E) and/or also other Operator PLMN's (PLMN A and PLMN C) (e.g., in response to the user's selection of the PREF class option in the manual selection). Scenario-2 (Single PLMN is selected): Consider, the UE (100) registered on PLMN B after manually selecting PLMN B. PLMN D and PLMN E may be Equivalent PLMNs with respect to PLMN B. As per the proposed method, the UE (100) may select only EPLMN's (PLMN D, PLMN E) (e.g., in response to the user's selection of the PLMN B in the manual selection). The UE (100) may be prevented from, or limited with regards to, attempting registration on other Operator PLMN's (PLMN A and PLMN C) (e.g., by the processor (110)) because the user of the UE (100) did not select PREF class option. In embodiments, the processor (110) determines a PLMN equal or similar to the user selected PLMN with reference to a 3GPP SIM Preferred list or a 3GPP2 Preferred list, with PLMNs included in a same class being equal or similar. In response to determining that the UE (100) is to be registered with the selected PLMN based on the user selected preferred network class PLMN, the processor (110) may be configured to perform the UE selection on the user selected preferred network class PLMN, or a PLMN equal or similar to the user selected preferred network class PLMN. In embodiments, the processor (110) determines a PLMN equal or similar to the user selected preferred network class PLMN with reference to a 3GPP SIM Preferred list or a 3GPP2 Preferred list, with PLMNs included in the selected network class being equal or similar to the selected network class. Based on a registration result from the GSM PLMN (e.g., the selected PLMN), the processor (110) may be configured to determine whether to attempt registration on the CDMA network of a corresponding GSM PLMN network (e.g., the user selected PLMN) or a network corresponding to the preferred network class selected by the user. In an example, if the 3GPP system does not support voice services (based on registration result) then, the UE (100) may determine to attempt registration on the CDMA network. In embodiments, the processor (110) may be configured to attempt registration with the selected PLMN and, after the processor (110) successfully registers with the selected PLMN, the processor (110) may be configured to perform wireless communication (e.g., transmit and/or receive data) with and/or via the selected PLMN. Further, the processor (110) may be configured to determine the selected PLMN is a low priority PLMN and start the timer (140) based on the determination. The processor (110) may determine the low priority PLMN based on a network class and/or a SIM card priority list. In embodiments, the processor (110) may be configured to determine that the selected PLMN is a low priority PLMN with reference to a 3GPP SIM Preferred list or a 3GPP2 Preferred list, with PLMNs included in at least one of the ANY class and/or the Preferred class being low priority PLMNs. In embodiments, PLMNs included in a network class of lower priority than the selected network class may be low priority PLMNs. Further, the processor (110) may be configured to detect that the timer (140) is expired and scan a high priority system corresponding to the user selected network class based on the timer expiry. The high priority system may be a better system as per an MSPL/MLPL configuration. MSPL/MLPL is discussed further above. In an example, as per Table 1, if the UE (100) is registered on a Universal Mobile Telecommunication Service (UMTS) Operator PLMN (OPLMN) (PREF class) network (e.g., record index 3), then, based on a scanning result UE (100) may move to the high priority system (e.g., record index 0, 1 or 2). In embodiments, the high priority system may include at least one PLMN of the selected network class. Further, the processor (110) may be configured to determine whether the high priority system is available (e.g., available for registration by the processor (110)) in the wireless communication system based on the scanning. The processor (110) may determine the high priority system when at least one of the selected network class is received and/or the selected PLMN is received. In response to determining that the high priority system is available in the wireless communication system, the processor (110) may be configured to attempt to register on the high priority system in the wireless communication system. In response to determining that the high priority system is not available in the wireless communication system, the processor (110) may be configured to restart the timer (140). The processor (110) may be configured to execute instructions stored in the memory (130) and to perform various processes. The communicator (120) may be configured for communicating internally between internal hardware components and/or with external devices via one or more networks. Further, the memory (130) may store instructions to be executed by the processor (110). The memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, and/or forms of electrically programmable memory (EPROM) or electrically erasable and programmable memory (EEPROM). In addition, the memory (130) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (130) is non-movable. In some examples, the memory (130) may be configured to store larger amounts of information than the memory (130). In certain examples, a non-transitory storage medium may store data that may, over time, change (e.g., in Random Access Memory (RAM) or cache). Although theFIG.1Ashows various hardware components of the UE (100), it is to be understood that embodiments are not limited thereon. In embodiments, the UE (100) may include less or more components. Further, the labels or names of the components are used only for illustrative purposes and do not limit the scope of embodiments. One or more components may be combined together to perform the same or a substantially similar function to select the PLMN in the wireless communication system. FIG.1Bshows various hardware components of the processor (110) included in the UE (100), according to embodiments as disclosed herein. In embodiments, the processor (110) includes an interworking mode detection engine (110a), a manual scan triggering engine (110b), a PLMN selection and registration engine (110c), and/or a high priority system scanning engine (110d). The interworking mode detection engine (110a) may be configured to detect that the UE (100) is operating in an interworking mode. Further, the manual scan triggering engine (110b) may be configured to trigger the manual scan in the interworking mode for acquiring a list of available GSM network based PLMNs in the wireless communication system. After triggering the manual scan in the interworking mode, the PLMN selection and registration engine (110c) may be configured to display the list of available GSM network based PLMNs on the display (150). Further, the PLMN selection and registration engine (110c) may be configured to select at least one PLMN from the displayed list of available GSM network based PLMNs by a user of the UE (100). In embodiments, the PLMN selection and registration engine (110c) may be configured to receive the selection from the user of the UE (100) of the at least one PLMN displayed in the list of available GSM network based PLMNs. Based on the selection, the PLMN selection and registration engine (110c) may be configured to determine whether the UE (100) is to be registered with the at least one PLMN based on one of the user selection and/or a user selected preferred network class PLMN. In response to determining that the UE (100) is to be registered with the at least one PLMN based on the user selection, the PLMN selection and registration engine (110c) may be configured to perform the UE selection on the user selected PLMN or a PLMN equal or similar to the user selected PLMN. In response to determining that the UE (100) is to be registered with the at least one PLMN based on the user selected preferred network class PLMN, the PLMN selection and registration engine (110c) may be configured to perform the UE selection on the user selected preferred network class PLMN or a PLMN equal or similar to the user selected preferred network class PLMN. Further, the PLMN selection and registration engine (110c) may be configured to determine the at least one selected PLMN is a low priority PLMN and start the timer (140) based on the determination. Further, the PLMN selection and registration engine (110c) may be configured to detect that the timer (140) is expired and scan a high priority system corresponding to the user selected network class based on the timer expiry using the high priority system scanning engine (110d). Further, the PLMN selection and registration engine (110c) may be configured to determine whether the high priority system is available in the wireless communication system based on the scanning. In response to determining that the high priority system is available in the wireless communication system, the PLMN selection and registration engine (110c) may be configured to attempt to register on the high priority system in the wireless communication system. In response to determining that the high priority system is not available in the wireless communication system, the PLMN selection and registration engine (110c) may be configured to restart the timer (140). Although theFIG.1Bshows various hardware components of the processor (110) but it is to be understood that embodiments are not limited thereon. In embodiments, the processor (110) may include less or more components. Further, the labels or names of the components are used only for illustrative purposes and do not limit the scope of embodiments. One or more components may be combined together to perform same or substantially similar function to select the PLMN in the wireless communication system. FIG.2Ais an example illustration in which a manual selection of a PLMN is depicted, according to embodiments as disclosed herein. Based on the proposed method, when the user selects a PLMN, the UE (100) will attempt registration on all the Radio Access Technologies (RAT's) (e.g., 3GPP and 3GPP2) that it is capable of (e.g., configured to register with). FIG.2Bis an example illustration in which a network class based manual selection is depicted, according to embodiments as disclosed herein. Based on the proposed method, the are 3 types of network classes that may be categorised into:I. Home Class (depicted as “Home”): (E) Home PLMN (HPLMN),II. Preferred Class (depicted as “Partner Networks”): All PLMN's that (U)SIM card (Operator) has tie up with. These PLMN's are configured by operator in EF_OPLMNwACT file or EF_Selector PLMN List, and/orIII. Any Class (depicted as “Other Available Networks”): All other PLMN's apart from above PLMN's. When the user selects network class (e.g., selection of the Preferred Class as depicted), the UE (100) will attempt registration on all the networks that are configured for that class in all the RAT's (e.g., 3GPP and 3GPP2) that UE is capable of. The network class may be selected by the user. This is an additional option provided to the user as part of the proposed method over existing 3GPP standard defined selection of a PLMN from the list. FIG.2Cis an example illustration in which manual selection of a Forbidden PLM (FPLMN), according to embodiments as disclosed herein. Based on the proposed method, the user has an option now to select FPLMN in Global mode. In embodiments, the FPLMN is removed from a “forbidden PLMNs” list if, after a subsequent manual selection of that FPLMN there is a successful registration thereto. FIGS.3A-3Bdepict a flow diagram (300) illustrating a method for selecting the PLMN in the wireless communication system including the GSM network, the CDMA network and the UE (100), according to embodiments as disclosed herein. The operations (302-330) may be performed by the processor (110). At302, the method includes detecting that the UE (100) is operating in the interworking mode. At304, the method includes triggering the manual scan in the interworking mode for acquiring the list of available GSM network based PLMNs in the wireless communication system. At306, the method includes causing to display the list of available GSM network based PLMNs in response to triggering the manual scan in the interworking mode. At308, the method includes selecting the at least one PLMN from the displayed list of available GSM network based PLMNs by the user of the UE (100). At310, the method includes determining whether the UE (100) is to be registered with the at least one PLMN based on one of the user selection and/or the user selected preferred network class PLMN. In response to determining that the UE is to be registered with the at least one PLMN based on the user selection then, at312, the method includes performing the UE selection on the user selected PLMN, or a PLMN equal or similar to the user selected PLMN (e.g., an Equivalent PLMN (EPLMN)). In response to determining that the UE (100) is to be registered with the at least one PLMN based on the user selected preferred network class PLMN then, at314, the method includes performing the UE selection on the user selected preferred network class PLMN, or the PLMN equal or similar to the user selected preferred network class PLMN (e.g., an EPLMN). Based on a registration result from the GSM PLMN network, the method includes determining whether to attempt registration on the CDMA network of corresponding GSM PLMN network or corresponding to the preferred network class selected by the user. At316, method includes determining whether the at least one selected PLMN is the low priority PLMN. If the at least one selected PLMN is the low priority PLMN then, at318, the method includes starting the timer (140) based on the determination that the at least one selected PLMN is the low priority PLMN. At320, the method includes detecting that the timer (140) is expired. At322, the method includes scanning the high priority system corresponding to the user selected network class (e.g., same or similar MSPL entry, or a higher priority MSPL entry). At324, the method includes determining whether the high priority system is available in the wireless communication system based on the scanning. In response to determining that the high priority system is available in the wireless communication system then, at326, the method includes attempting to register on the high priority system in the wireless communication system. In response to determining that the high priority system is not available in the wireless communication system then, at328, the method includes restarting the timer and returning to320. If the at least one selected PLMN is not the low priority PLMN then, at330, the method includes attempting to register to a high priority system (e.g., on the user selected PLMN or a PLMN equal or similar to the user selected PLMN). Conventional methods and devices for performing wireless communication according to the 3GPP2 standard automatically select a PLMN for registration without providing a user with the opportunity to manually select the PLMN for registration. This lack of functionality results in, e.g., excessive roaming charges, an inability to register to a PLMN included on a FPLMN list, and low data throughput. However, embodiments provide improved methods and devices that enable manual selection of PLMN for registration while operating under the 3GPP2 standard. In so doing, the improved methods and devices override the routine operations under the 3GPP2 standard to provide additional functionality in the form of a manual PLMN selection. Accordingly, the improved methods and devices overcome the deficiencies of the conventional methods and devices to prevent or reduce excessive roaming charges, enable registration to a PLMN included on a FPLMN list and/or improve data throughput. The various actions, acts, blocks, operations, or the like in the flow diagram300may be performed in the order presented, in a different order, or simultaneously or contemporaneously. Further, in embodiments, some of the actions, acts, blocks, operations, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of embodiments. FIG.4shows an overview of the wireless communication system (4000) including the UE (100) and a network (400), according to embodiments as disclosed herein. The network (400) may be, for example, but is not limited to the GSM network, the CDMA network, the LTE network, a new radio (NR) network and/or any other 3GPP network. The UE (100) may be configured to detect whether the UE (100) is operating in the interworking mode. In an example, based on the SIM card used, the UE (100) may determine whether the UE (100) may operate in the interworking mode or not. Further, the UE (100) may support radio access technologies defined both by 3GPP and 3GPP2 and may consider all supported access technologies in all supported bands when performing PLMN selection. During the PLMN selection process, the UE (100) may find the highest priority PLMN and to attempt to register to the highest priority PLMN. The UE (100) may follow PLMN selection procedures across both 3GPP and 3GPP2 access technologies based on the methods described herein. Further, the UE (100) may be configured to trigger the manual scan in the interworking mode for acquiring the list of available 3GPP network based PLMNs (e.g., GSM network based PLMNs or the like) in the wireless communication system (4000). In embodiments, the UE (100) may be configured to perform the manual scan in the interworking mode for acquiring the list of available 3GPP network based PLMNs. After triggering the manual scan in the interworking mode, the UE (100) may be configured to display the list of available 3GPP network based PLMNs on the display (150). Further, the UE (100) may be configured to receive the selection of the PLMN from the displayed list of available 3GPP network based PLMNs by the user of the UE (100). In embodiments, the UE (100) may be configured to receive the selection of the preferred network class (e.g., from the displayed list of available 3GPP network based PLMNs) by the user of the UE (100). Based on the selection(s), the UE (100) may be configured to determine whether the UE (100) is to be registered with the selected PLMN based on one of the user selection of the PLMN and/or a user selected preferred network class PLMN (also referred to herein as a selected network class and/or a preferred network class). In response to determining that the UE (100) is to be registered with the selected PLMN based on the user selection, the UE (100) may be configured to perform the UE selection on the user selected PLMN, or a PLMN equal or similar to the user selected PLMN. In embodiments, the UE (100) determines the PLMN equal or similar to the user selected PLMN with reference to the 3GPP SIM preferred list or the 3GPP2 preferred list, with PLMNs included in a same class, or similar classes, being equal or similar. In response to determining that the UE (100) is to be registered with the selected PLMN based on the user selected preferred network class PLMN, the UE (100) may be configured to perform the UE selection on the user selected preferred network class PLMN, or the PLMN equal or similar to the user selected preferred network class PLMN. In embodiments, the UE (100) may determine the PLMN to be equal or similar to the user selected preferred network class PLMN with reference to the 3GPP SIM preferred list or the 3GPP2 preferred list, with PLMNs included in the selected network class being equal or similar to the selected network class. Based on the registration result from the GSM PLMN (e.g., the selected PLMN), the UE (100) may be configured to determine whether to attempt registration on the CDMA network of a corresponding GSM PLMN network (e.g., the user selected PLMN) or the network corresponding to the preferred network class selected by the user. In an example, if the 3GPP system does not support voice services (based on registration result) then, the UE (100) may determine to attempt registration on the CDMA network. In embodiments, the UE (100) may be configured to attempt registration with the selected PLMN and, after the UE (100) successfully registers with the selected PLMN, the UE (100) may be configured to perform wireless communication (e.g., transmit and/or receive data) with and/or via the selected PLMN. Further, the UE (100) may be configured to determine the selected PLMN is a low priority PLMN and start the timer (140) based on the determination. The low priority PLMN may be determined based on a network class and SIM card priority list. In embodiments, the UE (100) may be configured to determine that the selected PLMN is a low priority PLMN with reference to the 3GPP SIM preferred list or a 3GPP2 preferred list, with PLMNs included in at least one of the ANY class and/or the preferred class being low priority PLMNs. In embodiments, the PLMNs included in a network class(es) of lower priority than the selected network class may be low priority PLMNs. Further, the UE (100) may be configured to detect that the timer (140) is expired and scan the high priority system corresponding to the user selected network class based on the timer expiry. The high priority system may be the better system as per MSPL/MLPL configuration. The MSPL/MLPL is discussed further above. If the selected PLMN is not the low priority PLMN then, the UE (100) may attempt to register to the high priority system. In embodiments, the high priority system may include at least one PLMN of the selected network class. Further, the UE (100) may be configured to determine whether the high priority system is available (e.g., available for registration by the processor (110)) in the wireless communication system based on the scanning. The high priority system may be determined when at least one of the selected network class is received and the selected PLMN is received. In response to determining that the high priority system is available in the wireless communication system, the UE (100) may be configured to attempt to register on the high priority system in the wireless communication system. In response to determining that the high priority system is not available in the wireless communication system, the UE (100) may be configured to restart the timer (140). Embodiments disclosed herein may be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements. According to embodiments, operations described herein as being performed by the UE (100), the processor (110), the communicator (120), the timer (140), the interworking mode detection engine (110a), the manual scan triggering engine (110b), the PLMN selection and registration engine (110c) and/or the high priority system scanning engine (110d) may be performed by processing circuitry. The term ‘processing circuitry,’ as used in the present disclosure, may refer to, for example, hardware including logic circuits; a hardware/software combination such as a processor executing software; or a combination thereof. For example, the processing circuitry more specifically may include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, application-specific integrated circuit (ASIC), etc. The various operations of methods described above may be performed by any suitable device capable of performing the operations, such as the processing circuitry discussed above. For example, as discussed above, the operations of methods described above may be performed by various hardware and/or software implemented in some form of hardware (e.g., processor, ASIC, etc.). The software may comprise an ordered listing of executable instructions for implementing logical functions, and may be embodied in any “processor-readable medium” for use by or in connection with an instruction execution system, apparatus, or device, such as a single or multiple-core processor or processor-containing system. The blocks or operations of a method or algorithm and functions described in connection with embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a tangible, non-transitory computer-readable medium. A software module may reside in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD ROM, or any other form of storage medium known in the art. The foregoing description of embodiments will so fully reveal the general nature of the same that others can, by applying current knowledge, readily modify and/or adapt for various applications such embodiments without departing from the generic concept thereof, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while embodiments herein have been described in terms of examples thereof, those skilled in the art will recognize that embodiments herein can be practiced with modification within the spirit and scope of embodiments as described herein. | 34,797 |
11943709 | DETAILED DESCRIPTION Hereinafter, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be noted that the same elements will be designated by the same reference numerals although they are shown in different drawings. In the following description, specific details such as detailed configurations and components are merely provided to assist with the overall understanding of the embodiments of the present disclosure. Therefore, it should be apparent to those skilled in the art that various changes and modifications of the embodiments described herein may be made without departing from the scope of the present disclosure. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness. The terms described below are terms defined in consideration of the functions in the present disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be determined based on the contents throughout this specification. The present disclosure may have various modifications and various embodiments, among which embodiments are described below in detail with reference to the accompanying drawings. However, it should be understood that the present disclosure is not limited to the embodiments, but includes all modifications, equivalents, and alternatives within the scope of the present disclosure. Although the terms including an ordinal number such a first, second, etc. may be used for describing various elements, the structural elements are not restricted by the terms. The terms are only used to distinguish one element from another element. For example, without departing from the scope of the present disclosure, a first structural element may be referred to as a second structural element. Similarly, the second structural element may also be referred to as the first structural element. As used herein, the term “and/or” includes any and all combinations of one or more associated items. The terms used herein are merely used to describe various embodiments of the present disclosure but are not intended to limit the present disclosure. Singular forms are intended to include plural forms unless the context clearly indicates otherwise. In the present disclosure, it should be understood that the terms “include” or “have” indicate the existence of a feature, a number, a step, an operation, a structural element, parts, or a combination thereof, and do not exclude the existence or probability of the addition of one or more other features, numerals, steps, operations, structural elements, parts, or combinations thereof. Unless defined differently, all terms used herein have the same meanings as those understood by a person skilled in the art to which the present disclosure belongs. Terms such as those defined in a generally used dictionary are to be interpreted to have the same meanings as the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the present disclosure. The electronic device according to one embodiment may be one of various types of electronic devices. The electronic devices may include, for example, a portable communication device (e.g., a smart phone), a computer, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. According to one embodiment of the disclosure, an electronic device is not limited to those described above. The terms used in the present disclosure are not intended to limit the present disclosure but are intended to include various changes, equivalents, or replacements for a corresponding embodiment. With regard to the descriptions of the accompanying drawings, similar reference numerals may be used to refer to similar or related elements. A singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise. As used herein, each of such phrases as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C,” may include all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, terms such as “1st,” “2nd,” “first,” and “second” may be used to distinguish a corresponding component from another component, but are not intended to limit the components in other aspects (e.g., importance or order). It is intended that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it indicates that the element may be coupled with the other element directly (e.g., wired), wirelessly, or via a third element. As used herein, the term “module” may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms, such as, for example, “logic,” “logic block,” “part,” and “circuitry.” A module may be a single integral component, or a minimum unit or part thereof, adapted to perform one or more functions. For example, according to one embodiment, a module may be implemented in a form of an application-specific integrated circuit (ASIC). FIG.1is a diagram illustrating a virtual BSS, according to one embodiment. A virtual BSS100is an infrastructure BSS with a group of coordinated APs. In the coordinated AP group, there is a single coordinator102and one or more member APs.FIG.1illustrates a first member AP104and a second member AP106. All member APs share the same service set identifier (SSID). All member APs may share the same basic service set identifier (BSSID). All member APs also share the association and/or authentication with a STA108, such that when the STA108is roaming within the virtual BSS100, no re-association and/or re-authentication is required. The STA108uses the same association identifier (AID) in the virtual BSS100. Specifically, after the AID is assigned by the coordinator102, it is shared among all APs in the group of coordinated APs (i.e., the first member AP104and the second member AP106ofFIG.1). The STA108selects an anchor AP, from member APs in the group of coordinated APs, based on link quality metrics, such as, for example, received signal strength indicators (RSSIs). The STA keeps a local copy of capabilities of the anchor AP and neighboring APs in the group of coordinated APs. FIG.2is a flowchart illustrating a method for dynamic AP selection by a STA, according to one embodiment. The STA obtains link quality metrics for each link between the STA and member APs, at202. Link quality metrics may be obtained through measurements at the STA (e.g., RSSI), or from information received from member APs. Such information may include, for example, a member AP's channel capacity to a coordinator, a member AP's capabilities, and a number of STAs attached to a member AP. A member AP may send all AP side link quality metric information measured at member APs (AP side link quality metrics) to the STA. New information elements (IEs) for the AP side link quality metrics are defined. The member AP may send the new IEs in a beacon.FIG.3is a diagram illustrating an IE for AP side link quality metrics, according to an embodiment. The IE includes an element identifier (ID)302, a length304, and a quantized channel capacity to a coordinator306. Referring back toFIG.2, the STA dynamically selects an anchor AP for the STA from the member APs based on the link quality metrics for each link with the member APs, at204. The anchor AP is used to relay transmissions between the STA and a coordinator. Authentication of the STA with the at least one anchor AP is shared with all APs in the coordinated AP group, allowing the STA utilize any subsequently selected anchor AP to relay transmissions without re-authentication. When the STA selects an anchor AP or switches to a new anchor AP, the STA initiates an UL transmission, at206. The STA sets an Address 1 in the MAC header to a MAC address of the selected anchor AP, sets an Address 2 to a MAC address of the STA, and sets the Address 4 to a MAC address of the coordinator. The anchor AP relays the data to the coordinator, and sets the Address 4 to the MAC address of the STA, sets the Address 2 to the MAC address of the anchor AP, and sets the Address 1 to the MAC address of the coordinator. DL packets are transmitted from the coordinator to the STA, at208. The coordinator sends the data to the anchor AP indicated in the Address 1 of the most recent UL packet from the STA. FIG.4is a flowchart illustrating a method for coordinator controlled AP selection, according to one embodiment. A STA requests switching of an anchor AP and broadcasts sounding frames, at402. The STA provides measurement information to the neighboring member APs by, for example, individually reporting channel state information (CSI) to the neighboring member APs, or broadcasting sounding neighbor discovery protocol (NDP) packets to the neighboring member APs, or reporting CSI of member APs to the anchor AP. Member APs that receive the broadcast sounding frames measure the link quality metric (e.g., RSSI) based on the sounding packets, at404, and report the link quality metric to the coordinator, at406. The coordinator selects the anchor AP for the STA based on the received link quality metrics, at408. The coordinator indicates the selected anchor AP by a data frame to the STA, at410. The coordinator sets the Address 3 to the MAC address of the STA, the Address 1 to the MAC address of the anchor AP, and the Address 2 to MAC address of the coordinator. The anchor AP relays the packet to the STA, sets the Address 1 to the MAC address of the STA, sets the Address 2 to the MAC address of the anchor AP, and sets the Address 4 to the MAC address of the coordinator. The STA uses the MAC address of the anchor AP as the Address 1 for the following or subsequent UL packets. In a combination of STA driven AP selection and coordinator controlled AP selection, the STA selects a first anchor AP for UL transmission, and the coordinator determines a second anchor AP for DL transmission. FIG.5is a diagram illustrating a virtual BSS with more than one anchor AP, according to one embodiment. Within a virtual BSS500, UL traffic flows from a STA508, to a coordinator502, via a first member anchor AP504. DL traffic flows from the coordinator502, to the STA508, via a second member anchor AP506. FIG.6is a diagram illustrating a virtual BSS with more than one anchor AP, according to another embodiment. Within a virtual BSS600, DL traffic flows from a coordinator602, to a STA608, via both a first member anchor AP604and a second member anchor AP606. Joint transmission can be performed using the same time and frequency resources, or different time and frequency resources (e.g., in a time division multiplexing (TDM)/frequency division multiplexing (FDM) manner). When the STA driven AP selection scheme is used with multiple anchor APs, the STA is required to inform the coordinator of the list of anchor APs using a new management frame. When the coordinator controlled AP selection scheme is used with multiple anchor APs, the coordinator chooses anchor APs for a STA in DL traffic, and the STA may select an anchor AP for UL transmission. If there is more than one hop from the coordinator to the STA, the coordinator controlled AP selection scheme remains similar to that described above. In STA driven AP selection, the coordinator may no longer be able to find the anchor AP of the STA based on the UL data packets. Thus, after the STA selects or switches to a new anchor AP, the STA is required to inform the coordinator of its selected/updated anchor AP using a management frame so that the coordinator can update the routing for DL traffic to the STA. FIG.7is a block diagram of an electronic device in a network environment, according to one embodiment. Referring toFIG.7, an electronic device701in a network environment700may communicate with an electronic device702via a first network798(e.g., a short-range wireless communication network), or an electronic device704or a server708via a second network799(e.g., a long-range wireless communication network). The electronic device701may communicate with the electronic device704via the server708. The electronic device701may include a processor720, a memory730, an input device750, a sound output device755, a display device760, an audio module770, a sensor module776, an interface777, a haptic module779, a camera module780, a power management module788, a battery789, a communication module790, a subscriber identification module (SIM)796, or an antenna module797. In one embodiment, at least one (e.g., the display device760or the camera module780) of the components may be omitted from the electronic device701, or one or more other components may be added to the electronic device701. In one embodiment, some of the components may be implemented as a single integrated circuit (IC). For example, the sensor module776(e.g., a fingerprint sensor, an iris sensor, an illuminance sensor, etc.) may be embedded in the display device760(e.g., a display). The processor720may execute, for example, software (e.g., a program740) to control at least one other component (e.g., a hardware or a software component) of the electronic device701coupled with the processor720, and may perform various data processing or computations. As at least part of the data processing or computations, the processor720may load a command or data received from another component (e.g., the sensor module776or the communication module790) in volatile memory732, process the command or the data stored in the volatile memory732, and store resulting data in non-volatile memory734. The processor720may include a main processor721(e.g., a central processing unit (CPU) or an application processor (AP)), and an auxiliary processor723(e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently from, or in conjunction with, the main processor721. Additionally or alternatively, the auxiliary processor723may be adapted to consume less power than the main processor721, or execute a particular function. The auxiliary processor723may be implemented as being separate from, or a part of, the main processor721. The auxiliary processor723may control at least some of the functions or states related to at least one component (e.g., the display device760, the sensor module776, or the communication module790) among the components of the electronic device701, instead of the main processor721while the main processor721is in an inactive (e.g., sleep) state, or together with the main processor721while the main processor721is in an active state (e.g., executing an application). According to one embodiment, the auxiliary processor723(e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera module780or the communication module790) functionally related to the auxiliary processor723. The memory730may store various data used by at least one component (e.g., the processor720or the sensor module776) of the electronic device701. The various data may include, for example, software (e.g., the program740) and input data or output data for a command related thereto. The memory730may include the volatile memory732or the non-volatile memory734. The program740may be stored in the memory730as software, and may include, for example, an operating system (OS)742, middleware744, or an application746. The input device750may receive a command or data to be used by another component (e.g., the processor720) of the electronic device701, from the outside (e.g., a user) of the electronic device701. The input device750may include, for example, a microphone, a mouse, or a keyboard. The sound output device755may output sound signals to the outside of the electronic device701. The sound output device755may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or recording, and the receiver may be used for receiving an incoming call. According to one embodiment, the receiver may be implemented as being separate from, or a part of, the speaker. The display device760may visually provide information to the outside (e.g., a user) of the electronic device701. The display device760may include, for example, a display, a hologram device, or a projector and control circuitry to control a corresponding one of the display, hologram device, and projector. The display device760may include touch circuitry adapted to detect a touch, or sensor circuitry (e.g., a pressure sensor) adapted to measure the intensity of force incurred by the touch. The audio module770may convert a sound into an electrical signal and vice versa. According to one embodiment, the audio module770may obtain the sound via the input device750, or output the sound via the sound output device755or a headphone of an external electronic device702directly (e.g., wired) or wirelessly coupled with the electronic device701. The sensor module776may detect an operational state (e.g., power or temperature) of the electronic device701or an environmental state (e.g., a state of a user) external to the electronic device701, and then generate an electrical signal or data value corresponding to the detected state. The sensor module776may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor. The interface777may support one or more specified protocols to be used for the electronic device701to be coupled with the external electronic device702directly (e.g., wired) or wirelessly. The interface777may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface. A connecting terminal778may include a connector via which the electronic device701may be physically connected with the external electronic device702. The connecting terminal778may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector). The haptic module779may convert an electrical signal into a mechanical stimulus (e.g., a vibration or a movement) or an electrical stimulus which may be recognized by a user via tactile sensation or kinesthetic sensation. The haptic module779may include, for example, a motor, a piezoelectric element, or an electrical stimulator. The camera module780may capture a still image or moving images. The camera module780may include one or more lenses, image sensors, image signal processors, or flashes. The power management module788may manage power supplied to the electronic device701. The power management module788may be implemented as at least part of, for example, a power management integrated circuit (PMIC). The battery789may supply power to at least one component of the electronic device701. According to one embodiment, the battery789may include, for example, a primary cell which is not rechargeable, a secondary cell which is rechargeable, or a fuel cell. The communication module790may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device701and the external electronic device (e.g., the electronic device702, the electronic device704, or the server708) and performing communication via the established communication channel. The communication module790may include one or more communication processors that are operable independently from the processor720(e.g., the AP) and supports a direct (e.g., wired) communication or a wireless communication. According to one embodiment, the communication module790may include a wireless communication module792(e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module794(e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules may communicate with the external electronic device via the first network798(e.g., a short-range communication network, such as Bluetooth™, wireless-fidelity (Wi-Fi) direct, or a standard of the Infrared Data Association (IrDA)) or the second network799(e.g., a long-range communication network, such as a cellular network, the Internet, or a computer network (e.g., LAN or wide area network (WAN)). These various types of communication modules may be implemented as a single component (e.g., a single IC), or may be implemented as multiple components (e.g., multiple ICs) that are separate from each other. The wireless communication module792may identify and authenticate the electronic device701in a communication network, such as the first network798or the second network799, using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module796. The antenna module797may transmit or receive a signal or power to or from the outside (e.g., the external electronic device) of the electronic device701. According to one embodiment, the antenna module797may include one or more antennas, and, therefrom, at least one antenna appropriate for a communication scheme used in the communication network, such as the first network798or the second network799, may be selected, for example, by the communication module790(e.g., the wireless communication module792). The signal or the power may then be transmitted or received between the communication module790and the external electronic device via the selected at least one antenna. At least some of the above-described components may be mutually coupled and communicate signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)). According to one embodiment, commands or data may be transmitted or received between the electronic device701and the external electronic device704via the server708coupled with the second network799. Each of the electronic devices702and704may be a device of a same type as, or a different type, from the electronic device701. All or some of operations to be executed at the electronic device701may be executed at one or more of the external electronic devices702,704, or708. For example, if the electronic device701should perform a function or a service automatically, or in response to a request from a user or another device, the electronic device701, instead of, or in addition to, executing the function or the service, may request the one or more external electronic devices to perform at least part of the function or the service. The one or more external electronic devices receiving the request may perform the at least part of the function or the service requested, or an additional function or an additional service related to the request, and transfer an outcome of the performing to the electronic device701. The electronic device701may provide the outcome, with or without further processing of the outcome, as at least part of a reply to the request. To that end, a cloud computing, distributed computing, or client-server computing technology may be used, for example. One embodiment may be implemented as software (e.g., the program740) including one or more instructions that are stored in a storage medium (e.g., internal memory736or external memory738) that is readable by a machine (e.g., the electronic device701). For example, a processor of the electronic device701may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. Thus, a machine may be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include code generated by a complier or code executable by an interpreter. A machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term “non-transitory” indicates that the storage medium is a tangible device, and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium. According to one embodiment, a method of the disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store (e.g., Play Store™), or between two user devices (e.g., smart phones) directly. If distributed online, at least part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as memory of the manufacturer's server, a server of the application store, or a relay server. According to one embodiment, each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities. One or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In this case, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. Operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added. Although certain embodiments of the present disclosure have been described in the detailed description of the present disclosure, the present disclosure may be modified in various forms without departing from the scope of the present disclosure. Thus, the scope of the present disclosure shall not be determined merely based on the described embodiments, but rather determined based on the accompanying claims and equivalents thereto. | 27,344 |
11943710 | It should be noted that throughout the drawings, similar reference numerals and signs refer to corresponding parts. In addition, multiple instances of the same part are designated by a common prefix separated from the instance number by a dash. DESCRIPTION OF EMBODIMENTS The following detailed description is made with reference to the Attached Drawings, and the following detailed description is provided to facilitate comprehensive understanding of various exemplary embodiments of the present disclosure. The following description includes various details for facilitation of understanding. However, these details are merely considered as examples, not for limiting the present disclosure. The present disclosure is limited by the attached claims and their equivalents. The words and phrases used in the following description are only used to enable a clear and consistent understanding of the present disclosure. In addition, for clarity and brevity, descriptions of well-known structures, functions, and configurations may be omitted. Those of ordinary skill in the art will realize that various changes and modifications can be made to the examples described in the present specification without departing from the gist and scope of the present disclosure. As described above, in order to provide a wireless communication network to clients, the wireless network interface of the extender node in the wireless communication network is always powered on uninterruptedly. Therefore, wireless communication networks with a plurality of extender nodes usually consume more power. According to an embodiment of the present disclosure, the main access point can be used to monitor the status of each extender node and instruct the extender node to power off its wireless network interface when it satisfies the sleep condition, thereby reducing power consumption. In addition, the sleeping extender node may wake up in response to the wake-up condition. Sleep and wake-up of extender nodes can be automatically executed without being perceived by users, so it will not significantly affect the performance of the network. FIG.1shows an exemplary block diagram of a network system100according to an embodiment of the present disclosure, in which various technologies according to an embodiment of the present disclosure is implemented. The network system100may be implemented as a home network, an office network, a factory network, or any other type of network. As shown inFIG.1, the network system100may include an electronic device110, one or a plurality of extender nodes120, and one or a plurality of clients130. The electronic device110may connect the network system100to the external network600. The extender node120-1can be connected to the electronic device110and connected to the clients130-1and130-2. The extender node120-2can be connected to the electronic device110and connected to the clients130-3and130-4. Additionally, the client130-5may be directly connected to the electronic device110. The clients130-1to130-5can exchange data with the external network600through the network system100to obtain various services. According to an embodiment of the present disclosure, the electronic device110may act as or operate with the main access point of the network system100. The main access point may be various types of electronic devices capable of transmitting communication between the network system100and the external network600. In other words, each device in the network system100can access the external network600through the electronic device110. The external network600may include various types of networks, such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, an optical fiber, the internet, and the like. Note that the present disclosure does not specifically limit the type of the external network600. The electronic device110can be implemented as, e.g., an access point, a gateway (such as Touchstone® TG3452 gateway), a router (such as a wireless router and a mobile hotspot router), and a home network controller, or as a part of them. The electronic device110may have one or a plurality of wireless network interface (not shown), such as one or a plurality of Wi-Fi interfaces. These wireless network interfaces allow wireless links to be established between other devices in the network system100(e.g., the extender node120and/or the client130) and the electronic device110. Additionally or alternatively, the electronic device110may also have a wired interface (e.g., an Ethernet interface, not shown), thereby allowing a wired link to be established between other devices (e.g., the extender node120) in the network system100and the electronic device110. According to an embodiment of the present disclosure, the electronic device110may be connected to one or a plurality of extender nodes120. The extender node120can be used to expand the coverage of the wireless communication network provided by the electronic device110. Each extender node120may be arranged in a corresponding area away from the electronic device110and serve as a wireless access point in the corresponding area. The extender node120can bridge the client130and the electronic device110. In other words, the extender node120can act as a relay between the client130and the electronic device110. Accordingly, the client130can be connected to the extender node120and use the wireless communication network provided by the extender node120as if the client130were connected to the electronic device110. Each extender node120may have a one or a plurality of wireless network interface (not shown), such as one or a plurality of Wi-Fi interfaces. These wireless network interfaces allow wireless links to be established between other devices (e.g., the electronic device110and/or the client130) in the network system100and the extender node120. Additionally, the extender node120may also have a wired interface (e.g., an Ethernet interface, not shown), thereby allowing a wired link to be established between other devices (e.g., the electronic device110) in the network system100and the extender node120. According to an embodiment of the present disclosure, the link between the electronic device110and the extender node120may be a wired link or a wireless link. As an example of a wired link, the extender node120may be connected to the electronic device110through an Ethernet backhaul or a MoCA (Multimedia over Coax Alliance) backhaul. As an example of a wireless link, the extender node120may be connected to the electronic device110through a Wi-Fi backhaul. Compared with wired links, wireless links have higher flexibility. However, the wireless link depends on the wireless network interface of the extender node120to work normally. If the wireless network interface of the extender node120is powered off, the wireless link between the extender node120and the electronic device110will be interrupted. According to embodiments of the present disclosure, the extender node120may be implemented as various types of electronic devices. For example, an electronic device (e.g., a router) similar to the electronic device110may be utilized as the extender node120. In this case, the extender node120is different from the electronic device110in that the electronic device110is configured to act as a primary access point connecting the network system100with the external network600, while the extender node120is configured to act as a secondary access point inside the network system100. Alternatively, the extender node120may be implemented with a simpler device than the electronic device110. For example, the extender node120may not have an interface adapted to the external network600, but only retain an interface adapted to the electronic device110and the client130. The extender node120as a secondary access point is not responsible for functions associated with the primary access point, such as IP allocation, maintaining network topology information, managing and monitoring the extender nodes, and so on. According to an embodiment of the present disclosure, each client130can be connected to the extender node120or the electronic device110through a wireless link, so that various services provided by the network operator through the external network600can be accessed. These services include but are not limited to data services, telephone or voice services, and multimedia services. The client130may be disconnected from the extender node120or the electronic device110and connected to another extender node120. The client130can be various types of devices, including but not limited to personal computers, smart phones, tablet computing devices, wearable devices, smart home devices, smart office devices, smart production devices, and so on. According to an embodiment of the present disclosure, the wireless communication network provided by the electronic device110along with the extender nodes120could be a wireless communication network that supports any of Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), RF4CE, ZigBee, Z-Wave, IEEE 802.15.4, MQTT (Message Queue Telemetry Transport), DDS (Data Distribution Service), AMQP (Advanced Message Queuing Protocol), or other short range protocols. Also, the wireless links between the electronic device110, the extender node120and/or the client130may be of a respective type that corresponds to the wireless communication network. The wireless network interface of any of the electronic device110, the extender node120and/or the client130may be a wireless network interface that is used for the wireless link of the respective type. It should be noted that the number of each element shown inFIG.1is only schematic. According to other embodiments of the present disclosure, the network system100may include more or fewer elements without limitation. For example, the network system100may include more extender nodes120. Each extender node120can be connected to more or fewer clients130. Some extender nodes120may not be connected to any clients130. FIG.2shows an exemplary block diagram of an electronic device200according to an embodiment of the present disclosure. The electronic device200can be used as the electronic device110or the extender node120described inFIG.1. As shown inFIG.2, the electronic device200includes a processing subsystem210, a memory subsystem212, and a networking subsystem214. The processing subsystem210comprises one or a plurality of devices configured to perform computing operations. The processing subsystem210performs any of the methods described in the present disclosure. For example, the processing subsystem210may comprise one or a plurality of microprocessors, ASICs, microcontrollers, programmable logic devices, graphic processing units (GPU), and/or one or a plurality of digital signal processors (DSP). The memory subsystem212comprises one or a plurality of devices for storing data and/or instructions used for the processing subsystem210and the networking subsystem214. For example, the memory subsystem212may include a dynamic random access memory (DRAM), a static random access memory (SRAM), and/or other types of memory (sometimes collectively or individually referred to as “computer-readable storage medium”). In some embodiments, the instructions used in the memory subsystem212of the processing subsystem210comprise: one or a plurality of program modules or sets of instructions (such as program instructions222or operating system224), which can be executed by the processing subsystem210to implement various operations described in the present disclosure. It should be noted that one or a plurality of computer programs may constitute a computer program mechanism. In addition, an instruction in the various modules of the memory subsystem212may be implemented by the following: advanced programming languages, object-oriented programming languages and/or assembly or machine languages. Moreover, the programming language may be compiled or interpreted, e.g., configurable or configured (used interchangeably in this discussion), to be executed by the processing subsystem210. In addition, the memory subsystem212may comprise mechanism for controlling access to memory. In some embodiments, the memory subsystem212includes a memory hierarchy, and the memory hierarchy includes one or a plurality of caches coupled to the memory in the electronic device200. In some of these embodiments, one or a plurality of the caches are located in the processing subsystem210. In some embodiments, the memory subsystem212is coupled to one or a plurality of high-capacity mass storage devices (not shown). For example, the memory subsystem212may be coupled to a magnetic or optical driver, a solid state driver, or another type of mass storage device. In these embodiments, the electronic device200may use the memory subsystem212as a fast-access storage of frequently used data, whereas the mass storage device is used for storing infrequently used data. The networking subsystem214comprises one or a plurality of devices configured to be coupled to a wired and/or wireless network and to communicate over the wired and/or wireless network (i.e., to perform network operations), including: control logic216, an interface circuit218, and one or a plurality of antennas220(or antenna elements). AlthoughFIG.2includes one or a plurality of antennas220, in some embodiments, the electronic device200includes one or a plurality of nodes, such as the node208, which may be coupled to the one or a plurality of antennas220. Therefore, the electronic device200may include or not include one or a plurality of antennas220. For example, the networking subsystem214may include a networking system based on Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), RF4CE, ZigBee, Z-Wave, IEEE 802.15.4, MQTT (Message Queue Telemetry Transport), DDS (Data Distribution Service), AMQP (Advanced Message Queuing Protocol), or other short range protocols. Accordingly, the networking subsystem214may include a respective wireless network interface. Additionally, the networking subsystem214may also include an Ethernet networking system, a cellular networking system (e.g., 3G/4G/2G networks such as UMTS and LTE), a USB networking system, and/or another networking system. In some embodiments, the pattern shaper (such as a reflector) in one or a plurality of antennas220(or antenna elements) is used to adapt or change the transmission antenna radiation pattern of the electronic device200, and the one or the plurality of antennas220are independently and selectively electrically coupled to the ground to guide the transmission antenna radiation pattern in different directions. Therefore, if one or a plurality of antennas220include N of antenna radiation pattern shapers, the one or a plurality of antenna220may have 2N of different antenna radiation pattern configurations. More generally, a given antenna radiation pattern includes the amplitude and/or phase of a signal specifying the main lobe or the direction of the main lobe of the given antenna radiation pattern, and a so-called “exclusion zone” (sometimes called “notch” or “null value”). Note that the exclusion zone of the given antenna radiation pattern includes a low-intensity region of the given antenna radiation pattern. Although the intensity is not necessarily zero in the exclusion zone, the intensity may be below a threshold such as 4 dB or lower than the peak gain of the given antenna radiation pattern. Therefore, a given antenna radiation pattern may include a local maximum value (e.g., main beam) that points the maximum value to the gain in the direction of the electronic device of interest, and one or a plurality of local minimum values that reduce the gain in the direction of other electronic devices of no-interest. In this way, a given antenna radiation pattern can be selected so that undesirable communication, such as communication with other electronic devices, can be avoided so as to reduce or eliminate adverse effects, such as interference or crosstalk. The networking subsystem214includes a processor, controller, radio device/antenna, socket/plug and/or other devices for coupling to each supported network system, communicating on each supported network system, and processing the data and events for each supported network system. Please note that sometimes the network for coupling to each network system, and the mechanisms used to communicate on that network, and process data and events on that network are collectively referred to as the “network interface” of the network system. For example, the networking subsystem214may include one or a plurality of wireless network interface, such as one or a plurality of Wi-Fi interfaces, for establishing and maintaining wireless links with other devices. Furthermore, in some embodiments, the “network” or “connection” between electronic devices does not yet exist. Therefore, the electronic device200can use the mechanism in the networking subsystem214to perform simple wireless communication between electronic devices, e.g., sending frames and/or scanning frames sent by other electronic devices. In the electronic device200, a bus228is used to couple the processing subsystem210, the memory subsystem212, and the networking subsystem214together. Bus228may comprise electro, optic and/or electro-optic connections where subsystems can be used to communicate commands and data, and so on. Although only one bus228is shown for clarity, different embodiments may comprise different numbers or configurations of electrical, optical, and/or electro-optical connections in the subsystems. In some embodiments, the electronic device200includes a display subsystem226for showing information on a display device, which may include a display driver and a display, e.g., a liquid crystal display, a multi-touch screen, etc. Although specific components are used to describe the electronic device200, in an alternative embodiment, there may be different components and/or subsystems in the electronic device200. For example, the electronic device200may include one or a plurality of additional processing subsystems, memory subsystems, networking subsystems, and/or display subsystems. In addition, one or a plurality of the subsystems may not exist in the electronic device200. Moreover, in some embodiments, the electronic device200may include one or a plurality of additional subsystems not shown inFIG.2. In addition, although separate subsystems are shown inFIG.2, in some embodiments, some or all of the given subsystems or components may be integrated into one or a plurality of the other subsystems or components in the electronic device200. For example, in some embodiments, the program instruction222is comprised in the operating system224, and/or the control logic216is comprised in the interface circuit218. Moreover, any combination of analog and/or digital circuits may be used to implement the circuits and components in the electronic device200, including: bipolar, PMOS and/or NMOS gates or transistors. In addition, the signals in these embodiments may include digital signals with approximate discrete values and/or analog signals with continuous values. In addition, the components and circuits may be single-ended or differential, and power supplies may be unipolar or bipolar. An integrated circuit (sometimes referred to as a “communication circuit” or “device for communication”) can implement some or all of the functions of the networking subsystem214. The integrated circuit may include hardware and/or software mechanisms, and is used to transmit wireless signals from the electronic device200and receive signals at the electronic device200from other electronic devices. In addition to the mechanisms described herein, radio devices are generally known in the art, and therefore will not be elaborated. Generally, the networking subsystem214and/or the integrated circuit may include any number of radio devices. Note that the radio devices in the multiple radios embodiment function in a similar manner to the single radio embodiment described. In some embodiments, the networking subsystem214and/or the integrated circuit includes a configuration mechanism (such as one or a plurality of hardware and/or software mechanisms) that configures the radio to perform transmission and/or reception on a given communication channel (e.g., a given carrier frequency). For example, in some embodiments, the configuration mechanism may be used to switch the radio from monitoring and/or transmitting on a given communication channel to monitoring and/or transmitting on a different communication channel. Please note that “monitoring” as used herein includes receiving signals from other electronic devices and possibly performing one or a plurality of processing operations on the received signals. Although the foregoing discussion uses Wi-Fi and/or Ethernet communication protocols as illustrative examples, in other embodiments, various communication protocols may additionally be used. Therefore, communication technologies can be used in various network interfaces. In addition, although some operations in the aforementioned embodiments are implemented by hardware or software, in general, the operations in the aforementioned embodiments may be implemented in various configurations and frameworks. Therefore, some or all of the operations in the aforementioned embodiments may be executed by hardware, software, or both. For example, at least some operations in the communication technology can be implemented using the program instruction222, the operating system224(e.g., a driver for the interface circuit218), or firmware in the interface circuit218. Alternatively or in addition, at least some operations in the communication technology may be implemented at physical layer, e.g., hardware in the interface circuit218. FIG.3shows an exemplary block diagram of a router300according to an embodiment of the present disclosure. The router300may be a further exemplary embodiment of the electronic device110and the extender node120described inFIG.1. Although referred to herein as a router, the router300can be, e.g., a hardware electronic device capable of combining functions of a modem, an access point, and/or a router. It is also conceivable that the router300may include, but is not limited to, the functions of an IP/QAM set-top box (STB) or a smart media device (SMD), which can decode audio/video content and play the content provided by OTT or MSO. As shown inFIG.3, the router300includes a user interface320, a network interface321, a power supply322, a WAN interface323, a memory324and a controller326. The user interface320includes, but is not limited to, buttons, keyboards, keypads, LCD, CRT, TFT, LED, HD, or other similar display devices, including display devices with touch screen capability to enable interaction between users and gateway devices. The network interface321may include various network cards and circuitries implemented in software and/or hardware, so as to be able to communicate with wireless expander devices and clients using wireless protocols, such as IEEE 802.11 Wi-Fi protocol. The power supply322supplies power to the internal components of the router300through the internal bus327. The power supply322may be self-contained power supply, e.g., a battery pack; its interface is charged by a charger connected (e.g., directly or via another device) to a socket. The power source322may further include a rechargeable battery that is detachable for replacement, e.g., NiCd, NiMH, Li-ion, or Li-pol battery. The WAN interface323may include various network cards and circuitries implemented in software and/or hardware. Specifically, the WAN interface323may at least include one or a plurality of wireless network interface (not shown), such as one or a plurality of Wi-Fi interfaces. The power supply322may be controlled to individually power off and power on the wireless network interface. When the wireless network interface is powered on, the router300may establish and/or maintain a wireless link with other devices. When the wireless network interface is powered off, the router300cannot establish a wireless link with other devices, and the existing wireless link will be interrupted. The memory unit324comprises a single memory unit or one or a plurality of memory units or memory positions, including but not limited to the random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), read only memory (ROM), EPROM, EEPROM, flash memory, FPGA logic block, hard drive, or any other layers of a memory hierarchy. The memory324may be used to store any type of instructions, software or algorithms, including software325for controlling the general functions and operations of the router300. The controller326controls the general operation of the router300and performs management functions related to other devices in the network (such as expanders and clients). The controller326may include, but is not limited to, a CPU, a hardware microprocessor, a hardware processor, a multi-core processor, a single-core processor, a microcontroller, an application specific integrated circuit (ASIC), a DSP or other similar processing device, and any type of instructions, algorithms or software capable of performing operations and functions according to embodiments described in the present disclosure. The controller326can be of various types of implementations of digital circuit systems, analog circuit systems, or mixed signal (a combination of analog and digital signals) circuit systems executing functions in a computer system. The controller326may comprise, e.g., an integrated circuit (IC), a portion or circuit of a separate processor core, an entire processor core, a separate processor, a programmable hardware device, such as a field programmable gate array (FPGA), and/or a system comprising a plurality of processors. The internal bus327is used to establish communication between components (such as320-322,324and326) of the router300. It should be noted that although the exemplary embodiments of both the electronic device110and the extender node120ofFIG.1have been described above in conjunction with the electronic device200and the router300, this does not mean that the electronic device110and the extender node120will necessarily be implemented as the same device. It should be understood that both the electronic device110and the extender node120can adopt the exemplary architecture of the electronic device200or the router300, and are configured as devices different from each other. FIG.4shows an exemplary flowchart of a method400for making an extender node sleep according to the present disclosure. The method400will be described below in connection with the network system100ofFIG.1. The method400may be performed by the electronic device110in the network system100. Moreover, the extender node described inFIG.4may be the extender node120in the network system100. The method400may start from step410. In step410, it may be determined whether the current time falls within a specified sleep time interval. The designated sleep time interval may be a time interval associated with a low traffic period of the extender node120. In the specified sleep time interval, the extender node120may be connected to fewer clients130and/or only need to transmit less traffic. In response to determining that the current time falls within the specified sleep time interval, the method400may continue to step420. In step420, the electronic device110may determine whether the extender node120is in an idle connection state. The idle connection state may include the extender node120being not connected to any client130, or the extender node120being only connected to a sleeping client. The extender node120in the idle connection state generally does not need to transmit traffic to the clients, or only needs to transmit a very small amount of traffic to the clients. In response to determining that the extender node120is in an idle connection state, the method400may continue to step430. In step430, the electronic device110may send a sleep command to the extender node120, instructing the extender node120to power off the wireless network interface of the extender node. When the wireless network interface is powered off, the extender node120will enter a sleep state with low power consumption, thus keeping low power consumption. A wireless network interface being power-off herein may mean turning off the front haul wireless interface but leaving the back haul wireless interface on. Preferably, a wireless network interface being power-off herein may mean that no power is supplied to the wireless network interface of the extender node120, so that it is completely turned off. Compared with other energy-saving methods that only reduce the signaling overhead on the wireless link without disconnecting the wireless link, powering off the wireless network interface will achieve the greatest power saving. According to embodiments of the present disclosure, the electronic device110can obtain the current time in various ways. For example, the electronic device110may maintain a local clock and read the current time from the local clock. Additionally or alternatively, the electronic device110may receive an indication about the current time from the external network600. According to the embodiments of the present disclosure, the sleep time interval can be specified for the extender node120in various ways. In one example, the sleep time interval may be a default time interval designated by the manufacturer of the electronic device110or the extender node120, e.g., 00:00-06:00 every day. In another example, the sleep time interval may be specified by the user of the network system100. In another example, the electronic device110may specify a different sleep time interval for each extender node120. For example, different production equipment sharing a factory network may have different production shifts, so different sleep time intervals can be specified for different extender nodes120serving production equipment with different shifts. The electronic device110can identify the low traffic period of each extender node120by analyzing the historical traffic data thereof, and specify the sleep time interval of the extender node120based on the identified low traffic period. The electronic device110can dynamically update the sleep time interval designated for each extender node120and push the new sleep time interval to the clients130of each extender node120. According to an embodiment of the present disclosure, the electronic device110may determine whether an extender node120is in an idle connection state based on the topology information of the network system100. For example, the electronic device110can maintain the topology information of the network system100. The topology information may include information associated with one or a plurality of extender nodes120connected to the electronic device110, and may include information associated with one or a plurality of clients130connected to each extender node120. For example, the electronic device110may maintain a client table. The client table may indicate an extender node120(e.g., extender node120-1) to which a specific client (e.g., client130-1) is connected, connection establishment time, connection disconnection time, IP address used, traffic data analysis, and so on. The electronic device110can update the topology information of the network system100by polling each extender node120. According to an embodiment of the present disclosure, the electronic device110may determine whether the extender node120is not connected to any client130based on the topology information (e.g., client table) of the network system100. For example, the electronic device110may determine the number of clients130connected to a specific extender node120(e.g., the extender node120-1) based on the client table. In response to determining that the number of clients130connected to the specific extender node120is zero, it can be determined that the extender node120is in an idle connection state. According to an embodiment of the present disclosure, if the extender node120is connected to one or a plurality of clients130, the electronic device110can identify whether each client130of the one or a plurality of clients is a sleeping client. If all clients connected to the extender node120are sleeping clients, it can be determined that the extender node120is in an idle connection state. Otherwise, it can be determined that the extender node120is not in the idle connection state. According to the embodiment of the present disclosure, it can be identified whether the client is a sleeping client based on the traffic pattern of each client. For example, if the traffic of a client within a specified length of time is lower than a predetermined threshold, the client can be identified as a sleeping client. Although the sleeping client may still have a small amount of traffic, it is likely that such traffic is unimportant background traffic, so it can be discarded. “Traffic below the predetermined threshold” may include the flow rate being lower than the predetermined rate threshold within a specified time length, and/or the total net flow within a specified time length being lower than the predetermined flow threshold. In the above embodiments, the electronic device110may set different specified time lengths and/or predetermined thresholds for different types of clients130. Specifically, the electronic device110may identify the type of the client130connected to the extender node120, and determine at least one of a predetermined threshold and a specified time length for the client based on the identified type. Since different types of clients130generally have different traffic patterns, it is advantageous to adaptively set a specified length of time and/or a traffic threshold for each client. For example, for a streaming media device (such as a smart TV), a larger predetermined threshold value and/or a smaller specified time length can be set. For a text reader device (e.g., an electronic reader), a smaller predetermined threshold value and/or a longer specified time length can be set. For security monitoring devices (such as surveillance cameras and security sensors), the predetermined threshold can be set to zero, which means that these security monitoring devices will never be considered as sleeping clients. In this case, the wireless network interface of the extender node120serving the security monitoring devices will not be powered off, which ensures that the security monitoring devices can access the wireless communication network continuously and stably through the extender node120. According to an optional embodiment of the present disclosure, if a specific key client is not connected to the extender node120, the extender node120may be considered to be in an idle connection state, and thus enter a sleep state. Specifically, one or a plurality of specific clients (e.g., smart phones of users and controllers of smart home systems) can be identified as key clients of the network system100. If the electronic device110recognizes that the extender node120is not connected to any of the specific one or a plurality of clients, it can determine that the extender node120is in an idle connection state and send a sleep command to it. Accordingly, the extender node will no longer provide the wireless communication network. This setting is advantageous in some scenarios. For example, some scenarios require access to key clients to maintain network security. According to an optional embodiment of the present disclosure, the electronic device110may also enter a sleep state. The electronic device110can execute its own sleep policy. In response to determining that the electronic device110is about to enter a sleep state, the electronic device110may send a sleep command to each extender node120in the network system100. FIG.5shows an exemplary flowchart of a method500for waking up an extender node according to the present disclosure. The method500will be described below in connection with the network system100ofFIG.1. The method500may be performed by the electronic device110and the extender node120in the network system100, e.g. The method500may start from step510. In step510, for the sleeping extender node120, it may be determined whether the wake-up condition is satisfied. According to embodiments of the present disclosure, various wake-up conditions can be set, including but not limited to: (i) when the specified sleep interval expires; (ii) when the timer set by the extender node120expires; or (iii) when the user has conducted any physical operation on the extender node120. In response to any one of the wake-up conditions being met, the method500may continue to step520. In step520, the sleeping extender node120may be awakened. According to an embodiment of the present disclosure, when the extender node120is connected to the electronic device110through a wired link (e.g., Ethernet backhaul and MoCA backhaul), the wired link will not be interrupted due to the closing of the wireless network interface of the extender node120. Therefore, the sleeping extender node120can be awakened by the electronic device110. For example, the electronic device110may monitor whether a designated sleep time interval for the extender node120expires. In response to the expiration of the specified sleep time interval, the electronic device110may send a wake-up command to the extender node120through the wired link between the extender node120and the electronic device110to wake up the extender node120. According to an embodiment of the present disclosure, when the extender node120is connected to the electronic device110through a wireless link, the wireless link will be interrupted when the wireless network interface of the extender node120is turned off. Therefore, the extender node120cannot wake up depending on the electronic device110, but should wake up autonomously. In this case, the sleep command sent by the electronic device110to the extender node120in step430may additionally instruct the extender node120to start the timer while turning off the wireless network interface. The extender node120can autonomously wake up when the timer expires without receiving a wake-up command from the electronic device110. According to the embodiment of the present disclosure, the extender node120can be autonomously woken up in response to the physical operation of the sleeping extender node120by the user. For example, when the user presses any physical button on the extender node120, the extender node120can be awakened. Alternatively, when the user unplugs and plugs in the power supply on the extender node120, the extender node120may be awakened. This way allows the user to wake up the extender node120manually. According to the embodiment of the present disclosure, the electronic device110may update the sleep time interval of the extender node according to the history of manual awakening of the extender node120. For example, if the number of times the extender node120is manually woken up in a period of time (e.g., one month or more) exceeds a specified threshold, the electronic device110may consider that the original sleep time interval does not conform to the user's usage habits. Accordingly, the electronic device110can update the sleep time interval of the extender node120. For example, the electronic device110may modify the expiration time of the sleep time interval to a time point associated with the time point when the user manually wakes up the extender node120. According to an embodiment of the present disclosure, waking up the extender node120may include powering on the wireless network interface of the extender node120again. It may take a certain time for the wireless network interface to power on, during which the extender node120may be in a transitional state from the sleep state to the normal state. The wireless network interface after being re-powered allows the extender node120to re-establish or restore the wireless link with other devices (e.g., the electronic device110or the client130). Accordingly, the extender node120can operate as a wireless access point again. According to an embodiment of the present disclosure, waking-up of the extender node120may further include restoring the wireless link between the extender node120and the electronic device110. Before the wireless network interface of the extender node120is powered off, the extender node120may save wireless link information associated with the wireless link between the extender node120and the electronic device110. In the wake-up process, the extender node120may try to restore the wireless link based on the saved wireless link information. In this way, the original wireless link between the extender node120and the electronic device110can be quickly restored without going through a complicated process of establishing a new wireless link. According to the embodiments of the present disclosure, the main access point in the wireless communication network can be utilized to monitor the status of each extender node and instruct the extender node to power off its wireless network interface when the sleep condition is satisfied, thereby reducing the power consumption of the extender node. A sleeping extender node may be woken up in response to a wake-up condition. Sleep and wake-up of extender nodes can be automatically performed without being perceived by users, so it will not significantly affect the performance of the network. The present disclosure may be implemented as any combination of devices, systems, integrated circuits, and computer programs on non-transitory computer-readable media. One or a plurality of processors may be implemented as an integrated circuit (IC), an application specific integrated circuit (ASIC) or a large-scale integrated circuit (LSI), a system LSI, a super LSI, or an ultra LSI component that performs some or all of the functions described in the present disclosure. The present disclosure includes the use of software, applications, computer programs, or algorithms. Software, application programs, computer programs or algorithms can be stored on a non-transitory computer readable medium, so that a computer with one or a plurality of processors can execute said steps and the steps described in the drawings. For example, one or a plurality of memories store software or algorithms in executable instructions, and one or a plurality of processors associate a set of instructions for executing the software or algorithms to provide reliable management of gateways in an MSO network according to embodiments described in the present disclosure. Software and computer programs (also called programs, software applications, applications, components, or codes) include machine instructions for programmable processors, and may be realized in high-level procedural languages, object-oriented programming languages, functional programming languages, logic programming languages, or assembly languages or machine languages. The term “computer-readable medium” refers to any computer program product, device or apparatus used to be executed on hardware to provide machine instructions or data to a programmable data processor, such as magnetic disks, optical disks, solid-state storage devices, memories, and programmable logic devices (PLDs), including computer-readable media that receive machine instructions as computer-readable signals. For example, the computer-readable medium may include the dynamic random access memory (DRAM), random access memory (RAM), read only memory (ROM), electrically erasable read only memory (EEPROM), compact disk read only memory (CD-ROM) or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the required computer-readable program codes in the form of instructions or data structures and can be accessed by a general or special computer or a general or special processor. As used herein, magnetic disks or disks include compact discs (CDs), laser disks, optical disks, digital versatile discs (DVDs), floppy disks, and Blu-ray disks, wherein magnetic disks usually copy data magnetically, and disks copy data optically via laser. Combinations of the above are also included in the scope of computer-readable media. In one or a plurality of embodiments, the use of the words “able”, “can”, “operable as” or “configured as” refers to some devices, logics, hardware and/or components designed to be used in a specified manner. The subject matter of the present disclosure is provided as an example of the apparatus, system, method, and program for performing the features described in the present disclosure. However, in addition to the aforementioned features, other features or modifications can be expected. It can be expected that any emerging technology that may replace any of the aforementioned implementation technologies may be used to complete the implementation of the components and functions of the present disclosure. In addition, the above description provides examples without limiting the scope, applicability, or configuration set forth in the claims. Without departing from the spirit and scope of the present disclosure, changes may be made to the functions and layouts of the discussed components. Various embodiments may omit, substitute, or add various processes or components as appropriate. For example, features described with respect to some embodiments may be combined in other embodiments. Similarly, although operations are depicted in a specific order in the Attached Drawings, this should not be understood as a requirement that such operations should be executed in the specific order shown or in the sequential order, or that all illustrated operations be executed to achieve the desired result. In some cases, multi-tasking and parallel processing can be advantageous. | 46,287 |
11943711 | DESCRIPTION OF EMBODIMENTS Terms used in implementations of this application are merely used to explain specific embodiments of this application, but are not intended to limit this application. The embodiments of this application may be applied to various communications systems.FIG.1is a schematic diagram of an application scenario according to an embodiment of this application. A communications system shown inFIG.1mainly includes a network device11and a terminal device12. (1) The network device11may be a network side device, for example, a wireless fidelity (WI-FI) access point (AP), or a next-generation communications base station such as a gNB, a small cell, a micro base station, or a TRP in 5G, or may be a relay station, an access point, a vehicle-mounted device, a wearable device, or the like. In this embodiment, communications systems of different communications standards have different base stations. For ease of differentiation, a base station in a 4G communications system is referred to as an LTE eNB, a base station in a 5G communications system is referred to as an NR gNB, and a base station that supports both the 4G communications system and the 5G communications system is referred to as an eLTE eNB. These names are merely used for ease of differentiation, and do not have limitation meanings. (2) The terminal device12is also referred to as user equipment (UE), and is a device that provides a user with voice and/or data connectivity, for example, a handheld device or a vehicle-mounted device having a wireless connection function. Common terminal devices include a mobile phone, a tablet, a notebook computer, a palmtop computer, a mobile internet device (MID), a wearable device such as a smartwatch, a smart band, or a pedometer, and the like. (3) The term “a plurality of” indicates two or more, and another quantifier is similar to the term “a plurality of”. The term “and/or” describes an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. The character “I” generally indicates an “or” relationship between the associated objects. It should be noted that a quantity of terminal devices12included in the communications system shown inFIG.1and types of the terminal devices12are merely an example. This embodiment of this application is not limited thereto. For example, the communications system may further include more terminal devices12that communicate with the network device11. In addition, although the network device11and the terminal device12are shown in the communications system shown inFIG.1, the communications system may not be limited to the network device11and the terminal device12, for example, may further include a core network node, or a device configured to carry a virtualized network function. In addition, the embodiments of this application may be applied to not only a next-generation wireless communications system, that is, the 5G communications system, but also another system that may appear in the future, for example, a next-generation Wi-Fi network or a 5G internet of vehicles. It should be noted that, with continuous evolution of a communications system, names of the network device and the terminal device may change in another system that may appear in the future. In this case, the solutions provided in the embodiments of this application are also applicable. The following briefly describes an implementation scenario of this application. In a process in which a network device communicates with a terminal device, a base station sends DCI to the terminal device, and the DCI is used to indicate a specific time-frequency resource location and a specific configuration parameter used by the terminal device to receive and demodulate downlink data. Therefore, the terminal device needs to continually perform blind PDCCH detection, to determine whether there is DCI sent to the terminal device, so that the terminal device can receive and demodulate the downlink data based on the received DCI. However, for any terminal device, an amount of DCI sent by the base station, a moment at which the base station sends the DCI, and an object to which the base station sends the DCI are not determined. Therefore, the terminal device needs to continually perform blind PDCCH detection. Consequently, a large amount of energy of the terminal device is consumed. In addition, in an existing technology branch of a 5G NR technology, to reduce energy consumption of the terminal device, a discontinuous reception (DRX) mechanism in a long term evolution (LTE) technology is still used. Referring toFIG.2, a base station configures one DRX cycle for a terminal device that is in a radio resource control (RRC) connected mode, and each DRX cycle includes an “on duration” part and an “opportunity for DRX” part. The terminal device monitors and receives a physical downlink control channel (PDCCH) within the “on duration”, and the terminal device may not monitor or receive a PDCCH within the “opportunity for DRX” to reduce energy consumption. The DRX mechanism may be implemented by using an on duration timer (or drx-on Duration Timer). Specifically, at the beginning of each DRX cycle (that is, at the beginning of the on duration of each DRX cycle), the terminal device needs to start the on duration timer. When the on duration timer expires, it indicates that the “on duration” ends. In this case, the terminal device enters the “opportunity for DRX”. In addition, the DRX cycle may be a long DRX cycle, or may be a short DRX cycle. A long DRX cycle is generally a default mandatory configuration manner, and a short DRX cycle is an optional configuration manner. If a short DRX cycle is configured, the terminal device starts a short cycle timer in the short DRX cycle, and switches to a long DRX cycle when the short cycle timer expires. In an existing energy saving solution, a DRX cycle is formulated. However, if no data is transmitted between the base station and the terminal device within on duration in a DRX cycle or even in an entire DRX cycle, energy consumed by the terminal device within the on duration in the DRX cycle is wasted, and consequently energy consumption of the terminal device is relatively high. An information sending and receiving method provided in this application is intended to resolve the foregoing technical problem in the prior art, and the following solution idea is provided: Information sent by a network device to a terminal device carries energy saving state information that indicates the terminal device to go to sleep or wake up and/or information about duration in which an energy saving state is maintained. Therefore, after receiving the message, the terminal device may adjust a working state of the terminal device based on the message, thereby reducing energy consumption of the terminal device. By using specific embodiments, the following describes in detail the technical solutions of this application and how to resolve the foregoing technical problem by using the technical solutions of this application. The following several specific embodiments may be combined with each other, and a same or similar concept or process may not be described repeatedly in some embodiments. The following describes the embodiments of this application with reference to the accompanying drawings. An embodiment of this application provides an information sending and receiving method. The following specifically describes the method by using a scenario of interaction between a network device and a terminal device shown inFIG.1as an example. Referring toFIG.3, the method may include the following procedure. S102: A network device configures first information, where the first information includes a first field and/or a second field, the first field includes information indicating an energy saving state of a terminal device, and the second field includes information indicating a time length in which the terminal device maintains the energy saving state. The energy saving state information is information that indicates the terminal device to wake up/wake up, or information that indicates the terminal device to go to sleep/go to sleep. Correspondingly, the energy saving state of the terminal device includes a sleep state or a wake-up state. When the terminal device is in a sleep state, the terminal device does not monitor or receive a PDCCH to reduce energy consumption. Alternatively, when the terminal device is in a wake-up state, the terminal device starts to monitor and receive a PDCCH. In this embodiment of this application, the network device may configure the first information based on a status that the network device sends data to the terminal device. S104: The network device sends the first information to the terminal device. S106: The terminal device receives the first information sent by the network device. S108: The terminal device obtains at least one of the energy saving state information and the time length information based on the first information. S110: The terminal device adjusts the energy saving state of the terminal device based on the at least one of the energy saving state information and the time length information. When the first information carries the first field, if the energy saving state information is the information that indicates the terminal device to wake up, the terminal device adjusts the energy saving state of the terminal device to a wake-up state. On the contrary, if the energy saving state information is the information that indicates the terminal device to go to sleep, the terminal device adjusts the energy saving state of the terminal device to a sleep state. In the foregoing steps, the network device configures the first field based on whether the network device sends data to the terminal device; and/or configures the second field based on a specific time period in which the network device sends or stops sending data to the terminal device, and sends the information to the terminal device. Correspondingly, the terminal device adjusts the energy saving state of the terminal device based on the received first information, so that blind PDCCH detection can be stopped when there is no data to be received, thereby reducing power consumption. The following specifically describes implementations of the foregoing steps. For an implementation of configuring the first information in step S102, there are three aspects below: A first aspect is configuring the first field. The energy saving state information included in the first field is the information that indicates the terminal device to go to sleep, or the information that indicates the terminal device to wake up. It is considered that the terminal device performs blind PDCCH detection to receive data sent by the network device. Therefore, the network device may determine content of the first field based on whether the network device sends data to the terminal device. Correspondingly, the terminal device may determine, based on the first information, whether the network device sends data to the terminal device, and adjust the energy saving state of the terminal device (to a sleep state or a wake-up state) based on the first information, thereby reducing energy consumption. A manner of representing the energy saving state information is not particularly limited in this embodiment of this application. For example, bit information may be used to indicate the terminal device to go to sleep or wake up. For example, 1-bit information is used to indicate the energy saving state information. For example, “0” is used to indicate the terminal device to go to sleep, and “1” is used to indicate the terminal device to wake up. Alternatively, different values are used to indicate the device to go to sleep or wake up. Alternatively, two different identifiers may be used to indicate the terminal device to go to sleep or wake up. For example, “+” is used to indicate the terminal device to go to sleep, and “−” is used to indicate the terminal device to wake up. Alternatively, text information may be used to directly indicate the terminal device to go to sleep or wake up. It should be noted that the first field in this embodiment of this application may be a newly added field or an original field in the first information. In this case, the network device may configure the first field in the first information in at least the following three manners: In a first manner, new first information used to indicate the energy saving state of the terminal device is designed. In this implementation, a field quantity, a field location, and a definition of each field of the first information may be configured as required. Essentially, a new information format is designed. An example in which the first information is DCI is still used. Referring toFIG.4, the 1stfield in the first information includes the information that indicates the terminal device to go to sleep or wake up, which is the first field. In addition, in a feasible implementation, the first information may be downlink control information (DCI). In this case, if the first information is in a newly designed DCI format, the first information may further include other fields, and these fields may be defined as required. For example, when the first field indicates the terminal to go to sleep, the terminal device needs to adjust the energy saving state of the terminal device to a sleep state. In this case, other fields may be ignored or may not be configured. This can make configuration of the network device easier and improve configuration efficiency. On the contrary, if the first field indicates the terminal to wake up, the terminal device needs to adjust the energy saving state of the terminal device to a wake-up state. In this case, the terminal device needs to monitor and receive a PDCCH, and therefore needs to read another field in the first information, and the network device further needs to configure, in the first information, information such as a specific time-frequency resource location and a specific configuration parameter used by the terminal device to receive and demodulate downlink data. Therefore, in a specific implementation scenario, the first information may further include one or more of the following fields:a bandwidth part indicator (BWP indicator) field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, and an antenna port(s) field. When the first field indicates the terminal device to wake up, the bandwidth part indicator field is used to indicate a BWP of downlink data that the terminal device needs to receive subsequently, and the terminal device may correspondingly receive the downlink data at the BWP; the SRS request field is used to indicate the terminal device to perform aperiodic SRS sending; and the TPC command for scheduled PUSCH field is used to indicate a power adjustment value for scheduling uplink data sending. The foregoing fields are merely preferred fields. During actual implementation of this solution, the first information may further include another field. Optionally, the first information may further include one or more of the following fields: a bandwidth part indicator (BWP indicator) field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, an antenna port(s) field, a synchronization signal/broadcast channel indicator (SS/PBCH index) field, a short message field, a modulation and coding scheme (MCS) field, a downlink assignment index (DAI) field, a transmitted precoding matrix indicator (TPMI) acknowledgment field, a precoding matrix indicator (PMI) acknowledgment field, a downlink power compensation (Downlink power offset) field, a hybrid automatic repeat request (HARQ) process number field, a transport block to codeword swap flag field, a precoding information field, a transmit power control (TPC) field, a scrambling identity field, an antenna port(s), scrambling identity and number of layers field, a physical downlink shared channel resource element mapping and quasi-co-location indicator field, a demodulation reference signal phase rotation and OCC index (Cyclic shift for Demodulation Reference Signal and Orthogonal Cover Code index) field, an uplink index (ULI) field, a downlink assignment index (DAI) field, a channel state information request field, and the like. In an optional implementation scenario, the first information may be configured in a manner shown inFIG.4. To be specific, in addition to the first field, the first information further includes the foregoing fields. It should be noted that a configuration location of each field in the first information may be set as required. For example, the first field may be configured in any field in the first information. Specifically, as shown inFIG.4, the first field may be configured in an initial field of the first information, or the first field may be configured at any location in the middle of the first information, or the first field may be configured at an end location of the first information. In the configuration manner shown inFIG.4, the first field is configured in the initial field of the first information. This can help the terminal device quickly determine to adjust the energy saving state of the terminal device to a wake-up state or a sleep state after receiving the first information. Therefore, when the terminal device specifically maintains the energy saving state, the terminal device may read or abandon reading information carried in another field of the first information, thereby further reducing energy consumption. In this way, if the first field is the initial field of the first information and the first field is the information that indicates the terminal device to go to sleep, after reading the first information, the terminal device determines to adjust the energy saving state of the terminal device to a sleep state. Therefore, the terminal device directly controls the terminal device to enter a sleep mode without a need of reading a subsequent field. This can reduce an amount of data processed by the terminal device, and reduce energy consumption of the terminal device. That the first field in this embodiment of this application includes the information indicating the energy saving state of the terminal device may include but is not limited to the following configuration manners:using all or some bits of the first field to indicate the energy saving state information of the terminal device; and/orusing all or some values of the first field to indicate the energy saving state information of the terminal device. When a part of the first field is used to indicate the energy saving state information of the terminal device, other bits of the first field may be used to carry other information, or other bits of the first field may be empty, in other words, do not carry information. In addition, when some values of the first field are used to indicate the energy saving state information of the terminal device, other values of the first field may be used to carry other information. Therefore, this embodiment of this application provides a feasible solution for a combination of the foregoing two configuration manners. For example, all bits and all data of the first field are used to indicate the energy saving state information of the terminal device. Alternatively, for another example, some bits and all values of the first field are used to indicate the energy saving state information of the terminal device. In this case, other bits of the first field have no data. It can be learned that a configuration manner of another field is the same as that of the first field. In this implementation, a meaning of each field in the first information may be defined as required. Compared with an existing DCI format, the first information defined in this manner can reduce fields included in the DCI format to some extent, so that the terminal device enables a minimum quantity of functions, thereby achieving energy saving. In addition, a user-defined manner is relatively flexible. In a second manner, a new field is added to existing information to obtain the first information. For ease of understanding, refer to a schematic structural diagram of first information shown inFIG.5. The first information includes (N+1) fields in total, where N is an integer greater than or equal to 1. The first N fields of the first information are all fields in existing DCI, and an (N+1)thfield is the first field described in this application. The field is a newly added field in the existing DCI, and specifically includes the information that indicates the terminal device to go to sleep or wake up. In addition, it should be further noted that a location of the newly added field is not particularly limited in this embodiment of this application. As shown inFIG.5, a manner of configuring the newly added first field at an end location of the existing DCI is merely a feasible implementation. In addition, the newly added field may be alternatively configured at a start location of the existing DCI, or the newly added field may be configured at any location in the middle of the existing DCI. An existing DCI format includes a DCI format for a group, for example, a DCI format 2-2. A field length of the DCI format is variable, a base station configures different format lengths for different quantities of terminals in the group, and information in the DCI format may be used to simultaneously indicate a plurality of terminals. Therefore, in a preferred implementation process, if the first field is a newly added field in the first information, the first information may be in but is not limited to being in the DCI format 2-2. When the first information is in the DCI format 2-2, a plurality of first fields may be added to indicate energy saving state information of different terminals in the group. Specifically, refer to first information shown inFIG.6. InFIG.6, two first fields are added to the existing DCI information. A first field of a terminal device1is used to indicate energy saving state information of the terminal device1, and a first field of a terminal device2is used to indicate energy saving state information of the terminal device2. It should be noted that, when first fields of a plurality of different terminal devices are configured in one piece of first information, energy saving states of the terminal devices that are indicated by the fields may be the same or may be different.FIG.6is still used as an example. The first field of the terminal device1may be configured as information that indicates the terminal1to go to sleep, and the first field of the terminal device2may be configured as information that indicates the terminal2to wake up. In addition, in a feasible implementation scenario, one first field may alternatively include a plurality of pieces of energy saving state information, and each piece of energy saving state information may include information that indicates one terminal device in the group to go to sleep or wake up. Certainly, all other existing DCI formats may also be used as the first information, for example, a DCI format 0-0, a DCI format 0-1, a DCI format 1-0, a DCI format 1-1, a DCI format 2-0, a DCI format 2-1, and a DCI format 2-3. For example, when the first information is in the DCI format 1-0, a first field may be added to the DCI format 1-0, and the first field includes the information used to indicate the terminal device to go to sleep or wake up. Optionally, when a first field is added to an existing DCI format, if the field includes the information that indicates the terminal device to go to sleep, the terminal device may ignore an original field in the DCI format, and may directly start to enter a sleep state in a slot slot or a subframe in which the DCI is located, instead of performing related scheduling based on the original field. In another optional implementation scenario, when a first field is added to an existing DCI format, if the field includes the information that indicates the terminal device to go to sleep, the terminal device reads an original field in the DCI format, performs related scheduling based on the original field, and enters a sleep state after completing the related scheduling. Because current-slot slot scheduling and cross-slot scheduling exist, an effective time of the first field may be a next slot of a slot slot in which the DCI is located, or may be a plurality of slots following a slot slot in which the DCI is located. After completing the related scheduling, the terminal enters a sleep state. In another optional implementation scenario, when a first field is added to an existing DCI format, if the field includes the information that indicates the terminal device to wake up, the terminal device performs related scheduling based on an original field, and directly starts to enter a wake-up state in a slot slot or a subframe in which the DCI is located. Because current-slot slot scheduling and cross-slot scheduling exist, an effective time of the first field may be the slot slot in which the DCI is located, or may be one or more slots following the slot slot in which the DCI is located. The terminal enters a wake-up state. When the first information is configured in a configuration manner of adding a new field, all or some bits of the newly added field may be used to indicate the energy saving state information of the terminal device, and/or all or some values of the newly added field are used to indicate the energy saving state information of the terminal device. For an implementation thereof, refer to the first implementation. In this configuration manner of adding a new field, existing DCI is lengthened, and the energy saving state information of the terminal device is indicated by using the newly added field. In addition, because no multiplexing or other processing is performed on an original field in the existing DCI, no function limitation is imposed on the original field in the existing DCI. In a third manner, an original field in existing information is multiplexed to obtain the first information. A principle of this implementation is as follows: Without changing a field length of existing DCI, an entire field or a part of the filed that can be multiplexed in the DCI is multiplexed into the first field, and the energy saving state information is set in the first field. In this way, when the first field occupies only a part of an original field, the part of the original field multiplexed into the first field may be located at a start location of the original field, any location in the middle of the original field, or an end location of the original field. Referring toFIG.7, the first field includes N original fields in total, where N is an integer greater than or equal to 1. A part that is of an xthoriginal field and that is located in the middle of the xthoriginal field is multiplexed into the first field. In this way, the information indicating the energy saving state of the terminal device needs to be configured in the part that is of the field and that is multiplexed, where x is an integer ranging from 1 to N. A field that can be multiplexed may be selected and configured as required. In a preferred implementation process, the first field may be but is not limited to a frequency domain resource allocation field in the first information. For example, a frequency domain resource assignment field in existing DCI for a DCI format of a single terminal device such as a DCI format 0-0, a DCI format 0-1, a DCI format 1-1, or a DCI format 0-1 is used to indicate downlink/uplink data frequency resource allocation in the existing DCI. Therefore, a part of the field may be multiplexed into the first field to carry the energy saving state information. For example, 1-bit information in the frequency domain resource allocation field is used to indicate the energy saving state information of the terminal, where “0” is used to indicate the terminal device to go to sleep, and “1” is used to indicate the terminal device to wake up. Other bit information is still used to indicate frequency resource allocation. Optionally, when the first field is obtained by multiplexing an existing field in a DCI format, and energy saving state information of the field indicates the terminal device to go to sleep, the terminal device ignores another field in the DCI format other than the first field, and directly starts to enter a sleep state in a slot slot or a subframe in which the DCI is located, instead of performing related scheduling based on another field. When only a part of the existing field is multiplexed into the first field, a meaning of the other part of the existing fields may be ignored. In another optional implementation scenario, when the first field is obtained by multiplexing an existing field in a DCI format, and energy saving state information of the field indicates the terminal device to go to sleep, the terminal device reads the original field in the DCI format, performs related scheduling based on the original field, and enters a sleep state after completing the related scheduling. Because current-slot slot scheduling and cross-slot scheduling exist, an effective time of the first field may be a next slot of a slot slot in which the DCI is located, or may be a plurality of slots following a slot slot in which the DCI is located. After completing the related scheduling, the terminal enters a sleep state. In another optional implementation scenario, when the first field is obtained by multiplexing an existing field in a DCI format, and the field includes information that indicates the terminal device to wake up, the terminal device reads the original field in the DCI format, performs related scheduling based on the original field, and directly starts to enter a wake-up state in a slot slot or a subframe in which the DCI is located. Because current-slot slot scheduling and cross-slot scheduling exist, an effective time of the first field may be the slot slot in which the DCI is located, or may be one or more slots following the slot slot in which the DCI is located. The terminal enters a wake-up state. Optionally, the multiplexed field may alternatively be another field in the existing DCI format, for example, a bandwidth part indicator (BWP indicator) field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, an antenna port(s) field, a synchronization signal/broadcast channel indicator (SS/PBCH index) field, a short message field, a modulation and coding scheme (MCS) field, a downlink assignment index (DAI) field, a transmitted precoding matrix indicator (TPMI) acknowledgment field, a precoding matrix indicator (PMI) acknowledgment field, a downlink power compensation (Downlink power offset) field, a hybrid automatic repeat request (HARQ) process number field, a transport block to codeword swap flag field, a precoding information field, a transmit power control (TPC) field, a scrambling identity field, an antenna port(s), scrambling identity and number of layers field, a physical downlink shared channel resource element mapping and quasi-co-location indicator field, a demodulation reference signal phase rotation and OCC index (Cyclic shift for Demodulation Reference Signal and Orthogonal Cover Code index) field, an uplink index (ULI) field, a downlink assignment index (DAI) field, a channel state information request field, or another field. Similar to the foregoing two configuration manners, all or some bits of the first field may be used to indicate the energy saving state information of the terminal device, and/or all or some values of the first field are used to indicate the energy saving state information of the terminal device. For an implementation thereof, refer to the first implementation. This configuration manner of multiplexing a field does not affect a field length of DCI, and does not affect a quantity of blind PDCCH detections performed by the terminal device. In other words, a workload and energy consumption of performing blind PDCCH detection by the terminal device are not increased. However, because an original field is multiplexed into the first field, some functions of the original field may be limited. In the foregoing three implementations, only an example in which the first information is DCI is used for description. During specific implementation, the first information may alternatively be information in another form. A second aspect is configuring the second field. The network device may determine content of the second field based on a specific time period in which the network device sends data to the terminal device and a specific time period in which the network device stops sending data to the terminal device. In other words, the network device may set the time period in which the network device sends data to the terminal device to duration in which the terminal device maintains a wake-up state, and set the time period in which the network device stops sending data to the terminal device to duration in which the terminal device maintains a sleep state. Correspondingly, if the first information received by the terminal device includes the second field, the terminal device only needs to maintain a sleep state or a wake-up state in a specific time period based on the indication of the second field. It should be noted that the energy saving state in the second field is indicated in a plurality of manners, including but not limited to indication by using the first field. For example, the energy saving state maintained in the second field may be a current state of the terminal device, or may be indicated by sending indication information to the terminal device, or may be indicated by using a preset rule. This embodiment of this application imposes no limitation thereto. A manner of representing the second field is not particularly limited in this embodiment of this application. For example, bit information may be used to indicate the duration of the energy saving state of the terminal device. For example, 2-bit information is used to indicate the energy saving state information. For example, “00”, “01”, “10”, and “11” are used to indicate different time length information. Different bit information may be used to indicate one or more symbols, one or more slots, one or more subframes, one or more radio frames, one or more pieces of on duration on duration, one or more DRX cycles, one or more downlink control channel monitoring occasions (PDCCH monitoring occasion), and the like. In addition, in the 2-bit information, a specific bit such as “00” may be used to indicate other information, for example, to indicate whether a field in which the bit information is located or another field is meaningful, or to indicate that the field retains an original meaning. If a unit of the time length has been determined, bit information of different lengths is directly used to indicate specific lengths. For example, the second field is used to indicate the terminal device to maintain the energy saving state within one or more pieces of on duration on duration. Therefore, “01” is used to indicate that the terminal device maintains the energy saving state within next one piece of on duration on duration, “10” is used to indicate that the terminal device maintains the energy saving state within next two pieces of on duration on duration, and “11” is used to indicate that the terminal device maintains the energy saving state within next three pieces of on duration on duration. In this embodiment of this application, the content of the second field may include but is not limited to the following configuration manners:using all or some bits of the second field to indicate the information about the time length in which the terminal device maintains the energy saving state; and/orusing all or some values of the second field to indicate the information about the time length in which the terminal device maintains the energy saving state. When a part of the second field is used to indicate the information about the time length in which the terminal device maintains the energy saving state, other bits of the second field may be used to carry other information, or other bits of the second field may be empty, in other words, do not carry information. In addition, when some values of the second field are used to indicate the information about the time length in which the terminal device maintains the energy saving state, other values of the second field may be used to carry other information. Therefore, this embodiment of this application provides a feasible solution for a combination of the foregoing two configuration manners. For example, all bits and all data of the second field are used to indicate the information about the time length in which the terminal device maintains the energy saving state. Alternatively, for another example, some bits and all values of the second field are used to indicate the information about the time length in which the terminal device maintains the energy saving state. In this case, other bits of the second field have no data. In this embodiment of this application, the time length information in the second field is used to represent the time length, and may have a plurality of representation forms. In a specific implementation scenario, the time length information may be represented in the following manners:one or more slots; orone or more subframes; orone or more pieces of on duration on duration; orone or more physical downlink control channel monitoring occasions PDCCH monitoring occasion. Specifically, the time length information may be represented in at least one of the following manners: a symbol, a slot, a subframe, a radio frame, on duration related to discontinuous transmission, and a DRX cycle. In addition, the time length information may alternatively be represented by using a downlink control channel monitoring occasion (PDCCH monitoring occasion). When the second field indicates one or more symbols (or slots, or subframes, or radio frames), an effective location of the field may start from a symbol (or a slot, or a subframe, or a radio frame) in which the second field is located, or may start from one or more symbols (or slots, or subframes, or radio frames) following a symbol (or a slot, or a subframe, or a radio frame) in which the second field is located. When the second field indicates one or more pieces of on duration (or DRX cycles), the effective location of the field may be on duration (or a DRX cycle) in which the second field is located, or may be one or more pieces of on duration (or DRX cycles) following on duration (or a DRX cycle) in which the second field is located. When the second field may indicate one or more PDCCH monitoring occasions, the field is used to indicate the terminal to maintain a corresponding energy saving state in the one or more PDCCH monitoring occasions. The second field may indicate the terminal device to maintain the energy saving state in one or more PDCCH monitoring occasions starting from a current PDCCH monitoring occasion, or indicate the terminal device to maintain the corresponding energy saving state in one or more PDCCH monitoring occasions starting from a next PDCCH monitoring occasion. Therefore, if the energy saving state is a sleep state, the terminal device skips the one or more PDCCH monitoring occasions indicated by the second field. To be specific, the terminal device is indicated not to perform PDCCH detection within the one or more PDCCH monitoring occasions and not to perform data scheduling; or the terminal is indicated to perform data scheduling after the one or more PDCCH monitoring occasions, and the terminal device starts to monitor a PDCCH after the one or more PDCCH monitoring occasions. The PDCCH monitoring occasion is obtained based on a configuration of the base station. Usually, the network device configures one or more search spaces for the terminal device, and the terminal device determines the PDCCH monitoring occasion based on a configuration status of the search space. For example, it is assumed that the network device configures a search space 0 for the terminal device, and a monitoring period of the search space 0 is two slots. Therefore, when the second field indicates two PDCCH monitoring occasions, optionally, the terminal device is in a corresponding energy saving state in two PDCCH monitoring occasions starting from a current PDCCH monitoring occasion, or the terminal device is in a corresponding energy saving state in two PDCCH monitoring occasions starting from a next PDCCH monitoring occasion of a current PDCCH monitoring occasion. Alternatively, for another example, the network device configures a search space 0 and a search space 1 for the terminal device, a monitoring period of the search space 0 is two slots, and a monitoring period of the search space 1 is one slot, which is shown inFIG.8. In this case, for the terminal device, there may be the following several manners for the PDCCH monitoring occasion: In a first processing manner, the PDCCH monitoring occasion means PDCCH monitoring occasion of all search spaces. In this case, the terminal device needs to monitor the search space 0 and the search space 1 in each of a slot 0 to a slot 9. Therefore, each of the slot 0 to the slot 9 includes one PDCCH monitoring occasion. Optionally, if the second field indicates the terminal device to maintain a corresponding energy saving state in subsequent two PDCCH monitoring occasions, it is equivalent to indicating the terminal device to maintain the corresponding energy saving state in a total of three slots including a current slot. Optionally, if the second field indicates the terminal device to maintain a corresponding energy saving state in two PDCCH monitoring occasions starting from a current PDCCH monitoring occasion, it is equivalent to indicating the terminal device to maintain the corresponding energy saving state in a total of two slots including a current slot. In a second processing manner, the PDCCH monitoring occasion means a PDCCH monitoring occasion of a specific search space. For a PDCCH monitoring occasion of the search space 0, there is one PDCCH monitoring occasion in every two slots. Optionally, if the second field indicates the terminal device to maintain a corresponding energy saving state in subsequent two PDCCH monitoring occasions, it is equivalent to indicating the terminal device to maintain the corresponding energy saving state in six slots. Optionally, if the second field indicates the terminal device to maintain a corresponding energy saving state in two PDCCH monitoring occasions starting from a current PDCCH monitoring occasion, it is equivalent to indicating the terminal device to maintain the corresponding energy saving state in four slots. Similarly, for a PDCCH monitoring occasion of the search space 1, there is one PDCCH monitoring occasion in each slot. Optionally, if the second field indicates the terminal device to maintain a corresponding energy saving state in subsequent two PDCCH monitoring occasions, it is equivalent to indicating the terminal device to maintain the corresponding energy saving state in three slots. Optionally, if the second field indicates the terminal device to maintain a corresponding energy saving state in two PDCCH monitoring occasions starting from a current PDCCH monitoring occasion, it is equivalent to indicating the terminal device to maintain the corresponding energy saving state in two slots. It can be understood that, in the foregoing two processing manners, if a same PDCCH monitoring occasion may be obtained based on configurations of the two search spaces, results of the two methods are the same. In addition, there may be another setting manner, for example, a manner of a smaller time granularity TS. No enumeration is listed herein. In addition to the configuration for the manner of representing the time length information, a start moment of the time period further needs to be configured in the time length information. The start moment may be directly configured as a specific moment, or may be configured in a preset manner. For example, a moment at which the terminal device receives the first information may be used as the start moment. For another example, a start moment of a next one or more slots (or subframes) after the terminal device receives the first information may be used as the start moment of the time period. In addition to the foregoing configuration manner for specific content in each second time period, the configuration manner of the second field is similar to that of the first field, but the second field and the first field carry different information. Therefore, there may be at least the following three configuration manners: In a first manner, new first information used to indicate the energy saving state of the terminal device is designed. In this implementation, a field quantity, a field location, and a definition of each field of the first information may be configured as required. Essentially, a new information format is designed. An example in which the first information is DCI is still used. Referring toFIG.9, the 1stfield in the first information includes the information indicating the time length in which the terminal device maintains the energy saving state, which is the second field. In addition, in a feasible implementation, the first information may be downlink control information (DCI). In this case, if the first information is in a newly designed DCI format, the first information may further include other fields, and these fields may be defined as required. Therefore, in a specific implementation scenario, the first information may further include one or more of the following fields:a bandwidth part indicator (BWP indicator) field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, and an antenna port(s) field. When the energy saving state that needs to be maintained and that corresponds to the second field is a wake-up state, the bandwidth part indicator field is used to indicate a BWP of downlink data that the terminal device needs to receive subsequently, and the terminal device may correspondingly receive the downlink data at the BWP; the SRS request field is used to indicate the terminal device to perform aperiodic SRS sending; and the TPC command for scheduled PUSCH field is used to indicate a power adjustment value for scheduling uplink data sending. In an optional implementation scenario, the first information may be configured in a manner shown inFIG.9. To be specific, in addition to the second field, the first information further includes the foregoing fields. It should be noted that a configuration location of each field in the first information may be set as required. For example, the second field may be configured in any field in the first information. Specifically, as shown inFIG.9, the second field may be configured in an initial field of the first information, or the second field may be configured at any location in the middle of the first information, or the second field may be configured at an end location of the first information. In the configuration manner shown inFIG.9, the second field is configured in the initial field of the first information. This can help the terminal device quickly determine, after receiving the first information, the time period in which the terminal device needs to maintain the energy saving state. Therefore, when the terminal device specifically maintains the energy saving state, the terminal device may read or abandon reading information carried in another field of the first information, thereby further reducing energy consumption. The foregoing fields are merely preferred fields. During actual implementation of this solution, the first information may further include another field. Optionally, the first information may further include one or more of the following fields: a bandwidth part indicator (BWP indicator) field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, an antenna port(s) field, a synchronization signal/broadcast channel indicator (SS/PBCH index) field, a short message field, a modulation and coding scheme (MCS) field, a downlink assignment index (DAI) field, a transmitted precoding matrix indicator (TPMI) acknowledgment field, a precoding matrix indicator (PMI) acknowledgment field, a downlink power compensation (Downlink power offset) field, a hybrid automatic repeat request (HARQ) process number field, a transport block to codeword swap flag field, a precoding information field, a transmit power control (TPC) field, a scrambling identity field, an antenna port(s), scrambling identity and number of layers field, a physical downlink shared channel resource element mapping and quasi-co-location indicator field, a demodulation reference signal phase rotation and OCC index (Cyclic shift for Demodulation Reference Signal and Orthogonal Cover Code index) field, an uplink index (ULI) field, a downlink assignment index (DAI) field, a channel state information request field, and the like. In this implementation, a meaning of each field in the first information may be defined as required. Compared with an existing DCI format, the first information defined in this manner can reduce fields included in the DCI format to some extent, so that the terminal device enables a minimum quantity of functions, thereby achieving energy saving. In addition, a user-defined manner is relatively flexible. In a second manner, a new field is added to existing information to obtain the first information. For ease of understanding, refer to a schematic structural diagram of first information shown inFIG.10. The first information includes (N+1) fields in total, where N is an integer greater than or equal to 1. The first N fields in the first information are all fields in existing DCI, and an (N+1)thfield is the second field described in this application. The field is a newly added field in the existing DCI, and specifically includes the information indicating the time length in which the terminal device maintains the energy saving state. In addition, it should be further noted that a location of the newly added field is not particularly limited in this embodiment of this application. As shown inFIG.10, a manner of configuring the newly added second field at an end location of the existing DCI is merely a feasible implementation. In addition, the newly added second field may be further configured at a start location of the existing DCI, or the newly added field may be configured at any location in the middle of the existing DCI. An existing DCI format includes a DCI format for a group, for example, a DCI format 2-2. A field length of the DCI format is variable, a base station configures different format lengths for different quantities of terminals in the group, and information in the DCI format may be used to simultaneously indicate a plurality of terminals. Therefore, in a preferred implementation process, if the second field is a newly added field in the first information, the first information may be but is not limited to the DCI format 2-2. When the first information is in the DCI format 2-2, a plurality of second fields may be added to indicate time length information of different terminals in the group. Specifically, refer to first information shown inFIG.11. InFIG.11, M second fields are added to the existing DCI information. A second field of a terminal device1is used to indicate information about a time length in which the terminal device1maintains an energy saving state1, and a second field of a terminal device2is used to indicate information about a time length in which the terminal device2maintains an energy saving state2. By analogy, a second field of a terminal device M is used to indicate information about a time length in which the terminal device M maintains an energy saving state M, where M is an integer greater than 1. It should be noted that, when second fields of a plurality of different terminal devices are configured in one piece of first information, energy saving states of the terminal devices that are indicated by the fields may be the same or may be different, and time lengths of the terminal devices that are indicated by the fields may be the same or may be different. The terminal device1and the terminal device2inFIG.11are still used as an example. The second field of the terminal device1may be configured to indicate a time period1in which the terminal1maintains a sleep state, and the second field of the terminal device2may be configured to indicate a time period2in which the terminal2maintains a wake-up state. In addition, in a feasible implementation scenario, one second field may alternatively include a plurality of pieces of energy saving state information, and each piece of energy saving state information may indicate information about a time length in which one terminal device in the group maintains an energy saving state. Certainly, all other existing DCI formats may also be used as the first information, for example, a DCI format 0-0, a DCI format 0-1, a DCI format 1-0, a DCI format 1-1, a DCI format 2-0, a DCI format 2-1, and a DCI format 2-3. For example, when the first information is in the DCI format 1-0, a second field may be added to the DCI format 1-0, and the second field includes the information indicating the time length in which the terminal device maintains the energy saving state. Optionally, when a second field is added to an existing DCI format, if the field includes information indicating a time length in which the terminal device maintains a sleep state, the terminal device may ignore an original field in the DCI format in a time period corresponding to the time length, and may directly enter a sleep state at a start moment of the time period instead of performing related scheduling based on the original field. When the first information is configured in a configuration manner of adding a new field, all or some bits of the newly added field may be used to indicate the energy saving state information of the terminal device, and/or all or some values of the newly added field are used to indicate the energy saving state information of the terminal device. For an implementation thereof, refer to the first implementation. In this configuration manner of adding a new field, existing DCI is lengthened, and the energy saving state information of the terminal device is indicated by using the newly added field. In addition, because no multiplexing or other processing is performed on an original field in the existing DCI, no function limitation is imposed on the original field in the existing DCI. In a third manner, an original field in existing information is multiplexed to obtain the first information. A principle of this implementation is as follows: Without changing a field length of existing DCI, an entire field or a part of the filed that can be multiplexed in the DCI is multiplexed into the second field, and the energy saving state information is set in the second field. In this way, when the second field occupies only a part of an original field, the part of the original field multiplexed into the second field may be located at a start location of the original field, any location in the middle of the original field, or an end location of the original field. Referring toFIG.12, the second field includes N original fields in total, where N is an integer greater than or equal to 1. A part that is of a ythoriginal field and that is located at an end location of the ythoriginal field is multiplexed into the second field. In this way, the information indicating the time length in which the terminal device maintains the energy saving state needs to be configured in the part that is of the field and that is multiplexed, where y is an integer ranging from 1 to N. A field that can be multiplexed may be selected and configured as required. In a preferred implementation process, the second field may be but is not limited to a frequency domain resource allocation field in the first information. For example, a frequency domain resource assignment field in existing DCI for a DCI format of a single terminal device such as a DCI format 0-0, a DCI format 0-1, a DCI format 1-1, or a DCI format 0-1 is used to indicate downlink/uplink data frequency resource allocation in the existing DCI. Therefore, a part of the field may be multiplexed into the second field to carry the energy saving state information. Optionally, when the second field is added to the existing DCI format, if the field includes information indicating a time length in which the terminal device maintains a sleep state, the terminal device may ignore an original field in the DCI format in a time period corresponding to the time length, and may enter a sleep state at a start moment of the time period instead of performing related scheduling based on the original field. Optionally, the multiplexed field may alternatively be another field in the existing DCI format, for example, a bandwidth part indicator (BWP indicator) field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, an antenna port(s) field, a synchronization signal/broadcast channel indicator (SS/PBCH index) field, a short message field, a modulation and coding scheme (MCS) field, a downlink assignment index (DAI) field, a transmitted precoding matrix indicator (TPMI) acknowledgment field, a precoding matrix indicator (PMI) acknowledgment field, a downlink power compensation (Downlink power offset) field, a hybrid automatic repeat request (HARQ) process number field, a transport block to codeword swap flag field, a precoding information field, a transmit power control (TPC) field, a scrambling identity field, an antenna port(s), scrambling identity and number of layers field, a physical downlink shared channel resource element mapping and quasi-co-location indicator field, a demodulation reference signal phase rotation and OCC index (Cyclic shift for Demodulation Reference Signal and Orthogonal Cover Code index) field, an uplink index (ULI) field, a downlink assignment index (DAI) field, or a channel state information request field. A third aspect is configuring both the first field and the second field in the first information. First, it should be noted that the first field and the second field may be a same field, or may be different fields. For example, referring to first information shown inFIG.13, the first information is configured in a manner of designing a new information format, and the first information includes a first field, a second field, a BWP indicator field, an SRS request field, a TPC command for scheduled PUSCH field, and another field (which is represented by an ellipsis). The first field and the second field occupy locations of two fields in the first information. For another example, referring to first information shown inFIG.14, the first information is configured by adding a field to an original field of existing information, and includes N+1 fields in total. In addition to N original fields, the first field and the second field jointly occupy a location of an (N+1)thfield. In addition, the first field and the second field may be configured in a same configuration manner, or may be configured in different configuration manners. For example, first information shown inFIG.15includes (N+2M) fields in total. In addition to N original fields, the first information further includes first fields and second fields of M terminal devices. In this case, each first field and each second field are configured in a same manner, and are obtained in a manner of adding a field to an original field in existing information. Alternatively, for another example, first information shown inFIG.16includes (N+1) fields in total, N fields are original fields in existing DCI, and an (N+1)thfield is a newly added field. In addition, the newly added field is the first field, and a part of a ythfield in the original fields is multiplexed into the second field, where y is an integer ranging from 1 to N. In this case, the first field is the newly added field in the existing DCI, and the second field is obtained by multiplexing the part of the original field. The two configuration manners are different. In addition, when one piece of first information carries first fields and second fields of a plurality of terminal devices, in a preferred case, as shown inFIG.15, M first fields are in a one-to-one correspondence with M second fields, and quantities of the M first fields and the M second fields are equal. In an extreme case, the first field and the second field may be set only for some terminal devices, and the first field is set only for the other terminal devices, or the second field is set only for the other terminals, which may be used in combination. In the foregoing manner, the network device may complete configuration of the first information, and then the network device sends the first information to the terminal device. The following describes an information receiving method from the perspective of a terminal. After receiving the first information, the terminal device may obtain different information based on different configuration manners of the first information, including at least one of the energy saving state information and the time length information. Therefore, when the terminal device adjusts the energy saving state of the terminal device, there may be at least the following cases: In a first case, the terminal device obtains the energy saving state information and the time length information based on the first information. In this case, in the time period indicated by the time length information, the terminal adjusts the energy saving state of the terminal and maintains a sleep state or a wake-up state indicated by the energy saving state information. In a second case, the terminal device obtains the energy saving state information only based on the first information. Optionally, the terminal device may directly adjust the energy saving state of the terminal device and maintain a sleep state or a wake-up state indicated by the energy saving state information. Optionally, based on a preset time period: next one or more slots (or subframes, or on duration, or PDCCH monitoring occasions) of the first information, the terminal device adjusts the energy saving state of the terminal device and maintains a sleep state or a wake-up state indicated by the energy saving state information. Optionally, the network device may send indication information including the second field to the terminal device. Correspondingly, the terminal device receives and reads the indication information, to obtain a target time period indicated by the second field. Therefore, in the target time period, the terminal device adjusts the energy saving state of the terminal device and maintains a sleep state or a wake-up state indicated by the energy saving state information. Optionally, the network device may send configuration manner information of the first information to the terminal device, and the terminal device reads the first information based on the configuration manner information, to obtain the energy saving state information and a target time period corresponding to the energy saving state. The configuration manner information is used to indicate a meaning of each field in the first information, or preset duration corresponding to each first field, or preset duration corresponding to each energy saving state. For example, if the first information includes only a plurality of first fields (referring toFIG.6), and the configuration manner information of the first information indicates preset duration corresponding to each first field, the terminal device determines the preset duration corresponding to each first field as the target time period. For another example, if the network device presets preset duration corresponding to a sleep state to one slot, and preset duration corresponding to a wake-up state to three slots, in addition to configuring only the first field in the first information and sending the first field to the terminal device, the network device further sends the configuration manner information including the correspondence to the terminal device. In this case, the terminal device may determine a specific period for maintaining the energy saving state. The target time period may be obtained in any one of the foregoing implementations. In a third case, the terminal device obtains, based on only the first information, the information about the time length for maintaining the energy saving state. Optionally, the terminal device may set, by default, the energy saving state that needs to be maintained as a sleep state. In this case, only after the terminal device receives the first information, in other words, within the time period indicated by the second field, the terminal device adjusts the energy saving state of the terminal device and switches to a sleep state. Optionally, the terminal device may set, by default, the energy saving state that needs to be maintained to be opposite to a current energy saving state. In this case, the terminal device only needs to determine a current energy saving state of the terminal device after receiving the first information. Therefore, within the time period indicated by the second field, the terminal device adjusts the energy saving state of the terminal device and switches to an energy saving state that is opposite to the current energy saving state. Optionally, the network device may send indication information including the first field to the terminal device. Correspondingly, the terminal device receives and reads the indication information, to obtain the energy saving state indicated by the first field. Therefore, in the time period indicated by the second field, the terminal device adjusts the energy saving state of the terminal device and maintains a sleep state or a wake-up state indicated by the indication information. For example, in a specific implementation scenario, the network device may send third information to the terminal device, and the third information is used to indicate that the terminal device is in a sleep state or a wake-up state. Correspondingly, the terminal device receives the third information sent by the network device, and obtains, based on the third information, the target state corresponding to the target time period. Optionally, the network device may send the configuration manner information of the first information to the terminal device, and the terminal device reads the first information based on the configuration manner information, to obtain the energy saving state information and the target time period corresponding to the energy saving state. The configuration manner information is used to indicate a meaning of each field in the first information, or an energy saving state corresponding to each first field. For example, the first information includes only a plurality of second fields (referring toFIG.11), and the configuration manner information of the first information indicates an energy saving state corresponding to each second field. In this case, the terminal device determines, based on identification information of the terminal device, the second field corresponding to the terminal device, and further determines the energy saving state corresponding to the second field. Therefore, within the time period indicated by the second field, the terminal device adjusts the energy saving state of the terminal device and maintains a sleep state or a wake-up state corresponding to the second field. The target time period may be obtained in any one of the foregoing implementations. In this embodiment of this application, to further reduce energy consumption of the terminal device, classification may be performed based on whether the terminal device supports an energy saving working mode. The energy saving working mode is a working mode in which the terminal device can support switching between a sleep state and a wake-up state. In addition, the terminal device can monitor and receive a PDCCH in a wake-up state, and cannot monitor or cannot receive a PDCCH in a sleep state, thereby reducing energy consumption. A normal working mode is relative to the energy saving working mode. In the normal working mode, the terminal device performs blind PDCCH detection in a preset manner. Based on this, during specific implementation, the terminal device may send capability information of the terminal device to the network device, so that the network device indicates, based on the capability information, whether the terminal device switches to the energy saving working mode. The capability information is used to indicate whether the terminal device has the energy saving working mode. Therefore, correspondingly, the network device receives the capability information. Therefore, to reduce energy consumption, the network device may send the first information to only a terminal device that supports the energy saving working mode, and does not send the first information to a terminal device that does not support the energy saving working mode. This reduces energy consumption caused by meaningless information receiving by this part of terminal devices. In addition, the network device may further send second information to the terminal device that supports the energy saving working mode, and the second information may be used to indicate whether the terminal device switches to the energy saving working mode. Correspondingly, the terminal device receives the second information sent by the network device. Optionally, if the second information indicates the terminal device to switch a current working mode to the energy saving working mode, a working mode switching process is performed. It can be learned that, if the current working mode is the energy saving working mode, no switching processing needs to be performed. Alternatively, the network device may receive only the capability information but not indicate to send the first information. In this case, the network device still sends the first information through group-sending or one-by-one sending in an original manner. In this process, whether the terminal device has the energy saving working mode is not considered. In addition, in this embodiment of this application, it is considered that the terminal device needs specific duration to receive and demodulate the first information, in other words, needs offset duration offset. The offset duration is used to represent a time length between a receiving moment at which the terminal device receives the first information and a preset moment. The preset moment is the first slot or the first subframe in which the terminal device enters on duration on duration in a discontinuous reception (DRX) state. In addition, it should be noted that a delay between the receiving moment at which the terminal device receives the first information and a sending moment at which the network device sends the first information is relatively small. In some application scenarios, the offset is used to represent a time length between the sending moment at which the network device sends the first information and the preset moment. In this case, this definition manner is also applicable to the foregoing solution provided in this application. Therefore, the method may further include the following steps:sending, by the terminal device, offset information to the network device, so that the network device configures the first information based on the offset information; andreceiving, by the network device, the offset information. After receiving the offset information, the network device may use the offset duration as a reference, to configure a specific value of the time length information included in the second field. During specific implementation, the target time period indicated by the time length information is greater than or equal to the offset duration. Alternatively, similar to the second information, the network device may receive only the offset information, and is not configured to indicate to configure the time length information in the second field. In this case, the network device does not consider the offset information, and still configures the second field in an original manner. The first information, the second information, the third information, the capability information, the offset information, and the like in this embodiment of this application may be carried in higher layer control signaling to implement sending and receiving. The higher layer control signaling may include but is not limited to at least one of radio resource control (RRC) signaling, media access control control element (MAC CE) signaling, and DCI signaling. Optionally, the second information is at least one of an RRC message, a MAC CE message, and DCI. Optionally, the third information is at least one of an RRC message, a MAC CE message, and DCI. It can be understood that some or all of the steps in the foregoing embodiments are merely examples. In this embodiment of this application, other operations or variants of operations may be further performed. In addition, the steps may be performed in a sequence different from that presented in the foregoing embodiment, and possibly, not all operations in the foregoing embodiment need to be performed. It can be understood that, in the foregoing embodiments, an operation or a step implemented by the terminal device may alternatively be implemented by a component (for example, a chip or a circuit) that can be used for the terminal device, an operation or a step implemented by a core network node may alternatively be implemented by a component (for example, a chip or a circuit) that can be used for the core network node, and an operation or a step implemented by the network device (for example, a first network device, a second network device, or a third network device) may alternatively be implemented by a component (for example, a chip or a circuit) that can be used for the network device. FIG.17is a schematic structural diagram of a communications device170. The communications device may be configured to implement the method in the part corresponding to the network device or the method in the part corresponding to the terminal device described in the foregoing method embodiments. For details, refer to the descriptions in the foregoing method embodiments. The communications device170may include one or more processors171. The processor171may also be referred to as a processing unit, and may implement a specific control function. The processor171may be a general-purpose processor, a special-purpose processor, or the like. In an optional design, the processor171may also store an instruction, and the instruction may be run by the processor171, so that the communications device170is enabled to perform the method, described in the foregoing method embodiment, corresponding to the terminal device or the network device. In another possible design, the communications device170may include a circuit, and the circuit may implement the transmission, reception, or communication function in the foregoing method embodiments. Optionally, the communications device170may include one or more memories172. The memory172stores an instruction or intermediate data. The instruction may be run on the processor171, so that the communications device170is enabled to perform the methods described in the foregoing embodiments. Optionally, the memory172may further store other related data. Optionally, the processor171may also store an instruction and/or data. The processor171and the memory172may be separately disposed, or may be integrated together. Optionally, the communications device170may further include a transceiver173. The processor171may be referred to as a processing unit. The transceiver173may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver, or the like, and is configured to implement sending and receiving functions of the communications device. If the communications device is configured to implement an operation corresponding to a network device side in the embodiment shown inFIG.3, for example, the transceiver173may send the first information and the second information to the terminal device, and the transceiver173receives the capability information and the offset information that are sent by the terminal device. The transceiver173may further complete another corresponding communication function. The processor171is configured to complete a corresponding determining or control operation. Optionally, a corresponding instruction may be further stored in the memory172. For a specific processing manner of each component, refer to the related descriptions in the foregoing embodiments. If the communications device is configured to implement an operation corresponding to a terminal device side in the embodiment shown inFIG.3, for example, the transceiver173may receive the first information, the second information, and the third information that are sent by the network device, and the transceiver173sends the capability information and the offset information to the network device. The transceiver173may further complete another corresponding communication function. The processor171is configured to complete a corresponding determining or control operation. Optionally, a corresponding instruction may be further stored in the memory172. For a specific processing manner of each component, refer to the related descriptions in the foregoing embodiments. The processor and the transceiver described in this application may be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a composite signal IC, an application-specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, or the like. The processor and the transceiver may also be manufactured by using various1C process technologies, for example, a complementary metal-oxide-semiconductor (CMOS), an N-channel metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), a p-channel metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), a bipolar junction transistor (BJT), a bipolar CMOS (BiCMOS), silicon germanium (SiGe), and gallium arsenide (GaAs). Optionally, the communications device may be an independent device or may be a part of a relatively large device. For example, the device may be:(1) an independent IC, a chip, or a chip system or subsystem;(2) a set having one or more ICs, where optionally, the IC set may also include a storage component configured to store data and/or an instruction;(3) an ASIC, for example, a modem (MSM);(4) a module that can be embedded in another device;(5) a receiver, a terminal device, a cellular phone, a wireless device, a handheld phone, a mobile unit, or a network device; or(6) another device or the like. FIG.18is a schematic structural diagram of a communications device according to an embodiment of this application. As shown inFIG.18, the communications device180includes a configuration module181and a transceiver module182. The configuration module181is configured to configure first information, where the first information includes a first field and/or a second field, the first field includes information indicating an energy saving state of a terminal device, and the second field includes information indicating a time length in which the terminal device maintains the energy saving state. The transceiver module182is configured to send the first information to the terminal device. InFIG.18, optionally, all or some bits of the first field are used to indicate the energy saving state information of the terminal device. Optionally, all or some values of the first field are used to indicate the energy saving state information of the terminal device. Optionally, the first field is a newly added field or an original field in the first information. In a possible manner, when the first field is an original field in the first information, the first field is a frequency domain resource allocation field in the first information. In another possible manner, when the first field is a newly added field in the first information, the first information is in a downlink control information format DCI format 2-2. InFIG.18, the energy saving state information includes:information that indicates the terminal device to go to sleep; orinformation that indicates the terminal device to wake up. InFIG.18, optionally, all or some bits of the second field are used to indicate the information about the time length in which the terminal device maintains the energy saving state. Optionally, all or some values of the second field are used to indicate the information about the time length in which the terminal device maintains the energy saving state. Optionally, the second field is a newly added field or an original field in the first information. In a possible manner, when the second field is an original field in the first information, the second field is a frequency domain resource allocation field in the first information. In another possible manner, when the second field is a newly added field in the first information, the first information is in the downlink control information format 2-2. InFIG.18, optionally, the time length information is:one or more slots; orone or more subframes; orone or more pieces of on duration on duration; orone or more physical downlink control channel monitoring occasions PDCCH monitoring occasion. InFIG.18, the first information further includes at least one of the following fields:a bandwidth part indicator field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, and an antenna port(s) field. InFIG.18, the transceiver module182is further configured to:receive offset duration offset information sent by the terminal device, where the offset information indicates information about a time length between a receiving moment at which the terminal device receives the first information and a preset moment, and the preset moment is the first slot or the first subframe in which the terminal device enters on duration on duration in a discontinuous reception state. InFIG.18, the transceiver module182is further configured to:receive capability information sent by the terminal device, where the capability information is used to indicate whether the terminal device has an energy saving working mode. InFIG.18, the transceiver module182is further configured to:send second information to the terminal device, where the second information is used to indicate whether the terminal device switches to the energy saving working mode. Optionally, the second information is at least one of a radio resource control Radio Resource Control message, a media access control control element (MAC CE) message, and downlink control information (DCI). InFIG.18, the transceiver module182is further configured to:send third information to the terminal device, where the third information is used to indicate that the terminal device is in a sleep state or a wake-up state. Optionally, the third information is at least one of a radio resource control (RRC) message, a media access control control element (MAC CE) message, and downlink control information (DCI). Optionally, the first information is downlink control information (DCI). The communications device in the embodiment shown inFIG.18may be configured to execute the technical solution on a network device side in the foregoing method embodiment. For an implementation principle and a technical effect of the communications device, further refer to related descriptions in the method embodiment. Optionally, the communications device may be a base station, or may be a component (for example, a chip or a circuit) of a base station. FIG.19is a schematic structural diagram of another communications device according to an embodiment of this application. As shown inFIG.19, the communications device190includes a transceiver module191, an obtaining module192, and an adjustment module193. The transceiver module191is configured to receive first information sent by a network device, the first field includes information indicating an energy saving state of a terminal device, and the second field includes information indicating a time length in which the terminal device maintains the energy saving state. The obtaining module192is configured to obtain at least one of the energy saving state information and the time length information based on the first information. The adjustment module193is configured to adjust the energy saving state of the terminal device based on the at least one of the energy saving state information and the time length information. InFIG.19, optionally, all or some bits of the first field are used to indicate the energy saving state information of the terminal device. Optionally, all or some values of the first field are used to indicate the energy saving state information of the terminal device. Optionally, the first field is a newly added field or an original field in the first information. In a possible manner, when the first field is an original field in the first information, the first field is a frequency domain resource allocation field in the first information. In another possible manner, when the first field is a newly added field in the first information, the first information is in a downlink control information format DCI format 2-2. InFIG.19, optionally, the energy saving state information includes:information that indicates the terminal device to go to sleep; orinformation that indicates the terminal device to wake up. InFIG.19, optionally, all or some bits of the second field are used to indicate the information about the time length in which the terminal device maintains the energy saving state. Optionally, all or some values of the second field are used to indicate the information about the time length in which the terminal device maintains the energy saving state. Optionally, the second field is a newly added field or an original field in the first information. In a possible manner, when the second field is an original field in the first information, the second field is a frequency domain resource allocation field in the first information. In another possible manner, when the second field is a newly added field in the first information, the first information is in the downlink control information format 2-2. InFIG.19, optionally, the time length information is:one or more slots; orone or more subframes; orone or more pieces of on duration on duration; orone or more physical downlink control channel (PDCCH) monitoring occasions. InFIG.19, optionally, the first information further includes at least one of the following fields:a bandwidth part indicator field, a sounding reference signal request (SRS request) field, a transmit power control command for a preset physical uplink shared channel (TPC command for scheduled PUSCH) field, and an antenna port(s) field. InFIG.19, the transceiver module191is further configured to:send offset duration offset information to the network device, where the offset information indicates information about a time length between a receiving moment at which the terminal device receives the first information and a preset moment, and the preset moment is the first slot or the first subframe in which the terminal device enters on duration on duration in a discontinuous reception state. InFIG.19, the transceiver module191is further configured to:send capability information to the network device, where the capability information is used to indicate whether the terminal device has an energy saving working mode. InFIG.19, the transceiver module191is further configured to receive second information sent by the network device, where the second information is used to indicate whether the terminal device switches to the energy saving working mode. Optionally, the second information is at least one of a radio resource control (RRC) message, a media access control control element (MAC CE) message, and downlink control information (DCI). InFIG.19, the transceiver module191is further configured to receive third information sent by the network device, where the third information is used to indicate that the terminal device is in a sleep state or a wake-up state. Optionally, the third information is at least one of a radio resource control (RRC) message, a media access control control element (MAC CE) message, and downlink control information (DCI). Optionally, the first information is downlink control information (DCI). InFIG.19, when the first information includes the first field and the first field is the information that indicates the terminal device to go to sleep, the obtaining module192is further configured to abandon reading other information in the first information. The communications device in the embodiment shown inFIG.19may be configured to execute the technical solution in the foregoing method embodiment. An implementation principle and a technical effect of the communications device are similar to those of the method embodiment. The communications device may be a terminal device, or may be a component (for example, a chip or a circuit) of a terminal device. It should be understood that division of the modules in the communications devices inFIG.18andFIG.19is merely logical function division. During actual implementation, all or some of the units may be integrated into one physical entity, or the units may be physically separated. In addition, all of the modules may be implemented in a form of software invoked by a processing element or in a form of hardware. Alternatively, some of the modules may be implemented in a form of software invoked by a processing element, and some of the modules may be implemented in a form of hardware. For example, the transceiver module may be an independently disposed processing element, or may be integrated into a communications device, for example, a specific chip of the terminal device for implementation. In addition, the transceiver module may be stored in a memory of the communications device in a form of a program, and a specific processing element of the communications device invokes and performs a function of each of the foregoing modules. Implementations of other modules are similar. In addition, all or some of the modules may be integrated, or may be implemented independently. The processing element described herein may be an integrated circuit and has a signal processing capability. In an implementation process, steps in the foregoing methods or the foregoing modules can be implemented by using a hardware integrated logical circuit in the processing element, or by using an instruction in a form of software. For example, the foregoing modules may be configured as one or more integrated circuits for implementing the foregoing methods, for example, one or more application-specific integrated circuits (ASIC), one or more microprocessors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a module is implemented in a form of a program invoked by a processing element, the processing element may be a general-purpose processor, for example, a central processing unit (CPU) or another processor that can invoke the program. For still another example, the modules may be integrated together, and implemented in a form of a system-on-a-chip (SOC). An embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is run on a computer, the computer is enabled to perform the information sending method and/or the information receiving method in the foregoing embodiments. In addition, an embodiment of this application further provides a computer program product. The computer program product includes a computer program. When the computer program is run on a computer, the computer is enabled to perform the information sending method and/or the information receiving method in the foregoing embodiments. This application further provides a chip, including a memory and a processor. The memory is coupled to the processor. The processor is configured to perform the information sending method and/or the information receiving method described in the foregoing embodiments. Implementations of the information sending method and the information receiving method performed by the chip are described in the foregoing embodiments. Optionally, the chip may be an independently disposed chip, or may be a chip shared by a plurality of different processors. This is not particularly limited in this embodiment of this application. All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the procedure or functions according to this application are completely or partially generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable apparatuses. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state drive Solid State Disk), or the like. | 96,095 |
11943712 | DETAILED DESCRIPTION A wake-up radio manages power states of an information handling system and peripherals through a wake-up protocol separate from wireless networking protocols, such as BLUETOOTH and WiFi. For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components. Referring now toFIG.1, a portable information handling system10is depicted having wireless network interfaces with plural different types of peripheral devices. In the example embodiment, portable information handling system10is built in a portable housing12that integrates a display14in a lid portion rotationally coupled to a main portion having processing components that cooperate to process information. For example, a motherboard16couples to housing12and interfaces processing components to support information processing. A central processing unit (CPU)18executes instructions to process information with the instructions and information stored in a random access memory (RAM)20. A solid state drive (SSD)22provides persistent storage of instructions and information, such as an operating system and applications that are retrieved at runtime to RAM20for execution on CPU18. A wireless interface module24interfaces with CPU18to provide wireless communications for portable information handling system10with external devices and networks. For example, wireless interface module24supports wireless communication through wireless local area networks (WLAN), such as IEEE 802.11 (b, g and n) WiFi networks, through wireless personal area networks (WPAN), such as BLUETOOTH and BLE, or through other types of user data wireless interfaces that communication through shared public radio bands having channels in the 2.4 to 5 GHz frequency ranges. Although the example embodiment depicts a portable information handling system, other types of housing configurations may be used, such as desktop and server configurations. In the example embodiment, a variety of peripherals are depicted that communicate with portable information handling system10through their own wireless interface modules24, such as with WLAN or WPAN communications. A speaker26receives audible information through WLAN or WPAN wireless signals to play audible information as sounds. A keyboard28accepts inputs at keys30and communicates the inputs to portable information handling system10through WLAN or WPAN wireless signals for use as inputs. Similarly, a mouse32has a housing34that moves to allow position sensing by a position sensor38and to accept inputs at buttons36as inputs to portable information handling system10communicated through an integrated wireless interface module24. In the example of keyboard28and mouse32, communication is often performed with BLUETOOTH LOW ENERGY (BLE), which uses periodic communication intervals to help reduce power consumption. For instance, communication by the BLE protocol with periodic interval connections reduces power by reducing temperatures generated by the radio transmitter. A printer40includes a wireless interface module24to receive print jobs from portable information handling system10. A location peripheral42includes a wireless interface module24in a housing46that runs in a low power mode on a battery44to provide intermittent communications as an aid for location of an attached item, such as keys48. For instance, location peripheral42is a TILE or similar product that helps track locations based upon the location of an information handling system that detects wireless signals and reports a position of the information handling system to a server or other network location when location peripheral42wireless signals are detected. One advantage of using a secondary radio in the location peripheral is that other peripheral devices, not just information handling systems, can track location beacon reports, such as by relaying the beacons to host devices. Location peripheral42is one example of an IoT device, other examples might include temperature or humidity sensors that integrate a BLE system on chip. One difficulty with peripheral wireless communication interfaces to an information handling system is that a radio on both systems has to be simultaneously active to establish user data communication. Arranging simultaneous radio communication generally means increased power consumption at both the information handling system and peripheral, which can impact battery charge life. When battery power consumption becomes excessive, the radios are typically shut off so that end user interaction is required to wake the device. To achieve reduced power consumption, each wireless interface module24includes both a primary radio that supports WLAN and/or WPAN protocol wireless communications and a low power secondary radio that supports wake and sleep coordination. The secondary radio has minimal logical functions to support wake and sleep wireless commands that, when detected, wake the primary radio and its associated processing resource, such as by setting a GPIO signal high to the processing resource. The low power sleep state provided by the secondary radio allows peripherals to wake each other and an information handling system with minimal impact on battery charge. For example, an end user might make an input with a mouse or keyboard to activate the secondary radio and in turn wake the information handling system through its secondary radio. Conversely, the information handling system may power up and use the secondary radio to awaken the keyboard and mouse so that the system as a whole is more quickly ready to interact with the end user. Although the example embodiment relates to peripheral devices, alternative embodiments may include IoT devices, such as an IoT temperature sensor or gateway hub. IoT implementations may use the hardware and software solutions described below for peripheral devices. Referring now toFIG.2, a state diagram depicts one example for power state transitions based upon primary and secondary radio operations. At an initial state50, the primary radio is active to communicate user data through a network protocol, such as a WLAN or WPAN like BLUETOOTH. At state52a sleep event is determined, such as a command to power down or a predetermined idle time at an information handling system or peripheral. At the sleep event, a command to sleep is communicated with the primary radio to other primary radios of associated devices and the secondary radio is activated to receive an acknowledgement sent by the associated device. As is described below in greater detail, associations may be between information handling systems and one or more peripheral devices as well as between peripheral devices. For example, a keyboard might control power state at a mouse and vice versa. At state54, the secondary radio is activated and sends an acknowledgement so that the primary radios on both devices may be powered down to a low power mode. In the low power mode, the device may monitor for wake events, such as an input or power button press that wakes the processing resource, such as with an input at a GPIO. If a wake event is detected, the signal may also command a transmission of a wake command from the secondary radio to command a wake of other associated secondary radios of other associated devices. Similarly, in the low power mode when the secondary radio receives a wake command it initiates a wake of the processing resource by an input to a GPIO. At the wake event state56, the processing resource transitions the secondary radio to an off state and the primary radio to an on state. If the wake command is received by the secondary radio, an acknowledgement may be transmitted by the secondary radio or by the primary radio after the secondary radio is powered off. Similarly, when a secondary radio transmits the wake command, the processing resource may wait for an acknowledgment on the secondary radio or may transition to the primary radio. Referring now toFIG.3, a block diagram depicts a wireless interface module24having wake and sleep states supported by primary and secondary radios. Wireless interface module24provides a bi-directional wake-up using a shared radio infrastructure to communicate user data and wake commands between associated devices so that independent events on the associated devices initiates a wake and/or sleep state on the associated devices. Essentially, a parasite radio dedicated to wake-up command sharing in a same frequency band as a main radio reduces power consumption during low power states. In the example embodiment, a processing resource56is provided by a microcontroller unit (MCU) that executes instructions to manage a primary radio58and secondary radio60. Primary radio58communicates user data through user data protocols, such as WPAN and WLAN protocols. Secondary radio60communicates wake protocol commands that sleep and wake wireless interface module24. In the example embodiment, both primary radio58and secondary radio60transmit and receive in the 2.4 GHz band through a shared antenna76. For example, primary radio58supports BLE protocol communication at defined intervals and secondary radio60is programmed by processing resource56at entry to a sleep state to monitor a defined channel in the 2.4 GHz range for communication of wake commands. A flash memory57stores instructions for execution on processing resource56that manages user data communications and programs secondary radio to manage wake commands in the low power state. Pairing information68is defined by processing resource56to define BLE or other protocol communications and stored in RAM or flash memory. Although the processing resource56is depicted as a separate element from flash memory57and primary radio58, a system on chip (SOC) or similar architecture may combine these elements in one integrated circuit. In the example embodiment, an accelerometer65senses accelerations, a CMOS sensor64senses light, such as for power, and an LED66provides a visual indication of the operational state of wireless interface module24. Component interactions and programming may be supported through a number of interfaces, such as SPI links72and I2C links74. In operation, wireless interface module24powers up primary radio58when a need arises to transmit or receive user data and sleeps primary radio58during idle periods. Secondary radio60wakes when primary radio58sleeps so that low power is expended when listening for a wake command. If a wake command is detected, secondary radio60issues a wake signal through GPIO62that wakes processing resource56to initiate a wake of primary radio58and sleep of secondary radio60. A GPIO70interface between processing resource56and CMOS sensor64allows a local input to wake processing resource56so that it can command secondary radio60to send a wake command. Similarly, an acceleration sensed by accelerometer65may wake processing resource56to initiate a transmission of a wake command by secondary radio60. In one embodiment, secondary radio60communicates only the wake protocol, such as only transmitting and receiving wake and sleep commands. The wake protocol may be provided with a simple modulation scheme that is readily recognized by a comparator of secondary radio60, such as modulation of some portion of pairing information68with an On-Off Keying (OOK) or Amplitude-Shift Keying (ASK) modulation scheme in a defined channel, such as within a narrow bandwidth of less than 100 KHz. With just the secondary radio60active, power consumption of less than 10 microWatts may be achieved. A variety of power efficiencies may be accomplished with the primary and secondary radios. For instance, a shared antenna76reduces the component size and expense. Similarly, a shared crystal may provide both radios with accurate frequency control. Secondary radio60provides an attractive low power solution without a processing resource, such as by pre-programming wake and sleep commands in an internal register for comparison against detected incoming signals with an internal comparator. Wake and sleep commands defined by the wake protocol may be selected to enhance efficient transmission and reception, such as with lower data rates and unique preambles. In one alternative embodiment, to help promote backwards compatibility primary radio58may be selectively re-programmed to perform functions of secondary radio60. For example, if an information handling system having a conventional wireless interface that supports BLE interfaces with a peripheral having a wireless interface module and secondary radio, the wake protocol may be programmed into primary radio58when the peripheral goes to a low power state and returned to the BLE protocol when the peripheral wakes. Referring now toFIG.4, a block diagram depicts secondary radio protocol communications between an information handling system10and a peripheral, such as a keyboard28or mouse32. During normal operations, primary radios58communicate through a user data protocol, such as BLE, with user data packets78using parameters set in part by the transmission range between information handling system10and the peripherals. For example, primary radio58sets a transmit power that varies based on signal strength (RSSI) at each primary radio. At a predetermined condition, such as an idle time in which no end user interactions are detected, the peripheral device transmits to information handling system10through user data with the BLE protocol a sleep command to indicate entry to a sleep state of primary radio58. The peripheral then sleeps primary radio58and wake secondary radio60to listen for an acknowledgement. Information handling system10upon receiving the sleep command sleeps its primary radio58and wakes its secondary radio60to acknowledge the sleep command. Note that the sleep may be commanded from the information handling system10to the peripherals, such as at shutdown of information handling system10. Further, when information handling system10has external power, it may elect to have both the primary and secondary radios remain powered up. After both primary radios58are powered off, low power wake-up secondary radios60monitor a preprogrammed radio channel for a defined wake command, such as an OOK or ASK modulated signal that includes pairing information of the primary radio user data protocol, such as a BLE MAC address of a paired device. A wake-up packet80formatted with the wake protocol is transmitted by a first secondary radio60upon a wake event, such as a power up of information handling system10or an input at mouse32or keyboard28, and received by the second secondary radio60. At transmission of the wake command, the first secondary radio60wakes its primary radio58and at receipt of the wake command the second secondary radio60wakes its primary radio58. In the example embodiment, the wake command provides a unique preamble, a MAC header for the receive address and a frame body to provide a frame check sequence. Preprogrammed frequency channel, pairing information and protocol selections allow the wake command monitoring to consume a minimal amount of power. In addition, the RSSI determined transmission range from user data communications may be applied to set a transmission strength and data transmission length of the wake command. Slow data rates tend to increase secondary radio range while also increasing the amount of time need to communicate the wake command. Referring now toFIGS.5A,5B,5C,5D,5E and5F, flow diagrams depict a process for setting up and monitoring wake commands between low power wake-up secondary radios. The process starts at step82ofFIG.5Awith a host device, such as an information handling system, in an always-listen mode for pairing advertisement and continues to step84to determine if an advertisement packet is received. At a client device, such as a peripheral, the process starts at step86with the device placed in a pairing mode and continues to step88to broadcast advertisement packets. At step90a determination is made of whether a pairing initiation is made from the host and, if not the process returns to step88to continue advertisement. At step92and94a pairing sequence is initiate for the host and device by exchange of BLE keys. At step96and98a BLE session is established between the host and device, such as in accordance with the BLE standards. Once the BLE session is established, the process continues to step100and102for the host and device to exchange wake-up capabilities. At steps102and104, each device determines if a wake-up capability exists and, if so, the process continues to step106ofFIG.5B. If a wake-up capability does not exist, the process continues to step132ofFIG.5C. Referring now toFIG.5B, at step106the host device generates a 5 bit security key for the peripheral device and shares a wake-up key with the peripheral device. At step108the wake-up keys are sent as BLE user data through the primary radios and received at the peripheral device at step110. At step112and116the host and peripheral devices turn on their respective secondary radios and, at step114the peripheral device generates a wake command for communication by the secondary radio to the host device, such as by using the wake-up keys and device MAC addresses to define the content of a wake-up packet sent by OOK or ASK wireless signals. At step118the host device receives the wake command at the secondary radio and, at step120the host device verifies the wake command and generates an acknowledgement. At step122the peripheral device receives the acknowledgment and verifies the expected information. At step124the host device generates a wake command and transmits the wake command to the peripheral device. At step126the peripheral device receives the wake command and, at step128verifies the wake command and sends an acknowledgement to the host device. At step130upon receiving the acknowledgment, the host device confirms complete setup of the wake command for bi-directional wake of the host and peripheral devices. The process then continues to step132ofFIG.5Cto determine if a configuration should be performed for a group wake command. Referring now toFIG.5C, a flow diagram depicts a process for configuration of a group wake command. The process continues to step132for the peripheral device when prepared to set up a group wake command and then continues to step146ofFIG.5D. The host device continues to step134to determine if there is an existing group wake command at the host device. If yes, the process continues to step136to prompt the end user to select whether to join the existing group. If not the process continues to step170ofFIG.5E. If the end user elects to join the existing group the process continues to step138to share the 5 bit group key for with the peripheral device. If at step134no group wake exists, the process continues to step140to prompt the user to generate a group of peripherals. If not the process continues to step170ofFIG.5E. If the end user elects to form a group the process continues to step142to generate a 5 bit security key for the new group and continues to step144ofFIG.5D. In one alternative embodiment, at step132a group may be defined around plural peripheral devices independent of an information handling system, such as by associating a keyboard and a mouse by a group wake command that either the keyboard or mouse can initiate separate from an information handling system. Referring now toFIG.5D, a flow diagram depicts configuration of group wake command. The process starts at step144with transmission of the group wake command keys through a BLE interface to the peripheral device at step146. At step148the peripheral device turns on its wake-up secondary radio and at step150generates a group wake command to communicate to the host device. At step154the host device receives the wake command and at step158verifies the group wake command and sends an acknowledgement, which is received at the peripheral device at step160. At step162the host device generates a group wake command and transmits the group wake command to the peripheral device at step164. At step166the peripheral device verifies the wake command and transmits an acknowledgement to the host device at step168, which verifies completion of the verification. Although the process relates devices in defined groups, in alternative embodiments, the groups could be defined on an area basis. For example, a cube might have a keyboard, mouse, printer and display that interface through wireless signals and are associated based upon their area so that an end user interaction with one device may wake all other devices in a defined area. Referring now toFIG.5E, a flow diagram depict a process for setting up a sleep command at a peripheral. At step170, the host device generates a sleep command for the peripheral device based upon the pairing information and wake command key. The sleep command is transmitted to the peripheral device at step174through the BLE interface and received at step172. In response at step178the peripheral device generates an acknowledgement packet to transmit at step180through the secondary radio using the wake protocol. At step176the host device receives the acknowledgement to confirm the sleep configuration. The process then continues to step182ofFIG.5Fto set up a location beacon if desired. At step182the peripheral device generates a location beacon sent with the secondary a radio at step186with the wake protocol. At step184the host device receives the location beacon and at step188generate an acknowledgement for transmission through the primary radio at step190for communication to the peripheral device, which receives the acknowledgement at step192. The process ends at step194with the host and peripheral devices configured for communication supported by the low power wake-up secondary radio. In various embodiment, variations to the configuration may be done. For instance, instead of exchanging wake command keys, the BLE security may be used and the BLE pairing information may be hashed or otherwise adapted to provide a unique wake command. The unique wake command may include a unique preamble to help further reduce power consumption by reading irrelevant radio signals. The wake command may provide a capability exchange inserted by default in all wake protocol packets. Alternatively, conditional information insertion may depend on mode indication bits. In another embodiment wake packets may be defined without capability exchange inserted with a pre-promised condition between receive and transmit. Although the example embodiment describes a setup configuration through BLE, other protocols may be used, such as WLAN protocols. Referring now toFIGS.6A,6B and6C, radio transmit and receive events are depicted that provide low power secondary radio operations. Both the primary and secondary radios have an ability to sleep in off and low power modes. Sleep in an off or low power mode reduces power consumption to near zero, such as by powering down the radio crystal or even cutting off power dissipation at the radio entirely. In a receive mode, the radio consumes an increased amount of power but less than in a transmit mode. In order to minimize power consumption, in the low power modes the secondary radios attempt to synchronize transmit and receive windows so that wake commands are more effectively monitored with minimal power consumption. One technique that helps to reduce overall power consumption is to acknowledge commands received at a primary radio with a secondary radio and vice versa. Another technique is to use a longer term transmit for the secondary radio with shorter term periodic listen windows where the wake commands are infrequent events. In contrast, the BLE protocol defines a periodic connection interval for primary radios to interface for confirming the interface and transfer of data. The secondary radio provides a lower power solution by removing logic-dependent radio control that relies upon a processing resource and initiating logic-dependent radio control when a wake event is detected. FIG.6Adepicts an example where a 10 ms receive window is spaced every 200 ms to detect a 100 ms wake command transmission. In some example embodiments, the device that experiences the wake event may shift the transmit window over time to fall within the receive window of the sleeping device. Although the transmitting device consumes greater power than the receiving device, where wake events are dispersed over time the longer transmit window has a cumulatively reduced power consumption. The transmission may be, for example a repeat of the wake command over the transmit time period so that the receive device has a sufficient window to match the wake command against the wake command stored in an internal register.FIG.6Bdepicts an overlap of the receive window and the transmit window by decreasing the interval between periodic receives at the sleeping device to at least the length of the transmission by the device having he wake event.FIG.6Cillustrates another example of overlapping receive and transmit windows that can help to extend the interval between receive windows at a sleeping device. For example, a secondary radio receives a part of a wake command that matches a part of the wake command stored in the internal register, a wake may be performed to determine with the primary radio whether the other device in fact commanded and entered a wake state. Referring now toFIGS.7A and7B, flow diagrams depict a process to wake a device from a low power state with a wake command. In the example embodiment, the low power device receives in short bursts to listen for a wake command transmitted for at least a length of time greater than the interval between the receives. At step196and198, both devices are in a low power mode. At step200, the first device monitors for a wake event, such as a press at a keyboard key, a movement of a mouse or a power on at an information handling system. When a wake event is detected, the process continues to step202to bring the first device out of the low power mode, such as by a signal at a GPIO of a processing resource or the secondary radio that commands a wake. At step204a determination is made of whether the second device is active or sleeping. If the second device is active, the process continues to step214ofFIG.7B. If the second device is sleeping, the process continues to step206to create a wake command packet for communication by the secondary radio. At step208, the secondary radio broadcasts the wake command in a preassigned frequency channel is a “blast” mode that has a transmit time of greater than the second device receive window interval, as depicted byFIG.6B. At step210the second device secondary radio determines if it has received a wake command and monitors for a wake command until received. Once a wake command is received, the process continues to step212verify if the wake command is for the second device. If not the process returns to step198to continue monitoring for a wake command. If the wake command is for the second device, the process continues to step216ofFIG.7B. At step214, the first device initiates BLE bonding with the second device, such as with stored pairing information. At step216, the second device transitions from a sleep to a wake state, such as by providing a signal from the secondary radio to a GPIO of the processing resource that controls the primary radio. At step218, the second device establishes BLE bonding with the first device, such as through advertisement and reconnection BLE protocols of the primary radio. Although the example embodiment wakes a primary radio for BLE communications, in alternative embodiments, a wake command may be specific to different types of primary radios and user data protocols. For example, the wake command may include one or more bits that specify which primary radio and protocol are woken. In one embodiment, a two bit indication can command wake BLE only (0,1), wake WiFi only (1,0), wake up both BLE and WiFi (1,1), and wake an entire system (0,0). As is described below, adjustments to the wake command may also set devices to wake as part of a group or an area. For instance, a wake command can include a two bit indication that defines which of plural devices of a group should wake, either individually or collectively. Referring now toFIGS.8A and8B, flow diagrams depict a process for wake up of devices as a group. The process starts at step220with a first device in a low power mode and step22with a group of devices2through N in a low power mode. At step224the first device monitors for an event that indicates a transition to a wake state and, when an event is detected, continues to step226to generate a wake command for the group of devices2through N. At step228, the first device transmits the group wake command for a time period of greater than the interval between receive windows of the group of devices. After broadcast of the group wake command, the process continues to step234ofFIG.8B. At step222the group of devices are in a low power mode with at step230a periodic determination of receiving of the wake command. Once the wake command is determined, the process continues to steps232to verify that the wake command is for the device and/or a group to which the device is assigned. If so the process continues to step236ofFIG.8B. At step234the first device comes out of the low power mode and powers the primary radio. At step236, each of the devices of the group wake from the low power mode at receive of the group wake command. At step238and240the first device establishes BLE bonding with each device of the group using the primary radio user data protocol. At step242a determination is made of whether all of the devices of the group are awake, such as by the acknowledgement received through the primary radios. If not, the process returns to step226to attempt to wake remaining devices, either with another group wake command or with individual wake commands. As described above, the transition to an on state may relate to BLE only, WiFi only, or both radios, as well as to different types of wake states at each device as specified by the wake command or subsequent BLE communications. Referring now toFIGS.9A,9B and9C, examples of wake commands are depicted between an information handling system and plural peripherals.FIG.9Adepicts a one-to-one wake scenario where one device that detects a wake event transmits a wake command to another device, such as an information handling system10waking a mouse32at power up or a mouse waking an information handling system when movement is detected.FIG.9Bdepicts a one-to-many wake scenario where an information handling system10wakes keyboard28and mouse32, such as a broadcast wake command transmitted at power up of information handling system10.FIG.9Cdepicts a one-to-one-to-many scenario where a mouse32issues a wake command to information handling system10and then information handling system10wakes a group of devices associated with it, such as a keyboard28and mouse32. The trigger to wake ofFIG.9Cmay extend to situations where an area around of an information handling system is transitioned to wake or where a wake command at one device triggers a wake from that device to other devices as a relay, essentially hopping between associated devices and groups of devices. Referring now toFIG.10, a flow diagram depicts a process for distribution of wake commands between plural devices. The process starts at step244with a determination that a wake is initiated by a peripheral. If so the process continues to step246, if not to step248. At steps246and248a determination is made of whether a peer device associated with wake is a single device. If yes, the process continues to steps250and262where a determination is made of whether the target of the wake command is the peer device. If so, the process continues to step252and264to perform a one-to-one wake command to the peer device. If not, the process continues to step254and266to perform a relay of one-to-one-to-one to wake the target devices, such as mouse to an information handling system to a target keyboard. If at steps246and248the peer device is not a single device, the process continues to steps256and268to determine if the target device is the peer. If so, a one-to-one wake is commanded at steps258and270. If not, a one-to-one-to an area is commanded at step260and272. In various embodiments, wake-up secondary radios may be pre-programmed for desired wake scenarios that coordinate a desktop operational space, such as managed power states at plural information handling systems, input devices, displays, speakers, printers, etc. . . . Referring now toFIGS.11A and11B, examples of broadcast packets associated with a location peripheral device are depicted. A location peripheral device establishes radio communication with other devices so that the position of the other devices helps to locate the location peripheral device. Minimal battery consumption is an important concern for such location peripheral devices so that minimal receive and transmit windows are a consideration. Including a secondary radio in a location peripheral device provides an advantage of reduced power consumption and also allows the location device to interact with other peripheral devices, such as through a relay to host devices.FIG.11Adepicts an example of a location peripheral device transmission packet that had a recent connection, such as within the past 24 hours. In the example embodiment, the location peripheral transmits a packet every second so that over an extended period of time another peripheral will overlap with the transmission to locate the location peripheral device.FIG.11Bdepicts an example of location peripheral device packet broadcasts after a failure to connect for a defined intermediate time, such as 24 hours to a week. The location beacon transmission time is decreased to 500 msec. In one example embodiment, the location packet after a recent connection may simply include the device identifier, such as the BLE MAC address while the location packet after an intermediate time since the last contact may include a time stamp. Including the time stamp allows peripheral devices that detect the location packet to store the device ID and time stamp so that the peripheral devices may relay the contact information to an information handling system when next in use. In another example a location packet may be transmitted differently where a last contact occurred an extended time ago, such as greater than a week. In the example embodiment, the location packet is sent every five minutes with the device identifier and a time stamp. In various embodiments, the location peripheral device may rely on only the secondary radio to transmit location or may include a primary radio and processing resource that cooperate at connections to adapt the configuration of the location beacons. Referring now toFIG.12, a flow diagram depicts a process for a time based location packet transmission. The process starts at step274and continues to step276to determine if a BLE connection exists with the primary radio. If yes, the process ends at step296where the update for the position and communication to the network location is performed through the BLE interface. If no BLE connection exists at step276, the process continues to step278to determine if the last BLE connection was within a short defined time period, such as less than 24 hours ago. If so, the process continues to step280to define a location packet for transmission of the short time period and to step282at which the packet is transmitted. Successful interactions by the secondary radio can result in establishment of a BLE interface to update a network location, such as a cloud storage location. In one example embodiment, an accelerometer in the location peripheral device may be used to track changes in position indicated by accelerations, so that the location beacon timing may be adjusted after reporting a position to a cloud location since the location will not change without detection of an acceleration. From step282the process repeats to send the location beacon until the intermediate time period is detected at step278and the process continues to step284to apply the intermediate time period transmission pattern. At step284a determination is made of whether the last interface by the primary radio, such as with BLE, was greater than 24 hours and less than a week. If so the process continues to step286to generate a packet having the intermediate time period configuration and to step288to broadcast the intermediate time period packet. If a connection is established by the primary radio, the location information is updated to the network location and the process starts again at step274. If a connection is not made, the process returns to step284until the intermediate time period passes of greater than one week, and then continues to step290. At step290if the time from the last contact is greater than a week, the process continues to step292to generate a location beacon associated with an extended time since reporting a position. At step294the extended time location beacon is transmitted. The process continues from step290until a BLE connection is established and then returns to the start at step274. Referring now toFIG.13, a flow diagram depicts a network location packet transmission configuration. The process starts at step298and at step300determines if the device has reported location within the short term period, such as the last 24 hours. If not, the process stops at step308. If the device location was reported in the last 24 hours, the process continues to step302to determine if the device location has changed in the last 24 hours. If the position has changed, the process returns to step298. If at step302the position was reported in less than 24 hours and has not changed for 24 hours, the process continues to step304to determine if the location peripheral is in a known location, such as a home or office. If not, the process returns to step298. If the location peripheral device is in a known location, the process continues to step306for the host to send to the location peripheral device a command that sets the location beacon transmission frequency to the extended time transmission profile. The more extended times between location beacons reduces battery charge consumption while the location peripheral device is in a location where it is less likely to become lost. The process then ends at step308. Although the present invention has been described in detail, it should be understood that various changes, substitutions and alterations can be made hereto without departing from the spirit and scope of the invention as defined by the appended claims. | 40,074 |
11943713 | DETAILED DESCRIPTION For simplicity and illustrative purposes, the present invention is described by referring mainly to an exemplary embodiment thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be readily apparent to one of ordinary skill in the art that the present invention may be practised without limitation to these specific details. In this description, well known methods and structures have not been described in detail so as not to unnecessarily obscure the present invention. FIG.1depicts functional blocks of a wireless device10according to one embodiment. The wireless device10includes a battery12(or power scavenging device), power management circuit14, and baseband processor16connected to memory18. When actively connected to a wireless network, the baseband processor16communicates with the network (e.g., a base station) via a transmitter20and primary receiver22. A duplexer24provides isolation between transmit and receive functions, in connecting them both to an antenna26(which may be internal or external, as indicated by the dashed lines). In TDD implementations, the duplexer24may comprise a switch. Of course, the wireless device10may include other functions not depicted inFIG.1, such as sensors, cameras, monitors, actuators, control circuits, other communication interfaces, a user interface, and the like, depending on the specific purpose of the wireless device10. As indicated by dashed arrows, the power management circuit14controls the provision of power (and/or clock signals) to other circuits and functions of the wireless device10. In particular, the power management circuit14places circuits in a “sleep,” or inactive mode, when the respective functionality is not being currently utilized, to conserve power. As discussed above, the power management circuit14may efficiently and accurately control the provision of power to circuits such as the baseband processor16and transmitter20, in response to current computational or outgoing communication demands. However, the wireless device10has no knowledge when incoming communications, such as paging messages, may be directed to it from the network, and continuously monitoring the network consumes large amounts of power. While the power management circuit14can reduce the power consumption of the primary receiver22by operating it in a duty cycle, this results in wasted air interface resources, increased interference, and possible congestion as the network is required to repeatedly transmit paging messages until one coincides with a primary receiver22“on” time. Accordingly, the wireless device includes a wakeup receiver28. The wakeup receiver28is a low-power, limited-functionality circuit, the purpose of which is to monitor the network for an indication of pending transmissions directed to the wireless device10when operation of the primary receiver22is suspended for power savings. This indication may be in the form of a wakeup signal transmitted by the network and identifying the wireless device10(or a group, of which the wireless device10is a member). Upon detecting such a signal, the wakeup receiver alerts the power management circuit14, which in turn activates the primary receiver22, which e.g., monitors the network for paging messages, performs a random access procedure, or otherwise engages in conventional (power-consuming) communication protocols with the network. When the wireless device10completes a task, or otherwise believes no further network transmissions directed to it are likely for a time, the power management circuit14again suspends operation of the primary receiver22, and activates the wakeup receiver28. FIG.2depicts the architecture of a wakeup receiver28according to one embodiment. The wakeup receiver28is a limited-function, low-power receiver intended to be activated by a wireless device10when a primary, full-function receiver22is in “sleep” mode for power conservation. The wakeup receiver28listens for a wakeup signal transmitted by the network (e.g., by a base station or eNB). If the decoded wakeup signal includes an ID associated with the wireless device10, the wakeup receiver28outputs a signal to the wireless device10—such as to a power management system14on the wireless device10—to activate the primary receiver22. The primary receiver22may then receive broadcasts such as System Information, and receive for paging messages. In this manner, the wireless device10may remain dormant, in a very low power consumption mode, for extended periods. However, during such dormant times, the wireless device10, via the wakeup receiver28, continues to monitor network transmissions, and hence the network need not repeat paging messages directed to the wireless device10when it has downlink data to transfer. The wakeup receiver28comprises a front-end filter32, mixer(s)34, amplifier(s)36, narrowband filter(s)38, Analog to Digital (ADC) converter(s)40, digital processing and control logic42, and a Local Oscillator (LO) signal source44. The LO source may be a Digitally Controlled Oscillator (DCO). The dual paths depicted inFIG.1reflect In-phase (I) and Quadrature (Q) mixing, although other mixers34may be employed. Operation of the wakeup receiver28is straightforward to those of skill in the art. A signal received at an antenna26(FIG.1) and passed through a duplexer24for isolation from transmitter circuits20is initially filtered by front-end filter32. Mixers34frequency downconvert received signals by mixing them with LO signals generated by the DCO44, under the control of control logic42. The mixer34may be a passive structure, to minimize power consumption and flicker noise. The mixer34precedes the amplifiers36, the narrowband filters38, and ADCs40—hence, the wakeup receiver28employs a “mixer-first” architecture. ADC circuits40digitize the filtered baseband signal, and digital processing circuits42further process the signal, such as demodulating and decoding the transmitted data. If the data indicates that the wakeup signal was targeted to the wireless device10(for example, if it matches a unique identifier of the wireless device10, such as IMSI, C-RNTI, or the like), the primary receiver22is activated to receive further messages from the network. The DCO44is the major power consumer of the wakeup receiver28. To minimize power consumption, no external frequency reference, such as a crystal oscillator, is used. Furthermore, phase locked loop designs are avoided, as they are heavy consumers of power. In one embodiment, a ring oscillator is used in the DCO44for ultra-low power consumption. Due to these power-saving design considerations, the DCO44is neither highly accurate nor particularly stable. That is, the output frequency of the DCO44LO signal will drift over time. Uncertainty in frequency propagates to the mixer circuits34. Because of the uncertainty in the frequency downconversion performed by the mixers34, the filters38must remain relatively wideband to avoid filtering out the baseband signal along with adjacent interference. That is, a more accurate LO signal from the DCO44would allow for more narrowband filtering by the filters38, dramatically improving the signal to noise ratio (SNR) by eliminating nearby interference. According to embodiments of the present invention, the network assists wakeup receivers28in maintaining more accurate frequency references by including information related to the transmission frequency in wakeup signals that are transmitted to wireless devices10. The transmission frequency information may take numerous forms, as detailed herein. The transmitted wakeup signals may identify particular wireless devices10to which the network has data to transmit. Alternatively, even if the network has no occasion to “wake up” a particular wireless device10, it nonetheless regularly transmits wakeup signals that include information related to their transmission frequency. All such wakeup signals may be monitored by wakeup receivers28in wireless devices10, and used to calibrate the wakeup receivers'28local oscillator frequency generators. That is, even if a received and decoded wakeup signal does not identify a wireless device10, that wireless device10may still improve its wakeup receiver28sensitivity and frequency accuracy by using the frequency information included in the received wakeup signal to calibrate or otherwise adjust its DCO44, countering the effects of frequency drift. By transmitting wakeup signals according to a known time/frequency pattern, the network assists all low-power wireless devices10in a cell, which have wakeup receivers28as disclosed herein, to maintain accurate receiver clocks. Initially, the wakeup receiver28must acquire a wakeup signal. In embodiments in which the network transmits wakeup signals according to a known pattern, the wakeup receiver28is tuned to, or near, the mid-frequency of the DCO44, and listens for the duration of a wakeup signal transmission pattern period. If no wakeup signal is detected, the DCO44is tuned to a different frequency, and the process repeats. Once a wakeup signal is detected, in embodiments in which the network uses the same time interval between messages, the start time of the next wakeup message is known. Otherwise, the wakeup receiver28must tune to an expected frequency and begin listening at the earliest time that a wakeup message could be transmitted. In some embodiments, the network transmits wakeup messages in a known frequency hopping pattern, to help avoid interference. In these embodiments, the network may embed next-hop frequency information in each transmitted wakeup signal. In one embodiment, each wakeup signal may include the frequency of the next wakeup signal. In another embodiment, in which the frequency hopping pattern is triangular with known spacing, it is sufficient for each wakeup message to indicate whether the next wakeup message will be at a higher or lower frequency. In this embodiment, a single bit is sufficient to convey the information, and it can be represented by a relatively long sequence, to minimize the risk for errors.FIG.3depicts a simple triangular hopping pattern, in which each wakeup message need only carry an up/down indicator. In other embodiments, more complicated schemes use more bits, for example to facilitate skipping of frequencies with strong interference. In another embodiment, a plurality of wakeup signals are transmitted simultaneously on different frequencies and each signal includes information identifying its transmission frequency. With a high likelihood, a wakeup receiver28will be able to receive one of the signals, whereas the other signals will be attenuated by the narrowband filters38. Upon demodulating and decoding the data in the wakeup signal, the wakeup receiver28will know the signal's transmission frequency, and hence its own local oscillator frequency, and can use this information to calibrate its DCO44. This approach is particularly useful when a wakeup receiver28is initially switched on (e.g., when a primary receiver22has been placed in a sleep mode for power conservation). In the wakeup receiver28, wakeup signals are received by a homodyne receiver where the local oscillator is free running. It is thus not locked in any PLL circuit, but instead it is calibrated at occasional or regular time intervals to limit errors due to frequency drift. Due to this, substantial frequency errors must be tolerated, and it must also be possible to measure these errors. Because of this frequency uncertainty, amplitude modulation is more suitable for the wakeup signals than phase modulation. The absolute frequency of the down-converted signal is then of less concern in the detection. In one embodiment (for example, that depicted inFIG.1), the amplitude detection is performed in the digital domain by summation of the squared in-phase (I) and quadrature phase (Q) components. While in principle this is independent of intermediate frequency (IF), in real-world receivers28, close to DC there are DC-offsets, 1/f noise, and even order intermodulation distortion, all of which should preferably by filtered out. It is therefore an advantage if a portion around DC can be filtered out, regardless of the actual IF frequency of the received signal. This is in contrast to regular homodyne receivers where the LO frequency is accurately locked. In that case, the signal can be tailored to have little information near its center frequency, which is then down-converted to DC. In contrast, in the wakeup receiver28, the loss of information can occur anywhere in the signal spectrum, and is not necessarily confined to the center. Wakeup signals are thus advantageously constructed so that a loss can be handled anywhere in the signal bandwidth without loss of functionality. In some embodiments, this is realized by using several carrier frequencies, each amplitude modulated using On-Off Keying (OOK). In particular, the transmitted signal is generated using an inverse fast Fourier transform (IFFT) block, where the different carrier frequencies are generated by using a set of sub-carriers. Specifically, the wakeup signal is generated using an ordinary OFDM transmitter. Due to the ND conversion and digital signal processing in the wakeup receiver28, each carrier can be filtered out in the digital domain before amplitude detection is performed. In one embodiment a bank of digital filters with different center frequencies is used. The filter outputs are amplitude demodulated and correlated for the different PN sequences of the wakeup message. In embodiments where the signal is generated using an IFFT, the filter-bank is effectively implemented using an FFT, similar to an ordinary OFDM receiver. The frequency offset is determined by which part of the message is found at which filter. Carriers at DC are not used, and their energy is lost. However, since the other carriers are uncorrupted by DC they are used instead, and their combined energy is used to detect the message. The signal situation after frequency down-conversion is illustrated inFIGS.4A(no carriers at DC) and4B (DC carrier not used). The pseudo noise (PN) sequence is selected in different ways, in different embodiments. In one embodiment, each wakeup signal on a different carrier contains a different PN sequence. In another embodiment, the same PN sequence is used in all wakeup signals. In the latter case, a digital mixer in the digital processing and control unit42may further downconvert all of the carriers to the same frequency, then perform amplitude detection and correlation together. This is depicted inFIG.5A, where the wakeup signals transmitted on different carrier frequencies are mixed to the same, non-DC frequency and combined, resulting in improved signal strength and SNR. Alternatively, since the signals are in the digital domain, they can be mixed close to DC, as depicted inFIG.5B. Because it is not important for the detection at exactly what frequency the carriers end up, only that they end up at the same, the digital mixers must operate with a frequency equal to the difference frequency between carriers. As this frequency is low compared to the RF frequency, the digital frequency accuracy is relaxed. However, even though this difference frequency is low, due to uncertainty of time of arrival of the message, the local digital carrier phases will differ when receiving the signal. For constructive summation, the phase offsets must then be found and compensated for, e.g., with 90 degrees resolution, by switching the quadrature signals. In one embodiment, this is accomplished by using multiple digital mixers and correlators, so that mixing phase is always synchronized with correlation. Each set of mixers is then started in phase, the mixer outputs first added, then multiplied by +/−1 according to the PN sequence, after which the result is accumulated. Several such units are operated in parallel with different starting times to find the message. To ascertain the LO frequency error in this embodiment, the outputs from different sets of filters are used in the signal detection, and the magnitude of the signal after the correlators is then compared to find the frequency location. In another embodiment, the carriers are demodulated individually; this is also done when different codes are used for different carriers. Those of skill in the art will recognize a trade-off between simplicity and sensitivity. FIG.6depicts a method100of operating a low-power wakeup receiver28in a wireless device10operative in a wireless communication network, in accordance with particular embodiments. Operation of a primary receiver circuit22is suspended to conserve power (block102). A low-power wakeup receiver circuit is operated (block104). One or more wakeup signals, transmitted by the network, are received (block106). The one or more wakeup signals are down-converted using an uncalibrated local oscillator signal (block108). The down-converted one or more wakeup signals are demodulated and decoded (block110). Frequency related information is extracted from the decoded one or more wakeup signals (block112). The extracted frequency related information is used to correct the local oscillator signal frequency (block114). The frequency-corrected local oscillator signal is used to down-convert subsequent wakeup signals transmitted by the network (block116). Narrowband filtering is performed on the down-converted, subsequent wakeup signals (block118). The filtered, down-converted, subsequent wakeup signals are demodulated and decoded (block120). FIG.7depicts a method200of operating a base station serving one or more low-power wireless devices10in a wireless communication network, in accordance with other particular embodiments. One or more wakeup signals are generated (block202). Each wakeup signal includes information related to a transmission frequency. The wakeup signals are transmitted (block204). Each wakeup signal is transmitted on a corresponding frequency carrier. Apparatuses described herein may perform the methods100,200described herein, and any other processing, by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein. As described above,FIG.1for example illustrates a wireless device10as implemented in accordance with one or more embodiments. In general, a wireless device10is any type of device capable of communicating with a network node and/or base station using radio signals. A wireless device10may therefore refer to a machine-to-machine (M2M) device, a machine-type communications (MTC) device, a Narrowband Internet of Things (NB IoT) device, etc. The wireless device10may also be a User Equipment (UE); however it should be noted that the UE does not necessarily have a “user” in the sense of an individual person owning and/or operating the device. A wireless device10may also be referred to as a radio device, a radio communication device, a wireless communication device, a wireless terminal, or simply a terminal—unless the context indicates otherwise, the use of any of these terms is intended to include device-to-device UEs or devices, machine-type devices, or devices capable of machine-to-machine communication, sensors equipped with a radio network device, wireless-enabled tablet computers, mobile terminals, smart phones, laptop-embedded equipped (LEE), laptop-mounted equipment (LME), USB dongles, wireless customer-premises equipment (CPE), etc. In the discussion herein, the terms machine-to-machine (M2M) device, machine-type communication (MTC) device, wireless sensor, and sensor may also be used. It should be understood that these devices may be UEs, but may be configured to transmit and/or receive data without direct human interaction. A wireless device10as described herein may be, or may be comprised in, a machine or device that performs monitoring or measurements, and transmits the results of such monitoring measurements to another device or a network node. Particular examples of such machines are power meters, industrial machinery, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a wireless device10as described herein may be comprised in a vehicle and may perform monitoring and/or reporting of the vehicle's operational status or other functions associated with the vehicle. FIG.8illustrates a schematic block diagram of a wireless device50operative in a wireless communication network according to still other embodiments. As shown, the wireless device50implements various functional means, units, or modules, e.g., via the baseband processor16, power management circuit14, primary receiver22, or wakeup receiver28inFIG.1and/or via software code. These functional means, units, or modules, e.g., for implementing method100herein, include for instance: primary receiver suspending unit51, wakeup receiver operating unit52, wakeup signal receiving unit53, wakeup signal down-converting unit54, wakeup signal demodulating and decoding unit55, information extracting unit56, LO signal correcting unit57, and narrowband filtering unit58. The primary receiver suspending unit51is configured to suspend operation of a primary receiver circuit to conserve power. The wakeup receiver operating unit52is configured to operate a low-power wakeup receiver circuit. The wakeup signal receiving unit53is configured to receive one or more wakeup signals transmitted by the network. The wakeup signal down-converting unit54is configured to down-convert the one or more wakeup signals using an uncalibrated local oscillator signal. The wakeup signal demodulating and decoding unit55is configured to demodulate and decode the down-converted one or more wakeup signals. The information extracting unit56is configured to extract frequency related information from the decoded one or more wakeup signals. The LO signal correcting unit57is configured to use the extracted frequency related information to correct the local oscillator signal frequency. The wakeup signal down-converting unit54is further configured to use the frequency-corrected local oscillator signal to down-convert subsequent wakeup signals transmitted by the network. The narrowband filtering unit58is configured to performing narrowband filtering on the down-converted, subsequent wakeup signals. The wakeup signal demodulating and decoding unit55is further configured to demodulate and decode the filtered, down-converted, subsequent wakeup signals. FIG.9illustrates a network node70as implemented in accordance with one or more embodiments. In particular, the network node70may function as a base station in a wireless communication network. As those of skill in the art are aware, a base station is a network node70providing wireless communication services to one or more wireless devices10in a geographic region (known as a cell or sector). The base station10in LTE is called an e-NodeB or eNB; in NR it is known as gNB. However the present invention is not limited to LTE or NR. As shown, the network node70includes processing circuitry72and communication circuitry76. The communication circuitry76is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The communication circuitry76is connected to one or more antennas78, to effect wireless communication across an air interface to one or more wireless devices10. As those of skill in the art are aware, and as indicated by the continuation lines in the antenna feed line ofFIG.9, the antenna(s)78may be physically located separately from the network node70, such as mounted on a tower, building, or the like. Although the memory74is depicted as being internal to the processing circuitry72, those of skill in the art understand that the same or additional memory74may be separate from the processing circuitry72. Those of skill in the art additionally understand that virtualization techniques allow some functions nominally executed by the processing circuitry74to actually be executed by other hardware, perhaps remotely located (e.g., in the so-called “cloud”). The processing circuitry72is configured to perform processing described above, such as by executing instructions stored in memory74. The processing circuitry72in this regard may implement certain functional means, units, or modules. FIG.10illustrates a schematic block diagram of a network node80in a wireless network according to still other embodiments. As shown, the network node80implements various functional means, units, or modules, e.g., via the processing circuitry72inFIG.9and/or via software code. These functional means, units, or modules, e.g., for implementing the method200herein, include for instance: wakeup signal generating unit82and wakeup signal transmitting unit84. The wakeup signal generating unit82is configured to generate one or more wakeup signals, each including information related to a transmission frequency. The wakeup signal transmitting unit84is configured to transmit the wakeup signals, each wakeup signal being transmitted on a corresponding carrier. Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs. A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above. Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium. In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above. Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium. Embodiments of the present invention present numerous advantages over the prior art. By frequency correcting a low-power, free-running DCO44using frequency information transmitted by the network in wakeup signals, a narrowband but ultra-low power wakeup receiver10is realized. It achieves high performance in terms of sensitivity and immunity to interference. The wakeup receiver28is quickly calibrated at startup, and remains calibrated despite drift in circuit parameters. In some embodiments, performance is further improved by using multiple carriers to achieve immunity to loss of parts of the signal spectrum, such as close to the LO frequency in a homodyne receiver. In other embodiments, immunity to interference is further improved by use of a frequency hopping mechanism, calibrating the wakeup receivers28for accurate operation over a full frequency band. The present invention may, of course, be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the invention. The present embodiments are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein. | 28,962 |
11943714 | DETAILED DESCRIPTION In the following, downlink (DL) refers to communication from a base station (BS) to a user equipment (UE), and uplink (UL) refers to communication from the UE to the BS. In the case of DL, a transmitter may be a part of the BS, and a receiver may be a part of the UE. In the case of UL, a transmitter may be a part of the UE, and a receiver may be a part of the BS. The technology described herein is applicable to various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. The CDMA may be implemented as radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. The TDMA may be implemented as radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). The OFDMA may be implemented as radio technology such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), etc. The UTRA is a part of a universal mobile telecommunication system (UMTS). The 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of an evolved UMTS (E-UMTS) using the E-UTRA. LTE-advance (LTE-A) or LTE-A pro is an evolved version of the 3GPP LTE. 3GPP new radio or new radio access technology (3GPP NR) is an evolved version of the 3GPP LTE, LTE-A, or LTE-A pro. Although the present disclosure is described based on 3GPP communication systems (e.g., LTE-A, NR, etc.) for clarity of description, the spirit of the present disclosure is not limited thereto. The LTE refers to the technology beyond 3GPP technical specification (TS) 36.xxx Release 8. In particular, the LTE technology beyond 3GPP TS 36.xxx Release 10 is referred to as the LTE-A, and the LTE technology beyond 3GPP TS 36.xxx Release 13 is referred to as the LTE-A pro. The 3GPP NR refers to the technology beyond 3GPP TS 38.xxx Release 15. The LTE/NR may be called ‘3GPP system’. Herein, “xxx” refers to a standard specification number. The LTE/NR may be commonly referred to as ‘3GPP system’. Details of the background, terminology, abbreviations, etc. used herein may be found in documents published before the present disclosure. For example, the following documents may be referenced. 3GPP LTE36.211: Physical channels and modulation36.212: Multiplexing and channel coding36.213: Physical layer procedures36.300: Overall description36.304: User Equipment (UE) procedures in idle mode36.331: Radio Resource Control (RRC) 3GPP NR38.211: Physical channels and modulation38.212: Multiplexing and channel coding38.213: Physical layer procedures for control38.214: Physical layer procedures for data38.300: NR and NG-RAN Overall Description38.304: User Equipment (UE) procedures in Idle mode and RRC Inactive state36.331: Radio Resource Control (RRC) protocol specification A. System Architecture FIG.1illustrates an example of the 3GPP LTE system architecture. A wireless communication system may be referred to as an evolved-UMTS terrestrial radio access network (E-UTRAN) or a long term evolution (LTE)/LTE-A system. Referring toFIG.1, the E-UTRAN includes at least one BS20that provides control and user planes to a UE10. The UE10may be fixed or mobile. The UE10may be referred to as another terminology such as ‘mobile station (MS)’, ‘user terminal (UT)’, ‘subscriber station (SS)’, ‘mobile terminal (MT)’, or ‘wireless device’. In general, the BS20may be a fixed station that communicates with the UE10. The BS20may be referred to as another terminology such as ‘evolved Node-B (eNB)’, ‘general Node-B (gNB)’, ‘base transceiver system (BTS)’, or ‘access point (AP)’. The BSs20may be interconnected through an X2 interface. The BS20may be connected to an evolved packet core (EPC) through an S1 interface. More particularly, the BS20may be connected to a mobility management entity (MME) through S1-MME and to a serving gateway (S-GW) through S1-U. The EPC includes the MME, the S-GW, and a packet data network-gateway (P-GW). Radio interface protocol layers between the UE and network may be classified into Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3) based on three lower layers of the open system interconnection (OSI) model well known in communication systems. A physical (PHY) layer, which belongs to L1, provides an information transfer service over a physical channel. A radio resource control (RRC) layer, which belongs to L3, controls radio resources between the UE and network. To this end, the BS and UE may exchange an RRC message through the RRC layer. FIG.2illustrates an example of the 3GPP NR system architecture. Referring toFIG.2, a NG-RAN includes gNBs, each of which provides a NG-RA user plane (e.g., new AS sublayer/PDCP/RLC/MAC/PHY) and a control plane (RRC) protocol terminal to a UE. The gNBs are interconnected through an Xn interface. The gNB is connected to an NGC through a NG interface. More particularly, the gNB is connected to an access and mobility management function through an N2 interface and to a user plane function (UPF) through an N3 interface. B. Frame Structure Hereinafter, an LTE frame structure will be described. In the LTE standards, the sizes of various fields in the time domain are expressed in a time unit (Ts=1/(15000×2048) seconds) unless specified otherwise. DL and UL transmissions are organized in radio frames, each of which has a duration of 10 ms (Tf=307200×Ts=10 ms). Two radio frame structures are supported.Type 1 is applicable to frequency division duplex (FDD).Type 2 is applicable to time division duplex (TDD). (1) Frame Structure Type 1 Frame structure type 1 is applicable to both full-duplex FDD and half-duplex FDD. Each radio frame has a duration of Tf=307200·Ts=10 ms and is composed of 20 slots, each of which has a length of Tslot=15360·Ts=0.5 ms. The 20 slots are indexed from 0 to 19. A subframe is composed of two consecutive slots. That is, subframe i is composed of slot 2i and slot (2i+1). In the FDD, 10 subframes may be used for DL transmission, and 10 subframes may be available for UL transmissions at every interval of 10 ms. DL and UL transmissions are separated in the frequency domain. However, the UE may not perform transmission and reception simultaneously in the half-duplex FDD system. FIG.3illustrates a radio frame structure of frame structure type 1. Referring toFIG.3, the radio frame includes 10 subframes. Each subframe includes two slots in the time domain. The time to transmit one subframe is defined as a transmission time interval (TTI). For example, one subframe may have a length of 1 ms, and one slot may have a length of 0.5 ms. One slot may include a plurality of orthogonal frequency division multiplexing (OFDM) symbols in the time domain. Since the 3GPP LTE system uses OFDMA in DL, the OFDM symbol may represent one symbol period. The OFDM symbol may be referred to as an SC-FDMA symbol or a symbol period. A resource block (RB) is a resource allocation unit and includes a plurality of consecutive subcarriers in one slot. This radio frame structure is merely exemplary. Therefore, the number of subframes in a radio frame, the number of slots in a subframe, or the number of OFDM symbols in a slot may be changed in various ways. (2) Frame Structure Type 2 Frame structure type 2 is applicable to TDD. Each radio frame has a length of Tf=307200×Ts=10 ms and includes two half-frames, each of which has a length of 15360·Ts=0.5 ms. Each half-frame includes five subframes, each of which has a length of 30720·Ts=1 ms. Supported UL-DL configurations are defined in the standards. In each subframe of a radio frame, “D” denotes a subframe reserved for DL transmission, “U” denotes a subframe reserved for UL transmission, and “S” denotes a special subframe including the following three fields: downlink pilot time slot (DwPTS), guard period (GP), and uplink pilot time slot (UpPTS). The DwPTS may be referred to as a DL period, and the UpPTS may be referred to as a UL period. The lengths of the DwPTS and UpPTS depend on the total length of the DwPTS, GP, and UpPTS, which is equal to 30720·Ts=1 ms Subframe i is composed of two slots, slot 2i and slot (2i+1), each of which has a length of Tslot=15360·Ts=0.5 ms. FIG.4illustrates a radio frame structure of frame structure type 2. FIG.4shows that a UL-DL configuration supports DL-to-UL switch-point periodicities of 5 ms and 10 ms. In the case of the 5-ms DL-to-UL switch-point periodicity, the special subframe exists across two half-frames. In the case of the 10-ms DL-to-UL switch-point periodicity, the special subframe exists only in the first half-frame. The DwPTS and subframe 0 and 5 are always reserved for DL transmission, and the UpPTS and a subframe next to the special subframe are always reserved for UL transmission. Next, a description will be given of a frame structure of NR. FIG.5illustrates an example of a frame structure in NR. The NR system may support various numerologies. The numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacing may be derived by scaling basic subcarrier spacing by an integer N (or μ). In addition, even though very low subcarrier spacing is assumed not to be used at a very high subcarrier frequency, a numerology to be used may be selected independently from frequency bands. In the NR system, various frame structures may be supported based on multiple numerologies. Hereinafter, an OFDM numerology and a frame structure, which may be considered in the NR system, will be described. Table 1 shows multiple OFDM numerologies supported in the NR system. TABLE 1μΔf = 2μ· 15 [kHz]Cyclic prefix015Normal130Normal260Normal,Extended3120Norma14240Normal Regarding a frame structure in the NR system, the sizes of various fields in the time domain are expressed in multiples of a time unit, Ts=1/(Δfmax·Nf). In this case, Δfmax=480·103and Nf=4096. Downlink and uplink transmissions are configured in a radio frame having a duration of Tf=(ΔfmaxNf/100)·Ts=10 ms. The radio frame is composed of 10 subframes, each having a duration of Tsf=(ΔfmaxNf/1000)·Ts=1 ms. In this case, there may be a set of uplink frames and a set of downlink frames. Transmission of an uplink frame with frame number i from a UE needs to be performed earlier by TTA=NTATsthan the start of a corresponding downlink frame of the UE. Regarding the numerology μ, slots are numbered in a subframe in the following ascending order: nsμ∈{0, . . . , Nsubframeslots,μ−1} and numbered in a frame in the following ascending order: ns,fμ∈{0, . . . , Nframeslots,μ−1}. One slot is composed of Nsymbμconsecutive OFDM symbols, and Nsymbμis determined by the current numerology and slot configuration. The starts of nsμslots in a subframe are temporally aligned with those of nsμNsymbμOFDM symbols in the same subframe. Some UEs may not perform transmission and reception at the same time, and this means that some OFDM symbols in a downlink slot or an uplink slot are unavailable. Table 2 shows the number of OFDM symbols per slot (Nsymbslot), the number of slots per radio frame (Nslotframe,μ), and the number of slots per subframe (Nslotsubframe,μ) in the case of a normal CP, and Table 3 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the case of an extended CP. TABLE 2μNsymbslotNslotframe, μNslotsubframe, μ01410111420221440431480841416016 TABLE 3μNsymbslotNslotframe, μNslotsubframe, μ212404 FIG.5shows an example of μ=2, i.e., 60 kHz subcarrier spacing (SCS). Referring to Table 2, one subframe may include four slots.FIG.5shows slots in a subframe (subframe={1, 2, 4}). In this case, the number of slots included in the subframe may be defined as shown in Table 2 above. In addition, a mini-slot may be composed of 2, 4, or 7 symbols. Alternatively, the number of symbols included in the mini-slot may vary. C. Physical Resource FIG.6illustrates a resource grid for one DL slot. Referring toFIG.6, a downlink slot includes a plurality of OFDM symbols in the time domain. One downlink slot includes 7 OFDM symbols in the time domain, and a resource block (RB) for example includes 12 subcarriers in the frequency domain. However, the present disclosure is not limited thereto. Each element of the resource grid is referred to as a resource element (RE). One RB includes 12×7 REs. The number of RBs in the DL slot depends on a downlink transmission bandwidth. An uplink slot may have the same structure as the downlink slot. FIG.7illustrates the structure of a downlink subframe. Referring toFIG.7, up to three OFDM symbols at the start of the first slot in a downlink subframe are used as a control region to which a control channel is allocated. The remaining OFDM symbols are used as a data region to which a physical downlink shared channel (PDSCH) is allocated. Downlink control channels used in the 3GPP LTE system include a physical control format indicator channel (PCFICH), a physical downlink control channel (PDCCH), a physical hybrid ARQ indicator channel (PHICH), etc. The PCFICH is transmitted in the first OFDM symbol in a subframe and carries information for the number of OFDM symbols used for transmitting a control channel. The PHICH carries a hybrid automatic repeat request (HARQ) acknowledgement/negative-acknowledgement or not-acknowledgement (ACK/NACK) signal in response to uplink transmission. Control information transmitted on the PDCCH is referred to as downlink control information (DCI). The DCI contains uplink or downlink scheduling information or an uplink transmission (Tx) power control command for a random UE group. The PDCCH carries information for resource allocation for a downlink shared channel (DL-SCH), information for resource allocation for a uplink shared channel, paging information for a paging channel (PCH), and a DL-SCH voice over Internet protocol (VoIP) corresponding to resource allocation for a higher layer control message such as a random access response transmitted on the PDSCH, a set of Tx power control commands for individual UEs in a random UE group, a Tx power control command, activation of the Tx power control command, etc. Multiple PDCCHs may be transmitted in the control region, and the UE may monitor the multiple PDCCHs. The PDCCH may be transmitted on one control channel element (CCE) or aggregation of multiple consecutive CCEs. The CCE is a logical allocation unit used to provide the PDCCH with a coding rate based on the state of a radio channel. The CCE corresponds to a plurality of resource element groups (REGs). A PDCCH format and the number of available PDCCH bits are determined based on a relationship between the number of CCEs and the coding rate provided by the CCE. The base station determines the PDCCH format depending on DCI to be transmitted to the UE and adds a cyclic redundancy check (CRC) to control information. The CRC is masked with a unique identifier (e.g., radio network temporary identifier (RNTI)) according to the owner or usage of the PDCCH. If the PDCCH is for a specific UE, the CRC may be masked with a unique UE identifier (e.g., cell-RNTI). If the PDCCH is for a paging message, the CRC may be masked with a paging indication identifier (e.g., paging-RNTI (P-RNTI)). If the PDCCH is for system information (more specifically, for a system information block (SIB)), the CRC may be masked with a system information identifier and a system information RNTI (SI-RNTI). Further, the CRC may be masked with a random access-RNTI (RA-RNTI) to indicate a random access response in response to transmission of a random access preamble of the UE. FIG.8illustrates the structure of an uplink subframe. Referring toFIG.8, an uplink subframe may be divided into a control region and a data region in the frequency domain. A physical uplink control channel (PUCCH) for carrying uplink control information may be allocated to the control region, and a physical uplink shared channel (PUSCH) for carrying user data may be allocated to the data region. The UE may not transmit the PUCCH and the PUSCH at the same time to maintain single-carrier characteristics. The PUCCH for the UE is allocated to an RB pair in a subframe. The RBs included in the RB pair occupy different subcarriers in two slots. In other words, the RB pair allocated for the PUCCH may be frequency-hopped at a slot boundary. As physical resources in the NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. may be considered. Hereinafter, the above physical resources considered in the NR system will be described in detail. First, an antenna port may be defined such that a channel carrying a symbol on the antenna port is inferred from a channel carrying another symbol on the same antenna port. When the large-scale properties of a channel carrying a symbol on an antenna port are inferred from a channel carrying a symbol on another antenna port, the two antenna ports may be said to be in quasi co-located or quasi co-location (QC/QCL) relationship. The large-scale properties may include at least one of delay spread, Doppler spread, frequency shift, average received power, and received timing. FIG.9illustrates an example of a resource grid in NR. Referring to the resource grid ofFIG.9, there are NRBμNscRBsubcarriers in the frequency domain, and there are 14·2μ OFDM symbols in one subframe. However, the resource grid is merely exemplary and the present disclosure is not limited thereto. In the NR system, a transmitted signal is described by one or more resource grids, each including NRBμNscRBsubcarriers, and 2μNsymb(μ)OFDM symbols. In this case, NRBμ≤NRBmax,μ. NRBmax,μdenotes the maximum transmission bandwidth and may change not only between numerologies but also between uplink and downlink. As shown inFIG.9, one resource grid may be configured for each numerology μ and antenna port p. Each element of the resource grid for the numerology μ and antenna port p is referred to as a resource element, and it is uniquely identified by an index pair (k,l), where k is an index in the frequency domain (k=0, . . . , NRBμNscRB−1) andldenotes the location of a symbol in the subframe (l=0, . . . , 2μNsymb(μ)−1). The resource element (k,l) for the numerology p and antenna port p corresponds to a complex value ak,l(p,μ). When there is no risk of confusion or when a specific antenna port or numerology is not specified, the indexes p and μ may be dropped, and as a result, the complex value may be ak,l(p)or ak,l. In addition, a resource block (RB) is defined as NscRB=12 consecutive subcarriers in the frequency domain. Point A serves as a common reference point for resource block grids and may be obtained as follows.OffsetToPointA for primary cell (PCell) downlink represents a frequency offset between point A and the lowest subcarrier of the lowest resource block in an SS/PBCH block used by the UE for initial cell selection. OffsetToPointA is expressed in the unit of resource block on the assumption of 15 kHz SCS for frequency range 1 (FR1) and 60 kHz SCS for frequency range 2 (FR2).AbsoluteFrequencyPointA represents the frequency location of point A expressed as in absolute radio-frequency channel number (ARFCN). Common resource blocks are numbered from 0 upwards in the frequency domain for SCS configuration μ. The center of subcarrier 0 of common resource block 0 for the SCS configuration μ is equivalent to point A. The relation between a common RB number nCRBμin the frequency domain and a resource element (k,l) for the SCS configuration μ is determined as shown in Equation 1. nCRBμ=⌊kNscRB⌋Equation1 In Equation 1, k is defined relative to point A such that k=0 corresponds to a subcarrier centered on point A. Physical resource blocks are defined within a bandwidth part (BWP) and numbered from 0 to NBWP,isize−1, where i denotes the number of the BWP. The relationship between a physical resource block nPRBand a common resource block nCRBin BWP i is given by Equation 2. nCRB=nPRB+nBWP,istartEquation 2 In Equation 2, NBWP,istartis a common resource block where the BWP starts relative to common resource block 0. FIG.10illustrates an example of a physical resource block in NR D. Wireless Communication Devices FIG.11illustrates a block diagram of a wireless communication apparatus to which the methods proposed in the present disclosure are applicable. Referring toFIG.11, a wireless communication system includes a base station1110and multiple UEs1120located within coverage of the base station1110. The base station1110and the UE may be referred to as a transmitter and a receiver, respectively, and vice versa. The base station1110includes a processor1111, a memory1114, at least one transmission/reception (Tx/Rx) radio frequency (RF) module (or RF transceiver)1115, a Tx processor1112, an Rx processor1113, and an antenna1116. The UE1120includes a processor1121, a memory1124, at least one Tx/Rx RF module (or RF transceiver)1125, a Tx processor1122, an Rx processor1123, and an antenna1126. The processors are configured to implement the above-described functions, processes and/or methods. Specifically, the processor1111provides a higher layer packet from a core network for downlink (DL) transmission (communication from the base station to the UE). The processor implements the functionality of layer 2 (L2). In downlink (DL), the processor provides the UE1120with multiplexing between logical and transmission channels and radio resource allocation. That is, the processor is in charge of signaling to the UE. The Tx processor1112implements various signal processing functions of layer 1 (L1) (i.e., physical layers). The signal processing functions include facilitating the UE to perform forward error correction (FEC) and performing coding and interleaving. Coded and modulated symbols may be divided into parallel streams. Each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (RS) in the time and/or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to create a physical channel carrying a time domain OFDMA symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Each spatial stream may be provided to a different antenna1116through the Tx/Rx module (or transceiver)1115. Each Tx/Rx module may modulate an RF carrier with each spatial stream for transmission. At the UE, each Tx/Rx module (or transceiver)1125receives a signal through each antenna1126thereof. Each Tx/Rx module recovers information modulated on the RF carrier and provides the information to the RX processor1123. The Rx processor implements various signal processing functions of layer 1. The Rx processor may perform spatial processing on the information to recover any spatial streams toward the UE. If multiple spatial streams are destined for the UE, the multiple spatial streams may be combined by multiple Rx processors into a single OFDMA symbol stream. The RX processor converts the OFDMA symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). A frequency-domain signal includes a separate OFDMA symbol stream for each subcarrier of an OFDM signal. The symbols and the reference signal on each subcarrier are recovered and demodulated by determining the most probable signal constellation points transmitted by the base station. Such soft decisions may be based on channel estimation values. The soft decisions are decoded and deinterleaved to recover data and control signals originally transmitted by the base station over the physical channel. The corresponding data and control signals are provided to the processor1121. Uplink (UL) transmission (communication from the UE to the base station) is processed by the base station1110in a similar way to that described in regard to the receiver functions of the UE1120. Each Tx/Rx module (or transceiver)1125receives a signal through each antenna1126. Each Tx/Rx module provides an RF carrier and information to the Rx processor1123. The processor1121may be connected to the memory1124storing program codes and data. The memory may be referred to as a computer-readable medium. E. Machine Type Communication (MTC) The Machine Type Communication (MTC) refers to communication technology adopted by 3rdGeneration Partnership Project (3GPP) to meet Internet of Things (IoT) service requirements. Since the MTC does not require high throughput, it may be used as an application for machine-to-machine (M2M) and Internet of Things (IoT). The MTC may be implemented to satisfy the following requirements: (i) low cost and low complexity; (ii) enhanced coverage; and (iii) low power consumption. The MTC was introduced in 3GPP release 10. Hereinafter, the MTC features added in each 3GPP release will be described. The MTC load control was introduced in 3GPP releases 10 and 11. The load control method prevents IoT (or M2M) devices from creating a heavy load on the base station suddenly. Specifically, according to release 10, when a load occurs, the base station may disconnect connections with IoT devices to control the load. According to release 11, the base station may prevent the UE from attempting to establish a connection by informing the UE that access will become available through broadcasting such as SIB14. In release 12, the features of low-cost MTC were added, and to this end, UE category 0 was newly defined. The UE category indicates the amount of data that the UE is capable of processing using a communication modem. Specifically, a UE that belongs to UE category 0 may use a reduced peak data rate, a half-duplex operation with relaxed RF requirements, and a single reception antenna, thereby reducing the baseband and RF complexity of the UE. In Release 13, enhanced MTC (eMTC) was introduced. In the eMTC, the UE operates in a bandwidth of 1.08 MHz, which is the minimum frequency bandwidth supported by legacy LTE, thereby further reducing the cost and power consumption. Although the following description relates to the eMTC, the description is equally applicable to the MTC, 5G (or NR) MTC, etc. For convenience of description, all types of MTC is commonly referred to as ‘MTC’. In the following description, the MTC may be referred to as another terminology such as ‘eMTC’, ‘LTE-M1/M2’, ‘bandwidth reduced low complexity/coverage enhanced (BL/CE)’, ‘non-BL UE (in enhanced coverage)’, ‘NR MTC’, or ‘enhanced BL/CE’. Further, the term “MTC” may be replaced with a term defined in the future 3GPP standards. 1) General Features of MTC (1) The MTC operates only in a specific system bandwidth (or channel bandwidth). The specific system bandwidth may use 6 RBs of the legacy LTE as shown in Table 4 below and defined by considering the frequency range and subcarrier spacing (SCS) shown in Tables 5 to 7. The specific system bandwidth may be referred to as narrowband (NB). Here, the legacy LTE may encompass the contents described in the 3GPP standards expect the MTC. In the NR, the MTC may use RBs corresponding the smallest system bandwidth in Tables 6 and 7 as in the legacy LTE. Alternatively, the MTC may operate in at least one BWP or in a specific band of a BWP. TABLE 4Channel bandwidth1.435101520BWChannel [MHz]Transmission615255075100bandwidthconfiguration NRB Table 5 shows the frequency ranges (FRs) defined for the NR. TABLE 5Frequency rangedesignationCorresponding frequency rangeFR1450 MHz-6000 MHzFR224250 MHz-52600 MHz Table 6 shows the maximum transmission bandwidth configuration (NRB) for the channel bandwidth and SCS in NR FR1. TABLE 6510152025304050608090100SCSMHzMHzMHzMHzMHzMHzMHzMHzMHzMHzMHzMHz(kHz)NRBNRBNRBNRBNRBNRBNRBNRBNRBNRBNRBNRB15255279106133160216270N/AN/AN/AN/A3011243851657810613316221724527360N/A1118243138516579107121135 Table 7 shows the maximum transmission bandwidth configuration (NRB) for the channel bandwidth and SCS in NR FR2. TABLE 7SCS50 MHz100 MHz200 MHz400 MHz(kHz)NRBNRBNRBNRB6066132264N.A1203266132264 Hereinafter, the MTC narrowband (NB) will be described in detail. The MTC follows narrowband operation to transmit and receive physical channels and signals, and the maximum channel bandwidth is reduced to 1.08 MHz or 6 (LTE) RBs. The narrowband may be used as a reference unit for allocating resources to some downlink and uplink channels, and the physical location of each narrowband in the frequency domain may vary depending on the system bandwidth. The 1.08 MHz bandwidth for the MTC is defined to allow an MTC UE to follow the same cell search and random access procedures as those of the legacy UE. The MTC may be supported by a cell with a much larger bandwidth (e.g., 10 MHz), but the physical channels and signals transmitted/received in the MTC are always limited to 1.08 MHz. The larger bandwidth may be supported by the legacy LTE system, NR system, 5G system, etc. The narrowband is defined as 6 non-overlapping consecutive physical RBs in the frequency domain. If NNBUL≥4, a wideband is defined as four non-overlapping narrowbands in the frequency domain. If NNBUL<4, NWBUL=1 and a single wideband is composed of NNBULnon-overlapping narrowband(s). For example, in the case of a 10 MHz channel, 8 non-overlapping narrowbands are defined. FIGS.12A and12Billustrate examples of narrowband operations and frequency diversity. Specifically,FIG.12Aillustrates an example of the narrowband operation, andFIG.12Billustrates an example of repetitions with RF retuning. Hereinafter, frequency diversity by RF retuning will be described with reference toFIG.12B. The MTC supports limited frequency, spatial, and time diversity due to the narrowband RF, single antenna, and limited mobility. To reduce the effects of fading and outages, frequency hopping is supported between different narrowbands by the RF retuning. The frequency hopping is applied to different uplink and downlink physical channels when repetition is enabled. For example, if 32 subframes are used for PDSCH transmission, the first 16 subframes may be transmitted on the first narrowband. In this case, the RF front-end is retuned to another narrowband, and the remaining 16 subframes are transmitted on the second narrowband. The MTC narrowband may be configured by system information or DCI. (2) The MTC operates in half-duplex mode and uses limited (or reduced) maximum transmission power. (3) The MTC does not use a channel (defined in the legacy LTE or NR) that should be distributed over the full system bandwidth of the legacy LTE or NR. For example, the MTC does not use the following legacy LTE channels: PCFICH, PHICH, and PDCCH. Thus, a new control channel, an MTC PDCCH (MPDCCH), is defined for the MTC since the above channels are not monitored. The MPDCCH may occupy a maximum of 6 RBs in the frequency domain and one subframe in the time domain. The MPDCCH is similar to an evolved PDCCH (EPDCCH) and supports a common search space for paging and random access. In other words, the concept of the MPDCCH is similar to that of the EPDCCH used in the legacy LTE. (4) The MTC uses newly defined DCI formats. For example, DCI formats 6-0A, 6-0B, 6-1A, 6-1B, 6-2, etc. may be used. In the MTC, a physical broadcast channel (PBCH), physical random access channel (PRACH), MPDCCH, PDSCH, PUCCH, and PUSCH may be repeatedly transmitted. The MTC repeated transmission enables decoding of an MTC channel in a poor environment such as a basement, that is, when the signal quality or power is low, thereby increasing the radius of a cell or supporting the signal propagation effect. The MTC may support a limited number of transmission modes (TMs), which are capable of operating on a single layer (or single antenna), or support a channel or reference signal (RS), which are capable of operating on a single layer. For example, the MTC may operate in TM 1, 2, 6, or 9. (6) In the MTC, HARQ retransmission is adaptive and asynchronous and performed based on a new scheduling assignment received on the MPDCCH. (7) In the MTC, PDSCH scheduling (DCI) and PDSCH transmission occur in different subframes (cross-subframe scheduling). (8) All resource allocation information (e.g., a subframe, a transport block size (TBS), a subband index, etc.) for SIB1 decoding is determined by a master information block (MIB) parameter (in the MTC, no control channel is used for the SIB1 decoding). (9) All resource allocation information (e.g., a subframe, a TBS, a subband index, etc.) for SIB2 decoding is determined by several SIB1 parameters (in the MTC, no control channel is used for the SIB2 decoding). (10) The MTC supports an extended discontinuous reception (DRX) cycle. (11) The MTC may use the same primary synchronization signal/secondary synchronization signal/common reference signal (PSS/SSS/CRS) as that used in the legacy LTE or NR. In the NR, the PSS/SSS is transmitted in the unit of SS block (or SS/PBCH block or SSB), and a tracking RS (TRS) may be used for the same purpose as the CRS. That is, the TRS is a cell-specific RS and may be used for frequency/time tracking. 2) MTC Operation Mode and Level Hereinafter, MTC operation modes and levels will be described. To enhance coverage, the MTC may be divided into two operation modes (first and second modes) and four different levels as shown in Table 8 below. The MTC operation mode may be referred to CE mode. The first and second modes may be referred to CE mode A and CE mode B, respectively. TABLE 8ModeLevelDescriptionMode ALevel 1No repetition for PRACHLevel 2Small Number of Repetition for PRACHMode BLevel 3Medium Number of Repetition for PRACHLevel 4Large Number of Repetition for PRACH The first mode is defined for small coverage where full mobility and channel state information (CSI) feedback are supported. In the first mode, the number of repetitions is zero or small. The operation in the first mode may have the same operation coverage as that of UE category 1. The second mode is defined for a UE with a very poor coverage condition where CSI feedback and limited mobility are supported. In the second mode, the number of times that transmission is repeated is large. The second mode provides up to 15 dB coverage enhancement with reference to the coverage of UE category 1. Each level of the MTC is defined differently in RACH and paging procedures. Hereinafter, a description will be given of how to determine the MTC operation mode and level. The MTC operation mode is determined by the base station, and each level is determined by the MTC UE. Specifically, the base station transmits RRC signaling including information for the MTC operation mode to the UE. The RRC signaling may include an RRC connection setup message, an RRC connection reconfiguration message, or an RRC connection reestablishment message. Here, the term “message” may refer to an information element (IE). The MTC UE determines a level within the operation mode and transmits the determined level to the base station. Specifically, the MTC UE determines the level within the operation mode based on measured channel quality (e.g., RSRP, RSRQ, SINR, etc.) and informs the base station of the determined level using a PRACH resource (e.g., frequency, time, preamble, etc.). 3) MTC Guard Period As described above, the MTC operates in the narrowband. The location of the narrowband may vary in each specific time unit (e.g., subframe or slot). The MTC UE tunes to a different frequency in every time unit. Thus, all frequency retuning may require a certain period of time. In other words, the guard period is required for transition from one time unit to the next time unit, and no transmission and reception occurs during the corresponding period. The guard period varies depending on whether the current link is downlink or uplink and also varies depending on the state thereof. An uplink guard period (i.e., guard period defined for uplink) varies depending on the characteristics of data carried by a first time unit (time unit N) and a second time unit (time unit N+1). In the case of a downlink guard period, the following conditions need to be satisfied: (1) a first downlink narrowband center frequency is different from a second narrowband center frequency; and (2) in TDD, a first uplink narrowband center frequency is different from a second downlink center frequency. The MTC guard period defined in the legacy LTE will be described. A guard period consisting of at most NsymbretuneSC-FDMA symbols is created for Tx-Tx frequency retuning between two consecutive subframes. When the higher layer parameter ce-RetuningSymbols is configured, Nsymbretuneis equal to ce-RetuningSymbols. Otherwise, Nsymbretuneis 2. For an MTC UE configured with the higher layer parameter srs-UpPtsAdd, a guard period consisting of SC-FDMA symbols is created for Tx-Tx frequency retuning between a first special subframe and a second uplink subframe for frame structure type 2. FIG.13illustrates physical channels available in MTC and a general signal transmission method using the same. When an MTC UE is powered on or enters a new cell, the MTC UE performs initial cell search in step S1301. The initial cell search involves acquisition of synchronization with a base station. Specifically, the MTC UE synchronizes with the base station by receiving a primary synchronization signal (PSS) and a second synchronization signal (SSS) from the base station and obtains information such as a cell identifier (ID). The PSS/SSS used by the MTC UE for the initial cell search may be equal to a PSS/SSS or a resynchronization signal (RSS) of the legacy LTE. Thereafter, the MTC UE may acquire broadcast information in the cell by receiving a PBCH signal from the base station. During the initial cell search, the MTC UE may monitor the state of a downlink channel by receiving a downlink reference signal (DL RS). The broadcast information transmitted on the PBCH corresponds to the MIB. In the MTC, the MIB is repeated in the first slot of subframe #0 of a radio frame and other subframes (subframe #9 in FDD and subframe #5 in the TDD). The PBCH repetition is performed such that the same constellation point is repeated on different OFDM symbols to estimate an initial frequency error before attempting PBCH decoding. FIGS.14A and14Billustrate an example of system information transmissions in MTC. Specifically,FIG.14Aillustrates an example of a repetition pattern for subframe #0 in FDD and a frequency error estimation method for a normal CP and repeated symbols, andFIG.14Billustrates an example of transmission of an SIB-BR on a wideband LTE channel. Five reserved bits in the MIB are used in the MTC to transmit scheduling information for a new system information block for bandwidth reduced device (SIB1-BR) including a time/frequency location and a TBS. The SIB-BR is transmitted on a PDSCH directly without any related control channels. The SIB-BR is maintained without change for 512 radio frames (5120 ms) to allow a large number of subframes to be combined. Table 9 shows an example of the MIB. TABLE 9-- ASN1STARTMasterInformationBlock ::=SEQUENCE {dl-BandwidthENUMERATED {n6 , n15 , n25 , n50, n75, n1001,phich-ConfigPHICH-Config ,systemFrameNumberBIT STRING (SIZE (8)),schedulingInfoSIB1-BR-r13INTEGER (0..31),systemInfoUnchanged-BR-r15BOOLEAN,spareBIT STRING (SIZE (4))}-- ASNISTOP In Table 9, the schedulingInfoSIB1-BR field indicates the index of a table that defines SystemInformationBlockType1-BR scheduling information. The zero value means that SystemInformationBlockType1-BR is not scheduled. The overall function and information carried by SystemInformationBlockType1-BR (or SIB1-BR) is similar to SIB1 of the legacy LTE. The contents of SIB1-BR may be categorized as follows: (1) PLMN; (2) cell selection criteria; and (3) scheduling information for SIB2 and other SIBs. After completing the initial cell search, the MTC UE may acquire more detailed system information by receiving a MPDCCH and a PDSCH based on information in the MPDCCH in step S1302. The MPDCCH has the following features: (1) The MPDCCH is very similar to the EPDCCH; (2) The MPDCCH may be transmitted once or repeatedly (the number of repetitions is configured through higher layer signaling); (3) Multiple MPDCCHs are supported and a set of MPDCCHs are monitored by the UE; (4) the MPDCCH is generated by combining enhanced control channel elements (eCCEs), and each CCE includes a set of REs; and (5) the MPDCCH supports an RA-RNTI, SI-RNTI, P-RNTI, C-RNTI, temporary C-RNTI, and semi-persistent scheduling (SPS) C-RNTI. To complete the access to the base station, the MTC UE may perform a random access procedure in steps S1303to S1306. The basic configuration of an RACH procedure is carried by SIB2. SIB2 includes parameters related to paging. A paging occasion (PO) is a subframe in which the P-RNTI is capable of being transmitted on the MPDCCH. When a P-RNTI PDCCH is repeatedly transmitted, the PO may refer to a subframe where MPDCCH repetition is started. A paging frame (PF) is one radio frame, which may contain one or multiple POs. When DRX is used, the MTC UE monitors one PO per DRX cycle. A paging narrowband (PNB) is one narrowband, on which the MTC UE performs paging message reception. To this end, the MTC UE may transmit a preamble on a PRACH (S1303) and receive a response message (e.g., random access response (RAR)) for the preamble on the MPDCCH and the PDSCH related thereto (S1304). In the case of contention-based random access, the MTC UE may perform a contention resolution procedure including transmission of an additional PRACH signal (S1305) and reception of a MPDCCH signal and a PDSCH signal related thereto (S1306). In the MTC, the signals and messages (e.g., Msg 1, Msg 2, Msg 3, and Msg 4) transmitted during the RACH procedure may be repeatedly transmitted, and a repetition pattern may be configured differently depending on coverage enhancement (CE) levels. Msg 1 may represent the PRACH preamble, Msg 2 may represent the RAR, Msg 3 may represent uplink transmission for the RAR at the MTC UE, and Msg 4 may represent downlink transmission for Msg 3 from the base station. For random access, signaling of different PRACH resources and different CE levels is supported. This provides the same control of the near-far effect for the PRACH by grouping UEs that experience similar path loss together. Up to four different PRACH resources may be signaled to the MTC UE. The MTC UE measures RSRP using a downlink RS (e.g., CRS, CSI-RS, TRS, etc.) and selects one of random access resources based on the measurement result. Each of four random access resources has an associated number of PRACH repetitions and an associated number of RAR repetitions. Thus, the MTC UE in poor coverage requires a large number of repetitions so as to be detected by the base station successfully and needs to receive as many RARs as the number of repetitions such that the coverage levels thereof are satisfied. The search spaces for RAR and contention resolution messages are defined in the system information, and the search space is independent for each coverage level. A PRACH waveform used in the MTC is the same as that in the legacy LTE (for example, OFDM and Zadoff-Chu sequences). After performing the above-described processes, the MTC UE may perform reception of an MPDCCH signal and/or a PDSCH signal (S1307) and transmission of a PUSCH signal and/or a PUCCH signal (S1308) as a normal uplink/downlink signal transmission procedure. Control information that the MTC UE transmits to the base station is commonly referred to as uplink control information (UCI). The UCI includes a HARQ-ACK/NACK, scheduling request, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. When the MTC UE has established an RRC connection, the MTC UE blindly decodes the MPDCCH in a configured search space to obtain uplink and downlink data assignments. In the MTC, all available OFDM symbols in a subframe are used to transmit DCI. Accordingly, time-domain multiplexing is not allowed between control and data channels in the subframe. Thus, the cross-subframe scheduling may be performed between the control and data channels as described above. If the MPDCCH is last repeated in subframe #N, the MPDCCH schedules a PDSCH assignment in subframe #N+2. DCI carried by the MPDCCH provides information for how many times the MPDCCH is repeated so that the MTC UE may know the number of repetitions when PDSCH transmission is started. The PDSCH assignment may be performed on different narrowbands. Thus, the MTC UE may need to perform retuning before decoding the PDSCH assignment. For uplink data transmission, scheduling follows the same timing as that of the legacy LTE. The last MPDCCH in subframe #N schedules PUSCH transmission starting in subframe #N+4. FIG.15illustrates an example of scheduling for each of MTC and legacy LTE. A legacy LTE assignment is scheduled using the PDCCH and uses the initial OFDM symbols in each subframe. The PDSCH is scheduled in the same subframe in which the PDCCH is received. On the other hand, the MTC PDSCH is cross-subframe scheduled, and one subframe is defined between the MPDCCH and PDSCH to allow MPDCCH decoding and RF retuning. MTC control and data channels may be repeated for a large number of subframes to be decoded in an extreme coverage condition. Specifically, the MTC control and data channels may be repeated for a maximum of 256 subframes for the MPDCCH and a maximum of 2048 subframes for the PDSCH F. Narrowband-Internet of Things (NB-IoT) The NB-IoT may refer to a system for providing low complexity and low power consumption based on a system bandwidth (BW) corresponding to one physical resource block (PRB) of a wireless communication system (e.g., LTE system, NR system, etc.). Herein, the NB-IoT may be referred to as another terminology such as ‘NB-LTE’, ‘NB-IoT enhancement’, ‘further enhanced NB-IoT’, or ‘NB-NR’. The NB-IoT may be replaced with a term defined or to be defined in the 3GPP standards. For convenience of description, all types of NB-IoT is commonly referred to as ‘NB-IoT’. The NB-IoT may be used to implement the IoT by supporting an MTC device (or MTC UE) in a cellular system. Since one PRB of the system BW is allocated for the NB-IoT, frequency may be efficiently used. In addition, considering that in the NB-IoT, each UE recognizes a single PRB as one carrier, the PRB and carrier described herein may be considered to have the same meaning. Although the present disclosure describes frame structures, physical channels, multi-carrier operation, operation modes, and general signal transmission and reception of the NB-IoT based on the LTE system, it is apparent that the present disclosure is applicable to the next-generation systems (e.g., NR system, etc.). In addition, the details of the NB-IoT described in the present disclosure may be applied to the MTC, which has similar purposes (e.g., low power, low cost, coverage enhancement, etc.). 1) Frame Structure and Physical Resource of NB-IoT The NB-IoT frame structure may vary depending on subcarrier spacing. FIGS.16and17illustrate examples of NB-IoT frame structures according to subcarrier spacing (SCS). Specifically,FIG.16illustrates a frame structure with SCS of 15 kHz, andFIG.17illustrates a frame structure with SCS of 3.75 kHz. However, the NB-IoT frame structure is not limited thereto, and different SCS (e.g., 30 kHz, etc.) may be applied to the NB-IoT by changing the time/frequency unit. Although the present disclosure describes the NB-IoT frame structure based on the LTE frame structure, this is merely for convenience of description and the present disclosure is not limited thereto. That is, the embodiments of the present disclosure are applicable to the NB-IoT based on the frame structure of the next-generation system (e.g., NR system). Referring toFIG.16, the NB-IoT frame structure for the 15 kHz subcarrier spacing is the same as the frame structure of the legacy system (LTE system). Specifically, a 10 ms NB-IoT frame may include 10 NB-IoT subframes of 1 ms each, and the 1 ms NB-IoT subframe may include two NB-IoT slots, each having a duration of 0.5 ms. Each 0.5 ms NB-IoT slot ms may include 7 OFDM symbols. Referring toFIG.17, a 10 ms NB-IoT frame may include five NB-IoT subframes of 2 ms each, and the 2 ms NB-IoT subframe may include 7 OFDM symbols and one guard period (GP). The 2 ms NB-IoT subframe may be expressed as an NB-IoT slot or an NB-IoT resource unit (RU). Hereinafter, downlink and uplink physical resources for the NB-IoT will be described. The NB-IoT downlink physical resource may be configured based on physical resources of other communication systems (e.g., LTE system, NR system, etc.) except that the system BW is composed of a specific number of RBs (e.g., one RB=180 kHz). For example, when NB-IoT downlink supports only the 15 kHz subcarrier spacing as described above, the NB-IoT downlink physical resource may be configured by limiting the resource grid of the LTE system illustrated inFIG.6to one RB (i.e., one PRB) in the frequency domain. The NB-IoT uplink physical resource may be configured by limiting to the system bandwidth to one RB as in the NB-IoT downlink. For example, when NB-IoT uplink supports the 15 kHz and 3.75 kHz subcarrier spacing as described above, a resource grid for the NB-IoT uplink may be represented as shown inFIG.18. The number of subcarriers NscULand the slot period Tslotmay be given in Table 10 below. FIG.18illustrates an example of the resource grid for NB-IoT uplink. TABLE 10Subcarrier spacingNscULTslotΔf = 3.75 kHz4861440 · TsΔf = 15 kHz1215360 · Ts A resource unit (RU) for the NB-IoT uplink may include SC-FDMA symbols in the time domain and NsymbULNslotsULconsecutive subcarriers in the frequency domain. In frame structure type 1 (i.e., FDD), the values of NscRUand NsymbULmay be given in Table 11 below. In frame structure type 2 (i.e., TDD), the values of NscRUand NsymbULmay be given in Table 12. TABLE 11NPUSCH formatΔfNscRUNslotsULNsymbUL13.75kHz116715kHz116386412223.75kHz1415kHz14 TABLE 12SupportedNPUSCHuplink-downlinkformatΔfconfigurationsNscRUNslotsULNsymbUL13.75kHz1, 4116715kHz1, 2, 3, 4, 5116386412223.75kHz1, 41415kHz1, 2, 3, 4, 514 2) Physical Channels of NB-IoT A base station and/or UE that support the NB-IoT may be configured to transmit and receive physical channels and signals different from those in the legacy system. Hereinafter, the physical channels and/or signals supported in the NB-IoT will be described in detail. First, the NB-IoT downlink will be described. For the NB-IoT downlink, an OFDMA scheme with the 15 kHz subcarrier spacing may be applied. Accordingly, orthogonality between subcarriers may be provided, thereby supporting coexistence with the legacy system (e.g., LTE system, NR system, etc.). To distinguish the physical channels of the NB-IoT system from those of the legacy system, ‘N (narrowband)’ may be added. For example, DL physical channels may be defined as follows: ‘narrowband physical broadcast channel (NPBCH)’, ‘narrowband physical downlink control channel (NPDCCH)’, ‘narrowband physical downlink shared channel (NPDSCH)’, etc. DL physical signals may be defined as follows: ‘narrowband primary synchronization signal (NPSS)’, ‘narrowband secondary synchronization signal (NSSS)’, ‘narrowband reference signal (NRS)’, ‘narrowband positioning reference signal (NPRS)’, ‘narrowband wake-up signal (NWUS)’, etc. Generally, the above-described downlink physical channels and physical signals for the NB-IoT may be configured to be transmitted based on time-domain multiplexing and/or frequency-domain multiplexing. The NPBCH, NPDCCH, and NPDSCH, which are downlink channels of the NB-IoT system, may be repeatedly transmitted for coverage enhancement. The NB-IoT uses newly defined DCI formats. For example, the DCI formats for the NB-IoT may be defined as follows: DCI format NO, DCI format N1, DCI format N2, etc. Next, the NB-IoT uplink will be described. For the NB-IoT uplink, an SC-FDMA scheme with the subcarrier spacing of 15 kHz or 3.75 kHz may be applied. The NB-IoT uplink may support multi-tone and single-tone transmissions. For example, the multi-tone transmission may support the 15 kHz subcarrier spacing, and the single-tone transmission may support both the 15 kHz and 3.75 kHz subcarrier spacing. In the case of the NB-IoT uplink, ‘N (narrowband)’ may also be added to distinguish the physical channels of the NB-IoT system from those of the legacy system, similarly to the NB-IoT downlink. For example, uplink physical channels may be defined as follows: ‘narrowband physical random access channel (NPRACH)’, ‘narrowband physical uplink shared channel (NPUSCH)’, etc. UL physical signals may be defined as follows: ‘narrowband demodulation reference signal (NDMRS)’. The NPUSCH may be configured with NPUSCH format 1 and NPUSCH format 2. For example, NPUSCH format 1 is used for UL-SCH transmission (or transfer), and NPUSCH format 2 may be used for UCI transmission such as HARQ ACK signaling. The NPRACH, which is a downlink channel of the NB-IoT system, may be repeatedly transmitted for coverage enhancement. In this case, frequency hopping may be applied to the repeated transmission. 3) Multi-Carrier Operation in NB-IoT Hereinafter, the multi-carrier operation in the NB-IoT will be described. The multi-carrier operation may mean that when the base station and/or UE uses different usage of multiple carriers (i.e., different types of multiple carriers) in transmitting and receiving a channel and/or a signal in the NB-IoT. In general, the NB-IoT may operate in multi-carrier mode as described above. In this case, NB-IoT carriers may be divided into an anchor type carrier (i.e., anchor carrier or anchor PRB) and a non-anchor type carrier (i.e., non-anchor carrier or non-anchor PRB). From the perspective of the base station, the anchor carrier may mean a carrier for transmitting the NPDSCH that carries the NPSS, NSSS, NPBCH, and SIB (N-SIB) for initial access. In other words, in the NB-IoT, the carrier for initial access may be referred to as the anchor carrier, and the remaining carrier(s) may be referred to as the non-anchor carrier. In this case, there may be one or multiple anchor carriers in the system. 4) Operation Mode of NB-IoT The operation mode of the NB-IoT will be described. The NB-IoT system may support three operation modes.FIGS.19A to19Cillustrate an examples of operation modes supported in the NB-IoT system. Although the present disclosure describes the NB-IoT operation mode based on the LTE band, this is merely for convenience of description and the present disclosure is also applicable to other system bands (e.g., NR system band). FIG.19Aillustrates an in-band system,FIG.19Billustrates a guard-band system, andFIG.19Cillustrates a stand-alone system. The in-band system, guard-band system, and stand-alone system may be referred to as in-band mode, guard-band mode, and stand-alone mode, respectively. The in-band system may mean a system or mode that uses one specific RB (PRB) in the legacy LTE band for the NB-IoT. To operate the in-band system, some RBs of the LTE system carrier may be allocated. The guard-band system may mean a system or mode that uses a space reserved for the guard band of the legacy LTE band for the NB-IoT. To operate the guard-band system, the guard band of the LTE carrier which is not used as the RB in the LTE system may be allocated. For example, the legacy LTE band may be configured such that each LTE band has the guard band of minimum 100 kHz at the end thereof. In order to use 200 kHz, two non-contiguous guard bands may be used. The in-band system and the guard-band system may operate in a structure where the NB-IoT coexists in the legacy LTE band. Meanwhile, the stand-alone system may mean a system or mode independent from the legacy LTE band. To operate the stand-alone system, a frequency band (e.g., reallocated GSM carrier) used in a GSM EDGE radio access network (GERAN) may be separately allocated. The above three operation modes may be applied independently, or two or more operation modes may be combined and applied. 5) General Signal Transmission and Reception Procedure in NB-IoT FIG.20illustrates an example of physical channels available in the NB-IoT and a general signal transmission method using the same. In a wireless communication system, an NB-IoT UE may receive information from a base station in downlink (DL) and transmit information to the base station in uplink (UL). In other words, the base station may transmit the information to the NB-IoT UE in downlink and receive the information from the NB-IoT UE in uplink in the wireless communication system. Information transmitted and received between the base station and the NB-IoT UE may include various data and control information, and various physical channels may be used depending on the type/usage of information transmitted and received therebetween. The NB-IoT signal transmission and reception method described with reference toFIG.20may be performed by the aforementioned wireless communication apparatuses (e.g., base station and UE inFIG.11). When the NB-IoT UE is powered on or enters a new cell, the NB-IoT UE may perform initial cell search (S11). The initial cell search involves acquisition of synchronization with the base station. Specifically, the NB-IoT UE may synchronize with the base station by receiving an NPSS and an NSSS from the base station and obtain information such as a cell ID. Thereafter, the NB-IoT UE may acquire information broadcast in the cell by receiving an NPBCH from the base station. During the initial cell search, the NB-IoT UE may monitor the state of a downlink channel by receiving a downlink reference signal (DL RS). In other words, when the NB-IoT UE enters the new cell, the BS may perform the initial cell search, and more particularly, the base station may synchronize with the UE. Specifically, the base station may synchronize with the NB-IoT UE by transmitting the NPSS and NSSS to the UE and transmit the information such as the cell ID. The base station may transmit the broadcast information in the cell by transmitting (or broadcasting) the NPBCH to the NB-IoT UE. The BS may transmit the DL RS to the NB-IoT UE during the initial cell search to check the downlink channel state. After completing the initial cell search, the NB-IoT UE may acquire more detailed system information by receiving a NPDCCH and a NPDSCH related to thereto (S12). In other words, after the initial cell search, the base station may transmit the more detailed system information by transmitting the NPDCCH and the NPDSCH related to thereto to the NB-IoT UE. Thereafter, the NB-IoT UE may perform a random access procedure to complete the access to the base station (S13to S16). Specifically, the NB-IoT UE may transmit a preamble on an NPRACH (S13). As described above, the NPRACH may be repeatedly transmitted based on frequency hopping for coverage enhancement. In other words, the base station may (repeatedly) receive the preamble from the NB-IoT UE over the NPRACH. Then, the NB-IoT UE may receive a random access response (RAR) for the preamble from the base station on the NPDCCH and the NPDSCH related thereto (S14). That is, the base station may transmit the random access response (RAR) for the preamble to the base station on the NPDCCH and the NPDSCH related thereto. The NB-IoT UE may transmit an NPUSCH using scheduling information in the RAR (S15) and perform a contention resolution procedure based on the NPDCCH and the NPDSCH related thereto (S16). That is, the base station may receive the NPUSCH from the NB-IoT UE based on the scheduling information in the RAR and perform the contention resolution procedure. After performing the above-described processes, the NB-IoT UE may perform NPDCCH/NPDSCH reception (S17) and NPUSCH transmission (S18) as a normal UL/DL signal transmission procedure. After the above-described processes, the base station may transmit the NPDCCH/NPDSCH to the NB-IoT UE and receive the NPUSCH from the NB-IoT UE during the normal uplink/downlink signal transmission procedure. In the NB-IoT, the NPBCH, NPDCCH, NPDSCH, etc. may be repeatedly transmitted for the coverage enhancement as described above. In addition, UL-SCH (normal uplink data) and UCI may be transmitted on the NPUSCH. In this case, the UL-SCH and UCI may be configured to be transmitted in different NPUSCH formats (e.g., NPUSCH format 1, NPUSCH format 2, etc.) As described above, the UCI means control information transmitted from the UE to the base station. The UCI may include the HARQ ACK/NACK, scheduling request (SR), CSI, etc. The CSI may include the CQI, PMI, RI, etc. Generally, the UCI may be transmitted over the NPUSCH in the NB-IoT as described above. In particular, the UE may transmit the UCI on the NPUSCH periodically, aperiodically, or semi-persistently according to the request/indication from the network (e.g., base station). 6) Initial Access Procedure in NB-IoT The procedure in which the NB-IoT UE initially accesses the BS is briefly described in the section “General Signal Transmission and Reception Procedure in NB-IoT”. Specifically, the above procedure may be subdivided into a procedure in which the NB-IoT UE searches for an initial cell and a procedure in which the NB-IoT UE obtains system information. FIG.21illustrates a particular procedure for signaling between a UE and a BS (e.g., NodeB, eNodeB, eNB, gNB, etc.) for initial access in the NB-IoT. In the following, a normal initial access procedure, an NPSS/NSSS configuration, and acquisition of system information (e.g., MIB, SIB, etc.) in the NB-IoT will be described with reference toFIG.21. FIG.21illustrates an example of the initial access procedure in the NB-IoT. The name of each physical channel and/or signal may vary depending on the wireless communication system to which the NB-IoT is applied. For example, although the NB-IoT based on the LTE system is considered inFIG.21, this is merely for convenience of description and details thereof are applicable to the NB-IoT based on the NR system. The details of the initial access procedure are also applicable to the MTC. Referring toFIG.21, the NB-IoT UE may receive a narrowband synchronization signal (e.g., NPSS, NSSS, etc.) from the base station (S2110and S2120). The narrowband synchronization signal may be transmitted through physical layer signaling. The NB-IoT UE may receive a master information block (MIB) (e.g., MIB-NB) from the base station on an NPBCH (S2130). The MIB may be transmitted through higher layer signaling (e.g., RRC signaling). The NB-IoT UE may receive a system information block (SIB) from the base station on an NPDSH (S2140and S2150). Specifically, the NB-IoT UE may receive SIB1-NB, SIB2-NB, etc. on the NPDSCH through the higher layer signaling (e.g., RRC signaling). For example, SIB1-NB may refer to system information with high priority among SIBs, and SIB2-NB may refer to system information with lower priority than SIB1-NB. The NB-IoT may receive an NRS from the BS (S2160), and this operation may be performed through physical layer signaling. 7) Random Access Procedure in NB-IoT The procedure in which the NB-IoT UE performs random access to the base station is briefly described in the section “General Signal Transmission and Reception Procedure in NB-IoT”. Specifically, the above procedure may be subdivided into a procedure in which the NB-IoT UE transmits a preamble to the base station and a procedure in which the NB-IoT receives a response for the preamble. FIG.22illustrates a particular procedure for signaling between a UE and a base station (e.g., NodeB, eNodeB, eNB, gNB, etc.) for random access in the NB-IoT. In the following, detail of the random access procedure in the NB-IoT will be described based on messages (e.g., msg1, msg2, msg3, msg4) used therefor. FIG.22illustrates an example of the random access procedure in the NB-IoT. The name of each physical channel, physical signal, and/or message may vary depending on the wireless communication system to which the NB-IoT is applied. For example, although the NB-IoT based on the LTE system is considered inFIG.22, this is merely for convenience of description and details thereof are applicable to the NB-IoT based on the NR system. The details of the initial access procedure are also applicable to the MTC. Referring toFIG.22, the NB-IoT may be configured to support contention-based random access. First, the NB-IoT UE may select an NPRACH resource based on the coverage level of the corresponding UE. The NB-IoT UE may transmit a random access preamble (i.e., message 1, msg1) to the base station on the selected NPRACH resource. The NB-IoT UE may monitor an NPDCCH search space to search for an NPDCCH for DCI scrambled with an RA-RNTI (e.g., DCI format N1). Upon receiving the NPDCCH for the DCI scrambled with the RA-RNTI, the UE may receive an RAR (i.e., message 2, msg2) from the base station on an NPDSCH related to the NPDCCH. The NB-IoT UE may obtain a temporary identifier (e.g., temporary C-RNTI), a timing advance (TA) command, etc. from the RAR. In addition, the RAR may also provide an uplink grant for a scheduled message (i.e., message 3, msg3). To start a contention resolution procedure, the NB-IoT UE may transmit the scheduled message to the base station. Then, the base station may transmit an associated contention resolution message (i.e., message 4, msg4) to the NB-IoT UE in order to inform that the random access procedure is successfully completed. By doing the above, the base station and the NB-IoT UE may complete the random access. 8) DRX Procedure in NB-IoT While performing the general signal transmission and reception procedure of the NB-IoT, the NB-IoT UE may transit to an idle state (e.g., RRC_IDLE state) and/or an inactive state (e.g., RRC_INACTIVE state) to reduce power consumption. The NB-IoT UE may be configured to operate in DRX mode after transiting to the idle state and/or the inactive state. For example, after transiting to the idle state and/or the inactive state, the NB-IoT UE may be configured to monitor an NPDCCH related to paging only in a specific subframe (frame or slot) according to a DRX cycle determined by the BS. Here, the NPDCCH related to paging may refer to an NPDCCH scrambled with a P-RNTI. FIG.23illustrates an example of DRX mode in an idle state and/or an inactive state. A DRX configuration and indication for the NB-IoT UE may be provided as shown inFIG.24. That is,FIG.24illustrates an example of a DRX configuration and indication procedure for the NB-IoT UE. However, the procedure inFIG.24is merely exemplary, and the methods proposed in the present disclosure are not limited thereto. Referring toFIG.24, the NB-IoT UE may receive DRX configuration information from the base station (e.g., NodeB, eNodeB, eNB, gNB, etc.) (S2410). In this case, the UE may receive the information from the base station through higher layer signaling (e.g., RRC signaling). The DRX configuration information may include DRX cycle information, a DRX offset, configuration information for DRX-related timers, etc. Thereafter, the NB-IoT UE may receive a DRX command from the base station (S2420). In this case, the UE may receive the DRX command from the base station through higher layer signaling (e.g., MAC-CE signaling). Upon receiving the DRX command, the NB-IoT UE may monitor an NPDCCH in a specific time unit (e.g., subframe, slot, etc.) based on the DRX cycle (S2430). The NPDCCH monitoring may mean a process of decoding a specific portion of the NPDCCH based on a DCI format to be received in a corresponding search space and scrambling a corresponding CRC with a specific predefined RNTI value in order to check whether the scrambled CRC matches (i.e. corresponds to) a desired value. When the NB-IoT UE receives its paging ID and/or information indicating that system information is changed over the NPDCCH during the process shown inFIG.24, the NB-IoT UE may initialize (or reconfigure) the connection (e.g., RRC connection) with the base station (for example, the UE may perform the cell search procedure ofFIG.20). Alternatively, the NB-IoT UE may receive (or obtain) new system information from the base station (for example, the UE may perform the system information acquisition procedure ofFIG.20). G. Proposal for Sub-Grouping WUS-Capable UEs In an LTE system, a user equipment (UE) may determine a position at which the UE will monitor paging based on a paging occasion (PO) and paging frame (PF) determined based on its UE_ID. The same technical idea is applied to NB-IoT and MTC which have been newly introduced to the 3GPP LTE Rel-13 standard. A plurality of UEs may expect paging in one PO, and the number of the UEs may be determined according to a configuration in an SIB transmitted by a base station (BS). Hereinafter, a group of a plurality of UEs which may expect paging in the same PO will be defined as a UE-group-per-PO. A method of using a wake-up signal (WUS) for power saving of a UE has been introduced to the Rel-15 NB-IoT and MTC standard. In this method, a UE capable of using the WUS, that is, a WUS-capable UE attempts to detect the WUS based on information configured by a BS before monitoring a search space for paging. When the UE detects the WUS, the UE may expect transmission of paging in POs related to the position of detecting the WUS and monitor the search space for paging. When the UE fails to detect the WUS, the UE may not monitor (or skip monitoring) the search space for paging. The Rel-15 standard defines that a WUS transmission position is determined to be a position relative to a PO indicated by the WUS, and all WUS-capable UEs monitoring the same PO share the same WUS and the same WUS transmission position. Accordingly, when a WUS transmitted for a specific PO is present, all WUS-capable UEs in a UE-group-per-PO corresponding to the PO should perform paging monitoring. FIG.25illustrates an exemplary timing relationship between a WUS and a PO. A UE may receive WUS configuration information from a BS and monitor a WUS based on the WUS configuration information. More specifically, the UE receives the configuration information related to the WUS from the BS by higher-layer signaling. The UE monitors/receives the WUS from the BS during a configured maximum WUS duration. The WUS configuration information may include, for example, information about the maximum WUS duration, the number of consecutive POs related to the WUS, and a gap. The maximum WUS duration is a maximum time period during which the WUS is transmittable, which may be expressed as a ratio of a maximum repetition number (e.g., Rmax) related to a PDCCH. The WUS may be transmitted repeatedly one or more times during the maximum WUS duration. The number of POs related to the WUS is the number of POs in which the UE will not monitor a channel related to paging, when the UE fails to detect the WUS (or the number of POs in which the UE will monitor the channel related to paging, when the UE detects the WUS). The gap information indicates a time gap between the end of the maximum WUS duration and the first PO related to the WUS. A WUS duration may be short for a UE in good coverage and long for a UE in bad coverage. Upon detection of the WUS, a UE does not monitor the WUS until the first PO related to the WUS. The UE does not monitor the WUS either during a gap duration. Therefore, when the UE fails to detect the WUS during the maximum WUS duration, the UE does not monitor the channel related to paging in the POs related to the WUS (or the UE remains in sleep mode). Paging may be transmitted only to a part of the UEs of the same UE-group-per-PO according to determination of a mobility management entity (MME) or a BS (eNB or gNB). Because according to the current standard, information indicating UEs to which a WUS and paging are directed among the UEs of a UE-group-per-PO is delivered on an NPDSCH carrying paging traffic, some UEs may perform unnecessary NPDCCH/NPDSCH decoding. Particularly, for an NB-IoT UE and an MTC UE, a PDCCH (MPDCCH or NPDCCH) and PDSCH (or NPDSCH) for paging reception may be repeatedly transmitted and received tens of times to a few thousand times, for coverage enhancement. When paging is directed only to a part of the UEs of a UE-group-per-PO, UEs to which the paging is not directed may identify the absence of paging for the UEs only after decoding both of a PDCCH (MPDCCH or NPDCCH) and a related PDSCH (or NPDSCH) as well as after detecting the WUS. Accordingly, the UEs may suffer from much unnecessary power consumption due to the unnecessary operation of receiving the WUS, the PDCCH (MPDCCH or NPDCCH), and the related PDSCH (or NPDSCH). In light of the above problem, the present disclosure proposes criteria for applying a WUS based on UE sub-grouping and methods of configuring the UE sub-grouping, in order to reduce unnecessary paging monitoring of WUS-capable UEs. Each UE sub-group configured in the proposed methods of the present disclosure may be configured independently with a WUS distinguished by a time-domain resource, frequency-domain resource, and/or code-domain resource. In the following description, a specific time-domain resource, frequency-domain resource, and/or code-domain resource configurable for a specific UE sub-group to transmit and receive a WUS is referred to as a WUS resource. While the proposed methods of the present disclosure are described below in the context of NB-IoT and MTC, it is apparent that the same technical idea is generally applicable to any communication system. Further, while the proposed methods of the present disclosure are described in the context of a WUS indicating whether paging will be transmitted in IDLE mode, it is apparent that the same technical idea is generally applicable to any signal (or channel) used to indicate additional information about a channel (or signal) serving any purpose (e.g., information indicating whether the channel (or signal) is to be transmitted). Further, while the present disclosure is described based on an LTE standard (e.g., 3GPP technical specification 36 series), the present disclosure may be applied in the same/similar manner to a 5G/NR system. In this case, in relation to a frame structure, the term “subframe” may be replaced with “slot” (e.g., refer toFIGS.5and9and a related description) in the 5G/NR system. Although the proposed methods of the present disclosure may be performed independently of each other, it is apparent that they may be performed in combination, unless conflicting with each other. In the present disclosure, a WUS refers to a signal used to indicate whether a UE should monitor a PDCCH (MPDCCH or NPDCCH) to receive paging (in a specific cell). The WUS is associated with one or more POs according to whether extended discontinuous reception (DRX) is configured. A UE (which has received the WUS) may additionally perform the afore-described DRX operation and/or cell reselection operation. A more specific UE operation and BS operation related to reception of a WUS (e.g., MTC wake-up signal (MWUS) or narrowband wake-up signal (NWUS) may be summarized as follows and may apparently be described in relation to methods described later. (1) Base Station (BS) Operation A BS first generates a sequence (used) for a WUS in a specific subframe. For example, the BS may generate the sequence (used) for the WUS by using an equation defined in 3GPP technical specification (TS) 36.211 V15.2.0. More specifically, the sequence w(m) (used) for the WUS may be generated based on Equation 3. w(m)=θnf,ns(m′)·e-jπun(n+1)131m=0,1,…,131m′=m+132xn=mmod132Equation3θnf,ns(m′)={1,ifcnf,ns(2m′)=0andcnf,ns(2m′+1)=0-1,ifcnf,ns(2m′)=0andcnf,ns(2m′+1)=1j,ifcnf,ns(2m′)=1andcnf,ns(2m′+1)=0-j,ifcnf,ns(2m′)=1andcnf,ns(2m′+1)=1u=(NIDNcellmod126)+3 In Equation 3, x represents a subframe carrying the WUS, ranging from 0 to M−1 where M is the number of subframes carrying the WUS, corresponding to an actual WUS duration. Further, in Equation 3, e-jπun(n+1)131 represents a Zadoff-Chu (ZC) sequence and θnf,ns(m′) represents a complex-valued symbol related to a scrambling sequence. NIDNcellrepresents a physical layer cell identity (ID), and cnf,ns(i) represents a scrambling sequence which may have a sample length of 2*132M. Herein, i may range from 0 to 2*132M−1. The scrambling sequence may be given based on a Gold sequence. The BS maps the generated sequence to at least one resource element (RE), and transmits the WUS on the mapped RE(s) to a UE. In concept, the at least one RE may cover at least one of a time resource, a frequency resource, or an antenna port. (2) User Equipment (UE) Operation The UE receives the WUS from the BS (or the UE may assume that the WUS is transmitted on specific RE(s) from the BS) (e.g., refer to step S2604inFIG.26). The UE may then identify (or determine) whether paging will be received, based on the received WUS (e.g., refer to step S2606inFIG.26). When paging is transmitted, the UE receives the paging based on the afore-described paging reception-related operation, and performs an RRC idle mode-to-RRC connected mode transmission procedure. G.1 UE Sub-Grouping Criteria The present disclosure proposes a method of determining a condition for applying UE sub-grouping and configuring the UE sub-grouping by a base station and a method of recognizing and performing the UE sub-grouping by a UE, when the UE sub-grouping is applied to WUS transmission and reception. One or a combination of two or more of the following Method 1-1, Method 1-2, Method 1-3, Method 1-4, Method 1-5, Method 1-6, or Method 1-7 can be used as a method of performing the UE sub-grouping. [Method 1-1] Method of Performing UE Sub-Grouping for a WUS Based on UE_ID In Method 1-1, it is proposed that UE sub-grouping is performed for a WUS based on the UE_IDs of UEs. UE_ID is UE identification information based on an international mobile subscriber identity (IMSI). Characteristically, the definition of UE_ID used to determine a PO in 3GPP TS 36.304 V15.0.0. may be used for UE_ID herein. For example, when a P-RNTI is monitored on a PDCCH, UE_ID may be given as (IMSI mod 1024). When a P-RNTI is monitored on an NPDCCH, UE_ID may be given as (IMSI mod 4096). When a P-RNTI is monitored on an MPDCCH, UE_ID may be given as (IMSI mod 16394). Herein, mod represents a modulo operation. A PF, a PO, and a paging narrowband (PNB) are determined based on DRX parameters provided in system information according to Equation 4, Equation 5, and Equation 6. Specifically, the PF is determined by Equation 4. SFN modT=(TdivN)*(UE_ID modN) Equation 4 An index i_s indicating a PO from a paging-related subframe pattern is derived by Equation 5. i_s=floor(UE_ID/N)modNs[Equation 5] When the P-RNTI is monitored on the MPDCCH (or NPDCCH), the PNB is determined by Equation 6. PNB=floor(UE_ID/(N*Ns))modNnEquation 6 The parameters used in Equation 4, Equation 5, and Equation 6 are defined as follows, mod represents a modulo operation, floor represents a floor function, / represents division, * represents multiplication, div represents a function of obtaining a quotient, min(A, B) represents the smaller value among A and B, and max (A, B) represents the larger value among A and B. T: DRX cycle of the UE nB: 4T, 2T, T, T/2, T/4, T/8, T/16, T/32, T/64, T/128, and T/256, and for NB-IoT also T/512, and T/1024 N: min(T,nB) Ns: max(1,nB/T) Nn: number of paging narrowbands (for P-RNTI monitored on MPDCCH) or paging carriers (for P-RNTI monitored on NPDCCH) provided in system information Uniform Sub-Grouping Method As a characteristic example of Method 1-1, a method of uniformly distributing UE_IDs to UE sub-groups may be considered. In MTC, when the index of each UE sub-group is defined as cgbased on UE_IDs, cgmay be determined by Equation (Eq-1-1-a-MTC). In NB-IoT, when the index of each UE sub-group is defined as cgbased on UE_IDs, cgmay be determined by Equation (Eq-1-1-a-NB). In Equation (Eq-1-1-a-MTC) and Equation (Eq-1-1-a-NB), UE_ID, Ns, Nn, and W conform to the definitions of Section 7 of 3GPP TS 36.304 V 15.0.0 (e.g., refer to the description related to Equation 4, Equation 5, and Equation 6). NSGrepresents the number of deployed sub-groups. The UE may select a WUS resource (e.g., a time-domain resource, frequency-domain resource, and/or code-domain resource) corresponding to a UE sub-group index calculated by Equation (Eq-1-1-a-MTC) or Equation (Eq-1-1-a-NB) and monitor a WUS in the selected WUS resource. cg=floor(UE_ID/(N*NS*Nn))modNSG(Eq-1-1-a-MTC) cg=floor(UE_ID/(N*NS*W))modNSG(Eq-1-1-a-NB) When sub-group index 0 (cg=0) is used as an index for representing a common WUS (e.g., a WUS that all WUS-capable UEs may identify irrespective of UE sub-groups), Equation (Eq-1-1-a-MTC2) or Equation (Eq-1-1-a-NB2) may be used to prevent a specific UE sub-group from selecting subgroup index 0 (cg=0). cg=floor(UE_ID/(N*Ns*Nn))modNSG+1 (Eq-1-1-a-MTC2) cg=floor(UE_ID/(N*NS*W))modNSG+1 (Eq-1-1-a-NB2) Non-Uniform Sub-Grouping Method As another characteristic example of Method 1-1, a method of non-uniformly distributing UE_IDs to UE sub-groups may be considered. This may be intended to reduce the selection frequency of a WUS resource corresponding to a specific UE sub-group. For example, when a WUS corresponding to a specific UE sub-group shares the same resource with a legacy WUS (e.g., a WUS for a UE to which UE sub-grouping is not applied), the above operation may be intended to control effects on legacy WUS-capable UEs. In MTC, when the index of each UE sub-group is defined as cgbased on UE_IDs, cgmay be determined to be a smallest index cg(0≤cg≤NSG−1) satisfying Equation (Eq-1-1-b-MTC). In NB-IoT, cgmay be determined to be a smallest index cg(0≤cg≤NSG−1) satisfying Equation (Eq-1-1-b-NB). NSGrepresents the number of used sub-groups. In Equation (Eq-1-1-b-MTC) and Equation (Eq-1-1-b-NB), UE_ID, NS, Nn, and W are defined in Section 7 of 3GPP TS 36.304 V15.0.0 (e.g., refer to the descriptions of Equation 4, Equation 5, and Equation 6). In the following mathematical formula, WWUS(n) represents a weight for an nthUE sub-group, for non-uniformly distributing UE_IDs to UE sub-groups so that each UE sub-group includes a different number of UE_IDs, and WWUSrepresents the sum of the weights of all sub-groups. Accordingly, WWUS=WWUS(0)+WWUS(1)+ . . . +WWUS(NSG−1). floor(UE_ID/(N*NS*Nn))modWWUS<WWUS(0)+WWUS(1)+ . . . +WWUS(cg) (Eq-1-14MTC) floor(UE_ID/(N*NS*W))modWWUS<WWUS(0)+WWUS(1)+ . . . +WWUS(cg) (Eq-1-14NB) WWUS(n) corresponding to a specific index may be determined to be a weight for a sub-group sharing the same resource with a legacy WUS (e.g., WWUS(0)). When sub-group index 0 (cg=0) is used as an index indicating a common WUS (e.g., a WUS that all WUS-capable UEs may identify irrespective of UE sub-groups), Equation (Eq-1-1-b-MTC2) or Equation (Eq-1-1-b-NB2) may be used to prevent a specific UE sub-group from selecting subgroup index 0 (cg=0). floor(UE_ID/(N*NS*Nn))modWWUS<WWUS(1)+WWUS(2)+ . . . +WWUS(cg) (Eq-1-1-b-MTC2) floor(UE_ID/(N*NS*W))modWWUS<WWUS(1)+WWUS(2)+ . . . +WWUS(cg) (Eq-1-1-b-NB2) In the above mathematical formula, cgmay be determined to satisfy the condition that 1≤cg≤NSG. The values of WWUS(n) may be signaled by a system information block (SIB) or higher-layer signaling such as radio resource control (RRC) signaling. This signaling may be intended to adjust distribution of UE_IDs per sub-group according to a situation. For example, the base station (BS) may configure NSGweights for the respective sub-groups by an SIB. This operation may advantageously lead to flexible control of UE_ID distribution ratios across all sub-groups. In another example, the BS may configure a weight (e.g., WWUS(0)) for a sub-group sharing the same resource with a legacy WUS and a weight (e.g., WWUS(n), for all n not zero) for a sub-group using a different resource from the legacy WUS by an SIB. This operation may be intended to uniformly distribute UE_IDs among sub-groups using resources distinguished from resources for the legacy WUS, while variably controlling effects on the legacy WUS. In another example, the BS may configure a ratio between a weight for a sub-group sharing the same resource with the legacy WUS and a weight for a sub-group using a different resource from the legacy WUS by an SIB. This operation may advantageously reduce signaling overhead under the premise that the resources used for the legacy WUS are always used for a specific sub-group. Instead of the ratio between the two weights, the weight for the sub-group sharing the same resource with the legacy WUS may always be fixed to 1, while only the weight for the sub-group using a different resource from the legacy WUS may be configured. In another method of non-uniformly distributing UE_IDs to UE sub-groups, the indexes of the UE sub-groups may be determined by a method of uniformly distributing UE_IDs (e.g., Eq-1-1-a-MTC or Eq-1-1-a-NB), and a WUS resource corresponding to each sub-group index may be determined by an SIB or higher-layer signaling such as RRC signaling. Herein, when UE_IDs are non-uniformly distributed such that a plurality of sub-group indexes correspond to a specific WUS resource, the effect that the number of UE_IDs is non-uniform for each WUS resource may be expected. [Method 1-2] Method of Performing UE Sub-Grouping for a WUS Based on Coverage Levels. In Method 1-2, it is proposed that UE sub-grouping is performed for a WUS based on the coverage levels of UEs. The coverage level of a UE refers to the state of a wireless channel environment in which the UE is placed. In a characteristic example, a coverage level may be represented by, for example, a measurement such as reference signal received power (RSRP)/reference signal received quality (RSRQ) measured by the UE or a repetition number that the UE uses to transmit and receive an uplink (UL) or downlink (DL) channel. An RSRP/RSRQ value may be represented as quality information related a channel quality. In Method 1-2, when a UE identifies a change in its coverage level, the UE may indicate the change to a BS. In a characteristic example, when an RSRP/RSRQ value measured by the UE changes and thus does not satisfy the coverage level requirement of a current UE sub-group, the UE may indicate the change of the coverage level to the BS in a random access procedure. In a more specific example, the UE may use an idle-mode UL data transmission scheme such as early data transmission (EDT) to avoid unnecessary transition to the RRC connected mode. To ensure stable reporting of the coverage level of the UE, the BS may configure an additional RACH resource for coverage level reporting and indicate the configuration to the UE. [Method 1-3] Method of Performing UE Sub-Grouping for a WUS by Dedicated Signaling from a BS (eNB or gNB). In Method 1-3, when UE sub-grouping of UEs is indicated by UE-specific dedicated signaling, a method to be applied is proposed. In a specific method of applying Method 1-3, UE-specific dedicated signaling may be dedicated RRC signaling that a UE obtains during RRC connection setup or in the RRC connected mode. For this purpose, a UE may report information required for configuring UE sub-grouping (e.g., a coverage level, a type of service, a capability, and so on) on an NPUSCH. In another specific method of applying Method 1-3, UE-specific dedicated signaling may be information that the UE obtains in a step for Msg2 or Msg4 of an RACH procedure (or random access procedure). For this purpose, the UE may report information required for configuring UE sub-grouping (e.g., a coverage level, a type of service, a capability, and so on) in a step for Msg1 or Msg3. [Method 1-4] Method of Performing UE Sub-Grouping for a WUS Based on the Usage of a Corresponding Channel Indicated by the WUS. In Method 1-4, it is proposed that UE sub-grouping of UEs is applied based on a corresponding channel indicated by a WUS. The corresponding channel refers to a channel about which the WUS indicates information. Capability Report In a specific method of applying Method 1-4, for UE sub-grouping, the UE may report its capability for a corresponding channel supported by the UE. After the UE reports the capability, UE sub-grouping may be performed only when the BS provides the UE with additional signaling information. For example, the additional signaling information may be dedicated signaling as proposed in Method 1-3 or information that enables/disables WUS support for a specific corresponding channel obtainable in the RRC idle mode, such as an SIB. UE Behavior and Corresponding Channel Identification) In Method 1-4, after UE sub-grouping, the UE may monitor only a WUS corresponding to its UE sub-group. When the WUS indicates multiple corresponding channels, the UE may identify information about a corresponding channel by comparing bit information included in a subsequent control channel or masked RNTIs, or may finally confirm information about the corresponding channel on a data channel indicated by the subsequent control channel. Alternatively in Method 1-4, after the UE sub-grouping is determined, the UE may monitor all available WUSs that can be monitored, irrespective of a WUS corresponding to its UE sub-group and a UE sub-grouping capability. When a WUS indicates multiple corresponding channels, the UE may distinguish the corresponding channels by distinguishing WUS resources (e.g., time-domain, frequency-domain, and/or code-domain resources). In a characteristic example, the UE may simultaneously monitor a WUS serving a purpose other than paging, which is distinguishable by a sequence (and/or frequency) in a specific time resource (e.g., a subframe period determined by a gap from a PO and a maximum duration) in which the UE monitors a WUS for paging. The UE may determine how a subsequent corresponding channel will be transmitted, based on a detected WUS. Examples of Corresponding Channel In Method 1-4 Other Than Paging DCI In an example of Method 1-4, the defined corresponding channel may be a UL resource for a preconfigured UL transmission (e.g., semi-persistent scheduling (SPS)). A WUS for which UE sub-grouping has been performed may be used for activating/deactivating the use of the preconfigured UL resource or indicating an ACK/NACK or a retransmission for the preconfigured UL resource. In an example of Method 1-4, the defined corresponding channel may be a DL resource for a preconfigured UL transmission (e.g., SPS). A WUS for which UE sub-grouping has been performed may be used to indicate whether DCI providing information related to the preconfigured UL transmission is transmitted. In an example of Method 1-4, the defined corresponding channel may be DCI masked by a G-RNTI (or SC-RNTI) in single cell point to multipoint (SC-PTM). A WUS for which UE sub-grouping has been performed may be used to indicate whether DCI masked by a G-RNTI (or SC-RNTI) is transmitted or whether a single cell multicast transport channel (SC-MTCH)(or single cell multicast control channel (SC-MCCH)) has been modified. When a WUS indicates whether DCI masked by a G-RNTI is transmitted, different UE sub-groups may be configured in correspondence with different G-RNTIs. When both of DCI masked by an SC-RNTI and DCI masked by a G-RNTI are subjected to UE sub-grouping, different UE sub-groups may be configured in correspondence with the SC-RNTI and the G-RNTI. In an example of Method 1-4, the defined corresponding channel may have a multi-TB transmission structure. A WUS for which UE sub-grouping has been performed may be used to activate/deactivate the use of the multi-TB transmission structure. Alternatively, the WUS may be used to indicate whether a subsequent corresponding channel is in a DCI format supporting multi-TB transmission or a DCI format supporting single-TB transmission. Multi-TB transmission refers to a transmission structure in which a plurality of traffic channels (e.g., (N)PDCCH or (N)PUSCH) are scheduled by one DCI (or a preconfigured resource without DCI). [Method 1-5] Method of Performing UE Sub-Grouping for a WUS Only Based on a Cell (or Carrier) for which a UE has Obtained UE Sub-Grouping Information. In Method 1-5, it is proposed UE sub-grouping is applied only to a cell for which a UE has obtained UE sub-grouping information. In NB-IoT, when UE sub-grouping information is provided carrier-specifically, the term cell may be replaced with carrier. In a specific method of applying Method 1-5, when UE sub-grouping is applied according to specific criteria (e.g., UE_ID, a coverage level, dedicated signaling, a corresponding channel, and so on), a UE may perform a UE sub-grouping-related operation only for a cell for which the UE has been configured with UE sub-grouping information, skipping the UE sub-grouping-related operation for a cell for which the UE has not been configured with UE sub-grouping information. The UE may not expect a WUS-related operation until before obtaining UE sub-grouping information in an adjacent cell or a new cell, or may perform the WUS-related operation in a WUS resource (e.g., a WUS defined in Rel-15) which may be monitored UE-commonly irrespective of UE sub-grouping criteria. [Method 1-6] Method of Performing UE Sub-Grouping Based on a Time Passed after the Last UL Transmission and/or DL Reception. In Method 1-6, it is proposed that a UE is included in a specific UE sub-group based on a time of completing the last UL transmission and/or DL reception, and then switched to another UE sub-group a predetermined time later or skipping UE sub-grouping until before the next UL transmission and/or DL reception is completed. The proposed method may be useful when there is a low possibility that the UE will be paged during a predetermined time after transmitting or receiving traffic. In a specific method for which Method 1-6 is applied, Method 1-6 may be applied only to a case where the BS and the UE are capable of confirming transmission and reception of a channel to which the UL transmission and/or the DL reception is directed. For example, this case may correspond to a case in which the UE and the BS exchange information as is done in the EDT, a case in which whether a specific channel has been received may be feed backed through an HARQ-ACK channel, or a case of an RRC message. [Method 1-7] Method of Hopping the Sub-Group Index of a UE. In Method 1-7, it is proposed that when there is a fixed WUS resource corresponding to each sub-group index, the WUS sub-group index of a UE hops over time. This operation may be intended to prevent continuous performance degradation caused by the use of a specific WUS resource at a UE, when there is a difference in feature or gain between WUS resources used for sub-grouping. In a specific method of Method 1-7, the UE may determine that the sub-group index of a corresponding WUS hops in each PO. A selected sub-group index may be maintained unchanged during a time period in which a WUS transmission starts and is repeated. In a specific method of Method 1-7, when sub-group index hopping is determined by a system frame number (SFN), a parameter such as floor(SFN/T) may be used to achieve hopping effects. In a characteristic example, when a sub-group index is hopped every period of a DRX cycle, the value of T may be determined to be the value of the DRX cycle. Herein, floor( ) represents a floor function. In an example of Method 1-7, when the UE_ID-based uniform distribution method proposed in Method 1-1 and sub-group index hopping are applied, a sub-group index may be determined by Equation (Eq-1-7-a-MTC) for MTC, and Equation (Eq-1-7-a-NB) for NB-IoT. Alternatively, in an example of Method 1-7, when the UE_ID-based non-uniform distribution method proposed in Method 1-1 and sub-group index hopping are applied, a sub-group index may be determined by Equation (Eq-1-7-b-MTC) for MTC, and Equation (Eq-1-7-b-NB) for NB-IoT. In Equations (Eq-1-7-a-MTC), (Eq-1-7-a-NB), (Eq-1-7-b-MTC), and (Eq-1-7-b-NB), β is a parameter used to achieve sub-group index hopping effects, which is defined as a variable determined by a reference value distinguishable on the time axis. For example, when an SFN and a DRX cycle are used as references, it may be defined that β=floor(SFN/T). For the other parameters than β and operations, Equations (Eq-1-1-a-MTC), (Eq-1-1-a-NB), (Eq-1-1-b-MTC), and (Eq-1-1-b-NB) are used in the same manner. cg=[floor(UE_ID/(N*NS*Nn))+β] modNSG(Eq-1-7-a-MTC) cg=[floor(UE_ID/(N*NS*W))+β] modNSG(Eq-1-7-s-NB) [floor(UE_ID/(N*NS*Nn))+β] modWWUS<WWUS(0)+WWUS(1)+ . . . +WWUS(cg) (Eq-1-7-b-MTC) [floor(UE_ID/(N*NS*W))+β] modWWUS<WWUS(0)+WWUS(1)+ . . . +WWUS(cg) (Eq-1-7-b-NB) In another method to achieve the same effects as Method 1-7, a mapping relationship between sub-group indexes and WUS resources may be changed over time, with the sub-group index of a UE fixed. G.2 UE Sub-Grouping Configuration The present disclosure proposes a method of configuring related information by a base station (BS) and operations performed by a user equipment (UE), to apply UE sub-grouping to WUS transmission and reception. One or a combination of two or more of the following Method 2-1, Method 2-2, Method 2-3, or Method 2-4 may be used as a method of configuring UE sub-grouping. [Method 2-1] Unit of Applying U E Sub-Grouping Information In Method 2-1, when UE sub-grouping is configured, a method of determining a range to which the UE sub-grouping configuration is applied and related operations are proposed. In Method 2-1, a unit for which UE sub-grouping information is configured may be a cell. This may be intended to reduce signaling overhead. Alternatively, when hopping is applied to a WUS, this may be intended to maintain the same WUS configuration irrespective of the transmission position (e.g., narrowband or carrier) of the WUS. In Method 2-1, a unit for which UE sub-grouping information is configured may be a carrier in NB-IoT. Because a WUS is repeated a different number of times, power boosting is available or unavailable, or a different number of resources are available in each carrier, a carrier may be set as the unit in order to control the type of UE sub-grouping or the number of UE sub-groups, or enable/disable UE sub-grouping in consideration of the difference. In MTC, the term carrier may be replaced with narrowband. When frequency hopping is applied between narrowbands, a UE sub-grouping criterion may be determined to be a narrowband carrying a corresponding channel indicated by a WUS. In Method 2-1, a unit for which UE sub-grouping is configured may be a corresponding channel indicated by a WUS. For example, when UE sub-grouping is applied to paging, a carrier (or narrowband) for which UE sub-grouping is supported may be limited to a carrier carrying paging. Alternatively, for example, when UE sub-grouping is applied to SC-PTM, SPS, or multi-TB transmission, UE sub-grouping may be performed only on a carrier (or narrowband) in which a transmission and reception structure for each purpose is operated. [Method 2-2] Method of Determining Whether UE Sub-Grouping is Applied According to the Gap Capability of a UE. In Method 2-2, it is proposed that UE sub-grouping configurations are differentiated according to the WUS-to-PO gap capabilities of UEs. A WUS-to-PO gap capability of a UE refers to a UE capability used to determine the size of a gap configured between the ending subframe of a WUS and a PO and may be defined as in 3GPP TS 36.304 V15.0.0. In a specific method of applying Method 2-2, a configuration related to UE sub-grouping may be independently set for each WUS-to-PO gap capability. For example, a higher-layer signal carrying UE sub-grouping-related configuration information may be designed to have an independent field for each WUS-to-PO gap capability. In a specific method of applying Method 2-2, UE sub-grouping may not be applied to a UE having a specific WUS-to-PO gap capability. For example, UE sub-grouping may not be applied to a large gap-capable UE (e.g., a UE configurable with a WUS-to-PO gap of {1s, 2s} in an eDRX situation). Alternatively, in a contrary example, UE sub-grouping may not be applied to a short gap-capable UE (e.g., a UE unconfigurable with the WUS-to-PO gap of {1s, 2s} in the eDRX situation). Considering that the implementation complexity and performance of a WUS detector may be different according to a WUS-to-PO gap capability, the method proposed in Method 2-2 may be intended to reduce an increase in UE complexity for UE sub-grouping or the degradation of WUS detection performance for a UE having a capability with a relatively low requirement (e.g., a larger cap capability). Alternatively, the method may be intended to reduce the degradation of WUS detection performance caused by UE sub-grouping for a UE having a shorter gap capability, to secure a sufficient time required to prepare for monitoring a corresponding channel after fast WUS detection. [Method 2-3] Method of Determining Whether UE Sub-Grouping is Applied According to the Size of a Gap Configured by a BS In Method 2-3, it is proposed that UE sub-grouping configurations are differentiated according to a configured size of a WUS-to-PO gap. The size of a WUS-to-PO gap refers to the size of a gap configured between the ending subframe of a WUS and a PO, and may be defined as in 3GPP TS 36.304 V15.0.0. That is, a gap mentioned in Method 2-3 may be a gap illustrated in the afore-described drawing (e.g.,FIG.25) illustrating a WUS timing. In a specific method of applying Method 2-3, a configuration related to UE sub-grouping may be independently set for each WUS-to-PO gap size. For example, a BS may configure two or more gaps corresponding to one PO, and a higher-layer signal carrying UE sub-grouping-related configuration information may be designed to have an independent field for each WUS-to-PO gap size. In a specific method of applying Method 2-3, UE sub-grouping may not be applied for a specific WUS-to-PO gap size. For example, UE sub-grouping may not be applied to a larger gap (e.g., a gap size of {1s, 2s} configured in an eDRX situation). This is because for a larger gap, a separate WUS receiver operating with low complexity may be applied, and in this case, the degradation of WUS performance caused by UE sub-grouping may be relatively serious. Alternatively, in a contrary example, UE sub-grouping may not be applied to a shorter gap (e.g., a configured gap size of {40 ms, 80 ms, 160 ms, 240 ms}). This may be intended to secure an extra spacing by shortening an actual transmission duration instead of performing UE sub-grouping because there is a relative shortage of an extra spacing between a WUS and a PO. In another specific method of applying Method 2-3, UE sub-grouping may be applied depending on whether a UE performs an eDRX operation. For example, UE sub-grouping may not be applied in eDRX. This is intended to prevent the degradation of WUS detection performance caused by UE sub-grouping because missed paging may lead to a fatal delay to the next paging transmittable time in eDRX. Alternatively, in another method for the same purpose, a separate configuration may be used, which distinguishes UE sub-grouping for an eDRX operation from UE sub-grouping for a DRX operation. [Method 2-4] Method of Reporting Information Related to its Mobility for UE Sub-Grouping by a UE In Method 2-4, it is proposed that a UE reports information related to its mobility for UE sub-grouping. The mobility may mean a change in a communication channel environment, caused by movement of the UE to another physical position. In a specific method of applying Method 2-4, the UE may autonomously determine whether to perform UE sub-grouping based on its mobility and report the determination to the BS. In the presence of a UE sub-grouping request report based on the mobility of the UE, the BS may transmit a WUS by applying a UE sub-grouping-related operation for the UE. The UE may identify that the UE sub-grouping operation is possible at a transmission position at which the UE expects a WUS, and perform the UE sub-grouping-related operation after transmitting a UE sub-groping-capable report based on its mobility to the BS. Alternatively, the UE may start UE sub-grouping after receiving separate confirmation signaling for the report. In this method, (1) a reference predetermined in a standard or (2) a reference configurable by higher-layer signaling from the BS may be used as reference mobility for determining whether to perform UE sub-grouping by the UE. In a specific method of applying Method 2-4, the UE may report information about its mobility to the BS, and the BS may determine whether UE sub-grouping is to be performed based on the report and configure the determination result for the UE. After reporting the information about its measured mobility, the UE may expect signaling indicating whether UE sub-grouping is to be performed from the BS. Upon acquisition of information related to UE sub-grouping, the UE may determine whether to apply UE sub-grouping according to the received information. Whether the UE fails to acquire the information about UE sub-grouping, the UE may monitor a common WUS (e.g., a WUS identifiable by all WUS-capable UEs irrespective of UE sub-groups), without expecting a UE sub-grouping-related operation. Characteristically in applying Method 2-4, when the BS operates UE sub-grouping based on a plurality of criteria or purposes, the mobility-based report may be restrictively reflected in specific UE sub-grouping criteria. For example, because the coverage level of a UE with mobility may change over time, it may be determined whether coverage level-based UE sub-grouping is to be applied according to a mobility-based report. In contrast, a criterion such as UE_ID is applicable without much relation to the mobility of a UE, UE_ID-based UE sub-grouping may always be applied irrespective of the mobility-based report information. G.3 Flowcharts of Methods of the Present Disclosure FIG.26is an exemplary flowchart illustrating a method of the present disclosure. While the example ofFIG.26is described in the context of a user equipment (UE), an operation corresponding to the operation illustrated inFIG.26may be performed by a base station (BS). As described before, Method 1-1 to Method 1-7 of the present disclosure may be performed independently, or in combination of one or more of them. In step S2602, a UE may determine a WUS resource based on UE sub-grouping for a WUS. For example, in step S2602, the UE may determine index information (e.g., UE sub-group index information cg) indicating a WUS resource based on identification information (e.g., UE_ID) of the UE and determine a WUS resource related to a sub-group of the UE based on the determined index information (e.g., refer to the description of Method 1-1). For example, when the UE supports MTC, the index information indicating the WUS resource may be determined based on the identification information (e.g., UE_ID) of the UE, parameters (e.g., N and Ns) related to a DRX cycle of the UE, information (e.g., Nn) about the number of paging narrowbands, and information (e.g., NSG) about the number of UE groups for the WUS (e.g., refer to Eq-1-1-a-MTC). When the UE supports MTC, the index information indicating the WUS resource may be determined based on the identification information (e.g., UE_ID) of the UE, the parameters (e.g., N and Ns) related to the DRX cycle of the UE, the information (e.g., Nn) about the number of paging narrowbands, and information (e.g., WWUS) about the sum of weights of all UE sub-groups (e.g., refer to Eq-1-1-b-MTC). In another example, when the UE supports NB-IoT, the index information indicating the WUS resource may be determined based on the identification information (e.g., UE_ID) of the UE, the parameters (e.g., N and Ns) related to the DRX cycle of the UE, information about the sum (e.g., W) of weights of paging carriers, and the information (e.g., NSG) about the number of UE groups for the WUS (e.g., refer to Eq-1-1-a-NB). Alternatively, when the UE supports NB-IoT, the index information indicating the WUS resource may be determined based on the identification information (e.g., UE_ID) of the UE, the parameters (e.g., N and Ns) related to the DRX cycle of the UE, the information about the sum (e.g., W) of the weights of the paging carriers, and the information (e.g., WWUS) about the sum of the weights of all UE sub-groups (e.g., refer to Eq-1-1-b-NB). Independently or additionally, the UE may determine a WUS resource based on a coverage level (e.g., refer to Method 1-2) in step S2602. For example, the coverage level of a UE refers to the state of a wireless channel environment in which the UE is placed. In a characteristic example, a measurement such as a UE-measured RSRP/RSRQ or a repetition number used for the UE to transmit a UL channel or receive a DL channel may be used as the coverage level. Independently or additionally, in step S2602, the UE may receive UE-specific dedicated signaling from the BS. When the dedicated signaling indicates UE sub-grouping, the UE may report information for configuring UE sub-grouping (e.g., a coverage level, a type of service, a capability, and so on) via a PUSCH (e.g., NPUSCH), Msg1, or Msg3 (e.g., refer to Method 1-3). Independently or additionally, in step S2602, the UE may determine a WUS resource only for a cell (or carrier) for which the UE has acquired UE sub-grouping information, based on UE sub-grouping (e.g., refer to Method 1-5). Independently or additionally, in step S2602, the UE may determine a UE sub-group and a WUS resource corresponding to the UE sub-group, based on a time of completing the last UL transmission and/or DL reception (e.g., refer to Method 1-6). Independently or additionally, in step S2602, UE sub-group index information and/or a WUS resource corresponding to the UE sub-group index information may hop over time by the UE (e.g., refer to Method 1-7). More specifically, the UE sub-group index information and/or the WUS resource corresponding to the UE sub-group index information may be determined based on an SFN (e.g., refer to Method 1-7). Independently or additionally, the WUS may be used to indicate transmission and reception of a channel as well as a paging signal. The UE may determine a WUS resource based on the channel (e.g., corresponding channel) indicated by the WUS (e.g., refer to Method 1-4). In this case, the UE may report a capability for a channel (e.g., corresponding channel) supported for UE sub-grouping to the BS, and the BS may indicate to the UE to determine a WUS resource based on UE sub-grouping by separate signaling information (e.g., refer to Method 1-4). In step S2604, the UE may monitor a WUS based on the WUS resource. For example, the UE may monitor the WUS based on the index information (e.g., the UE sub-group index information cg) determined in step S2602(or based on the WUS resource indicated by the index information) (e.g., refer to Method 1-1). Alternatively, for example, the UE may monitor the WUS based on a WUS resource corresponding to the coverage level determined in step S2602(e.g., refer to Method 1-2). Independently or additionally, when the index information indicating a WUS resource (e.g., the UE sub-group index information cg) (and/or the WUS resource corresponding to the index information) hops over time, the UE may monitor the WUS based on the hopped index information (and/or the WUS resource corresponding to the hopped index information) (e.g., refer to Method 1-7). Upon detection of the WUS in step S2604, the UE may receive a paging signal in a PO related to the detected WUS in step S2606. As described before, the WUS may be used to indicate whether a paging signal will be transmitted and received, and also whether a channel (e.g., corresponding channel) other than the paging signal will be transmitted and received (e.g., refer to Method 1-4). For example, the channel (e.g., corresponding channel) related to the WUS may be a UL resource for a preconfigured UL transmission (e.g., SPS), a DL resource for a preconfigured DL transmission (e.g., SPS), DCI masked by a G-RNTI (or SC-RNTI) in SC-PTM, an SC-MTCH (or SC-MCCH), and/or a channel of a multi-TB transmission structure (refer to Method 1-4). When multiple channels (e.g., corresponding channels) are related to the WUS, the UE may determine and receive the channel related to the WUS based on bit information included in a control channel, an RNTI by which the control channel is masked, information received on a data channel indicated by the control channel, and/or the WUS resource (e.g., refer to Method 1-4). When the UE fails to detect the WUS in step S2604, the UE may skip reception of a paging signal related to the WUS in step S2606. The UE (which has received the WUS) may additionally perform the afore-described DRX operation and/or cell reselection operation. The operations described in Method 1- to Method 1-7 and/or a combination thereof may be performed in the steps ofFIG.26, and the description of Method 1-1 to Method 1-7 is incorporated by reference in the description ofFIG.26in its entirety. G.4 Communication System and Devices to Which the Present Disclosure is Applied Various descriptions, functions, procedures, proposals, methods, and/or flowcharts of the present disclosure may be applied to, but not limited to, various fields requiring wireless communication/connection (e.g., 5G) among devices. Hereinafter, they will be described in more detail with reference to the drawings. In the following drawings/description, the same reference numerals may denote the same or corresponding hardware blocks, software blocks, or functional blocks, unless specified otherwise. FIG.27illustrates a communication system1applied to the present disclosure. Referring toFIG.27, the communication system1applied to the present disclosure includes wireless devices, base stations (BSs), and a network. The wireless devices refer to devices performing communication by radio access technology (RAT) (e.g., 5G New RAT (NR) or LTE), which may also be called communication/radio/5G devices. The wireless devices may include, but no limited to, a robot100a, vehicles100b-1and100b-2, an extended reality (XR) device100c, a hand-held device100d, a home appliance100e, an IoT device100f, and an artificial intelligence (AI) device/server400. For example, the vehicles may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing vehicle-to-vehicle (V2V) communication. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR)/virtual reality (VR)/mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television (TV), a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and so on. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smart glasses), and a computer (e.g., a laptop). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smart meter. For example, the BSs and the network may be implemented as wireless devices, and a specific wireless device200amay operate as a BS/network node for other wireless devices. The wireless devices100ato100fmay be connected to the network300via the BSs200. An AI technology may be applied to the wireless devices100ato100f, and the wireless devices100ato100fmay be connected to the AI server400via the network300. The network300may be configured by using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices100ato100fmay communicate with each other through the BSs200/network300, the wireless devices100ato100fmay perform direct communication (e.g., sidelink communication) with each other without intervention of the BSs/network. For example, the vehicles100b-1and100b-2may perform direct communication (e.g. V2V/vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices100ato100f. Wireless communication/connections150a,150b, or150cmay be established between the wireless devices100ato100fand the BSs200, or between the BSs200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as UL/DL communication150a, sidelink communication150b(or, D2D communication), or inter-BS communication150c(e.g. relay, integrated access backhaul (IAB)). A wireless device and a BS/a wireless devices, and BSs may transmit/receive radio signals to/from each other through the wireless communication/connections150a,150b, and150c. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure. FIG.28illustrates wireless devices applicable to the present disclosure. Referring toFIG.28, a first wireless device100and a second wireless device200may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, (the first wireless device100and the second wireless device200) may correspond to (the wireless devices100ato100fand the BSs200) and/or (the wireless devices100ato100fand the wireless devices100ato100f) ofFIG.27. The first wireless device100may include at least one processor102and at least one memory104, and may further include at least one transceiver106and/or at least one antenna108. The processor102may control the memory104and/or the transceiver106and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor102may process information within the memory104to generate first information/signal and then transmit a radio signal including the first information/signal through the transceiver106. The processor102may receive a radio signal including second information/signal through the transceiver106and then store information obtained by processing the second information/signal in the memory104. The memory104may be coupled to the processor102and store various types of information related to operations of the processor102. For example, the memory104may store software code including commands for performing a part or all of processes controlled by the processor102or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor102and the memory104may be a part of a communication modem/circuit/chip designed to implement an RAT (e.g., LTE or NR). The transceiver106may be coupled to the processor102and transmit and/or receive radio signals through the at least one antenna108. The transceiver106may include a transmitter and/or a receiver. The transceiver106may be interchangeably used with an RF unit. In the present disclosure, a wireless device may refer to a communication modem/circuit/chip. The second wireless device200may include at least one processor202and at least one memory204, and may further include at least one transceiver206and/or at least one antenna208. The processor202may control the memory204and/or the transceiver206and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor202may process information within the memory204to generate third information/signal and then transmit a radio signal including the third information/signal through the transceiver206. The processor202may receive a radio signal including fourth information/signal through the transceiver206and then store information obtained by processing the fourth information/signal in the memory204. The memory204may be coupled to the processor202and store various types of information related to operations of the processor202. For example, the memory204may store software code including commands for performing a part or all of processes controlled by the processor202or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor202and the memory204may be a part of a communication modem/circuit/chip designed to implement an RAT (e.g., LTE or NR). The transceiver206may be coupled to the processor202and transmit and/or receive radio signals through the at least one antenna208. The transceiver206may include a transmitter and/or a receiver. The transceiver206may be interchangeably used with an RF unit. In the present disclosure, a wireless device may refer to a communication modem/circuit/chip. Hereinafter, hardware elements of the wireless devices100and200will be described in greater detail. One or more protocol layers may be implemented by, but not limited to, one or more processors102and202. For example, the one or more processors102and202may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors102and202may generate one or more protocol data units (PDUs) and/or one or more service data units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers106and206. The one or more processors102and202may receive the signals (e.g., baseband signals) from the one or more transceivers106and206and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors102and202may be implemented in hardware, firmware, software, or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented in firmware or software, which may be configured to include modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors102and202, or may be stored in the one or more memories104and204and executed by the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented as code, instructions, and/or a set of instructions in firmware or software. The one or more memories104and204may be coupled to the one or more processors102and202and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories104and204may be configured as read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories104and204may be located at the interior and/or exterior of the one or more processors102and202. The one or more memories104and204may be coupled to the one or more processors102and202through various technologies such as wired or wireless connection. The one or more transceivers106and206may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers106and206may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers106and206may be coupled to the one or more processors102and202and transmit and receive radio signals. For example, the one or more processors102and202may control the one or more transceivers106and206to transmit user data, control information, or radio signals to one or more other devices. The one or more processors102and202may control the one or more transceivers106and206to receive user data, control information, or radio signals from one or more other devices. The one or more transceivers106and206may be coupled to the one or more antennas108and208and configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas108and208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers106and206may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors102and202. The one or more transceivers106and206may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors102and202from the base band signals into the RF band signals. To this end, the one or more transceivers106and206may include (analog) oscillators and/or filters. FIG.29illustrates another example of wireless devices applied to the present disclosure. The wireless devices may be implemented in various forms according to use-cases/services (refer toFIG.27). Referring toFIG.29, wireless devices100and200may correspond to the wireless devices100and200ofFIG.28and may be configured as various elements, components, units/portions, and/or modules. For example, each of the wireless devices100and200may include a communication unit110, a control unit120, a memory unit130, and additional components140. The communication unit may include a communication circuit112and transceiver(s)114. For example, the communication circuit112may include the one or more processors102and202and/or the one or more memories104and204ofFIG.28. For example, the transceiver(s)114may include the one or more transceivers106and206and/or the one or more antennas108and208ofFIG.28. The control unit120is electrically coupled to the communication unit110, the memory unit130, and the additional components140and provides overall control to operations of the wireless devices. For example, the control unit120may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit130. The control unit120may transmit the information stored in the memory unit130to the outside (e.g., other communication devices) via the communication unit110through a wireless/wired interface or store, in the memory unit130, information received through the wireless/wired interface from the outside (e.g., other communication devices) via the communication unit110. The additional components140may be configured in various manners according to the types of wireless devices. For example, the additional components140may include at least one of a power unit/battery, an input/output (I/O) unit, a driver, and a computing unit. The wireless device may be configured as, but not limited to, the robot (100aofFIG.27), the vehicles (100b-1and100b-2ofFIG.27), the XR device (100cofFIG.27), the hand-held device (100dofFIG.27), the home appliance (100eofFIG.27), the IoT device (100fofFIG.27), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400ofFIG.27), the BSs (200ofFIG.27), a network node, etc. The wireless device may be mobile or fixed according to a use-case/service. InFIG.29, all of the various elements, components, units/portions, and/or modules in the wireless devices100and200may be coupled to each other through a wired interface or at least a part thereof may be wirelessly coupled to each other through the communication unit110. For example, in each of the wireless devices100and200, the control unit120and the communication unit110may be coupled wiredly, and the control unit120and first units (e.g.,130and140) may be wirelessly coupled through the communication unit110. Each element, component, unit/portion, and/or module within the wireless devices100and200may further include one or more elements. For example, the control unit120may be configured as a set of one or more processors. For example, the control unit120may be configured as a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphical processing unit, and a memory control processor. In another example, the memory unit130may be configured as a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof. An implementation example ofFIG.29will be described in detail with reference to the drawings. FIG.30illustrates a portable device applied to the present disclosure. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smart watch and smart glasses), and a portable computer (e.g., a laptop). The portable device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT). Referring toFIG.30, a portable device100may include an antenna unit108, a communication unit110, a control unit120, a power supply unit140a, an interface unit140b, and an I/O unit140c. The antenna unit108may be configured as a part of the communication unit110. The blocks110to130/140ato140ccorrespond to the blocks110to130/140ofFIG.29, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from another wireless device and a BS. The control unit120may perform various operations by controlling elements of the portable device100. The control unit120may include an application processor (AP). The memory unit130may store data/parameters/programs/code/commands required for operation of the portable device100. Further, the memory unit130may store input/output data/information. The power supply unit140amay supply power to the portable device100, and include a wired/wireless charging circuit and a battery. The interface unit140bmay include various ports (e.g., an audio I/O port and a video I/O port) for connectivity to external devices The I/O unit140cmay acquire information/signals (e.g., touch, text, voice, images, and video) input by a user, and store the acquired information/signals in the memory unit130. The communication unit110may receive or output video information/signal, audio information/signal, data, and/or information input by the user. The I/O unit140cmay include a camera, a microphone, a user input unit, a display140d, a speaker, and/or a haptic module. For example, for data communication, the/O unit140cmay acquire information/signals (e.g., touch, text, voice, images, and video) received from the user and store the acquired information/signal sin the memory unit130. The communication unit110may convert the information/signals to radio signals and transmit the radio signals directly to another device or to a BS. Further, the communication unit110may receive a radio signal from another device or a BS and then restore the received radio signal to original information/signal. The restored information/signal may be stored in the memory unit130and output in various forms (e.g., text, voice, an image, video, and a haptic effect) through the I/O unit140c. FIG.31illustrates a vehicle or an autonomous driving vehicle applied to the present disclosure. The vehicle or autonomous driving vehicle may be configured as a mobile robot, a car, a train, a manned/unmanned aerial vehicle (AV), a ship, or the like. Referring toFIG.31, a vehicle or autonomous driving vehicle100may include an antenna unit108, a communication unit110, a control unit120, a driving unit140a, a power supply unit140b, a sensor unit140c, and an autonomous driving unit140d. The antenna unit108may be configured as a part of the communication unit110. The blocks110/130/140ato140dcorrespond to the blocks110/130/140ofFIG.29, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit120may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle100. The control unit120may include an ECU. The driving unit140amay enable the vehicle or the autonomous driving vehicle100to travel on a road. The driving unit140amay include an engine, a motor, a powertrain, a wheel, a brake, a steering device, and so on. The power supply unit140bmay supply power to the vehicle or the autonomous driving vehicle100and include a wired/wireless charging circuit, a battery, and so on. The sensor unit140cmay acquire vehicle state information, ambient environment information, user information, and so on. The sensor unit140cmay include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, and so on. The autonomous driving unit140dmay implement a technology for maintaining a lane on which a vehicle is driving, a technology for automatically adjusting speed, such as adaptive cruise control, a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a path, when a destination is set, and the like. For example, the communication unit110may receive map data, traffic information data, and so on from an external server. The autonomous driving unit140dmay generate an autonomous driving path and a driving plan from the obtained data. The control unit120may control the driving unit140asuch that the vehicle or autonomous driving vehicle100may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit110may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit140cmay obtain vehicle state information and/or ambient environment information. The autonomous driving unit140dmay update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit110may transmit information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology or the like, based on the information collected from vehicles or autonomous driving vehicles and provide the predicted traffic information data to the vehicles or the autonomous driving vehicles. FIG.32illustrates an exemplary vehicle applied to the present disclosure. The vehicle may be configured as a transportation means, a train, an aircraft, a ship, or the like. Referring toFIG.32, a vehicle100may include a communication unit110, a control unit120, a memory unit130, an I/O unit140a, and a positioning unit140b. The blocks110to130/140aand140bcorrespond to the blocks110to130/140ofFIG.29. The communication unit110may transmit and receive signals (e.g., data, control signals, and so on) to and from external devices such as other vehicles or a BS. The control unit120may perform various operations by controlling the components of the vehicle100. The memory unit130may store data/parameters/programs/code/commands supporting various functions of the vehicle100. The I/O unit140amay output an AR/VR object based on information in the memory unit130. The I/O unit140amay include an HUD. The positioning unit140bmay acquire position information about the vehicle100. The position information may include absolute position information, information about a position within a lane, acceleration information, information about a position relative to a neighbor vehicle, and so on of the vehicle100. The positioning unit140bmay include a GPS and various sensors. For example, the communication unit110of the vehicle100may receive map information and traffic information from an external server and store the received information in the memory unit130. The positioning unit140bmay acquire vehicle position information through the GPS and various sensors and store the acquired vehicle position information in the memory unit130. The control unit120may generate a virtual object based on the map information, traffic information, and vehicle position information, and the I/O unit140amay display the generated virtual object on a window in the vehicle (140mand140n). Further, the control unit120may determine whether the vehicle100is traveling normally within a lane based on the vehicle position information. When the vehicle100is abnormally outside the lane, the control unit120may display a warning on a window in the vehicle via the I/O unit140a. Further, the control unit130may broadcast a warning message about the abnormal driving to neighboring vehicles. Under circumstances, the control unit120may transmit position information about the vehicle and information about a driving/vehicle abnormality to an authority through the communication unit110. The embodiments of the present disclosure described hereinbelow are combinations of elements and features of the present disclosure. The elements or features may be considered selective unless otherwise mentioned. Each element or feature may be practiced without being combined with other elements or features. Further, an embodiment of the present disclosure may be constructed by combining parts of the elements and/or features. Operation orders described in embodiments of the present disclosure may be rearranged. Some constructions or features of any one embodiment may be included in another embodiment and may be replaced with corresponding constructions or features of another embodiment. It is obvious to those skilled in the art that claims that are not explicitly cited in each other in the appended claims may be presented in combination as an embodiment of the present disclosure or included as a new claim by a subsequent amendment after the application is filed. The present disclosure is applicable to wireless communication devices such as a user equipment (UE) and a base station (BS) operating in various wireless communication systems including 3GPP LTE/LTE-A/5G (or New RAT (NR)). | 141,729 |
11943715 | DETAILED DESCRIPTION In some wireless communications systems, a network device such as a base station, a transmission reception point (TRP), or some other network device may transmit one or more channel state information (CSI) reference signals (CSI-RSs) to a user equipment (UE) for the purpose of channel sounding. A UE may receive one or more CSI-RSs and measure one or more characteristics of a channel over which the CSI-RS was transmitted. The UE may be configured to transmit, to the network device, a feedback report (e.g., a CSI report, a channel state feedback (CSF) report) associated with the one or more received CSI-RSs. In some cases, the UE may receive an indication of a configuration for transmitting the feedback report. For example, the UE may receive an indication of one or more CSI-RS resources to monitor for, and/or a type of CSI measurements to perform on received CSI-RSs. Accordingly, the feedback report may be based on the indicated configuration. In recent years there has been a growing concern over the power consumed by cellular networks due to environmental factors such as carbon emissions. As a result, network energy efficiency becomes increasingly important. Accordingly, in some cases, a wireless network device may turn off one or more antenna panels (or sub-panels) so as to reduce energy consumption. For example, a wireless network device may switch from a full-duplex mode to a half-duplex mode, such as when the wireless network device detects low traffic and/or activity in the cell. In some implementations, a wireless network device may dynamically adapt an antenna configuration in accordance with an energy saving mode and may signal such adaptation to one or more UEs. By signaling such adaption to the one or more UEs, the one or more UEs may determine how to receive signals from the wireless network device and/or how to transmit feedback to the wireless network device. In some cases, such energy saving procedure may impact a CSI procedure. For example, by dynamically de-activating (e.g., turning off) one or more antenna panels, the wireless network device may reduce a number of CSI-RS resources and/or a number of CSI-RS ports over which the wireless network device may transmit CSI-RSs, which may impact a UEs reception of such CSI-RSs and/or a UEs configuration of a CSI feedback report. As such, a wireless network device may transmit an indication of an energy saving mode the wireless network device is using and an indication of the energy saving mode may impact a CSI procedure. For example, a wireless network device may be configured with a set of energy saving modes where each mode may be associated with a number of CSI-RS ports per CSI-RS resource, a number of CSI-RS resources, a number of antenna panels (or subpanels) being used by the wireless network device, or a combination thereof. The wireless network device may signal to a UE the set of energy saving modes. Then, a wireless network device may switch to one of the energy saving modes from the set (where the wireless network device may reduce a number of CSI-RS ports, reduce a number of CSI-RS resources, reduce number of panels or sub-panels) and indicate, to the UE, the energy saving mode the base station switched to. Accordingly, the UE may monitor for CSI-RSs in the appropriate resources and provide channel state information feedback in accordance with the energy saving mode. Particular aspects of the subject matter described herein may be implemented to realize one or more advantages. The described techniques may support improvements in CSI measurement and reporting by improving reliability, improving coordination between network device, and decreasing energy consumption, among other advantages. As such, supported techniques may include improved network operations and, in some examples, may promote network efficiencies, among other benefits. Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects are then described with reference to energy saving mode configurations, and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for configuring use of an energy saving mode. FIG.1illustrates an example of a wireless communications system100that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The wireless communications system100may include one or more base stations105, one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communications system100may support enhanced broadband communications, ultra-reliable communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof. The base stations105may be dispersed throughout a geographic area to form the wireless communications system100and may be devices in different forms or having different capabilities. The base stations105and the UEs115may wirelessly communicate via one or more communication links125. Each base station105may provide a coverage area110over which the UEs115and the base station105may establish one or more communication links125. The coverage area110may be an example of a geographic area over which a base station105and a UE115may support the communication of signals according to one or more radio access technologies. The UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. The UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115, the base stations105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown inFIG.1. The base stations105may communicate with the core network130, or with one another, or both. For example, the base stations105may interface with the core network130through one or more backhaul links120(e.g., via an S1, N2, N3, or other interface). The base stations105may communicate with one another over the backhaul links120(e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations105), or indirectly (e.g., via core network130), or both. In some examples, the backhaul links120may be or include one or more wireless links. One or more of the base stations105described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology. A UE115may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE115may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE115may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as the base stations105and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown inFIG.1. The UEs115and the base stations105may wirelessly communicate with one another via one or more communication links125over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links125. For example, a carrier used for a communication link125may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements that a UE115receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE115. A wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE115. The time intervals for the base stations105or the UEs115may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, where Δfmaxmay represent the maximum supported subcarrier spacing, and Nfmay represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023). Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation. A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system100and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)). Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs115. For example, one or more of the UEs115may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs115and UE-specific search space sets for sending control information to a specific UE115. In some examples, a base station105may be movable and therefore provide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas110associated with different technologies may overlap, but the different geographic coverage areas110may be supported by the same base station105. In other examples, the overlapping geographic coverage areas110associated with different technologies may be supported by different base stations105. The wireless communications system100may include, for example, a heterogeneous network in which different types of the base stations105provide coverage for various geographic coverage areas110using the same or different radio access technologies. The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC). The UEs115may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein. In some examples, a UE115may also be able to communicate directly with other UEs115over a device-to-device (D2D) communication link135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs115utilizing D2D communications may be within the geographic coverage area110of a base station105. Other UEs115in such a group may be outside the geographic coverage area110of a base station105or be otherwise unable to receive transmissions from a base station105. In some examples, groups of the UEs115communicating via D2D communications may utilize a one-to-many (1:M) system in which each UE115transmits to every other UE115in the group. In some examples, a base station105facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs115without the involvement of a base station105. The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs115served by the base stations105associated with the core network130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services150for one or more network operators. The IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service. Some of the network devices, such as a base station105, may include subcomponents such as an access network entity140, which may be an example of an access node controller (ANC). Each access network entity140may communicate with the UEs115through one or more other access network transmission entities145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs). Each access network transmission entity145may include one or more antenna panels. In some configurations, various functions of each access network entity140or base station105may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station105). The wireless communications system100may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs115located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz. The wireless communications system100may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communications system100may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as the base stations105and the UEs115may employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples. A base station105or a UE115may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station105or a UE115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a base station105may be located in diverse geographic locations. A base station105may have an antenna array with a number of rows and columns of antenna ports that the base station105may use to support beamforming of communications with a UE115. Likewise, a UE115may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port. Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station105, a UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation). In some wireless communications systems, such as wireless communications system100, a base station105(or a transmission reception point (TRP) of a base station105) may determine or be configured with a set of energy saving modes, where each energy saving mode may impact how the base station105transmits CSI-RSs. For example, each energy saving mode may be associated with a different number of CSI-RS resources, CSI-RS ports, antenna panels, antenna sub-panels, or a combination thereof. Accordingly, the base station105may transmit an indication of the set of energy saving modes to a UE115configured to receive one or more CSI-RSs from the base station105. The UE115may then receive a second message indicating a first energy saving mode from the set of energy saving modes, where the first energy saving mode may be indicative of a number of CSI-RS resources used by the base station105or TRP. The UE115may monitor one or more of the CSI-RS resources for a CSI-RS in accordance with the first energy saving mode, and transmit, to the base station105, CSI feedback determined based on measurements made by the UE115of the CSI-RS. For example, the format of the CSI feedback message may be based on the indicated energy saving mode. FIG.2illustrates an example of a wireless communications system200that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The wireless communications system200may include base station105-aand UE115-a, which may be examples of a base station105and a UE115as described with reference toFIG.1. Base station105-amay serve a geographic coverage area110-a. In some cases, base station105-amay implement an energy saving mode implementation procedure in which base station105-amay switch to an energy saving mode, indicate the energy saving mode to UE115-a, and UE115-amay receive signals from base station105-aand/or transmit feedback to base station105-b, accordingly. Additionally or alternatively, other wireless devices, such as a TRP or UE115, may implement and same or similar procedure to conserve energy. In some wireless communications systems, a network device such as base station105-a, a transmission reception point (TRP), or some other network device may transmit one or more channel state information (CSI) reference signals (CSI-RSs) to a UE115(e.g.,115-a) for the purpose of channel sounding. UE115-amay receive one or more CSI-RSs and measure one or more characteristics of a channel over which the CSI-RS was transmitted. UE115-amay be configured to transmit, to the network device (e.g., base station105-a), a feedback report (e.g., a CSI report, a channel state feedback (CSF) report) associated with the one or more received CSI-RSs. In some cases, UE115-amay receive an indication of a configuration for transmitting the feedback report. For example, UE115-amay receive an indication of one or more CSI-RS resources to monitor, and/or a type of CSI measurements to perform. UE115-amay be configured (e.g., by radio resource control (RRC)) with a CSI resources configuration, which may be associated with at least one of multiple resource settings (e.g., non-zero power (NZP) CSI-RS for channel measurement, CSI-RS for interference measurement (CSI-IM), NZP CSI-RS for interference measurement, etc.). In some cases, UE115-amay be configured with a link to one or more resource settings, such as a link to one resource setting (e.g., channel measurement resource (CMR)), a link to two resource settings (e.g., CMR and CSI-IM or NZP interference management resource (NZP-IMR)), a link to three resource settings (e.g., e.g., CMR and CSI-IM, and NZP-IMR). Each of the resource settings may be associated with multiple resource sets, but only one may be active at a time. Each resource set may include one or more resources, where each resource may be associated with a transmission configuration indication (TCI) state (e.g., each resource may be transmitted with a different beam). By way of example, the NZP CSI-RS resource setting for channel measurement may include resource set n−1, resource set n, and resource set n+1. If resource set n is active, then UE115-amay be configured with resource n1associated with TCI state A, and resource n2associated with TCI state B. Accordingly, based on the resource configuration UE115-ais configured with, UE115-amay measure CMR to measure the channel and CSI-IM and interference management resource (IMR) to measure the interference. UE115-amay select a CMR resource from a set of CMR resources and UE115-amay report a CSI-RS resource indicator (CRI) as part of CSI feedback (e.g., it may be beneficial for base station105-ato know which resource the reported CSI corresponds to). Accordingly, the feedback report may be based on the indicated configuration. In recent years there has been a growing concern over the power consumed by cellular networks due to environmental factors such as carbon emissions. As a result, network energy efficiency becomes increasingly important. In some implementations, power consumption may be influenced by larger bandwidths and increasing a number of antennas used for communications. For example, some technologies, such as sub-band full-duplex (SBFD) and massive-MIMO in lower bands may utilize multiple co-located panels where each panel may be equipped with large number of PAs and an antenna subsystem which may consume a large amount of power. Accordingly, in some cases, a wireless network device, such as base station105-a, may turn off (e.g., deactivate) one or more antenna panels (or sub-panels, where sub-panels may refer to a group of antenna elements225) so as to reduce energy consumption. In some implementations, a wireless network device may dynamically adapt an antenna configuration of the wireless network device in accordance with an energy saving mode. For example, base station105-amay configure (e.g., autonomously determine) or be configured with (e.g., pre-configured, receive a message from some other network device including the configuration) of a set of energy saving modes. Each energy mode may be associated with a number of CSI-RS resources, a number of CSI-RS ports (e.g., a number of CSI-RS ports per CSI-RS resource), a number of antenna panels, a number of antenna subpanels, or a combination thereof. For example, base station105-amay be configured with Table 1, where Table 1 may be indicate a set of energy saving modes that base station105-amay employ. TABLE 1EnergyNumber of CSI-RS portsNumber of antennamode Indexper CSI-RS resourcepanels (or subpanels)E0324E1162. . .. . .. . .En41 It should be understood that Table 1 is merely an example. A wireless network device may be configured with energy saving mode configurations in any format (e.g., a non-table format). A wireless network device may be configured with any number of energy saving modes, where each energy saving mode may be associated with any number of parameters associated with energy saving (e.g., a number of CSI-RS resource, a number of CSI-RS ports, a number of antenna panels, a number of antenna subpanels, etc.). In some cases, energy saving modes (and the configurations associated with each mode) may be network device specific, or multiple network devices may be configured with the same set of energy saving modes and configurations. In some cases, such energy saving procedure may impact a CSI procedure. For example, by dynamically de-activating (e.g., turning off) one or more antenna panels, the wireless network device may reduce a number of CSI-RS resources and/or a number of CSI-RS ports over which base station105-amay transmit CSI-RSs, which may impact reception of such CSI-RSs by UE115-aand/or impact a configuration of a CSI feedback report transmitted by UE115-a. For example, a channel produced with a large number of antenna elements225may not be the same as the channel produced by a reduced number of antenna elements225. For example, the downlink precoders, a precoding matrix indicator (PMI), a channel quality indicator (CQI), a rank indicator (RI), or a modulation and coding scheme (MCS), etc. may be dependent on how base station105-atransmits the downlink signal. Accordingly, it may be beneficial to increase UE awareness of the energy saving procedure being used by base station105-abecause the CSF framework may change based on a number of panels210or antenna elements225being used by base station105-a. Accordingly, to improve a CSI procedure, base station105-amay transmit an indication of an energy saving mode the wireless network device is using and an indication of how the energy saving mode may impact a CSI procedure. For example, UE115-amay be configured with a set of energy saving modes and a CSI configuration associated with each energy saving mode, such as a number of CSI-RS resources, a number of CSI-RS ports, a number of antenna panels, a number of antenna subpanels, etc. For example, UE115-amay be configured with a number of CSI-RS ports per CSI-RS resource for each energy saving mode, which may be an implicit indication of how base station105-ais saving energy as UE115-amay be unaware of the antenna panel configuration of base station105-a. In another example, UE115-amay be configured with a number of antenna panels210associated with each energy saving mode, which may be an explicit indication of how base station105-ais saving energy. In some cases, UE115-amay be configured with Table 1 (e.g., or some variation of Table 1). UE115-amay be preconfigured with Table 1, or may receive an indication of Table 1 from base station105-a(e.g., via RRC signaling, broadcast signaling, MAC-CE signaling, DCI signaling). Again, it should be understood that Table 1 is merely an example. UE115-amay be configured with energy saving mode configurations in any format (e.g., a non-table format) and may be configured with any number of energy saving modes, where each energy saving mode may be associated with any number of parameters associated with energy saving (e.g., a number of CSI-RS resource, a number of CSI-RS ports, a number of antenna panels, a number of antenna subpanels, etc.). Upon being configured with the set of energy saving modes, UE115-amay receive an indication of an energy saving mode215being implemented by base station105-a(e.g., via communication link205-a, which may be referred to as a downlink communication link, a channel, a beam, etc.). For example, base station105-amay determine to implement energy mode, En, in which one antenna panel210is active (e.g., turned on). Accordingly, base station105-amay deactivate (e.g., turn off, place in an idle mode) all other antenna panels210, resulting in three deactivated antenna panels210with reference to the example depicted inFIG.2. Alternatively, base station105-amay determine to implement an energy saving mode, En, in which three antenna panels are turned off, and accordingly, may keep any additional antenna panels (over three) active. In either case, base station105-amay transmit a message (e.g., a control message such as RRC) to UE115-aindicating the energy saving mode, En. In some implementations, the contents (or payload) of the energy saving mode indication message may include an energy saving mode index (e.g., En), one or more antenna panel identifiers (e.g., to identify antenna panels that are active, inactive, or both), a number (e.g., a value) indicating how many antenna panels are active, inactive, or both. In some implementations, UE115-amay assume that base station105-ais operating in accordance with a default energy saving mode (e.g., a non-energy saving mode) unless UE115-areceives an indication of the energy saving mode base station105-ais using. A UE115may receive an indication of an energy saving mode and may determine how to receive signals from base station105-aand/or how to transmit feedback to base station105-a. For example, UE115-amay receive the indication of energy mode, En, and may identify the configuration associated with En, such as by using Table 1. Accordingly, UE115-amay determine that En is associated with four CSI-RS ports per CSI-RS resource, and/or that En is associated with one antenna panel of base station105-a. In some cases, if UE115-ais configured with a number of antenna panels associated with an energy saving mode, UE115-amay be configured with a method for determining a number of CSI-RS ports, and/or a number of CSI-RS resources associated with the energy saving mode based on the number of active antenna panels of base station105-a. For example, UE115-amay be configured with a mapping between a number of CSI-RS ports and the corresponding panels and/or number of panels, and/or a mapping between specific CSI-RS ports and the corresponding panels and/or number of panels. In some cases, UE115-amay be preconfigured with the mapping, or receive the mapping via control signaling (e.g., RRC signaling), such as in a same or different message that configures UE115-awith the set of energy saving modes, or a same or different message that indicates the selected energy saving mode of base station105-a. In some cases, the wireless network device may indicate to one or more UEs115at which resource (e.g., time resource) a new energy saving mode may start. The wireless network device may allow enough time for the one or more UEs115to decode the energy saving mode indication message before transmitting CSI-RS with the new energy saving mode. Accordingly, upon receiving an indication of an energy saving mode215employed by base station105-a, and upon determining a CSI configuration associated with the indicated energy saving mode, UE115-amay monitor for one or more CSI-RSs, and may perform measurements on received CSI-RSs (e.g., channel measurements, interference measurements). UE115-amay include an indication of a preferred channel, or indicate the measurements in a feedback message220(e.g., via communications link205-b, which may be referred to as an uplink communications link, a channel, a beam). The feedback message220may be a CSF report in accordance with the energy saving mode. In some cases, UE115-amay transmit UE-assisted information to base station105-a, where the UE-assisted information may include an indication of a future traffic pattern, application types being used, traffic periodicity, a CSF-based metric (e.g., reduce a number of CSI-RS ports), etc. In some implementations, base station105-amay receive feedback (e.g., CSF), UE-assisted information, or both from one UE115or multiple UEs115. Base station105-amay analyze the feedback, the UE-assisted information, or both from the one or more UEs115and determine whether to switch energy saving modes. For example, base station105-amay determine that traffic in geographic coverage area110-ahas increased and accordingly, may determine to switch to an energy saving mode so as to increase CSI-RS resources. In some cases, the wireless network device may switch to any energy saving mode in the set such that the wireless network device may switch from E0to E4. In some cases, the wireless network device may be configured to switch energy saving modes incrementally in order of the set such that the wireless network device may switch modes from E0to E1, then from E1to E2, and so on. In some cases, the wireless network device may be configured to fallback to a default energy saving mode (e.g., a non-energy saving mode) at any time, so as to ensure network reliability. Accordingly, upon switching modes, base station105-amay transmit a message indicating the new energy saving mode. In some cases, base station105-amay transmit the message indicating the selected energy saving mode to a specific UE115(e.g., via a UE-specific message such as MAC-CE or DCI), or to multiple UEs115, such as to each UE115served by base station105-a, or to a group of specific UEs115, such as a group of UEs115in a zone. Base station105-amay transmit the energy mode indication via a broadcast message (e.g., SIB), or via a group-based message (e.g., group common (GC) DCI (GC-DCI). In some implementations, a wireless network device may be configured with a single set of energy saving modes to use for transmitting and receiving. In some implementations, energy saving mode configurations may be direction-specific. For example, a wireless network device may be configured with a first set of energy saving modes that the wireless network device may employ while transmitting, and/or be configured with a second set of energy saving modes that the wireless network device may employ while receiving. The first set of energy saving modes and the second set of energy saving modes and configurations may be the same, partially different, or entirely different. For example, transmitting may consume more power than receiving. Accordingly, all receiving chains may be enabled all the time while the wireless network device adapts the transmitting antenna panels in accordance with an energy saving mode. Accordingly, the wireless network device may not be configured with a set of energy modes for receiving communications. In some implementations, a wireless network device may be configured to switch energy saving modes autonomously (e.g., without restriction), such as based on traffic, load, etc. In some cases, a wireless network device may receive signaling from another network device to switch energy saving modes. In some cases, a wireless network device may be configured to switch energy saving modes based on a timer. The wireless network device may be configured with the timer (e.g., pre-configured, or receive an indication of the timer). A timer may dictate how frequently a wireless network device may switch energy saving modes. For example, the timer may be configured so that the coverage of the network is not impacted by frequent energy mode switching. For example, a wireless network device may be configured to transmit synchronization signal blocks (SSBs) across all panels (e.g., in accordance with a default energy saving mode). Accordingly, a wireless network device may switch to an energy saving mode in between SSBs, and transition back to a non-energy saving mode (e.g., default mode) to transmit SSBs. In another example, a wireless network device may transmit SSBs in accordance with an energy saving mode (e.g., such as when traffic is below a threshold, at nighttime). In some cases, the wireless network device may be configured with categories that may dictate how frequently a wireless network device may switch energy saving modes, such as a CAT-A, CAT-B, and CAT-C. In accordance with CAT-A, the wireless network device may be configured to switch energy saving modes within 10 ms to 20 ms (e.g., and/or 20-40 slots) so that the switch occurs within an SSB periodicity). To perform dynamic adaption in accordance with CAT-A, the wireless network device may perform fast adaption (e.g., within 1-2 symbols). In accordance with CAT-B, the wireless network device may be configured to switch energy saving modes within 100 ms to 1 second. In such cases, SSB power, SSB beams, or both may be changed. In accordance with CAT-C, the wireless network device may be configured to switch energy saving modes based on RRC reconfiguration for adaptions longer than 1 second. FIGS.3A and3Billustrate examples of energy saving mode configurations300and301, respectively that support techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The energy saving mode configurations300and301may be implemented by a base station105, or a TRP, a Remote radio head (RRH), an IAB node, a fixed wireless device, or a consumer customer premises equipment (CPE), which may be examples of the corresponding devices as described with reference toFIGS.1and2. In some cases, a UE115may perform communications in accordance the energy saving mode configurations300and301, where the UE115may be an example of the corresponding devices as described with reference toFIGS.1and2. With reference toFIG.3A, one CSI-RS resource may be mapped with one antenna panel305(e.g., one-to-one mapping between CSI-RS resource and antenna panel305). For example, antenna panel305-amay be associated with a first CSI-RS resource, antenna panel305-bmay be associated with a second CSI-RS resource, antenna panel305-bmay be associated with a third CSI-RS resource, and antenna panel305-dmay be associated with a first CSI-RS resource (e.g., CSI-RS set={CSI-RSID1, CIS-RSID2, . . . , CSI-RSID4} may be mapped to panels305-a,305-b, . . . , and305-d, respectively). Accordingly, a wireless network device may switch from a default energy saving mode (e.g., E0with reference toFIG.2) to a first energy saving mode (e.g., E1with reference toFIG.2). Accordingly, the wireless network device may reduce the number of antenna panels305the wireless network device is using from four to two antenna panels305. For example, the wireless network device may deactivate antenna panels305-cand305-d. In accordance with the CSI configuration associated with the first energy saving mode, the wireless network device may reduce the number of CSI-RS ports from 32 to 16 based on reducing the number of antenna panels305from four to two. The wireless network device may indicate to one or more UEs that the wireless network device switched to the first energy saving mode, and in some cases, may indicate that panels305-aand305-bare active, and/or that panels305-cand305-dare inactive. Based on the indication of the activate (or inactive) panels, the one or more UEs may identify the CSI-RS ports and/or CSI-RS resources that are active for monitoring CSI-RSs and transmitting a feedback report. For example, a UE may determine that a first CSI-RS resource and a second CSI-RS resources are active based on panels305-aand305-bbeing active (e.g., CSI-RS set={CSI-RSID1, CIS-RSID2} may be mapped to panels305-a, and305-b, respectively). With reference toFIG.3B, multiple CSI-RS port groups may be mapped to a single CSI-RS resource (e.g., multiple CSI-RS ports per CSI-RS resource). For example, a single CSI-RS resource may be associated with a number of port groups, such as port group 1, port group 2, port group 3, up to port group n. In some cases, a total number of ports (e.g., 32) may be divided among the port groups. For example, in the case that four port groups are configured per a CSI-RS resource, each port group may be associated with 8 CSI-RS ports. A wireless network device may first be operating in accordance with a default energy saving mode (e.g., E0with reference toFIG.2), in which a total number of antenna panels305(e.g., panels305-e,305-f,305-g, and305-hare active) are active and accordingly, the total number of CSI-RS ports (e.g., 32 ports) are active. The wireless network device may then switch to a first energy saving mode (e.g., E1with reference toFIG.2), in which the wireless network device may deactivate two antenna panels305, such as panels305-gand305-h. Port group 1 may be associated with panel305-e, port group 2 may be associated with panel305-fport group 3 may be associated with panel305-g, and port group 4 may be associated with panel305-h. In some cases, the panel configuration of the wireless network device may be hidden from the UE. Accordingly, the wireless network device may transmit an indication to one or more UEs that the wireless network device switched to the first energy saving mode and indicate which ports are active (e.g., port group 1, and port group 2), and/or which ports are inactive. Based on the indication of the activate (or inactive) ports, the one or more UEs may identify the CSI-RS resources that are active for monitoring CSI-RSs and transmitting a feedback report. FIG.4illustrates an example of a process flow400that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The process flow400may illustrate an example energy mode implementation procedure. For example, base station105-bmay switch to an energy saving mode, indicate the energy saving mode to UE115-b, and UE115-bmay receive signals from base station105-band/or transmit feedback to base station105-baccordingly. Base station105-band UE115-bmay be examples of the corresponding wireless devices described with reference toFIGS.1through3B. In some cases, instead of base station105-bimplementing the energy saving mode procedure, a different type of wireless device (e.g., a UE115, or TRP) may perform a same or similar procedure. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added. At405, UE115-bmay receive, from a wireless network device (e.g., base station105-b, or a TRP of base station105-b), a first control message comprising an indication of a set of energy saving modes of the wireless network device. In some cases, receiving the set of energy saving modes may include receiving an indication of a number of channel state information reference signal ports allocated per channel state information reference signal resource associated with each energy saving mode of the set of energy saving modes. In some cases, receiving the set of energy saving modes may include receiving an indication of a number of antenna panels of the wireless network device, a number of antenna sub-panels of the wireless network device, or both associated with each energy saving mode of the set of energy saving modes. In some cases, receiving the first control message may include receiving a radio resource control message comprising the indication of the set of energy saving modes of the wireless network device. The first control message may indicate that the set of energy saving modes are applicable to uplink communications only, downlink communications only, or both. At410, UE115-bmay receive a second control message indicating a first energy saving mode from the set of energy saving modes, where the first energy saving mode may be indicative of a number of channel state information reference signal resources to be used by the wireless network device. In some cases, UE115-bmay receive a message identifying a set of channel state information reference signal ports that are activated during the energy saving mode. In some cases, UE115-bmay receive a message identifying a set of antenna panels, a set of antenna sub-panels, or both that are activated during the energy saving mode. The message may include an indication of a mapping of a set of channel state information reference signal ports corresponding with each antenna panel of the set of antenna panels, with each antenna sub-panel from the set of antenna sub-panels, or a combination thereof. In some cases, receiving the second control message may include receiving a broadcasted message, a UE-specific message, or a group-common message indicating the first energy saving mode from the set of energy saving modes. Receiving the second control message may include receiving a radio resource control reconfiguration message indicating the first energy saving mode based at least in part on a duration between a previous energy saving mode and the first energy saving mode. The second control message may indicate the first energy saving mode is received based at least in part on a synchronization signal block configuration. Receiving the second control message may include receiving a system information block, a medium access control (MAC) control element message, or downlink control information message, or a combination thereof indicating the first energy saving mode from the set of energy saving modes. In some implementations, UE115-bmay monitor, prior to receiving the second control message, a set of channel state information reference signal resources for the channel state information reference signal in accordance with a default energy saving mode, and may transmit, to the wireless network device, channel state information feedback determined based at least in part on measurements made by UE115-bof the channel state information reference signal in accordance with the default energy saving mode. At415, UE115-bmay monitor one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode. At420, base station105-bmay transmit one or more channel state information reference signals in accordance with the first energy saving mode. At425, UE115-bmay transmit, to the wireless network device, channel state information feedback determined based at least in part on measurements made by UE115-bof the channel state information reference signal. In some cases, at430, UE115-bmay transmit, to the wireless network device, a signal comprising UE assisted information. The UE assisted information may be indicative of communication traffic at the UE, a number of antenna panels, a number of channel state information reference signal ports, or a combination thereof. In some cases, at435, UE115-bmay receive a third control message indicating a second energy saving mode from the set of energy saving modes, where the second energy saving mode may be indicative of a number of channel state information reference signal resources to be used by the wireless network device. In some cases, the second energy saving mode may be based at least in part on the UE assisted information from one or more UEs115. FIG.5shows a block diagram500of a device505that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The device505may be an example of aspects of a UE115as described herein. The device505may include a receiver510, a transmitter515, and a communications manager520. The device505may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver510may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). Information may be passed on to other components of the device505. The receiver510may utilize a single antenna or a set of multiple antennas. The transmitter515may provide a means for transmitting signals generated by other components of the device505. For example, the transmitter515may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). In some examples, the transmitter515may be co-located with a receiver510in a transceiver module. The transmitter515may utilize a single antenna or a set of multiple antennas. The communications manager520, the receiver510, the transmitter515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of techniques for configuring use of an energy saving mode as described herein. For example, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may support a method for performing one or more of the functions described herein. In some examples, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory). Additionally or alternatively, in some examples, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure). In some examples, the communications manager520may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver510, the transmitter515, or both. For example, the communications manager520may receive information from the receiver510, send information to the transmitter515, or be integrated in combination with the receiver510, the transmitter515, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager520may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager520may be configured as or otherwise support a means for receiving, from a wireless network device, a first control message including an indication of a set of energy saving modes of the wireless network device. The communications manager520may be configured as or otherwise support a means for receiving a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The communications manager520may be configured as or otherwise support a means for monitoring one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode. The communications manager520may be configured as or otherwise support a means for transmitting, to the wireless network device, channel state information feedback determined based on measurements made by the UE of the channel state information reference signal. By including or configuring the communications manager520in accordance with examples as described herein, the device505(e.g., a processor controlling or otherwise coupled to the receiver510, the transmitter515, the communications manager520, or a combination thereof) may support techniques for reduced power consumption, and more efficient utilization of communication resources. FIG.6shows a block diagram600of a device605that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The device605may be an example of aspects of a device505or a UE115as described herein. The device605may include a receiver610, a transmitter615, and a communications manager620. The device605may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver610may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). Information may be passed on to other components of the device605. The receiver610may utilize a single antenna or a set of multiple antennas. The transmitter615may provide a means for transmitting signals generated by other components of the device605. For example, the transmitter615may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). In some examples, the transmitter615may be co-located with a receiver610in a transceiver module. The transmitter615may utilize a single antenna or a set of multiple antennas. The device605, or various components thereof, may be an example of means for performing various aspects of techniques for configuring use of an energy saving mode as described herein. For example, the communications manager620may include an energy mode set indication manager625, an energy mode indication manager630, a reference signal monitoring manager635, a feedback manager640, or any combination thereof. The communications manager620may be an example of aspects of a communications manager520as described herein. In some examples, the communications manager620, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver610, the transmitter615, or both. For example, the communications manager620may receive information from the receiver610, send information to the transmitter615, or be integrated in combination with the receiver610, the transmitter615, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager620may support wireless communications at a UE in accordance with examples as disclosed herein. The energy mode set indication manager625may be configured as or otherwise support a means for receiving, from a wireless network device, a first control message including an indication of a set of energy saving modes of the wireless network device. The energy mode indication manager630may be configured as or otherwise support a means for receiving a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The reference signal monitoring manager635may be configured as or otherwise support a means for monitoring one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode. The feedback manager640may be configured as or otherwise support a means for transmitting, to the wireless network device, channel state information feedback determined based on measurements made by the UE of the channel state information reference signal. FIG.7shows a block diagram700of a communications manager720that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The communications manager720may be an example of aspects of a communications manager520, a communications manager620, or both, as described herein. The communications manager720, or various components thereof, may be an example of means for performing various aspects of techniques for configuring use of an energy saving mode as described herein. For example, the communications manager720may include an energy mode set indication manager725, an energy mode indication manager730, a reference signal monitoring manager735, a feedback manager740, a UE information manager745, a reference signal port indication manager750, an antenna panel indication manager755, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications manager720may support wireless communications at a UE in accordance with examples as disclosed herein. The energy mode set indication manager725may be configured as or otherwise support a means for receiving, from a wireless network device, a first control message including an indication of a set of energy saving modes of the wireless network device. The energy mode indication manager730may be configured as or otherwise support a means for receiving a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The reference signal monitoring manager735may be configured as or otherwise support a means for monitoring one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode. The feedback manager740may be configured as or otherwise support a means for transmitting, to the wireless network device, channel state information feedback determined based on measurements made by the UE of the channel state information reference signal. In some examples, the UE information manager745may be configured as or otherwise support a means for transmitting, to the wireless network device, a signal including UE assisted information, the UE assisted information indicative of communication traffic at the UE, a number of antenna panels, a number of channel state information reference signal ports, or a combination thereof, where the first energy saving mode is based on the UE assisted information. In some examples, to support receiving the set of energy saving modes, the reference signal port indication manager750may be configured as or otherwise support a means for receiving an indication of a number of channel state information reference signal ports allocated per channel state information reference signal resource associated with each energy saving mode of the set of energy saving modes. In some examples, the reference signal port indication manager750may be configured as or otherwise support a means for receiving a message identifying a set of channel state information reference signal ports that are activated during the energy saving mode. In some examples, to support receiving the set of energy saving modes, the antenna panel indication manager755may be configured as or otherwise support a means for receiving an indication of a number of antenna panels of the wireless network device, a number of antenna sub-panels of the wireless network device, or both associated with each energy saving mode of the set of energy saving modes. In some examples, the antenna panel indication manager755may be configured as or otherwise support a means for receiving a message identifying a set of antenna panels, a set of antenna sub-panels, or both that are activated during the energy saving mode. In some examples, the message includes an indication of a mapping of a set of channel state information reference signal ports corresponding with each antenna panel of the set of antenna panels, with each antenna sub-panel from the set of antenna sub-panels, or a combination thereof. In some examples, the reference signal monitoring manager735may be configured as or otherwise support a means for monitoring, prior to receiving the second control message, a set of channel state information reference signal resources for the channel state information reference signal in accordance with a default energy saving mode. In some examples, the feedback manager740may be configured as or otherwise support a means for transmitting, to the wireless network device, channel state information feedback determined based on measurements made by the UE of the channel state information reference signal in accordance with the default energy saving mode. In some examples, to support receiving the first control message, the energy mode set indication manager725may be configured as or otherwise support a means for receiving a radio resource control message including the indication of the set of energy saving modes of the wireless network device. In some examples, the first control message indicates that the set of energy saving modes are applicable to uplink communications only, downlink communications only, or both. In some examples, to support receiving the second control message, the energy mode indication manager730may be configured as or otherwise support a means for receiving a broadcasted message, a UE-specific message, or a group-common message indicating the first energy saving mode from the set of energy saving modes. In some examples, to support receiving the second control message, the energy mode indication manager730may be configured as or otherwise support a means for receiving a radio resource control reconfiguration message indicating the first energy saving mode based on a duration between a previous energy saving mode and the first energy saving mode. In some examples, the second control message indicating the first energy saving mode is received based on a synchronization signal block configuration. In some examples, to support receiving the second control message, the energy mode indication manager730may be configured as or otherwise support a means for receiving a system information block, a medium access control (MAC) control element message, or downlink control information message, or a combination thereof indicating the first energy saving mode from the set of energy saving modes. In some examples, the wireless network device is a base station, or a transmission reception point of the base station. FIG.8shows a diagram of a system800including a device805that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The device805may be an example of or include the components of a device505, a device605, or a UE115as described herein. The device805may communicate wirelessly with one or more base stations105, UEs115, or any combination thereof. The device805may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager820, an input/output (I/O) controller810, a transceiver815, an antenna825, a memory830, code835, and a processor840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus845). The I/O controller810may manage input and output signals for the device805. The I/O controller810may also manage peripherals not integrated into the device805. In some cases, the I/O controller810may represent a physical connection or port to an external peripheral. In some cases, the I/O controller810may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I/O controller810may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller810may be implemented as part of a processor, such as the processor840. In some cases, a user may interact with the device805via the I/O controller810or via hardware components controlled by the I/O controller810. In some cases, the device805may include a single antenna825. However, in some other cases, the device805may have more than one antenna825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver815may communicate bi-directionally, via the one or more antennas825, wired, or wireless links as described herein. For example, the transceiver815may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver815may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas825for transmission, and to demodulate packets received from the one or more antennas825. The transceiver815, or the transceiver815and one or more antennas825, may be an example of a transmitter515, a transmitter615, a receiver510, a receiver610, or any combination thereof or component thereof, as described herein. The memory830may include random access memory (RAM) and read-only memory (ROM). The memory830may store computer-readable, computer-executable code835including instructions that, when executed by the processor840, cause the device805to perform various functions described herein. The code835may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code835may not be directly executable by the processor840but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory830may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices. The processor840may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor840may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor840. The processor840may be configured to execute computer-readable instructions stored in a memory (e.g., the memory830) to cause the device805to perform various functions (e.g., functions or tasks supporting techniques for configuring use of an energy saving mode). For example, the device805or a component of the device805may include a processor840and memory830coupled to the processor840, the processor840and memory830configured to perform various functions described herein. The communications manager820may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager820may be configured as or otherwise support a means for receiving, from a wireless network device, a first control message including an indication of a set of energy saving modes of the wireless network device. The communications manager820may be configured as or otherwise support a means for receiving a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The communications manager820may be configured as or otherwise support a means for monitoring one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode. The communications manager820may be configured as or otherwise support a means for transmitting, to the wireless network device, channel state information feedback determined based on measurements made by the UE of the channel state information reference signal. By including or configuring the communications manager820in accordance with examples as described herein, the device805may support techniques for reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, and longer battery life. In some examples, the communications manager820may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver815, the one or more antennas825, or any combination thereof. Although the communications manager820is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager820may be supported by or performed by the processor840, the memory830, the code835, or any combination thereof. For example, the code835may include instructions executable by the processor840to cause the device805to perform various aspects of techniques for configuring use of an energy saving mode as described herein, or the processor840and the memory830may be otherwise configured to perform or support such operations. FIG.9shows a block diagram900of a device905that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The device905may be an example of aspects of a base station105as described herein. The device905may include a receiver910, a transmitter915, and a communications manager920. The device905may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver910may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). Information may be passed on to other components of the device905. The receiver910may utilize a single antenna or a set of multiple antennas. The transmitter915may provide a means for transmitting signals generated by other components of the device905. For example, the transmitter915may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). In some examples, the transmitter915may be co-located with a receiver910in a transceiver module. The transmitter915may utilize a single antenna or a set of multiple antennas. The communications manager920, the receiver910, the transmitter915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of techniques for configuring use of an energy saving mode as described herein. For example, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may support a method for performing one or more of the functions described herein. In some examples, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory). Additionally or alternatively, in some examples, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure). In some examples, the communications manager920may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver910, the transmitter915, or both. For example, the communications manager920may receive information from the receiver910, send information to the transmitter915, or be integrated in combination with the receiver910, the transmitter915, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager920may support wireless communications at a wireless network device in accordance with examples as disclosed herein. For example, the communications manager920may be configured as or otherwise support a means for transmitting, to a UE, a first control message including an indication of a set of energy saving modes of the wireless network device. The communications manager920may be configured as or otherwise support a means for transmitting a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The communications manager920may be configured as or otherwise support a means for transmitting one or more channel state information reference signals in accordance with the first energy saving mode. The communications manager920may be configured as or otherwise support a means for receiving, from the UE, channel state information feedback determined based on measurements made by the UE of the one or more channel state information reference signals. By including or configuring the communications manager920in accordance with examples as described herein, the device905(e.g., a processor controlling or otherwise coupled to the receiver910, the transmitter915, the communications manager920, or a combination thereof) may support techniques for reduced power consumption, and more efficient utilization of communication resources. FIG.10shows a block diagram1000of a device1005that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The device1005may be an example of aspects of a device905or a base station105as described herein. The device1005may include a receiver1010, a transmitter1015, and a communications manager1020. The device1005may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver1010may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). Information may be passed on to other components of the device1005. The receiver1010may utilize a single antenna or a set of multiple antennas. The transmitter1015may provide a means for transmitting signals generated by other components of the device1005. For example, the transmitter1015may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for configuring use of an energy saving mode). In some examples, the transmitter1015may be co-located with a receiver1010in a transceiver module. The transmitter1015may utilize a single antenna or a set of multiple antennas. The device1005, or various components thereof, may be an example of means for performing various aspects of techniques for configuring use of an energy saving mode as described herein. For example, the communications manager1020may include an energy mode set indication component1025, an energy mode indication component1030, a reference signal transmission component1035, a feedback reception component1040, or any combination thereof. The communications manager1020may be an example of aspects of a communications manager920as described herein. In some examples, the communications manager1020, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver1010, the transmitter1015, or both. For example, the communications manager1020may receive information from the receiver1010, send information to the transmitter1015, or be integrated in combination with the receiver1010, the transmitter1015, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager1020may support wireless communications at a wireless network device in accordance with examples as disclosed herein. The energy mode set indication component1025may be configured as or otherwise support a means for transmitting, to a UE, a first control message including an indication of a set of energy saving modes of the wireless network device. The energy mode indication component1030may be configured as or otherwise support a means for transmitting a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The reference signal transmission component1035may be configured as or otherwise support a means for transmitting one or more channel state information reference signals in accordance with the first energy saving mode. The feedback reception component1040may be configured as or otherwise support a means for receiving, from the UE, channel state information feedback determined based on measurements made by the UE of the one or more channel state information reference signals. FIG.11shows a block diagram1100of a communications manager1120that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The communications manager1120may be an example of aspects of a communications manager920, a communications manager1020, or both, as described herein. The communications manager1120, or various components thereof, may be an example of means for performing various aspects of techniques for configuring use of an energy saving mode as described herein. For example, the communications manager1120may include an energy mode set indication component1125, an energy mode indication component1130, a reference signal transmission component1135, a feedback reception component1140, a UE information component1145, an energy mode switching component1150, a deactivation component1155, a port indication component1160, an antenna panel indication component1165, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications manager1120may support wireless communications at a wireless network device in accordance with examples as disclosed herein. The energy mode set indication component1125may be configured as or otherwise support a means for transmitting, to a UE, a first control message including an indication of a set of energy saving modes of the wireless network device. The energy mode indication component1130may be configured as or otherwise support a means for transmitting a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The reference signal transmission component1135may be configured as or otherwise support a means for transmitting one or more channel state information reference signals in accordance with the first energy saving mode. The feedback reception component1140may be configured as or otherwise support a means for receiving, from the UE, channel state information feedback determined based on measurements made by the UE of the one or more channel state information reference signals. In some examples, the UE information component1145may be configured as or otherwise support a means for receiving, from at least the UE, a signal including UE assisted information, the UE assisted information indicative of communication traffic at the UE, a number of antenna panels, a number of channel state information reference signal ports, or a combination thereof. In some examples, the energy mode switching component1150may be configured as or otherwise support a means for determining to switch energy saving modes based on the UE assisted information from at least the UE. In some examples, the deactivation component1155may be configured as or otherwise support a means for deactivating one or more channel state information reference signals ports, one or more antenna panels, one or more antenna sub-panels, or a combination thereof based on the first energy saving mode. In some examples, to support transmitting the set of energy saving modes, the port indication component1160may be configured as or otherwise support a means for transmitting an indication of a number of channel state information reference signal ports allocated per channel state information reference signal resource associated with each energy saving mode of the set of energy saving modes. In some examples, the port indication component1160may be configured as or otherwise support a means for transmitting a message identifying a set of channel state information reference signal ports that are activated during the energy saving mode. In some examples, the channel state information reference signal ports are configured into one or more groups. In some examples, to support transmitting the set of energy saving modes, the antenna panel indication component1165may be configured as or otherwise support a means for transmitting an indication of a number of antenna panels, a number of antenna sub-panels, or both associated with each energy saving mode of the set of energy saving modes. In some examples, the antenna panel indication component1165may be configured as or otherwise support a means for transmitting a message identifying a set of antenna panels, a set of antenna sub-panels, or both that are activated during the energy saving mode. In some examples, the message includes an indication of a mapping of a set of channel state information reference signal ports corresponding with each antenna panel of the set of antenna panels, with each antenna sub-panel from the set of antenna sub-panels, or a combination thereof. In some examples, the reference signal transmission component1135may be configured as or otherwise support a means for transmitting, one or more channel state information references signals via a set of resources in accordance with a default energy saving mode. In some examples, the feedback reception component1140may be configured as or otherwise support a means for receiving, from the UE, channel state information feedback determined based on measurements made by the UE of the one or more channel state information reference signals in accordance with the default energy saving mode. In some examples, the energy mode switching component1150may be configured as or otherwise support a means for determining to switch to the first energy saving mode from the default energy saving mode, where transmitting the second control message is based on the determination. In some examples, to support transmitting the first control message, the energy mode indication component1130may be configured as or otherwise support a means for transmitting a radio resource control message including the indication of the set of energy saving modes of the wireless network device. In some examples, the first control message indicates that the set of energy saving modes are applicable to uplink communications, downlink communications, or both. In some examples, to support transmitting the second control message, the energy mode indication component1130may be configured as or otherwise support a means for transmitting a broadcasted message, a UE-specific message, or a group-common message indicating the first energy saving mode from the set of energy saving modes. In some examples, to support transmitting the second control message, the energy mode indication component1130may be configured as or otherwise support a means for transmitting a radio resource control reconfiguration message indicating the first energy saving mode based on a duration between a previous energy saving mode and the first energy saving mode. In some examples, the second control message indicating the first energy saving mode is received based on a synchronization signal block configuration. In some examples, to support transmitting the second control message, the energy mode indication component1130may be configured as or otherwise support a means for transmitting a system information block, a medium access control (MAC) control element message, or downlink control information message, or a combination thereof indicating the first energy saving mode from the set of energy saving modes. In some examples, the wireless network device is a base station, or a transmission reception point of the base station. FIG.12shows a diagram of a system1200including a device1205that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The device1205may be an example of or include the components of a device905, a device1005, or a base station105as described herein. The device1205may communicate wirelessly with one or more base stations105, UEs115, or any combination thereof. The device1205may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager1220, a network communications manager1210, a transceiver1215, an antenna1225, a memory1230, code1235, a processor1240, and an inter-station communications manager1245. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1250). The network communications manager1210may manage communications with a core network130(e.g., via one or more wired backhaul links). For example, the network communications manager1210may manage the transfer of data communications for client devices, such as one or more UEs115. In some cases, the device1205may include a single antenna1225. However, in some other cases the device1205may have more than one antenna1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver1215may communicate bi-directionally, via the one or more antennas1225, wired, or wireless links as described herein. For example, the transceiver1215may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1215may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas1225for transmission, and to demodulate packets received from the one or more antennas1225. The transceiver1215, or the transceiver1215and one or more antennas1225, may be an example of a transmitter915, a transmitter1015, a receiver910, a receiver1010, or any combination thereof or component thereof, as described herein. The memory1230may include RAM and ROM. The memory1230may store computer-readable, computer-executable code1235including instructions that, when executed by the processor1240, cause the device1205to perform various functions described herein. The code1235may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1235may not be directly executable by the processor1240but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1230may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. The processor1240may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1240may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1240. The processor1240may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1230) to cause the device1205to perform various functions (e.g., functions or tasks supporting techniques for configuring use of an energy saving mode). For example, the device1205or a component of the device1205may include a processor1240and memory1230coupled to the processor1240, the processor1240and memory1230configured to perform various functions described herein. The inter-station communications manager1245may manage communications with other base stations105, and may include a controller or scheduler for controlling communications with UEs115in cooperation with other base stations105. For example, the inter-station communications manager1245may coordinate scheduling for transmissions to UEs115for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager1245may provide an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between base stations105. The communications manager1220may support wireless communications at a wireless network device in accordance with examples as disclosed herein. For example, the communications manager1220may be configured as or otherwise support a means for transmitting, to a UE, a first control message including an indication of a set of energy saving modes of the wireless network device. The communications manager1220may be configured as or otherwise support a means for transmitting a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The communications manager1220may be configured as or otherwise support a means for transmitting one or more channel state information reference signals in accordance with the first energy saving mode. The communications manager1220may be configured as or otherwise support a means for receiving, from the UE, channel state information feedback determined based on measurements made by the UE of the one or more channel state information reference signals. By including or configuring the communications manager1220in accordance with examples as described herein, the device1205may support techniques for reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, and longer battery life. In some examples, the communications manager1220may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver1215, the one or more antennas1225, or any combination thereof. Although the communications manager1220is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1220may be supported by or performed by the processor1240, the memory1230, the code1235, or any combination thereof. For example, the code1235may include instructions executable by the processor1240to cause the device1205to perform various aspects of techniques for configuring use of an energy saving mode as described herein, or the processor1240and the memory1230may be otherwise configured to perform or support such operations. FIG.13shows a flowchart illustrating a method1300that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The operations of the method1300may be implemented by a UE or its components as described herein. For example, the operations of the method1300may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware. At1305, the method may include receiving, from a wireless network device, a first control message including an indication of a set of energy saving modes of the wireless network device. The operations of1305may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1305may be performed by an energy mode set indication manager725as described with reference toFIG.7. At1310, the method may include receiving a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The operations of1310may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1310may be performed by an energy mode indication manager730as described with reference toFIG.7. At1315, the method may include monitoring one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode. The operations of1315may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1315may be performed by a reference signal monitoring manager735as described with reference toFIG.7. At1320, the method may include transmitting, to the wireless network device, channel state information feedback determined based on measurements made by the UE of the channel state information reference signal. The operations of1320may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1320may be performed by a feedback manager740as described with reference toFIG.7. FIG.14shows a flowchart illustrating a method1400that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The operations of the method1400may be implemented by a UE or its components as described herein. For example, the operations of the method1400may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware. At1405, the method may include receiving, from a wireless network device, a first control message including an indication of a set of energy saving modes of the wireless network device. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by an energy mode set indication manager725as described with reference toFIG.7. At1410, the method may include receiving a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by an energy mode indication manager730as described with reference toFIG.7. At1415, the method may include receiving an indication of a number of channel state information reference signal ports allocated per channel state information reference signal resource associated with each energy saving mode of the set of energy saving modes. The operations of1415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1415may be performed by a reference signal port indication manager750as described with reference toFIG.7. At1420, the method may include monitoring one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode. The operations of1420may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1420may be performed by a reference signal monitoring manager735as described with reference toFIG.7. At1425, the method may include transmitting, to the wireless network device, channel state information feedback determined based on measurements made by the UE of the channel state information reference signal. The operations of1425may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1425may be performed by a feedback manager740as described with reference toFIG.7. FIG.15shows a flowchart illustrating a method1500that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The operations of the method1500may be implemented by a base station or its components as described herein. For example, the operations of the method1500may be performed by a base station105as described with reference toFIGS.1through4and9through12. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using special-purpose hardware. At1505, the method may include transmitting, to a UE, a first control message including an indication of a set of energy saving modes of the wireless network device. The operations of1505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1505may be performed by an energy mode set indication component1125as described with reference toFIG.11. At1510, the method may include transmitting a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The operations of1510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1510may be performed by an energy mode indication component1130as described with reference toFIG.11. At1515, the method may include transmitting one or more channel state information reference signals in accordance with the first energy saving mode. The operations of1515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1515may be performed by a reference signal transmission component1135as described with reference toFIG.11. At1520, the method may include receiving, from the UE, channel state information feedback determined based on measurements made by the UE of the one or more channel state information reference signals. The operations of1520may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1520may be performed by a feedback reception component1140as described with reference toFIG.11. FIG.16shows a flowchart illustrating a method1600that supports techniques for configuring use of an energy saving mode in accordance with aspects of the present disclosure. The operations of the method1600may be implemented by a base station or its components as described herein. For example, the operations of the method1600may be performed by a base station105as described with reference toFIGS.1through4and9through12. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using special-purpose hardware. At1605, the method may include transmitting, to a UE, a first control message including an indication of a set of energy saving modes of the wireless network device. The operations of1605may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1605may be performed by an energy mode set indication component1125as described with reference toFIG.11. At1610, the method may include transmitting a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device. The operations of1610may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1610may be performed by an energy mode indication component1130as described with reference toFIG.11. At1615, the method may include transmitting one or more channel state information reference signals in accordance with the first energy saving mode. The operations of1615may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1615may be performed by a reference signal transmission component1135as described with reference toFIG.11. At1620, the method may include receiving, from the UE, channel state information feedback determined based on measurements made by the UE of the one or more channel state information reference signals. The operations of1620may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1620may be performed by a feedback reception component1140as described with reference toFIG.11. At1625, the method may include receiving, from at least the UE, a signal including UE assisted information, the UE assisted information indicative of communication traffic at the UE, a number of antenna panels, a number of channel state information reference signal ports, or a combination thereof. The operations of1625may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1625may be performed by a UE information component1145as described with reference toFIG.11. At1630, the method may include determining to switch energy saving modes based on the UE assisted information from at least the UE. The operations of1630may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1630may be performed by an energy mode switching component1150as described with reference toFIG.11. The following provides an overview of aspects of the present disclosure: Aspect 1: A method for wireless communications at a UE, comprising: receiving, from a wireless network device, a first control message comprising an indication of a set of energy saving modes of the wireless network device; receiving a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device; monitoring one or more of the channel state information reference signal resources for a channel state information reference signal in accordance with the first energy saving mode; and transmitting, to the wireless network device, channel state information feedback determined based at least in part on measurements made by the UE of the channel state information reference signal. Aspect 2: The method of aspect 1, further comprising: transmitting, to the wireless network device, a signal comprising UE assisted information, the UE assisted information indicative of communication traffic at the UE, a number of antenna panels, a number of channel state information reference signal ports, or a combination thereof, wherein the first energy saving mode is based at least in part on the UE assisted information. Aspect 3: The method of any of aspects 1 through 2, wherein receiving the set of energy saving modes further comprises: receiving an indication of a number of channel state information reference signal ports allocated per channel state information reference signal resource associated with each energy saving mode of the set of energy saving modes. Aspect 4: The method of aspect 3, further comprising: receiving a message identifying a set of channel state information reference signal ports that are activated during the first energy saving mode. Aspect 5: The method of any of aspects 1 through 4, wherein receiving the set of energy saving modes further comprises: receiving an indication of a number of antenna panels of the wireless network device, a number of antenna sub-panels of the wireless network device, or both associated with each energy saving mode of the set of energy saving modes. Aspect 6: The method of aspect 5, further comprising: receiving a message identifying a set of antenna panels, a set of antenna sub-panels, or both that are activated during the first energy saving mode. Aspect 7: The method of aspect 6, wherein the message comprises an indication of a mapping of a set of channel state information reference signal ports corresponding with each antenna panel of the set of antenna panels, with each antenna sub-panel from the set of antenna sub-panels, or a combination thereof. Aspect 8: The method of any of aspects 1 through 7, further comprising: monitoring, prior to receiving the second control message, a set of channel state information reference signal resources for the channel state information reference signal in accordance with a default energy saving mode; and transmitting, to the wireless network device, channel state information feedback determined based at least in part on measurements made by the UE of the channel state information reference signal in accordance with the default energy saving mode. Aspect 9: The method of any of aspects 1 through 8, wherein receiving the first control message further comprises: receiving a radio resource control message comprising the indication of the set of energy saving modes of the wireless network device. Aspect 10: The method of any of aspects 1 through 9, wherein the first control message indicates that the set of energy saving modes are applicable to uplink communications only, downlink communications only, or both. Aspect 11: The method of any of aspects 1 through 10, wherein receiving the second control message further comprises: receiving a broadcasted message, a UE-specific message, or a group-common message indicating the first energy saving mode from the set of energy saving modes. Aspect 12: The method of any of aspects 1 through 11, wherein receiving the second control message further comprises: receiving a radio resource control reconfiguration message indicating the first energy saving mode based at least in part on a duration between a previous energy saving mode and the first energy saving mode. Aspect 13: The method of any of aspects 1 through 12, wherein the second control message indicating the first energy saving mode is received based at least in part on a synchronization signal block configuration. Aspect 14: The method of any of aspects 1 through 13, wherein receiving the second control message further comprises: receiving a system information block, a medium access control (MAC) control element message, or downlink control information message, or a combination thereof indicating the first energy saving mode from the set of energy saving modes. Aspect 15: The method of any of aspects 1 through 14, wherein the wireless network device is a base station, or a transmission reception point of the base station. Aspect 16: A method for wireless communications at a wireless network device, comprising: transmitting, to a UE, a first control message comprising an indication of a set of energy saving modes of the wireless network device; transmitting a second control message indicating a first energy saving mode from the set of energy saving modes, the first energy saving mode indicative of a number of channel state information reference signal resources to be used by the wireless network device; transmitting one or more channel state information reference signals in accordance with the first energy saving mode; and receiving, from the UE, channel state information feedback determined based at least in part on measurements made by the UE of the one or more channel state information reference signals. Aspect 17: The method of aspect 16, further comprising: receiving, from at least the UE, a signal comprising UE assisted information, the UE assisted information indicative of communication traffic at the UE, a number of antenna panels, a number of channel state information reference signal ports, or a combination thereof; and determining to switch energy saving modes based at least in part on the UE assisted information from at least the UE. Aspect 18: The method of any of aspects 16 through 17, further comprising: deactivating one or more channel state information reference signals ports, one or more antenna panels, one or more antenna sub-panels, or a combination thereof based at least in part on the first energy saving mode. Aspect 19: The method of any of aspects 16 through 18, wherein transmitting the set of energy saving modes further comprises: transmitting an indication of a number of channel state information reference signal ports allocated per channel state information reference signal resource associated with each energy saving mode of the set of energy saving modes. Aspect 20: The method of aspect 19, further comprising: transmitting a message identifying a set of channel state information reference signal ports that are activated during the first energy saving mode. Aspect 21: The method of any of aspects 19 through 20, wherein the channel state information reference signal ports are configured into one or more groups. Aspect 22: The method of any of aspects 16 through 21, wherein transmitting the set of energy saving modes further comprises: transmitting an indication of a number of antenna panels, a number of antenna sub-panels, or both associated with each energy saving mode of the set of energy saving modes. Aspect 23: The method of aspect 22, further comprising: transmitting a message identifying a set of antenna panels, a set of antenna sub-panels, or both that are activated during the first energy saving mode. Aspect 24: The method of aspect 23, wherein the message comprises an indication of a mapping of a set of channel state information reference signal ports corresponding with each antenna panel of the set of antenna panels, with each antenna sub-panel from the set of antenna sub-panels, or a combination thereof. Aspect 25: The method of any of aspects 16 through 24, further comprising: transmitting, one or more channel state information references signals via a set of resources in accordance with a default energy saving mode; and receiving, from the UE, channel state information feedback determined based at least in part on measurements made by the UE of the one or more channel state information reference signals in accordance with the default energy saving mode. Aspect 26: The method of aspect 25, further comprising: determining to switch to the first energy saving mode from the default energy saving mode, where transmitting the second control message is based at least in part on the determination. Aspect 27: The method of any of aspects 16 through 26, wherein transmitting the first control message further comprises: transmitting a radio resource control message comprising the indication of the set of energy saving modes of the wireless network device. Aspect 28: The method of any of aspects 16 through 27, wherein the first control message indicates that the set of energy saving modes are applicable to uplink communications, downlink communications, or both. Aspect 29: The method of any of aspects 16 through 28, wherein transmitting the second control message further comprises: transmitting a broadcasted message, a UE-specific message, or a group-common message indicating the first energy saving mode from the set of energy saving modes. Aspect 30: The method of any of aspects 16 through 29, wherein transmitting the second control message further comprises: transmitting a radio resource control reconfiguration message indicating the first energy saving mode based at least in part on a duration between a previous energy saving mode and the first energy saving mode. Aspect 31: The method of any of aspects 16 through 30, wherein the second control message indicating the first energy saving mode is received based at least in part on a synchronization signal block configuration. Aspect 32: The method of any of aspects 16 through 31, wherein transmitting the second control message further comprises: transmitting a system information block, a medium access control (MAC) control element message, or downlink control information message, or a combination thereof indicating the first energy saving mode from the set of energy saving modes. Aspect 33: The method of any of aspects 16 through 32, wherein the wireless network device is a base station, or a transmission reception point of the base station. Aspect 34: An apparatus for wireless communications, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 15. Aspect 35: An apparatus for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 15. Aspect 36: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 15. Aspect 37: An apparatus for wireless communications, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 16 through 33. Aspect 38: An apparatus for wireless communications, comprising at least one means for performing a method of any of aspects 16 through 33. Aspect 39: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 16 through 33. It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined. Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” The term “determine” or “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and other such similar actions. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label. The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples. The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein. | 130,002 |
11943716 | DETAILED DESCRIPTION The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments. Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments. The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way. Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification. Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control. Embodiments of the present disclosure include systems and methods for mobile application traffic optimization. Embodiments of the present disclosure include systems and methods for context aware traffic management for network and device resource conservation. Embodiments of the present disclosure include systems and methods for mobile network traffic coordination across multiple applications. Embodiments of the present disclosure include systems and methods for prediction of activity session for mobile network use optimization and/or user experience enhancement. One embodiment of the disclosed technology includes, a system that optimizes multiple aspects of the connection with wired and wireless networks and devices through a comprehensive view of device and application activity including: loading, current application needs on a device, controlling the type of access (push vs. pull or hybrid), location, concentration of users in a single area, time of day, how often the user interacts with the application, content or device, and using this information to shape traffic to a cooperative client/server or simultaneously mobile devices without a cooperative client. Because the disclosed server is not tied to any specific network provider it has visibility into the network performance across all service providers. This enables optimizations to be applied to devices regardless of the operator or service provider, thereby enhancing the user experience and managing network utilization while roaming. Bandwidth has been considered a major issue in wireless networks today. More and more research has been done related to the need for additional bandwidth to solve access problems—many of the performance enhancing solutions and next generation standards, such as LTE, 4G, and WiMAX are focused on providing increased bandwidth. A key problem is lack of bandwidth on the signaling channel more so than the data channel. Embodiments of the disclosed technology includes, for example, alignment of requests from multiple applications to minimize the need for several polling requests; leverage specific content types to determine how to proxy/manage a connection/content; and apply specific heuristics associated with device, user behavioral patterns (how often they interact with the device/application) and/or network parameters. Embodiments of the present technology can further include, moving recurring HTTP polls performed by various widgets, RSS readers, etc., to remote network node (e.g., Network operation center (NOC)), thus considerably lowering device battery/power consumption, radio channel signaling, and bandwidth usage. Additionally, the offloading can be performed transparently so that existing applications do not need to be changed. In some embodiments, this can be implemented using a local proxy on the mobile device which automatically detects recurring requests for the same content (RSS feed, Widget data set) that matches a specific rule (e.g., happens every 15 minutes). The local proxy can automatically cache the content on the mobile device while delegating the polling to the server (e.g., a proxy server operated as an element of a communications network). The server can then notify the mobile/client proxy if the content changes, and if content has not changed (or not changed sufficiently, or in an identified manner or amount) the mobile proxy provides the latest version in its cache to the user (without need to utilize the radio at all). This way the mobile device (e.g., a mobile phone, smart phone, etc.) does not need to open up (e.g., thus powering on the radio) or use a data connection if the request is for content that is monitored and that has been not flagged as new, changed, or otherwise different. The logic for automatically adding content sources/application servers (e.g., including URLs/content) to be monitored can also check for various factors like how often the content is the same, how often the same request is made (is there a fixed interval/pattern?), which application is requesting the data, etc. Similar rules to decide between using the cache and request the data from the original source may also be implemented and executed by the local proxy and/or server. For example, when the request comes at an unscheduled/unexpected time (user initiated check), or after every (n) consecutive times the response has been provided from the cache, etc., or if the application is running in the background vs. in a more interactive mode of the foreground. As more and more mobile applications base their features on resources available in the network, this becomes increasingly important. In addition, the disclosed technology allows elimination of unnecessary chatter from the network, benefiting the operators trying to optimize the wireless spectrum usage. Cross Application Traffic Coordination In one embodiment of the present disclosure, a group of applications [A, B, C . . . ] may have a timeline of transfers of data from the mobile device (or client (e.g., mobile application, software agent, widget, etc.) on the mobile device) to the network, or from the network to the mobile device (for receipt by the client). The time of the transfers can be represented as: Application A: tA1, tA2, tA3, . . . Application B: tB1, tB2, tB3, . . . Application C: tC1, tC2, tC3, . . . Each of the times ‘t’ can have a natural point of occurring based upon the independent activity of the corresponding application as operations are executed at the application server/provider and/or on the software client on the mobile device. For example, an application can transfer a message, an event, or other types of data to the network (or vice versa) at a regular or semi-regular series of times as part of polling, satisfying a device, application, or user request, application maintenance, or other operation. Similarly, an application can transfer a message, event, or other types data via the network (or vice versa) at a regular, semi-regular, or irregular series of times to perform its inherent functions or operations, such as synchronizing two data stores, determining the contents of a data store, accessing new data from the application server/service provider, communicating with a peer device (e.g., another device with the same application or another application with which the requesting application interacts), exchanging control messages, etc. In some instances, there is typically no correlation or weak correlation between the times at which data transfers or event transactions occur for one application as compared to a second application on a given mobile device, or for different data requests for the same application. In some cases, there may be a stronger correlation between the times at which a transfer occurs for one application as compared to a second application (e.g., where an operation of a first application is dependent upon or triggers an operation of a second application, or where a user typically executes an operation of one application in conjunction with an operation of a second application). Note that in some instances, the second application may be the same application as the first application and that correlations can be tracked and determined for multiple requests sent by one application in a similar fashion. In some embodiments, in order to optimize (e.g., typically to minimize) the number of times that a device (e.g., a mobile device or smart phone) radio is turned on to decrease the consumption of power (and hence conserve its battery or other power source), a distributed proxy system including a local proxy and/or proxy server can operate to intercept the events or transactions (or requests for transfer) of information. When intercepted, the local proxy and/or the proxy server can delay (or expedite) the time at which one or more of these transfers would normally occur in order to perform multiple transfers together as part of a single transfer operation (i.e., instead of performing multiple, individual transfers). Alternatively, the local and/or proxy server can pre-retrieve data for a non-priority application or less important/time sensitive application whose polls are typically expected to happen before another application having higher priority, for example. In other words, a delay could be negative resulting in content pre-retrieval for alignment with an anticipated data request which typically happens before the request of the lesser priority application. The delay time (D) can represent a maximum time delay value (or in some instances, expedited time value) after receipt of a request to make such a transfer, with the value of D determined so as to enable the collection of as many of the transfers as feasible in a single, optimized data transfer. The delay times or expedited times of one or more transfers are determined so as to factor in any potential impact on performance and user experience. Ideally, the system determines D to prevent undesired penalties or inefficiencies, and to prevent undesired impact on the user experience. Note that as described above, the delay ‘D’ could be negative or positive for alignment purposes (e.g., to implement a delayed or an expedited transfer). In some embodiments, delay time ‘D’ (use to represent both positive and negative delays (effectively and expedited transfer)) can be determined based on consideration of one or more of the following factors: the priority of the application (or the relative priority of one application in comparison to another), the nature or amount of data involved in the transfer (e.g., whether it represents fresh data, a housekeeping function, a control instruction, etc.), the status of the application (e.g., active, inactive, background, foreground, etc.), a useable lifetime of the data to be transferred (a period before it becomes stale), the interval between the transfer times of multiple data requests for a single application, the interval between the transfer times across more than one application (e.g., the largest transfer time interval based on consideration of all active applications), network characteristics (available bandwidth, network latency, etc.), or another relevant factor. In some embodiments, the delay time ‘D’ of specific events/transactions can be controlled by the mobile device (e.g., platform, device settings, or OS specifications), network service provider, and/or the user as part of optimizing the battery life to align data transfer requests across multiple applications or the same application, as opposed to performing each data transfer individually. In some instances, the user can manually configure a setting specifying that requests across multiple applications or the same application are to be batched. The user can enable the setting, and allow the system to configure the details. In addition, the user can specify preferences, priorities, or any other constraints related to alignment of data request transfer of the mobile network. Activity Session Method As will be described, in some embodiments the present disclosure is directed to a method for augmenting a distributed proxy-based solution by introducing the concept of an “activity session”. An activity session is a pattern of multiple mobile application use by a user that can be “predicted” by using contextual clues available to a local proxy on a mobile device. Based on the prediction, a multiplex connection can be created and pre-caching of content can be performed to support the data activity during the session, thus minimizing the signaling overhead as well as the multiplexed transaction duration. In some embodiments this approach will also provide the additional benefit of an improved user experience (e.g., by reducing a perceived latency). In one embodiment, an activity session is a pattern of multiple mobile application use by a mobile user that can be “predicted” (or otherwise anticipated or expected) based on contextual clues detected and analyzed by a local proxy on a device (e.g., the user's mobile or portable phone, smartphone) and/or by a proxy server in a distributed proxy system. Based on the prediction, a multiplex connection can be created and pre-caching of content can be performed to support the data activity during the session, thus minimizing the signaling overhead as well as the multiplexed transaction duration. Further, in some embodiments this approach can provide enhanced user experience by reducing or eliminating user wait times or other sources of latency in the user experience. Connection Optimization TCP connections, such as persistent TCP sessions and TCP connection pooling can be utilized for reusing connections. Both techniques on a mobile device allow previously-established TCP connections to the same server (e.g., a host server, an application server, or content provider) to be reused for multiple HTTP transactions, which saves connection establishment and tear-down times between transactions. However, with multiple applications running, and each establishing its own TCP connections to multiple host servers (application servers/content providers), there are potentially many TCP connections being established on a mobile device during a given time of network activity. A benefit of a distributed proxy system (such as that shown in the examples ofFIGS.1A-1B), where each component (i.e., the local proxy in the mobile device and the proxy server in the host server) is acknowledged by the system and each other, is that a single TCP connection can be used to transport all of the application traffic during an established activity session. For example, the WebMUX and SCP protocols allow multiplexing of multiple sessions of application-level protocols (such as HTTP) over a single TCP connection. In one embodiment, an activity session can be supported by a multiplexed TCP connection using these or additional mechanisms. In another embodiment, the activity session is supported by a TCP connection pool, with the connection reuse enhanced by nature of connecting to a single and known proxy server such as the disclosed proxy system. Prediction Basis The disclosed distributed proxy and cache system can eliminate or decrease resource consumption of “background” data access of mobile applications and processes in order to improve signaling efficiency, power consumption (battery life), and use of network resources. The prioritization or prediction of the occurring of data access or the background data access may be based on one or more data types or characteristics, heuristics, algorithms, collaborative filtering techniques, etc. that process data to determine a most likely behavior by a user. For example, the data processing may determine that there is a relatively high correlation between a user accessing one type of application, followed by them accessing a second application. Or, that when a user becomes active on their device after a certain amount of time, they are likely to engage in a series of actions, data requests, etc. Or, that when sufficient new data (notifications, messages, etc.) has become available to the user, they are likely to access it in a certain order (such as by activating a series of applications or generating a series of requests in a certain order). In some embodiments, or in addition to the server prediction approach described above, the mobile device may use contextual cues available via hardware sensors or application activity indications to predict the likelihood of the start of an activity session. For example, the local proxy may monitor location changes in the device to predict that a location update may be sent to a location-based service, or may monitor user activity at certain geographical locations and anticipate an activity session, for example, based on historical application usage at a particular location. The anticipated activity session, which can be derived by means of hardware context on the mobile device (e.g., the state or operating status of the device), can be the same or different in structure as that created by the proxy server (e.g., server100ofFIGS.1A-1B). Establishing the Activity Session An activity session may be recognized and activated based on a predicted activity session by either the proxy server or the local proxy in the following manner. On the device side, application activity after a period of inactivity, during which a potential activity session has been identified, can cause the local proxy to compare the data request to a list of host URLs associated with a predicted/anticipated activity session. If the data activity matches a higher-priority entry in the URL list, for example, based on a priority threshold, the data activity may trigger the start of an activity session based on the predicted activity session. If there is no match or a lower-priority match, then the activity session may not be initiated. Other embodiments may include other prioritization schemes or priority criteria to determine when or if an activity session will be established. A predicted activity session can be recognized and converted to an Activity Session in the host server (proxy server) in a similar manner. In some embodiments, if an activity session is detected or created by the local proxy, the local proxy can request a multiplexed connection be established to optimize the signaling during the session. If an activity session is identified by the server, the existing TCP connection opened from the mobile device can be converted into a multiplexed session and used for the optimized connection. Alternatively, the first data request from the mobile device can be accomplished outside of the multiplexed connection, and the multiplexed connection can be established for subsequent data transfers. Once an activity session is established and has been acknowledged by the local proxy and/or proxy server, the proxy server can now proactively cache data (e.g., access the URLs or application servers/providers anticipated in the predicted activity sessions) for more rapid access to content anticipated to be needed in the predicted activity session. The system can “piggy-back” transfer of the anticipated data with other data requested by the mobile device for caching in the local cache on the mobile device. These mechanisms effectively increase the availability of desired data on the mobile, and shorten the duration of an established connection needed for the present activity session. One example of a use case for the present technology is described as follows: i. Predicting an activity session based on push activity in the idle state:1. While user is sleeping, his phone has received three push notifications from Facebook, and five emails;2. When user wakes up and checks his phone, he sees these notifications and emails. His natural tendency is to open these two applications and check his emails and Facebook status;3. Upon the transition from screen-lock to unlock, the server recognizes that based on the push activity, the user is likely to get access to these two applications. The device sends a state change notification to the server, and in response, the server sends an activity session indicator to the device. The server pre-caches information relevant to the session, and creates a persistent connection with the device to support the activity session;4. User accesses the services, and is pleased that the relevant data seems to be already on his device;5. The persistent connection is managed by the device and server to time out based on certain criteria, to maximize device battery life. ii. Predicting an activity session based on a change in geographical location during idle state—as a user moves between locations, the system can recognize that they are more likely to engage in certain requests or activities based on the transit route or the new location. iii. Predicting an activity session based on receiving a phone call in idle state based on previous user behavior, the system now recognizes that the user is likely to engage in certain behaviors upon accessing the call (such as checking a specific applications, making certain updates, accessing certain contacts in the contact book, etc.). FIG.1Aillustrates an example diagram of a system where a host server100facilitates management of traffic between client devices102and an application server or content provider110in a wireless network for resource conservation. The client devices102A-D can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server100and/or application server/content provider110. Client devices102will typically include a display and/or other output functionalities to present information and data exchanged between among the devices102and/or the host server100and/or application server/content provider110. For example, the client devices102can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Palm device, Treo, a handheld tablet (e.g., an iPad or any other tablet), a hand held console, a hand held gaming device or console, any SuperPhone such as the iPhone, and/or any other portable, mobile, hand held devices, etc. In one embodiment, the client devices102, host server100, and app server110are coupled via a network106and/or a network108. In some embodiments, the devices102and host server100may be directly connected to one another. The input mechanism on client devices102can include touch screen keypad (including single touch, multi-touch, gesture sensing in2D or3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above. Signals received or detected indicating user activity at client devices102through one or more of the above input mechanism, or others, can be used in the disclosed technology in acquiring context awareness at the client device102. Context awareness at client devices102generally includes, by way of example but not limitation, client device102operation or state acknowledgement, management, user activity/behavior/interaction awareness, detection, sensing, tracking, trending, and/or application (e.g., mobile applications) type, behavior, activity, operating state, etc. Context awareness in the present disclosure also includes knowledge and detection of network side contextual data and can include network information such as network capacity, bandwidth, traffic, type of network/connectivity, and/or any other operational state data. Network side contextual data can be received from and/or queried from network service providers (e.g., cell provider112and/or Internet service providers) of the network106and/or network108(e.g., by the host server and/or devices102). In addition to application context awareness as determined from the client102side, the application context awareness may also be received from or obtained/queried from the respective application/service providers110(by the host100and/or client devices102). The host server100can use, for example, contextual information obtained for client devices102, networks106/108, applications (e.g., mobile applications), application server/provider110, or any combination of the above, to manage the traffic in the system to satisfy data needs of the client devices102(e.g., to satisfy application or any other request including HTTP request). In one embodiment, the traffic is managed by the host server100to satisfy data requests made in response to explicit or non-explicit user103requests and/or device/application maintenance tasks. The traffic can be managed such that network consumption, for example, use of the cellular network is conserved for effective and efficient bandwidth utilization. In addition, the host server100can manage and coordinate such traffic in the system such that use of device102side resources (e.g., including but not limited to battery power consumption, radio use, processor/memory use) are optimized with a general philosophy for resource conservation while still optimizing performance and user experience. For example, in context of battery conservation, the device150can observe user activity (for example, by observing user keystrokes, backlight status, or other signals via one or more input mechanisms, etc.) and alters device102behaviors. The device150can also request the host server100to alter the behavior for network resource consumption based on user activity or behavior. In one embodiment, the traffic management for resource conservation is performed using a distributed system between the host server100and client device102. The distributed system can include proxy server and cache components on the server100side and on the client102side, for example, as shown by the server cache135on the server100side and the local cache150on the client102side. Functions and techniques disclosed for context aware traffic management for resource conservation in networks (e.g., network106and/or108) and devices102, reside in a distributed proxy and cache system. The proxy and cache system can be distributed between, and reside on, a given client device102in part or in whole and/or host server100in part or in whole. The distributed proxy and cache system are illustrated with further reference to the example diagram shown inFIG.1B. Functions and techniques performed by the proxy and cache components in the client device102, the host server100, and the related components therein are described, respectively, in detail with further reference to the examples ofFIGS.2A-3B. In one embodiment, client devices102communicate with the host server100and/or the application server110over network106, which can be a cellular network. To facilitate overall traffic management between devices102and various application servers/content providers110to implement network (bandwidth utilization) and device resource (e.g., battery consumption), the host server100can communicate with the application server/providers110over the network108, which can include the Internet. In general, the networks106and/or108, over which the client devices102, the host server100, and/or application server110communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, UDP, HTTP, DNS, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc. The networks106and/or108can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices102and the host server100and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices102can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS). In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMAX, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMAX, WiMAX2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1×RTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols. FIG.1Billustrates an example diagram of a proxy and cache system distributed between the host server100and device150which facilitates network traffic management between the device150and an application server/content provider100(e.g., a source server) for resource conservation. The distributed proxy and cache system can include, for example, the proxy server125(e.g., remote proxy) and the server cache,135components on the server side. The server-side proxy125and cache135can, as illustrated, reside internal to the host server100. In addition, the proxy server125and cache135on the server-side can be partially or wholly external to the host server100and in communication via one or more of the networks106and108. For example, the proxy server125may be external to the host server and the server cache135may be maintained at the host server100. Alternatively, the proxy server125may be within the host server100while the server cache is external to the host server100. In addition, each of the proxy server125and the cache135may be partially internal to the host server100and partially external to the host server100. The distributed system can also, include, in one embodiment, client-side components, including by way of example but not limitation, a local proxy175(e.g., a mobile client on a mobile device) and/or a local cache185, which can, as illustrated, reside internal to the device150(e.g., a mobile device). In addition, the client-side proxy175and local cache185can be partially or wholly external to the device150and in communication via one or more of the networks106and108. For example, the local proxy175may be external to the device150and the local cache185may be maintained at the device150. Alternatively, the local proxy175may be within the device150while the local cache185is external to the device150. In addition, each of the proxy175and the cache185may be partially internal to the host server100and partially external to the host server100. In one embodiment, the distributed system can include an optional caching proxy server199. The caching proxy server199can be a component which is operated by the application server/content provider110, the host server100, or a network service provider112, and or any combination of the above to facilitate network traffic management for network and device resource conservation. Proxy server199can be used, for example, for caching content to be provided to the device150, for example, from one or more of, the application server/provider110, host server100, and/or a network service provider112. Content caching can also be entirely or partially performed by the remote proxy125to satisfy application requests or other data requests at the device150. In context aware traffic management and optimization for resource conservation in a network (e.g., cellular or other wireless networks), characteristics of user activity/behavior and/or application behavior at a mobile device150can be tracked by the local proxy175and communicated, over the network106to the proxy server125component in the host server100, for example, as connection metadata. The proxy server125which in turn is coupled to the application server/provider110provides content and data to satisfy requests made at the device150. In addition, the local proxy175can identify and retrieve mobile device properties including, one or more of, battery level, network that the device is registered on, radio state, whether the mobile device is being used (e.g., interacted with by a user). In some instances, the local proxy175can delay, expedite (pre-fetch) and/or modify data prior to transmission to the proxy server125, when appropriate, as will be further detailed with references to the description associated with the examples ofFIGS.2A-3B. The local database185can be included in the local proxy175or coupled to the proxy175and can be queried for a locally stored response to the data request prior to the data request being forwarded on to the proxy server125. Locally cached responses can be used by the local proxy175to satisfy certain application requests of the mobile device150, by retrieving cached content stored in the cache storage185, when the cached content is still valid. Similarly, the proxy server125of the host server100can also delay, expedite, or modify data from the local proxy prior to transmission to the content sources (e.g., the app server/content provider110). In addition, the proxy server125uses device properties and connection metadata to generate rules for satisfying request of applications on the mobile device150. The proxy server125can gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device150or other mobile devices. In general, the local proxy175and the proxy server125are transparent to the multiple applications executing on the mobile device. The local proxy175is generally transparent to the operating system or platform of the mobile device and may or may not be specific to device manufacturers. For example, the local proxy may be implemented without adding a TCP stack and thus act transparently to both the US and the mobile applications. In some instances, the local proxy175is optionally customizable in part or in whole to be device specific. In some embodiments, the local proxy175may be bundled into a wireless model, into a firewall, and/or a router. In one embodiment, the host server100can in some instances, utilize the store and forward functions of a short message service center (SMSC)112, such as that provided by the network service provider112, in communicating with the device150in achieving network traffic management. As will be further described with reference to the examples ofFIG.3Aand/orFIG.3B, the host server100can forward content or HTTP responses to the SMSC112such that it is automatically forwarded to the device150if available, and for subsequent forwarding if the device150is not currently available. In general, the disclosed distributed proxy and cache system allows optimization of network usage, for example, by serving requests from the local cache185, the local proxy175reduces the number of requests that need to be satisfied over the network106. Further, the local proxy175and the proxy server125may filter irrelevant data from the communicated data. In addition, the local proxy175and the proxy server125can also accumulate low priority data and send it in batches to avoid the protocol overhead of sending individual data fragments. The local proxy175and the proxy server125can also compress or transcode the traffic, reducing the amount of data sent over the network106and/or108. The signaling traffic in the network106and/or108can be reduced, as the networks are now used less often and the network traffic can be synchronized among individual applications. With respect to the battery life of the mobile device150, by serving application or content requests from the local cache185, the local proxy175can reduce the number of times the radio module is powered up. The local proxy175and the proxy server125can work in conjunction to accumulate low priority data and send it in batches to reduce the number of times and/or amount of time when the radio is powered up. The local proxy175can synchronize the network use by performing the batched data transfer for all connections simultaneously. FIG.2Adepicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a device250that manages traffic in a wireless network for resource conservation. The device250, which can be a portable or mobile device, such as a portable phone, generally includes, for example, a network interface208, an operating system204, a context API206, and mobile applications which may be proxy unaware210or proxy aware220. Note that the device250is specifically illustrated in the example ofFIG.2Aas a mobile device, such is not a limitation and that device250may be any portable/mobile or non-portable device able to receive, transmit signals to satisfy data requests over a network including wired or wireless networks (e.g., Wi-Fi, cellular, Bluetooth, etc.). The network interface208can be a networking module that enables the device250to mediate data in a network with an entity that is external to the host server250, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface208can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, Wi-Fi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater. Device250can further include, client-side components of the distributed proxy and cache system which can include, a local proxy275(e.g., a mobile client of a mobile device) and a cache285. In one embodiment, the local proxy275includes a user activity module215, a proxy API225, a request/transaction manager235, a caching policy manager245, a traffic shaping engine255, and/or a connection manager265. The traffic shaping engine255may further include an alignment module256and/or a batching module257, the connection manager265may further include a radio controller266. The request/transaction manager235can further include an application behavior detector236and/or a prioritization engine241, the application behavior detector236may further include a pattern detector237and/or and application profile generator239. Additional or less components/modules/engines can be included in the local proxy275and each illustrated component. As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware. In one embodiment, a portion of the distributed proxy and cache system for network traffic management resides in or is in communication with device250, including local proxy275(mobile client) and/or cache285. The local proxy275can provide an interface on the device250for users to access device applications and services including email, IM, voice mail, visual voicemail, feeds, Internet, other applications, etc. The proxy275is generally application independent and can be used by applications (e.g., both proxy aware and proxy-unaware mobile applications210and220) to open TCP connections to a remote server (e.g., the server100in the examples ofFIGS.1A-1Band/or server proxy125/325shown in the examples ofFIG.1BandFIG.3A). In some instances, the local proxy275includes a proxy API225which can be optionally used to interface with proxy-aware applications220(or mobile applications on a mobile device). The applications210and220can generally include any user application, widgets, software, HTTP-based application, web browsers, video or other multimedia streaming or downloading application, video games, social network applications, email clients, RSS management applications, application stores, document management applications, productivity enhancement applications, etc. The applications can be provided with the device OS, by the device manufacturer, by the network service provider, downloaded by the user, or provided by others. One embodiment of the local proxy275includes or is coupled to a context API206, as shown. The context API206may be a part of the operating system204or device platform or independent of the operating system204, as illustrated. The operating system204can include any operating system including but not limited to, any previous, current, and/or future versions/releases of, Windows Mobile, iOS, Android, Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc. The context API206may be a plug-in to the operating system204or a particular client application on the device250. The context API206can detect signals indicative of user or device activity, for example, sensing motion, gesture, device location, changes in device location, device backlight, keystrokes, clicks, activated touch screen, mouse click or detection of other pointer devices. The context API206can be coupled to input devices or sensors on the device250to identify these signals. Such signals can generally include input received in response to explicit user input at an input device/mechanism at the device250and/or collected from ambient signals/contextual cues detected at or in the vicinity of the device250(e.g., light, motion, piezoelectric, etc.). In one embodiment, the user activity module215interacts with the context API206to identify, determine, infer, detect, compute, predict, and/or anticipate, characteristics of user activity on the device250. Various inputs collected by the context API206can be aggregated by the user activity module215to generate a profile for characteristics of user activity. Such a profile can be generated by the module215with various temporal characteristics. For instance, user activity profile can be generated in real-time for a given instant to provide a view of what the user is doing or not doing at a given time (e.g., defined by a time window, in the last minute, in the last 30 seconds, etc.), a user activity profile can also be generated for a ‘session’ defined by an application or web page that describes the characteristics of user behavior with respect to a specific task they are engaged in on the device250, or for a specific time period (e.g., for the last 2 hours, for the last 5 hours). Additionally, characteristic profiles can be generated by the user activity module215to depict a historical trend for user activity and behavior (e.g., 1 week, 1 mo, 2 mo, etc.). Such historical profiles can also be used to deduce trends of user behavior, for example, access frequency at different times of day, trends for certain days of the week (weekends or week days), user activity trends based on location data (e.g., IP address, GPS, or cell tower coordinate data) or changes in location data (e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.) to obtain user activity characteristics. In one embodiment, user activity module215can detect and track user activity with respect to applications, documents, files, windows, icons, and folders on the device250. For example, the user activity module215can detect when an application or window (e.g., a web browser) has been exited, closed, minimized, maximized, opened, moved into the foreground, or into the background, multimedia content playback, etc. In one embodiment, characteristics of the user activity on the device250can be used to locally adjust behavior of the device (e.g., mobile device) to optimize its resource consumption such as battery/power consumption and more generally, consumption of other device resources including memory, storage, and processing power. In one embodiment, the use of a radio on a device can be adjusted based on characteristics of user behavior (e.g., by the radio controller266of the connection manager265) coupled to the user activity module215. For example, the radio controller266can turn the radio on or off, based on characteristics of the user activity on the device250. In addition, the radio controller266can adjust the power mode of the radio (e.g., to be in a higher power mode or lower power mode) depending on characteristics of user activity. In one embodiment, characteristics of the user activity on device250can also be used to cause another device (e.g., other computers, a mobile device, or a non-portable device) or server (e.g., host server100and300in the examples ofFIGS.1A-1BandFIGS.3A-3B) which can communicate (e.g., via a cellular or other network) with the device250to modify its communication frequency with the device250. The local proxy275can use the characteristics information of user behavior determined by the user activity module215to instruct the remote device as to how to modulate its communication frequency (e.g., decreasing communication frequency, such as data push frequency if the user is idle, requesting that the remote device notify the device250if new data, changed data, different, data, or data of a certain level of importance becomes available, etc.). In one embodiment, the user activity module215can, in response to determining that user activity characteristics indicate that a user is active after a period of inactivity, request that a remote device (e.g., server host server100and300in the examples ofFIGS.1A-1BandFIGS.3A-3B) send the data that was buffered as a result of the previously decreased communication frequency. In addition, or in alternative, the local proxy275can communicate the characteristics of user activity at the device250to the remote device (e.g., host server100and300in the examples ofFIGS.1A-BandFIGS.3A-3B) and the remote device determines how to alter its own communication frequency with the device250for network resource conservation and conservation of device250resources. One embodiment of the local proxy275further includes a request/transaction manager235, which can detect, identify, intercept, process, manage, data requests initiated on the device250, for example, by applications210and/or220, and/or directly/indirectly by a user request. The request/transaction manager235can determine how and when to process a given request or transaction, or a set of requests/transactions, based on transaction characteristics. The request/transaction manager235can prioritize requests or transactions made by applications and/or users at the device250, for example by the prioritization engine241. Importance or priority of requests/transactions can be determined by the manager235by applying a rule set, for example, according to time sensitivity of the transaction, time sensitivity of the content in the transaction, time criticality of the transaction, time criticality of the data transmitted in the transaction, and/or time criticality or importance of an application making the request. In addition, transaction characteristics can also depend on whether the transaction was a result of user-interaction or other user initiated action on the device (e.g., user interaction with a mobile application). In general, a time critical transaction can include a transaction resulting from a user-initiated data transfer, and can be prioritized as such. Transaction characteristics can also depend on the amount of data that will be transferred or is anticipated to be transferred as a result of the request/requested transaction. For example, the connection manager265, can adjust the radio mode (e.g., high power or low power mode via the radio controller266) based on the amount of data that will need to be transferred. In addition, the radio controller266/connection manager265can adjust the radio power mode (high or low) based on time criticality/sensitivity of the transaction. The radio controller266can trigger the use of high power radio mode when a time-critical transaction (e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria) is initiated or detected. In general, the priorities can be determined or set by default, for example, based on device platform, device manufacturer, operating system, etc. Priorities can alternatively or in additionally be set by the particular application; for example, the Facebook mobile application can set its own priorities for various transactions (e.g., a status update can be of higher priority than an add friend request or a poke request, a message send request can be of higher priority than a message delete request, for example), an email client or IM chat client may have its own configurations for priority. The prioritization engine241may include set of rules for assigning priority. The prioritization engine241can also track network provider limitations or specifications on application or transaction priority in determining an overall priority status for a request/transaction. Furthermore, priority can in part or in whole be determined by user preferences, either explicit or implicit. A user, can in general, set priorities at different tiers, such as, specific priorities for sessions, or types, or applications (e.g., a browsing session, a gaming session, versus an IM chat session, the user may set a gaming session to always have higher priority than an IM chat session, which may have higher priority than web-browsing session). A user can set application-specific priorities, (e.g., a user may set Facebook related transactions to have a higher priority than LinkedIn related transactions), for specific transaction types (e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.), and/or for specific folders. The prioritization engine241can track and resolve conflicts in priorities set by different entities. For example, manual settings specified by the user may take precedence over device OS settings, network provider parameters/limitations (e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type) may limit any user-specified settings and/or application-set priorities. In some instances, a manual sync request received from a user can override some, most, or all priority settings in that the requested synchronization is performed when requested, regardless of the individually assigned priority or an overall priority ranking for the requested action. Priority can be specified and tracked internally in any known and/or convenient manner, including but not limited to, a binary representation, a multi-valued representation, a graded representation and all are considered to be within the scope of the disclosed technology. TABLE IChangeChange(initiated on device)Priority(initiated on server)PrioritySend emailHighReceive emailHighDelete emailLowEdit emailOften not(Un)read emailLowpossible to sync(Low ifpossible)Move messageLowNew email in deletedLowRead moreHighitemsDown loadHighDelete an emailLowattachment(Un)Read an emailLowNew Calendar eventHighMove messagesLowEdit/changeHighAny calendar changeHighCalendar eventAny contact changeHighAdd a contactHighWipe/lock deviceHighEdit a contactHighSettings changeHighSearch contactsHighAny folder changeHighChange a settingHighConnector restartHigh (if nochanges nothingManual send/receiveHighis sent)IM status changeMediumSocial NetworkMediumStatus UpdatesAuction outbid orHighSevere WeatherHighchange notificationAlertsWeather UpdatesLowNews UpdatesLow Table I above shows, for illustration purposes, some examples of transactions with examples of assigned priorities in a binary representation scheme. Additional assignments are possible for additional types of events, requests, transactions, and as previously described, priority assignments can be made at more or less granular levels, e.g., at the session level or at the application level, etc. As shown by way of example in the above table, in general, lower priority requests/transactions can include, updating message status as being read, unread, deleting of messages, deletion of contacts; higher priority requests/transactions, can in some instances include, status updates, new IM chat message, new email, calendar event update/cancellation/deletion, an event in a mobile gaming session, or other entertainment related events, a purchase confirmation through a web purchase or online, request to load additional or download content, contact book related events, a transaction to change a device setting, location-aware or location-based events/transactions, or any other events/request/transactions initiated by a user or where the user is known to be, expected to be, or suspected to be waiting for a response, etc. Inbox pruning events (e.g., email, or any other types of messages), are generally considered low priority and absent other impending events, generally will not trigger use of the radio on the device250. Specifically, pruning events to remove old email or other content can be ‘piggy backed’ with other communications if the radio is not otherwise on, at the time of a scheduled pruning event. For example, if the user has preferences set to ‘keep messages for 7 days old,’ then instead of powering on the device radio to initiate a message delete from the device250the moment that the message has exceeded 7 days old, the message is deleted when the radio is powered on next. If the radio is already on, then pruning may occur as regularly scheduled. The request/transaction manager235, can use the priorities for requests (e.g., by the prioritization engine241) to manage outgoing traffic from the device250for resource optimization (e.g., to utilize the device radio more efficiently for battery conservation). For example, transactions/requests below a certain priority ranking may not trigger use of the radio on the device250if the radio is not already switched on, as controlled by the connection manager265. In contrast, the radio controller266can turn on the radio such a request can be sent when a request for a transaction is detected to be over a certain priority level. In one embodiment, priority assignments (such as that determined by the local proxy275or another device/entity) can be used cause a remote device to modify its communication with the frequency with the mobile device. For example, the remote device can be configured to send notifications to the device250when data of higher importance is available to be sent to the mobile device. In one embodiment, transaction priority can be used in conjunction with characteristics of user activity in shaping or managing traffic, for example, by the traffic shaping engine255. For example, the traffic shaping engine255can, in response to detecting that a user is dormant or inactive, wait to send low priority transactions from the device250, for a period of time. In addition, the traffic shaping engine255can allow multiple low priority transactions to accumulate for batch transferring from the device250(e.g., via the batching module257). In one embodiment, the priorities can be set, configured, or readjusted by a user. For example, content depicted in Table I in the same or similar form can be accessible in a user interface on the device250and for example, used by the user to adjust or view the priorities. The batching module257can initiate batch transfer based on certain criteria. For example, batch transfer (e.g., of multiple occurrences of events, some of which occurred at different instances in time) may occur after a certain number of low priority events have been detected, or after an amount of time elapsed after the first of the low priority event was initiated. In addition, the batching module257can initiate batch transfer of the cumulated low priority events when a higher priority event is initiated or detected at the device250. Batch transfer can otherwise be initiated when radio use is triggered for another reason (e.g., to receive data from a remote device such as host server100or300). In one embodiment, an impending pruning event (pruning of an inbox), or any other low priority events, can be executed when a batch transfer occurs. In general, the batching capability can be disabled or enabled at the event/transaction level, application level, or session level, based on any one or combination of the following: user configuration, device limitations/settings, manufacturer specification, network provider parameters/limitations, platform specific limitations/settings, device OS settings, etc. In one embodiment, batch transfer can be initiated when an application/window/file is closed out, exited, or moved into the background; users can optionally be prompted before initiating a batch transfer; users can also manually trigger batch transfers. In one embodiment, the local proxy275locally adjusts radio use on the device250by caching data in the cache285. When requests or transactions from the device250can be satisfied by content stored in the cache285, the radio controller266need not activate the radio to send the request to a remote entity (e.g., the host server100,300, as shown inFIGS.1A-1BandFIGS.3A-3Bor a content provider/application server such as the server/provider110shown in the examples ofFIGS.1A-1B). As such, the local proxy275can use the local cache285and the cache policy manager245to locally store data for satisfying data requests to eliminate or reduce the use of the device radio for conservation of network resources and device battery consumption. In leveraging the local cache, once the request/transaction manager225intercepts a data request by an application on the device250, the local repository285can be queried to determine if there is any locally stored response, and also determine whether the response is valid. When a valid response is available in the local cache285, the response can be provided to the application on the device250without the device250needing to access the cellular network. If a valid response is not available, the local proxy275can query a remote proxy (e.g., the server proxy325ofFIG.3A) to determine whether a remotely stored response is valid. If so, the remotely stored response (e.g., which may be stored on the server cache135or optional caching server199shown in the example ofFIG.1B) can be provided to the mobile device, possibly without the mobile device250needing to access the cellular network, thus relieving consumption of network resources. If a valid cache response is not available, or if cache responses are unavailable for the intercepted data request, the local proxy275, for example, the caching policy manager245, can send the data request to a remote proxy (e.g., server proxy325ofFIG.3A) which forwards the data request to a content source (e.g., application server/content provider110ofFIG.1A) and a response from the content source can be provided through the remote proxy, as will be further described in the description associated with the example host server300ofFIG.3A. The cache policy manager245can manage or process requests that use a variety of protocols, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP and/or ActiveSync. The caching policy manager245can locally store responses for data requests in the local database285as cache entries, for subsequent use in satisfying same or similar data requests. The manager245can request that the remote proxy monitor responses for the data request, and the remote proxy can notify the device250when an unexpected response to the data request is detected. In such an event, the cache policy manager245can erase or replace the locally stored response(s) on the device250when notified of the unexpected response (e.g., new data, changed data, additional data, different response, etc.) to the data request. In one embodiment, the caching policy manager245is able to detect or identify the protocol used for a specific request, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP and/or ActiveSync. In one embodiment, application specific handlers (e.g., via the application protocol module246of the manager245) on the local proxy275allows for optimization of any protocol that can be port mapped to a handler in the distributed proxy (e.g., port mapped on the proxy server325in the example ofFIG.3A). In one embodiment, the local proxy275notifies the remote proxy such that the remote proxy can monitor responses received for the data request from the content source for changed results prior to returning the result to the device250, for example, when the data request to the content source has yielded same results to be returned to the mobile device. In general, the local proxy275can simulate application server responses for applications on the device250, using locally cached content. This can prevent utilization of the cellular network for transactions where new/changed/different data is not available, thus freeing up network resources and preventing network congestion. In one embodiment, the local proxy275includes an application behavior detector236to track, detect, observe, monitor, applications (e.g., proxy aware and/or unaware applications210and220) accessed or installed on the device250. Application behaviors, or patterns in detected behaviors (e.g., via the pattern detector237) of one or more applications accessed on the device250can be used by the local proxy275to optimize traffic in a wireless network needed to satisfy the data needs of these applications. For example, based on detected behavior of multiple applications, the traffic shaping engine255can align content requests made by at least some of the applications over the network (wireless network) (e.g., via the alignment module256). The alignment module can delay or expedite some earlier received requests to achieve alignment. When requests are aligned, the traffic shaping engine255can utilize the connection manager to poll over the network to satisfy application data requests. Content requests for multiple applications can be aligned based on behavior patterns or rules/settings including, for example, content types requested by the multiple applications (audio, video, text, etc.), mobile device parameters, and/or network parameters/traffic conditions, network service provider constraints/specifications, etc. In one embodiment, the pattern detector237can detect recurrences in application requests made by the multiple applications, for example, by tracking patterns in application behavior. A tracked pattern can include, detecting that certain applications, as a background process, poll an application server regularly, at certain times of day, on certain days of the week, periodically in a predictable fashion, with a certain frequency, with a certain frequency in response to a certain type of event, in response to a certain type user query, frequency that requested content is the same, frequency with which a same request is made, interval between requests, applications making a request, or any combination of the above, for example. Such recurrences can be used by traffic shaping engine255to offload polling of content from a content source (e.g., from an application server/content provider110ofFIGS.1A-1B) that would result from the application requests that would be performed at the mobile device250to be performed instead, by a proxy server (e.g., proxy server125ofFIG.1Bor proxy server325ofFIG.3A) remote from the device250. Traffic engine255can decide to offload the polling when the recurrences match a rule. For example, there are multiple occurrences or requests for the same resource that have exactly the same content, or returned value, or based on detection of repeatable time periods between requests and responses such as a resource that is requested at specific times during the day. The offloading of the polling can decrease the amount of bandwidth consumption needed by the mobile device250to establish a wireless (cellular) connection with the content source for repetitive content polls. As a result of the offloading of the polling, locally cached content stored in the local cache285can be provided to satisfy data requests at the device250, when content change is not detected in the polling of the content sources. As such, when data has not changed, application data needs can be satisfied without needing to enable radio use or occupying cellular bandwidth in a wireless network. When data has changed, or when data is different, and/or new data has been received, the remote entity to which polling is offloaded, can notify the device250. The remote entity may be the host server300as shown in the example ofFIG.3A. In one embodiment, the local proxy275can mitigate the need/use of periodic keep alive messages (heartbeat messages) to maintain TCP/IP connections, which can consume significant amounts of power thus having detrimental impacts on mobile device battery life. The connection manager265in the local proxy (e.g., the heartbeat manager267) can detect, identify, and intercept any or all heartbeat (keep-alive) messages being sent from applications. The heartbeat manager267can prevent any or all of these heartbeat messages from being sent over the cellular, or other network, and instead rely on the server component of the distributed proxy system (e.g., shown inFIG.1B) to generate the and send the heartbeat messages to maintain a connection with the backend (e.g., app server/provider110in the example ofFIGS.1A-1B). The local proxy275generally represents any one or a portion of the functions described for the individual managers, modules, and/or engines. The local proxy275and device250can include additional or less components; more or less functions can be included, in whole or in part, without deviating from the novel art of the disclosure. FIG.2Bdepicts a block diagram illustrating another example of components in the application behavior detector236and the traffic shaping engine255in the local proxy275on the client-side of the distributed proxy system shown in the example ofFIG.2A. In one embodiment, the pattern detector237of the application behavior detector236further includes a correlation detector238and the application profile generator239further includes an application status detector240. The correlation detector238, in one embodiment, can detect, determine, identify, compute, track, any correlations in the timing of data transfer requests made by applications, agents, and/or widgets accessed via (e.g., application streaming or accessed through a cloud) or running on the device250. In general, correlation types include event-level correlations and application-level correlations, and can include system/application. The correlation detector238can track and monitor system/application triggered events and/or user-triggered events/transactions. In addition, the correlation detector238can identify or track correlations between events for a given application or across different applications. A correlation can be detected, for example, when a first event/transaction type of a first application triggers the initiation of a second event/transaction type of the same application. The triggering can be detected by the correlation detector238through identifying patterns in the timing characteristics of such events occurring within the first application. For example, a correlation can include, an identification of the ordering of the first and second event/transaction types (e.g., the second event type always occurs after the first event type). A correlation can also include, determining that the first and second event/transaction types occur within a timeframe of one another (e.g., the first event type occurs within a 10 ms time window of the second event type), etc. A correlation can also be detected, for example, when a specific event type of one application triggers a specific event type of another application (or has a timing or ordering relationship thereof). Similarly, the correlation detector238can detect that operation of one application (e.g., such as the launching of one application or any other activity) is related to the operation of another application. For example, the detector can determine that if one application is launched, the other application is also launched. The detector can also detect that one application is always launched within a certain time window of another application being launched/accessed, or the activity status of one application is linked to the application status of the activity status of another application (e.g., when one application moves into the foreground/background, the other application moves into the foreground/background, or when one application becomes active/inactive, the other application also changes state and becomes either active or inactive, etc.). Generally, such events/transactions detected and tracked for correlation can include system or application-initiated events, or user-triggered events (e.g., including explicit user requests or implicit user requests). In some instances, the correlation detector238uses user activity module215and can also detect application or application event correlations in relation to and/or in conjunction with user activity. For example, the correlation detector238can determine that an occurrence of a first event type frequently causes the user to perform an action which triggers a second event (of the same application or different application). While examples are described herein for two events and examples given for two applications, note that the correlation detector238can track, detect, and identify correlations in occurrences of events/transactions, correlations for multiple events (e.g., 2, 3, 4, 5, etc.) that can be detected and identified. In general, the correlation detector238tracks the timing characteristics of requests made by applications to detect correlations. The correlations can be incorporated into an application's profile by the profile generator239. In one embodiment, the profile generator includes an application status detector240. The application status detector240can detect an activity state of an application on the device250. An activity state can indicate, by way of example but not limitation, whether a specific application is operating in the background or foreground on the mobile device250, whether the application is active or inactive, whether the application is being interacted with (e.g., by a user, or another application or device). The activity state or status of an application on the device250can also be included in an application's profile (e.g., by the profile generator239) along with any correlation with other events or applications and used for data request alignment. For example, one embodiment of the alignment module256of the traffic shaping engine255which is able to use the application behavior (e.g., as determined by the application behavior detector236) of one or multiple applications on a device250to align some of the content requests (e.g., aligned by the alignment module256) made by the same application or at least a portion the multiple applications from the mobile device over the network. The application behaviors can be indicated in application profiles generated by the application profile generator239, for example. In some instances the content requests (made by the same application or different applications) are aligned by delaying or expediting a time at which some of the content requests would occur without alignment and the traffic shaping engine256can transfer the content requests that are delayed or expedited in a single transfer operation over the network (cellular or other wireless network). The amount of time that a request can be delayed (time ‘D’) is generally determined (e.g., by the delay module258) to optimize a number of content requests able to be aligned in the single transfer operation. Hence delay module258can utilize the correlations in event/transaction occurrences within an application or across multiple applications as identified by the correlation detector238in determining delay time for aligning multiple requests. The delay time ‘D’ (e.g., refers to the time by which a request is expedited or delayed) is generally determined based on application behavior (e.g., as determined by the application behavior detector236and/or indicated in an application profile). More specifically, the time that is delayed in transfer of a given content request can be determined based on priority of a specific application (e.g., as determined by the prioritization engine241of the application behavior detector236) making the given content request, or based on the priority of the specific application relative to other applications on the mobile device250. In addition, the delay module258can determine delays in transfer further based on, one or more of amount of data involved in the given content request, a nature of data involved in the given content request, usable lifetime of data to be transferred in the given content request, and/or network characteristics including available bandwidth or network latency. Thus in one example of a system level operation in aligning requests, the local proxy275of the device250detects a first data request made via a first application and a second data request made via a second application, or where first and second data requests are made by the same application. The alignment module256of the traffic shaping engine255in the local proxy275on the device250can delay the transfer of the first data transfer request made via the first application to the proxy server (e.g., proxy server125or325in the examples ofFIG.1BandFIG.3A) until another data transfer request made via the second application is detected by the local proxy275such that the transfer the first data transfer request and the second data transfer request occur in a single transfer operation over the network (thus needing to enable radio use only once, assuming that the radio was off on the device250when the first data request occurred). The delay of the first data transfer request can be determined by the delay module258and the decision can be made when, for example, the second application is of a higher priority relative to the first application, or that the second application is running in the foreground, or that a user is interacting with the second application and the second data request is initiated in response to the user interaction, or that the second application is more data intensive than the first application. FIG.2Cdepicts a block diagram illustrating another example of the user activity module215having a prediction engine216in the local proxy275on the client-side of the distributed proxy system shown in the example ofFIG.2A. As described inFIG.2A, the user activity module215is able to detect, track, monitor, process, analyze, user activities at the mobile device250. The user activities can be used to determine user activity characteristics such as tracking user activity given the time of day or day of the week, tracking frequency of application use, tracking an order with which new data is accessed or an order with which applications are accessed on the mobile device, etc. The activity module215can generally detect, determine, track, analyze user actions to determine characteristics for user actions, which can include habits, tendencies, or patterns. The activity module215can identify a user's general behavior with respect to using the device250. For example, the activity module215can determine that a user uses the device250more frequently during certain hours of the day, or days of the week; the module can determine that the user250has a preference for calling vs. SMS based on time, day of week, etc; time/day-dependent preference for using certain applications, types of applications, checking certain email accounts (e.g., if a user tends to check one email account more frequently during the week and another email account during the weekend), time/day-dependent frequency of checking certain applications (e.g., if a user checks Facebook more often on weekends, or in the afternoons during weekdays compared to in the morning; if a user Tweets more at night or in the day time; if a user uses Yelp mobile more on the weekends or on the weekdays, or during the daytime or night time); if a user tends to access, launch, check applications, accounts, services in a certain order (whether the ordering has time/day dependencies). The user's behavior with respect to a particular application can be determined by the module215. For example, the activity module215can detect, identify, analyze, or process a user's activities on a certain application, account, or service. The module215can, for instance, determine that the user tends to use certain features but not others on a certain application (e.g., a user tends to use Facebook Walls for messaging rather than private messaging), a user tends to communicate with one individual via one service and another individual via another service, etc. In addition to time/day dependent preferences or time/day dependent frequencies of use/access, the above actions may also include location-based dependencies, or location-based dependencies in conjunction with time/day based dependencies. For example, the activity module215can determine that a user uses Google maps when the device250is detected to be on-the-go, or when the user is away from a specific geo-location (e.g., home location or office location), etc. The activity module215can determine that the frequency with which a user uses certain applications or accounts changes with geo-location, and/or when the user is determined to be on-the-go, or traveling, etc. In one embodiment, the user activity module215can detect, identify, and/or determining a user's quiet time (e.g., the user is sleeping or otherwise does not use the device250(e.g., or if the user is driving/commuting), a time when the user turns off certain connections, closes out of certain applications, or does not check certain applications, accounts, and/or services, etc. Based on the tracked user behaviors, activities, habits, tendencies, the prediction engine216can use any of the information related to user activity characteristics to predict user behavior, and use the predicted user behavior to anticipate or predict future activity sessions at the device250. Predicted activity sessions can be used to facilitate data transfer to optimize network use and can have the advantage of also enhancing user experience with mobile applications/accounts. For example, the prediction engine216can communicate any predicted activity sessions or predicted user behavior to the proxy server325for use in determining a timing with which to transfer impending data from the host server (e.g., server300ofFIG.3A) to the device250. For example, the prediction engine216may, based on determined user activities and past behavior, determine that the user typically accesses his/her Outlook Enterprise email account at around 7:30 am most week day mornings. The prediction engine216can then generate a predicted activity session for this email access event for use by the host server to time when emails for the email account are transmitted to the device250. For example, the server may not need to initiate a transaction to push emails received between 3 am-7 am to the device250until around 7:15 or some time before the predicted activity session since the user is not expected to access it until around 7:30 am. This way, network resources can be conserved, as can power consumption of the device250. In some instances, the server can in addition to, or instead use the behavior of a content provider/application server (e.g., the server/provider110in the examples ofFIG.1A-1Bwith which the mobile device250interacts to satisfy content requests or needs of the device250) to determine an optimal timing with which to transfer data to the mobile device, as will be further described in conjunction with the example ofFIG.3B. The activity of the provider/server can be detected and/or tracked through the server-side of the proxy system, as shown in the example ofFIG.3B. FIG.3Adepicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system residing on a host server300that manages traffic in a wireless network for resource conservation. The host server300generally includes, for example, a network interface308and/or one or more repositories312,314,316. Note that server300may be any portable/mobile or non-portable device, server, cluster of computers and/or other types of processing units (e.g., any number of a machine shown in the example ofFIG.11) able to receive, transmit signals to satisfy data requests over a network including any wired or wireless networks (e.g., Wi-Fi, cellular, Bluetooth, etc.). The network interface308can include networking module(s) or devices(s) that enable the server300to mediate data in a network with an entity that is external to the host server300, through any known and/or convenient communications protocol supported by the host and the external entity. Specifically, the network interface308allows the server308to communicate with multiple devices including mobile phone devices350, and/or one or more application servers/content providers310. The host server300can store information about connections (e.g., network characteristics, conditions, types of connections, etc.) with devices in the connection metadata repository312. Additionally, any information about third party application or content providers can also be stored in312. The host server300can store information about devices (e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.) in the device information repository314. Additionally, the host server300can store information about network providers and the various network service areas in the network service provider repository316. The communication enabled by308allows for simultaneous connections (e.g., including cellular connections) with devices350and/or connections (e.g., including wired/wireless, HTTP, Internet connections, LAN, Wi-Fi, etc.) with content servers/providers310, to manage the traffic between devices350and content providers310, for optimizing network resource utilization and/or to conserver power (battery) consumption on the serviced devices350. The host server300can communicate with mobile devices350serviced by different network service providers and/or in the same/different network service areas. The host server300can operate and is compatible with devices350with varying types or levels of mobile capabilities, including by way of example but not limitation, 1G, 2G, 2G transitional (2.5G, 2.75G), 3G (IMT-2000), 3G transitional (3.5G, 3.75G, 3.9G), 4G (IMT-advanced), etc. In general, the network interface308can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, Wi-Fi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G type networks such as LTE, WiMAX, etc.), Bluetooth, Wi-Fi, or any other network whether or not connected via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater. The host server300can further include, server-side components of the distributed proxy and cache system which can include, a proxy server325and a server cache335. In one embodiment, the server proxy325can include an HTTP access engine345, a caching policy manager355, a proxy controller365, a traffic shaping engine375, a new data detector386, and/or a connection manager395. The HTTP access engine345may further include a heartbeat manager346, the proxy controller365may further include a data invalidator module366, the traffic shaping engine375may further include a control protocol276and a batching module377. Additional or less components/modules/engines can be included in the proxy server325and each illustrated component. As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, or engine can be centralized or its functionality distributed. The module, manager, handler, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware. In the example of a device (e.g., mobile device350) making an application or content request to an app server or content provider310, the request may be intercepted and routed to the proxy server325, which is coupled to the device350and the provider310. Specifically, the proxy server is able to communicate with the local proxy (e.g., proxy175and275of the examples ofFIG.1andFIGS.2A-2Crespectively) of the device350, the local proxy forwards the data request to the proxy server325for, in some instances, further processing, and if needed, for transmission to the content server310for a response to the data request. In such a configuration, the host300, or the proxy server325in the host server300can utilize intelligent information provided by the local proxy in adjusting its communication with the device in such a manner that optimizes use of network and device resources. For example, the proxy server325can identify characteristics of user activity on the device350to modify its communication frequency. The characteristics of user activity can be determined by, for example, the activity/behavior awareness module366in the proxy controller365, via information collected by the local proxy on the device350. In one embodiment, communication frequency can be controlled by the connection manager396of the proxy server325, for example, to adjust push frequency of content or updates to the device350. For instance, push frequency can be decreased by the connection manager396when characteristics of the user activity indicate that the user is inactive. In one embodiment, when the characteristics of the user activity indicate that the user is subsequently active after a period of inactivity, the connection manager396can adjust the communication frequency with the device350to send data that was buffered as a result of decreased communication frequency, to the device350. In addition, the proxy server325includes priority awareness of various requests, transactions, sessions, applications, and/or specific events. Such awareness can be determined by the local proxy on the device350and provided to the proxy server325. The priority awareness module367of the proxy server325can generally assess the priority (e.g., including time-criticality, time-sensitivity, etc.) of various events or applications; additionally, the priority awareness module367can track priorities determined by local proxies of devices350. In one embodiment, through priority awareness, the connection manager395can further modify communication frequency (e.g., use or radio as controlled by the radio controller396) of the server300with the devices350. For example, the server300can notify the device350, thus requesting use of the radio if it is not already in use, when data or updates of an importance/priority level which meets a criteria becomes available to be sent. In one embodiment, the proxy server325can detect multiple occurrences of events (e.g., transactions, content, data received from server/provider310) and allow the events to accumulate for batch transfer to device350. Batch transfer can be cumulated and transfer of events can be delayed based on priority awareness and/or user activity/application behavior awareness, as tracked by modules366and/or367. For example, batch transfer of multiple events (of a lower priority) to the device350can be initiated by the batching module377when an event of a higher priority (meeting a threshold or criteria) is detected at the server300. In addition, batch transfer from the server300can be triggered when the server receives data from the device350, indicating that the device radio is already in use and is thus on. In one embodiment, the proxy server324can order the each messages/packets in a batch for transmission based on event/transaction priority, such that higher priority content can be sent first, in case connection is lost or the battery dies, etc. In one embodiment, the server300caches data (e.g., as managed by the caching policy manager355) such that communication frequency over a network (e.g., cellular network) with the device350can be modified (e.g., decreased). The data can be cached, for example in the server cache335, for subsequent retrieval or batch sending to the device350to potentially decrease the need to turn on the device350radio. The server cache335can be partially or wholly internal to the host server300, although in the example ofFIG.3A, it is shown as being external to the host300. In some instances, the server cache335may be the same as and/or integrated in part or in whole with another cache managed by another entity (e.g., the optional caching proxy server199shown in the example ofFIG.1B), such as being managed by an application server/content provider110, a network service provider, or another third party. In one embodiment, content caching is performed locally on the device350with the assistance of host server300. For example, proxy server325in the host server300can query the application server/provider310with requests and monitor changes in responses. When changed, different or new responses are detected (e.g., by the new data detector347), the proxy server325can notify the mobile device350, such that the local proxy on the device350can make the decision to invalidate (e.g., indicated as outdated) the relevant cache entries stored as any responses in its local cache. Alternatively, the data invalidator module368can automatically instruct the local proxy of the device350to invalidate certain cached data, based on received responses from the application server/provider310. The cached data is marked as invalid, and can get replaced or deleted when new content is received from the content server310. Note that data change can be detected by the detector347in one or more ways. For example, the server/provider310can notify the host server300upon a change. The change can also be detected at the host server300in response to a direct poll of the source server/provider310. In some instances, the proxy server325can in addition, pre-load the local cache on the device350with the new/updated/changed/different data. This can be performed when the host server300detects that the radio on the mobile device is already in use, or when the server300has additional content/data to be sent to the device350. One or more the above mechanisms can be implemented simultaneously or adjusted/configured based on application (e.g., different policies for different servers/providers310). In some instances, the source provider/server310may notify the host300for certain types of events (e.g., events meeting a priority threshold level). In addition, the provider/server310may be configured to notify the host300at specific time intervals, regardless of event priority. In one embodiment, the proxy server325of the host300can monitor/track responses received for the data request from the content source for changed results prior to returning the result to the mobile device, such monitoring may be suitable when data request to the content source has yielded same results to be returned to the mobile device, thus preventing network/power consumption from being used when no new/changes are made to a particular requested. The local proxy of the device350can instruct the proxy server325to perform such monitoring or the proxy server325can automatically initiate such a process upon receiving a certain number of the same responses (e.g., or a number of the same responses in a period of time) for a particular request. In one embodiment, the server300, for example, through the activity/behavior awareness module366, is able to identify or detect user activity, at a device that is separate from the mobile device350. For example, the module366may detect that a user's message inbox (e.g., email or types of inbox) is being accessed. This can indicate that the user is interacting with his/her application using a device other than the mobile device350and may not need frequent updates, if at all. The server300, in this instance, can thus decrease the frequency with which new, different, changed, or updated content is sent to the mobile device350, or eliminate all communication for as long as the user is detected to be using another device for access. Such frequency decrease may be application specific (e.g., for the application with which the user is interacting with on another device), or it may be a general frequency decrease (e.g., since the user is detected to be interacting with one server or one application via another device, he/she could also use it to access other services) to the mobile device350. In one embodiment, the host server300is able to poll content sources310on behalf of devices350to conserve power or battery consumption on devices350. For example, certain applications on the mobile device350can poll its respective server310in a predictable recurring fashion. Such recurrence or other types of application behaviors can be tracked by the activity/behavior module366in the proxy controller365. The host server300can thus poll content sources310for applications on the mobile device350, that would otherwise be performed by the device350through a wireless (e.g., including cellular connectivity). The host server can poll the sources310for new, different, updated, or changed data by way of the HTTP access engine345to establish HTTP connection or by way of radio controller396to connect to the source310over the cellular network. When new, different, updated, or changed data is detected, the new data detector can notify the device350that such data is available and/or provide the new/changed data to the device350. In one embodiment, the connection manager395determines that the mobile device350is unavailable (e.g., the radio is turned off) and utilizes SMS to transmit content to the device350, for instance via the SMSC shown in the example ofFIG.1B. SMS may be used to transmit invalidation messages, batches of invalidation messages, or even content in the case the content is small enough to fit into just a few (usually one or two) SMS messages. This avoids the need to access the radio channel to send overhead information. The host server300can use SMS for certain transactions or responses having a priority level above a threshold or otherwise meeting a criteria. The server300can also utilize SMS as an out-of-band trigger to maintain or wake-up an IP connection as an alternative to maintaining an always-on IP connection. In one embodiment, the connection manager395in the proxy server325(e.g., the heartbeat manager398) can generate and/or transmit heartbeat messages on behalf of connected devices350, to maintain a backend connection with a provider310for applications running on devices350. For example, in the distributed proxy system, local cache on the device350can prevent any or all heartbeat messages needed to maintain TCP/IP connections required for applications, from being sent over the cellular, or other network, and instead rely on the proxy server325on the host server300to generate and/or send the heartbeat messages to maintain a connection with the backend (e.g., app server/provider110in the example ofFIGS.1A-1B). The proxy server can generate the keep-alive (heartbeat) messages independent of the operations of the local proxy on the mobile device. The repositories312,314, and/or316can additionally store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server300and/or any other servers for operation. The repositories may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc. The repositories can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package. FIG.3Bdepicts a block diagram illustrating another example of the server-side components of the distributed proxy system shown in the example ofFIG.3Aas further including a user experience (UE) enhancement engine385and with the traffic shaping engine375further including a delay module378. The UE enhancement engine385may further include an activity prediction engine386having a server activity tracker387, a contextual data tracker389and/or a pre-caching engine390. The server activity tracker387can track the activity or behavior of a server (application server/content provider110in the examples ofFIG.1A-1B) for use in predicting data activity at the app server/content provider. The activity/behavior determined by the activity tracker can be used, for example, by the traffic shaping engine375in determining a timing with which data received from the server is to be transmitted to a mobile device. In general, the server is a host (e.g., Facebook server, email server, RSS service, any other web services, etc.) with which the mobile device interacts to satisfy content requests/needs. In general, server activity/behavior can include any action or activity detected on the server for servicing content requests made by an associated application, service, or account on a device (e.g., device250in the example ofFIG.2A). Server activity can include, for example, amount of impending data to be transferred to the mobile device, last-accessed time or a frequency of access, etc. Determined or detected server activity can be used in determining a timing with which to transfer impending data from the host server. For example, if the activity tracker387detects that a recent data transfer was made from the Facebook server to the device, the traffic shaping engine375, may delay the time (e.g., via the delay module378) with which the next data transfer is to be made, for example, based on predicted future activity session. Alternatively, in response to determining that a large amount of data is impending at the host to be sent to the mobile device, the traffic shaping engine375may decide to initiate a transfer without delay or with minimal delay. One embodiment of the activity prediction engine386further includes a contextual data tracker389to detect contextual data for use in the anticipation of future activity session(s). Contextual data can be used alone or in conjunction with server activity by the prediction engine386in anticipating future activity sessions (e.g., future activity, future data events/transactions at a content host/app server/provider). Contextual data can include, for example, location changes or motion of a mobile device, states or statuses of applications on the mobile device (e.g., if the application is active or inactive, running in the foreground or background, if a user is actively interacting with the application or if background maintenance processes are running, etc.). Contextual data can be determined from one or more hardware sensors on a device, for example, device backlight, a device electronic compass, motion sensor, tilt sensor, light sensor, gesture sensor, input detector (keyboard, mouse, touch screen), proximity sensor, capacitive sensor, resistive sensor, image detector, a camera, GPS receiver, etc. In one embodiment, the traffic shaping engine375can categorize the activity that is being processed by the host server300since the last user activity session. Predicted or anticipated activity sessions which can be generated by the activity prediction engine386can include: 1) A list of URLs representing application servers/content providers (e.g., the provider/server110ofFIGS.1A-1B); 2) For each URL, a count of impending data that is available to the user for that URL to be transmitted to the device; 3) For each URL, a last-accessed time and/or a frequency of access. Once created, the traffic shaping engine375can prioritize the app servers/content providers (or the representing URLs) based on last accessed time, frequency, impending data count, or other criteria to form a prioritized list of host URL targets. This predicted or anticipated activity session may form the basis for predicting whether a subsequent mobile device data request will activate the session (i.e., turn the predicted activity session into an activity session). The predicted activity session can be used by the traffic shaping engine375to determining a timing with which to transfer impending data from the host server to the mobile device to support predicted data activity for the future activity session. In one embodiment, transfer of the impending content is performed over a multiplexed TCP connection supporting multiple HTTP sessions. In some instances, the impending content is transferred from the host server the mobile device to pre-cache content (e.g., by the pre-caching module390) on the mobile device to support predicted data activity for the future activity session. The pre-caching can enhance a user's experience since the data is provided to the user before it is actually requested (e.g., in the predicted activity session). FIG.4Adepicts a diagram showing how data requests from a mobile device450to an application server/content provider496in a wireless network can be coordinated by a distributed proxy system460in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system460. In satisfying application or client requests on a mobile device450without the distributed proxy system460, the mobile device450, or the software widget executing on the device450performs a data request402(e.g., an HTTP GET, POST, or other request) directly to the application server495and receives a response404directly from the server/provider495. If the data has been updated, the widget on the mobile device450can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider495. In one embodiment, the requesting client or software widget455on the device450can utilize the distributed proxy system460in handling the data request made to server/provider495. In general, the distributed proxy system460can include a local proxy465(which is typically considered a client-side component of the system460and can reside on the mobile device450), a caching proxy (475, considered a server-side component470of the system460and can reside on the host server485or be wholly or partially external to the host server485), a host server485. The local proxy465can be connected to the proxy475and host server485via any network or combination of networks. When the distributed proxy system460is used for data/application requests, the widget455can perform the data request406via the local proxy465. The local proxy465, can intercept the requests made by device applications, and can identify the connection type of the request (e.g., an HTTP get request or other types of requests). The local proxy465can then query the local cache for any previous information about the request (e.g., to determine whether a locally stored response is available and/or still valid). If a locally stored response is not available or if there is an invalid response stored, the local proxy465can update or store information about the request, the time it was made, and any additional data, in the local cache. The information can be updated for use in potentially satisfying subsequent requests. The local proxy465can then send the request to the host server485and the server485can perform the request406and returns the results in response408. The local proxy465can store the result and in addition, information about the result and returns the result to the requesting widget455. In one embodiment, if the same request has occurred multiple times (within a certain time period) and it has often yielded same results, the local proxy465can notify410the server485that the request should be monitored (e.g., steps412and414) for result changes prior to returning a result to the local proxy465or requesting widget455. In one embodiment, if a request is marked for monitoring, the local proxy465can now store the results into the local cache. Now, when the data request416, for which a locally response is available, is made by the widget455and intercepted at the local proxy465, the proxy465can return the response418from the local cache without needing to establish a connection communication over the wireless network. In one embodiment, the response is stored at the server proxy in the server cache for subsequent use in satisfying same or similar data requests. The response can be stored in lieu of or in addition to storage on the local cache on the mobile device. In addition, the server proxy performs the requests marked for monitoring420to determine whether the response422for the given request has changed. In general, the host server485can perform this monitoring independently of the widget455or local proxy465operations. Whenever an unexpected response422is received for a request, the server485can notify the local proxy465that the response has changed (e.g., the invalidate notification in step424) and that the locally stored response on the client should be erased or replaced with a new (e.g., changed or different) response. In this case, a subsequent data request426by the widget455from the device450results in the data being returned from host server485(e.g., via the caching proxy475). Thus, through utilizing the distributed proxy system460the wireless (cellular) network is intelligently used when the content/data for the widget or software application455on the mobile device450has actually changed. As such, the traffic needed to check for the changes to application data is not performed over the wireless (cellular) network. This reduces the amount of generated network traffic and shortens the total time and the number of times the radio module is powered up on the mobile device450, thus reducing battery consumption, and in addition, frees up network bandwidth. FIG.4Bdepicts a timing diagram showing how data requests from a mobile device450to an application server/content provider495in a wireless network can be aligned at the local proxy465in the distributed proxy system460to optimize network and radio use. When a data request A432is detected at the local proxy465on the mobile device450, the local proxy465can determine that the radio on the mobile device450is currently off and decide to wait to transfer the request A432over the network. When data request B434is detected, the proxy465can determine (e.g., based on conditions and/or processes illustrated in the flow charts in the examples ofFIGS.6A-10C) whether to transfer the data request B434and/or whether also to transfer the impending data request A432. In the example shown inFIG.4B, the local proxy465does not transfer data requests A and B until data request C436is detected at the device450by the proxy465. The time ‘D1’433with which request A432and time ‘D2’435with which request B434are delayed, can be determined by the local proxy465(e.g., as described in conjunction with the traffic shaping module and delay module in the example ofFIG.2B). The radio can be turned on when request C436is received and data transfers for requests A, B, and C438can be aligned at this point to be transferred to the host server480on the server-side470of the distributed proxy460which can forward the request to the server/provider495, immediately in transfer440, or possibly with some delay, in transfer442. Note that the data requests A, B, and C can all originate from the same application or different applications on the mobile device450. FIG.5depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device550using a distributed proxy and cache system (e.g., such as the distributed system shown in the example ofFIG.1B). In step502, the local proxy (e.g., proxy175in the example ofFIG.1B) monitors the device for user activity. When the user is determined to be active, server push is active. For example, always-on-push IP connection can be maintained and if available, SMS triggers can be immediately sent to the mobile device550as it becomes available. In process504, after the user has been detected to be inactive or idle over a period of time (e.g., the example is shown for a period of inactivity of 20 min.), the local proxy can adjust the device to go into the power saving mode. In the power saving mode, when the local proxy receives a message or a correspondence from a remote proxy (e.g., the server proxy135in the example ofFIG.1B) on the server-side of the distributed proxy and cache system, the local proxy can respond with a call indicating that the device550is currently in power save mode (e.g., via a power save remote procedure call). In some instances, the local proxy take the opportunity to notify multiple accounts or providers (e.g.,510A, and510B) of the current power save status (e.g., timed to use the same radio power-on event). In one embodiment, the response from the local proxy can include a time (e.g., the power save period) indicating to the remote proxy (e.g., server proxy135) and/or the app server/providers510A/B when the device550is next able to receive changes or additional data. A default power savings period can be set by the local proxy. Consecutive power saving periods can increase in duration. For example, if a first power saving period has elapsed without an activity occurring, the device550can continue into a second power saving mode with a longer time period (e.g., see periods one 503 and period two 505). In general, any activity on the device takes the client out of power saving mode and ends that particular power save event. In one embodiment, if new, change, or different data or event is received before the end of any one power saving period, then the wait period communicated to the servers510A/B can be the existing period, rather than an incremented time period. For example, in step506, since new content was received during the power saving mode, the next wait period communicated in step508to servers510A/B may again be the same time saving period. In response, the remote proxy server, upon receipt of power save notification from the device550, can stop sending changes (data or SMSs) for the period of time requested (the wait period). At the end of the wait period, any notifications received can be acted upon and changes sent to the device550, for example, as a single batched event or as individual events. If no notifications come in, then true push can be resumed with the data or an SMS being sent immediately to the device550. To optimize batch sending content to the mobile device550, the proxy server can start the poll or data collect event earlier (before the end of a power save period) in order to increase the chance that the client will receive data at the next radio power on event. In one embodiment, whenever new data or content comes into the device550while it is in a power saving mode, it can respond with the power saving remote procedure call to all end points currently registered (e.g., server/providers510A/B). Note that the wait period can be updated in operation in real time to accommodate operating conditions. For example, as the mobile device550sends additional power saving calls (e.g., with updated wait times) if multiple servers510A/B or others, respond to the end of a wait period with different delays, the local proxy can adjust the wait period on the fly to accommodate the different delays. Detection of user activity512at the device550causes the power save mode to be exited. When the device550exits power save mode, it can send power save cancel call to the proxy server and immediately receives any changes associated with any pending notifications. This may require a poll to be run by the proxy server after receiving the power saving cancel call. If the latest power saving period has expired, then no power save cancel call may be needed as the proxy server will already be in traditional push operation mode. In one embodiment, power save mode is not applied when the device550is plugged into a charger. This setting can be reconfigured or adjusted by the user or another party. In general, the power save mode can be turned on and off, for example, by the user via a user interface on device550. In general, timing of power events to receive data can be synced with any power save calls to optimize radio use. FIG.6Adepicts a flow chart illustrating example processes through which context awareness is used for traffic management. In process602A, characteristics of user activity on the mobile device are detected. In process604A, behavior of the mobile device is adjusted to optimize battery consumption on the mobile device. The adjustment of the behavior of the mobile device can include, for example, adjusting the use of radio on the mobile device, as in process606A. In addition, in process608A, the radio can be switched on/off. Further, the radio can also be placed in low power or high power radio mode in process612A. In addition, data can be cached at the mobile device in process610A to adjust radio use. Data may also be cached at the server in wireless communication with the mobile device to in order to modify communication frequency with the mobile device. In one embodiment, in response to detection of user activities on the mobile device, the characteristics of the user activity can be communicated from the mobile device to the server, in process614A. Similarly, based on the user activity characteristics, communication frequency of a server with the mobile device can be adjusted in process616A. For example, data push frequency from the server to the mobile device is decreased, in process618A. Similarly, data can be cached at the server in process620A to adjust communication frequency. In addition, characteristics of transactions occurring at the mobile device can also be used to locally adjust radio use on the mobile device. For example, characteristics of transactions include time criticality of the transactions and that a low power radio mode or a high power radio mode can be selected for use on the mobile device based on the time criticality of the transactions. Additionally, a low power radio mode or a high power radio mode is selected for use on the mobile device based on amount of data to be transferred in the transactions. FIG.6Bdepicts a flow chart illustrating example processes through which application behavior on a mobile device is used for traffic optimization. In process602B, application behavior of multiple applications accessed on a mobile device is detected. Using application behavior, the distributed proxy system can implement one or more of several processes for optimizing traffic. For example, beginning in process604B, content requests for the at least some of the multiple applications are aligned and polling can be performed over the wireless network in accordance with the alignment to satisfy data requests of the multiple applications, in process606B. In one embodiment, content requests for some of the multiple applications can be aligned based on content types requested by the multiple applications. For example, content requests from different applications requesting RSS feeds can be aligned. In addition, content requests from different applications requesting content from the same sources may be aligned (e.g., a social networking application and a web page may both be requesting media content from an online video streaming site such as Youtube). In another example, multiple Facebook applications on one device (one from OEM, one from marketplace) that both poll for same data. In addition, content requests can be aligned based on user's explicit and/or implicit preferences, user settings, mobile device parameters/parameters, and/or network parameters (e.g., network service provider specifications or limitations, etc.) or conditions (e.g., traffic, congestion, network outage, etc.). For example, when congestion is detected in a user's network service area, content requests can be aligned for the network is less congested. For example, when user is inactive, or when the battery is low, alignment may be performed more aggressively. In some instances, the polling can be performed by the proxy server on behalf of multiple devices and can thus detect requests for polls from the same content source from multiple devices. The proxy server, can align such requests occurring around the same time (e.g., within a specific time period) for multiple devices and perform a poll of the source to satisfy the data needs of the multiple mobile devices. For example, during the Superbowl, the proxy server can detect a larger number of requests to poll ESPN.com or NFL.com for live score updates for the game. The proxy server can poll the content source once for a current score and provide the updates to each of the mobile devices that have applications which have (within a time period) requested polls for score updates. In another example, beginning in process608B, recurrences in application requests made by the multiple applications are detected. Recurrences of application behavior can be identified by, for example, tracking patterns in application behavior. Using the recurrences, polling of content sources as a result of the application requests that would be performed at the mobile device can now be offloaded, to be performed instead, for example, by a proxy server remote from the mobile device in the wireless network, in process610B. The application behavior can be tracked by, for example, a local proxy on the mobile device and communicated to the proxy server as connection metadata, for use in polling the content sources. The local proxy can delays or modifies data prior to transmission to the proxy serve and can additionally identify and retrieve mobile device properties including, one or more of, battery level, network that the device is registered on, radio state, whether the mobile device is being used. The offloading to the proxy server can be performed, for example, when the recurrences match a rule or criteria. In addition, the proxy server and/or the local proxy can delay the delivery of a response received from a content source and/or perform additional modification, etc. For example, the local proxy can delay the presentation of the response via the mobile device to the user, in some instances. Patterns of behavior can include, one or more of, by way of example but not limitation, frequency that requested content is the same, frequency with which a same request is made, interval between requests, applications making a request, frequency of requests at certain times of day, day of week. In addition, multi-application traffic patterns can also be detected and tracked. In process612B, the proxy server can notify the mobile device when content change is detected in response to the polling of the content sources. In one embodiment, cached content, when available, can be provided to satisfy application requests when content change is not detected in the polling of the content sources. For example, the local proxy can include a local cache and can satisfy application requests on the mobile device using cached content stored in the local cache. In one embodiment, the decision to use cached content versus requesting data from the content source is determined based on the patterns in application behavior. In addition, an application profile can be generated, using the application behavior of the multiple applications, in process614B. FIG.7Adepicts a flow chart illustrating an example process for managing traffic in a wireless network based on user interaction with a mobile device. In process702A, it is determined if the user actively interacting with the mobile device. If the user is actively interacting with the mobile device, the mobile device714A can be notified, as in process714A, of new data or changes in data. If not, in process704A, device can wait to send low priority transactions until after the user activity has been dormant for a period of time, for example, low priority transactions include, one or more of, updating message status as being read, unread, and deleting of messages. In addition, low priority transactions can be sent when a higher priority transaction needs to be sent, thus utilizing the same radio power-up event. Low priority transactions can generally include application maintenance events, events not requested by a user, events scheduled to be in the future, such as, by way of example but not limitation, one or more of, updating message status as being read, unread, and deleting of messages. Similarly, if the user is not active, data push frequency from the server can be decreased in process706A. In process708A, if the user is detected to be subsequently active after being inactive, then data buffered as a result of decreased communication frequency can be sent to the mobile device, in process710A. Alternatively, even if the user is not actively interacting with the mobile device, an assessment can be made as to whether high importance data (e.g., data importance or priority meeting a threshold level) is pending to be sent to the mobile device, in process712A. If so, the mobile device is notified, in process714A. As a result of the notification, the mobile device radio can be enabled such that the high importance data can be sent to the mobile device. In general, the importance of data can be determined based on one or more of several criteria including but not limited to, application to which the data is relevant, time criticality, and time sensitivity, etc. An example of a time critical transaction includes a transaction resulting from a user-initiated data transfer. FIG.7Bdepicts a flow chart illustrating an example process for mobile application traffic optimization through data monitoring and coordination in a distributed proxy and cache system. In process702B, a data request made by the mobile application on a mobile device is intercepted. In process704B, a local cache on the mobile device is queried. In process706B, it is determined whether a locally stored valid response exists (e.g., whether a locally stored response is available and if so, if the stored response is still valid. If so, in process708B, the locally stored response to the mobile device without the mobile device needing to access the cellular network If not, a locally stored response is not available, or available but invalid, one or more of several approaches may be taken to optimize the traffic used in the wireless network for satisfying this request, as will be described below. In one example, in process710B, the data request is sent to a remote proxy which forwards the data request to a content source. In general, the remote proxy can delay or modify data from the local proxy prior to transmission to the content sources. In one embodiment, the proxy server can use device properties and/or connection metadata to generate rules for satisfying request of applications on the mobile device. In addition, the proxy server can optionally gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device or other mobile devices. In process712B, a response provided by the content source is received through the remote proxy. In one embodiment, the remote proxy can simulate an application server authentication and querying a local cache on the mobile device to retrieve connection information if available or needed to connect to the content source. Upon authentication application server responses for the mobile application can be simulated by the remote proxy on the mobile device for data requests where responses are available in the local cache. In process714B, the response is locally stored as cache entries in a local repository on the mobile device. The local cache entries can be stored for subsequent use in satisfying same or similar data request. In addition, in process716B, data request to the content source is detected to yielded same results to be returned to the mobile device (e.g., detected by the local proxy on the mobile device). In response to such detection, the remote proxy is notified to monitor responses received for the data request from the content source for changed results prior to returning the result to the mobile device. In one embodiment, the local proxy can store the response as a cache entry in the local cache for the data request when the remote proxy is notified to monitor the responses for the data request. In process722B, the remote proxy performs the data request identified for monitoring and notifies the mobile device when an unexpected response to the data request is detected. In process724B. The locally stored response on the mobile device is erased or replaced when notified of the unexpected response to the data request. In another example, when a locally stored response is not available or otherwise invalid, in process718B, a remote proxy is queried for a remotely stored response. In process720B, the remotely stored response is provided to the mobile device without the mobile device needing to access the cellular network. In process722B, the remote proxy performs the data request identified for monitoring and notifies the mobile device when an unexpected response to the data request is detected. In process724B, the locally stored response on the mobile device is erased or replaced when notified of the unexpected response to the data request. FIG.8Adepicts a flow chart illustrating another example process for managing traffic in a wireless network based on user interaction with a mobile device. In process802A, user activity is detected at a device separate from a mobile device. In process804A, it is determined whether the user activity at the device is able to access the same data, content, or application, which is also setup to be delivered to or accessed at the mobile device. For example, user activity at the device separate from the mobile device can include user access of an email inbox or other types applications via an interface other than that accessed from the mobile device (e.g., from a laptop or desktop computer). Since the user is now accessing the client from another device, the user now may not need content to be updated as frequently on the mobile device. Thus, in process806A, communication frequency from a server to the mobile device is decreased. FIG.8Bdepicts a flow chart illustrating an example process for preventing applications from needing to send keep-alive messages to maintain an IP connection with a content server. In process802B, applications attempting to send keep-alive messages to a content server are detected at a mobile device. In process804B, the keep-alive messages are intercepted and prevented from being sent from the mobile device over the wireless network to the content server. Since keep-alives are similar to any other (long-poll) requests—the content on the back end typically does not change and the proxy server can keep polling the content server. In process806B, the keep-alive messages are generated at a proxy server remote from the mobile device and sent from the proxy server to the content server, in process808B. FIG.9Adepicts a flow chart illustrating an example process for managing traffic initiated from a mobile device in a wireless network through batching of event transfer based on event priority. In process902A, multiple occurrences of events having a first priority type initiated on the mobile device are detected. In process904A, the mobile device cumulates multiple occurrences of events having a first priority type initiated on the mobile device, before transfer over the wireless network. The first priority type can be a generally low priority type indicating a request or update which is not time critical or time sensitive. Thus, if the device radio is currently off, the radio may not be immediately turned on to transmit individual events which are not time critical, until other triggering events occur or other criteria is met. For example, in process906A, occurrence of an event of a second priority type is detected, which can trigger batch transfer of the cumulated events to a server in wireless communication with the mobile device, in process916A, where the second priority type is of a higher priority than the first priority type. In another example, in process908A, data transfer from the server can trigger the radio use on the mobile device, which can trigger batch transfer of the cumulated events to a server in wireless communication with the mobile device, in process916A. Alternatively, in process910A, after a period of time elapses, batch transfer of the cumulated events to a server in wireless communication with the mobile device can be triggered, in process916A. In one embodiment, in process912A, a user trigger (e.g., a manual sync request) or in response to a user prompt, batch transfer of the cumulated events to a server in wireless communication with the mobile device can be triggered, in process916A. In process914A, when it is detected that an application is exited and/or moved into the background, batch transfer of the cumulated events to a server in wireless communication with the mobile device can be triggered, in process916A. FIG.10Adepicts a flow chart illustrating another example process for managing traffic initiated remotely from a mobile device in a wireless network through batching of event transfer based on event priority. In process1002A, multiple occurrences of events having a first priority type are detected at a server wirelessly coupled to a mobile device. In process1004A, the server cumulates the multiple occurrences of events having a first priority type, before transfer over the wireless network. The first priority type may not be of a high priority type or having a priority exceeding a certain threshold level indicating a level or time criticality or urgency. Thus, such events, upon occurrence, may not be immediately transferred to the mobile device, until certain criterion is met, or until one or more triggering events occur. For example, in process1006A, occurrence of an event of a second priority type is detected at the server, which can trigger batch transfer of the cumulated events to the mobile device, in process1016A, when the second priority type is of a higher priority than the first priority type. In another example, in process1008A, data transfer from the mobile device indicates the radio use on the mobile device, which can trigger batch transfer of the cumulated events to the mobile device, in process1016A. Alternatively, in process1010A, after a period of time elapses, batch transfer of the cumulated events to the mobile device can be triggered, in process1016A. In process1012A, a user trigger or in response to a user prompt, batch transfer of the cumulated events to the mobile device can be triggered, in process1016A. In process1014A, when it is detected that an application is exited and/or moved into the background, batch transfer of the cumulated events to the mobile device can be triggered, in process1016A. In general, manual overrides or manual syncs can cause batch transfers to occur, either from the mobile device to the server or vice versa. FIG.6Cdepicts a flow chart illustrating example selection processes through which data transfer requests of multiple applications can be coordinated into a single transfer operation. In process602C, a first data transfer request initiated by a first application on a device or mobile device is received. One or more selection processes can be performed to determine whether to delay transfer of the first data transfer request, as shown in steps604C-608C, including, determining whether the user is interacting with the first application, whether the first application is in the foreground, or whether the radio of the mobile device on which the request is initiated is already on. Note that although the selection processes are illustrated and identified in a specific order, the order in which the system checks for applicability is not limited to such, any of the above conditions can be checked in any ordering or any combination with one of the other conditions. If one of the above applies, in process610C, in general, a decision can be made to transfer the data request over the wireless (cellular or others) network, or to power on the radio (e.g., via the radio controller256shown in the example ofFIG.2A) to perform the transfer without or with minimal delay. Additional conditions that are not shown here which may cause the transfer of the data request to occur immediately or upon receipt may be included. If none of the conditions in604C-608C applies (or other suitable conditions depending on the specific implementation), in process612C, the transfer of the first data transfer request can be delayed. In process614C, it is determined whether another data transfer request has been initiated. If not, the process continues at flow ‘A’ inFIG.7C. If so, the system performs one or more of several condition checks shown in decision flows616C-624C including determining whether the second application is of higher priority than the first application, whether the second application running in the foreground, whether the user interacting with the second application, whether the other data request initiated in response to user interaction, and/or whether the second application is more data intensive than the first application. The flow chart continues at ‘A’ inFIG.7Cif none of the above conditions apply. If any of the above conditions apply, then in process626C, the first data transfer request of the first application and the other data transfer request of the second application are transferred in a single transfer operation over the network. Note that the conditions shown in616C-624C can be applied in any order or any combination with one another, although illustrated in the example flow chart as having a particular order. FIG.7Cdepicts an example of triggering events that would cause a data request to be transferred without alignment with another data request. The events shown in processes702C-710C can occur independently or in conjunction with one another and cause the data request to be transferred over the wireless network without or with minimal delay upon occurrences of these events. For example, in process702C, the mobile device radio is turned on due to another event. In process704C, a certain time period has elapsed, in process706C, a user trigger is detected, and/or the first application exits in process708C and/or moves into the background in process710C. When any of the above conditions are detected, n process721C, the data request is transferred over the wireless (cellular or others) network. FIG.8Cdepicts a flow chart illustrating an example process for using timing characteristics of data requests made by individual applications to delay transfer of one or more of the data requests made by one of the individual applications. In processes802C and804C, data transfer requests made by first and second application on the mobile device are tracked. For example, the transaction/request manager235of the local proxy275shown in the example ofFIG.2Acan detect the occurrence of the data transfer requests and request that the application behavior detector236begin to track correlations or other types of behaviors of the requesting applications. In process806C, a first timing characteristic of data transfer requests made by the first application is determined and in process808C, a second timing characteristic of data transfer requests made by the second application is determined, and can be used, for example, by the correlation detector238to identify any correlations in the requests. Based on the identified timing characteristics and any determined correlations or applicable priorities (e.g., as determined by the prioritization engine238in the example ofFIG.2A). In process810C, the transfer of the first data request can be delayed using the first and second timing characteristics or in process812C, the transfer of the second data request can be delayed using the first and second timing characteristics. Such delay (e.g., determined by the delay module258of the local proxy shown in the example ofFIG.2B) can be until another event occurs, until a manual (user) trigger is detected, or after a certain amount of time, or when another triggering event (e.g., user interaction) occurs. Note that the delays are user-configurable and can be tracked and factored into consideration by the delay module258. While the example is illustrated and described for different applications (e.g., first and second applications are different applications), the process can similarly be applied to different requests within the same application (e.g., first and second applications may be the same application). FIG.9Bdepicts a flow chart illustrating an example process for using application behavior of multiple applications to align their content requests made over the network. In process902B, application behavior of multiple applications are detected on a mobile device. In general, the behaviors of any number of applications on the mobile device that are detected can be tracked. Any or all mobile applications on a device can be monitored for the potential for its requests to be aligned for traffic coordination. In addition, the user can select the applications to be aligned, or specify applications not to be tracked for traffic coordination. Furthermore, the device platform, manufacturer, OS settings, and/or network provider may have additional specifications or conditions for aligning traffic requests and selection of applications for traffic coordination. In process904B, some of the content requests made by at least a portion the multiple applications from the mobile device over the network, are aligned. Process flow continues to step ‘B’ as shown in the example ofFIG.10Bwhich depicts an example of processes through which the time of delay ‘D’ for content requests can be determined to align content requests over the wireless network. In process906B, some of the content requests that are delayed in a single transfer operation are transferred over the network. Example processes applied to determine delay time ‘D’ include, by way of example but not limitation: Determine priority of a specific application or priority of the application relative to other applications in process1002B, Determine an amount of data involved in a given content request in step1004B, Determine the useable lifetime of data to be transferred in the content request in step1006B, Determine a nature of data involved in a given content request in step1008B, Determine a status of the application making the content request in step1010B, and/or Determine the network characteristics when the request is made in step1012B. Any number of the above conditions can be applied in any order. Additional conditions which can be used may not be illustrated in the example above. In process1014B, any user configuration or overriding settings can be factored into consideration in determining delay to align content request, in process1016B. FIG.6Ddepicts a flow chart illustrating an example process for using user activity and/or application server/provider activity to time the transfer of data from the host to the mobile device to optimize use of network resources. In process602D, user activity at a mobile device is detected and tracked in process606D. In process604D, server activity is detected for a host server (e.g., an application server or content provider such as app server/provider110in the examples ofFIGS.1A-1B) with which the mobile device interacts to satisfy content requests at the mobile device. In process608D, the server activity can be tracked. In one embodiment, the user behavior and activity are detected and tracked by a local proxy on the mobile device and the server activity of the host server (app server/content provider) is tracked and detected by a remote proxy which is able to wirelessly communicate with the local proxy in a distributed proxy system. Some examples of the types of user activities and server activities that can be tracked or characterized are shown in the examples ofFIGS.7D and8D. Using the user activity and/or the server activity, the timing with which to transfer impending data from the host server to the mobile device is determined. In one embodiment, the timing is determined based on prediction of a future activity session at the mobile device. In process610D and in process612D, the impending data is transferred from the host server to the mobile device according to the timing. The timing is generally determined such that network resource use is optimized and/or such that user experience is enhanced or preserved. For example, the transferring of impending data comprises pre-caching of content on the mobile device to support data activity for a future activity session predicted based on the user behavior and the server activity. In addition, server activities of multiple host servers (e.g., multiple application servers or content providers including by way of example but not limitation, push notification servers, email hosts, RSS, web services, web sites, gaming sites, etc.) with which the mobile device interacts to satisfy content requests at the mobile device are detected and/or tracked in process616D. In process618D, based on the server activities of multiple hosts and providers, the likelihood that an activity session initiated at the mobile device will interact with a given host server (application server or provider) can be predicted. Based on the prediction, each of the multiple host servers are prioritized based on the prediction of likelihood an activity session initiated at the mobile device will interact with a given host server, in process620D. FIG.7Ddepicts an example of processes which can be used to for user behavior prediction. For example, the system (either the local proxy on the device side or the server proxy on the server side, or a combination thereof) can detect a pattern of user-initiated events at the mobile device, in process702D. For example, a pattern can include, a correlation in time between initiations of one application and another application, or correlation between initiation of one event/transaction and another event/transaction. The system can also track the user activity given the time of day or day of the week in process704D, and identify any patterns in user behavior such as preferences or habits with regards to application use frequency, which applications are used, and/or which activities the user is engaged in with each application, The system can further track an order with which new data is accessed or an order with which applications are accessed on the mobile device, in process708D, and/or through collaborative filtering, in process710D. Any number of and combination of the above events can be used to predict user behavior, in step712D. Note that user behavior can be determined for different contexts. For example, the system can determine user behavior with respect to accessing work email and behavior with respect to accessing personal email accounts (e.g., time of day or day of week a user accesses certain accounts, frequency, actions taken, features used, etc.). In addition, user behavior may also be determined with respect to different applications or services (e.g., when and how frequently a user uses Facebook, tweets, accesses Yelp, uses Maps/Location/Direction applications, etc.) FIG.8Ddepicts an example of processes which can be used to detect app server/provider characteristics. For example, the last last-accessed time or a frequency of access of the host server (application server/service provider) can be determined in process802D, or an amount of impending data to be transferred to the mobile device can be determined in process804D. In general, server activities can be detected and monitored by the server-side components (e.g., the proxy server) of the distributed proxy and cache system. Such information can be used alone or in conjunction to detect server activity characteristics, in process806D. FIG.9Cdepicts a flow chart illustrating an example process to anticipate a future activity session at a mobile device to enhance user experience with a mobile application. In process902C, user activity characteristics at a mobile device and server activity characteristics of a host server are detected. The host server is a server with which the mobile device interacts with to satisfy application requests (e.g., mobile applications) at the mobile device and can include, for example, application servers or content providers. In process904C, a future activity session can be anticipated at the mobile device. In addition, contextual cues can be used in the anticipation of the activity session as illustrated at flow ‘A’ in the example ofFIG.10C. In process906C, decision is made to pre-cache content on the mobile device to support predicted data activity for the future activity session that has been predicted. In process908C, impending content is transferred from the host server the mobile device to pre-cache content, such that user experience with the mobile application can be enhanced. FIG.10Cdepicts an example of processes through which contextual data for use in anticipation of future activity sessions can be determined. For example, location change of the mobile device can be detected, in step1004C; changes in readings of hardware sensors (e.g., motion, GPS, temperature, tilt, vibration, capacitive, resistive, ambient light, device backlight, etc.) on the mobile device can be detected in1006C, and/or states or statuses of applications (e.g., activity state, foreground/background status, etc.) on the mobile device can be detected in1008C. FIG.11shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation. In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure. Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution. Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include but are not limited to recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links. In some embodiments, the network interface device may enable the machine1100to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater. In some embodiments, the network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand. Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure. Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list. The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges. The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments. Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure. These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims. While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. § 112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. § 112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure. | 163,133 |
11943717 | The same reference numerals are used to represent the same elements throughout the drawings. DETAILED DESCRIPTION The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents. It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. FIG.1is a block diagram illustrating an electronic device101in a network environment100according to an embodiment of the disclosure. Referring toFIG.1, the electronic device101in the network environment100may communicate with an electronic device102via a first network198(e.g., a short-range wireless communication network), or an electronic device104or a server108via a second network199(e.g., a long-range wireless communication network). According to an embodiment, the electronic device101may communicate with the electronic device104via the server108. According to an embodiment, the electronic device101may include a processor120, memory130, an input module150, a sound output module155, a display module160, an audio module170, a sensor module176, an interface177, a connecting terminal178, a haptic module179, a camera module180, a power management module188, a battery189, a communication module190, a subscriber identification module (SIM)196, or an antenna module197. In some embodiments, at least one (e.g., the connecting terminal178) of the components may be omitted from the electronic device101, or one or more other components may be added in the electronic device101. According to an embodiment, some (e.g., the sensor module176, the camera module180, or the antenna module197) of the components may be integrated into a single component (e.g., the display module160). The processor120may execute, for example, software (e.g., a program140) to control at least one other component (e.g., a hardware or software component) of the electronic device101coupled with the processor120, and may perform various data processing or computation. According to one embodiment, as at least part of the data processing or computation, the processor120may store a command or data received from another component (e.g., the sensor module176or the communication module190) in volatile memory132, process the command or the data stored in the volatile memory132, and store resulting data in non-volatile memory134. According to an embodiment, the processor120may include a main processor121(e.g., a central processing unit (CPU) or an application processor (AP)), or an auxiliary processor123(e.g., a graphics processing unit (GPU), a neural processing unit (NPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently from, or in conjunction with, the main processor121. For example, when the electronic device101includes the main processor121and the auxiliary processor123, the auxiliary processor123may be configured to use lower power than the main processor121or to be specified for a designated function. The auxiliary processor123may be implemented as separate from, or as part of the main processor121. The auxiliary processor123may control at least some of functions or states related to at least one component (e.g., the display module160, the sensor module176, or the communication module190) among the components of the electronic device101, instead of the main processor121while the main processor121is in an inactive (e.g., sleep) state, or together with the main processor121while the main processor121is in an active state (e.g., executing an application). According to an embodiment, the auxiliary processor123(e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera module180or the communication module190) functionally related to the auxiliary processor123. According to an embodiment, the auxiliary processor123(e.g., the neural processing unit) may include a hardware structure specified for artificial intelligence model processing. The artificial intelligence model may be generated via machine learning. Such learning may be performed, e.g., by the electronic device101where the artificial intelligence is performed or via a separate server (e.g., the server108). Learning algorithms may include, but are not limited to, e.g., supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), deep Q-network or a combination of two or more thereof but is not limited thereto. The artificial intelligence model may, additionally or alternatively, include a software structure other than the hardware structure. The memory130may store various data used by at least one component (e.g., the processor120or the sensor module176) of the electronic device101. The various data may include, for example, software (e.g., the program140) and input data or output data for a command related thereto. The memory130may include the volatile memory132or the non-volatile memory134. The program140may be stored in the memory130as software, and may include, for example, an operating system (OS)142, middleware144, or an application146. The input module150may receive a command or data to be used by another component (e.g., the processor120) of the electronic device101, from the outside (e.g., a user) of the electronic device101. The input module150may include, for example, a microphone, a mouse, a keyboard, keys (e.g., buttons), or a digital pen (e.g., a stylus pen). The sound output module155may output sound signals to the outside of the electronic device101. The sound output module155may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or playing record. The receiver may be used for receiving incoming calls. According to an embodiment, the receiver may be implemented as separate from, or as part of the speaker. The display module160may visually provide information to the outside (e.g., a user) of the electronic device101. The display module160may include, for example, a display, a hologram device, or a projector and control circuitry to control a corresponding one of the display, hologram device, and projector. According to an embodiment, the display module160may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch. The audio module170may convert a sound into an electrical signal and vice versa. According to an embodiment, the audio module170may obtain the sound via the input module150, or output the sound via the sound output module155or a headphone of an external electronic device (e.g., an electronic device102) directly (e.g., wiredly) or wirelessly coupled with the electronic device101. The sensor module176may detect an operational state (e.g., power or temperature) of the electronic device101or an environmental state (e.g., a state of a user) external to the electronic device101, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module176may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor. The interface177may support one or more specified protocols to be used for the electronic device101to be coupled with the external electronic device (e.g., the electronic device102) directly (e.g., wiredly) or wirelessly. According to an embodiment, the interface177may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface. A connecting terminal178may include a connector via which the electronic device101may be physically connected with the external electronic device (e.g., the electronic device102). According to an embodiment, the connecting terminal178may include, for example, a HDMI connector, a USB connector, a SD card connector, or an audio connector (e.g., a headphone connector). The haptic module179may convert an electrical signal into a mechanical stimulus (e.g., a vibration or motion) or electrical stimulus which may be recognized by a user via his tactile sensation or kinesthetic sensation. According to an embodiment, the haptic module179may include, for example, a motor, a piezoelectric element, or an electric stimulator. The camera module180may capture a still image or moving images. According to an embodiment, the camera module180may include one or more lenses, image sensors, image signal processors, or flashes. The power management module188may manage power supplied to the electronic device101. According to one embodiment, the power management module188may be implemented as at least part of, for example, a power management integrated circuit (PMIC). The battery189may supply power to at least one component of the electronic device101. According to an embodiment, the battery189may include, for example, a primary cell which is not rechargeable, a secondary cell which is rechargeable, or a fuel cell. The communication module190may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device101and the external electronic device (e.g., the electronic device102, the electronic device104, or the server108) and performing communication via the established communication channel. The communication module190may include one or more communication processors that are operable independently from the processor120(e.g., the application processor (AP)) and supports a direct (e.g., wired) communication or a wireless communication. According to an embodiment, the communication module190may include a wireless communication module192(e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module194(e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules may communicate with the external electronic device104via a first network198(e.g., a short-range communication network, such as Bluetooth™, wireless-fidelity (Wi-Fi) direct, or infrared data association (IrDA)) or a second network199(e.g., a long-range communication network, such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., local area network (LAN) or wide area network (WAN)). These various types of communication modules may be implemented as a single component (e.g., a single chip), or may be implemented as multi components (e.g., multi chips) separate from each other. The wireless communication module192may identify or authenticate the electronic device101in a communication network, such as the first network198or the second network199, using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module196. The wireless communication module192may support a 5G network, after a 4G network, and next-generation communication technology, e.g., new radio (NR) access technology. The NR access technology may support enhanced mobile broadband (eMBB), massive machine type communications (mMTC), or ultra-reliable and low-latency communications (URLLC). The wireless communication module192may support a high-frequency band (e.g., the mmWave band) to achieve, e.g., a high data transmission rate. The wireless communication module192may support various technologies for securing performance on a high-frequency band, such as, e.g., beamforming, massive multiple-input and multiple-output (massive MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module192may support various requirements specified in the electronic device101, an external electronic device (e.g., the electronic device104), or a network system (e.g., the second network199). According to an embodiment, the wireless communication module192may support a peak data rate (e.g., 20 Gbps or more) for implementing eMBB, loss coverage (e.g., 164 dB or less) for implementing mMTC, or U-plane latency (e.g., 0.5 ms or less for each of downlink (DL) and uplink (UL), or a round trip of 1 ms or less) for implementing URLLC. The antenna module197may transmit or receive a signal or power to or from the outside (e.g., the external electronic device). According to an embodiment, the antenna module197may include one antenna including a radiator formed of a conductor or conductive pattern formed on a substrate (e.g., a printed circuit board (PCB)). According to an embodiment, the antenna module197may include a plurality of antennas (e.g., an antenna array). In this case, at least one antenna appropriate for a communication scheme used in a communication network, such as the first network198or the second network199, may be selected from the plurality of antennas by, e.g., the communication module190. The signal or the power may then be transmitted or received between the communication module190and the external electronic device via the selected at least one antenna. According to an embodiment, other parts (e.g., radio frequency integrated circuit (RFIC)) than the radiator may be further formed as part of the antenna module197. According to various embodiments, the antenna module197may form a mmWave antenna module. According to an embodiment, the mmWave antenna module may include a printed circuit board, a RFIC disposed on a first surface (e.g., the bottom surface) of the printed circuit board, or adjacent to the first surface and capable of supporting a designated high-frequency band (e.g., the mmWave band), and a plurality of antennas (e.g., array antennas) disposed on a second surface (e.g., the top or a side surface) of the printed circuit board, or adjacent to the second surface and capable of transmitting or receiving signals of the designated high-frequency band. At least some of the above-described components may be coupled mutually and communicate signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)). According to an embodiment, commands or data may be transmitted or received between the electronic device101and the external electronic device104via the server108coupled with the second network199. The external electronic devices102or104each may be a device of the same or a different type from the electronic device101. According to an embodiment, all or some of operations to be executed at the electronic device101may be executed at one or more of the external electronic devices102,104, or108. For example, if the electronic device101should perform a function or a service automatically, or in response to a request from a user or another device, the electronic device101, instead of, or in addition to, executing the function or the service, may request the one or more external electronic devices to perform at least part of the function or the service. The one or more external electronic devices receiving the request may perform the at least part of the function or the service requested, or an additional function or an additional service related to the request, and transfer an outcome of the performing to the electronic device101. The electronic device101may provide the outcome, with or without further processing of the outcome, as at least part of a reply to the request. To that end, a cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device101may provide ultra-low-latency services using, e.g., distributed computing or mobile edge computing. In another embodiment, the external electronic device104may include an internet-of-things (IoT) device. The server108may be an intelligent server using machine learning and/or a neural network. According to an embodiment, the external electronic device104or the server108may be included in the second network199. The electronic device101may be applied to intelligent services (e.g., smart home, smart city, smart car, or health-care) based on 5G communication technology or IoT-related technology. FIG.2Ais a block diagram200illustrating an electronic device101for supporting legacy network communication and 5G network communication according to an embodiment of the disclosure. Referring toFIG.2A, the electronic device101may include a first communication processor212, a second communication processor214, a first radio frequency integrated circuit (RFIC)222, a second RFIC224, a third RFIC226, a fourth RFIC228, a first radio frequency front end (RFFE)232, a second RFFE234, a first antenna module242, a second antenna module244, a third antenna module246, and antennas248. The electronic device101may further include a processor120and a memory130. The second network199may include a first cellular network292and a second cellular network294. According to another embodiment, the electronic device101may further include at least one component among the components ofFIG.1, and the second network199may further include at least one other network. According to an embodiment, the first communication processor212, the second communication processor214, the first RFIC222, the second RFIC224, the fourth RFIC228, the first RFFE232, and the second RFFE234may form at least part of the wireless communication module192. According to another embodiment, the fourth RFIC228may be omitted or be included as part of the third RFIC226. The first communication processor212may establish a communication channel of a band that is to be used for wireless communication with the first cellular network292or may support legacy network communication via the established communication channel According to various embodiments, the first cellular network may be a legacy network that includes second generation (2G), third generation (3G), fourth generation (4G), or long-term evolution (LTE) networks. The second CP214may establish a communication channel corresponding to a designated band (e.g., from about 6 GHz to about 60 GHz) among bands that are to be used for wireless communication with the second cellular network294or may support fifth generation (5G) network communication via the established communication channel According to an embodiment, the second cellular network294may be a 5G network defined by the 3rd generation partnership project (3GPP). Additionally, according to an embodiment, the first CP212or the second CP214may establish a communication channel corresponding to another designated band (e.g., about 6 GHz or less) among the bands that are to be used for wireless communication with the second cellular network294or may support fifth generation (5G) network communication via the established communication channel. The first communication processor212may perform data transmission/reception with the second communication processor214. For example, data classified as transmitted via the second cellular network294may be changed to be transmitted via the first cellular network292. In this case, the first communication processor212may receive transmission data from the second communication processor214. For example, the first communication processor212may transmit/receive data to/from the second communication processor214via an inter-processor interface213. The inter-processor interface213may be implemented as, e.g., universal asynchronous receiver/transmitter (UART) (e.g., high speed-UART (HS-UART)) or peripheral component interconnect bus express (PCIe) interface, but is not limited to a specific kind. The first communication processor212and the second communication processor214may exchange packet data information and control information using, e.g., a shared memory. The first communication processor212may transmit/receive various pieces of information, such as sensing information, output strength information, or resource block (RB) allocation information, to/from the second communication processor214. According to implementation, the first communication processor212may not be directly connected with the second communication processor214. In this case, the first communication processor212may transmit/receive data to/from the second communication processor214via a processor120(e.g., an application processor). For example, the first communication processor212and the second communication processor214may transmit/receive data to/from the processor120(e.g., an application processor) via an HS-UART interface or PCIe interface, but the kind of the interface is not limited thereto. The first communication processor212and the second communication processor214may exchange control information and packet data information with the processor120(e.g., an application processor) using a shared memory. According to an embodiment, the first communication processor212and the second communication processor214may be implemented in a single chip or a single package. According to an embodiment, the first communication processor212or the second communication processor214, along with the processor120, an auxiliary processor123, or communication module190, may be formed in a single chip or single package. For example, referring toFIG.2B, an integrated communication processor260may support all of the functions for communication with the first cellular network292and the second cellular network294. Upon transmission, the first RFIC222may convert a baseband signal generated by the first communication processor212into a radio frequency (RF) signal with a frequency ranging from about 700 MHz to about 3 GHz which is used by the first cellular network292(e.g., a legacy network). Upon receipt, the RF signal may be obtained from the first cellular network292(e.g., a legacy network) through an antenna (e.g., the first antenna module242) and be pre-processed via an RFFE (e.g., the first RFFE232). The first RFIC222may convert the pre-processed RF signal into a baseband signal that may be processed by the first communication processor212. Upon transmission, the second RFIC224may convert the baseband signal generated by the first communication processor212or the second communication processor214into a Sub6-band (e.g., about 6 GHz or less) RF signal (hereinafter, “5G Sub6 RF signal”) that is used by the second cellular network294(e.g., a 5G network). Upon receipt, the 5G Sub6 RF signal may be obtained from the second cellular network294(e.g., a 5G network) through an antenna (e.g., the second antenna module244) and be pre-processed via an RFFE (e.g., the second RFFE234). The second RFIC224may convert the pre-processed 5G Sub6 RF signal into a baseband signal that may be processed by a corresponding processor of the first communication processor212and the second communication processor214. The third RFIC226may convert the baseband signal generated by the second communication processor214into a 5G Above6 band (e.g., about 6 GHz to about 60 GHz) RF signal (hereinafter, “5G Above6 RF signal”) that is to be used by the second cellular network294(e.g., a 5G network). Upon receipt, the 5G Above6 RF signal may be obtained from the second cellular network294(e.g., a 5G network) through an antenna (e.g., the antenna248) and be pre-processed via the third RFFE236. The third RFIC226may convert the pre-processed 5G Above6 RF signal into a baseband signal that may be processed by the second communication processor214. According to an embodiment, the third RFFE236may be formed as part of the third RFIC226. According to an embodiment, the electronic device101may include the fourth RFIC228separately from, or as at least part of, the third RFIC226. In this case, the fourth RFIC228may convert the baseband signal generated by the second communication processor214into an intermediate frequency band (e.g., from about 9 GHz to about 11 GHz) RF signal (hereinafter, “IF signal”) and transfer the IF signal to the third RFIC226. The third RFIC226may convert the IF signal into a 5G Above6 RF signal. Upon receipt, the 5G Above6 RF signal may be received from the second cellular network294(e.g., a 5G network) through an antenna (e.g., the antenna248) and be converted into an IF signal by the third RFIC226. The fourth RFIC228may convert the IF signal into a baseband signal that may be processed by the second communication processor214. According to an embodiment, the first RFIC222and the second RFIC224may be implemented as at least part of a single chip or single package. According to various embodiments, when the first RFIC222and the second RFIC224inFIG.2A or2Bare implemented as a single chip or a single package, they may be implemented as an integrated RFIC. In this case, the integrated RFIC is connected to the first RFFE232and the second RFFE234to convert a baseband signal into a signal of a band supported by the first RFFE232and/or the second RFFE234, and may transmit the converted signal to one of the first RFFE232and the second RFFE234. According to an embodiment, the first RFFE232and the second RFFE234may be implemented as at least part of a single chip or single package. According to an embodiment, at least one of the first antenna module242or the second antenna module244may be omitted or be combined with another antenna module to process multi-band RF signals. According to an embodiment, the third RFIC226and the antenna248may be disposed on the same substrate to form the third antenna module246. For example, the wireless communication module192or the processor120may be disposed on a first substrate (e.g., a main painted circuit board (PCB)). In this case, the third RFIC226and the antenna248, respectively, may be disposed on one area (e.g., the bottom) and another (e.g., the top) of a second substrate (e.g., a sub PCB) which is provided separately from the first substrate, forming the third antenna module246. Placing the third RFIC226and the antenna248on the same substrate may shorten the length of the transmission line therebetween. This may reduce a loss (e.g., attenuation) of high-frequency band (e.g., from about 6 GHz to about 60 GHz) signal used for 5G network communication due to the transmission line. Thus, the electronic device101may enhance the communication quality with the second cellular network294(e.g., a 5G network). According to an embodiment, the antenna248may be formed as an antenna array which includes a plurality of antenna elements available for beamforming. In this case, the third RFIC226may include a plurality of phase shifters238corresponding to the plurality of antenna elements, as part of the third RFFE236. Upon transmission, the plurality of phase shifters238may change the phase of the 5G Above6 RF signal which is to be transmitted to the outside (e.g., a 5G network base station) of the electronic device101via their respective corresponding antenna elements. Upon receipt, the plurality of phase shifters238may change the phase of the 5G Above6 RF signal received from the outside to the same or substantially the same phase via their respective corresponding antenna elements. This enables transmission or reception via beamforming between the electronic device101and the outside. The second cellular network294(e.g., a 5G network) may be operated independently (e.g., as standalone (SA)) from, or in connection (e.g., as non-standalone (NSA)) with the first cellular network292(e.g., a legacy network). For example, the 5G network may include access networks (e.g., 5G access networks (RANs)) but lack any core network (e.g., a next-generation core (NGC)). In this case, the electronic device101, after accessing a 5G network access network, may access an external network (e.g., the Internet) under the control of the core network (e.g., the evolved packet core (EPC)) of the legacy network. Protocol information (e.g., LTE protocol information) for communication with the legacy network or protocol information (e.g., New Radio (NR) protocol information) for communication with the 5G network may be stored in the memory230and be accessed by other components (e.g., the processor120, the first communication processor212, or the second communication processor214). FIG.3is a view illustrating wireless communication systems providing a legacy communication network and/or a 5G communication network according to an embodiment of the disclosure. Referring toFIG.3, the network environment300cmay include at least one of a legacy network and a 5G network. The legacy network may include, e.g., a 3GPP-standard 4G or LTE base station (e.g., an eNodeB (eNB))340that supports radio access with the electronic device101and an evolved packet core (EPC)342that manages 4G communication. The 5G network may include, e.g., a new radio (NR) base station (e.g., a gNodeB (gNB))350that supports radio access with the electronic device101and a 5th generation core (5GC)352that manages 5G communication for the electronic device101. According to an embodiment, the electronic device101may transmit or receive control messages and user data via legacy communication and/or 5G communication. The control messages may include, e.g., messages related to at least one of security control, bearer setup, authentication, registration, or mobility management for the electronic device101. The user data may mean, e.g., user data except for control messages transmitted or received between the electronic device101and the core network330(e.g., the EPC). Referring toFIG.3, according to an embodiment, the electronic device101may transmit or receive at least one of a control message or user data to/from at least part (e.g., the NR base station or 5GC) of the 5G network via at least part (e.g., the LTE base station or EPC) of the legacy network. According to an embodiment, the network environment300cmay include a network environment that provides wireless communication dual connectivity (DC) to the LTE base station and the NR base station and transmits or receives control messages to/from the electronic device101via one core network330of the EPC or the 5GC. According to an embodiment, in the DC environment, one of the LTE base station or the NR base station may operate as a master node (MN)310, and the other as a secondary node (SN)320. The MN310may be connected with the core network330to transmit or receive control messages. The MN310and the SN320may be connected with each other via a network interface to transmit or receive messages related to radio resource (e.g., communication channel) management therebetween. According to an embodiment, in E-UTRA new radio dual connectivity (EN-DC), the MN310may include the LTE base station, the SN may include the NR base station, and the core network330may include the EPC. For example, control messages may be transmitted/received via the LTE base station and the EPC, and user data may be transmitted/received at least one of the LTE base station or the NR base station. According to an embodiment, in new radio dual E-UTRA connectivity (NE-DC), the MN310may include the NR base station, the SN320may include the LTE base station, and the core network330may include the 5GC. For example, control messages may be transmitted/received via the NR base station and the 5GC, and user data may be transmitted/received at least one of the LTE base station or the NR base station. According to an embodiment, the electronic device101may be registered in at least one of the EPC or the 5GC to transmit or receive control messages. According to an embodiment, the EPC or the 5GC may interwork with each other to manage communication for the electronic device101. For example, mobility information for the electronic device101may be transmitted or received via the interface between the EPC and the 5GC. Besides the EN-DC, the MR DC may have other various applications. For example, a first network and a second network by the MR DC may be both related to LTE communication, and the second network may be a network corresponding to a small cell of a specific frequency. For example, the first network and the second network by the MR DC may be both related to 5G, and the first network may correspond to a frequency band (e.g., below 6) less than 6 GHz, and the second network may correspond to a frequency band (e.g., over 6) not less than 6 GHz. It will be easily appreciated by one of ordinary skill in the art that other various dual-connectivity-applicable network structures may be applied to embodiments of the disclosure. FIG.4Ais a view illustrating transmission of a reference signal by an electronic device according to an embodiment of the disclosure. Referring toFIG.4A, an electronic device101(e.g., the electronic device101ofFIG.1) may transmit a reference signal (e.g., an SRS) through four antennas (e.g., a first antenna411, a second antenna412, a third antenna413, and a fourth antenna414). For example, the electronic device101may amplify the reference signal through at least one power amplifier (PA)415and may transmit the amplified reference signal to the first antenna411, the second antenna412, the third antenna413, and the fourth antenna414through at least one switch416. The reference signal (e.g., an SRS) transmitted through each antenna (e.g., the first antenna411, the second antenna412, the third antenna413, and the fourth antenna414) of the electronic device101may be received through each antenna421of a base station420(e.g., a gNB). According to various embodiments, the base station420may receive the reference signal transmitted from the electronic device101and may estimate the channel for each antenna (e.g., the first antenna411, the second antenna412, the third antenna413, and the fourth antenna414) of the electronic device101from the received reference signal. The base station420may transmit a precoded downlink signal to the electronic device101based on the channel estimation. For example, the electronic device101and the base station420may perform MIMO communication. According to various embodiments, the base station420may perform beamforming based on channel estimation in an FR2 band. AlthoughFIG.4Aillustrates one power amplifier415and one switch416connected with a plurality of antennas (a first antenna411, a second antenna412, a third antenna413, and a fourth antenna414) for ease of description, it will readily be appreciated by one of ordinary skill in the art that embodiments of the disclosure are not limited thereto. Referring toFIG.4B, if the electronic device101transmits a reference signal (e.g., an SRS) through a plurality of transmission paths, the base station420may identify the channel environment with each antenna (e.g., the first antenna411, the second antenna412, the third antenna413, and the fourth antenna414)) of the electronic device101and may use the identified channel environment for precoding (or beamforming), enhancing the reference signal received power (RSRP) and/or signal to noise ratio (SNR) of the downlink channel. If the RSRP and/or SNR of the downlink channel is enhanced, the rank index (RI) or channel quality indicator (CQI) for the electronic device may be increased. The base station420allocates a high rank or modulation and code schemes (MCS) to the electronic device101based on the enhanced performance of the electronic device101so that the downlink throughput of the electronic device101may be enhanced. According to various embodiments, the base station420may use a downlink reference signal for downlink channel estimation. For example, if the base station420transmits the downlink reference signal to the electronic device101, the electronic device101may receive the downlink reference signal transmitted from the base station420and perform channel estimation. The electronic device101may transmit the result of channel estimation to the base station420, and the base station420may perform downlink beamforming with reference to the result of the channel estimation transmitted from the electronic device101. According to various embodiments, when the base station420performs channel estimation by the reference signal (e.g., an SRS) transmitted from the electronic device101, channel estimation may be performed faster than the channel estimation by the downlink reference signal, According to various embodiments, a first communication network (e.g., a base station (gNB)) or a second communication network (e.g., a base station (gNB)) may send a request for various configuration information for the electronic device101by transmitting a UE capability enquiry message to the electronic device101. For example, a first communication network (e.g., a base station (gNB)) or a second communication network (e.g., a base station (eNB)) may send a request for information related to the reception antenna of the electronic device101through the UE capability enquiry message. The electronic device101may receive the UE capability enquiry message from the first communication network or the second communication network and, in response thereto, may transmit a UE capability information message to the first communication network or the second communication network. According to various embodiments, information related to the reception antenna of the electronic device101, such as ‘supportedSRS-TxPortSwitch t1r4,’ may be included in the UE capability information message, according to the content of the UE capability enquiry message. As the antenna-related information is specified as ‘supportedSRS-TxPortSwitch t1r4’, the first communication network may determine that the electronic device101may transmit signals using four reception antennas and transmit an RRC reconfiguration message including information for the time of transmission of a reference signal (e.g., an SRS) for each of the four antennas. FIG.5is a flowchart illustrating a signal transmission/reception procedure between an electronic device and a communication network according to an embodiment of the disclosure. Referring toFIG.5, an electronic device101may establish an RRC connection with a first communication network (e.g., a base station (gNB))600through a random access channel (RACH) procedure. According to various embodiments, in operation510, the first communication network500may transmit an RRC reconfiguration message to the electronic device101. For example, the first communication network500may transmit an RRC reconfiguration message in response to the RRC request message transmitted by the electronic device101. As described above, the RRC reconfiguration message may include information regarding a time at which the electronic device101transmits a reference signal (e.g., an SRS) through each antenna as follows.perodicityAndOffset-p s120:17perodicityAndOffset-p s120:7perodicityAndOffset-p s 120:13perodicityAndOffset-p s120:3nrofSymbols n1 Referring to the RRC reconfiguration message, it may be seen that as specified as “nrofSymbols n1.”, the duration of SRS transmission may be determined as an allocated symbol. Further, referring to the RRC reconfiguration message, as specified as “periodicityAndOffset-p s120:17”, the first SRS may be set to be transmitted in the 17th slot while being transmitted once every 20 slots. As specified as “periodicityAndOffset-p s120:7”, the second SRS may be set to be transmitted in the 7th slot while being transmitted once every 20 slots. As specified as “periodicityAndOffset-p s120:13”, the third SRS is transmitted in the 13th slot while being transmitted once every 20 slots. As specified as “periodicityAndOffset-p s120:3”, the fourth SRS is set to be transmitted in the 3rd slot while being transmitted once every 20 slots. According to various embodiments, the electronic device101may transmit four SRSs at different times through the respective antennas every 20 slots according to the configuration of RRC reconfiguration. The size of one slot may be determined by the subcarrier spacing (SCS). For example, when the SCS is 30 KHz, the time interval of one slot may be 0.5 ms, and the time interval of 20 slots may be 10 ms. Accordingly, the electronic device101may repeatedly transmit the SRS at different times through the respective antennas every 10 ms. According to various embodiments, one slot may include 14 symbols and, assuming that one symbol is allocated for one SRS transmission, it may have a symbol duration (or symbol enable time) of 0.5 ms* 1/14=35 μs (0.035 ms). According to various embodiments, in operation520, the electronic device101may transmit an RRC reconfiguration complete message to the first communication network500. As the RRC reconfiguration procedure is normally completed, in operation530, the electronic device101and the first communication network600may complete RRC connection establishment. According to various embodiments, as described above, the electronic device101may transmit reference signals at different times for each time period (e.g., 10 ms) set through each antenna transmission path based on information regarding the transmission time of the reference signal (e.g., an SRS) received from the first communication network500as described above. FIG.6is a view illustrating a transmission period of a reference signal according to an embodiment of the disclosure. Referring toFIG.6, e.g., the electronic device101may transmit the first SRS in the 17th slot among 20 slots every 10 ms, the second SRS in the 7th slot, the third SRS in the 13th slot, and the fourth SRS in the third slot. For example, the electronic device101may include four reception antennas, supporting 1T4R (e.g., a scenario in which among the four antennas, one antenna is mapped for transmission purposes). The electronic device101may transmit an SRS signal through each of four reception antennas (e.g., RX0, RX1, RX2, and RX3 ofFIG.6). According to various embodiments, the reference signal may be a sounding reference signal (SRS) used for multi-antenna signal processing (e.g., multi input multi output (MIMO) or beamforming) through uplink channel state measurement, but embodiments of the disclosure are not limited thereto. For example, although SRS is used as an example of the reference signal in the above description or the following description, any type of uplink reference signal (e.g., uplink demodulation reference signal (DM-RS)) transmitted from the electronic device101to the base station signal may be included in the reference signal described below. FIG.7is a block diagram illustrating an electronic device according to an embodiment of the disclosure. The embodiment ofFIG.7is described with reference toFIGS.8A to8D. FIGS.8A and8Billustrate block error rates (BLERs) measured in a plurality of frequency bands while SRS transmission is performed according to various embodiments of the disclosure. FIGS.8C and8Dillustrate BLERs measured in a plurality of frequency bands while SRS transmission is stopped according to various embodiments of the disclosure. Referring toFIG.7, an electronic device101may include a communication processor710(e.g., at least one of the first communication processor212, the second communication processor214, or the integrated communication processor260) and an RF circuit720(e.g., at least one of the first RFIC222, the second RFIC224, the third RFIC226, or the fourth RFIC228). The electronic device101may include at least one of at least one amplifier730,750, and770, at least one switch735,755, and775, or at least one antenna741,742,743,744,761,762,763,764,781,782,783, and784. For convenience of description, althoughFIG.7illustrates that elements for RF signal transmission are included in the electronic device101, it will be easily appreciated by one of ordinary skill in the art that elements for receiving and/or processing RF signals may further be included in the electronic device101. According to various embodiments, the communication processor710may support a plurality of RATs (e.g., LTE communication and NR communication). In the communication processor710, protocol stacks (e.g., a 3GPP protocol stack for LTE communication and a 3GPP protocol stack for NR communication) for the plurality of RATs may be defined (or stored). The protocol stack may receive a data packet (or Internet protocol (IP) packet) from the application processor (e.g., the processor120) (or the transmission control protocol (TCP)/IP stack) and process and output it. If the RF signal received from the outside is converted into a baseband signal and received, the protocol stack may process the baseband signal and provide it to the application processor (e.g., the processor120(or TCP/IP stack)). The protocol stack may perform an operation for signaling (e.g., control). According to various embodiments, the RF circuit720may process the signal (e.g., a baseband signal) from the communication processor710and output an RF signal. At least one amplifier730,750, or770may amplify and provide the received RF signal. As the at least one amplifier730,750, and770is controlled, the output power of the RF signal may be adjusted. The SRS of NR communication may be transmitted through each of the first antenna741, the second antenna742, the third antenna743, and the fourth antenna744. For example, the electronic device101may support 1T4R. The first antenna741may be an antenna capable of performing both transmission and reception, and the second antenna742, the third antenna743, and the fourth antenna744may be antennas for reception. The communication processor710may identify SRS transmission power and may control the amplifier730so that the identified SRS transmission power is applied to the port for each antenna. The switch735may selectively connect the RF circuit720and the antenna so that the RF signal is applied to a designated antenna. For example, the connection state of the switch735may be controlled so that the SRS is sequentially applied through each of the antennas741,742,743, and744. For example, in the example ofFIG.7, the SRS is shown as transmitted in the n78 frequency band, but the frequency band is not limited thereto. It will be easily appreciated by one of ordinary skill in the art that the number of antennas741,742,743, and744for NR communication is exemplary and is not limited thereto. 1T4R is merely an example. The electronic device101may support 1T2R, 2T4R, or other capabilities, and it will be easily appreciated by one of ordinary skill in the art that the number of antennas, the number of amplifiers, and/or the connection relationship between the antennas is not limited to a specific one. According to various embodiments, the electronic device101may support carrier aggregation (CA) for LTE. For example, in the embodiment ofFIG.7, the frequency band of B7 associated with the primary cell (PCell) may be selected, and at least one frequency band (not shown) associated with the secondary cell (SCell) may be selected. The number of component carriers (CCs) for CA is not limited to a specific one. However, depending on hardware (HW) restrictions and the frequency band operated by the operator, 2 or more and 32 or less CCs may be typically operated. The signal associated with the PCell may be transmitted/received via at least one of the antennas761,762,763, and764via the amplifier750and/or the switch755. The signal associated with the S Cell may be transmitted/received via at least one of the antennas781,782,783, and784, via the amplifier770and/or the switch775. The number of antennas761,762,763, and764and the number of antennas781,782,783, and784are exemplary. According to various embodiments, a plurality of frequency bands may correspond to one antenna. For example, the antennas761,762,763, and764may correspond not only to ultra-high bands (e.g., frequency bands78and79) but also to high bands (e.g., frequency bands7,38,39,40, and41). Accordingly, it will be easily appreciated by one of ordinary skill in the art that the number of antennas may be smaller than that ofFIG.7. According to various embodiments, the electronic device101may transmit an SRS based on the first RAT (e.g., NR communication). For example, the electronic device101may report the UE capability of 1T4R to the network and may receive an SRS configuration from the network. The electronic device101may identify times of transmission of four SRSs for transmitting the SRS based on the SRS configuration. The SRS transmission time may be referred to as an SRS slot. The electronic device101may control the amplifier730and/or the switch735to transmit the first SRS through the first antenna741during the first SRS slot, the second SRS through the second antenna742during the second SRS slot, the third SRS through the third antenna743during the third SRS slot, and the fourth SRS through the fourth antenna744during the fourth SRS slot. The electronic device101may receive downlink data based on the second RAT (e.g., LTE). The electronic device101may receive downlink data through, e.g., at least some of the antennas761,762,763,764,781,782,783, and784. However, the RF path for SRS transmission for the first RAT may not be completely isolated from the RF path for downlink data reception for the second RAT. In this case, noise may occur in the RF path for receiving downlink data for the second RAT. Or, a harmonic component corresponding to SRS transmission may occur, and noise may be caused in the RF path due to the harmonic component. Accordingly, the BLER corresponding to the downlink frequency band may increase. In the embodiment ofFIG.7, the case in which the electronic device101performs CA for any one RAT (e.g., LTE) has been described. However, it is exemplary, and various embodiments of the disclosure may also be applied even when any one RAT does not perform CA. For example,FIG.8Aillustrates BLERs801to810for each subframe in the frequency band (e.g., B7) of the PCell of the second RAT (e.g., LTE). Referring toFIG.8A, the electronic device101may transmit the first SRS in the SRS slot of the first RAT (e.g., NR communication) corresponding to the fourth subframe of the second RAT (e.g., LTE), the second SRS in the SRS slot of the first RAT (e.g., NR communication) corresponding to the 7th subframe of the second RAT (e.g., LTE), the third SRS in the SRS slot of the first RAT (e.g., NR communication) corresponding to the 8th subframe of the second RAT (e.g., LTE), and the fourth SRS in the SRS slot of the first RAT (e.g., NR communication) corresponding to the 9th subframe of the second RAT (e.g., LTE). The BLER805corresponding to the fourth subframe, the BLER807corresponding to the sixth subframe, and the BLER810corresponding to the ninth subframe may be measured to be relatively high. FIG.8Billustrates the BLERs of the frequency bands of four SCells based on CA of 5CC. Referring toFIG.8B, it may be identified that the BLER821corresponding to the fourth subframe in the first SCell frequency band, the BLER822corresponding to the sixth subframe, and the BLER823corresponding to the ninth subframe are relatively large. It may be identified that the BLER831corresponding to the fourth subframe in the second SCell frequency band, the BLER832corresponding to the sixth subframe, and the BLER833corresponding to the ninth subframe are relatively large. It may be identified that the BLER841corresponding to the fourth subframe in the third SCell frequency band, the BLER842corresponding to the sixth subframe, and the BLER843corresponding to the ninth subframe are relatively large. It may be identified that the BLER851corresponding to the fourth subframe in the fourth SCell frequency band, the BLER852corresponding to the sixth subframe, and the BLER853corresponding to the ninth subframe are relatively large. This may be due to the fact that the RF path for the first SRS, the RF path for the second SRS, and the RF path for the fourth SRS are not completely isolated from the RF path corresponding to the PCell. FIG.8Cillustrates BLERs861to870for each subframe in the frequency band (e.g., B7) of the PCell of the second RAT (e.g., LTE) when no SRS is transmitted in the same environment. Referring toFIG.8C, it may be identified that the BLER865corresponding to the fourth subframe, the BLER867corresponding to the sixth subframe, and the BLER870corresponding to the ninth subframe are reduced as compared to the case ofFIG.8A. Referring toFIG.8D, the BLERs of frequency bands of four SCells based on CA of 5CC when no SRS is transmitted are shown. It may be identified that the BLER871corresponding to the fourth subframe in the first SCell frequency band, the BLER872corresponding to the sixth subframe, and the BLER873corresponding to the ninth subframe are relatively reduced as compared withFIG.8B. It may be identified that the BLER874corresponding to the fourth subframe in the second SCell frequency band, the BLER875corresponding to the sixth subframe, and the BLER876corresponding to the ninth subframe are relatively reduced as compared withFIG.8B. It may be identified that the BLER877corresponding to the fourth subframe in the third SCell frequency band, the BLER878corresponding to the sixth subframe, and the BLER879corresponding to the ninth subframe are relatively reduced as compared withFIG.8B. It may be identified that the BLER880corresponding to the fourth subframe in the fourth SCell frequency band, the BLER881corresponding to the sixth subframe, and the BLER882corresponding to the ninth subframe are relatively reduced as compared withFIG.8B. As a result of comparison betweenFIGS.8A and8Band betweenFIGS.8C and8D, it may be identified that the high BLERs in some subframes inFIGS.8A and8Bare attributed to SRS transmission. According to various embodiments, when the BLER meets a designated condition, the electronic device101may perform a restriction operation on the corresponding SRS. For example, inFIGS.8A and8B, when the BLERs in the fourth subframe and the ninth subframe of the second RAT (e.g., LTE) meets a designated condition, restriction operations corresponding to the first SRS corresponding to the fourth subframe and the fourth SRS corresponding to the ninth subframe may be performed. Alternatively, the electronic device101may perform a restriction operation corresponding to all the SRSs. According to various embodiments, restriction operations are described below. As the SRS restriction operation is performed, the BLER may be reduced and the overall data throughput may be prevented from being reduced. FIG.9is a flowchart illustrating an operation method of an electronic device according to an embodiment of the disclosure. According to various embodiments, an electronic device101(e.g., at least one of the processor120, the first communication processor212, the second communication processor214, or the integrated communication processor260) may identify at least one time (e.g., at least one time point) of transmission of the SRS configured in NR communication in operation901. Referring toFIG.9, the electronic device101may use EN-DC based on LTE communication and NR communication, but as described above, the type of DC is not limited. The electronic device101may identify at least one time of transmission (e.g., at least one SRS slot) of SRS based on the SRS configuration received from the network. According to various embodiments, the electronic device101may identify at least one time (e.g., at least one of the time of reception or the time of transmission) for data transmission/reception of LTE communication corresponding to at least one time of transmission of the SRS, in operation903. For example, the electronic device101may identify at least one time of reception of LTE communication corresponding to at least one time of transmission of the SRS using a real time clock (RTC) defined therein. In one example, the electronic device101may identify the first time of the RTC corresponding to the synchronization channel of the NR communication. The electronic device101may identify a difference between the time of NR communication and the time of LTE communication by identifying the synchronization channel of LTE communication corresponding to the first time of RTC. The electronic device101may identify at least one time of reception of LTE communication corresponding to at least one time of transmission of SRS using the identified difference. As another example, the electronic device101may identify at least one time of RTC corresponding to at least one time of transmission of the SRS. The electronic device101may identify at least one time (e.g., a subframe (or slot)) of LTE communication corresponding to at least one time of the RTC. Meanwhile, the scheme for identifying the time of LTE communication corresponding to the above-described time of transmission of SRS is not limited. According to various embodiments, in operation905, the electronic device101may identify the BLER of at least one frequency band associated with LTE communication at, at least, one time for data transmission/reception of LTE communication. For example, referring toFIG.8A, the electronic device101may identify a fourth subframe, a sixth subframe, an eighth subframe, and a ninth subframe of LTE communication corresponding to four SRS slots corresponding to four SRSs. The electronic device101may identify the BLERs in the fourth subframe, the sixth subframe, the eighth subframe, and the ninth subframe of LTE communication. If CA is being performed in LTE communication, the electronic device101may identify the BLERs in the frequency band corresponding to the PCell and at least one frequency band corresponding to the Scell. The electronic device101may be configured to identify the BLER for all the frequency bands but, in another example, the electronic device101may be configured to identify the BLER for some of all the frequency bands. According to various embodiments, in operation907, the electronic device101may perform an SRS restriction operation based on the BLER meeting a designated condition. The designated condition may be when the BLER is greater than or equal to a threshold (e.g., 50%) at which data throughput may be determined to be degraded, but is not limited thereto. If the BLER is measured for a plurality of frequency bands, a threshold corresponding to the PCell and a threshold corresponding to the SCell may be set to differ from each other. The electronic device101may perform the SRS restriction operation, e.g., when the BLER in any one of the plurality of frequency bands is equal to or greater than a threshold. Alternatively, the electronic device101may perform the SRS restriction operation when the number of frequency bands, in which the BLER is equal to or greater than the threshold, among the plurality of frequency bands is equal to or greater than a threshold number. Alternatively, the electronic device101may determine whether to perform the SRS restriction operation based on whether the sum (or weighted sum) or average of the BLER in a specific subframe in the PCell and the BLER in a specific subframe in the SCell meets a designated condition. It will be easily appreciated by one of ordinary skill in the art that the above-described designated condition of BLER is not limited as long as it is a condition indicating that data throughput is reduced due to SRS transmission. It will be easily appreciated by one of ordinary skill in the art that other indicators (e.g., modulation and coding scheme (MCS) or channel quality information (CQI)) indicating the quality of downlink, other than BLER, may be used instead of and/or in addition to the BLER according to various embodiments of the disclosure. According to various embodiments, the electronic device101may also determine whether to perform an SRS restriction operation based on a result of comparison between the BLER in the subframe of LTE communication when no SRS is not transmitted and the BLER in the subframe when an SRS is transmitted. For example, in the example ofFIG.7A, subframes of LTE communication corresponding to SRS slots of NR communication are a fourth subframe, a sixth subframe, an eighth subframe, and a ninth subframe. The electronic device101may identify the BLER of the subframe (e.g., the third subframe) when no SRS is transmitted. The electronic device101may determine whether to perform an SRS restriction operation based on the result of comparison between the two BLERs. If the difference between the two BLERs is equal to or greater than a threshold difference, the electronic device101may perform an SRS restriction operation. Alternatively, if the ratio between the two BLERs is equal to or greater than a threshold ratio, the electronic device101may perform an SRS restriction operation. The electronic device101may set, as a reference, the BLER of the subframe before or after the subframe where an SRS is transmitted, but this is exemplary. Any BLER of the subframe where no SRS is not transmitted may be used as a reference without limitation. Alternatively, the electronic device101may set an average or an intermediate value of the BLERs of a plurality of subframes where no SRS is transmitted, as a reference, and the reference is not limited to a specific one. According to various embodiments, when a condition designated for the BLER in a specific subframe is met, the electronic device101may perform an SRS restriction operation immediately in response thereto. In another embodiment, the electronic device101may also be configured to perform an SRS restriction operation if it is identified that the number of times in which the designated condition is met during a predetermined period (e.g.,10radio frames) is equal to or greater than a threshold number, or occasions of meeting the designated condition continuously occur (e.g., three consecutive times). The identification of the BLER when an SRS is transmitted and whether the designated condition is met as described above may be performed, e.g., by the L1 layer, but is not limited as performed by a specific entity. The L1 layer may perform, e.g., identification of the subframe of LTE communication corresponding to the SRS slot of NR communication, identification of the BLER in the identified subframe, and/or identification of whether the identified BLER meets a designated condition. According to various embodiments, SRS restriction operations may include at least one of adjusting the transmission power of the SRS, adjusting the port of the SRS, or stopping the SRS, which are described below. FIG.10is a flowchart illustrating an operation method of an electronic device according to an embodiment of the disclosure. According to various embodiments, an electronic device101(e.g., at least one of the processor120, the first communication processor212, the second communication processor214, or the integrated communication processor260) may identify at least one time of transmission of the SRS configured in NR communication in operation1001. In operation1003, the electronic device101may identify at least one time (e.g., a time of reception and/or time of transmission of LTE communication) for data transmission/reception of LTE communication corresponding to at least one time of transmission of the SRS. In operation1005, the electronic device101may identify the BLER of at least one frequency band associated with LTE communication at, at least, one time for data transmission/reception of LTE communication. In operation1007, the electronic device101may determine whether the BLER meets a designated condition. For example, with reference toFIG.9, the electronic device101may determine whether the BLER meets the designated condition based on various schemes. If the BLER does not meet the designated condition (No in1007), in operation1009, the electronic device101may transmit the SRS at, at least, one time of transmission. For example, the electronic device101may transmit an SRS at, at least, one time of transmission identified based on the SRS configuration. SRS transmission power may be determined, e.g., as defined in 3GPP TS 38.213, which is described below. If the BLER meets the designated condition (Yes in1007), according to various embodiments, the electronic device101may determine whether the ratio of the data throughput of LTE communication to the overall data throughput is equal to or greater than a threshold ratio in operation1011. In one example, the electronic device101may identify the theoretical data throughput corresponding to each of the currently used frequency bands (e.g., at least one frequency band of NR communication and at least one frequency band of LTE communication). Unless the ratio of the data throughput of LTE communication to the overall data throughput is equal to or greater than the threshold ratio (No in1011), the electronic device101may transmit an SRS without an SRS restriction operation in operation1009. If the ratio of the data throughput of LTE communication to the overall data throughput is equal to or greater than the threshold ratio (Yes in1011), the electronic device101may perform an SRS restriction operation in operation1013. Even when a high BLER occurs in LTE communication according to SRS transmission in NR communication, if the proportion of the data throughput of LTE communication is not large, an SRS restriction operation may rather cause a decrease in the overall data throughput. Accordingly, according to various embodiments, the electronic device101may be configured to perform an SRS restriction operation when the ratio of the data throughput of LTE communication to the overall data throughput is equal to or greater than the threshold ratio. According to various embodiments, the electronic device101may identify the theoretical data throughput of NR communication based on Equation 1. datarate(inMbps)=∑j=1J(νLayers(j)·Qm(j)·f(j)·Rmax·BW(j)·Su(j)·(1-OH(j)))Equation1 In Equation 1, J may be the number of CCs. Equation 1 may represent the sum of per-CC data throughputs. vLayers(j)may be the maximum number of layers, Qm(j)may be the maximum value of the modulation order, f(j)may be the scaling factor, Rmaxmay be a fixed value (e.g., 948/1024=0.926), BW(j)may be the bandwidth, Su(j)may be spectral utilization, and OH(j)may be overhead. Each parameter, e.g., Equation 1, may be based on 3GPP TS 38.306 dp, but is not limited thereto. The electronic device101may identify the theoretical data throughput in the frequency band of NR communication, e.g., as defined in 3GPP TS 38.331. For example, the electronic device101may set the periodicity of the DL slot and the UL slot considering TDD-UL-DL-ConfigCommon in the received RRC reconfiguration message. For example, when the SCS is 30 kHz and the RB is 273, it is assumed that the electronic device101identifies a theoretical data throughput of 584.25 Mbps based on, e.g., Equation 1. In TDD, in the case of nrofDownlinkSlots(3) and nrofUplinkSlots(1), the slot periodicity may be DDDSU. Accordingly, when the overall bandwidth is, e.g., 100 Mhz, the downlink dedicated bandwidth may be 60 Mhz, which is 60% of the overall bandwidth. Here, 10 out of 14 symbols in S may be used as a downlink. In this case, the theoretical data throughput may be 434.014 Mbps as a value obtained by multiplying 584.25 Mbs based on Equation 1 by (0.6+0.2*( 10/14)). 0.6 may correspond to DDD among DDDSU, 0.2 may correspond to S, and 10/14 may mean a ratio of downlink symbols to all the symbols in S. According to various embodiments, the electronic device101may identify the theoretical data throughputs of PCell and SCell of LTE communication. The electronic device101may identify the theoretical data throughput based on, e.g., the TBS index and NPRB. For example, the electronic device101may store data throughput information for each NPRBand TBS index of 3GPP TS 36.213 (e.g., 7.1.7.2.1-1 of 3 GPPP TS 36.213: transport block size table) and identify the data throughput corresponding to the identified information. The electronic device101may also identify the TBS index based on the MCS index and the modulation order. The electronic device101may identify the theoretical data throughput based on the identified data throughput, layer, and MCS. For example, it is assumed that the PCell supports 4×4 MIMO and 256QAM. The electronic device101may identify the data throughput as 75376 kbps based on data throughput information (e.g., 7.1.7.2.1-1 of 3 GPPP TS 36.213: transport block size table). Based on 4×4 MIMO, the electronic device101may identify the theoretical data throughput as 4 times 75376 kbps or about 300 Mbps. If 256QAM is applied, the electronic device101may identify the identified theoretical data throughput as 400 Mbps, rather than 300 Mbps. The electronic device101may identify the theoretical data throughput for the SCell in the same manner. The electronic device101may identify the layer when adding CA of the SCell of LTE communication. For example, when referring to ScellIndex-r10 1, it is antennaPortsCount an4 and, when referring to ScellIndex-r10 2, it is antennaPortsCount an2. Based on this, it may be identified that SCC1 is operated in 4×4 MIMO and SCC2 is operated in 2×2 MIMO. Further, the bandwidth of the SCell may be identified based on “dl-Bandwidth-r10” of the RRC reconfiguration message and, based thereupon, the theoretical data throughput of the SCell of LTE communication may be calculated. For example, with 75 RBs in the case of 4×4 MIMO and 256 QAM, a theoretical data throughput of 300 Mbps may be calculated. Tables 1 and 2 are examples of the theoretical data throughput and actual data throughput when 3CC CA in LTE communication and EN-DC of NR communication are in use. Tables 1 and 2 may be the results of measurement by different operators. TABLE 1FrequencyTP (Mbps)TP whenbandCenterwhen SRSno SRSTheoreticalRATCC(Bandwidth)frequency (MHz)is transmittedis transmittedTPLTEPCellB3 (20 Mhz)1385183279400LTESCell-1B7 (20 Mhz)3150194293400LTESCell-2B7 (20 Mhz)285094172200NR—N78 (20 Mhz)626722250235580Sum7219791590 TABLE 2FrequencyTP (Mbps)TP whenbandCenterwhen SRS isno SRSTheoreticalRATCC(Bandwidth)frequency (MHz)transmittedis transmittedTPLTEPCellB7 (20 Mhz)3350113174200LTESCell-1B3 (10 Mhz)16515376100LTESCell-2B1 (10 Mhz)10262135200NR—N78 (30 Mhz)626722506471860Sum7348561360 In the example of Table 1, the ratio of data throughput (e.g., 400+400+200=1000 Mbps) by LTE communication to the total data throughput (e.g., 1590 Mbps) may be 63.29%. Further, a reduction rate of the overall data throughput (e.g., 721 Mbps) when an SRS is transmitted, relative to the overall data throughput (e.g., 979 Mbps) when no SRS is transmitted, may be 26.35%. In the example of Table 2, the ratio of data throughput (e.g., 200+100+200=600 Mbps) by LTE communication to the total data throughput (e.g., 1360 Mbps) may be 36.76%. Further, a reduction rate of the overall data throughput (e.g., 734 Mbps) when an SRS is transmitted, relative to the overall data throughput (e.g., 856 Mbps) when no SRS is transmitted, may be 14.25%. It may be identified that when the proportion of the data throughput of LTE communication is relatively high, the reduction of the overall data throughput is relatively high. Accordingly, the electronic device101may be configured to perform an SRS restriction operation when the ratio of the data throughput of the remaining RATs other than the transmission RATs of the SRS, relative to the total data throughput is equal to or greater than a threshold ratio (e.g., 30%), The threshold ratio may be a fixed value or an adjustable value. The above-described identification of the ratio of data throughput of LTE communication to the overall data throughput may be performed, e.g., by the L3 layer, but is not limited as performed by a specific entity. The L3 layer may identify the data throughput for each RAT based on information obtained from the RRC message and/or information obtained from the L1 layer. When it is identified that the BLER in operation1007meets the designated condition, the L1 layer may obtain the data throughput for each RAT (or the ratio of the LTE communication data throughput to the overall data throughput) from the L3 layer and may perform operation1011. In another embodiment, the electronic device101may determine whether to perform an SRS restriction operation using an actual data throughput instead of the theoretical data throughput. FIG.11is a flowchart illustrating an operation method of an electronic device according to an embodiment of the disclosure. The embodiment ofFIG.11is described with reference toFIG.12. FIG.12illustrates a BLER and SRS transmission power of LTE communication, according to an embodiment of the disclosure. According to various embodiments, an electronic device101(e.g., at least one of the processor120, the first communication processor212, the second communication processor214, or the integrated communication processor260) may identify SRS transmission power in operation1101. In operation1103, the electronic device101may transmit an SRS based on the identified SRS transmission power. The electronic device101may determine the transmission power of the SRS based on SRS target power and/or the maximum power (e.g., UE Tx MAX power) of the electronic device101. The electronic device101may determine the SRS target power (or SRS output power) based on Equation 2 according to, e.g., 3GPP TS 38.213. PO_SRS,b,f,c(qs)+10 log10(2μ·MSRS,b,f,c(i))+αSRS,b,f,c(qs)·PLb,f,c(qd)+hb,f,c(i,l) Equation 2 The definition of Equation 1 may follow 3GPP TS 38.213. For example, PO_SRS,b,f,c(qs)may be provided by p0 for the activation uplink bandwidth part (UL BWP)(b) of the serving cell c and the SRS resource set (qs) provided by the SRS-ResourceSetID and the SRS-ResourceSet according to the SRS configuration. MSRS,b,f,c(i) is the SRS bandwidth expressed as the numbers of resource blocks for the SRS transmission occasion (i) on the activation UL BWP(b) of the carrier f of the serving cell c, and μ is the SCS. αSRS,b,f,c(qs) is provided by alpha for the activation UL BWP of the carrier f of the serving cell c and the SRS resource set qs. PLb,f,c(qd) is the downlink pathloss predicted in dB by the user equipment (UE) using the RS resource index qdfor the activation downlink BWP (DL BWP) of the serving cell c and the SRS resource set qs. hb,f,c(i, 1) may be δSRS,b,f,c(i, 1) and, for the condition, may follow 3GPP TS 38.213, and it is a value that may be adjusted by downlink control information (DCI) from the base station. The maximum power of the electronic device101may be determined as the minimum value of the maximum available transmission power PcMax of the electronic device101considering the characteristics of the electronic device101, the maximum transmission power PeMax according to the power class set in the electronic device101, and the maximum transmission power (SAR Max Power) considering the specific absorption rate (SAR) backoff event, but the scheme of determination is not limited to a specific one. In one example, the maximum power for SRS may be set to be larger than the common UE TX Max Power. The electronic device101may determine, e.g., the lower value of the SRS target power and the maximum power as the SRS transmission power. The electronic device101may be installed inside or outside the RFFE to control the power amplifier to transmit an SRS with the SRS transmission power. In various embodiments, transmitting the SRS in a specific size may mean controlling at least one amplifier in the electronic device101so that power (e.g., in dBm) corresponding to the specific size is provided to the antenna. According to various embodiments, the electronic device101may determine whether a condition of an SRS restriction operation is identified in operation1105. For example, referring toFIG.9, the electronic device101may determine whether the BLER in LTE communication meets a designated condition. Referring toFIG.10, the electronic device101may determine whether the BLER in LTE communication meets the designated condition and whether the ratio of the data throughput of LTE communication to the overall data throughput is greater than or equal to a threshold ratio. If the condition of the SRS restriction operation is identified (Yes in1105), the electronic device101may adjust the SRS transmission power and transmit an SRS in operation1107. The electronic device101may determine whether the condition of the SRS restriction operation is identified even after the SRS transmission power is adjusted and may adjust the SRS transmission power until the condition of the SRS restriction operation is not identified. If the condition of the SRS restriction operation is not identified (No in1105), the electronic device101may maintain the SRS transmission power in operation1109. However, the electronic device101may adjust the SRS transmission power according to a change in the SRS target power of 3GPP TS 38.211 (e.g., reception of DCI from the network). Referring toFIG.12, the electronic device101may transmit the SRSs1211,1212,1213,1214, and1215at a set time using an antenna designated based on a configuration for SRS transmission. For example, it is assumed that the SRSs1211,1212,1213,1214, and1215inFIG.12are transmitted through any one designated antenna port. SRSs transmitted through the other antenna ports are omitted for clarity of description. The electronic device101may transmit a first SRS1211in NR communication at t1. The SRS transmission power of the first SRS1211may be b1. At t1, the BLER1201in a first frequency band of LTE communication may be a1%, which may be above a threshold BLER (BLER-TH). The electronic device101may thus adjust the SRS transmission power. At t2, the electronic device101may transmit a second SRS1212. The SRS transmission power of the second SRS1212may be b2. The electronic device101may adjust the SRS transmission power using, e.g., a designated adjustment amount (e.g., b2-b1 dB), but the adjustment amount and/or adjustment scheme is not limited to a specific one. For example, the electronic device101may determine the adjustment amount of SRS transmission power of NR communication based on the BLER1202and BLER1203measured in LTE communication. The electronic device101may adjust the SRS transmission power up to b4 until a BLER (e.g., BLER1204) less than the threshold BLER (BLER-TH) is identified. When a fourth SRS1214is transmitted, the BLER1204below the threshold BLER (BLER-TH) may be identified, and accordingly, the electronic device101may maintain the SRS transmission power as b4. The electronic device101may transmit a fifth SRS1215based on the SRS transmission power of b4. The BLER1205in LTE communication while the fifth SRS1215is transmitted may be a5. However, it will be easily appreciated by one of ordinary skill in the art that as described above, if the SRS transmission power based on 3GPP TS 38.211 is adjusted, the electronic device101may adjust the SRS transmission power even when the BLER1204less than the threshold BLER (BLER-TH) is identified. In various embodiments, the electronic device101may adjust the SRS transmission power of a specific port so that the BLER corresponding to the specific port is the same as the BLER corresponding to another port (or to a level having a difference within a threshold range). FIG.13is a flowchart illustrating an operation method of an electronic device according to an embodiment of the disclosure. The embodiment ofFIG.13is described with reference toFIG.14. FIG.14illustrates a BLER and SRS transmission power of LTE communication, according to an embodiment of the disclosure. According to various embodiments, an electronic device101(e.g., at least one of the processor120, the first communication processor212, the second communication processor214, or the integrated communication processor260) may adjust and transmit transmission power in operation1301. For example, as in operation1107ofFIG.11, it is assumed that the condition of the SRS restriction operation is identified and the SRS transmission power is adjusted. In operation1303, the electronic device101may determine whether a reduction in the number of downlink layers configured in at least one specific CC in the LTE or NR network is identified. If no reduction in the number of layers is identified (No in1303), the electronic device101may transmit the first SRS with the adjusted SRS transmission power and the remaining SRSs (e.g., the SRSs corresponding to the remaining ports) with the set transmission power in operation1305. The SRS transmission power of the remaining SRSs may be determined, e.g., based on 3GPP TS 38.211 if it is not adjusted, or it may be in an adjusted state. According to various embodiments, if a reduction in the number of downlink layers configured in at least one specific CC in the LTE or NR network is identified (Yes in1303), the electronic device101may adjust and transmit the transmission power of at least some of the SRSs in operation1307. For example, referring toFIG.14, the electronic device101may transmit a 1-1st SRS1401corresponding to a first port with an SRS transmission power of c1, a 2-1st SRS1402corresponding to a second port with an SRS transmission power of c2, a 3-1st SRS1403corresponding to a third port with an SRS transmission power of c3, and a 4-1st SRS1404corresponding to a fourth port with an SRS transmission power of c1. For example, as the BLER of LTE communication corresponding to the third port is identified as greater than or equal to the threshold BLER so that the electronic device101adjusts the SRS transmission power corresponding to the third port, the SRS transmission power c3 of the 3-1st SRS1403may be set to be smaller than the remaining SRS transmission powers. When the imbalance between the SRS transmission powers is large, there is a possibility of allocating a lower layer to the electronic device101in the NR network. It is assumed that the electronic device101identifies a reduction in layer as compared with the previous time after transmitting the SRSs1401,1402,1403, and1404. Thus, the electronic device101may determine to adjust the SRS transmission power of the SRSs. In one example, the electronic device101may set the SRS transmission powers of the SRSs1411,1412,1413, and1414as the same value (e.g., c4), but this is exemplary, and at least some of the per-port SRS transmission powers may differ. C4 may be the same as, or different from, any one of c1, c2, or c3. For example, the SRS transmission power of the 3-2ndSRS1413may be increased, but this is also exemplary. For example, the electronic device101may set the difference between the SRS transmission powers of the SRSs1411,1412,1413, and1414to be within a threshold difference. In operation1309, the electronic device101may determine whether an increase in the downlink layers of the NR network is identified. For example, the electronic device101may identify the layer when the SRSs1411,1412,1413, and1414are transmitted. As the difference between the SRSs1411,1412,1413, and1414is not significant, the layer allocated to the electronic device101by the network may be increased. If there is no increase in layer (No in1309), the electronic device101may readjust the SRS transmission power of the SRSs. If there is an increase in layer (Yes in1309), the electronic device101may transmit the next SRSs with the adjusted transmission power in operation1311. FIG.15is a flowchart illustrating an operation method of an electronic device according to an embodiment of the disclosure. According to various embodiments, an electronic device101(e.g., at least one of the processor120, the first communication processor212, the second communication processor214, or the integrated communication processor260) may identify SCG addition in operation1501. The electronic device101may receive, e.g., an RRC reconfiguration message for configuring SCG addition from a network. The electronic device101may identify, e.g., the frequency band of NR communication from the RRC reconfiguration message in operation1502. Although not shown, the electronic device101may identify the frequency band of LTE communication (or all frequency bands of CA of LTE communication). In operation1503, the electronic device101may identify information for determining the SRS transmission power corresponding to the DC frequency combination. For example, Table 3 is an example of information for determining the SRS transmission power corresponding to the frequency combination. TABLE 3FrequencyAntennaAntennaAntennaAntennacombinationport 1port 2port 3port 4NR: n78LTE:18 dBm16 dBm17 dBm18 dBmB1/B3/B7NR: n78LTE:19 dBm19 dBm17 dBm18 dBmB1/B5/B7 The electronic device101may store the SRS transmission power for each antenna port and for each frequency combination as illustrated in Table 3, for example. The electronic device101may store the SRS transmission power, identified according to the embodiment ofFIG.11orFIG.13, corresponding to the frequency combination. The electronic device101may set the SRS transmission power as illustrated in Table 3, as the maximum power during the process of determining the SRS transmission power. In operation1505, the electronic device101may identify the SRS transmission power based on the identified information. Accordingly, the electronic device101may directly set the SRS transmission power without repeating the operations ofFIG.11orFIG.13. The electronic device101may set the SRS transmission power based on the stored information as illustrated in Table 3 and may then perform fine-tuning. Fine-tuning may be, e.g., the operations ofFIG.11orFIG.13. FIG.16is a flowchart illustrating an operation method of an electronic device according to an embodiment of the disclosure. According to various embodiments, an electronic device101(e.g., at least one of the processor120, the first communication processor212, the second communication processor214, or the integrated communication processor260) may transmit an SRS in operation1601. In operation1602, the electronic device101may identify a condition of an SRS restriction operation in a first port. For example, the electronic device101may identify that a condition (e.g., the BLER of LTE communication meets a designated condition and/or the ratio of the data throughput of LTE communication to the overall data throughput is a threshold ratio or more) of the SRS restriction operation associated with LTE communication is met while the SRS is transmitted through the first port. In operation1603, the electronic device101may transmit an SRS through a second port in a first slot corresponding to the first port. If the electronic device101supports 1T4R and is configured to transmit SRSs in the order of the first port, the second port, the third port, and the fourth port, the electronic device101may transmit SRSs in the order of the first port, the second port, the third port, and the fourth port. For example, the electronic device101may transmit the SRS through the port having the lowest BLER instead of the first port, but embodiments are not limited thereto. FIG.17is a flowchart illustrating an operation method of an electronic device according to an embodiment of the disclosure. According to various embodiments, an electronic device101(e.g., at least one of the processor120, the first communication processor212, the second communication processor214, or the integrated communication processor260) may transmit an SRS in operation1701. In operation1703, the electronic device101may identify a condition of an SRS restriction operation. For example, the electronic device101may identify that the BLER of LTE communication meets a designated condition and/or that the ratio of the data throughput of LTE communication to the overall data throughput is equal to or greater than a threshold ratio. In operation1705, the electronic device101may control the SRS transmission power as in the embodiment ofFIG.11or13and/or change the port as in the embodiment ofFIG.16. According to various embodiments, the electronic device101may determine whether a condition of an SRS restriction operation is identified in operation1707. If the condition of the SRS restriction operation is still identified (Yes in1707), the electronic device101may stop SRS transmission in operation1709. The electronic device101may stop SRS transmission if the condition of the restricted operation is still identified after performing the SRS restriction operation once. In another example, the electronic device101may be configured to stop SRS transmission if the condition of the restriction operation is still identified even after the SRS restriction operation is performed a designated number of times. Alternatively, the electronic device101may be configured to immediately stop SRS transmission in response to first identification of the condition of the SRS restriction operation. In one embodiment, the electronic device101may be configured to immediately stop SRS transmission when the BLER of LTE communication is significantly high. The stopping of SRS transmission may be the SRS restriction operation. For example, the electronic device101may set a plurality of thresholds for the BLER of LTE communication. A plurality of ranges may be set in the BLER by the plurality of thresholds. The electronic device101may selectively perform any one of adjustment of the SRS transmission power, changing of the port, and stopping of SRS transmission according to the range including the BLER of LTE communication measured. If the condition of the SRS restriction operation is still not identified (No in1707), the electronic device101may transmit the SRS in a changed state (e.g., a change in SRS transmission power and/or a change in port) in operation1711. According to various embodiments, when it is determined to stop SRS transmission, the electronic device101may report a UE capability indicating that SRS transmission is not supported to the network. For example, the electronic device101may report a UE capability indicating that SRS transmission is not supported based on a tracking area update (TAU) procedure. For example, the electronic device101may change the supportedSRS-TxPortSwitch from “t1r4” to “notsupported”. According to various embodiments, an electronic device comprises a plurality of antennas and at least one processor configured to support long-term evolution (LTE) communication and new radio (NR) communication. The at least one processor may be configured to identify at least one time of transmission of a sounding reference signal (SRS) set in the NR communication, transmitted through each of the plurality of antennas, identify at least one time of the LTE communication corresponding to the at least one time of transmission of the SRS, identify a block error rate (BLER) of the LTE communication in at least one frequency band associated with the LTE communication simultaneously in use with the NR communication, at the at least one time of the LTE communication, and based on the BLER satisfying a designated condition, perform an SRS restriction operation. According to various embodiments, the at least one processor may be configured to, as at least part of identifying the BLER of the LTE communication, identify the BLER in the at least one frequency band corresponding to a component carrier associated with carrier aggregation (CA) of the LTE communication. According to various embodiments, the at least one processor may be configured to, as at least part of based on the BLER satisfying a designated condition, performing the SRS restriction operation, based on identifying that the BLER is more than or equal to a designated threshold BLER, perform the SRS restriction operation. According to various embodiments, the at least one processor may be configured to, as at least part of based on the BLER satisfying the designated condition, performing the SRS restriction operation, identify a BLER for comparison at a time of reception other than a time of reception of the LTE communication corresponding to the at least one time of transmission of the SRS, and determine whether the BLER satisfies the designated condition based on a result of comparison between the BLER and the BLER for the comparison. According to various embodiments, the at least one processor may be configured to, as at least part of based on the BLER satisfying the designated condition, performing the SRS restriction operation, identify a first data throughput corresponding to the LTE communication based on the BLER meeting the designated condition, identify a second data throughput corresponding to the NR communication, based on the ratio of the first data throughput being more than or equal to a threshold ratio, identify a ratio of the first data throughput to a sum of the first data throughput and the second data throughput, and perform the SRS restriction operation. According to various embodiments, the at least one processor may be further configured to identify a first SRS transmission power of the SRS. The at least one processor may be configured to, as at least part of identifying the BLER, identify the BLER corresponding to each of the at least one frequency band associated with the LTE communication while the SRS is transmitted in the first SRS transmission power. According to various embodiments, the at least one processor may be configured to, as at least part of based on the BLER satisfying the designated condition, performing the SRS restriction operation, adjust the first SRS transmission power of the SRS to a second SRS transmission power. According to various embodiments, the at least one processor may be configured to, as at least part of adjusting the first SRS transmission power of the SRS to the second SRS transmission power, based on applying a predesignated amount of adjustment to the first SRS transmission power, identify the second SRS transmission power. According to various embodiments, the at least one processor may be configured to, upon transmitting the SRS in the second SRS transmission power, identify a reduction in a number of downlink layers of the NR communication set in the electronic device, and based on identifying the reduction in the number of the downlink layers, change the SRS transmission power from the second SRS transmission power to a third SRS transmission power. According to various embodiments, the at least one processor may be configured to, as at least part of adjusting the first SRS transmission power of the SRS to the second SRS transmission power, identify the second SRS transmission power pre-stored corresponding to a combination of at least one frequency corresponding to the LTE communication and at least one frequency corresponding to the NR communication. According to various embodiments, the adjusting of the first SRS transmission power of the SRS may be repeatedly performed until the designated condition is not satisfied. According to various embodiments, the at least one processor may be configured to, as at least part of based on the BLER satisfying the designated condition, performing the SRS restriction operation, identify that a BLER at a first time of reception of the LTE communication corresponding to a first time of transmission of the SRS corresponding to a first antenna among the plurality of antennas satisfies the designated condition, and transmit the SRS through an antenna, other than the first antenna, among the plurality of antennas at the first time of transmission of the SRS. According to various embodiments, the at least one processor may be configured to, as at least part of based on the BLER satisfying the designated condition, performing the SRS restriction operation based on the BLER meeting the designated condition, stop the transmission of the SRS. According to various embodiments, the at least one processor may be further configured to report a UE capability indicating that the electronic device does not support the SRS to a network based on the stopping of the transmission of the SRS. According to various embodiments, a method for operating an electronic device including a plurality of antennas supporting NR communication and LTE communication comprises: identifying at least one time of transmission of a sounding reference signal (SRS) set in the NR communication, transmitted through each of the plurality of antennas, identifying at least one time of the LTE communication corresponding to the at least one time of transmission of the SRS, identifying a block error rate (BLER) of the LTE communication in at least one frequency band associated with the LTE communication simultaneously in use with the NR communication, at the at least one time of the LTE communication, and based on the BLER satisfying a designated condition, performing an SRS restriction operation. According to various embodiments, based on the BLER satisfying the designated condition, performing the SRS restriction operation may comprise performing the SRS restriction operation based on identifying that the BLER is a designated threshold BLER or more. According to various embodiments, based on the BLER satisfying the designated condition, performing the SRS restriction operation may comprise: identifying a BLER for comparison at a time of reception other than a time of reception of the LTE communication corresponding to the at least one time of transmission of the SRS, and determining whether the BLER satisfies the designated condition based on a result of comparison between the BLER and the BLER for the comparison. According to various embodiments, based on the BLER meeting the designated condition, performing the SRS restriction operation may comprise: based on the BLER meeting the designated condition, identifying a first data throughput corresponding to the LTE communication, identifying a second data throughput corresponding to the NR communication, identifying a ratio of the first data throughput to a sum of the first data throughput and the second data throughput, and based on the ratio of the first data throughput being more than or equal to a threshold ratio, performing the SRS restriction operation. According to various embodiments, the method may further comprise identifying a first SRS transmission power of the SRS. Identifying the BLER may comprise identifying the BLER corresponding to each of the at least one frequency band associated with the LTE communication while the SRS is transmitted in the first SRS transmission power. According to various embodiments, based on the BLER meeting the designated condition, performing the SRS restriction operation may comprise adjusting the first SRS transmission power of the SRS to a second SRS transmission power. The electronic device according to various embodiments may be one of various types of electronic devices. The electronic devices may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. According to an embodiment of the disclosure, the electronic devices are not limited to those described above. It should be appreciated that various embodiments of the disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment. With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related elements. It is to be understood that a singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise. As used herein, each of such phrases as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C,” may include all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, such terms as “1st” and “2nd,” or “first” and “second” may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., wiredly), wirelessly, or via a third element. As used herein, the term “module” may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms, for example, “logic,” “logic block,” “part,” or “circuitry”. A module may be a single integral component, or a minimum unit or part thereof, adapted to perform one or more functions. For example, according to an embodiment, the module may be implemented in a form of an application-specific integrated circuit (ASIC). Various embodiments as set forth herein may be implemented as software (e.g., the program140) including one or more instructions that are stored in a storage medium (e.g., internal memory136or external memory138) that is readable by a machine (e.g., the electronic device101). For example, a processor (e.g., the processor120) of the machine (e.g., the electronic device101) may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. This allows the machine to be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include a code generated by a complier or a code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Wherein, the term “non-transitory” simply means that the storage medium is a tangible device, and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium. According to an embodiment, a method according to various embodiments of the disclosure may be included and provided in a computer program product. The computer program products may be traded as commodities between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store (e.g., Play Store™), or between two user devices (e.g., smart phones) directly. If distributed online, at least part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as memory of the manufacturer's server, a server of the application store, or a relay server. According to various embodiments, each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities. Some of the plurality of entities may be separately disposed in different components. According to various embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, according to various embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added. While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. | 106,851 |
11943718 | DETAILED DESCRIPTION It will be appreciated that for simplicity and clarity of illustration, where appropriate, reference numerals have been repeated among the different figures to indicate corresponding or analogous elements. Additionally, numerous specific details are set forth in order to provide a thorough understanding of the embodiments described herein. However, it will be understood by those of ordinary skill in the art that the embodiments described herein can be practiced without these specific details. In other instances, methods, procedures, and components have not been described in detail so as not to obscure the related relevant feature being described. The drawings are not necessarily to scale and the proportions of certain parts may be exaggerated to better illustrate details and features. The description is not to be considered as limiting the scope of the embodiments described herein. Several definitions that apply throughout this disclosure will now be presented. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The connection can be such that the objects are permanently connected or releasably connected. The term “comprising” means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in a so-described combination, group, series, and the like. A base station is a key infrastructure of communication network. In one application scenario of the base station, a terminal is moving at a high speed. To ensure a stable communication between the terminal and the base station, the base station conducts frequent power control checks, occupying a high resource cost of a control signaling and increasing a power consumption of the terminal. The present disclosure provides a method and system for power control, which increases bandwidth utilization by the base station, reduces the resource cost of the control signaling, and reduces power cost at the terminal. FIG.1illustrates a communication scenario between a base station and a terminal according to one embodiment of the present disclosure. As shown inFIG.1, a base station100establishes communication with a terminal200. A signal coverage of the base station100can be divided into N signal regions, N being a positive integer. For example, the signal coverage can be divided into three signal regions, which is a first region310, a second region320, and a third region330. Each region is a concentric circle or a concentric ellipse, for instance, as shown inFIG.1, each of the first region310, the second region320, and the third region330is an ellipse in shape. The manner of division into signal regions of the base station100is not limited in the present disclosure. In fact, the higher the value of N, the finer the power control will be. In one embodiment of the present disclosure, the terminal200makes a connection with the base station100. After the terminal200establishes communication with the base station100, the base station100establishes a transmission power conversion table and sends the transmission power conversion table to the terminal200. When the terminal200is displaced (i.e., moved), the terminal200may obtain a transmit power corresponding to the moving distance and the transmission power conversion table. The terminal200communicates with the base station100according to the obtained transmission power conversion table. The method for generating the transmit power map is described below with respect toFIG.2. As shown inFIG.2, after the terminal200connects to the base station100, the base station100controls transmission power with the terminal200in a closed loop way. The base station100obtains a transmit power of the terminal200, noted as Pref. Then, the base station100establishes a two-dimensional coordinate system (including an x axis and a y axis) with its own position as an origin. The base station100obtains a distance between the terminal200and the base station100, noted as S. The base station100calculates the per unit distance transmit power Pavgaccording to a formula (1). Pavg=PrefS(1) After obtaining the per unit distance transmit power Pavg, the base station100calculates a transmit power P of the terminal200in different regions according to the per unit distance transmit power Pavgand a formula (2). P=Pavg*S(2) S is the distance between the terminal200and the base station100. In order to simplify the transmission power conversion table, the base station100can calculate different transmission powers of different signal regions. For example, the base station100can divide the signal coverage into the first region310, the second region320, and the third region330, and calculate the distances S1, S2, and S3 between edge of each regions and the base station100. In one embodiment, the base station100can calculate transmit power P1, P2, and P3 of the terminal200in the respective first region310, the second region320, and the third region330to the formula (2). In some embodiments, when the base station100establishes the transmission power conversion table, the base station100calculates the distance S between the terminal200and the base station100according to global positioning system (GPS) or received signal strength indication (RSSI). For instance, in some embodiments, if the base station100is disposed outdoors and the terminal200includes a GPS chip, the distance between the terminal200and the base station100can be calculated by using GPS positioning. When calculating the distance using GPS positioning, the base station100transmits a Location Request message to the terminal200. The terminal200transmits a current GPS coordinate to the base station100. The base station100generates a transmission power conversion table according to the current GPS coordinate of the terminal200and the GPS coordinate of the base station100. The base station100transmits the transmission power conversion table to the terminal200. The transmission power conversion table further includes a GPS coordinate of the terminal200, so that the terminal200calculates a distance from the base station100when the terminal200is moved. In some embodiments, if the base station100is disposed indoors or in an area where the GPS signal cannot be received or the received GPS signal is weak, the distance between the terminal200and the base station100can be calculated using the RSSI. Specifically, when the base station100calculates the distance using the RSSI, the base station100transmits a location requirement message to the terminal200. The terminal200calculates the distance between the terminal200and the base station100based on the RSSI strength in a Beacon broadcast packet. When the distance S between the terminal200and the base station100is calculated using the RSSI, the following formula (3) is applied. S=10❘"\[LeftBracketingBar]"RSSI❘"\[RightBracketingBar]"-A)10*n(3) The parameter RSSI is a signal intensity of the terminal200received (Negative value). The parameter A is the signal intensity when the distance between the terminal200and the base station100is 1 meter. The parameter n is an environmental attenuation factor. The parameter RSSI needs to take the absolute value since the RSSI is a negative value, which converts the RSSI value to a positive value through absolute value calculation for subsequent calculations. The base station100generates the transmission power conversion table according to the distance transmitted by the terminal200and transmits the transmission power conversion table to the terminal200. In one embodiment, in order to reduce the amount of data of the transmission power conversion table of the base station100, the transmit power in the transmission power conversion table may be set to different steps according to different areas. For example, when the terminal200is in the first region310, the transmit power is set at P1. When the terminal200is in the second region320, the transmit power is P2. When the terminal200is in the third region330, the transmit power is P3. In one embodiment, after the base station100transmits the transmission power conversion table to the terminal200, the base station100sets an interval period T. The base station100does not generate the transmission power conversion table during the interval period T. Obviously, setting the interval period T reduces communication frequency between the base station100and the terminal200, reducing the signaling cost of the terminal200, and further reducing the power consumption of the terminal200. Within interval period T, the terminal200adjusts the transmit power according to the transmission power conversion table transmitted by the base station100and the distance between the terminal200and the base station100, so as to implement closed-loop power control at the terminal200. The base station100sets the interval period T by a timer. Specifically, referring toFIG.3, when the terminal200is displaced within the interval period T, the terminal200adjusts the transmit power according to the located area and the transmission power conversion table without performing frequent closed-loop power control. For example, when the terminal200moves from point A to point B, the terminal200checks the transmission power conversion table to establish that the terminal200moves from the third area330to the second area320. The terminal200adjusts the transmit power of the terminal200from the transmit power P3 at point A to the transmit power P2 in the second area according to the power value corresponding to the transmission power conversion table. As another example, when the terminal200detects that the position moves from the second area320to the first area310through the transmission power conversion table, the transmit power of the terminal200is adjusted from P2 to P1. When the terminal200moves, if the position of the terminal200is at a boundary of the two areas, the higher transmission power of two possible powers corresponding to the two areas is selected, so as to avoid communication quality being affected by insufficient transmission power of the terminal200at the boundary of the areas. After the interval period T, the base station100re-obtains the transmit power of the terminal200to establish a new transmission power conversion table. The method of establishing a new transmission power conversion table can be referred to in conjunction withFIG.2and is not described herein again. If the distance between the terminal200and the base station100is calculated through RSSI, the base station100needs to send the Beacon broadcast packet in timely manner. FIG.4illustrates a flowchart of an embodiment of the method for controlling power. The embodiment is provided by way of example, as there are a variety of ways to carry out the method. The method includes obtaining a transmit power of the terminal; obtaining a location information of the terminal; generating a transmission power conversion table; transmitting the transmission power conversion table to the terminal; adjusting the transmission power according to the transmission power conversion table; and renewing the transmission power conversion table after an interval period. The method described below can be carried out using the configurations illustrated inFIGS.1,2, and3, for example, and various elements of these figures are referenced in explaining the embodiment. Each block shown inFIG.4represents one or more processes, methods, or subroutines carried out in the embodiment. Furthermore, the illustrated order of blocks is by example only, and the order of the blocks can be changed. Additional blocks can be added or fewer blocks can be utilized, without departing from this disclosure. This method can begin at block S100. At block S100, the base station100obtains the transmit power of the terminal200. The base station100transmits Downlink Control Information (DCI) to the terminal200through Physical Downlink Control Channel (PDCCH) to obtain Sounding Reference Signal (SRS). The terminal200sends the SRS to the base station100. The base station100generates control instruction according to the SRS testing result. The base station100transmits the SRS testing result to the terminal200through Total Power Control (TPC) message. The terminal200calculates the transmit power according to the TPC message. The terminal200transmits Uplink Control Information (UCI) to the base station100through Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH). The base station100obtains the transmit power of the terminal200through UCI information which is received. At block S200, the base station100obtains location information of the terminal200. Specifically, the base station100sends location request to the terminal200, and the terminal200transmits location information to the base station100. At block S300, the base station100generates the transmission power conversion table according to the location information of the terminal200. The location information of the terminal200includes the GPS coordinate or RSSI information. The base station100generates the transmission power conversion table according to the GPS coordinate or RSSI information and the transmission power of the terminal200. SeeFIG.2for the method of generating the transmission power conversion table. At block S400, the base station100transmits the transmission power conversion table to the terminal200. Specifically, the base station100transmits downlink control information to the terminal200through Physical Downlink Shared Channel. The downlink control information includes the transmission power conversion table. At block S500, the terminal200adjusts the transmit power according to the transmission power conversion table. The method of adjusting the transmit power according to the transmission power conversion table can be referred to in conjunction withFIG.2and is not described herein again. At block S600, the base station100moves back to block S100to renew the transmission power conversion table after the interval period. The method of renewing the transmission power conversion table can be referred to in conjunction withFIG.2and is not described herein again. FIG.5illustrates interaction between the terminal200and the base station100in one embodiment of the power control method. Blocks S100, S200, S300, S400, S500, and S600are same as blocks S100, S200, S300, S400, S500, and S600inFIG.4, which can be referred to in conjunction withFIG.4and is not described herein again. The block S200further includes the following steps. At block S210and block S220, the base station100transmits the downlink control information to the terminal200through Physical Downlink Shared Channel. The downlink control information includes the transmission power conversion table. After receiving the location request, the terminal200sends an uplink control information message to the base station100through a physical uplink control channel or a physical uplink shared channel, where the uplink control information message carries location information of the terminal200. Referring toFIG.6, the present embodiment further provides a power control system300. The power control system300includes a base station301and a terminal302. The base station301can be the base station100described above, and is configured to perform the steps S100, S210, S300, S400and S600. Specifically, refer toFIG.4toFIG.5. The terminal302may be the terminal200described above, and is configured to execute the step S220and the step S500, which may specifically refer toFIG.4toFIG.5and the related description thereof, and will not be described herein again. The base station301in the above embodiment can also be implemented as an aggregate (group of several devices). Each device constituting the device group may include a part or all of the functions or functional blocks of the base station301according to the above embodiment. The device group may have all the functions or functional blocks of the base station301. Further, the terminal302according to the above embodiment can also communicate with the base station301as part of an aggregation. In the power control method and the power control system300provided in the embodiment of the present application, the base station301may calculate the transmission power comparison table, the terminal302is not required to calculate the transmission power comparison table, thereby reducing the power consumption and the response time of the terminal302. The base station301and the terminal302only perform calculation by reference to the transmission power comparison table once within an interval period T, thereby reducing the signaling overhead and improving the utilization rate of the data bandwidth. Each calculation of the transmission power comparison table is closed-loop control, and the terminal302is required to repeatedly transmit a detection signal, which has higher power consumption, whereas the power control method provided by the embodiment of the present application performs a calculation only once in each interval period, which reduces the power consumption of the terminal302. It can be understood that the power control method and the power control system300provided in the embodiment of the present application may be based on the existing communication architecture and device, the hardware level does not need to be modified, thereby reducing the deployment difficulty. For example, the power control method and the power control system provided in the embodiment of the present application may be deployed in an industrial interne and may be implemented only by installing an algorithm and a flow logic program in the base station301. Even though numerous characteristics and advantages of the present technology have been set forth in the foregoing description, together with details of the structure and function of the present disclosure, the disclosure is illustrative only, and changes may be made in the detail, especially in matters of shape, size, and arrangement of the parts within the principles of the present disclosure, up to and including the full extent established by the broad general meaning of the terms used in the claims. It will therefore be appreciated that the exemplary embodiments described above may be modified within the scope of the claims. | 18,488 |
11943719 | DETAILED DESCRIPTION FIGS.1through9, discussed below, and the various embodiments used to describe the principles of the present disclosure in this disclosure are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged wireless communication system. Depending on the network type, the term ‘network node’ or ‘base station’ can refer to any component, or collection of components, configured to provide wireless access to a network, such as a transmit point (TP), a TRP, a gNB, a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations can provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G 3GPP New Radio Interface/Access (NR), long term evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a/b/g/n/ac, etc. The terms ‘gNB’ and ‘network node’ can be used interchangeably in this disclosure to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term UE can refer to any component such as mobile station, subscriber station, remote terminal, wireless terminal, receive point, or user device. A UE can be a mobile device or a stationary device. To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post LTE System’. A 5G communication system can be implemented in higher frequency (mmWave) bands, such as 28 GHz or 60 GHz bands or, in general, above 6 GHz bands, so as to accomplish higher data rates, or in lower frequency bands, such as below 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are considered in 5G communication systems. In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud Radio Access Networks (RANs), ultra-dense networks, device-to-device (D2D) communication on sidelink, wireless backhaul, moving network, cooperative communication, Coordinated Multi-Point (CoMP) transmissions/receptions such as from multiple TRPs, reception-end interference cancellation and the like. The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the present disclosure can be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or the frequency bands associated therewith, and embodiments of the present disclosure can be utilized in connection with any frequency band. FIG.1illustrates an example wireless network100according to various embodiments of the present disclosure. The embodiment of the wireless network100shown inFIG.1is for illustration only. Other embodiments of the wireless network100can be used without departing from the scope of the present disclosure. The wireless network100includes a BS101, a BS102, and a BS103. The BS101communicates with the BS102and the BS103. The BS101also communicates with at least one Internet Protocol (IP) network130, such as the Internet, a proprietary IP network, or other data network. The gNB102provides wireless broadband access to the network130for a first plurality of UEs within a coverage area120of the gNB102. The first plurality of UEs includes a UE111, which can be located in a small business; a UE112, which can be located in an enterprise (E); a UE113, which can be located in a WiFi hotspot (HS); a UE114, which can be located in a first residence (R); a UE115, which can be located in a second residence (R); and a UE116, which can be a mobile device (M) like a cell phone, a wireless laptop, a wireless PDA, or the like. The gNB103provides wireless broadband access to the network130for a second plurality of UEs within a coverage area125of the gNB103. The second plurality of UEs includes the UE115and the UE116. In some embodiments, one or more of the gNBs101-103can communicate with each other and with the UEs111-116using 5G, LTE, LTE-A, WiMAX, or other advanced wireless communication techniques. Dotted lines show the approximate extents of the coverage areas120and125, which are shown as approximately circular for the purposes of illustration and explanation only. For example, the coverage areas associated with gNBs, such as the coverage areas120and125, can have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions. AlthoughFIG.1illustrates one example of a wireless network100, various changes can be made toFIG.1. For example, the wireless network100can include any number of gNBs and any number of UEs in any suitable arrangement. The gNB101can communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network130. Similarly, each gNB102-103can communicate directly with the network130and provide UEs with direct wireless broadband access to the network130. Further, the gNB101,102, and/or103can provide access to other or additional external networks, such as other types of data networks. FIG.2illustrates an example gNB102according to embodiments of the present disclosure. The embodiment of the gNB102illustrated inFIG.2is for illustration only, and the gNBs101and103ofFIG.1could have the same or similar configuration. However, gNBs come in a wide variety of configurations, andFIG.2does not limit the scope of the present disclosure to any particular implementation of a gNB. As shown inFIG.2, the gNB102includes multiple antennas205a-205n, multiple RF transceivers210a-210n, transmit (TX) processing circuitry215, and receive (RX) processing circuitry220. The gNB102also includes a controller/processor225, a memory230, and a backhaul or network interface235. The RF transceivers210a-210nreceive, from the antennas205a-205n, incoming RF signals, such as signals transmitted by UEs in the network100. The RF transceivers210a-210ndown-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to the RX processing circuitry220, which generates processed baseband signals by filtering, decoding, and/or digitizing the baseband or IF signals. The RX processing circuitry220transmits the processed baseband signals to the controller/processor225for further processing. The TX processing circuitry215receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller/processor225. The TX processing circuitry215encodes, multiplexes, and/or digitizes the outgoing baseband data to generate processed baseband or IF signals. The RF transceivers210a-210nreceive the outgoing processed baseband or IF signals from the TX processing circuitry215and up-converts the baseband or IF signals to RF signals that are transmitted via the antennas205a-205n. The controller/processor225can include one or more processors or other processing devices that control the overall operation of the gNB102. For example, the controller/processor225could control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers210a-210n, the RX processing circuitry220, and the TX processing circuitry215in accordance with well-known principles. The controller/processor225could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller/processor225transmit downlink control channels for communication with multiple TRPs. Any of a wide variety of other functions could be supported in the gNB102by the controller/processor225. The controller/processor225is also capable of executing programs and other processes resident in the memory230, such as an OS. The controller/processor225can move data into or out of the memory230as required by an executing process. The controller/processor225is also coupled to the backhaul or network interface235. The backhaul or network interface235allows the gNB102to communicate with other devices or systems over a backhaul connection or over a network. The interface235could support communications over any suitable wired or wireless connection(s). For example, when the gNB102is implemented as part of a cellular communication system (such as one supporting 5G, LTE, or LTE-A), the interface235could allow the gNB102to communicate with other gNBs over a wired or wireless backhaul connection. When the gNB102is implemented as an access point, the interface235could allow the gNB102to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface235includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver. The memory230is coupled to the controller/processor225. Part of the memory230could include a RAM, and another part of the memory230could include a Flash memory or other ROM. AlthoughFIG.2illustrates one example of the gNB102, various changes may be made toFIG.2. For example, the gNB102could include any number of each component shown inFIG.2. As a particular example, an access point could include a number of interfaces235, and the controller/processor225could support routing functions to route data between different network addresses. As another particular example, while shown as including a single instance of TX processing circuitry215and a single instance of RX processing circuitry220, the gNB102could include multiple instances of each (such as one per RF transceiver). Also, various components inFIG.2could be combined, further subdivided, or omitted and additional components could be added according to particular needs. FIG.3illustrates an example UE116according to embodiments of the present disclosure. The embodiment of the UE116illustrated inFIG.3is for illustration only, and the UEs111-115ofFIG.1could have the same or similar configuration. However, UEs come in a wide variety of configurations, andFIG.3does not limit the scope of the present disclosure to any particular implementation of a UE. As shown inFIG.3, the UE116includes an antenna305, a radio frequency (RF) transceiver310, TX processing circuitry315, a microphone320, and receive (RX) processing circuitry325. The UE116also includes a speaker330, a processor340, an input/output (I/O) interface (IF)345, a touchscreen350, a display355, and a memory360. The memory360includes an operating system (OS)361and one or more applications362. The RF transceiver310receives, from the antenna305, an incoming RF signal transmitted by a gNB of the network100. The RF transceiver310down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuitry325, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry325transmits the processed baseband signal to the speaker330(such as for voice data) or to the processor340for further processing (such as for web browsing data). The TX processing circuitry315receives analog or digital voice data from the microphone320or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor340. The TX processing circuitry315encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver310receives the outgoing processed baseband or IF signal from the TX processing circuitry315and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna305. The processor340can include one or more processors or other processing devices and execute the OS361stored in the memory360in order to control the overall operation of the UE116. For example, the processor340could control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver310, the RX processing circuitry325, and the TX processing circuitry315in accordance with well-known principles. In some embodiments, the processor340includes at least one microprocessor or microcontroller. The processor340is also capable of executing other processes and programs resident in the memory360, such as processes for transmitting to or receiving from a master node and a secondary node. The processor340can move data into or out of the memory360as required by an executing process. In some embodiments, the processor340is configured to execute the applications362based on the OS361or in response to signals received from gNBs or an operator. The processor340is also coupled to the I/O interface345, which provides the UE116with the ability to connect to other devices, such as laptop computers and handheld computers. The I/O interface345is the communication path between these accessories and the processor340. The processor340is also coupled to the touchscreen350and the display355. The operator of the UE116can use the touchscreen350to enter data into the UE116. The display355may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from web sites. The memory360is coupled to the processor340. Part of the memory360could include a random-access memory (RAM), and another part of the memory360could include a Flash memory or other read-only memory (ROM). AlthoughFIG.3illustrates one example of the UE116, various changes may be made toFIG.3. For example, various components inFIG.3could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor340could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, whileFIG.3illustrates the UE116configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices. FIG.4Ais a high-level diagram of transmit path circuitry400. For example, the transmit path circuitry400may be used for an orthogonal frequency division multiple access (OFDMA) communication.FIG.4Bis a high-level diagram of receive path circuitry450. For example, the receive path circuitry450may be used for an orthogonal frequency division multiple access (OFDMA) communication. InFIGS.4A and4B, for downlink communication, the transmit path circuitry400may be implemented in a base station (gNB)102or a relay station, and the receive path circuitry450may be implemented in a user equipment (e.g. user equipment116ofFIG.1). In other examples, for uplink communication, the receive path circuitry450may be implemented in a base station (e.g. gNB102ofFIG.1) or a relay station, and the transmit path circuitry400may be implemented in a user equipment (e.g. user equipment116ofFIG.1). Transmit path circuitry400comprises channel coding and modulation block405, serial-to-parallel (S-to-P) block410, Size N Inverse Fast Fourier Transform (IFFT) block415, parallel-to-serial (P-to-S) block420, add cyclic prefix block425, and up-converter (UC)430. Receive path circuitry450comprises down-converter (DC)455, remove cyclic prefix block460, serial-to-parallel (S-to-P) block465, Size N Fast Fourier Transform (FFT) block470, parallel-to-serial (P-to-S) block475, and channel decoding and demodulation block480. At least some of the components inFIGS.4A and4Bmay be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. In particular, it is noted that the FFT blocks and the IFFT blocks described in this disclosure document may be implemented as configurable software algorithms, where the value of Size N may be modified according to the implementation. Furthermore, although this disclosure is directed to an embodiment that implements the Fast Fourier Transform and the Inverse Fast Fourier Transform, this is by way of illustration only and should not be construed to limit the scope of the disclosure. It may be appreciated that in an alternate embodiment of the disclosure, the Fast Fourier Transform functions and the Inverse Fast Fourier Transform functions may easily be replaced by discrete Fourier transform (DFT) functions and inverse discrete Fourier transform (IDFT) functions, respectively. It may be appreciated that for DFT and IDFT functions, the value of the N variable may be any integer number (i.e., 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of the N variable may be any integer number that is a power of two (i.e., 1, 2, 4, 8, 16, etc.). In transmit path circuitry400, channel coding and modulation block405receives a set of information bits, applies coding (e.g., LDPC coding) and modulates (e.g., quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) the input bits to produce a sequence of frequency-domain modulation symbols. Serial-to-parallel block410converts (i.e., de-multiplexes) the serial modulated symbols to parallel data to produce N parallel symbol streams where N is the IFFT/FFT size used in BS102and UE116. Size N IFFT block415then performs an IFFT operation on the N parallel symbol streams to produce time-domain output signals. Parallel-to-serial block420converts (i.e., multiplexes) the parallel time-domain output symbols from Size N IFFT block415to produce a serial time-domain signal. Add cyclic prefix block425then inserts a cyclic prefix to the time-domain signal. Finally, up-converter430modulates (i.e., up-converts) the output of add cyclic prefix block425to RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency. The transmitted RF signal arrives at UE116after passing through the wireless channel, and reverse operations to those at gNB102are performed. Down-converter455down-converts the received signal to baseband frequency, and remove cyclic prefix block460removes the cyclic prefix to produce the serial time-domain baseband signal. Serial-to-parallel block465converts the time-domain baseband signal to parallel time-domain signals. Size N FFT block470then performs an FFT algorithm to produce N parallel frequency-domain signals. Parallel-to-serial block475converts the parallel frequency-domain signals to a sequence of modulated data symbols. Channel decoding and demodulation block480demodulates and then decodes the modulated symbols to recover the original input data stream. Each of gNBs101-103may implement a transmit path that is analogous to transmitting in the downlink to user equipment111-116and may implement a receive path that is analogous to receiving in the uplink from user equipment111-116. Similarly, each one of user equipment111-116may implement a transmit path corresponding to the architecture for transmitting in the uplink to gNBs101-103and may implement a receive path corresponding to the architecture for receiving in the downlink from gNBs101-103. A time unit for DL signaling or for UL signaling on a cell is one symbol. A symbol belongs to a slot that includes a number of symbols, such as 14 symbols, and is referred to as DL symbol if used for DL signaling, UL symbol if used for UL signaling, or flexible symbol if it can be used for either DL signaling or UL signaling. The slot can also be a time unit for DL or UL signaling on a cell. A bandwidth (BW) unit is referred to as a resource block (RB). One RB includes a number of sub-carriers (SCs), such as 12 subcarriers. An RB in one symbol of a slot is referred to as physical RB (PRB) and includes a number of resource elements (REs). For example, a slot can have a duration of 1 millisecond and an RB can have a BW of 180 kHz and include 12 SCs with SC spacing of 15 kHz. As another example, a slot can have a duration of 0.25 milliseconds and an RB can have a BW of 720 kHz and include 12 SCs with SC spacing of 60 kHz. DL signals include data signals conveying information content, control signals conveying DL control information (DCI), and reference signals (RS) that are also known as pilot signals. A gNB transmits data information or DCI through respective physical DL shared channels (PDSCHs) or physical DL control channels (PDCCHs). A PDSCH or a PDCCH transmission can be over a variable number of slot symbols including one slot symbol. A gNB transmits one or more of multiple types of RS including channel state information RS (CSI-RS) and demodulation RS (DM-RS). A CSI-RS is primarily intended for UEs to perform measurements and provide channel state information (CSI) to a gNB. For channel measurement, non-zero power CSI-RS (NZP CSI-RS) resources are used. For interference measurement reports (IMRs), CSI interference measurement (CSI-IM) resources associated with a zero power CSI-RS (ZP CSI-RS) configuration are used. A CSI process consists of NZP CSI-RS and CSI-IM resources. A UE can determine CSI-RS transmission parameters through DL control signaling or higher layer signaling, such as radio resource control (RRC) signaling from a gNB. Transmission instances of a CSI-RS can be indicated by DL control signaling or configured by higher layer signaling. A DM-RS is typically transmitted only in the BW of a respective PDCCH or PDSCH and a UE can use the DM-RS to demodulate data or control information. UL signals also include data signals conveying information content, control signals conveying UL control information (UCI), DM-RS associated with data or UCI demodulation, sounding RS (SRS) enabling a gNB to perform UL channel measurement, and a random access (RA) preamble enabling a UE to perform random access. A UE transmits data information or UCI through a respective physical UL shared channel (PUSCH) or a physical UL control channel (PUCCH). A PUSCH or a PUCCH can be transmitted over a variable number of slot symbols including one slot symbol. When a UE simultaneously transmits data information and UCI, the UE can multiplex both in a PUSCH. UCI includes hybrid automatic repeat request acknowledgement (HARQ-ACK) information, indicating correct or incorrect detection of data transport blocks (TB s) in a PDSCH, scheduling request (SR) indicating whether a UE has data in its buffer, and CSI reports enabling a gNB to select appropriate parameters for PDSCH or PDCCH transmissions to a UE. HARQ-ACK information can be configured to be with a smaller granularity than per TB and can be per data code block (CB) or per group of data CBs where a data TB includes a number of data CBs. A CSI report from a UE can include a channel quality indicator (CQI) informing a gNB of a largest modulation and coding scheme (MCS) for the UE to detect a data TB with a predetermined block error rate (BLER), such as a 10% BLER, of a precoding matrix indicator (PMI) informing a gNB how to combine signals from multiple transmitter antennas in accordance with a multiple input multiple output (MIMO) transmission principle, and of a rank indicator (RI) indicating a transmission rank for a PDSCH. UL RS includes DMRS and SRS. DMRS is transmitted only in a BW of a respective PUSCH or PUCCH transmission. A gNB can use a DMRS to demodulate information in a respective PUSCH or PUCCH. SRS is transmitted by a UE to provide a gNB with an UL CSI and, for a TDD system, an SRS transmission can also provide a PMI for DL transmission. Additionally, in order to establish synchronization or an initial higher layer connection with a gNB, a UE can transmit a physical random access channel (PRACH). FIG.5illustrates an example transmitter structure500using OFDM according to embodiments of the present disclosure. An embodiment of the transmitter structure500shown inFIG.5is for illustration only. One or more of the components illustrated inFIG.5can be implemented in specialized circuitry configured to perform the noted functions or one or more of the components can be implemented by one or more processors executing instructions to perform the noted functions. Other embodiments are used without departing from the scope of the present disclosure. Information bits, such as DCI bits or data bits510, are encoded by encoder520, rate matched to assigned time/frequency resources by rate matcher530, and modulated by modulator540. Subsequently, modulated encoded symbols and DMRS or CSI-RS550are mapped to SCs560by SC mapping unit575, an inverse fast Fourier transform (IFFT) is performed by filter570, a cyclic prefix (CP) is added by CP insertion unit580, and a resulting signal is filtered by filter590and transmitted by a radio frequency (RF) unit595. FIG.6illustrates an example receiver structure600using OFDM according to embodiments of the present disclosure. An embodiment of the receiver structure600shown inFIG.6is for illustration only. One or more of the components illustrated inFIG.6can be implemented in specialized circuitry configured to perform the noted functions or one or more of the components can be implemented by one or more processors executing instructions to perform the noted functions. Other embodiments are used without departing from the scope of the present disclosure. A received signal610is filtered by filter620, a CP removal unit removes a CP630, a filter640applies a fast Fourier transform (FFT), SCs de-mapping unit650de-maps SCs selected by BW selector unit675, received symbols are demodulated by a channel estimator and a demodulator unit660, a rate de-matcher670restores a rate matching, and a decoder680decodes the resulting bits to provide information bits690. A UE can be configured to operate with carrier aggregation (CA) or dual connectivity (DC). For operation with CA or with DC, the UE can be configured with a first group of cells comprising a master cell group (MCG) and with a second group of cells comprising a secondary cell group (SCG). For operation with DC, the UE can be configured a first and second maximum powers for transmissions to the MCG and the SCG, respectively. A maximum UE transmission power for operation with a MCG and a SCG can be semi-statically partitioned, by higher layer signaling, between the master node (MN) of the MCG and the secondary node (SN) of the SCG, or dynamic power sharing can be possible under certain conditions where transmissions on the SCG can use leftover power from transmissions on the MCG, and the reverse, subject to a total transmission power not exceeding the maximum UE transmission power for operation with the MCG and the SCG. The terms MCG and MN and the terms SCG and SN are used interchangeably in this disclosure. A power control mechanism can depend on whether transmissions on different cells have a same duration and on whether transmissions on different cells are synchronized with respect to a slot boundary. Moreover, for LTE and NR coexistence at a UE, where LTE provides the MCG and NR provides the SCG. A fixed partitioning of a maximum UE transmission power between the MCG and the SCG is suboptimal as it reduces a maximum UE transmission power per CG below the maximum UE transmission power. Such partitioning results to reduced coverage since, for example, the UE has less available power to transmit on the MCG, and to reduced spectral efficiency. A dynamic power sharing (DPS) mechanism enabling the UE to use available power for transmissions on either the MCG or the SCG depending on actual transmissions at a given time circumvents the shortcomings of a fixed partitioning of the maximum UE transmission power between the MCG and the SCG but introduces new challenges to the UE for determining the available power at a given time since this requires the UE to know the actual transmissions and their contents at that time. Power allocation to transmissions on the MCG can be prioritized and then the problem reduces to determining an available power that the UE can use for transmissions on the SCG at a given time, after allocating power for transmissions on the MCG. In order to determine a transmission power at a given time, the transmitted channels/signals and their contents need to be determined. Also, if a UE would have time overlapping transmissions on a cell (or a bandwidth part of a cell) at a given time, the UE may need to resolve such overlapping by multiplexing the information contents in one channel and transmitting only that one channel. For example, if a UE would transmit on a cell a PUCCH and a PUSCH that would overlap in time, the UE can multiplex the UCI of the PUCCH in the PUSCH and transmit only the PUSCH. For example, if a UE would transmit on a cell a first PUCCH and a second PUCCH that would overlap in time, the UE can multiplex all UCI in a one PUCCH and transmit the one PUCCH. Such resolutions of time overlapped transmissions on a same cell require a certain processing time that is determined by a processing time of respective PDCCH receptions, in case the transmissions are scheduled by DCI formats, and a preparation time for a transmission after resolving an overlapping of the transmissions. If a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH(s) and PUSCH(s) in a slot and the UE is configured to multiplex different UCI types in one PUCCH, and at least one of the multiple overlapping PUCCHs or PUSCHs is in response to a DCI format detection by the UE, the UE multiplexes all corresponding UCI types if the following conditions are met. If one of the PUCCH transmissions or PUSCH transmissions is in response to a DCI format detection by the UE, the UE expects that the first symbol S0of the earliest PUCCH or PUSCH, among a group overlapping PUCCHs and PUSCHs in the slot, satisfies the following timeline conditions:S0is not before a symbol with cyclic prefix (CP) starting after Tproc,11after a last symbol of any corresponding PDSCH, Tproc,1muxgiven by maximum of {Tproc,1mux,1, . . . , Tproc,1mux,i. . . } are for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, Tproc,1mux=(N1+d1,1+1)·(2048+144)·κ·2−μ·TC, d1,1is selected for the i-th PDSCH following, N1is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest subcarrier spacing (SCS) configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH (if any), the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.S0is not before a symbol with CP starting after Tproc,releasemuxafter a last symbol of any corresponding semi-persistently scheduled (SPS) PDSCH release. Tproc,releasemuxis given by maximum of {Tproc,releasemux,1, . . . , Tproc,releasemux,i, . . . } where for the i-th PDCCH providing the SPS PDSCH release with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, Tproc,releasemux,i=(N+1)·(2048+144)·κ·2−μ·TC, N is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH providing the i-th SPS PDSCH release, the PUCCH with corresponding HARQ-ACK transmission for i-th SPS PDSCH release, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.if there is no aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs, S0is not before a symbol with CP starting after Tproc,2muxafter a last symbol ofany PDCCH with the DCI format scheduling an overlapping PUSCH, andany PDCCH scheduling a PDSCH or SPS PDSCH release with corresponding HARQ-ACK information in an overlapping PUCCH in the slot If there is at least one PUSCH in the group of overlapping PUCCHs and PUSCHs, Tproc,2muxis given by maximum of {Tproc,2mux,1, . . . , Tproc,2mux,i. . . } where for the i-th PUSCH which is in the group of overlapping PUCCHs and PUSCHs, Tproc,2mux,i=max((N2+d2,1+1)·(2048+144)·κ·2−μ·TC, d2,2), d2,1and d2,2are selected for the i-th PUSCH, N2is selected based on the UE PUSCH processing capability of the i-th PUSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PUSCH (if any), the PDCCHs scheduling the PDSCHs with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs/PUSCHs, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. If there is no PUSCH in the group of overlapping PUCCHs and PUSCHs, Tproc,2muxis given by maximum of {Tproc,2mux,1, . . . , Tproc,2mux,i. . . } where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs, Tproc,2mux,i=(N2+1)·(2048+144)·κ·2−μ·TC, N2is selected based on the UE PUSCH processing capability of the PUCCH serving cell if configured. N2is selected based on the UE PUSCH processing capability 1, if PUSCH processing capability is not configured for the PUCCH serving cell. μ is selected based on the smallest SCS configuration between the SCS configuration used for the PDCCH scheduling the i-th PDSCH (if any) with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs, and the SCS configuration for the PUCCH serving cell.if there is an aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs, S0is not before a symbol with CP starting after Tproc,CSImux=max ((Z+d)·(2048+144)·κ·2−μ·TC, d2,2) after a last symbol ofany PDCCH with the DCI format scheduling an overlapping PUSCH, andany PDCCH scheduling a PDSCH or SPS PDSCH release with corresponding HARQ-ACK information in an overlapping PUCCH in the slotwhere μ corresponds to the smallest SCS configuration among the SCS configuration of the PDCCHs, the smallest SCS configuration for the group of the overlapping PUSCHs, and the smallest SCS configuration of CSI-RS associated with the DCI format scheduling the PUSCH with the multiplexed aperiodic CSI report, and d=2 for μ=0,1, d=3 for μ=2 and d=4 for μ=3N1, N2, d1,1, d2,1, d2,2, and Z are defined in TS 38.214 v16.0.0, and κ and TCare defined in TS 38.211 V16.0.0. TABLE 1PUSCH preparation time for PUSCHtiming/processing capability 1PUSCH preparationμtime N2[symbols]010112223336 TABLE 2PUSCH preparation time for PUSCHtiming/processing capability 2PUSCH preparationμtime N2[symbols]0515.5211 for frequency range 1 If a UEis configured for DPS between MCG and SCG, for example, by setting a value of a higher layer parameter NR-DC-PC-mode to Dynamic, andindicates a capability to determine a total transmission power on the SCG at a first symbol of a transmission occasion on the SCG by determining transmissions on the MCG thatare scheduled by DCI formats in PDCCH receptions with a last symbol that is earlier by more than Toffsetfrom the first symbol of the transmission occasion on the SCG, andoverlap with the transmission occasion on the SCG the UE determines a maximum transmission power on the SCG at the beginning of the transmission occasion on the SCG asmin({circumflex over (P)}SCG, {circumflex over (P)}TotalNR-DC−{circumflex over (P)}MCGactual), if the UE determines transmissions on the MCG with a {circumflex over (P)}MCGactualtotal power (in the linear domain){circumflex over (P)}TotalNR-DC, if the UE does not determine any transmissions on the MCG where {circumflex over (P)}SCGis a linear value of a maximum transmission power on the SCG and {circumflex over (P)}TotalNR-DCis a linear value of a of a configured maximum transmission power for NR-DC operation in a same frequency range. A UE does not expect to have transmissions on the MCG thatare scheduled by DCI formats in PDCCH receptions with a last symbol that is earlier by less than or equal to Toffsetfrom the first symbol of the transmission occasion on the SCG, andoverlap with the transmission occasion on the SCG In order to maximize the gains from DPS when a UE indicates the aforementioned capability to determine a transmission power on the SCG, the value of Toffsetis of material importance as a value that is too small cannot satisfy UE processing requirements while a value that is too large diminishes the gains from DPS operation in dual connectivity. The UE processing requirements depend on a UE PUSCH processing capability and on a SCS configuration. As the UE prioritizes power allocation on the MCG and determines an available power on the SCG after power is allocated on the MCG, at a given time the UE needs to know the transmissions and their contents on the MCG in order to determine a corresponding total transmission power on the MCG and this needs to be prior to a time the UE needs to transmit on the SCG. Therefore, Toffsetneeds to depend on the UE PUSCH processing capability for PUSCH preparation on both the MCG and the SCG and on corresponding SCS configurations. In a first embodiment, once a UE knows the information content and the channels/signals to transmit at a given time, determination of transmission power can be on a symbol basis. Consequently, Toffsetcan be based on a time the UE requires to determine the information contents and channels/signals at a given time in the future on the MCG/SCG. The larger the Toffset, the easier the UE implementation but the smaller the gains from DPS. Therefore, Toffsetshould not be unnecessarily larger than a time a UE requires to determine a transmission power after preparing the contents of a transmission. Similar to determining required UE processing times for resolving overlapping, there could be multiple Toffsetvalues depending on the channels a UE transmits on the MCG/SCG. A single Toffsetvalue can offer simplicity without materially penalizing performance gains from DPS in dual connectivity. For example, the largest processing time (across all cells of the MCG and the SCG), Tproc,CSImux, for resolving overlapping can be used. For example, depending on a DPS capability that a UE indicates to the network, the processing time for the UE can be assumed to be the maximum Tproc,2mux, instead of the maximum Tproc,CSImux, across all cells of the MCG and the SCG, as in case there is PUCCH and PUSCH overlapping. Using Tproc,2muxinstead of Tproc,CSImuxfor Toffsetcan result to a substantially smaller value of Toffsetand in return substantially increase the operational gains from DPS. Tproc,2muxfor a cell of the MCG and Tproc,2muxfor a cell of the SCG depend on the UE PUSCH processing capability used on the cell of the MCG and the cell of the SCG, such as a UE PUSCH capability 1 or a UE PUSCH capability 2 as defined in TS 38.214 v16.0.0, and also depend on the SCS configuration on the cell of the MCG and the cell of the SCG. For example, for a UE operating with PUSCH processing capability 1 and μ=2 on a cell of the MCG and with PUSCH processing capability 1 and μ=0 on a cell of the SCG, Tproc,2muxcan be determined using Tables 6.4-1 and 6.4-2 from TS 38.214 v16.0.0, Tproc,2mux=24 symbols for μ=2, or equivalently Tproc,2mux=6 symbols for μ=0 on the MCG, while Tproc,2mux=10 symbols on the SCG (for simplicity, a same corresponding UE PUSCH processing capability and SCS is assumed for all cells on the MCG and all cells of the SCG; otherwise, the maximum Tproc,2muxamong cells of the MCG and the maximum Tproc,2muxamong all cells of the SCG is applicable). Therefore, about 4 additional symbols on the SCG would be needed in that case. For example, for a UE operating with PUSCH capability 2 and μ=2 on the MCG for determining and with PUSCH capability 1 and μ=0 on the SCG, Tproc,2mux=12 symbols for μ=2, or equivalently 3 symbols for μ=0, on the MCG while Tproc,2mux=10 symbols on the SCG. Therefore, about 7 additional symbols on the SCG would be needed in that case. For example, if the previous setups for the MCG and the SCG were reversed, 0 additional symbols to Tproc,2muxwould be needed. In general, Toffsetcan be expressed as Toffset=Tproc,2mux+δ where δ depends on the PUSCH processing capability and the SCS used on the MCG and the SCG. In a first approach, a “worst case” scenario is considered where a single Toffsetvalue is defined corresponding to the largest possible value of Toffsetunder allowed configurations for the UE processing time and the SCS on the MCG (across all cells of the MCG) and the SCG (across all cells of the SCG). That Toffsetis the one corresponding to the maximum across all cells of the MCG and the SCG as it is the largest value among Tproc,2, Tproc,2mux, Tproc,releasemux, Tproc,CSI, and Tproc,CSImux. This is simple but inefficient and penalizes DPS operation for DC as Tproc,CSImux(and Tproc,CSI) are typically much larger than Tproc,2, Tproc,2mux, and Tproc,releasemuxand would therefore result to a value of Toffsetthat is too large to be beneficial in practice for DPS as it requires significant delays on the MCG scheduling. For example, for UE processing PUSCH capability 1 and SCS of 15 kHz (μ=0), Tproc,CSImuxis 3 milliseconds while Tproc,2muxis 0.785 milliseconds. In a second approach, Toffsetcan be determined according to the MCG/SCG UE configurations in terms of corresponding UE PUSCH processing capability (PUSCH timing capability) and SCS configuration. Based on a DPS UE capability, Tproc,CSImuxand Tproc,CSIcan be excluded from the determination of Toffsetto avoid large values (the maximum corresponding value of Tproc,2muxacross all cells of the MCG and all cells of the SCG is used instead). Additionally, as not all combinations are relevant, it is possible to select a subset of combinations for the UE to operate with for DPS in dual connectivity. For example, such combinations can be based on ones provided in Table 3. TABLE 3PUSCH timing/processing capability andSCS combinations for MCG and SCGδ (symbolsCapabilityμfor μ = 0)Same or lower on MCGSame or lower on MCG0Higher on MCGSame or lower on MCG5Same or lower on MCGHigher on MCG3Higher on MCGHigher on MCG7 Further, a power of configured (by higher layers) transmissions on the MCG can depend on a detection of a DCI format providing transmit power control (TPC) commands, such as a DCI format 2_2, in a PDCCH reception. For example, when a UE has overlapping transmissions on the MCG and the SCG, the UE may not apply a TPC command in a DCI format 2_2 to the transmission on the MCG when a time between the end of a PDCCH reception on the MCG that provides DCI format 2_2 and the beginning of the transmission on the SCG is less than Toffset. For example, application of a positive TPC command value can lead to power scaling for the transmissions on the SCG. However, Toffset=Tproc,2mux+6 can be viewed as an upper bound and includes timelines needed for determining other transmission powers. The same applies for a triggered SRS transmission by a DCI format 2_3 and for a PRACH transmission triggered by a PDCCH order. FIG.7illustrates a method700for a UE to determine a transmission power on a SCG by considering scheduled transmissions on an MCG according to this disclosure. For example, the method700may be performed by the UE116. The embodiment of the method700inFIG.7is provided for illustration only; other embodiments may be implemented in accordance with the principles of the present disclosure. A UE indicates a first or second capability for dynamic power sharing for operation with dual connectivity step710. The UE determines whether the UE indicated a first or a second DPS capability step720. The UE does not expect to have transmissions on the MCG that are scheduled by DCI formats in PDCCH receptions with a last symbol that is earlier by less than or equal to ToffsetTproc,CSImuxfrom the first symbol of the transmission occasion on the SCG, and overlap with the transmission occasion on the SCG, wherein Toffset=Tproc,2muxwhen the UE indicates the first DPS capability step730and Toffset=Tproc,CSImuxwhen the UE indicates the second DPS capability step740wherein Tproc,2mux,maxand Tproc,CSImux,maxare the maximum of the corresponding values of Tproc,2muxand Tproc,CSImuxfor the UE across all cells of the MCG and of the SCG. In the following, Toffset=max {Tproc,MCGmax, Tproc,SCGmax}. For example, based on the configurations on the MCG and the SCG, Tproc,MCGmaxand Tproc,SCGmaxcan be either a corresponding Tproc,2mux, and then Toffset=max (Tproc,2mux), when a UE indicates a first value for the DPS capability (DPS capability 1) or a corresponding Tproc,CSImux, and then Toffset=max (Tproc,CSImux), when the UE indicates a second value for the DPS capability (DPS capability 2). DPS for DC operation relies on the MCG scheduler ensuring that a UE transmission on the MCG is delayed by Toffsetfrom the time of the end of an associated PDCCH reception so that it can be ensured that the UE does not have to adjust a transmission power on the MCG or the SCG due to an overlapping transmission on the MCG. Further, power allocation for transmissions on the MCG is prioritized. As previously discussed, in order to maximize throughput/spectral efficiency and coverage gains from DPS, the value of Toffsetis of material importance as a value that is too small cannot satisfy UE processing requirements while a value that is too large diminishes the gains from DPS operation in DC. As Toffsetdepends on Tproc,SCGmaxand as Tproc,SCGmaxdepends on configurations of several parameters the UE has on the SCG, particularly of the UE PUSCH processing/timing capability but also the configurations for CSI reporting on a PUSCH transmission for DPS capability 1, the SCS of the active UL BWP, and so on, the MN/MCG needs to know the configurations of such parameters on the SCG. Such knowledge is not always possible as some of those parameters can change by physical layer signaling, such as the active BWP, and it is also possible for the SCG to modify those parameters without MCG involvement. In such cases, the MN can negotiate with the SN a value for Tproc,SCGmaxreferred to as Tproc,SCGmax,xCGand can compute Toffsetas Toffset=max {Tproc,MCGmax, Tproc,SCGmax,xCG}. It is also possible that the SN rejects the negotiation with the MN to avoid any restrictions in allowable configurations of parameters to the UE. In a second embodiment, when the SN rejects a negotiation with the MN for a value of Tproc,SCGmax,xCG, the MN has to determine a value for Tproc,SCGmax,xCGso that the actual Tproc,SCGmaxon the SCG will always be smaller than or equal to Tproc,SCGmax,xCG. The MN will need to assume the following for the configurations of the UE on the SN:a) Configuration of PUSCH processing/timing capability 1b) A cell where the UE is configured SCS configuration μ=0 (15 kHz SCS) if at least one cell of the SCG has a carrier frequency in a first frequency range (FR1) of frequencies below 6 GHz.c) A-CSI multiplexing in the PUSCH resulting to the largest possible value of Z equal to 40 symbols for SCS configuration μ=0 (15 kHz SCS). Then,a) when the UE declares DPS capability 1, Tproc,SCGmax,xCG=Tproc,CSImux=max ((Z+d)·(2048+144)·κ·2−μ·Tc, d2,2)=max((40+2)·(2048+144)/(15·103·2048)·1000, 1) milliseconds=3 millisecondsb) when the UE declares DPS capability 2, Tproc,SCGmax,xCG=Tproc,2mux,i=max ((N2+d2,1+1)·(2048+144)·κ·2−μ·Tc, d2,2)=max((10+1)·(2048+144)/(15·103·2048)·1000, 1) millisecondsa. If the UE indicates a capability for BWP change, Tproc,SCGmax,xCG=d2,2=1 millisecond (for SCS configuration μ=0)b. If the UE does not indicate a capability for BWP change, Tproc,SCGmax,xCG=(N2+d2,1+1)·(2048+144)·κ·2−μ·Tc=0.785 milliseconds (for SCS configuration μ=0) When the MN knows that all cells of the SN operate in carrier frequencies of a second frequency range (FR2) that is above 6 GHz, then the MN knows that the UE operates with PUSCH processing/timing capability 1 and SCS configuration μ=3 (120 kHz SCS), and Z=152 symbols. Then,a) when the UE declares DPS capability 1, Tproc,SCGmax,xCG=Tproc,CSImux=max ((Z+d)·(2048+144)·κ·2−μ·Tc, d2,2)=max((152+2)·(2048+144)/(8·15·103·2048)·1000, 0.625) milliseconds=1.374 millisecondsb) when the UE declares DPS capability 2, Tproc,SCGmax,xCG=Tproc,2mux,i=max ((N2+d2,1+1)·(2048+144)·κ·2−μ·Tc, d2,2)=max((36+1)·(2048+144)/(8·15·103·2048)·1000, 0.625) millisecondsa. If the UE indicates a capability for BWP change, Tproc,SCGmax,xCG=d2,2=0.625 millisecondb. If the UE does not indicate a capability for BWP change, Tproc,SCGmax,xCG=(N2+d2,1+1)·(2048+144)·κ·2−μ·Tc=0.330 milliseconds FIG.8illustrates a method800for an MN to determine a maximum processing time for transmissions from a UE on an SN according to this disclosure. For example, the method800may be performed by any of the BS101-103. The embodiment of the method800inFIG.8is provided for illustration only; other embodiments may be implemented in accordance with the principles of the present disclosure. A MN assumes that a UE configured for DC operation is also configured with PUSCH processing/timing capability 1 and SCS configuration μ=0 on at least one cell of the SN step810. The MN further considers whether the UE indicates a first DPS capability or a second DPS capability for DC operation step820. When the UE indicates the first DPS capability, the MN considers a PUSCH transmission where a UE multiplexes a CSI report based on a corresponding request in a DCI format scheduling the PUSCH transmission (A-CSI report) in order to determine a maximum processing time for transmission from the UE on the SN step830. When the UE indicates the second DPS capability, the MN considers a PUSCH transmission where a UE multiplexes UCI that the UE would transmit in a PUCCH, that is UCI other than an A-CSI report, in order to determine a maximum processing time for transmission from the UE on the SN840. Further the MN can consider whether the UE indicates a DPS capability for an active BWP change. A third embodiment considers establishing a common understanding of Toffsetamong a MN, a SN, and a UE. A UE needs to know Toffsetbecause Toffsetdetermines several UE functionalities including scheduling of PUSCH/PUCCH/SRS transmissions and processing of TPC commands. When a MN knows the UE configurations on the SN, the MN does not need to provide any additional information to the UE. As the MN knows its own configurations for the UE and as the UE knows the configurations from the MN and the SN, the UE can determine Toffsetas Toffset=max {Tproc,MCGmax, Tproc,SCGmax}. When the MN does not know the UE configurations on the SN, the MN needs to provide to the UE a value for Tproc,SCGmax,xCGin order for the UE to determine Toffsetas Toffset=max {Tproc,MCGmax, Tproc,SCGmax,xCG}, regardless of whether or not the SN accepts a suggestion by the MN for a value of Tproc,SCGmax,xCG. Therefore, the UE can determine Toffsetdepending on whether or not the UE is provided Tproc,SCGmax,xCGby a higher layer parameter maxTprocSCG. If the UE is not provided maxTprocSCG, the UE determines Toffset=max {Tproc,MCGmax, Tproc,SCGmax}. If the UE is provided maxTprocSCG with value Tproc,SCGmax,xCG, the UE determines Toffset=max {Tproc,MCG, Tproc,SCGmax,xCG}. FIG.9illustrates a method900for a UE to determine a minimum time offset between an end of a PDCCH reception scheduling a transmission and the beginning of the transmission according to this disclosure. For example, the method900may be performed by the UE116. The embodiment of the method900inFIG.9is provided for illustration only; other embodiments may be implemented in accordance with the principles of the present disclosure. A UE determines whether or not the UE is provided higher layer parameter maxTprocSCG by a MN step910. When the UE is provided maxTprocSCG by the MN, the UE determines the time offset as Toffset=max {Tproc,MCGmax, Tproc,SCGmax,xCG}, where Tproc,SCGmax,xCGis the value of maxTprocSCG step920. When the UE is not provided maxTprocSCG by the MN, the UE determines the time offset as Toffset=max {Tproc,MCGmax, Tproc,SCGmax,xCG} step930, where the UE determines Tproc,SCGmaxbased on configurations of transmission parameters, such as a UE processing/timing capability, on cells of the SN depending on whether the UE indicates a first DPS capability or a second DPS capability. The UE determines Tproc, MCGmaxbased on configurations of transmission parameters on cells of the MN depending on whether the UE indicates a first DPS capability or a second DPS capability. When the UE indicates the first DPS capability, Tproc,SCGmaxincludes a processing time for multiplexing an A-CSI report in a PUSCH. When the indicates the second DPS capability, Tproc,SCGmaxdoes not include a processing time for multiplexing an A-CSI report in a PUSCH. It is also possible to avoid use of higher layer signaling to a UE for the UE to determine Tproc,SCGmax,xCGand Toffset. In such case, a UE can assume that Tproc,SCGmaxis not determined according to actual configurations at a given time on the SCG, such as for SCS or UE PUSCH processing capability, but instead Tproc,SCGis determined over all possible configurations on the SCG and Tproc,SCGmax=maxSCG,configsTproc,SCGmax. Then, when the MN and the SN determine, for example through a negotiating procedure, a Toffsetthat is larger than the maximum Toffsetfor DPS capability 2, the MN can configure the UE to operate with DPS capability 1. Then the UE can assume, for example, Tproc,SCGmax=3 milliseconds or, in general, a maximum Toffsetfor DPS capability 1. When the MN and the SN determine a Toffsetthat is not larger than the maximum Toffsetfor DPS capability 2, the MN can configure the UE to operate with DPS capability 2. Then the UE can assume, for example, that Tproc,SCGmax=0.86 milliseconds (equal to Tproc,2muxfor SCS configuration μ=0) or, in general, a maximum Toffsetfor DPS capability 2 such as for example 0.50 milliseconds (equal to Tproc,2muxfor SCS configuration μ=1) if SCS configuration μ=0 is not configured (cannot be used) for any BWP on the SCG and SCS configuration μ=1 is configured (can be used). The BWP can be an active BWP or any configured BWP on the SCG. Therefore, if a UE is not provided Tproc,SCGmax,xCG, the UE assumes Toffset=3 milliseconds when the UE is configured for DPS capability 1 and the UE assumes Toffset=0.86 milliseconds when the UE is configured for DPS capability 2. As an enhancement, the maximum value for Toffsetfor a corresponding DPS capability can be reduced based on a smallest possible SCS configuration μ the UE can determine that the UE is possible to operate with on an active BWP of the MN or the SN. Although the present disclosure has been described with an example embodiment, various changes and modifications can be suggested by or to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. | 55,754 |
11943720 | MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be hereinafter described with reference to drawings. The embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment. In operation of a wireless communication system according to embodiment of the present invention, existing techniques are used as appropriate. However, an example of existing technique includes an existing LTE, but is not limited to the existing LTE. In addition, the term “LTE” used in this specification has a broad meaning including LTE-Advanced, specifications newer than LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network) unless otherwise specified. In the embodiment of the present invention, the duplex method may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or others (for example, Flexible Duplex and the like). Further, in the embodiment of the present invention, “to configure” a radio parameter or the like may be that a predetermined value is configured in advance (Pre-configure), or that a radio parameter indicated by a base station apparatus10or user equipment20is set. FIG.1is a drawing for explaining V2X. In 3GPP, the implementation of V2X (Vehicle to Everything) or eV2X (enhanced V2X) by extending the D2D function has been discussed, and V2X and eV2X are being fixed as technical specifications. As illustrated inFIG.1, V2X is a part of ITS (Intelligent Transport Systems) and is a general term including V2V (Vehicle to Vehicle) meaning a form of communication performed between vehicles, a V2I (Vehicle to Infrastructure) meaning a form of communication performed between a vehicle and a road-side unit (RSU) installed on a roadside, a V2N (Vehicle to Network) meaning a form of communication performed between a vehicle and an ITS server, and a V2P (Vehicle to Pedestrian) meaning a form of communication performed between a vehicle and a mobile terminal carried by a pedestrian. In 3GPP, V2X using LTE or NR cellular communication and inter-terminal communication is being studied. V2X using cellular communication is also referred to as cellular V2X. NR-based V2X is being studied to achieve a higher capacity, a lower delay, a higher reliability, and QoS (Quality of Service) control. It is anticipated that discussions not limited to 3GPP specifications will be advanced in the future for LTE or NR-based V2X. It is expected that the following items will be discussed, for example, ensuring interoperability, reducing costs by implementing higher layers, methods for using or switching multiple RATS (Radio Access Technology), handling regulations in various countries, data acquisition, distribution, database management, and usage methods for LTE or NR-based V2X platforms. In the embodiment of the present invention, a communication apparatus is mainly assumed to be mounted on a vehicle, but the embodiment of the present invention is not limited thereto. For example, the communication apparatus may be a terminal held by a person, or the communication apparatus may be an apparatus mounted on a drone or an aircraft, the communication apparatus may be a base station, an RSU, a relay station (relay node), a user equipment having scheduling capability, or the like. SL (Sidelink) may be distinguished from UL (Uplink) or DL (Downlink) based on any one of or a combination of items (1) to (4) below. SL may be given a different name. (1) Time domain resource assignment (2) Frequency domain resource assignment (3) Reference synchronization signals (including SLSS (Sidelink Synchronization Signal) (4) Reference signal used for path loss measurement for transmission power control OFDM (Orthogonal Frequency Division Multiplexing) techniques for SL or UL may be any one of OFDM techniques including CP-OFDM (Cyclic-Prefix OFDM), DFT-S-OFDM (Discrete Fourier Transform-Spread-OFDM), OFDM without transform precoding, and OFDM with transform precoding. In SL of LTE, Mode 3 and Mode 4 are defined for SL resource assignment to user equipment20. In Mode 3, transmission resources are dynamically assigned by DCI (Downlink Control Information) transmitted from the base station apparatus10to the user equipment20. In Mode 3, SPS (Semi Persistent Scheduling) is also possible. In Mode 4, user equipment20autonomously selects a transmission resource from the resource pool. A slot in the embodiment of the present invention may be read as a symbol, a mini-slot, a subframe, a radio frame, a TTI (Transmission Time Interval), or the like. Further, a cell in the embodiment of the present invention may be read as a cell group, a carrier component, a BWP, a resource pool, a resource, a RAT (Radio Access Technology), a system (including a wireless LAN), or the like. FIG.2is a drawing for explaining an example (1) of transmission mode of V2X. In a sidelink communication transmission mode illustrated inFIG.2, in step1, the base station apparatus10transmits sidelink scheduling to user equipment20A. Subsequently, the user equipment20A transmits a PSCCH (Physical Sidelink Control Channel) and a PSSCH (Physical Sidelink Shared Channel) to user equipment20B based on the received scheduling (step2). The transmission mode of the sidelink communication illustrated inFIG.2may be referred to as a sidelink transmission mode 3 in LTE. The sidelink transmission mode 3 in LTE performs Uu-based sidelink scheduling. Uu is a radio interface between UTRAN (Universal Terrestrial Radio Access Network) and UE (User Equipment). Note that the transmission mode of sidelink communication illustrated inFIG.2may be referred to as a sidelink transmission mode 1 in NR. FIG.3is a drawing for explaining an example (2) of transmission mode of V2X. In a sidelink communication transmission mode illustrated inFIG.3, in step1, the user equipment20A transmits PSCCH and PSSCH to the user equipment20B using the autonomously selected resource. The transmission mode of the sidelink communication illustrated inFIG.3may be referred to as a sidelink transmission mode 4 in LTE. In the sidelink transmission mode 4 in LTE, the UE itself performs resource selection. FIG.4is a drawing for explaining an example (3) of transmission mode of V2X. In the sidelink communication transmission mode illustrated inFIG.4, in step1, the user equipment20A transmits PSCCH and PSSCH to the user equipment20B using an autonomously selected resource. Likewise, the user equipment20B transmits PSCCH and PSSCH to the user equipment20A using the autonomously selected resource (step1). The transmission mode of sidelink communication illustrated inFIG.4may be referred to as a sidelink transmission mode 2a in NR. In the sidelink transmission mode 2 in NR, the UE itself executes resource selection. FIG.5is a drawing for explaining an example (4) of transmission mode of V2X. In the sidelink communication transmission mode illustrated inFIG.5, in step0, the base station apparatus10transmits a scheduling grant of a sidelink to the user equipment20A via RRC (Radio Resource Control) configuration. Subsequently, the user equipment20A transmits PSSCH to the user equipment20B based on the received scheduling (step1). Alternatively, the user equipment20A transmits PSSCH to the user equipment20B based on configurations determined in advance according to specifications. The transmission mode of sidelink communication illustrated inFIG.5may be referred to as a sidelink transmission mode 2c in NR. FIG.6is a drawing for explaining an example (5) of transmission mode of V2X. In a sidelink communication transmission mode illustrated inFIG.6, in step1, the user equipment20A transmits sidelink scheduling to the user equipment20B via PSCCH. Subsequently, the user equipment20B transmits PSSCH to the user equipment20A based on the received scheduling (step2). The transmission mode of the sidelink communication illustrated inFIG.6may be referred to as a sidelink transmission mode 2d in NR. FIG.7is a drawing for explaining an example (1) of a communication type of V2X. The communication type of the sidelink illustrated inFIG.7is unicast. The user equipment20A transmits PSCCH and PSSCH to the user equipment20. In the example illustrated inFIG.7, the user equipment20A performs unicast to the user equipment20B and performs unicast to the user equipment20C. FIG.8is a drawing for explaining an example (2) of a communication type of V2X. The sidelink communication type illustrated inFIG.8is groupcast. The user equipment20A transmits PSCCH and PSSCH to a group to which one or more user equipments20belong. In the example illustrated inFIG.8, the group includes the user equipment20B and the user equipment20C, and the user equipment20A performs groupcast to the group. FIG.9is a drawing for explaining an example (3) of a communication type of V2X. The communication type of the sidelink illustrated inFIG.9is broadcast. The user equipment20A transmits PSCCH and PSSCH to one or a plurality of user equipments20. In the example illustrated inFIG.9, the user equipment20A performs broadcast to the user equipment20B, the user equipment20C, and user equipment20D. In NR-V2X, HARQ is supported for unicast and groupcast of sidelink. Further, in NR-V2X, SFCI (Sidelink Feedback Control Information) including a HARQ response is defined. Furthermore, it is studied that SFCI is transmitted via PSFCH (Physical Sidelink Feedback Channel). Here, only one physical resource is used for PSSCH transmission for performing unicast or groupcast. However, in a case where the communication type is a groupcast and both ACK and NACK are transmitted as HARQ responses, many PSFCH resources are consumed. Therefore, the following options (1) and (2) are conceivable. (1) Only in a case of NACK, a HARQ response is transmitted, and all the user equipments20included in the group transmit an HARQ response using a single PSFCH resource. (2) In the case of either ACK or NACK, a HARQ response is transmitted, and the user equipments20included in the group transmit a HARQ response using different PSFCH resources. In a case where the option (1) is adopted, there is an advantage in that less resources are consumed. In a case where the option (2) is adopted, there is an advantage in that the reliability is improved. FIG.10is a drawing for explaining an example of a HARQ response during groupcast. The transmission power of PSFCH that is a channel for transmitting HARQ responses needs to be determined appropriately. In particular, in a case where the above option (1) is adopted, multiple user equipments20that receive groupcast transmit HARQ responses with the same PSFCH resource, and accordingly, there is a problem in the leakage power to adjacent channels of PSFCH as illustrated inFIG.10. The user equipment20A illustrated inFIG.10performs groupcast to a user equipment20B, a user equipment20C, a user equipment20D, and a user equipment20E. Subsequently, the user equipment20B, the user equipment20C, the user equipment20D, and the user equipment20E transmit PSFCH to the user equipment20A and a HARQ response with the same PSFCH resource. Here, in a case where the user equipment20F illustrated inFIG.10transmits PSSCH to the user equipment20G, there may be a situation in which the leakage power from PSFCH transmitted from the user equipment20B, the user equipment20C, the user equipment20D, and the user equipment20E interferes with PSSCH transmitted from the user equipment20F. Hereinafter, a method for setting or controlling the transmission power of the HARQ response in PSFCH will be described. The following description of “transmission power” may correspond to “transmission power” or may correspond to “PSD (Power spectral density)”. For example, the transmission power of the HARQ response may be fixedly set or may be fixedly defined in advance. The transmission power of the HARQ response may be set for each user equipment20or may be defined in advance for each user equipment20. FIG.11is a sequence drawing for explaining an example (1) of a HARQ response during groupcast according to an embodiment of the present invention. For example, the transmission power of the HARQ response may be dynamically set or may be defined in advance. The transmission power may be set as an absolute value or set with an offset or may be defined in advance. For each user equipment20, one or more absolute values may be determined and indicated, or one or more offsets may be determined and indicated. When the base station apparatus10or the user equipment20having scheduling capability dynamically determines the transmission power of HARQ response for each user, a user equipment20performing sidelink transmission may report a status in sidelink transmission to a base station apparatus10or the user equipment20having scheduling capability. The status in the sidelink transmission may be, for example, the number of UEs receiving groupcast. In step S11illustrated inFIG.11, the user equipment20A that performs groupcast transmits a scheduling request including the number of reception-side UEs of groupcast to the base station apparatus10. Subsequently, the base station apparatus10determines a PSFCH transmission power for each UE or common to the UEs, based on the received number of reception-side UEs of groupcast (S12). For example, the base station apparatus10may decrease the PSFCH transmission power as the number of groupcast reception-side UEs increases. Subsequently, the base station apparatus10transmits sidelink scheduling including the indication of PSFCH transmission power determined in step S12to the user equipment20A (S13). In step S14, the user equipment20A transmits in groupcast a sidelink signal including the indication of PSFCH transmission power received in step S13to the group including the user equipment20B. The group includes one or a plurality of user equipments20other than the user equipment20B, and the user equipments20included in the group receive the sidelink signal including the indication of PSFCH transmission power, in a manner similar to the user equipment20B. Subsequently, the user equipment20B applies the indicated PSFCH transmission power based on the reception state of the groupcasted sidelink signal and transmits an HARQ response via PSFCH (S15). The user equipments20that have received the groupcast apply the indicated PSFCH transmission power in a manner similar to the user equipment20B, and transmit HARQ responses via PSFCH. It should be noted that the base station apparatus10illustrated inFIG.11may be replaced with the user equipment20having scheduling capability. Further, the sidelink signal transmission from the user equipment20A to the user equipment20B illustrated inFIG.11may be unicast. When the sidelink signal transmission is unicast, the number of reception-side UEs in the groupcast may be 1. FIG.12is a sequence drawing for explaining an example (2) of a HARQ response during groupcast according to an embodiment of the present invention. When a user equipment20performing groupcast dynamically determines the transmission power of HARQ response for each user, the transmission power of PSFCH with which the corresponding HARQ response is transmitted may be set or may be defined in advance, in a user equipment20performing sidelink transmission, based on the status in the sidelink transmission. The status in the sidelink transmission may be, for example, the number of reception-side UEs of groupcast, or may be a power offset value with respect to the transmission power of PSCCH or PSSCH via which groupcast is transmitted. In step S21illustrated inFIG.12, the user equipment20A performing the groupcast determines the PSFCH transmission power based on the number of reception-side UEs of the groupcast or the power offset value with respect to the transmission power of the PSCCH or PSSCH via which the groupcast is transmitted. Subsequently, the user equipment20A transmits in groupcast a sidelink signal including the indication of PSFCH transmission power determined in step S21to the group including the user equipment20B (S22). The group includes one or a plurality of user equipments20in addition to the user equipment20B, and the user equipments20included in the group receive the sidelink signal including the indication of PSFCH transmission power, in a manner similar to the user equipment20B. Subsequently, the user equipment20B applies the indicated PSFCH transmission power based on the reception state of the groupcasted sidelink signal and transmits a HARQ response via PSFCH (S23). The user equipments20that have received the groupcast apply the PSFCH transmission power indicated in a manner similar to the user equipment20B, and transmit HARQ responses via PSFCH. Note that the sidelink signal transmission from the user equipment20A to the user equipment20B illustrated inFIG.12may be unicast. When the sidelink signal transmission is unicast, the number of reception-side UEs in the groupcast may be 1. In addition, “PSFCH transmission power indication” inFIG.11andFIG.12may be indicated via a physical layer signal link or a higher layer signaling such as SCI (Sidelink Control Information), DCI (Downlink Control Information), MAC (Medium Access Control) CE (Control Element), RRC, and the like. In the physical layer signal link or the higher layer signaling, which signaling is to be used or set may be defined in advance based on the sidelink transmission mode explained inFIG.2toFIG.5. Note that the method of fixedly setting the transmission power of the HARQ response and the method of dynamically setting the transmission power of the HARQ response may be executed in combination. Whether the method of setting the transmission power of the HARQ response fixedly described above or the method of dynamically setting the transmission power of the HARQ response is executed may be determined according to the communication type such as unicast or groupcast. The leakage power from PSFCH to the adjacent channels can be controlled by the method of fixedly setting the transmission power of the HARQ response or the method of dynamically setting the transmission power of the HARQ response. FIG.13is a drawing for explaining an example of channel arrangement in an embodiment of the present invention. The leakage power from PSFCH to adjacent channels may be controlled by the channel arrangement of PSFCH. For example, PSFCH for the HARQ response of groupcast may be set in time division with other channels or may be defined in advance. Also, for example, as illustrated inFIG.13, PSFCH for HARQ response of groupcast is arranged in frequency division with other channels, and further, guard subcarriers may be arranged between another channel and PSFCH. The guard subcarrier may be, for example, a guard band, a guard PRB (Physical Resource Block), a guard subchannel, or the like. Another channel adjacent to PSFCH having the guard subcarrier interposed therebetween may be PSCCH, PSSCH, PSFCH for unicast HARQ response, or the like. The operation of the user equipment20relating to the guard subcarrier may be defined based on a sidelink transmission mode described with reference toFIG.2toFIG.5. For example, in the sidelink transmission mode 1 or 2d, the user equipment20does not expect any other channel to be transmitted or scheduled on the guard subcarrier. Further, for example, in the sidelink transmission mode 2a or 2c, the user equipment20selects resources in the frequency domain excluding guard subcarriers for transmission of other channels. Also, for example, if any other channel can be transmitted on the guard subcarrier, the transmission on that other channel is dropped. The guard subcarrier may be set or may be defined in advance. For example, the guard subcarrier may be set by a higher layer signaling such as RRC. The time domain in which guard subcarriers are arranged may have at least the length of PSFCH in time domain for HARQ response with groupcast. According to the above embodiment, the user equipment20and the base station apparatus10can suppress leakage power from PSFCH to adjacent channels according to either the method of fixedly setting the transmission power of PSFCH via which the HARQ response is transmitted or the method of dynamically setting the transmission power of PSFCH via which the HARQ response is transmitted. The user equipment20may suppress the leakage power from PSFCH to adjacent channels by the channel arrangement of PSFCH including the guard subcarrier. Therefore, a response related to retransmission control can be appropriately transmitted in direct communication between terminals. <Apparatus Configuration> Next, an example of functional configuration of the base station apparatus10and the user equipment20that execute the processing and operations described so far will be described. The base station apparatus10and the user equipment20include a function for implementing the above-described embodiment. However, each of the base station apparatus10and the user equipment20may have only some of the functions in the embodiment. <Base Station Apparatus10> FIG.14is a drawing illustrating an example of a functional configuration of the base station apparatus10. As illustrated inFIG.14, the base station apparatus10includes a transmitting unit110, a receiving unit120, a configuring unit130, and a control unit140. The functional configuration illustrated inFIG.14is only an example. As long as the operation according to the embodiment of the present invention can be executed, the functions may be divided in any way, and the functional units may be given any names. The transmitting unit110includes a function of generating signals to be transmitted to the user equipment20and wirelessly transmitting the signals. The receiving unit120includes a function of receiving various types of signals transmitted from the user equipment20and acquiring, for example, information on a higher layer from the received signals. Further, the transmitting unit110has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, a DL/UL control signal, a DL reference signal or the like to the user equipment20. The configuring unit130stores configuration information configured in advance and various configuration information to be transmitted to the user equipment20in a storage device and reads out the setting information from the storage device as needed. The contents of the configuration information are, for example, information about configuration of D2D communication. As described in the embodiment, the control unit140performs processing of configuration for allowing the user equipment20to perform D2D communication. Also, the control unit140transmits scheduling of D2D communication via the transmitting unit110to the user equipment20. The control unit140determines the transmission power of the HARQ response of D2D communication and transmits the HARQ response to the user equipment20via the transmitting unit110. A functional unit for transmitting signals in the control unit140may be included in the transmitting unit110, and a functional unit for receiving signals in the control unit140may be included in the receiving unit120. <User Equipment20> FIG.15is a drawing illustrating an example of a functional configuration of the user equipment20. As illustrated inFIG.15, the user equipment20includes a transmitting unit210, a receiving unit220, a configuring unit230, and a control unit240. The functional configuration illustrated inFIG.15is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functions may be divided in any way, and the functional units may be given any names. The transmitting unit210generates a transmission signal from transmission data and wirelessly transmits the transmission signal. The receiving unit220wirelessly receives various types of signals, and acquires a signal in a higher-layer from the received signal in the physical layer. Also, the receiving unit220has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL/SL control signals, reference signals, and the like that are transmitted from the base station apparatus10. Also, for example, in D2D communication, the transmitting unit210transmits, to another user equipment20, a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like. The receiving unit220receives the PSCCH, the PSSCH, the PSDCH, the PSBCH, and the like, from the another user equipment20. The configuring unit230stores in a storage device various types of configuration information received from the base station apparatus10or the user equipment20by the receiving unit220and reads out the configuration information from the storage device as needed. The configuring unit230also stores configuration information configured in advance. The contents of the configuration information are, for example, information about configuration of D2D communication. As described in the embodiment, the control unit240controls D2D communication with another user equipments20. The control unit240performs processing relating to HARQ for D2D communication. The control unit240may schedule D2D communication for another user equipment20. The control unit240transmits a HARQ response of D2D communication to the user equipment20via the transmitting unit210with a transmission power set or a transmission power defined in advance. A functional unit for transmitting signals in the control unit240may be included in the transmitting unit210, and a functional unit for receiving signals in the control unit240may be included in the receiving unit220. <Hardware Configuration> The block diagrams (FIGS.14and15) used for explaining the above embodiment illustrate blocks in units of functions. These functional blocks (constituting units) are implemented by any combinations of at least one of hardware and software. In this regard, a method for implementing the various functional blocks is not particularly limited. That is, each functional block may be implemented by one device united physically and logically. Alternatively, each functional block may be implemented by connecting directly or indirectly (for example, in a wired or wireless manner) two or more devices that are physically or logically separated and connected together and using these multiple devices. The functional block may be implemented by combining software with the single device or multiple devices. Functions include, but are not limited to, determining, calculating, processing, deriving, investigating, searching, confirming, receiving, transmitting, outputting, accessing, resolving, selecting, establishing, comparing, assuming, expecting, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, and the like. For example, a functional block (constituting unit) that has a function of transmitting is referred to as a transmitting unit or a transmitter. As described above, a method for implementing these functions is not particularly limited. For example, the base station apparatus10, the user equipment20, and the like according to one embodiment of the present disclosure may function as a computer that performs processing of a wireless communication according to the present disclosure.FIG.16is a drawing illustrating an example of a hardware configuration of the base station apparatus10or the user equipment20according to an embodiment of the present disclosure. Each of the base station apparatus10and user equipment20may be physically configured as a computer device including a processor1001, a storage device1002, an auxiliary storage device1003, a communication device1004, an input device1005, an output device1006, a bus1007, and the like. It is noted that, in the following description, the term “device” may be read as a circuit, an apparatus, a unit, or the like. The hardware configurations of the base station apparatus10and the user equipment20may be configured to include one or more of the devices illustrated in drawings, or may be configured not to include some of the devices. Each function of the base station apparatus10and the user equipment20may be implemented by reading predetermined software (program) to hardware such as the processor1001, the storage device1002, or the like, causing the processor1001to perform operations, controlling communication by the communication device1004, and controlling at least one of reading and writing of data in the storage device1002and the auxiliary storage device1003. The processor1001executes, for example, an operating system to control the overall operation of the computer. The processor1001may be a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, the control unit140, the control unit240, and the like described above may be realized by the processor1001. The processor1001reads a program (program code), a software module, or data from at least one of the auxiliary storage device1003and the communication device1004onto the storage device1002, and performs various processes according to the program, the software module, or the data. As the program, a program that causes a computer to perform at least some of the operations described in the embodiment explained above is used. For example, the control unit140of the base station apparatus10, as illustrated inFIG.14, may be implemented by a control program that is stored in the storage device1002and that is executed by the processor1001. Also, for example, the control unit240of the user equipment20, as illustrated inFIG.15, may be implemented by a control program that is stored in the storage device1002and that is executed by the processor1001. Explanation has been provided above for the case in which the above various processings are performed by the single processor1001. However, such processing may be simultaneously or sequentially performed by two or more processors1001. The processor1001may be implemented with one or more chips. It is noted that the program may be transmitted from a network through an electronic communication line. The storage device1002is a computer-readable recording medium and may be constituted by at least one of, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), and the like. The storage device1002may also be referred to as a register, a cache, a main memory (main storage device), or the like. The storage device1002can store a program (program code), a software module and the like that can be executed to perform a communication method according to an embodiment of the present disclosure. The auxiliary storage device1003is a computer-readable recording medium and may be configured by at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, or a Blu-ray (registered trademark) disk), a smart card, a flash memory (for example, a card, a stick, or a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. The auxiliary storage device1003may be referred to as a storage. The above storage medium may be, for example, a database including at least one of the storage device1002and the auxiliary storage device1003, a server, or other appropriate media. The communication device1004is hardware (a transmission and reception device) for performing communication between computers through at least one of a wired network and a wireless network and may also be referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. The communication device1004may include, for example, a radio frequency switch, a duplexer, a filter, a frequency synthesizer, or the like to implement at least one of a frequency division duplex (FDD) and a time division duplex (TDD). For example, a transmission and reception antenna, an amplifier, a transmitting and receiving unit, a transmission line interface, and the like may be implemented by the communication device1004. The transmitting and receiving unit may be implemented in such a manner that a transmitting unit and a receiving unit are physically or logically separated. The input device1005is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or the like) that receives an input from the outside. The output device1006is an output device (for example, a display, a speaker, an LED lamp, or the like) that performs an output to the outside. It is noted that the input device1005and the output device1006may be integrated with each other (for example, a touch panel). The devices, such as the processor1001and the storage device1002, are connected to each other via a bus1007for communicating information. The bus1007may be constituted by using a single bus, or may be constituted by using busses different depending on devices. The base station apparatus10and the user equipment20may include hardware, such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), or alternatively, some or all of the functional blocks may be implemented by the hardware. For example, the processor1001may be implemented with at least one of these hardware components. Summary of Embodiment As described above, according to an embodiment of the present invention, provided is a user equipment including a transmitting unit configured to transmit a groupcast to a group including a plurality of user equipments, a receiving unit configured to receive a response related to a retransmission control for the groupcast, and a control unit configured to control a leakage power to another channel arranged by frequency division with a channel via which a response related to the retransmission control for the groupcast is received. According to the above configuration, the user equipment20can suppress leakage power from PSFCH to adjacent channels according to either a method of fixedly setting the transmission power of PSFCH via which a HARQ response is transmitted or a method of dynamically setting the transmission power of PSFCH via which a HARQ response is transmitted. Therefore, a response related to retransmission control can be appropriately transmitted in direct communication between terminals. Regarding the channel via which the response related to the retransmission control for the groupcast is received, a guard region may be arranged between the channel and the another channel. According to the above configuration, the user equipment20may suppress the leakage power from PSFCH to adjacent channels by the PSFCH channel arrangement including the guard subcarrier. The control unit may transmit, to the group, information indicating a transmission power to be applied to the channel via which the response related to the retransmission control for the groupcast is received, the transmission power being determined based on a status of the groupcast. According to the above configuration, the leakage power from PSFCH to adjacent channels can be suppressed by the method of dynamically setting the transmission power of PSFCH via which a HARQ response is transmitted. The status of the groupcast is a number of user equipments included in the group or a power offset value with respect to a transmission power of a channel via which the groupcast is transmitted. According to the above configuration, based on the number of reception-side user equipments20included in the group or the power offset value with respect to the transmission power of the groupcast, the leakage power from PSFCH to adjacent channels can be suppressed by the method of dynamically setting the transmission power of PSFCH via which a HARQ response is transmitted. The control unit may transmit, to a base station apparatus, the status of the groupcast together with a scheduling request of the groupcast, and may receive, from the base station apparatus, the information indicating the transmission power to be applied to the channel via which the response related to the retransmission control for the groupcast is received, the transmission power being determined based on the status of the groupcast. According to the above configuration, based on information indicating the transmission power of PSFCH received from the base station apparatus10, the leakage power from PSFCH to adjacent channels can be suppressed by the method of dynamically setting the transmission power of PSFCH via which a HARQ response is transmitted. According to an embodiment of the present invention, provided is a base station apparatus including a receiving unit configured to receive a status of a groupcast from a user equipment, a control unit configured to determine a transmission power applied to a channel via which a response related to a retransmission control for the groupcast is received, based on the status of the groupcast, and a transmitting unit configured to transmit, to the user equipment, information indicating the transmission power to be applied to the channel via which the response related to the retransmission control for the groupcast is received. According to the above configuration, the base station apparatus10can suppress the leakage power from PSFCH to adjacent channels by the method of dynamically setting the transmission power of PSFCH via which a HARQ response is transmitted. Therefore, a response related to retransmission control can be appropriately transmitted in direct communication between terminals. Supplements to Embodiment The embodiment of the present invention has been described above, but the disclosed invention is not limited to the above embodiment, and those skilled in the art would understand that various modified examples, revised examples, alternative examples, substitution examples, and the like can be made. In order to facilitate understanding of the present invention, specific numerical value examples are used for explanation, but the numerical values are merely examples, and any suitable values may be used unless otherwise stated. Classifications of items in the above description are not essential to the present invention, contents described in two or more items may be used in combination if necessary, and contents described in an item may be applied to contents described in another item (unless a contradiction arises). The boundaries between the functional units or the processing units in the functional block diagrams do not necessarily correspond to the boundaries of physical components. Operations of a plurality of functional units may be physically implemented by a single component and an operation of a single functional unit may be physically implemented by a plurality of components. Concerning the processing procedures described above in the embodiment, the orders of steps may be changed unless a contradiction arises. For the sake of convenience for describing the processing, the base station apparatus10and the user equipment20have been described with the use of the functional block diagrams, but these apparatuses may be implemented by hardware, software, or a combination thereof. Each of software functioning with a processor of the base station apparatus10according to the embodiment of the present invention and software functioning with a processor of the user equipment20according to the embodiment of the present invention may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an EPROM, an EEPROM, a register, a hard disk (HDD), a removable disk, a CD-ROM, a database, a server, or any suitable recording media. Also, the indication of information is not limited to the aspect or embodiment described in the present disclosure, but may be performed by other methods. For example, the indication of information may be performed by physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (an MIB (Master Information Block) and an SIB (System Information Block)), other signals, or combinations thereof. The RRC signaling may be also be referred to as an RRC message and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like. Each aspect and embodiment described in the present disclosure may be applied to at least one of a system that uses a suitable system such as LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), or Bluetooth (registered trademark), and a next-generation system expanded on the basis thereof. Also a plurality of systems may be combined and applied (for example, a combination of at least one of LTE and LTE-A with 5G, and the like). In the operation procedures, sequences, flowcharts, and the like according to each aspect and embodiment described in the present disclosure, the orders of steps may be changed unless a contradiction arises. For example, in the methods described in the present disclosure, elements of various steps are illustrated by using an exemplary order and the methods are not limited to the specific orders presented. The specific operations performed by the base station apparatus10described in the present disclosure may in some cases be performed by an upper node. It is clear that, in a network that includes one or more network nodes including the base station apparatus10, various operations performed for communication with the user equipment20can be performed by at least one of the base station apparatus10and another network node other than the base station apparatus10(for example, a MME, a S-GW, or the like may be mentioned, but not limited thereto). In the above, the description has been made for the case where another network node other than the base station apparatus10is a single node as an example. But the another network node may be a combination of a plurality of other network nodes (for example, a MME and a S-GW). Information, signals, or the like described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Information, signals, or the like described in the present disclosure may be input and output via a plurality of network nodes. Information or the like that has been input or output may be stored at a predetermined place (for example, a memory) and may be managed with the use of a management table. Information or the like that is input or output can be overwritten, updated, or appended. Information or the like that has been output may be deleted. Information or the like that has been input may be transmitted to another apparatus. In the present disclosure, determination may be made with the use of a value expressed by one bit (0 or 1), may be made with the use of a Boolean value (true or false), and may be made through a comparison of numerical values (for example, a comparison with a predetermined value). Regardless of whether software is referred to as software, firmware, middleware, microcode, a hardware description language, or another name, software should be interpreted broadly to mean instructions, instruction sets, codes, code segments, program codes, a program, a sub-program, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable file, an execution thread, a procedure, a function, and the like. Software, instructions, information, or the like may be transmitted and received through transmission media. For example, in a case where software is transmitted from a website, a server or another remote source through at least one of wired technology (such as a coaxial cable, an optical-fiber cable, a twisted pair, or a digital subscriber line (DSL)) and radio technology (such as infrared or microwaves), at least one of the wired technology and the radio technology is included in the definition of a transmission medium. Information, signals, and the like described in the present disclosure may be expressed with the use of any one of various different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like mentioned herein throughout the above explanation may be expressed by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combinations thereof. The terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). A signal may be a message. A component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like. The terms “system” and “network” used in the present disclosure are used interchangeably. Information, parameters, and the like described in the present disclosure may be expressed by absolute values, may be expressed by relative values with respect to predetermined values, and may be expressed by corresponding different information. For example, radio resources may be indicated by indexes. The above-described names used for the parameters are not restrictive in any respect. In addition, formulas or the like using these parameters may be different from those explicitly disclosed in the present disclosure. Various channels (for example, a PUCCH, a PDCCH, and the like) and information elements can be identified by any suitable names, and therefore, various names given to these various channels and information elements are not restrictive in any respect. In the present disclosure, terms such as “base station (BS)”, “radio base station”, “base station apparatus”, “fixed station”, “NodeB”, “eNodeB (eNB)”, “gNodeB (gNB)”, “access point”, “transmission point”, “reception point”, “transmission/reception point”, “cell”, “sector”, “cell group”, “carrier”, “component carrier”, and the like may be used interchangeably. A base station may be referred to as a macro-cell, a small cell, a femtocell, a pico-cell, or the like. A base station can accommodate one or a plurality of (for example, three) cells (that may be called sectors). In a case where a base station accommodates a plurality of cells, the whole coverage area of the base station can be divided into a plurality of smaller areas. For each smaller area, a base station subsystem (for example, an indoor miniature base station RRH (Remote Radio Head)) can provide a communication service. The term “cell” or “sector” denotes all or a part of the coverage area of at least one of a base station and a base station subsystem that provides communication services in the coverage. In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” may be used interchangeably. By the person skilled in the art, a mobile station may be referred to as any one of a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, and other suitable terms. At least one of a base station and a mobile station may be referred to as a transmitting apparatus, a receiving apparatus, a user equipment, or the like. At least one of a base station and a mobile station may be an apparatus mounted on a mobile body, or may be a mobile body itself, or the like. A mobile body may be a transporting device (e.g., a vehicle, an airplane, and the like), an unmanned mobile (e.g., a drone, an automated vehicle, and the like), or a robot (of a manned or unmanned type). It is noted that at least one of a base station and a mobile station includes an apparatus that does not necessarily move during a communication operation. For example, at least one of a base station and a mobile station may be an IoT (Internet of Things) device such as a sensor. In addition, a base station according to the present disclosure may be read as a user terminal. For example, each aspect or embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced by communication between a plurality of user equipments (that may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), or the like). In this case, a user equipment20may have above-described functions of the base station apparatus10. In this regard, a word such as “up” or “down” may be replaced with a word corresponding to communication between terminals (for example, “side”). For example, an uplink channel, a downlink channel, or the like may be replaced with a side channel. Similarly, a user terminal according to the present disclosure may be read as a base station. In this case, a base station may have above-described functions of the user terminal. The term “determine” used herein may mean various operations. For example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (for example, looking up a table, a database, or another data structure), ascertaining, or the like may be deemed as making determination. Also, receiving (for example, receiving information), transmitting (for example, transmitting information), inputting, outputting, or accessing (for example, accessing data in a memory), or the like may be deemed as making determination. Also, resolving, selecting, choosing, establishing, comparing, or the like may be deemed as making determination. That is, doing a certain operation may be deemed as making determination. “To determine” may be read as “to assume”, “to expect”, “to consider”, or the like. Each of the terms “connected” and “coupled” and any variations thereof mean any connection or coupling among two or more elements directly or indirectly and can mean that one or a plurality of intermediate elements are inserted among two or more elements that are “connected” or “coupled” together. Coupling or connecting among elements may be physical one, may be logical one, and may be a combination thereof. For example, “connecting” may be read as “accessing”. In a case where the terms “connected” and “coupled” and any variations thereof are used in the present disclosure, it may be considered that two elements are “connected” or “coupled” together with the use of at least one type of a medium from among one or a plurality of wires, cables, and printed conductive traces, and in addition, as some non-limiting and non-inclusive examples, it may be considered that two elements are “connected” or “coupled” together with the use of electromagnetic energy such as electromagnetic energy having a wavelength of the radio frequency range, the microwave range, or the light range (including both of the visible light range and the invisible light range). A reference signal can be abbreviated as an RS (Reference Signal). A reference signal may be referred to as a pilot depending on an applied standard. A term “based on” used in the present disclosure does not mean “based on only” unless otherwise specifically noted. In other words, a term “base on” means both “based on only” and “based on at least”. Any references to elements denoted by a name including terms such as “first” or “second” used in the present disclosure do not generally limit the amount or the order of these elements. These terms can be used in the present disclosure as a convenient method for distinguishing two or more elements. Therefore, references to first and second elements do not mean that only the two elements can be employed or that the first element should be, in some way, prior to the second element. “Means” in each of the above-described apparatuses may be replaced with “unit”, “circuit”, “device”, or the like. In a case where any one of “include”, “including”, and variations thereof is used in the present disclosure, each of these terms is intended to be inclusive in the same way as the term “comprising”. Further, the term “or” used in the present disclosure is intended to be not exclusive-or. A radio frame may include, in terms of time domain, one or a plurality of frames. Each of one or a plurality of frames may be referred to as a subframe in terms of time domain. A subframe may include, in terms of time domain, one or a plurality of slots. A subframe may have a fixed time length (e.g., 1 ms) independent of Numerology. Numerology may be a communication parameter that is applied to at least one of transmission and reception of a signal or a channel. Numerology may mean, for example, at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame configuration, a specific filtering processing performed by a transceiver in frequency domain, a specific windowing processing performed by a transceiver in time domain, and the like. A slot may include, in terms of time domain, one or a plurality of symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols) symbols, or the like). A slot may be a time unit based on Numerology. A slot may include a plurality of minislots. Each minislot may include one or a plurality of symbols in terms of the time domain. A minislot may also be referred to as a subslot. A minislot may include fewer symbols than a slot. A PDSCH (or PUSCH) transmitted at a time unit greater than a minislot may be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using minislots may be referred to as a PDSCH (or PUSCH) mapping type B. Each of a radio frame, a subframe, a slot, a minislot, and a symbol means a time unit for transmitting a signal. Each of a radio frame, a subframe, a slot, a minislot, and a symbol may be referred to as other names respectively corresponding thereto. For example, one subframe may be referred to as a transmission time interval (TTI), a plurality of consecutive subframes may be referred to as a TTI, and one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) according to the existing LTE, may have a period shorter than 1 ms (e.g., 1 to 13 symbols), and may have a period longer than 1 ms. Instead of subframes, units expressing a TTI may be referred to as slots, minislots, or the like. A TTI means, for example, a minimum time unit of scheduling in radio communication. For example, in an LTE system, a base station performs scheduling for each user equipment20to assign, in TTI units, radio resources (such as frequency bandwidths, transmission power, and the like that can be used by each user equipment20). However, the definition of a TTI is not limited thereto. A TTI may be a transmission time unit for channel-coded data packets (transport blocks), code blocks, code words, or the like, and may be a unit of processing such as scheduling, link adaptation, or the like. When a TTI is given, an actual time interval (e.g., the number of symbols) to which transport blocks, code blocks, code words, or the like are mapped may be shorter than the given TTI. In a case where one slot or one minislot is referred to as a TTI, one or a plurality of TTIs (i.e., one or a plurality of slots or one or a plurality of minislots) may be a minimum time unit of scheduling. The number of slots (the number of minislots) included in the minimum time unit of scheduling may be controlled. A TTI having a time length of 1 ms may referred to as an ordinary TTI (a TTI according to LTE Rel. 8-12), a normal TTI, a long TTI, an ordinary subframe, a normal subframe, a long subframe, a slot, or the like. A TTI shorter than an ordinary TTI may be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, or the like. Note that a long TTI (for example, normal TTI, subframe, and the like) may be read as TTI having a time length exceeding 1 ms, and a short TTI (for example, shortened TTI) may be read as a TTI having a TTI length less than the TTI length of the long TTI and equal to or more than 1 ms. A resource block (RB) is a resource assignment unit in terms of time domain and frequency domain and may include one or a plurality of consecutive subcarriers in terms of frequency domain. The number of subcarriers included in an RB may be the same regardless of Numerology, and, for example, may be 12. The number of subcarriers included in an RB may be determined based on Numerology. In terms of time domain, an RB may include one or a plurality of symbols, and may have a length of 1 minislot, 1 subframe, or 1 TTI. Each of 1 TTI, 1 subframe, and the like may include one or a plurality of resource blocks. One or a plurality of RBs may be referred to as physical resource blocks (PRBs: Physical RBs), a subcarrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, or the like. A resource block may include one or a plurality of resource elements (RE: Resource Elements). For example, 1 RE may be a radio resource area of 1 subcarrier and 1 symbol. A bandwidth part (BWP) (which may be called a partial bandwidth or the like) may mean a subset of consecutive common RBs (common resource blocks) for Numerology, in any given carrier. A common RB may be identified by a RB index with respect to a common reference point in the carrier. PRBs may be defined by a BWP and may be numbered in the BWP. A BWP may include a BWP (UL BWP) for UL and a BWP (DL BWP) for DL. For a UE, one or a plurality of BWPs may be set in 1 carrier. At least one of BWPs that have been set may be active, and a UE need not assume sending or receiving a predetermined signal or channel outside the active BWP. A “cell”, a “carrier” or the like in the present disclosure may be read as a “BWP”. The above-described structures of radio frames, subframes, slots, minislots, symbols, and the like are merely examples. For example, the number of subframes included in a radio frame, the number of slots included in a subframe or a radio frame, the number of minislots included in a slot, the number of symbols and the number of RBs included in a slot or a minislot, the number of subcarriers included in an RB, the number of symbols included in a TTI, a symbol length, a cyclic prefix (CP) length, and the like can be variously changed. Throughout the present disclosure, in a case where an article such as “a”, “an”, or “the” in English is added through a translation, the present disclosure may include a case where a noun following the article is of a plural form. Throughout the present disclosure, an expression that “A and B are different” may mean that “A and B are different from each other”. Also this term may mean that “each of A and B is different from C”. Terms such as “separate” and “coupled” may also be interpreted in a manner similar to “different”. Each aspect or embodiment described in the present disclosure may be solely used, may be used in combination with another embodiment, and may be used in a manner of being switched with another embodiment upon implementation. indication of predetermined information (for example, indication of “being x”) may be implemented not only explicitly but also implicitly (for example, by not indicating predetermined information). In the present disclosure, sidelink communication is an example of direct communication between terminals. An HARQ response is an example of a response related to retransmission control. PSFCH is an example of a channel that receives an HARQ response. A guard subcarrier, a guard band, a guard PRB, or a guard subchannel are examples of a guard region. PSCCH or PSSCH is an example of a channel via which groupcast is transmitted. Although the present disclosure has been described above, it will be understood by those skilled in the art that the present disclosure is not limited to the embodiment described in the present disclosure. Modifications and changes of the present disclosure may be possible without departing from the subject matter and the scope of the present disclosure defined by claims. Therefore, the descriptions of the present disclosure are for illustrative purposes only, and are not intended to be limiting the present disclosure in any way. REFERENCE SIGNS LIST 10base station apparatus110transmitting unit120receiving unit130configuring unit140control unit20user equipment210transmitting unit220receiving unit230configuring unit240control unit1001processor1002storage device1003auxiliary storage device1004communication device1005input device1006output device | 62,080 |
11943721 | Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding, but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purposes only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces. FIG.1is a diagram illustrating the architecture of a Long Term Evolution (LTE) system according to an exemplary embodiment of the present invention. Referring toFIG.1, the radio access network of the mobile communication system includes evolved Node Bs (eNBs)105,110,115, and120, a Mobility Management Entity (MME)125, and a Serving-Gateway (S-GW)130. The User Equipment (UE)135connects to an external network via eNBs105,110,115, and120and the S-GW130. InFIG.1, the eNBs105,110,115, and120correspond to legacy node Bs of Universal Mobile Communications System (UMTS). The eNBs105,110,115, and120allow the UE to establish a radio link and are responsible for more complicated functions as compared to the legacy node B. In the LTE system, all the user traffic including real time services such as Voice over Internet Protocol (VoIP) are provided through a shared channel and thus there is a need for a device which is located in the eNB to schedule data based on the state information such as UE buffer conditions, power headroom state, and channel state. Typically, one eNB controls a plurality of cells. In order to secure the data rate of up to 100 Mbps, the LTE system adopts Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology. The LTE system adopts Adaptive Modulation and Coding (AMC) to determine the modulation scheme and channel coding rate in adaptation to the channel condition of the UE. S-GW130is an entity to provide data bearers so as to establish and release data bearers under the control of the MME125. MME125is responsible for various control functions and is connected to a plurality of eNBs105,110,115, and120. FIG.2is a diagram illustrating a protocol stack of an LTE system according to an exemplary embodiment of the present invention. Referring toFIG.2, the protocol stack of the LTE system, as employed at a UE and an eNB, includes a Packet Data Convergence Protocol (PDCP) layer205and240, a Radio Link Control (RLC) layer210and235, a Medium Access Control (MAC) layer215and230, and a Physical (PHY) layer220and225. The PDCP layer205and240is responsible for Internet Protocol (IP) header compression/decompression, and the RLC layer210and235is responsible for segmenting the PDCP Protocol Data Unit (PDU) into segments in appropriate size for Automatic Repeat Request (ARQ) operation. The MAC layer215and230is responsible for establishing connection to a plurality of RLC entities so as to multiplex the RLC PDUs into MAC PDUs and demultiplex the MAC PDUs into RLC PDUs. The PHY layer220and225performs channel coding on the MAC PDU and modulates the MAC PDU into OFDM symbols to transmit over a radio channel or performs demodulating and channel-decoding on the received OFDM symbols and delivers the decoded data to the higher layer. The PHY layer uses Hybrid ARQ (HARQ) for additional error correction by transmitting 1 bit information indicating for positive or negative acknowledgement from the receiver to the transmitter. This is referred to as HARQ ACK/NACK information. The downlink HARQ ACK/NACK information corresponding to an uplink transmission is transmitted through Physical Hybrid-ARQ Indicator Channel (PHICH), and the uplink HARQ ACK/NACK information corresponding to a downlink transmission may be transmitted through Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH). FIG.3is a diagram illustrating an exemplary situation of carrier aggregation in an LTE system according to an exemplary embodiment of the present invention. Referring toFIG.3, an eNB may typically use multiple carriers transmitted and received in different frequency bands. For example, the eNB305may be configured to use the carrier315with center frequency f1 and the carrier310with center frequency f3. If carrier aggregation is not supported, the UE330transmits/receives data using one of the carriers310and315. However, the UE330having the carrier aggregation capability may transmit/receive data using both the carriers310and315. The eNB may increase the amount of the resource to be allocated to the UE having the carrier aggregation capability in adaptation to the channel condition of the UE so as to improve the data rate of the UE. By taking notice that a cell is configured with one downlink carrier and one uplink carrier in the related art, the carrier aggregation may be understood as if the UE communicates data via multiple cells. With the use of carrier aggregation, the maximum data rate increases in proportion to the number of aggregated carriers. In the following description, the phrase “the UE receives data through a certain downlink carrier or transmits data through a certain uplink carrier” denotes transmitting or receiving data through control and data channels provided in a cell corresponding to center frequencies and frequency bands of the downlink and uplink carriers. Although the description is directed to an LTE mobile communication system for convenience of explanation, exemplary embodiments of the present invention may be applied to other types of wireless communication systems supporting carrier aggregation. FIG.4is a diagram illustrating a principle of uplink timing synchronization in an Orthogonal Frequency Division Multiplexing (OFDM)-based 3rdGeneration Partnership Project (3GPP) LTE system according to an exemplary embodiment of the present invention. Referring toFIG.4, the diagram is directed to an exemplary case where the UE #1 is located near the eNB while the UE #2 is located far from the eNB. InFIG.4, T_pro1 indicates the first propagation delay time to the UE #1, and T_pro2 indicates the second propagation delay to the UE #2. As shown inFIG.4, the UE #1 is closer to the eNB than the UE #2 and thus has a relatively short propagation delay (T_pro1 is 0.333 us, T_pro2 is 3.33 us). When the UE #1 and UE #2 power on or operate in idle mode within a cell of the eNB, the uplink timing of the UE #1, uplink timing of the UE #2, and uplink timings of other UEs detected by the eNB in the cell may fail in synchronization. Reference number401denotes uplink OFDM symbol transmission timing of the UE #1, and reference number403denotes uplink OFDM symbol transmission timing of the UE #2. By taking notice of the uplink transmission propagation delays of the UE #1 and UE #2, the eNB may receive the uplink OFDM symbols at the timings denoted by reference numbers405,407, and409. The UE #1's uplink symbol transmitted at the timing401is received by the eNB at the timing407with propagation delay while the UE #2's uplink symbol transmitted at the timing403is received by the eNB at the timing409with propagation delay. InFIG.4, since the timings407and409are before the synchronization is acquired between the uplink transmission timings of the UE #1 and UE #2, the uplink OFDM symbol reception and decoding start timing405of the eNB, the UE #1's uplink OFDM symbol reception timing407, and the UE #2's uplink OFDM symbol reception timing409are different. In this case, the uplink symbols transmitted by the UE #1 and UE #2 have no orthogonality, and thus interfere with each other. As a consequence, the eNB is likely to fail decoding the uplink symbols transmitted at the timing401and403by the UE #1 and UE #2, due to the interference and the mismatch between the uplink symbol reception timings407and409. Uplink timing synchronization is a procedure for acquiring the eNB's uplink symbol reception timings with the UE #1 and UE #2. If the uplink timing synchronization procedure completes, it is possible to acquire the synchronization among the eNB's uplink OFDM symbol reception and decoding start timing, UE #1's uplink OFDM symbol reception timing, and UE #2's uplink OFDM symbol reception timing as denoted by reference numbers411,413, and415. In the uplink timing synchronization procedure, the eNB transmits Timing Advance (TA) information to the UEs to notify of the timing adjustment amount. The eNB may transmit the TA information in the Timing Advance Commence MAC Control Element (TAC MAC CE) or in the Random Access Response (RAR) message in response to the random access preamble transmitted by the UE for initial access. If the TA information is received, the UE starts a time alignment timer (timeAlignmentTimer or TAT). The TAT is a timer for verifying the validity of the TA. The TA is valid before the expiration of the TAT, and the validity of the TA is not guaranteed after the expiration of the TAT. If the additional TA information is received afterward, the TAT restarts and, if the TAT expires, it is regarded that the TA information received from the eNB after the expiration of the TAT is invalid so as to set the uplink communication with the eNB. By acquiring the synchronization among the transmission timings as described above, it is possible to maintain the orthogonality between the uplink symbols of the UE #1 and UE #2 such that the eNB may decode the uplink symbols from the UE #1 and UE #2 at the timings401and403successfully. FIG.5is a diagram illustrating an exemplary network environment having network entities operating on primary and secondary carriers at different locations in a system according to an exemplary embodiment of the present invention supporting carrier aggregation. Referring toFIG.5, the Remote Radio Heads (RRHs)503operating on frequency band F2507are around the macro eNB501using frequency band F1505. If the UE is connected to both the macro eNB and RRH and located near the RRH and if the UE transmits signal via the RRH, the signal may reach the RRH at an appropriate timing even when there is a little delay due to the short distance. However, the signal transmitted to the macro eNB does not reach the macro eNB at appropriate timing due to the long distance. In order to address this issue, the UE operating with aggregated carriers should synchronize multiple uplink transmission timings. There is therefore a need for a method of operating TATs efficiently in association with multiple uplink transmission timings. According to an exemplary embodiment of the present invention, the eNB categorizes the carriers having uplink timings identical or similar among each other into groups to facilitate management. This technique is referred to as Timing Advance Group (TAG). In an exemplary case that one Primary Cell (PCell) (or first cell) and three Secondary Cells (SCells) A, B and C (or second cells) are aggregated, if the PCell and the SCell A have similar uplink timings, they may be categorized into group1while the SCell B and SCell C are categorized into group2. In this case, the eNB transmits the TA information to the group1in the TAC MAC CE or RAR to command uplink timing adjustment such that the UE adjusts uplink timings of both the PCell and SCell A based on the information carried in the TAC MAC CE. Upon receipt of the TA information, the UE starts a TAT for the group1. The TAT is the timer for verifying the validity of the TA information. The uplink data may be transmitted through the carriers (i.e., PCell and SCell A) belonging to the group1before the TAT of the group1expires. If the TAT expires, it is regarded that the TA information is no longer valid such that the UE cannot transmit data on the corresponding carriers before receiving new TA information from the eNB. The TAT of the group including the PCell such as group1in the above example, i.e., the TAT of PCell TAG, is referred to as PTAG TAT. The TAT of the group including no PCell is referred to as STAG TAT. FIG.6is a signaling diagram illustrating signal flows between an eNB and a UE in a method according to an exemplary embodiment of the present invention. Referring toFIG.6, the UE601is connected to the eNB609through only the PCell with the TAT of the PTAG, i.e. TAT #1, at step611. The eNB609instructs the UE to configure carrier aggregation under the assumption that the UE601supports the carrier aggregation at step613. The eNB configures carrier aggregation with the UE, PTAG TAT for a plurality of carriers, information on the SCells to be aggregated, and TAT value per TAG through RRC layer message603so as to configure the PTAG TAT on the plural carriers and set one or more STAG TATs to different values at step615. The TATs of the respective TAG may be set to the same value or different values. The RRC layer message may be the RRC CONNECTION RECONFIGURATION (RRCConnectionReconfiguration) message. The RRC layer entity of the UE which has received the RRC layer message transmits an acknowledgement message at step617. The acknowledgement message may be the RRC CONNECTION RECONFIGURATION Complete (RRCConnectionReconfigurationComplete) message. In order to use a SCell, the eNB transmits an activation/deactivation control message (activation/deactivation MAC CE message to the UE on the MAC layer605to notify the UE of the activation/deactivation of the SCell at step621. In a case of the PCell, the UE is in the connected state to the eNB such that step621may be omitted. In a case where the SCells do not belong to the PTAG even though they have received the Activation/deactivation MAC CE to be activated (i.e., the SCells belonging to an STAG), if the uplink synchronization is not acquired as described with reference toFIG.4(or TAT is not running), there is a need for a process of uplink timing synchronization. For this purpose, the eNB transmits a command (i.e., PDCCH order) to request the UE to transmit a random access preamble through a certain cell at step623. Upon receipt of the PDCCH order, the PHY layer607of the UE instructs the MAC layer605to start random access at step624. The MAC layer of the UE instructs the PHY layer607to transmit Random Access Preamble at step625, such that the PHY layer607of the UE transmits the Random Access Preamble to the eNB through a specific cell at step626. If the random access preamble is received, the eNB determines the transmission timing adjustment amount according to the arrival timing of the preamble and then transmits a Random Access Response (RAR) carrying the TA information to the UE at step627. Upon receipt of the RAR, the UE starts the TAT of the corresponding STAG, i.e., TAT #2 inFIG.6at step629. Accordingly, the HARQ ACK/NACK corresponding to the data transmitted through the SCells belonging to the STAG is delivered from the MAC layer605to the PHY layer607(C1, C2, and C3 inFIG.6), and the PHY layer607transmits the HARQ ACK/NACK to the eNB (C1-1, C2-1, and C3-1 ofFIG.6). Afterward, the STAG TAT (i.e., TAT #2) expires at a certain time at step631. In this case, the UE may operate as follows. The UE stops transmission of Uplink Shared Channel (UL-SCH) for the cells of TAG to which the corresponding SCell belongs. Since the TAT information used by the STAG is determined to be no longer valid, the UE stops uplink transmission through SCells belonging to the corresponding STAG. The HARQ ACK/NACK corresponding to the data transmitted/received through the PCell or SCell is delivered to the PHY layer607(C4, C5, and C6 ofFIG.6), and the PHY layer607transmits the HARQ ACK/NACK to the eNB (C4-1, C5-1, and C6-1 ofFIG.6). Although the timing information of the TAG to which the SCell belongs is not valid, the HARQ ACK/NACK is still transmitted through Physical Uplink Control Channel (PUCCH) through the PCell. Although not depicted in the drawing, since the HARQ ACK/NACK information is not delivered to the PHY layer, the following options may be considered for determination. Option 1: The UE suspends delivering HARQ ACK/NACK information to the PHY layer only when PTAG TAT has expired (643). Option 2: The UE suspends delivering HARQ ACK/NACK information to the PHY layer when all of the TATs have expired (645). Option 3: The UE suspends delivering the HARQ ACK/NACK information to the PHY layer when the PTAG TAT has expired and no uplink data allocation information exist at the corresponding Transmission Time Interval (TTI) (647). This is because the HARQ ACK/NACK information may be transmitted in the uplink data region when the resource is allocated in the uplink data region. Relevant to the delivery of PUCCH/Sounding Reference Signal (SRS) release information to the RRC layer, the PUCCH/SRS may be handled according to any of the exemplary embodiments described below. Embodiment 1: The MAC layer605delivers PUSCH/SRS release indication with TAG ID (ID of STAG corresponding to TAT #2 in this embodiment) (633). Upon receipt of the PUSCH/SRS release information, the RRC layer releases the SRS resource for transmission through the SCell belonging to the corresponding STAG with the exception of the SRS of the PCell and SCell not belonging to the corresponding TAG (A2 inFIG.6). Embodiment 2: The MAC layer605suspends delivery of the PUCCH/SRS release indication (B1 inFIG.6). Embodiment 3: Although not depicted in the drawing, the PUCCH/SRS release indication is delivered to the RRC layer when all of the TATs including the STAG TAT (TAT #2) have expired. Afterward, the eNB performs random access process triggered by the PDCCH order (see steps623,625, and627) at step641and restarts the TAT #2 at step643. While the TAT #2 corresponding to the STAG is running at step645, the MAC layer605delivers the generated HARQ ACK/NACK to the PHY layer607(C7, C8, and C9 ofFIG.6) in the same manner as C1, C2, and C3 ofFIG.6, and the PHY layer607transmits the HARQ ACK/NACK to the eNB (C7-1, C8-1, and C901 ofFIG.6). Afterward, the TAT #1 as TAT of the PTAG expires at step647. At this time, the UE performs operations as follows. The UE suspends uplink transmission through the cells of the TAG to which the PCell belongs. The transmission is suspended because the timing information of the TAG to which the PCell belongs is determined to be no longer valid. The UE discards all the data in the HARQ buffer (i.e., flushes the buffer). The UE stops delivery of the HARQ ACK/NACK to the PHY layer607(see embodiment 1, and following embodiments 2 and 3) (C10, C11, and C12). The HARQ ACK/NACK corresponding to downlink data is transmitted through PDCCH and this is in the meaning of the suspension of the uplink transmission through the PCell since the PUCCH is always transmitted through the PCell. Although not depicted in the drawing, the information may be delivered to the PHY layer607; this may be determined in consideration of the following options. Embodiment 2: The UE suspends delivery of the HARQ ACK/NACK information to the PHY layer607when all the TATs including PTAG TAT have expired. Embodiment 3: The UE suspends delivery of the HARQ ACK/NACK information to the PHY layer607when the PTAG TAT has expired and there is on uplink data allocation information at the corresponding TTI (647). This is because the HARQ ACK/NACK may be transmitted in the uplink data region of the SCell belonging to the STAG when the resource is located in the uplink data region. The UE suspends PUCCH transmission; suspends SRS transmission through the cells of the TAG to which the PCell belongs with the exception of the SRS transmission through the SCell not belonging to the corresponding TAG (see following embodiment 2); or suspends all of the SRS transmissions (see following embodiment 1). The PUCCH transmission through PCell is suspended, and since the SRS is configured per cell, only the PUCCH of the PCell and SRS configured for the PTAG are suspended while others are maintained. The following options may be considered for transmitting the suspension information. Embodiment 1: The entire PUCCH/SRS release indication is delivered to the RRC layer (B2 inFIG.6). Upon receipt of the PUCCH/SRS release information, the RRC layer releases the resources allocated for Channel Quality Indicators (CQI), SRS, and Service Request (SR) of all the cells. Embodiment 2: The PUCCH/SRS release indication with the TAG IDs of respective TAGs is delivered to the RRC layer (A3 ofFIG.6). Upon receipt of the PUCCH/SRS release indication, the RRC layer release the resources allocated for CQI, SRS, and SR of the cell belonging to the PTAG (A4 ofFIG.6). Embodiment 3: The UE delivers the PUCCH/SRS release indication to the RRC layer when all of the TATs including the TATs of PTAG expire. Although various exemplary embodiments related to the HARQ ACK/NACK information and PUCCH/SRS release indication delivery have been proposed, these exemplary embodiments related to delivery of the PUCCH/SRS release indication and HARQ ACK/NACK information operate separately with the possibility of available combinations (i.e., all available combinations of the embodiments associated with the PTAG and STAG. For example, the HARQ ACK/NACK-related embodiments 1, 2, and 3 and PUCCH/SRS release-related embodiments 1, 2, and 3 may be implemented in every combination and are not limited to the combinations described above). FIG.7is a flowchart illustrating a UE procedure of a method according to a first exemplary embodiment of the present invention. Referring toFIG.7, the UE receives an RRC message carrying the carrier configuration for aggregation, TAG configuration, and TAT values of the respective TAGs from the eNB at step703. If an RAR is received through a certain SCell activated by the eNB (the PCell activation is not necessary in PCell) or if a TAC MAC CE is received but the TAT of the TAG to which the corresponding SCell belongs is not running, the UE starts (executes) the TAT at step705. If it is determined that the TAT of the corresponding TAG is running, the UE restarts (re-executes) the TAT. If the TAT expires at step707, the UE determines whether the TAT is the PTAG TAT or STAG TAT at step709. In embodiment 1 of the present invention, if the TAT is the PTAG TAT, the UE spends uplink data transmission in the PTAG and delivery of the HARQ ACK/NACK information to the PHY layer607, delivers the PUCCH/SRS release indication to the RRC layer, and discards the packets in the UE's HARQ buffer at step711. If the TAT is the STAG TAT, the UE suspends the uplink data transmission through the cell belonging to the corresponding STAG but maintains the delivery of the HARQ ACK/NACK information to the PHY layer607even when the TAT expires, and suspends the delivery of the PUCCH/SRS release indication to the RRC layer at step713. FIG.8is a flowchart illustrating a UE procedure of a method according to a second exemplary embodiment of the present invention. Referring toFIG.8, the UE receives an RRC message carrying the carrier configuration for aggregation, TAG configuration, and TAT values of the respective TAGs from the eNB at step803. If an RAR is received through a certain SCell activated by the eNB (the PCell activation is not necessary in PCell) or if a TAC MAC CE is received but the TAT of the TAG to which the corresponding SCell belongs is not running, the UE starts (executes) the TAT at step805. If it is determined that the TAT of the corresponding TAG is running, the UE restarts (re-executes) the TAT. When the TAT expires at step807, the UE determines whether the TAT is the PTAG TAT or STAG TAT at step809. In embodiment 2-1 of the present invention, regardless of whether the TAT is PTAG TAT or STAG TAT, the UE suspends uplink data transmission through the cell belonging to the corresponding TAG, maintains delivery of the HARQ ACK/NACK information as long as at least one TAT is running, and, when all of the TATs expire, delivers the PUCCH/SRS resource release indication to the RRC layer at steps811and813. In embodiment 2-2 of the present invention, if the TAT is the PTAG TAT, the UE maintains delivery of the HARQ ACK/NACK information to the physical layer until all of the TATs expire and, when all of the TATs expire, delivers the PUCCH/SRS release indication to the RRC at step811. However, if the TAT is the STAG TAT, the UE sends the eNB an RRC message to notify the TAT expiration or an RRC message with TAG ID to stop SRS transmission through the cell of the corresponding TAG at step813. FIG.9is a flowchart illustrating a UE procedure of the method according to a third exemplary embodiment of the present invention. Referring toFIG.9, the UE receives an RRC message carrying the carrier configuration for aggregation, TAG configuration, and TAT values of the respective TAGs from the eNB at step903. If an RAR is received through a certain SCell activated by the eNB (the PCell activation is not necessary in PCell) or if a TAC MAC CE is received but the TAT of the TAG to which the corresponding SCell belongs is not running, the UE starts (executes) the TAT at step905. If it is determined that the TAT of the corresponding TAG is running, the UE restarts (re-executes) the TAT. When the TAT expires at step907, the UE determines whether the TAT is the PTAG TAT or STAG TAT at step909. In embodiment 3 of the present invention, if the TAT is PTAG TAT, the UE suspends uplink data transmission in the corresponding TAG, delivers the HARQ ACK/NACK information to the PHY layer607only when the uplink resource is allocated in other TAG of which a TAT is running, delivers the PUCCH/SRS release indication with the TAG ID to the RRC layer per TAG, and discards the data buffered in all of the HARQ buffers at step911. Upon receipt of the information, the RRC layer stops transmission of SR, CQI, and SRS on the PUCCH. If the TAT is the STAG TAT, the UE maintains the delivery of the HARQ ACK/NACK information to the PHY layer after the expiration of the TAT and delivers the SRS release indication with TAG ID to the RRC layer per TAG such that the RRC layer stops SRS transmission through the cell belonging to the corresponding STAG at step913. FIG.10is a flowchart illustrating an eNB procedure of a method according to an exemplary embodiment of the present invention. Referring toFIG.10, the eNB transmits an RRC message carrying the carrier configuration for carrier aggregation, tag configuration, and TAT values of respective TAGs at step1003. The TAT values may be different from each other or be identical with each other. In order to activate a certain SCell, the eNB transmits an Activation/Deactivation MAC CE to the UE at step1005. Step1005is not necessary for the PCell. The eNB transmits a PDCCH order to the UE to request for the transmission of preamble through a certain SCell at step1007. If a preamble is received from the UE, the eNB analyzes the reception timing to transmit an RAR message including the timing adjustment information at step1009. When the STAG TAT expiration is notified to the eNB as shown in the embodiment 2-2 ofFIG.8, the eNB receives the RRC message informing of the STAG TAT expiration from the UE at step1011. The eNB may perform the procedure for deactivating the corresponding SCell or releases the resource allocated to the SCell by transmitting an RRC message at step1013. FIG.11is a block diagram illustrating a configuration of the UE according to an exemplary embodiment of the present invention. Referring toFIG.11, the UE transmits/receives data generated by a higher layer device1105and control messages generated by a control message processor1107. When transmitting control signal and/or data to the eNB, the UE multiplexes the control signal and/or data via the multiplexer/demultiplexer1103under the control of the controller1109. When receiving control signal and/or data from the eNB, the UE receives the physical signal via the transceiver1101, demultiplexes the received signal via the multiplexer/demultiplexer1103, and delivers the demultiplexed signal to the corresponding higher layer device1105or control message processor1107. When the TAC MAC CE is received, the control message processor1107notifies the carrier aggregation processor1111of the TAC MAC CE to start (restart) the TAT of the corresponding TAG. If the TAT of the corresponding TAG expires, the UE determines whether the expired TAT is PTAG TAT or STAG TAT and then commands the controller1109to execute the operations as described with reference toFIG.5. Although the description is directed to the case where the function blocks constituting the UE are responsible to the respective functions, exemplary embodiments of the present invention are not limited thereto. For example, the functions of the control message processor1107may be performed by the controller1109. In this case, the controller1109starts the first TAT for the first group including the first cell and, when the TA information on the second group not including the first cell is received, starts the second TAT. The controller1109determines transmission of at least one of HARQ ACK/NACK message, physical uplink control channel, and sounding reference signal according to the operation or expiration of the first or second TAT. According to an exemplary embodiment of the present invention, the controller1109may control transmission of the HARQ ACK/NACK corresponding to the data transmitted through the second cells belonging to the second group to the eNB when the second TAT starts. According to an exemplary embodiment of the present invention, the controller1109may also control to stop transmission of the uplink shared channel through the second cells belonging to the second group when the second TAT expires. According to an exemplary embodiment of the present invention, the controller1019may control to stop transmission of the uplink shared channel through the second cells belonging to the second group when the second TAT expires. According to an exemplary embodiment of the present invention, the controller1109may control to transmit a message for suspending transmission of at least one of the physical uplink control channel with ID of the second group and sounding reference signal. According to an exemplary embodiment of the present invention, the controller1109may control to suspend the transmission of at least one of the uplink control channel with the ID of the second group and sounding reference signal when the second TAT expires. According to an exemplary embodiment of the present invention, the controller1109may control to suspend uplink transmission through the cells belonging to the first group when the first TAT expires. According to an exemplary embodiment of the present invention, the controller1109may control to discard the data buffered in the HARQ buffer when the first TAT expires. According to an exemplary embodiment of the present invention, the controller1109may control to suspend the transmission of the HARQ ACK/NACK when the first TAT expires. According to an exemplary embodiment of the present invention, the controller1109may control to suspend the transmission of the physical uplink control channel when the first TAT expires. FIG.12is a block diagram illustrating a configuration of an eNB according to an exemplary embodiment of the present invention. Referring toFIG.12, the eNB transmits/receives data generated by a higher layer device1205and control messages generated by a control message generator1207. In transmission mode, the data is multiplexed by the multiplexer/demultiplexer1203and then transmitted through the transceiver1201under the control of the controller1209. In reception mode, the physical signal is received by the transceiver1201, demultiplexed by the multiplexer/demultiplexer1203, and then delivered to the higher layer device1205or the control message processor1207according to the message information under the control of the controller1209. The carrier aggregation processor1211configures the carrier aggregation and TAT value per TAG for a certain UE. The control message processor1207generates an RRC message for transmission to the UE. In case of activating a SCell for the corresponding UE, the eNB transmits a TAC MAC CE via the control message processer1207, receives a preamble form the UE in response to the PDCCH order, and generates an RAR message including the timing adjustment information to the UE. In case of transmitting the RRC message when the STAG TAT for a certain UE expires as described with reference toFIG.8, the eNB receives the RRC message via the control message processor1207, determines whether the carrier aggregation processor1211should perform addition operation (e.g., deactivation of the SCells belonging to the corresponding TAG), and commands the corresponding UE to deactivate the SCells belonging to the corresponding TAG. As described above, a method according to an exemplary embodiment of the present invention defines the detailed UE's operations with multiple uplink timings in the system supporting carrier aggregation so as to avoid malfunction of the system and improve operation reliability. A method according to an exemplary embodiment of the present invention is capable of managing multiple uplink timings without error by defining the UE operations in detail in the system operating with a plurality of time alignment timers. While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents. | 34,875 |
11943722 | While the invention is susceptible to various modifications and alternative forms, specific aspects thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. DETAILED DESCRIPTION OF THE ASPECTS Acronyms The following acronyms are used in the present Patent Application: UE: User Equipment BS: Base Station ENB: eNodeB (Base Station) GNB: gNodeB (Base Station) LTE: Long Term Evolution UMTS: Universal Mobile Telecommunications System RAT: Radio Access Technology RAN: Radio Access Network E-UTRAN: Evolved UMTS Terrestrial RAN CN: Core Network EPC: Evolved Packet Core MME: Mobile Management Entity HSS: Home Subscriber Server SGW: Serving Gateway PS: Packet-Switched CS: Circuit-Switched EPS: Evolved Packet-Switched System RRC: Radio Resource Control IE: Information Element QoS: Quality of Service QoE: Quality of Experience TFT: Traffic Flow Template RSVP: Resource ReSerVation Protocol API: Application programming interface Terms The following is a glossary of terms used in the present application: Memory Medium—Any of various types of memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks104, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may comprise other types of memory as well or combinations thereof. In addition, the memory medium may be located in a first computer in which the programs are executed, or may be located in a second different computer which connects to the first computer over a network, such as the Internet. In the latter instance, the second computer may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computers that are connected over a network. Computer System—any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term “computer system” can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium. User Equipment (UE) (or “UE Device”)—any of various types of computer systems or devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile telephones or smart phones, tablet computers, portable gaming devices, wearable devices (e.g., smart watch, smart glasses), laptops, PDAs, portable Internet devices, music players, data storage devices, other handheld devices, automobiles and/or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication. Processing Element—refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above. FIGS.1and2—Communication System FIG.1illustrates a simplified example wireless communication system, according to some aspects. It is noted that the system ofFIG.1is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired. As shown, the example wireless communication system includes a base station102which communicates over a transmission medium with one or more user devices106A,106B, etc., through106N. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the user devices106are referred to as UEs or UE devices. The base station (BS)102may be a base transceiver station (BTS) or cell site (a “cellular base station”), and may include hardware that enables wireless communication with the UEs106A through106N. The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station102and the UEs106may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), 6G, HSPA, 3GPP2 CDMA2000 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station102is implemented in the context of LTE, it may alternately be referred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station102is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’. As shown, the base station102may also be equipped to communicate with a network100(e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station102may facilitate communication between the user devices and/or between the user devices and the network100. In particular, the cellular base station102may provide UEs106with various telecommunication capabilities, such as voice, SMS and/or data services. Base station102and other similar base stations operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or more cellular communication standards. Thus, while base station102may act as a “serving cell” for UEs106A-N as illustrated inFIG.1, each UE106may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by other base stations102B-N), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and/or between user devices and the network100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and/or cells which provide any of various other granularities of service area size. Other configurations are also possible. In some aspects, base station102may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some aspects, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs. Note that a UE106may be capable of communicating using multiple wireless communication standards. For example, the UE106may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE106may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M/H), and/or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible. FIG.2illustrates user equipment106(e.g., one of the devices106A through106N) in communication with a base station102, according to some aspects. The UE106may be a device with cellular communication capability such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device. The UE106may include a processor that is configured to execute program instructions stored in memory. The UE106may perform any of the method aspects described herein by executing such stored instructions. Alternatively, or in addition, the UE106may include a programmable hardware clement such as an FPGA (field-programmable gate array) that is configured to perform any of the method aspects described herein, or any portion of any of the method aspects described herein. The UE106may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some aspects, the UE106may be configured to communicate using, for example, CDMA2000 (1xRTT/1xEV-DO/HRPD/eHRPD) or LTE using a single shared radio and/or GSM or LTE using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for multiple-input, multiple-output or “MIMO”) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE106may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above. In some aspects, the UE106may include any number of antennas and may be configured to use the antennas to transmit and/or receive directional wireless signals (e.g., beams). Similarly, the BS102may also include any number of antennas and may be configured to use the antennas to transmit and/or receive directional wireless signals (e.g., beams). To receive and/or transmit such directional signals, the antennas of the UE106and/or BS102may be configured to apply different “weight” to different antennas. The process of applying these different weights may be referred to as “precoding”. In some aspects, the UE106may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE106may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE106might include a shared radio for communicating using either of LTE or 5G NR (or LTE or 1xRTT or LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible. FIG.3—Block Diagram of a UE FIG.3illustrates an example simplified block diagram of a communication device106, according to some aspects. It is noted that the block diagram of the communication device ofFIG.3is only one example of a possible communication device. According to aspects, communication device106may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices. As shown, the communication device106may include a set of components300configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components300may be implemented as separate components or groups of components for the various purposes. The set of components300may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device106. For example, the communication device106may include various types of memory (e.g., including NAND flash310), an input/output interface such as connector I/F320(e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display360, which may be integrated with or external to the communication device106, and cellular communication circuitry330such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry329(e.g., Bluetooth™ and WLAN circuitry). In some aspects, communication device106may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet. The cellular communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas335and336as shown. The short to medium range wireless communication circuitry329may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas337and338as shown. Alternatively, the short to medium range wireless communication circuitry329may couple (e.g., communicatively; directly or indirectly) to the antennas335and336in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas337and338. The short to medium range wireless communication circuitry329and/or cellular communication circuitry330may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration. In some aspects, as further described below, cellular communication circuitry330may include dedicated receive chains (including and/or coupled to, e.g., communicatively, directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some aspects, cellular communication circuitry330may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain. The communication device106may also include and/or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display360(which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display), a mouse, a microphone and/or speakers, one or more cameras, one or more buttons, and/or any of various other elements capable of providing information to a user and/or receiving or interpreting user input. The communication device106may further include one or more smart cards345that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards345. As shown, the SOC300may include processor(s)302, which may execute program instructions for the communication device106and display circuitry304, which may perform graphics processing and provide display signals to the display360. The processor(s)302may also be coupled to memory management unit (MMU)340, which may be configured to receive addresses from the processor(s)302and translate those addresses to locations in memory (e.g., memory306, read only memory (ROM)350, NAND flash memory310) and/or to other circuits or devices, such as the display circuitry304, short range wireless communication circuitry229, cellular communication circuitry330, connector I/F320, and/or display360. The MMU340may be configured to perform memory protection and page table translation or set up. In some aspects, the MMU340may be included as a portion of the processor(s)302. As noted above, the communication device106may be configured to communicate using wireless and/or wired communication circuitry. The communication device106may be configured to transmit a request to attach to a first network node operating according to the first RAT and transmit an indication that the wireless device is capable of maintaining substantially concurrent connections with the first network node and a second network node that operates according to the second RAT. The wireless device may also be configured transmit a request to attach to the second network node. The request may include an indication that the wireless device is capable of maintaining substantially concurrent connections with the first and second network nodes. Further, the wireless device may be configured to receive an indication that dual connectivity (DC) with the first and second network nodes has been established. As described herein, the communication device106may include hardware and software components for implementing features for using multiplexing to perform transmissions according to multiple radio access technologies in the same frequency carrier (e.g., and/or multiple frequency carriers), as well as the various other techniques described herein. The processor302of the communication device106may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor302may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor302of the communication device106, in conjunction with one or more of the other components300,304,306,310,320,329,330,340,345,350,360may be configured to implement part or all of the features described herein. In addition, as described herein, processor302may include one or more processing elements. Thus, processor302may include one or more integrated circuits (ICs) that are configured to perform the functions of processor302. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)302. Further, as described herein, cellular communication circuitry330and short range wireless communication circuitry329may each include one or more processing elements and/or processors. In other words, one or more processing elements or processors may be included in cellular communication circuitry330and, similarly, one or more processing elements or processors may be included in short range wireless communication circuitry329. Thus, cellular communication circuitry330may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry330. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry330. Similarly, the short range wireless communication circuitry329may include one or more ICs that are configured to perform the functions of short range wireless communication circuitry329. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short range wireless communication circuitry329. FIG.4—Block Diagram of a Base Station FIG.4illustrates an example block diagram of a base station102, according to some aspects. It is noted that the base station ofFIG.4is merely one example of a possible base station. As shown, the base station102may include processor(s)404which may execute program instructions for the base station102. The processor(s)404may also be coupled to memory management unit (MMU)440, which may be configured to receive addresses from the processor(s)404and translate those addresses to locations in memory (e.g., memory460and read only memory (ROM)450) or to other circuits or devices. The base station102may include at least one network port470. The network port470may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices106, access to the telephone network as described above inFIGS.1and2. The network port470(or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices106. In some cases, the network port470may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider). In some aspects, base station102may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such aspects, base station102may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, base station102may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs. The base station102may include at least one antenna434, and possibly multiple antennas. The radio430and at least one antenna434may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices106. The antenna434may communicate with the radio430via communication chain432. Communication chain432may be a receive chain, a transmit chain or both. The radio430may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc. The base station102may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station102may include multiple radios, which may enable the base station102to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station102may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station102may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station102may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.). As described further subsequently herein, the BS102may include hardware and software components for implementing or supporting implementation of features described herein. The processor404of the base station102may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor404may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor404of the BS102, in conjunction with one or more of the other components430,432,434,440,450,460,470may be configured to implement or support implementation of part or all of the features described herein. In addition, as described herein, processor(s)404may include one or more processing elements. Thus, processor(s)404may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s)404. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)404. Further, as described herein, radio430may include one or more processing elements. Thus, radio430may include one or more integrated circuits (ICs) that are configured to perform the functions of radio430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio430. FIG.5—Block Diagram of Cellular Communication Circuitry FIG.5illustrates an example simplified block diagram of cellular communication circuitry, according to some aspects. It is noted that the block diagram of the cellular communication circuitry ofFIG.5is only one example of a possible cellular communication circuit; other circuits, such as circuits including or coupled to sufficient antennas for different RATs to perform uplink activities using separate antennas, are also possible. According to aspects, cellular communication circuitry330may be included in a communication device, such as communication device106described above. As noted above, communication device106may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices. The cellular communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas335a-band336as shown (inFIG.3). In some aspects, cellular communication circuitry330may include dedicated receive chains (including and/or coupled to, e.g., communicatively, directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown inFIG.5, cellular communication circuitry330may include a modem510and a modem520. Modem510may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem520may be configured for communications according to a second RAT, e.g., such as 5G NR. As shown, modem510may include one or more processors512and a memory516in communication with processors512. Modem510may be in communication with a radio frequency (RF) front end530. RF front end530may include circuitry for transmitting and receiving radio signals. For example, RF front end530may include receive circuitry (RX)532and transmit circuitry (TX)534. In some aspects, receive circuitry532may be in communication with downlink (DL) front end550, which may include circuitry for receiving radio signals via antenna335a. Similarly, modem520may include one or more processors522and a memory526in communication with processors522. Modem520may be in communication with an RF front end540. RF front end540may include circuitry for transmitting and receiving radio signals. For example, RF front end540may include receive circuitry542and transmit circuitry544. In some aspects, receive circuitry542may be in communication with DL front end560, which may include circuitry for receiving radio signals via antenna335b. In some aspects, a switch570may couple transmit circuitry534to uplink (UL) front end572. In addition, switch570may couple transmit circuitry544to UL front end572. UL front end572may include circuitry for transmitting radio signals via antenna336. Thus, when cellular communication circuitry330receives instructions to transmit according to the first RAT (e.g., as supported via modem510), switch570may be switched to a first state that allows modem510to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry534and UL front end572). Similarly, when cellular communication circuitry330receives instructions to transmit according to the second RAT (e.g., as supported via modem520), switch570may be switched to a second state that allows modem520to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry544and UL front end572). In some aspects, the cellular communication circuitry330may be configured to transmit, via the first modem while the switch is in the first state, a request to attach to a first network node operating according to the first RAT and transmit, via the first modem while the switch is in a first state, an indication that the wireless device is capable of maintaining substantially concurrent connections with the first network node and a second network node that operates according to the second RAT. The wireless device may also be configured transmit, via the second radio while the switch is in a second state, a request to attach to the second network node. The request may include an indication that the wireless device is capable of maintaining substantially concurrent connections with the first and second network nodes. Further, the wireless device may be configured to receive, via the first radio, an indication that dual connectivity with the first and second network nodes has been established. As described herein, the modem510may include hardware and software components for implementing features for using multiplexing to perform transmissions according to multiple radio access technologies in the same frequency carrier, as well as the various other techniques described herein. The processors512may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor512may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor512, in conjunction with one or more of the other components530,532,534,550,570,572,335and336may be configured to implement part or all of the features described herein. In some aspects, processor(s)512,522, etc. may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor(s)512,522, etc. may be configured as a programmable hardware element, such as an FPGA, or as an ASIC, or a combination thereof. In addition, as described herein, processor(s)512,522, etc. may include one or more processing elements. Thus, processor(s)512,522, etc. may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s)512,522, etc. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)512,522, etc. As described herein, the modem520may include hardware and software components for implementing features for using multiplexing to perform transmissions according to multiple radio access technologies in the same frequency carrier, as well as the various other techniques described herein. The processors522may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor522may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor522, in conjunction with one or more of the other components540,542,544,550,570,572,335and336may be configured to implement part or all of the features described herein. FIGS.6-7—5G NR Architecture In some implementations, fifth generation (5G) wireless communication will initially be deployed concurrently with other wireless communication standards (e.g., LTE). For example, whereasFIG.6illustrates a possible standalone (SA) implementation of a next generation core (NGC) network606and 5G NR base station (e.g., gNB604), dual connectivity between LTE and 5G new radio (5G NR or NR), such as in accordance with the exemplary non-standalone (NSA) architecture illustrated inFIG.7, has been specified as part of the initial deployment of NR. Thus, as illustrated inFIG.7, evolved packet core (EPC) network600may continue to communicate with current LTE base stations (e.g., eNB602). In addition, eNB602may be in communication with a 5G NR base station (e.g., gNB604) and may pass data between the EPC network600and gNB604. In some instances, the gNB604may also have at least a user plane reference point with EPC network600. Thus, EPC network600may be used (or reused) and gNB604may serve as extra capacity for UEs, e.g., for providing increased downlink throughput to UEs. In other words, LTE may be used for control plane signaling and NR may be used for user plane signaling. Thus, LTE may be used to establish connections to the network and NR may be used for data services. As will be appreciated, numerous other non-standalone architecture variants are possible. FIG.8—Wireless Communication System FIG.8illustrates an example simplified portion of a wireless communication system. The UE106may be in communication with a wireless network, e.g., a radio access network (RAN), which may include one or more base stations (BS)102and may provide connection to a core network (CN)100, such as an evolved packet core (EPC). The base station102may be an eNodeB and/or gNB (e.g., a 5G or NR base station) or other type of base station. The UE106may communicate in a wireless manner with the base station102. In turn, the base station102may be coupled to a core network100. As shown, the CN100may include a mobility management entity (MME)322, a home subscriber server (HSS)324, and a serving gateway (SGW)326. The CN100may also include various other devices known to those skilled in the art. Operations described herein as being performed by the wireless network may be performed by one or more of the network devices shown inFIG.8, such as one or more of the base station102or the CN100, and/or the MME322, HSS324, or SGW326in the CN100, among other possible devices. Operations described herein as being performed by the radio access network (RAN) may be performed, for example, by the base station102, or by other components of the RAN usable to connect the UE and the CN. FIG.9—Example Cellular Environment FIG.9illustrates an example cellular environment where multiple UEs are within the range of a macro cell or an LTE cell (e.g., which may be part of a master cell group (MCG) of one or more UEs). Within the macro cell, multiple smaller cells (e.g., 5G or NR cells) may be available for providing connectivity to UE(s). The smaller cells may be secondary cells or part of a secondary cell group (SCG) of one or more UEs. When a UE is configured with a SCG, the UE may maintain connectivity to both the MCG and the SCG. For example, for the MCG, the primary cell (PCell) may always be activated. In the SCG, the primary secondary cell (PSCell) may be activated or deactivated. In some aspects, the PSCell may be in an activated state or a deactivated state, e.g., based on signaling between the network and the UE. FIG.10—Timing Advance FIG.10is a diagram illustrating the effects of timing advance. As shown in the Figure, UEs1,2, and3are located at different distances from the gNB and may have different pathlosses, environments, etc. when communicating with the gNB. If these UEs transmitted without any timing advance adjustments, they arrive at the gNB at different times, as shown on the left side “Without TA”. Accordingly, by providing timing advance information (e.g., parameters, indications, values, etc.) to these UEs, each UE can transmit at different times, allowing the gNB to receive the transmissions at approximately the same time. By aligning the reception of the UE uplink transmissions, the gNB is able to successfully decode the transmitted data from all three UEs. In this example, UE2transmits sooner than UE1, which transmits sooner than UE3due to UE2being further away from the gNB than UE1, which is in turn further away than UE3. Usually, during random access channel (RACH) attachment, the network (e.g., the gNB) may estimate the timing advance a UE needs to make, so that “all” the receptions from different UEs arrive at the same time at the gNB (as shown inFIG.11). The gNB may then provide the respective timing advance (TA) feedback based on respective uplink transmissions received from each UE. The gNB may also provide periodic TA adjustments based on uplink transmissions, e.g., while each UE is in connected mode and performing (e.g., continuous) respective uplink transmissions. FIG.11—SCG Reactivation FIG.11illustrates an example flow chart for SCG reactivation. Aspects of the method ofFIG.11may be implemented by a wireless device, such as the UE(s)106, in communication with a network, e.g., via one or more base stations (e.g., BS102) as illustrated in and described with respect to the Figures, or more generally in conjunction with any of the computer systems or devices shown in the Figures, among other circuitry, systems, devices, elements, or components shown in the Figures, among other devices, as desired. For example, one or more processors (or processing elements) of the UE (e.g., processor(s)302, baseband processor(s), processor(s) associated with communication circuitry, etc., among various possibilities) may cause the UE to perform some or all of the illustrated method elements. Similarly, one or more processors (or processing elements) of the BS (e.g., processor(s)404, baseband processor(s), processor(s) associated with communication circuitry, etc., among various possibilities) may cause the UE to perform some or all of the illustrated method elements. Note that while at least some elements of the method are described in a manner relating to the use of communication techniques and/or features associated with 3GPP specification documents, such description is not intended to be limiting to the disclosure, and aspects of the method may be used in any suitable wireless communication system, as desired. In various aspects, some of the elements of the methods shown may be performed concurrently, in a different order than shown, may be substituted for by other method elements, or may be omitted. Additional method elements may also be performed as desired. As shown, the method may operate as follows. In1106, the UE1102may be connected to cellular network1104. The UE may be in communication with the network in various different ways and may have established communication according to various techniques, e.g., according to 3GPP standards. In some aspects, the UE may establish communication with one or more cells of an MCG. The UE (e.g., at the direction of the MCG) may also establish communication with one or more cells of an SCG. A primary cell (PCell) of the MCG may be a macro cell (e.g., as show inFIG.9). A primary cell of the SCG (PSCell) may be a small cell and/or a gNB. However, other connections are also envisioned, e.g., where one or more cells of the MCG is a small cell and/or one or more cells of the SCG is a macro cell, as desired. In some aspects, the UE may be communicating with the network while in connected mode. The network may provide TA parameters and/or adjustments to the UE, e.g., based on uplink communication from the UE to the network. Note that there may be different TA parameters used for different cells, e.g., the PCell may indicate one set of TA parameters for communication while the PSCell may indicate a different set of TA parameters for communication. In general, the TA parameters discussed herein may primarily apply to cell(s) of the SCG, although these aspects may also be applied to cell(s) of the MCG, as appropriate. In1108, a secondary cell (e.g., in an SCG) and/or the SCG may be deactivated for a UE. For example, the UE may be connected to a primary cell (e.g., and potentially other cells) in the MCG as well as a primary cell (e.g., and potentially other cells) in the SCG. One or more cells (or all of the cells) of the SCG may be put in a deactivated state, e.g., based on message(s) received from the network (e.g., from the MCG, the SCG, and/or another node of the network). Thus, one or more SCG deactivation messages may be received from cell(s) in the MCG and/or cell(s) in the SCG. For example, the PSCell may provide an SCG deactivation indication (e.g., via one or more messages) to the UE, e.g., via one or more control channels. Alternatively, the PCell may provide an SCG deactivation indication (e.g., via one or more messages) to the UE, e.g., via one or more control channels. In the control plane, for the deactivated state of SCG, uplink communication with the PSCell may not be permitted. In some aspects, all of the SCells in the SCG (or the SCG itself) may be deactivated. In some aspects, there may not be any radio resource control (RRC) signaling to the UE on the SCG. However, the UE may still be expected to perform radio resource management (RRM), e.g., including signal quality measurements of cell(s) in the SCG. Additionally, the UE may still remain in the RRC connected state (e.g., when communicating with cell(s) in the MCG). Thus, the UE may be configured to continue to perform communication with the MCG while the SCG is in the deactivated state, as desired. In the user plane, according to some aspects, the UE may not monitor PDCCH on the PSCell, which results in no uplink allocations or uplink grants. Thus, in some aspects, in the SCG deactivated state, the UE may not be required to transmit PUSCH and PUSCH in the uplink for as long as the UE is in SCG deactivated state. As noted above, TA parameters may be established and/or adjusted based on uplink communications. Accordingly, because the UE may not perform uplink communication with cell(s) of the SCG while in the SCG deactivated state, the TA parameters may not be updated or adjusted during the period of deactivation. Accordingly, the UE may not know if the previous TA values or parameters are still valid during the deactivated state. Upon reactivation, the UE may determine whether to use the previous TA parameters (e.g., stored prior to deactivation and/or at the time of deactivation) or to initiate a RACH or other process in order to obtain new TA parameters. Thus, in1112and1114, at the transition to the SCG activated state (e.g., from the SCG deactivated state), the UE may determine to whether to use stored TA parameters or to perform a different process, such as RACH, to reestablish synchronization in communicating with cell(s) in the SCG. In some aspects, the UE may attempt to reuse the stored TA parameters and/or avoid RACH process whenever possible. When the UE is able to use the stored TA parameters, the UE may be able to begin communicating much faster than would otherwise be possible using another process, such as RACH. Said another way, the RACH process may take time to reestablish communication (e.g., including TA parameters), which may provide a worse user experience (e.g., a delay in communication) than if the stored TA parameters could be used. Thus, aspects described herein may allow the UE to be able to perform uplink transmission quickly, e.g., without network involvement, for faster SCG activation. As described regardingFIG.9, usually (but not always), the MCG is provided by a macro cell and the SCG is via a small cell (e.g., using greater than 6 GHz spectrum). In some aspects, the UEs TA parameters may not need to be adjusted in small cells, e.g., because the signal propagation delay is not significant between cell edge and center of the cell for small cells. However, due to higher frequencies and/or the higher sub-carrier spacing (SCS), there can be some TA adjustment needed even in small cells, e.g., when using higher SCS such as 60 or 120 kHz SCS, among other possibilities. Additionally, or alternatively, beam switching may also result in an adjustment of TA. In some aspects, the UE may be able to use information from UE activities during SCG deactivation to determine whether to reuse previous TA values. For example, the UE may perform signal quality measurements for the PSCell during the SCG deactivated state, e.g., as part of RRM (e.g., in1110). For example, these signal quality measurements may include measuring reference signals and associated beams to derive the cell quality and/or beam quality. These measurements may be used by the UE to make a decision on whether to reuse previous TA parameters for uplink communication. For example, while the signal strength fluctuates, e.g., due to beams and beam switching, it may reflect the UE's movement to/away from the SCG PSCell (e.g., the gNB base station). For example, a long-term filtered and/or averaged value may be particularly useful in determining the UE's movement to/away from the cell of the SCG. These signal quality measurements may be any of various signal quality measurements, e.g., SINR (signal to interference and noise ratio), SNR (signal to noise ratio), RSRP (reference signal received power), RSRQ (reference signal received quality), RSSI (received signal strength indicator), path loss, BLER (block error rate), and/or any desired signal quality measurement. These measurements may be performed with regard to reference signals transmitted by the SCG (e.g., the PSCell). For example, the cell may transmit CRS (cell specific reference signals), SS (synchronization signals), CSI (channel state information) reference signal (CSI-RS), etc. and the UE may perform measurements of those signals to determine one or more signal quality metric(s), such as those discussed above. Thus, the signal quality measurements could include SS-RSRP, CSI-RSRP, NR-RSSI, CSI-RSSI, SS-RSRQ, CSI-RSRQ, SS-SINR, CSI-SINR, etc. In some aspects, the UE may perform a plurality of measurements over time and may determine a moving average of the signal quality. The moving average may be based on a duration or a number of measurements (e.g., which may be configurable by the network (e.g., the MCG and/or the SCG), specified by 3GPP standards, implemented by the UE, etc.). The moving average may be compared to one or more thresholds to determine whether to use the previous TA parameters (e.g., the last TA parameters used for the SCG prior to deactivation, among other possibilities) or perform a different process. Thus, in some aspects, the UE may use this filtered or long-term averaged signal strength to determine if the TA parameters can be reused or not. For example, the decision may be based on deviation of the measured PSCell signal strength throughout the deactivated SCG state. In some aspects, the baseline signal strength (from which the deviation is measured) may be the last signal quality measurement value at the time of deactivation, the moving average at the time of deactivation, or another value, as desired. FIG.12illustrates an exemplary UE movement over time with corresponding signal quality measurements, average signal-quality measurement over time, and a threshold for determining whether to use the previously stored TA parameters. As shown, while the UE moves between beams, the single signal quality measurements may fall below the threshold, while the average remains above the threshold. In the example ofFIG.12, the UE may reuse the TA parameters because the average signal quality remains above the threshold. As shown in the Figure, the final UE distance from the PSCell is similar to the original distance from the PSCell, so reusing the TA parameters should not cause any signal reception errors and allows the UE to skip RACH or another process to redetermine appropriate TA values. FIG.13illustrates a different example, where the UE is moving away from the PSCell and the average declines to below the threshold. In this example, the UE may need to refresh its TA values, e.g., by performing RACH or another process, as desired. FIG.14illustrates an example where the UE may use two thresholds (e.g., an upper and lower threshold). In this instance, the UE moves closer to the PSCell over time, so the TA parameters may need to be redetermined so that the TA values are appropriate for the new, closer distance to the PSCell. In some aspects, the network may configure various aspects of how and/or when the UE reuses TA parameters. For example, the network (e.g., via communication by the MCG and/or SCG) may configure the UE reuse the TA parameters, e.g., at (e.g., within the SCG deactivation message) or before SCG deactivation. In some cases, the network may provide an indication to use the stored TA parameters irrespective of whether RRM is configured for the SCG. Thus, in some aspects, the network may intend the UE to always use the TA. Such an indication may be applicable in the cases where the SCG is a small cell and there is no adjustment needed between cell-edge and center of the cell. As another possibility, the network may configure the UE to use or not use RRM for the SCG, and the UE may modify its behavior based on whether RRM is configured for the SCG. For example, if the network configures the UE to perform the RRM measurements on the PSCell of the deactivated SCG, the UE may perform the determination of whether to reuse the TA parameters as described herein. Alternatively, if the network does not configure RRM for the SCG, the UE may assume that no TA maintenance is necessary. For example, the UE may simply default to reusing the previously stored TA parameters without performing signal quality measurements. In other words, for the case of small cells, where the network determines that the TA deviation is not large between a UE which as the edge of the cell compared to a UE that is near the cell, the network may configure the UE with no actions to perform if the measured time-averaged signal strength has deviated from the configured thresholds. Alternatively, the UE may interpret the lack of configuration of RRM for the SCG as indicating the TA parameters are not valid and perform a different process at activation (e.g., RACH), which results in refreshing the TA parameters. In some aspects, the network may configure various parameters (e.g., in RRC or other messaging from the MCG, SCG, or another network node) that are used to determine whether to reuse the previously stored TA parameters. Such configuration(s) may be provided at the time of SCG deactivation (e.g., within one or more SCG deactivation messages) or at other times, e.g., prior to SCG deactivation or even during SCG deactivation, as desired. For example, the network may specify the set of reference signals the UE may measure for determining whether to reuse the TA parameters. These reference signals can be the same reference signals the UE uses for RRM purposes, or they can be different, as desired. As another example, the network may also configure the lower signal quality threshold below which the UE will determine that the TA parameter(s) are not valid. Similarly, the network could configure the upper signal quality threshold above which the UE will determine that the TA parameter(s) are not valid. Note that these thresholds may be configured in an absolute or relative basis. In one aspect, the network may configure a “mean deviation” instead of low/high thresholds, and if the UE's signal strength deviates away from its prior signal quality by more than this value in either direction, the UE may consider the TA value as not valid. This aspect may be particularly relevant to the example shown inFIG.14. The network may configure the manner in which the UE averages or filters the signal quality measurements used for determining if the TA parameter(s) are valid. For example, the network may specify the time duration or number of measurements to use for the moving average. The parameters for this averaging may depend on the situation and/or environment of the UE and/or the PSCell. For example, these parameters may depend on the nature of the PSCell (e.g., if it is a small cell), the spectrum used (e.g., greater than 5 GHz), the terrain surrounding the cell, the current or long-term interference associated with the cell, etc. The network may also configure how the UE behaves when the UE determines the TA parameter(s) are not valid. For example, the network may configure the UE to perform RACH upon SCG reactivation if the TA parameters should not be used. As another possibility, the network may configure the UE to inform the network (e.g., using the MCG) that the TA is not valid for the SCG. The UE may be configured to inform the network as soon as it determines this (e.g., during SCG deactivation and prior to SCG reactivation) and/or at other times, such as when the network reactivates SCG. In some aspects, the network (e.g., in response to the UE informing the network that the TA parameters are not valid) may trigger uplink SRS (e.g., with the PSCell) in order to update the TA parameters. When the UE performs uplink SRS during the deactivated state, the UE may then receive TA parameters (e.g., a TA adjustment for the previously stored TA parameters) from the PSCell. The UE can then use these updated TA parameters when SCG reactivation occurs. In some aspects, the network may simply request (e.g., periodically) for the UE to trigger SRS regardless of signal quality measurement results. By performing SRS (e.g., with the PSCell), the UE may be able to perform uplink transmissions and receive TA adjustments even while in the SCG deactivated state. In some aspects, the signal quality measurements may be outside of the threshold(s) for a period temporarily (including the averaged signal quality measurements), but may return to within the threshold(s) by the time the SCG is reactivated. In such cases, the UE may be configured (e.g., by the network) to reuse the stored TA parameters. For example, this behavior may be useful in configurations where signal strength fluctuations are not very prevalent due to topology and the signal strength reflects the location of the UE from the PSCell in a reasonable way. Alternatively, the UE may be configured to not reuse the TA parameters in such a situation, if desired. While various aspects discussed above involve the network configuring the UE in determining whether to reuse TA parameters, the network may not be required to perform such configuration. For example, various ones of those configurations could be specified by standards (e.g., 3GPP standards) and/or otherwise known by the UE and/or the network. Additionally, or alternatively, various ones of these configurations may simply be set by the UE (e.g., statically or dynamically) as desired. In some aspects, the UE may be able to use other information to augment or replace using the signal quality measurements for determining whether to use previously stored TA parameters. For example, the UE may include GPS circuitry that allows it to determine its location. The UE could monitor its GPS location to determine if it is moving and/or is closer or farther away from the PSCell, which may be used to determine whether to reuse the TA parameters. For example, the UE may be aware of the location of the PSCell and may determine a current distance from the PSCell using the UE's current location at the time of reactivation (or before, as desired). In some aspects, the UE may determine to reuse the TA parameter(s) if the distance is within a threshold range. This behavior could be used in addition to or alternatively to the signal quality measurement aspects discussed above. Additionally, the UE may be able to determine whether it has moved significantly based on MCG communications, which may still be active during the SCG deactivation. For example, the UE may monitor the signal quality or TA parameters of the MCG to determine if the UE has moved significantly relative to the PCell. If the UE determines that it has not moved significantly relative to the MCG, it may infer that it has had low mobility and the TA parameter(s) of the PSCell may still be valid. Similar to above, this behavior could be used in addition to or alternatively to the signal quality measurement aspects discussed above. EXEMPLARY ASPECTS The following descriptions provide exemplary aspects corresponding to various aspects described herein, e.g., such as corresponding to the methods ofFIGS.10-16. Example 1. A method of operating a wireless device, comprising: by the wireless device: establishing communication with a first base station of a cellular network, wherein the first base station is comprised in a master cell group (MCG); establishing communication a second base station, wherein the second base station is comprised in a secondary cell group (SCG), wherein said establishing communication with the second base station comprises maintaining one or more timing advance (TA) parameters for performing uplink communication with the second base station; receiving an indication to deactivate the SCG; in response to the indication to deactivate the SCG, storing the one or more TA parameters; performing a plurality of signal quality measurements of the second base station; receiving an indication to activate the SCG; comparing one or more of the plurality of signal quality measurements of the second base station to one or more signal quality thresholds; based on said comparing, determining whether to use the stored one or more TA parameters or to obtain a new one or more TA parameters; and communicating with the second base station based on said determining, wherein said communicating with the second base station uses the stored one or more TA parameters or the new one or more TA parameters. Example 2. The method of example 1, wherein said comparing the one or more of the plurality of signal quality measurements comprises comparing a moving average of two or more of the plurality of signal quality measurements to a lower threshold, wherein said communicating with the second base station is performed using the stored one or more TA parameters based on the moving average of the two or more of the plurality of signal quality measurements being above the lower threshold. Example 3. The method of Example 2, wherein said comparing comprising comparing the moving average of the two or more of the plurality of signal quality measurements to an upper threshold, wherein said communicating with the second base station is performed using the stored one or more TA parameters based on the moving average of the two or more of the plurality of signal quality measurements being below the upper threshold. Example 4. The method of Example 1, further comprising: receiving a configuration from the first base station or the second base station, wherein the configuration indicates to attempt to reuse the stored one or more TA parameters. Example 5. The method of Example 4, wherein the configuration indicates to perform the plurality of signal measurements of the second base station. Example 6. The method of Example 4, wherein the network configuration indicates the one or more signal quality thresholds. Example 7. The method of Example 1, further comprising: performing a random access channel (RACH) procedure in response to determining to obtain the new one or more TA parameters, wherein said communicating with the second base station based on the determining is performed after completing the RACH procedure. Example 8. The method of Example 1, wherein said comparing the one or more of the plurality of signal quality measurements is performed prior to receiving the indication to activate the SCG, wherein the method further comprises: providing an indication that the one or more TA parameters are invalid to the first base station; triggering uplink communication with the second base station during the SCG deactivated state; and determining the new one or more TA parameters based on the uplink communication. Example 9. The method of Example 1, wherein said comparing the one or more of the plurality of signal quality measurements of the second base station to the one or more signal quality thresholds is performed after receiving the indication to activate the SCG. Example 10. An apparatus, comprising: at least one processor, configured to cause a wireless device to: establish communication with a first base station of a cellular network, wherein the first base station is comprised in a master cell group (MCG); establish communication a second base station, wherein the second base station is comprised in a secondary cell group (SCG); maintain one or more timing advance (TA) parameters for performing uplink communication with the second base station; receive an indication to deactivate the SCG; perform a plurality of signal quality measurements of the second base station while the SCG is deactivated; receiving an indication to activate the SCG; in response to receiving an indication to activate the SCG, compare a moving average of the plurality of signal quality measurements of the second base station to one or more signal quality thresholds; based on said comparing, determining whether to use previously stored one or more TA parameters or to obtain a new one or more TA parameters; and communicate with the second base station based on said determining, wherein said communicating with the second base station uses the previously stored one or more TA parameters or the new one or more TA parameters. Example 11. The of apparatus Example 10, wherein said comparing the moving average of the plurality of signal quality measurements comprises comparing the moving average to a lower threshold and an upper threshold, wherein said communicating with the second base station is performed using the stored one or more TA parameters based on the moving average of the two or more of the plurality of signal quality measurements being above the lower threshold and below the upper threshold. Example 12. The apparatus of Example 10, wherein the at least one processor is further configured to cause the wireless device to: receive a configuration from the first base station or the second base station, wherein the configuration indicates to attempt to reuse the stored one or more TA parameters. Example 13. The apparatus of Example 12, wherein the network configuration indicates the one or more signal quality thresholds. Example 14. The apparatus of Example 10, wherein the at least one processor is further configured to cause the wireless device to: perform a random access channel (RACH) procedure in response to determining to obtain the new one or more TA parameters, wherein said communicating with the second base station based on the determining is performed after completing the RACH procedure. Example 15. The apparatus of Example 10, wherein said determining comprises determining to use the previously stored one or more TA parameters, wherein when using the previously stored one or more TA parameters fails, the at least one processor is further configured to cause the wireless device to: perform a random access channel (RACH) procedure to obtain the new one or more TA parameters; and communicate with the second base station using the new one or more TA parameters. Example 16. A method, comprising: by one or more nodes of the cellular network: establishing communication with the wireless device, wherein a first node is comprised in a master cell group (MCG) of the wireless device, wherein a second node is comprised in a secondary cell group (SCG) of the wireless device, wherein at least the second node is comprised in the one or more nodes of the cellular network; maintaining one or more timing advance (TA) parameters for receiving uplink communication from the wireless device using the second node; providing a configuration to the wireless device for determining whether to reuse the one or more TA parameters after SCG activation, wherein the configuration indicates to attempt to reuse the one or more TA parameters; at a first time, deactivating the SCG for the wireless device; at a second time, activating the SCG for the wireless device, wherein the wireless device is configured to determine whether to reuse the one or more TA parameters based on the configuration; and communicating with the wireless device using the second node. Example 17. The method of Example 16, wherein said communicating is performed without performing a random access channel (RACH) procedure with the wireless device in response to the wireless device determining to reuse the one or more TA parameters. Example 18. The method of Example 16, further comprising: performing a random access channel (RACH) procedure with the wireless device in response to the wireless device determining not to reuse the one or more TA parameters. Example 19. The method of Example 16, wherein the network configuration indicates at least a first threshold for the wireless device to compare to one or more signal quality measurements of the second base station. Example 20. The method of Example 16, wherein the first node performs said providing the configuration to the wireless device. Aspects of the present disclosure may be realized in any of various forms. For example, some aspects may be realized as a computer-implemented method, a computer-readable memory medium, or a computer system. Other aspects may be realized using one or more custom-designed hardware devices such as ASICs. Still other aspects may be realized using one or more programmable hardware elements such as FPGAs. In some aspects, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of a method aspects described herein, or, any combination of the method aspects described herein, or, any subset of any of the method aspects described herein, or, any combination of such subsets. In some aspects, a device (e.g., a UE) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method aspects described herein (or, any combination of the method aspects described herein, or, any subset of any of the method aspects described herein, or, any combination of such subsets). The device may be realized in any of various forms. In some aspects, a device includes: an antenna; a radio coupled to the antenna; and a processing element coupled to the radio. The device may be configured to implement any of the method aspects described above. In some aspects, a memory medium may store program instructions that, when executed, cause a device to implement any of the method aspects described above. In some aspects, an apparatus includes: at least one processor (e.g., in communication with a memory), that is configured to implement any of the method aspects described above. In some aspects, a method includes any action or combination of actions as substantially described herein in the Detailed Description and claims. In some aspects, a method is performed as substantially described herein with reference to each or any combination of the Figures contained herein, with reference to each or any combination of paragraphs in the Detailed Description, with reference to each or any combination of Figures and/or Detailed Description, or with reference to each or any combination of the claims. In some aspects, a wireless device is configured to perform any action or combination of actions as substantially described herein in the Detailed Description, Figures, and/or claims. In some aspects, a wireless device includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a wireless device. In some aspects, a non-volatile computer-readable medium may store instructions that, when executed, cause the performance of any action or combination of actions as substantially described herein in the Detailed Description and/or Figures. In some aspects, an integrated circuit is configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures. In some aspects, a mobile station is configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures. In some aspects, a mobile station includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile station. In some aspects, a mobile device is configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures. In some aspects, a mobile device includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device. In some aspects, a network node is configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures. In some aspects, a network node includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device. In some aspects, a base station is configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures. In some aspects, a base station includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device. In some aspects, a 5G NR network node or base station is configured to perform any action or combination of actions as substantially described herein in the Detailed Description and/or Figures. In some aspects, a 5G NR network node or base station includes any component or combination of components as described herein in the Detailed Description and/or Figures as included in a mobile device. It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users. Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message/signal X received by the UE in the downlink as message/signal X transmitted by the base station, and each message/signal Y transmitted in the uplink by the UE as a message/signal Y received by the base station Although the aspects above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. | 73,144 |
11943723 | DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, based on 3rd Generation Partnership Project (3GPP) long term evolution (LTE) or 3GPP LTE-advanced (LTE-A), the present invention will be applied. This is just an example, and the present invention may be applied to various wireless communication systems. Hereinafter, LTE includes LTE and/or LTE-A. The technical terms used herein are used to merely describe specific embodiments and should not be construed as limiting the present invention. Further, the technical terms used herein should be, unless defined otherwise, interpreted as having meanings generally understood by those skilled in the art but not too broadly or too narrowly. Further, the technical terms used herein, which are determined not to exactly represent the spirit of the invention, should be replaced by or understood by such technical terms as being able to be exactly understood by those skilled in the art. Further, the general terms used herein should be interpreted in the context as defined in the dictionary, but not in an excessively narrowed manner. The expression of the singular number in the present invention includes the meaning of the plural number unless the meaning of the singular number is definitely different from that of the plural number in the context. In the following description, the term ‘include’ or ‘have’ may represent the existence of a feature, a number, a step, an operation, a component, a part or the combination thereof described in the present invention, and may not exclude the existence or addition of another feature, another number, another step, another operation, another component, another part or the combination thereof. The terms ‘first’ and ‘second’ are used for the purpose of explanation about various components, and the components are not limited to the terms ‘first’ and ‘second’. The terms ‘first’ and ‘second’ are only used to distinguish one component from another component. For example, a first component may be named as a second component without deviating from the scope of the present invention. It will be understood that when an element or layer is referred to as being “connected to” or “coupled to” another element or layer, it can be directly connected or coupled to the other element or layer or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly connected to” or “directly coupled to” another element or layer, there are no intervening elements or layers present. Hereinafter, exemplary embodiments of the present invention will be described in greater detail with reference to the accompanying drawings. In describing the present invention, for ease of understanding, the same reference numerals are used to denote the same components throughout the drawings, and repetitive description on the same components will be omitted. Detailed description on well-known arts which are determined to make the gist of the invention unclear will be omitted. The accompanying drawings are provided to merely make the spirit of the invention readily understood, but not should be intended to be limiting of the invention. It should be understood that the spirit of the invention may be expanded to its modifications, replacements or equivalents in addition to what is shown in the drawings. As used herein, ‘base station’ generally refers to a fixed station that communicates with a wireless device and may be denoted by other terms such as eNB (evolved-NodeB), BTS (base transceiver system), or access point. As used herein, ‘user equipment (UE)’ may be stationary or mobile, and may be denoted by other terms such as device, wireless device, terminal, MS (mobile station), UT (user terminal), SS (subscriber station), MT (mobile terminal) and etc. FIG.1illustrates a wireless communication system. As seen with reference toFIG.1, the wireless communication system includes at least one base station (BS)20. Each base station20provides a communication service to specific geographical areas (generally, referred to as cells)20a,20b, and20c. The cell can be further divided into a plurality of areas (sectors). The UE generally belongs to one cell and the cell to which the UE belong is referred to as a serving cell. Abase station that provides the communication service to the serving cell is referred to as a serving BS. Since the wireless communication system is a cellular system, another cell that neighbors to the serving cell is present. Another cell which neighbors to the serving cell is referred to a neighbor cell. A base station that provides the communication service to the neighbor cell is referred to as a neighbor BS. The serving cell and the neighbor cell are relatively decided based on the UE. Hereinafter, a downlink means communication from the base station20to the UE10and an uplink means communication from the UE10to the base station20. In the downlink, a transmitter may be a part of the base station20and a receiver may be a part of the UE10. In the uplink, the transmitter may be a part of the UE10and the receiver may be a part of the base station20. Meanwhile, the wireless communication system may be generally divided into a frequency division duplex (FDD) type and a time division duplex (TDD) type. According to the FDD type, uplink transmission and downlink transmission are achieved while occupying different frequency bands. According to the TDD type, the uplink transmission and the downlink transmission are achieved at different time while occupying the same frequency band. A channel response of the TDD type is substantially reciprocal. This means that a downlink channel response and an uplink channel response are approximately the same as each other in a given frequency area. Accordingly, in the TDD based wireless communication system, the downlink channel response may be acquired from the uplink channel response. In the TDD type, since an entire frequency band is time-divided in the uplink transmission and the downlink transmission, the downlink transmission by the base station and the uplink transmission by the terminal may not be performed simultaneously. In the TDD system in which the uplink transmission and the downlink transmission are divided by the unit of a subframe, the uplink transmission and the downlink transmission are performed in different subframes. Hereinafter, the LTE system will be described in detail. FIG.2shows a downlink radio frame structure according to FDD of 3rd generation partnership project (3GPP) long term evolution (LTE). The radio frame ofFIG.2may be found in the section 5 of 3GPP TS 36.211 V10.4.0 (2011-12) “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 10)”. The radio frame includes 10 sub-frames indexed 0 to 9. One sub-frame includes two consecutive slots. Accordingly, the radio frame includes 20 slots. The time taken for one sub-frame to be transmitted is denoted TTI (transmission time interval). For example, the length of one sub-frame may be 1 ms, and the length of one slot may be 0.5 ms. The structure of the radio frame is for exemplary purposes only, and thus the number of sub-frames included in the radio frame or the number of slots included in the sub-frame may change variously. One slot includes NRBresource blocks (RBs) in the frequency domain. For example, in the LTE system, the number of resource blocks (RBs), i.e., NRB, may be one from 6 to 110. The resource block is a unit of resource allocation and includes a plurality of sub-carriers in the frequency domain. For example, if one slot includes seven OFDM symbols in the time domain and the resource block includes 12 sub-carriers in the frequency domain, one resource block may include 7×12 resource elements (REs). The physical channels in 3GPP LTE may be classified into data channels such as PDSCH (physical downlink shared channel) and PUSCH (physical uplink shared channel) and control channels such as PDCCH (physical downlink control channel), PCFICH (physical control format indicator channel), PHICH (physical hybrid-ARQ indicator channel) and PUCCH (physical uplink control channel). The uplink channels include a PUSCH, a PUCCH, an SRS (Sounding Reference Signal), and a PRACH (physical random access channel). <Measurement and Measurement Report> In the mobile communication system, mobility support of the UE100is required. Accordingly, the UE100continuously measures a quality of a serving cell providing a current service and the quality of a neighboring cell. The UE100reports a measurement result to the network at an appropriate time and the network provides optimum mobility to the UE through handover or the like. Often, measurement of such a purpose is referred to as radio resource management (RRM). Meanwhile, the UE100monitors a downlink quality of a primary cell (Pcell) based on a CRS. This is referred to as radio link monitoring (RLM). FIG.3illustrates a cell detection and measurement procedure. As can be seen with reference to fromFIG.3, the UE detects the neighboring cell based on a synchronization signal (SS) transmitted from the neighboring cell. The SS may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). In addition, when each of he serving cell200aand the neighboring cell200btransmits a cell-specific reference signal (CRS) to the UE100, the UE100performs measure through the CRS and transmits a measurement result thereof to the serving cell200a. In this case, the UE100compares power of the received CRS based on information on received reference signal power. In this case, the UE100may perform the measurement by three following methods. 1) Reference signal received power (RSRP): represents average received power of all REs that carry the CRS transmitted over the entire band. In this case, the average received power of all REs that carry a channel state information (CSI)-reference signal (RS) instead of the CRS. 2) Received signal strength indicator (RSSI): represents received power measured in the entire band. The RSSI includes all of the signal, interference, and thermal noise. 3) Reference symbol received quality (RSRQ): represents the CQI and may be determined as the RSRP/RSSI depending on a measurement bandwidth or subband. That is, the RSRQ refers to a signal-to-noise interference ratio (SINR). Since the RSRP does not provide sufficient mobility information, the RSRQ may be used instead of the RSRP in the process of handover or cell reselection. The RSRQ may be calculated as RSSI/RSSP. Meanwhile, as shown inFIG.3, the UE100receives a radio resource configuration information element (IE) from the serving cell100afor the measurement. The radio resource configuration dedicated information element (IE) is used for configuring/modifying/canceling a radio bearer, or modifying a MAC configuration, and the like. The radio resource configuration IE includes subframe pattern information. The subframe pattern information is information on a measurement resource restriction pattern on the time domain for measuring RSRP and RSRQ for a serving cell (e.g., a primary cell). Meanwhile, the UE100receives a measurement configuration (hereinafter also referred to as “measconfig”) information element (IE) from the serving cell100afor the measurement. A message including the measurement configuration information element (IE) is referred to as a measurement configuration message. Here, the measurement configuration information element (IE) may be received through an RRC connection reconfiguration message. When a measurement result satisfies a reporting condition in the measurement configuration information, the UE reports the measurement result to the base station. A message including the measurement result is referred to as a measurement report message. The measurement configuration IE may include measurement object information. The measurement object information is information about an object to be measured by the UE. The measurement object includes at least any one of an intra-frequency measurement object which is an intra-cell measurement object, an inter-frequency measurement object which is an inter-cell measurement object, and an inter-RAT measurement object which is an inter-RAT measurement object. For example, the intra-frequency measurement object may indicate a neighbor cell having the same frequency band as a serving cell, the inter-frequency measurement object may indicate a neighbor cell having a different frequency band from the serving cell, and the inter-RAT measurement object may indicate a neighbor cell of am RAT different from the RAT of the serving cell. TABLE 1Description of measurement object fieldcarrierFreqThis indicates an E-UTRA carrier frequency to which thisconfiguration applies.measCycleSCellThis indicates a cycle for measuring SCell in a deactivated state.The value may be set to 160, 256, and the like. When the value is 160,measurement is performed every 160 subframes. Meanwhile, the measurement configuration IE includes an information element (IE) as shown in Table below. TABLE 2Description of MeasConfig fieldallowInterruptionsWhen the value is True, this indicates that when the UE performsmeasurements using MeasCycleScell for carriers of the deactivatedScell, it is allowed to stop sending and receiving with the serving cell.measGapConfigConfigure or release a measurement gap. The measGapConfig is used to configure or release a measurement gap (MG). The measurement gap MG is a period for performing cell identification and RSRP measurement on an inter frequency different from the serving cell. TABLE 3Description of MeasConfig fieldgap OffsetThe value of gapOffset may be set to either gp0 or gp1. gp0 correspondsto a gap offset of a pattern ID “0” having MGRP = 40 ms. Gp1corresponds to a gap offset of a pattern ID “1” having MGRP = 40 ms. TABLE 4Minimum timeMeasurementto performGapmeasurement forMeasurementRepetitioninter-frequency andGapGapPeriodinter-RAT duringpattern IdLength (MGL)(MGRP)period of 480 ms06 ms40 ms60 ms16 ms80 ms30 ms If the UE requires a measurement gap to identify and measure inter-frequency and inter-RAT cells, the E-UTRAN (i.e., the base station) provides one measurement gap (MG) having a constant gap period. The UE does not transmit or receive any data from the serving cell during the measurement gap period, retunes its RF chain to the inter-frequency, and then performs the measurement at the corresponding inter-frequency. <Carrier Aggregation> A carrier aggregation system is now described. A carrier aggregation system aggregates a plurality of component carriers (CCs). A meaning of an existing cell is changed according to the above carrier aggregation. According to the carrier aggregation, a cell may signify a combination of a downlink component carrier and an uplink component carrier or an independent downlink component carrier. Further, the cell in the carrier aggregation may be classified into a primary cell, a secondary cell, and a serving cell. The primary cell signifies a cell operated in a primary frequency. The primary cell signifies a cell which UE performs an initial connection establishment procedure or a connection reestablishment procedure or a cell indicated as a primary cell in a handover procedure. The secondary cell signifies a cell operating in a secondary frequency. Once the RRC connection is established, the secondary cell is used to provide an additional radio resource. As described above, the carrier aggregation system may support a plurality of component carriers (CCs), that is, a plurality of serving cells unlike a single carrier system. The carrier aggregation system may support a cross-carrier scheduling. The cross-carrier scheduling is a scheduling method capable of performing resource allocation of a PDSCH transmitted through other component carrier through a PDCCH transmitted through a specific component carrier and/or resource allocation of a PUSCH transmitted through other component carrier different from a component carrier basically linked with the specific component carrier. <Internet of Things (IoT) Communication> Meanwhile, hereinafter, IoT will be described. IoT refers to information exchange through the base station between IoT devices without accompanying human interaction and information exchange through the base station between an IoT device and a server. As such, IoT communication communicates via cellular base stations and thus is also referred to as cellular Internet of Things (CIoT). Such IoT communication is a kind of machine type communication (MTC). Therefore, the IoT device may be referred to as an MTC device. Since the IoT communication has features that a transmission data amount is small and uplink or downlink data transmission and reception rarely occur, it is preferable to lower the cost of the IoT device and reduce battery consumption in accordance with a low data transmission rate. In addition, since the IoT device has a feature of low mobility, the channel environment is not almost changed. As one method for low-cost IoT devices, regardless of a system bandwidth of the cell, the IoT device may use a sub-band of, for example, approximately 1.4 MHz. As such, IoT communication operating on such a reduced bandwidth may be called narrow band (NB) IoT communication or NB CIoT communication. <Next-Generation Mobile Communication Network> Thanks to the success of long term evolution (LTE)/LTE-advanced (LTE-A) for 4G mobile communication, interest in the next generation, that is, 5-generation (so called 5G) mobile communication has been increased and researches have been continuously conducted. The 5G mobile telecommunications defined by the International Telecommunication Union (ITU) refers to providing a data transmission rate of up to 20 Gbps and a feel transmission rate of at least 100 Mbps or more at any location. The official name is ‘IMT-2020’ and its goal is to be commercialized worldwide in 2020. ITU proposes three usage scenarios, for example, enhanced mobile broadband (eMBB) and massive machine type communication (mMTC) and ultra reliable and low latency communications (URLLC). The URLLC relates to a usage scenario that requires high reliability and a low latency time. For example, services such as autonomous navigation, factory automation, and augmented reality require high reliability and low latency (e.g., a latency time of 1 ms or less). Currently, the latency time of 4G (LTE) is statistically 21 to 43 ms (best 10%) and 33 to 75 ms (median). This is insufficient to support a service requiring the latency time of 1 ms or less. Next, the eMBB usage scenario relates to a usage scenario requiring a mobile ultra-wideband. That is, the 5G mobile communication system aims at higher capacity than the current 4G LTE, and may increase the density of mobile broadband users and support device to device (D2D), high stability, and machine type communication (MTC). 5G research and development also aims at a lower latency time and lower battery consumption than a 4G mobile communication system to better implement the Internet of things. A new radio access technology (new RAT or NR) may be proposed for such 5G mobile communication. In the NR, it may be considered that the reception from the base station uses a downlink subframe and the transmission to the base station uses an uplink subframe. This method may be applied to paired spectra and unpaired spectra. A pair of spectra means that two carrier spectra are included for downlink and uplink operations. For example, in a pair of spectra, one carrier may include a downlink band and an uplink band that are paired with each other. FIG.4illustrates an example of a subframe type in NR. A transmission time interval (TTI) illustrated inFIG.4may be referred to as a subframe or slot for NR (or new RAT). The subframe (or slot) ofFIG.4may be used in a TDD system of the NR (or new RAT) to minimize the data transmission delay. As illustrated inFIG.4, a subframe (or slot) includes 14 symbols, like the current subframe. The front symbol of the subframe (or slot) may be used for a DL control channel and the rear symbol of the subframe (or slot) may be used for a UL control channel. The remaining symbols may be used for DL data transmission or UL data transmission. According to such a subframe (or slot) structure, downlink transmission and uplink transmission may be sequentially performed in one subframe (or slot). Accordingly, downlink data may be received within the subframe (or slot) and an uplink acknowledgment response (ACK/NACK) may be transmitted within the subframe (or slot). The structure of such a subframe (or slot) may be referred to as a self-contained subframe (or slot). The use of such a sub-frame (or slot) structure has an advantage that the time taken to retransmit the data where a receive error occurs is reduced and a latency time of the last data transmission may be minimized. In such a self-contained subframe (or slot) structure, a time gap may be required in a transition process from the transmission mode to the reception mode or from the reception mode to the transmission mode. To this end, some OFDM symbols at the time of switching from DL to UL in the subframe structure may be configured as a guard period (GP). <Support of Various Numerologies> In the next system, a number of numerologies may be provided to the UE with the development of a wireless communication technology. The numerology may be defined by a cycle prefix (CP) length and a subcarrier spacing. One cell may provide a plurality of numerologies to the UE. When the index of the numerology is denoted by μ, each subcarrier spacing and corresponding CP length may be as shown in Table below. TABLE 5μΔf = 2μ· 15 [kHz]CP015Normal130Normal260Normal, Extended3120Normal4240Normal In the case of a normal CP, when the index of the numerology is denoted by μ, the number Nslotsymbof OFDM symbols per slot, the number Nframe,μslotof slots per frame, and the number Nsubframe,μslotof slots per subframe are shown in Table below. In the case of a normal CP, when the index of the numerology is denoted by μ, the number Nslotsymbof OFDM symbols per slot, the number Nframe,μslotof slots per frame, and the number Nsubframe,μslotof slots per subframe are shown in Table below. TABLE 6μNslotsymbNframe,μslotNsubframe,μslot0141011142022144043148084141601651432032 In the case of an extended CP, when the index of the numerology is denoted by μ, the number Nslotsymbof OFDM symbols per slot, the number Nframe,μslotof slots per frame, and the number Nsubframe,μslotof slots per subframe are shown in Table below. TABLE 7μNslotsymbNframe,μslotNsubframe,μslot212404 Meanwhile, in the next-generation mobile communication, each symbol in a symbol may be used as a downlink or as an uplink as shown in Table below. In the following table, the uplink is denoted by U and the downlink is denoted by D. In Table below, X represents a symbol that may be used flexibly in the uplink or downlink. TABLE 8Symbol number in slotFormat0123456789101112130DDDDDDDDDDDDDD1UUUUUUUUUUUUUU2XXXXXXXXXXXXXX3DDDDDDDDDDDDDX4DDDDDDDDDDDDXX5DDDDDDDDDDDXXX6DDDDDDDDDDXXXX7DDDDDDDDDXXXXX8XXXXXXXXXXXXXU9XXXXXXXXXXXXUU10XUUUUUUUUUUUUU11XXUUUUUUUUUUUU12XXXUUUUUUUUUUU13XXXXUUUUUUUUUU14XXXXXUUUUUUUUU15XXXXXXUUUUUUUU16DXXXXXXXXXXXXX17DDXXXXXXXXXXXX18DDDXXXXXXXXXXX19DXXXXXXXXXXXXU20DDXXXXXXXXXXXU21DDDXXXXXXXXXXU22DXXXXXXXXXXXUU23DDXXXXXXXXXXUU24DDDXXXXXXXXXUU25DXXXXXXXXXXUUU26DDXXXXXXXXXUUU27DDDXXXXXXXXUUU28DDDDDDDDDDDDXU29DDDDDDDDDDDXXU30DDDDDDDDDDXXXU31DDDDDDDDDDDXUU32DDDDDDDDDDXXUU33DDDDDDDDDXXXUU34DXUUUUUUUUUUUU35DDXUUUUUUUUUUU36DDDXUUUUUUUUUU37DXXUUUUUUUUUUU38DDXXUUUUUUUUUU39DDDXXUUUUUUUUU40DXXXUUUUUUUUUU41DDXXXUUUUUUUUU42DDDXXXUUUUUUUU43DDDDDDDDDXXXXU44DDDDDDXXXXXXUU45DDDDDDXXUUUUUU46DDDDDDXDDDDDDX47DDDDDXXDDDDDXX48DDXXXXXDDXXXXX49DXXXXXXDXXXXXX50XUUUUUUXUUUUUU51XXUUUUUXXUUUUU52XXXUUUUXXXUUUU53XXXXUUUXXXXUUU54DDDDDXUDDDDDXU55DDXUUUUDDXUUUU56DXUUUUUDXUUUUU57DDDDXXUDDDDXXU58DDXXUUUDDXXUUU59DXXUUUUDXXUUUU60DXXXXXUDXXXXXU61DDXXXXUDDXXXXU <Operating Band in NR> An operating band in NR is as follows. TABLE 9NRUplink (UL)Downlink (DL)operatingoperating bandoperating bandDuplexbandFUL_low-FUL_highFDL_low-FDL_highmoden11920 MHz-1980 MHz2110 MHz-2170 MHzFDDn21850 MHz-1910 MHz1930 MHz-1990 MHzFDDn31710 MHz-1785 MHz1805 MHz-1880 MHzFDDn5824 MHz-849 MHz869 MHz-894 MHzFDDn72500 MHz-2570 MHz2620 MHz-2690 MHzFDDn8880 MHz-915 MHz925 MHz-960 MHzFDDn20832 MHz-862 MHz791 MHz-821 MHzFDDn28703 MHz-748 MHz758 MHz-803 MHzFDDn382570 MHz-2620 MHz2570 MHz-2620 MHzTDDn412496 MHz-2690 MHz2496 MHz-2690 MHzTDDn501432 MHz-1517 MHz1432 MHz-1517 MHzTDDn511427 MHz-1432 MHz1427 MHz-1432 MHzTDDn661710 MHz-1780 MHz2110 MHz-2200 MHzFDDn701695 MHz-1710 MHz1995 MHz-2020 MHzFDDn71663 MHz-698 MHz617 MHz-652 MHzFDDn741427 MHz-1470 MHz1475 MHz-1518 MHzFDDn75N/A1432 MHz- 1517 MHzSDLn76N/A1427 MHz-1432 MHzSDLn773300 MHz-4200 MHz3300 MHz-4200 MHzTDDn783300 MHz-3800 MHz3300 MHz-3800 MHzTDDn794400 MHz-5000 MHz4400 MHz-5000 MHzTDDn801710 MHz-1785 MHzN/ASULn81880 MHz-915 MHzN/ASULn82832 MHz-862 MHzN/ASULn83703 MHz-748 MHzN/ASULn841920 MHz-1980 MHzN/ASUL TABLE 10n25726500 MHz-29500 MHz26500 MHz-29500 MHzTDDn25824250 MHz-27500 MHz24250 MHz-27500 MHzTDDn25937000 MHz-40000 MHz37000 MHz-40000 MHzTDD On the other hand, when the operating band of the above table is used, the channel bandwidth is used as shown in Table below. TABLE 115101520253040506080100MHzMHzMHzMHzMHzMHzMHzMHzMHzMHzMHzSCS (kHz)NRBNRBNRBNRBNRBNRBNRBNRBNRBNRBNRB15255279106133[160]216270N/AN/AN/A301124385165[78]10613316221727360N/A11182431[38]516579107135 In the above table, SCS means a subcarrier spacing. In the above table, NRB represents the number of RBs. On the other hand, when the operating band of the above table is used, the channel bandwidth is used as shown in the table below. TABLE 12SCS50 MHz100 MHz200 MHz400 MHz(kHz)NRBNRBNRBNRB6066132264N.A1203266132264 <SS Block in NR> In 5G NR, a physical broadcast channel (PBCH) including information required for the UE to perform an initial access, that is, a master information block (MIB) and a synchronization signal SS (including PSS and SSS) are defined as an SS block. In addition, a plurality of SS blocks are bound to be defined as an SS burst, and a plurality of SS bursts are bound to be defined as an SS burst set. Each SS block is assumed to be beamformed in a specific direction, and several SS blocks in the SS burst set are designed to support UEs in different directions. FIG.5is an exemplary diagram illustrating an example of an SS block in NR. Referring toFIG.5, the SS burst is transmitted every predetermined periodicity. Therefore, the UE receives the SS block and performs cell detection and measurement. On the other hand, in 5G NR, beam sweeping is performed on the SS. This will be described with reference toFIG.6. FIG.6is an exemplary diagram illustrating an example of beam sweeping in NR. The base station transmits each SS block in the SS burst with beam sweeping over time. At this time, the SS blocks in the SS burst set are transmitted in order to support UEs existing in different directions. InFIG.6, the SS burst set includes SS blocks ito6, and each SS burst includes two SS blocks. <Disclosure of this Specification> I. First Disclosure In the present section, a channel raster and a synchronization raster will be discussed. A frequency channel raster is defined as a set of RF reference frequencies FREF. The RF reference frequency may be used as a signal for indicating the locations of an RF channel, an SS block, and the like. A global frequency raster is defined for all frequencies of 0 to 100 GHz. The unit of the global frequency raster is denoted by AFGlobal. The RF reference frequency is specified by an NR absolute radio frequency channel number (NR-ARFCN) in the range of the global frequency raster (0 . . . 2016666). The relationship between the NR-ARFCN and the RF reference frequency FREF of MHz may be expressed by the following equation. Here, FREF-Offs and NRef-Offsare shown in the following Table. FREF=FREF‐Offs+ΔFGlobal(NREF-NREF‐Offs)[Equation1] TABLE 13Frequency rangeΔFGlobalFREF-Offs(MHz)(kHz)(MHz)NREF-OffsRange of NREF0-30005000-5999993000-24250153000600000600000-201666624250-1000006024250.0820166672016667-3279165 The channel raster represents a subset of RF reference frequencies that may be used to identify RF channel locations in the uplink and downlink. The RF reference frequency for the RF channel may be mapped to a resource element on the subcarrier. The mapping between the RF reference frequency of the channel raster and the corresponding resource element may be used to identify an RF channel location. The mapping depends on the total number of RBs allocated to the channel and is applies to both UL and DL. In the case of NRB mod 2=0, an RE index k is 0, and the PRB number is as follows. nPRB=⌊NRB2⌋ In the case of NRB mod 2=1, an RE index k is 6, and the PRB number is as follows. nPRB=⌊NRB2⌋ The RF channel location of the channel raster on each NR operating band may be represented as shown in the following Table. TABLE 14NRUplink frequencyDownlink frequency rangeoperatingΔFRasterrange of NREFof NREFband(kHz)(First - <Step size> - Last)(First - <Step size> - Last)n1100384000 - <20> - 396000422000 - <20> - 434000n2100370000 - <20> - 382000386000 - <20> - 398000n3100342000 - <20> - 357000361000 - <20> - 376000n5100164800 - <20> - 169800173800 - <20> - 178800n7100500000 - <20> - 514000524000 - <20> - 538000n8100176000 - <20> - 183000185000 - <20> - 192000n12100139800 - <20> - 143200145800 - <20> - 149200n20100166400 - <20> - 172400158200 - <20> - 164200n25100370000 - <20> - 383000386000 - <20> - 399000n28100140600 - <20> - 149600151600 - <20> - 160600n34100402000 - <20> - 405000402000 - <20> - 405000n38100514000 - <20> - 524000514000 - <20> - 524000n39100376000 - <20> - 384000376000 - <20> - 384000n40100460000 - <20> - 480000460000 - <20> - 480000n4115499200 - <3> - 537999499200 - <3> - 53799930499200 - <6> - 537996499200 - <6> - 537996n51100285400 - <20> - 286400285400 - <20> - 286400n66100342000 - <20> - 356000422000 - <20> - 440000n70100339000 - <20> - 342000399000 - <20> - 404000n71100132600 - <20> - 139600123400 - <20> - 130400n75100N/A286400 - <20> - 303400n76100N/A285400 - <20> - 286400n7715620000 - <1> - 680000620000 - <1> - 68000030620000 - <2> - 680000620000 - <2> - 680000n7815620000 - <1> - 653333620000 - <1> - 65333330620000 - <2> - 653332620000 - <2> - 653332n7915693334 - <1> - 733333693334 - <1> - 73333330693334 - <2> - 733332693334 - <2> - 733332n80100342000 - <20> - 357000N/An81100176000 - <20> - 183000N/An82100166400 - <20> - 172400N/An83100140600 - <20> - 149600N/An84100384000 - <20> - 396000N/An86100342000 - <20> - 356000N/A TABLE 15Uplink and downlinkNR operatingΔFRasterfrequency rangeband(kHz)(First - <Step size> - Last)n257602054166 - <1> - 21041651202054167 - <2> - 2104165n258602016667 - <1> - 20708321202016667 - <2> - 2070831n260602229166 - <1> - 22791651202229167 - <2> - 2279165n261602070833 - <1> - 20849991202070833 - <2> - 2087497 On the other hand, the synchronization raster represents the frequency location of the SS block used to obtain system information by the UE. The frequency location of the SS block may be defined as SSREFusing the corresponding GSCN number. I-1. Relationship Between Channel Raster and Synchronization Raster In the present section, a synchronization raster considering the concept of floating synchronization will be described. In the existing LTE/LTE-A, since a synchronization signal has been located at the center of a channel bandwidth (CBW), a synchronization raster and a channel raster are equally handled. However, in NR, the SS block is not at the center of the channel bandwidth (CBW). Also, in NR, multiple SS blocks may be arranged in an FDM scheme considering a broadband operation. Once NR UE detects an SS block, the NR UE may receive signaling information from the network. That is, the channel raster is mainly associated with provider's spectral retention, while the synchronization raster may be more important in terms of UE implementation. Considering the synchronization raster, the SS block may be aligned with a center frequency of the data by at least subcarrier. Otherwise, inter-channel interference (ICI) between the data and the SS block may occur. As a result, the data signal and the SS block need to be aligned at least in units of the subcarrier. RSS=floor((CBWeff‐min-BWSS+1RB)/RCH)*RCH[Equation2] Here, RSSrepresents a synchronization raster. CBWeff-minrefers to an effective minimum bandwidth of the subcarrier. BWSSrefers to a bandwidth of the SS block. RCHrefers to a channel raster. Basically, the above equation means that the synchronization raster is a multiple of the channel raster. For a first input of the synchronization raster, the following Equation may be considered because the minimum CBW for each frequency band is much larger than the channel raster. FSS0=FDL_low+floor((0.5*(CBWmin+CBWeff‐min)-BWSS)/RCH)*RCH[Equation3] In the above Equation, FDL_LOWrefers to a start frequency of each frequency band. On the other hand, an actual synchronization raster entry for each frequency band may be determined as follows. FSS=FSS0+n*RSS[Equation4] In Equations 2 and 3 above, an example of the synchronization raster is shown in the following Table. TABLE 16Bandreformedfrom LTENR(below 2.4band below 6Frequency rangeGHz)GHzmmWave bandSynchronization1001560raster unit [kHz]Subcarrier spacing of151530120240SS (SCSss) [kHz]The number of SS288288288288288subcarriersBandwidth (BWss) of4.324.328.6434.5669.12SS [MHz]Minimum bandwidth551050100(CBW) [MHz]Subcarrier spacing of15151560120data (SCSData) [kHz]Agreed SU [NRB]2525526666Effective channel4.54.59.3647.5295.04bandwidth(CBW) [MHz]SS offset from the40042010351416028380outside of band [kHz]SS raster [kHz]3003608851368026640 Based on the table, the following options are proposed. Option 1: The synchronization raster may be configured in units of 100 kHz. Option 2: The synchronization raster may be configured as a multiple of a subcarrier spacing. On the other hand, another alternative is needed to maintain the orthogonality between the data and the SS because the channel raster of 100 kHz is not a multiple of the subcarrier spacing (SCS) (e.g., 15/30/60 kHz). Since the least common multiple (LCM) of 100 kHz and 15 kHz is 300 kHz, the synchronization entry of three times may be used. This means that three synchronization raster entries shifted by ⅓ SCS within the same frequency band are superimposed. A 100 kHz raster-based synchronization raster may be evaluated based on Equation 1, and the evaluated values are shown in Table below by considering 5 MHz CBW and 15 kHz SCS. From the evaluated results, it seems that since the effective synchronization raster is still 100 kHz when considering three times superimposition, there is no advantage of floating synchronization. In addition to the synchronization raster entry, one more PRB may be required for the floating synchronization. In the band refarmed from the LTE, it is expected that the spectrum and the frequency band retained by the provider are relatively narrower than those of a new NR dedicated band. Therefore, it is considered that a broadband operation is not atop priority. Based thereon, when the 100 kHz channel raster is used, it may be effective to use option 1 in the band refarmed from the LTE. Thus, the band reformed from LTE using the 100 kHz channel raster is proposed as follows. Proposal: Using synchronization raster of 100 kHz without using the floating synchronization On the other hand, the subcarrier spacing of the SS block will be described as follows. The subcarrier spacing for the PSS/SSS may be differentially defined with respect to the following frequency ranges. 1) In the case below 6 GHz, 15 kHz/30 kHz 2) In the case of 6 GHz or more, 120 kHz/240 kHz Since information on the subcarrier spacing SCSss for the SS may be signaled to non-stand alone (NSA) UE, it is not particularly problematic. However, there is a problem when the stand-alone (SA) UE performs initial cell detection. Using multiple SCSss may require more assumptions for the SS block and affect complexity, power consumption of the UE, and an initial cell detection time. In Tables 9 and 10 below, the band below 6 GHz and the mmWave are illustrated. In Tables 9 and 10, in the band below 6 GHz, a single subcarrier spacing may be used for the SS block. Also, in the case of the mmWave band, multiple SCSss may be used for all currently available frequency bands. TABLE 17MinimumBand of 6channelSubcarrier spacingGHz or lessbandwidth(SCS) of SS block15 MHz15 kHz35 MHz15 kHz510 MHz/5 MHz[30 kHz/15 kHz]75 MHz15 kHz85 MHz15 kHz205 MHz15 kHz285 MHz15 kHz4110 MHz30 kHz665 MHz/10 MHz[15 kHz/30 kHz]705 MHz15 kHz715 MHz15 kHz1.427-1.518 GHz5 MHz15 kHz3.3-3.8 GHz10 MHz[15 kHz/30 kHz]3.3-4.2 GHz10 MHz[15 kHz/30 kHz]4.4-4.99 GHz[40 MHz]30 kHz TABLE 18MinimumSubcarrier spacingchannel(SCS) ofmmWave bandbandwidthSS block24.25-27.5GHz50 MHz120 kHz/240 kHz26.5-29.5GHz50 MHz120 kHz/240 kHz31.8-33.4GHz50 MHz120 kHz/240 kHz37-40GHz50 MHz120 kHz/240 kHz Based on the above-described contents, the following Options may be considered. Option 1) An SS block redesign, particularly, reducing the bandwidth of the SS block in the PBCH may be considered. Option 2) It may be considered to specify a different band number for each SCSss for the same frequency range. Option 3) It may be considered to specify a single basic SCSss for each band. Option 4) It may be considered to allow multiple SS SCS for some frequency bands. In the case of option 1 above, the NR cell range may be affected due to the deterioration of target performance of the PBCH design in the SS block. In the case of option 2, it may be inefficient to redefine the band. In the case of option 3, contradictions may occur depending on the spectrum retained by the provider. In case of option 4, UE complexity is not important if the UE may sequentially perform initial cell detection. According to option 4, only the initial cell detection time of some stand-alone (SA) UEs may be affected and high-performance UE that may perform an improved initial cell detection procedure may not be affected. Therefore, it may be proposed as follows. Proposal 1. It may be considered to specify a basic SCS for the SS as a first priority in the band-by-band manner. Proposal 2. When multiple SCSss is allowed, it may be assumed that the initial cell detection is performed sequentially. II. Second Disclosure In the present section, an initial cell detecting operation of the NR UE will be described. In particular, an operation of the NR UE on a band switched from LTE using a 100 kHz channel raster will be described. Multiple basic SCSss may be considered as follows. Multiple SCS is proposed as follows with respect to a specific frequency band. Alt 1: The SS block may be designed again by reducing a PBCH bandwidth to 12 PRBs. Alt 2: Up to two SCS values may be selected with respect to the SS/PBCH and a minimum bandwidth of the UE may be selected with respect to each band of a restricted set. In the case of Alt 1 above, PBCH decoding performance may be influenced, and as a request, an NR cell range may be reduced. In the case of Alt 2 above, when a plurality of basic SCSss, initial cell detection for a stand alone (SA) UE may be influenced. A non-stand alone (NSA) UE may receive information on the SCSss through LTE RAT. However, in the case of the SA UE, even though single basic SCSss is used, a potential UE implementation problem may occur in some frequency bands. Further, when multiple SCSss is specified, the UE needs to perform search according to various combinations, so UE implementation complexity and power consumption may increase and the UE may be influenced even by an initial cell detection time. Result 1). Using the single basic SCSss may be effective in terms of UE implementation/power consumption and the initial cell time. Therefore, using multiple basic SCSss is permitted and FEO, Proposal 1) The UE may sequentially perform the initial cell detection. Proposal 2) The requirement for the initial cell detection may not be designated similarly to the LTE. By the above method, the UE may perform the initial cell detection even in a band in which multiple is defined without improvement of hardware and a required time which is a disadvantage may be overcome through a separate configuration or signaling. II-1. Synchronization Raster In the existing LTE/LTE-A, since a synchronization signal is located at the center of a channel bandwidth (CBW), the synchronization signal is handled equally to a synchronization raster and a channel raster. However, in the NR, the SS block is not at the center of the channel bandwidth (CBW). Further, in the NR, multiple SS blocks may be arranged in an FDM scheme considering a broadband operation. Once the NR UE detects the SS block, the NR UE may receive signaling information from the network. That is, the channel raster is mainly associated with provider's spectral retention, while the synchronization raster may be more important in terms of UE implementation. For definition of the synchronization raster, since the UE needs to adjust a frequency of a mixer in an RF unit during the initial cell detection time, the synchronization raster needs to represent an actual frequency location of the mixer. Therefore, the synchronization raster may be proposed as follows. Proposal) The synchronization raster needs to be located at the center of the SS block. When the synchronization raster is considered, two followings need to be considered for the initial cell detection.The subcarrier of the SS block needs to be aligned with the subcarrier of the data signal in order to avoid the ICI.At least one SS block may be located in the CBW of the UE which operates in a minimum CBW. Based thereto, an actual synchronization raster for the initial cell detection may be formulated as follows. RSS=floor((CBWeff‐minBWSS+RCH)/RCH)*RCH[Equation5] Here, RSSrepresents the synchronization raster. CBWeff-minrepresents a minimum bandwidth of the carrier which may be effective. BWSSrepresents the bandwidth of the SS block. RCHrepresents the channel raster. In Equation 1 above, when a synchronization raster value is described as an example by considering a minimum CBW/SCS set, the synchronization raster value is described in a table below. TABLE 19Band refarmedfrom LTENR band ofFrequency range(2.4 GHz or less)6 GHz or lessmm Wave bandMinimum channel51051050100bandwidth (CBW)[MHz]Data subcarrier spacing1530153060120(SCSData) [kHz]Channel raster [kHz]1001560SCSSS[kHz]15301530120240Number of SS carriers288288288288288288SS bandwidth (BWSS)4.328.644.328.6434.5669.12[MHz]Agreed SU [NRB]252425246666Channel bandwidth which4.58.644.58.6447.5295.04may be effective CBW)[MHz]SS raster [kHz]200100195151302025980 From the above table, the synchronization raster may be proposed as follows. Proposal: One of values of the above table may be used with respect to the synchronization raster. II-2. Synchronization raster for 100 kHz channel raster The 100 kHz channel raster may be used with respect to a frequency band of 2.4 GHz or less. Since the 100 kHz channel raster is not a multiple, when the SCS is 15 kHz, there may be additional considerations to ensure orthogonality between the data subcarrier and the SS block subcarrier when floating synchronization is used. When 300 kHz which is a minimum common multiple of 100 kHz and 15 kHz is considered, synchronization may be performed up to three times for the synchronization raster. This may mean that three different synchronization signals need to be used. This may influence the UE implementation. When three synchronization signals are not intended to be used as an alternative, the following options may be considered. When the 100 kHz channel raster is used and the band refarmed from the LTE I used, Option) The UE may detect the cell only by a specific SS block. In the case of the above option, gNB which operates in a broadband may generally transmit multiple SS blocks. However, since the synchronization raster is not continuously aligned with a subcarrier boundary, the specific SS block from gNB may be detected by the UE during the initial cell detection time. However, when there is a method for notifying a secondary SSB location to the UE, the UE may activate secondary BWP after detecting an initial cell. Further, the orthogonality between the data and the SS block needs to be maintained. The channel raster itself may not have to guarantee orthogonality with other adjacent channel raster. Thus, when the synchronization raster may represent a specific subcarrier, the channel raster may represent the specific subcarrier. Further, if the synchronization raster may not be adjusted with respect to the 100 kHz channel raster, the synchronization raster needs to be placed in a channel center. In this sense, the synchronization raster needs to be the multiple of the channel raster and the synchronization raster may have to be overlaid on the channel raster for a frequency band that uses at least the 100 kHz channel raster. The band using the 100 kHz channel raster may be proposed as follows. Proposal) The channel raster needs to be located at the center of the CBW. Proposal) The synchronization raster may be overlaid on the channel raster. By the above method, the UE may define the synchronization raster that is to perform the initial cell search. Further, when the broadband is used, in the case where the UE is attached to the cell by using specific SSB by the proposed method, the cell may transfer configuration information for second BWP to the UE, and as a result, it may be necessary to additionally increase the raster. III. Third Disclosure Cell search in the 5G NR network is performed in a predefined synchronization raster and it is desirable to set the number of such synchronization rasters as small as possible in each frequency band, considering the time required and the power consumption for the UE are considered. However, in a current NR frequency band, in the case of the band refarmed from the existing LTE, the 100 kHz channel raster needs to be applied similarly to the LTE for coexistence with the existing LTE system. In this case, since the 100 kHz channel raster is not the multiple of the subcarrier spacing of 15 kHz, the orthogonality between the data and the synchronization signal may not be maintained. In the present section, an additional operation of the UE related with the proposal for solving that the orthogonality is not maintained will be described. III-1. Basic principle for synchronization raster In the existing LTE/LTE-A, since the synchronization signal is located at the center of the channel bandwidth (CBW), the synchronization signal is handled equally to the synchronization raster and the channel raster. However, in the NR, the SS block is not at the center of the channel bandwidth (CBW). Further, in the NR, multiple SS blocks may be arranged in an FDM scheme considering a broadband operation. Once the NR UE detects the SS block, the NR UE may receive the signaling information from the network. That is, the channel raster is mainly associated with provider's spectral retention, while the synchronization raster may be more important in terms of UE implementation. For the definition of the synchronization raster, since the UE needs to adjust a frequency of the mixer in the RF unit during the initial cell detection time, the synchronization raster needs to represent an actual frequency location of the mixer. Therefore, the synchronization raster may be proposed as follows. Proposal) The synchronization raster needs to be located at the center of the SS block. When the synchronization raster is considered, two followings need to be considered for the initial cell detection.The subcarrier of the SS block needs to be aligned with the subcarrier of the data signal in order to avoid the ICI.At least one SS block may be located in the CBW of the UE which operates in a minimum CBW. Based thereto, the actual synchronization raster for the initial cell detection may be formulated as follows. RSS=floor((CBWeff‐minBWSS+RCH)/RCH)*RCH[Equation6] Here, RSSrepresents the synchronization raster. CBWeff-minrepresents a minimum bandwidth of the carrier which may be effective. BWSSrepresents the bandwidth of the SS block. RCHrepresents the channel raster. III-2. Synchronization Raster for Band Refarmed from LTE The 100 kHz channel raster may be used in the case of the frequency band of 2.4 GHz or less. Since the 100 kHz channel raster is not the multiple of the SCS of 15 kHz, more considerations are required for maintaining the orthogonality between the subcarrier of the data signal and the subcarrier of the SS block signal. Two following methods may be considered in order to maintain the orthogonality with the 100 kHz channel raster. Option 1. The synchronization raster may be calculated by assuming 300 kHz effective channel raster and three multiple synchronization raster sets shifted to 100 kHz may be used. Option 2. A single synchronization raster calculated by assuming the 100 kHz channel raster may be used. In this case, the UE may assume that three synchronization rasters shifted to 5 kHz are implicitly located at each location which is predefined. FIG.7Aillustrates an example of a synchronization raster according to option 1 of section III-2 andFIG.7Billustrates an example of a synchronization raster according to option 2 of section III-2. First, the channel raster is in units of 100 kHz. Therefore, the multiple of the SCS of 15 kHz may not be aligned with the channel raster. Referring toFIG.7A, three synchronization rasters may be shifted and arranged in units of 100 kHz. Each synchronization raster may be arranged at an interval of 1.2 MHz. Referring toFIG.7B, three synchronization rasters may be shifted and arranged in units of 5 kHz. Each synchronization raster may be arranged at an interval of 1 MHz. In the case of option 1 above, the synchronization raster of each set may be calculated by assuming the effective channel raster of 300 kHz and each synchronization raster may be arranged every 1.2 MHz. In the case of option 2 above, the synchronization raster may be calculated by assuming an actual channel raster of 100 kHz and each synchronization raster may be arranged every 1.0 MHz. When the total number of calculations of an SS correlation is considered, option 1 may be more efficient than option 2. When option 2 is adopted, the UE may rapidly perform the cell search and reduce power consumption by using an improved cell detecting operation. Further, since the bandwidth of the PBCH is reduced, the synchronization raster of 1 MHz may not significantly increase UE complexity. In this case, the UE may perform tuning of the RF unit in the single raster and an offset up to remaining ±5 kHz may be processed through CFO detected together during detection of the corresponding SS block. In this case, a detecting operation of the SS block actually performed by the UE may be significantly reduced. Further, a method may be considered, in which when the UE detects the SS block, the UE may acquire information on the corresponding offset through MIB to enhance reception performance of remaining minimum system information (RMSI). Therefore, the method may be proposed as follows. Proposal: When the 100 kHz channel raster is used, option 2 may be used. Based on option 1 above, the number of synchronization rasters may be organized as shown in the table below with respect to the existing NR frequency band. TABLE 20DataTotalsubcarrierNumber ofnumber ofDLspacingsynchroni-synchroni-NRfrequencyBWΔFCR(SCSData)ΔFSRzatonzationbandband[MHz][kHz][kHz]CBW min/SCSss[MHz]rastersrastersn12110-217060100155 MHz/15 kHz1.2147 (3 × 49)147n21930-199060100155 MHz/15 kHz1.2147 (3 × 49)147n31805-188075100155 MHz/15 kHz1.2186 (3 × 62)186n5869-89425100155 MHz/15 kHz1.260 (3 × 20)1053010 MHz/30 kHz1.545 (3 × 15)n72620-269070100155 MHz/15 kHz1.2171 (3 × 57)171n8925-96035100155 MHz/15 kHz1.284 (3 × 28)84n20791-82130100155 MHz/15 kHz1.272 (3 × 24)72n28758-80345100155 MHz/15 kHz1.2108 (3 × 36)108n382570-2620501003010 MHz/30 kHz1.596 (3 × 32)96n501432-151785100155 MHz/15 kHz1.2210 (3 × 70)210n511427-14325100155 MHz/15 kHzN/A11n662110-220090100155 MHz/15 kHz1.2222 (3 × 74)3993010 MHz/30 kHz1.5177 (3 × 59)n701995-202025100155 MHz/15 kHz1.260 (3 × 20)60n71617-65235100155 MHz/15 kHz1.284 (3 × 28)84n741475-151843100155 MHz/15 kHz1.2105 (3 × 35)105n761427-14325100155 MHz/15 kHzN/A11 ΔFSRrepresents that among three synchronization rasters, each synchronization raster is located at an interval indicated by ΔFSRon the frequency axis. In the above table, when the channel bandwidth of 100 kHz is used in the band refarmed from the LTE, three synchronization rasters shifted every 100 kHz may be used. Each synchronization raster may be calculated by assuming the 300 kHz channel raster. For example, in the case of band n5 of the above table, the bandwidth is 25 MHz and ΔFCRis 100 kHz. In this case, when the subcarrier spacing (SCSData) of data is 15 kHz, the number of synchronization rasters is 60 and when the subcarrier spacing (SCSData) of data is 30 kHz, the number of synchronization rasters is 45. Thus, the total number of synchronization rasters which may be effective in band n5 is 105 (=60+45). Meanwhile, based on option 2 above, the synchronization raster may be organized as shown in the table below with respect to the existing NR frequency band. TABLE 21DataTotalBand-subcarrierNumber ofnumber ofDLwidthspacingsynchroni-synchroni-NRfrequencyBWΔFCR(SCSData)ΔFSRzatonzationbandband[MHz][kHz][kHz]CBW min/SCSSS[MHz]rastersrastersn12110-217060100155 MHz/15 kHz1177 (3 × 59)177n21930-199060100155 MHz/15 kHz1177 (3 × 59)177n31805-188075100155 MHz/15 kHz1222 (3 × 74)222n5869-89425100155 MHz/15 kHz172 (3 × 24)1173010 MHz/30 kHz1.545 (3 × 15)n72620-269070100155 MHz/15 kHz1207 (3 × 69)207n8925-96035100155 MHz/15 kHz1102 (3 × 34)102n20791-82130100155 MHz/15 kHz187 (3 × 29)87n28758-80345100155 MHz/15 kHz1132 (3 × 44)132n382570-2620501003010 MHz/30 kHz1.596 (3 × 32)96n501432-151785100155 MHz/15 kHz1252 (3 × 84)252n511427-14325100155 MHz/15 kHzN/A11n662110-220090100155 MHz/15 kHz1267 (3 × 89)4443010 MHz/30 kHz1.5177 (3 × 59)n701995-202025100155 MHz/15 kHz172 (3 × 24)72n71617-65235100155 MHz/15 kHz1102 (3 × 34)102n741475-151843100155 MHz/15 kHz1126 (3 × 42)126n761427-14325100155 MHz/15 kHzN/A11 In the above table, ΔFSRrepresents that among three synchronization rasters, each synchronization raster is located at an interval indicated by ΔFSRon the frequency axis. In the above table, when the channel bandwidth of 100 kHz is used in the band refarmed from the LTE, the synchronization raster may be calculated by assuming the 100 kHz channel raster. The UE may assume that there are three synchronization rasters shifted every 5 kHz at each location. III-3. Synchronization Raster for SCS Based Channel Raster For a frequency band that use an SCS based channel raster, there may be some limitations because units are different between the SCS based channel raster and the offset of the floating synchronization. Thus, the synchronization raster may indicate second and fourth data REs for SCSss of 120 kHz and 240 kHz, respectively. In this regard, for the frequency band using the SCS based channel raster, two methods may be considered in the case of numerology in which data and the SS block are mixed. Option 3) An approach scheme similar to option 1 and option 2 in section III-2 may be used for the SCS based channel raster. Option 4) For standard alone (SA) arrangement, there may be a restriction on using the channel raster. FIG.8Aillustrates an example of a synchronization raster according to option 3 of section III-3 andFIG.8Billustrates an example of a synchronization raster according to option 4 of section III-2. Referring toFIG.8A, for the SCS based channel raster, when mixed numerology is used between the data and the SS block, allocation of the synchronization raster to SCSss of 120 kHz is shown. In addition, referring toFIG.8B, for the SCS based channel raster, when the mixed numerology is used between the data and the SS block, allocation of the synchronization raster to SCSss of 240 kHz is shown. When option 3 is used, the NR may be arranged in all channel rasters regardless of the restriction on the floating synchronization. However, option 3 requires that the UE performs synchronization processes which are two or four times more than option 4. In the case of option 4, there may be a restriction on using the channel raster. For example, the second and fourth channel rasters may be used only in a stand alone (SA) environment using 120 kHz and 240 kHz SCSss, respectively. Considering that the NR band is relatively wider than the LTE/LTE-A band, option 4, which uses the mixed numerology the data and the SSB may be more efficient for the frequency band using the SCS based channel raster. Therefore, the synchronization raster may be proposed as follows. In the case of the NR frequency band using the SCS based channel raster, the synchronization raster is organized as shown in the table below. TABLE 22DataTotalsubcarrierNumber ofnumber ofDLspacingsynchroni-synchroni-NRfrequencyBWFCR(SCSData)ΔFSRzatonzationbandband[MHz][kHz][kHz]CBW min/SCSSS[MHz]rastersrastersn412496-2690194151510 MHz/15 kHz5.775322983010 MHz/30 kHz1.44266 (2 × 133)n773.3-4.2900151510 MHz/30 kHz2.16830 (2 × 415)830n783.3-3.8500151510 MHz/30 kHz2.16460 (2 × 230)460n794.4-5600151540 MHz/30 kHz31.6834 (2 × 17)34n25726.5-29.53000606050 MHz/120 kHz18.72318 (2 × 159)634120100 MHz/240 kHz37.44316 (4 × 79)n25824.25-27.53250606050 MHz/120 kHz18.72344 (2 × 172)684120100 MHz/240 kHz37.44340 (4 × 85)n26037-403000606050 MHz/120 kHz18.72318 (2 × 159)634120100 MHz/240 kHz37.44316 (4 × 79) In the above table, ΔFSRrepresents that among three synchronization rasters, each synchronization raster is located at an interval indicated by ΔFSRon the frequency axis. When the mixed numerology is used between the data and synchronization in the SCS based raster, 2/4 multiple synchronization rasters having the SCS offset may be used for option 3 due to the restriction on the floating synchronization. When option 4 is used, a disadvantage of the channel raster due to the multiple synchronization rasters may be overcome. I-4. Synchronization Raster for Band NR n41 Meanwhile, SCSss needs to be considered in band n41. In band 41, two options may be present as follows. Option 1: Fixed to any one value of 30 kHz or 15 kHz Option 2: Using 15 kHz and 30 kHz as basic SCSss Since a larger synchronization raster may be advantageous to the UE in terms of the cell detection time and the power consumption, it may be better to choose option 1 for band 41. Since the minimum channel bandwidth of n41 is 10 MHz, the synchronization raster due to the support of the basic 15 kHz SCS may be somewhat limited compared to the case of basic 30 kHz SCS. Further, in a higher frequency range, larger SCS may be used more. Therefore, the synchronization raster may be proposed as follows. Proposal: For band n41, as the basic SCS, both 15 kHz and 30 kHz may be used. Further, with respect to the synchronization raster, in the NR, the MIB on the SS block needs to include information for informing an actual location of the RMSI in order for the UE to detect the SS block and then, receive the RMSI. On the other hand, considering the complexity and the required time for the UE, when the synchronization raster is large, a size of a bit for representing the information also increases. Such an increase in bit results in a decrease in decoding rate, resulting in a decrease in reception performance of the SS block. Therefore, the present section additionally proposes signaling for indicating the location of the RMSI. FIG.9illustrates an example of signaling for indicating a location of RMSI. As illustrated inFIG.9, information of 1 bit may be added onto the MIB. A frequency-axis offset of a data region may be defined as illustrated inFIG.9for RMSI transmission due to the 1 bit. FIG.10is a flowchart schematically illustrating an operation of a UE according to the disclosures of this specification. Referring toFIG.10, a user equipment (UE) determines frequency locations of multiple SSBs. In addition, the UE receives at least one SSB among the multiple SSBs. The multiple SSBs may be arranged to be spaced apart from each other by a predetermined offset. Herein, the predetermined offset may be 100 kHz. The at least one SSB may be located at an interval of 1.2 MHz on the frequency axis. The multiple SSBs may include at least three SSBs. The at least one SSB may not be located a center frequency of the cell. The frequency locations may be defined by the synchronization raster. Here, the synchronization raster may be different from the channel raster. According to the disclosures of this specification, the synchronization raster represents the frequency location of the SS block used to obtain system information by the UE. The frequency location of the SS block may be defined as SSREFusing a GSCN number as shown in the table below. TABLE 23Frequency rangeSS block frequency location SSREFGSCNRange of GSCN0-3000MHzN * 1200 kHz + M * 50 kHz,3 N + (M−3)/22-7498N = 1:2499, M ϵ {1, 3, 5} (Note 1)3000-24250MHz3000 MHz + N * 1.44 MHz7499 + N7499-22255N = 0:1475624250-100000MHz24250.08 MHz + N * 17.28 MHz,22256 + N[22256-26639]N = 0:4383 The synchronization raster for each band is illustrated as follows. A distance between GSCNs is represented as a step size as follows. TABLE 24NR operatingSS blockRange of GSCNbandSCS(First - <Step size> - Last)n115 kHz5279 - <1> - 5419n215 kHz4829 - <1> - 4969n315 kHz4517 - <1> - 4693n515 kHz2177 - <1> - 223030 kHz2183 - <1> - 2224n715 kHz6554 - <1> - 6718n815 kHz2318 - <1> - 2395n1215 kHz1828 - <1> - 1858n2015 kHz1982 - <1> - 2047n2515 kHz4829 - <1> - 4981n2815 kHz1901 - <1> - 2002n3415 kHz5030 - <1> - 5056n3815 kHz6431 - <1> - 6544n3915 kHz4706 - <1> - 4795n4015 kHz5756 - <1> - 5995n4115 kHz6246 - <1> - 671430 kHz6252 - <1> - 6714n5115 kHz3572 - <1> - 3574n6615 kHz5279 - <1> - 549430 kHz5285 - <1> - 5488n7015 kHz4993 - <1> - 5044n7115 kHz1547 - <1> - 1624n7515 kHz3584 - <1> - 3787n7615 kHz3572 - <1> - 3574n7730 kHz7711 - <1> - 8329n7830 kHz7711 - <1> - 8051n7930 kHz8480 - <16> - 8880n257120 kHz22388 - <1> - 22558240 kHz22390 - <2> - 22556n258120 kHz22257 - <1> - 22443240 kHz22258 - <2> - 22442n260120 kHz22995 - <1> - 23166240 kHz22996 - <2> - 23164n261120 kHz22446 - <1> - 22492240 kHz22446 - <2> - 22490 The embodiments of the present invention which has been described up to now may be implemented through various means. For example, the embodiments of the present invention may be implemented by hardware, firmware, software, or combinations thereof. In detail, the embodiments will be descried with reference to the drawings.FIG.11is a block diagram illustrating a wireless device and a base station in which a disclosure of this specification is implemented. Referring toFIG.11, a wireless device100and a base station200may implement the disclosure of this specification. The illustrated wireless device100includes a processor101, a memory102, and a transceiver103. Similarly, the illustrated base station200includes a processor201, a memory202, and a transceiver203. The processors101and201, the memories102and202and the transceivers103and203illustrated may be implemented as separate chips, or at least two blocks/functions may be implemented through a single chip. The transceivers103and203include transmitters and receivers. When a specific operation is performed, only the operation of either the transmitter or the receiver may be performed, or both the transmitter and the receiver operations may be performed. The transceivers103and203may include one or more antennas that transmit and/or receive the radio signals. In addition, the transceivers103and203may include an amplifier for amplifying a reception signal and/or a transmission signal, and a band-pass filter for transmission on a specific frequency band. The processors101and201may implement functions, processes, and/or methods proposed in this specification. The processors101and201may include encoders and decoders. For example, the processors101and202may perform operations according to the foregoing description. The processors101and201may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, a data processing device and/or a converter converting a baseband signal and the radio signal into each other. The memories102and202may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and/or other storage devices. FIG.12is a detailed block diagram of the transceiver of the wireless device illustrated inFIG.11. Referring toFIG.12, the transceiver110includes a transmitter111and a receiver112. The transmitter111includes a discrete Fourier transform (DFT) unit1111, a subcarrier mapper1112, an IFFT unit1113, a CP inserting unit11144, and a wireless transmitter1115. The transmitter111may further include a modulator. Further, the transceiver110may further include a scramble unit, a modulation mapper (not shown), a layer mapper, and a layer permutator, which may be arranged before the DFT unit1111. That is, in order to prevent an increase in peak-to-average power ratio (PAPR), the transmitter111first passes information through the DFT1111before mapping a signal to a subcarrier. A signal spread (or precoded in the same sense) by the DFT unit1111is subcarrier-mapped through the subcarrier mapper1112and then made to a signal on a time axis through the inverse fast Fourier transform (IFFT) unit1113. The DFT unit1111performs DFT on the input symbols to output complex-valued symbols. For example, when Ntx symbols are input (however, Ntx is a natural number), the DFT size is Ntx. The DFT unit1111may be referred to as a transform precoder. The subcarrier mapper1112maps the complex-valued symbols to subcarriers in the frequency domain. The complex-valued symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission. The subcarrier mapper1112may be referred to as a resource element mapper. The IFFT unit1113performs IFFT on the input symbol and outputs a baseband signal for data, which is a time domain signal. The CP inserting unit1114copies a part of the rear part of the base band signal for data and inserts the copied rear part to the front part of the base band signal for data. Inter-symbol interference (ISI) and inter-carrier interference (ICI) are prevented through CP insertion, and orthogonality may be maintained in a multi-path channel. On the other hand, the receiver112includes a wireless receiving unit1121, a CP removing unit1122, an FFT unit1123, and an equalizing unit1124. The wireless receiving unit1121, the CP removing unit1122and the FFT unit1123of the receiver112perform a reverse function of the wireless receiving unit1115, the CP removing unit1114and the FFT unit1113of the transmitter111. The receiver112may further include a demodulator. | 67,815 |
11943724 | DETAILED DESCRIPTION FIG.1Ais a diagram illustrating an example communications system100in which one or more disclosed embodiments may be implemented. The communications system100may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system100may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems100may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like. As shown inFIG.1A, the communications system100may include wireless transmit/receive units (WTRUs)102a,102b,102c,102d, a RAN104/113, a CN106/115, a public switched telephone network (PSTN)108, the Internet110, and other networks112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs102a,102b,102c,102dmay be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs102a,102b,102c,102d, any of which may be referred to as a “station” and/or a “STA”, may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs102a,102b,102cand102dmay be interchangeably referred to as a UE. The communications systems100may also include a base station114aand/or a base station114b. Each of the base stations114a,114bmay be any type of device configured to wirelessly interface with at least one of the WTRUs102a,102b,102c,102dto facilitate access to one or more communication networks, such as the CN106/115, the Internet110, and/or the other networks112. By way of example, the base stations114a,114bmay be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations114a,114bare each depicted as a single element, it will be appreciated that the base stations114a,114bmay include any number of interconnected base stations and/or network elements. The base station114amay be part of the RAN104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station114aand/or the base station114bmay be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station114amay be divided into three sectors. Thus, in one embodiment, the base station114amay include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station114amay employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions. The base stations114a,114bmay communicate with one or more of the WTRUs102a,102b,102c,102dover an air interface116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface116may be established using any suitable radio access technology (RAT). More specifically, as noted above, the communications system100may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station114ain the RAN104/113and the WTRUs102a,102b,102cmay implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface115/116/117using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA). In an embodiment, the base station114aand the WTRUs102a,102b,102cmay implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface116using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro). In an embodiment, the base station114aand the WTRUs102a,102b,102cmay implement a radio technology such as NR Radio Access, which may establish the air interface116using New Radio (NR). In an embodiment, the base station114aand the WTRUs102a,102b,102cmay implement multiple radio access technologies. For example, the base station114aand the WTRUs102a,102b,102cmay implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs102a,102b,102cmay be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB). In other embodiments, the base station114aand the WTRUs102a,102b,102cmay implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like. The base station114binFIG.1Amay be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station114band the WTRUs102c,102dmay implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station114band the WTRUs102c,102dmay implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station114band the WTRUs102c,102dmay utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown inFIG.1A, the base station114bmay have a direct connection to the Internet110. Thus, the base station114bmay not be required to access the Internet110via the CN106/115. The RAN104/113may be in communication with the CN106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs102a,102b,102c,102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN106/115may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown inFIG.1A, it will be appreciated that the RAN104/113and/or the CN106/115may be in direct or indirect communication with other RANs that employ the same RAT as the RAN104/113or a different RAT. For example, in addition to being connected to the RAN104/113, which may be utilizing a NR radio technology, the CN106/115may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. The CN106/115may also serve as a gateway for the WTRUs102a,102b,102c,102dto access the PSTN108, the Internet110, and/or the other networks112. The PSTN108may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet110may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks112may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks112may include another CN connected to one or more RANs, which may employ the same RAT as the RAN104/113or a different RAT. Some or all of the WTRUs102a,102b,102c,102din the communications system100may include multi-mode capabilities (e.g., the WTRUs102a,102b,102c,102dmay include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU102cshown inFIG.1Amay be configured to communicate with the base station114a, which may employ a cellular-based radio technology, and with the base station114b, which may employ an IEEE 802 radio technology. FIG.1Bis a system diagram illustrating an example WTRU102. As shown inFIG.1B, the WTRU102may include a processor118, a transceiver120, a transmit/receive element122, a speaker/microphone124, a keypad126, a display/touchpad128, non-removable memory130, removable memory132, a power source134, a global positioning system (GPS) chipset136, and/or other peripherals138, among others. It will be appreciated that the WTRU102may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. The processor118may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor118may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU102to operate in a wireless environment. The processor118may be coupled to the transceiver120, which may be coupled to the transmit/receive element122. WhileFIG.1Bdepicts the processor118and the transceiver120as separate components, it will be appreciated that the processor118and the transceiver120may be integrated together in an electronic package or chip. The transmit/receive element122may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station114a) over the air interface116. For example, in one embodiment, the transmit/receive element122may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element122may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element122may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element122may be configured to transmit and/or receive any combination of wireless signals. Although the transmit/receive element122is depicted inFIG.1Bas a single element, the WTRU102may include any number of transmit/receive elements122. More specifically, the WTRU102may employ MIMO technology. Thus, in one embodiment, the WTRU102may include two or more transmit/receive elements122(e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface116. The transceiver120may be configured to modulate the signals that are to be transmitted by the transmit/receive element122and to demodulate the signals that are received by the transmit/receive element122. As noted above, the WTRU102may have multi-mode capabilities. Thus, the transceiver120may include multiple transceivers for enabling the WTRU102to communicate via multiple RATs, such as NR and IEEE 802.11, for example. The processor118of the WTRU102may be coupled to, and may receive user input data from, the speaker/microphone124, the keypad126, and/or the display/touchpad128(e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor118may also output user data to the speaker/microphone124, the keypad126, and/or the display/touchpad128. In addition, the processor118may access information from, and store data in, any type of suitable memory, such as the non-removable memory130and/or the removable memory132. The non-removable memory130may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory132may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor118may access information from, and store data in, memory that is not physically located on the WTRU102, such as on a server or a home computer (not shown). The processor118may receive power from the power source134, and may be configured to distribute and/or control the power to the other components in the WTRU102. The power source134may be any suitable device for powering the WTRU102. For example, the power source134may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like. The processor118may also be coupled to the GPS chipset136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU102. In addition to, or in lieu of, the information from the GPS chipset136, the WTRU102may receive location information over the air interface116from a base station (e.g., base stations114a,114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU102may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment. The processor118may further be coupled to other peripherals138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals138may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals138may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor. The WTRU102may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit139to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor118). In an embodiment, the WTRU102may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)). FIG.10is a system diagram illustrating the RAN104and the CN106according to an embodiment. As noted above, the RAN104may employ an E-UTRA radio technology to communicate with the WTRUs102a,102b,102cover the air interface116. The RAN104may also be in communication with the CN106. The RAN104may include eNode-Bs160a,160b,160c, though it will be appreciated that the RAN104may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs160a,160b,160cmay each include one or more transceivers for communicating with the WTRUs102a,102b,102cover the air interface116. In one embodiment, the eNode-Bs160a,160b,160cmay implement MIMO technology. Thus, the eNode-B160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU102a. Each of the eNode-Bs160a,160b,160cmay be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown inFIG.10, the eNode-Bs160a,160b,160cmay communicate with one another over an X2 interface. The CN106shown inFIG.10may include a mobility management entity (MME)162, a serving gateway (SGW)164, and a packet data network (PDN) gateway (or PGW)166. While each of the foregoing elements are depicted as part of the CN106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. The MME162may be connected to each of the eNode-Bs162a,162b,162cin the RAN104via an S1 interface and may serve as a control node. For example, the MME162may be responsible for authenticating users of the WTRUs102a,102b,102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs102a,102b,102c, and the like. The MME162may provide a control plane function for switching between the RAN104and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA. The SGW164may be connected to each of the eNode Bs160a,160b,160cin the RAN104via the S1 interface. The SGW164may generally route and forward user data packets to/from the WTRUs102a,102b,102c. The SGW164may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs102a,102b,102c, managing and storing contexts of the WTRUs102a,102b,102c, and the like. The SGW164may be connected to the PGW166, which may provide the WTRUs102a,102b,102cwith access to packet-switched networks, such as the Internet110, to facilitate communications between the WTRUs102a,102b,102cand IP-enabled devices. The CN106may facilitate communications with other networks. For example, the CN106may provide the WTRUs102a,102b,102cwith access to circuit-switched networks, such as the PSTN108, to facilitate communications between the WTRUs102a,102b,102cand traditional land-line communications devices. For example, the CN106may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN106and the PSTN108. In addition, the CN106may provide the WTRUs102a,102b,102cwith access to the other networks112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. Although the WTRU is described inFIGS.1A-1Das a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. In representative embodiments, the other network112may be a WLAN. A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication. When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS. High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel. Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC). Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life). WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available. In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code. FIG.1Dis a system diagram illustrating the RAN113and the CN115according to an embodiment. As noted above, the RAN113may employ an NR radio technology to communicate with the WTRUs102a,102b,102cover the air interface116. The RAN113may also be in communication with the CN115. The RAN113may include gNBs180a,180b,180c, though it will be appreciated that the RAN113may include any number of gNBs while remaining consistent with an embodiment. The gNBs180a,180b,180cmay each include one or more transceivers for communicating with the WTRUs102a,102b,102cover the air interface116. In one embodiment, the gNBs180a,180b,180cmay implement MIMO technology. For example, gNBs180a,108bmay utilize beamforming to transmit signals to and/or receive signals from the gNBs180a,180b,180c. Thus, the gNB180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU102a. In an embodiment, the gNBs180a,180b,180cmay implement carrier aggregation technology. For example, the gNB180amay transmit multiple component carriers to the WTRU102a(not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs180a,180b,180cmay implement Coordinated Multi-Point (CoMP) technology. For example, WTRU102amay receive coordinated transmissions from gNB180aand gNB180b(and/or gNB180c). The WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cusing transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cusing subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time). The gNBs180a,180b,180cmay be configured to communicate with the WTRUs102a,102b,102cin a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cwithout also accessing other RANs (e.g., such as eNode-Bs160a,160b,160c). In the standalone configuration, WTRUs102a,102b,102cmay utilize one or more of gNBs180a,180b,180cas a mobility anchor point. In the standalone configuration, WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cusing signals in an unlicensed band. In a non-standalone configuration WTRUs102a,102b,102cmay communicate with/connect to gNBs180a,180b,180cwhile also communicating with/connecting to another RAN such as eNode-Bs160a,160b,160c. For example, WTRUs102a,102b,102cmay implement DC principles to communicate with one or more gNBs180a,180b,180cand one or more eNode-Bs160a,160b,160csubstantially simultaneously. In the non-standalone configuration, eNode-Bs160a,160b,160cmay serve as a mobility anchor for WTRUs102a,102b,102cand gNBs180a,180b,180cmay provide additional coverage and/or throughput for servicing WTRUs102a,102b,102c. Each of the gNBs180a,180b,180cmay be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF)184a,184b, routing of control plane information towards Access and Mobility Management Function (AMF)182a,182band the like. As shown inFIG.1D, the gNBs180a,180b,180cmay communicate with one another over an Xn interface. The CN115shown inFIG.1Dmay include at least one AMF182a,182b, at least one UPF184a,184b, at least one Session Management Function (SMF)183a,183b, and possibly a Data Network (DN)185a,185b. While each of the foregoing elements are depicted as part of the CN115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. The AMF182a,182bmay be connected to one or more of the gNBs180a,180b,180cin the RAN113via an N2 interface and may serve as a control node. For example, the AMF182a,182bmay be responsible for authenticating users of the WTRUs102a,102b,102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF183a,183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF182a,182bin order to customize CN support for WTRUs102a,102b,102cbased on the types of services being utilized WTRUs102a,102b,102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like. The AMF162may provide a control plane function for switching between the RAN113and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi. The SMF183a,183bmay be connected to an AMF182a,182bin the CN115via an N11 interface. The SMF183a,183bmay also be connected to a UPF184a,184bin the CN115via an N4 interface. The SMF183a,183bmay select and control the UPF184a,184band configure the routing of traffic through the UPF184a,184b. The SMF183a,183bmay perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like. The UPF184a,184bmay be connected to one or more of the gNBs180a,180b,180cin the RAN113via an N3 interface, which may provide the WTRUs102a,102b,102cwith access to packet-switched networks, such as the Internet110, to facilitate communications between the WTRUs102a,102b,102cand IP-enabled devices. The UPF184,184bmay perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like. The CN115may facilitate communications with other networks. For example, the CN115may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN115and the PSTN108. In addition, the CN115may provide the WTRUs102a,102b,102cwith access to the other networks112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs102a,102b,102cmay be connected to a local Data Network (DN)185a,185bthrough the UPF184a,184bvia the N3 interface to the UPF184a,184band an N6 interface between the UPF184a,184band the DN185a,185b. In view ofFIGS.1A-1D, and the corresponding description ofFIGS.1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU102a-d, Base Station114a-b, eNode-B160a-c, MME162, SGW164, PGW166, gNB180a-c, AMF182a-ab, UPF184a-b, SMF183a-b, DN185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions. The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications. The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data. Based on the general requirements set out by the ITU Radio communication Sector (ITU-R), Next Generation Mobile Networks (NGMN) group and 3rdGeneration Partnership Project (3GPP), a broad classification of the use cases for emerging 5G systems may be depicted as follows: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communications (mMTC) and Ultra Reliable and Low latency Communications (URLLC). Different use cases may focus on different requirements such as higher data rate, higher spectrum efficiency, low power and higher energy efficiency, lower latency and higher reliability. A wide range of spectrum bands ranging from 700 MHz to 80 GHz are being considered for a variety of deployment scenarios. It is well known that as the carrier frequency increases, the severe path loss becomes a crucial limitation to guarantee a sufficient coverage area. Transmission in millimetre wave systems could additionally suffer from non-line-of-sight losses, for example, diffraction loss, penetration loss, oxygen absorption loss, foliage loss, etc. During initial access, a base station and WTRU may need to overcome these high path losses and discover each other. Utilizing dozens or even hundreds of antenna elements to generated beam formed signal is an effective way to compensate the severe path loss by providing significant beam forming gain. Beamforming techniques may include digital, analog and hybrid beamforming. Cell search is the procedure by which a WTRU acquires time and frequency synchronization with a cell and detects the Cell ID of that cell. LTE synchronization signals are transmitted are transmitted in the 0th and 5th subframes of every radio frame and are used for time and frequency synchronization during initialization. As part of the system acquisition process, a WTRU synchronizes sequentially to the OFDM symbol, slot, subframe, half-frame, and radio frame based on the synchronization signals. The two synchronization signals are primary synchronization signal (PSS) and secondary synchronization signal (SSS). The PSS is used to obtain slot, subframe and half-frame boundary. It also provides physical layer cell identity (PCI) within the cell identity group. The SSS is used to obtain the radio frame boundary. It also enables the WTRU to determine the cell identity group, which may range from 0 to 167. Following a successful synchronization and PCI acquisition, the WTRU decodes the Physical Broadcast Channel (PBCH) with the help of CRS and acquire the MIB information regarding system bandwidth, System Frame Number (SFN) and PHICH configuration. It should be noted the LTE synchronization signals and PBCH are transmitted continuously according to the standardized periodicity. It was agreed in NR that no blind detection of NR-PBCH transmission scheme or number of antenna ports is required by the WTRU. For NR-PBCH transmission, a single fixed number of antenna port(s) is supported. For NR-PBCH transmission, NR may employ both digital and analog beamforming technologies, especially for high frequency band. Digital beamforming using multi-antenna technologies and/or analog beamforming using single or multi-port beamforming technologies may be considered in NR. For reference signal of NR-PBCH demodulation, NR may employ the use of a synchronization signal (e.g. NR-SSS) or self-contained DMRS for NR-PBCH demodulation. A mobility reference signal (MRS) may also be multiplexed in an SS block if MRS is supported in an SS block. The numerology of NR-PBCH may be the same or different as that of NR-SSS. Embodiments for digital beamforming using multi-antenna technologies, analog beamforming using single or multi-port beamforming technologies or hybrid scheme that combines both digital and analog beamforming have been considered for data transmission in connected mode. The similar technologies should also be considered in idle mode or for initial access and designed for broadcast channel such as NR-PBCH for optimum system performance. NR-PSS and/or NR-SSS may be used as a reference signal for NR-PBCH demodulation. Alternatively, a reference signal that is dedicated to NR-PBCH may be used. Such reference signal may be self-contained within NR-PBCH signal and channel. Even without an additional signal or reference signal, a receiver may still be able to demodulate an NR-PBCH signal and channel. Such reference signal for demodulation or demodulation reference signal (DMRS) is specific to NR-PBCH and may be multiplexed and embedded within NR-PBCH resources. By doing so an NR-PBCH dedicated demodulation reference signal (DMRS) may be used for NR-PBCH demodulation. The term DMRS may refer to a demodulation reference signal or demodulation reference signals as used herein. In order to use NR-SS (either NR-PSS or NR-SSS) as a reference signal for NR-PBCH demodulation, time-division multiplexing (TDM) of NR-SS and NR-PBCH may be preferred. FIG.2depicts NR-PBCH multiplexing with NR-PSS and NR-SSS, where NR-PBCH, NR-PSS and NR-SSS are multiplexed in a TDM fashion. NR-PBCH signal and channel may be repeated and may be placed before or after NR-SS. Such a design may be used for but is not limited to a carrier frequency offset compensation purpose. As depicted inFIG.2, each one of PSS204,214,226, SSS206,218,228and PBCH208,210,216,220,224,230occupy a same frequency. In a first example, option 1202, PSS204is transmitted prior to SSS206, followed by first PBCH208and second PBCH210. In option 2212, PSS214is transmitted prior to PBCH216, followed by SSS218and PBCH220. Option 2212may be used to provide PBCH information prior to complete synchronization. In option 2212, PSS214is transmitted before PBCH216, SSS218and PBCH220. In yet another option, option 3222, PBCH224is transmitted prior to PSS226followed by SSS228and PBCH230. Option 3222may allow for PBCH information to be received prior to any synchronization information. Similarly,FIG.3is a timing diagram300which depicts use of an NR-SS signal in two different options310,320. Either NR-PSS or NR-SSS or both may be repeated and may be placed before or after NR-PBCH. The repeated NR-PSS or NR-SSS may also be used for but is not limited to carrier frequency offset estimation or compensation purposes. As shown inFIG.3, in option 4310, a first PSS transmission312may be made prior to a second PSS transmission314. After the second PSS transmission314an SSS transmission316may be sent followed by a PBCH transmission318. In option 5320, an SSS322may be transmitted prior to a PSS transmission324. An SSS transmission326may follow the PSS transmission324along with an SSS transmission326and PBCH transmission328. FIG.4is an example illustration of a first NR-PBCH dedicated demodulation reference signal design400in which one antenna port is used in two options401,420. In both option 1402and option 2420, one antenna port for NR-PBCH dedicated DMRS is used. In the first option, option 1402, the repeated NR-PBCH dedicated DMRS are placed in the same frequency location or subcarriers in order to assist carrier frequency offset (CFO) estimation. In one example, DMRS404is in a same frequency location as DMRS406; DMRS408is in a same frequency location as DMRS410; DMRS412is in a same frequency location as DMRS414and DMRS416is in a same frequency location as DMRS418. In a second option, option 2420, another pattern for NR-PBCH DMRS is used in which DMRS are placed with a fixed offset in frequency domain to cover other frequency locations or subcarriers and/or obtain frequency diversity. For example, if the DMRS density is ⅙ for both the NR-PBCH symbols, the DMRS in the second PBCH OFDM symbol may be offset by 3 REs with respective to the first PBCH OFDM symbol. This may create a perfect comb-pattern for DMRS between two NR-PBCH OFDM symbols. The combined or joint DMRS in two PBCH OFDM symbols may effectively become DMRS density of ⅓ in lower Doppler channels and channel estimation performance may be improved. This may come at an expense of not being able to estimate or correct CFO using DMRS. However, a mapping of data RE in this case may have some data REs repeated in case PBCH data is repeated in the second PBCH OFDM symbol, which may be used for CFO estimation and compensation. As shown in option 2,420, DMRS422is offset from DMRS430; DMRS424is offset from DMRS432; DMRS426is offset from DMRS434and DMRS428is offset from DMRS436. FIG.5is a third example of an NR-PBCH dedicated demodulation reference signal design500using two antenna ports in two options502,540. An NR-PBCH dedicated DMRS with two antenna ports is depicted inFIG.5. In the first option502the repeated NR-PBCH dedicated DMRS504-534are placed in the same frequency location or subcarriers for each antenna port in order to assist CFO estimation. In the second option, option 2540another pattern for NR-PBCH DMRS is used in which DMRS for two antenna ports are placed with a fixed offset in frequency domain to cover other frequency locations or subcarriers and/or obtain frequency diversity. In option 2540DMRS1542,548,550,556,558,564,566,572and DMRS2544,546,552,554,560,562,568,570are alternated in frequency. In one or more embodiments, a hybrid dedicated demodulation reference signal (H-DMRS) may be utilized. Some of the repeated NR-PBCH dedicated DMRS may be placed in the same frequency location or subcarriers for each antenna port in order to assist CFO estimation and others of the repeated NR-PBCH dedicated DMRS may be placed in the different frequency locations or subcarriers and/or obtain frequency diversity. FIG.6is an illustration600of two different NR-PBCH hybrid dedicated demodulation reference signal (H-DMRS) designs602,620. As shown inFIG.6, in a hybrid 1-port approach602, DMRS604may be in a same frequency location as DMRS606while DMRS608may be in a different frequency location from DMRS610. DMRS612may be located in a same frequency location as DMRS614, while DMRS616is located in a different frequency location from DMRS618. In a hybrid 2-port620approach, DMRS1622may be in a same frequency location as DMRS1624; DMRS2626may be in a same frequency location as DMRS2628; DMRS1630may be in a same frequency location as DMRS2632; DMRS2634may be in a same frequency location as DMRS1636; DMRS1638may be in a same frequency location as DMRS1640; DMRS2642may be in a same frequency location as DMRS2644; DMRS1646may be in a same frequency location as DMRS2648; and DMRS2650may be in a same frequency location as DMRS1652. DMRS is transmitted on two different ports. In an example, DMRS1 is transmitted from antenna port 1 and DMRS2 is transmitted from antenna port two with a fixed offset in frequency. If the offset is zero, the DMRS for both antenna ports have the same frequency locations In an embodiment, a non-uniform DMRS density which may employ a different density of demodulation reference signal (DMRS) may be used. In the a OFDM symbol of NR-PBCH, a higher density DMRS may be placed to assist in channel estimation. However, a lower density of DMRS may be placed in the second OFDM symbol of NR-PBCH for reducing the overhead of the DMRS. These DMRS may be the same as the DMRS for the same sub-carrier in the first OFDM symbol of NR-PBCH, which may facilitate estimation of the CFO. This may decrease the code-rate. As the second symbol is closer to the SSS, channel estimation may be supported through use of the SSS. FIG.7depicts a non-uniform density NR-PBCH demodulation reference signal700for use in two different configuration options702,720. In an embodiment, precoding may or may not be applied to the pilot sub-carrier. Precoding may also be used to remove the common phase error for the second OFDM symbol, hence improving detection performance of NR-PBCH at the receiver. NR-PBCH/SS multiplexing embodiments as well as DMRS allocation embodiments may allow for both efficient and high performing NR-PBCH demodulation.FIG.4andFIG.5show how the DMRS may be mapped to the same frequency location across symbols to, for example, improve the performance of CFO estimation. These FIGs also show that the DMRS may be mapped with a fixed frequency offset between symbols, which may improve channel estimation due to the frequency diversity obtained. Both of these performance enhancing techniques may be realized using a hybrid DMRS mapping similar to that shown inFIG.6. InFIG.7and other embodiments, the PSS and/or SSS may be used to assist in the channel estimation where the DMRS density is lower. This may be referred to as a diverse density (DD) method.FIG.7illustrates a DD-DMRS 1-port702and DD-DMRS 2-port720embodiments. In the DD-DMRS 1-port702embodiment, a PSS signal704may be transmitted before an SSS signal706. Prior to the PSS signal704DMRS708,712,714,718may be transmitted at a first time. After the SSS signal706, DMRS signals710,716may be transmitted at a second time. At the second time there may be a lower number of DMRS transmitted. DMRS signals708,710,714,716of the first and second time may partially overlap in frequency as shown. In the DD-DMRS 2-port720example, more DMRS signals726-744may be transmitted as compared to the DD-DMRS 1-port702example. These DMRS726-744may be transmitted before the PSS722and after the SSS724, similar to the 1-port option702. In one example, the NR-PSS and NR-SSS having a different bandwidth allocation compared to NR-PBCH. For example, the NR-PSS and NR-SSS may use 12 RBs, whereas PBCH uses 24 RBs. Hence there are 12 RBs of PBCH which overlaps with NR-PSS/NR-SSS and another 12 which don't overlap with NR-PSS/NR-SSS. In the receiver after the detection of cell-ID, NR-PSS and NR-SSS may be considered as known sequences that may serve as reference symbols for demodulating the overlapping RBs of the NR-PBCH. This technique may be used to improve performance and/or increase efficiency of the design. A performance improvement may be realized by allowing the NR-PSS and/or NR-SSS to assist in the channel estimation, while efficiency is realized by allowing the reduction or even full removal of the DMRS within the SS bandwidth. This concept is illustrated inFIG.8. The left side800ofFIG.8shows a design where SS Block mapping order is NR-[PSS PBCH1 SSS PBCH2]. The right side830ofFIG.8shows a design where the SS Block mapping order is NR-[PBCH1 PSS SSS PBCH2]. The same design for DMRS may apply to other possible mapping orders are NR-[PSS-SSS-PBCH1-PBCH2], NR-[PSS-PBCH1-PBCH2-SSS]. As shown inFIG.8, the center RBs806,808of NR-PBCH symbol one802or symbol two804have no-DMRS or a reduced density DMRS. This increases number of REs available for data transmission and hence reduces the effective code-rate for the same payload. If the channel estimation performance is similar, a reduced effective coding rate may improve the performance. If no DMRS are used for the center RBs, PSS810, or SSS812or both may be used for channel estimation. If reduced density DMRS are used for the center RBs, PSS810, SSS812or both may use as additional assistance along with existing DMRS to do 2D channel estimation for center RBs. PBCH1 DMRS814and818may contain DMRS at full density. The same may be true for PBCH2 DMRS816and820. It should also be noted that the reduction in NR-PBCH density may also depend on the distance from the NR-SSS. In the case of NR-[PSS PBCH1 SSS PBCH2]800, both the NR-PBCH may have same density for DMRS or may have no DMRS. However, in the NR-[PBCH1 PSS SSS PBCH2] configuration830, PBCH1 may have a higher DMRS density than PBCH2 even in the RBs which are overlapping with NR-PSS and NR-SSS. As shown in the NR-[PBCH1 PSS SSS PBCH2] configuration830, PSS832and SSS834are in-between PBCH1836and PBCH2838. PBCH1836and PBCH2838are comprised of no or reduced density DMRS in center frequency sections836and838. PBCH1 DMRS840and844may contain DMRS at full density. The same may be true for PBCH2 DMRS842and846. The DMRS density may be ⅓, ¼, ⅙ or another density depending on a chosen design. If DMRS density is ⅓, it may mean that one out of three resource elements (REs) is used for DMRS. Similarly, if DMRS density is ¼ or ⅙, it may mean that one out of four and six resource elements (REs) is used for DMRS respectively. The various options disclosed may provide different performance advantages as well as efficiency enhancements that may be applicable in different scenarios. In order to allow for all possible options, simple signalling may be provided, for example, on the NR-SSS and/or a new radio tertiary synchronization signal (NR-TSS) to indicate which option is being used. FIG.9is a flow diagram900which details an exemplary performance of a configurable NR-PBCH demodulation. The following example procedure may be used at the receiver. A NR-PSS signal may be searched for902. Timing and frequency information may be acquired904using NR-PSS/NR-SSS. The configuration indicator carried on the NR-SSS indicating reference signal configuration may be decoded and the configuration indicator may be checked906. As an example,FIG.9illustrates two overall reference configurations, configuration 1908and configuration 2910. In configuration 1908, PBCH reference signals are self-contained using DMRS. The DMRS may be mapped according to one of the various configurations shown inFIGS.4-7. This information may also be carried on the NR-SSS. In configuration 2910, joint SS/DMRS reference signals are provided. An exemplary scenario, for configuration 2910may be when the PBCH bandwidth is greater that the SS bandwidth and hence a reduced DMRS density may be used in the overlapping bandwidth. This may be in accordance with an embodiment disclosed with reference to one or more ofFIG.7or8among others. Regardless of choice between configuration 1908or configuration 2910, NR-PBCH may be ultimately demodulated916using estimated channel responses. Examples of this non-uniform DMRS mapping of configuration 2910are shown inFIG.7andFIG.8. The exact density of DMRS in the overlapping region may span from one in reference to using the same density in the non-overlapping regions, to zero, in reference to no DMRS in the overlapping region. Additionally, the DMRS mapping portions may use any of the same techniques shown on the same techniques shown inFIGS.4-6. Finally, as in the configuration 1906case, this lower level of configuration may also be signalled from the NR-SSS and/or NR-TSS. Channel estimation using DMRS only (configuration 1908) may be performed912. Alternatively, channel estimation using joint SS/DMRS (configuration 2910) may be selected914as appropriate. A receiver may use a 2D (Time-Frequency) based algorithm for better joint interpolation across time and frequency. An OFDM symbol for NR-PBCH may be received. The channel estimate to equalize and detect the NR-PBCH symbols may be used and the symbols may be decoded916using the appropriate channel decoder, for example using polar decoding. NR-PBCH may be transmitted on N OFDM symbols. In a first embodiment, NR-PBCH coded bits are mapped across REs in N PBCH symbols, where N is the number of PBCH symbols in a NR-SS block. In a second embodiment, NR-PBCH coded bits are mapped across REs in a PBCH symbol, the NR-PBCH symbol is copied to N−1 NR-PBCH symbol in a NR-SS block. For example, for the case where N=2, the following may be used: in the first embodiment, NR-PBCH coded bits are mapped across REs in both PBCH symbols. In the second embodiment, NR-PBCH coded bits are mapped across REs in NR-PBCH symbol, the NR-PBCH symbol is copied to the second NR-PBCH symbol NR-SS block In the first embodiment, wherein NR-PBCH coded bits are mapped across REs in both PBCH symbols: NR-PBCH coded bits are mapped across REs in N PBCH symbols without repetition. An NR-PBCH resource may be allocated in different ways. The frequency first mapping solution may be used. The data to RE mapping may be mapped in frequency first order. RE mapping may be performed in frequency first and then time second. RE mapping in frequency may be followed by RE mapping in time. RE mapping may be applied to data, DMRS, sequence or the like. In this case, the QPSK symbols generated from data coming from the channel encoder are first mapped to first NR-PBCH OFDM symbol followed by the second or remaining N−1 NR-PBCH OFDM symbol. A time first mapping may be used. The QPSK symbols generated from data coming from channel encoder may be first mapped to a first RE of each NR-PBCH OFDM symbol followed by a second RE of each NR-PBCH OFDM symbol and so on. A hybrid method may be used where the QPSK symbols generated from data coming from channel encoder are first mapped to first (n) RB of each NR-PBCH OFDM symbol followed by second (n) RB of each NR-PBCH OFDM symbol. ‘n’ may be a predefined or configured integer known to both transmitter and receiver. In the second embodiment, wherein NR-PBCH coded bits are mapped across REs in an NR-PBCH symbol, the NR-PBCH symbol is copied to the second NR-PBCH symbol NR-SS block, NR-PBCH coded bits are mapped across REs in a PBCH symbols with repetition. In a simple design, NR-PBCH data (and/or DMRS) may be copied on to the second or the remaining N−1 NR-PBCH OFDM symbol. In another embodiment, frequency hopping of data may be performed. The data mapped to one RB in first NR-PBCH symbol may be mapped to other RB in second NR-PBCH symbol. The pattern of this frequency hopping is known to receiver and hence it may be able to combine them increasing frequency of the decoding. The DMRS in this case may not frequency hop. Hence CFO may be estimated at the receiver using the DMRS location. In other embodiment, frequency hopping may be used only for the 12 RBs which are not overlapping with NR-PSS and NR-SSS. In one embodiment, an offset may be applied in a second PBCH symbol with respect to the first PBCH symbol. This offset may be in terms of a phase of data symbols. This phase offset may be detected at the receiver and implicit information may be decodable. For example, if the phase difference between the first and second symbols are [0, pi/2, pi, 3pi/2] 2 bits of implicit information may be indicated. It also may be possible to have a known shift which is based on cell ID. In this case, the purpose may not be to indicate anything, but rather to randomize the data using a cell-specific shift. This offset may be in terms of frequency location of the data symbols. Similar to phase, this may be cell-specific shift that may be known to increase randomization or used to blindly decode a few bits. The shift may also be a frequency shift, time shift, phase shift or the like or combination of one or more of them. In an embodiment, a hybrid design may be implemented. In this hybrid design, the first center 12 RBs of both PBCH symbols may be filled with all the data. This data may then be copied to the side 12 RBs, for example, 6+6 on both the sides of center. This design is important as all the data symbols are present in center RBs. If SNR is good, this permits the WTRU to detect PBCH using a smaller bandwidth, for example, the 12 RBs in the middle. In this way, a WTRU only has to receive and demodulate the center 12 RB, which may also save power. Frequency hopping may or may not be used here. If frequency hopping is used, the center part of first symbol may be copied on 12 RBs of second symbol; the center part of second symbol may be copied on 12 RBs of first symbol. As a receiver knows this pattern, it may carefully extract and assemble the DMRS block before sending to the channel decoder. This may result in a better performance at the WTRU with a lower SNR; while combining at the receiver, careful demapping of the RE is needed. In another embodiment, a RE mapping may be as a function Cell ID and/or SS Block ID. This embodiment is motivated by the randomization of interference. Before detecting NR-PBCH, a WTRU should have detected the Cell ID using NR-PSS/NR-SSS. Also, in some cases, SS Block ID might be already known before decoding the NR-PBCH. This may be the case, for example, if TSS was transmitted and the SS Block ID was carried by TSS, or some prior knowledge about SS block index is available. It may be desirable to use the DMRS RE mapping as a function of cell ID or SS block index or both. If the frequency location of DMRS is dependent on cell-ID, it may reduce the interference from neighboring cells. For example, this may include a shift of a location for DMRS for one, multiple or all of the OFDM symbols for NR-PBCH. In one or more embodiments, the term SS block ID, SS block index and SS block time index may be used interchangeably. At the receiver, once a WTRU detects NR-PSS/NR-SSS, the Cell ID and/or SS Block ID is known. A WTRU may be able to identify the locations for DMRS of NR-PBCH using Cell ID and/or SS Block ID and the mapping function. The WTRU may then continue with the channel estimation for PBCH using DMRS. PBCH demodulation and decoding is then followed. As different cells are transmitting DMRS on different locations, the interference may be reduced, mitigated or avoided. To achieve even better randomization, the sequence of DMRS (e.g., sequence or scrambling sequence) may also be dependent on cell ID or SS block index or both. The sequence of DMRS (e.g., sequence or scrambling sequence) may also be dependent on other information such as half radio frame indication, either jointly, individually or separately with SS block index or cell ID. DMRS may use any of different sequences. The options may include an M sequence, a Gold sequence, a ZC sequence or PN sequences. Different parameters of these sequences may be function of the cell ID or SS block index. In any of the above cases, DMRS for PBCH may be also used as DMRS for PDSCH. This is true for the RBs occupied by PBCH. Rate matching may be used to convert (512) coded bits to all the used data REs which may change depending on DMRS design. Different sequences may be used as DMRS for the NR-PBCH. One of the sequences of interest is a maximal length sequence (M-Sequence). Due to optimal noise-like characteristics and very good correlation properties, M-Sequences may serve a dual purpose. M-Sequences may be used to deliver information and also may serve as reference symbols for demodulation of the NR-PBCH. As an example, if 24 RBs are allocated for NR-PBCH, then 2 DMRS may exist in each RB in each OFDM symbol. Hence, in each OFDM symbol 48 symbols may be needed as a DMRS. There may be a design choice to have a lower or higher number of DMRS based on a particular embodiment or implementation choice. M Sequences have lengths of 2{circumflex over ( )}M−1, making different options possible. FIG.10Aillustrates circuitry1000configured to produce a length 7 M-sequence. As shown inFIG.10A, there are 7 stages1002-1014representing 7 bits available for shifting. At each clock pulse of the circuitry, a bit from stage 61012is shifted into stage 71014, from stage 51010into stage 61012, from stage 41008into stage 51010, from stage 31006into stage 41008, from stage 21004into stage 31006, and from stage 11002into stage 21004. The output of stage 71014is OR-ed1016with an output of stage 61012and fed into stage 11002. In this way, an input bit is continually shifted into stage 1. Output1018is illustrated from stage 71014. In this way, an M-Sequence of length 127 may be generated from a shift register of length 7 using 7 stages. This may be used for one or both of the OFDM symbols of NR-PBCH. FIG.10Billustrates M-Sequence of length 63 which may be generated from a shift register1020of length 6. In this way, there are only 6 stages1022-1032shown inFIG.10B. Output1036may be achieved from stage 61032. OR1034of stage 51030and stage 61032may be fed into stage 11022. This sequence may be used for one or both of the OFDM symbols of NR-PBCH with some repetition or padding along with some known symbols. For example, all ones may be padded to match length of sequence to number of DMRS needed. It also may be possible to generate a length 31 M-Sequence using a shift register of length 5 and repeat it to cover all the DMRS of each OFDM symbol. A same or different sequence may be used for the other OFDM symbols. It is also possible to concatenate two different M-Sequences of a same or different length. This may enable two shifts at the cost of higher correlation. This increases the amount of information to be transmitted at the expense of confidence on the detection. However, if the sequence is long, this may be a viable option. An M-Sequence may be also scrambled with another sequence or another PN Sequence may also be used. The parameters like shift or the polynomial of the sequence may be a function of the cell-ID. This may enable orthogonal DMRS between different cells. A higher length M-Sequence may provide for a better correlation property. These sequences may be use with different shifts. Using different shifts, it may be possible to indicate [5,6,7] bits of information implicitly using a 31, 62, or 127 M-Sequence bit length. One option may include but is not limited to indicating an SS Block index, indicating details to aid channel decoding of NR-PBCH including information about polar codes and a Beam-ID. This may further be used for any other information that needs very low latency. If SS Block ID is not indicated using the DMRS but known prior to the decoding of the NR-PBCH, the parameters like shift or the polynomial of the sequence may be a function of SS Block ID. The shift may be, but is not limited to, a frequency shift, time shift, phase shift, location shift or the like. A combination of these shift types may also be used. FIG.11is a flowchart1100which illustrates a procedure used for exemplary receiver processing and information detection. A receiver may first acquire timing and frequency1102using NR-PSS and NR-SSS. The receiver may receive1104an OFDM symbol for NR-PBCH. DMRS RE allocation may be a function1106of cell-ID and/or SS Block ID, and the DMRS RE mapping may be found based on the cell-ID and/or SS Block ID. The SS Block ID may be indicated implicitly1108in DMRS, the receiver may use1110NR-PSS to estimate the channel and pre-equalize the REs that contain DMRS for NR-PBCH. The receiver may then extract1118frequency domain symbols for DMRS for NR-PBCH. These symbols are correlated with the original M-Sequence that was used to generate DMRS for PBCH. A strong peak will be given at one of the offsets. This will give the information embedded in DMRS, similar to SS-Block Index. If multiple M-Sequences are used, with careful extraction and correlation, transmission-shifts for each M sequences may be identified. Using the detected shift, a local copy of DMRS may be generated. This may then be used to detect and decode the NR-PBCH. The DMRS sequence may be a function of1112cell-ID and/or SS Block ID and a local copy of DMRS based may be generated based on the cell-ID and/or SS Block ID. The local copy of DMRS may be used for channel estimation for NR-PBCH and to demodulate/decode NR-PBCH. A local copy may be found1114via a lookup1116in a local table or database. In another embodiment, ZC sequences may be used as DMRS for the NR-PBCH. They may be used to deliver information using different cyclic shifts and also serve as reference symbols for demodulation of the NR-PBCH. As an example, if 24 RBs are allocated for NR-PBCH, 2 DMRS in each RB in each OFDM symbol may be had. Hence, in each OFDM symbol, N symbols may be needed for DMRS. N may be 48 in one embodiment. A length of a ZC sequence may be selected to match the number of DMRS. The best root for the ZC sequence may be determined by simulation. It is also possible to concatenate two different ZC sequences of a same or different length. A ZC sequence may be also scrambled with another PN sequence or M sequence. Parameters, for example, a root of ZC sequence or the cyclic shift of the ZC the sequence may be a function of the cell-ID. This may enable orthogonal DMRS between different cells. The higher the length of the ZC-Sequence, the better the correlation property. These sequences may be used with different cyclic shifts. Using different shifts, it may be possible to carry [4,5,6] bits of information for 31, 62, 127 length of ZC-Sequences respectively, which may be used to indicate information to aid channel decoding of NR-PBCH, This may include information about polar encoding and/or decoding including Beam-ID. It is also possible to use different roots of ZC sequence. A WTRU may be able to blindly identify the ZC sequence used. This may be used to convey implicit information as well. This may be used for any other information that needs very low latency. If SS Block ID is not indicated using the DMRS but known prior to the decoding of the NR-PBCH, the parameters like root of ZC sequence or the cyclic shift of the ZC the sequence may be a function of SS Block ID. For receiver processing, the following procedure may be used to detect information. A receiver may first acquire timing and frequency using NR-PSS/NR-SSS. The receiver may receive an OFDM symbol for NR-PBCH. DMRS RE allocation may be a function of cell-ID and/or SS Block ID and the DMRS RE mapping may be acquired based on the cell-ID and/or SS Block ID. The DMRS sequence may be a function of cell-ID and/or SS Block ID and a local copy of DMRS may be generated based on the cell-ID and/or SS Block ID. A local copy of DMRS may be used for channel estimation for NR-PBCH and demodulate/decode NR-PBCH. Gold sequences may also be used for DMRS. Gold sequences may be generated by multiplying two M sequences with each other. These M sequences should be generated from irreducible primitive polynomials and both the polynomial should be preferred pair. For the design following process may be used. Two M Sequences may be generated from preferred pair polynomial. Two different shifts are used (m0 and m1) for both. These are then XOR-ed. This sequence is BPSK modulated and then repeated or truncated to fill all DMRS. If the chosen length of the M sequences is 31 which may be repeated, a combination of the following polynomial may be used. Octal values are in the order of 45, 75, 67. For: g(x)=x5+x2+1 x(ī+5)=(x(ī+2)+x(ī))mod 2, 0≤ī≤25 For: g(x)=x5+x4+x3+x2+1 x(ī+5)=(x(ī+4)+x(ī+3)+x(ī+2)+x(ī))mod 2, 0≤ī≤25 For: g(x)=x5+x4+x2+x+1 x(ī+5)=(x(ī+4)+x(ī+2)+x(ī+1)+x(ī))mod 2, 0≤ī≤25 Other irreducible primitive polynomials are not excluded (Octal value 51, 37, 73). Initialization as follows may be used but other initialization may not be precluded: x(0)=0,x(1)=0,x(2)=0,x(3)=0,x(4)=1 If the length of M Sequences 63 (for higher density DMRS) a combination of following polynomial may be used (Octal value in order are 103, 147, 155) For: g(x)=x6+x+1 x(ī+6)=(x(ī+1)+x(ī))mod 2, 0≤ī≤56 For: g(x)=x6+x5+x2+x+1 x(ī+6)=(x(ī+5)+x(ī+2)+x(ī+1)+x(ī))mod 2, 0≤ī≤56 For: g(x)=x6+x5+x3+x2+1 x(ī+6)=(x(ī+5)+x(ī+3)+x(ī+2)+x(ī))mod 2, 0≤ī≤56 Other irreducible primitive polynomials are not excluded (Octal values 133, 141, 163). Initialization as follows may be used but other initialization may not be precluded: x(0)=0,x(1)=0,x(2)=0,x(3)=0,x(4)=0x(5)=1 Shifts in two sequence may be defined using the following equations. Where the s1, s2 are the two sequences of length L. m0 and m1 are two shifts. Value of n goes from 0 to L−1. s1(m0)(n)={tilde over (s)}1((n+m0)modL) s2(m1)(n)={tilde over (s)}2((n+m1)modL) A combination function m0 and m1 may be used to indicate the following: details to aid channel decoding of NR-PBCH, which may include information about polar encoding and/or decoding; and a beam-ID. In another option, parameters such as the polynomial of the sequence and/or the shift of the sequence(s) may be a function of the cell-ID. This may enable orthogonal DMRS between different cells. If SS Block ID is not indicated using the DMRS but known prior to the decoding of the NR-PBCH, those parameters may also be a function of SS Block ID. For receiver processing, the following procedure may be used to detect the information: the receiver may first acquire timing and frequency using NR-PSS/NR-SSS; the receiver may receive an OFDM symbol for NR-PBCH; the DMRS RE allocation may be a function of cell-ID and/or SS Block ID and the DMRS RE mapping may be acquired based on cell-ID and/or SS Block ID; the DMRS sequence may be a function of cell-ID and/or SS Block ID, a local copy of DMRS may be generated based on cell-ID and/or SS Block ID; a local copy of DMRS may be used for channel estimation for NR-PBCH and to demodulate/decode the NR-PBCH. The NR-PBCH may employ precoder cycling techniques to improve performance. In this case, the NR-PBCH reference signal(s), DMRS and/or SS, may or may not also be precoded using the same precoder cycling pattern as the NR-PBCH data. Assuming the same precoder is used, the precoder cycling may be applied either in the frequency domain or the time domain. For frequency domain precoder cycling some different options that may be used are detailed below: A single precoder per NR-PBCH may be uses. A single precoder may be applied to all the RBs, for example, 24 RBs, NR-PBCH data and associated reference signals. The DMRS may be generated from a single sequence, for example, a M, ZC or Gold Sequence, since a longer sequence may improve detection performance. The DMRS may also be generated from two separate sequences split over the bandwidth. A single precoder per RBG may be used. The RBs, along with the associated reference signals, in the PBCH may be divided into multiple RB groups (RBG) and a different precoder may be applied to each group. It should be noted that using different precoders may increase frequency diversity and hence improve performance. In general, the RBG may vary from 1 to N, where N is the number of RBs in the NR-PBCH, which in this case reverts back to the option above. The pattern may be known by the WTRU either via signaling from the SS or defined prior. Each RBG may use a different sequence; however it may be important to adjust the number of DMRS and length of sequences to match each other. Sequence length should be such that an attempt to achieve optimal correlation properties is made, and as such a particular sequence may span more multiple RBGs. A single precoder may be used per sub-RB. In an exemplary scenario, one precoder may be used per RE, subcarrier or OFDM symbol for PBCH. A predefined precoder cycling pattern may be used across REs, subcarriers or OFDM symbols for PBCH. One precoder per DMRS group may be used. One DMRS group may be defined as half RB, partition of RB, or RE group (REG). An association between DMRS REs and data REs in a PBCH may be defined. This may also improve frequency diversity. Precoder cycling may also be applied in the time domain. For time domain precoder cycling, some different options that may be used are detailed herein. A single precoder may be applied for all NR-PBCH transmissions. In this case, a single precoder is applied to all PBCH data and reference signals. Different Precoders per modulo(n) NR-PBCH transmissions may be applied. In this case, a different precoder is applied for each NR-PBCH transmission per modulo(n). For example, when n=2 the following may apply: NR-PBCH transmission (0) applies precoder (0), NR-PBCH transmission (1) applies precoder (1), NR-PBCH transmission (3) applies precoder (0), NR-PBCH transmission (4) applies precoder (1), etc. Cycling may allow different WTRUs to obtain enhanced performance on different NR-PBCH transmissions based on each WTRUs unique spatial and frequency domain channel characteristics. In each of the above cases, when there is more than one precoder being applied per NR-PBCH, the cycling pattern may be chosen to maximize the spatial and frequency diversity. In open loop schemes, this cycling pattern is pre-determined and may be chosen for example based on spatial properties for the precoder beams generated. Frequency domain characteristics may also be considered when choosing the precoder pattern in order to maximize the diversity in the frequency domain. In order to use both NR-SS and self-contained DMRS for NR-PBCH demodulation, an indication may be introduced to indicate to a WTRU whether NR-SS and self-contained DMRS may be used jointly for channel estimation and coherent combining for NR-PBCH demodulation. A quasi-co-located (QCL) indicator may be introduced for initial access and NR-PBCH demodulation. When two signals are transmitted from two different antennas, the channels experienced by the two antennas may still have many large-scale properties in common. For example, the two signals may have the same or similar Doppler spread or shift, average delay, average delay spread or average gain, therefore they may be used by the WTRU in the setting of parameters for channel estimation. However when these two antennas are separated in distance, signals from these two antenna ports may differ even in terms of large-scale properties. A QCL indicator may be used to indicate the long-term channel properties of different antenna ports and different reference signals. For example, NR-SS and PBCH-dedicated DMRS may be assumed QCL even they are not in the same antenna port. In multiple transmission point (TRP) (multi-TRP) transmission, NR-SS and PBCH-dedicated DMRS may not be assumed QCL depending on whether or not they are in the same location or not. A QCL indicator may be indicated in NR-SS signal. If a message-based NR-SS is used, the QCL indicator may be carried by a Sync payload. If a sequence-based NR-SS is used, the QCL may be embedded in either NR-PSS or NR-SSS or combination of both. For example, different frequency and/or time relative offset may be used to indicate QCL. Different root indices or cyclic shifts of ZC sequence may be used to indicate QCL. Furthermore, different combinations of X and Y components in either NR-PSS or NR-SSS may be used to indicate QCL. Once QCL is indicated to the WTRU, the WTRU may use both NR-PSS and/or NR-SSS as combined reference signal together with NR-PBCH-dedicated DMRS for channel estimation. QCL-aided initial access and NR-PBCH demodulation may be performed. Such QCL parameters may include but not limited to Doppler spread or shift, channel average delay, channel average delay spread, channel average gain, beam correlation and spatial correlation. FIG.12is a flowchart1200which illustrates an example a QCL indicator-aided or assisted initial access procedure and NR-PBCH demodulation. Demodulation of an NR-PBCH assisted by a QCL indicator is depicted inFIG.12. In this method, a QCL indicator is introduced to assist NR-PBCH demodulation. Depending on the value of the QCL, different configurations of channel estimation may be used for NR-PBCH demodulation. One exemplary method for NR-PBCH demodulation assisted by a QCL indicator is detailed as follows. A WTRU may search1202for an NR-SS signal and may detect1204NR-PSS and NR-SSS. A received QCL indicator and/or the value of the QCL indicator may be checked. If the QCL indicates a first configuration, for example configuration 11208, the WTRU may perform channel estimation1210using both NR-SS and NR-PBCH-DMRS. If the QCL indicates a second configuration, for example configuration 21212, the WTRU may perform channel estimation1214using only NR-PBCH-DMRS. The WTRU may demodulate1216the NR-PBCH signal and channel using the estimated channel responses from either configuration 11208or configuration 21212. Multi-antenna technologies may be used for transmission of NR-PBCH. For example, two port space frequency block coding (SFBC) and two port precoder cycling may be used as multi-antenna technologies for NR-PBCH. A single antenna port may also be used for simplicity reasons. When more than one multi-antenna technology is used for NR-PBCH, information for multi-antenna technologies used for NR-PBCH may be indicated to a WTRU. Such indication may be conveyed via NR-PSS and/or NR-SSS to indicate the one or more multi-antenna technologies or in one embodiment, a MIMO scheme or method to use for NR-PBCH. Both digital and analog beamforming technologies may be used. A hybrid digital and analog beamforming scheme may also be used. Precoder cycling may be used as one of the indicated multi-antenna technologies. Both open-loop and semi-open loop methods may be used. A precoder using a large delay cyclic delay diversity (CDD) and/or small delay CDD, may be used. Precoder cycling patterns may be performed in time and/or frequency and may be predetermined and known to the WTRU. Both an NR-PBCH signal and a channel comprising self-contained DMRS within the NR-PBCH signal may use the same precoder sets and the same precoder cycling patterns may be applied. A gNB or TRP may perform digital beam sweeping in time and/or frequency. Digital beamforming using precoder cycling or SFBC may be combined with analog beamforming and beam sweep for NR-PBCH. Exemplary precoder cycling designs for NR-PBCH are disclosed herein. A transmission of NR-PBCH may be based on two antenna ports with precoder cycling. The transmission on these two ports may have the same or different kinds of precoders and precoder schemes, for example, open-loop (including large delay CDD or small delay CDD), semi-open loop or the like may be utilized. In semi open-loop, the gNB or TRP may apply a precoder, which may be expressed as W=W1·W2, where the wideband precoding matrix W1represents the long-term statistics and the (narrow band) precoding matrix W2represents an instantaneous channel condition. In a semi open-loop PBCH scheme, the long-term precoding matrix W1is fed back from one or more WTRUs to the gNB. This may actually define the set of DFT beams to be used for this WTRU, implying the approximate direction of the WTRU. It should be noted that this semi open-loop procedure may work for a connected mode WTRU. If WTRUs of a cell are located in certain small range of areas of a gNB, then the semi open-loop PBCH scheme might be applied, where W1may be determined by the WTRU locations. The gNB may then cycle the narrow band precoding matrix W2to determine a final precoder. The cycling patterns may be in time and/or frequency domain. A digital precoder or an analog beamformer may be used for W1and a digital beamformer may be used for W2. One exemplary design may use analog beamforming, for example, W1based on DFT and a digital precoder W2. Precoder cycling may be performed on W2. In another exemplary design, a digital W1, for example, DFT-based and W2may be used. Precoder cycling may be performed on W2or both W1and W2. In another exemplary design, a digital W1, for example, a precoder codebook-based and W2may be used. Precoder cycling may be performed on W2, or both W1and W2. Precoder cycling may be performed on analog, digital beamforming or precoding or combination of the two. FIG.13is an example1300of using SS blocks associated with different precoders. In an open-loop CDD transmission of PBCH, the CDD coefficients could be applied at sub-carrier level or at RB level. The cycling patterns could be in time and/or frequency domain. Since the PBCH is repeatedly broadcast over a certain time period, each PBCH message may be associated with a transmission pattern of PBCH.FIG.13shows an example of 4 SS blocks1302-1308each having the same contents. Each SS block1302-1408may be associated with a different precoder1310-1316, which points the PBCH message to different directions. In this example, SS11302is associated with precoder 11310, SS21304is associated with precoder 21312, SS31306is associated with precoder 31314and SS41308is associated with precoder 11316. Each one of precoder 1-41310-1316is shown drawn for illustration purposes only. A quality of each one of the precoders selected may be similar to or different from traditional MIMO precoders of 4G. For example, a three dimensional (3D) precoder may be used. In this way, a third dimension may consider WTRU elevation in a vertical domain. Other precoders may support highly parallel antenna technology. Existing MIMO precoding, for example 4G technologies may also be used. Existing codebooks may be used. New codebooks may be added on top of existing codebooks in a backwards compatible and/or flexible deployment scenario. FIG.14illustrates examples1400of which SS blocks are associated with different precoders, shifted over different PBCH messages1402,14201440,1460. Among different PBCH messages1402,14201440,1460, the association between precoder and SS block might be the same or might be different. In one embodiment the association may be shifted.FIG.14shows an example illustrating ways in which the association of the precoder and the SS block shifts with PBCH messages1402,14201440,1460. Specifically, for the first PBCH message1402, the SS block i is associated with precoder i. In this way, pre-coder 11404is associated with SS block 11406, pre-coder 21408is associated with SS block 21410, pre-coder 31412is associated with SS block 31414and pre-coder 41416is associated with SS block 41418. For the second PBCH message1420, the SS block i is associated with precoder i+1 mod 4; etc. In this way, pre-coder 21422is associated with SS block 11424, pre-coder 31426is associated with SS block 21428, pre-coder 41430is associated with SS block 31432and pre-coder 11434is associated with SS block 41436. In message 31440, pre-coder 31442is associated with SS block 11444, pre-coder 41446is associated with SS block 21448, pre-coder 11450is associated with SS block 31452and pre-coder 21454is associated with SS block 41456. In message 41460, pre-coder 41462is associated with SS block 11464, pre-coder 11466is associated with SS block 21468, pre-coder 21470is associated with SS block 31472and pre-coder 31474is associated with SS block 41476. As noted above with respect toFIG.13, various precoding schemes may be used withFIG.14as well. Some precoding schemes may include nonlinear precoding (NLP) schemes, for example, Tomlinson-Harashima precoding or vector perturbation. Other hybrid precoding schemes may involve semi-dynamic or dynamic switching between linear precoding and NLP. FIG.15is an illustration of transmission circuitry1500configured for an exemplary combination of two port cyclic delay diversity (CDD) with analog beamforming for diversity. The above digital beam sweeping scheme ofFIG.14could be combined with an analog beam sweep.FIG.15shows an example of combining CDD with analog beamforming. This is aimed at exploring more diversity gain over spatial, frequency and time domains.FIG.15illustrates two RF chains, RF chain 11502and RF chain 21504. RF chain 11502circuitry may be configured to transmit1510at time t11506using a first precoder. After a delay period which may be implemented, for example by a timer or clock circuitry1510, a second transmission may be sent1512by RF chain 21504using a second precoder. Second transmission may be sent at time t21508. First transmission1510and second transmission1512may overlap in time partially, fully or not at all. FIG.16is an illustration1600of an exemplary combination of digital and analog beam forming shown in time domain. Suppose there are n1patterns in digital beam sweeping MIMO schemes, and n2patterns in analog beam sweeping schemes. The total of n1·n2combinations for cycling may be supported. An exemplary combination is shown inFIG.14, where n1=n2=2. Furthermore, only an n2beam sweep for an analog beam may be needed, while the digital beam sweep is kept simultaneously. An alternative embodiment is to do the n2beam sweep for analog beam sweep in time domain, while the n1beam sweep for digital sweep may be done in the frequency domain, as shown inFIG.17. As shown inFIG.16, a same digital precoder1602and1604may be used for a first and second transmission. For those same transmissions, two different analog beams1606and1608may be generated. For a third and fourth transmission, a second digital precoder1610and1612may be used. Second digital precoders1610and1612may be the same digital precoder. Analog beam 11614and analog beam 21616may be different analog beams to achieve diversity. FIG.17is an illustration of an exemplary combination of digital and analog beam forming in time and frequency domain. In this embodiment, alternative analog beams are illustrated in time domain while alternative digital beams are shown in frequency domain. With reference toFIG.17, in a first transmission in time a second digital precoder1702is used in a same frequency as a first digital precoder1704. At the same time, two same analog beams1706and1708are transmitted. As a second transmission at another time, two different digital precoders1710and1712are used along with two same analog beams1714and1716. FIG.18is an illustration of an exemplary combining two port space frequency block coding (SFBC) transmitter1800with analog beamforming for transmit diversity. Using circuitry as shown inFIG.18, transmission of NR-PBCH may be based on one or more transmit diversity schemes including a two port SFBC scheme. In a high frequency band for example, a transmission on each port may be associated with multiple antenna elements, and the analog beamforming on each port could be used for further diversity gain.FIG.18shows exemplary SFBC designs combined with analog beamforming to achieve further diversity gain. As shown, the symbols S01802and S11804are sent over different subcarriers, subcarrier 11806and subcarrier 21808, on antenna port 11810, while the symbols −S1* 1814 and S0*1812are sent over different subcarriers, subcarrier 11806and subcarrier 21808, on antenna port 21816. In this example, diversity in the digital domain is achieved via the reversing of S11804, S01802and S0*1814, −S1*1812. In this way, a bit stream provided to each of RF chain 11818and RF chain 21820is inverse. In the analog domain, RF chain 11818and RF chain 21820may each use different beamforming techniques. If so, there may be different beams shapes1822and1824transmitted to a receiver. In one embodiment, the analog beamforming circuitry may adjust beam direction and beam width for each of the antenna ports1810and1816in an SFBC scheme1800. The control of the analog beamforming may be dependent on prior knowledge of WTRU geographic distributions. WTRU geographic distributions or beam-location profiles may be provided by WTRUs via uplink signalling or grant-free access. Communication at frequencies above 6 GHz for 5G NR will likely rely on highly directional transmission and reception. The first steps for establishing a reliable link are the so called initial access procedures, including cell search, PBCH transmission, and an RACH procedure. The procedures associated with the current 4G LTE systems may be used as a baseline. However, since LTE is limited to below 6 GHz, directional transmission and reception is not required and is not built into these initial access procedures. Therefore new initial access procedures may need to be designed that take into account the additional complexities that are associated with directional communication systems. Each transmission and reception beam may cover a limited angular space and therefore a procedure for identifying a beam pair that may be used for communication may need to be established. This procedure may be performed via a beam sweep at the transmission and/or reception points. An addition of a beam sweep procedure may add significant complexity and power consumption, overhead, latency and the like may need to be taken into account. A conventional beam sweep procedure may be include a TRP and WTRU “testing” all combinations of beam pairs and choosing the beam pair that may provide the best performance. The “testing” may be performed by the TRP transmitting a known sequence on a given beam while the WTRU receives a given beam and measures the resulting SINR. The measurement may be repeated for all possible beam pairs and the beam pair that returns the maximum SINR value is chosen. A framework for this type of procedure has been defined at the TRP for 5G NR as depicted inFIG.19. FIG.19is an exemplary TRP transmission structure1900which may be used for initial access. Transmission of the initial access based signals occur during a synchronization signal burst time, Tssb1902and repeats every Tpseconds of an SS period1904. To accommodate a beam sweep procedure Tssb1902may be comprised of an integer number of OFDM symbols1906and1908, where, as an example, each OFDM symbol is transmitted at an OFDM symbol time Tsym1910with a different beam that covers a different angular region. Using this basic framework, a WTRU may additionally sweep through a set of beams and ultimately decide on a beam pair to use for subsequent communications. In this way, for any time Tpseconds it may be possible to cycle through and test a plurality of plurality of beams during initial synchronization. This may provide for a substantial performance improvement as opposed to performing an additional test after synchronization. One straightforward way to design a full beam sweep procedure using the framework defined inFIG.19is to perform an exhaustive search over all available beam pairs at the TRP and WTRU, as shown inFIG.20. FIG.20illustrates an example single stage exhaustive search beam sweep procedure2000. InFIG.20, each SS burst2002,2004,2006may be comprised of N OFDM symbols, where each symbol transmits a single beam and the N beams cover the entire angular region of the TRP2008. Also shown, the WTRU2010receives from a single beam for the entire SS burst so that a full beam sweep requires M SS bursts2012,2014,2016to test all possible beam pairs. It should be noted that in order to account for signal blockage at the WTRU2010, it is likely that there will be more than one receiving array. In one example, an array may be on each side of a rectangular device. With this being the case and with each array supporting M beams the total number of WTRU beams, therefore the total number of SS bursts for a full beam sweep is 4M. As mentioned, system overhead, access latency, and overall power consumption are concerns for the initial access procedures. These concerns are made clear herein with respect to overhead, latency and power consumption. In terms of overhead, each OFDM symbol used for synchronization is not available for other purposes, such as data transmission. This may be a concern for a large N. The duration of the entire procedure may also be viewed as additional overhead with respect to reduced time that may be used for communication. With respect to latency, one of the things that provides an enhanced user experience is the ability to establish a communication link quickly. In this sense, a large M, further coupled with more than one array to combat blocking, may drastically increase access time. Power consumption is another concern, and generally speaking, low power consumption is desirable. Low power consumption is especially desirable at the WTRU since a WTRU is typically a battery operated device. Each beam pair measurement requires WTRU power so that limiting the number of beam pair measurements may be used to reduce power consumption. FIG.21is an example of a multi stage WTRU hierarchical beam sweep2100. An alternative to the single stage exhaustive beam sweep method shown inFIG.20is a multi-stage hierarchical approach2100. A search may be started with wide beams covering relatively large angular regions in a first stage and then gradually decreasing the angular search space and width of beams used in later stages. This gradual decrease may be applied at the TRP only, WTRU only, or both the TRP and WTRU simultaneously. For illustrative purposes an example of a three-stage hierarchical WTRU beam sweep is shown inFIG.21. In this example, the WTRU2102is using four arrays, each of which covers its angular region using 12 beams. From a latency perspective, an exhaustive beam sweep procedure may require 4*12=48 SS bursts. The three-stage2104-2108procedure shown may require only 4+4+3=11 SS bursts2110-2120. Additionally, from a power consumption perspective the exhaustive beam sweep procedure requires 48N measurements, but the current three stage procedure required only 11N measurements to be performed. In both cases this is an approximate 77% savings. The following disclosure outlines the procedure in more detail. For all stages2104-2108the TRP2122transmits N beams per SS burst2110-2120over N OFDM symbols. The WTRU2102, on the other hand, operates differently over time. In a first stage2104, WTRU2102receives using a single quasi-Omni beam per array2124per SS burst. In a second stage2106, the WTRU2102receives from four wide beams2126from the array which resulted in the maximum SINR from stage 12104. In a third stage2108, the WTRU2102receives from three narrow beams2128that are spatially contained within the wide beam that resulted in the maximum SINR from stage 22106. An additional example of using a multi-stage TRP hierarchical beam sweep is shown inFIG.22. It should be noted thatFIG.22also shows an embodiment where the WTRU may be hierarchical, so that a multi-stage TRP/WTRU hierarchical beam sweep is possible. For these cases, an exemplary procedure is as follows. In a first stage2202, the TRP2204transmits from four wide beams for per SS burst2208-2210over 4 OFDM symbols. Meanwhile, in the first stage2202, the WTRU2206receives from M beams, using a single beam per SS burst2208-2210. In a second stage2212, the TRP transmits from N narrow beams per SS burst2214-2216over N OFDM symbols. In the second stage2212, the WTRU2206has three options2214-2218. In a first option2214, the WTRU2206receives from M beams, using one beam per SS burst, however the WTRU2206may only measure the TRP narrow beams that are spatially contained within the TRP wide beam detected in the first stage2202. In a second option2216, to further reduce power consumption, the WTRU2206may receive from only the one WTRU beam that resulted in the largest SINR measurement from the first stage2202. In a third option2218, to increase SINR from directional gain the WTRU may use a hierarchical approach and receive from a set of narrow beams that are spatially contained within detected WTRU2206wide beam from the first stage2202. For the first two options2214-2216if it is assumed there are three narrow TRP beams per wide beam, the number of beam pair measurements required is 4M+3M for option 1 and 4M+3 for option 2. This compares to the number of measurements required in the single stage exhaustive procedure where the number of measurements required is 12M. This results in an approximately 42% and 60% savings respectively. The third option2218combines TRP2204and WTRU2206hierarchal beam sweep. In this case, a number of measurements required is 4M+3Mnarrow. In this case, if it is assumed that M=4 and Mnarrow=3, the number of measurements required is 25. It should be noted that this case uses narrower beams in stage 22212and therefore may see an additional array gain associated with the narrow beam compared to option one2214and option two2216. The single stage exhaustive comparison for this option would require 12*12=144 measurements, so that this third option2218results in an approximately 83% savings. Another aspect of an initial access procedure to consider is the amount of interference seen at the WTRU from other TRPs. The multi-stage procedures that were primarily used to reduce latency, power consumption, and overhead may be further modified to also address the interference issue. The main idea for reducing interference is to capitalize on the use of the multiple stages so that information from earlier stages may be used in later stages to potentially “turn off” by filtering out certain TRP beams. FIG.23illustrates an example of such an approach, which is referred to as a selective beam sweep, combined with a multi-stage TRP/WTRU hierarchical beam sweep procedure. A general description of this procedure is detailed as follows. In a first stage2302, a TRP2304transmits from Nwwide beams2306for each SS burst2308-2310over NwOFDM symbols. In the same stage2302, a WTRU2312receives from Mwwide beams2314, using one beam per SS burst. In a second stage2316, the TRP2304transmits from only the selected LNNnarrow beams2318, where L is the total number of wide beams detected from all WTRUs and NNis the number of narrow beams within each wide beam. The TRP2304may repeat transmission for each SS burst2318-2322. The TRPs may learn or acquire the information for the detected wide beams either directly from the WTRUs via an uplink using the beam pair from the first stage or indirectly from an anchor TRP for which the WTRU is already attached. A WTRU may receive from NNnarrow beams spatially contained within the WTRU wide beam detected in the first stage. The procedure illustrated inFIG.23combines a TRP hierarchical beam sweep, a WTRU hierarchical beam sweep, and a TRP selective beam sweep in order to maximize the SINR while at the same time reduce power consumption, latency, and overhead. With regard to the improvement in SINR due the reduction in WTRU interference from “other” TRPs, it should be noted that this method may have advantages when either the WTRU density is low and/or the WTRUs are non-uniformly distributed. As an illustration, a circumstance may be considered in which all WTRUs are gathered in a certain geographical area within a TRP coverage area. For example, this may be the case in a sports viewing event or concert. In this case, each WTRU may be accessing the TRP using similarly directed TRP beams, so that once this is learned by the TRP there is no need for the TRP to transmit on certain beams. It should also be noted that in addition to reducing interference, this embodiment may provide for a power consumption savings at the TRP. The advantage of the procedures above may also be seen empirically via system simulations.FIG.24illustrates SINR results2400from four different beam sweep procedures, three of which are repeated with a non-uniform WTRU distribution to illustrate the TRP selective sweep performance gains. The results of the simulated procedures are summarized herein. One result shown includes a single stage beam sweep2402. The single stage beam sweep may be a single stage simulation run with a uniform WTRU distribution only, since a second stage is needed to active TRP selective beam sweep. The performance of the single stage beam sweep2402is virtually identical to two-stage TRP selective beam sweep procedure with a uniform WTRU distribution. As such, they are both labelled2402. There is no hierarchical sweep in two-stage TRP selective beam sweep2402, so as mentioned above the performance is virtually identical single stage procedure above when the WTRUs are uniformly distributed. When the WTRUs are non-uniformly distributed, an SINR gain based on a reduction in the interference level may be realized. The two-stage selective non-uniform2408case is illustrated for comparison. Another result shown is a two-stage TRP hierarchical selective beam sweep2404. There is an overall gain with respect to the procedures above based on the TRP hierarchical approach using narrower beams in a second stage. There is also a gain when the WTRUs are non-uniformly distributed again based on a reduction in the interference from TRP beams being “turned off”. The two-stage selective TRP hierarchical non-uniform2410case is illustrated for comparison. Another result is a two-stage TRP/WTRU hierarchical selective beam sweep2406. There is an additional gain based on adding the WTRU hierarchical approach using again narrower beams in a second stage. There is also a gain when the WTRUs are non-uniformly distributed again based on a reduction in the interference from TRP beams being “turned off”. The two-stage selective TRP/WTRU non-uniform2412case is illustrated for comparison. FIG.25illustrates an alternative form2500of the TRP transmission structure shown inFIG.19. As shown inFIG.25, the defined SS bursts2502-2508and SS period2510are still kept. In this case, a single SS burst2502-2508, which still occupies more than one OFDM symbol is assumed to be transmitted in a single beam direction. The SS burst2502-2508is, as shown before, repeated every TPseconds in SS period TP2510, however in this case instead of repeating the same beam pattern a different beam direction is chosen for each SS burst. After N SS bursts the pattern then repeats. Therefore in this case, a full beam sweep would take a minimum of N SS burst times depending on how a WTRU beam sweep is implemented. A straightforward full beam sweep procedure using the framework defined inFIG.25may be performed by conducting an exhaustive search over all available TRP and WTRU beam pairs. This procedure2600, illustrated inFIG.26, is similar to the procedure shown inFIG.20, except the roles of the WTRU and TRP are switched with respect to the beam sweep sequencing. The TRP2602transmits one of N beam directions during an SS burst2604-2608while the WTRU2610sequences through all M beam directions during each SS burst2604-2608. With this process, a full beam sweep requires N SS burst times to complete. An general observation may apply to cell center WTRUs. In general, it is likely that less antenna gain may be required of the cell center WTRUs as compared to cell edge WTRUs. This is likely to be true during and before completion of the initial access procedure and in order to enable successful data transfers. Furthermore, it should be noted that multiple RF chain transmission is more feasible at the TRP than at the WTRU due to things like cost and power. With these observations in mind, a beam sweep procedure may be performed based on the transmission structure shown inFIG.25. The procedure may reduce access latency, and save processing power for cell center WTRUs, while simultaneously allowing cell edge WTRUs to acquire access. This procedure is illustrated inFIG.27. FIG.27is an example of a single stage multi-RF chain TRP beam sweep2700. In the example shown inFIG.27, two RF chains2702-2704are used for the initial access procedure at a TRP. The first RF chain2702covers the TRP serving area using NNnarrow beams2706, while the second RF chain2704covers the same TRP serving area with NWwide beams2708, where NW<NN. One or more WTRUs2710may then receive from all M beams during each SS burst2712-2722. This configuration allows cell center WTRUs to finish the initial access procedure with a reduced latency as compared to cell edge WTRUs. The procedure is described in more detail as follows. A first TRP RF chain2702transmits one of NNbeams every SS burst2712-2716. The beam sweep period is NNbursts. A second RF chain2704transmits one of NWbeams every SS burst2718-2722. The beam sweep period is NWbursts. In one embodiment, NW<NN. RF chain 1 and 2 may use same, partially overlapping or completely different circuitry. With respect to the WTRU side, a WTRU cycles through all M beams during each SS burst2724-2730. Cell center WTRUs may decide on a beam pair after NWSS bursts. Cell edge WTRUs may decide on a beam pair after NNSS bursts. WTRUs may decide to search for wide or narrow TRP beam based on various criteria, for example, information from an anchor TRP, an initial signal power measurement, or the like. MIMO and multi-beam transmission may be enabled for initial access and in one embodiment, grant-free transmissions may be enabled for MIMO and beamforming for PBCH and subsequent DL transmission. At least one set of beamforming parameters may be provided, determined, configured, and/or known, for example, by specification. A configuration may be provided and/or transmitted, for example, by a gNB, via signaling such as broadcast or dedicated signaling. A configuration may be received by a WTRU. A precoder may be used herein as a non-limiting example of a beamforming parameter. Some other examples include an antenna port, for example, a CSI-RS port, a set of antenna ports, a beam ID, a set of beam IDs, or the like. In the embodiments and examples described herein any other beamforming parameter may be substituted for precoder and still be consistent with one or more embodiments herein. A WTRU may choose at least one precoder, for example, W1or W2, from a set of precoders. A WTRU may choose a first precoder from a first set of precoders. A WTRU may choose a second precoder from a second set of precoders. The first and second set may be the same or different. A WTRU may choose a precoder that may be a preferred or recommended precoder. A WTRU may signal or indicate at least one precoder that it chooses, for example to a gNB. A WTRU may choose a precoder for a broadcast transmission such as for a broadcast channel, for example, PBCH. A WTRU may use a first precoder for a first reception of a broadcast channel. The WTRU may determine or may know the first precoder in advance of use. The first precoder may be a default precoder that may be known by the WTRU. The WTRU may determine the first precoder from at least one synchronization channel for example from at least one of: a time and/or frequency positions, for example, relative positions, of a first and second synchronization channel; a payload associated with a synchronization channel; or a sequence of a synchronization channel. The WTRU may use the first precoder, for example until instructed to use another precoder. A WTRU may indicate a precoder, for example, a preferred precoder, for example for a broadcast channel. A WTRU may indicate a precoder to a gNB. The WTRU may indicate a precoder in a grant-free access that WTRU may make, for example before or without establishing an RRC connection. The WTRU may indicate a precoder in a grant-free access that WTRU may make, for example before or without establishing an RRC connection with the gNB. A grant-free access may be a transmission using resources in time and/or frequency without a grant, for example, an explicit grant. A grant free access may be or include a random access such as a 2-step or 4-step random access. A grant-free access may be or include a 1-step transmission or a 1-step random access, for example, message 1 or only message 1 of a random access procedure. The resources and/or preambles that may be used for the grant-free access may be configured via the broadcast channel or system information. A grant-free access may include transmission of at least one of the following: a preamble, control information, and/or a data payload. A WTRU may use a preamble, control information, and/or a data payload to indicate a selected precoder. A WTRU may expect a response or acknowledgement to a grant free access and/or to the information conveyed by the grant-free access. Alternatively, a WTRU may not expect a response or acknowledgement to a grant free access such as a grant free access that may be used to indicate a beamforming parameter. A gNB may receive a precoder indication, for example from a WTRU. A gNB may receive a precoder indication via a grant-free access. A gNB may receive a precoder indication for a broadcast channel. A gNB may use the precoder for semi-open loop MIMO applied to a broadcast channel. A gNB may receive a first precoder indication from a first WTRU and a second precoder indication from a second WTRU. The gNB may determine a precoder to use, for example for a broadcast channel based on the first precoder indication and the second precoder indication. The gNB may use the determined precoder, for example for the transmission of the broadcast channel. In an example, the determined precoder may be a compromise between the first precoder and the second precoder. In another example, the first precoder may be used sometimes and the second precoder may be used sometimes. For example the gNB may cycle through a set of indicated precoders it receives from a set of WTRUs that may provide the indications on the same beam or beam set or from the same or similar direction. The gNB may alternate between a first and second indicated precoders. A gNB may indicate a beamforming parameter such as a precoder in a response to a grant free access. The response may be via DL control information (DCI) or a DL data channel that may have an associated DCI that may indicate the resources of the DL data channel. The DCI may use a common RNTI. A WTRU may monitor for the common RNTI to receive the DCI and/or DL data. A synchronization (sync) channel or set of synchronization channels may be used to indicate the precoder that may be used for the broadcast channel. The gNB may modify the sync channel or set of sync channel when it modifies the precoder for the broadcast channel. The modification may be to a sync channel sequence, the time and/or frequency positions, for example, using relative positions, of a first and second synchronization channel, and/or to a payload associated with a synchronization channel. A first broadcast channel may be used to indicate the precoder and/or precoder cycling pattern that may be used for a second broadcast channel. The indication may be provided in the payload carried by the first broadcast channel. A WTRU may use an indicated precoder and/or precoder cycling pattern for reception of a channel such as a secondary broadcast channel. The indication may be provided by a gNB. A WTRU may use a selected precoder for reception of a channel such as a broadcast channel or secondary broadcast channel. The selected precoder or precoder cycling pattern may be one that the WTRU indicated, for example in a grant-free access. The selected precoder or precoder cycling pattern may be one that the WTRU indicated, for example to a gNB. In an example, a WTRU may use a first precoder to receive a channel such as a broadcast channel. The WTRU may use a second precoder to receive a channel, for example when reception with a first precoder may not be successful or to receive a secondary broadcast channel. The first precoder or second precoder may be a precoder selected by the WTRU. The WTRU may use the first or second precoder after indicating the first or second precoder (e.g., to a gNB and/or in a grant-free access). The second or first precoder may be an initial precoder, a default precoder, a configured precoder, or an indicated precoder. A WTRU may use grant-free transmission to feedback at least one of the following: precoder, for example, W1for long-term statistics; precoder, for example, W2for short-term statistics or instantaneous channel condition; analog beamformer, for example, beam ID or a set of beam IDs; beam pair link or beam pair link set; antenna port or virtual antenna port, e.g., CSI-RS port or a set of CSI-RS ports; beam-location profile(s); ACK/NACK that responds to beam(s); WTRU beam correspondence or reciprocity; or the like. A length-72 DMRS sequence may be generated in the case of a time duplicated sequence DMRS. This sequence may then be mapped to 72 REs DMRS of first OFDM symbol and then copied over to the second OFDM symbol. If QPSK modulation is used, length 144 sequence is generated converted to 72 QPSK symbol and mapped to all the REs of each OFDM symbol. If BPSK modulation is used, a length 72 sequence may be generated and mapped to all the REs of each OFDM symbol. In this configuration as only one sequence is generated, it may carry the SS block time index (SBTI). The terms SS block ID, SS block index and SS block time index may be used interchangeably. Different ways of SBTI indication are disclosed. As each DMRS RE is repeated in time, for a second OFDM symbol, and hence a residual CFO estimation may be performed and corrected. However, a reduced length of a sequence may reduce the detection performance of SBTI. Similar to using channel estimation to perform pre-equalization of these symbols being difficult outside of NR-PSS/NR-SSS bandwidth. This may force receiver to perform non-coherent detection and hence reducing performance. For example, in a frequency duplicated sequence DMRS configuration, a length-72 DMRS sequence may be generated (S(1:72)). This is then mapped center 12 RB on both OFDM symbols of NR-PBCH. This same sequence also copied to the rest of the 12 RB (outside of SS Bandwidth). This may be done in few different ways. FIGS.28and29show a frequency repetition or a frequency swapped repetition2800,2900. InFIG.28, on PBCH1, bits S(19:36)2802-2804are found twice. The same is true with bits S(1:18)2808-2810. On PBCH2, a similar ordering may be found. In this example, bits S(55:72)2814-2816are repeated twice along with bits S(37:54)2818-2820.FIG.28provides repetition in the frequency domain but not in the time domain. FIG.29is another example2900of frequency repetition. InFIG.29, PBCH12902convey bits S(19:36)2906inbetween bits S(1:18)2904and bits S(1:18)2908. Adjacent bits S(1:18)2908is another instance of bits S(19:36)1910. On PBCH22912, bits S(55:72)2916are found between bits S(37:54)2914and bits S(37:54)2918. Adjacent bits S(37:54)2918are bits S(55:72)2920. Frequency swapping may generate more diversity. It may also be possible to perform a frequency and/or time swap repetition in different ways. Some exemplary embodiments3000,3100are illustrated inFIGS.30and31. InFIG.30, on PBCH13002, bits S(19:36)3006are located inbetween bits S(55:72)3004and S(1:18)3008. Adjacent to bits S(1:18)3008are bits S(37:54)3010. PBCH23012is comprised of bits S(55:72)3016located in between bits S(19:36)3014and bits S(37:54)3018. Bits S(37:54)3018are located adjacent bits S(1:18)3020. In this way, redundancy is provided in time domain and frequency interleaving is applied. FIG.31is a similar example to that ofFIG.30. InFIG.31, on PBCH13102, bits S(19:36)3106are located in-between bits S(37:54)3104and S(1:18)3108. Adjacent to bits S(1:18)3108are bits S(55:72)3110. PBCH23112is comprised of bits S(55:72)3116located in between bits S(1:18)3014and bits S(37:54)3118. Bits S(37:54)3118are located adjacent bits S(19:36)3120.FIG.31reverses bit ordering ofFIG.30in such a way that higher numbered bits3004and3014ofFIG.30are moved to opposite frequency ends3110,3120ofFIG.31. This is similar with respect to bits S(37:54)3002and S(1:18)3020ofFIG.30with S(37:54)3104and S(1:18)3114ofFIG.31. A potential feature of these configurations is that only the center RE may need be decoded to find the SBTI. If it is known that a channel condition is good, based on NR-PSS/NR-SSS detection, these configurations may reduce the SBTI detection complicity. In this configuration NR-PSS/NR-SSS may be used for the pre-equalization for the coherent detection of a sequence carried on the center RBs. For the RBs outside of NR-SS bandwidth, non-coherent detection may have to be performed. They may be combined with coherent detection of center RBs. NR-PSS and NR-SSS may occupy only N REs, for example, N=127 REs in the center instead of all 144 REs of 12 RBs. Hence, good channel estimation may be performed only for 31 REs in one OFDM symbol or a total of 62 REs in two OFDM symbols. Extrapolation of the channel estimates may not perform very well. Also, this method may not allow the sub-carriers to be repeated in time and hence residual CFO estimation is not possible. Hence a modified method may be used additionally or in combination. In one embodiment, a length-62 DMRS sequence may be mapped to the central 12 RBs on the sub-carrier which are overlapping with NR-PSS/NR-SSS, and a repeated sequence is mapped the remaining 12 RBs.FIG.32shows a length 62 sequence with repetition in frequency. An exemplary illustration of a PBCH13202and PBCH2 are shown. Areas marked with x3204-3216are areas where a payload may be transmitted. Shaded areas ofFIG.32represent REs and a sequence for PBCH DMRS, but not a payload. DMRS sub-carriers3204-3216are populated with symbols which are repeated in a second OFDM symbol of NR-PBCH on DMRS REs. Because of asymmetry, the upper band (outside of SS bandwidth) has 2 such REs and the lower band (outside of SS bandwidth) has 3 such REs in each OFDM symbol. They may be used for CFO compensation and channel estimation. In regions outside the NR-SS bandwidth these sub carriers may be distributed more evenly. This length 62 scheme may also have different configurations, for example, time and frequency swapping, as illustrated inFIGS.28-31. As shown inFIG.32, shaded areas3218-3236may carry a sequence for PBCH DMRS. PBCH2 contains payload elements3240-3252and bits used for DMRS3254-3270. In this way, payload elements may be interleaved with DMRS. All the schemes described above had only single sequence containing the information about SBTI. Hence, for channel estimation using these DMRS is only possible after the SBTI is decoded. Hence to coherently decode SBTI, only information within SS-Bandwidth may be used. To overcome this issue, another design is disclosed. In this design, there are two sequences used. The first sequence is mapped on DMRS REs of first OFDM symbol of NR-PBCH. The second sequence is mapped on DMRS REs of the second OFDM symbol NR-PBCH. A first sequence is generated using a Cell ID. For convenience, this is referred to as reference-DMRS. A Cell ID may be determined from the detection of NR-PSS/NR-SSS. Using the Cell ID, the first sequence may be determined. Channel estimation may be performed on those REs using the knowledge of the sequence. These channel estimates may be used to pre-equalize DMRS REs or sub-carriers. The second sequence depends on SBTI only or depends jointly on Cell ID and SBTI. As this sequence is used for indicating SBTI, as used herein the term indication-DMRS is used to refer to this sequence. After coherently detecting the second sequence, the SBTI may be decoded. This sequence may be a function of a number of variables. In another variation of a similar concept, a known base sequence may be generated. The base is modified using the Cell ID to generate a sequence for reference-DMRS. The sequence may also be modified using SBTI to generate a sequence for indication-DMRS. The reference-DMRS is used for pre-equalization and coherently estimating the indication-DMRS and hence detecting SBTI. These modifications as function of SBTI may be performed using some of the following ways: different initialization of linear feedback shift register (LFSR) for an M-Sequence of a gold code; a frequency or circular shift of an M sequence of a gold code; a frequency or circular shift of a gold sequence; a cyclic shift; and performing scrambling on top of original sequences. Once NR-PSS and NR-SSS are detected, they may be used as a known sequence for channel estimation and pre-equalization for the central RBs, it may be possible to use the reference-DMRS on only RBs (or sub-carriers) not occupied by the NR-PSS/NR-SSS. Hence the indication-DMRS are mapped on first and second OFDM symbol of NR-PBCH for the bandwidth that overlaps with NR-PSS and NR-SSS. This may increase the length of a sequence used for indication-DMRS and may improve the performance of indication-DMRS. In the design above, the first sequence is mapped on the first OFDM symbol of NR-PPBCH and second sequence is mapped on the second OFDM symbol. It also may be possible to alternate the two sequences within one OFDM symbol. Hence the sequence is mapped on DMRS REs of alternating OFDM symbols of NR-PBCH. This may improve the channel estimation performance using one of the sequences. It may also improve diversity for the second sequence and hence the detection performance of SBTI. This pattern is illustrated inFIG.33which shows an NR-PBCH DMRS distribution of two sequences in a comb pattern. FIG.33is an example3300of an NR-PBCH DMRS distribution of two sequences in a comb pattern. InFIG.33, r13304-3310shows the REs where the reference-DMRS are mapped and r23312-3316shows the REs where indication DMRS are mapped. With reference to NR-PBCH13302, r13304-3310are dispersed between r23312-3316. With reference to NR-PBCH23318, r13320-3324are dispursed inbetween r23326-3332. This comb pattern may be use to transmit reference-DMRS and indication-DMRS. In one design, reference-DMRS sequence may be generated using Cell ID only. This may then be modified using SBTI to generate indication DMRS sequence. In another option, a known base sequence is generated. This sequence is modified using the Cell ID to generate sequence for reference-DMRS. The base sequence is also modified using SBTI to generate sequence for indication-DMRS. Like the simple pattern case, a different modification as a function of SBTI may be performed in one or more of the following ways: a different initialization of a Linear Feedback Shift Register (LFSR) for an M-Sequence of a gold code; a frequency or circular shift of an M sequence of a gold code; a frequency or circular shift of a Gold sequence; a cyclic shift; and/or a scrambling on top of one or more original sequences. Like the simple pattern case, NR-PSS and NR-SSS may be used for channel estimation and pre-equalization for the central RBs. It is possible to use the reference-DMRS only on the RBs (or sub-carriers) not occupied by the NR-PSS/NR-SSS. Hence the indication-DMRS are mapped on a first and second OFDM symbol of NR-PBCH for the bandwidth that overlaps with NR-PSS and NR-SSS. This may increase the length of a sequence used for indication-DMRS and hence may improve the performance of indication-DMRS. Short LFSR gold sequences may be implemented with shift registers. In this way, different length shift registers may be used to generate the gold sequence. For example, if short length lf LFSR of length 7 is used: c(n)=(x1(n)+x2(n))mod 2 x1(n+7)=(x1(n+4)+x1(n))mod 2 x2(n+7)=(x2(n+1)+x2(n))mod 2 One or both the m-sequences may be initialized with the state x(0)=0, x(1)=0, x(2)=0, . . . ,x(5)=0 x(6)=1. If only one LFSR is initialized with [00001], another LFSR may be initialized using SS Block Time index or Cell ID or combination of both. A long LFSR Gold sequence may be used in addition or combination. A long LFSR gold sequence may also be generated via a longer shift register and a shift (Nc) while selecting the output may be used to select the part of gold sequence of desired length. c(n)=(x1(n+NC)+x2(n+NC))mod 2 x1(n+31)=(x1(n+3)+x1(n))mod 2 x2(n+31)=(x2(n+3)+x2(n+2)+x2(n+1)+x2(n))mod 2 Nc may be defined as an integer. For eg: NC=1600. A very long LFSR gold sequence, for example of length 64, may also be generated by longer shift register and a shift (Nc) while selecting the output may be used to select the part of gold sequence of desired length. c(n)=(x1(n+NC)+x2(n+NC))mod 2 x1(n+63)=(x1(n+1)+x1(n))mod 2 x2(n+63)=(x2(n+38)+x2(n+13)+x2(n+1)+x2(n))mod 2 In this example, n=01, 2, 3 . . . . NREDMRS−1. Here Nc may be much larger integer number and may be found experimentally to find good correlation sequences. Any of the above sequences may have scrambling applied on top before modulation (BPSK/QPSK). The scrambling code may be generated from similar length LFSR. Cyclic shifts may be applied to any of the Gold sequences after modulation (BPSK/QPSK). A cyclic shift may be of the form seqcs(m)=seq(m)×e2πm×iM, where m=0, 1, . . . M−1 and i is the shift index. In this example, seq is the original modulated sequence and seq, is the sequence with cyclic shifts. Modulation is used for the sequences and all of the above sequences may be BPSK or QPSK modulated. Using BPSK, r(m)=(1−2·c(m)) m=0, 1, . . . , NREPBCH−1. Using QPSK, every two bits may be combined into one symbol r(m)=12(1-2·c(2m))+j12(1-2·c(2m+1)),m=0,1,…,NREPBCH-1. Bits which are at a NREPBCHdistance apart, may be combined into one symbol, r(m)=12(1-2·c(2m))+j12(1-2·c(m+NREPBCH)),m=0,1,…,NREPBCH-1. In an embodiment, a NR-PBCH DMRS time block ID indication/detection may be implemented. A different initialization of M-Sequence LFSR may be performed. As an example, consider the gold code defined by: c(n)=(x1(n)+x2(n))mod 2 (n+7)=(x1(n+4)+x1(n))mod 2 x2(n+7)=(x2(n+1)+x2(n))mod 2 x1 is first m sequence and x2 is second m sequence to generate the gold code. The LFSR to generate one or both m-Sequences x1, x2 used to generate the gold code may be initialized using SBTI or Cell ID or combination of both or combination of even more number of variables such as RNTI, slot number, cell ID, half frame. Different examples of these initializations are enumerated below: Option 1: cint=NIDcell. Option 2: cint=mod(NIDcell,x), where x is a known integer. Option 3: cint=2xNIDcell−1 (x is an integer <Llfsr-1-10), as 10 bits are used to indicate NIDcell. Option 4: cint=2x·(2·NIDcell+1)+2·sbti−1. Option 5 may be more generalized option of option 5. cint=2x1·(x2·NIDcell+x3)+x4·sbti+x5, where x1 to x5 may be determined imperially to have best correlation properties. More options are also possible. It may also be possible to generate two different gold sequences using two different initializations. For Example, a first shift resulting in reference-DMRS may be used for pre-equalization and another shift resulting in indication-DMRS may be used for indicating the SBTI. If only one sequence is used, partial coherent/partial non-coherent detection may be performed. Different hypothesis of gold sequences be generated (using different initialization of M sequences) at the receiver to detect SBTI. A frequency or circular shift of individual M sequence may be applied. c(n)=(xm01(n)+xm12(n))mod 2 x1(n+7)=(x1(n+4)+x1(n))mod 2x1(m0)(n)=x1((n+m0)modL) x2(n+7)=(x2(n+1)+x2(n))mod 2 wherex2(m1)(n)=x2((n+m1)modL) Circular shift values m0,m1 are jointly or individually determined by a Cell ID and/or SBTI. Knowing the relations between the Cell ID SBTI and m0, m1, and the knowledge of Cell ID from detection of PSS/SSS, a hypothesis may be generated for SBTI, and may be used to detect which SBTI was indicated in the gold code. It may be possible to generate two different gold sequences using two different circular shifts in M sequences. First shift resulting in reference-DMRS used for pre-equalization and another shift resulting in indication-DMRS used for indicating the STBI. If only one sequence is used, partial coherent/partial non-coherent detection may be performed. Different hypothesis be generated (using different frequency shift of individual M-Sequences) at the receiver to detect STBI. A frequency or circular shift of a gold sequence may be: r=c((n+m0)modL) c(n)=(x1(n)+x2(n))mod 2 x1(n+7)=(x1(n+4)+x1(n))mod 2 x2(n+7)=(x2(n+1)+x2(n))mod 2 Circular shift values m0 may be determined by the Cell ID and/or SBTI. Knowing the relations between the Cell ID SBTI and m0, and the knowledge of Cell ID from detection of PSS/SSS, a hypothesis may be generated for SBTI. And detect which SBTI was indicated by the gold code. This is a special case of the ‘Circular shift of individual M sequence’ where both sequence have same shift. (m0=m1). It may be possible to generate two different gold sequences using two different circular shifts in frequency. One used for pre-equalization and another for indicating the SBTI. If only one sequence is used, partial coherent/partial non-coherent detection may be performed. A different hypothesis may be generated, for example using a different frequency shift of this gold sequence, at the receiver to detect STBI. FIG.34is an example3400of DMRS and STBI indication using cyclic shifts.FIG.35is an example3500of DMRS and STBI indication using cyclic shifts in a comb pattern. Cyclic shift techniques may be employed and some examples are illustrated herein. A first sequence (Reference DMRS) is generated using following procedure: An initial value cintmay be used to generate a sequence c of length 144 (6NRBPBCH−1). The demodulation reference-signal for first OFDM symbol of NR-PBCH r1pbch(m) are QPSK modulated and is defined by: r1pbch(m)=12(1-2·c(2m))+j12(1-2·c(2m+1)),m=0,1,…,6NREPBCH-1 In the above equation, NRBPBCH=24 denotes the assigned bandwidth in resource blocks of the NR-PBCH transmission. The pseudo-random sequence c(i) is may be defined according to one or more embodiments described herein. A second sequence (Indication DMRS) is generated using following procedure: The demodulation reference-signal for a second OFDM symbol of NR-PBCH is generated with cyclic shifts to the sequence of first symbol. r2pbch(m)=r1pbch(m)×e2πm×sbti2km=0,1,…,3NRBPBCH-1sbti=0,1,…,2k-1 In this example, k=2 or 3 depending on how many bits needs to be indicated for SS Block timing index. These sequences may be mapped in a simple pattern of a comb pattern. Due to the circular nature of cyclic shifts, every 8th tone of both the reference-DMRS and indication-DMRS will be identical. This property be used to estimate CFO at the receiver and the cyclic shift may be used to estimate the SBTI. The CFO estimation may be performed using: rCfo=fc×mean(arctan(REbpch1REpbch2))×2π×ΔnOFDM, where fc is carrier frequency, ΔnOFDM=2 (distance been two OFDM symbols). This property illustrated below. As an example e2πm×[0-7]8 for m=0:17 is shown inFIG.36. The 8 rows (rows 0-8) shown inFIG.36represent different cyclic shifts used to indicate a different SBTI. Different columns are used to show values of a multiplier used for DMRS REs. These cyclic shifts are orthogonal to each other. The cyclically shifted DMRS may also be taken to the time domain. The phase shift in frequency domain translates to time-index-offset in time domain. This may result in faster detection of SBTI (without multiple hypothesis testing). Hence a ratio of (DMRSpbch2/DMRSpbch1) is a differential estimation free of channel (if channel hasn't changed much from one symbol to other). IFFT of these ratios for each STBI are time shifted version of each other. Hence coherent detection of SBTI may be performed quickly and with lower complexity. A scrambling sequence, which may be a function of SBTI, may be applied to the reference-DMRS to generate indication-DMRS. Using the scrambling pattern known at receiver, hypothesis to find SBTI may be generated and hence SBTI may be detected. The transmit power of REs for PBCH DMRS could be higher than that of REs for PBCH data. To achieve this, power boosting with a known factor could be applied for PBCH DMRS transmission. Knowledge of this factor at receiver may be important. Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention. Although each one of the beams shown in the FIGs may be illustrated as to a particular direction, it should be kept in mind that this is for illustration purposes and a limitation with respect to a particular beam format, width or orientation is not intended. Although the embodiments described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it is understood that the embodiments described herein are not restricted to this scenario and are applicable to other wireless systems as well. Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. | 136,582 |
11943725 | DETAILED DESCRIPTION Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details. The described features generally relate to reporting of timing difference for different synchronization signal blocks (SSBs) in fifth generation new radio (5G NR). For example, multi-beam operation may be enhanced by targeting frequency range two (FR2) while also being applicable to FR1. In an example, these enhancements may include identifying and specifying features to facilitate more efficient (lower latency and overhead) downlink or uplink (DL/UL) beam management to support higher intra- and layer 1 or layer 2 (L1/L2) centric inter-cell mobility and/or a larger number of configured transmission configuration indicator (TCI) states. This example may include common beam for data and control tran1smission/reception for DL and UL, especially for intra-band carrier aggregation (CA), unified TCI framework for DL and UL beam indication, and enhancement on signalling mechanisms for the above features to improve latency and efficiency with more usage of dynamic control signalling (as opposed to radio resource control (RRC)). In another example, these enhancements may include identifying and specifying features to facilitate UL beam selection for UEs equipped with multiple panels, considering UL coverage loss mitigation due to maximum permissible exposure (MPE), based on UL beam indication with the unified TCI framework for UL fast panel selection. In an aspect, the support for multi-TRP deployment may be enhanced by targeting both FR1 and FR2. For example, these enhancements may include identifying and specifying features to improve reliability and robustness for channels other than physical downlink shared channel (PDSCH) (that is, physical downlink control (PDCCH), physical uplink shared channel (PUSCH), and physical uplink control channel (PUCCH)) using multi-transmission reception points (TRP) and/or multi-panel, with Release 16 reliability features as the baseline. These enhancements may further include identifying and specifying quasi-co-location (QCL)/TCI-related enhancements to enable inter-cell multi-TRP operations, assuming multi-downlink control information (DCI) based multi-PDSCH reception. These enhancements may further include evaluating and, if needed, specifying beam-management-related enhancements for simultaneous multi-TRP transmission with multi-panel reception. Additionally, these enhancements may include enhancements to support high speed train (HST)-single frequency network (SFN) deployment scenario. This example may include identifying and specifying solution(s) on QCL assumption for demodulation reference signal (DMRS) (e.g. multiple QCL assumptions for the same DMRS port(s), targeting DL-only transmission), and/or evaluating and, if the benefit over Release 16 HST enhancement baseline is demonstrated, specifying QCL/QCL-like relation (i.e., including applicable type(s) and the associated requirement) between DL and UL signal by reusing the unified TCI framework. The present disclosure relates generally to current issues of L1/L2 based mobility with SSB split among remote radio headers (RRH). For example, in an aspect, each serving cell may have multiple RRHs, which share the same SSB ID space. Each RRH may transmit a sub-set of SSB IDs but with a same physical cell identity (PCI) for the serving cell. Accordingly, when a UE switches among RRHs within the same serving cell, propagation delay to different RRHs may be different. However, in Release 15/16, each serving cell belongs to a single timing advance group (TAG), which has a single TA offset value. Therefore, when the UE switches RRH, a gNB may have to trigger PDCCH order for UL TA measurement and send the updated TA offset to the UE. This may increase RRH switching latency and overhead. In one implementation, the present aspects provide a UE that may determine to switch from a first RRH to a second RRH. The UE may further identify a TAG for the second RRH, the TAG associated with a TA offset, the first RRH and the second RRH are associated with a serving cell. The UE may further switch from the first RRH to the second RRH in accordance with the TAG and the associated TA offset. The UE may further transmit, on an uplink communication channel, data to the second RRH. In another implementation, the present aspects also provide a serving cell having a first RRH and a second RRH. The serving cell may transmit, on a downlink communication channel, a first TAG and associated TA offset for the second RRH to a UE. The serving cell may further detect a switch of the UE from the first RRH to the second RRH. The serving cell may further receive, on an uplink communication channel, data from the second RRH. In some aspects, an RRH may be a remote radio transceiver that connects to an operator radio control panel via electrical or wireless interface. More specifically, the RRH may be a physical unit within a base station containing the base station's RF circuitry plus analog-to-/digital or digital-to-analog converters and up/down converters. The described features will be presented in more detail below with reference toFIGS.1-6. As used in this application, the terms “component,” “module,” “system” and the like are intended to include a computer-related entity, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms “system” and “network” may often be used interchangeably. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-656 standards. IS-2000 Releases 0 and A are commonly referred to as CDMA2000 1×, 1×, etc. IS-656 (TIA-656) is commonly referred to as CDMA2000 1×EV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. The description below, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to fifth generation (5G) NR networks or other next generation communication systems). The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in other examples. Various aspects or features will be presented in terms of systems that can include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems can include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches can also be used. FIG.1is a diagram illustrating an example of a wireless communications system and an access network100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) can include base stations102, UEs104, an Evolved Packet Core (EPC)160, and/or a 5G Core (5GC)190. The base stations102, which may also be referred to as network entities, may include macro cells (high power cellular base station) and/or small cells (low power cellular base station). The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells. In an example, the base stations102may also include gNBs180, as described further herein. In one example, some nodes such as base station102/gNB180, may have a modem240and communicating component242for supporting cell mobility based on a TAG per subset of SSBs, as described herein. Though a base station102/gNB180is shown as having the modem240and communicating component242, this is one illustrative example, and substantially any node may include a modem240and communicating component242for providing corresponding functionalities described herein. In another example, some nodes such as UE104of the wireless communication system may have a modem340and communicating component342for intra or inter cell mobility based on a TAG per subset of SSBs, as described herein. Though a UE104is shown as having the modem340and communicating component342, this is one illustrative example, and substantially any node or type of node may include a modem340and communicating component342for providing corresponding functionalities described herein. For example, the communicating components242and342may be configured to support inter and/or intra cell mobility based on a TAG per subset of SSBs. Specifically, each SSB or subset of SSBs of a serving cell (e.g., base station102/gNB180) can be associated with one TAG. The TA offset per TAG may be continuously updated, regardless if the UE104is served by corresponding SSB(s) (RRH(s)) or not. Further, if the UE104is switched to the beams quasi co-located (QCLed) with SSB(s) in a new TAG, the UE104may use the latest TA offset for that TAG for uplink transmission. So, the forgoing may save the uplink TA measurement and sending of the updated TA offset to UE104. In some aspects, the SSB concept can also extend to other cell defining reference signals (RSs), including a channel state information reference signal (CSI-RS) or a PRS (positioning RS). In some aspects related to L1/L2 based mobility via PCI selection, each cell may have a single physical cell identifier (PCI). The DCI/MAC-CE can select which cell(s) or PCI(s) to serve the UE104. Here, the cell can include serving cell/PCI, or non-serving cell/PCI, or both. In another implementation related to L1/L2-centric inter-cell mobility, a number of operation modes may be defined. In a first example, each serving cell may one PCI and can have multiple physical cell sites, e.g. RRH. Each RRH may transmit a different set of SSB IDs but with same PCI for this serving cell. The DCI/MAC-CE can select which RRH(s) or corresponding SSBs to serve the UE104based on RSRP per reported SSB ID. In a second example, each serving cell can be configured with multiple PCIs. Each RRH of the serving cell can use one PCI configured for this serving cell and can transmit the full set of SSB IDs. The DCFMAC-CE can select which RRH(s) or corresponding PCI(s) and/or SSB(s) to serve the UE104based on RSRP per reported SSB ID per reported PCI. In a third example, each serving cell may have one PCI. The DCFMAC-CE can select which serving cell(s) or corresponding serving cell ID(s) to serve the UE104based on RSRP per reported SSB ID per reported PCI. The forgoing SSB concept may be extended to other cell-defining RS, e.g. CSI-RS, PRS (positioning reference signal). The base stations102configured for 4G LTE (which can collectively be referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC160through backhaul links132(e.g., using an S1 interface). The base stations102configured for 5G NR (which can collectively be referred to as Next Generation RAN (NG-RAN)) may interface with 5GC190through backhaul links184. In addition to other functions, the base stations102may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations102may communicate directly or indirectly (e.g., through the EPC160or 5GC190) with each other over backhaul links134(e.g., using an X2 interface). The backhaul links132,134and/or184may be wired or wireless. The base stations102may wirelessly communicate with one or more UEs104. Each of the base stations102may provide communication coverage for a respective geographic coverage area110. There may be overlapping geographic coverage areas110. For example, the small cell102′ may have a coverage area110′ that overlaps the coverage area110of one or more macro base stations102. A network that includes both small cell and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group, which can be referred to as a closed subscriber group (CSG). The communication links120between the base stations102and the UEs104may include uplink (UL) (also referred to as reverse link) transmissions from a UE104to a base station102and/or downlink (DL) (also referred to as forward link) transmissions from a base station102to a UE104. The communication links120may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations102/UEs104may use spectrum up to Y MHz (e.g., 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (e.g., for x component carriers) used for transmission in the DL and/or the UL direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell). In another example, certain UEs104may communicate with each other using device-to-device (D2D) communication link158. The D2D communication link158may use the DL/UL WWAN spectrum. The D2D communication link158may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR. The wireless communications system may further include a Wi-Fi access point (AP)150in communication with Wi-Fi stations (STAs)152via communication links154in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs152/AP150may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available. The small cell102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell102′ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP150. The small cell102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. A base station102, whether a small cell102′ or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or other type of base station. Some base stations, such as gNB180may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE104. When the gNB180operates in mmW or near mmW frequencies, the gNB180may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band has extremely high path loss and a short range. The mmW base station180may utilize beamforming182with the UE104to compensate for the extremely high path loss and short range. A base station102referred to herein can include a gNB180. The EPC160may include a Mobility Management Entity (MME)162, other MMES164, a Serving Gateway166, a Multimedia Broadcast Multicast Service (MBMS) Gateway168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway172. The MME162may be in communication with a Home Subscriber Server (HSS)174. The MME162is the control node that processes the signaling between the UEs104and the EPC160. Generally, the MME162provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway166, which itself is connected to the PDN Gateway172. The PDN Gateway172provides UE IP address allocation as well as other functions. The PDN Gateway172and the BM-SC170are connected to the IP Services176. The IP Services176may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC170may provide functions for MBMS user service provisioning and delivery. The BM-SC170may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway168may be used to distribute MBMS traffic to the base stations102belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information. The 5GC190may include a Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. The AMF192may be in communication with a Unified Data Management (UDM)196. The AMF192can be a control node that processes the signaling between the UEs104and the 5GC190. Generally, the AMF192can provide QoS flow and session management. User Internet protocol (IP) packets (e.g., from one or more UEs104) can be transferred through the UPF195. The UPF195can provide UE IP address allocation for one or more UEs, as well as other functions. The UPF195is connected to the IP Services197. The IP Services197may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station102provides an access point to the EPC160or 5GC190for a UE104. Examples of UEs104include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a positioning system (e.g., satellite, terrestrial), a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, robots, drones, an industrial/manufacturing device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a vehicle/a vehicular device, a meter (e.g., parking meter, electric meter, gas meter, water meter, flow meter), a gas pump, a large or small kitchen appliance, a medical/healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs104may be referred to as IoT devices (e.g., meters, pumps, monitors, cameras, industrial/manufacturing devices, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC/enhanced MTC (eMTC, also referred to as CAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. The UE104may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. Turning now toFIGS.2-5, aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional. Although the operations described below inFIGS.4and5are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation. Moreover, it should be understood that the following actions, functions, and/or described components may be performed by a specially-programmed processor, a processor executing specially-programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions. Referring toFIG.2, one example of an implementation of a node, such as base station102(e.g., a base station102and/or gNB180, as described above) may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors212and memory216and transceiver202in communication via one or more buses244, which may operate in conjunction with modem240and/or communicating component242for supporting inter or intra cell mobility based on a TAG per subset of SSBs. In an aspect, the one or more processors212can include a modem240and/or can be part of the modem240that uses one or more modem processors. Thus, the various functions related to communicating component242may be included in modem240and/or processors212and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors212may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver202. In other aspects, some of the features of the one or more processors212and/or modem240associated with communicating component242may be performed by transceiver202. Also, memory216may be configured to store data used herein and/or local versions of applications275or communicating component242and/or one or more of its subcomponents being executed by at least one processor212. Memory216can include any type of computer-readable medium usable by a computer or at least one processor212, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory216may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining communicating component242and/or one or more of its subcomponents, and/or data associated therewith, when base station102is operating at least one processor212to execute communicating component242and/or one or more of its subcomponents. Transceiver202may include at least one receiver206and at least one transmitter208. Receiver206may include hardware and/or software executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). Receiver206may be, for example, a radio frequency (RF) receiver. In an aspect, receiver206may receive signals transmitted by at least one base station102. Additionally, receiver206may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter208may include hardware and/or software executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). A suitable example of transmitter208may including, but is not limited to, an RF transmitter. Moreover, in an aspect, base station102may include RF front end288, which may operate in communication with one or more antennas265and transceiver202for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one base station102or wireless transmissions transmitted by UE104. RF front end288may be connected to one or more antennas265and can include one or more low-noise amplifiers (LNAs)290, one or more switches292, one or more power amplifiers (PAs)298, and one or more filters296for transmitting and receiving RF signals. The antennas265may include one or more antennas, antenna elements, and/or antenna arrays. In an aspect, LNA290can amplify a received signal at a desired output level. In an aspect, each LNA290may have a specified minimum and maximum gain values. In an aspect, RF front end288may use one or more switches292to select a particular LNA290and its specified gain value based on a desired gain value for a particular application. Further, for example, one or more PA(s)298may be used by RF front end288to amplify a signal for an RF output at a desired output power level. In an aspect, each PA298may have specified minimum and maximum gain values. In an aspect, RF front end288may use one or more switches292to select a particular PA298and its specified gain value based on a desired gain value for a particular application. Also, for example, one or more filters296can be used by RF front end288to filter a received signal to obtain an input RF signal. Similarly, in an aspect, for example, a respective filter296can be used to filter an output from a respective PA298to produce an output signal for transmission. In an aspect, each filter296can be connected to a specific LNA290and/or PA298. In an aspect, RF front end288can use one or more switches292to select a transmit or receive path using a specified filter296, LNA290, and/or PA298, based on a configuration as specified by transceiver202and/or processor212. As such, transceiver202may be configured to transmit and receive wireless signals through one or more antennas265via RF front end288. In an aspect, transceiver may be tuned to operate at specified frequencies such that UE104can communicate with, for example, one or more base stations102or one or more cells associated with one or more base stations102. In an aspect, for example, modem240can configure transceiver202to operate at a specified frequency and power level based on the UE configuration of the UE104and the communication protocol used by modem240. In an aspect, modem240can be a multiband-multimode modem, which can process digital data and communicate with transceiver202such that the digital data is sent and received using transceiver202. In an aspect, modem240can be multiband and be configured to support multiple frequency bands for a specific communications protocol. In an aspect, modem240can be multimode and be configured to support multiple operating networks and communications protocols. In an aspect, modem240can control one or more components of UE104(e.g., RF front end288, transceiver202) to enable transmission and/or reception of signals from the network based on a specified modem configuration. In an aspect, the modem configuration can be based on the mode of the modem and the frequency band in use. In another aspect, the modem configuration can be based on UE configuration information associated with UE104as provided by the network during cell selection and/or cell reselection. In an aspect, the processor(s)212may correspond to one or more of the processors described in connection with the UE inFIG.6. Similarly, the memory216may correspond to the memory described in connection with the UE inFIG.6. Referring toFIG.3, one example of an implementation of UE104may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors312and memory316and transceiver302in communication via one or more buses344, which may operate in conjunction with modem340. The transceiver302, receiver306, transmitter308, one or more processors312, memory316, applications375, buses344, RF front end388, LNAs390, switches392, filters396, PAs398, and one or more antennas365may be the same as or similar to the corresponding components of base station102, as described above, but configured or otherwise programmed for base station operations as opposed to base station operations. In an aspect, the processor(s)312may correspond to one or more of the processors described in connection with the base station inFIG.6. Similarly, the memory316may correspond to the memory described in connection with the base station inFIG.6. Turning now toFIGS.4and5, aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional. Although the operations described below inFIGS.4and5are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation. Moreover, it should be understood that the following actions, functions, and/or described components may be performed by reference to one or more components ofFIGS.1,2,3, and/or6, as described herein, a specially-programmed processor, a processor executing specially-programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions. FIG.4illustrates a flow chart of an example of a method400for wireless communication, for example, at a UE. In an example, UE104can perform the functions described in method400using one or more of the components described inFIGS.1,3, and6. At block402, the method400may determine to switch from a first RRH to a second RRH. In an aspect, the communicating component342, e.g., in conjunction with processor(s)312, memory316, and/or transceiver302, may be configured to determine to switch from a first RRH to a second RRH. Thus, the UE104, the processor(s)312, the communicating component342or one of its subcomponents may define the means for determining to switch from a first RRH to a second RRH. In some aspects, switching from a first RRH to a second RRH at a cell includes communicating with the cell using beams of the second RRH and not beams of the first RRH. At block404, the method400may identify a TAG for the second RRH, the TAG associated with a TA offset, the first RRH and the second RRH are associated with a serving cell. In an aspect, the communicating component342, e.g., in conjunction with processor(s)312, memory316, and/or transceiver302, may be configured to identify a TAG for the second RRH, the TAG associated with a TA offset, the first RRH and the second RRH are associated with a serving cell. Thus, the UE104, the processor(s)312, the communicating component342or one of its subcomponents may define the means for identifying a TAG for the second RRH, the TAG associated with a TA offset, the first RRH and the second RRH are associated with a serving cell. In some aspects, the second RRH may be different from the first RRH. At block406, the method400may switch from the first RRH to the second RRH in accordance with the TAG and the associated TA offset. In an aspect, the communicating component342, e.g., in conjunction with processor(s)312, memory316, and/or transceiver302, may be configured to switch from the first RRH to the second RRH in accordance with the TAG and the associated TA offset. Thus, the UE104, the processor(s)312, the communicating component342or one of its subcomponents may define the means for switching from the first RRH to the second RRH in accordance with the TAG and the associated TA offset. At block408, the method400may transmit, on an uplink communication channel, data to the second RRH. In an aspect, the communicating component342, e.g., in conjunction with processor(s)312, memory316, and/or transceiver302, may be configured to transmit, on an uplink communication channel, data to the second RRH. Thus, the UE104, the processor(s)312, the communicating component342or one of its subcomponents may define the means for transmitting, on an uplink communication channel, data to the second RRH. In some aspects, the first RRH may be associated with a different TAG and associated TA offset that is different from the TAG associated with the TA offset of the second RRH. In some aspects, the first RRH may be associated with a first subset of RSs and the second RRH is associated with a second subset of RSs, and wherein the second subset of RSs may be associated with the TAG and the first subset of RSs is associated with the different TAG. In some aspects, switching from the first RRH to the second RRH may include switching from a first set of beams associated with the first RRH to a second set of beams associated with the second RRH, the second set of beams are quasi co-located with the second subset of RSs of the TAG. In some aspects, the method400may include receiving, on a downlink communication channel, DCI or a MAC CE indicating one or both of the first RRH or the second RRH to serve the UE. In some aspects, the method400may include performing uplink TA measurement for both the first RRH and the second RRH, and updating the TAG and TA offset of the second RRH and the different TAG and TA offset of the first RRH. In some aspects, the TAG for the second RRH may correspond to a most recently received TAG for the second RRH. In some aspects, the data may be transmitted on the uplink communication channel based on the most recently received TAG for the second RRH. In some aspects, the RSs may correspond to at least one of a SSB reference signal, a channel state information reference signal, or positioning reference signal. In some aspects, the method400may include receiving a DCI or MAC CE indicating one or both of a number of cells or PCIs, the number of cells or PCIs are associated with one or both of a serving cell or non-serving cell. FIG.5illustrates a flow chart of an example of a method500for wireless communication, for example, at a network entity. In an example, a base station102can perform the functions described in method500using one or more of the components described inFIGS.1,2, and6. At block502, the method500may transmit, on a downlink communication channel, a first TA) and associated TA offset for the second RRH to a UE. In an aspect, the communicating component242, e.g., in conjunction with processor(s)212, memory216, and/or transceiver202, may be configured to transmit, on a downlink communication channel, a first TA) and associated TA offset for the second RRH to a UE. Thus, the base station102, the processor(s)212, the communicating component242or one of its subcomponents may define the means for transmitting, on a downlink communication channel, a first TA) and associated TA offset for the second RRH to a UE. At block504, the method500may detect a switch of the UE from the first RRH to the second RRH. In an aspect, the communicating component242, e.g., in conjunction with processor(s)212, memory216, and/or transceiver202, may be configured to detect a switch of the UE from the first RRH to the second RRH. Thus, the base station102, the processor(s)212, the communicating component242or one of its subcomponents may define the means for detecting a switch of the UE from the first RRH to the second RRH. At block506, the method500may receive, on an uplink communication channel, data from the second RRH. In an aspect, the communicating component242, e.g., in conjunction with processor(s)212, memory216, and/or transceiver202, may be configured to receive, on an uplink communication channel, data from the second RRH. Thus, the base station102, the processor(s)212, the communicating component242or one of its subcomponents may define the means for receiving, on an uplink communication channel, data from the second RRH. In some aspects, the method500may include transmitting a second TAG and associated TA offset for the second RRH to the UE following transmission of the first TAG. In some aspects, detecting the switch from the first RRH to the second RRH may include detecting the switch in accordance with the second TAG and associated TA offset for the second RRH, the second TAG and associated TA offset corresponding to a most recent TAG. In some aspects, the first RRH may be associated with a first subset of RSs and the second RRH may be associated with a second subset of RSs, and wherein the second subset of RSs is associated with the TAG and the first subset of RSs is associated with the different TAG. In some aspects, the RSs may correspond to at least one of a SSB reference signal, a channel state information reference signal, or positioning reference signal. In some aspects, the method500may include transmitting, on the downlink communication channel, DCI or a MAC CE indicating one or both of the first RRH or the second RRH to serve the UE. In some aspects, the method500may include transmitting a DCI or MAC CE indicating one or both of a number of cells or PCIs, the number of cells or PCIs are associated with one or both of a serving cell or non-serving cell. FIG.6is a block diagram of a MIMO communication system680including a base station102and a UE104. The MIMO communication system600may illustrate aspects of the wireless communication access network100described with reference toFIG.1. The base station102may be an example of aspects of the base station102described with reference toFIG.1. The base station102may be equipped with antennas634and635, and the UE104may be equipped with antennas652and653. In the MIMO communication system600, the base station102may be able to send data over multiple communication links at the same time. Each communication link may be called a “layer” and the “rank” of the communication link may indicate the number of layers used for communication. For example, in a 2×2 MIMO communication system where base station102transmits two “layers,” the rank of the communication link between the base station102and the UE104is two. At the base station102, a transmit (Tx) processor620may receive data from a data source. The transmit processor620may process the data. The transmit processor620may also generate control symbols or reference symbols. A transmit MIMO processor630may perform spatial processing (e.g., precoding) on data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to the transmit modulator/demodulators632and633. Each modulator/demodulator632through633may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator/demodulator632through633may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a DL signal. In one example, DL signals from modulator/demodulators632and633may be transmitted via the antennas634and635, respectively. The UE104may be an example of aspects of the UEs104described with reference toFIGS.1and2. At the UE104, the UE antennas652and653may receive the DL signals from the base station102and may provide the received signals to the modulator/demodulators654and655, respectively. Each modulator/demodulator654through655may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator654through655may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector656may obtain received symbols from the modulator/demodulators654and655, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (Rx) processor658may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE104to a data output, and provide decoded control information to a processor680, or memory682. The processor680may in some cases execute stored instructions to instantiate a communicating component242(see e.g.,FIGS.1and2). On the uplink (UL), at the UE104, a transmit processor864may receive and process data from a data source. The transmit processor864may also generate reference symbols for a reference signal. The symbols from the transmit processor864may be precoded by a transmit MIMO processor666if applicable, further processed by the modulator/demodulators654and655(e.g., for SC-FDMA, etc.), and be transmitted to the base station102in accordance with the communication parameters received from the base station102. At the base station102, the UL signals from the UE104may be received by the antennas634and635, processed by the modulator/demodulators632and633, detected by a MIMO detector636if applicable, and further processed by a receive processor638. The receive processor638may provide decoded data to a data output and to the processor640or memory642. The components of the UE104may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each of the noted modules may be a means for performing one or more functions related to operation of the MIMO communication system600. Similarly, the components of the base station102may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each of the noted components may be a means for performing one or more functions related to operation of the MIMO communication system600. The above detailed description set forth above in connection with the appended drawings describes examples and does not represent the only examples that may be implemented or that are within the scope of the claims. The term “example,” when used in this description, means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and apparatuses are shown in block diagram form in order to avoid obscuring the concepts of the described examples. Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof. The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a specially-programmed device, such as but not limited to a processor, a digital signal processor (DSP), an ASIC, a FPGA or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. A specially-programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially-programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The functions described herein may be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a specially programmed processor, hardware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Moreover, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from the context, the phrase, for example, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, for example the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. Also, as used herein, including in the claims, “or” as used in a list of items prefaced by “at least one of” indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (A and B and C). Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media. The previous description of the disclosure is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the common principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Furthermore, although elements of the described aspects and/or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. | 52,355 |
11943726 | DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS The following describes the technical solutions of this application with reference to the accompanying drawings. FIG.1is a schematic diagram of a system to which an embodiment of this application is applied. As shown inFIG.1, a system100may include a network device102and terminal devices104,106,108,110,112, and114. The network device and the terminal devices are connected in a wireless manner. It should be understood that only an example in which the system includes one network device is used inFIG.1for description. However, this embodiment of this application is not limited thereto. For example, the system may include more network devices. Similarly, the system may include more terminal devices. It should be further understood that the system may also be referred to as a network. This is not limited in this embodiment of this application. This specification describes the embodiments with reference to a terminal device. The terminal device may also be referred to as user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communications device, a user agent, or a user apparatus. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with a wireless communications function, a computing device or another processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network, a terminal device in a future evolved public land mobile network (PLMN), or the like. By way of example but not limitation, the terminal device may be a wearable device in the embodiments of this application. The wearable device may also be referred to as a wearable intelligent device, and is a generic term of wearable devices that are developed based on intelligent design of routine wear by using a wearable technology, such as glasses, gloves, watches, clothes, or shoes. The wearable device is a portable device that is directly worn on a human body or integrated into user's clothes or ornaments. The wearable device is not merely a hardware device, and further implements a powerful function through software support, data exchange, or cloud interaction. In a broad sense, the wearable intelligent device includes a full-featured and large-sized device that can implement all or some functions without relying on a smartphone, for example, a smartwatch or smart glasses; and includes a device that is dedicated to only one specific type of application function and that needs to be used in combination with another device such as a smartphone, for example, various smart bands or smart ornaments for vital sign monitoring. This specification describes the embodiments with reference to a network device. The network device may be a device configured to communicate with the terminal device. The network device may be a base transceiver station (BTS) in the Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA), a NodeB (NB) in a Wideband Code Division Multiple Access (WCDMA) system, an evolved NodeB (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a radio controller in a cloud radio access network (CRAN) scenario. Alternatively, the network device may be a relay node, an access point, an in-vehicle device, a wearable device, a network device in a future 5G network, a network device in a future evolved PLMN, or the like. In addition, in the embodiments of this application, the network device provides a cell with a service, and the terminal device communicates with the network device by using a transmission resource (for example, a frequency domain resource or a frequency spectrum resource) used in the cell. The cell may be a cell corresponding to the network device (for example, a base station). The cell may be a macro base station, or a base station corresponding to a small cell. The small cell herein may include a metro cell (Metro cell), a micro cell, a pico cell, a femto cell, and the like. These small cells feature in a small coverage area and low transmit power, and are suitable for providing a high-rate data transmission service. In addition, the cell may be a hypercell. It may be understood that the transmission service includes both an uplink transmission service and a downlink transmission service. In this application, transmission includes sending and/or receiving. For the network device in this specification, by way of example but not limitation, one network device may be divided into one centralized unit (CU) and a plurality of transmission reception points (TRP)/distributed units (DU). In other words, a bandwidth based unit (BBU) of the network device is reconstructed as a DU function entity and a CU function entity. It needs to be noted that forms of and quantities of centralized units and TRPs/DUs shall not be construed as a limitation on the embodiments of this application. The CU can process functions of a wireless high-layer protocol stack, such as a radio resource control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer, and even can also support moving of some core network functions down to an access network termed as an edge computing network, thereby meeting a higher network delay requirement of emerging services such as video, online shopping, and virtual/augmented reality in a future communications network. The DU can mainly process physical layer functions and functions of a layer2that has a relatively high real time requirement. In consideration of transmission resources of a radio remote unit (RRU) and the DU, some physical layer functions of the DU may be moved up to the RRU. With miniaturization of the RRU, even more radically, the DU may be combined with the RRU. The CU may be centrally disposed. Disposition of the DUs relies on an actual network environment. The DUs may be centrally disposed in a core urban area with relatively high traffic density and a relatively small inter-station distance, or an area with limited equipment room resources, for example, a college or a large-scale performance venue. The DUs may be disposed in a distributed manner in an area with sparse traffic and a large inter-station distance, for example, a suburban county or a mountainous area. In consideration of a plurality of beams, a plurality of synchronization signal blocks (SS block, SSB) are used in a 5G NR system. FIG.2is a schematic diagram of an example of but not a limitation on a resource structure of a synchronization signal block according to an embodiment of this application. As shown inFIG.2, each SSB may include a primary synchronization signal (PSS) on one orthogonal frequency division multiplexing (OFDM) symbol, a secondary synchronization signal (SSS) on one symbol, and PBCHs on two symbols. A sequence length of an NR-PSS/SSS is 127. The NR-PSS/SSS occupies 127 subcarriers (SC) in frequency domain, and an NR-PBCH occupies 288 subcarriers in frequency domain. In some possible implementations, the NR-SSS may be used for coherent demodulation of the NR-PBCH. Because bandwidth of the NR-PSS/SSS may be inconsistent with bandwidth of the NR-PBCH, even if an AP of the NR-SSS is consistent with an AP of the NR-PBCH, the coherent demodulation of the NR-PBCH may not completely rely on the NR-SSS. Therefore, a new resource structure of the NR-PBCH needs to be considered, and a reference signal needs to be used. The reference signal may be referred to as an NR-PBCH demodulation reference signal (DMRS). The NR-PBCH demodulation reference signal may be another name. This is not limited in this application. In the embodiments of this application, for brevity, the NR-PSS, the NR-SSS, and the NR-PBCH in the synchronization signal block are respectively briefly referred to as a PSS, a SSS, and a PBCH. It should be understood that the PBCH may represent a broadcast signal. It should be understood that in the embodiments of this application, locations of the PSS, the SSS, and the PBCH in the synchronization signal block may change. For example, a location of the PSS and a location of the SSS may interchange with each other, or the SSS may be located in the middle of the PBCHs. This is not limited in the embodiments of this application. It should be understood that the reference signal provided in the technical solutions of the embodiments of this application may be used for PBCH demodulation, and may be further used for estimation of other channels. This is not limited in the embodiments of this application. It should be understood that in the embodiments of this application, a symbol and a subcarrier respectively represent granularity units of a signal transmission time-frequency resource in time domain and frequency domain. The symbol and the subcarrier may have meanings in a current communications system, and may further have meanings in a future communications system. In addition, if names of the symbol and the subcarrier change in the future communications system, the symbol and the subcarrier may also be changed to names in the future communications system. FIG.3is a schematic flowchart of a signal transmission method according to an embodiment of this application. InFIG.3, a network device may be the network device102inFIG.1, and a terminal device may be a terminal device in the terminal devices104,106,108,110,112, and114inFIG.1. Certainly, a quantity of network devices and a quantity of terminal devices in an actual system may not be limited to an example given in this embodiment or another embodiment, and details are not described below again. 310. The network device generates a reference signal. This step is optional. Optionally, the reference signal in this embodiment of this application may be used for channel estimation, for example, PBCH demodulation. However, this is not limited in this embodiment of this application. The network device may generate the reference signal based on a pseudo-random sequence. A manner of generating the reference signal by the network device is not limited in this embodiment of this application. A reference signal generation solution provided in another embodiment of this application is given in the following description, and the reference signal generation solution may also be used in this embodiment. 320. The network device sends the reference signal, where the reference signal is sent in a specific time-frequency resource, and the specific time-frequency resource is located on symbols corresponding to a synchronization signal block. In this embodiment of this application, the specific time-frequency resource represents a time-frequency resource mapping range of the reference signal, and the specific time-frequency resource may also be referred to as a specific time-frequency resource area. The specific time-frequency resource is located on the symbols corresponding to the synchronization signal block. To be specific, in this embodiment of this application, the reference signal can be sent only in the specific time-frequency resource area on the symbols corresponding to the synchronization signal block, instead of being distributed on entire system bandwidth of a radio frame. In this way, the reference signal in this embodiment of this application can be used to ensure demodulation of a signal on the symbols corresponding to the synchronization signal block, for example, PBCH demodulation. In addition, a relatively small quantity of time-frequency resources is occupied, thereby reducing resource overheads. Optionally, in an embodiment of this application, the reference signal is sent in the specific time-frequency resource. To be specific, the reference signal is discretely mapped in the specific time-frequency resource. It may also be understood that resource elements (RE) mapped to the reference signal are not centrally or not consecutively distributed. Optionally, in the specific time-frequency resource, a plurality of REs mapped to the reference signal may be not adjacent in time domain and not adjacent in frequency domain; or a plurality of REs mapped to the reference signal are adjacent in time domain and not adjacent in frequency domain; or a plurality of REs mapped to the reference signal are adjacent in frequency domain and not adjacent in time domain. In this embodiment of this application, a time domain range of the specific time-frequency resource is the symbols corresponding to the synchronization signal block, and may be some of the symbols corresponding to the synchronization signal block, for example, a symbol corresponding to a PBCH of the synchronization signal block or a symbol corresponding to a primary synchronization signal and/or a secondary synchronization signal of the synchronization signal block, or may be all of the symbols corresponding to the synchronization signal block. A frequency domain range of the specific time-frequency resource may be a subcarrier corresponding to the PBCH of the synchronization signal block, or may be entire system bandwidth or partial bandwidth, or the like. In examples in the following embodiments, the frequency domain range of the specific time-frequency resource is the subcarrier corresponding to the PBCH of the synchronization signal block. However, this is not limited in the embodiments of this application. Optionally, in an embodiment of this application, the specific time-frequency resource includes at least one symbol corresponding to the PBCH of the synchronization signal block. Specifically, the specific time-frequency resource may include the symbol corresponding to the PBCH of the synchronization signal block, but not include a symbol corresponding to a synchronization signal of the synchronization signal block. In other words, the reference signal can be sent only in the symbol corresponding to the PBCH. For example, the reference signal can be sent only in a specific time-frequency resource of 288 subcarriers and two symbols that are corresponding to the PBCH. In other words, the specific time-frequency resource may be the 288 subcarriers and the two symbols that are corresponding to the PBCH. Optionally, in an embodiment of this application, as shown inFIG.4, the reference signal is sent only in two symbols corresponding to the PBCH. The plurality of REs mapped to the reference signal is not adjacent in time domain and not adjacent in frequency domain. In other words, the reference signal is mapped to REs that are interleaved in time domain and frequency domain. Optionally, reference signals of different cells may be mapped to different resource locations. To be specific, resource mapping of the reference signal may rely on a cell identifier, thereby avoiding mutual reference signal interference between cells. As shown inFIG.5, resource locations of a reference signal in another cell different from that inFIG.4may be different from those inFIG.4. When performing channel estimation, the terminal device may perform linear interpolation on a neighboring reference signal to relatively precisely estimate an RE to which no reference signal is mapped, thereby ensuring PBCH demodulation accuracy. In this embodiment, a reference signal exists on a symbol corresponding to each PBCH. Therefore, for PBCH demodulation, channel estimation may be performed without relying on a synchronization signal. Optionally, in an embodiment of this application, as shown inFIG.6, the reference signal is sent only in two symbols corresponding to the PBCH. Two REs mapped to the reference signal are adjacent in time domain and not adjacent in frequency domain. In other words, the reference signal is mapped to REs that are consecutive in time domain. Optionally, reference signals of different cells may be mapped to different resource locations. To be specific, resource mapping of the reference signal may rely on a cell identifier, thereby avoiding mutual reference signal interference between cells. As shown inFIG.7, resource locations of a reference signal in another cell different from that inFIG.6may be different from those inFIG.6. In this embodiment, the reference signal is mapped to the REs that are consecutive in time domain, so that a quantity of APs of the reference signal can be increased by using orthogonal cover code (OCC) on consecutive resources, thereby supporting a multi-AP PBCH transmission solution. In the foregoing embodiment, the REs mapped to the reference signal are adjacent in time domain and not adjacent in frequency domain. Optionally, the REs mapped to the reference signal may be adjacent in frequency domain and not adjacent in time domain. In other words, the reference signal may be mapped to REs that are consecutive in frequency domain. In this way, similarly, a quantity of APs of the reference signal can be increased by using orthogonal cover code on consecutive resources, thereby supporting a multi-AP PBCH transmission solution. Optionally, in an embodiment of this application, the reference signal is not sent on the at least one symbol corresponding to the PBCH. It may also be understood that the reference signal is sent on some symbols corresponding to the PBCH. In this embodiment, the reference signal is not sent on all symbols corresponding to the PBCH. For example, the reference signal may be sent on only one symbol corresponding to the PBCH, or sent on none of the symbols corresponding to the PBCH. For example, as shown inFIG.8, the reference signal is sent on only one symbol corresponding to the PBCH. As shown inFIG.9, the reference signal is sent on neither of two symbols corresponding to the PBCH. Similar to the foregoing embodiments, reference signals of different cells may be mapped to different resource locations. To be specific, resource mapping of the reference signal may rely on a cell identifier, thereby avoiding mutual reference signal interference between cells. For brevity, details are not described again in the following embodiments. When the reference signal is sent on neither of the two symbols corresponding to the PBCH, the terminal device performs channel estimation based on a SSS. When the reference signal is sent on one symbol corresponding to the PBCH, when performing channel estimation, the terminal device may perform linear interpolation on a SSS and a neighboring reference signal to relatively precisely estimate an RE to which no reference signal is mapped, thereby ensuring PBCH demodulation accuracy. In this way, resource overheads of the reference signal in the symbol corresponding to the PBCH are reduced. Optionally, in an embodiment of this application, a quantity of REs mapped to the reference signal in a first area of the specific time-frequency resource is greater than a quantity of REs mapped to the reference signal in a second area of the specific time-frequency resource, the primary synchronization signal and/or the secondary synchronization signal of the synchronization signal block are/is not sent on a subcarrier corresponding to the first area, and the primary synchronization signal and/or the secondary synchronization signal are/is sent on a subcarrier corresponding to the second area. Specifically, because bandwidth of a synchronization signal is inconsistent with bandwidth of the PBCH, two areas exist in the specific time-frequency resource. The primary synchronization signal and/or the secondary synchronization signal of the synchronization signal block are/is not sent on the subcarrier corresponding to the first area, and the primary synchronization signal and/or the secondary synchronization signal are/is sent on the subcarrier corresponding to the second area. For the two types of areas, different quantities of REs may be used to map to the reference signal. To be specific, the quantity of REs mapped to the reference signal in the first area may be greater than the quantity of REs mapped to the reference signal in the second area. For example, inFIG.10, a synchronization signal is sent in the upper area, and no synchronization signal is sent in the lower area. Therefore, reference signal resources are relatively sparse in an upper area of the symbol corresponding to the PBCH, and reference signal resources are relatively dense in a lower area of the symbol corresponding to the PBCH. When a SSS is sent, the terminal device may improve PBCH estimation accuracy by performing linear interpolation on the SSS, thereby lowering a requirement for the reference signal. Optionally, in an embodiment of this application, the specific time-frequency resource may further include the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal of the synchronization signal block. In a third area of the specific time-frequency resource, the reference signal is sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal. In a fourth area of the specific time-frequency resource, the reference signal is not sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal. The primary synchronization signal and/or the secondary synchronization signal are/is not sent on a subcarrier corresponding to the third area. The primary synchronization signal and/or the secondary synchronization signal are/is sent on a subcarrier corresponding to the fourth area. Specifically, in this embodiment, the specific time-frequency resource is expanded to further include the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal of the synchronization signal block. In addition, when the bandwidth of the synchronization signal is inconsistent with the bandwidth of the PBCH, in an area in which the primary synchronization signal and/or the secondary synchronization signal are/is not sent, the reference signal is sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal; and in an area in which the primary synchronization signal and/or the secondary synchronization signal are/is sent, the reference signal is not sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal. For example, inFIG.11, no secondary synchronization signal is sent in the lower area. Therefore, the reference signal is sent in a lower area of a symbol corresponding to the secondary synchronization signal. Optionally, no or few reference signals may be sent in a lower area of the symbol corresponding to the PBCH. In this way, on a PRB without a SSS, the terminal device may improve PBCH estimation accuracy by performing linear interpolation on a time-domain reference signal while no or few resources of the PBCH are occupied. It should be understood that some changes may be made to the embodiments of this application. For example, the resource locations of the reference signal or a quantity of reference signals may be properly changed. These changes should also be considered as embodiments of this application. For brevity, these similar changes are not described one by one. It should be understood that the implementations of the embodiments of this application may be separately implemented or jointly implemented. This is not limited in the embodiments of this application. Various solutions for mapping a reference signal to resource locations are given in the foregoing embodiments. It should be understood that a specific manner of mapping a reference signal sequence to resource locations is not limited in the embodiments of this application. A specific mapping manner provided in another embodiment of this application is given in the following description, and the specific mapping manner may be combined into this embodiment. For transmission of the reference signal, the terminal device receives the reference signal accordingly and performs subsequent processing, for example, performs channel estimation based on the reference signal. The receiving by the terminal device corresponds to the sending by the network device, and therefore details are not described again. The resource locations to which the reference signal is mapped are described in the foregoing embodiments. The embodiments of this application further provide a reference signal generation solution, which is described below in detail. It should be understood that the following embodiments may be combined with the foregoing embodiments. For example, the reference signal may be generated in the manner in the following embodiments, and then sent in the transmission manner in the foregoing embodiments. In addition, for the following embodiments, refer to related description in the foregoing embodiments. For brevity, details are not described again. FIG.12is a schematic flowchart of a signal transmission method according to another embodiment of this application. A network device generates a reference signal by using a time-frequency resource unit as a unit, where the time-frequency resource unit is located on symbols corresponding to a synchronization signal block. In this embodiment of this application, the time-frequency resource unit is located on the symbols corresponding to the synchronization signal block, and the network device generates the reference signal by using the time-frequency resource unit as a unit. In other words, a unit based on which the network device generates the reference signal is limited to the symbols corresponding to the synchronization signal block, instead of a radio frame. In this way, a reference signal sequence may be repeated for different synchronization signal blocks, and therefore a terminal device does not need to extract a sequence from a long sequence during reference signal detection. In this embodiment of this application, a time domain range of the time-frequency resource unit is the symbols corresponding to the synchronization signal block, and may be all of the symbols corresponding to the synchronization signal block or some of the symbols corresponding to the synchronization signal block. For example, the time domain range of the time-frequency resource unit may be a symbol corresponding to a PBCH of the synchronization signal block, or a symbol corresponding to a primary synchronization signal and/or a secondary synchronization signal of the synchronization signal block. A frequency domain range of the time-frequency resource unit may be all subcarriers corresponding to the synchronization signal block, or subcarriers of one or more PRBs corresponding to the synchronization signal block, or entire system bandwidth. This is not limited in this embodiment of this application. Optionally, in an embodiment of this application, the time-frequency resource unit is a time-frequency resource corresponding to the PBCH of the synchronization signal block on at least one PRB. In other words, the time-frequency resource unit may be all time-frequency resources corresponding to the BPCH of the synchronization signal block, or a time-frequency resource corresponding to the PBCH of the synchronization block on one or more PRBs. Optionally, in an embodiment of this application, the time-frequency resource unit is a time-frequency resource corresponding to the synchronization signal block on at least one PRB. Optionally, in an embodiment of this application, the time-frequency resource unit is a time-frequency resource corresponding to the synchronization signal block. Optionally, in an embodiment of this application, the time-frequency resource unit is a time-frequency resource corresponding to the primary synchronization signal and/or the secondary synchronization signal of the synchronization signal block on at least one PRB. Optionally, in an embodiment of this application, for a multi-subband system, the frequency domain range of the time-frequency resource unit may be expanded to the entire system bandwidth. The network device generates a reference signal sequence by using the time-frequency resource unit as a unit. In other words, a length of the reference signal sequence depends on the time-frequency resource unit. Optionally, in an embodiment of this application, a parameter for generating the reference signal is associated with at least one of a cell ID, a subband sequence number, a PRB sequence number, and an antenna port number. For example, the reference signal sequence may be in the following form: rl,p(m)=12(1-2c(2m))+j12(1-2c(2m+1)),(1) where m indicates an mthunit (or referred to as element) in the sequence, l is a sequence number of an OFDM symbol in one SS block, values of m and l may be determined based on the time-frequency resource unit, p is the antenna port number, and c(m) is a pseudo-random sequence and may be initialized in the following manner: cinit=f(l,p,NIDcell) (2), where NIDcellis the cell ID. In formula (1), the values of m and l may be determined based on the time-frequency resource unit, so that the length of the reference signal sequence may be determined based on the time-frequency resource unit. Therefore, the time-frequency resource unit is used as a unit for the reference signal sequence generated in this manner. To be specific, the reference signal sequence may be repeated on different time-frequency resource units, thereby preventing the terminal device from extracting a sequence from a long sequence during reference signal detection. 1220. The network device sends the reference signal. This processing is optional. Optionally, in an embodiment of this application, the reference signal may be mapped by using the time-frequency resource unit as a unit. After generating the reference signal by using the time-frequency resource unit as a unit, the network device may map the reference signal by using the time-frequency resource unit as a unit during the sending. In other words, a reference signal may be independently generated and mapped based on each time-frequency resource unit. This manner is easy to expand, and is not limited by a size of a physical channel resource block. Optionally, in an embodiment of this application, a manner of mapping the reference signal is associated with at least one of the cell ID, the subband sequence number, the PRB sequence number, and the antenna port number. For example, the foregoing sequence ri,p(m) is mapped to a complex modulation symbol ak,j(p)and then is used as a reference symbol of a timeslot port: ak,l(p)=rl,p(m′) (3) k=6m+(v+vshift) mod 6 (4) l={0,NsymbDL-3ifp∈{0,1}1ifp∈{2,3}(5) m=0,1, . . . ,2·NRBDL−1 (6) m′=m+NRBmax,DL−NRBDL(7),where variables v and vshiftdefine a frequency-domain location of the reference signal, a frequency shift vshift=NIDcellmod 6, NRBDLrepresents configured downlink system bandwidth for which a resource block (RB) is used as a unit, NRBmax,DLrepresents maximum downlink system bandwidth for which a resource block (RB) is used as a unit, k is a subcarrier sequence number, and m is a mapping unit. Optionally, because the PBCH has a limited quantity of transmission ports, for reference signals corresponding to different antenna ports, orthogonality may be ensured through frequency division multiplexing (FDM), time division multiplexing (TDM), or code division multiplexing (CDM) (OCC may be used). For transmission of the reference signal, the terminal device receives the reference signal accordingly and performs subsequent processing, for example, performs channel estimation based on the reference signal. The receiving by the terminal device corresponds to the sending by the network device, and therefore details are not described again. It should be understood that specific examples in the embodiments of this application are merely intended to help persons skilled in the art better understand the embodiments of this application, rather than limiting the scope of the embodiments of this application. It should be understood that in the embodiments of this application, the sequence numbers of the foregoing processes do not mean execution orders. The execution orders of the processes should be determined based on functions and internal logic of the processes, and should not be construed as any limitation on the implementation processes in the embodiments of this application. The signal transmission methods according to the embodiments of this application are described above in detail. The following describes signal transmission apparatuses according to the embodiments of this application. FIG.13is a schematic block diagram of a signal transmission apparatus1300according to an embodiment of this application. The apparatus1300may be a network device. It should be understood that the apparatus1300may correspond to the network device in the method embodiments, and may have any function of the network device in the methods. As shown inFIG.13, the apparatus1300includes a processor1310and a transceiver1320. In an embodiment, the processor1310is configured to generate a reference signal and the transceiver1320is configured to send the reference signal, where the reference signal is sent in a specific time-frequency resource, and the specific time-frequency resource is located on symbols corresponding to a synchronization signal block. Optionally, the specific time-frequency resource includes at least one symbol corresponding to a physical broadcast channel PBCH of the synchronization signal block. Optionally, in the specific time-frequency resource, a plurality of resource elements REs mapped to the reference signal are not adjacent in time domain and not adjacent in frequency domain, or a plurality of REs mapped to the reference signal are adjacent in time domain and not adjacent in frequency domain, or a plurality of REs mapped to the reference signal are adjacent in frequency domain and not adjacent in time domain. Optionally, the reference signal is not sent on the at least one symbol corresponding to the PBCH. Optionally, a quantity of REs mapped to the reference signal in a first area of the specific time-frequency resource is greater than a quantity of REs mapped to the reference signal in a second area of the specific time-frequency resource, a primary synchronization signal and/or a secondary synchronization signal of the synchronization signal block are/is not sent on a subcarrier corresponding to the first area, and the primary synchronization signal and/or the secondary synchronization signal are/is sent on a subcarrier corresponding to the second area. Optionally, the specific time-frequency resource further includes a symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal of the synchronization signal block. In a third area of the specific time-frequency resource, the reference signal is sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal. In a fourth area of the specific time-frequency resource, the reference signal is not sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal. The primary synchronization signal and/or the secondary synchronization signal are/is not sent on a subcarrier corresponding to the third area. The primary synchronization signal and/or the secondary synchronization signal are/is sent on a subcarrier corresponding to the fourth area. Optionally, a frequency domain range of the specific time-frequency resource is a subcarrier corresponding to the PBCH of the synchronization signal block. Optionally, the processor1310is configured to generate the reference signal by using a time-frequency resource unit as a unit, where the time-frequency resource unit is located on the symbols corresponding to the synchronization signal block. Optionally, the time-frequency resource unit is a time-frequency resource corresponding to the PBCH of the synchronization signal block on at least one physical resource block PRB, or the time-frequency resource unit is a time-frequency resource corresponding to the synchronization signal block. Optionally, a parameter for generating the reference signal is associated with at least one of a cell ID, a subband sequence number, a PRB sequence number, and an antenna port number. Optionally, the transceiver1320is configured to map the reference signal by using the time-frequency resource unit as a unit, or the processor1310is configured to map the reference signal by using the time-frequency resource unit as a unit. Optionally, a manner of mapping the reference signal is associated with at least one of the cell ID, the subband sequence number, the PRB sequence number, and the antenna port number. In another embodiment, the processor1310is configured to generate a reference signal by using a time-frequency resource unit as a unit, where the time-frequency resource unit is located on symbols corresponding to a synchronization signal block and the transceiver1320is configured to send the reference signal. Optionally, the time-frequency resource unit is a time-frequency resource corresponding to a physical broadcast channel PBCH of the synchronization signal block on at least one physical resource block PRB, or the time-frequency resource unit is a time-frequency resource corresponding to the synchronization signal block. Optionally, a parameter for generating the reference signal is associated with at least one of a cell ID, a subband sequence number, a PRB sequence number, and an antenna port number. Optionally, the transceiver1320is configured to map the reference signal by using the time-frequency resource unit as a unit. Optionally, a manner of mapping the reference signal is associated with at least one of the cell ID, the subband sequence number, the PRB sequence number, and the antenna port number. FIG.14is a schematic block diagram of a signal transmission apparatus1400according to another embodiment of this application. The apparatus1400may be a terminal device. It should be understood that the apparatus1400may correspond to the terminal device in the method embodiments, and may have any function of the terminal device in the methods. As shown inFIG.14, the apparatus1400includes a transceiver1420, and optionally, further includes a processor1410. In an embodiment, the transceiver1420is configured to receive a reference signal, where the reference signal is sent in a specific time-frequency resource, and the specific time-frequency resource is located on symbols corresponding to a synchronization signal block. Optionally, the processor1410is configured to perform channel estimation based on the reference signal. Optionally, the specific time-frequency resource includes at least one symbol corresponding to a physical broadcast channel PBCH of the synchronization signal block. Optionally, in the specific time-frequency resource, a plurality of resource elements REs mapped to the reference signal are not adjacent in time domain and not adjacent in frequency domain, or a plurality of REs mapped to the reference signal are adjacent in time domain and not adjacent in frequency domain, or a plurality of REs mapped to the reference signal are adjacent in frequency domain and not adjacent in time domain. Optionally, the reference signal is not sent on the at least one symbol corresponding to the PBCH. Optionally, a quantity of REs mapped to the reference signal in a first area of the specific time-frequency resource is greater than a quantity of REs mapped to the reference signal in a second area of the specific time-frequency resource, a primary synchronization signal and/or a secondary synchronization signal of the synchronization signal block are/is not sent on a subcarrier corresponding to the first area, and the primary synchronization signal and/or the secondary synchronization signal are/is sent on a subcarrier corresponding to the second area. Optionally, the specific time-frequency resource further includes a symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal of the synchronization signal block. In a third area of the specific time-frequency resource, the reference signal is sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal. In a fourth area of the specific time-frequency resource, the reference signal is not sent on the symbol corresponding to the primary synchronization signal and/or the secondary synchronization signal. The primary synchronization signal and/or the secondary synchronization signal are/is not sent on a subcarrier corresponding to the third area. The primary synchronization signal and/or the secondary synchronization signal are/is sent on a subcarrier corresponding to the fourth area. Optionally, a frequency domain range of the specific time-frequency resource is a subcarrier corresponding to the PBCH of the synchronization signal block. Optionally, the reference signal is generated by using a time-frequency resource unit as a unit, and the time-frequency resource unit is located on the symbols corresponding to the synchronization signal block. Optionally, the time-frequency resource unit is a time-frequency resource corresponding to the PBCH of the synchronization signal block on at least one physical resource block PRB, or the time-frequency resource unit is a time-frequency resource corresponding to the synchronization signal block. Optionally, a parameter for generating the reference signal is associated with at least one of a cell ID, a subband sequence number, or a PRB sequence number. Optionally, the reference signal is mapped by using the time-frequency resource unit as a unit. Optionally, a manner of mapping the reference signal is associated with at least one of the cell ID, the subband sequence number, the PRB sequence number, and an antenna port number. In another embodiment, the transceiver1420is configured to receive a reference signal, where the reference signal is generated by using a time-frequency resource unit as a unit, and the time-frequency resource unit is located on symbols corresponding to a synchronization signal block. Optionally, the apparatus1400further includes the processor1410, configured to perform channel estimation based on the reference signal. Optionally, the time-frequency resource unit is a time-frequency resource corresponding to a physical broadcast channel PBCH of the synchronization signal block on at least one physical resource block PRB, or the time-frequency resource unit is a time-frequency resource corresponding to the synchronization signal block. Optionally, a parameter for generating the reference signal is associated with at least one of a cell ID, a subband sequence number, or a PRB sequence number. Optionally, the reference signal is mapped by using the time-frequency resource unit as a unit. Optionally, a manner of mapping the reference signal is associated with at least one of the cell ID, the subband sequence number, the PRB sequence number, and an antenna port number. It should be understood that the processor1310or the processor1410in the embodiments of this application may be implemented by using a processing unit or a chip. Optionally, in an implementation process, the processing unit may include a plurality of units, such as a mapping unit, and/or a signal generation unit, and/or a channel estimation unit. It should be understood that the transceiver1320or the transceiver1420in the embodiments of this application may be implemented by using a transceiver unit or a chip. Optionally, the transceiver1320or the transceiver1420may include a transmitter or a receiver, or may include a transmission unit or a receiving unit. It should be understood that the processor1310and the transceiver1320in the embodiments of this application may be implemented by using a chip, and the processor1410and the transceiver1420may be implemented by using a chip. Optionally, the network device or the terminal device may further include a memory, the memory may store program code, and the processor invokes the program code stored in the memory, to implement a corresponding function of the network device or the terminal device. Optionally, the processor and the memory may be implemented by using a chip. An embodiment of this application further provides a processing apparatus, including a processor and an interface and the processor is configured to perform the methods in the foregoing embodiments of this application. The processing apparatus may be a chip, and the processor may be implemented by using hardware or software. When being implemented by using hardware, the processor may be a logic circuit, an integrated circuit, or the like. When being implemented by using software, the processor may be a general-purpose processor, and is implemented by reading software code stored in a memory. The memory may be integrated into the processor, or may be located independently of the processor. For example, the processing apparatus may be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system on chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro control unit (MCU), a programmable logic device (PLD), or another integrated chip. An embodiment of this application further provides a communications system, including the network device in the foregoing network device embodiment and the terminal device in the terminal device embodiment. All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or some of the embodiments may be implemented in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or some of the procedures or functions according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instruction may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible to a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), a semiconductor medium (for example, a solid state disk (SSD)), or the like. It should be understood that the term “and/or” in the embodiments of this application describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, the character “/” in this specification generally indicates an “or” relationship between the associated objects. Persons of ordinary skill in the art may be aware that in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps can be implemented by using electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by using hardware or software depends on particular applications and design constraint conditions of the technical solutions. Persons skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application. It may be clearly understood by persons skilled in the art that for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, reference may be made to a corresponding process in the foregoing method embodiments, and details are not described herein again. In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus embodiments are merely examples. For example, the unit division is merely logical function division and may be other division during actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms. The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, to be specific, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments. In addition, the function units in the embodiments of this application may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit. When the functions are implemented in a form of a software function unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods described in the embodiments of this application. The storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc. The foregoing descriptions are merely specific implementations of this application, but are not intended to limit the protection scope of this application. Any variation or replacement readily figured out by persons skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims. | 51,822 |
11943727 | DESCRIPTION OF EMBODIMENTS The following first briefly describes related concepts in embodiments of this application. FIG.1is a schematic structural diagram of a synchronization signal block. A synchronization signal block is a signal structure, and includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). It should be noted that the synchronization signal block usually occupies four orthogonal frequency division multiplexing (OFDM) symbols. The primary synchronization signal and the secondary synchronization signal are used to assist a terminal in identifying a cell and performing synchronization with the cell. The PBCH includes most basic system information, such as a system frame number and intra-frame timing information. Currently, a sequence of the secondary synchronization signal is generated according to the following formula (1): c(n)=(x0(n+i1)+x1(n+i2))mod 2 (1) c(n) is the sequence of the secondary synchronization signal, where n is an integer greater than or equal to 0 and less than or equal to 126. i1=(3×⌊NID1112⌋+NID2)×5,andi2=(NID1)mod112. NID1 is an identifier of a physical cell identifier group, and NID1 is an integer greater than or equal to 0 and less than or equal to 335. NID2 is an intra-group ID of the physical cell identifier group, and a value range of NID2 is {0, 1, 2}. It should be noted that, Ncell=3*NID1+NID2, where Ncellis a physical cell identifier (physical cell identifier, PCI). x0(n) and x1(n) are both M-sequences. It should be noted that the M-sequence is a pseudo-random-sequence generated by using a linear feedback shift register (LFSR). There is a unique M-sequence corresponding to a determined LFSR with a given initial value. Therefore, a transmit end generates M-sequences by using different initial values, and a receive end may uniquely determine the M-sequence through sequence detection. A used shift register in x0(n) is: x0(i+7)=(x0(i+4)+x0(i))mod 2, where initial values are: x0(0)=0, x0(1)=0, x0(2)=0, x0(3)=0, x0(4)=0, x0(5)=0, and x0(6)=1. A used shift register in x1(n) is: x1(i+7)=(x1(i+1)+x1(i))mod 2, where initial values are: x1(0)=0, x1(1)=0, x1(2)=0, x1(3)=0, x1(4)=0, x1(5)=0, and x1(6)=1. In descriptions of this application, unless otherwise specified, “/” means “or”. For example, A/B may represent A or B. The term “and/or” in this specification describes only an association relationship for associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, “at least one” means one or more, and “a plurality of” means two or more. Words such as “first” and “second” do not limit a quantity and an execution sequence, and the words such as “first” and “second” do not indicate a definite difference. It should be noted that in this application, the word such as “example” or “for example” is used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as an “example” or “for example” in this application should not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the word “example”, “for example”, or the like is intended to present a related concept in a specific manner. The following describes technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. FIG.2shows a synchronization signal block sending and receiving method according to an embodiment of this application. The method includes the following steps. S101. A first terminal determines, based on a correspondence between information about locations of M antenna panels and P synchronization signal blocks of the first terminal and information about locations of N antenna panels, a synchronization signal block corresponding to each of the N antenna panels. The M antenna panels are configured for the first terminal, where M is a positive integer. The M antenna panels are deployed on different parts of the first terminal, for example, a front bumper, a rear bumper, and the top of a vehicle. It may be understood that the N antenna panels are included in the M panels. In other words, the N antenna panels are all or a part of the M antenna panels of the first terminal. N is less than or equal to M, P is an integer multiple of M, and M, N and P are positive integers. It may be understood that P is equal to M, and information about a location of one of the M antenna panels of the first terminal corresponds to one of the M synchronization signal blocks. Alternatively, P is at least twice greater than M, and information about a location of one of the M antenna panels of the first terminal corresponds to at least two of the P synchronization signal blocks. In this embodiment of this application, the information about the locations of the M antenna panels is used to indicate the locations of the M antenna panels on the first terminal. Optionally, the information about the location of the antenna panel may be a location index, a location identifier, or the like. For example, the information about the location of the antenna panel is a location index. For the location indexes of the antenna panels, refer to Table 1. TABLE 1LocationindexLocation of an antenna panel on the first terminal00The antenna panel is on the front bumper of the first terminal.01The antenna panel is on the rear bumper of the first terminal.10The antenna panel is on the left side of the vehicle bodyof the first terminal.11The antenna panel is on the right side of the vehicle body ofthe first terminal.. . .. . . In this embodiment of this application, the M antenna panels of the first terminal are configured to cover different sectors. It may be understood that the antenna panel on the front bumper of the first terminal can cover only a front area of the vehicle, but cannot cover a rear area of the vehicle. The antenna panel on the right side of the vehicle body of the first terminal can cover only an area on the right side of the vehicle body, but cannot cover an area on the left side of the vehicle body. In this way, in actual application, to ensure a coverage effect, a sector covered by the antenna panel is determined by a location of the antenna panel on the first terminal. That is, there is a correspondence between a sector covered by an antenna panel and information about a location of the antenna panel. In other words, information about a location of an antenna panel is further used to implicitly indicate a sector covered by the antenna panel. Optionally, the correspondence between the sector covered by the antenna panel and the sector covered by the antenna panel is preconfigured, or is specified in a standard. For example, in a polar coordinate system in which the first terminal is used as a pole and a vehicle head direction is used as a polar axis, the antenna panel on the front bumper of the first terminal is responsible for covering a sector from 45° to 315°, the antenna panel on the right side of the vehicle body of the first terminal is responsible for covering a sector from 45° to 135°, the antenna panel on the rear bumper of the first terminal is responsible for a sector from 135° to 225°, and the antenna panel on the right side of the vehicle body of the first terminal is responsible for covering a sector from 225° to 315°. For another example, descriptions are provided with reference toFIG.3. The antenna panel on the front bumper of the first terminal is responsible for a sector1, the antenna panel on the left side of the vehicle body of the first terminal is responsible for a sector2, the antenna panel on the rear bumper of the first terminal is responsible for a sector3, and the antenna panel on the right side of the vehicle body of the first terminal is responsible for a sector4. In this embodiment of this application, there is a correspondence between information about a location of an antenna panel and a synchronization signal block. The correspondence between the information about the location of the antenna panel and the synchronization signal block may be preconfigured on the first terminal and/or a second terminal, determined through negotiation between the first terminal and a second terminal, or specified in a standard. Because there is the correspondence between the information about the location of the antenna panel and the synchronization signal block, antenna panels at different locations on the first terminal correspond to different synchronization signal blocks. In other words, the synchronization signal block may be used to indicate the information about the location of the antenna panel that sends the synchronization signal block. In an implementation, the synchronization signal block explicitly indicates the information about the location of the antenna panel that sends the synchronization signal block. Optionally, a PBCH in the synchronization signal block carries the information about the location of the antenna panel that sends the synchronization signal block. In another implementation, the synchronization signal block implicitly indicates the information about the location of the antenna panel that sends the synchronization signal block. In this case, the correspondence between the information about the locations of the M antenna panels and the P synchronization signal blocks includes one or any combination of the following cases. Case 1: There is a correspondence between the information about the locations of M antenna panels and P resource mapping modes. The resource mapping mode is used to indicate a location of a time-frequency resource occupied by a primary synchronization signal and a location of a time-frequency resource occupied by a secondary synchronization signal in the synchronization signal block. It should be noted that the resource mapping mode may have different names, for example, a resource pattern. This is not limited in this embodiment of this application. If P is equal to M, information about a location of one of the M antenna panels of the first terminal corresponds to one of the P resource mapping modes. Alternatively, if P is at least twice greater than M, information about a location of one of the M antenna panels of the first terminal corresponds to at least two of the P resource mapping modes. It may be understood that because there is a correspondence between information about a location of an antenna panel and a resource mapping mode, antenna panels at different locations on the first terminal correspond to different resource mapping modes. In other words, synchronization signal blocks sent by antenna panels at different locations on the first terminal use different resource mapping modes. Therefore, the synchronization signal blocks sent by the antenna panels at the different locations on the first terminal are constructed differently, so that synchronization signal blocks sent by the antenna panels at different locations on the first terminal are different. It should be noted that, that synchronization signal blocks using different resource mapping modes are constructed differently includes the following two cases. Case (1): If the synchronization signal blocks use different resource mapping modes, locations of a time-frequency resource occupied by a primary synchronization signal and a time-frequency resource occupied by a secondary synchronization signal in a synchronization signal block are different from those in another synchronization signal block. The following describes the foregoing case (1) by using an example. For example, the information about the location of the antenna panel is a location index, and P is equal to M. For a correspondence between a location index of an antenna panel and a resource mapping mode, refer to Table 2. For example, for a resource mapping mode 1, refer toFIG.4. For a resource mapping mode 2, refer toFIG.5. For a resource mapping mode 3, refer toFIG.6. For a resource mapping mode 4, refer toFIG.7. TABLE 2Location index of an antenna panelResource mapping mode00Resource mapping mode 111Resource mapping mode 201Resource mapping mode 310Resource mapping mode 4. . .. . . For example, the information about the location of the antenna panel is a location index, and P is twice greater than M. For a correspondence between a location index of an antenna panel and a resource mapping mode, refer to Table 3. TABLE 3Location index of an antenna panelResource mapping mode00Resource mapping mode 100Resource mapping mode 201Resource mapping mode 301Resource mapping mode 4. . .. . . Case (2): If the synchronization signal blocks use different resource mapping modes, a time domain resource occupied by a primary synchronization signal and a time domain resource occupied by a secondary synchronization signal in a synchronization signal block are different from those in another synchronization signal block. Optionally, in this case, the correspondence between the information about the locations of the M antenna panels and the P resource mapping modes includes a correspondence between the information about the locations of the M antenna panels and time domain offsets of P primary synchronization signals, and/or a correspondence between the information about the locations of the M antenna panels and time domain offsets of P secondary synchronization signals. The time domain offset of the primary synchronization signal is an offset between an OFDM symbol occupied by the primary synchronization signal in the synchronization signal block and an initial OFDM symbol of the synchronization signal block. The time domain offset of the secondary synchronization signal is an offset between an OFDM symbol occupied by the secondary synchronization signal in the synchronization signal block and an initial OFDM symbol of the synchronization signal block. For example, the information about the location of the antenna panel is a location index, and P is equal to M. For a correspondence between information about a location of an antenna panel and a time domain offset of a primary synchronization signal in a synchronization signal block, and a correspondence between information about a location of an antenna panel and a time domain offset of a secondary synchronization signal in a synchronization signal block, refer to Table 4. TABLE 4Location indexTime domain offsetTime domain offsetof anof a primaryof a secondaryantenna panelsynchronization signalsynchronization signal0010111201311002. . .. . .. . . For example, with reference to Table 3, for a resource mapping mode corresponding to an antenna panel whose location index is 00, refer toFIG.8. For a resource mapping mode corresponding to an antenna panel whose location index is 11, refer toFIG.9. For a resource mapping mode corresponding to an antenna panel whose location index is 01, refer toFIG.10. For a resource mapping mode corresponding to an antenna panel whose location index is 10, refer toFIG.11. It may be understood that the resource mapping modes shown inFIG.4toFIG.11are merely examples provided in the embodiments of this application, and constitute no limitation. Case (2): There is a correspondence between the information about the locations of the M antenna panels and sequences of P secondary synchronization signals. If P is equal to M, information about a location of one of the M antenna panels of the first terminal corresponds to a sequence of one secondary synchronization signal in the sequences of the P secondary synchronization signals. Alternatively, if P is at least twice greater than M, information about a location of one of the M antenna panels of the first terminal corresponds to sequences of at least two secondary synchronization signals in the sequences of the P secondary synchronization signals. It may be understood that because there is a correspondence between information about a location of an antenna panel and a sequence of a secondary synchronization signal, antenna panels at different locations on the first terminal correspond to different sequences of secondary synchronization signals, so that the antenna panels at different locations on the first terminal correspond to different synchronization signal blocks. In an implementation, a sequence of a secondary synchronization signal is generated according to the following formula (2): c(n)=(x0(n+i1+k)+x1(n+i2+l))mod 2 (2) c(n) is the sequence of the secondary synchronization signal, where n is a positive integer greater than or equal to 0 and less than or equal to 126. i1=(3×⌊NID1112⌋+NID2)×5,andi2=(NID1)mod112. NID1 is an identifier of a physical cell identifier group, and NID1 is an integer greater than or equal to 0 and less than or equal to 335. NID2 is an intra-group ID of a physical cell identifier group, and a value range of NID2 is {0, 1, 2}. x0(n) and x1(n) are both M-sequences. For x0(n) and x1(n), refer to the foregoing descriptions. Details are not described herein again. k is a first cyclic displacement parameter, and l is a second cyclic displacement parameter. Both k and l are integers, and k and l are determined based on the information about the location of the antenna panel. For example, k and l are determined based on a correspondence between the information about the location of the antenna panel, k, and l. For example, the information about the location of the antenna panel is a location index, and P is equal to M. For a correspondence between k, l, and the location index of the antenna panel, refer to Table 5. TABLE 5Location index of an antenna panelkl0012113401231014. . .. . .. . . For example, the information about the location of the antenna panel is a location index, and P is twice greater than M. For a correspondence between k, l, and the location index of the antenna panel, refer to Table 6. TABLE 6Location index of an antenna panelkl00120034112311141034104301560165. . .. . .. . . The following describes, by using an example, a scenario in which Case (1) and Case (2) are combined. For example, P is equal to M. For a correspondence between information about a location of an antenna panel and a synchronization signal block, refer to Table 7. TABLE 7Location index ofan antenna panelResource mapping modekl000Resource mapping mode 112001Resource mapping mode 134010Resource mapping mode 212011Resource mapping mode 234100Resource mapping mode 312. . .. . .. . .. . . In other words, for any two antenna panels of the first terminal, resource mapping modes used for synchronization signal blocks corresponding to the two antenna panels are different, and/or sequences of secondary synchronization signals in the synchronization signal blocks corresponding to the two antenna panels are different. It may be understood that Case (1) and Case (2) are merely examples of the correspondence between the information about the locations of the M antenna panels and the P synchronization signal blocks. This embodiment of this application is not limited thereto. S102. The first terminal separately sends, by using each of the N antenna panels, the synchronization signal block corresponding to each of the N antenna panels. It may be understood that, compared with a synchronization signal block sending method in a conventional technology in which N antenna panels form an antenna array to perform beam scanning, in technical solutions provided in this embodiment of this application, because the N antenna panels cover different sectors, the first terminal simultaneously sends, by using each of the N antenna panels, the synchronization signal block corresponding to each of the N antenna panels, so that a beam scanning time period can be reduced, and a transmission delay of the synchronization signal blocks can be reduced. For example, it is assumed that the antenna panel on the front bumper of the first terminal corresponds to a synchronization signal block 1, the antenna panel on the rear bumper of the first terminal corresponds to a synchronization signal block 2, the antenna panel on the left side of the vehicle body of the first terminal corresponds to a synchronization signal block 3, and the antenna panel on the right side of the vehicle body of the first terminal corresponds to a synchronization signal block 4. Therefore, the first terminal sends the synchronization signal block 1 by using the antenna panel on the front bumper, sends the synchronization signal block 2 by using the antenna panel on the rear bumper, sends the synchronization signal block 3 on the antenna panel on the left side of the vehicle body, and sends the synchronization signal block 4 on the antenna panel on the right side of the vehicle body. Optionally, for any one of the N antenna panels, the first terminal sends, by using the antenna panel, a synchronization signal block in a beam scanning manner in a sector covered by the antenna panel. S103. A second terminal receives a plurality of synchronization signal blocks. S104. The second terminal determines a synchronization signal block with the greatest signal strength from the plurality of synchronization signal blocks. Optionally, a signal strength of a synchronization signal block is reference signal received power (RSRP) of a synchronization signal included in the synchronization signal block. The synchronization signal includes a primary synchronization signal and/or a secondary synchronization signal. It may be understood that, in this case, the synchronization signal block with the greatest signal strength is the synchronization signal block including a synchronization signal with the greatest RSRP. In an implementation, for each of the plurality of synchronization signal blocks, the second terminal determines RSRP of a synchronization signal included in the synchronization signal block. Then, the second terminal determines, from the plurality of synchronization signal blocks, the synchronization signal block including the synchronization signal with the greatest RSRP. Currently, a signal strength of a synchronization signal block is not limited to RSRP, and may be another parameter. This is not limited in this embodiment of this application. S105. The second terminal determines, based on the correspondence between the information about the locations of the M antenna panels and the P synchronization signal blocks of the first terminal, information about a location of an antenna panel used by the first terminal to send the synchronization signal block with the greatest signal strength. It may be understood that the second terminal can indirectly determine a relative location relationship between the second terminal and the first terminal by determining the information about the location of the antenna panel used by the first terminal to send the synchronization signal block with the greatest signal strength. The following describes step S105by using an example. In addition, it is assumed that the antenna panel on the front bumper of the first terminal corresponds to the synchronization signal block 1, the antenna panel on the rear bumper of the first terminal corresponds to the synchronization signal block 2, the antenna panel on the left side of the vehicle body of the first terminal corresponds to the synchronization signal block 3, and the antenna panel on the right side of the vehicle body of the first terminal corresponds to the synchronization signal block 4. In an example, as shown inFIG.12, because the second terminal is located behind the first terminal, in the plurality of synchronization signal blocks received by the second terminal, the synchronization signal block 2 is the synchronization signal block with the greatest signal strength. In this way, the second terminal can determine, based on the correspondence between the information about the location of the antenna panel and the synchronization signal block, that the antenna panel that sends the synchronization signal block 2 is the antenna panel on the rear bumper of the first terminal, so that the second terminal can determine that the second terminal is located behind the first terminal. In another example, as shown inFIG.13, because the second terminal is located on the left side of the first terminal, in the plurality of synchronization signal blocks received by the second terminal, the synchronization signal block 3 is the synchronization signal block with the greatest signal strength. In this way, the second terminal can determine, based on the correspondence between the information about the location of the antenna panel and the synchronization signal block, that the antenna panel that sends the synchronization signal block 2 is the antenna panel on the left side of the vehicle body of the first terminal, so that the second terminal can determine that the second terminal is located on the left side of the first terminal. In another example, as shown inFIG.14, because the second terminal is located in front of the first terminal, in the plurality of synchronization signal blocks received by the second terminal, the synchronization signal block 1 is the synchronization signal block with the greatest signal strength. In this way, the second terminal can determine, based on the correspondence between the information about the location of the antenna panel and the synchronization signal block, that the antenna panel that sends the synchronization signal block 1 is the antenna panel on the front bumper of the first terminal, so that the second terminal can determine that the second terminal is located in front of the first terminal. In addition, the foregoing method embodiments are mainly described from a V2V scenario, but it does not indicate that the technical solutions provided in this embodiment of this application are applicable only to the V2V scenario. For example, the technical solutions provided in this embodiment of this application may be further applied to a device-to-device (D2D) scenario. This is not limited in this embodiment of this application. The foregoing mainly describes the solutions provided in the embodiments of this application from a perspective of interaction between the network elements. It may be understood that, to implement the foregoing functions, each network element such as the first terminal or the second terminal includes a corresponding hardware structure and/or software module for implementing each function. A person skilled in the art should easily be aware that, in combination with units and algorithm steps of the examples described in the embodiments disclosed in this specification, this application may be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement a described function for each particular application, but it should not be considered that the implementation goes beyond the scope of this application. FIG.15is a schematic structural diagram of a synchronization signal block sending apparatus according to an embodiment of this application. As shown inFIG.15, the synchronization signal block sending apparatus includes a processing module101and a sending module102. The processing module101is configured to support the synchronization signal block sending apparatus in performing step S101inFIG.2, and/or another process used for the technical solutions described in this specification. The sending module102is configured to support a first terminal in performing step S102inFIG.2, and/or another process used for the technical solutions described in this specification. All related content of the steps in the foregoing method embodiments may be cited in function descriptions of the corresponding functional modules. Details are not described herein again. The synchronization signal block sending apparatus shown inFIG.15may be implemented by using a hardware structure shown inFIG.16. As shown inFIG.16, the synchronization signal block sending apparatus includes a processor201and a communication interface202. The processor201is configured to support the synchronization signal block sending apparatus in performing step S101shown inFIG.2, and/or another process used for the technology described in this specification. The communication interface202is configured to support the synchronization signal block sending apparatus in performing step S102shown inFIG.2, and/or another process used for the technical solutions described in this specification. In addition, the synchronization signal block sending apparatus may further include a memory203and a bus204. The processor201may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Alternatively, the processor may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication interface202is configured to communicate with another device or communication network, such as the Ethernet, a radio access network, or a wireless local area network. The memory203may be a read-only memory or another type of static storage device that can store static information and instructions, or a random access memory or another type of dynamic storage device that can store information and instructions; or may be an electrically erasable programmable read-only memory, a compact disc read-only memory or another compact disc storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, or the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in a form of an instruction or a data structure and that can be accessed by a computer. However, the memory203is not limited thereto. The memory203may exist independently, and be connected to the processor201by using a bus204. Alternatively, the memory203may be integrated with the processor201. The memory203is configured to store a software program for executing the solutions provided in this embodiment of the present invention, and the processor201controls execution of the software program. The bus204may be a peripheral component interconnect bus, an extended industry standard architecture bus, or the like. The bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent the bus inFIG.16, but this does not mean that there is only one bus or only one type of bus. An embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions. When the computer-readable storage medium runs on a first terminal, the first terminal is enabled to perform the method shown inFIG.2. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium, a semiconductor medium (for example, a solid-state drive (SSD)), or the like. In the embodiments of this application, the computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. An embodiment of this application further provides a chip system. The chip system includes a processor, configured to support a first terminal in implementing the method shown inFIG.2. In a possible design, the chip system further includes a memory. The memory is configured to store program instructions and data that are necessary for the first terminal. Certainly, the memory may not exist in the chip system. The chip system may include a chip, or may include a chip and another discrete device. This is not specifically limited in this embodiment of this application. An embodiment of this application further provides a computer program product including computer instructions. When the computer program product runs on a first terminal, the first terminal can perform the method shown inFIG.2. The first terminal, the computer storage medium, the chip system, and the computer program product provided in the embodiments of this application are all configured to perform the synchronization signal block sending and receiving method provided above. Therefore, for beneficial effects that can be achieved by the first terminal, the computer storage medium, the chip system, and the computer program product, refer to beneficial effects corresponding to the methods provided above. Details are not described herein again. FIG.17is a schematic structural diagram of a synchronization signal block receiving apparatus according to an embodiment of this application. As shown inFIG.17, the synchronization signal block receiving apparatus includes a processing module301and a receiving module302. The processing module301is configured to support the synchronization signal block receiving apparatus in performing step S104and S105inFIG.2, and/or another process used for the technical solutions described in this specification. The receiving module302is configured to support the synchronization signal block receiving apparatus in performing step S103inFIG.2, and/or another process used for the technical solutions described in this specification. All related content of the steps in the foregoing method embodiments may be cited in function descriptions of the corresponding functional modules. Details are not described herein again. The synchronization signal block receiving apparatus shown inFIG.17may be implemented by using a hardware structure shown inFIG.18. As shown inFIG.18, the synchronization signal block receiving apparatus includes a processor401and a communication interface402. The processor401is configured to support the synchronization signal block receiving apparatus in performing step S104and S105shown inFIG.2, and/or another process used for the technical solutions described in this specification. The communication interface402is configured to support the synchronization signal block receiving apparatus in performing step S103shown inFIG.2, and/or another process used for the technical solutions described in this specification. In addition, the synchronization signal block receiving apparatus may further include a memory403and a bus404. The processor401may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Alternatively, the processor may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication interface402is configured to communicate with another device or communication network, such as the Ethernet, a radio access network, or a wireless local area network. The memory403may be a read-only memory or another type of static storage device that can store static information and instructions, or a random access memory or another type of dynamic storage device that can store information and instructions; or may be an electrically erasable programmable read-only memory, a compact disc read-only memory or another compact disc storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, or the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in a form of an instruction or a data structure and that can be accessed by a computer. However, the memory403is not limited thereto. The memory403may exist independently, and be connected to the processor401by using a bus404. Alternatively, the memory403may be integrated with the processor401. The memory403is configured to store a software program for executing the solutions provided in this embodiment of the present invention, and the processor401controls execution of the software program. The bus404may be a peripheral component interconnect bus, an extended industry standard architecture bus, or the like. The bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent the bus inFIG.18, but this does not mean that there is only one bus or only one type of bus. An embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions. When the computer-readable storage medium runs on a second terminal, the second terminal is enabled to perform the method shown inFIG.2. An embodiment of this application further provides a chip system. The chip system includes a processor, configured to support a second terminal in implementing the method shown inFIG.2. In a possible design, the chip system further includes a memory. The memory is configured to store program instructions and data that are necessary for the second terminal. Certainly, the memory may not exist in the chip system. The chip system may include a chip, or may include a chip and another discrete device. This is not specifically limited in this embodiment of this application. An embodiment of this application further provides a computer program product including computer instructions. When the computer program product runs on a second terminal, the second terminal can perform the method shown inFIG.2. The second terminal, the computer storage medium, the chip system, and the computer program product provided in the embodiments of this application are all configured to perform the synchronization signal block sending and receiving method provided above. Therefore, for beneficial effects that can be achieved by the first terminal, the computer storage medium, the chip system, and the computer program product, refer to beneficial effects corresponding to the methods provided above. Details are not described herein again. Although this application is described with reference to specific features and the embodiments thereof, it is clear that various modifications and combinations may be made to them without departing from the spirit and scope of this application. Correspondingly, the specification and accompanying drawings are merely example descriptions of this application defined by the appended claims, and are considered as any of or all modifications, variations, combinations or equivalents that cover the scope of this application. It is clear that a person skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. This application is intended to cover these modifications and variations of this application provided that they fall within the scope of protection defined by the following claims and their equivalent technologies. | 40,373 |
11943728 | DETAILED DESCRIPTION OF THE DISCLOSURE One goal of the system or method of the present disclosure is to ensure that nodes (e.g., device #1and device #2) are in synchronization with each other so that data crossing a physical layer is preserved to the greatest extent possible. In a typical communication system, data loss is almost unavoidable, and as such there is a need to reduce data loss as much as possible. In extreme cases where data loss occurs, data will be retransmitted with instructions from the transport layer (see,FIG.1). To maintain the physical layer (e.g., minimize data loss), calibration of the physical layer for the device is required from time to time. This calibration can be done offline in the manufacturing lab or on-line without bringing the physical layer device back to the manufacturer. It is understood that a lot of computing equipment is operating in remote or critical areas such that replacement and calibration in a lab is impossible. The devices used in these fields require on-line calibration (i.e., automatically calibrating a device whenever it is not in use). One embodiment of the system and method of clock synchronization of the present disclosure provides for automatic, on-line calibration of network clocks to reduce the probability of data sampling failure for high speed asynchronous serial interfaces. Alternatively, in one embodiment, a user may start the process during certain period of time when the communication channel is under maintenance. During this period of time, a user can start the calibration and the calibration will run through without any pause because the communication channel is all IDLE traffic. In one embodiment, real time adaptive clock trimming is used to maintain the difference between a receive clock and a transmitter clock to be within an acceptable range so that the probability of data failure will be negligible. In certain embodiments, on-line calibration does not require the communication equipment to be off-line before the calibration can be applied. Referring toFIG.1, a communication network for one embodiment of a system and method of clock synchronization for use in high speed asynchronous serial interfaces according to the principles of the present disclosure is shown. In the diagram, device #1talks to device #2via seven network layers. As used herein, device and node will be used interchangeably. The layers shown inFIG.1include the application layer7,7′; the presentation layer6,6′; the session layer5,5′; the transport layer4,4′; the network layer3,3′; the data link layer2,2′; and the physical layer1,1′. For each layer, a unit of information is exchanged. The units of information are an application protocol data unit (APDU)17, a presentation protocol data unit (PPDU)16, a session protocol data unit (SPDU)15, a transport protocol data unit (TPDU)14, a packet13, a frame12, and a bit11, respectively. Still referring toFIG.1, a message, such as a voice call from device #110, must go to the Application layer7′ of device #120. Virtually, each network layer talks to each other layer between the two nodes (10,20). Ultimately, the processed message sent from device #1is presented to the bottom layer, or physical layer of device #21′. In the physical layer, the two devices are typically connected to each other physically, via cables or the like. Referring toFIG.2AandFIG.2B, a physical layer of a communication network for one embodiment of a system and method of clock synchronization for use in high speed asynchronous serial interfaces according to the principles of the present disclosure is shown. More specifically, a device according to the principles of the present disclosure (device #1FIG.2Aor device #2FIG.2B) is at a bottom layer, or physical layer of the communication system. As used herein, Ingress Traffic comprises Ingress Active Traffic+Ingress Idle Traffic+Ingress Calibration Traffic; Ingress Regular Traffic=Ingress Active Traffic+Ingress Idle Traffic; and Egress Regular Traffic=Egress Active Traffic+Egress Idle Traffic. Still referring toFIG.2A, transmit serial pairs and receive serial pairs communicatively connect device #110inFIG.2Ato device #220inFIG.2B. Egress regular traffic is passed through an 8B10B encoder22to a transmitter24to transmit signals from device #1to device #2(not shown). Ingress regular traffic from device #2(not shown) is received by a receiver36in device #1and is passed through a 8B10B decoder38and onto a traffic splitter40. The traffic splitter40splits the signal into calibration feedback traffic32and ingress active traffic. The feedback traffic, used for calibration, is only from device to device and this feedback, or calibration feedback traffic, is mixed with regular traffic. For both the transmitter and the receiver, if the serial link does not have sufficient bandwidth to handle the calibration traffic in addition to the active traffic, the calibration traffic will be paused until adequate bandwidth is available. In certain embodiments, the 8B10B encoder22encodes all the data traffic, i.e., the active traffic and the idle traffic. The idle traffic, once 8B10B encoded, becomes a stream of K28.5 idle characters. Ideally, the samples of idle character K28.5 have an equal chance to fall into two successive sample periods N and N+1 (see, e.g.,FIG.4). The 8B10B decoder38will decode both the regular traffic and the calibration traffic, and split the calibration traffic32off to the calibration message receiver34. In certain embodiments of the present disclosure, calibration circuitry30comprises a calibration message receiver34and a tunable clock28. One embodiment of the tunable clock has a tunable clock oscillator plus a charge pump. In certain embodiments, the charge pump is an electronic integrator which accumulates voltages resulting from small calibration steps. Referring toFIG.2B, transmit serial pairs and receive serial pairs communicatively connect device #110inFIG.2Ato device #220inFIG.2B. Ingress regular traffic from device #1(not shown) is received by a receiver42of device #2and is passed through a 8B10B decoder44. The ingress regular traffic is passed through a traffic splitter45that splits the signal into ingress idle traffic32and ingress active traffic. In certain embodiments, the self-calibration process starts as long as the number of 8B10B IDLE characters is greater than N. This is detected in the idle character detection block46. This detection block determines when the error check block48should start and when is should end so a starting boundary and an ending boundary for the collection of the K28.5 IDLE characters can be set. This error rate check block48detects the error by sampling the K28.5 IDLE characters and generates a count-up and/or count-down: 1. If the IDLE sample is generated below the “threshold” (i.e., the clock edge), the monitor circuitry will generate a count-down pulse; and 2. If the IDLE sample is generated above the “threshold” (i.e., the clock edge), the monitor circuitry will generate a count-up pulse. These error counters offer an up/down direction for clock adjustment to the clock in device #1to provide for synchronization between the two devices. The counters capture the positive and negative transition of the receive signals. Still referring toFIG.2B, egress regular traffic is passed through an 8B10B encoder56to a transmitter58to transmit signals from device #2to device #1(not shown). As with device #1, for both the transmitter and the receiver, if the serial link does not have sufficient bandwidth to handle the calibration traffic in addition to the active traffic, the calibration traffic will be paused until adequate bandwidth is available. In certain embodiments, it is not necessary to worry about the hysteresis for the counter52, as any errors due to hysteresis will be taken care of over the long run. As used herein, a long run means that the adaptive process will eventually reach the equilibrium state within some number of iterations (i.e., clock cycles). The adaptive process is similar to inventor's previous work on a multi-stage multi-dimensional switch. To reach an equilibrium state some number of iterations are required, because of the nature of the up/down counter operation. Every time the counter is counted up or down once, a relatively very small electric charge to the charge pump is added or subtracted. Eventually, the charge pump will reach a state such that adding or subtracting charge will be fewer and fewer (but may not completely stop). This state is called the equilibrium state. This also means that two successive sample intervals are almost identical. This is also called a nearly uniform probability distribution. At equilibrium state, the calibration voltage will be oscillating about the ideal position with pre-defined voltage range. The number of iterations needed for synchronization is based on how big the initial error is, and how often the error occurs. In some cases, the error is caused by various operation conditions such as environmental changes (temperature, pressure, aging, etc.). In certain embodiments, there is yet another check on the error rate, where if the error rate is zero, the adjustment stops. Time-wise, a clock cycle is defined as the inverse of the clock frequency, which is usually about 250 MHz or above. The clock cycle period is therefore about 4 ns or less. This amount of calibration run time is negligible, when a node/device is in a relatively stable condition. Still referring toFIG.2B, the calibration message generator block54generates a special message to tell device #1what to do. In some cases, the clock adjustment information is sent to the link partner (e.g., device #1in this case), and it extracts the adjustment info and passes it to a tunable phase lock loop (PLL) to provide for the clock in device #1to be adjusted. A PLL is a control system that generates an output signal whose phase is related to the phase of an input signal. A clock is generated by inputting a voltage representing the clock frequency to a voltage controlled oscillator (VCO). In certain embodiments of the system and method of clock synchronization for use in high speed asynchronous serial interfaces, a clock monitor block monitors a local clock to make sure it is within a certain range (e.g., +/−100 ppm). There, the “good” device (e.g., device #2in this example) will be the device to send out adjustment information. Referring toFIG.3, a physical layer of a communication network for one embodiment of a system and method of clock synchronization for use in high speed asynchronous serial interfaces according to the principles of the present disclosure is shown. More specifically, this figure provides additional detail for the calibration step between device #1and device #2shown inFIG.2AandFIG.2B. In device #220, in certain embodiments the self-calibration process starts as long as the number of 8B10B IDLE characters is greater than N, which is detected in the idle character detection block46. This detection block ensures when the error check block48should start and when is should end so a starting boundary and an ending boundary for the collection of the K28.5 IDLE characters can be set. This error check block48detects the error by sampling the K28.5 IDLE characters and generates a count-up and/or count-down signal. The calibration message generator54then sends a message to device #110via the calibration message receiver34containing the count-up or count-down information. In device #110, one embodiment of the tunable clock circuitry has a tunable clock oscillator plus a conventional charge pump. In certain embodiments, the charge pump is an electronic integrator which accumulates voltages resulting from small calibration voltages. The frequency is adjusted via a clock PLL with a charge pump, where a digital signal is provided to the charge pump, the charge pump integrates the digital input, and then outputs the analog signal to the clock PLL. The output is the nominal value+varying delta (increment+decrement) as shown, for example, inFIG.3. When device #1receives the calibration message, the calibration message tunes the frequency of the PLL accordingly to go fast or go slow (up/down). In certain embodiments, the adjusted local clock is used for the transmitter in device #1. In one embodiment, the clock is about 250 MHz and the transmitter and the receiver is in the same chip. It is important though to ensure that 250 MHz clock on both sides are synchronized. In some cases, the period of 250 MHz is divided into four phases. In certain embodiments, the rate of clock adjustment does not have to be the same as that of the operating clock. For example, if the operating clock is running at 250 MHz, the clock adjustment step does not have to be at 250 MHz. The adjustment could be averaged out over a number of samples. In one example, the clock frequency is tuned once every 100 samples. In this case, the tuning only occurs at 2.5 MHz. The noise in the system will then be negligible. This will slow down the convergence to the equilibrium, from possibly microsecond to mini-second, but it is not going to be noticed by the Layer3and above (See,FIG.1) in a real system. Referring toFIG.4A, a conceptual diagram of one embodiment of a trim circuit using a charge pump according to the principles of the system and method of clock synchronization for use in high speed asynchronous serial interfaces of the present disclosure is shown. Referring toFIG.4B, a conceptual diagram of one embodiment of a trim circuit using a charge pump according to the principles of the system and method of clock synchronization for use in high speed asynchronous serial interfaces of the present disclosure is shown. Referring toFIG.4C, a diagram of clock drift across periods according to the principles of the system and method of clock synchronization for use in high speed asynchronous serial interfaces of the present disclosure is shown. More specifically, the system logic samples the IDLE character flow based on the clock edge. In the front end data recovery block of a data receiver, the data sample edge could be either rising edge (clock phase degree 0) or falling edge (clock phase degree 180) or both rising edge (clock phase degree 0) and failing edge (clock phase degree 180) and between rising edge and falling edge (clock phase degree 90 and clock phase degree 270). In one embodiment, the sample will be made at the clock edge N (i.e., every clock edge) also referred to as the threshold. The clock edge keeps drifting for various reasons with respect to the ideal position. Reasons are: aging, temperature change and operation environmental change, or the like. If a sample is generated below the clock threshold, the count DOWN pulse is generated. If a sample is generated above the clock threshold, the count UP pulse is generated. With this approach, one need not worry about the clock hysteresis. Any errors due to the clock hysteresis will be taken care of over the long run. One embodiment of the system and method of clock synchronization for use in high speed asynchronous serial interfaces forces the sample clock edges to be nearly identical or achieve a nearly uniform probability distribution using 8B10B encoding and error check logic, which is, in essence, bin collecting of samples of incoming encoded 8B10B IDLE characters. One embodiment of the system and method of clock synchronization uses a prediction model that allows the system to keep working without interruption during calibration. There are existing adaptive clock estimation and synchronization approaches that use adaptive filtering, but they require a complex mathematical model to predict when the clock should begin the synchronization process. Prior systems with a complex mathematical model require digital signal processing and thus is very difficult implement it in analog circuitry. One embodiment of the present disclosure simplifies the prediction logic and does not require a mathematical model prediction. Instead, the present disclosure uses the DC balance of 8B10B encoding as a prediction model. During the 8B10B transmission, the adaptive filter process is accomplished by adaptively adjusting the frequency for the clock, and drives the statistical properties of the frequency to nearly uniform probability distribution. In certain embodiments of the method and system for clock synchronization for high speed asynchronous serial interfaces of the present disclosure, the closed adaptive filtering system is a stable system. An adaptive filter system is, in essence, a state-space system. The adaptive filter system of the preset disclosure can be analyzed, for example, by a z-transform as illustrated in inventor's previous work on Frequency-Domain Analysis of A/D converter nonlinearity. There, it shows an adaptive filter system is a stable system and is also referred to as a converging system, which iteratively reduces the LMS error and ultimately converges to the ideal position. The system is a first-order low-pass (LP) filter characterized in the Z transfer domain with all the poles located inside the unit circle. The previous work demonstrates that a self-trim algorithm can drive a calibration error to zero (the system can converge to equilibrium), and how quickly. In accordance with the goals of the present disclosure, this approach requires an active, real-time handshake between each node and its “leader” node. Due to the nature of adaptive filtering this interaction could be very slow and irregular. The self-adaptive model of the present disclosure provides that over the long run, the samples that fall into two successive intervals (i.e., “thresholds”) conform to the uniform probability distribution. Based on this model, the relationship between the clock precision and synchronization time is induced and the synchronization process will begin and eventually force the intervals of successive “thresholds” to become equal. In certain embodiments, by operating the system to reduce the error a little bit a time, the system and method ultimately achieves sampling thresholds that are in equilibrium bringing the sampling error for the data to a minimum. Importantly, this approach can also be implemented in the analog domain. Referring toFIG.5A, a flowchart of one embodiment of a method of clock synchronization for use in high speed asynchronous serial interfaces according to the principles of the present disclosure is shown. More specifically, on a first device, receiving ingress traffic from a second device (100) and decoding the ingress traffic using 8B10B (102). Next, the ingress traffic is split into ingress regular traffic and calibration feedback traffic (104). A calibration message receiver (106) processes the calibration feedback traffic. A frequency of a clock is then tuned based on the calibration feedback (108). At least one active message and idle traffic is then encoded on the first device using 8B10B (110) and the encoded at least one active message and idle traffic is transmitted to a second device with an adjusted frequency (112). Referring toFIG.5B, a flowchart of one embodiment of a method of clock synchronization for use in high speed asynchronous serial interfaces according to the principles of the present disclosure is shown. More specifically, on a second device a signal comprising at least one active message and encoded idle traffic is received from a first device (200) and the signal is decoded using 8B10B (202). The signal is the split into ingress regular traffic and ingress idle traffic (204) using a traffic splitter on the second device. The ingress idle traffic is monitored to determine an amount of K28.5 characters (206) and an error check is started if the amount of K28.5 characters is above a threshold value (208). A count-up or count-down signal is generated via an up/down counter (210) and a calibration message comprising calibration feedback traffic from the up/down counter is generated (212). The calibration message is merged with the at least one active message to form a feedback message (214). The feedback message is encoded using 8B10B (216) and transmitted to the first device (218). The steps are repeated for a plurality of sample intervals, thereby reducing a probability of data sampling failure for high speed asynchronous serial interfaces. The computer readable medium as described herein can be a data storage device, or unit such as a magnetic disk, magneto-optical disk, an optical disk, or a flash drive. Further, it will be appreciated that the term “memory” herein is intended to include various types of suitable data storage media, whether permanent or temporary, such as transitory electronic memories, non-transitory computer-readable medium and/or computer-writable medium. It will be appreciated from the above that the disclosure may be implemented as computer software, which may be supplied on a storage medium or via a transmission medium such as a local-area network or a wide-area network, such as the Internet. It is to be further understood that, because some of the constituent system components and method steps depicted in the accompanying figures can be implemented in software, the actual connections between the systems components (or the process steps) may differ depending upon the manner in which the present disclosure is programmed. Given the teachings of the present disclosure provided herein, one of ordinary skill in the related art will be able to contemplate these and similar implementations or configurations of the present disclosure. It is to be understood that the present disclosure can be implemented in various forms of hardware, software, firmware, special purpose processes, or a combination thereof. In one embodiment, the present disclosure can be implemented in software as an application program tangible embodied on a computer readable program storage device. The application program can be uploaded to, and executed by, a machine comprising any suitable architecture. While various embodiments of the present disclosure have been described in detail, it is apparent that various modifications and alterations of those embodiments will occur to and be readily apparent to those skilled in the art. However, it is to be expressly understood that such modifications and alterations are within the scope and spirit of the present disclosure, as set forth in the appended claims. Further, the disclosure(s) described herein is capable of other embodiments and of being practiced or of being carried out in various other related ways. In addition, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” or “having,” and variations thereof herein, is meant to encompass the items listed thereafter and equivalents thereof as well as additional items while only the terms “consisting of” and “consisting only of” are to be construed in a limitative sense. The foregoing description of the embodiments of the present disclosure has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the present disclosure be limited not by this detailed description, but rather by the claims appended hereto. A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the scope of the disclosure. Although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. While the principles of the disclosure have been described herein, it is to be understood by those skilled in the art that this description is made only by way of example and not as a limitation as to the scope of the disclosure. Other embodiments are contemplated within the scope of the present disclosure in addition to the exemplary embodiments shown and described herein. Modifications and substitutions by one of ordinary skill in the art are considered to be within the scope of the present disclosure. | 24,591 |
11943729 | DETAILED DESCRIPTION The following embodiments are only examples. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations, this does not necessarily mean that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Furthermore, words “comprising” and “including” should be understood as not limiting the described embodiments to consist of only those features that have been mentioned and such embodiments may also contain features, structures, units, modules etc. that have not been specifically mentioned. Some embodiments of the present invention are applicable to user equipment, user terminal, a base station, eNodeB, gNodeB, a distributed realisation of a base station, a network element of a communication system, a corresponding component, and/or to any communication system or any combination of different communication systems that support required functionality. The protocols used, the specifications of communication systems, servers and user equipment, especially in wireless communication, develop rapidly. Such development may require extra changes to an embodiment. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate, not to restrict, embodiments. In the following, different exemplifying embodiments will be described using, as an example of an access architecture to which the embodiments may be applied, a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR, 5G), without restricting the embodiments to such an architecture, however. The embodiments may also be applied to other kinds of communications networks having suitable means by adjusting parameters and procedures appropriately. Some examples of other options for suitable systems are the universal mobile telecommunications system (UMTS) radio access network (UTRAN or E-UTRAN), long term evolution (LTE, the same as E-UTRA), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad-hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof. FIG.1depicts examples of simplified system architectures showing some elements and functional entities, all or some being logical units, whose implementation may differ from what is shown. The connections shown inFIG.1are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system typically comprises also other functions and structures than those shown inFIG.1. The embodiments are not, however, restricted to the system given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties. The example ofFIG.1shows a part of an exemplifying radio access network. FIG.1shows devices100and102. The devices100and102may, for example, be user devices or user terminals. The devices100and102are configured to be in a wireless connection on one or more communication channels with a node104. The node104is further connected to a core network106. In one example, the node104may be an access node such as (e/g)NodeB providing or serving devices in a cell. In one example, the node104may be a non-3GPP access node. The physical link from a device to a (e/g)NodeB is called uplink or reverse link and the physical link from the (e/g)NodeB to the device is called downlink or forward link. It should be appreciated that (e/g)NodeBs or their functionalities may be implemented by using any node, host, server or access point etc. entity suitable for such a usage. A communications system typically comprises more than one (e/g)NodeB in which case the (e/g)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signalling purposes. The (e/g)NodeB is a computing device configured to control the radio resources of communication system it is coupled to. The NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment. The (e/g)NodeB includes or is coupled to transceivers. From the transceivers of the (e/g)NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to devices. The antenna unit may comprise a plurality of antennas or antenna elements. The (e/g)NodeB is further connected to the core network106(CN or next generation core NGC). Depending on the system, the counterpart on the CN side can be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of devices (UEs) to external packet data networks, or mobile management entity (MME), etc. The device (also called user device, a subscriber unit, user equipment (UE), user terminal, terminal device, etc.) illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a device may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station. The device typically refers to a device (e.g. a portable or non-portable computing device) that includes wireless mobile communication devices operating with or without an universal subscriber identification module (USIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a device may also be a nearly exclusive uplink device, of which an example is a camera or video camera loading images or video clips to a network. A device may also be a device having capability to operate in Internet of Things (IoT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction, e.g. to be used in smart power grids and connected vehicles. The device may also utilise cloud. In some applications, a device may comprise a user portable device with radio parts (such as a watch, earphones or eyeglasses) and the computation is carried out in the cloud. The device (or in some embodiments a layer 3 relay node) is configured to perform one or more of user equipment functionalities. Various techniques described herein may also be applied to a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected information and communications technology, ICT, devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. Additionally, although the apparatuses have been depicted as single entities, different units, processors and/or memory units (not all shown inFIG.1) may be implemented. 5G enables using multiple input-multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available. 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications (such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real-time control. 5G is expected to have multiple radio interfaces, namely below 6 GHz, cmWave and mmWave, and also being integrable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6 GHz-cmWave, below 6 GHz-cmWave-mmWave). One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility. The current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network. The low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications). The communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet112, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted inFIG.1by “cloud”114). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing. The technology of Edge cloud may be brought into a radio access network (RAN) by utilizing network function virtualization (NVF) and software defined networking (SDN). Using the technology of edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. Application of cloudRAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU104) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU108). It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent. Some other technology advancements probably to be used are Big Data and all-IP, which may change the way networks are being constructed and managed. 5G (or new radio, NR) networks are being designed to support multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well. 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future railway/maritime/aeronautical communications. Satellite communication may utilise geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). At least one satellite110in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node104or by a gNB located on-ground or in a satellite. It is obvious for a person skilled in the art that the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g)NodeBs, the device may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (e/g)NodeBs may be a Home(e/g)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The (e/g)NodeBs ofFIG.1may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of (e/g)NodeBs may be needed to provide such a network structure. For fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs has been introduced. Typically, a network which is able to use “plug-and-play” (e/g)Node Bs, includes, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown inFIG.1). An HNB Gateway (HNB-GW), which is typically installed within an operator's network may aggregate traffic from a large number of HNBs back to a core network. FIG.2illustrates an example of a communication system based on 5G network components. A user terminal or user equipment200communicating via a 5G network202with a data network204. The user equipment200is connected to a base station or gNB206which provides the user equipment a connection to data network204via one or more User Plane Functions208. The user equipment200is further connected to Core Access and Mobility Management Function, AMF210, which is a control plane core connector for (radio) access network and can be seen from this perspective as the 5G version of Mobility Management Entity, MME, in LTE. The 5G network further comprises Session Management Function, SMF212, which is responsible for subscriber sessions, such as session establishment, modify and release and a Policy Control Function214which is configured to govern network behavior by providing policy rules to control plane functions. The network further comprises operations and maintenance unit (O&M)220of the operator of the network. In order to operate, wireless communications synchronous systems need common time reference. Otherwise communication over the radio interface may fail as network elements transmit/receive in erroneous times. This requirement for stabile and accurate time source requires provision of Precision Reference Clock, PRC, such as GNSS time or atomic clocks. This may be costly for network operators, and also creates the risk of single point of failure, which may be related to availability of PRC service. Thus, there is a need for monitoring accuracy of provided Network Time over radio interface even in standalone mode operations for radio access nodes such as eNBs, when PRC was lost. A possibility to correct erroneous timing would be valuable. FIG.3is a flowchart illustrating an embodiment. The flowchart illustrates an example of the operation of the apparatus or network element acting as a user equipment or a part of a user equipment. In step300, the apparatus is configured to store information on a reference propagation delay between the apparatus and one or more radio access nodes. In step302, the apparatus is configured to control reception of a reference signal from one or more radio access nodes, the reference signal comprising information on the transmission time instant of the signal. In step304, the apparatus is configured to determine the reception time instant of the reference signal. In step306, the apparatus is configured to determine the propagation delay of the reference signal based on the time difference of the reception time instant and the transmission time instant. In step308, the apparatus is configured to determine correctness of time references of the apparatus and the one or more radio access nodes based on the determined and stored propagation delays. In an embodiment, if the determined and stored propagation delays related to more than one radio access nodes are unequal, the apparatus may be configured to determine that the time reference of the apparatus is incorrect. In an embodiment, if the determined and stored propagation delay related to a first radio access node is unequal and the determined and stored propagation delay related to a second radio access nodes is equal with a given margin, the apparatus may be configured to determine that the time reference of the first radio access node is incorrect. In an embodiment, determine correction for the incorrect time reference. In an embodiment, the apparatus may be configured to control transmission of an indication to the first radio access node, the indication comprising information on the correction for the incorrect time reference. In an embodiment, the apparatus may be configured to correct the time reference of the apparatus based on the determined correction. FIG.4is a flowchart illustrating an embodiment. The flowchart illustrates an example of the operation of the apparatus or network element acting as a radio access node or a part of a radio access node. In step400, the apparatus is configured to control transmission of a reference signal to a user equipment, the reference signal comprising information on the transmission time instant of the signal. In step402, the apparatus is configured to control reception of an indication from the user equipment, the indication comprising information on the correction for the time reference of the apparatus. In step404, the apparatus is configured to correct the time reference of the apparatus based on the indication. In an embodiment, a user equipment may be utilised to monitor the timing of radio access nodes and timing of the user equipment itself. The method described above thus assures that time alignment within the network monitored by user equipment is stable, even if radio access nodes operated in a standalone mode, without PRC for unlimited time. FIGS.5A and5Billustrate an example. The figure shows a user equipment500. The user equipment500, which may be denoted as Reference User Terminal, Ref UT, or Reference User Equipment, Ref UE, may be an Internet of Things, lot device or wideband UE. It may be in the coverage area of a number of cells from different radio access nodes, for example eNBs. In the example ofFIG.5A, the Ref UE500is shown to be in the coverage area of two access nodes502,504, for simplicity. In an embodiment, the Ref UE may be stationery, for example mounted on a mast or any other suitable facility. In an embodiment, the location of the Ref UE may enable line of sight visibility to radio access nodes within the coverage of Ref UE. It may be possible to measure a line of sight distance between Ref UE and eNBs within the coverage and then convert this distance to time equivalent as microwaves utilises on the radio interface travel at speed of light. In an embodiment, radio access nodes may be configured to transmit or broadcast a Reference Signal, which comprises information about the physical signal transmission time T0. The time T0uses as a time reference the internal clock of the access node. Let us assume here that eNB1502transmitted the reference signal. The transmission time may be denoted as T0(e1). The reference signal may be any selected frame, subframe or symbol. Reference signal transmitted by a radio access node may be received by the Ref UE at time T1. Time T1uses as a reference the internal clock of the Ref UE. The reception time may be denoted as T1(ue). Thus, a Time Of Arrival, TOA, time difference T1−T0may correspond to signal propagation delay but two different reference time sources are used—access node and Ref UE. As synchronous transmission is used, time relation between many measurements may be compared. Using above notation, the time difference of reference signal transmitted by eNB1502may be denoted as Tprop(eNB1, Te1, Tue). As mentioned above, the Ref UE may be configured to store information on a reference propagation delay between the apparatus and one or more radio access nodes. The reference propagation delay506between user equipment500and access node eNB1502may be denoted as Tref(eNB1) and reference propagation delay510between user equipment500and access node eNB2504may be denoted as Tref(eNB2). The determined TOA propagation delay between Ref UE and an access node may be compared with reference propagation delay for the same access node. Any deviation in TOA measurement may indicate that time reference source at the access node or Ref UE side drifted in time. By analysing TOA measurements to other access nodes, the Ref UE may determine whether reference clock drift is present at the access node or Ref UE side. In an embodiment, Ref UE may propose a time compensation to access node or Ref UE accordingly. The Ref UE may determine the source of time drift and may provide time correction to eNB or to Ref UE internal reference clock. This way a bottom-up time synchronization may be provided, which differ with respect to legacy top-down approach for time synchronization. In the example ofFIGS.5A and5B, the reference propagation delay506between user equipment500and access node eNB1502Tref(eNB1) and reference propagation delay510between user equipment500and access node eNB2504Tref(eNB2) have been determined at some earlier point of time. For example, the distance between the user equipment Ref UE and access node eNB1502and access node eNB2504may be measured, for example utilising a laser range finder with the accuracy of millimetres. The propagation time is proportional to the distance. For example, for access node eNB1, following applies: Tref(eNB1)=Dref(eNB1)c,(Eq.1) where Tref(eNB1) is reference signal propagation delay to eNB1 based on distance measurement, c is the speed of light and Dref(eNB1) is measured reference distance between Ref UE and eNB1. The access node eNB1502transmits a reference signal508to the user equipment500at a time T0and the user equipment receives the signal at a time T1. Respectively, the access node eNB2504transmits a reference signal512to the user equipment500at a time T3and the user equipment receives the signal at a time T4. Using the above method, it is possible to determine corresponding TOA rings, with radius514,516, proportional to TOA propagation delay. The equation to determine reference signal propagation delay, using eNB1 as an example, is as follows: Tprop(eNB1,Te1,Tue)=T1(Tue)−T0(Te1), (Eq. 2) where Tprop(eNB1, Te1, Tue) is the reference signal propagation delay, which is a function of distance between Ref UE and eNB1, and reference clocks of eNB1 and Ref UE, T1(Tue) is time of physical reference signal reception by Ref UE, which depends on Ref UE clock and T0(Te1) is time of physical reference signal transmission by eNB1, which depends on eNB1 clock. In the example ofFIG.5A, the reference clocks of Ref UE, eNB1 and eNB2 are in correct time. Thus, following conditions of equations 3 and 4 are met (using again eNB1 as an example): Tprop(eNB1,Te1,Tue)=Tref(eNB1),(Eq.3)T1(Tue)-T0(Te1)=Dref(eNB1)c,(Eq.4) If the above equations match, then there is no error in the reference clocks. It may be that the both the access point eNB and Ref UE are synchronized with precise reference clock PRC, which may be defined as a function Tue(Te1(T)), what is a typical situation for mobile network operations. Typically, the access point provides synchronisation for the user equipment. Thus, in a normal situation the reference time in user equipment is a function of the reference time of the user equipment, which in turn is a function of the reference time of the access point. Based on equations 3 and 4, it may be possible to determine whether reference times Tueor Te1are correct as relative TOA propagation delay needs to be substantially equal reference delay determined by accurate distance measurement equipment. If equations 3 and 4 are fulfilled, the time references of access point and Ref UE are in order. If the equations do not match, there is an error in either the reference time of access point of the Ref UE. Further, if one of the equations does not match, by analysing equations Eq. 3 and Eq. 4 for more than one access point, it may be possible to determine whether instability of reference time source is related to an access point of for whether there is a common point of failure—Ref UE. If there is an error regarding one access point but other access point equations match, the respective access point may have erroneous timing in its reference clock. If more than one access point equations indicate error, the faulty timing is in the Ref UE. In an embodiment, a given error tolerance may be applied when determining the correctness of equations 3 and 4. FIGS.5A and5Billustrate a situation where propagation delays of reference signal transmissions of both eNB1 and eNB2 are substantially equal to the respective reference signal propagation delays.FIGS.6A and6Bin turn illustrate an example, where the access point eNB1502lost synchronization with PRC for a period of time. It means that eNB1 needs to rely on own internal clock to maintain clock synchronization. In this case, time relation may be denoted as Tue(Te1(Te1)). In the example ofFIGS.6A and6Bthis lack of PRC has led to instability of the clock of the eNB1. FIGS.6A and6Billustrate an example where TOA propagation delay distance between Ref UE and eNB1 is not substantially equal to the reference delay to eNB1, and conditions defined by equations 3 and 4 are not met. Propagation delay T1(Tue)−T0(Te1) is greater than reference delay Tref(eNB1): T1(Tue)−T0(Te1)>Tref(eNB1). As neither eNB1 and Ref UE position is not changed, the reason for TOA error may be reference time source drift at either eNB1 or Ref UE. This is the option as speed of microwave is constant. At this moment, based on one TOA measurement to one eNB, it may not be possible to determine whether problem lies in Ref UE reference time source, Tue, or in eNB1 reference time source, Te1. Ref UE may unambiguously indicate the source of time drift by analysing further pairs of eNBs-Ref UE and associated TOA measurements. In the example ofFIGS.6A and6B, TOA measurement to eNB2 fulfils conditions in equations 3 and 4: T4(Tue)−T3(Te2)=Tref(eNB2). This indicates that Ref UE reference time source Tue, and eNB2 reference time source Te2have the common reference clock with the given tolerance. As for TOA measurement with eNB1 the same Ref UE clock Tueis used, it can be determined that the problem is associated with eNB1 internal clock Te1, as it affects time determined by T0(Te1). In the example ofFIGS.6A and6B, the error causes too long propagation delay. Similar scenario may be when particular TOA propagation delay is shorter than corresponding reference delay, i.e. where Propagation delay T1(Tue)−T0(Te1) is shorter than reference delay Tref(eNB1). FIGS.7A and7Billustrate another example. In this example, neither the reference signal transmitted by eNB1 nor the reference signal transmitted by eNB2 satisfy the equation 3: T1(Tue)−T0(Te1)>Tref(eNB1), T4(Tue)−T3(Te2)>Tref(eNB2). This kind of situation may occur when, due to any reason, the Ref UE500has lost synchronization, for example. The wrong reference time at Ref UE may cause incorrect TOA measurements as Tueaffects time determined by T1(Tue) and T4(Tue). As Tueis common for TOA measurements, any TOA propagation measurement may be incorrect. It may be noted currently user equipment needs to periodically synchronize with a radio access node, which procedure requires a Random Access procedure and consumes radio resources. Similar scenario as inFIGS.7A and7Bmay also be when any TOA propagation delay is shorter than any related reference delay. It may be noted that a typical time drift is a continuous and gradual process, which with respect to Ref UE sampling period may be enough for time drift modelling. A parameter for allowed time drift, e.g. Tdrift1Maxfor eNB1 may be determined in order to specify whether any correction action from Ref UE is needed. An intersection area for TOA measurements with different current Tdrift1indications may be used for further assessment of reference time stability and may also trigger optimum corrective action. In an embodiment, the Ref UE500may be calibrated prior usage. In LTE, a basic time unit Ts=0.0325 microsecond is used, as it is sampling time of an OFDM symbol. This Ts=0.0325 microsecond creates a granularity (accuracy) of 4,875 m in distance, which is poor accuracy with respect to values of Tref, which may be determined with an accuracy of nanoseconds. FIG.8illustrates an example of an activity diagram for a Ref UE calibration process for three eNBs. However, a similar process applies for any number of eNBs. At the step800, “PRC: Precise Reference Clock”, a time from a precise reference clock T is provided to eNB1, which may be common for eNBs. It may be assumed that this requirement may be fulfilled during calibration. At the step802“eNB1: Synchronize internal clock”, the eNB1 internal clock may be synchronized with PRC. Thus, the eNB1 internal clock Te1is a function of T, i.e. Te1(T). If PRC is available for eNBs, the substantially same time is used within entire mobile network: Te1(T)=Te2(T) (Eq. 5) Without synchronisation with PRC, time Te1needs to rely on stability of its own crystal oscillator (or other means), in which case Te1time value may be expressed as Te1(Te1) and relation equation 5 may not be true. At the step804, “eNB1: Send TOA Reference Symbol”, the eNB1 broadcasts or transmits a reference symbol, which comprise information about the physical reference symbol transmission time. In an embodiment, it may be the transmission time from the eNB1 antenna system. In this case, T0(Te1) may be provided in a form of HH:MM:SS:MS:US:NS and due to latching process, T0depends on quality of Te1. As T0(Te1) represents the physical transmission time, an eNB1 processing and eNB1 specific transmission delay may need to be compensated. At the next step806, “Ref UE: Synchronize internal clock with eNB1”, the Ref UE may perform a random access procedure in order to receive network time. This way, the Ref UE may synchronize its own internal clock Tuewith the connected eNB1, which means initially a function Tue(Te1). Any inaccuracies in Te1may affect Tue. This step is for calibration. Also, Ref UE time drift may be expected, so after some period synchronisation may be lost: Tue(Tue)=Tue(Te1) (Eq. 6) If PRC is available for Ref UE, Ref UE time may be a function of time T as specified in equation 7, which may be considered as typical case. Tuetime drift may be regularly compensated when Ref UE synchronize with the network. Tue(Tue)=Tue(Te1)=Tue(Te1(T)) (Eq. 7) At the step808, “Ref UE: Receive TOA Reference Symbol from eNB1”, the Ref UE may receive the reference symbol and latch time of its reception T1with respect to own time reference source Tue, which means it is a function T1(Tue). Ref UE may take into consideration Ref UE processing and transmission delay. At the step810, “Ref UE: Measure TOA Propagation Delay to eNB1”, the Ref UE measures TOA signal propagation delay to eNB1 using T0and T1values. Signal propagation delay Tprop1(eNB1, Te1, Tue) is determined by equation 2 but is measured with granularity of basic time unit Ts. In step812, “Ref UE: Reference Delay (Distance) to eNB1”, reference delays for eNBs may be determined as specified by equation 1. The step814, “Ref UE: Calibration Ref UE TOA Propagation Delay (Distance) for eNB1” describes a process of fine tuning TOA accuracy improvement. A TOA related correction factor eNB1corr is determined. This correction factor may be added to TOA propagation delay measurements for the given eNB. This may be explained on the following numerical example with exemplary data also illustrated inFIG.9. The non-limiting numerical values are merely an illustrative example. Ref UE is in this example fully synchronized with the network time, i.e. Tue(Tue)=Tue(Te1); this assures that any initial time drift is compensated. Transmission time of reference signal T0(Te1) is HH:MM:SS:MS:US:NS=00:00:00:00:00:00. In this example, Ref UE is at a distance Dref1(eNB1)=10000 m from the eNB antenna system900, which corresponds to 33,356 microseconds for microwave signal propagation and to Tref1(eNB1)=102.64 Ts; 00:00:00:00:33:36. Ref UE may latch information about T1(Tue) with Tsresolution902, which means T1(Tue)=103 Ts. There may be an error related to T1(Tue) granularity, which may be equal −0.36 Ts, which may be denoted as eNB1corr. In the next step eNB1corr=−0.36 Tsmay be added to Tue(Tue) for reference to eNB1, which in this case may be denoted as Tue1(Tue): Tue1(Tue)=Tue(Tue)−eNB1corr (Eq. 8) Based on equation 8, any following TOA measurement regarding eNB1 may be compensated by eNB1corr. In the result, Tsboundary is aligned with real propagation delay determined by Tref1(eNB1). A slight difference in the accuracy of time reference in T1(Tue) may be then signaled by change of indicated Ts, which may be 103 Ts(if on the left side ofFIG.9) or 104 Ts(if on the right ofFIG.9); Further, additional accuracy of TOA measurement may be achieved by the usage of quadrature time references Tue1I(Tue)904and Tue1Q(Tue)906, shifted by 0.5 Ts; as it may be seen, for Tue1I(Tue) reference symbol may be latched at T1(Tue)=104 Ts, whereas for Tue1Q(Tue) at T1(Tue)=103 Ts; In the result, T1(Tue) event may be allocated with accuracy of ¼ Ts, which may be four times better with respect to regular TOA measurement, for example. By adding eNB1corr to time reference at Ref UE side, it may be possible to detect any changes in TOA measurements, which means higher TOA precision. In an embodiment, correction eNB1corr is static. Other corrections factors may be determined for any other eNBs. Moving back toFIG.8, at the step816, “Ref UE: Measure reference clock drift for eNB1”, Ref UE measures stability of Tdrift1(Te1, Tue1). By usage of Tue1I(Tue) and Tue1Q(Tue) (or more shifted reference clocks for TOA measurements), TOA accuracy may be enhanced. In this case, it may be detected a time shift of 8,125 ns, which may be sufficient for mobile network time monitoring and verification. This may be also denoted as Tdrift1Maxvalue, which may be used as a trigger if measured TOA delay exceeds this limit with respect to Tref1(eNB1). In an embodiment, higher TOA precision may be also possible by usage of more Tsshifts as a time reference at Ref UE, which is not technically complicated as T1latching process needs to be multiplied for shifted reference times such as: Tue1I(Tue)=Tue1(Tue), (Eq. 9A) Tue1Q(Tue)=Tue1(Tue)+½Ts(Eq. 9B) In an embodiment, once Ref UE is calibrated, any changes in TOA propagation delay may be caused by instabilities related to Ref UE Tuefor T1(Tue), or to eNB1 Te1for T0(Te1). In an embodiment, instabilities at eNB1 Te1(Te1) may have impact on TOA measurement related to eNB1. In an embodiment, instabilities at Ref UE Tue(Tue) may have impact on any TOA measurement performed by Ref UE with respect to any other eNB, as time floor Tue(Tue) may be common and any added corrections are static, such as equation 8. In normal mobile network operations where PRC is available, time reference at eNBs are within tolerances, which also means that Ref UE (or any UE) connected to the network may have accurate and precise time. The timing of UEs may be periodically resynchronised to cover any instabilities at UE reference time source. However, if PRC is not available to some eNB, the resynchronisation mechanism may give wrong results. Finally, in step818, Ref UE TOA measurements may be calibrated with any eNBs in the coverage. Parameter Tdrift1Maxfor eNB1 may determine accuracy and may be used as a trigger, if exceeded, for Tueor Te1time corrections. As explained, higher precision may be achieved if quadrature or similar technique is used, see equations 9A and 9B. FIG.10illustrates an example of an activity diagram for a calibrated Ref UE500. In this example, eNB1 may have lost synchronisation with PRC. However, PRC may be still available for eNB2 and eNBX. ENB1 operation is based on its own internal clock. In an embodiment, Ref UE may detect any reference time drift once TOA measurement utilising a reference signal transmitted by eNB1 exceeds the given threshold level, such as Tdrift1Max. It may be that although an access node has lost synchronisation, the internal clock of the node may still keep time accurately enough, at least for a period of time. In the example ofFIG.10, time drift of ENB1 may still be within limits although it lost synchronization with PRC. Ref UE may determine that TOA measurements from eNBs are correct, which means conditions in equation 3 and 4 are true for eNBs. No further action is needed from Ref UE. This state may correspond to scenario shown inFIGS.5A and5B. With respect toFIG.10, after the given period of time, the internal clock of eNB1 may drift beyond TOA defined Tdrift1Maxthreshold. In such a case, Ref UE may detect this state as illustrated inFIG.11by NOK state from step1100for eNB1. This may correspond to scenario shown inFIGS.6A and6B. In order to determine the source of problem, Ref UE may measure TOA propagation delays to other eNBs in the vicinity, which may be eNB2 and eNBX. These additional TOA measurements are in this example correct, as indicated by OK state from steps1102and1104. This confirms to Ref UE that the problem is related to Te1drift of eNB1. The reference time at Ref UE, Tue, is correct because Tueis common for eNBs (eNB1corr is a static shift). In an embodiment, eNB1 Te1time drift may be assessed to be substantially equal to Tdrift1Max, or in general Tdrift1, if better accuracy is needed. A change may be positive or negative, which may be denoted as +/−Tdrift1. In an embodiment, when Ref UE has determined that the eNB1 internal clock Te1needs to be adjusted, it may perform actions as illustrated onFIG.12. InFIG.12, at the step1200, “Ref UE: Required Time Correction to eNB1”, Ref UE determines that time correction for eNB1 may be needed by +/−Tdrift1, which may be exact value, if precise reference time floor is available as explained earlier, or Tdrift1Max. Ref UE requests an RRC Connection to eNB1. Then, at the step1202, “Ref UE: Send eNB Time Correction”, Ref UE may report to eNB1 that eNB1 internal clock needs to be adjusted by +/−Tdrift1, which means that Te1time should be changed to Te1+/−Tdrift1. At the step1204, “eNB1: Resynchronize internal clock”, eNB1 is configured to adjust the internal clock of eNB1 to Te1+/−Tdrift1. This also affects any UE connected to this eNB. Thus, any other UE will receive corrected time per legacy synchronization mechanism, even if the given eNB operate without connection with PRC. At the step1206, “Ref UE: Resynchronize internal clock”, Ref UE, which is in RRC Connected state, also adjust its internal clock Tue(Te1+/−Tdrift1), which means both eNB1 and Ref UE will have common reference clock for TOA measurements. In step1208, eNB1 sends a reference signal at time instant T0. Ref UE receives signal at step1210as time instant T1, as described earlier. These transmissions occur during updated internal clocks of eNB1 and Ref UE. For Ref UE, it means that TOA measurement to eNB1 is correct again. Ref UE is configured to continuously measure also other TOA measurements to verify whether other measurements are still correct, which confirms that problem was solved by Te1time adjustment. If other TOA measurements are ok, problem is solved, and no further actions are needed. Synchronization is restored. If PRC is not available for larger number of eNBs or not present at all, Ref UE may determine time drift in more than one eNB, as illustrated onFIG.13, where two NOK states1300,1302may be received. This scenario also applies for instability of Ref UE internal clock, Tue. This condition may be signalled by more than one TOA measurement errors, which is different condition if one eNB is affected. In this case, Ref UE may determine which TOA measurements are incorrect and assess errors by Tdrift1Maxor Tdrift1values respectively for eNBs. Then, Ref UE may determine time correction for Tue, which may be as illustrated by equation 10: min(Tdrift1,Tdrift2), (Eq. 10) where Tdrift1, Tdrift2are values for different eNBs. Proposed solution ensures that changes are implemented in smaller increments, which improves management of such changes. It may be noted, that a change in Tuealso affects other TOA measurements.FIG.14illustrates an example how a change to reference time at Ref UE, (equation 10), may be implemented. Ref UE may stay in RRC Idle state, or if it is already in RRC Connected state, changes may be applied to received time value, so current time value may have no impact on these changes. After implementation of changes in Ref UE internal clock reference time, Ref UE may be configured to repeat TOA measurements until TOA measurements are similar to these from calibration. In an embodiment, in more complicated scenarios, corrections may be proposed both to any eNB and to Ref UE until results are correct again. Thus, as illustrated in the above example, Ref UE may be able to distinguish whether reference time source needs to be corrected at eNB or Ref UE, which is useful if mobile network needs to operate without access to PRC due to any reason. This may be the case when the network utilises satellite-based synchronization and when the performance of the satellite-based synchronization is affected by natural phenomena such as solar flare or is jammed, or such system is not available. As illustrated, the proposed solution does not require sophisticated and costly equipment with respect to PRC in the form of atomic clock, for example. Ref UE may be IoT/LTE-M or Wideband UE and still its performance may be sufficient for maintaining operation. FIG.15illustrates an embodiment. The figure illustrates a simplified example of an apparatus or network entity applying embodiments of the invention. In some embodiments, the apparatus may be a user equipment such as Ref UE500or a part of Ref UE. It should be understood that the apparatus is depicted herein as an example illustrating some embodiments. It is apparent to a person skilled in the art that the apparatus may also comprise other functions and/or structures and not all described functions and structures are required. Although the apparatus has been depicted as one entity, different modules and memory may be implemented in one or more physical or logical entities. The apparatus500of the example includes a control circuitry1500configured to control at least part of the operation of the apparatus. The apparatus may comprise a memory1502for storing data. Furthermore, the memory may store software1504executable by the control circuitry1500. The memory may be integrated in the control circuitry. The apparatus further comprises one or more interface circuitries1506configured to connect the apparatus to other devices and network elements or entities of the radio access network, such as access nodes or eNBs. In an embodiment, the software1504may comprise a computer program comprising program code means adapted to cause the control circuitry1500of the apparatus to realise at least some of the embodiments described above. FIG.16illustrates an embodiment. The figure illustrates a simplified example of an apparatus or network entity applying embodiments of the invention. In some embodiments, the apparatus may be a network element or network entity acting as a radio access node or eNB502, or a part of a radio access node or eNB. It should be understood that the apparatus is depicted herein as an example illustrating some embodiments. It is apparent to a person skilled in the art that the apparatus may also comprise other functions and/or structures and not all described functions and structures are required. Although the apparatus has been depicted as one entity, different modules and memory may be implemented in one or more physical or logical entities. The apparatus502of the example includes a control circuitry1600configured to control at least part of the operation of the apparatus. The apparatus may comprise a memory1602for storing data. Furthermore, the memory may store software1604executable by the control circuitry1600. The memory may be integrated in the control circuitry. The apparatus further comprises one or more interface circuitries1606,1608, configured to connect the apparatus to other devices and network elements or entities of the radio access network, such as core network and user terminals. The interfaces may provide wired or wireless connections. In an embodiment, the software1604may comprise a computer program comprising program code means adapted to cause the control circuitry1600of the apparatus to realise at least some of the embodiments described above. The steps and related functions described in the above and attached figures are in no absolute chronological order, and some of the steps may be performed simultaneously or in an order differing from the given one. Other functions can also be executed between the steps or within the steps. Some of the steps can also be left out or replaced with a corresponding step. The apparatuses or controllers able to perform the above-described steps may be implemented as an electronic digital computer, processing system or a circuitry which may comprise a working memory (random access memory, RAM), a central processing unit (CPU), and a system clock. The CPU may comprise a set of registers, an arithmetic logic unit, and a controller. The processing system, controller or the circuitry is controlled by a sequence of program instructions transferred to the CPU from the RAM. The controller may contain a number of microinstructions for basic operations. The implementation of microinstructions may vary depending on the CPU design. The program instructions may be coded by a programming language, which may be a high-level programming language, such as C, Java, etc., or a low-level programming language, such as a machine language, or an assembler. The electronic digital computer may also have an operating system, which may provide system services to a computer program written with the program instructions. As used in this application, the term ‘circuitry’ refers to all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and software (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term in this application. As a further example, as used in this application, the term ‘circuitry’ would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and/or firmware. The term ‘circuitry’ would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device. An embodiment provides a computer program embodied on a distribution medium, comprising program instructions which, when loaded into an electronic apparatus, are configured to control the apparatus to execute the embodiments described above. The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, and a software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The apparatus may also be implemented as one or more integrated circuits, such as application-specific integrated circuits ASIC. Other hardware embodiments are also feasible, such as a circuit built of separate logic components. A hybrid of these different implementations is also feasible. When selecting the method of implementation, a person skilled in the art will consider the requirements set for the size and power consumption of the apparatus, the necessary processing capacity, production costs, and production volumes, for example. In an embodiment, an apparatus comprises at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: store information on a reference propagation delay between the apparatus and one or more radio access nodes; control reception of a reference signal from one or more radio access nodes, the reference signal comprising information on the transmission time instant of the signal; determine the reception time instant of the reference signal; determine the propagation delay of the reference signal based on the time difference of the reception time instant and the transmission time instant; determine correctness of time references of the apparatus and the one or more radio access nodes based on the determined and stored propagation delays. In an embodiment, an apparatus comprises at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: control transmission of a reference signal to user equipment, the reference signal comprising information on the transmission time instant of the signal; control reception of an indication from the user equipment, the indication comprising information on the correction for the time reference of the apparatus; and correct the time reference of the apparatus based on the indication. In an embodiment, a non-transitory computer readable medium comprises program instructions for causing an apparatus to perform at least the following: storing information on a reference propagation delay between the apparatus and one or more radio access nodes; controlling reception of a reference signal from one or more radio access nodes, the reference signal comprising information on the transmission time instant of the signal; determining the reception time instant of the reference signal; determining the propagation delay of the reference signal based on the time difference of the reception time instant and the transmission time instant; and determining correctness of time references of the apparatus and the one or more radio access nodes based on the determined and stored propagation delays. In an embodiment, a non-transitory computer readable medium comprises program instructions for causing an apparatus to perform at least the following: controlling transmission of a reference signal to a user terminal, the reference signal comprising information on the transmission time instant of the signal; controlling reception of an indication from the user equipment, the indication comprising information on the correction for the time reference of the apparatus; and correcting the time reference of the apparatus based on the indication. It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The invention and its embodiments are not limited to the examples described above but may vary within the scope of the claims. | 54,403 |
11943730 | DETAILED DESCRIPTION The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts. While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution. Physical downlink control channels (PDCCHs) carry downlink control information (DCI) that is needed for proper assignment and decoding of data channels, such as a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH). A base station may transmit a PDCCH to a user equipment (UE), such that the UE may decode the PDCCH and schedule a downlink data in a PDSCH or an uplink data in a PUSCH. The UE may decode the PDCCH by blind decoding attempts on search spaces configured by the base station. The base station may configure a time delay (e.g., K0) between a communication of the PDCCH and a scheduled downlink of a corresponding downlink data in a PDSCH, and/or a time delay (e.g., K2) between a communication of the PDCCH and a scheduled uplink of a corresponding downlink data in a PUSCH, per bandwidth part (BWP). The base station may configure a minimum time delay (e.g., K0min) between a communication of the PDCCH and a scheduled downlink of a corresponding downlink data in a PDSCH, and/or a minimum time delay (e.g., K2min) between a communication of the PDCCH and a scheduled uplink of a corresponding downlink data in a PUSCH, per BWP. Each BWP may include multiple search spaces where the PDCCH may possibly decoded. However, configuring such a time delay for the PDSCH or PUSCH per BWP may not be desirable, especially for higher frequencies and larger subcarrier spacings that cause less available time for decoding and processing a PDCCH. Hence, more flexibility in configuring a time delay may be advantageous. According to some aspects of the disclosure, a time delay may be configured per search space, instead of configuring the time delay per BWP. For example, the base station may configure a time delay (e.g., K0) between a communication of the PDCCH and a scheduled downlink of a corresponding downlink data in a PDSCH, and/or a time delay (e.g., K2) between a communication of the PDCCH and a scheduled uplink of a corresponding downlink data in a PUSCH, per search space. In some examples, the base station may also configure a minimum time delay (e.g., K0min) between a communication of the PDCCH and a scheduled downlink of a corresponding downlink data in a PDSCH, and/or a minimum time delay (e.g., K2min) between a communication of the PDCCH and a scheduled uplink of a corresponding downlink data in a PUSCH, per search space. As such, by configuring a time delay per search space, a different time delay may be configured for a different search space, and thus different time delays may be configured for different search spaces within a BWP. On the other hand, configuring the time delay per BWP results configuring the same time delay for all search spaces within the BWP. Hence, configuring a time delay per search space provides more flexibility than configuring a time delay per BWP. The various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards. Referring now toFIG.1, as an illustrative example without limitation, various aspects of the present disclosure are illustrated with reference to a wireless communication system100. The wireless communication system100includes three interacting domains: a core network102, a radio access network (RAN)104, and a user equipment (UE)106. By virtue of the wireless communication system100, the UE106may be enabled to carry out data communication with an external data network110, such as (but not limited to) the Internet. The RAN104may implement any suitable wireless communication technology or technologies to provide radio access to the UE106. As one example, the RAN104may operate according to 3rdGeneration Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G. As another example, the RAN104may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. The 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure. As illustrated, the RAN104includes a plurality of base stations108. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE106. In different technologies, standards, or contexts, a base station may variously be referred to by those skilled in the art as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology. The RAN104is further illustrated supporting wireless communication for multiple mobile apparatuses. A mobile apparatus may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be an apparatus (e.g., a mobile apparatus) that provides a user with access to network services. Within the present document, a “mobile” apparatus need not necessarily have a capability to move and may be stationary. The term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies. UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, antenna array modules, radio frequency (RF) chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of a mobile apparatus include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC), a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA), and a broad array of embedded systems, e.g., corresponding to an “Internet of things” (IoT). A mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, etc. A mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc. A mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid), lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc. Still further, a mobile apparatus may provide for connected medicine or telemedicine support, e.g., health care at a distance. Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data. Wireless communication between a RAN104and a UE106may be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station108) to one or more UEs (e.g., UE106) may be referred to as downlink (DL) transmission. In accordance with certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station108). Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE106) to a base station (e.g., base station108) may be referred to as uplink (UL) transmissions. In accordance with further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE106). In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs106, which may be scheduled entities, may utilize resources allocated by the scheduling entity108. A UE106that may operate as an unscheduled and/or a scheduled entity may be referred to as a scheduled entity106herein. Base stations, represented in both the singular and the plural by scheduling entity108, are not the only entities that may function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). As illustrated inFIG.1, a scheduling entity108may broadcast downlink traffic112to one or more scheduled entities106). Broadly, the scheduling entity108is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic112and, in some examples, uplink traffic116from one or more scheduled entities106to the scheduling entity108. On the other hand, the scheduled entity106is a node or device that receives downlink control information114(DCI), including but not limited to scheduling information (e.g., a grant), synchronization or timing information, or other control information from another entity in the wireless communication network such as the scheduling entity108. In addition, the uplink and/or downlink control information and/or traffic information may be time-divided into frames, subframes, slots, and/or symbols. As used herein, a symbol may refer to a unit of time that, in an orthogonal frequency division multiplexed (OFDM) waveform, carries one resource element (RE) per sub-carrier. A slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and various time divisions of the waveform may have any suitable duration. In general, scheduling entities, as graphically represented in the singular and plural by scheduling entity108, may include a backhaul interface for communication with a backhaul portion120of the wireless communication system100. The backhaul portion120may provide a link between a scheduling entity108and the core network102. Further, in some examples, a backhaul network may provide interconnection between the respective base stations (each similar to scheduling entity108). Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network. The core network102may be a part of the wireless communication system100and may be independent of the radio access technology used in the RAN104. In some examples, the core network102may be configured according to 5G standards (e.g., 5GC). In other examples, the core network102may be configured according to a 4G evolved packet core (EPC), or any other suitable standard or configuration. FIG.2is a schematic illustration of an example of a radio access network (RAN)200according to some aspects of the disclosure. The RAN200may implement any suitable wireless communication technology or technologies to provide radio access to a UE, such as UE222,224,226,228,230,232,234,236. As one example, the RAN200may operate according to 3GPP NR specifications, often referred to as 5G. As another example, the RAN200may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. The 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure. In some examples, the RAN200may be the same as the RAN104described above and illustrated inFIG.1. The geographic area covered by the RAN200may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station.FIG.2illustrates macrocells202,204, and206, and a small cell208, each of which may include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector. In a cell that is divided into sectors, the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell. Various base station arrangements can be utilized. For example, inFIG.2, two base stations210and212are shown in cells202and204; and a third base station214is shown controlling a remote radio head (RRH)216in cell206. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH216by feeder cables. In the illustrated example, the cells202,204, and206may be referred to as macrocells, as the base stations210,212, and214support cells having a large size. Further, a base station218is shown in the small cell208(e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc.) which may overlap with one or more macrocells. In this example, the cell208may be referred to as a small cell, as the base station218supports a cell having a relatively small size. Cell sizing can be done according to system design as well as component constraints. It is to be understood that the RAN200may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell. The base stations210,212,214,218provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the base stations210,212,214, and/or218may be the same as or similar to the base station/scheduling entity108described above and illustrated inFIG.1. FIG.2further includes a quadcopter or drone220, which may be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station such as a quadcopter or drone220. Within the RAN200, the cells may include UEs that may be in communication with one or more sectors of each cell. Further, each base station210,212,214,218, and220may be configured to provide an access point to a core network102(seeFIG.1) for all the UEs in the respective cells. For example, UEs222and224may be in communication with base station210; UEs226and228may be in communication with base station212; UEs230and232may be in communication with base station214by way of RRH216; UE234may be in communication with base station218; and UE236may be in communication with mobile base station220. In some examples, the UEs222,224,226,228,230,232,234,236,238,240, and/or242may be the same as or similar to the UE/scheduled entity106described above and illustrated inFIG.1. In some examples, a mobile network node (e.g., an unmanned aerial vehicle (UAV) such as a quadcopter or drone220) may be configured to function as a UE. For example, the quadcopter or drone220may operate within cell202by communicating with base station210. In a further aspect of the RAN200, sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs226and228) may communicate with each other using peer to peer (P2P) or sidelink signals227without relaying that communication through a base station (e.g., base station212). In some examples, the sidelink signals227include sidelink traffic and sidelink control. In a further example, UE238is illustrated communicating with UEs240and242. Here, the UE238may function as a scheduling entity or a primary/transmitting sidelink device, and UEs240and242may function as a scheduled entity or a non-primary (e.g., secondary/receiving) sidelink device. For example, a UE may function as a scheduling entity or a scheduled entity in a device-to-device (D2D), peer-to-peer (P2P), vehicle-to-vehicle (V2V) network, vehicle-to-everything (V2X), and/or in a mesh network. In a mesh network example, UEs240and242may optionally communicate directly with one another in addition to communicating with the UE238functioning as the scheduling entity. Thus, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, a P2P/D2D configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources. The air interface in the RAN200may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices. For example, 5G NR specifications provide multiple access for UL transmissions from UEs222and224to base station210, and for multiplexing DL transmissions from base station210to one or more UEs222and224, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier 1-DMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other suitable multiple access schemes. Further, multiplexing DL transmissions from the base station210to UEs222and224may be provided utilizing time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes. Further, the air interface in the RAN200may utilize one or more duplexing algorithms Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions. Full duplex means both endpoints can simultaneously communicate with one another. Half duplex means only one endpoint can send information to the other at a time. In a wireless link, a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies. Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g., several times per slot. In the RAN200, the ability for a UE to communicate while moving, independent of its location, is referred to as mobility. The various physical channels between the UE and the RAN200are generally set up, maintained, and released under the control of an access and mobility management function (AMF), which may include a security context management function (SCMF) that manages the security context for both the control plane and the user plane functionality and a security anchor function (SEAF) that performs authentication. In various aspects of the disclosure, a RAN200may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if signal quality from a neighboring cell exceeds that from the serving cell for a given amount of time, the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell. For example, UE224(illustrated as a vehicle, although any suitable form of UE may be used) may move from the geographic area corresponding to its serving cell202to the geographic area corresponding to a neighbor cell206. When the signal strength or quality from the neighbor cell206exceeds that of its serving cell202for a given amount of time, the UE224may transmit a reporting message to its serving base station210indicating this condition. In response, the UE224may receive a handover command, and the UE may undergo a handover to the cell206. In a network configured for UL-based mobility, UL reference signals from each UE may be utilized by the network to select a serving cell for each UE. In some examples, the base stations210,212, and214/216may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs), unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH)). The UEs222,224,226,228,230, and232may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal. The uplink pilot signal transmitted by a UE (e.g., UE224) may be concurrently received by two or more cells (e.g., base stations210and214/216) within the RAN200. Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations210and214/216and/or a central node within the core network) may determine a serving cell for the UE224. As the UE224moves through the RAN200, the network may continue to monitor the uplink pilot signal transmitted by the UE224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds that of the signal strength or quality measured by the serving cell, the network may handover the UE224from the serving cell to the neighboring cell, with or without informing the UE224. Although the synchronization signal transmitted by the base stations210,212, and214/216may be unified, the synchronization signal may not identify a particular cell, but rather may identify a zone of multiple cells operating on the same frequency and/or with the same timing. The use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network may be reduced. In some aspects of the disclosure, the scheduling entity and/or scheduled entity may be configured for beamforming and/or multiple-input multiple-output (MIMO) technology.FIG.3illustrates an example of a wireless communication system300supporting beamforming and/or MIMO. In a MIMO system, a transmitter302includes multiple transmit antennas304(e.g., N transmit antennas) and a receiver306includes multiple receive antennas308(e.g., M receive antennas). Thus, there are N×M signal paths310from the transmit antennas304to the receive antennas308. The multiple transmit antennas304and multiple receive antennas308may each be configured in a single panel or multi-panel antenna array. Each of the transmitter302and the receiver306may be implemented, for example, within a base station/scheduling entity108, as illustrated inFIGS.1and/or2, a UE/scheduled entity106, as illustrated inFIGS.1and/or2, or any other suitable wireless communication device. The use of such multiple antenna technology enables the wireless communication system300to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data, also referred to as layers, simultaneously on the same time-frequency resource. The data streams may be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data streams with different weighting and phase shifting) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE(s) with different spatial signatures, which enables each of the UE(s) to recover the one or more data streams destined for that UE. On the uplink, each UE transmits a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream. The number of data streams or layers corresponds to the rank of the transmission. In general, the rank of the MIMO system (e.g., the wireless communication system300supporting MIMO) is limited by the number of transmit or receive antennas304or308, whichever is lower. In addition, the channel conditions at the UE, as well as other considerations, such as the available resources at the base station, may also affect the transmission rank. For example, the rank (and therefore, the number of data streams) assigned to a particular UE on the downlink may be determined based on the rank indicator (RI) transmitted from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and a measured signal-to-interference-plus-noise ratio (SINR) on each of the receive antennas. The RI may indicate, for example, the number of layers that may be supported under the current channel conditions. The base station may use the RI, along with resource information (e.g., the available resources and amount of data to be scheduled for the UE), to assign a transmission rank to the UE. In Time Division Duplex (TDD) systems, the UL and DL are reciprocal, in that each uses different time slots of the same frequency bandwidth. Therefore, in TDD systems, the base station may assign the rank for DL MIMO transmissions based on UL SINR measurements (e.g., based on a sounding reference signal (SRS) transmitted from the UE or other pilot signal). Based on the assigned rank, the base station may then transmit a channel state information-reference signal (CSI-RS) with separate CSI-RS sequences for each layer to provide for multi-layer channel estimation. From the CSI-RS, the UE may measure the channel quality across layers and resource blocks and feed back channel quality indicator (CQI) and rank indicator (RI) values to the base station for use in updating the rank and assigning REs for future downlink transmissions. In one example, as shown inFIG.3, a rank-2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will transmit one data stream from each of the transmit antennas304. Each data stream reaches each of the receive antennas308along a different one of the signal paths310. The receiver306may then reconstruct the data streams using the received signals from each of the receive antennas308. Beamforming is a signal processing technique that may be used at the transmitter302or receiver306to shape or steer an antenna beam (e.g., a transmit/receive beam) along a spatial path between the transmitter302and the receiver306. Beamforming may be achieved by combining the signals communicated via antennas304or308(e.g., antenna elements of an antenna array) such that some of the signals experience constructive interference while others experience destructive interference. To create the desired constructive/destructive interference, the transmitter302or receiver306may apply amplitude and/or phase offsets to signals transmitted or received from each of the antennas304or308associated with the transmitter302or receiver306. In some examples, to select one or more serving beams for communication with a UE, the base station may transmit a reference signal, such as a synchronization signal block (SSB), a tracking reference signal (TRS), or a channel state information reference signal (CSI-RS), on each of a plurality of beams in a beam-sweeping manner. The UE may measure the reference signal received power (RSRP) on each of the beams and transmit a beam measurement report to the base station indicating the Layer 1 (L-1 RSRP) of each of the measured beams. The base station may then select the serving beam(s) for communication with the UE based on the beam measurement report. In other examples, when the channel is reciprocal, the base station may derive the particular beam(s) to communicate with the UE based on uplink measurements of one or more uplink reference signals, such as a sounding reference signal (SRS). In 5G New Radio (NR) systems, particularly for above 6 GHz or millimeter wave (mmWave) systems, beamformed signals may be utilized for downlink channels, including the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH). In addition, for UEs configured with beamforming antenna array modules, beamformed signals may also be utilized for uplink channels, including the physical uplink control channel (PUCCH) and the physical uplink shared channel (PUSCH). However, it should be understood that beamformed signals may also be utilized by, for example, enhanced mobile broadband (eMBB) gNBs for sub 6 GHz systems. Beamforming may be used in both half duplex and full duplex wireless communication networks. In full duplex networks, downlink and uplink transmissions may occur simultaneously. In some examples, full duplex networks may utilize sub-band FDD in unpaired spectrum, in which transmissions in different directions are carried in different sub-bands or BWPs of the carrier bandwidth. Various aspects of the present disclosure will be described with reference to an OFDM waveform, schematically illustrated inFIG.4. It should be understood by those of ordinary skill in the art that the various aspects of the present disclosure may be applied to a DFT-s-OFDMA or an SC-FDMA waveform in substantially the same way as described herein below. That is, while some examples of the present disclosure may focus on an OFDM link for clarity, it should be understood that the same principles may be applied as well to DFT-s-OFDMA or SC-FDMA waveforms. Within the present disclosure, a frame400refers to a duration of 10 ms for wireless transmissions, with each frame400consisting of 10 subframes of 1 ms each. A transmission burst may include multiple frames. On a given carrier, there may be one set of frames in the UL, and another set of frames in the DL. Referring now toFIG.4, an expanded view of an OFDM resource grid402including an exemplary first subframe407is illustrated. However, as those skilled in the art will readily appreciate, the physical (PHY) transmission structure for any particular application may vary from the example described here, depending on any number of factors. Here, time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers or tones. The resource grid402may be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input-multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple number of resource grids402may be available for communication. The resource grid402is divided into multiple resource elements (REs)404. An RE404, which is 1 subcarrier×1 symbol, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB)406, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, the RB406may include 12 subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as the RB406entirely corresponds to a single direction of communication (either transmission or reception for a given device). A set of continuous or discontinuous resource blocks may be referred to herein as a Resource Block Group (RBG), sub-band, or bandwidth part (BWP). A set of sub-bands or BWPs may span the entire bandwidth. Scheduling of UEs (scheduled entities) for downlink or uplink transmissions typically involves scheduling one or more resource elements404within one or more sub-bands or bandwidth parts (BWPs). Thus, a UE generally utilizes only a subset of the resource grid402. An RB may be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme chosen for the air interface, the higher the data rate for the UE. In this illustration, the RB406is shown as occupying less than the entire bandwidth of the first subframe407, with some subcarriers illustrated above and below the RB406. In a given implementation, the first subframe407may have a bandwidth corresponding to any number of one or more RBs406. Further, in this illustration, the RB406is shown as occupying less than the entire duration of the first subframe407, although this is merely one possible example. Each of the first subframe407and a second subframe408(e.g., where each subframe has a 1 ms duration) may consist of one or multiple adjacent slots. In the illustrative example shown inFIG.4, the first subframe407includes one slot and the second subframe408includes four slots. In some examples, a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots, sometimes referred to as shortened transmission time intervals (TTIs), having a shorter duration (e.g., one to three OFDM symbols). These mini-slots or shortened TTIs may in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs. Any number of resource blocks may be utilized within a subframe or slot. An expanded view of one of the slots410illustrates the slot410as including a control region412and a data region414. In a first downlink example of the slot410, the control region412may carry control channels (e.g., a physical downlink control channel (PDCCH)) and the data region414may carry data channels (e.g., a physical downlink shared channel (PDSCH)). In a second uplink example of the slot410, the relative positions of the control region412and the data region414may be reversed and the control region412may carry control channels (e.g., a physical uplink control channel (PUCCH)) and the data region414may carry data channels (e.g., a physical uplink shared channel (PUSCH)). Of course, a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. The structures illustrated inFIG.4are merely exemplary in nature, and different slot structures may be utilized, and may include one or more of each of the control region(s) and data region(s). Although not illustrated inFIG.4, the various REs404within an RB406may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs404within the RB406may also carry pilots or reference signals, including but not limited to a demodulation reference signal (DMRS), a control reference signal (CRS), channel state information reference signal (CSI-RS), and/or a sounding reference signal (SRS). These pilots or reference signals may provide for a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channels within the RB406. In some examples, the slot410may be utilized for broadcast or unicast communication. For example, a broadcast, multicast, or groupcast communication may refer to a point-to-multipoint transmission by one device (e.g., a base station, UE, or other similar device) to other devices. As used herein, a broadcast communication is delivered to all devices, whereas a multicast communication is delivered to multiple intended recipient devices. A unicast communication may refer to a point-to-point transmission by a one device to a single other device. In a DL transmission, a transmitting device (e.g., the base station/scheduling entity108) may allocate one or more REs404(e.g., DL REs within the control region412) to carry DL control information (DCI) including one or more DL control channels that may carry information, for example, originating from higher layers, such as a physical broadcast channel (PBCH), a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), a physical downlink control channel (PDCCH), etc., to one or more scheduled entities (e.g., UE/scheduled entity106). A Physical Control Format Indicator Channel (PCFICH) may provide information to assist a receiving device in receiving and decoding the PDCCH and/or Physical HARQ Indicator Channel (PHICH). The PHICH carries HARQ feedback transmissions such as an acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission confirmed, an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc. The PDCCH may carry downlink traffic112, including downlink control information (DCI) for one or more UEs in a cell. This may include, but not limited to, power control commands, scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions. The base station may further allocate one or more REs404to carry other DL signals, such as a demodulation reference signal (DMRS); a phase-tracking reference signal (PT-RS); a positioning reference signal (PRS), a channel-stated information reference signal (CSI-RS); a primary synchronization signal (PSS); and a secondary synchronization signal (SSS). These DL signals, which may also be referred to as downlink physical signals, may correspond to sets of resource elements used by the physical layer but they generally do not carry information originating from higher layers. A UE may utilize the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell. The synchronization signals PSS and SSS, and in some examples, the PBCH and a PBCH DMRS, may be transmitted in a synchronization signal block (SSB). The PBCH may further include a master information block (MIB) that includes various system information, along with parameters for decoding a system information block (SIB). The SIB may be, for example, a SystemInformationType 1 (SIB1) that may include various additional system information. Examples of system information transmitted in the MIB may include, but are not limited to, a subcarrier spacing, system frame number, a configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), and a search space for SIB1. Examples of additional system information transmitted in the SIB1 may include, but are not limited to, a random access search space, downlink configuration information, and uplink configuration information. The MIB and SIB1 together provide the minimum system information (SI) for initial access. The synchronization signals PSS and SSS (collectively referred to as a synchronization signal or SS), and in some examples, the PBCH, may be transmitted in an SS block that may include 4 consecutive OFDM symbols, numbered via a time index in increasing order from 0 to 3. In the frequency domain, the SS block may extend over 240 contiguous subcarriers, with the subcarriers being numbered via a frequency index in increasing order from 0 to 239. Of course, the present disclosure is not limited to this specific SS block configuration. Other nonlimiting examples may utilize greater or fewer than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit a PBCH; and/or may utilize nonconsecutive symbols for an SS block, within the scope of the present disclosure. In an UL transmission, a transmitting device (e.g., a UE/scheduled entity106) may utilize one or more REs404, including one or more UL control channels that may carry uplink control information (UCI) to the base station/scheduling entity108, for example. UCI may include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. In some examples, the uplink control information may include a scheduling request (SR), i.e., request for the scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted on the uplink control channel from the scheduled entity106, the scheduling entity108may transmit downlink control information (DCI) that may schedule resources for uplink packet transmissions. UCI may also include HARQ feedback, such as an acknowledgment (ACK) or negative acknowledgment (NACK), channel state information (CSI), channel state feedback (CSF), or any other suitable UL control information (UCI). The UCI may originate from higher layers via one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. Further, UL REs404may carry UL physical signals that generally do not carry information originating from higher layers, such as demodulation reference signals (DMRS), phase-tracking reference signals (PT-RS), sounding reference signals (SRS), etc. In addition to control information, one or more REs404(e.g., within the data region414) may be allocated for user data traffic. Such traffic may be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH), or for an UL transmission, a physical uplink shared channel (PUSCH). In some examples, one or more REs404within the data region414may be configured to carry SIBs (e.g., SIB1), carrying information that may enable access to a given cell. The physical channels described above are generally multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TB). The transport block size (TB S), which may correspond to a number of bits of information, may be a controlled parameter, based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission. FIG.5is another schematic illustration of an organization of wireless resources in an air interface utilizing OFDM and exemplifying a location of a plurality of physical resource blocks (PRBs) within CCEs and DCIs according to some aspects of the disclosure. InFIG.5, time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers or tones. As withFIG.4, a frame500refers to a duration of 10 ms, with each frame400consisting of 10 subframes of 1 ms each. An expanded view of an OFDM resource grid502depicts an exemplary first subframe507with one slot and an exemplary second subframe508with four slots. As withFIG.4, the resource grid502may be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input-multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple number of resource grids502may be available for communication. The resource grid502is divided into multiple resource elements (REs)504. An RE504, which is 1 subcarrier×1 symbol, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In the example ofFIG.5, a block of REs may be referred to as a physical resource block (PRB)506, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, the PRB506may include 12 subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an PRB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single PRB such as the PRB506entirely corresponds to a single direction of communication (either transmission or reception for a given device). In the illustrative example shown inFIG.5, the first subframe507includes one slot and the second subframe508includes four slots. InFIG.5, one PRB506representing one OFDM symbol of a physical downlink control channel (PDCCH) is depicted in greater detail than other illustrated PRBs for purposes of explanation. The PRB506is comprised of 12 subcarriers and one OFDM symbol. Of the 12 subcarriers, 3 are used for demodulation reference signals (DMRSs) and9are used for PDCCH payload. The REs504carrying the DMRS are the first, fifth, and ninth REs504of the PRB506. A plurality of PRBs510, spanning a greater (e.g., wider) bandwidth than PRB506alone, are depicted inFIG.5. For example, the plurality of PRBs510includes PRB506and PRB512. One PRB, such as PRB512, may be referred to as a resource element group (REG). As illustrated for exemplary PRB512corresponds to REG514. According to some aspects, a control channel entity (CCE)516may include 6 REGs. A CCE516may be a smallest unit of a scheduled PDCCH transmission. According to some examples, a collection of 1, 2, 4, 8, or 16 CCEs (such as CCE516) (where the number may be referred to as the aggregation level) may be referred to as downlink control information (DCI)518. The CCE may be the unit upon which search spaces for blind decoding of PDCCH candidates is defined. In the example ofFIG.5, the DCI518may carry control information used to schedule a user data channel (e.g., the PDSCH) on the downlink, for example. In the example ofFIG.5, the DCI518may be carried by the PDCCH. FIG.6is another schematic illustration of an organization of wireless resources in an air interface utilizing OFDM according to some aspects of the disclosure. InFIG.6, time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of CCEs. For example, the vertical dimension of each major solid line rectangle represents one CCE602. Each CCE602includes 6 resource element groups (REGs). Each REG includes one physical resource block (PRB) of 12 subcarriers by one OFDM symbol. The 6 REGs are each represented by a minor dished line rectangle. One slot604in the time domain is represented. The time-frequency resources ofFIG.6are depicted in a downlink resource grid600. FIG.6depicts one bandwidth part (BWP)606within a carrier bandwidth (CBW)605. According to some aspects, a BWP606is a contiguous set of physical resource blocks (PRBs) on a given carrier. InFIG.6, the contiguous set of PRBs are represented by a contiguous set of CCEs602. The BWP606may be offset607in frequency from a common reference point for all resource grids in the frequency domain referred to as “Point A” and illustrated inFIG.6. Point A may be a center of a subcarrier 0 of a common resource block 0 of a lowest resource grid. Point A may be outside of a carrier BW assigned to or used by a particular device. In the example ofFIG.6, the BWP606corresponds to a set of 48 PRBs, which represent 576 subcarriers (i.e., 12 REs/REG×6 REGs/DCI×8 DCI). A scheduling entity (e.g., a base station) can define common CCEs and scheduled entity-specific (e.g., UE-specific) CCEs. InFIG.6, for example, CORESET0608includes 24 REGs (corresponding to 24 PRBs) in one set of four CCEs (where each CCE may be similar to CCE602), configured as four CCEs in the frequency domain and one OFDM symbol in the time domain. The four CCE may be grouped as a first DCI (DCI0610) and a second DCI (DCI1612). There are two CCEs in DCI0610and two CCEs in DCI1612. Within CORESET0608, DCI0610may be associated with a first scheduled entity (e.g. a first UE, UE1) and DCI1612may be associated with a second scheduled entity (e.g. a second UE, UE2). In another example, CORESET1614includes two CCEs, grouped as a third DCI (DCI2616) and four DCIs grouped as a fourth DCI (DCI3620). DCI2616may be configured as one CCE in the frequency domain and 2 OFDM symbols in the time domain. DCI2616may be associated with a third scheduled entity (e.g. a third UE, UE3). DCI3620may be configured as two CCEs in the frequency domain and 2 OFDM symbols in the time domain. DCI3620may be associated with the first scheduled entity (e.g. the first UE, UE1). Three search spaces are identified in the downlink resource grid600. A first search space624may be in CORESET0608and may be coincident with outline of DCI0610and DCI1612. A second search space626and a third search space628may be in CORESET1614. The second search space626may be coincident with the outline of DCI3620. The third search space628may be coincident with the outline of DCI2616. A search space may include a number of PDCCH candidates. There may be a mapping between a CORESET and a search space. For example, a CORESET may include a plurality of search spaces. In general, the scheduled entity may attempt to blind decode a PDCCH candidate in each search space; even if a scheduling entity did not schedule a PDCCH in any given search space. A CORESET may be associate with a common search space, a scheduled entity-specific search space, or a combination of both. The following relationships between CORESETs, BWPs, and search spaces are made with reference to NR; however, the following is exemplary and non-limiting and other relationships between CORESETs, BWPs, and search spaces (or their equivalents, for example in other radio technologies) are within the scope of the disclosure. In general, there may be up to three CORESETs per BWP, including both common and scheduled entity-specific CORESETs. There may be up to four BWPs per serving cell, with only one of the BWPs active at a given time. Accordingly, a maximum number of CORESETs per serving cell may be twelve (e.g., 3 CORESETs per BWP×4 BWPs per serving cell). The resource elements of a CORESET may be mapped to one or more CCEs. One or more CCEs from one CORESET may be aggregated to form the resources used by one PDCCH. Blind decoding of PDCCH candidates is based on search spaces. A maximum number of search spaces per BWP may be ten. Multiple search spaces may use the time-frequency resources of one CORESET. According to one example, a scheduling entity may compute a cyclic redundancy check (CRC) of a payload of a DCI carried by a PDCCH. The CRC may be scrambled using an identifier of a scheduled entity (e.g., using a C-RNTI). Upon receipt of the DCI, the scheduled entity may compute a scrambled CRC on the payload of the DCI using the same procedure as used by the scheduling entity. The scheduled entity may then compare the scrambled CRC to the received CRC. If the CRCs are equal, the DCI was meant for the scheduled entity. If the payload was corrupted or the CRC was scrambled using another scheduled entity's identification, then the CRCs would not match and the scheduled entity may disregard the DCI. Limits on a total number of PDCCH blind decodes and a total number of control channel elements (CCEs) corresponding to PDCCH candidates may be defined per slot. In the example illustrated inFIG.6, the limit on the total number of PDCCH blind decodes may be 3 as the number of search spaces where the PDCCH candidates are present is 3, and the limit on the total number of CCEs corresponding to PDCCH candidates is 10. A higher limit on the PDCCH blind decodes per slot is generally beneficial to provide more flexibility for a base station to schedule the PDCCH. If a higher frequency and/or a large subcarrier spacing is used for communicating a PDCCH, a less time is available for decoding and processing the PDCCH, which may cause the limits on the PDCCH blind decodes to become lower. In other words, with the less time available for decoding and processing the PDCCH, a total number of possible PDCCH blind decoding attempts may become smaller. As the limits on the PDCCH blind decodes become lower, flexibility for a base station to schedule the PDCCH may be reduced. Further, as the limits on the PDCCH blind decodes become lower, a blocking probability associated with the PDCCH may increase, where the blocking probability indicates the probability of UEs that cannot be scheduled for receiving DCI via the PDCCH. Depending on the configuration of search spaces and periodicities of the search spaces, and/or time offsets, the number of PDCCH candidates may vary from one slot to another. For example, one slot may have a larger number of PDCCH candidates than another slot. Less time available for processing the PDCCH (e.g., due to a higher frequency and/or a large subcarrier spacing) may force the number of PDCCH candidates per slot to be smaller, which may cause the number of search spaces to decrease and/or may cause strict limits on designing of the search spaces. The PDCCH decoding and processing may be performed over multiple slots if a configuration for the UE allows a delay in PDCCH decoding and processing. In an aspect, time delay parameters such as K0and K2may be introduced to indicate a delay in PDCCH decoding and processing. In particular, K0indicates a delay between reception of DCI (e.g., for downlink scheduling) in a PDCCH and scheduled reception of a corresponding downlink data in a PDSCH, in a number of slots. K2indicates a delay between reception of DCI (e.g., for uplink scheduling) in a PDCCH and scheduled transmission of a corresponding uplink data in a PUSCH, in a number of slots. Generally, different types of DCI are used for a PDSCH and a PUSCH, respectively. For example, the DCI format 0 may be used for uplink scheduling of the uplink data in the PUSCH, and the DCI format 1 may be used for downlink scheduling of the downlink data in the PDSCH. FIGS.7A and7Bare example diagrams illustrating various time delays associated with PDCCH processing according to some aspects of the disclosure.FIG.7Ais an example diagram700illustrating a delay K0between a slot location of a PDCCH and a slot location of a PDSCH. InFIG.7A, the delay K0702indicates a time delay between a slot location of a PDCCH712and a slot location of a PDSCH714, in a number of slots. DCI in the PDCCH712is received in slot n722, where n is a slot number and is an integer that is 0 or greater than 0. Because the time delay between the slot location of a PDCCH712and the slot location of a PDSCH714is K0, the downlink data in the PDSCH714is scheduled to be received in slot n+K0724. Thus, if K0is zero, the PDCCH is processed and a downlink data in the PDSCH is received within the same slot (e.g., slot n722). On the other hand, if K0is greater than zero, a downlink data in the PDSCH is received in a later slot than a slot (e.g., slot n722) where the PDCCH is received. InFIG.7B, the delay K2752indicates a time delay between a slot location of a PDCCH762and a slot location of a PUSCH764, in a number of slots. DCI in the PDCCH762is received in slot m772, where m is a slot number and is an integer that is 0 or greater than 0. Because the time delay between the slot location of a PDCCH762and the slot location of a PUSCH764is K2, the uplink data in the PUSCH764is scheduled to be transmitted in slot m+K2774. Thus, if K2is zero, the PDCCH is processed and an uplink data in the PUSCH is transmitted within the same slot (e.g., slot m772). On the other hand, if K2is greater than zero, an uplink data in the PDSCH is transmitted in a later slot than a slot (e.g., slot m772) where the PDCCH is received. A base station may configure K0and K2values and convey the K0and K2values to a UE. The base station may also configure K0min and K2min values and may convey the K0min and K2min values to a UE, where K0min indicates a minimum delay between a slot location of a PDCCH and a slot location of a corresponding PDSCH, and K2min indicates a minimum delay between a slot location of a PDCCH and a slot location of a corresponding PUSCH. If K0min and K2min allow sufficient delays, the complexity of PDCCH blind decoding by the UE may be distributed over multiple slots. For example, if K0min is greater than 0, the blind decoding of a PDCCH may be distributed over multiple slots, prior to reception of a downlink data in a corresponding PDSCH. Similarly, if K2min is greater than 0, the blind decoding of a PDCCH may be distributed over multiple slots, prior to transmission of an uplink data in a corresponding PUSCH. K0and K2values and/or K0min and K2min values may be configured per BWP. As discussed above, multiple search spaces may exist per BWP. If K0min and K2min values are configured for a particular BWP, all of the search spaces within the particular BWP may be associated with the same K0min and K2min values. Hence, considering that multiple search spaces may exist per BWP, assigning the same K0and K0values and/or the same K0min and K2min values for all search spaces within the same BWP may be a restrictive approach that does not allow flexibility in configurations of the K0and K2values and/or K0min and K2min values for different search spaces within the same BWP. For example, if K0min is zero, all of the search spaces per BWP need to decode the PDCCH and receive the downlink data in the PUSCH within the same slot, which may cause undesirable pressure to process the PDCCH quickly. On the other hand, if K0min is a large number, all of the search spaces per BWP may experience a large delay in decoding of the PDCCH, which may cause undesirable delays in receiving a downlink data in a corresponding PUSCH. According to some aspects of a disclosure, K0and K2values may be determined for each search space, regardless of whether search spaces are within the same BWP or not. Because each search space may be associated with its own K0value and K2value, different delays may be applied for different search spaces. Similarly, K0min and K2min values may be determined for each search space that is suitable for configuring K0min and K2min values. Hence, even for search spaces within the same BWP, each search space may be associated with its own K0value and K2value and its own K0min and K2min values. As such, flexibility in configuring delays associated with a downlink control channel (e.g., PDCCH) for different search spaces is increased. FIG.8is an example diagram800illustrating communication between a base station802and a UE804according to some aspects of the disclosure. In an aspect, the base station802may be a base station, a gNB, or a network access node as illustrated in any one or more ofFIG.1,FIG.2, and/orFIG.3. In an aspect, the UE804may be a UE as illustrated in any one or more ofFIG.1,FIG.2, and/orFIG.3. The base station802may determine search spaces where a downlink control channel (e.g., PDCCH) may be decoded, where each search space may include one or more CCEs. In particular, the base station802may determine first search spaces that are potential locations where a first downlink control channel for downlink scheduling of a downlink data (e.g., in a PDSCH) may be decoded. The base station802may determine second search spaces that are potential locations where a second downlink control channel for uplink scheduling of an uplink data (e.g., in a PUSCH) may be decoded. In an aspect, each of the first search spaces may include at least one first respective CCE, and each of the second search spaces may include at least one respective second CCE. In an aspect, the first search spaces and/or the second search spaces may be located within a BWP (e.g., the same BWP). After determining the first search spaces and the second search spaces, the base station may transmit at812information indicating the first search spaces and/or the second search spaces to the UE804. In an aspect, each first search space may be a user specific search space and/or a common search space, and each second search space may be a user specific search space and/or a common search space. For example, the information indicating the first search spaces and/or the second search spaces may be transmitted via RRC signaling, where an RRC parameter “searchSpaceId” may be used to indicate each of the first search spaces and/or the second search spaces. The base station802may configure first delays (e.g., K0values), where each first delay indicates a respective time delay between a resource location (e.g., slot location) of the first downlink control channel (e.g., PDCCH) and a resource location (e.g., slot location) of a downlink data (e.g., in a PDSCH) associated with the first downlink control channel and is configured for a respective first search space of the first search spaces. For example, each first search space may be configured with a respective first delay. The downlink data may be the downlink data in a PDSCH, and the first downlink control channel may be a PDCCH for scheduling the downlink data. In an aspect, the resource location of the first downlink control channel and the resource location of the downlink data may be a slot location of the first downlink control channel and a slot location of the downlink data, respectively. For example, each first delay for a respective search space may be a respective K0value that indicates a respective slot offset between a slot location of a PDCCH for the downlink data and a slot location of scheduled downlink of the downlink data in a PDSCH for the respective search space. The base station802may configure second delays (e.g., K2values), where each second delay indicates a respective time delay between a resource location (e.g., slot location) of the second downlink control channel (e.g., PDCCH) and a resource location (e.g., slot location) of a uplink data (e.g., in a PUSCH) associated with the second downlink control channel and is configured for a respective second search space of the second search spaces. For example, each second search space may be configured with a respective second delay. The uplink data may be the uplink data in a PUSCH, and the second downlink control channel may be a PDCCH for scheduling the uplink data. In an aspect, the resource location of the second downlink control channel and the resource location of the uplink data may be a slot location of the second downlink control channel and a slot location of the uplink data, respectively. For example, each second delay for a respective search space may be a respective K2value that indicates a respective slot offset between a slot location of a PDCCH for the uplink data and a slot location of scheduled uplink of the uplink data in a PUSCH for the respective search space. In an aspect, the base station802may determine a minimum first delay indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel per first search space for one or more of the first search spaces. In an aspect, the base station802may determine a minimum second delay indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel per second search space for one or more second search spaces. For example, for a larger K0min and/or K2min, an available time for blind decoding of a corresponding PDCCH may be longer, which relaxes a time restriction in the blind decoding but may cause a longer delay in decoding and processing the corresponding PDCCH. In one example, if a base station802may determine that a low-latency in decoding the PDCCH is not needed and/or that the UE804needs additional time for decoding the PDCCH, the base station802may define a larger minimum first delay and/or a larger minimum second delay. Otherwise, in this example, the base station802may define a shorter minimum first delay and/or a shorter minimum second delay. For example, for a particular search space, a first delay may be at least a minimum first delay. Similarly, for example, for a particular search space, a second delay may be at least a minimum second delay for the particular search space. In particular, in an aspect, the base station802may determine at least one minimum first delay (e.g., K0min), each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel and is configured for the at least one first search space of the search spaces, respectively. For example, for one or more of the first search spaces, each first search space may be configured with a respective minimum first delay. For example, for one or more of the first search spaces, each minimum first delay for a respective search space may be a respective K0min value that indicates a respective minimum slot offset between a slot location of a PDCCH for the downlink data and a slot location of scheduled downlink of the downlink data in a PDSCH for the respective search space. In an aspect, at least one periodicity respectively associated with the at least one first search space may be longer than one slot. For example, the base station802may configure minimum first delays for first search spaces with a periodicity of longer than one slot, but not for the other first search spaces with a periodicity not exceeding one slot. Thus, minimum first delays may be applicable only for first search spaces with a periodicity of longer than one slot, and may not be applicable for other first search spaces with a periodicity not exceeding one slot. Therefore, in this example, the at least one first search space for which the at least one minimum first delay is configured may have the periodicity of longer than one slot, while the other first search spaces may have the periodicity that does not exceed one slot and may not be configured with minimum first delays. In an example, if a particular search space is not configured with a minimum first delay, a first delay for the particular search space may be any value. In an aspect, the base station802may determine at least one minimum second delay (e.g., K2min), each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel and is configured for the at least one second search space of the search spaces, respectively. For example, for one or more of the second search spaces, each second search space may be configured with a respective minimum second delay. For example, for one or more of the second search spaces, each minimum second delay for a respective search space may be a respective K2min value that indicates a respective minimum slot offset between a slot location of a PDCCH for the uplink data and a slot location of scheduled uplink of the uplink data in a PUSCH for the respective search space. In an aspect, at least one periodicity respectively associated with the at least one second search space may be longer than one slot. For example, the base station802may configure minimum second delays for second search spaces with periodicity of longer than one slot, but not for the other second search spaces with periodicity not exceeding one slot. Thus, minimum second delays may be applicable only for second search spaces with a periodicity of longer than one slot, and may not be applicable for other second search spaces with a periodicity not exceeding one slot. Therefore, in this example, the at least one second search space for which the at least one minimum second delay is configured may have the periodicity of longer than one slot, while the other second search spaces may have the periodicity that does not exceed one slot and may not be configured with minimum second delays. In an example, if a particular search space is not configured with a minimum second delay, a second delay for the particular search space may be any value. In an aspect, each of the at least one minimum first delay may be configured based on a periodicity of a respective first search space of the at least one first search space. In an aspect, each of the at least one minimum second delay may be configured based on a periodicity of a respective second search space of the at least one second search space. In an example, for a BWP, the base station may configure a minimum first delay and/or a minimum second delay to be one half of the periodicity of the corresponding search space. For example, the base station may configure K0min and/or K2min per search space based on equation(s) K0min=floor(n/2) and/or K2min=floor(n/2), where n is the periodicity of a corresponding search space in terms of number of slots. For example, the periodicity (e.g., n) of a particular search space in terms of number of slots may be conveyed by the base station, e.g., via an RRC parameter “monitoringSlotPeriodicityAndOffset” for the particular search space that is indicated as an RRC parameter “searchSpaceId.” In an aspect, the base station may convey an indication of how the at least one minimum first delay and/or the at least one minimum second delay may be determined based on a periodicity of a corresponding search space, such as the above equations. After configuring the at least one first minimum delay and/or the at least one second minimum delay as discussed above, the base station802may transmit at814the at least one first minimum delay and/or the at least one second minimum delay to the UE804. In an aspect, the base station802may transmit the at least one first minimum delay and/or the at least one second minimum delay via an RRC message. Further, after configuring the first delays and/or the second delays as discussed above, the base station802may transmit at816the first delays (e.g., K0values) and/or the second delays (e.g., K2values) to the UE804. In an aspect, the first delays may be transmitted via first DCI on the first downlink control channel. In an aspect, the second delays may be transmitted via second DCI on the second downlink control channel Hence, for example, the first delays for first search spaces and/or the second delays for the second search spaces may be communicated dynamically via the first DCI and/or the second DCI, respectively, while the at least one first minimum delay and/or the at least one second minimum delay may be communicated semi-statically via RRC signaling as discussed above. For example, the first DCI may be DCI format 1 for a downlink assignment, and the second DCI may be DCI format 0 for an uplink grant. After receiving information indicating the first search spaces and receiving the first delays, the UE804may perform detection for the first downlink control channel at the first search spaces respectively based on the first delays. For example, the UE804may attempt blind decoding of the first downlink control channel at various first search spaces based on the first delays configured respectively for the first search spaces. For example, a longer first delay may provide more time for decoding and processing the first downlink control channel. A single slot blind detection limit may indicate a number of maximum blind decodes that may be performed per a single slot, while multi-slot blind detection limit may indicate a number of maximum blind decodes that may be performed over P slots, where P is greater than 1. In some cases, the multi-slot blind detection limit may be utilized instead of the single slot blind detection limit. In an aspect, the at least one minimum first delay may cause at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots. Thus, in an aspect, in response to receiving the at least one minimum first delay configured for the at least one first search space, the UE804may determine at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots (e.g., as a multi-slot blind detection limit), where the UE804may perform the detection for the first downlink control channel at the at least one first search space further based on the first downlink control channel detection limit over first multiple slots. For example, when a minimum first delay (e.g., K0min) is configured for a particular search space, the UE804may determine that the blind decoding limit for the first downlink control channel is a multi-slot detection limit over the first multiple slots, instead of a single-slot detection limit applied for a single slot. Hence, the configuration of the minimum first delay for a particular search space may implicitly trigger the UE804to determine that the blind decoding limit for the first downlink control channel is the multi-slot detection limit. In an aspect, the UE804may determine a first downlink control channel detection limit for the first downlink control channel to be over a single slot if a corresponding one of the least one minimum first delay is less than or equal to a limit threshold, and may determine the first downlink control channel detection limit for the first downlink control channel to be over multiple slots if a corresponding one of the least one minimum first delay exceeds the limit threshold. For example, if a minimum first delay (e.g., K0min) for a particular search space is less than or equal to the limit threshold of 0 or 1 slot, the minimum first delay may be too small to provide the first downlink control channel detection limit to be over multiple slots and thus the UE804may determine the first downlink control channel detection limit to be over a single slot. On the other hand, if the minimum first delay (e.g., K0min) for this particular search space exceeds the limit threshold of 0 or 1 slot, the minimum first delay may be large enough for a multi-slot detection limit and thus the UE804may determine the first downlink control channel detection limit to be over multiple slots. The base station802at818may transmit to the UE804the first downlink control channel in a first search space of the first search spaces that corresponds to the resource location of the first downlink control channel. For example, the base station802may transmit the PDCCH for the downlink data in one of the search spaces that is determined by the base station802and corresponds to the slot location for communication of the PDCCH for the downlink data. The first DCI may be transmitted in the PDCCH for the downlink data. After the base station802transmits the first downlink channel, the base station802at820may transmit to the UE804the downlink data in the resource location of the downlink data based on a first delay of first delays that is configured for the first search space of the first search spaces where the first downlink channel is transmitted. For example, the base station802may transmit the downlink data in the PDSCH in the slot location of the downlink data after a time delay according to one of the first delays that is configured for respective one of the first search spaces where the PDCCH for the downlink data is communicated. In an aspect, the base station802may transmit the downlink data at the resource location of the downlink data based on the at least one minimum first delay when a frequency range of the first downlink control channel exceeds a frequency threshold and/or when a subcarrier spacing of the first downlink control channel exceeds a subcarrier spacing threshold. For example, the frequency threshold may be based on a highest frequency in FR2, which is 52600 MHz, and/or the subcarrier spacing threshold may be 120 kHz. As discussed above, the flexibility in assigning K0min values is more desired for a higher frequency and/or a larger subcarrier spacing that results shorter symbols and less available time for decoding and processing a PDCCH. Thus, for example, K0min per search space may be determined for a higher frequency and/or a larger subcarrier spacing, but may not be determined for a lower frequency and/or a smaller subcarrier spacing. After receiving information indicating the second search spaces and receiving the second delays, the UE804may perform detection for the second downlink control channel at the second search spaces respectively based on the second delays. For example, the UE804may attempt blind decoding of the second downlink control channel at various second search spaces based on the second delays configured respectively for the second search spaces. For example, a longer second delay may provide more time for decoding and processing the second downlink control channel. In an aspect, the at least one minimum second delay may cause at least one second downlink control channel detection limit for the second downlink control channel to be over multiple slots. Thus, in an aspect, in response to receiving the at least one minimum second delay configured for the at least one second search space, the UE804may determine at least one second downlink control channel detection limit for the second downlink control channel to be over multiple slots (e.g., as a multi-slot blind detection limit), where the UE804may perform the detection for the second downlink control channel at the at least one second search space further based on the second downlink control channel detection limit over second multiple slots. For example, when a minimum second delay (e.g., K2min) is configured for a particular search space, the UE804may determine that the blind decoding limit for the second downlink control channel is a multi-slot detection limit over second multiple slots, instead of a single-slot detection limit applied for a single slot. Hence, the configuration of the minimum second delay for a particular search space may implicitly trigger the UE804to determine that the blind decoding limit for the second downlink control channel is the multi-slot detection limit. In an aspect, the UE804may determine a second downlink control channel detection limit for the second downlink control channel to be over a single slot if a corresponding one of the least one minimum second delay is less than or equal to a limit threshold, and determine the second downlink control channel detection limit for the second downlink control channel to be over multiple slots if a corresponding one of the least one minimum second delay exceeds the limit threshold. For example, if a minimum second delay (e.g., K2min) for a particular search space is less than or equal to the limit threshold of 0 or 1 slot, the minimum second delay may be too small to provide the second downlink control channel detection limit to be over multiple slots and thus the UE804may determine the second downlink control channel detection limit to be over a single slot. On the other hand, if the minimum second delay (e.g., K2min) for this particular search space exceeds the limit threshold of 0 or 1 slot, the minimum second delay may be large enough for a multi-slot detection limit and thus the UE804may determine the second downlink control channel detection limit to be over multiple slots. The base station802at822may transmit to the UE804the second downlink control channel in a second search space of the second search spaces that corresponds to the resource location of the second downlink control channel. For example, the base station802may transmit the PDCCH for the uplink data in one of the search spaces that is determined by the base station802and corresponds to the slot location for communication of the PDCCH for the uplink data. The second DCI may be transmitted in the PDCCH for the uplink data. After the UE804receives the second downlink control channel, the UE804at824may transmit to the base station802the uplink data in the resource location of the uplink data based on a second delay of second delays that is configured for the second search space of the second search spaces where the second downlink channel is transmitted. For example, the UE804may transmit the uplink data in the PUSCH in the slot location of the uplink data after a time delay according to one of the second delays that is configured for respective one of the second search spaces where the PDCCH for the uplink data is communicated. In an aspect, the UE804may transmit the uplink data at the resource location of the uplink data based on the at least one minimum second delay when a frequency range of the second downlink control channel exceeds a frequency threshold and/or when a subcarrier spacing of the second downlink control channel exceeds a subcarrier spacing threshold. For example, the frequency threshold may be based on a highest frequency in FR2, which is 52600 MHz, and/or the subcarrier spacing threshold may be 120 kHz. As discussed above, the flexibility in assigning K2min values is more desired for a higher frequency and/or a larger subcarrier spacing that results shorter symbols and less available time for decoding and processing a PDCCH. Thus, for example, K2min per search space may be determined for a higher frequency and/or a larger subcarrier spacing, but may not be determined for a lower frequency and/or a smaller subcarrier spacing. In an aspect, the base station802may also configure and transmit to the UE804a minimum first delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel per BWP and/or a minimum second delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel per BWP. In an aspect, the UE804may receive the minimum first delay configured for a BWP, but may perform the detection for the first downlink control channel at the at least one first search space based on the at least one minimum first delay (e.g., configured per search space) while ignoring the minimum first delay configured for the BWP. Further, in an aspect, the UE804may receive the minimum second delay configured for a BWP, but may perform the detection for the second downlink control channel at the at least one second search space based on the at least one minimum second delay (e.g., configured per search space) while ignoring the minimum second delay configured for the BWP. For example, if the UE804receives a minimum first delay and/or a minimum second delay per search space and also receives a minimum first delay and/or a minimum second delay per BWP, the minimum first delay and/or a minimum second delay per search space may override the minimum first delay and/or a minimum second delay per BWP, such that the UE804considers the minimum first delay and/or a minimum second delay per search space while ignoring the minimum first delay and/or a minimum second delay per BWP. It is noted that the order in which the above processes812-824take place is not limited to the order explained above and illustrated inFIG.8. Hence, the above processes812-824may take place in different orders than the orders explained above and illustrated inFIG.8. FIGS.9A-9Dare example diagrams illustrating various delays between a slot location of a downlink control channel and a slot location of a corresponding downlink data/uplink data per search space.FIG.9Ais an example diagram900illustrating a delay between a slot location of a PDCCH and a slot location of a corresponding downlink data in a PDSCH for a particular search space. InFIG.9A, the PDCCH for the downlink data is received at a search space912in slot n902, where n is an integer number. Because the K0value for the search space912is 3, the downlink data in the PDSCH914is received in slot n+3904.FIG.9Bis an example diagram920illustrating a delay between a slot location of a PDCCH and a slot location of a corresponding downlink data in a PDSCH for a different search space. InFIG.9B, the PDCCH for the downlink data is received at a search space932in slot n902. Because the K0value for the search space912is 1, the downlink data in the PDSCH914is received in slot n+1924. FIG.9Cis an example diagram940illustrating a delay between a slot location of a PDCCH and a slot location of a corresponding uplink data in a PUSCH for a particular search space. InFIG.9C, the PDCCH for the uplink data is received at a search space952in slot n902. Because the K2value for the search space952is 0, the uplink data in the PDSCH914is transmitted in the same slot where the PDCCH is received, which is in slot n902.FIG.9Dis an example diagram960illustrating a delay between a slot location of a PDCCH and a slot location of a corresponding uplink data in a PUSCH for a different search space. InFIG.9D, the PDCCH for the uplink data is received at a search space972in slot n902. Because the K2value for the search space972is 2, the uplink data in the PDSCH914is transmitted in slot n+2964. FIG.10is a block diagram illustrating an example of a hardware implementation for a base station1000employing a processing system1014. For example, the base station1000may be a base station as illustrated in any one or more ofFIGS.1,2,3, and/or8. The base station1000may be implemented with a processing system1014that includes one or more processors1004. Examples of processors1004include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. In various examples, the base station1000may be configured to perform any one or more of the functions described herein. That is, the processor1004, as utilized in a base station1000, may be used to implement any one or more of the processes and procedures described below and illustrated inFIGS.11and12. In this example, the processing system1014may be implemented with a bus architecture, represented generally by the bus1002. The bus1002may include any number of interconnecting buses and bridges depending on the specific application of the processing system1014and the overall design constraints. The bus1002communicatively couples together various circuits including one or more processors (represented generally by the processor1004), a memory1005, and processor-readable media (represented generally by the processor-readable storage medium1006). The bus1002may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. A bus interface1008provides an interface between the bus1002and a transceiver1010. The transceiver1010provides a communication interface or means for communicating with various other apparatus over a transmission medium. Depending upon the nature of the apparatus, a user interface1012(e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface1012is optional, and may be omitted in some examples, such as a base station. In some aspects of the disclosure, the processor1004may include search space configuration circuitry1040configured for various functions, including, for example, determining a plurality of first search spaces indicating potential locations for a first downlink control channel or a plurality of second search spaces indicating potential locations for a second downlink control channel or both. For example, the search space configuration circuitry1040may be configured to implement one or more of the functions described below in relation toFIGS.11and12, including, e.g., blocks1102and1202. In some aspects of the disclosure, the processor1004may include delay configuration circuitry1042configured for various functions, including, for example, configuring a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of the plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. For example, the delay configuration circuitry1042may be configured to implement one or more of the functions described below in relation toFIGS.11and12, including, e.g., blocks1104and1254. In some aspects, the delay configuration circuitry1042may be configured to configure and transmit at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively. For example, the delay configuration circuitry1042may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1206. In some aspects, the delay configuration circuitry1042may be configured to configure and transmit at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively. For example, the delay configuration circuitry1042may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1208. In some aspects of the disclosure, the processor1004may include communication and processing circuitry1044configured for various functions, including, for example, transmitting the plurality of first delays or the plurality of second delays or both to a UE. For example, the communication and processing circuitry1044may be configured to implement one or more of the functions described below in relation toFIGS.11and12, including, e.g., blocks1106and1256. In some aspects, the communication and processing circuitry1044may be configured to transmit information indicating the plurality of first search spaces, or the plurality of second search spaces, or both. For example, the communication and processing circuitry1044may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1204. In some aspects, the communication and processing circuitry1044may be configured to transmit at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel, or the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel. For example, the communication and processing circuitry1044may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1258. In some aspects, the communication and processing circuitry1044may be configured to transmit the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. For example, the communication and processing circuitry1044may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1260. In some aspects, the communication and processing circuitry1044may be configured to receive the uplink data in the resource location of the uplink data based on a second delay of the plurality of second delays that is configured for the second search space. For example, the communication and processing circuitry1044may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1262. The processor1004is responsible for managing the bus1002and general processing, including the execution of software stored on the processor-readable storage medium1006. The software, when executed by the processor1004, causes the processing system1014to perform the various functions described below for any particular apparatus. The processor-readable storage medium1006and the memory1005may also be used for storing data that is manipulated by the processor1004when executing software. One or more processors1004in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a processor-readable storage medium1006. The processor-readable storage medium1006may be a non-transitory processor-readable storage medium. A non-transitory processor-readable storage medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a smart card, a flash memory device (e.g., a card, a stick, or a key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. The processor-readable storage medium1006may reside in the processing system1014, external to the processing system1014, or distributed across multiple entities including the processing system1014. The processor-readable storage medium1006may be embodied in a computer program product. By way of example, a computer program product may include a processor-readable storage medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system. In one or more examples, the processor-readable storage medium1006may include search space configuration software/instructions1050configured for various functions, including, for example, determining a plurality of first search spaces indicating potential locations for a first downlink control channel or a plurality of second search spaces indicating potential locations for a second downlink control channel or both. For example, the search space configuration software/instructions1050may be configured to implement one or more of the functions described below in relation toFIGS.11and12, including, e.g., blocks1102and1202. In some aspects of the disclosure, the processor-readable storage medium1006may include delay configuration software/instructions1052configured for various functions, including, for example, configuring a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of the plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. For example, the delay configuration software/instructions1052may be configured to implement one or more of the functions described below in relation toFIGS.11and12, including, e.g., blocks1104and1254. In some aspects, the delay configuration software/instructions1052may be configured to configure and transmit at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively. For example, the delay configuration software/instructions1052may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1206. In some aspects, the delay configuration software/instructions1052may be configured to configure and transmit at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively. For example, the delay configuration software/instructions1052may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1208. In some aspects of the disclosure, the processor-readable storage medium1006may include communication and processing software/instructions1054configured for various functions, including, for example, transmitting the plurality of first delays or the plurality of second delays or both to a UE. For example, the communication and processing software/instructions1054may be configured to implement one or more of the functions described below in relation toFIGS.11and12, including, e.g., blocks1106and1256. In some aspects, the communication and processing software/instructions1054may be configured to transmit information indicating the plurality of first search spaces, or the plurality of second search spaces, or both. For example, the communication and processing software/instructions1054may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1204. In some aspects, the communication and processing software/instructions1054may be configured to transmit at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel, or the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel. For example, the communication and processing software/instructions1054may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1258. In some aspects, the communication and processing software/instructions1054may be configured to transmit the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. For example, the communication and processing software/instructions1054may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1260. In some aspects, the communication and processing software/instructions1054may be configured to receive the uplink data in the resource location of the uplink data based on a second delay of the plurality of second delays that is configured for the second search space. For example, the communication and processing software/instructions1054may be configured to implement one or more of the functions described below in relation toFIG.12, including, e.g., block1262. FIG.11is a flow chart illustrating an exemplary process1100(e.g., a method) of wireless communications, at base station in accordance with some aspects of the disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process1100may be carried out by the base station1000illustrated inFIG.10. In some examples, the process1100may be carried out by any suitable apparatus or means for carrying out the functions or algorithms described herein. At block1102, the base station may determine a plurality of first search spaces indicating potential locations for a first downlink control channel or a plurality of second search spaces indicating potential locations for a second downlink control channel or both. At block1104, the base station may configure a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of the plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. At block1106, the base station may transmit the plurality of first delays or the plurality of second delays or both to a UE. FIG.12Ais a flow chart illustrating an exemplary process1200(e.g., a method) of wireless communications, at a base station in accordance with some aspects of the disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process1200may be carried out by the base station1000illustrated inFIG.10. In some examples, the process1200may be carried out by any suitable apparatus or means for carrying out the functions or algorithms described herein. At block1202, the base station may determine a plurality of first search spaces indicating potential locations for a first downlink control channel or a plurality of second search spaces indicating potential locations for a second downlink control channel or both. In an aspect, each of the plurality of first search spaces may include at least one respective first CCE, and each of the plurality of second search spaces may include at least one respective second CCE. At block1204, the base station may transmit information indicating the plurality of first search spaces, or the plurality of second search spaces, or both to a UE. At block1206, the base station may configure and transmit at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively. At block1208, the base station may configure and transmit at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively. In an aspect, the at least one minimum first delay or the at least one minimum second delay or both may be transmitted via an RRC message. In an aspect, at least one periodicity respectively associated with the at least one first search space may be longer than one slot, and at least one periodicity respectively associated with the at least one second search space may be longer than one slot. In an aspect, each of the at least one minimum first delay may be configured based on a periodicity of a respective first search space of the at least one first search space, and each of the at least one minimum second delay may be configured based on a periodicity of a respective second search space of the at least one second search space. In an aspect, the at least one minimum first delay may cause at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots, and the at least one minimum second delay may cause at least one first downlink control channel detection limit for the second downlink control channel to be over multiple slots. At block1210, the base station may perform additional features, as described below. FIG.12Bis a flow chart illustrating an exemplary process1250(e.g., a method) of wireless communications continuing from the exemplary process1200ofFIG.12A, at the base station in accordance with some aspects of the disclosure. At block1252, the exemplary process1250may continue from the exemplary process1200ofFIG.12A. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process1250may be carried out by the base station1000illustrated inFIG.10. In some examples, the process1250may be carried out by any suitable apparatus or means for carrying out the functions or algorithms described herein. At block1254, the base station may configure a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of the plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. In an aspect, the resource location of the first downlink control channel and the resource location of the downlink data may be a slot location of the first downlink control channel and a slot location of the downlink data, respectively, and the resource location of the first downlink control channel and the resource location of the downlink data may be a slot location of the first downlink control channel and a slot location of the downlink data, respectively. At block1256, the base station may transmit the plurality of first delays or the plurality of second delays or both to a UE. At block1258, the base station may transmit at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel, or the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel. In an aspect, the downlink data may be transmitted at the resource location of the downlink data based on the at least one minimum first delay when a frequency range of the first downlink control channel exceeds a frequency threshold and/or when a subcarrier spacing of the first downlink control channel exceeds a subcarrier spacing threshold. In an aspect, the downlink data may be transmitted at the resource location of the downlink data based on the at least one minimum first delay when a frequency range of the first downlink control channel exceeds a frequency threshold and/or when a subcarrier spacing of the first downlink control channel exceeds a subcarrier spacing threshold. At block1260, the base station may transmit the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. At block1262, the base station may receive the uplink data in the resource location of the uplink data based on a second delay of the plurality of second delays that is configured for the second search space. In one configuration, the base station1000for wireless communication includes means for determining a plurality of first search spaces indicating potential locations for a first downlink control channel or a plurality of second search spaces indicating potential locations for a second downlink control channel or both, means for configuring a plurality of first delays, or a plurality of second delays, or both, and means for transmitting the plurality of first delays or the plurality of second delays or both to a UE. In an aspect, each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of the plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. In an aspect, the base station1000may further include means for transmitting at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel, or the second downlink control channel in a second search space of the plurality of second search spaces that corresponds to the resource location of the second downlink control channel. In an aspect, the base station1000may further include means for transmitting the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. In an aspect, the base station1000may further include means for receiving the uplink data in the resource location of the uplink data based on a second delay of the plurality of second delays that is configured for the second search space. In an aspect, the base station1000may further include means for configuring and transmitting at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively, and/or means for configuring and transmitting at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively. In one aspect, the aforementioned means may be the processor(s)1004shown inFIG.10configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions recited by the aforementioned means. FIG.13is a conceptual diagram illustrating an example of a hardware implementation for an exemplary user equipment1300employing a processing system1314. In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system1314that includes one or more processors1304. For example, the user equipment1300may be a user equipment (UE) as illustrated in any one or more ofFIGS.1,2,3, and/or8. The processing system1314may be substantially the same as the processing system1014illustrated inFIG.10, including a bus interface1308, a bus1302, memory1305, a processor1304, and a processor-readable storage medium1306. Furthermore, the user equipment1300may include a user interface1312and a transceiver1310substantially similar to those described above inFIG.10. That is, the processor1304, as utilized in a user equipment1300, may be used to implement any one or more of the processes described below and illustrated inFIGS.14-15. In some aspects of the disclosure, the processor1304may include communication and processing circuitry1340configured for various functions, including, for example, receiving information indicating a plurality of first search spaces, or a plurality of second search spaces, or both, wherein the plurality of first search spaces indicate potential locations for a first downlink control channel and the plurality of second search spaces indicate potential locations for a second downlink control channel. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIGS.14and15, including, e.g., blocks1402and1502. In some aspects, the communication and processing circuitry1340may be configured to receive a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of a plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIGS.14and15, including, e.g., blocks1404and1574. In some aspects, the communication and processing circuitry1340may be configured to receive at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the at least one minimum first delay, respectively. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1504. In some aspects, the communication and processing circuitry1340may be configured to receive at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the at least one minimum second delay, respectively. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1506. In some aspects, the communication and processing circuitry1340may be configured to receive a minimum first delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the minimum first delay being configured for a BWP. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1508. In some aspects, the communication and processing circuitry1340may be configured to receive a minimum second delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the minimum second delay being configured for the BWP. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1510. In some aspects, the communication and processing circuitry1340may be configured to receive at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel based on the detection for the first downlink control channel, or the second downlink control channel in a second search space of the plurality of second search spaces that corresponds to the resource location of the second downlink control channel based on the detection for the second downlink control channel. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1578. In some aspects, the communication and processing circuitry1340may be configured to receive the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1580. In some aspects, the communication and processing circuitry1340may be configured to transmit the uplink data in the resource location of the uplink data based on the second delay of the plurality of second delays that is configured for the second search space. For example, the communication and processing circuitry1340may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1582. In some aspects of the disclosure, the processor1304may include downlink control channel processing circuitry1342configured for various functions, including, for example, performing at least one of: detection for the first downlink control channel at the plurality of first search spaces respectively based on the plurality of first delays, or detection for the second downlink control channel at the plurality of second search spaces respectively based on the plurality of second delays. For example, the downlink control channel processing circuitry1342may be configured to implement one or more of the functions described below in relation toFIGS.14and15, including, e.g., blocks1406and1576. In some aspects, the downlink control channel processing circuitry1342may be configured, in response to receiving the at least one minimum first delay configured for the at least one first search space, to determine at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the first downlink control channel detection limit over a first plurality of slots. For example, the downlink control channel processing circuitry1342may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1544. In some aspects, the downlink control channel processing circuitry1342may be configured, in response to receiving the at least one minimum second delay configured for the at least one second search space, to determine at least one second downlink control channel detection limit for the second downlink control channel to be over multiple slots, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the second downlink control channel detection limit over a second plurality of slots. For example, the downlink control channel processing circuitry1342may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1546. In some aspects, the downlink control channel processing circuitry1342may be configured to determine a first downlink control channel detection limit for the first downlink control channel to be over multiple slots if a corresponding one of the least one minimum first delay is less than or equal to a limit threshold. For example, the downlink control channel processing circuitry1342may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1548. In some aspects, the downlink control channel processing circuitry1342may be configured to determine the first downlink control channel detection limit for the first downlink control channel to be over a single slot if a corresponding one of the least one minimum first delay exceeds the limit threshold. For example, the downlink control channel processing circuitry1342may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1550. In some aspects, the downlink control channel processing circuitry1342may be configured to determine a second downlink control channel detection limit for the second downlink control channel to be over multiple slots if a corresponding one of the least one minimum second delay is less than or equal to a limit threshold. For example, the downlink control channel processing circuitry1342may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1552. In some aspects, the downlink control channel processing circuitry1342may be configured to determine the second downlink control channel detection limit for the second downlink control channel to be over a single slot if a corresponding one of the least one minimum second delay exceeds the limit threshold. For example, the downlink control channel processing circuitry1342may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1554. The processor1304is responsible for managing the bus1302and general processing, including the execution of software stored on the processor-readable storage medium1306. The software, when executed by the processor1304, causes the processing system1314to perform the various functions described below for any particular apparatus. The processor-readable storage medium1306and the memory1305may also be used for storing data that is manipulated by the processor1304when executing software. One or more processors1304in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a processor-readable storage medium1306. The processor-readable storage medium1306may be a non-transitory processor-readable storage medium. A non-transitory processor-readable storage medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a smart card, a flash memory device (e.g., a card, a stick, or a key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. The processor-readable storage medium1306may reside in the processing system1314, external to the processing system1314, or distributed across multiple entities including the processing system1314. The processor-readable storage medium1306may be embodied in a computer program product. By way of example, a computer program product may include a processor-readable storage medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system. In one or more examples, the processor-readable storage medium1306may include communication and processing software/instructions1350configured for various functions, including, for example, receiving information indicating a plurality of first search spaces, or a plurality of second search spaces, or both, wherein the plurality of first search spaces indicate potential locations for a first downlink control channel and the plurality of second search spaces indicate potential locations for a second downlink control channel. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIGS.14and15, including, e.g., blocks1402and1502. In some aspects, the communication and processing software/instructions1350may be configured to receive a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of a plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIGS.14and15, including, e.g., blocks1404and1574. In some aspects, the communication and processing software/instructions1350may be configured to receive at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the at least one minimum first delay, respectively. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1504. In some aspects, the communication and processing software/instructions1350may be configured to receive at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the at least one minimum second delay, respectively. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1506. In some aspects, the communication and processing software/instructions1350may be configured to receive a minimum first delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the minimum first delay being configured for a BWP. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1508. In some aspects, the communication and processing software/instructions1350may be configured to receive a minimum second delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the minimum second delay being configured for the BWP. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1510. In some aspects, the communication and processing software/instructions1350may be configured to receive at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel based on the detection for the first downlink control channel, or the second downlink control channel in a second search space of the plurality of second search spaces that corresponds to the resource location of the second downlink control channel based on the detection for the second downlink control channel. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1578. In some aspects, the communication and processing software/instructions1350may be configured to receive the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1580. In some aspects, the communication and processing software/instructions1350may be configured to transmit the uplink data in the resource location of the uplink data based on the second delay of the plurality of second delays that is configured for the second search space. For example, the communication and processing software/instructions1350may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1582. In one or more examples, the processor-readable storage medium1306may include downlink control channel processing software/instructions1352configured for various functions, including, for example, performing at least one of: detection for the first downlink control channel at the plurality of first search spaces respectively based on the plurality of first delays, or detection for the second downlink control channel at the plurality of second search spaces respectively based on the plurality of second delays. For example, the downlink control channel processing software/instructions1352may be configured to implement one or more of the functions described below in relation toFIGS.14and15, including, e.g., blocks1406and1576. In some aspects, the downlink control channel processing software/instructions1352may be configured, in response to receiving the at least one minimum first delay configured for the at least one first search space, to determine at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the first downlink control channel detection limit over a first plurality of slots. For example, the downlink control channel processing software/instructions1352may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1544. In some aspects, the downlink control channel processing software/instructions1352may be configured, in response to receiving the at least one minimum second delay configured for the at least one second search space, to determine at least one second downlink control channel detection limit for the second downlink control channel to be over multiple slots, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the second downlink control channel detection limit over a second plurality of slots. For example, the downlink control channel processing software/instructions1352may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1546. In some aspects, the downlink control channel processing software/instructions1352may be configured to determine a first downlink control channel detection limit for the first downlink control channel to be over multiple slots if a corresponding one of the least one minimum first delay is less than or equal to a limit threshold. For example, the downlink control channel processing software/instructions1352may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1548. In some aspects, the downlink control channel processing software/instructions1352may be configured to determine the first downlink control channel detection limit for the first downlink control channel to be over a single slot if a corresponding one of the least one minimum first delay exceeds the limit threshold. For example, the downlink control channel processing software/instructions1352may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1550. In some aspects, the downlink control channel processing software/instructions1352may be configured to determine a second downlink control channel detection limit for the second downlink control channel to be over multiple slots if a corresponding one of the least one minimum second delay is less than or equal to a limit threshold. For example, the downlink control channel processing software/instructions1352may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1552. In some aspects, the downlink control channel processing software/instructions1352may be configured to determine the second downlink control channel detection limit for the second downlink control channel to be over a single slot if a corresponding one of the least one minimum second delay exceeds the limit threshold. For example, the downlink control channel processing software/instructions1352may be configured to implement one or more of the functions described below in relation toFIG.15, including, e.g., block1554. FIG.14is a flow chart illustrating an exemplary process1400(e.g., a method) of wireless communications, at a UE in accordance with some aspects of the disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process1400may be carried out by the user equipment1300illustrated inFIG.13. In some examples, the process1400may be carried out by any suitable apparatus or means for carrying out the functions or algorithms described herein. At1402, the UE may receive information indicating a plurality of first search spaces, or a plurality of second search spaces, or both, wherein the plurality of first search spaces indicate potential locations for a first downlink control channel and the plurality of second search spaces indicate potential locations for a second downlink control channel. At1404, the UE may receive a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of a plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. At1406, the UE may perform at least one of: detection for the first downlink control channel at the plurality of first search spaces respectively based on the plurality of first delays, or detection for the second downlink control channel at the plurality of second search spaces respectively based on the plurality of second delays. FIG.15Ais a flow chart illustrating an exemplary process1500(e.g., a method) of wireless communications, at a UE in accordance with some aspects of the disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process1500may be carried out by the user equipment1300illustrated inFIG.13. In some examples, the process1500may be carried out by any suitable apparatus or means for carrying out the functions or algorithms described herein. At1502, the UE may receive information indicating a plurality of first search spaces, or a plurality of second search spaces, or both, wherein the plurality of first search spaces indicate potential locations for a first downlink control channel and the plurality of second search spaces indicate potential locations for a second downlink control channel. In an aspect, each of the plurality of first search spaces may include at least one respective first CCE, and each of the plurality of second search spaces may include at least one respective second CCE. At1504, the UE may receive at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the at least one minimum first delay, respectively. At1506, the UE may receive at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the at least one minimum second delay, respectively. In an aspect, the at least one minimum first delay or the at least one minimum second delay or both may be received via an RRC message. In an aspect, at least one periodicity respectively associated with the at least one first search space may be longer than one slot, and at least one periodicity respectively associated with the at least one second search space may be longer than one slot. In an aspect, each of the at least one minimum first delay may be configured based on a periodicity of a respective first search space of the at least one first search space, and each of the at least one minimum second delay may be configured based on a periodicity of a respective second search space of the at least one second search space. At1508, the UE may receive a minimum first delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the minimum first delay being configured for a BWP. In an aspect, the detection for the first downlink control channel may be performed at the at least one first search space based on the at least one minimum first delay while ignoring the minimum first delay configured for the BWP At1510, the UE may receive a minimum second delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the minimum second delay being configured for the BWP. In an aspect, the detection for the second downlink control channel may be performed at the at least one second search space based on the at least one minimum second delay while ignoring the minimum second delay configured for the BWP. At1512, the UE may perform additional features, as described below. FIG.15Bis a flow chart illustrating an exemplary process1540(e.g., a method) of wireless communications continuing from the exemplary process ofFIG.15A, at the UE in accordance with some aspects of the disclosure. At block1542, the exemplary process1540may continue from the exemplary process1500ofFIG.15A. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process1540may be carried out by the user equipment1300illustrated inFIG.13. In some examples, the process1540may be carried out by any suitable apparatus or means for carrying out the functions or algorithms described herein. At1544, the UE may, in response to receiving the at least one minimum first delay configured for the at least one first search space, determine at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the first downlink control channel detection limit over a first plurality of slots. At1546, the UE may, in response to receiving the at least one minimum second delay configured for the at least one second search space, determine at least one second downlink control channel detection limit for the second downlink control channel to be over multiple slots, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the second downlink control channel detection limit over a second plurality of slots. At1548, the UE may determine a first downlink control channel detection limit for the first downlink control channel to be over multiple slots if a corresponding one of the least one minimum first delay is less than or equal to a limit threshold. At1550, the UE may determine the first downlink control channel detection limit for the first downlink control channel to be over a single slot if a corresponding one of the least one minimum first delay exceeds the limit threshold. At1552, the UE may determine a second downlink control channel detection limit for the second downlink control channel to be over multiple slots if a corresponding one of the least one minimum second delay is less than or equal to a limit threshold. At1554, the UE may determine the second downlink control channel detection limit for the second downlink control channel to be over a single slot if a corresponding one of the least one minimum second delay exceeds the limit threshold. At1556, the UE may perform additional features, as described below. FIG.15Cis a flow chart illustrating an exemplary process1570(e.g., a method) of wireless communications continuing from the exemplary process ofFIG.15B, at the UE in accordance with some aspects of the disclosure. At block1572, the exemplary process1570may continue from the exemplary process1540ofFIG.15B. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process1570may be carried out by the user equipment1300illustrated inFIG.13. In some examples, the process1570may be carried out by any suitable apparatus or means for carrying out the functions or algorithms described herein. At1574, the UE may receive a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of a plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. In an aspect, the resource location of the first downlink control channel and the resource location of the downlink data may be a slot location of the first downlink control channel and a slot location of the downlink data, respectively, and the resource location of the second downlink control channel and the resource location of the uplink data may be a slot location of the second downlink control channel and a slot location of the uplink data, respectively. In an aspect, the downlink data may be received at the resource location of the downlink data based on the at least one minimum first delay when a frequency range of the first downlink control channel exceeds a frequency threshold and/or when a subcarrier spacing of the first downlink control channel exceeds a subcarrier spacing threshold, and the uplink data may be transmitted at the resource location of the uplink data based on the at least one minimum second delay when a frequency range of the second downlink control channel exceeds the frequency threshold and/or when a subcarrier spacing of the second downlink control channel exceeds the subcarrier spacing threshold. At1576, the UE may perform at least one of: detection for the first downlink control channel at the plurality of first search spaces respectively based on the plurality of first delays, or detection for the second downlink control channel at the plurality of second search spaces respectively based on the plurality of second delays. At1578, the UE may receive at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel based on the detection for the first downlink control channel, or the second downlink control channel in a second search space of the plurality of second search spaces that corresponds to the resource location of the second downlink control channel based on the detection for the second downlink control channel. At1580, the UE may receive the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. At1582, the UE may transmit the uplink data in the resource location of the uplink data based on the second delay of the plurality of second delays that is configured for the second search space. In one configuration, the UE1300for wireless communication includes means for receiving information indicating a plurality of first search spaces, or a plurality of second search spaces, or both, wherein the plurality of first search spaces indicate potential locations for a first downlink control channel and the plurality of second search spaces indicate potential locations for a second downlink control channel, means for receiving a plurality of first delays, or a plurality of second delays, or both, and means for performing at least one of detection for the first downlink control channel at the plurality of first search spaces respectively based on the plurality of first delays, or detection for the second downlink control channel at the plurality of second search spaces respectively based on the plurality of second delays. In an aspect, each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of a plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces. In an aspect, the UE1300may further include means for receiving at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel based on the detection for the first downlink control channel, or the second downlink control channel in a second search space of the plurality of second search spaces that corresponds to the resource location of the second downlink control channel based on the detection for the second downlink control channel. In an aspect, the UE1300may further include means for receiving the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. In an aspect, the UE1300may further include means for transmitting the uplink data in the resource location of the uplink data based on the second delay of the plurality of second delays that is configured for the second search space. In an aspect, the UE1300may further include means for receiving at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the at least one minimum first delay, respectively, and/or means for receiving at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the at least one minimum second delay, respectively. In an aspect, the UE1300may further include means for receiving a minimum first delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the minimum first delay being configured for a BWP, wherein the detection for the first downlink control channel is performed at the at least one first search space based on the at least one minimum first delay while ignoring the minimum first delay configured for the BWP, and/or means for receiving a minimum second delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the minimum second delay being configured for the BWP, wherein the detection for the second downlink control channel is performed at the at least one second search space based on the at least one minimum second delay while ignoring the minimum second delay configured for the BWP. In an aspect, the UE1300may further include means for determining, in response to receiving the at least one minimum first delay configured for the at least one first search space, at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the first downlink control channel detection limit over a first plurality of slots, and/or means for determining, in response to receiving the at least one minimum second delay configured for the at least one second search space, at least one second downlink control channel detection limit for the second downlink control channel to be over multiple slots, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the second downlink control channel detection limit over a second plurality of slots. In an aspect, the UE1300may further include means for determining a first downlink control channel detection limit for the first downlink control channel to be over a single slot if a corresponding one of the least one minimum first delay is less than or equal to a limit threshold, and means for determining the first downlink control channel detection limit for the first downlink control channel to be over multiple slots if a corresponding one of the least one minimum first delay exceeds the limit threshold. In an aspect, the UE1300may further include means for determining a second downlink control channel detection limit for the second downlink control channel to be over a single slot if a corresponding one of the least one minimum second delay is less than or equal to a limit threshold, and means for determining the second downlink control channel detection limit for the second downlink control channel to be over multiple slots if a corresponding one of the least one minimum second delay exceeds the limit threshold. In one aspect, the aforementioned means may be the processor(s)1304shown inFIG.13configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions recited by the aforementioned means. Of course, in the above examples, the circuitry included in the processor1004and/or1304is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the processor-readable storage medium1006and/or1306, or any other suitable apparatus or means described in any one of theFIGS.1,2,3,10and/or13, and utilizing, for example, the processes and/or algorithms described herein in relation toFIGS.11-12and/orFIGS.14-15. The following provides an overview of several aspects of the present disclosure. Aspect 1: A method of wireless communication by a base station, comprising: determining a plurality of first search spaces indicating potential locations for a first downlink control channel or a plurality of second search spaces indicating potential locations for a second downlink control channel or both; configuring a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of the plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces; and transmitting the plurality of first delays or the plurality of second delays or both to a user equipment (UE). Aspect 2: The method of aspect 1, further comprising: transmitting at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel, or the second downlink control channel in a second search space of the plurality of second search spaces that corresponds to the resource location of the second downlink control channel. Aspect 3: The method of aspect 2, further comprising: transmitting the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. Aspect 4: The method of aspect 2 or 3, further comprising: receiving the uplink data in the resource location of the uplink data based on a second delay of the plurality of second delays that is configured for the second search space. Aspect 5: The method of any of aspects 1 through 4, wherein the plurality of first delays are transmitted via first downlink control information on the first downlink control channel, and/or wherein the plurality of second delays are transmitted via second downlink control information on the second downlink control channel. Aspect 6: The method of any of aspects 1 through 5, further comprising at least one of: configuring and transmitting at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively; or configuring and transmitting at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively. Aspect 7: The method of aspect 6, wherein the at least one minimum first delay or the at least one minimum second delay or both are transmitted via a radio resource control (RRC) message. Aspect 8: The method of aspect 6 or 7, wherein at least one periodicity respectively associated with the at least one first search space is longer than one slot, and at least one periodicity respectively associated with the at least one second search space is longer than one slot. Aspect 9: The method of any of aspects 6 through 8, wherein each of the at least one minimum first delay is configured based on a periodicity of a respective first search space of the at least one first search space, and each of the at least one minimum second delay is configured based on a periodicity of a respective second search space of the at least one second search space. Aspect 10: The method of any of aspects 6 through 9, wherein the at least one minimum first delay causes at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots, and the at least one minimum second delay causes at least one first downlink control channel detection limit for the second downlink control channel to be over multiple slots. Aspect 11: The method of any of aspects 6 through 10, wherein the downlink data is transmitted at the resource location of the downlink data based on the at least one minimum first delay when a frequency range of the first downlink control channel exceeds a frequency threshold and/or when a subcarrier spacing of the first downlink control channel exceeds a subcarrier spacing threshold, and wherein the uplink data is received at the resource location of the uplink data based on the at least one minimum second delay when a frequency range of the second downlink control channel exceeds the frequency threshold and/or when a subcarrier spacing of the second downlink control channel exceeds the subcarrier spacing threshold. Aspect 12: The method of any of aspects 1 through 11, wherein each of the plurality of first search spaces includes at least one respective first control channel element (CCE), and each of the plurality of second search spaces includes at least one respective second CCE. Aspect 13: The method of any of aspects 1 through 12, wherein the resource location of the first downlink control channel and the resource location of the downlink data are a slot location of the first downlink control channel and a slot location of the downlink data, respectively, and wherein the resource location of the second downlink control channel and the resource location of the uplink data are a slot location of the second downlink control channel and a slot location of the uplink data, respectively. Aspect 14: A base station comprising: a transceiver configured to communicate with a radio access network, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 1 through 13. Aspect 15: A base station configured for wireless communication comprising at least one means for performing any one of aspects 1 through 13. Aspect 16: A non-transitory processor-readable storage medium having instructions for a base station thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform any one of aspects 1 through 13. Aspect 17: A method of wireless communication by a user equipment (UE), comprising: receiving information indicating a plurality of first search spaces, or a plurality of second search spaces, or both, wherein the plurality of first search spaces indicate potential locations for a first downlink control channel and the plurality of second search spaces indicate potential locations for a second downlink control channel; receiving a plurality of first delays, or a plurality of second delays, or both, wherein each first delay indicates a respective time delay between a resource location of the first downlink control channel and a resource location of a downlink data associated with the first downlink control channel and is configured for a respective first search space of a plurality of first search spaces, and each second delay indicates a respective time delay between a resource location of the second downlink control channel and a resource location of an uplink data associated with the second downlink control channel and is configured for a respective second search space of the plurality of second search spaces; and performing at least one of: detection for the first downlink control channel at the plurality of first search spaces respectively based on the plurality of first delays, or detection for the second downlink control channel at the plurality of second search spaces respectively based on the plurality of second delays. Aspect 18: The method of aspect 17, further comprising: receiving at least one of: the first downlink control channel in a first search space of the plurality of first search spaces that corresponds to the resource location of the first downlink control channel based on the detection for the first downlink control channel, or the second downlink control channel in a second search space of the plurality of second search spaces that corresponds to the resource location of the second downlink control channel based on the detection for the second downlink control channel. Aspect 19: The method of aspect 18, further comprising: receiving the downlink data in the resource location of the downlink data based on a first delay of the plurality of first delays that is configured for the first search space. Aspect 20: The method of aspect 18 or 19, further comprising: transmitting the uplink data in the resource location of the uplink data based on the second delay of the plurality of second delays that is configured for the second search space. Aspect 21: The method of any of aspects 17 through 20, wherein the plurality of first delays are received via first downlink control information on the first downlink control channel, and/or wherein the plurality of second delays are received via second downlink control information on the second downlink control channel. Aspect 22: The method of any of aspects 17 through 21, further comprising at least one of: receiving at least one minimum first delay, each indicating a minimum time delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the at least one minimum first delay configured for at least one first search space of the plurality of first search spaces, respectively, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the at least one minimum first delay, respectively; or receiving at least one minimum second delay, each indicating a minimum time delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the at least one minimum second delay configured for at least one second search space of the plurality of second search spaces, respectively, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the at least one minimum second delay, respectively. Aspect 23: The method of aspect 22, wherein the at least one minimum first delay or the at least one minimum second delay or both are received via a radio resource control (RRC) message. Aspect 24: The method of aspect 22 or 23, further comprising at least one of: receiving a minimum first delay between the resource location of the first downlink control channel and the resource location of the downlink data associated with the first downlink control channel, the minimum first delay being configured for a bandwidth part (BWP), wherein the detection for the first downlink control channel is performed at the at least one first search space based on the at least one minimum first delay while ignoring the minimum first delay configured for the BWP; or receiving a minimum second delay between the resource location of the second downlink control channel and the resource location of the uplink data associated with the second downlink control channel, the minimum second delay being configured for the BWP, wherein the detection for the second downlink control channel is performed at the at least one second search space based on the at least one minimum second delay while ignoring the minimum second delay configured for the BWP. Aspect 25: The method of any of aspects 22 through 24, wherein at least one periodicity respectively associated with the at least one first search space is longer than one slot, and at least one periodicity respectively associated with the at least one second search space is longer than one slot. Aspect 26: The method of any of aspects 22 through 25, further comprising at least one of: in response to receiving the at least one minimum first delay configured for the at least one first search space, determining at least one first downlink control channel detection limit for the first downlink control channel to be over multiple slots, wherein the detection for the first downlink control channel is performed at the at least one first search space further based on the first downlink control channel detection limit over a first plurality of slots; or in response to receiving the at least one minimum second delay configured for the at least one second search space, determining at least one second downlink control channel detection limit for the second downlink control channel to be over multiple slots, wherein the detection for the second downlink control channel is performed at the at least one second search space further based on the second downlink control channel detection limit over a second plurality of slots. Aspect 27: The method of any of aspects 22 through 26, further comprising: determining a first downlink control channel detection limit for the first downlink control channel to be over a single slot if a corresponding one of the least one minimum first delay is less than or equal to a limit threshold; and determining the first downlink control channel detection limit for the first downlink control channel to be over multiple slots if a corresponding one of the least one minimum first delay exceeds the limit threshold. Aspect 28: The method of any of aspects 22 through 27, further comprising: determining a second downlink control channel detection limit for the second downlink control channel to be over a single slot if a corresponding one of the least one minimum second delay is less than or equal to a limit threshold; and determining the second downlink control channel detection limit for the second downlink control channel to be over multiple slots if a corresponding one of the least one minimum second delay exceeds the limit threshold. Aspect 29: The method of any of aspects 22 through 28, wherein each of the at least one minimum first delay is configured based on a periodicity of a respective first search space of the at least one first search space, and each of the at least one minimum second delay is configured based on a periodicity of a respective second search space of the at least one second search space. Aspect 30: The method of any of aspects 22 through 29, wherein the downlink data is received at the resource location of the downlink data based on the at least one minimum first delay when a frequency range of the first downlink control channel exceeds a frequency threshold and/or when a subcarrier spacing of the first downlink control channel exceeds a subcarrier spacing threshold, and wherein the uplink data is transmitted at the resource location of the uplink data based on the at least one minimum second delay when a frequency range of the second downlink control channel exceeds the frequency threshold and/or when a subcarrier spacing of the second downlink control channel exceeds the subcarrier spacing threshold. Aspect 31: The method of any of aspects 17 through 30, wherein each of the plurality of first search spaces includes at least one respective first control channel element (CCE), and each of the plurality of second search spaces includes at least one respective second CCE. Aspect 32: The method of any of aspects 17 through 31, wherein the resource location of the first downlink control channel and the resource location of the downlink data are a slot location of the first downlink control channel and a slot location of the downlink data, respectively, and wherein the resource location of the second downlink control channel and the resource location of the uplink data are a slot location of the second downlink control channel and a slot location of the uplink data, respectively. Aspect 33: A user equipment (UE) comprising: a transceiver configured to communicate with a radio access network, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform any one of aspects 17 through 32. Aspect 34: A UE configured for wireless communication comprising at least one means for performing any one of aspects 17 through 32. Aspect 35: A non-transitory processor-readable storage medium having instructions for a UE thereon, wherein the instructions, when executed by a processing circuit, cause the processing circuit to perform any one of aspects 17 through 32. Several aspects of a wireless communication network have been presented with reference to an exemplary implementation. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards. By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE), the Evolved Packet System (EPS), the Universal Mobile Telecommunication System (UMTS), and/or the Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA 2000 and/or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and/or other suitable systems. The actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system. Within the present disclosure, the word “exemplary” is used to mean “serving as an example, instance, or illustration.” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another—even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object. The terms “circuit” and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure. One or more of the components, steps, features and/or functions illustrated inFIGS.1-15may be rearranged and/or combined into a single component, step, feature, or function or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from novel features disclosed herein. The apparatus, devices, and/or components illustrated inFIGS.1-15may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware. It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” | 185,911 |
11943731 | DETAILED DESCRIPTION According to one aspect of the invention an architecture is provided as depicted inFIG.5. The 5G Fixed Mobile Interworking Function, FMIF, is connected with a database, FMIF-DB. The FMIF may also be referred to as a 5G Access Gateway Function (FAGF). The FMIF-DB stores in some embodiments of the invention: 1. UE credentials. Identity of the UE and credentials for proving the identity (e.g., a pre-shared key or certificate), typically indexed by existing practice such as circuit ID. 2. UE configuration data. Normally stored in USIM/UE but since this is a legacy FN-RG, there is no support to store this data in the UE. 3. UE dynamic data. All data normally received by a UE from the network, which it stores for future use. Examples could be 5G-GUTI, forbidden tracking areas, back off time etc. An Operations support system, OSS, can also be integrated with the FMIF-DB so that when an operator configures a new subscription, the UE UICC data can be stored in the FMIF-DB. According to still further embodiments of the invention there is provided a system as shown onFIG.6comprising a Provisioning Service Node20, coupled to a FMIF-DB10, a Unified Data Management, UDM,21and a Certificate Authority, CA,22, respectively. The provisioning service is a logical node that can carry out the task to setup a new subscription for a FN-RG. FMIF-DB is explained earlier. UDM is the Unified Data Management node as defined in 23.501 (this could also be a UDR as defined in same document). CA is a Certificate Authority node that can sign new certificates that are trusted by the network. Client certificates will be used if using EAP-TLS (Extensible Authentication Protocol-Transport Layer Security) to authenticate the UE (FN-RG) identity and is an example for credentials that can be used. Another possible credential could be to use username/password. InFIG.7, a procedure for theFIG.6system is shown. TheFIG.7procedure may be carried out initially and only once for a given 5G-RG. 71. An actor19(e.g. an operator) decides to create a new subscription for a certain circuit identity and the applicable subscription parameters are passed to the provisioning service node. Create user (circuit_id, subscription parameters) is transmitted to the provisioning service node20. 72. The provisioning service node20creates the UE subscription, which primarily is a set of subscription data for the FN-RG/circuit identity. 73. Optional steps: requesting and receiving a FN-RG certificate from a CA.73a. CSR enrol request (identity, CSR) is issued to CA.73b. CSR enrol answer (certificate) is responded with. 74. The provisioning service node sends request to UDM (Unified Data Management)/UDR (Unified Data Repository) to create subscription data/policy data for the FN-RG7.74a. Provisioning service node20sends a Create user request (identity, subscription parameters) to UDM/UDR.74b. UDM/UDR creates UE profile. 75. The provisioning service node20sends a request to FMIF-DB10to setup UE credential and configuration data for FN-RG7. Message75a. may take the form Create user request (identity, certificate, UE configuration data).75b. FMIF-DB entry is created for UE.75c. A Create user response is transmitted back to the provisioning service node20. 76. A response—Create user response—is transmitted back to actor19. InFIG.8, a call-flow is shown for an IPoE embodiment of the invention making use of theFIG.5architecture. IPoE relies on Dynamic Host Configuration Protocol (DHCP) to provide many of the capabilities provided by Point-to-Point Protocol over Ethernet (PPPoE). Steps83,84,88and89are novel steps. When FN-RG,7, attach to FMIF/5GC,9, the request/response map a circuit id with a set of UE parameters:PLMN identity to be preferred as serving PLMN identityidentity which could be a SUPI (SUbscription Permanent Identifier), SUCI (SUbscription Concealed Identifier) or 5G-GUTI (Globally Unique Temporary Identity) if the FN-RG has been registered to 5GC.Credentials which could be a pre-shared key and/or a certificate to be used for EAP-TLS to prove the FN-RG identity (e.g., SUPI).AS/NAS keys if there is already AS/NAS security contexts for the FN-RGOther parameters applicable for the FN-RG to be able to register to 5GC like UE 5G capabilities, requested NSSAI (Network Slice Selection Assistance Information), list of PDU sessions to be activated, MICO (Mobile Initiated Connection Only) mode preferences, requested DRX (Discontinuous Reception), parameters. All these parameters are described in 23.501 and 23.502. Step85and86will use the parameters received by FMIF in step83. At step88, FMIF update the FMIF-DB with the dynamic data received during step85and86. This could include:5G-GUTI i.e., a temporary identity for the UE which could be used for quicker re-registration and to come back to CM_CONNECTED mode if the FN-RG has been for some reason put to CM_IDLE mode.AS/NAS keys for the security contextsRegistration areaMobility restrictionsPDU session statusNSSAI value (allowed, mapping of allowed NSSAI, configured NSSAI for the serving PLMN)LADN informationAccepted MICO modeIMS voice over PS session supported indicatorAccepted DRX parameters Parameters are described in 23.501 and 23.502. The following signalling is provided over the nodes shown designated by their reference signs: 81. DHCP DISCOVER—FN-RG7to AN8 82. DHCP DISCOVER [CIRCUIT ID]—AN8-FMIF9 83. REQUEST [CIRCUIT ID]—FMIF9-FMIF DB10 84. RESPONSE [PLMN, IDENTITIES (SUPI, SUCI, 5G-GUTI), CREDENTIALS, AS/NAS KEYS, OTHER PARAMETERS]—FMIF DB10-FMIF9 85. NAS REGISTRATION PROCEDURES, between FMIF9, FMIF DB10,11 86. PDU SESSION INITIATION PROCEDURES between FMIF9, FMIF DB10,11 87. STATELESS DHCP PROCEDURES (TO SMF/UPF) between FMIF9, FMIF DB10,11 88. STORE REQUEST [CIRCUIT ID, 5G-GUTI, AS/NAS KEYS], FMIF9-FMIF DB10 810. DHCP OFFER, FMIF9-FN-RG7 811. DHCP REQUEST, FN-RG7-FMIF9 812. DHCP ACK, FMIF9-FN-RG7 813. SESSION TRAFFIC FN-RG7-AN8-FMIF9-FMIF DB10-AMF14 Nodes9FMIF and10FMIF-DB may in still other embodiments be combined in a combined node C-FMIF-DB12. InFIG.9an embodiment for a call-flow for a PPPoE solution is shown. Step92,93,910and911are novel steps and are identical to steps83,84,88and89inFIG.8. The only difference in this figure is that PPPoE is used between FN-RG and FMIF. PPPoE procedures do not offer an IP address as part of the initial solicitation, so the PPPoE PADR is obtained without needing to engage the 5GC (AMF) system (this would correspond to FMIF selection if there was more than 1). There is no need to perform session initiation until the FN-RG attempts to get an IPv4 or IPv6 address (open an NCP in step8). TheFIG.8embodiment is work conserving in relation to DHCP where there is a need to offer an address before the client picks the offer the client will accept. The following signalling is provided over the shown nodes designated by their reference signs: 91A. PPPOE PADI, FN-RG7-FMIF9 91B. PPPOE PADI [LINE ID], AN8-FMIF9 91C. PPPOE PADO, FMIF9-AN8 91D. PPPOE PADO, AN8-FN-RG7 91E. PPPOE PADR, FN-RG7-AN8 91F. PPPOE PADR, AN8-FMIF9 92. REQUEST [LINE ID], FMIF9-FMIF DB10 93. RESPONSE [PLMN . . . ], FMIF DB10-FMIF9 94. REGISTRATION PROCEDURES 95A. PPPOE PADS, FMIF9-AN8 95B. PPPOE PADS, AN8-FN-RG7 96. LCP PROCEDURES 97. PAP/CHAP/EAP PROCEDURES 98. OPEN NCP (IPCP), FN-RG7-FMIF9 99. PDU SESSION INITIATION 910. STORE REQUEST [SESSION DETAILS], FN-RG7-FMIF9-FMIF DB10 911. ACK, FMIF DB10-FMIF9 912. NCP ACK [IP ADDRESS], FMIF9-FN-RG7 913SESSION TRAFFIC, FN-RG7-AN8-FMIF9-FMIF DB10-AMF14. Nodes9FMIF and10FMIF-DB may in still other embodiments be combined in a combined node C-FMIF-DB12. InFIG.10, there is shown a user equipment, FN-RG7, apparatus according to an embodiment of the invention. The UE comprises a processor PCU_FG an interface IF_UE and a memory, MEM_FG, in which memory instructions are stored for carrying out the method steps explained above. The FN-RG7communicates via the interface IF_FG. The IF_FG comprises both an external interface, communicating with a transmitter and receiver, and internal interfaces (not shown). There is also shown an AN8comprising a processor PCU_A, an interface IF_A; and a memory, MEM_A. Instructions are stored in the memory for being performed by the processor such that the method steps explained above are carried out and signalling is communicated on the interface. Further, a FMIF9is provided comprising a processor PCU_M, an interface IF_M; and a memory, MEM_M. Instructions are stored in the memory for being performed by the processor such that the method steps explained above are carried out and signalling is communicated on the interface. Moreover, a FMIF-DB10is provided comprising a processor PCU_B, an interface IF_B; and a memory, MEM_B. Instructions are stored in the memory for being performed by the processor such that the method steps explained above are carried out and signalling is communicated on the interface. InFIG.10, there is moreover shown an Access and Mobility Management Function, AMF,14comprising a processor PCU_AM, an interface IF_AM; and a memory, MEM_AM. Instructions are stored in the memory for being performed by the processor such that the method steps explained above are carried out and signalling is communicated on the interface. Also, a Provisioning Service Node20is shown comprising a processor PCU_P, an interface IF_P; and a memory, MEM_P. Instructions are stored in the memory for being performed by the processor such that the method steps explained above are carried out and signalling is communicated on the interface. Finally, a UDM/UDR21is provided comprising a processor PCU_U an interface IF_U; and a memory, MEM_U. Instructions are stored in the memory for being performed by the processor such that the method steps explained above are carried out and such that corresponding signalling is effectuated on the interface. According to embodiments of the invention systems and apparatuses are disclosed: A 5G Fixed Mobile Interworking Function Database entity, FMIF-DB,10in a system comprising a Wireline 5G Access Network, W-5GAN, connecting to a Fixed Network Residential Gateway, FN-RG,7, the W-5GAN comprising a Wireline Access Node, AN,8and a 5G Fixed Mobile Interworking Function, FMIF,9, the FMIF9connecting to Ac-cess and Mobility Management Function, AMF,14and to an User Plane Function, UPF,13and the FMIF DN10, the wireline Access Node8, coupling to a Fixed Network Residential Gateway, FN-RG7providing services such as TV, Internet and voice, the database apparatus10being adapted for holdingUser entity, UE, credentials for providing an identity of an FN-RG7as a User Entity, UE, andUE configuration data for the FN-RG7. A Database is further provided moreover adapted for holdingUE dynamic data, such as 5G GUTI. A Provisioning service entity20is a provided in a system comprising a data base entity10, a UDM21and a Certificate Authority, CA22, the provisioning service entity20being adapted forreceiving a create user message71from an actor19such as an operator,creating72a subscription for a Fixed Network Residential Gateway, FN-RG,7, identity in the provisioning service entity20,issuing74A a request to UDM, Unified Data Management/UDR, Unified Data Repository,21to setup UE credential and configuration,issuing75A request to 5G Fixed Mobile Interworking Function Database, FMIF-DB10to setup UE credential and configuration data for FN-RG7. The provisioning service entity20may be configured such that, upon an FMIF-DB10entry is created for the UE, andreceiving75C a create user response message from the FMIF DB10,transmitting a Create User Response to the actor19. The provisioning service entity20may moreover being adapted for connecting to a Certificate Authority, CA, wherein the provisioning service entity mayrequest73A a FN-RG certificate from a CA,receive73B a FN-RG certificate from a CA. A 5G Fixed Mobile Interworking Function Database entity, FMIF,9adapted for communicating with a 5G Fixed Mobile Interworking Function Database entity database, FMIF-DB10, the FMIF moreover being adapted for communicating with a Wireline Access Node, AN,8and an Access and Mobility Management Function, AMF14, the FMIF being further adapted for uponreceiving82a Dynamic Host Configuration Protocol, DHCP, discover message from the AN comprising a circuit ID,issuing83a request for a circuit identity, ID,performing85,86,87NAS procedures with the AMF,issuing88a store request message to the FMIF-DB,receiving89a response from the FMIF-DB. FMIF according to claim7wherein, a DHCP offer is issued to a Fixed Network Residential Gateway, FN-RG,7. The above apparatuses/entities are adapted to communicate over known external telecom interfaces or via application programming interfaces, API, as appropriate. According to embodiments of the invention the following methods are disclosed. Method fora 5G Fixed Mobile Interworking Function Database entity, FMIF-DB,10in a system comprising a Wireline 5G Access Network, W-5GAN, connecting to a Fixed Net-work Residential Gateway, FN-RG,7, the W-5GAN comprising a Wireline Access Node, AN,8and a 5G Fixed Mobile Interworking Function, FMIF,9, the FMIF9connecting to Ac-cess and Mobility Management Function, AMF,14and to an User Plane Function, UPF,13and the FMIF DN10, the wireline Access Node8, coupling to a Fixed Net-work Residential Gateway, FN-RG7providing services such as TV, Internet and voice, the database apparatus10being adapted for holdingUser entity, UE, credentials for providing an identity of an FN-RG7as a User Entity, UE, andUE configuration data for the FN-RG7. A Method for a Database may moreover be adapted for holdingUE dynamic data, such as 5G GUTI. A Method for a provisioning service entity20in a system may comprise a data base entity10, a Unified Data Management/Unified Data Repository, UDM/UDR21and a Certificate Authority, CA22. The method may comprise the steps ofreceiving a create user message71from an actor19such as an operator,creating72a subscription for a Fixed Network Residential Gateway, FN-RG,7, identity in the provisioning service entity20,issuing74A a request to UDM, Unified Data Management/UDR, Unified Data Repository,21to setup UE credential and configuration,issuing75A request to 5G Fixed Mobile Interworking Function Database, FMIF-DB10to setup UE credential and configuration data for FN-RG7. A method for a provisioning service entity20is further provided, wherein upon an FMIF-DB10entry is created for the UE, the provisioning service entity20receiving75C a create user response message from the FMIF DB10,transmitting a Create User Response to the actor19. A method for a provisioning service entity20that is provided may moreover be adapted for connecting to a Certificate Authority, CA, the method comprisingissuing a request73A a FN-RG certificate from a CA,receive73B a FN-RG certificate from the CA. A method for a 5G Fixed Mobile Interworking Function Database entity, FMIF,9adapted for communicating with a 5G Fixed Mobile Interworking Function Database entity data-base, FMIF-DB10, the FMIF moreover being adapted for communicating with a Wireline Access Node, AN,8and an Access and Mobility Management Function, AMF14, the FMIF being further adapted for uponreceiving82a Dynamic Host Configuration Protocol, DHCP, discover message from the AN comprising a circuit ID,issuing83a request for a circuit identity, ID,performing85,86,87NAS procedures with the AMF,issuing88a store request message to the FMIF-DB,receiving89a response from the FMIF-DB. A method for a FMIF is provided wherein, a DHCP offer is issued to a Fixed Net-work Residential Gateway, FN-RG,7. It is noted that the features of the methods described above and, in the following, may be implemented in software and carried out on a data processing device or other processing means caused by the execution of program code means such as computer-executable instructions. Here and in the following, the term processing means comprises any circuit and/or device suitably adapted to perform the above functions. In particular, the above term comprises general- or special-purpose programmable microprocessors, Digital Signal Processors (DSP), Application Specific Integrated Circuits (ASIC), Programmable Logic Arrays (PLA), Field Programmable Gate Arrays (FPGA), special purpose electronic circuits, etc., or a combination thereof. For example, the program code means may be loaded in a memory, such as a RAM (Random Access Memory), from a storage medium, such as a read-only memory (ROM) or other non-volatile memory, such as flash memory, or from another device via a suitable data interface, the described features may be implemented by hardwired circuitry instead of software or in combination with software. The methods discussed above may alternatively be implemented by means of a system based on network functions virtualization. InFIG.16, further embodiments of the invention are implemented by means of such a network function virtualization system, NFVS, formed on e.g. general-purpose servers, standard storage and switches. The NFVS may be arranged along the lines described inFIG.4, ETSI GS NFV 002 V. 1.1.1 (2013-10) and comprises the following elements: A NFV management and orchestration system comprising an Orchestrator, ORCH, a VNF manager, VNF_MGR, and a virtualised Infrastructure manager, VIRT_INFRA_MGR. The NFVS moreover comprises an operational/business support system, OP/BUSS_SUPP_SYST; a number of virtual network function instances, VNF, by which the method steps explained above are instantiated; and a virtualised infrastructure, VIRT_INFRA. The VIRT_INFRA comprises a virtual computing, VIRT_COMP, virtual network; VIRT_NETW, and virtual memory, VIRT_MEM, a virtualisation layer, VIRT_LAYER, (e.g. hypervisor) and shared hardware resources, SHARED_HARDW_RES comprising computing devices, COMP, network devices, NETW, comprising e.g. standard switches and other network devices, and standard data storage devices, MEM. Also, one or more programs for a computer or computer program products, comprising instructions for carrying out any of methods according to the method steps above, are provided. Hence, embodiments of the invention concern among others: A 5G Fixed Mobile Interworking Function Database entity, FMIF-DB,10in a system comprising a Wireline 5G Access Network, W-5GAN, connecting to a Fixed Network Residential Gateway, FN-RG,7, the W-5GAN comprising a Wireline Access Node, AN,8and a 5G Fixed Mobile Interworking Function, FMIF,9, the FMIF9connecting to Access and Mobility Management Function, AMF,14and to an User Plane Function, UPF,13and the FMIF DN10, the wireline Access Node8, coupling to a Fixed Network Residential Gateway, FN-RG7providing services such as TV, Internet and voice, the database apparatus10being adapted for holdingUser entity, UE, credentials for providing an identity of an FN-RG7as a User Entity, UE, andUE configuration data for the FN-RG7. The database may moreover be adapted for holdingUE dynamic data, such as 5G GUTI. There is also provided a provisioning service entity20in a system comprising a data base entity10, a UDM21and a Certificate Authority, CA22, the provisioning service entity20being adapted forreceiving a create user message71from an actor19such as an operator,creating72a subscription for a Fixed Network Residential Gateway, FN-RG,7, identity in the provisioning service entity20,issuing74A a request to UDM, Unified Data Management/UDR, Unified Data Repository,21to setup UE credential and configuration,issuing75A request to 5G Fixed Mobile Interworking Function Database, FMIF-DB10to setup UE credential and configuration data for FN-RG7. Further, the provisioning service entity20may be adapted for, upon an FMIF-DB10entry is created for the UE, andreceiving75C a create user response message from the FMIF DB10,transmitting a Create User Response to the actor19. The provisioning service entity20may moreover be adapted for connecting to a Certificate Authority, CA, the method comprisingrequest73A a FN-RG certificate from a CA,receive73B a FN-RG certificate from the CA. Also, a 5G Fixed Mobile Interworking Function Database entity, FMIF,9is provided being adapted for communicating with a 5G Fixed Mobile Interworking Function Database entity database, FMIF-DB10, the FMIF moreover being adapted for communicating with a Wireline Access Node, AN,8and an Access and Mobility Management Function, AMF14, the FMIF being further adapted for uponreceiving82a Dynamic Host Configuration Protocol, DHCP, discover message from the AN comprising a circuit ID,issuing83a request for a circuit identity, ID,performing85,86,87NAS procedures with the AMF,issuing88a store request message to the FMIF-DB,receiving89a response from the FMIF-DB. For the FMIF, a DHCP offer may be issued to a Fixed Network Residential Gateway, FN-RG,7. A computer program product or computer program is set forty adapted for carrying out the steps above. Also a method fora 5G Fixed Mobile Interworking Function Database entity, FMIF-DB,10is set forth in a system comprising a Wireline 5G Access Network, W-5GAN, connecting to a Fixed Network Residential Gateway, FN-RG,7, the W-5GAN comprising a Wireline Access Node, AN,8and a 5G Fixed Mobile Interworking Function, FMIF,9, the FMIF9connecting to Ac-cess and Mobility Management Function, AMF,14and to an User Plane Function, UPF,13and the FMIF DN10, the wireline Access Node8, coupling to a Fixed Network Residential Gateway, FN-RG7providing services such as TV, Internet and voice, the database apparatus10being adapted for holdingUser entity, UE, credentials for providing an identity of an FN-RG7as a User Entity, UE, andUE configuration data for the FN-RG7. The Database may moreover be adapted for holdingUE dynamic data, such as 5G GUTI. Provided is also a method for a provisioning service entity20is in a system comprising a data base entity10, a Unified Data Management/Unified Data Repository, UDM/UDR21and a Certificate Authority, CA22, comprisingreceiving a create user message71from an actor19such as an operator,creating72a subscription for a Fixed Network Residential Gateway, FN-RG,7, identity in the provisioning service entity20,issuing74A a request to UDM, Unified Data Management/UDR, Unified Data Repository,21to setup UE credential and configuration,issuing75A request to 5G Fixed Mobile Interworking Function Database, FMIF-DB10to setup UE credential and configuration data for FN-RG7. The method for a provisioning service entity20, may involve upon an FMIF-DB10entry is created for the UE, andreceiving75C a create user response message from the FMIF DB10,transmitting a Create User Response to the actor19. The method for a provisioning service entity20may moreover be adapted for connecting to a Certificate Authority, CA, the method comprisingissuing a request73A for a FN-RG certificate from a CA,receiving73B a FN-RG certificate from the CA. There is provided a method for a 5G Fixed Mobile Interworking Function Database entity, FMIF,9adapted for communicating with a 5G Fixed Mobile Interworking Function Database entity database, FMIF-DB10, the FMIF moreover being adapted for communicating with a Wireline Access Node, AN,8and an Access and Mobility Management Function, AMF14, the FMIF being further adapted for uponreceiving82a Dynamic Host Configuration Protocol, DHCP, discover message from the AN comprising a circuit ID,issuing83a request for a circuit identity, ID,performing85,86,87NAS procedures with the AMF,issuing88a store request message to the FMIF-DB,receiving89a response from the FMIF-DB. For the method for a FMIF, a DHCP offer may be issued to a Fixed Network Residential Gateway, FN-RG,7. | 23,834 |
11943732 | MODE FOR INVENTION Reference will now be made in detail to embodiments of the disclosure, examples of which are illustrated in the accompanying drawings. A detailed description to be disclosed below together with the accompanying drawing is to describe exemplary implementations of the present disclosure and not to describe a unique implementation for carrying out the present disclosure. The detailed description below includes details to provide a complete understanding of the present disclosure. However, those skilled in the art know that the present disclosure can be carried out without the details. In some cases, in order to prevent a concept of the present disclosure from being ambiguous, known structures and devices may be omitted or illustrated in a block diagram format based on core functions of each structure and device. Description of Terms in the Present Disclosure In the present disclosure, a base station (BS) refers to a terminal node of a network directly performing communication with a terminal. In the present disclosure, specific operations described to be performed by the base station may be performed by an upper node of the base station, if necessary or desired. That is, it is obvious that in the network consisting of multiple network nodes including the base station, various operations performed for communication with the terminal can be performed by the base station or network nodes other than the base station. The ‘base station (BS)’ may be replaced by terms such as a fixed station, Node B, evolved-NodeB (eNB), a base transceiver system (BTS), an access point (AP), and gNB (general NB). Further, a ‘terminal’ may be fixed or movable and may be replaced by terms such as user equipment (UE), a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), a wireless terminal (WT), a machine type communication (MTC) device, a machine-to-machine (M2M) device, and a device-to-device (D2D) device. In the present disclosure, downlink (DL) refers to communication from the base station to the terminal, and uplink (UL) refers to communication from the terminal to the base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of the base station. Specific terms used in the following description are provided to help the understanding of the present disclosure, and may be changed to other forms within the scope without departing from the technical spirit of the present disclosure. The following technology may be used in various wireless access systems, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier-FDMA (SC-FDMA), and non-orthogonal multiple access (NOMA). The CDMA may be implemented by radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. The TDMA may be implemented by radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE). The OFDMA may be implemented as radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). The UTRA is a part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE), as a part of an evolved UMTS (E-UMTS) using E-UTRA, adopts the OFDMA in downlink and adopts the SC-FDMA in uplink. LTE-advanced (A) is an evolution of the 3GPP LTE. Embodiments of the present disclosure can be supported by standard documents disclosed in at least one of the IEEE 802, 3GPP, and 3GPP2 specifications regarding wireless access systems. In other words, in embodiments of the present disclosure, those steps or parts omitted for the purpose of clearly describing technical principles of the present disclosure can be supported by the standard documents. All the terms disclosed in the present disclosure can also be explained by the standard documents. 3GPP LTE/LTE-A is primarily described for clear description, but technical features of the present disclosure are not limited thereto. Terms used in the present disclosure are defined as follows.IP Multimedia Subsystem or IP Multimedia Core Network Subsystem (IMS): an architectural framework for providing standardization for delivering voice or other multimedia services on internet protocol (IP).Universal Mobile Telecommunication System (UMTS): the 3rd generation mobile communication technology based on global system for mobile communication (GSM) developed by the 3GPP.Evolved Packet System (EPS): a network system consisting of an evolved packet core (EPC), that is an internet protocol (IP) based packet switched core network, and an access network such as LTE and UTRAN. The EPS is a network of an evolved version of UMTS.NodeB: a base station of a UMTS network. It is installed outdoor, and its coverage has a scale of a macro cell.eNodeB: a base station of an EPS network. It is installed outdoor, and its coverage has a scale of a macro cell.Home NodeB: it is installed indoors as a base station of the UMTS network, and its coverage has a scale of a macro cell.Home eNodeB: it is installed indoors as a base station of the EPS network, and its coverage has a scale of a macro cell.User Equipment (UE): the UE may refer to terms such as a terminal, a mobile equipment (ME), and a mobile station (MS). The UE can be a portable device such as a notebook computer, a cellular phone, a personal digital assistant (PDA), a smart phone, and a multimedia device, or a non-portable device such as a personal computer (PC) and a vehicle-mounted device. The term of UE may refer to an MTC UE in the description related to MTC.Machine Type Communication (MTC): communication performed by machines without human intervention. It may be called Machine-to-Machine (M2M) communication.MTC terminal (MTC UE or MTC device or MTC apparatus): a terminal (e.g., a vending machine, meter, etc.) having a communication function (e.g., communication with an MTC server over PLMN) over a mobile communication network and performing a MTC function.Radio Access Network (RAN): a unit including a Node B and a radio network controller (RNC) and eNodeB controlling the Node B in the 3GPP network. The RAN exists at a UE end and provides a connection to a core network.Home Location Register (HLR)/Home Subscriber Server (HSS): a database containing subscriber information within the 3GPP network. The HSS can perform functions such as configuration storage, identity management, user state storage, etc.Public Land Mobile Network (PLMN): a network configured for the purpose of providing mobile communication services to individuals. The PLMN can be configured for each operator.Non-Access Stratum (NAS): a functional layer for exchanging signalling and a traffic message between a UE and a core network at the UMTS and EPS protocol stacks. The NAS mainly functions to support mobility of the UE and support a session management procedure for establishing and maintaining an IP connection between the UE and PDN GW.Service Capability Exposure Function (SCEF): an entity within the 3GPP architecture for service capability exposure that provides a means to safely expose the services and capabilities provided by 3GPP network interfaces.Mobility Management Entity (MME): a network node in the EPS network which performs mobility management and session management functions.Packet Data Network Gateway (PDN-GW): a network node in the EPS network which performs UE IP address allocation, packet screening and filtering, and charging data collection functions.Serving GW (Serving Gateway): a network node in the EPS network which performs functions such as mobility anchor, packet routing, idle mode packet buffering, and triggering of paging for the UE of MME.Policy and Charging Rule Function (PCRF): a node in the EPS network which performs policy decision to dynamically apply differentiated QoS and billing policies per each service flow.Open Mobile Alliance Device Management (OMA DM): A protocol designed to manage mobile devices, such as mobile phones, PDAs, and portable computers, which performs functions such as device configuration, firmware upgrade, and error reportOperation Administration and Maintenance (OAM): A network management function group which provides network fault indication, performance information, and data and diagnostic functions.Packet Data Network (PDN): a network in which a server (e.g., MMS server, WAP server, etc.) supporting a specific service is located.PDN connection: a connection from the UE to the PDN, i.e., the association (connection) between the UE represented by the IP address and the PDN represented by the APN.EPS Mobility Management (EMM): a sublayer of the NAS layer, where the EMM may be in an “EMM-Registered” or “EMM-Deregistered” state depending on whether the UE is network attached or detached.EMM Connection Management (ECM) connection: A signaling connection for the exchange of NAS messages, established between the UE and the MME. An ECM connection is a logical connection consisting of an RRC connection between the UE and an eNB and S1 signaling connection between the eNB and the MME. When the ECM connection is established/terminated, the RRC and S1 signaling connections are established/terminated as well. To the UE, the established ECM connection means having an RRC connection established with the eNB, and to the MME, it means having an S1 signaling connection established with the eNB. Depending on whether the NAS signaling connection, i.e., the ECM connection is established, the ECM may have an “ECM-Connected” or “ECM-Idle” state.Access-Stratum (AS): It includes a protocol stack between the UE and the radio (or access) network and is responsible for transmitting data and network control signals.NAS configuration Management Object (MO): A management object (MO) used to configure the UE with parameters related to NAS functionality.Packet Data Network (PDN): A network in which a server (e.g., multimedia messaging service (MMS) server, wireless application protocol (WAP) server, etc.) supporting a specific service is located.PDN connection: a logical connection between the UE and the PDN, represented by one IP address (one IPv4 address and/or one IPv6 prefix).Access Point Name (APN): a string that refers to or identifies a PDN. In order to access the requested service or network, it goes through a specific P-GW, which means a predefined name (string) in the network so that the P-GW can be found. (e.g., internet.mnc012.mcc345.gprs)Access Network Discovery and Selection Function (ANDSF): it is a network entity and provides policies that allow the UE to discover and select an available access on a per operator basis.EPC path (or infrastructure data path): a user plane communication path through EPC.E-UTRAN Radio Access Bearer (E-RAB): it refers to the concatenation of a S1 bearer and a corresponding data radio bearer. If there is an E-RAB, there is an one-to-one mapping between the E-RAB and the EPS bearer of the NAS.GPRS Tunneling Protocol (GTP): a group of IP-based communications protocols used to carry general packet radio service (GPRS) within GSM, UMTS and LTE networks. Within the 3GPP architecture, GTP and proxy mobile IPv6-based interfaces are specified on various interface points. GTP can be decomposed into several protocols (e.g., GTP-C, GTP-U and GTP′). GTP-C is used within a GPRS core network for signalling between gateway GPRS support nodes (GGSN) and serving GPRS support nodes (SGSN). GTP-C allows the SGSN to activate a session (e.g., PDN context activation), deactivate the same session, adjust the quality of service parameters, or renew a session for a subscriber, that has just operated from another SGSN, for the user. GTP-U is used to carry user data within the GPRS core network and between the radio access network and the core network.Cell as a radio resource: the 3GPP LTE/LTE-A system has used a concept of a cell to manage radio resources, and a cell related to the radio resource is distinguished from a cell of a geographic area. The “cell” related to the radio resource is defined as a combination of downlink (DL) resources and uplink (UL) resources, i.e., a combination of DL carriers and UL carriers. The cell may be configured with DL resource only or a combination of DL resources and UL resources. If carrier aggregation is supported, a linkage between a carrier frequency of the DL resource and a carrier frequency of the UL resource may be indicated by system information. Here, the carrier frequency refers to a center frequency of each cell or carrier. In particular, a cell operating on a primary frequency is called a primary cell or Pcell, and a cell operating on a secondary frequency is called a secondary cell or Scell. The Scell refers to a cell that can be configured after radio resource control (RRC) connection establishment is achieved and can be used for providing additional radio resources. Depending on capabilities of the UE, the Scell together with the Pcell can form a set of serving cells for the UE. For the UE that is in a RRC_CONNECTED state but is not configured with carrier aggregation, or does not support carrier aggregation, there is only one serving cell configured with only the Pcell. The “cell’ of the geographic area can be understood as a coverage in which a node can provide services using a carrier, and the “cell’ of the radio resource is related to a bandwidth (BW) that is a frequency range configured by the carrier. Since a downlink coverage that is a range within which the node can transmit a valid signal and an uplink coverage that is a range within which the node can receive the valid signal from the UE depend on the carrier carrying the corresponding signal, the coverage of the node is associated with the coverage of the “cell’ of the radio resource the node uses. Thus, the term “cell” may be used to sometimes denote the coverage of the service by the node, sometimes denote the radio resource, and sometimes denote a range that a signal using the radio resources can reach with a valid strength. The EPC is a key element of system architecture evolution (SAE) to improve the performance of 3GPP technologies. The SAE corresponds to a research project to determine a network structure supporting mobility between various kinds of networks. The SAE aims to provide an optimized packet-based system, for example, supporting various radio access technologies on an IP basis and providing more improved data transfer capability. More specifically, the EPC is a core network of an IP mobile communication system for the 3GPP LTE system and can support packet-based real-time and non-real time services. In the existing mobile communication system (i.e., in the 2nd or 3rd mobile communication system), functions of the core network have been implemented through two separate sub-domains including a circuit-switched (CS) sub-domain for voice and a packet-switched (PS) sub-domain for data. However, in the 3GPP LTE system that is an evolution of the 3rd mobile communication system, the CS and PS sub-domains have been unified into a single IP domain. That is, in the 3GPP LTE system, a connection between UEs having IP capabilities can be configured via an IP-based base station (e.g., evolved Node B (eNodeB)), an EPC, and an application domain (e.g., IP multimedia subsystem (IMS)). In other words, the EPC is an essential architecture to implement end-to-end IP services. The EPC may include various components, andFIG.1illustrates some of the EPC components, including a serving gateway (SGW), a packet data network gateway (PDN GW), a mobility management entity (MME), a SGSN (serving GPRS (general packet radio service) supporting node), and an enhanced packet data gateway (ePDG). The SGW (or S-GW) operates as a boundary point between a radio access network (RAN) and a core network, and is an element that functions to maintain a data path between the eNB and the PDN GW. Further, if the UE moves across areas served by the eNB, the SGW serves as a local mobility anchor point. That is, packets can be routed through the SGW for mobility within the E-UTRAN (evolved-universal mobile telecommunications system (UMTS) terrestrial radio access network defined in 3GPP Release-8 or later). The SGW may also serve as an anchor point for mobility with other 3GPP networks (RAN defined before 3GPP Release-8, for example, UTRAN or GERAN (global system for mobile communication (GSM)/enhanced data rates for global evolution (EDGE) radio access network). The PDN GW (or P-GW) corresponds to a termination point of a data interface to a packet data network. The PDN GW can support policy enforcement features, packet filtering, charging support, and the like. In addition, the PDN GW can serve as an anchor point for mobility management between the 3GPP network and a non-3GPP network (e.g., untrusted networks such as an interworking wireless local area network (I-WLAN) or trusted networks such as a code division multiple access (CDMA) network and Wimax). Hereinafter, the present disclosure is described based on the terms defined as above. Three major requirement areas of 5G include (1) an enhanced mobile broadband (eMBB) area, (2) a massive machine type communication (mMTC) area, and (3) an ultra-reliable and low latency communications (URLLC) area. Some use cases may require multiple areas for optimization, and other use cases may focus on only one key performance indicator (KPI). 5G supports these various use cases in a flexible and reliable method. eMBB is far above basic mobile Internet access and covers media and entertainment applications in abundant bidirectional tasks, cloud or augmented reality. Data is one of key motive powers of 5G, and dedicated voice services may not be first seen in the 5G era. In 5G, it is expected that voice will be processed as an application program using a data connection simply provided by a communication system. Major causes for an increased traffic volume include an increase in the content size and an increase in the number of applications that require a high data transfer rate. Streaming service (audio and video), dialogue type video and mobile Internet connections will be used more widely as more devices are connected to the Internet. Such many application programs require connectivity in which they are always turned on in order to push real-time information and notification to a user. A cloud storage and application suddenly increases in the mobile communication platform, and this can be applied to both business and entertainment. Furthermore, the cloud storage is a special use case that tows the growth of an uplink data transfer rate. 5G is also used for remote business of cloud. When a tactile interface is used, further lower end-to-end latency is required to maintain better user experiences. Entertainment, for example, cloud game and video streaming are other key elements which increase a need for the mobile broadband ability. Entertainment is essential in the smartphone and tablet anywhere including high mobility environments, such as a train, a vehicle and an airplane. Another use case is augmented reality and information search for entertainment. In this case, augmented reality requires very low latency and an instant amount of data. Furthermore, one of the most expected 5G use cases relates to a function capable of smoothly connecting embedded sensors in all fields, that is, mMTC. Until 2020, it is expected that potential IoT devices will reach 20.4 billions. The industry IoT is one of areas in which 5G performs major roles enabling smart city, asset tracking, smart utility, agriculture and security infra. URLLC includes a new service which will change the industry through remote control of major infra and a link with ultra reliability/low available latency, such as a self-driving vehicle. A level of reliability and latency is essential for smart grid control, industry automation, robot engineering, drone control and adjustment. Multiple use cases are described in more detail below. 5G can supplement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as means for providing a stream evaluated from several hundreds of megabits per second to gigabits per second. Such fast speed is required to deliver TV with a resolution of 4K or more (6K, 8K or more) in addition to virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include immersive sports games. A specific application program may require a special network configuration. For example, in VR games, in order for game companies to minimize latency, a core server may need to be integrated with the edge network server of a network operator. An automotive is expected to be an important and new motive power in 5G, along with many use cases for the mobile communication of an vehicle. For example, entertainment for a passenger requires a high capacity and a high mobility mobile broadband at the same time. This reason is that future users continue to expect a high-quality connection regardless of their location and speed. Another use example of the automotive field is an augmented reality dashboard. The augmented reality dashboard overlaps and displays information, that identifies an object in the dark and notifies a driver of the distance and movement of the object, over a thing seen by the driver through a front window. In the future, a wireless module enables communication between vehicles, information exchange between a vehicle and a supported infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver can drive more safely, thereby reducing a danger of an accident. A next stage will be a remotely controlled or self-driven vehicle. This requires very reliable, very fast communication between different self-driven vehicles and between an automotive and infra. In the future, a self-driving vehicle can perform all driving activities, and a driver will focus on only abnormal traffics, which cannot be identified by a vehicle itself. Technical requirements of a self-driving vehicle require ultra-low latency and ultra-high speed reliability so that traffic safety is increased up to a level which cannot be achieved by a person. A smart city and smart home mentioned as a smart society will be embedded as a high-density radio sensor network. The distributed network of intelligent sensors will identify the cost of a city or home and a condition for energy-efficient maintenance. Similar configuration may be performed for each home. All of a temperature sensor, a window and heating controller, a burglar alarm and home appliances are wirelessly connected. Many of these sensors are typically a low data transfer rate, low energy and low cost. However, for example, real-time HD video may be required for a specific type of device for surveillance. The consumption and distribution of energy including heat or gas are highly distributed and thus require automated control of a distributed sensor network. A smart grid collects information, and interconnects such sensors using digital information and a communication technology so that the sensors operate based on the information. The information may include the behaviors of suppliers and consumers, and thus the smart grid may improve the distribution of fuel, such as electricity, in an efficient, reliable, economical, production-sustainable and automated manner. The smart grid may be considered to be another sensor network with low latency. A health part owns many application programs which reap the benefits of mobile communication. A communication system can support remote treatment providing clinical treatment at a distant place. This helps to reduce a barrier for the distance and can improve access to medical services which are not continuously used at remote farming areas. Furthermore, this is used to save life in important treatment and an emergency condition. A radio sensor network based on mobile communication can provide remote monitoring and sensors for parameters, such as the heart rate and blood pressure. Radio and mobile communication becomes increasingly important in the industry application field. Wiring requires a high installation and maintenance cost. Accordingly, the possibility that a cable will be replaced with reconfigurable radio links is an attractive opportunity in many industrial fields. However, achieving the possibility requires that a radio connection operates with latency, reliability and capacity similar to those of the cable and that management is simplified. Low latency and a low error probability is a new requirement for a connection to 5G. Logistics and freight tracking is an important use case for mobile communication, which enables the tracking inventory and packages anywhere using a location-based information system. The logistics and freight tracking use case typically demands a low data speed, but requires a wide area and reliable location information. Embodiments of the present disclosure to be described below can be implemented through the combination or the modification in order to meet the 5G requirements described above. The following is described in detail in relation to the technical field to which embodiments of the present disclosure to be described below can be applied. Artificial Intelligence (AI) Artificial intelligence means the field in which artificial intelligence or methodology capable of making the artificial intelligence is researched. Machine learning means the field in which various problems handled in the artificial intelligence field are defined and methodology for solving the problems is researched. Machine learning is also defined as an algorithm for improving performance of a task through continuous experiences for the task. An artificial neural network (ANN) is a model used in machine learning, and may refer to the entire model with a problem-solving ability which consists of artificial neurons (nodes) forming a network through a combination of synapses. The artificial neural network may be defined by a connection pattern between neurons of different layers, a learning process of updating a model parameter, and an activation function for generating an output value. The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons. The artificial neural network may include a synapse connecting neurons. In the artificial neural network, each neuron may output a function value of an activation function for input signals, weights, and bias that are input through a synapse. A model parameter means a parameter determined through learning, and includes the weight of a synapse connection and the bias of a neuron. Furthermore, a hyper parameter refers to a parameter that shall be configured before learning in a machine learning algorithm, and includes a learning rate, the number of times of repetitions, a mini-deployment size, and an initialization function. The purpose of learning of the artificial neural network may be considered to determine a model parameter that minimizes a loss function. The loss function may be used as an index for determining an optimal model parameter in the learning process of an artificial neural network. Machine learning may be classified into supervised learning, unsupervised learning, and reinforcement learning based on a learning method. Supervised learning means a method of training an artificial neural network in the state in which a label for learning data has been given. The label may mean an answer (or a result value) that must be deduced by an artificial neural network when learning data is input to the artificial neural network. Unsupervised learning may mean a method of training an artificial neural network in the state in which a label for learning data has not been given. Reinforcement learning may mean a learning method in which an agent defined within an environment is trained to select a behavior or behavior sequence that maximizes accumulated compensation in each state. Machine learning implemented as a deep neural network (DNN) including a plurality of hidden layers, among artificial neural networks, is also called deep learning. The deep learning is part of the machine learning. Hereinafter, the machine learning is used as a meaning including the deep learning. Robot A robot may mean a machine that automatically processes a given task or operates based on an autonomously owned ability. Particularly, a robot having a function for recognizing and autonomously determining an environment and performing an operation may be called an intelligent robot. The robot may be classified for industry, medical treatment, home, and military based on its use purpose or field. The robot includes a driver including an actuator or motor, and can perform various physical operations, such as moving a robot joint. Furthermore, a movable robot includes a wheel, a brake, a propeller, etc. in the driver, and may run on the ground or fly in the air through the driver. Self-Driving (Autonomous-Driving) Self-driving means a technology for autonomous driving. A self-driving vehicle means a vehicle that runs without user manipulation or by user's minimum manipulation. For example, self-driving may include all of a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a fixed path, a technology for automatically setting and driving a path when a destination is set, and the like. A vehicle includes all of a vehicle having only an internal combustion engine, a hybrid vehicle including both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include a train, a motorcycle, etc. in addition to the vehicles. In this instance, the self-driving vehicle may be considered as a robot having a self-driving function. Extended Reality (XR) Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). The VR technology provides an object or background of the real world as a CG image only. The AR technology provides a virtually produced CG image on an actual thing image. The MR technology is a computer graphics technology for mixing and combining virtual objects with the real world and providing them. The MR technology is similar to the AR technology in that it shows a real object and a virtual object together. However, there is a difference in that a virtual object is used to supplement a real object in the AR technology, and on the other hand, a virtual object and a real object are used as the same character in the MR technology. The XR technology can be applied to a head-mount display (HMD), a head-up display (HUD), a mobile phone, a tablet PC, a laptop, a desktop, TV, a digital signage, and the like. A device to which the XR technology is applied may be called an XR device. FIG.1illustrates an AI device100according to an embodiment of the present disclosure. The AI device100may be implemented as a fixed device or mobile device, such as TV, a projector, a mobile phone, a smartphone, a desktop computer, a notebook, a terminal for digital broadcasting, a personal digital assistants (PDA), a portable multimedia player (PMP), a navigator, a tablet PC, a wearable device, a set-top box (STB), a DMB receiver, a radio, a washing machine, a refrigerator, a desktop computer, a digital signage, a robot, and a vehicle. Referring toFIG.1, the AI device100may include a communication unit110, an input unit120, a learning processor130, a sensing unit140, an output unit150, a memory170, and a processor180. The communication unit110may transmit and receive data to and from external devices, such as other AI devices100ato100eor an AI server200, using wired and wireless communication technologies. For example, the communication unit110may transmit and receive sensor information, a user input, a learning model, and a control signal to and from the external devices. Examples of communication technologies used by the communication unit110include a global system for mobile communication (GSM), code division multi access (CDMA), long term evolution (LTE), 5G, a wireless LAN (WLAN), wireless-fidelity (Wi-Fi), Bluetooth™ radio frequency identification (RFID), infrared data association (IrDA), ZigBee, near field communication (NFC), etc. The input unit120may obtain various types of data. The input unit120may include a camera for an image signal input, a microphone for receiving an audio signal, a user input unit for receiving information from a user, etc. Herein, the camera or the microphone is treated as a sensor, and thus a signal obtained from the camera or the microphone may be referred to as sensing data or sensor information. The input unit120can obtain learning data for model learning and input data to be used when an output is obtained using a learning model. The input unit120can obtain not-processed input data. In this case, the processor180or the learning processor130can extract an input feature by performing pre-processing on the input data. The learning processor130may be trained by a model constructed by an artificial neural network using learning data. In this case, the trained artificial neural network may be called a learning model. The learning model may be used to deduce a result value of new input data not learning data, and the deduced value may be used as a base for performing a given operation. The learning processor130can perform AI processing along with a learning processor240of the AI server200. The learning processor130may include a memory integrated or implemented in the AI device100. Alternatively, the learning processor130may be implemented using the memory170, an external memory directly coupled to the AI device100, or a memory maintained in an external device. The sensing unit140can obtain at least one of internal information of the AI device100, surrounding environment information of the AI device100, or user information using various sensors. Examples of sensors included in the sensing unit140include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertia sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, a photo sensor, a microphone, LIDAR, and a radar. The output unit150can generate an output related to a visual sense, an auditory sense or a tactile sense. The output unit150may include a display for outputting visual information, a speaker for outputting auditory information, and a haptic module for outputting tactile information. The memory170can store data supporting various functions of the AI device100. For example, the memory170can store input data obtained by the input unit120, learning data, a learning model, a learning history, etc. The processor180can determine at least one executable operation of the AI device100based on information that is determined or generated using a data analysis algorithm or a machine learning algorithm. Furthermore, the processor180can perform operation determined by controlling the components of the AI device100. To this end, the processor180can request, search, receive, or utilize data of the learning processor130or the memory170, and can control the components of the AI device100to execute a predicted operation or an operation determined to be preferred, among the at least one executable operation. In this case, if association with an external device is necessary to perform the determined operation, the processor180may generate a control signal for controlling the corresponding external device and transmit the generated control signal to the corresponding external device. The processor180can obtain intention information for a user input and transmit user requirements based on the obtained intention information. The processor180can obtain the intention information corresponding to the user input using at least one of a speech to text (STT) engine for converting a voice input into a text string or a natural language processing (NLP) engine for obtaining intention information of a natural language. In this case, at least one of the STT engine or the NLP engine may be constructed by an artificial neural network of which at least a portion is trained according to a machine learning algorithm. Furthermore, at least one of the STT engine or the NLP engine may have been trained by the learning processor130, may have been trained by the learning processor240of the AI server200, or may have been trained by distributed processing thereof. The processor180may collect history information including the feedback, etc. of the user for the operation contents or an operation of the AI device100, and may store the history information in the memory170or the learning processor130or may transmit the history information to an external device such as the AI server200. The collected history information may be used to update a learning model. The processor180may control at least some of the components of the AI device100in order to run an application program stored in the memory170. Moreover, the processor180may combine and operate two or more of the components included in the AI device100in order to run the application program. FIG.2illustrates an AI server200according to an embodiment of the present disclosure. Referring toFIG.2, the AI server200may refer to a device which is trained by an artificial neural network using a machine learning algorithm or which uses a trained artificial neural network. Herein, the AI server200consists of a plurality of servers and may perform distributed processing and may be defined as a 5G network. Further, the AI server200may be included as a partial configuration of the AI device100and may perform at least a part of AI processing. The AI server200may include a communication unit210, a memory230, a learning processor240, and a processor260. The communication unit210may transmit and receive data to and from an external device such as the AI device100. The memory230may include a model storage unit231. The model storage unit231may store a model (or artificial neural network231a) which is being trained or has been trained through the learning processor240. The learning processor240may train the artificial neural network231ausing learning data. The learning model may be used in the state in which it has been mounted on the AI server200of the artificial neural network, or may be mounted on an external device such as the AI device100and used. The learning model may be implemented as hardware, software or a combination of hardware and software. If a part or all of the learning model is implemented as software, one or more instructions constructing the learning model may be stored in the memory230. The processor260may deduce a result value of new input data using the learning model and generate a response or a control command based on the deduced result value. FIG.3illustrates an AI system1according to an embodiment of the present disclosure. Referring toFIG.3, in the AI system1, at least one of the AI server200, a robot100a, a self-driving vehicle100b, an XR device100c, a smartphone100d, or home appliances100eis connected to a cloud network10. The robot100a, the self-driving vehicle100b, the XR device100c, the smartphone100dor the home appliances100eto which the AI technology is applied may be called AI devices100ato100e. The cloud network10may constitute part of cloud computing infra or may mean a network present within cloud computing infra. The cloud network10may be configured using the 3G network, the 4G or long term evolution (LTE) network, or the 5G network. That is, the devices100ato100eand200constituting the AI system1may be interconnected over the cloud network10. In particular, the devices100ato100eand200may communicate with each other through a base station, or may directly communicate with each other without the intervention of the base station. The AI server200may include a server for performing AI processing and a server for performing calculation on big data. The AI server200is connected to at least one of the robot100a, the self-driving vehicle100b, the XR device100c, the smartphone100dor the home appliances100e, that are AI devices constituting the AI system1, over the cloud network10, and may help at least part of the AI processing of the connected AI devices100ato100e. The AI server200can train an artificial neural network based on a machine learning algorithm in place of the AI devices100ato100e, and can directly store a learning model or transmit the learning model to the AI devices100ato100e. The AI server200can receive input data from the AI devices100ato100e, deduce a result value of the received input data using the learning model, generate a response or control command based on the deduced result value, and transmit the response or control command to the AI devices100ato100e. Alternatively, the AI devices100ato100ecan directly deduce a result value of input data using a learning model, and can generate a response or a control command based on the deduced result value. Various implementations of the AI devices100ato100eto which the above-described technologies are applied are described below. Herein, the AI devices100ato100eillustrated inFIG.3may be considered as detailed implementations of the AI device100illustrated inFIG.1. AI and Robot to which the Present Disclosure is Applicable The AI technology is applied to the robot100a, and the robot100amay be implemented as a guidance robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned aerial robot, etc. The robot100amay include a robot control module for controlling an operation. The robot control module may mean a software module or a chip in which a software module is implemented using hardware. The robot100amay obtain status information of the robot100a, detect (recognize) a surrounding environment and an object, generate map data, determine a moving path and a running plan, determine a response to a user interaction, or determine an operation, using sensor information obtained from various types of sensors. The robot100amay use sensor information obtained by at least one sensor of LIDAR, a radar, and a camera in order to determine the moving path and the running plan. The robot100amay perform the above operations using a learning model consisting of at least one artificial neural network. For example, the robot100amay recognize a surrounding environment and an object using the learning model, and determine an operation using the recognized surrounding environment information or object information. Herein, the learning model may have been directly trained in the robot100aor may have been trained in an external device such as the AI server200. The robot100amay directly generate results using the learning model and perform an operation, but may perform an operation by transmitting sensor information to an external device such as the AI server200and receiving results generated in response to this. The robot100amay determine the moving path and the running plan using at least one of map data, object information detected from sensor information, or object information obtained from the external device. The robot100amay run along the determined moving path and running plan by controlling the driver. The map data may include object identification information for various objects disposed in the space in which the robot100amoves. For example, the map data may include object identification information for fixed objects, such as a wall and a door, and movable objects, such as a flowerport and a desk. Furthermore, the object identification information may include a name, a type, a distance, a location, etc. Furthermore, the robot100amay perform an operation or run by controlling the driver based on a user's control/interaction. In this case, the robot100amay obtain intention information of interaction according to a user's behavior or voice utterance, may determine a response based on the obtained intention information, and may perform an operation. AI and Self-Driving to which the Present Disclosure is Applicable The AI technology is applied to the self-driving vehicle100b, and the self-driving vehicle100bmay be implemented as a mobile robot, a vehicle, an unmanned aerial vehicle, etc. The self-driving vehicle100bmay include a self-driving control module for controlling a self-driving function. The self-driving control module may mean a software module or a chip in which a software module has been implemented using hardware. The self-driving control module may be included in the self-driving vehicle100bas the component of the self-driving vehicle100b, but may be configured as separate hardware outside the self-driving vehicle100band connected to the self-driving vehicle100b. The self-driving vehicle100bmay obtain status information of the self-driving vehicle100b, detect (recognize) a surrounding environment and object, generate map data, determine a moving path and a running plan, or determine an operation, using sensor information obtained from various types of sensors. In order to determine the moving path and the running plan, the self-driving vehicle100bmay use sensor information obtained from at least one sensor among LIDAR, a radar and a camera, in the same manner as the robot100a. Particularly, the self-driving vehicle100bmay recognize an environment or an object in an area in which a sight is blocked or an area of a predetermined distance or more by receiving sensor information from external devices, or may receive information that is directly recognized from the external devices. The self-driving vehicle100bmay perform the above operations using a learning model consisting of at least one artificial neural network. For example, the self-driving vehicle100bmay recognize a surrounding environment and object using a learning model and determine a running path using the recognized surrounding environment information or object information. Herein, the learning model may have been directly trained in the self-driving vehicle100bor may have been trained in an external device such as the AI server200. In this instance, the self-driving vehicle100bmay directly generate results using the learning model to perform an operation, but may perform an operation by transmitting sensor information to an external device such as the AI server200and receiving results generated in response to this. The self-driving vehicle100bmay determine a moving path and a running plan using at least one of map data, object information detected from sensor information, or object information obtained from an external device. The self-driving vehicle100bmay run based on the determined moving path and running plan by controlling the driver. The map data may include object identification information for various objects disposed in the space (e.g., road) on which the self-driving vehicle100bruns. For example, the map data may include object identification information for fixed objects, such as a streetlight, a rock, and a building, etc., and mobile objects, such as a vehicle and a pedestrian. Furthermore, the object identification information may include a name, a type, a distance, a location, etc. Furthermore, the self-driving vehicle100bmay perform an operation or run by controlling the driver based on a user's control/interaction. In this case, the self-driving vehicle100bmay obtain intention information of an interaction according to a user' behavior or voice speaking, may determine a response based on the obtained intention information, and may perform an operation. AI and XR to which the Present Disclosure is Applicable The AI technology is applied to the XR device100c, and the XR device100cmay be implemented as a head-mount display (HMD), a head-up display (HUD) provided in a vehicle, television, a mobile phone, a smartphone, a computer, a wearable device, home appliances, a digital signage, a vehicle, a fixed robot or a mobile robot. The XR device100cmay generate location data and attributes data for three-dimensional (3D) points by analyzing 3D point cloud data or image data obtained through various sensors or from an external device, may obtain information on a surrounding space or real object based on the generated location data and attributes data, and may output an XR object by rendering the XR object. For example, the XR device100cmay output an XR object including additional information for a recognized object by making the XR object correspond to the corresponding recognized object. The XR device100cmay perform the above operations using a learning model consisting of at least one artificial neural network. For example, the XR device100cmay recognize a real object in 3D point cloud data or image data using a learning model, and may provide information corresponding to the recognized real object. In this case, the learning model may have been directly trained in the XR device100cor may have been trained in an external device such as the AI server200. In this instance, the XR device100cmay directly generate results using a learning model and perform an operation, but may perform an operation by transmitting sensor information to an external device such as the AI server200and receiving results generated in response to this. AI, Robot and Self-Driving to which the Present Disclosure is Applicable The AI technology and the self-driving technology are applied to the robot100a, and the robot100amay be implemented as a guidance robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned aerial robot, etc. The robot100ato which the AI technology and the self-driving technology are applied may mean a robot itself having a self-driving function, or may mean the robot100ainteracting with the self-driving vehicle100b. The robot100awith the self-driving function may collectively refer to devices that move by itself along a given path without control of a user or determine by itself a moving path and move. The robot100awith the self-driving function and the self-driving vehicle100bmay use a common sensing method to determine one or more of a moving path or a running plan. For example, the robot100awith the self-driving function and the self-driving vehicle100bmay determine one or more of a moving path or a running plan using information sensed through LIDAR, radar, a camera, etc. The robot100ainteracting with the self-driving vehicle100bis present separately from the self-driving vehicle100b, and may perform an operation associated with a self-driving function inside or outside the self-driving vehicle100bor an operation associated with a user got in the self-driving vehicle100b. In this case, the robot100ainteracting with the self-driving vehicle100bmay control or assist the self-driving function of the self-driving vehicle100bby obtaining sensor information in place of the self-driving vehicle100band providing the sensor information to the self-driving vehicle100b, or by obtaining sensor information, generating surrounding environment information or object information, and providing the surrounding environment information or object information to the self-driving vehicle100b. Alternatively, the robot100ainteracting with the self-driving vehicle100bmay control the function of the self-driving vehicle100bby monitoring a user got in the self-driving vehicle100bor through an interaction with a user. For example, if it is determined that a driver is in a drowsiness state, the robot100amay activate the self-driving function of the self-driving vehicle100bor assist control of a driving unit of the self-driving vehicle100b. Herein, the function of the self-driving vehicle100bcontrolled by the robot100amay include a function provided by a navigation system or audio system provided within the self-driving vehicle100b, in addition to a self-driving function simply. Alternatively, the robot100ainteracting with the self-driving vehicle100bmay provide information to the self-driving vehicle100bor may assist a function outside the self-driving vehicle100b. For example, the robot100amay provide the self-driving vehicle100bwith traffic information including signal information, etc., as in a smart traffic light, and may automatically connect an electric charger to a filling inlet through an interaction with the self-driving vehicle100bas in the automatic electric charger of an electric vehicle. AI, Robot and XR to which the Present Disclosure is Applicable The AI technology and the XR technology are applied to the robot100a, and the robot100amay be implemented as a guidance robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned aerial robot, a drone, etc. The robot100ato which the XR technology is applied may mean a robot that is a target of control/interaction within an XR image. In this case, the robot100ais different from the XR device100c, and they may operate in conjunction with each other. If the robot100athat is a target of control/interaction within the XR image obtains sensor information from sensors including a camera, the robot100aor the XR device100cmay generate an XR image based on the sensor information, and the XR device100cmay output the generated XR image. Furthermore, the robot100amay operate based on a control signal received through the XR device100cor a user's interaction. For example, a user may identify a corresponding XR image at time of the robot100aremotely operating in conjunction through an external device such as the XR device100c, may adjust a self-driving path of the robot100athrough an interaction, may control an operation or driving, or may identify information of a surrounding object. AI, Self-Driving and XR to which the Present Disclosure is Applicable The AI technology and the XR technology are applied to the self-driving vehicle100b, and the self-driving vehicle100bmay be implemented as a mobile robot, a vehicle, an unmanned aerial vehicle, etc. The self-driving vehicle100bto which the XR technology is applied may mean a self-driving vehicle provided with a means for providing an XR image or a self-driving vehicle that is a target of control/interaction within the XR image. Particularly, the self-driving vehicle100bthat is the target of control/interaction within the XR image is different from the XR device100c, and they may operate in conjunction with each other. The self-driving vehicle100bprovided with the means for providing the XR image may obtain sensor information from sensors including a camera, and may output the XR image generated based on the obtained sensor information. For example, the self-driving vehicle100bincludes an HUD, and may provide a passenger with an XR object corresponding to a real object or an object within a screen by outputting an XR image. In this case, when the XR object is output to the HUD, at least a part of the XR object may be output to overlap with a real object toward which a passenger's view is directed. On the other hand, when the XR object is output to a display included within the self-driving vehicle100b, at least a part of the XR object may be output to overlap with an object within a screen. For example, the self-driving vehicle100bmay output XR objects corresponding to objects, such as a carriageway, other vehicles, a traffic light, a signpost, a two-wheeled vehicle, a pedestrian, and a building. If the self-driving vehicle100bthat is a target of control/interaction within an XR image obtains sensor information from sensors including a camera, the self-driving vehicle100bor the XR device100cmay create an XR image based on the sensor information, and the XR device100cmay output the created XR image. Furthermore, the self-driving vehicle100bmay operate based on a control signal received through an external device, such as the XR device100c, or a user's interaction. 5G System Architecture to which the Present Disclosure is Applicable A 5G system is an advanced technology from 4G LTE mobile communication technology and supports a new radio access technology (RAT), extended long term evolution (eLTE) as an extended technology of LTE, non-3GPP access (e.g., wireless local area network (WLAN) access), etc. through the evolution or a clean-state structure of an existing mobile communication network structure. The 5G system is defined as service-based, and the interaction between network functions (NFs) in architecture for the 5G system can be represented in two ways as follows.Reference point representation: shows the interaction between NF services in NFs described by a point-to-point reference point (e.g., N11) between two NFs (e.g., AMF and SMF).Service-based representation: network functions (e.g., AMF) within a control plane (CP) enable other authorized network functions to access their services. This representation also includes a point-to-point reference point, if necessary. 3GPP System Overview FIG.4illustrates various reference points. In an example of a network structure illustrated inFIG.4, the SGW and the PDN GW are configured as separate gateways, but the two gateways may be implemented according to a single gateway configuration option. The MME is an element to perform signaling and control functions for supporting access to the network connection of the UE, allocation, tracking, paging, roaming, and handover of network resources, and so on. The MME controls control plane functions related to subscribers and session management. The MME manages a large number of eNBs and performs signaling of the conventional gateway selection for handover to other 2G/3G networks. Further, the MME performs functions of security procedures, terminal-to-network session handling, idle terminal location management, etc. The SGSN handles all packet data such as mobility management and authentication of the user for another 3GPP network (e.g., GPRS network). The ePDG serves as a security node for an untrusted non-3GPP network (e.g., I-WLAN, WiFi hotspot, etc.). As described with reference toFIG.4, the UE with IP capability can access the IP service network (e.g., IMS) provided by a service provider (i.e., operator) via various components within the EPC based on the non-3GPP access as well as the 3GPP access. For example, reference points such as S1-U and S1-MME can connect two functions present in different functional entities. The 3GPP system defines a conceptual link connecting two functions present in different functional entities of E-UTRAN and EPC, as a reference point. The following Table 1 summarizes reference points illustrated inFIG.4. In addition to the example of Table 1, various reference points can exist depending on the network structure. TABLE 1ReferencePointDescriptionS1-MMEReference point for the control plane protocol betweenE-UTRAN and MMES1-UReference point between E-UTRAN and Serving GWfor the per bearer user plane tunneling and intereNodeB path switching during handoverS3It enables user and bearer information exchange for inter3GPP access network mobility in idle and/or active state.This reference point can be used intra-PLMN or inter-PLMN (e.g. in the case of Inter-PLMN HO).S4It provides related control and mobility support betweenGPRS Core and the 3GPP Anchor function of ServingGW. In addition, if Direct Tunnel is not established, itprovides the user plane tunneling.S5It provides user plane tunneling and tunnel managementbetween Serving GW and PDN GW. It is used for ServingGW relocation due to UE mobility and if the Serving GWneeds to connect to a non-collocated PDN GW for therequired PDN connectivity.S11Reference point for the control plane protocol betweenMME and SGWSGiIt is the reference point between the PDN GW and thepacket data network. Packet data network may be anoperator external public or private packet data networkor an intra operator packet data network, e.g. for provisionof IMS services. This reference point corresponds to Gifor 3GPP accesses. Among the reference points illustrated inFIG.4, S2aand S2bcorrespond to non-3GPP interfaces. S2ais a reference point to provide a user plane with related control and mobility support between the trusted non-3GPP access and the PDN GW. S2bis a reference point to provide a user plane with related control and mobility support between the ePDG and the PDN GW. FIG.5illustrates an example of a network structure of an evolved universal terrestrial radio access network (E-UTRAN) to which the present disclosure is applicable. An E-UTRAN system is an evolved version of the existing UTRAN system and may be, for example, 3GPP LTE/LTE-A system. Communication networks are widely deployed to provide various communication services such as voice (e.g., voice over Internet protocol (VoIP)) through IMS and packet data. Referring toFIG.5, an E-UMTS network includes an E-UTRAN, an EPC, and one or more UEs. The E-UTRAN consists of eNBs that provide control plane and user plane protocols to the UE, and the eNBs are interconnected with each other by means of the X2 interface. X2 user plane (X2-U) interface is defined between the eNBs. The X2-U interface provides non-guaranteed delivery of a user plane packet data unit (PDU). X2 control plane (X2-CP) interface is defined between two neighboring eNBs. The X2-CP performs functions of context delivery between the eNBs, control of user plane tunnel between a source eNB and a target eNB, delivery of handover-related messages, uplink load management, and the like. The eNB is connected to the UE via a radio interface and is connected to an evolved packet core (EPC) by means of the S1 interface. S1 user plane (S1-U) interface is defined between the eNB and a serving gateway (S-GW). S1 control plane interface (S1-MME) is defined between the eNB and a mobility management entity (MME). The S1 interface performs functions of evolved packet system (EPS) bearer service management, non-access stratum (NAS) signaling transport, network sharing, MME load balancing, and so on. The S1 interface supports many-to-many-relation between the eNB and the MME/S-GW. The MME can perform various functions such as NAS signaling security, access stratum (AS) security control, inter-core network (CN) node signaling for supporting mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmission), tracking area identity (TAI) management (for UE in idle and active modes), PDN GW and SGW selection, MME selection for handover with MME change, SGSN selection for handover to 2G or 3G 3GPP access networks, roaming, authentication, bearer management functions including dedicated bearer establishment, support of public warning system (PWS) (including earthquake and tsunami warning system (ETWS) and commercial mobile alert system (CMAS)) message transmission, and the like. FIG.6illustrates an example of a general architecture of E-UTRAN and EPC. As illustrated inFIG.6, the eNB can perform functions such as routing to gateway while radio resource control (RRC) connection is activated, scheduling and transmission of paging messages, scheduling and transmission of a broadcast channel (BCH), dynamic allocation of resources in uplink and downlink to the UE, configuration and provision for the measurement of the eNB, radio bearer control, radio admission control, and connection mobility control. The eNB can perform functions such as paging generation in the EPC, management of an LTE_IDLE state, ciphering of a user plane, SAE bearer control, and ciphering and integrity protection of NAS signaling. Annex J of 3GPP TR 23.799 shows various architectures by combining 5G and 4G. An architecture using NR and NGC is disclosed in 3GPP TS 23.501. FIG.7illustrates an example of a structure of a radio interface protocol in a control plane between a UE and eNB.FIG.8illustrates an example of a structure of a radio interface protocol in a user plane between a UE and eNB. The radio interface protocol is based on 3GPP radio access network standard. The radio interface protocol horizontally consists of a physical layer, a data link layer, and a network layer, and is vertically divided into a user plane for data information transmission and a control plane for control signaling delivery. The protocol layers may be divided into L1 (first layer), L2 (second layer), and L3 (third layer) based upon three lower layers of an open system interconnection (OSI) standard model that is well known in the art of communication systems. The layers of the radio protocol in the control plane illustrated inFIG.7and the layers of the radio protocol in the user plane illustrated inFIG.8are described below. The physical layer, the first layer, provides an information transfer service using a physical channel. The physical layer is connected with a medium access control (MAC) layer located at a higher level via a transport channel, and data between the MAC layer and the physical layer is transferred via the transport channel. Data is transferred between different physical layers, i.e., between physical layers of a transmission side and a reception side via the physical channel. The physical channel consists of several subframes on a time axis and several subcarriers on a frequency axis. Here, one subframe consists of a plurality of OFDM symbols and a plurality of subcarriers on the time axis. One subframe consists of a plurality of resource blocks, and one resource block consists of a plurality of OFDM symbols and a plurality of subcarriers. A unit time, a transmission time interval (TTI), at which data is transmitted is 1 ms corresponding to one subframe. Physical channels existing in the physical layers of the transmission side and the reception side may be divided into a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) that are data channels, and a physical downlink control channel (PDCCH), a physical control format indicator channel (PCFICH), a physical hybrid-ARQ indicator channel (PHICH), and a physical uplink control channel (PUCCH) that are control channels, according to 3GPP LTE. There are several layers in the second layer. A medium access control (MAC) layer of the second layer functions to map various logical channels to various transfer channels, and also performs a function of logical channel multiplexing for mapping several logical channels to one transfer channel. The MAC layer is connected to a radio link control (RLC) layer, that is an upper layer, via the logical channel. The logical channel is roughly divided into a control channel used to transmit information of the control plane and a traffic channel used to transmit information of the user plane according to a type of transmitted information. The MAC layer of the second layer segments and concatenate data received from the upper layer and adjusts a data size so that a lower layer is adapted to transmit data to a radio section. A packet data convergence protocol (PDCP) layer of the second layer performs a header compression function of reducing an IP packet header size that has a relatively large size and contains unnecessary control information, in order to efficiently transmit data in a radio section having a small bandwidth upon transmission of IP packet such as IPv4 or IPv6. In the LTE system, the PDCP layer also performs a security function, which consists of ciphering for preventing data interception by a third party and integrity protection for preventing data manipulation by a third party. A radio resource control (RRC) layer located at the uppermost part of the third layer is defined only in the control plane and is responsible for controlling logical channels, transport channels, and physical channels in relation to configuration, re-configuration, and release of radio bearers (RBs). The RB means services provided by the second layer to ensure data transfer between the UE and the E-UTRAN. If an RRC connection is established between an RRC layer of the UE and an RRC layer of a wireless network, the UE is in an RRC connected mode. Otherwise, the UE is in an RRC idle mode. An RRC state of the UE and an RRC connection method are described below. The RRC state refers to a state in which the RRC of the UE is or is not logically connected with the RRC of the E-UTRAN. The RRC state of the UE having logical connection with the RRC of the E-UTRAN is referred to as an RRC_CONNECTED state, and the RRC state of the UE not having logical connection with the RRC of the E-UTRAN is referred to as an RRC_IDLE state. Since the UE in the RRC_CONNECTED state has the RRC connection, the E-UTRAN can identify the presence of the corresponding UE on a per cell basis and thus efficiently control the UE. On the other hand, the E-UTRAN cannot identify the presence of the UE of the RRC_IDLE state, and the UE in the RRC_IDLE state is managed by a core network based on a tracking area (TA) which is an area unit larger than the cell. That is, for the UE in the RRC_IDLE state, only presence or absence of the corresponding UE is identified in an area unit larger than the cell. In order for the UE of the RRC_IDLE state to receive typical mobile communication services such as voice and data, the UE should transition to the RRC_CONNECTED state. Each TA is distinguished from another TA by a tracking area identity (TAI) thereof. The UE may configure the TAI through a tracking area code (TAC) which is information broadcasted from a cell. When the user initially turns on the UE, the UE first searches for a proper cell, and then establishes RRC connection in the corresponding cell and registers information of the UE in the core network. Thereafter, the UE stays in the RRC_IDLE state. The UE staying in the RRC_IDLE state (re)selects a cell and checks system information or paging information, if necessary. This operation is called camping on a cell. Only when the UE staying in the RRC_IDLE state needs to establish the RRC connection, the UE establishes the RRC connection with the RRC layer of the E-UTRAN through a RRC connection procedure and transitions to the RRC_CONNECTED state. There are several cases where the UE remaining in the RRC_IDLE state needs to establish the RRC connection. For example, the cases may include an attempt of a user to make a phone call, an attempt to transmit data, or transmission of a response message when receiving a paging message from the E-UTRAN. A non-access stratum (NAS) layer positioned over the RRC layer performs functions such as session management and mobility management. The NAS layer illustrated inFIG.7is described in detail below. The evolved session management (ESM) belonging to the NAS layer performs functions such as default bearer management and dedicated bearer management, and is responsible for controlling the UE to use a PS service from a network. The default bearer resources are allocated from a network when they are accessed to the network upon first access to a specific packet data network (PDN). In this instance, the network allocates an IP address available for the UE so that the UE can use a data service, and also allocates QoS of a default bearer. LTE roughly supports two types of bearers including a bearer with guaranteed bit rate (GBR) QoS characteristics for guaranteeing a specific bandwidth for data transmission/reception and a non-GBR bearer with best effort QoS characteristics without guaranteeing a bandwidth. The default bearer is allocated the non-GBR bearer. The dedicated bearer may be allocated a bearer with GBR or non-GBR QoS characteristics. A bearer that the network allocates to the UE is referred to as an evolved packet service (EPS) bearer. When the network allocates the EPS bearer to the UE, the network assigns one ID. This ID is called an EPS bearer ID. One EPS bearer has QoS characteristics of a maximum bit rate (MBR) and/or a guaranteed bit rate (GBR). FIG.9illustrates a general architecture of NR-RAN.Referring toFIG.9, the NR-RAN node may be one of the followings.gNB providing NR user plane and control plane protocols towards the UE; or ng-eNB providing E-UTRA user plane and control plane protocols towards the UE. The gNB and the ng-eNB are interconnected with each other by means of the Xn interface. The gNB and ng-eNB are also interconnected with the access and mobility management function (AMF) by means of the NG interface to 5GC, more specifically, by means of the NG-C interface, and are interconnected with the user plane function (UPF) by means of the NG-U interface (see 3GPP TS 23.501 [3]). For reference, architecture and F1 interface for functional split are defined in 3GPP TS 38.401 [4]. FIG.10illustrates an example of general functional split between NG-RAN and 5GC. Referring toFIG.10, yellow boxes depict logical nodes, and white boxes depict main functions. The gNB and ng-eNB host the following functions.Functions for Radio Resource Management: radio bearer control, radio admission control, connection mobility control, and dynamic allocation of resources to UEs in both uplink and downlink (scheduling);IP header compression, encryption and integrity protection of data;Selection of an AMF at IMT-2000 3GPP-UE attachment when no routing to an AMF can be determined from the information provided by the UE;Routing of user plane data towards UPF(s);Routing of control plane information towards AMF;Connection setup and release;Scheduling and transmission of paging messages;Scheduling and transmission of system broadcast information (originated from the AMF or OAM);Measurement and measurement reporting configuration for mobility and scheduling;Transport level packet marking in the uplink;Session management;Support of network slicing;QoS flow management and mapping to data radio bearers;Support of UEs in RRC_INACTIVE state;Distribution function for NAS messages;Radio access network sharing;Dual connectivity;Tight interworking between NR and E-UTRA. The AMF hosts the following main functions (see 3GPP TS 23.501 [3]).NAS signalling termination;NAS signalling security;AS security control;Inter CN node signalling for mobility between 3GPP access networks;Idle mode UE reachability (including control and execution of paging retransmission);Registration area management;Support of intra-system and inter-system mobility;Access authentication;Access authorization including check of roaming rights;Mobility management control (subscription and policies);Support of network slicing;SMF selection. The UPF hosts the following main functions (see 3GPP TS 23.501 [3]).Anchor point for intra-/inter-RAT mobility (when applicable);External PDU session point of interconnect to data network;Packet routing and forwarding;Packet inspection and user plane part of policy rule enforcement;Traffic usage reporting;Uplink classifier to support routing traffic flows to a data network;Branching point to support multi-homed PDU session;QoS handling for user plane (e.g., packet filtering, gating, UL/DL rate enforcement);Uplink traffic verification (SDF to QoS flow mapping);Downlink packet buffering and downlink data notification triggering. The session management function (SMF) hosts the following main functions (see 3GPP TS 23.501 [3]).Session management;UE IP address allocation and management;Selection and control of UP function;Configure traffic steering at UPF to route traffic to proper destination;Control part of policy enforcement and QoS;Downlink data notification. FIG.11illustrates an example of a general architecture of 5G. The following is given a description for each reference interface and each node illustrated inFIG.11. An access and mobility management function (AMF) supports functions of inter-CN node signaling for mobility between 3GPP access networks, termination of radio access network (RAN) CP interface (N2), termination of NAS signaling (N1), registration management (registration area management), idle mode UE reachability, support of network slicing, SMF selection, and the like. Some or all of the functions of the AMF can be supported in a single instance of one AMF. A data network (DN) means, for example, operator services, internet access, or 3rd party service, etc. The DN transmits a downlink protocol data unit (PDU) to the UPF or receives the PDU transmitted from the UE from the UPF. A policy control function (PCF) receives information about packet flow from an application server and provides functions of determining policies such as mobility management and session management. A session management function (SMF) provides a session management function. If the UE has a plurality of sessions, the sessions can be respectively managed by different SMFs. Some or all of the functions of the SMF can be supported in a single instance of one SMF. A unified data management (UDM) stores subscription data of user, policy data, etc. A user plane function (UPF) transmits the downlink PDU received from the DN to the UE via the (R)AN and transmits the uplink PDU received from the UE to the DN via the (R)AN. An application function (AF) interacts with 3GPP core network to provide services (e.g., to support functions of an application influence on traffic routing, network capability exposure access, interaction with policy framework for policy control, and the like). A (radio) access network (R)AN collectively refers to a new radio access network supporting both evolved E-UTRA, that is an evolved version of 4G radio access technology, and a new radio (NR) access technology (e.g., gNB). The gNB supports functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, and dynamic allocation of resources to UEs in uplink/downlink (i.e., scheduling)). The UE means a user equipment. In the 3GPP system, a conceptual link connecting between the NFs in the 5G system is defined as a reference point. N1 is a reference point between the UE and the AMF, N2 is a reference point between the (R)AN and the AMF, N3 is a reference point between the (R)AN and the UPF, N4 is a reference point between the SMF and the UPF, N6 is a reference point between the UPF and the data network, N9 is a reference point between two core UPFs, N5 is a reference point between the PCF and the AF, N7 is a reference point between the SMF and the PCF, N24 is a reference point between the PCF in the visited network and the PCF in the home network, N8 is a reference point between the UDM and the AMF, N10 is a reference point between the UDM and the SMF, N11 is a reference point between the AMF and the SMF, N12 is a reference point between the AMF and an authentication server function (AUSF), N13 is a reference point between the UDM and the AUSF, N14 is a reference point between two AMFs, N15 is a reference point between the PCF and the AMF in case of non-roaming scenario and a reference point between the PCF in the visited network and the AMF in case of roaming scenario, N16 is a reference point between two SMFs (reference point between the SMF in the visited network and the SMF in the home network in case of roaming scenario), N17 is a reference point between AMF and 5G-equipment identity register (EIR), N18 is a reference point between the AMF and an unstructured data storage function (UDSF), N22 is a reference point between the AMF and a network slice selection function (NSSF), N23 is a reference point between the PCF and a network data analytics function (NWDAF), N24 is a reference point between the NSSF and the NWDAF, N27 is a reference point between a network repository function (NRF) in the visited network and the NRF in the home network, N31 is a reference point between NSSF in the visited network and NSSF in the home network, N32 is a reference point between security protection proxy (SEPP) in the visited network and SEPP in the home network, N33 is a reference point between a network exposure function (NEF) and the AF, N40 is a reference point between the SMF and a charging function (CHF), and N50 is a reference point between the AMF and a circuit bearer control function (CBCF). FIG.11illustrates a reference model where the UE accesses to one DN using one PDU session, by way of example, for convenience of explanation, but the present invention is not limited thereto. The following has been described based on the EPS system using the eNB for convenience of explanation. However, the EPS system may be replaced with the 5G system by replacing the eNB by the gNB, the mobility management (MM) function of the MME by the AMF, the SM function of S/P-GW by the SMF, and the user plane-related function of the S/P-GW by the UPF. In the above, the present disclosure has been described based on the EPS, but the corresponding content can be supported by going through similar operations through processes/messages/information for similar purpose in the 5G system. PLMN Selection Procedure The following Table 2 is content related to a PLMN selection defined in 3GPP TS 22.011. TABLE 2The UE shall select and attempt registration on other PLMNs, ifavailable and allowable, if the location area is not in the list of“forbidden LAs for roaming” and the tracking area is notin the list of “forbidden TAs for roaming” (see 3GPP TS23.122 [3]), in the followingorder:i) An EHPLMN if the EHPLMN list is present or the HPLMN(derived from the IMSI) if the EHPLMN list is not present forpreferred access technologies in the order specified. In the casethat there are multiple EHPLMNs present then the highest priorityEHPLMN shall be selected. It shall be possible to configure a voicecapable UE so that it shall not attempt registration on a PLMN ifall cells identified as belonging to the PLMN do not support thecorresponding voice service.ii) Each entry in the “User Controlled PLMN Selector withAccess Technology” data field in the SIM/USIM (in priorityorder). It shall be possible to configure a voice capable UE sothat it shall not attempt registration on a PLMN if all cells identifiedas belonging to the PLMN do not support the corresponding voiceservice.iii) Each entry in the “Operator Controlled PLMN Selector withAccess Technology” data field in the SIM/USIM (in priorityorder). It shall be possible to configure a voice capable UE so that itshall not attempt registration on a PLMN if all cells identified asbelonging to the PLMN do not support the corresponding voiceservice.iv) Other PLMN/access technology combinations with sufficientreceived signal quality (see 3GPP TS 23.122 [3]) in randomorder. It shall be possible to configure a voice capable UE so thatit shall not attempt registration on a PLMN if all cells identified asbelonging to the PLMN do not support the corresponding voiceservice.v) All other PLMN/access technology combinations in order ofdecreasing signal quality. It shall be possible to configure a voicecapable UE so that it shall not attempt registration on a PLMN ifall cells identified as belonging to the PLMN do not support thecorresponding voice service.In the case of a UE operating in UE operation mode A or B, anallowable PLMN is one which is not in the “Forbidden PLMN”data field in the SIM/USIM. This data field may be extended in theME memory (see clause 3.2.2.4). In the case of a UE operating in UEoperation mode C, an allowable PLMN is one which is not in the“Forbidden PLMN” data field in the SIM/USIM or in thelist of “forbidden PLMNs for GPRS service” in the ME.If successful registration is achieved, the UE shall indicate theselected PLMN. Roaming Steering The following Table 3 represents a method of affecting the PLMN selection in relation to the registration, and is described in TS 22.011. TABLE 3Steering to a specific VPLMNIt shall be possible for the HPLMN at any time to direct a UE, thatis in automatic mode, to search for a specific VPLMN and, if it isavailable, move to that VPLMN as soon as possible. This VPLMNshall then be regarded as the highest priority VPLMN as defined bythe operator, though any EHPLMN or PLMN on the User ControlledPLMN list shall have higher priority. This process shall be donetransparently and without inconvenience to the user.If the UE is in manual mode, the steering request shall be ignored.If the UE is registered on a VPLMN that is present on the UserControlled PLMN List, the steering request shall be ignored. PLMNscontained on the User Controlled PLMN List shall have priority overthe steered-to-PLMN.The UE shall attempt to register on the specified VPLMN even if thespecified VPLMN is present on a Forbidden List.This mechanism shall be available to the HPLMN even if theVPLMN the UE is registered on is compliant to an earlier releaseof the 3GPP specifications.VPLMN RedirectionIt shall be possible for the HPLMN to request a UE, that is inautomatic mode, to find and register on a different VPLMN fromthe one it is currently using or trying to register on, if anotherVPLMN, that is not in a Forbidden List, is available. The originalVPLMN shall then be treated as the lowest priority VPLMN andwould not be selected by the UE unless it is the only one availableto the UE or has been selected in manual mode. This process shallbe done transparently and without inconvenience to the user.If the UE is in manual mode, the redirection request shall beignored.If the UE is registered on a VPLMN that is present on the UserControlled PLMN List, the redirection request shall be ignored.This mechanism shall be available to the HPLMN even if theVPLMN the UE is registered on is compliant to an earlier releaseof the 3GPP specifications. EMBODIMENTS OF THE PRESENT DISCLOSURE As the mobile communication services have become an indispensable service in daily life, each mobile service provider is making various attempts to prevent interruption of services. For example, the mobile service providers use a plurality of wired networks in a core network duration in a wireless network or install a plurality of core networks such as AMFs/MMEs, and thus can prevent interruption of communication services by performing backup in other network node even if there is a problem in one network node. However, in the event of a disaster such as a fire or an earthquake, the above measures may not be helpful. For example, this is because, in the event of a fire, all communication cables connected to the outside from one node of the wireless network may be lost. For example, in a virtualized cloud environment, the plurality of core networks such as AMFs/MMEs are highly likely to be implemented in one data center located in the same area. In addition, if the data center is located at a central point of the earthquake, there is a high possibility that all functions will be lost no matter how the plurality of AMFs/MMEs are implemented. Accordingly, the most efficient way is to think of roaming. That is, if the UE cannot receive communication services since there is a problem in a network of a mobile service provider to which the UE subscribes, the UE can roam to a network of other surrounding mobile service provider and receive communication services. Each mobile service provider installs wireless networks and core networks in its licensed area, installs networks in a different building, and builds networks in a different way. Hence, the disasters listed as examples in the preceding description may not have the same impact on all the mobile service providers. Each mobile service provider actively installs wireless networks and core networks in an area where he/she has obtained a license from an actual legal institution and obtained a business right, but cannot install the wireless/core networks in other areas because there is no business right. For example, if any UE leaves an area or a country to which it subscribes, the UE receives roaming service over a network of other service provider. However, if the UE is located in the area or country to which it subscribes, the UE cannot receive the roaming service in the area due to a relationship between the mobile service providers competing with each other in the area. In particular, in the case of a roaming service in an overseas area, when the UE is turned on in a new area, the UE automatically activates the roaming service since the UE cannot discover the network of the mobile service provider to which the UE subscribes. However, if the UE is located in an area where its provider mainly conducts business, the UE does not activate the roaming service and thus cannot receive the roaming service in the disaster situation as described above. In particular, depending on the reason why the mobile service provider, to which the UE subscribes, cannot provide the communication services, a service interruption time for which actual service is not provided to the UE may vary variously. For example, when the power supply to a wireless network is interrupted, the wireless network does not generate any radio waves. Therefore, the UE can recognize a problem of its subscribed network by detecting a radio wave reception failure. However, if wired communication lines of a wireless network and a core network are cut off, the wireless network still generates radio waves. Therefore, it is highly likely that the UE will recognize that the communication network is still alive and will not take any action. If someone attempts to make a call to the UE, the UE may not recognize it. Accordingly, in the above case, the UE moves to other surrounding communication networks and shall get services. That is, even if the UE is in the country in which a communication network, to which the UE subscribes, is located, the UE shall access a network of other mobile service providers. However, when the UE attempts to access other surrounding network as above, there may occur a problem in that the surrounding network cannot smoothly provide services due to an additional signal increase in the surrounding network if a large number of UEs attempt to access the surrounding network at once. Accordingly, the present disclosure is to provide communication services to a UE while minimizing an additional communication service failure in a surrounding network in a process in which any UE efficiently moves to other communication network when a problem occurs in a communication network that the UE accesses and thus the UE cannot get communication services from the communication network. Method 1 In order to achieve this, in the present disclosure, when a UE receives, from a base station connected to a currently accessed PLMN, a message including an indication that the UE can no longer get communication services from the PLMN, that the UE accesses currently, and shall use other surrounding PLMN, the UE may additionally receive information about the other surrounding PLMN from the base station through the message. The message may include an indication that allows the UE to access other PLMN. Hence, the UE may perform the access to the indicated PLMN based on the message. In this process, if the message indicates a specific PLMN, the UE may perform the access to the indicated PLMN. If the message indicates a plurality of PLMNs, the UE may select one PLMN based on the message when the message includes information related to a selection weight. If there is no information related to the selection weight, the UE may select randomly one PLMN. Method 1-1 Method 1-1 describes an example of the method 1. FIG.12illustrates a network selection method according to method 1-1. As illustrated inFIG.12, a first base station1211(RAN1) may detect a failure of a first PLMN1213(CN1) (core network1), in S1201. Next, the first base station may transmit, to a UE, a list of candidate networks (PLMNs), in S1203. For example, if it is determined that communication services cannot be provided to the UE due to a problem of the core network1, the first base station may indicate the UE to select other PLMN through a message, and at the same time, transmit the message to the UE by including a list of a plurality of selectable PLMNs in the message. Next, the UE may select a PLMN, that the UE will access newly, based on the message received from the first base station, in S1205. Next, the UE may perform camping/registration on the selected PLMN, in S1207. For example, the message illustrated inFIG.12may be a system information block (SIB) message, and the SIB may contain the following content. SIB1 contains information relevant when evaluating if a UE is allowed to access a cell, and defines the scheduling of other system information. It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control. The content of a SIB1 message is as follows. Signalling radio bearer: N/A RLC-SAP: TM Logical channel: BCCH Direction: Network to UE Table 4 is an example of the SIB1 message. TABLE 4-- ASN1START-- TAG-SIB1-STARTSIB1 ::= SEQUENCE {cellSelectionInfoSEQUENCE {q-RxLevMinQ-RxLevMin,q-RxLevMinOffsetINTEGER (1 .. 8)OPTIONAL, -- Need Rq-RxLevMinSULQ-RxLevMinOPTIONAL, -- Need Rq-QualMinQ-QualMinOPTIONAL, -- Need Rq-QualMinOffsetINTEGER (1 .. 8)OPTIONAL -- Need R}OPTIONAL, -- Need ScellAccessRelatedInfoCellAccessRelatedInfo,connEstFailureControlConnEstFailureControlOPTIONAL, -- Need Rsi-SchedulingInfoSI-SchedulingInfoOPTIONAL, -- Need RservingCellConfigCommonServingCellConfigCommonSIBOPTIONAL, -- Need Rims-Emergency SupportENUMERATED {true}OPTIONAL, -- Need ReCallOverIMS-SupportENUMERATED {true}OPTIONAL, -- Cond Absentue-TimersAndConstantsUE-TimersAndConstantsOPTIONAL, -- Need Ruac-BarringInfoSEQUENCE {uac-BarringForCommonUAC-BarringPerCatListOPTIONAL, -- Need Suac-BarringPerPLMN-ListUAC-BarringPerPLMN-ListOPTIONAL, -- Need Suac-BarringInfoSetListUAC-BarringInfoSetList,uac-AccessCategory 1-Selection AssistanceInfo CHOICE {plmnCommonUAC-AccessCategory 1-SelectionAssistanceInfo,individualPLMNListSEQUENCE (SIZE(2 .. maxPLMN)) OF UAC-AccessCategory 1-SelectionAssistanceInfo}OPTIONAL}OPTIONAL, -- Need RuseFullResumeIDENUMERATED {true}OPTIONAL, -- Need NSelectOtherPLMNBooleanlateNonCriticalExtensionOCTET STRINGOPTIONAL,nonCriticalExtensionSEQUENCE{ }OPTIONAL}UAC-AccessCategory 1-Selection AssistanceInfo ::=ENUMERATED {a, b, c}-- TAG-SIB1-STOP-- ASNISTOP Table 5 is an example of SIB1 field descriptions. TABLE 5SIB1 field descriptionsq-QualMinParameter “Qqualmin” in TS 38.304 [20], applicable for serving cell.If the field is not present, the UE applies the (default) value ofnegative infinity for Qqualmin.q-QualMinOffsetParameter “Qqualminoffset” in TS 38.304 [20]. Actual valueQqualminoffset= field value [dB]. IfcellSelectionInfois not presentor the field is not present, the UE applies the (default) value of0 dB for Qqualminoffset. Affects the minimum required qualitylevel in the cell.q-RxLevMinParameter “Qrxlevmin” in TS 38.304 [20], applicable for serving cell.q-RxLevMinOffsetParameter “Qrxlevminoffset” in TS 38.304 [20]. Actual value Qrxlevminoffset=field value * 2 [dB]. If absent, the UE applies the (default) value of0 dB for Qrxlevminoffset. Affects the minimum required Rx level in thecell.q-RxLevMinSULParameter “QrxlevminSUL” in TS 38.304 [4], applicable for serving celluac-BarringForCommonCommon access control parameters for each access category.Common values are used for all PLMNs, unless overwritten by thePLMN specific configuration provided inuac-BarringPerPLMN-List.The parameters are specified by providing an index to the set ofconfigurations (uac-BarringInfoSetList). UE behaviour upon absenceof this field is specified in section 5.3.14.2.useFullResumeIDIndicates which resume identifier and Resume request messageshould be used. UE uses full I-RNTI andRRCResumeRequest1if thefield is present, or short I-RNTI andRRCResume Requestif the fieldis absent.uac-AccessCategory1-SelectionAssistanceInfoInformation used to determine whether Access Category 1 applies tothe UE, as defined in [25]. A UE compliant with this version of thespecification shall ignore this field.selectotherPLMNIndicates whether the UE should select other PLMN.CandidatePLMNsWhen selectotherPLMN is indicated, this information shows thecandidate PLMNs which support emergency roaming. This informationcan further include weighing factor in selecting target PLMN. Table 6 represents an explanation of SIB1 field. TABLE 6ConditionalPresenceExplanationAbsentThe field is not used in thisversion of the specification, ifreceived, the UE shall ignore. That is, the first base station may transmit the SIB1 message to the UE by including SelectOtherPLMN or information of purpose/name similar to this in the SIB1 message. The UE receiving this may select/access other PLMN not a PLMN that the UE accesses currently. The first base station may transmit the SIB1 message to the UE by including a candidate PLMN list in the SIB1 message. The candidate PLMN list includes PLMNs that are connected to a base station transmitting the information among surrounding PLMNs and support roaming to UEs in a disaster situation by concluding a service arrangement. Thus, according to SelectOtherPLMN, if CandidatePLMN information is included in a message received from the base station, the UE selecting other PLMN may preferentially attempt registration to the PLMN included in the candidate PLMN list. In addition, the CandidatePLMN information may include a weighting factor determined based on a communication situation of each PLMN among candidate PLMNs. For example, if any UE subscribing to MNO A receives, from a base station of the MNO A, an indication that the UE shall move to other PLMN, and receives an indication for MNO B and MNO C through the candidate PLMN, the UE may receive an indication that the UE shall select the MNO B and the MNO C in a ratio of 7:3. The UE may set the probability of selecting the MNO B to 7 and set the probability of selecting the MNO C to 3 using a random number or an internal algorithm, select one of the MNO B and the MNO C according to the probability value, preferentially select the selected PLMN, and attempt registration to the PLMN. Hence, in the example, when the MNO A fails to properly provide services, the UE may flock to one of the MNO B and the MNO C and thus prevent these networks from additionally occurring a problem. As above, a method of informing a problem of a current PLMN via SIB (or MIB, etc.) may be applied to a UE that is in an idle mode or an RRC inactive mode. However, a base station may also indicate more rapidly a UE in an RRC Connected mode to move to other PLMN using information such as RRC Release. For example, the same information as that described in the method 1-1 may be transmitted to the UE via RRCRelease below. RRCRelease The RRCRelease message is used to command the release of an RRC connection or the suspension of the RRC connection. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE The RRC Release message is the same as the following Table 7. TABLE 7-- ASN1START-- TAG-RRCRELEASE-STARTRRCRelease ::=SEQUENCE {rrc-TransactionIdentifierRRC-TransactionIdentifier,criticalExtensionsCHOICE {rrcReleaseRRCRelease-IEs,criticalExtensionsFutureSEQUENCE { }}}RRCRelease-IEs ::=SEQUENCE {redirectedCarrierInfoRedirectedCarrierInfoOPTIONAL, -- Need NSelectOtherPLMNSelectOtherPLMNcellReselectionPrioritiesCellReselectionPrioritiesOPTIONAL, -- Need RsuspendConfigSuspendConfigOPTIONAL, -- Need RdeprioritisationReqSEQUENCE {deprioritisationTypeENUMERATED {frequency, nr},deprioritisationTimerENUMERATED {min5, min10, min15,min30}}OPTIONAL, -- Need NlateNonCriticalExtensionOCTET STRINGOPTIONAL,nonCriticalExtensionSEQUENCE{ }OPTIONAL}RedirectedCarrierInfo ::=CHOICE {nrCarrierInfoNR,eutraRedirectedCarrierInfo-EUTRA,...}RedirectedCarrierInfo-EUTRA ::=SEQUENCE {eutraFrequencyARFCN-ValueEUTRA,cnType-r15ENUMERATED {epc,fiveGC}OPTIONAL}CarrierInfoNR ::=SEQUENCE {carrierFreqARFCN-ValueNR,ssbSubcarrierSpacingSubcarrierSpacing,smtcSSB-MTCOPTIONAL, -- Need S...}SuspendConfig ::=SEQUENCE {fullI-RNTII-RNTI-Value,shortI-RNTIShortI-RNTI-Value,ran-PagingCyclePagingCycle,ran-NotificationAreaInfoRAN-NotificationAreaInfoOPTIONAL, -- Need Mt380PeriodicRNAU-TimerValueOPTIONAL, -- Need RnextHopChainingCountNextHopChainingCount,...}PeriodicRNAU-TimerValue ::=ENUMERATED { min5, min10, min20, min30,min60, min120, min360, min720}CellReselectionPriorities ::= SEQUENCE {freqPriority ListEUTRAFreqPriority ListEUTRAOPTIONAL, -- Need MfreqPriority ListNRFreqPriority ListNROPTIONAL, -- Need Mt320ENUMERATED {min5, min10, min20,min30, min60, min120, min180, spare1}OPTIONAL, -- Need R...}PagingCycle ::=ENUMERATED {rf32, rf64, rf128, rf256}FreqPriorityListEUTRA ::=SEQUENCE (SIZE (1..maxFreq)) OFFreqPriorityEUTRAFreqPriorityListNR ::=SEQUENCE (SIZE (1..maxFreq)) OFFreqPriorityNRFreqPriorityEUTRA ::=SEQUENCE {carrierFreqARFCN-ValueEUTRA,cellReselectionPriorityCellReselectionPriority,cellReselectionSubPriorityCellReselectionSubPriorityOPTIONAL -- Need R}FreqPriorityNR ::=SEQUENCE {carrierFreqARFCN-ValueNR,cellReselectionPriorityCellReselectionPriority,cellReselectionSubPriorityCellReselectionSubPriorityOPTIONAL -- Need R}RAN-NotificationAreaInfo ::=CHOICE {cellListPLMN-RAN-AreaCellList,ran-AreaConfigListPLMN-RAN-AreaConfigList,...}PLMN-RAN-AreaCellList ::=SEQUENCE (SIZE (1..maxPLMNIdentities))OF PLMN-RAN-AreaCellPLMN-RAN-AreaCell ::=SEQUENCE {plmn-IdentityPLMN-IdentityOPTIONAL, -- Need SSEQUENCE (SIZE (1..32)) OFran-AreaCellsCellIdentity}PLMN-RAN-AreaConfigList ::=SEQUENCE (SIZE (1..maxPLMNIdentities))OF PLMN-RAN-AreaConfigPLMN-RAN-AreaConfig ::=SEQUENCE {plmn-IdentityPLMN-IdentityOPTIONAL, -- Need Sran-AreaSEQUENCE (SIZE (1..16)) OF RAN-AreaConfig}RAN-AreaConfig :=SEQUENCE {trackingAreaCodeTrackingAreaCode,ran-AreaCodeListSEQUENCE (SIZE (1..32)) OF RAN-AreaCodeOPTIONAL -- Need R}-- TAG-RRCRELEASE-STOP-- ASN1STOP Here, FFS whether RejectWaitTimer is included in the RRCRelease message. Table 8 is an example of RRCRelease field descriptions. TABLE 8RRCRelease field descriptionscnTypeIndicate that the UE is redirected to EPC or 5GC.deprioritisationReqIndicates whether the current frequency or RAT is to be de-prioritised. The UE shall be ableto store a deprioritisation request for up to X frequencies (applicable when receivinganother frequency specific deprioritisation request before T325 expiry).deprioritisation TimerIndicates the period for which either the current carrier frequency or NR is deprioritised.Value minN corresponds to N minutes.suspendConfigIndicates configuration for the RRC_INACTIVE state.t380Refers to the timer that triggers the periodic RNAU procedure in UE. Value min5corresponds to 5 minutes, value min10 corresponds to 10 minutes and so on.ran-PagingCycleRefers to the UE specific cycle for RAN-initiated paging. Value rf32 corresponds to 32radio frames, rf64 corresponds to 64 radio frames and so on.redirectedCarrierInfoIndicates a carrier frequency (downlink for FDD) and is used to redirect the UE to an NR oran inter-RAT carrier frequency, by means of the cell selection upon leavingRRC_CONNECTED (see TS 38.304 [20])selectotherPLMNIndicates whether the UE should select other PLMN.CandidatePLMNsWhen selectotherPLMN is indicated, this information shows the candidate PLMNs whichsupport emergency roaming.This information can further include weighing factor inselecting target PLMN. Method 2 If competitor's UEs suddenly flock to any PLMN due to a problem occurring in PLMNs of surrounding competitors, additional network errors and communication failures may occur in the PLMN due to an access and registration request of the suddenly increasing UEs. In particular, if the PLMN (e.g., PLMN A) needs to temporarily provide service to a subscriber of other surrounding network (e.g., communication network B) while providing service to its subscriber (subscriber of communication network A), the PLMN A may preferentially provide service to its subscriber and may provide service to the subscriber of the communication network B within the limit that does not impair the stability of the network of the PLMN A if the PLMN A has free resources. To this end, in the present disclosure, the base station informs the UE about types of services provided to UEs that are subscribed to other PLMNs or providers, and whether to allow service, and the UE attempts to access other PLMN only when service is allowed to the UE. In particular, if UEs, in which a disaster occurs in a PLMN to which they subscribe, access other surrounding PLMNs, each base station may indicate, to the UE, whether or not other surrounding PLMNs each support national roaming, or whether or not the respective PLMNs permit the access attempt of the UE. Hence, if the UE attempts to access a different PLMN (hereinafter, referred to as communication network B for convenience of explanation) from a subscribed PLMN (hereinafter, referred to as communication network A for convenience of explanation) of the UE, the UE that attempts to access other surrounding PLMN due to a disaster occurring in the PLMN, to which the UE subscribes, may first read system information in the communication network B and determine whether or not national roaming or disaster roaming is allowed in the communication network B. If the UE receives, from the base station, that national roaming or disaster roaming has been allowed in the communication network B, or if the UE is informed that communication of the purpose similar to this has been allowed in the communication network B, the UE may attempt to access the communication network B and attempt the camping. Further, if national roaming or disaster roaming or the operation similar to this is not allowed in the communication network B, the UE does not attempt to access the communication network B. Method 2-1 For example, a base station connected to a surrounding PLMN may send each UE whether or not the base station has allowed the national roaming or disaster roaming attempt of UEs subscribed to other competitor PLMN using the following SIB message. That is, the UE that is indicated to select other surrounding PLMN other than a currently subscribed PLMN may determine whether the access attempt (or disaster roaming attempt) to other PLMN is allowed from other base station connected to other PLMN using the following SIB message. The SIB message contains information relevant when evaluating if a UE is allowed to access a cell, and defines the scheduling of other system information. It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control. The content of a SIB1 message is as follows. Signalling radio bearer: N/A RLC-SAP: TM Logical channel: BCCH Direction: Network to UE Table 9 is an example of the SIB1 message. TABLE 9-- ASN1START-- TAG-SIB1-STARTSIB1 ::=SEQUENCE {cellSelectionInfoSEQUENCE {q-RxLevMinQ-RxLevMin,q-RxLevMinOffsetINTEGER (1..8)OPTIONAL, -- Need Rq-RxLevMinSULQ-RxLevMinOPTIONAL, -- Need Rq-QualMinQ-QualMinOPTIONAL, -- Need Rq-QualMinOffsetINTEGER (1..8)OPTIONAL -- Need R}OPTIONAL, -- Need ScellAccessRelatedInfoCellAccessRelatedInfo,connEstFailureControlConnEstFailureControlOPTIONAL, -- Need Rsi-SchedulingInfoSI-SchedulingInfoOPTIONAL, -- Need RservingCellConfigCommonServingCellConfigCommonSIBOPTIONAL, -- Need Rims-Emergency SupportENUMERATED {true}OPTIONAL, -- Need ReCallOverIMS-SupportENUMERATED {true}OPTIONAL, -- Cond Absentue-TimersAndConstantsUE-TimersAndConstantsOPTIONAL, -- Need RNationalRoamingAlloweduac-BarringInfoSEQUENCE {uac-BarringForCommonUAC-BarringPerCatListOPTIONAL, -- Need Suac-BarringPerPLMN-ListUAC-BarringPerPLMN-ListOPTIONAL, -- Need Suac-BarringInfoSetListUAC-BarringInfoSetList,uac-AccessCategory1-Selection AssistanceInfo CHOICE {plmnCommonUAC-AccessCategory1-SelectionAssistanceInfo,individualPLMNListSEQUENCE (SIZE(2..maxPLMN)) OF UAC-AccessCategory1-SelectionAssistanceInfo}OPTIONAL}OPTIONAL, -- Need RuseFullResumeIDENUMERATED {true}OPTIONAL, -- Need NSelectOtherPLMNBooleanlateNonCriticalExtensionOCTET STRINGOPTIONAL,nonCriticalExtensionSEQUENCE{ }OPTIONALUAC-AccessCategory1-SelectionAssistanceInfo ::=ENUMERATED {a, b, c}-- TAG-SIB1-STOP-- ASN1STOP Table 10 is an example of SIB1 field descriptions. TABLE 10SIB1 field descriptionsq-QualMinParameter “Qqualmin” in TS 38.304 [20], applicable for serving cell. If the field is notpresent, the UE applies the (default) value of negative infinity for Qqualmin.q-QualMinOffsetParameter “Qqualminoffset” in TS 38.304 [20]. Actual value Qqualminoffset= field value [dB]. IfcellSelectionInfo is not present or the field is not present, the UE applies the (default) valueof 0 dB for Qqualminoffset. Affects the minimum required quality level in the cell.q-RxLevMinParameter “Qrxlevmin” in TS 38.304 [20], applicable for serving cell.q-RxLevMinOffsetParameter “Qrxlevminoffset” in TS 38.304 [20]. Actual value Qrxlevminoffset= field value * 2 [dB].If absent, the UE applies the (default) value of 0 dB for Qrxlevminoffset. Affects the minimumrequired Rx level in the cell.q-RxLevMinSULParameter “QrxlevminSUL” in TS 38.304 [4], applicable for serving celluac-BarringForCommonCommon access control parameters for each access category. Common values are used forall PLMNs, unless overwritten by the PLMN specific configuration provided in uac-BarringPerPLMN-List. The parameters are specified by providing an index to the set ofconfigurations (uac-BarringInfoSetList). UE behaviour upon absence of this field isspecified in section 5.3.14.2.useFullResumeIDIndicates which resume identifier and Resume request message should be used. UE usesfull I-RNTI and RRCResumeRequest1 if the field is present, or short I-RNTI andRRCResume Request if the field is absent.uac-AccessCategory 1-SelectionAssistanceInfoInformation used to determine whether Access Category 1 applies to the UE, as defined in[25]. A UE compliant with this version of the specification shall ignore this field.NationalRoamingAllowedIndicates whether current network access from national roaming UEs. An example of the UE's operation in the above method is the same as the following Table 11. TABLE 11TS 38.304The UE shall scan all RF channels in the NR bands according to its capabilities to findavailable PLMNs. On each carrier, the UE shall search for the strongest cell and read itssystem information, in order to find out which PLMN(s) the cell belongs to. If the UE canread one or several PLMN identities in the strongest cell, each found PLMN (see the PLMNreading in TS 38.331 [3]) shall be reported to the NAS as a high quality PLMN (but withoutthe RSRP value), provided that the following high-quality criterion is fulfilled:1. For an NR cell, the measured RSRP value shall be greater than or equal to −110 dBm.Found PLMNs that do not satisfy the high-quality criterion but for which the UE has beenable to read the PLMN identities are reported to the NAS together with their correspondingRSRP values. The quality measure reported by the UE to NAS shall be the same for eachPLMN found in one cell.The search for PLMNs may be stopped on request from the NAS. The UE may optimisePLMN search by using stored information e.g. frequencies and optionally also informationon cell parameters from previously received measurement control information elements.Once the UE has selected a PLMN, the cell selection procedure shall be performed in orderto select a suitable cell of that PLMN to camp on.When the UE are searching for a PLMN triggered by e.g. due to unavailability or HPLMN,due to trigger to start national roaming/emergency roaming, the UE check whether thefound PLMN allows national/emergency roaming or not. If the found PLMN and theHPLMN of the UE belongs to same country, and if the found PLMN supportnational/emergency roaming the UE selects the PLMN. Otherwise, the UE shall not selectthe PLMN except when there are no other candidate PLMNs.In case, PLMN of different country than the HPLMN of the UE is available, the UE shallnot select PLMN of same country.After that, the UE start registration. That is, in a situation in which national roaming is possible (i.e., PLMN of the same country as HPLMN to which the UE subscribes), the UE may attempt the access/camping/registration to the corresponding PLMN only if the PLMN of the same country allows national roaming or disaster roaming. If the found PLMN does not allow national roaming or disaster roaming, the UE may attempt selection for other PLMN other than the corresponding PLMN. If there is no PLMN that the UE can newly select, the UE perform the camping for receiving a limited service within a cell in which the UE is located currently. Method 2-1-1 In addition, in the method 2-1, a base station that informs an external UE that national roaming is allowed may inform the UE of conditions for a PLMN to which the corresponding UE subscribes. For example, in the above example, when a communication network B and a communication network C are around a communication network A, and when national roaming is pre-configured only between the communication network A and the communication network B and national roaming is not configured between the remaining networks, a UE subscribed to the communication network A may receive national roaming service in the communication network B, but cannot receive national roaming service in the communication network C. If any disaster does not occur in the communication network C, a UE subscribed to the communication network C shall not attempt to access the communication network B even if the communication network B supports national roaming. Accordingly, the communication network B supports national roaming for a subscriber of the communication network A, and shall be able to block national roaming for a subscriber of the communication network C. To this end, if national roaming for a PLMN connected to the base station is allowed to the UE, the base station may transmit, to the UE, a PLMN condition for whether national roaming is allowed for any PLMN (communication network). When the UE itself shall perform national roaming, the UE monitors the PLMN condition in the candidate PLMN list based on the PLMN condition and attempts to access only a PLMN allowed in a home PLMN to which the UE is subscribed. If the home PLMN of the UE is not included, the UE does not attempt to access the PLMN. The SIB1 message in the above example contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information. It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control. Signalling radio bearer: N/A RLC-SAP: TM Logical channel: BCCH Direction: Network to UE Table 12 is an example of the SIB1 message according to the method 2-1-1. TABLE 12-- ASN1START-- TAG-SIB1-STARTSIBI ::=SEQUENCE {cellSelectionInfoSEQUENCE {q-RxLevMinQ-RxLevMin,q-RxLevMinOffsetINTEGER (1..8)OPTIONAL, -- Need Rq-RxLevMinSULQ-RxLevMinOPTIONAL, -- Need Rq-QualMinQ-QualMinOPTIONAL, -- Need Rq-QualMinOffsetINTEGER (1..8)OPTIONAL -- Need R}OPTIONAL, -- Need ScellAccessRelatedInfoCellAccessRelatedInfo,connEstFailureControlConnEstFailureControlOPTIONAL, -- Need Rsi-SchedulingInfoSI-SchedulingInfoOPTIONAL, -- Need RservingCellConfigCommonServingCellConfigCommonSIBOPTIONAL, -- Need Rims-Emergency SupportENUMERATED {true}OPTIONAL, -- Need ReCallOverIMS-SupportENUMERATED {true}OPTIONAL, -- Cond Absentue-TimersAndConstantsUE-TimersAndConstantsOPTIONAL, -- Need RNationalRoamingAllowedAllowedPLMNforNationalRoaminguac-BarringInfoSEQUENCE {uac-BarringForCommonUAC-BarringPerCatListOPTIONAL, -- Need Suac-BarringPerPLMN-ListUAC-BarringPerPLMN-ListOPTIONAL, -- Need Suac-BarringInfoSetListUAC-BarringInfoSetList,uac-AccessCategory 1-Selection AssistanceInfo CHOICE {plmnCommonUAC-AccessCategory1-SelectionAssistanceInfo,individualPLMNListSEQUENCE (SIZE(2..maxPLMN)) OF UAC-AccessCategory 1-SelectionAssistanceInfo}OPTIONAL}OPTIONAL, -- Need RuseFullResumeIDENUMERATED {true}OPTIONAL, -- Need NSelectOtherPLMNBooleanlateNonCriticalExtensionOCTET STRINGOPTIONAL,nonCriticalExtensionSEQUENCE{ }OPTIONAL}UAC-AccessCategory 1-Selection AssistanceInfo ::=ENUMERATED {a, b, c}-- TAG-SIB1-STOP-- ASN1STOP Table 13 is an example of SIB1 field descriptions according to the method 2-1-1. TABLE 13SIB1 field descriptionsq-QualMinParameter “Qqualmin” in TS 38.304 [20], applicable for serving cell. If the field is notpresent, the UE applies the (default) value of negative infinity for Qqualmin.q-QualMinOffsetParameter “Qqualminoffset” in TS 38.304 [20]. Actual value Qqualminoffset= field value [dB]. IfcellSelectionInfo is not present or the field is not present, the UE applies the (default) valueof 0 dB for Qqualminoffset. Affects the minimum required quality level in the cell.q-RxLevMinParameter “Qrxlevmin” in TS 38.304 [20], applicable for serving cell..q-RxLevMinOffsetParameter “Qrxlevminoffset” in TS 38.304 [20]. Actual value Qrxlevminoffset= field value * 2 [dB].If absent, the UE applies the (default) value of 0 dB for Qrxlevminoffset.Affects the minimum required Rx level in the cell.q-RxLevMinSULParameter “QrxlevminSUL” in TS 38.304 [4], applicable for serving celluac-BarringForCommonCommon access control parameters for each access category. Common values are used forall PLMNs, unless overwritten by the PLMN specific configuration provided in uac-BarringPerPLMN-List. The parameters are specified by providing an index to the set ofconfigurations (uac-BarringInfoSetList). UE behaviour upon absence of this field isspecified in section 5.3.14.2.useFullResumeIDIndicates which resume identifier and Resume request message should be used. UE usesfull I-RNTI and RRCResumeRequest1 if the field is present, or short I-RNTI andRRCResume Request if the field is absent.uac-AccessCategory 1-SelectionAssistanceInfoInformation used to determine whether Access Category 1 applies to the UE, as defined in[25]. A UE compliant with this version of the specification shall ignore this field.NationalRoamingAllowedIndicates whether current network access from national roaming UEs.AllowedPLMNforNationalRoamingThe list of PLMN whose subscribed are allowed for national roaming. Method 2-2 For services that generate a lot of traffic and are important in daily life, such as services used by general smartphones, a UE shall get services on a new PLMN via national roaming or disaster roaming, but a UE of the purpose such as IoT (e.g., a UE that performs gas/electricity measurement once a month and transmits a result of the measurement) does not need to immediately move to a new PLMN or to perform roaming on a new PLMN. Accordingly, the above operations are performed on only a UE, for which national roaming or disaster roaming is allowed, based on information configured in, for example, a SIM or a memory of the UE, and are not performed on a UE if which national roaming or disaster roaming is not allowed based on configuration information, etc. Method 2-3 If a UE has accessed other network (network B or PLMN B) since a problem occurs in a network (network A or PLMN A) subscribed by the UE and thus the network A can no longer be used, and the network B has not yet recognized that the problem has occurred in the network A, the UE camps on the network B in a limited mode. In this case, the UE continues to monitor a SIB message in the network B. In the above process, whether to support national roaming may be indicated to the UE through a method listed in the above methods in the SIB message received by the UE. In this process, a base station may inform the UE that the access has been allowed for UEs of which PLMN. That is, if in the above scenario, the UE has attempted the access by the network B and receives a registration reject (attach reject) by the network B, the UE may configure the network B as a forbidden PLMN. However, if the UE receives, from the subsequent SIB, information notifying that national roaming or disaster roaming has been allowed on the network B or that the forbidden PLMN has been released, the UE may release the PLMN B from the forbidden PLMN configuration if the UE corresponds to this (i.e., subscription to the network A). Hence, the UE attempts to register again to the PLMN B. Method 2-3-1 Preferably, in the above situation, in a state where any UE camps on a base station belonging to a specific network, a PLMN of the corresponding network is configured as the forbidden PLMN and the UE accesses the corresponding PLMN in a limited service state. And, if the SIB that the base station transmits to the UE is updated, and it is indicated that the PLMN belongs to home PLMN of the UE, the UE may perform newly the registration procedure to the corresponding PLMN, and the UE may get out of the limited service state if it is successful. Method 2-3-1-1 Method 2-3-1-1 is an example of the method 2-3-1, and Table 14 represents an example of the method 2-3-1-1. TABLE 144.4.3 PLMN SelectionThe registration on the selected PLMN and the location registration are only necessary ifthe MS is capable of services which require registration. Otherwise, the PLMN selectionprocedures are performed without registration.The ME shall utilize all the information stored in the SIM related to the PLMN selection;e.g. “HPLMN Selector with Access Technology”, “Operator controlled PLMN Selectorwith Access Technology”, “User Controlled PLMN Selector with Access Technology”,“Forbidden PLMNs”, “Equivalent HPLMN”.The ″HPLMN Selector with Access Technology″, “User Controlled PLMN Selector withAccess Technology” and “Operator Controlled PLMN Selector with Access Technology”data files in the SIM include associated access technologies for each PLMN entry, see3GPP TS 31.102 [40]. The PLMN/access technology combinations are listed in priorityorder. If an entry indicates more than one access technology, then no priority is defined forthe access technologies within this entry and the priority applied to each access technologywithin this entry is an implementation issue. If no particular access technology is indicatedin an entry, it shall be assumed that all access technologies supported by the ME apply tothe entry. If an entry only indicates access technologies not supported by the ME, the entryshall be ignored. If an entry indicates at least one access technology supported by the ME,the entry shall be used in the PLMN selection procedures if the other criteria defined for thespecific PLMN selection procedures are fulfilled.The Mobile Equipment stores a list of “equivalent PLMNs”. This list is replaced or deletedat the end of each location update procedure, routing area update procedure, GPRS attachprocedure, tracking area update procedure, EPS attach procedure, and registrationprocedure. The list is deleted by an MS attached for emergency bearer services after detachor registered for emergency services after deregistration. The stored list consists of a list ofequivalent PLMNs as downloaded by the network plus the PLMN code of the registeredPLMN that downloaded the list. All PLMNs in the stored list, in all access technologiessupported by the PLMN, are regarded as equivalent to each other for PLMN selection, cellselection/re-selection and handover.When the MS reselects to a cell in a shared network, and the cell is a suitable cell formultiple PLMN identities received on the BCCH or on the EC-BCCH the AS indicatesthese multiple PLMN identities to the NAS according to 3GPP TS 44.018 [34],3GPP TS 44.060 [39], 3GPP TS 25.304 [32] and 3GPP TS 36.304 [43]. The MS shallchoose one of these PLMNs. If the registered PLMN is available among these PLMNs, theMS shall not choose a different PLMN.When a cell is updated to support multiple network (e.g. a cell becomes to be part of ashared network), and the cell is a suitable cell for multiple PLMN identities received on theBCCH or on the EC-BCCH the AS indicates these multiple PLMN identities to the NASaccording to 3GPP TS 44.018 [34], 3GPP TS 44.060 [39], 3GPP TS 25.304 [32] and3GPP TS 36.304 [43]. The MS shall choose one of these PLMNs.When a system information of a cell is updated and PLMN identities received on the BCCHor on the EC-BCCH is updated, the AS indicates these multiple PLMN identities to theNAS according to 3GPP TS 44.018 [34], 3GPP TS 44.060 [39], 3GPP TS 25.304 [32] and3GPP TS 36.304 [43]. The MS shall choose one of these PLMNs. If HPLMN is included inthe multiple PLMN and if the UE is in limited state or if the UE is registered in VPLMN,then the UE start registration with HPLMN is selected.The MS shall not use the PLMN codes contained in the “HPLMN Selector with AccessTechnology” data file.It is possible for the home network operator to identify alternative Network IDs as theHPLMN. If the EHPLMN list is present, and not empty, the entries in the EHPLMN list areused in the network selection procedures. When attempting to select a network the highestpriority EHPLMN that is available shall be selected. If the EHPLMN list is present and isempty or if the EHPLMN list is not present, the HPLMN derived from the IMSI is used fornetwork selection procedures. In the above, the UE is located in the same cell, but the same cell may additionally broadcast other PLMN according to the disaster situation. In this case, if SIB in a cell, in which RRC of the UE is located, is updated and a new PLMN is newly supported in the cell, the UE informs the upper layers of the corresponding content. For example, the NAS layer shall know that Home PLMN of the NAS layer is supported in the current cell, and shall properly allow the UE to attempt again the attach attempt or the registration request operation. Table 15 illustrates the registration operation. TABLE 155.2.2.7 Actions upon reception of SystemInformationBlockType1 messageUpon receiving the SystemInformationBlockType1 or SystemInformationBlockType1-BReither via broadcast or via dedicated signalling, the UE shall:1> if the upper layers indicate the selected core network type as 5GC:2> if the cellAccessRelatedInfoList-5GC contains an entry with the plmn-Identity or plmn-Index of the selected PLMN:3> in the remainder of the procedures use plmn-Identity List, trackingAreaCode, andcellIdentity for the cell as received in the corresponding cellAccessRelatedInfoList-5GCcontaining the selected PLMN.1> else if the cellAccessRelatedInfoList contains an entry with the PLMN-Identity of theselected PLMN:2> in the remainder of the procedures use plmn-Identity List, trackingAreaCode, andcellIdentity for the cell as received in the corresponding cellAccessRelatedInfoListcontaining the selected PLMN.1> if in RRC_IDLE or in RRC_CONNECTED while T311 is running;1> if the UE is a category 0 UE according to TS 36.306 [5];1> if category0Allowed is not included in SystemInformationBlockType1:2> consider the cell as barred in accordance with TS 36.304 [4].1> if in RRC_CONNECTED while T311 is not running, and the UE supports multi-bandcells as defined by bit 31 in featureGroupIndicators:2> disregard the freqBandIndicator and multiBandInfoList, if received, while inRRC_CONNECTED.2> forward the cellIdentity to upper layers.2> forward the trackingAreaCode to upper layers.2> if the received SystemInformationBlockType1 includes plmn-Identity List different fromthe last plmn-Identity List delivered to upper layer;2> or if this is the first received SystemInformationBlockType1 after upper layer requestedinformation available PLMNs2> or if the SystemInformationBlockType1 of the current cell is updated to include HPLMNID2> or if the SystemInformationBlockType1 of the current cell is updated to not includeHPLMN ID3> forward the plmn-IdentityList to upper layers.1> else:2> if the frequency band indicated in the freqBandIndicator is part of the frequency bandssupported by the UE and it is not a downlink only band; or2> if the UE supports multiBandInfoList, and if one or more of the frequency bandsindicated in the multiBandInfoList are part of the frequency bands supported by the UE andthey are not downlink only bands:3> forward the cellIdentity to upper layers.3> forward the trackingAreaCode to upper layers;3> forward the ims-EmergencySupport to upper layers, if present;3> forward the eCallOverIMS-Support to upper layers, if present;3> if the received SystemInformationBlockType1 includes plmn-Identity List different fromthe last plmn-Identity List delivered to upper layer;3> or if this is the first received SystemInformationBlockType1 after upper layer requestedinformation available PLMNs3> or if the SystemInformationBlockType1 of the current cell is updated to include HPLMNID3> or if the SystemInformationBlockType1 of the current cell is updated to not includeHPLMN ID4> forward the plmn-IdentityList to upper layers.3> if the UE is capable of 5G NAS:4> forward the ims-EmergencySupport-5GC to upper layers, if present;4> forward the eCallOverIMS-Support-5GC to upper layers, if present;3> if, for the frequency band selected by the UE (from freqBandIndicator ormultiBandInfoList), the freqBandInfo or the multiBandInfoList-v10j0 is present and the UEcapable of multiNS-Pmax supports at least one additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo or multiBandInfoList-v10j0:4> apply the first listed additionalSpectrumEmission which it supports among the valuesincluded in NS-PmaxList within freqBandInfo or multiBandInfolist-v10j0.4> if the additionalPmax is present in the same entry of the selectedadditionalSpectrumEmission within NS-PmaxList:5> apply the additionalPmax.4> else:5> apply the p-Max .3> else:4> apply the additionalSpectrumEmission in SystemInformationBlockType2 and the p-Max.2> else:3> consider the cell as barred in accordance with TS 36.304 [4].3> perform barring as if intraFreqReselection is set to notAllowed, and as if the csg-Indication is set to FALSE;1> if in RRC_INACTIVE:2> if the cell does not belong to the RAN notification area configured by RAN-Notification AreaInfo:3> initiate the RAN notification area update procedure as specified in 5.3.17.Upon receiving the SystemInformationBlockType1-NB, the UE shall:1> if the frequency band indicated in the freqBandIndicator is part of the frequency bandssupported by the UE; or1> if one or more of the frequency bands indicated in the multiBandInfoList are part of thefrequency bands supported by the UE:2> forward the cellIdentity to upper layers.2> forward the trackingAreaCode to upper layers.2> if the received SystemInformationBlockType1 includes plmn-Identity List different fromthe last plmn-Identity List delivered to upper layer,2> or if this is the first received SystemInformationBlockType1 after upper layer requestedinformation available PLMNs2> or if the SystemInformationBlockType1 of the current cell is updated to include HPLMNID2> or if the SystemInformationBlockType1 of the current cell is updated to not includeHPLMN ID3> forward the plmn-IdentityList to upper layers.2> if attach WithoutPDN-Connectivity is received for the selected PLMN:3> forward the attach WithoutPDN-Connectivity to upper layers.2>else3> indicate to upper layers that attach WithoutPDN-Connectivity is not present.2> if, for the frequency band selected by the UE (from freqBandIndicator ormultiBandInfoList), the freqBandInfo is present and the UE capable of multiNS-Pmaxsupports at least one additionalSpectrumEmission in the NS-PmaxList within thefreqBandInfo:3> apply the first listed additionalSpectrumEmission which it supports among the valuesincluded in NS-PmaxList within freqBandInfo.3> if the additionalPmax is present in the same entry of the selectedadditional SpectrumEmission within NS-PmaxList:4> apply the additionalPmax.3> else:4> apply the p-Max.2> else:3> apply the additionalSpectrumEmission in SystemInformationBlockType2-NB and the p-Max.1> else:2> consider the cell as barred in accordance with TS 36.304 [4].2> perform barring as if intraFreqReselection is set to notAllowed.No UE requirements related to the contents of SystemInformationBlockType1-MBMSapply other than those specified elsewhere e.g. within procedures using the concernedsystem information, and/ or within the corresponding field descriptions. Method 3 Even if a UE is additionally informed that national roaming is allowed in a certain network, a problem still occurs in a new network if a large number of UEs suddenly attempt to access the certain network at once. In particular, for a UE that directly subscribes service to the certain network, and a UE that temporarily performs the access to the certain network from other competitor's network, the certain network needs to selectively control the access of the UE that temporarily performs the access, i.e., perform national roaming. Accordingly, the present disclosure is to propose a method for performing the access control for national roaming in order to achieve this. Method 3-1 A base station can control the access for a UE attempting national roaming or disaster roaming using an access identity. For example, the base station can efficiently control the UE's access as above by extending the access identity as follows and can adjust a load of a system. That is, if the UE attempts to access a new PLMN, the UE may transmit the following access identity to a new network (base station/PLMN). Table 16 illustrates the access identity. TABLE 16Access IdentityNumberUE Configuration0UE is not configured with any parametersfrom this table.1 (NOTE 1)UE is configured for MultimediaPriority Service (MPS).2 (NOTE 2)UE is configured for Mission CriticalService (MCS).4 (NOTE 4)UE trying for national/emergency roaming4-10Reserved for future use11 (NOTE 3)Access Class 11 is configured in the UE.12 (NOTE 3)Access Class 12 is configured in the UE.13 (NOTE 3)Access Class 13 is configured in the UE.14 (NOTE 3)Access Class 14 is configured in the UE.15 (NOTE 3)Access Class 15 is configured in the UE.NOTE 1:Access Identity 1 is used by UEs configured for MPS, in the PLMNs where the configuration is valid. The PLMNs where the configuration is valid are HPLMN, PLMNs equivalent to HPLMN, and visited PLMNs of the home country. Access Identity 1 is also valid when the UE is explicitly authorized by the network based on specific configured PLMNs inside and outside the home country.NOTE 2:Access Identity 2 is used by UEs configured for MCS, in the PLMNs where the configuration is valid. The PLMNs where the configuration is valid are HPLMN or PLMNs equivalent to HPLMN and visited PLMNs of the home country. Access Identity 2 is also valid when the UE is explicitly authorized by the network based on specific configured PLMNs inside and outside the home country.NOTE 3:Access Identities 11 and 15 are valid in Home PLMN only if the EHPLMN list is not present or in any EHPLMN. Access Identities 12, 13 and 14 are valid in Home PLMN and visited PLMNs of home country only. For this purpose the home country is defined as the country of the MCC part of the IMSI.NOTE 4:Access Identity 4 is used for a UE which is accessing a PLMN of same home country as HPLMN. For this purpose the home country is defined as the country of the MCC part of the IMSI. The number of access IDs may be limited at once. In the example, the access identity 4 is an example and may be designated with other value. That is, when the UE attempts to access a specific PLMN, if a PLMN that the UE attempts to access is a PLMN of the same country as a HPLMN of the UE and does not correspond to the access identities 11 to 15 and the access identity 1/2, the UE can check whether its access is barred using the access identity 4. As a result, if the access is allowed, the UE enters a next step for actual RRC connection or NAS signalling or data transmission. In the above process, the UE does not use the access identity 4 for other PLMNs. Method 3-2 Table 17 represents an example using an access category. TABLE 17AccessCategoryNumberConditions related to UEType of access attempt0AllMO signalling resulting frompaging1 (NOTE 1)UE is configured for delay tolerantAll except for Emergencyservice and subject to access controlfor Access Category 1, whichis judged based on relation of UE'sHPLMN and the selected PLMN.2AllEmergency3All except for the conditions inMO signalling on NAS levelAccess Category 1.resulting from other than paging4All except for the conditions inMMTEL voice (NOTE 3)Access Category 1.5All except for the conditions inMMTEL videoAccess Category 1.6All except for the conditions inSMSAccess Category 1.7All except for the conditions inMO data that do not belong toAccess Category 1.any other Access Categories(NOTE 4)8All except for the conditions inMO signalling on RRC levelAccess Category 1.resulting from other than paging9A UE is accessing a PLMN of sameAll except for emergencyhome country but not HPLMN.10-31Reserved standardized AccessCategories32-63 (NOTE 2)AllBased on operator classificationNOTE 1:The barring parameter for Access Category 1 is accompanied with information that define whether Access Category applies to UEs within one of the followingcategories:a) UEs that are configured for delay tolerant service;b) UEs that are configured for delay tolerant service and are neither in their HPLMN nor in a PLMN that is equivalent to it;c) UEs that are configured for delay tolerant service and are neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN. When a UE is configured for EAB, the UE is also configured for delay tolerant service. In case a UE is configured both for EAB and for EAB override, when upper layer indicates to override Access Category 1, then Access Category 1 is not applicable.NOTE 2:When there are an Access Category based on operator classification and a standardized Access Category to both of which an access attempt can be categorized, and the standardized Access Category is neither 0 nor 2, the UE applies the Access Category based on operator classification. When there are an Access Category based on operator classification and a standardized Access Category to both of which an access attempt can be categorized, and the standardized Access Category is 0 or 2, the UE applies the standardized Access Category.NOTE 3:Includes Real-Time Text (RTT).NOTE 4:Includes IMS Messaging. Access Category 0 shall not be barred irrespective of access identities. NOTE: the network can control the amount of access attempts relating to Access Category 0 by controlling whether to send paging or not. That is, the example shows that the UE selects an access category specifically designated for national roaming or disaster roaming in the access categories, and then checks whether there is access barring using the selected access category. In other words, when any UE cannot perform the access due to a problem occurring in a HPLMN of the UE, but when the UE can use other network of the same home country, and when the UE shall access a network, the UE selects the access category and performs the access. Method 3-3 As another method according to the present disclosure, this method configures a value for national roaming in ACB, informs a UE of it via a SIB2 message, and allows a UE to operate based on this. Table 18 illustrates SIB2 information elements of the example. TABLE 18-- ASN1STARTSystemInformationBlockType2 ::=SEQUENCE {ac-BarringInfoSEQUENCE {ac-BarringForEmergencyBOOLEAN,ac-BarringForMO-SignallingAC-BarringConfigOPTIONAL,-- Need OPac-BarringForMO-DataAC-BarringConfigOPTIONAL-- Need OP}OPTIONAL,--NeedOPradioResourceConfigCommonRadioResourceConfigCommonSIB,ue-TimersAndConstantsUE-TimersAndConstants,freqInfoSEQUENCE {ul-CarrierFreqARFCN-ValueEUTRAOPTIONAL,-- Need OPul-BandwidthENUMERATED{n6, n15, n25, n50, n75, n100}OPTIONAL,--NeedOPadditionalSpectrumEmissionAdditionalSpectrumEmission},mbsfn-SubframeConfigListMBSFN-SubframeConfigListOPTIONAL,-- Need ORtimeAlignmentTimerCommonTimeAlignmentTimer,...,lateNonCriticalExtensionOCTETSTRING(CONTAININGSystemInformationBlockType2-v8h0-IEs)OPTIONAL,[[ssac-BarringForMMTEL-Voice-r9AC-BarringConfigOPTIONAL,-- Need OPssac-BarringForMMTEL-Video-r9AC-BarringConfigOPTIONAL-- Need OP]],[[ac-BarringForCSFB-r10AC-BarringConfigOPTIONAL-- Need OP]],[[ac-BarringSkipForMMTELVoice-r12ENUMERATED {true}OPTIONAL,-- Need OPac-BarringSkipForMMTELVideo-r12ENUMERATED {true}OPTIONAL,-- Need OPac-BarringSkipForSMS-r12ENUMERATED {true}OPTIONAL,-- Need OPac-BarringPerPLMN-List-r12AC-BarringPerPLMN-List-r12 OPTIONAL-- Need OPac-BarringPerNationalRoaming]],[[voiceServiceCauseIndication-r12ENUMERATED {true}OPTIONAL-- Need OP]],[[acdc-BarringForCommon-r13ACDC-BarringForCommon-r13OPTIONAL,-- Need OPacdc-BarringPerPLMN-List-r13ACDC-BarringPerPLMN-List-r13OPTIONAL-- Need OP]],[[udt-RestrictingForCommon-r13UDT-Restricting-r13OPTIONAL,-- Need ORudt-RestrictingPerPLMN-List-r13UDT-RestrictingPerPLMN-List-r13OPTIONAL,-- Need ORcIoT-EPS-OptimisationInfo-r13CIOT-EPS-OptimisationInfo-r13OPTIONAL,-- Need OPuseFullResumeID-r13ENUMERATED{true}OPTIONAL-- Need OP]],[[unicastFreqHoppingInd-r13ENUMERATED {true}OPTIONAL-- Need OP]],[[mbsfn-SubframeConfigList-v1430MBSFN-SubframeConfigList-v1430OPTIONAL,-- Need OPvideoServiceCauseIndication-r14ENUMERATED {true}OPTIONAL-- Need OP]],[[plmn-InfoList-r15PLMN-InfoList-r15OPTIONAL-- Need OP]],[[cp-EDT-r15ENUMERATED {true}OPTIONAL,-- Need ORup-EDT-r15ENUMERATED {true}OPTIONAL,-- Need ORidleModeMeasurements-r15ENUMERATED {true}OPTIONAL,-- Need ORreducedCP-Latency Enabled-r15ENUMERATED {true}OPTIONAL-- Need OR]]}SystemInformationBlockType2-v8h0-IEs ::=SEQUENCE {multiBandInfoListSEQUENCE(SIZE(1..maxMultiBands)) OF AdditionalSpectrumEmissionOPTIONAL, -- Need ORnonCriticalExtensionSystemInformationBlockType2-v9e0-IEsOPTIONAL}SystemInformationBlockType2-v9e0-IEs ::= SEQUENCE {ul-CarrierFreq-v9e0ARFCN-ValueEUTRA-v9e0OPTIONAL,-- Cond ul-FreqMaxnonCriticalExtensionSystemInformationBlockType2-v910-IEsOPTIONAL}SystemInformationBlockType2-v910-IEs ::= SEQUENCE {-- Following field is for any non-critical extensions from REL-9nonCriticalExtensionOCTETSTRING(CONTAININGSystemInformationBlockType2-v10m0-IEs)OPTIONAL,dummySEQUENCE { }OPTIONAL}SystemInformationBlockType2-v10m0-IEs ::= SEQUENCE {freqInfo-v10l0SEQUENCE {additionalSpectrumEmission-v10l0AdditionalSpectrumEmission-v10l0}OPTIONAL,multiBandInfoList-v10l0SEQUENCE(SIZE(1..maxMultiBands)) OFAdditionalSpectrumEmission-v10l0OPTIONAL,-- Following field is for non-critical extensions from REL-10nonCriticalExtensionSEQUENCE { }OPTIONAL}AC-BarringConfig ::=SEQUENCE {ac-BarringFactorENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40,p50, p60, p70, p75, p80, p85, p90, p95},ac-BarringTimeENUMERATED {s4, s8,s16, s32, s64, s128, s256, s512},ac-BarringForSpecialACBIT STRING (SIZE(5))}MBSFN-SubframeConfigList ::=SEQUENCE (SIZE (1..maxMBSFN-Allocations))OF MBSFN-SubframeConfigMBSFN-SubframeConfigList-v1430 ::=SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF MBSFN-SubframeConfig-v1430AC-BarringPerPLMN-List-r12 ::=SEQUENCE (SIZE (1.. maxPLMN-r11))OF AC-BarringPerPLMN-r12AC-BarringPerPLMN-r12 ::=SEQUENCE {plmn-Identity Index-r12INTEGER (1..maxPLMN-r11),ac-BarringInfo-r12SEQUENCE {ac-BarringForEmergency-r12BOOLEAN,ac-BarringForMO-Signalling-r12AC-BarringConfigOPTIONAL,-- Need OPac-BarringForMO-Data-r12AC-BarringConfigOPTIONAL-- Need OP}OPTIONAL,-- Need OPac-BarringSkipForMMTELVoice-r12ENUMERATED {true}OPTIONAL,-- Need OPac-BarringSkipForMMTELVideo-r12ENUMERATED {true}OPTIONAL,-- Need OPac-BarringSkipForSMS-r12ENUMERATED {true}OPTIONAL,-- Need OPac-BarringForCSFB-r12AC-BarringConfigOPTIONAL,-- Need OPssac-BarringForMMTEL-Voice-r12AC-BarringConfigOPTIONAL,-- Need OPssac-BarringForMMTEL-Video-r12AC-BarringConfigOPTIONAL-- Need OP}ACDC-BarringForCommon-r13 ::=SEQUENCE {acdc-HPLMNonly-r13BOOLEAN,barringPerACDC-CategoryList-r13BarringPerACDC-CategoryList-r13}ACDC-BarringPerPLMN-List-r13 ::=SEQUENCE (SIZE (1.. maxPLMN-r11))OF ACDC-BarringPerPLMN-r13ACDC-BarringPerPLMN-r13 ::=SEQUENCE {plmn-IdentityIndex-r13INTEGER (1..maxPLMN-r11),acdc-OnlyForHPLMN-r13BOOLEAN,barringPerACDC-CategoryList-r13BarringPerACDC-CategoryList-r13}BarringPerACDC-CategoryList-r13 ::= SEQUENCE (SIZE (1..maxACDC-Cat-r13)) OFBarringPerACDC-Category-r13BarringPerACDC-Category-r13 ::= SEQUENCE {acdc-Category-r13INTEGER(1..maxACDC-Cat-r13),acdc-BarringConfig-r13SEQUENCE {ac-BarringFactor-r13ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40,p50, p60, p70, p75, p80, p85, p90, p95},ac-BarringTime-r13ENUMERATED {s4, s8,s16, s32, s64, s128, s256, s512}}OPTIONAL-- Need OP}UDT-Restricting-r13 ::=SEQUENCE {udt-Restricting-r13ENUMERATED {true}OPTIONAL, -- Need ORudt-RestrictingTime-r13ENUMERATED {s4, s8, s16, s32,s64, s128, s256, s512} OPTIONAL -- Need OR}UDT-RestrictingPerPLMN-List-r13 ::=SEQUENCE (SIZE (1..maxPLMN-r11)) OF UDT-RestrictingPerPLMN-r13UDT-RestrictingPerPLMN-r13 ::= SEQUENCE {plmn-IdentityIndex-r13INTEGER (1..maxPLMN-r11),udt-Restricting-r13UDT-Restricting-r13OPTIONAL-- Need OR}CIOT-EPS-OptimisationInfo-r13 ::=SEQUENCE (SIZE (1.. maxPLMN-r11)) OFCIOT-OptimisationPLMN-r13CIOT-OptimisationPLMN-r13 ::= SEQUENCE {up-CIoT-EPS-Optimisation-r13ENUMERATED {true}OPTIONAL,-- Need OPcp-CIoT-EPS-Optimisation-r13ENUMERATED {true}OPTIONAL,-- Need OPattach WithoutPDN-Connectivity-r13ENUMERATED {true}OPTIONAL-- Need OP}PLMN-InfoList-r15 ::=SEQUENCE (SIZE (1..maxPLMN-r11))OF PLMN-Info-r15PLMN-Info-r15 ::=SEQUENCE {upperLayerIndication-r15ENUMERATED {true}OPTIONAL-- Need OR}-- ASN1STOP Table 19 is an example of SIB2 field descriptions. TABLE 19SystemInformationBlockType2 field descriptionsac-BarringFactorIf the random number drawn by the UE is lower than this value, access is allowed.Otherwise the access is barred. The values are interpreted in the range [0,1): p00 = 0, p05 =0.05, p10 = 0.10, . . . , p95 = 0.95. Values other than p00 can only be set if all bits of thecorresponding ac-BarringForSpecialAC are set to 0.ac-BarringForCSFBAccess class barring for mobile originating CS fallback.ac-BarringForEmergencyAccess class barring for AC 10.ac-BarringForMO-DataAccess class barring for mobile originating calls.ac-BarringForMO-SignallingAccess class barring for mobile originating signalling.ac-BarringForSpecialACAccess class barring for AC 11-15. The first/leftmost bit is for AC 11, the second bit is forAC 12, and so on.ac-BarringPerNationalRoamingAccess Class barring parameter for the UE performing national/emergency roaming.ac-BarringTimeMean access barring time value in seconds.acdc-BarringConfigBarring configuration for an ACDC category. If the field is absent, access to the cell isconsidered as not barred for the ACDC category in accordance with subclause 5.3.3.13.acdc-CategoryIndicates the ACDC category as defined in TS 24.105 [72].acdc-OnlyForHPLMNIndicates whether ACDC is applicable for UEs not in their HPLMN for the correspondingPLMN. TRUE indicates that ACDC is applicable only for UEs in their HPLMN for thecorresponding PLMN. FALSE indicates that ACDC is applicable for both UEs in theirHPLMN and UEs not in their HPLMN for the corresponding PLMN.additional SpectrumEmissionThe UE requirements related to IE AdditionalSpectrumEmission are defined in TS 36.101[42, table 6.2.4-1] for UEs neither in CE nor BL UEs and TS 36.101 [42, table 6.2.4E-1] forUEs in CE or BL UEs. NOTE 1.attach WithoutPDN-ConnectivityIf present, the field indicates that attach without PDN connectivity as specified in TS 24.301[35] is supported for this PLMN.barringPerACDC-Category ListA list of barring information per ACDC category according to the order defined in TS 22.011[10]. The first entry in the list corresponds to the highest ACDC category of whichapplications are the least restricted in access attempts at a cell, the second entry in the listcorresponds to the ACDC category of which applications are restricted more thanapplications of the highest ACDC category in access attempts at a cell, and so on. The lastentry in the list corresponds to the lowest ACDC category of which applications are the mostrestricted in access attempts at a cell.cloT-EPS-OptimisationInfoA list of CIOT EPS related parameters. Value 1 indicates parameters for the PLMN listed 1stin the 1st plmn-IdentityList included in SIB1. Value 2 indicates parameters for the PLMNlisted 2nd in the same plmn-IdentityList, or when no more PLMN are present within the sameplmn-IdentityList, then the value indicates paramters for PLMN listed 1st in the subsequentplmn-IdentityList within the same SIBI and so on. NOTE 1.cp-CIoT-EPS-OptimisationThis field indicates if the UE is allowed to establish the connection with Control plane CIoTEPS Optimisation, see TS 24.301 [35].cp-EDTThis field indicates whether the UE is allowed to initiate CP-EDT, see 5.3.3.1b.DummyThis field is not used in the specification. If received it shall be ignored by the UE.idleModeMeasurementsThis field indicates that the eNB can process indication of IDLE mode measurements fromUE.mbsfn-SubframeConfigListDefines the subframes that are reserved for MBSFN in downlink.NOTE 1. If the cell is a FeMBMS/Unicast mixed cell, EUTRAN includes mbsfn-Subframe ConfigList-v1430. If a FeMBMS/Unicast mixed cell does not use sub-frames #4 or#9 as MBSFN sub-frames, mbsfn-SubframeConfigList-v1430 is still included and indicatesall sub-frames as non-MBSFN sub-frames.multiBandInfoListA list of AdditionalSpectrumEmission i.e. one for each additional frequency band included inmultiBandInfoList in SystemInformationBlockType1, listed in the same order. If E-UTRANincludes multiBandInfoList-v1010 it includes the same number of entries, and listed in thesame order, as in multiBandInfoList.plmn-Identity IndexSystemInformationBlockType2 field descriptionsIndex of the PLMN across the plmn-IdentityList fields included in SIB1. Value 1 indicatesthe PLMN listed 1st in the 1st plmn-IdentityList included in SIB1. Value 2 indicates thePLMN listed 2nd in the same plmn-IdentityList, or when no more PLMN are present withinthe same plmn-IdentityList, then the PLMN listed 1st in the subsequent plmn-IdentityListwithin the same SIBI and so on. NOTE 1.plmn-InfoListIf E-UTRAN includes this field, it includes the same number of entries, and listed in thesame order as PLMNs across the plmn-IdentityList fields included in SIB1. That is, the firstentry corresponds to the first entry of the combined list that results from concatenating theentries included in the second to the original plmn-IdentityList field.reducedCP-Latency EnabledIf present, reduced control plane latency is enabled. UEs supporting reduced CP latencytransmit Msg3 according to k1≥ 5 timing as specified in TS 36.213 [23] when transmittingRRCConnectionResume Request in Msg3.ssac-BarringForMMTEL-VideoService specific access class barring for MMTEL video originating calls.ssac-BarringForMMTEL-VoiceService specific access class barring for MMTEL voice originating calls.udt-RestrictingValue TRUE indicates that the UE should indicate to the higher layers to restrict unattendeddata traffic TS 22.101 [77] irrespective of the UE being in RRC_IDLE orRRC_CONNECTED. The UE shall not indicate to the higher layers if the UE has one ormore Access Classes, as stored on the USIM, with a value in the range 11 . . . 15, which is validfor the UE to use according to TS 22.011 [10] and TS 23.122 [11].udt-RestrictingTimeIf present and when the udt-Restricting changes from TRUE, the UE runs a timer for a periodequal to rand * udt-RestrictingTime, where rand is a random number drawn that is uniformlydistributed in the range 0 ≤ rand < 1 value in seconds. The timer stops if udt-Restrictingchanges to TRUE. Upon timer expiry, the UE indicates to the higher layers that the restrictionis alleviated.unicastFreqHoppingIndThis field indicates if the UE is allowed to indicate support of frequency hopping for unicastMPDCCH/PDSCH/PUSCH as described in TS 36.321 [6]. This field is included only in theBR version of SI message carrying SystemInformationBlockType2.ul-BandwidthSystemInformationBlockType2 field descriptionsParameter: transmission bandwidth configuration, NRB, in uplink, see TS 36.101 [42, table5.6-1]. Value n6 corresponds to 6 resource blocks, n15 to 15 resource blocks and so on. If forFDD this parameter is absent, the uplink bandwidth is equal to the downlink bandwidth. ForTDD this parameter is absent and it is equal to the downlink bandwidth. NOTE 1.ul-CarrierFreqFor FDD: If absent, the (default) value determined from the default TX-RX frequencyseparation defined in TS 36.101 [42, table 5.7.3-1] applies.For TDD: This parameter is absent and it is equal to the downlink frequency. NOTE 1.up-CIoT-EPS-OptimisationThis field indicates if the UE is allowed to resume the connection with User plane CIoT EPSOptimisation, see TS 24.301 [35].up-EDTThis field indicates whether the UE is allowed to initiate UP-EDT, see 5.3.3.1b.upperLayerIndicationIndication to be provided to upper layers.useFullResumeIDThis field indicates if the UE indicates full resume ID of 40 bits inRRCConnectionResume Request.videoServiceCauseIndicationIndicates whether the UE is requested to use the establishment cause mo-VoiceCall formobile originating MMTEL video calls.voiceServiceCauseIndicationIndicates whether UE is requested to use the establishment cause mo-VoiceCall for mobileoriginating MMTEL voice calls. Table 20 is an explanation of SIB2 field. TABLE 20ConditionalPresenceExplanationul-FreqMaxThe field is mandatory present iful-CarrierFreq (i.e. without suffix)is present and set to maxEARFCN.Otherwise the field is not present. NOTE 1: E-UTRAN sets this field to the same value for all instances of SI message that are broadcasted within the same cell. The following Table 21 illustrates an access barring check for national roaming. TABLE 215.3.3.x Access barring check for national roaming1> if timer T302 or “Tbarring” is running:2> consider access to the cell as barred.1> else if SystemInformationBlockType2 includes “ac-BarringPerNationalRoaming”:2> if the selected PLMN is not of same country as the HPLMN or is not HPLMN:3> consider access to the cell as not barred in terms of national barring check.2> else:3> draw a random number ‘rand’ uniformly distributed in the range: 0 ≤ rand < 1;3> if ‘rand’ is lower than the value indicated by ac-BarringFactor included in “ACbarring parameter”:4> consider access to the cell as not barred. ;3> else:4> consider access to the cell as barred.1> else:2> consider access to the cell as not barred.1> if access to the cell is barred and both timers T302 and “Tbarring” are not running:2> draw a random number ‘rand’ that is uniformly distributed in the range 0 ≤ rand < 1.2> start timer “Tbarring” with the timer value calculated as follows, using the ac-BarringTime included in “AC barring parameter”:“Tbarring” = (0.7 + 0.6 * rand) * ac-BarringTime; Method 3-4 The methods 3, 3-1, 3-2 and 3-3 propose a method in which, for UEs performing national roaming, a certain network discriminately provides access control to UEs subscribing to the certain network and UEs subscribing to a surrounding competitor network. However, in the case of national roaming, there is a need to additionally distinguish a network user in which a problem occurs in an actual network, and a network user in which a problem does not occur in an actual network. For example, the following types of subscribers may be considered. Subscriber A: subscribing to operator KA of country K Subscriber B: subscribing to operator KB of country K Subscriber C: subscribing to operator KC of country K Subscriber D: subscribing to operator JD of country J In the above example, if a problem has occurred in the operator KB, the operators KA and KC accept a user subscribing to the operator KB. In this case, the following should be fulfilled:the operator KA accepts users subscribing to the operators KB and JD, but does not accept a subscriber of the operator KCthe operator KC accepts users subscribing to the operators KB and JD, but does not accept a subscriber of the operator KA. That is, in the methods 3, 3-1, 3-2 and 3-3, the above requirements are fulfilled based on that only subscribers corresponding to disaster roaming accept roaming. However, in order for the base station to inform more clearly the UE of an allowed situation and a non-allowed situation, in the examples of the methods 3, 3-1, 3-2, 3-3, the UE additionally transmits information of a PLMN corresponding to each information. Method 3-4-1 Any network may notify accepting roaming for a user of a specific network. In this process, the network informs the UE of an access control parameter (e.g., parameter such as ACB, SSAC, UAC, etc.) applied to the user of the specific network, and a network user corresponding to the above may apply a corresponding specific parameter, i.e., a value designated for each PLMN. That is, the access control parameter corresponding to ACB, or the access category, or the access identity is indicated for each allowed PLMN in which national roaming is allowed, and the corresponding UE applies it according to this. Method 4 A network may indicate, to a UE, whether it accepts national roaming users. The network may indicate whether access control applies specifically to the national roaming users, or indicate a list of PLMNs excluded for normal services or a list of PLMNs accepting national roaming. Preferably, in the above process, the fact that the UE performs the operation according to the present disclosure as above may be based on PLMN codes. That is, when the UE accesses a PLMN with the same MCC from among its PLMN codes, the UE notifies registering to the PLMN for a disaster reason, and does not notify otherwise. Alternatively, in addition, specific PLMNs designated to a SIM card of the UE may be modified so that the operations are performed. Alternatively, in addition, each PLMN may be modified so that the operations are performed on UEs subscribed to a specific PLMN. The present disclosure has described based on HPLMN, but can be applied to cases other than HPLMN. In the present disclosure, the UE may move to other surrounding network according to an indication in a wireless network of HPLMN, or the UE may move to other network when the UE cannot find a wireless network of HPLMN. In the present disclosure, the UE and the network may use subscription information of the UE and identify codes of the network when determining national roaming, disaster roaming, or the process of the purpose equivalent to this. For example, if a mobile country code (MCC) of subscription information is 450 according to subscription information of any UE, the UE may exclude its home network. If a MCC of any network is 450, and the UE attempts to access this network, the UE may determine it as a national roaming process or a disaster roaming process. In addition, even when the UE has equivalent home PLMN (EHPLMN) information the UE may determine similarly it. In addition, the UE may have information that which MCC is determined as home network by other configuration. Main Embodiments of the Present Disclosure FIG.13is a flow chart illustrating a method for a UE to select a network in accordance with an embodiment of the present disclosure. As illustrated inFIG.13, first, a UE may perform a registration to a first PLMN via a first base station, in S1301. Next, when a disaster is applied to the first PLMN, the UE may receive, from the first base station, information related to the disaster applied to a first network, in S1303. Next, the UE may transmit, to a second PLMN, a registration request message including information related to whether a disaster roaming service is applied to the UE, in S1305. Next, the UE may receive, from the second PLMN, a response message to the registration request message. FIG.14is a flow chart illustrating a method for a base station to register a UE to a network in accordance with an embodiment of the present disclosure. As illustrated inFIG.14, first, a base station may perform registering a UE to a first PLMN, in S1401. Next, when a disaster occurs in the first PLMN, the base station may transmit, to the UE, information related to the disaster applied to the first PLMN, in S1403. The information related to the disaster may include an indicator that allows the UE to select other PLMN. Overview of Device to which the Present Disclosure is Applicable FIG.15illustrates a block diagram of configuration of a communication device according to an embodiment of the present disclosure. Referring toFIG.15, a wireless communication system includes a network node1510and a plurality of UEs1520. The network node1510includes a processor1511, a memory1512, and a communication module (or transceiver)1513. The processor1511may implement functions, processes, and/or methods described above with reference toFIGS.1to14. Layers of wired/wireless interface protocol may be implemented by the processor1511. The memory1512is connected to the processor1511and stores various types of information for driving the processor1511. The communication module1513is connected to the processor1511and transmits and/or receives wired/wireless signals. Examples of the network node1510may include a base station, AMF, SMF, UDF, or the like. In particular, if the network node1510is the base station, the communication module1513may include a radio frequency (RF) unit for transmitting/receiving a radio signal. The UE1520includes a processor1521, a memory1522, and a communication module (or RF unit) (or transceiver)1523. The processor1521may implement functions, processes and/or methods described above with reference toFIGS.1to14. Layers of a radio interface protocol may be implemented by the processor1521. In particular, the processor1521may include the NAS layer and the AS layer. The memory1522is connected to the processor1521and stores various types of information for driving the processor1521. The communication module1523is connected to the processor1521and transmits and/or receives a radio signal. The memories1512and1522may be inside or outside the processors1511and1521and may be connected to the processors1511and1521through various well-known means. Further, the network node1510(in case of the base station) and/or the UE1520may have a single antenna or multiple antennas. FIG.16illustrates a block diagram of configuration of a communication device according to an embodiment of the present disclosure. In particular,FIG.16illustrates in more detail the UE illustrated inFIG.15. The communication module illustrated inFIG.15includes an RF module (or RF unit) illustrated inFIG.16. The processor illustrated inFIG.15corresponds to a processor (or a digital signal processor (DSP)1610) inFIG.16. The memory illustrated inFIG.15corresponds to a memory1630illustrated inFIG.16. Referring toFIG.16, the UE may include a processor (or digital signal processor (DSP))1610, an RF module (or RF unit)1635, a power management module1605, an antenna1640, a battery1655, a display1615, a keypad1620, a memory1630, a subscriber identification module (SIM) card1625(which is optional), a speaker1645, and a microphone1650. The UE may also include a single antenna or multiple antennas. The processor1610implements functions, processes, and/or methods described above. Layers of a radio interface protocol may be implemented by the processor1610. The memory1630is connected to the processor1610and stores information related to operations of the processor1610. The memory1630may be inside or outside the processor1610and may be connected to the processors1610through various well-known means. A user inputs instructional information, such as a telephone number, for example, by pushing (or touching) buttons of the keypad1620or by voice activation using the microphone1650. The processor1610receives and processes the instructional information to perform an appropriate function, such as to dial the telephone number. Operational data may be extracted from the SIM card1625or the memory1630. Further, the processor1610may display instructional information or operational information on the display1615for the user's reference and convenience. The RF module1635is connected to the processor1610and transmits and/or receives an RF signal. The processor1610forwards instructional information to the RF module1635in order to initiate communication, for example, transmit a radio signal configuring voice communication data. The RF module1635includes a receiver and a transmitter to receive and transmit the radio signal. The antenna1640functions to transmit and receive the radio signal. Upon reception of the radio signal, the RF module1635may send a signal to be processed by the processor1610and convert the signal into a baseband. The processed signal may be converted into audible or readable information output via the speaker1645. FIG.17illustrates an example of a structure of a radio interface protocol in a control plane between a UE and eNodeB. The radio interface protocol is based on 3GPP radio access network standard. The radio interface protocol horizontally consists of a physical layer, a data link layer, and a network layer, and is vertically divided into a user plane for data information transmission and a control plane for control signaling delivery. The protocol layers may be divided into L1 (first layer), L2 (second layer), and L3 (third layer) based on three lower layers of an open system interconnection (OSI) standard model that is well known in the art of communication systems. The layers of the radio protocol in the control plane illustrated inFIG.17are described below. The physical layer, the first layer, provides an information transfer service using a physical channel. The physical layer is connected to a medium access control (MAC) layer located at a higher level via a transport channel, and data between the MAC layer and the physical layer is transferred via the transport channel. Data is transferred between different physical layers, i.e., between physical layers of a transmission side and a reception side via the physical channel. The physical channel consists of several subframes on a time axis and several subcarriers on a frequency axis. One subframe consists of a plurality of symbols and a plurality of subcarriers on the time axis. One subframe consists of a plurality of resource blocks, and one resource block consists of a plurality of symbols and a plurality of subcarriers. A unit time, a transmission time interval (TTI), at which data is transmitted, is 1 ms corresponding to one subframe. Physical channels existing in the physical layers of the transmission side and the reception side may be divided into, according to 3GPP LTE, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) that are data channels, and a physical downlink control channel (PDCCH), a physical control format indicator channel (PCFICH), a physical hybrid-ARQ indicator channel (PHICH), and a physical uplink control channel (PUCCH) that are control channels. The PCFICH transmitted on a first OFDM symbol of a subframe carries a control format indicator (CFI) regarding the number of OFDM symbols used for transmission of control channels in the subframe (i.e., size of a control region). A wireless device first receives the CFI on the PCFICH and then monitors the PDCCH. Unlike the PDCCH, the PCFICH is transmitted via a fixed PCFICH resource of the subframe without the use of blind decoding. The PHICH carries positive acknowledgement (ACK)/negative acknowledgement (NACK) signal for uplink (UL) hybrid automatic repeat request (HARQ). The ACK/NACK signal for UL data on PUSCH transmitted by the wireless device is transmitted on the PHICH. A physical broadcast channel (PBCH) is transmitted on first four OFDM symbols of a second slot of a first subframe of a radio frame. The PBCH carries system information essential for the wireless device to communicate with the base station, and system information transmitted on the PBCH is referred to as a master information block (MIB). Compared to this, system information transmitted on the PDSCH indicated by the PDCCH is referred to as a system information block (SIB). The PDCCH may carry resource allocation and transport format of a downlink shared channel (DL-SCH), resource allocation information of an uplink shared channel (UL-SCH), paging information on a paging channel (PCH), system information on DL-SCH, resource allocation of an upper layer control message such as a random access response transmitted on PDSCH, a set of Tx power control commands on individual UEs within an arbitrary UE group, a Tx power control command, activation of a voice over internet protocol (VoIP), etc. A plurality of PDCCHs can be transmitted within a control region, and the UE can monitor the plurality of PDCCHs. The PDCCH is transmitted on aggregation of one or multiple consecutive control channel elements (CCEs). The CCE is a logical allocation unit used to provide the PDCCH with a coding rate based on a state of a radio channel. The CCE corresponds to a plurality of resource element groups. A format of the PDCCH and the number of bits of the available PDCCH are determined depending on a correlation between the number of CCEs and the coding rate provided by the CCEs. Control information transmitted on PDCCH is referred to as downlink control information (DCI). The DCI may contain resource allocation of PDSCH (which is also referred to as DL grant), resource allocation of PUSCH (which is also referred to as UL grant), a set of Tx power control commands on individual UEs within an arbitrary UE group, and/or activation of a voice over internet protocol (VoIP). There are several layers in the second layer. First, a medium access control (MAC) layer functions to map various logical channels to various transfer channels, and also performs a function of logical channel multiplexing for mapping several logical channels to one transfer channel. The MAC layer is connected to a radio link control (RLC) layer, that is an upper layer, via the logical channel. The logical channel is roughly divided into a control channel used to transmit information of the control plane and a traffic channel used to transmit information of the user plane, according to a type of transmitted information. The radio link control (RLC) layer of the second layer segments and concatenate data received from the upper layer and adjusts a data size so that a lower layer is adapted to transmit data to a radio section. In order to guarantee various QoS required by each radio bearer (RB), the RLC layer provides three operation modes of a transparent mode (TM), an unacknowledged mode (UM) (non-response mode), and an acknowledged mode (AM) (or response mode). In particular, the AM RLC performs a retransmission function through an automatic repeat and request (ARQ) function for reliable data transmission. A packet data convergence protocol (PDCP) layer of the second layer performs a header compression function of reducing an IP packet header size that has a relatively large size and contains unnecessary control information, in order to efficiently transmit data in a radio section having a small bandwidth upon transmission of IP packet such as IPv4 or IPv6. This allows only information, that is necessarily required in a header part of data, to be transmitted, thereby increasing transmission efficiency of the radio section. In the LTE system, the PDCP layer also performs a security function, which consists of ciphering for preventing data interception by a third party and integrity protection for preventing data manipulation by a third party. A radio resource control (RRC) layer located at the uppermost part of the third layer is defined only in the control plane and is responsible for controlling logical channels, transport channels, and physical channels in relation to configuration, re-configuration, and release of radio bearers (RBs). The RB means services provided by the second layer to ensure data transfer between the UE and the E-UTRAN. If an RRC connection is established between an RRC layer of the UE and an RRC layer of a wireless network, the UE is in an RRC connected mode. Otherwise, the UE is in an RRC idle mode. An RRC state of the UE and an RRC connection method are described below. The RRC state refers to a state in which the RRC of the UE is or is not logically connected with the RRC of the E-UTRAN. The RRC state of the UE having logical connection with the RRC of the E-UTRAN is referred to as an RRC_CONNECTED state, and the RRC state of the UE not having logical connection with the RRC of the E-UTRAN is referred to as an RRC_IDLE state. Since the UE in the RRC_CONNECTED state has the RRC connection, the E-UTRAN can identify the presence of the corresponding UE on a per cell basis and thus efficiently control the UE. On the other hand, the E-UTRAN cannot identify the presence of the UE of the RRC_IDLE state, and the UE in the RRC_IDLE state is managed by a core network based on a tracking area (TA) which is an area unit larger than the cell. That is, for the UE in the RRC_IDLE state, only presence or absence of the corresponding UE is identified in an area unit larger than the cell. In order for the UE of the RRC_IDLE state to receive typical mobile communication services such as voice and data, the UE should transition to the RRC_CONNECTED state. Each TA is distinguished from another TA by a tracking area identity (TAI) thereof. The UE may configure the TAI through a tracking area code (TAC) which is information broadcasted from a cell. When the user initially turns on the UE, the UE first searches for a proper cell, and then establishes RRC connection in the corresponding cell and registers information of the UE in the core network. Thereafter, the UE stays in the RRC_IDLE state. The UE staying in the RRC_IDLE state (re)selects a cell and checks system information or paging information, if necessary. This operation is called camping on a cell. Only when the UE staying in the RRC_IDLE state needs to establish the RRC connection, the UE establishes the RRC connection with the RRC layer of the E-UTRAN through a RRC connection procedure and transitions to the RRC_CONNECTED state. There are several cases where the UE remaining in the RRC_IDLE state needs to establish the RRC connection. Examples of the cases may include a case where transmission of uplink data is necessary for a reason of an attempt of a user to make a phone call, etc., or transmission of a response message when receiving a paging signal from the E-UTRAN. A non-access stratum (NAS) layer performs functions such as session management and mobility management. The NAS layer illustrated inFIG.17is described in detail below. The NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for session management (SM). 1) The NAS entity for MM generally provides the following functions. An NAS procedure related to the AMF includes the following.Registration management and connection management procedure. The AMF supports the functions.Secure NAS signal connection between the UE and the AMF (integrity protection, ciphering) 2) The NAS entity for SM performs session management between the UE and the SMF. A SM signalling message is generated and processed in the UE and the NAS-SM layer of the SMF. The content of the SM signalling message is not interpreted by the AMF.In case of SM signalling transmission,The NAS entity for MM generates security header indicating NAS transmission of SM signalling, and a NAS-MM message deriving a method and location of sending the SM signalling message via additional information for the received NAS-MM.Upon reception of SM signalling, the NAS entity for SM performs integrity check of the NAS-MM message, and derives a method and place of deriving the SM signalling message by interpreting additional information. InFIG.17, the RRC layer, the RLC layer, the MAC layer, and the PHY layer located below the NAS layer are collectively referred to as access stratum (AS) layer. Application Range of the Present Disclosure A wireless device in the present disclosure may be a base station, a network node, a transmitter UE, a receiver UE, a radio device, a wireless communication device, a vehicle, a vehicle with a self-driving function, a drone (unmanned aerial vehicle (UAV)), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, an MTC device, an IoT device, a medical device, a FinTech device (or financial device), a security device, a climate/environment device, or a device related to the fourth industrial revolution field or 5G service, or the like. For example, the drone may be an airborne vehicle that flies by a radio control signal without a person being on the flight vehicle. For example, the MTC device and the IoT device may be a device that does not require a person's direct intervention or manipulation, and may include a smart meter, a vending machine, a thermometer, a smart bulb, a door lock, a variety of sensors, or the like. For example, the medical device may be a device used for the purpose of diagnosing, treating, reducing, handling or preventing a disease and a device used for the purpose of testing, substituting or modifying a structure or function, and may include a device for medical treatment, a device for operation, a device for (external) diagnosis, a hearing aid, or a device for a surgical procedure, or the like. For example, the security device may be a device installed to prevent a possible danger and to maintain safety, and may include a camera, CCTV, a black box, or the like. For example, the FinTech device may be a device capable of providing financial services, such as mobile payment, and may include a payment device, point of sales (POS), or the like. For example, the climate/environment device may refer to a device for monitoring and predicting the climate/environment. Mobile terminals disclosed in the present disclosure may include cellular phones, smart phones, laptop computers, digital broadcast terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigators, slate PCs, tablet PCs, ultra-books, wearable devices (e.g., smart watches, smart glasses, head mounted displays (HMDs)), and the like. Furthermore, the mobile terminals may be used for controlling at least one device in an Internet of Things (IoT) environment or a smart greenhouse. By way of non-limiting example only, further description will be made with reference to particular types of mobile terminals. However, such teachings may be equally applied to other types of mobile terminals, such as those types noted above. In addition, it can be readily apparent to those skilled in the art that these teachings can also be applied to stationary terminals such as digital TV, desktop computers, digital signage, and the like. Hereinafter, embodiments related to a control method which can be implemented by the mobile terminal configured as above were described with reference to the accompanying drawings. It is apparent to those skilled in the art that various modifications can be made to within the range without departing from the spirit and essential features of the present invention. The embodiments of the present disclosure described above can be implemented by various means. For example, embodiments of the present disclosure can be implemented by hardware, firmware, software, or combinations thereof. When embodiments are implemented by hardware, a method according to embodiments of the present disclosure can be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like. When embodiments are implemented by firmware or software, a method according to embodiments of the present disclosure can be implemented by devices, procedures, functions, etc. performing functions or operations described above. Software code can be stored in a memory unit and can be executed by a processor. The memory unit is provided inside or outside the processor and can exchange data with the processor by various well-known means. The present disclosure described above can be implemented using a computer-readable medium with programs recorded thereon for execution by a processor to perform various methods presented herein. The computer-readable medium includes all kinds of recording devices capable of storing data that is readable by a computer system. Examples of the computer-readable mediums include hard disk drive (HDD), solid state disk (SSD), silicon disk drive (SDD), ROM, RAM, CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, other types of storage mediums presented herein, etc. If desired, the computer-readable medium may be implemented in the form of a carrier wave (e.g., transmission over Internet). The computer may include the processor of the terminal. Accordingly, the detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the present disclosure should be determined by rational interpretation of the appended claims, and all modifications within an equivalent scope of the present disclosure are included in the scope of the present disclosure. INDUSTRIAL APPLICABILITY The communication method described above can be applied to various wireless communication systems including IEEE 802.16x and 802.11x systems, in addition to the 3GPP system. Furthermore, the proposed method can be applied to the mmWave communication system using ultra-high frequency bands. | 183,215 |
11943733 | DETAILED DESCRIPTION Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, in the drawings, the same or like elements are designated by the same or like reference signs as much as possible. Further, a detailed description of known functions or configurations that may make the subject matter of the disclosure unclear will be omitted. In describing embodiments of the disclosure, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea. For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals. The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. In the following description, terms for identifying access nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, and the like are illustratively used for the sake of convenience. Therefore, the disclosure is not limited by the terms as used below, and other terms referring to subjects having equivalent technical meanings may be used. In the following description, terms and names defined in the standards for 5G and LTE systems will be used for the convenience of description. However, the disclosure is not limited by these terms and names, and may be applied in the same way to systems that conform other standards. That is, the following detailed description of embodiments of the disclosure will be mainly directed to the communication standards defined by 3GPP. However, based on determinations by those skilled in the art, the main idea of the disclosure may also be applied to other communication systems having similar technical backgrounds through some modifications without significantly departing from the scope of the disclosure. The disclosure proposes a method for managing access by using a NAS protocol in order for data communication in a next-generation 5G communication environment, a method for controlling access, or a device for performing such a function. Particularly, the disclosure enables communication to be performed without restricting (barring) access for communication in the case of performing communication such as an MMTEL voice, MMTEL video, and SMS over IMS by using a IP multimedia subsystem (IMS). Access control is to enable smooth communication under a congestion situation. Such a technology proposes a method for controlling or allowing access of a terminal, and providing a service by using a NAS protocol in an environment in which multiple terminals perform access, for example, an emergency or disaster situation, an environment in which multiple terminals perform access in disaster situations such as earthquake and tidal waves, or a situation where an event-based service occurs due to a cluster of multiple terminals, for example, a situation where it is necessary to control access of a terminal in an environment in which event-based service traffic or a multimedia streaming service occurs in a music event or in a situation where there are crowds in a large stadium. FIG.1illustrates examples of a communication procedure for performing communication having improved communication performance by allowing or controlling access of a terminal by using a NAS protocol in a 5G network, a terminal for a method, and a network environment, according to an embodiment of the disclosure. In an embodiment of the disclosure, assuming a 5G network, entities (or devices), such as user plane function (UPF), session management function (SMF), access and mobility management function (AMF), 5G radio access network (RAN), user data management (UDM), and policy control function (PCF), may configure a network system. For authentication of the entities, an authentication server function (AUSF), and authentication, authorization, and accounting (AAA) may also exist in the system. An N3 interworking function (N3IWF) may be required for the case in which a UE performs communication via non 3GPP access. In addition, in case that the UE performs communication via non 3GPP access, session management may be controlled via a UE, non 3GPP access, N3IWF, and SMF, and mobility management may be controlled via a UE, non 3GPP access, N3IWF, and AMF. In 5G, mobility management and session management entities may be separated into the AMF and SMF. A stand-alone deployment structure which performs communication only with 5G communication entities in order for 5G communication, and a non-stand-alone deployment structure which uses 4G and 5G entities in order for 5G communication have been also considered. There may be P-CSCF and S-CSCF in order to control IMS message signaling for an MMTEL voice, MMTEL video, and SMS over IMS service via an IP multimedia subsystem (IMS). In addition, an IMS AGW (gateway) exists for an IMS service, so that multimedia communication can be performed. The communication network on which the disclosure is based is assumed to be a 5G or 4G LTE network, but the same concept may also be applicable to other systems within a category which can be understood by those skilled in the art. (Method 1) FIG.2illustrates an embodiment of a procedure and a method for performing communication by allowing and controlling access of a terminal by using a NAS protocol in a 5G network environment, according to an embodiment of the disclosure. In operation201, a UE may receive information on an access category from a 5G RAN gNB. For example, the UE may receive access category information via broadcasted information, from the gNB, by using SIB1. The SIB1 is only an embodiment, and the UE may receive the information via any SIB. In operation203, the UE may store the received access category. In relation to the received access category-related information, barring-related information may be explicitly transmitted as information such as an access category-related barring factor and an access category, or may be implicitly transmitted as information including a predefined barring factor and an identifier of barring-related information. In operation211, the UE may perform communication with a UPF via a 5G RAN. In operation221, the UE may perform, via P-CSCF and S-CSCF, an IMS registration process, for example, a registration process for using an MMTEL voice, video, or SMS over IMS. Such a process is a session registration and session setup process for using an MMTEL voice, video, or SMS over IMS. In operation231, the UE may negotiate a session for a service such as an MMTEL voice, video, or SMS over IMS. Via such a session negotiation process, a resource reservation for a service such as an MMTEL voice, video, or SMS over IMS may be made. In addition, the UE may use a relevant service, for example, an MMTEL voice, video, or SMS over IMS. After operation231, for some reason, a situation in which a session for the IMS of the UE is disconnected and an RRC is also released may occur. Subsequent operations241and243to245are processes occurring inside the UE. Referring to operation241, an IMS signal may be transmitted to a NAS layer from an application layer of the UE, for example, an upper layer in charge of an IMS-related service. Such an IMS signal may be, for example, a signal related to mobile originating IMS registration, subscription, and notification. Particularly, for the IMS-related service, the application layer may trigger initiation of an operation in order to transmit an IMS session register message, a reregister or register message, or a signal (subscribe) message for subscription. Alternatively, in case that a notify message for transmission of information to the UE from an IMS-related network node is received, the initiation of the operation may be triggered to receive the notify message to the NAS layer from the upper layer of the UE, for example, the application layer. In operation243, the NAS layer of the UE may map an access attempt type and an access category descended from the upper layer (e.g., the application layer), so as to transmit the same to an AS layer. Alternatively, the NAS layer of the UE may map an access attempt type and an access category according to a signaling indication descended from the upper layer (e.g., the application layer), so as to transmit, to the AS layer, an access category corresponding to the signaling indication descended from the application layer. For example, the upper layer transmits, to the NAS layer, a signal indicating that an MO-IMS-registration-related signal has started, and the NAS layer maps an access attempt type and an access category related to the MO-IMS-registration-related signal. According to an embodiment, the NAS layer may transmit an access category corresponding to the MO-IMS-registration-related signal to the AS layer. In this case, one access category selected by mapping may be transmitted to the AS layer. According to another embodiment, in this case, an access category selected by mapping may be transmitted to multiple AS layers. In this case, the access attempt type may be an access attempt type corresponding to a mobile originating (MO) IMS-related signal such as an IMS register, IMS reregister, IMS subscribe, or IMS notify message. In addition, an access category mapped with the access attempt type may be 9 which is a new access category. Although 9 is taken as an example in the disclosure, 9 to 31 are currently reserved in order for use as a new standard access category, and thus a value from 9 to 31 may be used. Therefore, another value from 9 to 31 may be used as an access category. Thereafter, in operation245, in case that access category information stored in the UE is, for example, at least one of 3 or 7, the AS layer of the UE may determine whether to block access of the UE to a corresponding cell, based on access attempt type information, information of access category 9, and mapping information which are received from an NAS. Alternatively, as an embodiment, based on information which allows barring or access, and an access category-related barring factor stored in the UE, the AS layer of the UE may determine whether to block access of the UE to a corresponding cell, based on the access category information received from the NAS. Specifically, the AS layer may determine whether to block access by using a barring factor included in access class barring (ACB) information which is received. For example, in case that the received ACB value is 7, since a value received from the NAS indicates that an access category in which an access attempt type is mapped to an IMS registration-related value is 9, the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. Alternatively, in case that the received ACB values are 3 and 7, since a value received from the NAS indicates that an access category in which an access attempt type is mapped to an IMS registration-related value is 9, the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. Therefore, in operation251, the UE may transmit an RRC reconfiguration request (RRC reconfiguration request or RRC configuration request) message to the gNB (e.g., 5G NR). As in operation253, the NAS layer of the UE may deliver a service request message to the AMF. Thereafter, as in operation255, in response to the service request message, a service accept message may be transmitted from the AMF to the UE. According to another embodiment, in response to the service request message, a service reject message may be transmitted from the AMF to the UE. Thereafter, in operations261and265, a message such as reregistration, registration, or subscribe, which is IMS signaling, may be transmitted from the UE to the S-CSCF via the P-CSCF. Thereafter, as in operations271and275, a 200 OK message, which is a response to notify that reregistration, registration, or subscribe has succeeded, may be transmitted from the S-CSCF to the UE via the P-CSCF. Subsequent operations281,283, and285are processes occurring inside the UE. Thereafter, as in operation281, an IMS session negotiation-related signal for using a service such as an MMTEL voice, MMTEL video, or SMS over IMS inside the UE, that is, an IMS signal for reservation of a resource for an MMTEL voice, MMTEL video, or SMS over IMS service, for example, a signal such as INVITE or PRACK, may be triggered from the upper layer (e.g., the application layer) to the NAS layer. In operation283, according to an example, in the NAS layer of the UE, in case that an access attempt type corresponds to an MMTEL voice, 4 may be mapped to an access category, in case that the access attempt type corresponds to an MMTEL video, 5 may be mapped to the access category, and in case that the access attempt type corresponds to an SMS over IMS, 6 may be mapped to the access category. Thereafter, in operation285, in case that access category information stored in the UE is, for example, 3, 7, or the like, in the case of the MMTEL voice received from the NAS, the AS layer of the UE may determine whether to block access by using a barring factor included in the received access class barring (ACB) information, based on access attempt type information and information of access category 4. For example, in case that the received ACB value is 3 or 7, since a value received from the NAS indicates access category 4 in which an access attempt type is mapped to an MMTEL voice value, the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. For example, in case that the received ACB value is 4, since a value received from the NAS indicates access category 4 in which an access attempt type is mapped to an MMTEL voice value, the AS layer may block an access attempt from the NAS layer and may not allow access of the UE to a corresponding cell. Thereafter, as in operations291and295, a message such as INVITE or PRACK for an IMS MMTEL video, MMTEL voice, or IMS over SMS may be transmitted from the UE to the S-CSCF via the P-CSCF. Thereafter, as in operations296and297, a 200 OK message, which is a response to notify that the INVITE, PRACK, or the like for the IMS MMTEL video, MMTEL voice, or IMS over SMS, has succeeded, may be transmitted from the S-CSCF to the UE via the P-CSCF. Referring toFIG.2, the following operations may be performed. Among UE operations in a 5GMM-REGISTERED state,an operation of the UE in an ATTEMPTING-REGISTRATION-UPDATE state,1) in case that T3346 is not running when the UE is in 3GPP access,the UE may initiate a mobility and periodic registration update registration procedure upon request for MO-IMS-registration-related signaling from the upper layer (e.g., the application layer).2) in case that T3346 is not running when the UE is in 3GPP non access (e.g., Wi-Fi, etc.),upon request for MO-IMS-registration-related signaling from the upper layer (e.g., the application layer),the UE may initiate a mobility and periodic registration update registration procedure. The above contents are summarized as shown in Table 1-1 below. TABLE 1-15.2.3.2 Detailed description of UE behaviour in state 5GMM-REGISTERED5.2.3.2.3ATTEMPTING-REGISTRATION-UPDATEThe UE in 3GPP access:X) may initiate a registration procedure for mobility and periodicregistration update upon request for an MO-IMS-registration-related-signaling (eg, Register, Subscribe, re-Register, registration,reregistration, subscription refresh) from the upper layers, if timerT3346 is not running;The UE in non-3GPP accessmay initiate a registration procedure for mobility and periodicregistration update upon request for an MO-IMS-registration-related-signaling (eg. Register, Subscribe, re-Register, registration,reregistration, subscription refresh) from the upper layers, if timerT3346 is not running; Among UE operations in a 5GMM-REGISTERED state, an operation of the UE in an ATTEMPTING-REGISTRATION-UPDATE state,1) in case that timer T3346 is not running when the UE is in 3GPP access,the UE may initiate a registration procedure for mobility and periodic registration update upon request for MO-IMS-registration-related signaling from the upper layer (e.g., the application layer).2) in case that T3346 is not running when the UE is in non 3GPP access (e.g., Wi-Fi, etc.),the UE may initiate a registration procedure for mobility and periodic registration update upon request for MO-IMS-registration-related signaling from the upper layer (e.g., the application layer). The above contents are summarized as shown in Table 1-2 below. TABLE 1-25.2.3.2 Detailed description of UE behaviour in state 5GMM-REGISTERED5.2.3.2.3ATTEMPTING-REGISTRATION-UPDATEThe UE in 3GPP access:may initiate a registration procedure for mobility and periodicregistration update upon request for an MO IMS registration relatedsignaling (eg. Register, Subscribe, re-Register, registration,reregistration, subscription refresh) from the upper layers, if timerT3346 is not running;The UE in non-3GPP access:may initiate a registration procedure for mobility and periodicregistration update upon request for an MO IMS registration relatedsignaling (eg. Register, Subscribe, re-Register, reqistration,reregistration, subscription refresh) from the upper layers, if timerT3346 is not running; In case that the UE receives a REGISTRATION REJECT message, the UE takes the following operation according to a 5GMM cause value. For example, in case that the UE receives the REGISTRATION REJECT message from an AMF, the UE may perform the following operations according to a 5GMM cause value included in the message. For 5GMM cause #22 (congestion) In case that a mobility and periodic registration update registration procedure has been initiated in the following situation,1) in the case of MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),2) or in the case of ongoing MO-IMS-registration-related signaling (e.g., a register, sub scribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, for the signaling, in case that the procedure has been initiated for a reason such as NAS signaling connection recovery during access category 9 or an operator defined access category (32 as an embodiment)),the UE provides a notification that a request has been accepted to the upper layer (e.g., the application layer) despite network congestion. The above contents are summarized as shown in Table 2-1 below. TABLE 2-15.5.1.3.5 Mobility and periodic registration update not accepted by thenetworkIf the mobility and periodic registration update request cannot beaccepted by the network, the AMF shall send a REGISTRATIONREJECT message to the UE including an appropriate 5GMM causevalue.The UE shall take the following actions depending on the 5GMM causevalue received in the REGISTRATION REJECT message.5GMM cause #22 (Congestion).If the registration procedure for mobility and periodic registrationupdate was initiated for an MO-IMS-registration-related-signaling (eg.Register, Subscribe; re-Register, registration, reregistration subscriptionrefresh) (ie. access category 9, or operator defined access category(eg.32)) or for NAS signalling connecton recovery during an ongoingan MO-IMS-registration-related-signaling (eg. Register, Subscribe, re-Register, registration, reregistration, subscription refresh) (i.e, accesscategory 9, or operator defined access category (eg.32)) , then anotification that the request was accepted ( despite network congestion)shall be provided to upper layers. In case that the mobility and periodic registration update request cannot be accepted by the network, the AMF transmits a REGISTRATION REJECT message including an appropriate 5GMM cause value to the UE. The UE may take the following operations according to the 5GMM cause value received while being included in the REGISTRATION REJECT message. Case 1 as an embodiment) for 5GMM cause #22 (congestion), In case that a registration procedure for mobility and periodic registration update has been initiated in the following situation,1) for example, an MO MMTEL voice call (e.g., access category 4),2) or MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),3) or for NAS signaling connection recovery during an ongoing MMTEL voice call (e.g., access category 4),4) or in the case of ongoing MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, for the signaling, in case that the procedure has been initiated for a reason such as NAS signaling connection recovery during access category 9 or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) (in case that the UE receives a REGISTRATION REJECT message including a 5GMM cause value which is 22) provides a notification that a request has not been accepted due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 2 as an embodiment) for 5GMM cause #22 (congestion) In case that a registration procedure for mobility and periodic registration update has been initiated in the following situation,1) for example, an MO MMTEL voice call (e.g., access category 4),2) or MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),3) or for NAS signaling connection recovery during an ongoing MMTEL voice call (e.g., access category 4),4) or in the case of an ongoing procedure for MO-IMS-registration-related signaling(e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, for the signaling, in case that the procedure has been initiated for a reason such as NAS signaling connection recovery during access category 9 or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) (in case that the UE receives a REGISTRATION REJECT message including a 5GMM cause value which is 22) provides a notification that a request has not been accepted due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 3 as an embodiment) for 5GMM cause #22 (congestion), In case that a registration procedure for mobility and periodic registration update has been initiated in the following situation,1) for example, in the case of MO-IMS-registration-related signaling (e.g., a register, sub scribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),2) or in the case of ongoing MO-IMS-registration-related signaling (e.g., a register, sub scribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, for the signaling, in case that the procedure has been initiated for a reason such as NAS signaling connection recovery during access category 9 or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) (in case that the UE receives a REGISTRATION REJECT message including a 5GMM cause value which is 22) provides a notification that a request has not been accepted due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 4) as an embodiment) for 5GMM cause #22 (congestion), In case that a registration procedure for mobility and periodic registration update has been initiated in the following situation,1) for example, in the case of MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),2) or in the case of an ongoing procedure for MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, for the signaling, in case that the procedure has been initiated for a reason such as NAS signaling connection recovery during access category 9 or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) (in case that the UE receives a REGISTRATION REJECT message including a 5GMM cause value which is 22) provides a notification that a request has not been accepted due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). The above contents are summarized as shown in Table 2-2 below. TABLE 2-25.5.1.3.5Mobility and periodic registration update not accepted by thenetworkIf the mobility and periodic registration update request cannot beaccepted by the network, the AMF shall send a REGISTRATIONREJECT message to the UE including an appropriate 5GMM causevalue.The UE shall take the following actions depending on the 5GMM causevalue received in the REGISTRATION REJECT message.5GMM cause #22 (Congestion).Case 1)If the registration procedure for mobility and periodic registrationupdate was initiated for an MO MMTEL voice call (i.e. access category4), for an MO IMS registration related signalling (i.e. access category 9),or for NAS signalling connection recovery during an ongoing MOMMTEL voice call (i.e. access category 4) or during an ongoing MOIMS registration related signalling(i.e. access category 9), then anotification that the request was not accepted due to network congestionshall be provided to upper layers.Case 2)If the registration procedure for mobility and periodic registration updatewas initated for an MO MMTEL voice call (i.e. access category 4), foran MO IMS registration related signalling (i.e. access category 9), or forNAS signalling connection recovery during an ongoing MO MMTELvoice call (i.e. access category 4) or during an ongoing procedure forMO IMS registration related signalling(i.e. access category 9), then anotification that the request was not accepted due to network congestionshall be provided to upper layers.Case 3)If the registration procedure for mobility and periodic registration updatewas initiated for an MO IMS registration related signalling (eg. Register,Subscribe, re-Register, registration, reregistration subscription refresh)(i.e. access category 9) or for NAS signalling connection recovery duringan ongoing MO IMS registration related signalling (eg. Register,Subscribe, re-Register, registration, Registration, subscription refresh)(i.e. access category 9), then a notificaton that the request was notacccepted due to network congestion shall be provided to upper layers.Case 4)If the registration procedure for mobility and periodic registration updatewas initiated for an MO IMS registration related signalling (eg. Register,Subscribe, re-Register, registration, reregistration, subscription refresh)(i.e. access category 9) or for NAS signalling connection recovery duringan ongoing procedure for MO IMS registration related signalling (eg.Register, Subscribe, re-Register, registration, reregistration, subscriptionrefresh) (i.e. access category), then a noftification that the request wasnot accepted due to network congestion shall be provided to upper layers. The following abnormal process is defined. In case that T3346 is running,and in case that a mobility and periodic registration update registration procedure has been initiated in the following situation,1) in the case of MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),2) or in the case of ongoing MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, for the signaling, in case that the procedure has been initiated for a reason such as NAS signaling connection recovery during access category 9 or an operator defined access category (32 as an embodiment)),the UE provides a notification that a request has been accepted to the upper layer (e.g., the application layer) despite network congestion. The above contents are summarized as shown in Table 3-1 below. TABLE 3-15.5.1.3.7Abnormal cases in the UEThe following abnormal cases can be identified:a) Timer T3346 is running.If the registration procedure for mobility and periodic registration updatewas initiated for an MO-IMS-registration-related-signaling (eg. Register,Subscribe, re-Register, registration, reregistration, subscription refresh)(i.e. access category 9, or operator defined access category (eg.32)) orfor NAS signalling connection recovery during an ongoing an MO-IMS-registration-related-signaling (eg. Register, Subscribe, re-Register,registration, reregistration, subscription refresh) (i.e. access category 9,or operator defined access category (eg.32)), then a notification that theprocedure was initiated despite network congestion shall be provided toupper layers. In relation to a registration procedure for mobility and periodic registration update, The following abnormal process in the UE is defined. Case 1) In case that timer T3346 is running in the UE,and in case that the registration procedure for mobility and periodic registration update has been initiated in the following situation,1) in case that the registration procedure has been initiated for an MO MMTEL voice call (e.g., access category 4),2) or in case that the registration procedure has been initiated for MO-IMS-registration-related signaling (e.g., a register, sub scribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),3) or in case that the registration procedure has been initiated for NAS signaling connection recovery during an ongoing MO MMTEL voice call (e.g., access category 4),4) or in case that the registration procedure has been initiated for a reason such as NAS signaling connection recovery during (ongoing) MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) provides a notification that the procedure has not been initiated due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 2) In case that timer T3346 is running in the UE,and in case that the registration procedure for mobility and periodic registration update has been initiated in the following situation,1) in case that the registration procedure has been initiated for an MO MMTEL voice call (e.g., access category 4),2) or in case that the registration procedure has been initiated for MO-IMS-registration-related signaling (e.g., a register, sub scribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),3) or in case that the registration procedure has been initiated for NAS signaling connection recovery during an ongoing MO MMTEL voice call (e.g., access category 4),4) or in case that the registration procedure has been initiated for a reason such as NAS signaling connection recovery during a (ongoing) procedure of MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) provides a notification that the procedure has not been initiated due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 3) In case that timer T3346 is running in the UE,and in case that the registration procedure for mobility and periodic registration update has been initiated in the following situation,1) that is, in case that the registration procedure has been initiated for MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),2) or in case that the registration procedure has been initiated for a reason such as NAS signaling connection recovery during (ongoing) MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) provides a notification that the procedure has not been initiated due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 4) In case that timer T3346 is running in the UE,and in case that the registration procedure for mobility and periodic registration update has been initiated in the following situation,1) that is, in case that the registration procedure has been initiated for MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),2) or in case that the registration procedure has been initiated for a reason such as NAS signaling connection recovery during a (ongoing) procedure of MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),the UE (in the UE, inside the UE) provides a notification that the procedure has not been initiated due to network congestion (from the NAS layer) to the upper layer (e.g., the application layer). The above contents are summarized as shown in Table 3-2 below. TABLE 3-25.5.1.3 Registration procedure for mobility and periodic registrationupdate5.5.1.3.7Abnormal cases in the UEThe following abnormal cases can be identified:a) Timer T3346 is running.Case 1)If the registration procedure for mobility and perodic registration updatewas initiated for an MO MMTEL voice call (i.e. access category 4), foran MO IMS registration related signalling (i.e. access category 9), or forNAS signalling connection recovery during an ongoing MO MMTELvoice call (i.e. access category 4) or during an ongoing MO IMSregstration related signalling(i.e access catgory 9), then a notificationthat the procedure was not initiated due to network congestion shall beprovided to upper layers.Case 2)If the registration for mobility and peridoic registration update wasinitiated for an MO MMTEL voice call (i.e. access category 4), for anMO IMS registration related signalling (i.e. access category 9), or forNAS signalling connection recovery during an ongoing MO MMTELvoice call (i.e. access category 4) or during an ongoing procedure forMO IMS registration related signalling (i.e. access category 9), then anotification that the procedure was not intiated due to networkcongestion shall be provided to upper layers.Case 3)If the registration procedure for mobility and periodic registration updatewas initiated for an MO IMS registration related signalling (i.e. accesscategory 9) (eg. Register, Subscribe, re-Register, registration,reregistration, subscription refresh) (or operator defined access category(eg.32) or for NAS signalling connection recovery during an ongoingMO IMS registration related signalling (i.e. access category 9) (eg.Register, Subscribe, re-Register, registration, reregistration, subscriptionrefresh) (or operator defined access category (eg. 32)), then a notificationthat the procedure was not initiated due to network congestion shall beprovided to upper layers.Case 4)If the registration procedure for mobility and periodic registration updatewas initiated for an MO IMS registration related signalling (i.e. accesscategory 9) or for NAS signalling connection recovery during an ongoingprocedure for MO IMS registration related signalling (i.e. access category9), then a notification that the procedure was not initiated due to networkcongestion shall be provided to upper layers. As described above, the NAS layer of the UE may deliver a service request message to the AMF. In this case, in response to the service request message for a predetermined reason, a service reject message may be transmitted from the AMF to the UE. In case that the UE receives the service reject message, the UE takes the following operation according to a 5GMM cause value. For 5GMM cause #22 (congestion) In case that a service request procedure has been initiated in the following situation,1) MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),the UE provides a notification that a request has been accepted to the upper layer (e.g., the application layer) despite network congestion. The above contents are summarized as shown in Table 4-1 below. TABLE 4-15.6.1.5 Service request procedure not accepted by the networkIf the service request cannot be accepted, the network shall return aSERVICE REJECT message to the UE including an appropriate 5GMMcause value.The UE shall take the following actions depending on the 5GMM causevalue received in the SERVICE REJECT message.5GMM cause #22 (Congestion).If the service request procedure was initiated for an MO-IMS-registration-related-signaling (eg. Register, Subscribe, re-Register,registration, reregistration, subscription refresh) (i.e. access category 9,or operator defined access category (eg.32)), a notification that theservice request was accepted ( despite congestion ) shall be providedto the upper layers. In case that the network cannot accept a service request, a service reject message including a 5GMM cause value may be transmitted to the UE. The UE takes the following operation according to a 5GMM cause value (received) and while being (included) in the service reject message. For 5GMM cause #22 (congestion) In case that a service request procedure has been initiated in the following situation, Case 1) as an embodiment, In case that the service request procedure has been initiated for an MO MMTEL voice call (access category 4) or MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),in case that the UE receives 5GMM cause 22,the UE (in the UE, inside the UE) provides a notification that a request (or service request) has not been accepted due to (network) congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 2) as an embodiment,1) in case that the service request procedure has been initiated for MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling) (in addition, access category 9 for the signaling, or an operator defined access category (32 as an embodiment)),in case that the UE receives 5GMM cause 22,the UE (in the UE, inside the UE) provides a notification that the request (or service request) has not been accepted due to (network) congestion (from the NAS layer) to the upper layer (e.g., the application layer). The above contents are summarized as shown in Table 4-2 below. TABLE 4-25.6.1.5 Service request procedure not accepted by the networkIf the service request cannot be accepted, the network shall return aSERVICE REJECT message to the UE including an appropriate5GMM cause value.The UE shall take the following actions depending on the 5GMM causevalue received in the SERVICE REJECT message.5GMM cause #22 (Congestion).Case1 )If the service request procedure was iniated for an MO MMTEL voicecall (i.e. access category 4) or for an MO IMS registration relatedsignalling(i.e. access category 9), a notification that the service requestwas not accepted due to congestion shall be provided to the upper layers.Case 2)If the service request procedure was initiated for an MO IMS registrationrelated signalling (i.e. access category 9) (eg. Register, Subscribe,re-Register, registraation, reregistration, subscription refresh) (oroperator defined access category (eg. 32)), a notification that the servicerequest was not accepted due to congestion shall be provided to the upperlayers. In addition, in the service request procedure,a non-ideal situation of the UE, for example, in case that T3517 expires, a non-ideal situation occurs. The UE enters a 5GMM-REGISTERED state. In case that a service request attempt counter is equal to or greater than 5,the UE starts T3525. In addition,in case that the service request procedure has been initiated in the following situation,1) MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling)the UE provides a notification that a request has been accepted to the upper layer (e.g., the application layer) although T3525 has started. The above contents are summarized as shown in Table 5-1 below. TABLE 5-1Service request procedure5.6.1.7 Abnormal cases in the UEThe following abnormal cases can be identified:a) T3517 expired.The UE shall enter the state 5GMM-REGISTERED.If the service request attempt counter is greater than or equal to 5, theUE shall start timer T3525. Additionally, if the service request wasinitiated for an MO-IMS-registration-related-signaling (eg. Register,Subscribe, re-Register, registration, reregistration, subscription refresh) ,a notification that the service request was accepted despite the UEhaving started timer T3525 shall be provided to the upper layers. In addition, in the service request procedure,a non-ideal situation of the UE, for example, in case that T3517 expires, a non-ideal situation occurs. The UE enters a 5GMM-REGISTERED state.In case that a service request attempt counter is equal to or greater than 5, the UE initiates T3525. Case 1) In addition,in case that a service request procedure has been initiated in the following situation,1) that is, for MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling)or for an MO MMTEL voice call,in case that the service request procure has been initiated,the UE (in the UE) provides a notification that a service request has not been accepted (from the NAS layer) to the upper layer (e.g., the application layer) due to the (UE having) started timer T3525. Case 2) In addition,in case that a service request procedure has been initiated in the following situation,that is, for MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling),in case that the service request procure has been initiated,the UE (in the UE) provides a notification that a service request has not been accepted (from the NAS layer) to the upper layer (e.g., the application layer) due to the (UE having) started timer T3525. The above contents are summarized as shown in Table 5-2 below. TABLE 5-2Service request procedure5.6.1.7 Abnormal cases in the UEThe following abnormal cases can be identified:a) T3517 expired,The UE shall enter the state 5GMM-REGISTERED.If the service request attempt counter is greater than or equal to 5, theUE shall start timer T3525. Additionally, if the service request wasinitiated for an MO MMTEL voice call or an MO IMS registrationrelated signalling, a notification that the service request was notaccepted due to the UE having started timer T3525 shall be provided tothe upper layers.If the service request attempt counter is greater than or equal to 5, theUE shall start timer T3525.Additionally, if the service request was initiated for an MO IMSregistration related signalling (eg. Register, Subscribe, re-Register,registration, reregistration, subscription refresh), a notification that theservice request was not accepted due to the UE having started timerT3525 shall be provided to the upper layers. In addition, in the service request procedure,a non-ideal situation of the UE, for example, in case that T3346 is running, the following non-ideal situation occurs. In case that T3346 is running,or in case that a service request procedure has been triggered in the following situation,1) MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling),the UE provides a notification that a request has been accepted to the upper layer (e.g., the application layer) despite congestion. The above contents are summarized as shown in Table 6-1 below. TABLE 6-1Service request procedure5.6.1.7 Abnormal cases in the UEThe following abnormal cases can be identified:c) Timer T3346 is running.If the service request procedure was triggered for an MO-IMS-registration-related-signaling (eg, Register, Subscribe, re-Register,registration, reregistration, subscription refresh) (i.e. access category 9,or operator defined access category (eg.32)), a notification that the servicerequest procedure was intiated despite congestion shall be provided to theupper layers. In addition, in the service request procedure,a non-ideal situation of the UE, for example, in case that T3346 is running, the following non-ideal situation occurs. In case that T3346 is running,or in case that a service request procedure has been triggered in the following situation, Case 1) in case that the service request procedure has been triggered for MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling)or for an MO MMTEL voice call,the UE (in the UE) provides a notification that the service request procedure has not been initiated due to congestion (from the NAS layer) to the upper layer (e.g., the application layer). Case 2) in the case of MO-IMS-registration-related signaling (e.g., a register, subscribe, re-register, registration, reregistration, and subscription refresh message or signaling)the UE (in the UE) provides a notification that the service request procedure has not been initiated due to congestion (from the NAS layer) to the upper layer (e.g., the application layer). The above contents are summarized as shown in Table 6-2 below. TABLE 6-2Service request procedure5.6.1.7 Abnormal cases in the UEThe following abnormal cases can be identified:c) Timer T3346 is running.Case 1)If the service request procedure was triggered for an MO MMTEL voicecall i.e. access category 4) or an MO IMS registration related signalling(i.e access category 9), a notification than the service request procedurewas not iniatiated due to congestion shall be provided to the upper layers.Case 2)If the service request procedure was triggered for an MO IMS registrationrelated signaling(eg. Register, Subscribe, re-Register, registration,reregistration, subscription refresh) (i.e. access category 9, or operatordefined access category (eg.32)), a notification that the service requestprocedure was not initiated due to congestion shall be provided to theupper layers. (Method 2) FIG.3illustrates an embodiment of a procedure and a method for performing communication by allowing and controlling access of a terminal by using a NAS protocol in a 5G network environment, according to another embodiment of the disclosure. In operation301, a UE may receive information on an access category from a 5G RAN gNB. For example, the UE may receive access category information via broadcasted information by using SIB1. In operation303, the UE may store the received access category. In operation311, the UE may perform communication with a UPF via a 5G RAN. In operation321, the UE may perform, via P-CSCF and S-CSCF, an IMS registration process, for example, a registration process for using an MMTEL voice, video, or SMS over IMS. Such a process is a session registration and session setup process for using an MMTEL voice, video, or SMS over IMS. In operation331, the UE may negotiate a session for a service such as an MMTEL voice, video, or SMS over IMS. Via such a session negotiation process, a resource reservation for a service such as an MMTEL voice, video, or SMS over IMS may be made. In addition, the UE may use IMS, MMTEL, SMS over IMS-related services, for example, an MMTEL voice, video, or SMS over IMS. After operation331, for some reason, a situation in which a session for the IMS of the UE is disconnected and an RRC is also released may occur. Subsequent operations341and343to345are processes occurring inside the UE. Referring to operation341, an IMS signal may be transmitted to a NAS layer from an application layer of the UE, for example, an upper layer in charge of an IMS-related service. Such an IMS signal corresponds to, for example, a signal related to mobile originating IMS registration, subscription, and notification. Specifically, for an IMS-related service, the application layer may trigger initiation of an operation in order to transmit an IMS session register message, a reregister or register message, or a signal (subscribe) message for subscription. Alternatively, in case that a notify message for transmission of information to the UE from an IMS-related network node is received, the initiation of the operation may be triggered to receive the notify message to the NAS layer from the upper layer of the UE, for example, the application layer. In operation343the NAS layer of the UE may map an access attempt type and an access category descended from the upper layer (e.g., the application layer), so as to transmit the same to an AS layer. Alternatively, the NAS layer of the UE may map an access attempt type and an access category according to a signaling indication descended from the upper layer (e.g., the application layer), so as to transmit, to the AS layer, an access category corresponding to the signaling indication. For example, the upper layer transmits, to the NAS layer, a signal indicating that an MO-IMS-registration-related signal has started, and the NAS layer maps an access attempt type and an access category related to the MO-IMS-registration-related signal. According to an embodiment, the NAS layer may transmit an access category corresponding to the MO-IMS-registration-related signal to the AS layer. In this case, one access category selected by mapping may be transmitted to the AS layer. According to another embodiment, in this case, an access category selected by mapping may be transmitted to multiple AS layers. In this case, the access attempt type may be an access attempt type corresponding to a mobile originating (MO) IMS-related signal such as an IMS register, IMS reregister, IMS subscribe, or IMS notify message. In addition, an access category mapped with the access attempt type may be an operator defined access category. Therefore, in the case of the operator defined access category, values from 32 to 63 may be used, and thus an access category value configured in a corresponding operator network may be an access category for a mobile originating IMS-related signal, for example, an IMS register, IMS reregister, IMS subscribe, or IMS Notify message, and the like. In the disclosure, an example in which number 32 is used as the operator defined access category will be described. Thereafter, in operation345, in case that access category information stored in the UE is, for example, at least one of 3 or 7, the AS layer of the UE may determine whether to block access of the UE to a corresponding cell, based on access attempt type information and information of access category 32 received from an NAS. Specifically, the AS layer may determine whether to block access by using a barring factor included in access class barring (ACB) information which is received. Alternatively, as an embodiment, based on information which allows barring or access, and an access category-related barring factor stored in the UE, the AS layer of the UE may determine whether to block access of the UE to a corresponding cell, based on the access category information received from the NAS. For example, in case that the received ACB value is 7, since a value received from the NAS indicates access category 32 in which an access attempt type is mapped to an IMS registration-related value, the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. Alternatively, in case that the received ACB values are 3 and 7, since a value received from the NAS indicates access category 9 in which an access attempt type is mapped to an IMS registration-related value, the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. Therefore, in operation351, the UE may transmit an RRC reconfiguration request or RRC configuration request message to the gNB (e.g., 5G NR). As in operation353, the NAS layer of the UE may deliver a service request message to an AMF. Thereafter, as in operation355, in response to the service request message, a service accept message may be transmitted from the AMF to the UE. Thereafter, in operations361and365, a message such as reregistration, registration, or subscribe, which is IMS signaling, may be transmitted from the UE to the S-CSCF via the P-CSCF. Thereafter, as in operations371and375, a 200 OK message, which is a response to notify that reregistration, registration, or subscribe has succeeded, may be transmitted from the S-CSCF to the UE via the P-CSCF. Subsequent operations381,383, and385are processes occurring inside the UE. Thereafter, as in operation381, a signal related to IMS session negotiation for using a service such as an MMTEL voice, MMTEL video, or SMS over IMS inside the UE, that is, an IMS signal for reservation of a resource for an MMTEL voice, MMTEL video, or SMS over IMS service, for example, a signal such as INVITE or PRACK, may be triggered from the upper layer (e.g., the application layer) to the NAS layer. In operation383, according to an example, in the NAS layer of the UE, in case that an access attempt type corresponds to an MMTEL voice, 4 may be mapped to an access category, in case that the access attempt type corresponds to an MMTEL video, 5 may be mapped to the access category, and in case that the access attempt type corresponds to an SMS over IMS, 6 may be mapped to the access category. Thereafter, in operation385, in case that access category information stored in the UE is, for example, 3, 7, or the like, in the case of the MMTEL voice received from the NAS, the AS layer of the UE may determine whether to block access by using a barring factor included in the received access class barring (ACB) information, based on access attempt type information and information of access category 4. For example, in case that the received ACB value is 3 or 7, since a value received from the NAS indicates access category 4 in which an access attempt type is mapped to an MMTEL voice value, the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. For example, in case that the received ACB value is 4, since a value received from the NAS indicates access category 4 in which an access attempt type is mapped to an MMTEL voice value, the AS layer may block an access attempt from the NAS layer and may not allow access of the UE to a corresponding cell. Thereafter, as in operations391and395, a message such as INVITE or PRACK for an IMS MMTEL video, MMTEL voice, or IMS over SMS may be transmitted from the UE to the S-CSCF via the P-CSCF. Thereafter, as in operations396and398, a 200 OK message, which is a response to notify that the INVITE, PRACK, or the like for the IMS MMTEL video, MMTEL voice, or IMS over SMS, has succeeded, may be transmitted from the S-CSCF to the UE via the P-CSCF. FIG.4illustrates an embodiment of a procedure and a method for performing communication by allowing and controlling access of a terminal by using a NAS protocol in a 5G network environment, according to an embodiment of the disclosure. In operation401, a UE may receive information on an access category from a 5G RAN gNB. For example, the UE may receive access category information via broadcasted information, from the gNB, by using SIB1. In operation403, the UE may store the received access category. In operation411, the UE may perform communication with a UPF via a 5G RAN. In operation421, the UE may perform, via P-CSCF and S-CSCF, an IMS registration process, for example, a registration process for using an MMTEL voice, video, or SMS over IMS. Such a process is a session registration and session setup process for using an MMTEL voice, video, or SMS over IMS. In operation531, the UE may negotiate a session for a service such as an MMTEL voice, video, or SMS over IMS. Via such a session negotiation process, a resource reservation for a service such as an MMTEL voice, video, or SMS over IMS may be made. In addition, the UE may use a relevant service, for example, an MMTEL voice, video, or SMS over IMS. After operation531, for some reason, a situation in which a session for the IMS of the UE is disconnected and an RRC is also released may occur. Subsequent operations441and443to445are processes occurring inside the UE. Referring to operation441, an IMS signal may be transmitted to a NAS layer from an application layer of the UE, for example, an upper layer in charge of an IMS-related service. Such an IMS signal corresponds to, for example, a signal related to mobile originating IMS registration, subscription, and notification. Specifically, for an IMS-related service, the application layer may trigger initiation of an operation in order to transmit an IMS session register message, a reregister or register message, or a signal (subscribe) message for subscription. Alternatively, in case that a notify message for transmission of information to the UE from an IMS-related network node is received, the initiation of the operation may be triggered to receive the notify message to the NAS layer from the upper layer of the UE, for example, the application layer. In operation443, the NAS layer of the UE may map an access attempt type and an access category descended from the upper layer (e.g., the application layer), so as to transmit the same to an AS layer. Alternatively, the NAS layer of the UE may map an access attempt type and an access category according to a signaling indication descended from the upper layer (e.g., the application layer), so as to transmit, to the AS layer, an access category corresponding to the signaling indication. For example, the upper layer transmits, to the NAS layer, a signal indicating that an MO-IMS-registration-related signal has started, and the NAS layer maps an access attempt type and an access category related to the MO-IMS-registration-related signal. According to an embodiment, the NAS layer may transmit an access category corresponding to the MO-IMS-registration-related signal to the AS layer. In this case, one access category selected by mapping may be transmitted to the AS layer. According to another embodiment, in this case, an access category selected by mapping may be transmitted to multiple AS layers. In this case, the access attempt type may be an access attempt type corresponding to a mobile originating (MO) IMS-related signal such as an IMS register, IMS reregister, IMS subscribe, or IMS notify message. In addition, an access category mapped with the access attempt type may use an existing access category. Further, in the case of using such an existing access category, there is separate information (e.g., an indicator, an indication bit, etc.) as an SIB, so that a terminal is required to be able to determine whether corresponding information exists or whether a corresponding bit is set. That is, in the case where such an indicator or indication bit exists, even in case that the existing access category is used, the access category may not be blocked by referring to the corresponding indicator or indication bit. For example, number 7 may be used in the case of mobile originating data, that is, MO-data, or number 4 may be used in relation to an MMTEL voice, number 5 may be used in relation to an MMTEL video, and number 6 may be used in relation to an SMS over IMS. That is, in the case of mapping IMS-registration-related signaling (e.g., register, subscribe, etc.) to an access category of number 4, 5, or 6, or number 7, the AS layer may be informed whether a signal is related to IMS session setup. That is, such a case indicates that an access category and an access attempt type referred to as mobile originating (MO) IMS-related signal such as an IMS register, IMS reregister, IMS subscribe, and IMS Notify message are mapped and reported to the AS layer. In this case, even in case that the access category corresponds to number 4, 5, 6, or 7, in case that the AS layer receives mapping information from the NAS layer, the corresponding mapping information is separated from access category #4 for an MMTEL voice, access category #5 for an MMTEL video, access category #6 for an SMS over IMS, and general mobile originating data (MO-data), and in case that the AS layer performs a check related to access barring, the corresponding signal may be processed separately from the MMTEL voice, MMTEL video, SMS over IMS, or MO-data. Thereafter, in operation445, in case that access category information stored in the UE is, for example, at least one of 3 or 7, the AS layer of the UE may determine whether to block access of the UE to a corresponding cell, based on access attempt type information, information of access category, and mapping information which are received from an NAS. Specifically, the AS layer may determine whether to block access by using a barring factor included in access class barring (ACB) information which is received. Alternatively, as an embodiment, based on information which allows barring or access, and an access category-related barring factor stored in the UE, the AS layer of the UE may determine whether to block access of the UE to a corresponding cell, based on the access category information received from the NAS. In this case, the AS layer may allow access by using information such as an indicator which does not block access in the case of IMS-related signaling (an IMS register signal, subscribe, reregister, etc.), that is, an indicator which does not perform access barring, an indicator which can skip access barring, or an indication bit, as well as a barring factor (blocking factor) included in the ACB information. According to an embodiment, in the case where an access category received via an SIB is 4 and the IMS registration is performed again for an MMTEL voice, in case that the received ACB value is 4, a value received from the NAS indicates a case where an access attempt type corresponds to a value related to IMS registration and an access category mapped thereto is 4, but the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. According to another embodiment, in the case where an access category received via an SIB is 5 and the IMS registration is performed again for an MMTEL video, in case that the received ACB value is 5, a value received from the NAS indicates a case where an access attempt type corresponds to a value related to IMS registration and an access category mapped thereto is 5, but the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. According to still another embodiment, in the case where an access category received via an SIB is 6 and the IMS registration is performed again for an SMS over SMS, in case that the received ACB value is 6, a value received from the NAS indicates a case where an access attempt type corresponds to a value related to IMS registration and an access category mapped thereto is 6, but the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. According to still another embodiment, in the case where an access category received via an SIB is 7 and the IMS registration is performed again for MO data, in case that the received ACB value is 7, a value received from the NAS indicates a case where an access attempt type corresponds to a value related to IMS registration and an access category mapped thereto is 7, but the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. Therefore, in operation451, the UE may transmit an RRC reconfiguration request (RRC reconfiguration request or RRC configuration request) message to the gNB (e.g., 5G NR). As in operation453, the NAS layer of the UE may deliver a service request message to an AMF. Thereafter, as in operation455, in response to the service request message, a service accept message may be transmitted from the AMF to the UE. Thereafter, in operations461and465, a message such as reregistration, registration, or subscribe, which is IMS signaling, may be transmitted from the UE to the S-CSCF via the P-CSCF. Thereafter, as in operations471and475, a 200 OK message, which is a response to notify that reregistration, registration, or subscribe has succeeded, may be transmitted from the S-CSCF to the UE via the P-CSCF. Subsequent operations481and483to485are processes occurring inside the UE. Thereafter, as in operation481, a signal related to IMS session negotiation for using a service such as an MMTEL voice, MMTEL video, or SMS over IMS inside the UE, that is, an IMS signal for reservation of a resource for an MMTEL voice, MMTEL video, or SMS over IMS service, for example, a signal such as INVITE or PRACK, may be triggered from the upper layer (e.g., the application layer) to the NAS layer. In operation583, according to an example, in the NAS layer of the UE, in case that an access attempt type corresponds to an MMTEL voice, 4 may be mapped to an access category, in case that the access attempt type corresponds to an MMTEL video, 5 may be mapped to the access category, and in case that the access attempt type corresponds to an SMS over IMS, 6 may be mapped to the access category. Thereafter, in operation585, in case that access category information stored in the UE is, for example, at least one of 3 or 7, in the case of the MMTEL voice received from the NAS, the AS layer of the UE may determine whether to block access by using a barring factor included in the received access class barring (ACB) information, based on access attempt type information and information of access category 4. For example, in case that the received ACB value is 3 or 7, since a value received from the NAS indicates access category 4 in which an access attempt type is mapped to an MMTEL voice value, the AS layer may allow access of the UE to a corresponding cell without blocking an access attempt from the NAS layer. For example, in case that the received ACB value is 4, since a value received from the NAS indicates access category 4 in which an access attempt type is mapped to an MMTEL voice value, the AS layer may block an access attempt from the NAS layer and may not allow access of the UE to a corresponding cell. Thereafter, as in operations491and495, a message such as INVITE or PRACK for an IMS MMTEL video, MMTEL voice, or IMS over SMS may be transmitted from the UE to the S-CSCF via the P-CSCF. Thereafter, as in operations496and498, a 200 OK message, which is a response to notify that the INVITE, PRACK, or the like for the IMS MMTEL video, MMTEL voice, or IMS over SMS, has succeeded, may be transmitted from the S-CSCF to the UE via the P-CSCF. FIG.5is a block diagram illustrating a structure of a terminal, according to an embodiment of the disclosure. Referring toFIG.5, a terminal may include a transceiver510, a controller520, and a storage530. In the disclosure, the controller520may be defined as a circuit or an application-specific integrated circuit, or at least one processor. The transceiver510may transmit or receive a signal to or from other network entities. For example, the transceiver510may receive system information from a base station, and may receive a synchronization signal or a reference signal. Specifically, the transceiver510may receive SIB 1 including information on an access category. In addition, the transceiver510may receive a message from an AMF. The controller520may control the overall operation of the terminal according to the embodiments proposed in the disclosure. For example, the controller520may control a signal flow between blocks so as to perform the operation according to the above-described flowchart. Specifically, according to an embodiment of the disclosure, the controller520may control an operation proposed in the disclosure to control access barring for an IMS-related signal and an IMS service-related signal. Specifically, the controller520may control to cause an application layer to generate a mobile originating (MO) Internet protocol (IP) multimedia subsystem (IMS) registration-related IMS signal generated in the terminal, control to cause a non-access stratum (NAS) layer to map access category information to an access attempt type of the MO-IMS-registration-related IMS signal, and control the transceiver510to transmit the access category information mapped to the access attempt type from the NAS layer to an AS layer. In case that the access category information mapped to the access attempt type is 9, in the AS layer, the controller520may determine to allow access for the access attempt type. The storage530may store at least one of information transmitted or received via the transceiver510and information generated via the controller520. For example, the storage530may map and store an access category and an access attempt type such as a generated mobile originating access attempt type. The methods according to various embodiments described in the claims or the specification of the disclosure may be implemented by hardware, software, or a combination of hardware and software. In case that the methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured for execution by one or more processors within the electronic device. The at least one program may include instructions that cause the electronic device to perform the methods according to various embodiments of the disclosure as defined by the appended claims and/or disclosed herein. The programs (software modules or software) may be stored in non-volatile memories including a random access memory and a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other type optical storage devices, or a magnetic cassette. Alternatively, any combination of some or all of them may form a memory in which the program is stored. Further, a plurality of such memories may be included in the electronic device. In addition, the programs may be stored in an attachable storage device which may access the electronic device through communication networks such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), and Storage Area Network (SAN) or a combination thereof. Such a storage device may access the electronic device via an external port. Further, a separate storage device on the communication network may access a portable electronic device. In the above-described detailed embodiments of the disclosure, an element included in the disclosure is expressed in the singular or the plural according to presented detailed embodiments. However, the singular form or plural form is selected appropriately to the presented situation for the convenience of description, and the disclosure is not limited by elements expressed in the singular or the plural. Therefore, either an element expressed in the plural may also include a single element or an element expressed in the singular may also include multiple elements. Although specific embodiments have been described in the detailed description of the disclosure, various modifications and changes may be made thereto without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be defined as being limited to the embodiments, but should be defined by the appended claims and equivalents thereof. | 75,744 |
11943734 | DESCRIPTION OF EXAMPLE EMBODIMENTS Referring toFIG.1A, one embodiment of a communication system is shown.FIG.1Ais a simplified diagram of a system100for facilitating communication in a network environment. Users14-15interact with server20through terminals10a-b. Users14-15travel to location areas17a-cas indicated by paths30a-band31a-b. Server20is coupled to points of interest (“POI”) database40.FIG.1Bis a diagram showing, in one embodiment, example contents of terminal10a. Terminal10acomprises communication module11, display12, location module13, and interface16(so that user14may be able to interact with terminal10a).FIG.1Cis a diagram showing, in one embodiment, example contents of server20. Server20comprises memory26, at least one CPU28, and analysis module29. Terminals10a-band server20are communicatively coupled via network connections22and network24. In some embodiments, analysis module29may be configured to analyze location information, preferences, and characteristics sent from users14-15and determine whether user14should receive information related to user15. Users14-15are clients, customers, prospective customers, or entities wishing to participate in an on-line dating scenario and/or to view information associated with other participants in the system. Users14-15may also seek to access or to initiate communication with other users that may be delivered via network24. Users14-15may review data (such as profiles, for example, with user characteristics and preferences) associated with other users in order to make matching decisions or elections. Data, as used herein, refers to any type of numeric, voice, video, text, or location data, or any other suitable information in any appropriate format that may be communicated from one point to another. In one embodiment, terminals10a-brepresent (and are inclusive of) a personal computer that may be used to access network24. Alternatively, terminals10a-bmay be representative of a cellular telephone, an electronic notebook, a tablet computer, a laptop, a personal digital assistant (PDA), or any other suitable device (wireless or otherwise: some of which can perform web browsing), component, or element capable of accessing one or more elements within system100. Interface16, which may be provided in conjunction with the items listed above, may further comprise any suitable interface for a human user such as a video camera, a microphone, a keyboard, a mouse, or any other appropriate equipment according to particular configurations and arrangements. In addition, interface16may be a unique element designed specifically for communications involving system100. Such an element may be fabricated or produced specifically for matching applications involving a user. Communication module11may be implemented using any suitable combination of hardware, firmware, and software. Communication module11, in some embodiments, may be a modem, network interface card, wireless communication device, cellular data communication device, or other suitable module for communicating information using connections22. Communication module11may communicate one or more communication schemes, such as those defined by the IEEE LAN/MAN Standards Committee (IEEE 802), including both wired and wireless standards. Display12, in some embodiments, may be a computer monitor, a liquid crystal display (LCD), an active-matrix organic light-emitting diode display (AMOLED), a super AMOLED, a light-emitting diode (LED) based display, or other suitable displays for desktop and/or mobile devices. Alternatively, display12may be a projector, speaker, or other device that allows users14-15to appreciate information that system100transmits. Location module13may be implemented using any suitable combination of hardware, firmware, and software. Location module13may determine information regarding the physical location of terminal10a. Examples of such location information include latitude/longitude coordinates, physical address, zip code, area code, city, county, state, country, and geographic area. Location module13may determine the location information using one or more suitable technologies, such as Global Positioning System (GPS), available IEEE 802.11 networks, and cellular radio signals. For example, location module13may use triangulation of wireless signals such as 802.11 networks and/or cellular radio signals. As another example, Uplink Time Difference of Arrival (U-TDOA) may be used by location module13to determine location information. In some embodiments, location module13may determine location information using input from a user (such as users14-15). For example, location module13may use user input as one factor in determining location and rely on other technologies to make a determination as to the location of terminal10a. As another example, location module13may allow user14to specify location information (i.e., an intersection, an address, or a business). A user may specify location information by selecting location information from a list or map provided by location module13. Network24comprises one or more communicative platforms operable to exchange data or information emanating from users14-15. Network24could include a plain old telephone system (POTS). Transmission of information emanating from the user may be assisted by management associated with server20or manually keyed into a telephone or other suitable electronic equipment. In some embodiments, network24could include any packet data network offering a communications interface or exchange between any two nodes in system100. Network24may alternatively be any local area network (LAN), metropolitan area network (MAN), wide area network (WAN), wireless local area network (WLAN), virtual private network (VPN), intranet, or any other appropriate architecture or system that facilitates communications in a network or telephonic environment, including a combination of any networks or systems described above. In various embodiments, network connections22may include wired and/or wireless mediums which may be provisioned with routers and firewalls. In some embodiments, POI database40may be implemented using any suitable combination of hardware, firmware, and software. POI database40may include data indicating what is available at certain geographic locations. For example, POI database40may include data regarding restaurants, retailers, gas stations, historical sites, counties, cities, metropolitan areas, zip codes, or other locations that may be of interest to users such as users14and15. Examples of POI database40include the CITYSEARCH database and the POYNT database. Server20is operable to receive and to communicate information to terminal10. In some embodiments, server20may comprise a plurality of servers or other equipment, each performing different or the same functions in order to receive and communicate information to terminal10. Server20may include software and/or algorithms to achieve the operations for processing, communicating, delivering, gathering, uploading, maintaining, and/or generally managing data, as described herein. Alternatively, such operations and techniques may be achieved by any suitable hardware, component, device, application specific integrated circuit (ASIC), additional software, field programmable gate array (FPGA), server, processor, algorithm, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or any other suitable object that is operable to facilitate such operations. In some embodiments, server20may comprise one or more clusters of virtual or hardware-based computing nodes, a distributed computing infrastructure, or other suitable forms of providing a software service using multiple computers. In some embodiments, server20may offer one or more services to users14and15via network24such as social networking, professional networking, conference services, messaging, gaming, online dating, marketplace, discussion board, news, travel services, retail services, or other suitable services. Server20can be used to identify and to evaluate suitable candidates in various areas (e.g. hiring/employment, recruiting, real estate, general person searches, online dating, etc.). In some embodiments, memory26may include multiple storage structures, such as storage structures23and25, one or file systems, as well as other suitable structures for storing and retrieving data. For example, storage structures23and25may be implemented using one or more databases, file systems, tables, stacks, heaps, or other suitable storage structures. In some embodiments, location areas17a-cmay be a geographic area that users14-15visit. Examples of location areas include: latitude/longitude coordinates, a physical address, an intersection of streets, a city, a state, a zip code, a region, a province, a region defined by an area code, a business, a neighborhood, a shopping center, a borough, or other suitable geographic areas. In some embodiments, location areas17a-cmay be a location type, such as a business, a historical site, a library, or a restaurant. As another example, location areas17a-cmay be an event at a location area, such as a concert, speech, or a sports event. In some embodiments, users14-15, using terminals10, register with server20. Registration may include users14-15submitting information to server20about users14-15as well as characteristics with which users14-15are seeking to be matched. In various embodiments, server20may be configured to collect this information; for example, such information may include gender, preferred gender of a potential match, height, weight, age, location, ethnicity, birthplace, eating habits, activities, and goals. Server20may further receive information regarding what users14-15may be looking for in a match, such as gender, age, weight, height, location, ethnicity, diet, and education. Further, server20may receive information from users14-15indicating how important certain factors are when looking for a match. For example, server20may allow the user to indicate which characteristics in a potential match are a necessity. In another example, server20may ask, “How important is it that your match does not smoke?” Server20may also allow the user to indicate that certain characteristics are not important search criteria. For example, when asking user14about what height or weight user14is seeking in a match, server20may be configured to receive “not important” as a response. In yet another example, server20may allow user14to rate which factors are important on a numerical scale. For example, server20may ask user14the following: “On a scale of 1-10, how important is it that your match has the same education level as you?” In some embodiments, server20may specify that any number of questions or requested descriptions are necessary before registration may be concluded. As an example only, server20may require that user14communicate the sex of user14and the sex user14prefers to be matched with. Server20may be configured to receive the information submitted by users14-15and create profiles for users14-15based on that information, storing the profiles in memory26, such as in storage structure25. In some embodiments, server20may receive information from users14-15after registration. Server20may receive location information from users14-15after registration has been completed. For example, terminal10amay be configured to send location information regarding user14to server20passively or actively. For example, user14may travel to location area17aas indicated by path30a. At location area17a, terminal10amay transmit location information to server20(such as latitude and longitude coordinates). This may be done in response to user14requesting that terminal10atransmit the location information, or terminal10amay automatically send the location information. As another example, an application in terminal10amay be configured to send location information regarding user14to server20periodically or continuously. The application may be configured to operate as a background process on terminal10a. The location information may be transmitted using connections22and network24. Server20may receive location information and store it in storage structure23. Server20may also store the time when the location information was received from user14in storage structure23. In some embodiments, analysis module29may be implemented using any suitable combination of hardware, firmware, and software. Analysis module29may be configured to search through information such as profiles stored in storage structure25regarding users (such as users14-15) and present matches to user14. Techniques for determining relevant matches for users are well known in the art. Some include determining how closely one user's preferences match another user's characteristics and vice versa. In some embodiments, server20may be configured to generate a pool of potential matching users for user14according to various characteristics and preferences of user14and other users of the system. Server20may assign scores to the pool of potential matching users for user14based on preferences and/or activity of user14. Server20may also restrict entities from being included in the pool of potential matching users based on the status of the profile, location information regarding the entity, or location information regarding user14. User14may specify a preference to be matched with or not to be matched with users that visit certain locations or location types, such as stores, libraries, or restaurants. User14may specify a preference to be matched with or not to be matched with users that visit the same locations or location types as user14. Analysis module29may use the location information in storage structure23received from users14and15when applying preferences regarding location information of user14when determining matching users for user14. In some embodiments, analysis module29may be configured to present information regarding other users registered with server20(such as user15) to user14based on the present or past location(s) of user14. For example, users14and15may travel to location areas17a-cas indicated by paths30a-band31a-b. User15arrives at location area17band terminal10btransmits location information regarding user15and location area17bto server20. At a later time, after user15has left location area17b, user14arrives at location area17b. Terminal10asends location information regarding user14and location area17bto server20. Then, server20sends a notification to terminal10aindicating that user15was at location area17b. Server20may send the notification after determining that user15has one or more characteristics that are preferable to user14. The notification may be sent after user14has departed location area17b. Server20may provide an indication of the time difference between when user14arrived at location area17band when user15was at location area17b. Server20may send information regarding user15to user14. User14may also receive (using terminal10a) information regarding other users who are registered with server20that have also been at location area17bprevious to user14. For example, server20may send a list of users who have been at location area17band indicate when each of those users were at location area17brelative to when user14was at location area17b. In some embodiments, notifications to user14may provide information regarding when and where other users (such as user15) have been as they relate to when and where user14has been. The notifications may include information regarding a location area17a-cat which user15may have been present relative to a location area17a-cat which user14may be or have been present. For example, a notification may notify user14that user14missed being in the same location area as user15by a certain amount of time and may present information regarding user15to user14. For example, the notification may notify user14that user14missed being at the same restaurant as user15by 15 minutes and may provide information regarding user15such as a picture, profile information, or user identifier. The information provided may indicate that user15may be a good match for user14. A notification may notify user14that user14has similar patterns of behavior as user15, such as visiting the same type of location at the same or different times. For example, the notification may notify user14that user14and user15visit the same location area everyday (such as a coffee shop), visit the same park in the mornings, go to a gym three times a week, or attended the same event the previous night. A notification may notify user14that user15goes to the same type of locations as user14. For example, a notification may notify user14that user14and user15go to coffee shops in the morning or go to gyms in the evening. A notification may notify user14that user15travels the same or similar routes and/or paths as user14(i.e., user14and user15visit the same locations in the same order). As examples, a notification may notify user14that user14and user15take the same bus to work, use the same roads to get to work, attend the same restaurant and then the same movie theatre, or go to the same gym and then the same smoothie store. A notification may notify user14that user15are in nearby location areas at the same or different times. As examples, a notification may notify user14that user14and user15work on the same block during the week or that user14and user15go to restaurants in adjacent boroughs on different days. In some embodiments, this may provide an advantage in that user14may be provided with other users who visit the same location as user14which may interest user14in being matched with such users. Another example of how this may be advantageous is that server20may provide potential matches to user14in a manner that may be more relevant to user14given that such matches have visited the same location area17bas user14. In some embodiments, analysis module29may be configured to receive a request from user14to be matched with users in the same location or location type as the present location of user14. For example, user14may travel to location area17aas indicated by path30a. User14causes terminal10ato send an indication to server20that user14would like to be matched with other users that have been in location area17aor in a type of location that is similar to location area17a. Terminal10asends the preference(s) of user14along with location information regarding location area17ato server20. Server20uses location information stored in storage structure23of other users (such as user15) registered with server20to determine users to match with user14. Server20may use information from POI database40to determine location types that may be similar to location area17a. Server20may also use other characteristics of users registered with server20, such as those stored in storage structure25(including profile information), to determine users that may be of interest to user14. Analysis module29performs comparisons to determine which users should be presented to user14. The comparisons may take into account the preference expressed by user14regarding location area17a. The comparisons may be performed by scoring various characteristics of the users in light of stated preferences and activity of user14. In some embodiments, this may be advantageous in that user14may be able to express location as a preference to enhance the search for matches performed by server20which may provide more relevant potential matches. In some embodiments, analysis module29may be configured to provide an indication to user14of other users registered with server20(such as user15) that may be in the same location or location type as user14. For example, user15may arrive at location area17bas indicated by paths31aand31b. Sometime later, user14arrives at location area17bas indicated by paths30aand30b. After arriving at location area17b, terminal10btransmits location information regarding user15and location area17bto server20. After arriving at location area17b, terminal10atransmits information regarding user14and location area17bto server20. User14may send a request to server20to receive information regarding other users registered with server20that may be at location area17b. Analysis module29analyzes location information in storage structure23and information regarding characteristics of users registered with server20in storage structure25to determine other users of server20that may be at location area17b. Analysis module29may cause an indication to be sent to user14that provides information regarding one or more users (such as user15) that may also be at location17bat the same time as user14who have one or more characteristics that match preferences previously submitted by user14. The indication may be sent after user14has departed from location17bor while user14is still at location17b. Analysis module29may be configured to receive and process location information from user14and provide the indication to user14in real time. In some embodiments, presenting an indication to user14informing user14of one or more users that are at or have been at the same or similar location areas as user14may be advantageous in that user14may be provided information regarding other users that may be of interest to user14that are in the same location as user14. This may provide user14an opportunity to meet people in whom user14may have an interest. FIGS.2-4are flowcharts illustrating embodiments of the operation of system100ofFIG.1A. In general, the steps illustrated inFIGS.2-4may be combined, modified, or deleted where appropriate, and additional steps may also be added to the example operation. Furthermore, the described steps may be performed in any suitable order. In some embodiments, the steps described below may be performed by any suitable combination of the elements discussed above with respect toFIGS.1A-1Cor other suitable elements. FIG.2is a flowchart illustrating one embodiment of how analysis module29ofFIG.1Cmay provide an indication to user14ofFIG.1Aof users registered with server20ofFIG.1A(such as user15) that were at a location area or location type where user14also was at some time. One or more of the steps illustrated inFIG.2may be repeated by analysis module29for one or more users that have registered with server20. At step210, in some embodiments, server20may receive and store location information from various users who have registered with server20(such as user15). For example, historical location information may be received at this step indicating location areas where users registered with server20have been. Terminals such as terminals10a-bmay send the location information using modules such as location module13. The location information may include information regarding one or more of: longitude/latitude coordinates, a physical address, an intersection, a neighborhood, a county, a city, a state, a zip code, an area code, a region, a country, or other suitable information that describes geographic location. In some embodiments, a tolerance parameter(s) may be included with the location information indicating how precise the location information is. For example, the location information may include an intersection of two streets, and the tolerance parameter may indicate that the information is accurate within ten blocks. Server20may cause the location information received at this step to be stored in a stored structure such as storage structure23. Along with the location information, server20may store other information, such as: information regarding one or more of the users registered with server20associated with the location information, characteristics of the users submitting the location information, the times that the users arrived at and/or departed from the location associated with the location information, user preferences as to how the location information should be used, or other data associated with the location information. In some embodiments, server20may be configured to store the location type associated with the location information received at this step. As an example, server20may receive information about the location type from POI database40and store that information with the location information received at this step. Example location types include point-of-interest (POI), restaurant, business, historical site, shopping, names of businesses, museums, or other suitable descriptions of the geographic area identified by the location information. Information received and stored at step210may include event information related to the location information such as a concert, speech, or a sports event. At step220, in some embodiments, location information (such as persistent location information) from user14may be received by server20. For example, historical location information may be received at this step indicating location areas or events at location areas where user14has been. User14may have arrived at location area17aand terminal10amay have transmitted the location information received at this step using information from location module13. This transmission may have been performed passively or actively. For example, terminal10amay have been configured to transmit location information as user14travels to various location areas. As another example, terminal10amay have been configured to transmit location information when a particular application is launched on terminal10a. As another example, terminal10amay be configured to transmit location information in response to an indication from user14(i.e., user14presses a button or taps an active portion of a screen of terminal10ato indicate that the location information should be sent). At step230, in some embodiments, the location information received at step220is compared to the location information stored at step210by analysis module29. As an example, this may be done to determine whether other users have been in the same location area that user14is in or have attended the same event that user14is at as indicated by the location information received at step220. As another example, this may be done to determine whether other users have been in the same location area that user14has been as indicated by the location information received at step220. Various methods may be used to compare the location information at this step. Method used may, in various embodiments, be dependent on the type of location information received and/or stored at steps210and220. For example, latitude and longitude coordinates may be compared to one another, and a threshold may be used to determine whether they are considered to be within the same location area. As another example, location information such as addresses, zip codes, or area codes may be compared to one another to determine where there is a match. As another example, location information such as latitude and longitude coordinates may be compared to an address by determining what location the latitude and longitude coordinates are indicate of and calculating a distance from that location to the address. The distance may then be compared to a threshold as discussed further below. As another example, latitude and longitude coordinates may be compared to a zip code by determining whether the location indicated by the coordinates falls within geographic area associated with the zip code. As another example, at this step the location type of the location information received at step220and the location information stored at step210may be compared. At step235, in some embodiments, analysis module29may determine whether differences between the location information received at step220and the location information received at step210is below a threshold. For example, a distance threshold may be used at this step. This may determine whether the location information being compared are geographically close enough to indicate a same location area. Multiple distance thresholds may be used depending on the type of location information being compared. For example, when comparing two addresses, the threshold might be set such that to be below the threshold the addresses must be the same. As another example when comparing addresses, the threshold might be set to allow for the addresses to differ by a specified amount (i.e.,3blocks). As another example, if the location information being compared are two sets of latitude/longitude coordinates, then the threshold might be a distance between the two pairs of coordinates (e.g., two miles). As another example, when comparing an address to a zip code, the threshold may be that the address be located within the area associated with the zip code or may be that the address be located in the area associated with the zip or in an area adjacent to the area associated with the zip. As another example, when comparing location types, the threshold may be set such that a match is determined if the location types are the same. As another example, when comparing location types, the threshold may be set such that a match is determined if the location types are similar (i.e., a location type of a restaurant serving American cuisine may be considered a match to a location type of a restaurant serving Asian cuisine). The thresholds may be different based upon the location areas indicated by the location information. For example, thresholds may vary based on the city or region identified, such as using one threshold for a large city and another threshold for a small city. If the difference between the location information being compared is below the threshold, then users associated with the location information received at step210may be further considered at step240. If it is determined that the location information being compared is at or above the threshold, then the users associated with the location information received at step210may not be considered further. In some embodiments, if the difference between the location information is at or above the threshold, then user14may not be in the same location area that the user had been whose location information is being compared. In some embodiments, steps230and235may be performed multiple times as analysis module29analyzes the location information stored at step210from various users who have subscribed to server20. Analysis module29may perform these steps with groups of users or may perform these steps with all the users whose location information is stored in storage structure23. In some embodiments, steps230and235may be performed such that analysis module29determines whether user14visits the same or similar multiple location areas as users registered with server20. For example, analysis module29may determine that user14and user15visit the same or similar multiple location areas or have attended the same event with a location area. At step240, in some embodiments, analysis module29may compare time information included with the location information received at step220with time information associated with the location information received at step210that was determined to be in the same location area at steps230and235. The time information compared at this step may include milliseconds, seconds, minutes, hours, days, weeks, months, years and/or other suitable measurements of time. This step may be performed so that analysis module29may determine how long it has been since the users who were determined to be in the same location area as user14at steps230and235arrived at or departed from the location area and user14arrived at the location area. The time information compared at this step may be the time that user14arrived at the location area indicated by the location information received at step220, the time that the other users arrived at that location area, the time that the other users left that location area, and/or the time that the other users arrived at a different location area. In some embodiments, the time that a user left a location area may be determined based on the time that the user arrives at the location area, the time that the user arrives at a different location area, or the period of time the user remained in the same location area. At step245, in some embodiments, the difference in the time information compared at step240may be compared to a time threshold. If the difference is greater than the threshold, then step250may be performed. If the difference is less than the threshold, then the associated users may no longer be considered. The difference being greater than a threshold may indicate that user14had arrived at a location area after another user left the location area. The difference being below the threshold may indicate that user14is at the location area with another user at the same time. Example time thresholds include 10 minutes, 20 minutes, and 1 hour. In some embodiments, step245may be performed by determining whether any difference in the time information compared at step240is less than a time threshold. In such embodiments, if the difference is less than the threshold, then step250may be performed. If the difference is greater than the threshold, then the associated users may no longer be considered. Example time thresholds include 10 seconds, 10 minutes, 20 minutes, and 30 minutes. This may be applied in situations when analysis module29is configured to determine if user14has been to the same location area or location type as other users registered with server20at or near the same time. The time threshold discussed above may be configurable. For example, the time threshold may depend on the location information received at step220. As another example, the time threshold may depend on the population density associated with the location information received at step220. In some embodiments, steps240and245may not be performed. For example, analysis module29may be configured to present user14with a notification of users registered with server20who have been in the same location area at the same time as or at a different time than user14. At step250, in some embodiments, characteristics of certain users whose location information was stored at210may be compared to preferences and/or characteristics of user14. The users whose characteristics are compared at this step may be users who have been in the same location area as user14and who have left the location area at a time sufficiently later than when user14arrived as discussed above with respect to steps230through245. Examples of characteristics and/or preferences compared at step250may include interests, height, age, weight, sex, income, eye color, hair color, profession, residence or other suitable characteristics for matching. This step may be performed using information in storage structure25, such as profile information of users registered with server20. At step255, in some embodiments, it may be determined whether a sufficient number of preferences of user14match characteristics of the users compared at step250. The number of matching characteristics may be set depending on desired levels of tolerance. For example, if user14has few potential matching candidates according to his or her preferences, then only one preference being satisfied may be sufficient. As another example, if there are many potential candidates that match with user14, then more than one preference may be required to be met at this step. The determination at step255may be dynamic by responding to changes in the profile or preferences of user14. For example, if user14changes the associated profile, the number of potential matching candidates may change. The change in the number of potential matching candidates may also change the determination of whether a sufficient number of preferences of user14have been matched that occurs at step255. Step260may be performed with respect to users that have characteristics which satisfy a sufficient number of preferences of user14. Users that do not have characteristics which satisfy a sufficient number of preferences of user14may no longer be considered in this process. In some embodiments, this may result in selecting only users that user14be interested in meeting. In some embodiments, one or more scores may be used in step255. For example, a score may be given to one characteristic because it was close to matching a preference of user14while another characteristic may receive a lower score because it was not as close to matching a preference of user14. These scores (separately or combined) may be compared to one or more thresholds to determine if the preferences have been matched. The scores may also be analyzed based on importance levels that user14has indicated regarding his or her preferences. At step260, in some embodiments, analysis module29may cause an indication to be presented to user14that includes information related to users of server20that were at a location area or location type where user14also was at some time. The information in the indication may include information regarding a location area at which a user registered with server20may have been present relative to a location area at which user14may be or have been present. The indication may not reveal the exact location area that user14has in common with the other users. For example, instead of indicating exactly which coffee shop or gym another user attends, the indication may disclose to user14the area, neighborhood, shopping center, street block, or other geographical description that user14has in common with user15. As another example, the information in the indication may include information regarding the location type that user14has in common with other users registered with server20(e.g., user14and other users visit coffee shops, libraries, or bowling alleys). In some embodiments, the indication may include information indicating that: user14was at or near the same location area as user15at different times, user14was at or near the same location area as user15at the same or nearly the same time, user14was at the same location type as user15at the same or nearly the same time, or user14was at or near the same location type as user15at different times. The information that may be included in this indication may include user identifiers used in communicating with server20, real names, photographs, interests, personal information, contact information, and/or other characteristics of users registered with server20. The list of users presented to user14at this step may be sorted by one or more factors including residence of the users, the difference in time between when those users left the location area and when user14arrived at the location area, how many preferences of user14are met, or other suitable characteristics or factors. The information may also include the difference in time between when user14arrived at the location area and when the users whose information is presented at this step arrived or left the location area. The information may also include the distance between the location information of user14received at step220and the location information of users whose information is presented at this step. The information presented at this step may indicate that user14and user15have a path or route in common (i.e., users14and15visit the same location areas in the same order). The information presented at this step may be sent from server20to terminal10a. Terminal10amay provide user14with a notification that the indication is available to be presented. As an example, this information may be useful to user14in that user14may be able to determine which users user14missed the opportunity to meet and may be motivated to attempt to contact such users using one or more services offered by server20. User14may perceive that he or she missed a connection with a potential match because of the indication that analysis module29caused to be presented at step260. As another example of an advantage, user14may be able to determine characteristics of people who have visited the location area before and may determine to return because those characteristics are of interest to user14. User14may be provided with information or options to contact people-of-interest. For example, user14may contact people-of-interest using a service offered by server20, by e-mail, or by telephone. As another example of an advantage, user14may indicate that user14should not be matched with other users from the location areas user has visited after user14has been presented with the information at step260. In some embodiments, the steps ofFIG.2may be performed in a different order than illustrated. For example, steps250and255may be performed before steps230and235. As another example, steps250and255may be performed before steps240and245. FIG.3is a flowchart illustrating one embodiment of how analysis module29ofFIG.1Cmay provide an indication to user14ofFIG.1Aof the number of users registered with server20ofFIG.1A(such as user15) that have been at places in the same location area as user14. At step310, in some embodiments, location information may be received by server20from users that have registered with one or more services offered by server20(such as user15). This step may be performed similarly to step210ofFIG.2. Users registered with server20may have devices with them such as terminals10aand10bthat transmit location information to server20actively or passively. The location information may be stored in a structure such as storage structure23. Various types of location information may be received, such as a physical address or latitude/longitude coordinates. At step320, in some embodiments, places associated with location information received at step310may be determined. This step may be performed by analysis module29. The location information received by step310may compared to one or more databases or services to determine what places are at or near the location information received at step310. Examples of places determined at this step may include a type of place, a restaurant, a business, a shopping center, a neighborhood, a historical site, a service, or other points of interest. As another example, events occurring at a place may be determined. Places may be determined using a database or service such as POI database40ofFIG.1A. In some embodiments, multiple places may be determined for a given item of location information associated with one of the users registered with server20. For example, an address may have been received at step310, and, at step320, a business associated with that address may be determined. As another example, a zip code may be received at step310and multiple businesses or neighborhoods may be determined at step320. As another example, an address may have been received at step310, and, at step320, multiple businesses at or near that address may be determined. At step330, in some embodiments, the number of users associated with the places determined in step320may be determined. Analysis module29may perform this step. At this step, the places determined at step320from the information received at step310are then correlated to the users who sent the location information received at step310. The number of users registered with server20that have been to the places determined at step320may be determined at this step. For example, it may be determined that ten users submit the location information that was associated with a restaurant determined at step320. At step340, in some embodiments, server20may receive location information from user14. This step may be performed similarly to step220ofFIG.2. User14may have caused this information to be sent via terminal10a. This information may be sent via terminal10apassively or actively. At step350, in some embodiments, one or more places may be determined from the location information received from user14at step340. For example, if location information received at step340was a physical address, then one place may be determined such as a business, residence, or other entity occupying the physical address. As another example, if a zip code was received at step340, then the places within the zip code (such as businesses, residences, neighborhoods and other entities within the zip code's region) may be determined. In some embodiments, information that refers to a specific geographic location (such as an address or latitude/longitude coordinates) multiple places may be determined. For example, if an address was received at step340, then places in or around that address may be determined within a given radius (such as one mile, two blocks, 500 yards, and/or other suitable measurements). This step may be performed similarly to step320. For example, POI database40ofFIG.1Amay be used to compare the location information to the database to determine places such as points of interest that are in the database. At step360, in some embodiments, analysis module29may compare the places determined at step350to the places stored at step320. This may be done to determine whether there is a match between the places determined at step350to the places stored at step320. In some embodiments, this may be done to determine whether these place(s) are within the same geographic region (such as a block, neighborhood, zip code, shopping center, mall, or other suitable geographic region). At step370, in some embodiments, the number of users registered with server20and associated with the places determined at determined at step350are presented to user14. This may be performed by identifying the number of users determined at step330corresponding to the matching places determined at step360. For example, if a restaurant was determined to have 30 associated users registered with server20at step330, and that restaurant was determined at step350, 30 users would be determined at this step. After determining the number of users associated with the places determined at step350, analysis module29may cause server20to send an indication of the places determined at step350and the number of registered users that have visited the places determined at step350. In some embodiments this may be advantageous because user14may be presented with information regarding the number of users that frequent the places near which user14is located. For example, server20may offer a dating service or matchmaking service where user14and other registered users of server20are attempting to be matched or date each other. Being able to determine the number of registered users that have been to the places surrounding user14may be beneficial in that user14may be able meet the registered users in person in that location. As another example, user14may be a student and server20may be offering a service for students. Presenting user14with the number of other registered users of server20that have visited places surrounding user14may help user14to make a decision as to what place user14would prefer visiting. For example, if user14was attempting to choose a restaurant to eat at knowing that other students frequent that restaurant may help user14to make the decision. Terminal10aassociated with user14may receive the communication from server20and present the indication of the number of users and other places surrounding user14via a screen. Terminal10amay provide a notification that server20has sent such information, such as a sound, icon, badge, or vibration. As another example, this information may be provided as an augmented reality experience for user14such that user14may be capable of moving terminal10ato different location areas and receiving the number of other registered users in the places at the location areas. Such information may be visually represented on the screen of terminal10aalong with the places at the location areas. FIG.4is a flowchart illustrating one embodiment of how analysis module29ofFIG.1Cmay receive preferred location information from user14ofFIG.1Aand use it to enhance matching services with other users registered with server20ofFIG.1A(such as user15). At step410, in some embodiments, location information from users registered with server20may be received and stored at server20. This may be performed similar to step210ofFIG.2. Location information may be sent from terminals such as terminal10aof users registered with server20actively or passively. Location information may include, for example, physical addresses or latitude/longitude coordinates. The location information and users associated with that location information may be stored at server20along with other information (such as the time the location information was received or sent) in a structure such as storage structure23ofFIG.1C. At step420, in some embodiments, preferred location information from user14may be received by server20. For example, user14may be in a place such as a restaurant that user14appreciates. User14may desire to meet other people who also have visited the restaurant. As a result, user14may submit the location information of the restaurant to server20in order to be matched with others who have been at the restaurant. Terminal10amay be used to send the preferred location information that is received at step420. Examples of the location information received at step420may include latitude/longitude coordinates, an address, a city, a state, a zip code, a point of interest, and/or other suitable descriptions of a location. As an example, user14may use a mobile device, such as a smart phone, to start an application that is configured to communicate with server20. When at a location that user14appreciates, user14may indicate to the application to send the current location information regarding user14to server20. As another example, user14may be in a neighborhood that user14appreciates. User14may send the location information to server20in order to be matched with other users of server20that may be associated with the neighborhood. For example, server20may provide a matching service, a dating service, or a real estate listing service in which user14would want to be matched with those who are associated with the neighborhood. At step430, in some embodiments, analysis module29may compare the preferred location information received at step420to the location information stored at step410. This may be done to identify registered users of server20that have location information associated with them that match or correspond to the preferred location information received at step420. In some embodiments, location types corresponding to the location information are compared. Location types may be determined for the location information, and it may be determined whether there is a match in location types. Events occurring at places corresponding to the location information may be determined. For example, it may be determined that the preferred location information received at step420corresponds to a coffee shop. The location information submitted at step410may be analyzed to determine others who have been to coffee shops to see if there is a match in location type. Other characteristics may be taken into account during the comparison at step430. For example, user14may specify other preferences regarding desired matches and those preferences may be compared to users identified by comparing the preferred location information to the stored location information. For example, user14may have registered with a dating service offered by server20. User14may have specified that they prefer to be matched with users that are under the age of 40. Analysis module29may determine that a user over the age of 40 also had the same preferred location information and may disregard the user even though the preferred location information is the same as the stored location information. As another example, the preferred location information may be given more weight than other preferences submitted by user14. For example, user14may specify that he would prefer to meet with people who have blonde hair yet analysis module29may determine matches with user14of those that do not have blonde hair yet have matching location information. At step440, in some embodiments, matches based on the comparison of the preferred location information to the stored location information may be presented to user14. For example, analysis module29may cause such matches to be presented to user14. In some embodiments, this may be advantageous in that user14may be able to provide more preferences to one or more services offered by server20in order to obtain more relevant results. User14may also have an opportunity to discover new preferences and efficiently provide them to server20to obtain more relevant results. The matches may be presented on devices that user14has access to, such as terminal10a. The results may be presented as a response to user14submitting the preferred location information. For example, user14may enter into a location such as an museum and desire to be matched with those that have also attended a museum. As a response, server20may analyze the stored location information and provide the matches presented at step440within seconds, minutes, hours or days. User14may be notified of the new matches at terminal10aas they are sent by server20or user14may appreciate the new matches when accessing one or more services offered by server20after sending the preferred location information. The matches presented at step440may be matches that server20has already determined prior to receiving the preferred location information but have been prioritized as a result of receiving the preferred location information. For example, based on an initial set of preferences submitted before the preferred location information was submitted by user14, server20may have identified 100 candidates for potential matches with user14. As a result of receiving preferred location information and identifying of those 100 candidates those who also have location information that corresponds to the preferred location information analysis module29may reorder the set of 100 users such that those with matching location information may be presented sooner to user14than those matches without corresponding location information. In some embodiments, this may provide an advantage in that user14may be able to perceive more relevant results sooner. FIG.5illustrates an example computer system500suitable for implementing one or more portions of particular embodiments. Although the present disclosure describes and illustrates a particular computer system500having particular components in a particular configuration, the present disclosure contemplates any suitable computer system having any suitable components in any suitable configuration. Moreover, computer system500may have take any suitable physical form, such as for example one or more integrated circuit (ICs), one or more printed circuit boards (PCBs), one or more handheld or other devices (such as mobile telephones or PDAs), one or more personal computers, one or more super computers, one or more servers, and one or more distributed computing elements. One or more components ofFIGS.1A-1Cand one or more steps ofFIGS.2-4may be implemented using all of the components, or any appropriate combination of the components, of computer system500described below. Computer system500may have one or more input devices502(which may include a keypad, keyboard, mouse, stylus, or other input devices), one or more output devices504(which may include one or more displays, one or more speakers, one or more printers, or other output devices), one or more storage devices506, and one or more storage medium508. An input device502may be external or internal to computer system500. An output device504may be external or internal to computer system500. A storage device506may be external or internal to computer system500. A storage medium508may be external or internal to computer system500. In some embodiments, terminals10aand10b, server20, and POI database40ofFIG.1Amay be implemented using some or all of the components described above included in computer system500. System bus510couples subsystems of computer system500to each other. Herein, reference to a bus encompasses one or more digital signal lines serving a common function. The present disclosure contemplates any suitable system bus510including any suitable bus structures (such as one or more memory buses, one or more peripheral buses, one or more a local buses, or a combination of the foregoing) having any suitable bus architectures. Example bus architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Enhanced ISA (EISA) bus, Micro Channel Architecture (MCA) bus, Video Electronics Standards Association local (VLB) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express bus (PCI-X), and Accelerated Graphics Port (AGP) bus. Computer system500includes one or more processors512(or central processing units (CPUs)). A processor512may contain a cache514for temporary local storage of instructions, data, or computer addresses. Processors512are coupled to one or more storage devices, including memory516. Memory516may include random access memory (RAM)518and read-only memory (ROM)520. Data and instructions may transfer bidirectionally between processors512and RAM518. Data and instructions may transfer unidirectionally to processors512from ROM520. RAM518and ROM520may include any suitable computer-readable storage media. Computer system500includes fixed storage522coupled bi-directionally to processors512. Fixed storage522may be coupled to processors512via storage control unit507. Fixed storage522may provide additional data storage capacity and may include any suitable computer-readable storage media. Fixed storage522may store an operating system (OS)524, one or more executables (EXECs)526, one or more applications or programs528, data530and the like. Fixed storage522is typically a secondary storage medium (such as a hard disk) that is slower than primary storage. In appropriate cases, the information stored by fixed storage522may be incorporated as virtual memory into memory516. In some embodiments, fixed storage522may include network resources, such as one or more storage area networks (SAN) or network-attached storage (NAS). In some embodiments, memory26, storage structures23and25, and analysis module29ofFIGS.1A and1Cmay be implemented using configurations such as the description of memory516above. Processors512may be coupled to a variety of interfaces, such as, for example, graphics control532, video interface534, input interface536, output interface537, and storage interface538, which in turn may be respectively coupled to appropriate devices. Example input or output devices include, but are not limited to, video displays, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styli, voice or handwriting recognizers, biometrics readers, or computer systems. Network interface540may couple processors512to another computer system or to network542. Network interface540may include wired, wireless, or any combination of wired and wireless components. Such components may include wired network cards, wireless network cards, radios, antennas, cables, or any other appropriate components. With network interface540, processors512may receive or send information from or to network542in the course of performing steps of particular embodiments. Particular embodiments may execute solely on processors512. Particular embodiments may execute on processors512and on one or more remote processors operating together. In some embodiments, processors512may be used to implement analysis module29ofFIG.1Cand/or may perform the steps specified in instructions or code included in analysis module29ofFIG.1C. In a network environment, where computer system500is connected to network542, computer system500may communicate with other devices connected to network542. Computer system500may communicate with network542via network interface540. For example, computer system500may receive information (such as a request or a response from another device) from network542in the form of one or more incoming packets at network interface540and memory516may store the incoming packets for subsequent processing. Computer system500may send information (such as a request or a response to another device) to network542in the form of one or more outgoing packets from network interface540, which memory516may store prior to being sent. Processors512may access an incoming or outgoing packet in memory516to process it, according to particular needs. Particular embodiments involve one or more computer-storage products that include one or more tangible, computer-readable storage media that embody software for performing one or more steps of one or more processes described or illustrated herein. In particular embodiments, one or more portions of the media, the software, or both may be designed and manufactured specifically to perform one or more steps of one or more processes described or illustrated herein. In addition or as an alternative, in particular embodiments, one or more portions of the media, the software, or both may be generally available without design or manufacture specific to processes described or illustrated herein. Example computer-readable storage media include, but are not limited to, CDs (such as CD-ROMs), FPGAs, floppy disks, optical disks, hard disks, holographic storage devices, ICs (such as ASICs), magnetic tape, caches, PLDs, RAM devices, ROM devices, semiconductor memory devices, and other suitable computer-readable storage media. In particular embodiments, software may be machine code which a compiler may generate or one or more files containing higher-level code which a computer may execute using an interpreter. As an example and not by way of limitation, memory516may include one or more tangible, non-transitory, computer-readable storage media embodying software and computer system500may provide particular functionality described or illustrated herein as a result of processors512executing the software. Memory516may store and processors512may execute the software. Memory516may read the software from the computer-readable storage media in mass storage device516embodying the software or from one or more other sources via network interface540. When executing the software, processors512may perform one or more steps of one or more processes described or illustrated herein, which may include defining one or more data structures for storage in memory516and modifying one or more of the data structures as directed by one or more portions the software, according to particular needs. In some embodiments, memory26, storage structures23and25, and analysis module29ofFIGS.1A and1Cmay be implemented using configurations such as the description of memory516above. In some embodiments, the described processing and memory elements (such as processors512and memory516) may be distributed across multiple devices such that the operations performed utilizing these elements may also be distributed across multiple devices. For example, software operated utilizing these elements may be run across multiple computers that contain these processing and memory elements. Other variations aside from the stated example are contemplated involving the use of distributed computing. In addition or as an alternative, computer system500may provide particular functionality described or illustrated herein as a result of logic hardwired or otherwise embodied in a circuit, which may operate in place of or together with software to perform one or more steps of one or more processes described or illustrated herein. The present disclosure encompasses any suitable combination of hardware and software, according to particular needs. Although the present disclosure describes or illustrates particular operations as occurring in a particular order, the present disclosure contemplates any suitable operations occurring in any suitable order. Moreover, the present disclosure contemplates any suitable operations being repeated one or more times in any suitable order. Although the present disclosure describes or illustrates particular operations as occurring in sequence, the present disclosure contemplates any suitable operations occurring at substantially the same time, where appropriate. Any suitable operation or sequence of operations described or illustrated herein may be interrupted, suspended, or otherwise controlled by another process, such as an operating system or kernel, where appropriate. The acts can operate in an operating system environment or as stand-alone routines occupying all or a substantial part of the system processing. Although several embodiments have been illustrated and described in detail, it will be recognized that substitutions and alterations are possible without departing from the spirit and scope of the appended claims. | 65,229 |
11943735 | DETAILED DESCRIPTION To further illustrate the disclosure, embodiments detailing an indoor target positioning method based on an improved CNN model are described below. It should be noted that the following embodiments are intended to describe and not to limit the disclosure. According to the disclosure, an indoor target positioning method based on an improved CNN model is proposed. As shown inFIG.1, the method can be used in an offline stage and an online stage; the model is trained and a fingerprint database is generated in the offline stage, while the real-time indoor target positioning is realized in the online stage by the fingerprint database generated in the offline stage. According to the disclosure, the method comprises the following steps 1 and 2. Step 1, the target CSI data of a to-be-positioned target are acquired and preprocessed; and Step 2, the preprocessed target CSI data are matched with fingerprints in a positioning fingerprint database to obtain coordinate information of the to-be-positioned target. The generation method of the positioning fingerprint database comprises the following steps A to D. In step A, indoor WiFi signals are collected by an SDR platform to obtain indoor CSI data corresponding to the WiFi signals, and the data are preprocessed. In step B, the preprocessed indoor CSI data are partitioned into a plurality of data subsets through a clustering algorithm. In step C, the improved CNN model is trained by the data subsets to obtain the trained improved CNN model. In step D, a positioning fingerprint database is generated by the trained improved CNN model and the preprocessed indoor CSI data. According to the disclosure, the SDR platform is configured to collect data, which can collect WiFi signals and obtain CSI data by the WiFi signals. The CSI data contains more position information than radio frequency identification devices (RFID) and received signal strength indicators (RSSI), which makes it easier to extract multi-path components and is conducive to improving the accuracy of indoor positioning. The SDR platform comprises a mobile node, a plurality of signal base stations and a data processing unit. Both the mobile node and the signal base stations are defined by an SDR device, and the mobile node can periodically broadcast probe request frames and automatically send positioning requests. Each signal base station is configured to receive the positioning requests from the mobile node and acquire the WiFi signals of the mobile node. A special baseband receiver is disposed behind an RF front end in the base station to reduce the carrier frequency offset and improve the received signal to noise ratio. The data processing unit is connected to the signal base station through a coaxial cable, and is configured to process the WiFi signals acquired by the signal base stations to obtain the indoor CSI data corresponding to the WiFi signals. When the mobile node sends the positioning requests, the probe request frame, which belongs to a management frame and strictly complies with an ieee802.11b protocol, is taken as a request signal. In step 1 and the step A, the data may be preprocessed through principal component analysis (PCA) in which a set of linearly irrelevant variables can be extracted from vast amounts of CSI data, thus solving the complexity and data transmission problems associated with super-high dimensional CSI data in complex environments. The data preprocessing comprises following steps (1) to (4). In step (1), amplitude filtering, phase correction and mean removal are performed on the CSI data to obtain corrected CSI data, and the mean of the CSI data after mean removal is 0 in each feature dimension. In step (2), dimension reduction and noise elimination are performed on the corrected CSI data through PCA. PCA essentially takes the direction with the largest variance as a main feature, and “dissociates” the data in each orthogonal direction, i.e., makes them irrelevant in different directions, which minimizes the impact of noise on experimental data. The variance of the corrected CSI data is calculated through PCA by the following formula: Var(x)=1m∑j=1mxj2;(9) where Var(x) represents the variance of the corrected CSI data, m is the number of corrected CSI data, xj2represents the square of the value of the jthcorrected CSI data, j=1, . . . , m. In step (3), a CSI feature vector is calculated by the variance of the corrected CSI data; each CSI data contains values in three dimensions (x, y and z axes in a three-dimensional space coordinate system), and mapping directions of the values in three dimensions in the three-dimensional space constitute a mapping direction w, where w=(w1, w2, w3), and w1, w2and w3of the CSI data represent the mapping directions of the values in three dimensions in x, y and z axes, respectively. According the disclosure, a maximum CSI feature vector is obtained after being mapped to the direction w by gradient boosting: ∇f=2mXT(Xw);(10) where ∇f represents the variation of gradient, and X represents the CSI feature vector. In step (4), the maximum variance of the corrected CSI data is obtained by formula (10), and the corrected CSI data are processed based on the maximum variance to obtain the CSI data after dimension reduction and noise elimination, i.e., the preprocessed CSI data. To improve the learning performance of position estimation, a dataset partitioning method is proposed in the disclosure, which partitions a fingerprint database set of each small indoor space into several subsets, and a center of each data subset may be obtained based on a k-means clustering algorithm. Through PCA, the noise can be effectively reduced, and the redundancy of each data subset can be removed, so as to extract multi-path and non-line-of-sight (NLOS) effects of each data subset, which can improve the learning performance of position estimation, eliminate the final error and improve the positioning accuracy. In the embodiment of the disclosure, the step B comprises following substeps B01 to B04. In step B01, the preprocessed indoor CSI data are randomly partitioned into a plurality of data subsets based on the geographical position, and each data subset comprises a plurality of indoor CSI data. For large indoor places, the data subsets may be randomly partitioned according to the layout of shops and floors in the indoor places, or based on a default area (for example, 50 m2). In step B02, the data subsets are taken as clusters in the clustering algorithm, the center of each data subset is calculated based on the k-means algorithm by following specific formula: μi=1Ci∑x∈Cix;(1) where μirepresents the center of the ithdata subset (i.e., a mean component of the cluster, also known as the center of mass), Cirepresents the ithdata subset, x represents the indoor CSI data, i=1, . . . , k, where k is the number of data subsets. In step B03, in order to make points in the cluster closely connected together and make the distance between the clusters as large as possible, in the disclosure, a square error of all data subsets is calculated based on the center of the data subsets, and iteration is performed until the square error is minimized. The square error is calculated by the following formula: E=Σi=1kΣx∈Ci∥x−μi∥22(2); where E represents the square error of all data subsets. In step B04, a distance between the preprocessed indoor CSI data and the center of each data subset is calculated, and the data subsets are re-partitioned based on the distance, the steps B02 to B03 are repeated until the square error is minimized to obtain a final data subset. The improved CNN model is adopted in step C of the embodiment of the disclosure. As shown inFIG.2, the improved CNN model comprises five convolution layers and two fully connected layers connected in sequence, where the five convolution layers comprise 16, 32, 64, 64 and 128 kernels, respectively. In the first convolution layer, a convolution operation is performed to track results in the 16 kernels and extract information from the results, and then perform batch normalization, max-pooling and activation. In the second convolution layer, the 32 kernels are configured to track results and extract information, and each kernel is 16 in height, which is equivalent to the number of kernels in the first convolution layer. The data processing step in the third, fourth and fifth convolution layers is the same as that in the second convolution layer. The first fully connected layer is configured to flatten outputs of the fifth convolution layer. The second fully connected layer is configured to output the partitioned CSI data. The multi-path and NLOS effects are partitioned into five windows in the disclosure: (1) a monitoring window without NLOS and multi-path effects; (2) a monitoring window in which NLOS effects appear; (3) a monitoring window in which NLOS effects disappear; (4) a monitoring window in which multi-path effects appear; and (5) a monitoring window in which multi-path effects disappear, and five neural nodes of the second fully connected layer respectively represent the five windows defined by the disclosure. A regression model for position estimation and a classification model for removing noise interference may be obtained by training the data subsets by the CNN model. The step C comprises following steps C01 to C06. In step C01, in order to reduce the impact of data correlation errors and improve the speed of network convergence, the method in the disclosure standardizes each indoor CSI data in each data subset: xp=varp-mean(varp)total(varp);(3) where xprepresents the pthindoor CSI data after being standardized, varprepresents the pthindoor CSI data in the data subset, mean ( ) is a function MEAN, total ( ) is a function SUBTOTAL, p=1, . . . , n, where n is the number of indoor CSI data in each data subset. In step C02, model parameters of the improved CNN model are initialized, the standardized indoor CSI data in each data subset are input into the convolution layers of the improved CNN model to obtain the convoluted indoor CSI data, and features of the convoluted indoor CSI data are extracted. The indoor CSI data in each data subset are input into the convolution layers in sequence, and the features of the tracking results (the convoluted indoor CSI data) are extracted by a series of kernel functions. One kernel generates one tracking result feature mapping, and elements in the kernel are determined by network training. Each kernel is a three-dimensional matrix, with its rows and columns as user defined hyper-parameters. In step C03, batching, max-pooling and activation are performed on the features of the convoluted indoor CSI data to obtain mappings of the convoluted indoor CSI data. Batching can speed up network training, allow higher learning rates, make initial weighting easier, and simplify the creation of deep networks. The batching in the embodiment of the disclosure comprises following steps (1) to (3). In step (1), the mean is calculated based on the features of the convoluted indoor CSI data: UB=1M∑q=1Msq;(4) where UBrepresents the mean of the features of the convoluted indoor CSI data, M is the number of features of each convoluted indoor CSI data, sqrepresents the features of the qthconvoluted indoor CSI data, q=1, . . . , M. In step (2), a variance of the features is calculated based on UBby following formula: σB2=1M∑q=1M(sq-UB)2;(5) where σB2represents the variance of the features of the convoluted indoor CSI data. In step (3), the features of the convoluted indoor CSI data are standardized based on UBand σB2: =sq-UBσB2+ε;(6) whererepresents the standardized features of the indoor CSI data, and ε is a default standardized value. Pooling is an important concept of convolution layer, which is in form of nonlinear down-sampling. According to the disclosure, the tracking results are partitioned into a set of non-overlapping rectangles by max-pooling, and a maximum value is output in each rectangle. On the premise of keeping the main features, the computation burden is reduced by reducing the number of parameters. According to the disclosure, the method performs activation by taking Leaky ReLU as an activation function, and the activation function can make the CNN neural network show nonlinear features. In step C04, the mappings of the convoluted indoor CSI data are classified by the second fully connected layer of the improved CNN model to obtain the coordinate information corresponding to each indoor CSI data in each data subset. Each fully connected layer is a column vector comprising a plurality of nerve units, and coordinate information output thereby is calculated by following formula: yp=γp+β (7); where yprepresents the coordinate information corresponding to the pthindoor CSI data in the data subset, γ and β are the model parameters of the improved CNN model, respectively,prepresents the standardized features of the pthindoor CSI data in the data subset. In step C05, based on a default real coordinate label (i.e., the real 3D coordinate information corresponding to the CSI data) and the coordinate information (yp) output by the improved CNN model, losses of the improved CNN model are calculated by a loss function by following formula: L=−Σpy′plog(yp) (8); where L represents the losses of the improved CNN model, y′prepresents the real coordinate label of the pthindoor CSI data in the data subset, and yprepresents the coordinate information corresponding to the pthindoor CSI data in the data subset. In step C06, the model parameters of the improved CNN model are updated based on the losses, and the standardized indoor CSI data are processed by the updated improved CNN model. The steps C02 to C06 are repeated, and the loss convergence is observed through a loss function diagram. When the losses converge, the trained improved CNN model is obtained. According to the disclosure, in step D, a large number of indoor CSI data are collected and processed by the trained improved CNN model, so that the coordinate information corresponding to the CSI data can be obtained, and the positioning fingerprint database is generated by the CSI data and the corresponding coordinate information. According to the disclosure, the obtained positioning fingerprint database can be used directly for indoor positioning in the online stage, and the target CSI data of the to-be-positioned target are collected by the SDR platform. In step 2, the target CSI data are compared with the data in the positioning fingerprint database, and if the target CSI data are the same as the CSI data in the positioning fingerprint database, coordinate information can be directly extracted from the fingerprint database. In addition, considering that the target CSI data may not be exactly the same as the CSI data in the positioning fingerprint database, the fingerprint matching in the disclosure may also be performed according to the steps shown inFIG.3, multi-dimensional data operation and matching are performed based on the features of a root node and a split point, and the coordinate information with the highest matching degree is selected. According to the disclosure, the collected CSI data are processed by PCA and a data subset partitioning method, so as to remove noise interference and preliminarily improve the accuracy of positioning. The CSI data in the data subset are put into the improved CNN model for training, so as to suppress multi-path components and further improve the accuracy of indoor positioning. The method according to the disclosure can effectively remove noise and multi-path components, improve the accuracy of positioning and realize its application value in large indoor places. It will be obvious to those skilled in the art that changes and modifications may be made, and therefore, the aim in the appended claims is to cover all such changes and modifications. | 16,038 |
11943736 | DETAILED DESCRIPTION FIGS.1through17, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art may understand that the principles of the present disclosure may be implemented in any suitably arranged system or device. The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: IEEE Standard for Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Peer Aware Communications, IEEE Std 802.15.8, 2017; and IEEE Standard Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low Rate Wireless Personal Area Networks (WPANs), IEEE Std 802.15.4, 2105. Aspects, features, and advantages of the disclosure are readily apparent from the following detailed description, simply by illustrating a number of particular embodiments and implementations, including the best mode contemplated for carrying out the disclosure. The disclosure is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. The disclosure is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings. FIGS.1-4Bbelow describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions ofFIGS.1-3are not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably-arranged communications system. FIG.1illustrates an example wireless network according to embodiments of the present disclosure. The embodiment of the wireless network shown inFIG.1is for illustration only. Other embodiments of the wireless network100could be used without departing from the scope of the present disclosure. As shown inFIG.1, the wireless network includes a gNB101(e.g., base station (BS)), a gNB102, and a gNB103. The gNB101communicates with the gNB102and the gNB103. The gNB101also communicates with at least one network130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. The gNB102provides wireless broadband access to the network130for a first plurality of user equipments (UEs) within a coverage area120of the gNB102. The first plurality of UEs includes a UE111, which may be located in a small business (SB); a UE112, which may be located in an enterprise (E); a UE113, which may be located in a WiFi hotspot (HS); a UE114, which may be located in a first residence (R); a UE115, which may be located in a second residence (R); and a UE116, which may be a mobile device (M), such as a cell phone, a wireless laptop, a wireless PDA, or the like. The gNB103provides wireless broadband access to the network130for a second plurality of UEs within a coverage area125of the gNB103. The second plurality of UEs includes the UE115and the UE116. In some embodiments, one or more of the gNBs101-103may communicate with each other and with the UEs111-116using 5G, LTE, LTE-A, WiMAX, WiFi, or other wireless communication techniques. Depending on the network type, the term “base station” or “BS” can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G 3GPP new radio interface/access (NR), long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a/b/g/n/ac, etc. For the sake of convenience, the terms “BS” and “TRP” are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term “user equipment” or “UE” can refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receive point,” or “user device.” For the sake of convenience, the terms “user equipment” and “UE” are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine). Dotted lines show the approximate extents of the coverage areas120and125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs, such as the coverage areas120and125, may have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions. As described in more detail below, one or more of the UEs111-116include circuitry, programing, or a combination thereof, for changing an STS index/counter for IEEE 802.15.4z communications. In certain embodiments, and one or more of the gNBs101-103includes circuitry, programing, or a combination thereof, for changing an STS index/counter for IEEE 802.15.4z communications. AlthoughFIG.1illustrates one example of a wireless network, various changes may be made toFIG.1. For example, the wireless network could include any number of gNBs and any number of UEs in any suitable arrangement. Also, the gNB101could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network130. Similarly, each gNB102-103could communicate directly with the network130and provide UEs with direct wireless broadband access to the network130. Further, the gNBs101,102, and/or103could provide access to other or additional external networks, such as external telephone networks or other types of data networks. FIG.2illustrates an example gNB102according to embodiments of the present disclosure. The embodiment of the gNB102illustrated inFIG.2is for illustration only, and the gNBs101and103ofFIG.1could have the same or similar configuration. However, gNBs come in a wide variety of configurations, andFIG.2does not limit the scope of the present disclosure to any particular implementation of a gNB. As shown inFIG.2, the gNB102includes multiple antennas205a-205n, multiple RF transceivers210a-210n, transmit (TX) processing circuitry215, and receive (RX) processing circuitry220. The gNB102also includes a controller/processor225, a memory230, and a backhaul or network interface235. The RF transceivers210a-210nreceive, from the antennas205a-205n, incoming RF signals, such as signals transmitted by UEs in the network100. The RF transceivers210a-210ndown-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to the RX processing circuitry220, which generates processed baseband signals by filtering, decoding, and/or digitizing the baseband or IF signals. The RX processing circuitry220transmits the processed baseband signals to the controller/processor225for further processing. The TX processing circuitry215receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller/processor225. The TX processing circuitry215encodes, multiplexes, and/or digitizes the outgoing baseband data to generate processed baseband or IF signals. The RF transceivers210a-210nreceive the outgoing processed baseband or IF signals from the TX processing circuitry215and up-converts the baseband or IF signals to RF signals that are transmitted via the antennas205a-205n. The controller/processor225can include one or more processors or other processing devices that control the overall operation of the gNB102. For example, the controller/processor225could control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers210a-210n, the RX processing circuitry220, and the TX processing circuitry215in accordance with well-known principles. The controller/processor225could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller/processor225could support beam forming or directional routing operations in which outgoing signals from multiple antennas205a-205nare weighted differently to effectively steer the outgoing signals in a desired direction. Any of a wide variety of other functions could be supported in the gNB102by the controller/processor225. The controller/processor225is also capable of executing programs and other processes resident in the memory230, such as an OS. The controller/processor225can move data into or out of the memory230as required by an executing process. The controller/processor225is also coupled to the backhaul or network interface235. The backhaul or network interface235allows the gNB102to communicate with other devices or systems over a backhaul connection or over a network. The interface235could support communications over any suitable wired or wireless connection(s). For example, when the gNB102is implemented as part of a cellular communication system (such as one supporting 5G, LTE, or LTE-A), the interface235could allow the gNB102to communicate with other gNBs over a wired or wireless backhaul connection. When the gNB102is implemented as an access point, the interface235could allow the gNB102to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface235includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver. The memory230is coupled to the controller/processor225. Part of the memory230could include a RAM, and another part of the memory230could include a Flash memory or other ROM. AlthoughFIG.2illustrates one example of gNB102, various changes may be made toFIG.2. For example, the gNB102could include any number of each component shown inFIG.2. As a particular example, an access point could include a number of interfaces235, and the controller/processor225could support routing functions to route data between different network addresses. As another particular example, while shown as including a single instance of TX processing circuitry215and a single instance of RX processing circuitry220, the gNB102could include multiple instances of each (such as one per RF transceiver). Also, various components inFIG.2could be combined, further subdivided, or omitted and additional components could be added according to particular needs. FIG.3illustrates an example UE116according to embodiments of the present disclosure. The embodiment of the UE116illustrated inFIG.3is for illustration only, and the UEs111-115ofFIG.1could have the same or similar configuration. However, UEs come in a wide variety of configurations, andFIG.3does not limit the scope of the present disclosure to any particular implementation of a UE. As shown inFIG.3, the UE116includes an antenna305, a radio frequency (RF) transceiver310, TX processing circuitry315, a microphone320, and receive (RX) processing circuitry325. The UE116also includes a speaker330, a processor340, an input/output (I/O) interface (IF)345, a touchscreen350, a display355, and a memory360. The memory360includes an operating system (OS)361and one or more applications362. The RF transceiver310receives, from the antenna305, an incoming RF signal transmitted by a gNB of the network100. The RF transceiver310down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuitry325, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry325transmits the processed baseband signal to the speaker330(such as for voice data) or to the processor340for further processing (such as for web browsing data). The TX processing circuitry315receives analog or digital voice data from the microphone320or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor340. The TX processing circuitry315encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver310receives the outgoing processed baseband or IF signal from the TX processing circuitry315and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna305. The processor340can include one or more processors or other processing devices and execute the OS361stored in the memory360in order to control the overall operation of the UE116. For example, the processor340could control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver310, the RX processing circuitry325, and the TX processing circuitry315in accordance with well-known principles. In some embodiments, the processor340includes at least one microprocessor or microcontroller. The processor340is also capable of executing other processes and programs resident in the memory360, such as processes for CSI reporting on uplink channel. The processor340can move data into or out of the memory360as required by an executing process. In some embodiments, the processor340is configured to execute the applications362based on the OS361or in response to signals received from gNBs or an operator. The processor340is also coupled to the I/O interface345, which provides the UE116with the ability to connect to other devices, such as laptop computers and handheld computers. The I/O interface345is the communication path between these accessories and the processor340. The processor340is also coupled to the touchscreen350and the display355. The operator of the UE116can use the touchscreen350to enter data into the UE116. The display355may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from web sites. The memory360is coupled to the processor340. Part of the memory360could include a random-access memory (RAM), and another part of the memory360could include a Flash memory or other read-only memory (ROM). AlthoughFIG.3illustrates one example of UE116, various changes may be made toFIG.3. For example, various components inFIG.3could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor340could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, whileFIG.3illustrates the UE116configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices. FIG.4Ais a high-level diagram of transmit path circuitry. For example, the transmit path circuitry may be used for an orthogonal frequency division multiple access (OFDMA) communication.FIG.4Bis a high-level diagram of receive path circuitry. For example, the receive path circuitry may be used for an orthogonal frequency division multiple access (OFDMA) communication. InFIGS.4A and4B, for downlink communication, the transmit path circuitry may be implemented in a base station (gNB)102or a relay station, and the receive path circuitry may be implemented in a user equipment (e.g., user equipment116ofFIG.1). In other examples, for uplink communication, the receive path circuitry450may be implemented in a base station (e.g., gNB102ofFIG.1) or a relay station, and the transmit path circuitry may be implemented in a user equipment (e.g., user equipment116ofFIG.1). Transmit path circuitry comprises channel coding and modulation block405, serial-to-parallel (S-to-P) block410, Size N Inverse Fast Fourier Transform (IFFT) block415, parallel-to-serial (P-to-S) block420, add cyclic prefix block425, and up-converter (UC)430. Receive path circuitry450comprises down-converter (DC)455, remove cyclic prefix block460, serial-to-parallel (S-to-P) block465, Size N Fast Fourier Transform (FFT) block470, parallel-to-serial (P-to-S) block475, and channel decoding and demodulation block480. At least some of the components inFIGS.4A400and4B450may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. In particular, it is noted that the FFT blocks and the IFFT blocks described in the present disclosure document may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation. Furthermore, although the present disclosure is directed to an embodiment that implements the Fast Fourier Transform and the Inverse Fast Fourier Transform, this is by way of illustration only and may not be construed to limit the scope of the present disclosure. It may be appreciated that in an alternate embodiment of the present disclosure, the Fast Fourier Transform functions and the Inverse Fast Fourier Transform functions may easily be replaced by discrete Fourier transform (DFT) functions and inverse discrete Fourier transform (IDFT) functions, respectively. It may be appreciated that for DFT and IDFT functions, the value of the N variable may be any integer number (i.e., 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of the N variable may be any integer number that is a power of two (i.e., 1, 2, 4, 8, 16, etc.). In transmit path circuitry400, channel coding and modulation block405receives a set of information bits, applies coding (e.g., LDPC coding) and modulates (e.g., quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) the input bits to produce a sequence of frequency-domain modulation symbols. Serial-to-parallel block410converts (i.e., de-multiplexes) the serial modulated symbols to parallel data to produce N parallel symbol streams where N is the IFFT/FFT size used in BS102and UE116. Size N IFFT block415then performs an IFFT operation on the N parallel symbol streams to produce time-domain output signals. Parallel-to-serial block420converts (i.e., multiplexes) the parallel time-domain output symbols from Size N IFFT block415to produce a serial time-domain signal. Add cyclic prefix block425then inserts a cyclic prefix to the time-domain signal. Finally, up-converter430modulates (i.e., up-converts) the output of add cyclic prefix block425to RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency. The transmitted RF signal arrives at the UE116after passing through the wireless channel, and reverse operations to those at the gNB102are performed. Down-converter455down-converts the received signal to baseband frequency and remove cyclic prefix block460removes the cyclic prefix to produce the serial time-domain baseband signal. Serial-to-parallel block465converts the time-domain baseband signal to parallel time-domain signals. Size N FFT block470then performs an FFT algorithm to produce N parallel frequency-domain signals. Parallel-to-serial block475converts the parallel frequency-domain signals to a sequence of modulated data symbols. Channel decoding and demodulation block480demodulates and then decodes the modulated symbols to recover the original input data stream. Each of gNBs101-103may implement a transmit path that is analogous to transmitting in the downlink to user equipment111-116and may implement a receive path that is analogous to receiving in the uplink from user equipment111-116. Similarly, each one of user equipment111-116may implement a transmit path corresponding to the architecture for transmitting in the uplink to gNBs101-103and may implement a receive path corresponding to the architecture for receiving in the downlink from gNBs101-103. A peer aware communication (PAC) network is a fully distributed communication network that allows direct communication among the PAC devices (PDs). PAC networks may employ several topologies like mesh, star, etc. to support interactions among the PDs for various services. While the present disclosure uses PAC networks and PDs as an example to develop and illustrate the present disclosure, it is to be noted that the present disclosure is not confined to these networks. The general concepts developed in the present disclosure may be employed in various type of networks with different kind of scenarios. FIG.5illustrates an example electronic device501according to embodiments of the present disclosure. The embodiment of the electronic device501illustrated inFIG.5is for illustration only.FIG.5does not limit the scope of the present disclosure to any particular implementation. The electronic device501may be performed a function or functions of111-116as illustrated inFIG.1. In one embodiment, the electronic device may be111-116and/or101-103as illustrated inFIG.1. PDs can be an electronic device.FIG.5illustrates an example electronic device501according to various embodiments. Referring toFIG.5, the electronic device501may communicate with an electronic device502via a first network598(e.g., a short-range wireless communication network), or an electronic device104or a server508via a second network599(e.g., a long-range wireless communication network). According to an embodiment, the electronic device501may communicate with the electronic device504via the server508. According to an embodiment, the electronic device501may include a processor520, memory530, an input device550, a sound output device555, a display device560, an audio570, a sensor576, an interface577, a haptic579, a camera580, a power management588, a battery589, a communication interface590, a subscriber identification module (SIM)596, or an antenna597. In some embodiments, at least one (e.g., the display device560or the camera580) of the components may be omitted from the electronic device501, or one or more other components may be added in the electronic device501. In some embodiments, some of the components may be implemented as single integrated circuitry. For example, the sensor576(e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) may be implemented as embedded in the display device560(e.g., a display). The processor520may execute, for example, software (e.g., a program540) to control at least one other component (e.g., a hardware or software component) of the electronic device501coupled with the processor520and may perform various data processing or computation. According to one embodiment of the present disclosure, as at least part of the data processing or computation, the processor520may load a command or data received from another component (e.g., the sensor576or the communication interface590) in volatile memory532, process the command or the data stored in the volatile memory532, and store resulting data in non-volatile memory534. According to an embodiment of the present disclosure, the processor520may include a main processor521(e.g., a central processing unit (CPU) or an application processor (AP)), and an auxiliary processor523(e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently from, or in conjunction with, the main processor521. Additionally, or alternatively, the auxiliary processor523may be adapted to consume less power than the main processor521, or to be specific to a specified function. The auxiliary processor523may be implemented as separate from, or as part of the main processor521. The auxiliary processor523may control at least some of functions or states related to at least one component (e.g., the display device560, the sensor576, or the communication interface590) among the components of the electronic device501, instead of the main processor521while the main processor521is in an inactive (e.g., sleep) state, or together with the main processor521while the main processor521is in an active state (e.g., executing an application). According to an embodiment, the auxiliary processor523(e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera580or the communication interface190) functionally related to the auxiliary processor523. The memory530may store various data used by at least one component (e.g., the processor520or the sensor576) of the electronic device501. The various data may include, for example, software (e.g., the program540) and input data or output data for a command related thereto. The memory530may include the volatile memory532or the non-volatile memory534. The program50may be stored in the memory530as software, and may include, for example, an operating system (OS)542, middleware544, or an application546. The input device550may receive a command or data to be used by another component (e.g., the processor520) of the electronic device501, from the outside (e.g., a user) of the electronic device501. The input device550may include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus pen). The sound output device555may output sound signals to the outside of the electronic device501. The sound output device555may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or playing record, and the receiver may be used for incoming calls. According to an embodiment, the receiver may be implemented as separate from, or as part of the speaker. The display device560may visually provide information to the outside (e.g., a user) of the electronic device501. The display device560may include, for example, a display, a hologram device, or a projector and control circuitry to control a corresponding one of the displays, hologram device, and projector. According to an embodiment, the display device560may include touch circuitry adapted to detect a touch, or sensor circuitry (e.g., a pressure sensor) adapted to measure the intensity of force incurred by the touch. The audio570may convert a sound into an electrical signal and vice versa. According to an embodiment, the audio570may obtain the sound via the input device550, or output the sound via the sound output device555or a headphone of an external electronic device (e.g., an electronic device502) directly (e.g., using wired line) or wirelessly coupled with the electronic device501. The sensor576may detect an operational state (e.g., power or temperature) of the electronic device #01or an environmental state (e.g., a state of a user) external to the electronic device501, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor576may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor. The interface577may support one or more specified protocols to be used for the electronic device501to be coupled with the external electronic device (e.g., the electronic device502) directly (e.g., using wired line) or wirelessly. According to an embodiment of the present disclosure, the interface577may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface. A connecting terminal578may include a connector via which the electronic device501may be physically connected with the external electronic device (e.g., the electronic device502). According to an embodiment, the connecting terminal578may include, for example, a HDMI connector, a USB connector, a SD card connector, or an audio connector (e.g., a headphone connector). The haptic579may convert an electrical signal into a mechanical stimulus (e.g., a vibration or a movement) or electrical stimulus which may be recognized by a user via his tactile sensation or kinesthetic sensation. According to an embodiment, the haptic579may include, for example, a motor, a piezoelectric element, or an electric stimulator. The camera580may capture a still image or moving images. According to an embodiment of the present disclosure, the camera580may include one or more lenses, image sensors, image signal processors, or flashes. The power management588may manage power supplied to the electronic device501. According to one embodiment, the power management588may be implemented as at least part of, for example, a power management integrated circuit (PMIC). The battery589may supply power to at least one component of the electronic device501. According to an embodiment, the battery589may include, for example, a primary cell which is not rechargeable, a secondary cell which is rechargeable, or a fuel cell. The communication interface590may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device501and the external electronic device (e.g., the electronic device502, the electronic device504, or the server508) and performing communication via the established communication channel. The communication interface590may include one or more communication processors that are operable independently from the processor520(e.g., the application processor (AP)) and supports a direct (e.g., wired) communication or a wireless communication. According to an embodiment of the present disclosure, the communication interface590may include a wireless communication interface592(e.g., a cellular communication interface, a short-range wireless communication interface, or a global navigation satellite system (GNSS) communication interface) or a wired communication interface594(e.g., a local area network (LAN) communication interface or a power line communication (PLC)). A corresponding one of these communication interfaces may communicate with the external electronic device via the first network598(e.g., a short-range communication network, such as Bluetooth, wireless-fidelity (Wi-Fi) direct, ultra-wide band (UWB), or infrared data association (IrDA)) or the second network599(e.g., a long-range communication network, such as a cellular network, the Internet, or a computer network (e.g., LAN or wide area network (WAN)). These various types of communication interfaces may be implemented as a single component (e.g., a single chip), or may be implemented as multi components (e.g., multi chips) separate from each other. The wireless communication interface592may identify and authenticate the electronic device501in a communication network, such as the first network598or the second network599, using sub scriber information (e.g., international mobile sub scriber identity (IMSI)) stored in the subscriber identification module596. The antenna597may transmit or receive a signal or power to or from the outside (e.g., the external electronic device) of the electronic device501. According to an embodiment, the antenna597may include an antenna including a radiating element composed of a conductive material or a conductive pattern formed in or on a substrate (e.g., PCB). According to an embodiment, the antenna597may include a plurality of antennas. In such a case, at least one antenna appropriate for a communication scheme used in the communication network, such as the first network198or the second network599, may be selected, for example, by the communication interface590(e.g., the wireless communication interface592) from the plurality of antennas. The signal or the power may then be transmitted or received between the communication interface590and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as part of the antenna597. At least some of the above-described components may be coupled mutually and communicate signals (e.g., commands or data) there between via an inter-peripheral communication scheme (e.g., a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)). According to an embodiment of the present disclosure, commands or data may be transmitted or received between the electronic device501and the external electronic device504via the server508coupled with the second network599. Each of the electronic devices502and504may be a device of a same type as, or a different type, from the electronic device501. According to an embodiment, all or some of operations to be executed at the electronic device501may be executed at one or more of the external electronic devices502,504, or508. For example, if the electronic device501may perform a function or a service automatically, or in response to a request from a user or another device, the electronic device501, instead of, or in addition to, executing the function or the service, may request the one or more external electronic devices to perform at least part of the function or the service. The one or more external electronic devices receiving the request may perform the at least part of the function or the service requested, or an additional function or an additional service related to the request and transfer an outcome of the performing to the electronic device501. The electronic device501may provide the outcome, with or without further processing of the outcome, as at least part of a reply to the request. To that end, a cloud computing, distributed computing, or client-server computing technology may be used, for example. The electronic device according to various embodiments may be one of various types of electronic devices. The electronic devices may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. According to an embodiment of the present disclosure, the electronic devices are not limited to those described above. Various embodiments as set forth herein may be implemented as software (e.g., the program140) including one or more instructions that are stored in a storage medium (e.g., internal memory536or external memory538) that is readable by a machine (e.g., the electronic device501). For example, a processor(e.g., the processor520) of the machine (e.g., the electronic device501) may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. This allows the machine to be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include a code generated by a complier or a code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Wherein, the term “non-transitory” simply means that the storage medium is a tangible device, and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium. According to an embodiment of the present disclosure, a method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store (e.g., Play Store™), or between two user devices (e.g., smart phones) directly. If distributed online, at least part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as memory of the manufacturer's server, a server of the application store, or a relay server. According to various embodiments of the present disclosure, each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities. According to various embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively, or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, according to various embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as one or more functions are performed by a corresponding one of the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added. Ultra-wideband communication, realized by sending a short radio pulse, brings some key benefits to wireless communications, including low-complexity transceiver design, large capacity by utilizing large bandwidth, and robustness to inter-symbol-interference (ISI) of multi-path environment. Meanwhile, the extremely narrow pulses also lower the probability of interception and detection by the third party, which is promising for the data service with highly secure requirement, e.g., secure ranging. Currently, IEEE 802.15.4z is exploring and developing enhancements for capabilities of low rate and high rate UWB impulse radio, aiming to provide better integrity and efficiency. Ranging and relative localization are essential for various location-based services and applications, e.g., Wi-Fi direct, internet-of-things (IoTs), etc. With the tremendous increasing of network devices, high demands of ranging requests can be foreseen in the near future, which implies overall ranging message exchanges occur frequently in the network. This may worsen the bottleneck limited by the battery capacity. Energy efficiency becomes more critical for mobile devices, and self-sustained static devices, e.g., low-power sensors. Another critical issue in the dense environment is the latency to fulfill the scheduled ranging sessions for different ranging pairs. Based on the ranging procedures as defined in IEEE specification, each ranging pair may be assigned with dedicated time slots. It may result in long latency for latter scheduled pairs if there exist large amounts of ranging requests. Therefore, implementation of more efficient ranging protocols is necessary to reduce the number of required message exchanges for many ranging pairs. In the present disclosure, the optimized ranging procedure is provided between a group of devices and another group of devices. As illustrated inFIG.6, one or more devices of group-1has the ranging request to one or more devices of group-2or vice versa. Exploiting the broadcast characteristics of wireless channel, mechanisms of optimized transmissions can be respectively realized based on the ranging operation, i.e., single-sided two-way ranging (SS-TWR) and double-sided two-way ranging (DS-TWR), which significantly reduce the number of required information exchange, compared with the current standard. FIG.6illustrates an example many-to-many scenario600according to embodiments of the present disclosure. The embodiment of the many-to-many scenario600illustrated inFIG.6is for illustration only.FIG.6does not limit the scope of the present disclosure to any particular implementation. As illustrated inFIG.6, each node in group1and group2may performs a function or functions of111-116and101-103as illustrated inFIG.1. In one embodiment, each node in group1and group2may be one of111-116and/or be one of101-103as illustrated inFIG.1. As illustrated inFIG.6, group-1and group2determined with one or more devices. One or more devices from group-1have ranging requests to one or more devices from group-2. In the present disclosure, for a pair of devices to fulfill message exchange of ranging, the devices and associated messages is provided by following respective terms: initiator; device which initializes and sends the first ranging frame (RFRAME) to one or more responders; responder, device which expects to receive the first RFRAME from one or more initiators; poll, RFRAME sent by initiator, and ranging response. RFRAME is sent by responder. There are two aspects neglected in IEEE standard specification, which are essential for future use cases. The first one is the optimized transmission procedure between one or more initiators and one or more responders, which can be critical for energy-saving purpose. Since a poll can be broadcast to multiple responders, an initiator can initialize a multicast, i.e., one-to-many, ranging round by sending a single poll instead of launching multiple unicast ranging rounds. Similarly, since the ranging response can also be broadcast to multiple initiators, a responder can embed the requested data respectively from different initiator in a single ranging response message. Exploiting the broadcast characteristics of wireless channel, the optimized transmission procedure is promising for future UWB network. The other neglected aspect is the option for the contention-based ranging in an UWB network. In IEEE specification, one ranging round just contains a single pair of devices, i.e., one initiator and one responder. Within one ranging round, transmissions are implicitly scheduled: a responder/initiator expects to receive the message from the far end and may start to transmit afterwards. multiple ranging rounds can be scheduled by the CFP table of the sync frame. However, there can be other use cases that cannot be supported by IEEE standard specification. For example, the initiator broadcasts the poll, but the initiator does not have the prior-knowledge of who may response. Similarly, the responder may not have the prior-knowledge of who may initialize the ranging, so the responder can wait and listen for a certain period of time to collect polls respectively from different initiators. In the present disclosure, an UWB network is provided with ranging requests between a group of devices and another group of devices. As shown inFIG.6, one or more devices of group-1has the ranging request to one or more devices of group-2or vice versa. To accommodate optimized ranging transmission procedure and other new use cases, the configuration of device role, i.e., whether the configuration of device is an initiator or a responder, and the scheduling information for scheduling-based ranging, need to be determined and exchanged before the ranging round starts. Aiming to build a stand-alone UWB network, the present disclosure defines new control IE, and ranging scheduling IE for initiators and responders, which can be exchanged over the UWB MAC. However, the present disclosure does not preclude other methods to exchange information via the higher layer or out-of-band management. FIG.7illustrates an example single-sided two-way ranging700according to embodiments of the present disclosure. The embodiment of the single-sided two-way ranging700illustrated inFIG.7is for illustration only.FIG.7does not limit the scope of the present disclosure to any particular implementation. The single-sided two-way ranging700may be performed in the electronic device501as illustrated inFIG.5. SS-TWR involves a simple measurement of the round-trip delay of a single message from the initiator to the responder and a response sent back to the initiator. The operation of SS-TWR is as shown inFIG.7, where device A initiates the exchange and device B responds to complete the exchange. Each device precisely timestamps the transmission and reception times of the message frames, and so can calculate times Troundand Treplyby simple subtraction. Hence, the resultant time-of-flight, Tprop, can be estimated by the equation T^prop=12(Tround-Treply). FIG.8illustrates an example double-sided two-way ranging with three messages800according to embodiments of the present disclosure. The embodiment of the double-sided two-way ranging with three messages800illustrated inFIG.8is for illustration only.FIG.8does not limit the scope of the present disclosure to any particular implementation. The double-sided two-way ranging with three messages800may be performed in the electronic device501as illustrated inFIG.5. DS-TWR with three messages is illustrated inFIG.8, which reduces the estimation error induced by clock drift from long response delays. Device A is the initiator to initialize the first round-trip measurement, while device B as the responder, responses to complete the first round-trip measurement, and meanwhile initialize the second round-trip measurement. Each device precisely timestamps the transmission and reception times of the messages, and the resultant time-of-flight estimate, Tprop, can be calculated by the expression: T^prop=(Tround1×Tround2-Treply1×Treply2)(Tround1+Tround2+Treply1+Treply2). In the development of IEEE 802.15.4z, the main enhancement for secure ranging is the inclusion a scrambled timestamp sequence (STS) in the basic PHY protocol data unit (PPDU) format. Since the unique STS of a device is known by one or more far ends in a trusted group, the secure ranging can be performed within the trusted group, and the chance of being attacked is significantly reduced. In the present disclosure, it is provided that STSs of devices have been exchanged successfully, which can be done via, e.g., a higher layer control or out-of-band management. How to initialize/update STS and exchange it between devices is out of the scope of this disclosure. FIG.9illustrates an example secure ranging PPDU formats900according to embodiments of the present disclosure. The embodiment of secure ranging PPDU formats900illustrated inFIG.9is for illustration only.FIG.9does not limit the scope of the present disclosure to any particular implementation. The secure ranging PPDU formats900may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. As illustrated inFIG.9, three secure ranging PPDU formats may be supported, the difference between the formats being the location of the STS and existence of a PHR and PHY payload field asFIG.9. InFIG.9, a synchronization header (SHR), a (scrambled timestamp sequence) and a PHY header (PHY) are provided. Since the STS dynamically change per each ranging frame, it enhances the security to combat attacker. Specifically, it is extremely difficult for attacker to track the exact same STS of desired user for first path detection. However, in the current IEEE 802.15.4z, to update portions of STS may induce transmission of redundant bits. In the present disclosure, an UWB network is provided with ranging requests between a group of devices and another group of devices. As illustrated inFIG.6, one or more devices of group-1has the ranging request to one or more devices of group-2or vice versa. This disclosure modifies the format of control signaling to enhance the flexibility of adjusting STS. FIG.10illustrates an example structure of ranging round1000according to embodiments of the present disclosure. The embodiment of the structure of ranging round1000illustrated inFIG.10is for illustration only.FIG.10does not limit the scope of the present disclosure to any particular implementation. The structure of ranging round1000may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. A ranging configuration incorporates the control information of a ranging round, which consists of multiple time slots asFIG.10. Time slot is the basic time unit to fulfill a message exchange. Other conventions to fulfill the same functionalities as ranging round and time slot are not precluded in this disclosure. Depending on the device capabilities, slot duration and number of time slots in a ranging round can be adjusted in the ranging configuration, or they are fixed to a default setting. One or multiple pairs of devices can participate in a ranging round to fulfill the ranging requests. FIG.11illustrates a signaling flow including controller and controlee1100according to embodiments of the present disclosure. The embodiment of the flow including controller and controlee1100illustrated inFIG.11is for illustration only.FIG.11does not limit the scope of the present disclosure to any particular implementation. The flow including controller and controlee1100may be performed in the electronic device501as illustrated inFIG.5. The flow including controller and controlee1100may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. The setting of a ranging configuration determined by the next higher layer can be sent to one or more ranging controlees from a ranging controller (lead device) as illustrated inFIG.11. With different network formations, the ranging configuration can be conveyed via a dedicated data frame sent to one or more devices, or it can be embedded into a sync frame broadcast to all devices in the network. Meanwhile, this disclosure does not preclude other methods to exchange the ranging configuration information, e.g., via the higher layer or our-of-band management. FIG.12illustrates an example ranging round structure1200according to embodiments of the present disclosure. The embodiment of the ranging round structure1200illustrated inFIG.12is for illustration only.FIG.12does not limit the scope of the present disclosure to any particular implementation. The ranging round structure1200may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. Ranging configuration includes the structure of a ranging round which contains one or more polling periods (PP) and one or more ranging response periods (RRP), where a PP consists of one or more time slots to send polling messages from initiator(s), and an RRP consists one or more time slots to send response messages from responder(s).FIG.12respectively illustrates two examples for the SS-TWR and DS-TWR with three message exchanges, other examples are not precluded. A ranging round can start with a ranging control period to exchange the ranging configuration over the UWB MAC. However, a ranging round can also start with a polling period if the ranging configuration is exchanged at the higher layer. As illustrated inFIG.12, for the SS-TWR, one ranging round contains a PP and an RRP. For the DS-TWR with three messages, one ranging round contains a first PP, an RRP, and a second PP. Each period consists of one or more time slots, where transmissions from initiator(s)/responder(s) can be scheduled as determined by the next higher layer or they can contend time slots in the corresponding periods, respectively. FIG.13illustrates an example DRBG for STS1300according to embodiments of the present disclosure. The embodiment of the DRBG for STS1300illustrated inFIG.13is for illustration only.FIG.13does not limit the scope of the present disclosure to any particular implementation. The DRBG for STS1300may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. The STS may be generated using a deterministic random bit generator (DRBG). The structure of the DRBG is shown inFIG.13. Each time the DRBG is run, it produces a 128-bit pseudo-random number used to form128pulses of the STS. As illustrated inFIG.13, the upper layer is responsible for setting the 128-bit key, via the phyHrpUwbStsKey attribute, along with the 128-bit initial value for V, via the phyHrpUwbStsVCounter and phyHrpUwbStsVUpper96 attributes. The 32-bit counter part of V is incremented before each iteration of the DRBG to give a new V value each time it is run to produce 128 bits/pulses for the STS. The receiver may use the same mechanism and aligned values of the key and V to generate a complementary sequence for cross correlation with the transmitted sequence. The mechanisms for agreeing, coordinating and synchronizing these values between HRP-SRDEV, are the responsibility of the upper layers. FIG.14illustrates an example RSKI IE content field format1400according to embodiments of the present disclosure. The embodiment of the RSKI IE content field format1400illustrated inFIG.14is for illustration only.FIG.14does not limit the scope of the present disclosure to any particular implementation. The RSKI IE content field format1400may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. In the current spec of IEEE 802.15.4z, the ranging STS Key and IV IE (RSKI IE) may be used to convey and align the seed, (i.e., key and data IV), used for STS generation. The content field of the RSKI IE may be formatted as shown inFIG.14. The IVC field indicates the content of the STS IV Counter field as follows: an IVC field value of means that just the 4-octet Counter portion of the IV is included, while an IVC field value of 1 means that the full 16-octet IV is included. The SKP field indicates the presence of the STS Key field as follows: an SKP field value of 0 means that the STS Key field is not present, (is zero octets), while an SKP field value of 1 means that the 16-octet STS Key field is present. The ICP field indicates the presence of the Integrity Code field. The CP field is used when the RSKI IE is only conveying the 4-octet Counter portion of the IV, where a CP field value of 1 means the counter value applies to the current packet. A CP field value of 0 means that the RSKI IE applies to a future packet exchange. The STS IV counter field contains either a 16-octet string intended to initialize the full IV or a 4-octet string intended to set just counter portion of the IV. This is determined by the IVC field. The STS Key field if present, as determined by the SKP field, contains either a 16-octet string intended to initialize the STS Key. The integrity code field if present, as determined by the ICP field, contains a code intended to allow the upper layer to validate the supplied STS Key and STS IV counter fields. The STS Key, STS IV Counter and Integrity Code fields of the RSKI IE are determined and consumed by the upper layer. The upper layer is responsible for validating these as necessary and programming the phyHrpUwbStsKey, phyHrpUwbStsVUpper96 and phyHrpUwbStsVCounter PIB attributes accordingly. FIG.15illustrates an example modified content field format of RSKI IE1500according to embodiments of the present disclosure. The embodiment of the modified content field format of RSKI IE1500illustrated inFIG.15is for illustration only.FIG.15does not limit the scope of the present disclosure to any particular implementation. The modified content field format of RSKI IE1500may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. As illustrated inFIG.14, the STS IV counter can be used to exchange the full V value formed by phyHrpUwbStsVCounter and phyHrpUwbStsVUpper96 attributes inFIG.13, or its lower 32-bit counter in phyHrpUwbStsVCounter. In order to exchange the update for other portions, rather than lower 32-bit counter, of V, the full V value has to be sent in the RSKI IE, and occupies 16-octet, whereas many bit fields may be redundant to transmit. To enhance the flexibility of adjusting STS update, a modified content field structure of RSKI IE is illustrated inFIG.15. The first field of IV present (IVP) with 4-bit is used to indicate which portion of IV may be updated by the field of STS IV Counter. Specifically, 4 bits of IVP represent the bit ranges of IV, i.e., 1˜32, 33˜64, 65˜96, and 97˜128, respectively. STS IV Counter field concatenates 4-byte (32-bit) strings that are used to update IV portions with corresponding bit field being 1 in IVP. For example, if value of IVP field is “1111,” then STS IV counter field conveys the full 16-octet to update IV. If value of IVP is “1001,” then STS IV counter conveys 8-octet string, where first 4-octet string is used to update 1-32 bits of IV, and later 4-octet string is used to update 97128 bits of IV. Other fields ofFIG.15remain the same as those ofFIG.14. The present disclosure does not preclude other combinations of bit fields to fulfill the same function. FIG.16illustrates another example modified content field format of RSKI IE1600according to embodiments of the present disclosure. The embodiment of the modified content field format of RSKI IE1600illustrated inFIG.16is for illustration only.FIG.16does not limit the scope of the present disclosure to any particular implementation. The modified content field format of RSKI IE1600may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. As illustrated inFIG.16, the fields of IVS and WE indicate the starting byte index and ending byte index of IV respectively, which specify the range of IV that may be updated by the field of STS IV Counter. For example, if IVS is “0100,” and WE is “1000,” the starting byte index is 4, and the ending byte index is 8. Therefore, STS IV Counter occupies 5-octet to update 4-8 bytes of IV. Note that the index of first byte of IV is zero, i.e., “0000.” The size of STS IV Counter is aligned with the range specified by IVS and WE. This disclosure does not preclude other options to specify the bit ranges of IV, where STS IV Counter may apply to update. FIG.17illustrates a flowchart of a method1700for changing STS index/counter according to embodiments of the present disclosure, as may be performed by a network entity. The embodiment of the method1700illustrated inFIG.17is for illustration only.FIG.17does not limit the scope of the present disclosure to any particular implementation. The method1700may be performed in the electronic device501(e.g.,101-103and111-116as illustrated inFIG.1) as illustrated inFIG.5. The electronic device may be implemented as a network entity supporting a ranging operation. As illustrated inFIG.17, the method1700begins at step1702. In step1702, the network entity identifies at least one set of bit strings to generate a ranging scrambled timestamp sequence (STS). Subsequently, the network entity in step1704identifies at least one initialization vector (IV) field corresponding to the at least one set of bit strings, wherein the at least one IV field comprises a 4-octet string. Next, the network entity in step1706generates a ranging STS key and IV information element (RSKI IE) that includes the at least one IV field to convey and align a seed that is used to generate the ranging STS. In one embodiment, the RSKI IE includes: an IV starting (IVS) field indicating a starting byte index of the IV field; an IV ending (WE) field indicating an ending byte index of the IV field; an STS IV counter field indicating a value of STS IV counter; and the IVS field and the WE field identify a range of the IV field that is updated by the STS IV counter field. Finally, the network entity in step1708transmits, to another network entity, the generated RSKI IE for updating the ranging STS of the second network entity. In one embodiment, the network entity generates the RSKI IE to include an IV counter present (IVCP) field indicating whether an IV counter field is included in the RSKI IE. In such embodiment, the IV counter field includes a 4-octet string comprising information to set an IV counter. In one embodiment, the network entity generates the RSKI IE to include at least one IV present (IVP) field indicating whether the at least one IV field is included in the RSKI IE. In such embodiment, the at least one IVP field includes: an IV1P field indicating whether an IV1 field is included in the RSKI IE; an IV2P field indicating whether an IV2 field is included in the RSKI IE; an IV3P field indicating whether an IV3 field is included in the RSKI IE; the IV1 field includes a 4-octet string that is used to set bits32to63for updating an IV counter; the IV2 field includes a 4-octet string that is used to set bits64to95for updating the IV counter; and the IV3 field includes a 4-octet string that is used to set bits96to127for updating the IV counter. Although the present disclosure has been described with an exemplary embodiment, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope | 62,313 |
11943737 | DETAILED DESCRIPTION Referring now to the drawings in general, the illustrations are for the purpose of describing at least one preferred embodiment and/or examples of the invention and are not intended to limit the invention thereto. Various embodiments are described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers are used throughout the drawings to refer to the same or like parts. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the invention or the claims. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations. The present invention provides systems, methods, and devices for spectrum analysis and management by identifying, classifying, and cataloging at least one or a multiplicity of signals of interest based on radio frequency measurements and location and other measurements, and using near real-time parallel processing of signals and their corresponding parameters and characteristics in the context of historical and static data for a given spectrum. The systems, methods and apparatus according to the present invention preferably have the ability to detect in near real time, and more preferably to detect, sense, measure, and/or analyze in near real time, and more preferably to perform any near real time operations within about 1 second or less. Advantageously, the present invention and its real time functionality described herein uniquely provide and enable the apparatus units to compare to historical data, to update data and/or information, and/or to provide more data and/or information on the open space, on the device that may be occupying the open space, and combinations, in the near real time compared with the historically scanned (15 min to 30 days) data, or historical database information. The systems, methods, and devices of the various embodiments enable spectrum management by identifying, classifying, and cataloging signals of interest based on radio frequency measurements. In an embodiment, signals and the parameters of the signals may be identified and indications of available frequencies may be presented to a user. In another embodiment, the protocols of signals may also be identified. In a further embodiment, the modulation of signals, data types carried by the signals, and estimated signal origins may be identified. Embodiments are directed to a spectrum management device that may be configurable to obtain spectrum data over a wide range of wireless communication protocols. Embodiments may also provide for the ability to acquire data from and sending data to database depositories that may be used by a plurality of spectrum management customers. In one embodiment, a spectrum management device may include a signal spectrum analyzer that may be coupled with a database system and spectrum management interface. The device may be portable or may be a stationary installation and may be updated with data to allow the device to manage different spectrum information based on frequency, bandwidth, signal power, time, and location of signal propagation, as well as modulation type and format and to provide signal identification, classification, and geo-location. A processor may enable the device to process spectrum power density data as received and to process raw I/Q complex data that may be used for further signal processing, signal identification, and data extraction. In an embodiment, a spectrum management device may comprise a low noise amplifier that receives a radio frequency (RF) energy from an antenna. The antenna may be any antenna structure that is capable of receiving RF energy in a spectrum of interest. The low noise amplifier may filter and amplify the RF energy. The RF energy may be provided to an RF translator. The RF translator may perform a fast Fourier transform (FFT) and either a square magnitude or a fast convolution spectral periodogram function to convert the RF measurements into a spectral representation. In an embodiment, the RF translator may also store a timestamp to facilitate calculation of a time of arrival and an angle of arrival. The In-Phase and Quadrature (I/Q) data may be provided to a spectral analysis receiver or it may be provided to a sample data store where it may be stored without being processed by a spectral analysis receiver. The input RF energy may also be directly digital down-converted and sampled by an analog to digital converter (ADC) to generate complex I/Q data. The complex I/Q data may be equalized to remove multipath, fading, white noise and interference from other signaling systems by fast parallel adaptive filter processes. This data may then be used to calculate modulation type and baud rate. Complex sampled I/Q data may also be used to measure the signal angle of arrival and time of arrival. Such information as angle of arrival and time of arrival may be used to compute more complex and precise direction finding. In addition, they may be used to apply geo-location techniques. Data may be collected from known signals or unknown signals and time spaced in order to provide expedient information. I/Q sampled data may contain raw signal data that may be used to demodulate and translate signals by streaming them to a signal analyzer or to a real-time demodulator software defined radio that may have the newly identified signal parameters for the signal of interest. The inherent nature of the input RF allows for any type of signal to be analyzed and demodulated based on the reconfiguration of the software defined radio interfaces. A spectral analysis receiver may be configured to read raw In-Phase (I) and Quadrature (Q) data and either translate directly to spectral data or down convert to an intermediate frequency (IF) up to half the Nyquist sampling rate to analyze the incoming bandwidth of a signal. The translated spectral data may include measured values of signal energy, frequency, and time. The measured values provide attributes of the signal under review that may confirm the detection of a particular signal of interest within a spectrum of interest. In an embodiment, a spectral analysis receiver may have a referenced spectrum input of 0 Hz to 12.4 GHz with capability of fiber optic input for spectrum input up to 60 GHz. In an embodiment, the spectral analysis receiver may be configured to sample the input RF data by fast analog down-conversion of the RF signal. The down-converted signal may then be digitally converted and processed by fast convolution filters to obtain a power spectrum. This process may also provide spectrum measurements including the signal power, the bandwidth, the center frequency of the signal as well as a Time of Arrival (TOA) measurement. The TOA measurement may be used to create a timestamp of the detected signal and/or to generate a time difference of arrival iterative process for direction finding and fast triangulation of signals. In an embodiment, the sample data may be provided to a spectrum analysis module. In an embodiment, the spectrum analysis module may evaluate the sample data to obtain the spectral components of the signal. In an embodiment, the spectral components of the signal may be obtained by the spectrum analysis module from the raw I/Q data as provided by an RF translator. The I/Q data analysis performed by the spectrum analysis module may operate to extract more detailed information about the signal, including by way of example, modulation type (e.g., FM, AM, QPSK, 16QAM, etc.) and/or protocol (e.g., GSM, CDMA, OFDM, LTE, etc.). In an embodiment, the spectrum analysis module may be configured by a user to obtain specific information about a signal of interest. In an alternate embodiment, the spectral components of the signal may be obtained from power spectral component data produced by the spectral analysis receiver. In an embodiment, the spectrum analysis module may provide the spectral components of the signal to a data extraction module. The data extraction module may provide the classification and categorization of signals detected in the RF spectrum. The data extraction module may also acquire additional information regarding the signal from the spectral components of the signal. For example, the data extraction module may provide modulation type, bandwidth, and possible system in use information. In another embodiment, the data extraction module may select and organize the extracted spectral components in a format selected by a user. The information from the data extraction module may be provided to a spectrum management module. The spectrum management module may generate a query to a static database to classify a signal based on its components. For example, the information stored in static database may be used to determine the spectral density, center frequency, bandwidth, baud rate, modulation type, protocol (e.g., GSM, CDMA, OFDM, LTE, etc.), system or carrier using licensed spectrum, location of the signal source, and a timestamp of the signal of interest. These data points may be provided to a data store for export. In an embodiment and as more fully described below, the data store may be configured to access mapping software to provide the user with information on the location of the transmission source of the signal of interest. In an embodiment, the static database includes frequency information gathered from various sources including, but not limited to, the Federal Communication Commission, the International Telecommunication Union, and data from users. As an example, the static database may be an SQL database. The data store may be updated, downloaded or merged with other devices or with its main relational database. Software API applications may be included to allow database merging with third-party spectrum databases that may only be accessed securely. In the various embodiments, the spectrum management device may be configured in different ways. In an embodiment, the front end of system may comprise various hardware receivers that may provide In-Phase and Quadrature complex data. The front end receiver may include API set commands via which the system software may be configured to interface (i.e., communicate) with a third party receiver. In an embodiment, the front end receiver may perform the spectral computations using FFT (Fast Fourier Transform) and other DSP (Digital Signal Processing) to generate a fast convolution periodogram that may be re-sampled and averaged to quickly compute the spectral density of the RF environment. In an embodiment, cyclic processes may be used to average and correlate signal information by extracting the changes inside the signal to better identify the signal of interest that is present in the RF space. A combination of amplitude and frequency changes may be measured and averaged over the bandwidth time to compute the modulation type and other internal changes, such as changes in frequency offsets, orthogonal frequency division modulation, changes in time (e.g., Time Division Multiplexing), and/or changes in I/Q phase rotation used to compute the baud rate and the modulation type. In an embodiment, the spectrum management device may have the ability to compute several processes in parallel by use of a multi-core processor and along with several embedded field programmable gate arrays (FPGA). Such multi-core processing may allow the system to quickly analyze several signal parameters in the RF environment at one time in order to reduce the amount of time it takes to process the signals. The amount of signals computed at once may be determined by their bandwidth requirements. Thus, the capability of the system may be based on a maximum frequency Fs/2. The number of signals to be processed may be allocated based on their respective bandwidths. In another embodiment, the signal spectrum may be measured to determine its power density, center frequency, bandwidth and location from which the signal is emanating and a best match may be determined based on the signal parameters based on information criteria of the frequency. In another embodiment, a GPS and direction finding location (DF) system may be incorporated into the spectrum management device and/or available to the spectrum management device. Adding GPS and DF ability may enable the user to provide a location vector using the National Marine Electronics Association's (NMEA) standard form. In an embodiment, location functionality is incorporated into a specific type of GPS unit, such as a U.S. government issued receiver. The information may be derived from the location presented by the database internal to the device, a database imported into the device, or by the user inputting geo-location parameters of longitude and latitude which may be derived as degrees, minutes and seconds, decimal minutes, or decimal form and translated to the necessary format with the default being ‘decimal’ form. This functionality may be incorporated into a GPS unit. The signal information and the signal classification may then be used to locate the signaling device as well as to provide a direction finding capability. A type of triangulation using three units as a group antenna configuration performs direction finding by using multilateration. Commonly used in civil and military surveillance applications, multilateration is able to accurately locate an aircraft, vehicle, or stationary emitter by measuring the “Time Difference of Arrival” (TDOA) of a signal from the emitter at three or more receiver sites. If a pulse is emitted from a platform, it will arrive at slightly different times at two spatially separated receiver sites, the TDOA being due to the different distances of each receiver from the platform. This location information may then be supplied to a mapping process that utilizes a database of mapping images that are extracted from the database based on the latitude and longitude provided by the geo-location or direction finding device. The mapping images may be scanned in to show the points of interest where a signal is either expected to be emanating from based on the database information or from an average taken from the database information and the geo-location calculation performed prior to the mapping software being called. The user can control the map to maximize or minimize the mapping screen to get a better view which is more fit to provide information of the signal transmissions. In an embodiment, the mapping process does not rely on outside mapping software. The mapping capability has the ability to generate the map image and to populate a mapping database that may include information from third party maps to meet specific user requirements. In an embodiment, triangulation and multilateration may utilize a Bayesian type filter that may predict possible movement and future location and operation of devices based on input collected from the TDOA and geolocation processes and the variables from the static database pertaining to the specified signal of interest. The Bayesian filter takes the input changes in time difference and its inverse function (i.e., frequency difference) and takes an average change in signal variation to detect and predict the movement of the signals. The signal changes are measured within 1 ns time difference and the filter may also adapt its gradient error calculation to remove unwanted signals that may cause errors due to signal multipath, inter-symbol interference, and other signal noise. In an embodiment the changes within a 1 ns time difference for each sample for each unique signal may be recorded. The spectrum management device may then perform the inverse and compute and record the frequency difference and phase difference between each sample for each unique signal. The spectrum management device may take the same signal and calculates an error based on other input signals coming in within the 1 ns time and may average and filter out the computed error to equalize the signal. The spectrum management device may determine the time difference and frequency difference of arrival for that signal and compute the odds of where the signal is emanating from based on the frequency band parameters presented from the spectral analysis and processor computations, and determines the best position from which the signal is transmitted (i.e., origin of the signal). FIG.1illustrates a wireless environment100suitable for use with the various embodiments. The wireless environment100may include various sources104,106,108,110,112, and114generating various radio frequency (RF) signals116,118,120,122,124,126. As an example, mobile devices104may generate cellular RF signals116, such as CDMA, GSM, 3G signals, etc. As another example, wireless access devices106, such as Wi-Fi® routers, may generate RF signals118, such as Wi-Fi® signals. As a further example, satellites108, such as communication satellites or GPS satellites, may generate RF signals120, such as satellite radio, television, or GPS signals. As a still further example, base stations110, such as a cellular base station, may generate RF signals122, such as CDMA, GSM, 3G signals, etc. As another example, radio towers112, such as local AM or FM radio stations, may generate RF signals124, such as AM or FM radio signals. As another example, government service provides114, such as police units, fire fighters, military units, air traffic control towers, etc. may generate RF signals126, such as radio communications, tracking signals, etc. The various RF signals116,118,120,122,124,126may be generated at different frequencies, power levels, in different protocols, with different modulations, and at different times. The various sources104,106,108,110,112, and114may be assigned frequency bands, power limitations, or other restrictions, requirements, and/or licenses by a government spectrum control entity, such as the FCC. However, with so many different sources104,106,108,110,112, and114generating so many different RF signals116,118,120,122,124,126, overlaps, interference, and/or other problems may occur. A spectrum management device102in the wireless environment100may measure the RF energy in the wireless environment100across a wide spectrum and identify the different RF signals116,118,120,122,124,126which may be present in the wireless environment100. The identification and cataloging of the different RF signals116,118,120,122,124,126which may be present in the wireless environment100may enable the spectrum management device102to determine available frequencies for use in the wireless environment100. In addition, the spectrum management device102may be able to determine if there are available frequencies for use in the wireless environment100under certain conditions (i.e., day of week, time of day, power level, frequency band, etc.). In this manner, the RF spectrum in the wireless environment100may be managed. FIG.2Ais a block diagram of a spectrum management device202according to an embodiment. The spectrum management device202may include an antenna structure204configured to receive RF energy expressed in a wireless environment. The antenna structure204may be any type antenna, and may be configured to optimize the receipt of RF energy across a wide frequency spectrum. The antenna structure204may be connected to one or more optional amplifiers and/or filters208which may boost, smooth, and/or filter the RF energy received by antenna structure204before the RF energy is passed to an RF receiver210connected to the antenna structure204. In an embodiment, the RF receiver210may be configured to measure the RF energy received from the antenna structure204and/or optional amplifiers and/or filters208. In an embodiment, the RF receiver210may be configured to measure RF energy in the time domain and may convert the RF energy measurements to the frequency domain. In an embodiment, the RF receiver210may be configured to generate spectral representation data of the received RF energy. The RF receiver210may be any type RF receiver, and may be configured to generate RF energy measurements over a range of frequencies, such as 0 kHz to 24 GHz, 9 kHz to 6 GHz, etc. In an embodiment, the frequency scanned by the RF receiver210may be user selectable. In an embodiment, the RF receiver210may be connected to a signal processor214and may be configured to output RF energy measurements to the signal processor214. As an example, the RF receiver210may output raw In-Phase (I) and Quadrature (Q) data to the signal processor214. As another example, the RF receiver210may apply signals processing techniques to output complex In-Phase (I) and Quadrature (Q) data to the signal processor214. In an embodiment, the spectrum management device may also include an antenna206connected to a location receiver212, such as a GPS receiver, which may be connected to the signal processor214. The location receiver212may provide location inputs to the signal processor214. The signal processor214may include a signal detection module216, a comparison module222, a timing module224, and a location module225. Additionally, the signal processor214may include an optional memory module226which may include one or more optional buffers228for storing data generated by the other modules of the signal processor214. In an embodiment, the signal detection module216may operate to identify signals based on the RF energy measurements received from the RF receiver210. The signal detection module216may include a Fast Fourier Transform (FFT) module217which may convert the received RF energy measurements into spectral representation data. The signal detection module216may include an analysis module221which may analyze the spectral representation data to identify one or more signals above a power threshold. A power module220of the signal detection module216may control the power threshold at which signals may be identified. In an embodiment, the power threshold may be a default power setting or may be a user selectable power setting. A noise module219of the signal detection module216may control a signal threshold, such as a noise threshold, at or above which signals may be identified. The signal detection module216may include a parameter module218which may determine one or more signal parameters for any identified signals, such as center frequency, bandwidth, power, number of detected signals, frequency peak, peak power, average power, signal duration, etc. In an embodiment, the signal processor214may include a timing module224which may record time information and provide the time information to the signal detection module216. Additionally, the signal processor214may include a location module225which may receive location inputs from the location receiver212and determine a location of the spectrum management device202. The location of the spectrum management device202may be provided to the signal detection module216. In an embodiment, the signal processor214may be connected to one or more memory230. The memory230may include multiple databases, such as a history or historical database232and characteristics listing236, and one or more buffers240storing data generated by signal processor214. While illustrated as connected to the signal processor214the memory230may also be on chip memory residing on the signal processor214itself. In an embodiment, the history or historical database232may include measured signal data234for signals that have been previously identified by the spectrum management device202. The measured signal data234may include the raw RF energy measurements, time stamps, location information, one or more signal parameters for any identified signals, such as center frequency, bandwidth, power, number of detected signals, frequency peak, peak power, average power, signal duration, etc., and identifying information determined from the characteristics listing236. In an embodiment, the history or historical database232may be updated as signals are identified by the spectrum management device202. In an embodiment, the characteristic listing236may be a database of static signal data238. The static signal data238may include data gathered from various sources including by way of example and not by way of limitation the Federal Communication Commission, the International Telecommunication Union, telecom providers, manufacture data, and data from spectrum management device users. Static signal data238may include known signal parameters of transmitting devices, such as center frequency, bandwidth, power, number of detected signals, frequency peak, peak power, average power, signal duration, geographic information for transmitting devices, and any other data that may be useful in identifying a signal. In an embodiment, the static signal data238and the characteristic listing236may correlate signal parameters and signal identifications. As an example, the static signal data238and characteristic listing236may list the parameters of the local fire and emergency communication channel correlated with a signal identification indicating that signal is the local fire and emergency communication channel. In an embodiment, the signal processor214may include a comparison module222which may match data generated by the signal detection module216with data in the history or historical database232and/or characteristic listing236. In an embodiment the comparison module222may receive signal parameters from the signal detection module216, such as center frequency, bandwidth, power, number of detected signals, frequency peak, peak power, average power, signal duration, and/or receive parameter from the timing module224and/or location module225. The parameter match module223may retrieve data from the history or historical database232and/or the characteristic listing236and compare the retrieved data to any received parameters to identify matches. Based on the matches the comparison module may identify the signal. In an embodiment, the signal processor214may be optionally connected to a display242, an input device244, and/or network transceiver246. The display242may be controlled by the signal processor214to output spectral representations of received signals, signal characteristic information, and/or indications of signal identifications on the display242. In an embodiment, the input device244may be any input device, such as a keyboard and/or knob, mouse, virtual keyboard or even voice recognition, enabling the user of the spectrum management device202to input information for use by the signal processor214. In an embodiment, the network transceiver246may enable the spectrum management device202to exchange data with wired and/or wireless networks, such as to update the characteristic listing236and/or upload information from the history or historical database232. FIG.2Bis a schematic logic flow block diagram illustrating logical operations which may be performed by a spectrum management device202according to an embodiment. A receiver210may output RF energy measurements, such as I and Q data to an FFT module252which may generate a spectral representation of the RF energy measurements which may be output on a display242. The I and Q data may also be buffered in a buffer256and sent to a signal detection module216. The signal detection module216may receive location inputs from a location receiver212and use the received I and Q data to detect signals. Data from the signal detection module216may be buffered in a buffer262and written into a history or historical database232. Additionally, data from the historical database may be used to aid in the detection of signals by the signal detection module216. The signal parameters of the detected signals may be determined by a signal parameters module218using information from the history or historical database232and/or a static database238listing signal characteristics through a buffer268. Data from the signal parameters module218may be stored in the history or historical database232and/or sent to the signal detection module216and/or display242. In this manner, signals may be detected and indications of the signal identification may be displayed to a user of the spectrum management device. FIG.3illustrates a process flow of an embodiment method300for identifying a signal. In an embodiment the operations of method300may be performed by the processor214of a spectrum management device202. In block302the processor214may determine the location of the spectrum management device202. In an embodiment, the processor214may determine the location of the spectrum management device202based on a location input, such as GPS coordinates, received from a location receiver, such as a GPS receiver212. In block304the processor214may determine the time. As an example, the time may be the current clock time as determined by the processor214and may be a time associated with receiving RF measurements. In block306the processor214may receive RF energy measurements. In an embodiment, the processor214may receive RF energy measurements from an RF receiver210. In block308the processor214may convert the RF energy measurements to spectral representation data. As an example, the processor may apply a Fast Fourier Transform (FFT) to the RF energy measurements to convert them to spectral representation data. In optional block310the processor214may display the spectral representation data on a display242of the spectrum management device202, such as in a graph illustrating amplitudes across a frequency spectrum. In block312the processor214may identify one or more signal above a threshold. In an embodiment, the processor214may analyze the spectral representation data to identify a signal above a power threshold. A power threshold may be an amplitude measure selected to distinguish RF energies associated with actual signals from noise. In an embodiment, the power threshold may be a default value. In another embodiment, the power threshold may be a user selectable value. In block314the processor214may determine signal parameters of any identified signal or signals of interest. As examples, the processor214may determine signal parameters such as center frequency, bandwidth, power, number of detected signals, frequency peak, peak power, average power, signal duration for the identified signals. In block316the processor214may store the signal parameters of each identified signal, a location indication, and time indication for each identified signal in a history database232. In an embodiment, a history database232may be a database resident in a memory230of the spectrum management device202which may include data associated with signals actually identified by the spectrum management device. In block318the processor214may compare the signal parameters of each identified signal to signal parameters in a signal characteristic listing. In an embodiment, the signal characteristic listing may be a static database238stored in the memory230of the spectrum management device202which may correlate signal parameters and signal identifications. In determination block320the processor214may determine whether the signal parameters of the identified signal or signals match signal parameters in the characteristic listing236. In an embodiment, a match may be determined based on the signal parameters being within a specified tolerance of one another. As an example, a center frequency match may be determined when the center frequencies are within plus or minus 1 kHz of each other. In this manner, differences between real world measured conditions of an identified signal and ideal conditions listed in a characteristics listing may be accounted for in identifying matches. If the signal parameters do not match (i.e., determination block320=“No”), in block326the processor214may display an indication that the signal is unidentified on a display242of the spectrum management device202. In this manner, the user of the spectrum management device may be notified that a signal is detected, but has not been positively identified. If the signal parameters do match (i.e., determination block320=“Yes”), in block324the processor214may display an indication of the signal identification on the display242. In an embodiment, the signal identification displayed may be the signal identification correlated to the signal parameter in the signal characteristic listing which matched the signal parameter for the identified signal. Upon displaying the indications in blocks324or326the processor214may return to block302and cyclically measure and identify further signals of interest. FIG.4illustrates an embodiment method400for measuring sample blocks of a radio frequency scan. In an embodiment the operations of method400may be performed by the processor214of a spectrum management device202. As discussed above, in blocks306and308the processor214may receive RF energy measurements and convert the RF energy measurements to spectral representation data. In block402the processor214may determine a frequency range at which to sample the RF spectrum for signals of interest. In an embodiment, a frequency range may be a frequency range of each sample block to be analyzed for potential signals. As an example, the frequency range may be 240 kHz. In an embodiment, the frequency range may be a default value. In another embodiment, the frequency range may be a user selectable value. In block404the processor214may determine a number (N) of sample blocks to measure. In an embodiment, each sample block may be sized to the determined of default frequency range, and the number of sample blocks may be determined by dividing the spectrum of the measured RF energy by the frequency range. In block406the processor214may assign each sample block a respective frequency range. As an example, if the determined frequency range is 240 kHz, the first sample block may be assigned a frequency range from 0 kHz to 240 kHz, the second sample block may be assigned a frequency range from 240 kHz to 480 kHz, etc. In block408the processor214may set the lowest frequency range sample block as the current sample block. In block409the processor214may measure the amplitude across the set frequency range for the current sample block. As an example, at each frequency interval (such as 1 Hz) within the frequency range of the sample block the processor214may measure the received signal amplitude. In block410the processor214may store the amplitude measurements and corresponding frequencies for the current sample block. In determination block414the processor214may determine if all sample blocks have been measured. If all sample blocks have not been measured (i.e., determination block414=“No”), in block416the processor214may set the next highest frequency range sample block as the current sample block. As discussed above, in blocks409,410, and414the processor214may measure and store amplitudes and determine whether all blocks are sampled. If all blocks have been sampled (i.e., determination block414=“Yes”), the processor214may return to block306and cyclically measure further sample blocks. FIGS.5A,5B, and5Cillustrate the process flow for an embodiment method500for determining signal parameters. In an embodiment the operations of method500may be performed by the processor214of a spectrum management device202. Referring toFIG.5A, in block502the processor214may receive a noise floor average setting. In an embodiment, the noise floor average setting may be an average noise level for the environment in which the spectrum management device202is operating. In an embodiment, the noise floor average setting may be a default setting and/or may be user selectable setting. In block504the processor214may receive the signal power threshold setting. In an embodiment, the signal power threshold setting may be an amplitude measure selected to distinguish RF energies associated with actual signals from noise. In an embodiment the signal power threshold may be a default value and/or may be a user selectable setting. In block506the processor214may load the next available sample block. In an embodiment, the sample blocks may be assembled according to the operations of method400described above with reference toFIG.4. In an embodiment, the next available sample block may be an oldest in time sample block which has not been analyzed to determine whether signals of interest are present in the sample block. In block508the processor214may average the amplitude measurements in the sample block. In determination block510the processor214may determine whether the average for the sample block is greater than or equal to the noise floor average set in block502. In this manner, sample blocks including potential signals may be quickly distinguished from sample blocks which may not include potential signals reducing processing time by enabling sample blocks without potential signals to be identified and ignored. If the average for the sample block is lower than the noise floor average (i.e., determination block510=“No”), no signals of interest may be present in the current sample block. In determination block514the processor214may determine whether a cross block flag is set. If the cross block flag is not set (i.e., determination block514=“No”), in block506the processor214may load the next available sample block and in block508average the sample block508. If the average of the sample block is equal to or greater than the noise floor average (i.e., determination block510=“Yes”), the sample block may potentially include a signal of interest and in block512the processor214may reset a measurement counter (C) to 1. The measurement counter value indicating which sample within a sample block is under analysis. In determination block516the processor214may determine whether the RF measurement of the next frequency sample (C) is greater than the signal power threshold. In this manner, the value of the measurement counter (C) may be used to control which sample RF measurement in the sample block is compared to the signal power threshold. As an example, when the counter (C) equals 1, the first RF measurement may be checked against the signal power threshold and when the counter (C) equals 2 the second RF measurement in the sample block may be checked, etc. If the C RF measurement is less than or equal to the signal power threshold (i.e., determination block516=“No”), in determination block517the processor214may determine whether the cross block flag is set. If the cross block flag is not set (i.e., determination block517=“No”), in determination block522the processor214may determine whether the end of the sample block is reached. If the end of the sample block is reached (i.e., determination block522=“Yes”), in block506the processor214may load the next available sample block and proceed in blocks508,510,514, and512as discussed above. If the end of the sample block is not reached (i.e., determination block522=“No”), in block524the processor214may increment the measurement counter (C) so that the next sample in the sample block is analyzed. If the C RF measurement is greater than the signal power threshold (i.e., determination block516=“Yes”), in block518the processor214may check the status of the cross block flag to determine whether the cross block flag is set. If the cross block flag is not set (i.e., determination block518=“No”), in block520the processor214may set a sample start. As an example, the processor214may set a sample start by indicating a potential signal of interest may be discovered in a memory by assigning a memory location for RF measurements associated with the sample start. Referring toFIG.5B, in block526the processor214may store the C RF measurement in a memory location for the sample currently under analysis. In block528the processor214may increment the measurement counter (C) value. In determination block530the processor214may determine whether the C RF measurement (e.g., the next RF measurement because the value of the RF measurement counter was incremented) is greater than the signal power threshold. If the C RF measurement is greater than the signal power threshold (i.e., determination block530=“Yes”), in determination block532the processor214may determine whether the end of the sample block is reached. If the end of the sample block is not reached (i.e., determination block532=“No”), there may be further RF measurements available in the sample block and in block526the processor214may store the C RF measurement in the memory location for the sample. In block528the processor may increment the measurement counter (C) and in determination block530determine whether the C RF measurement is above the signal power threshold and in block532determine whether the end of the sample block is reached. In this manner, successive sample RF measurements may be checked against the signal power threshold and stored until the end of the sample block is reached and/or until a sample RF measurement falls below the signal power threshold. If the end of the sample block is reached (i.e., determination block532=“Yes”), in block534the processor214may set the cross block flag. In an embodiment, the cross block flag may be a flag in a memory available to the processor214indicating the signal potential spans across two or more sample blocks. In a further embodiment, prior to setting the cross block flag in block534, the slope of a line drawn between the last two RF measurement samples may be used to determine whether the next sample block likely contains further potential signal samples. A negative slope may indicate that the signal of interest is fading and may indicate the last sample was the final sample of the signal of interest. In another embodiment, the slope may not be computed and the next sample block may be analyzed regardless of the slope. If the end of the sample block is reached (i.e., determination block532=“Yes”) and in block534the cross block flag is set, referring toFIG.5A, in block506the processor214may load the next available sample block, in block508may average the sample block, and in block510determine whether the average of the sample block is greater than or equal to the noise floor average. If the average is equal to or greater than the noise floor average (i.e., determination block510=“Yes”), in block512the processor214may reset the measurement counter (C) to 1. In determination block516the processor214may determine whether the C RF measurement for the current sample block is greater than the signal power threshold. If the C RF measurement is greater than the signal power threshold (i.e., determination block516=“Yes”), in determination block518the processor214may determine whether the cross block flag is set. If the cross block flag is set (i.e., determination block518=“Yes”), referring toFIG.5B, in block526the processor214may store the C RF measurement in the memory location for the sample and in block528the processor may increment the measurement counter (C). As discussed above, in blocks530and532the processor214may perform operations to determine whether the C RF measurement is greater than the signal power threshold and whether the end of the sample block is reached until the C RF measurement is less than or equal to the signal power threshold (i.e., determination block530=“No”) or the end of the sample block is reached (i.e., determination block532=“Yes”). If the end of the sample block is reached (i.e., determination block532=“Yes”), as discussed above in block534the cross block flag may be set (or verified and remain set if already set) and in block535the C RF measurement may be stored in the sample. If the end of the sample block is reached (i.e., determination block532=“Yes”) and in block534the cross block flag is set, referring toFIG.5A, the processor may perform operations of blocks506,508,510,512,516, and518as discussed above. If the average of the sample block is less than the noise floor average (i.e., determination block510=“No”) and the cross block flag is set (i.e., determination block514=“Yes”), the C RF measurement is less than or equal to the signal power threshold (i.e., determination block516=“No”) and the cross block flag is set (i.e., determination block517=“Yes”), or the C RF measurement is less than or equal to the signal power threshold (i.e., determination block516=“No”), referring toFIG.5B, in block538the processor214may set the sample stop. As an example, the processor214may indicate that a sample end is reached in a memory and/or that a sample is complete in a memory. In block540the processor214may compute and store complex I and Q data for the stored measurements in the sample. In block542the processor214may determine a mean of the complex I and Q data. Referring toFIG.5C, in determination block544the processor214may determine whether the mean of the complex I and Q data is greater than a signal threshold. If the mean of the complex I and Q data is less than or equal to the signal threshold (i.e., determination block544=“No”), in block550the processor214may indicate the sample is noise and discard data associated with the sample from memory. If the mean is greater than the signal threshold (i.e., determination block544=“Yes”), in block546the processor214may identify the sample as a signal of interest. In an embodiment, the processor214may identify the sample as a signal of interest by assigning a signal identifier to the signal, such as a signal number or sample number. In block548the processor214may determine and store signal parameters for the signal. As an example, the processor214may determine and store a frequency peak of the identified signal, a peak power of the identified signal, an average power of the identified signal, a signal bandwidth of the identified signal, and/or a signal duration of the identified signal. In block552the processor214may clear the cross block flag (or verify that the cross block flag is unset). In block556the processor214may determine whether the end of the sample block is reached. If the end of the sample block is not reached (i.e., determination block556=“No”) in block558the processor214may increment the measurement counter (C), and referring toFIG.5Ain determination block516may determine whether the C RF measurement is greater than the signal power threshold. Referring toFIG.5C, if the end of the sample block is reached (i.e., determination block556=“Yes”), referring toFIG.5A, in block506the processor214may load the next available sample block. FIG.6illustrates a process flow for an embodiment method600for displaying signal identifications. In an embodiment, the operations of method600may be performed by a processor214of a spectrum management device202. In determination block602the processor214may determine whether a signal is identified. If a signal is not identified (i.e., determination block602=“No”), in block604the processor214may wait for the next scan. If a signal is identified (i.e., determination block602=“Yes”), in block606the processor214may compare the signal parameters of an identified signal to signal parameters in a history database232. In determination block608the processor214may determine whether signal parameters of the identified signal match signal parameters in the history database232. If there is no match (i.e., determination block608=“No”), in block610the processor214may store the signal parameters as a new signal in the history database232. If there is a match (i.e., determination block608=“Yes”), in block612the processor214may update the matching signal parameters as needed in the history database232. In block614the processor214may compare the signal parameters of the identified signal to signal parameters in a signal characteristic listing236. In an embodiment, the characteristic listing236may be a static database separate from the history database232, and the characteristic listing236may correlate signal parameters with signal identifications. In determination block616the processor214may determine whether the signal parameters of the identified signal match any signal parameters in the signal characteristic listing236. In an embodiment, the match in determination616may be a match based on a tolerance between the signal parameters of the identified signal and the parameters in the characteristic listing236. If there is a match (i.e., determination block616=“Yes”), in block618the processor214may indicate a match in the history database232and in block622may display an indication of the signal identification on a display242. As an example, the indication of the signal identification may be a display of the radio call sign of an identified FM radio station signal. If there is not a match (i.e., determination block616=“No”), in block620the processor214may display an indication that the signal is an unidentified signal. In this manner, the user may be notified a signal is present in the environment, but that the signal does not match to a signal in the characteristic listing. FIG.7illustrates a process flow of an embodiment method700for displaying one or more open frequency. In an embodiment, the operations of method700may be performed by the processor214of a spectrum management device202. In block702the processor214may determine a current location of the spectrum management device202. In an embodiment, the processor214may determine the current location of the spectrum management device202based on location inputs received from a location receiver212, such as GPS coordinates received from a GPS receiver212. In block704the processor214may compare the current location to the stored location value in the historical database232. As discussed above, the historical or history database232may be a database storing information about signals previously actually identified by the spectrum management device202. In determination block706the processor214may determine whether there are any matches between the location information in the historical database232and the current location. If there are no matches (i.e., determination block706=“No”), in block710the processor214may indicate incomplete data is available. In other words the spectrum data for the current location has not previously been recorded. If there are matches (i.e., determination block706=“Yes”), in optional block708the processor214may display a plot of one or more of the signals matching the current location. As an example, the processor214may compute the average frequency over frequency intervals across a given spectrum and may display a plot of the average frequency over each interval. In block712the processor214may determine one or more open frequencies at the current location. As an example, the processor214may determine one or more open frequencies by determining frequency ranges in which no signals fall or at which the average is below a threshold. In block714the processor214may display an indication of one or more open frequency on a display242of the spectrum management device202. FIG.8Ais a block diagram of a spectrum management device802according to an embodiment. Spectrum management device802is similar to spectrum management device202described above with reference toFIG.2A, except that spectrum management device802may include symbol module816and protocol module806enabling the spectrum management device802to identify the protocol and symbol information associated with an identified signal as well as protocol match module814to match protocol information. Additionally, the characteristic listing236of spectrum management device802may include protocol data804, hardware data808, environment data810, and noise data812and an optimization module818may enable the signal processor214to provide signal optimization parameters. The protocol module806may identify the communication protocol (e.g., LTE, CDMA, etc.) associated with a signal of interest. In an embodiment, the protocol module806may use data retrieved from the characteristic listing, such as protocol data804to help identify the communication protocol. The symbol detector module816may determine symbol timing information, such as a symbol rate for a signal of interest. The protocol module806and/or symbol module816may provide data to the comparison module222. The comparison module222may include a protocol match module814which may attempt to match protocol information for a signal of interest to protocol data804in the characteristic listing to identify a signal of interest. Additionally, the protocol module806and/or symbol module816may store data in the memory module226and/or history database232. In an embodiment, the protocol module806and/or symbol module816may use protocol data804and/or other data from the characteristic listing236to help identify protocols and/or symbol information in signals of interest. The optimization module818may gather information from the characteristic listing, such as noise figure parameters, antenna hardware parameters, and environmental parameters correlated with an identified signal of interest to calculate a degradation value for the identified signal of interest. The optimization module818may further control the display242to output degradation data enabling a user of the spectrum management device802to optimize a signal of interest. FIG.8Bis a schematic logic flow block diagram illustrating logical operations which may be performed by a spectrum management device according to an embodiment. Only those logical operations illustrated inFIG.8Bdifferent from those described above with reference toFIG.2Bwill be discussed. As illustrated inFIG.8B, as received time tracking850may be applied to the I and Q data from the receiver210. An additional buffer851may further store the I and Q data received and a symbol detector852may identify the symbols of a signal of interest and determine the symbol rate. A multiple access scheme identifier module854may identify whether the signal is part of a multiple access scheme (e.g., CDMA), and a protocol identifier module856may attempt to identify the protocol the signal of interested is associated with. The multiple access scheme identifier module854and protocol identifier module856may retrieve data from the static database238to aid in the identification of the access scheme and/or protocol. The symbol detector module852may pass data to the signal parameter and protocol module858which may store protocol and symbol information in addition to signal parameter information for signals of interest. FIG.9illustrates a process flow of an embodiment method900for determining protocol data and symbol timing data. In an embodiment, the operations of method900may be performed by the processor214of a spectrum management device802. In determination block902the processor214may determine whether two or more signals are detected. If two or more signals are not detected (i.e., determination block902=“No”), in determination block902the processor214may continue to determine whether two or more signals are detected. If two or more signals are detected (i.e., determination block902=“Yes”), in determination block904the processor214may determine whether the two or more signals are interrelated. In an embodiment, a mean correlation value of the spectral decomposition of each signal may indicate the two or more signals are interrelated. As an example, a mean correlation of each signal may generate a value between 0.0 and 1, and the processor214may compare the mean correlation value to a threshold, such as a threshold of 0.75. In such an example, a mean correlation value at or above the threshold may indicate the signals are interrelated while a mean correlation value below the threshold may indicate the signals are not interrelated and may be different signals. In an embodiment, the mean correlation value may be generated by running a full energy bandwidth correlation of each signal, measuring the values of signal transition for each signal, and for each signal transition running a spectral correlation between signals to generate the mean correlation value. If the signals are not interrelated (i.e., determination block904=“No”), the signals may be two or more different signals, and in block907processor214may measure the interference between the two or more signals. In an optional embodiment, in optional block909the processor214may generate a conflict alarm indicating the two or more different signals interfere. In an embodiment, the conflict alarm may be sent to the history database and/or a display. In determination block902the processor214may continue to determine whether two or more signals are detected. If the two signals are interrelated (i.e., determination block904=“Yes”), in block905the processor214may identify the two or more signals as a single signal. In block906the processor214may combine signal data for the two or more signals into a signal single entry in the history database. In determination block908the processor214may determine whether the signals mean averages. If the mean averages (i.e., determination block908=“Yes”), the processor214may identify the signal as having multiple channels910. If the mean does not average (i.e., determination block908=“Yes”) or after identifying the signal as having multiple channels910, in block914the processor214may determine and store protocol data for the signal. In block916the processor214may determine and store symbol timing data for the signal, and the method900may return to block902. FIG.10illustrates a process flow of an embodiment method1000for calculating signal degradation data. In an embodiment, the operations of method1000may be performed by the processor214of a spectrum management device202. In block1002the processor may detect a signal. In block1004the processor214may match the signal to a signal in a static database. In block1006the processor214may determine noise figure parameters based on data in the static database236associated with the signal. As an example, the processor214may determine the noise figure of the signal based on parameters of a transmitter outputting the signal according to the static database236. In block1008the processor214may determine hardware parameters associated with the signal in the static database236. As an example, the processor214may determine hardware parameters such as antenna position, power settings, antenna type, orientation, azimuth, location, gain, and equivalent isotropically radiated power (EIRP) for the transmitter associated with the signal from the static database236. In block1010processor214may determine environment parameters associated with the signal in the static database236. As an example, the processor214may determine environment parameters such as rain, fog, and/or haze based on a delta correction factor table stored in the static database and a provided precipitation rate (e.g., mm/hr). In block1012the processor214may calculate and store signal degradation data for the detected signal based at least in part on the noise figure parameters, hardware parameters, and environmental parameters. As an example, based on the noise figure parameters, hardware parameters, and environmental parameters free space losses of the signal may be determined. In block1014the processor214may display the degradation data on a display242of the spectrum management device202. In a further embodiment, the degradation data may be used with measured terrain data of geographic locations stored in the static database to perform pattern distortion, generate propagation and/or next neighbor interference models, determine interference variables, and perform best fit modeling to aide in signal and/or system optimization. FIG.11illustrates a process flow of an embodiment method1100for displaying signal and protocol identification information. In an embodiment, the operations of method1100may be performed by a processor214of a spectrum management device202. In block1102the processor214may compare the signal parameters and protocol data of an identified signal to signal parameters and protocol data in a history database232. In an embodiment, a history database232may be a database storing signal parameters and protocol data for previously identified signals. In block1104the processor214may determine whether there is a match between the signal parameters and protocol data of the identified signal and the signal parameters and protocol data in the history database232. If there is not a match (i.e., determination block1104=“No”), in block1106the processor214may store the signal parameters and protocol data as a new signal in the history database232. If there is a match (i.e., determination block1104=“Yes”), in block1108the processor214may update the matching signal parameters and protocol data as needed in the history database232. In block1110the processor214may compare the signal parameters and protocol data of the identified signal to signal parameters and protocol data in the signal characteristic listing236. In determination block1112the processor214may determine whether the signal parameters and protocol data of the identified signal match any signal parameters and protocol data in the signal characteristic listing236. If there is a match (i.e., determination block1112=“Yes”), in block1114the processor214may indicate a match in the history database and in block1118may display an indication of the signal identification and protocol on a display. If there is not a match (i.e., determination block1112=“No”), in block1116the processor214may display an indication that the signal is an unidentified signal. In this manner, the user may be notified a signal is present in the environment, but that the signal does not match to a signal in the characteristic listing. FIG.12Ais a block diagram of a spectrum management device1202according to an embodiment. Spectrum management device1202is similar to spectrum management device802described above with reference toFIG.8A, except that spectrum management device1202may include TDOA/FDOA module1204and modulation module1206enabling the spectrum management device1202to identify the modulation type employed by a signal of interest and calculate signal origins. The modulation module1206may enable the signal processor to determine the modulation applied to signal, such as frequency modulation (e.g., FSK, MSK, etc.) or phase modulation (e.g., BPSK, QPSK, QAM, etc.) as well as to demodulate the signal to identify payload data carried in the signal. The modulation module1206may use payload data1221from the characteristic listing to identify the data types carried in a signal. As examples, upon demodulating a portion of the signal the payload data may enable the processor214to determine whether voice data, video data, and/or text based data is present in the signal. The TDOA/FDOA module1204may enable the signal processor214to determine time difference of arrival for signals or interest and/or frequency difference of arrival for signals of interest. Using the TDOA/FDOA information estimates of the origin of a signal may be made and passed to a mapping module1225which may control the display242to output estimates of a position and/or direction of movement of a signal. FIG.12Bis a schematic logic flow block diagram illustrating logical operations which may be performed by a spectrum management device according to an embodiment. Only those logical operations illustrated inFIG.12Bdifferent from those described above with reference toFIG.8Bwill be discussed. A magnitude squared1252operation may be performed on data from the symbol detector852to identify whether frequency or phase modulation is present in the signal. Phase modulated signals may be identified by the phase modulation1254processes and frequency modulated signals may be identified by the frequency modulation processes1256. The modulation information may be passed to a signal parameters, protocols, and modulation module1258. In one embodiment, a time tracking and TDOA/FDOA module1250is applied to the I and Q data from the RF receiver210for determining TDOA and/or FDOA for signals of interest. FIG.13illustrates a process flow of an embodiment method1300for estimating a signal origin based on a frequency difference of arrival. In an embodiment, the operations of method1300may be performed by a processor214of a spectrum management device1202. In block1302the processor214may compute frequency arrivals and phase arrivals for multiple instances of an identified signal. In block1304the processor214may determine frequency difference of arrival for the identified signal based on the computed frequency difference and phase difference. In block1306the processor may compare the determined frequency difference of arrival for the identified signal to data associated with known emitters in the characteristic listing to estimate an identified signal origin. In block1308the processor214may indicate the estimated identified signal origin on a display of the spectrum management device. As an example, the processor214may overlay the estimated origin on a map displayed by the spectrum management device. FIG.14illustrates a process flow of an embodiment method for displaying an indication of an identified data type within a signal. In an embodiment, the operations of method1400may be performed by a processor214of a spectrum management device1202. In block1402the processor214may determine the signal parameters for an identified signal of interest. In block1404the processor214may determine the modulation type for the signal of interest. In block1406the processor214may determine the protocol data for the signal of interest. In block1408the processor214may determine the symbol timing for the signal of interest. In block1410the processor214may select a payload scheme based on the determined signal parameters, modulation type, protocol data, and symbol timing. As an example, the payload scheme may indicate how data is transported in a signal. For example, data in over the air television broadcasts may be transported differently than data in cellular communications and the signal parameters, modulation type, protocol data, and symbol timing may identify the applicable payload scheme to apply to the signal. In block1412the processor214may apply the selected payload scheme to identify the data type or types within the signal of interest. In this manner, the processor214may determine what type of data is being transported in the signal, such as voice data, video data, and/or text based data. In block1414the processor may store the data type or types. In block1416the processor214may display an indication of the identified data types. FIG.15illustrates a process flow of an embodiment method1500for determining modulation type, protocol data, and symbol timing data. Method1500is similar to method900described above with reference toFIG.9, except that modulation type may also be determined. In an embodiment, the operations of method1500may be performed by a processor214of a spectrum management device1202. In blocks902,904,905,906,908, and910the processor214may perform operations of like numbered blocks of method900described above with reference toFIG.9. In block1502the processor may determine and store a modulation type. As an example, a modulation type may be an indication that the signal is frequency modulated (e.g., FSK, MSK, etc.) or phase modulated (e.g., BPSK, QPSK, QAM, etc.). As discussed above, in block914the processor may determine and store protocol data and in block916the processor may determine and store timing data. In an embodiment, based on signal detection, a time tracking module, such as a TDOA/FDOA module1204, may track the frequency repetition interval at which the signal is changing. The frequency repetition interval may also be tracked for a burst signal. In an embodiment, the spectrum management device may measure the signal environment and set anchors based on information stored in the historic or static database about known transmitter sources and locations. In an embodiment, the phase information about a signal be extracted using a spectral decomposition correlation equation to measure the angle of arrival (“AOA”) of the signal. In an embodiment, the processor of the spectrum management device may determine the received power as the Received Signal Strength (“RSS”) and based on the AOA and RSS may measure the frequency difference of arrival. In an embodiment, the frequency shift of the received signal may be measured and aggregated over time. In an embodiment, after an initial sample of a signal, known transmitted signals may be measured and compared to the RSS to determine frequency shift error. In an embodiment, the processor of the spectrum management device may compute a cross ambiguity function of aggregated changes in arrival time and frequency of arrival. In an additional embodiment, the processor of the spectrum management device may retrieve FFT data for a measured signal and aggregate the data to determine changes in time of arrival and frequency of arrival. In an embodiment, the signal components of change in frequency of arrival may be averaged through a Kalman filter with a weighted tap filter from 2 to 256 weights to remove measurement error such as noise, multipath interference, etc. In an embodiment, frequency difference of arrival techniques may be applied when either the emitter of the signal or the spectrum management device are moving or when then emitter of the signal and the spectrum management device are both stationary. When the emitter of the signal and the spectrum management device are both stationary the determination of the position of the emitter may be made when at least four known other known signal emitters positions are known and signal characteristics may be available. In an embodiment, a user may provide the four other known emitters and/or may use already in place known emitters, and may use the frequency, bandwidth, power, and distance values of the known emitters and their respective signals. In an embodiment, where the emitter of the signal or spectrum management device may be moving, frequency deference of arrival techniques may be performed using two known emitters. FIG.16illustrates an embodiment method for tracking a signal origin. In an embodiment, the operations of method1600may be performed by a processor214of a spectrum management device1202. In block1602the processor214may determine a time difference of arrival for a signal of interest. In block1604the processor214may determine a frequency difference of arrival for the signal interest. As an example, the processor214may take the inverse of the time difference of arrival to determine the frequency difference of arrival of the signal of interest. In block1606the processor214may identify the location. As an example, the processor214may determine the location based on coordinates provided from a GPS receiver. In determination block1608the processor214may determine whether there are at least four known emitters present in the identified location. As an example, the processor214may compare the geographic coordinates for the identified location to a static database and/or historical database to determine whether at least four known signals are within an area associated with the geographic coordinates. If at least four known emitters are present (i.e., determination block1608=“Yes”), in block1612the processor214may collect and measure the RSS of the known emitters and the signal of interest. As an example, the processor214may use the frequency, bandwidth, power, and distance values of the known emitters and their respective signals and the signal of interest. If less than four known emitters are present (i.e., determination block1608=“No”), in block1610the processor214may measure the angle of arrival for the signal of interest and the known emitter. Using the RSS or angle or arrival, in block1614the processor214may measure the frequency shift and in block1616the processor214may obtain the cross ambiguity function. In determination block1618the processor214may determine whether the cross ambiguity function converges to a solution. If the cross ambiguity function does converge to a solution (i.e., determination block1618=“Yes”), in block1620the processor214may aggregate the frequency shift data. In block1622the processor214may apply one or more filter to the aggregated data, such as a Kalman filter. Additionally, the processor214may apply equations, such as weighted least squares equations and maximum likelihood equations, and additional filters, such as a non-line-of-sight (“NLOS”) filters to the aggregated data. In an embodiment, the cross ambiguity function may resolve the position of the emitter of the signal of interest to within 3 meters. If the cross ambiguity function does not converge to a solution (i.e., determination block1618=“No”), in block1624the processor214may determine the time difference of arrival for the signal and in block1626the processor214may aggregate the time shift data. Additionally, the processor may filter the data to reduce interference. Whether based on frequency difference of arrival or time difference of arrival, the aggregated and filtered data may indicate a position of the emitter of the signal of interest, and in block1628the processor214may output the tracking information for the position of the emitter of the signal of interest to a display of the spectrum management device and/or the historical database. In an additional embodiment, location of emitters, time and duration of transmission at a location may be stored in the history database such that historical information may be used to perform and predict movement of signal transmission. In a further embodiment, the environmental factors may be considered to further reduce the measured error and generate a more accurate measurement of the location of the emitter of the signal of interest. The processor214of spectrum management devices202,802and1202may be any programmable microprocessor, microcomputer or multiple processor chip or chips that can be configured by software instructions (applications) to perform a variety of functions, including the functions of the various embodiments described above. In some devices, multiple processors may be provided, such as one processor dedicated to wireless communication functions and one processor dedicated to running other applications. Typically, software applications may be stored in the internal memory226or230before they are accessed and loaded into the processor214. The processor214may include internal memory sufficient to store the application software instructions. In many devices the internal memory may be a volatile or nonvolatile memory, such as flash memory, or a mixture of both. For the purposes of this description, a general reference to memory refers to memory accessible by the processor214including internal memory or removable memory plugged into the device and memory within the processor214itself Identifying Devices in White Space. The present invention provides for systems, methods, and apparatus solutions for device sensing in white space, which improves upon the prior art by identifying sources of signal emission by automatically detecting signals and creating unique signal profiles. Device sensing has an important function and applications in military and other intelligence sectors, where identifying the emitter device is crucial for monitoring and surveillance, including specific emitter identification (SEI). At least two key functions are provided by the present invention: signal isolation and device sensing. Signal Isolation according to the present invention is a process whereby a signal is detected, isolated through filtering and amplification, amongst other methods, and key characteristics extracted. Device Sensing according to the present invention is a process whereby the detected signals are matched to a device through comparison to device signal profiles and may include applying a confidence level and/or rating to the signal-profile matching. Further, device sensing covers technologies that permit storage of profile comparisons such that future matching can be done with increased efficiency and/or accuracy. The present invention systems, methods, and apparatus are constructed and configured functionally to identify any signal emitting device, including by way of example and not limitation, a radio, a cell phone, etc. Regarding signal isolation, the following functions are included in the present invention: amplifying, filtering, detecting signals through energy detection, waveform-based, spectral correlation-based, radio identification-based, or matched filter method, identifying interference, identifying environmental baseline(s), and/or identify signal characteristics. Regarding device sensing, the following functions are included in the present invention: using signal profiling and/or comparison with known database(s) and previously recorded profile(s), identifying the expected device or emitter, stating the level of confidence for the identification, and/or storing profiling and sensing information for improved algorithms and matching. In preferred embodiments of the present invention, the identification of the at least one signal emitting device is accurate to a predetermined degree of confidence between about 80 and about 95 percent, and more preferably between about 80 and about 100 percent. The confidence level or degree of confidence is based upon the amount of matching measured data compared with historical data and/or reference data for predetermined frequency and other characteristics. The present invention provides for wireless signal-emitting device sensing in the white space based upon a measured signal, and considers the basis of license(s) provided in at least one reference database, preferably the federal communication commission (FCC) and/or other defined database including license listings. The methods include the steps of providing a device for measuring characteristics of signals from signal emitting devices in a spectrum associated with wireless communications, the characteristics of the measured data from the signal emitting devices including frequency, power, bandwidth, duration, modulation, and combinations thereof; making an assessment or categorization on analog and/or digital signal(s); determining the best fit based on frequency if the measured power spectrum is designated in historical and/or reference data, including but not limited to the FCC or other database(s) for select frequency ranges; determining analog or digital, based on power and sideband combined with frequency allocation; determining a TDM/FDM/CDM signal, based on duration and bandwidth; determining best modulation fit for the desired signal, if the bandwidth and duration match the signal database(s); adding modulation identification to the database; listing possible modulations with best percentage fit, based on the power, bandwidth, frequency, duration, database allocation, and combinations thereof; and identifying at least one signal emitting device from the composite results of the foregoing steps. According to methods of the present invention, the following steps are performed automatically by the apparatus unit(s): based on the measured signal(s), input the basis of the license provided in the FCC and/or user defined database; measure the frequency, power, bandwidth, and/or duration of the measured signal(s); determine the best method of modulation identification; perform an assessment on analog or digital signal; if power spectrum is stored in designated FCC, historical, and/or user database frequency ranges, determine best fit based on frequency; based on power and sideband combined with frequency allocation, determine if analog or digital signal(s); based on duration and bandwidth determine a TDM/FDM/CDM signal; if bandwidth and duration match signal database then determine best modulation fit for the desired signal; and add modulation identification to the database and list possible modulations with best percentage fit based on the power, bandwidth, frequency, and/or duration and database allocation. In embodiments of the present invention, an apparatus is provided for automatically identifying devices in a spectrum, the apparatus including a housing, at least one processor and memory, and sensors constructed and configured for sensing and measuring wireless communications signals from signal emitting devices in a spectrum associated with wireless communications; and wherein the apparatus is operable to automatically analyze the measured data to identify at least one signal emitting device in near real time from attempted detection and identification of the at least one signal emitting device. The characteristics of signals and measured data from the signal emitting devices include frequency, power, bandwidth, duration, modulation, and combinations thereof. The present invention systems including at least one apparatus, wherein the at least one apparatus is operable for network-based communication with at least one server computer including a database, and/or with at least one other apparatus, but does not require a connection to the at least one server computer to be operable for identifying signal emitting devices; wherein each of the apparatus is operable for identifying signal emitting devices including: a housing, at least one processor and memory, and sensors constructed and configured for sensing and measuring wireless communications signals from signal emitting devices in a spectrum associated with wireless communications; and wherein the apparatus is operable to automatically analyze the measured data to identify at least one signal emitting device in near real time from attempted detection and identification of the at least one signal emitting device. Identifying Open Space in a Wireless Communication Spectrum. The present invention provides for systems, methods, and apparatus solutions for automatically identifying open space, including open space in the white space of a wireless communication spectrum. Importantly, the present invention identifies the open space as the space that is unused and/or seldomly used (and identifies the owner of the licenses for the seldomly used space, if applicable), including unlicensed spectrum, white space, guard bands, and combinations thereof. Method steps of the present invention include: automatically obtaining a listing or report of all frequencies in the frequency range; plotting a line and/or graph chart showing power and bandwidth activity; setting frequencies based on a frequency step and/or resolution so that only user-defined frequencies are plotted; generating a .csv or .pdf file showing the average and/or aggregated values of power, bandwidth and frequency for each derived frequency step; and showing an activity report over time, over day vs. night, over frequency bands if more than one, in white space if requested, in ISM space if requested; and if frequency space seldomly used in area list frequencies and license holders. Additional steps include: scanning the frequency span, wherein a default scan includes a frequency span between about 54 MHz and about 804 MHz; an ISM scan between about 900 MHz and about 2.5 GHz; an ISM scan between about 5 GHz and about 5.8 GHz; and/or a frequency range based upon inputs provided by a user. Also, method steps include scanning for an allotted amount of time between a minimum of about 15 minutes up to about 30 days; preferably scanning for allotted times selected from the following: a minimum of about 15 minutes; about 30 minutes; about 1 hour increments; about 5 hour increments; about 10 hour increments; about 24 hours; about 1 day; and about up to 30 days; and combinations thereof. In preferred embodiments, if the apparatus is configured for automatically scanning for more than about 15 minutes, then the apparatus is preferably set for updating results, including updating graphs and/or reports for an approximately equal amount of time (e.g., every 15 minutes). The systems, methods, and apparatus also provide for automatically calculating a percent activity on each frequency band. Automated Reports and Visualization of Analytics. Various reports for describing and illustrating with visualization the data and analysis of the device, system and method results from spectrum management activities include at least reports on power usage, RF survey, and variance. The systems, methods, and devices of the various embodiments enable spectrum management by identifying, classifying, and cataloging signals of interest based on radio frequency measurements. In an embodiment, signals and the parameters of the signals may be identified and indications of available frequencies may be presented to a user. In another embodiment, the protocols of signals may also be identified. In a further embodiment, the modulation of signals, devices or device types emitting signals, data types carried by the signals, and estimated signal origins may be identified. Referring again to the drawings,FIG.17is a schematic diagram illustrating an embodiment for scanning and finding open space. A plurality of nodes are in wireless or wired communication with a software defined radio, which receives information concerning open channels following real-time scanning and access to external database frequency information. FIG.18is a diagram of an embodiment of the invention wherein software defined radio nodes are in wireless or wired communication with a master transmitter and device sensing master. FIG.19is a process flow diagram of an embodiment method of temporally dividing up data into intervals for power usage analysis and comparison. The data intervals are initially set to seconds, minutes, hours, days and weeks, but can be adjusted to account for varying time periods (e.g., if an overall interval of data is only a week, the data interval divisions would not be weeks). In one embodiment, the interval slicing of data is used to produce power variance information and reports. FIG.20is a flow diagram illustrating an embodiment wherein frequency to license matching occurs. In such an embodiment the center frequency and bandwidth criteria can be checked against a database to check for a license match. Both licensed and unlicensed bands can be checked against the frequencies, and, if necessary, non-correlating factors can be marked when a frequency is uncorrelated. FIG.21is a flow diagram illustrating an embodiment method for reporting power usage information, including locational data, data broken down by time intervals, frequency and power usage information per band, average power distribution, propagation models, atmospheric factors, which is capable of being represented graphical, quantitatively, qualitatively, and overlaid onto a geographic or topographic map. FIG.22is a flow diagram illustrating an embodiment method for creating frequency arrays. For each initialization, an embodiment of the invention will determine a center frequency, bandwidth, peak power, noise floor level, resolution bandwidth, power and date/time. Start and end frequencies are calculated using the bandwidth and center frequency and like frequencies are aggregated and sorted in order to produce a set of frequency arrays matching power measurements captured in each band. FIG.23is a flow diagram illustrating an embodiment method for reframe and aggregating power when producing frequency arrays. FIG.24is a flow diagram illustrating an embodiment method of reporting license expirations by accessing static or FCC databases. FIG.25is a flow diagram illustrating an embodiment method of reporting frequency power use in graphical, chart, or report format, with the option of adding frequencies from FCC or other databases. FIG.26is a flow diagram illustrating an embodiment method of connecting devices. After acquiring a GPS location, static and FCC databases are accessed to update license information, if available. A frequency scan will find open spaces and detect interferences and/or collisions. Based on the master device ID, set a random generated token to select channel form available channel model and continually transmit ID channel token. If node device reads ID, it will set itself to channel based on token and device will connect to master device. Master device will then set frequency and bandwidth channel. For each device connected to master, a frequency, bandwidth, and time slot in which to transmit is set. In one embodiment, these steps can be repeated until the max number of devices is connected. As new devices are connected, the device list is updated with channel model and the device is set as active. Disconnected devices are set as inactive. If collision occurs, update channel model and get new token channel. Active scans will search for new or lost devices and update devices list, channel model, and status accordingly. Channel model IDs are actively sent out for new or lost devices. FIG.27is a flow diagram illustrating an embodiment method of addressing collisions. FIG.28is a schematic diagram of an embodiment of the invention illustrating a virtualized computing network and a plurality of distributed devices.FIG.28is a schematic diagram of one embodiment of the present invention, illustrating components of a cloud-based computing system and network for distributed communication therewith by mobile communication devices.FIG.28illustrates an exemplary virtualized computing system for embodiments of the present invention loyalty and rewards platform. As illustrated inFIG.28, a basic schematic of some of the key components of a virtualized computing (or cloud-based) system according to the present invention is shown. The system2800comprises at least one remote server computer2810with a processing unit2811and memory. The server2810is constructed, configured and coupled to enable communication over a network2850. The server provides for user interconnection with the server over the network with the at least one apparatus as described hereinabove2840positioned remotely from the server. Apparatus2840includes a memory2846, a CPU2844, an operating system2847, a bus2842, an input/output module2848, and an output or display2849. Furthermore, the system is operable for a multiplicity of devices or apparatus embodiments2860,2870for example, in a client/server architecture, as shown, each having outputs or displays2869and2979, respectively. Alternatively, interconnection through the network2850using the at least one device or apparatus for measuring signal emitting devices, each of the at least one apparatus is operable for network-based communication. Also, alternative architectures may be used instead of the client/server architecture. For example, a computer communications network, or other suitable architecture may be used. The network2850may be the Internet, an intranet, or any other network suitable for searching, obtaining, and/or using information and/or communications. The system of the present invention further includes an operating system2812installed and running on the at least one remote server2810, enabling the server2810to communicate through network2850with the remote, distributed devices or apparatus embodiments as described hereinabove, the server2810having a memory2820. The operating system may be any operating system known in the art that is suitable for network communication. FIG.29shows a schematic diagram illustrating aspects of the systems, methods and apparatus according to the present invention. Each node includes an apparatus or device unit, referenced in theFIG.29as “SigSet Device A”, “SigSet Device B”, “SigSet Device C”, and through “SigSet Device N” that are constructed and configured for selective exchange, both transmitting and receiving information over a network connection, either wired or wireless communications, with the master SigDB or database at a remote server location from the units. FIG.30is a schematic diagram of an embodiment of the invention illustrating a computer system, generally described as3800, having a network3810and a plurality of computing devices3820,3830,3840. In one embodiment of the invention, the computer system3800includes a cloud-based network3810for distributed communication via the network's wireless communication antenna3812and processing by a plurality of mobile communication computing devices3830. In another embodiment of the invention, the computer system3800is a virtualized computing system capable of executing any or all aspects of software and/or application components presented herein on the computing devices3820,3830,3840. In certain aspects, the computer system3800may be implemented using hardware or a combination of software and hardware, either in a dedicated computing device, or integrated into another entity, or distributed across multiple entities or computing devices. By way of example, and not limitation, the computing devices3820,3830,3840are intended to represent various forms of digital devices and mobile devices, such as a server, blade server, mainframe, mobile phone, a personal digital assistant (PDA), a smart phone, a desktop computer, a netbook computer, a tablet computer, a workstation, a laptop, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the invention described and/or claimed in this document. In one embodiment, the computing device3820includes components such as a processor3860, a system memory3862having a random access memory (RAM)3864and a read-only memory (ROM)3866, and a system bus3868that couples the memory3862to the processor3860. In another embodiment, the computing device3830may additionally include components such as a storage device3890for storing the operating system3892and one or more application programs3894, a network interface unit3896, and/or an input/output controller3898. Each of the components may be coupled to each other through at least one bus3868. The input/output controller3898may receive and process input from, or provide output to, a number of other devices3899, including, but not limited to, alphanumeric input devices, mice, electronic styluses, display units, touch screens, signal generation devices (e.g., speakers) or printers. By way of example, and not limitation, the processor3860may be a general-purpose microprocessor (e.g., a central processing unit (CPU)), a graphics processing unit (GPU), a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated or transistor logic, discrete hardware components, or any other suitable entity or combinations thereof that can perform calculations, process instructions for execution, and/or other manipulations of information. In another implementation, shown inFIG.30, a computing device3840may use multiple processors3860and/or multiple buses3868, as appropriate, along with multiple memories3862of multiple types (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core). Also, multiple computing devices may be connected, with each device providing portions of the necessary operations (e.g., a server bank, a group of blade servers, or a multi-processor system). Alternatively, some steps or methods may be performed by circuitry that is specific to a given function. According to various embodiments, the computer system3800may operate in a networked environment using logical connections to local and/or remote computing devices3820,3830,3840through a network3810. A computing device3820may connect to a network3810through a network interface unit3896connected to the bus3868. Computing devices may communicate communication media through wired networks, direct-wired connections or wirelessly such as acoustic, RF or infrared through a wireless communication antenna3897in communication with the network's wireless communication antenna3812and the network interface unit3896, which may include digital signal processing circuitry when necessary. The network interface unit3896may provide for communications under various modes or protocols. In one or more exemplary aspects, the instructions may be implemented in hardware, software, firmware, or any combinations thereof. A computer readable medium may provide volatile or non-volatile storage for one or more sets of instructions, such as operating systems, data structures, program modules, applications or other data embodying any one or more of the methodologies or functions described herein. The computer readable medium may include the memory3862, the processor3860, and/or the storage device3890and may be a single medium or multiple media (e.g., a centralized or distributed computer system) that store the one or more sets of instructions3900. Non-transitory computer readable media includes all computer readable media, with the sole exception being a transitory, propagating signal per se. The instructions3900may further be transmitted or received over the network3810via the network interface unit3896as communication media, which may include a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics changed or set in a manner as to encode information in the signal. Storage devices3890and memory3862include, but are not limited to, volatile and non-volatile media such as cache, RAM, ROM, EPROM, EEPROM, FLASH memory, or other solid state memory technology; discs (e.g., digital versatile discs (DVD), HD-DVD, BLU-RAY, compact disc (CD), or CD-ROM) or other optical storage; magnetic cassettes, magnetic tape, magnetic disk storage, floppy disks, or other magnetic storage devices; or any other medium that can be used to store the computer readable instructions and which can be accessed by the computer system3800. It is also contemplated that the computer system3800may not include all of the components shown inFIG.30, may include other components that are not explicitly shown inFIG.30, or may utilize an architecture completely different than that shown inFIG.30. The various illustrative logical blocks, modules, elements, circuits, and algorithms described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application (e.g., arranged in a different order or partitioned in a different way), but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. The present invention further provides for aggregating data from at least two apparatus units by at least one server computer and storing the aggregated data in a database and/or in at least one database in a cloud-based computing environment or virtualized computing environment, as illustrated inFIG.28orFIG.30. The present invention further provides for remote access to the aggregated data and/or data from any of the at least one apparatus unit, by distributed remote user(s) from corresponding distributed remote device(s), such as by way of example and not limitation, desktop computers, laptop computers, tablet computers, mobile computers with wireless communication operations, smartphones, mobile communications devices, and combinations thereof. The remote access to data is provided by software applications operable on computers directly (as a “desktop” application) and/or as a web service that allows user interface to the data through a secure, network-based website access. In other embodiments of the present invention, which include the base invention described hereinabove, and further including the functions of machine “learning”, modulation detection, automatic signal detection, FFT replay, and combinations thereof. Automatic modulation detection and machine “learning” includes automatic signal variance determination by at least one of the following methods: date and time from location set, and remote access to the apparatus unit to determine variance from different locations and times, in addition to the descriptions of automatic signal detection and threshold determination and setting. Environments vary, especially where there are many signals, noise, interference, variance, etc., so tracking signals automatically is difficult, and a longstanding, unmet need in the prior art. The present invention provides for automatic signal detection using a sample of measured and sensed data associated with signals over time using the at least one apparatus unit of the present invention to provide an automatically adjustable and adaptable system. For each spectrum scan, the data is automatically subdivided into “windows”, which are sections or groups of data within a frequency space. Real-time processing of the measured and sensed data on the apparatus unit(s) or devices combined with the windowing effect provides for automatic comparison of signal versus noise within the window to provide for noise approximation, wherein both signals and noise are measured and sensed, recorded, analyzed compared with historical data to identify and output signals in a high noise environment. It is adaptive and iterative to include focused windows and changes in the window or frequency ranges grouped. The resulting values for all data are squared in the analysis, which results in signals identified easily by the apparatus unit as having significantly larger power values compared with noise; additional analytics provide for selection of the highest power value signals and review of the original data corresponding thereto. Thus, the at least one apparatus automatically determines and identifies signals compared to noise in the RF spectrum. The apparatus unit or device of the present invention further includes a temporal anomaly detector (or “learning channel”). The first screen shot illustrated inFIG.31shows the blank screen, the second screen shot illustrated inFIG.32shows several channels that the system has “learned”. This table can be saved to disk as a spreadsheet and reused on subsequent surveys at the same location. The third screen shot shown inFIG.33displays the results when run with the “Enable OOB Signals” button enabled. In this context OOB means “Out Of Band” or rogue or previously unidentified signals. Once a baseline set of signals has been learned by the system, it can be used with automatic signal detection to clearly show new, unknown signals that were not present when the initial learning was done, as shown inFIG.34. In a similar capacity, the user can load a spreadsheet that they have constructed on their own to describe the channels that they expect to see in a given environment, as illustrated inFIG.34. When run with OOB detection, the screen shot shows the detection of signals that were not in the user configuration. These rogue signals could be a possible source of interference, and automatic detection of them can greatly assist the job of an RF Manager. FIGS.31-34illustrate the functions and features of the present invention for automatic or machine “learning” as described hereinabove. Automatic signal detection of the present invention eliminates the need for a manual setting of a power threshold line or bar, as with the prior art. The present invention does not require a manual setting of power threshold bar or flat line to identify signals instead of noise, instead it uses information on the hardware parameters of the apparatus unit or device, environment parameters, and terrain data to derive the threshold bar or flatline, which are stored in the static database of the apparatus unit or device. Thus, the apparatus unit or device may be activated and left unattended to collect data continuously without the need for manual interaction with the device directly. Furthermore, the present invention allows remote viewing of live data in real time on a display of a computer or communications device in network-based connection but remotely positioned from the apparatus unit or device, and/or remote access to device settings, controls, data, and combinations thereof. The network-based communication may be selected from mobile, satellite, Ethernet, and functional equivalents or improvements with security including firewalls, encryption of data, and combinations thereof. Regarding FFT replay, the present invention apparatus units are operable to replay data and to review and/or replay data saved based upon an unknown event, such as for example and not limitation, reported alarms and/or unique events, wherein the FFT replay is operable to replay stored sensed and measured data to the section of data nearest the reported alarm and/or unique event. By contrast, prior art provides for recording signals on RF spectrum measurement devices, which transmit or send the raw data to an external computer for analysis, so then it is impossible to replay or review specific sections of data, as they are not searchable, tagged, or otherwise sectioned into subgroups of data or stored on the device. Automatic Signal Detection The previous approach to ASD was to subtract a calibration vector from each FFT sample set (de-bias), then square each resulting value and look for concentrations of energy that would differentiate a signal from random baseline noise. The advantages of this approach are that, by the use of the calibration vector (which was created using the receiver itself with no antenna), we are able to closely track variations in the baseline noise that are due to the characteristics of the receiver, front end filtering, attenuation and A/D converter hardware. On most modern equipment, the designers take steps to keep the overall response flat, but there are those that do not.FIG.35is an example of a receiver that has marked variations on baseline behavior across a wide spectrum (9 MHz-6 GHz). The drawbacks to this approach are: 1) It requires the use of several “tuning” variables which often require the user to adjust and fiddle with in order to achieve good signal recognition. A fully automatic signal detection system should be able to choose values for these parameters without the intervention of an operator. 2) It does not take into account variations in the baseline noise floor that are introduced by RF energy in a live environment. Since these variations were not present during calibration, they are not part of the calibration vector and cannot be “canceled out” during the de-bias phase. Instead they remain during the square and detect phase, often being mistakenly classified as signal. An example of this isFIG.36, a normal spectrum from 700 MHz to 790 MHz. The threshold line (baby blue) indicates the level where we would differentiate signal from noise.FIG.37illustrates the same spectrum at a different time where an immensely powerful signal at about 785 MHz has caused undulations in the noise floor all the way down to 755 MHz. It is clear to see by the placement of the threshold line large blocks of the noise are now going to be recognized as signal. Not only are the 4 narrow band signals now going to be mistakenly seen as one large signal, there is an additional lump of noise around 760 MHz that represents no signal at all, but will be classified as such. In order to solve these two problems, and provide a fully automatic signal detection system, a new approach has been taken to prepare the calibration vector. The existing square and detect algorithm works well if the data are de-biased properly with a cleverly chosen calibration vector, it's just that the way we were creating the calibration vector was not sufficient. FIG.38illustrates a spectrum from 1.9 GHz to 2.0 GHz, along with some additional lines that indicate the functions of the new algorithm. Line 1 (brown) at the bottom displays the existing calibration vector created by running the receiver with no antenna. It is clear to see that, if used as is, it is too low to be used to de-bias the data shown as line 2 (dark blue). Also, much of the elevations in noise floor will wind up being part of the signals that are detected. In order to compensate for this, the user was given a control (called “Bias”) that allowed them to raise or lower the calibration vector to hopefully achieve a more reasonable result. But, as illustrated inFIG.37, no adjustment will suffice when the noise floor has been distorted due to the injection of large amounts of energy. So, rather than attempt to make the calibration vector fit the data, the new approach examines the data itself in an attempt to use parts of it as the correction vector. This is illustrated by the light purple and baby blue lines in theFIG.38. Line 3 (light purple) inFIG.38is the result of using a 60-sample smoothing filter to average the raw data. It clearly follows the data, but it removes the “jumpiness”. This can be better seen inFIG.39which is a close-up view of the first part of the overall spectrum. The difference between the smoothed data shown as line 3 (light purple) and the original data shown as line 2 (dark blue) is displayed clearly. The new Gradient Detection algorithm is applied to the smoothed data to detect locations where the slope of the line changes quickly. In places where the slope changes quickly in a positive direction, the algorithm marks the start of a signal. On the other side of the signal the gradient again changes quickly to become more horizontal. At that point the algorithm determines it is the end of a signal. A second smoothing pass is performed on the smoothed data, but this time, those values that fall between the proposed start and end of signal are left out of the average. The result is line 4 (baby blue) inFIGS.38and39, which is then used as the new calibration vector. This new calibration vector shown as line 4 (baby blue) is then used to de-bias the raw data which is then passed to the existing square and detect ASD algorithm. One of the other user-tunable parameters in the existing ASD system was called “Sensitivity”. This was a parameter that essentially set a threshold of energy, above which each FFT bin in a block of bins averaged together must exceed in order for that block of bins to be considered a signal. In this way, rather than a single horizontal line to divide signal from noise, each signal can be evaluated individually, based on its average power. The effect of setting this value too low was that tiny fluctuations of energy that are actually noise would sometimes appear to be signals. Setting the value too high would result in the algorithm missing a signal. In order to automatically choose a value for this parameter, the new system uses a “Quality of Service” feedback from the Event Compositor, a module that processes the real-time events from the ASD system and writes signal observations into a database. When the sensitivity value is too low, the random bits of energy that ASD mistakenly sees as signal are very transient. This is due to the random nature of noise. The Event Compositor has a parameter called a “Pre-Recognition Delay” that sets the minimum number of consecutive scans that it must see a signal in order for it to be considered a candidate for a signal observation database entry (in order to catch large fast signals, an exception is made for large transients that are either high in peak power, or in bandwidth). Since the random fluctuations seldom persist for more than 1 or 2 sweeps, the Event Compositor ignores them, essentially filtering them out. If there are a large number of these transients, the Event Compositor provides feedback to the ASD module to inform it that its sensitivity is too low. Likewise, if there are no transients at all, the feedback indicates the sensitivity is too high. Eventually, the system arrives at an optimal setting for the sensitivity parameter. The result is a fully automated signal detection system that requires no user intervention or adjustment. The black brackets at the top ofFIG.38illustrate the signals recognized by the system, clearly indicating its accuracy. Because the system relies heavily upon averaging, a new algorithm was created that performs an N sample average in fixed time; i.e. regardless of the width of the average, N, each bin requires 1 addition, 1 subtraction, and 1 division. A simpler algorithm would require N additions and 1 division per bin of data. A snippet of the code is probably the best description: public double [ ] smoothingFilter( double [ ] dataSet, int filterSize ) {double [ ] resultSet = new double[ dataSet.length ];double temp = 0.0;int i=0;int halfSize = filterSize/2;for( i=0 ; i < filterSize ; i++ ) {temp += dataSet[i];// load accumulator with the first N/2 values.if( i < halfSize )resultSet[i] = dataSet[i];}for( i=halfSize ; i < (dataSet.length − halfSize) ; i++ ) {resultSet[i] = temp / filterSize; // Compute the average and storeittemp −= dataSet[ i−halfSize ]; // take out the oldest valuetemp += dataSet[ i+halfSize ]; // add in the newest value}while( i < dataSet.length ) {resultSet[i] = dataSet[i];i++;}return( resultSet );} Automatic Signal Detection (ASD) with Temporal Feature Extraction (TFE) The system in the present invention uses statistical learning techniques to observe and learn an RF environment over time and identify temporal features of the RF environment (e.g., signals) during a learning period. A knowledge map is formed based on learning data from a learning period. Real-time signal events are detected by an ASD system and scrubbed against the knowledge map to determine if the real-time signal events are typical and expected for the environment, or if there is any event not typical nor expected. The knowledge map consists of an array of normal distributions, where each distribution column is for each frequency bin of the FFT result set provided by a software defined radio (SDR). Each vertical column corresponds to a bell-shaped curve for that frequency. Each pixel represents a count of how many times that frequency was seen, detected, or observed at that power level. A learning routine takes power levels of each frequency bin, uses the power levels as an index into each distribution column corresponding to each frequency bin, and increments the counter in a location corresponding to a power level. FIG.40illustrates a knowledge map obtained by a TFE process. The top window shows the result of real-time spectrum sweep of an environment. The bottom window shows a knowledge map, which color codes the values in each column (normal distribution) based on how often the power level of that frequency (column) has been at a particular level. The TFE function monitors its operation and produces a “settled percent.” The settled percent is the percentage of the values of the incoming FFT result set that the system has seen, detected, or observed before. In this way, the system can know if it is ready to interpret the statistical data that it has obtained. Once it reaches a point where most of the FFT values have been seen, detected, or observed before (99.95% or better), it can then perform an interpretation operation. FIG.41illustrates an interpretation operation based on a knowledge map. During the interpretation operation, the system extracts valuable signal identification from the knowledge map. Some statistical quantities are identified. For each column, the power level at which a frequency is seen, detected, or observed the most is determined (peak of the distribution curve), which is represented by line a (red) inFIG.41. A desired percentage of power level values is located between the high and low boundaries of the power levels (shoulders of the curve), which are represented by lines b (white) inFIG.41. The desired percentage is adjustable. InFIG.41, the desired percentage is set at 42% based on the learning data. In one embodiment, a statistical method is used to obtain a desirable percentage that provides the highest degree of “smoothness” - - - lowest deviation from column to column. Then, a profile is drawn based on the learning data, which represents the highest power level at which each frequency has been seen, detected, or observed during learning. InFIG.41, the profile is represented by line c (green). Gradient detection is then applied to the profile to identify areas of transition. An algorithm continues to accumulate a gradient value as long as the “step” from the previous cell to this cell is always non-zero and the same direction. When it arrives at a zero or different direction step, it evaluates the accumulated difference to see if it is significant, and if so, considers it a gradient. A transition is identified by a continuous change (from left to right) that exceeds the average range between the high and low boundaries of power levels shown as lines b (white) inFIG.41. Positive and negative gradients are matched, and the resulting interval is identified as a signal.FIG.42shows the identification of signals, which are represented by the black brackets above the knowledge display. Similar toFIG.41, the knowledge map inFIG.42color codes (e.g., black, dark blue, baby blue) the values in each column (normal distribution) based on how often the power level of that frequency (column) has been at a particular level. Lines b (white) represent the high and low boundaries of a desirable percentage of power level. Line c (green) represents a profile of the RF environment comprising the highest power level at which each frequency has been seen during learning. FIG.43shows more details of the narrow band signals at the left of the spectrum around 400 MHz inFIG.42. Similar toFIG.41, the knowledge map inFIG.43color codes (e.g., black, dark blue, baby blue) the values in each column (normal distribution) based on how often the power level of that frequency (column) has been at a particular level. Lines b (white) represent the high and low boundaries of a desirable percentage of power level. Line c (green) represents a profile of the RF environment comprising the highest power level at which each frequency has been seen during learning. The red cursor at 410.365 MHz inFIG.43points to a narrow band signal. The real-time spectrum sweep on the top window shows the narrow band signal, and the TFE process identifies the narrow band signal as well. To a prior art receiver, the narrow band signal hidden within a wideband signal is not distinguishable or detectable. The systems and methods and devices of the present invention are operable to scan a wideband with high resolution or high definition to identify channel divisions within a wideband, and identify narrowband signals hidden within the wideband signal, which are not a part of the wideband signal itself, i.e., the narrow band signals are not part of the bundled channels within the wideband signal. FIG.44shows more details of the two wide band signals around 750 MHz and a similar signal starting at 779 MHz. Similar toFIG.41, the knowledge map inFIG.44color codes (e.g., black, dark blue, baby blue) the values in each column (normal distribution) based on how often the power level of that frequency (column) has been at a particular level. Lines b (white) represent the high and low boundaries of a desirable percentage of power level. Line c (green) represents a profile of the RF environment comprising the highest power level at which each frequency has been seen during learning. The present invention detects the most prominent parts of the signal starting at 779 MHz. The transmitters of these two wide band signals are actually in the distance, and normal signal detectors, which usually have a fixed threshold, are not able to pick up these two wide band signals but only see them as static noises. Because the TFE system in the present invention uses an aggregation of signal data over time, it can identify these signals and fine tune the ASD sensitivity of individual segments. Thus, the system in the present invention is able to detect signals that normal radio gear cannot. ASD in the present invention, is enhanced by the knowledge obtained by TFE and is now able to detect and record these signals where gradient detection alone would not have seen, detected, or observed them. The threshold bar in the present invention is not fixed, but changeable. Also, at the red cursor inFIG.44is a narrow band signal in the distance that normally would not be detected because of its low power at the point of observation. But the present invention interprets knowledge gained over time and is able to identify that signal. FIG.45illustrates the operation of the ASD in the present invention. Line A (green) shows the spectrum data between 720 MHz and 791 MHz. 1st and 2nd derivatives of the power levels are calculated inside spectrum on a cell by cell basis, displayed as the overlapping line B (blue) and line C (red) at the top. The algorithm then picks the most prominent derivatives and performs a squaring function on them as displayed by line D (red) trace. The software then matches positive and negative gradients, to identify the edges of the signals, which are represented by the brackets on the top. Two wideband signals are identified, which may be CDMA, LTE, or other communication protocol used by mobile phones. Line E (red) at the bottom is a baseline established by averaging the spectrum and removing areas identified by the gradients. At the two wideband signals, line E (red) is flat. By subtracting the baseline from the real spectrum data, groups of cells with average power above baseline are identified, and the averaging algorithm is run against those areas to apply the sensitivity measurement. The ASD system has the ability to distinguish between large eruptions of energy that increase the baseline noise and the narrow band signals that could normally be swamped by the additional energy because it generates its baseline from the spectrum itself and looks for relative gradients rather than absolute power levels. This baseline is then subtracted from the original spectrum data, revealing the signals, as displayed by the brackets at the top of the screen. Note that the narrow-band signals are still being detected (tiny brackets at the top that look more like dots) even though there is a hump of noise super-imposed on them. TFE is a learning process that augments the ASD feature in the present invention. The ASD system enhanced with TFE function in the present invention can automatically tune parameters based on a segmented basis, the sensitivity within an area is changeable. The TFE process accumulates small differences over time and signals become more and more apparent. In one embodiment, the TFE takes 40 samples per second over a 5-minute interval. The ASD system in the present invention is capable of distinguishing signals based on gradients from a complex and moving noise floor without a fixed threshold bar when collecting data from an environment. The ASD system with TFE function in the present invention is unmanned and water resistant. It runs automatically 24/7, even submerged in water. The TFE is also capable of detecting interferences and intrusions. In the normal environment, the TFE settles, interprets and identifies signals. Because it has a statistical knowledge of the RF landscape, it can tell the difference between a low power, wide band signal that it normally sees and a new higher power narrow band signal that may be an intruder. This is because it “scrubs” each of the FFT bins of each event that the ASD system detects against its knowledge base. When it detects that a particular group of bins in a signal from ASD falls outside the statistical range that those frequencies normally are observed, the system can raise an anomaly report. The TFE is capable of learning new knowledge, which is never seen, detected, or observed before, from the signals identified by a normal detector. In one embodiment, a narrow band signal (e.g., a pit crew to car wireless signal) impinges on an LTE wideband signal, the narrow band signal may be right beside the wideband signal, or drift in and out of the wideband signal. On display, it just looks like an LTE wideband signal. For example, a narrow band signal with a bandwidth of 12 kHz or 25-30 kHz in a wideband signal with a bandwidth of 5 MHz over a 6 GHz spectrum just looks like a spike buried in the middle. But, because signals are characterized in real time against learned knowledge, the proposed ASD system with TFE function is able to pick out narrow band intruder immediately. The present invention is able to detect a narrow band signal with a bandwidth from 1-2 kHz to 60 kHz inside a wideband signal (e.g., with a bandwidth of 5 MHz) across a 6 GHz spectrum. InFIGS.40-45, the frequency resolution is 19.5 kHz, and a narrow band signal with a bandwidth of 2-3 kHz can be detected. The frequency resolution is based on the setting of the FFT result bin size. Statistical learning techniques are used for extracting temporal feature, creating a statistical knowledge map of what each frequency is and determining variations and thresholds and etc. The ASD system with TFE function in the present invention is capable of identifying, demodulating and decoding signals, both wideband and narrowband with high energy. If a narrowband signal is close to the end of wideband LTE signal, the wideband LTE signal is distorted at the edge. If multiple narrowband signals are within a wideband signal, the top edge of the wideband signal is ragged as the narrow band signal is hidden within the wide band signal. If one narrow band signal is in the middle of a wideband signal, the narrow band signal is usually interpreted as a cell within the wideband signal. However, the ASD system with TFE function in the present invention learns power levels in a spectrum section over time, and is able to recognize the narrow band signal immediately. The present invention is operable to log the result, display on a channel screen, notify operator and send alarms, etc. The present invention auto records spectrum, but does not record all the time. When a problem is identified, relevant information is auto recorded in high definition. The ASD system with TFE in the present invention is used for spectrum management. The system in the present invention is set up in a normal environment and starts learning and stores at least one learning map in it. The learning function of the ASD system in the present invention can be enabled and disabled. When the ASD system is exposed to a stable environment and has learned what is normal in the environment, it will stop its learning process. The environment is periodically reevaluated. The learning map is updated at a predetermined timeframe. After a problem is detected, the learning map will also be updated. The ASD system in the present invention can be deployed in stadiums, ports, airports, or on borders. In one embodiment, the ASD system learns and stores the knowledge in that environment. In another embodiment, the ASD system downloads prior knowledge and immediately displays it. In another embodiment, an ASD device can learn from other ASD devices globally. In operation, the ASD system then collects real time data and compares to the learning map stored for signal identification. Signals identified by the ASD system with TFE function may be determined to be an error by an operator. In that situation, an operator can manually edit or erase the error, essentially “coaching” the learning system. The systems and devices in the present invention create a channel plan based on user input, or external databases, and look for signals that are not there. Temporal Feature Extraction not only can define a channel plan based on what it learns from the environment, but it also “scrubs” each spectrum pass against the knowledge it has learned. This allows it to not only identify signals that violate a prescribed channel plan, but it can also discern the difference between a current signal, and the signal that it has previously seen, detected, or observed in that frequency location. If there is a narrow band interference signal where there typically is a wide band signal, the system will identify it as an anomaly because it does not match the pattern of what is usually in that space. The device in the present invention is designed to be autonomous. It learns from the environment, and, without operator intervention, can detect anomalous signals that either were not there before, or have changed in power or bandwidth. Once detected, the device can send alerts by text or email and begin high resolution spectrum capture, or IQ capture of the signal of interest. FIG.40illustrates an environment in which the device is learning. There are some obvious signals, but there is also a very low level wide band signal between 746 MHz and 755 MHz. Typical threshold-oriented systems would not catch this. But, the TFE system takes a broader view over time. The signal does not have to be there all the time or be pronounced to be detected by the system. Each time it appears in the spectrum serves to reinforce the impression on the learning fabric. These impressions are then interpreted and characterized as signals. FIG.43shows the knowledge map that the device has acquired during its learning system, and shows brackets above what it has determined are signals. Note that the device has determined these signals on its own without any user intervention, or any input from any databases. It is a simple thing to then further categorize the signals by matching against databases, but what sets the device in the present invention apart is that, like its human counterpart, it has the ability to draw its own conclusions based on what it has seen, detected, or observed. FIG.44shows a signal identified by the device in the present invention between 746 MHz and 755 MHz with low power levels. It is clear to see that, although the signal is barely distinguishable from the background noise, TFE clearly has identified its edges. Over to the far right is a similar signal that is further away so that it only presents traces of itself. But again, because the device in the present invention is trained to distinguish random and coherent energy patterns over time, it can clearly pick out the pattern of a signal. Just to the left of that faint signal was a transient narrow band signal at 777.653 MHz. This signal is only present for a brief period of time during the training, typically 0.5-0.7 seconds each instance, separated by minutes of silence, yet the device does not miss it, remembers those instances and categorizes them as a narrow band signal. The identification and classification algorithms that the system uses to identify Temporal Features are optimized to be used in real time. Notice that, even though only fragments of the low level wide band signal are detected on each sweep, the system still matches them with the signal that it had identified during its learning phase. Also as the system is running, it is scrubbing each spectral sweep against its knowledge map. When it finds coherent bundles of energy that are either in places that are usually quiet, or have higher power or bandwidth than it has seen, detected, or observed before, it can automatically send up a red flag. Since the system is doing this in Real Time, it has critical relevance to those in harm's way—the first responder, or the war fighter who absolutely must have clear channels of communication or instant situational awareness of imminent threats. It's one thing to geolocate a signal that the user has identified. It's an entirely different dimension when the system can identify the signal on its own before the user even realizes it's there. Because the device in the present invention can pick out these signals with a sensitivity that is far superior to a simple threshold system, the threat does not have to present an obvious presence to be detected and alerted. Devices in prior art merely make it easy for a person to analyze spectral data, both in real time and historically, locally or remotely. But the device in the present invention operates as an extension of the person, performing the learning and analysis on its own, and even finding things that a human typically may miss. The device in the present invention can easily capture signal identifications, match them to databases, store and upload historical data. Moreover, the device has intelligence and the ability to be more than a simple data storage and retrieval device. The device is a watchful eye in an RF environment, and a partner to an operator who is trying to manage, analyze, understand and operate in the RF environment. Geolocation The prior art is dependent upon a synchronized receiver for power, phase, frequency, angle, and time of arrival, and an accurate clock for timing, and significantly, requires three devices to be used, wherein all are synchronized and include directional antennae to identify a signal with the highest power. Advantageously, the present invention does not require synchronization of receivers in a multiplicity of devices to provide geolocation of at least one apparatus unit or device, thereby reducing cost and improving functionality of each of the at least one apparatus in the systems described hereinabove for the present invention. Also, the present invention provides for larger frequency range analysis, and provides database(s) for capturing events, patterns, times, power, phase, frequency, angle, and combinations for the at least one signal of interest in the RF spectrum. The present invention provides for better measurements and data of signal(s) with respect to time, frequency with respect to time, power with respect to time, and combinations thereof. In preferred embodiments of the at least one apparatus unit of the present invention, geolocation is provided automatically by the apparatus unit using at least one anchor point embedded within the system, by power measurements and transmission that provide for “known” environments of data. The known environments of data include measurements from the at least one anchorpoint that characterize the RF receiver of the apparatus unit or device. The known environments of data include a database including information from the FCC database and/or user-defined database, wherein the information from the FCC database includes at least maximum power based upon frequency, protocol, device type, and combinations thereof. With the geolocation function of the present invention, there is no requirement to synchronize receivers as with the prior art; the at least one anchorpoint and location of an apparatus unit provide the required information to automatically adjust to a first anchorpoint or to a second anchorpoint in the case of at least two anchorpoints, if the second anchorpoint is easier to adopt. The known environment data provide for expected spectrum and signal behavior as the reference point for the geolocation. Each apparatus unit or device includes at least one receiver for receiving RF spectrum and location information as described hereinabove. In the case of one receiver, it is operable with and switchable between antennae for receiving RF spectrum data and location data; in the case of two receivers, preferably each of the two receivers are housed within the apparatus unit or device. A frequency lock loop is used to determine if a signal is moving, by determining if there is a Doppler change for signals detected. Location determination for geolocation is provided by determining a point (x, y) or Lat Lon from the at least three anchor locations (x1, y1); (x2, y2); (x3, y3) and signal measurements at either of the node or anchors. Signal measurements provide a system of non-linear equations that must be solved for (x, y) mathematically; and the measurements provide a set of geometric shapes which intersect at the node location for providing determination of the node. For trilateration methods for providing observations to distances the following methods are used: RSS=d=d010(P0-Pr10n)wherein do is the reference distance derived from the reference transmitter and signal characteristics (e.g., frequency, power, duration, bandwidth, etc.); Po is the power received at the reference distance; Pr is the observed received power; and n is the path loss exponent; and Distance from observations is related to the positions by the following equations: d1=(√{square root over ((x−x1)2+(y−y1)2)}) d2=(√{square root over ((x−x2)2+(y−y2)2)}) d3=(√{square root over ((x−x3)2+(y−y3)2)}) Also, in another embodiment of the present invention, a geolocation application software operable on a computer device or on a mobile communications device, such as by way of example and not limitation, a smartphone, is provided. Method steps are illustrated in the flow diagram shown inFIG.46, including starting a geolocation app; calling active devices via a connection broker; opening spectrum display application; selecting at least one signal to geolocate; selecting at least three devices (or apparatus unit of the present invention) within a location or region, verifying that the devices or apparatus units are synchronized to a receiver to be geolocated; perform signal detection (as described hereinabove) and include center frequency, bandwidth, peak power, channel power, and duration; identify modulation of protocol type, obtain maximum, median, minimum and expected power; calculating distance based on selected propagation model; calculating distance based on one (1) meter path loss; calculating distance based on one (1) meter path loss model; calculating distance based on one (1) meter path loss model; perform circle transformations for each location; checking if RF propagation distances form circles that are fully enclosed; checking if RF propagation form circles that do not intersect; performing trilateration of devices; deriving z component to convert back to known GPS Lat Lon (latitude and longitude) coordinate; and making coordinates and set point as emitter location on mapping software to indicate the geolocation. The equations referenced inFIG.46are provided hereinbelow: Equation 1 for calculating distance based on selected propagation model: PLossExponent=(ParameterC−6.55*log 10(BS_AntHeight))/10 MS_AntGainFunc=3.2*(log 10(11.75*MS_AntHeight))2−4.97 Constant(C)=ParameterA+ParameterB*log 10(Frequency)−13.82*log 10(BS_AntHeight)−MS_AntGainFunc DistanceRange=10((PLoss−PLossConstant)/10*PLossExponent)) Equation 2 for calculating distance based on 1 meter Path Loss Model (first device): d0=1;k=PLossExponent;PL_d=Pt+Gt−RSSI−TotalMargin PL_0=32.44+10*k*log 10(d0)+10*k*log 10(Frequency) D=d0*(10((PL_d−PL_0)/(10k))) Equation 3: (same as equation 2) for second device Equation 4: (same as equation 2) for third device Equation 5: Perform circle transformations for each location (x, y, z) Distance d; Verify ATA=0; where A={matrix of locations 1−N} in relation to distance; if not, then perform circle transformation check Equation 6: Perform trilateration of devices if more than three (3) devices aggregation and trilaterate by device; set circles to zero origin and solve from y=Ax where y=[x, y] locations [xy]=[2(xa-xc)2(ya-yc)2(xb-xc)2(yb-yc)]-1[xa2-xc2+ya2-yc2+dc2-da2xb2-xc2+yb2-yc2+dc2-db2]Equation7 Note that check if RF propagation distances form circles where one or more circles are Fully Enclosed if it is based upon Mod Type and Power Measured, then Set Distance1of enclosed circle to Distance2minus the distance between the two points. Also, next, check to see if some of the RF Propagation Distances Form Circles, if they do not intersect, then if so based on Mod type and Max RF power Set Distance to each circle to Distance of Circle+(Distance between circle points−Sum of the Distances)/2 is used. Note that deriving z component to convert back to known GPS lat lon coordinate is provided by: z=sqrt(Dist2−x2−y2). Accounting for unknowns using Differential Received Signal Strength (DRSS) is provided by the following equation when reference or transmit power is unknown: dιdj=10(Prj-Pri10n) And where signal strength measurements in dBm are provided by the following: Pr2(dBm)−Pr1(dBm)=10nlog10(√{square root over ((x−x1)2+(y−y1)2)})−10nlog10(√{square root over ((x−x2)2+(y−y2)2)}) Pr3(dBm)−Pr1(dBm)=10nlog10(√{square root over ((x−x1)2+(y−y1)2)})−10nlog10(√{square root over ((x−x3)2+(y−y3)2)}) Pr2(dBm)−Pr3(dBm)=10nlog10(√{square root over ((x−x3)2+(y−y3)2)})−10nlog10(√{square root over ((x−x2)2+(y−y2)2)}) For geolocation systems and methods of the present invention, preferably two or more devices or units are used to provide nodes. More preferably, three devices or units are used together or “joined” to achieve the geolocation results. Also preferably, at least three devices or units are provided. Software is provided and operable to enable a network-based method for transferring data between or among the at least two device or units, or more preferably at least three nodes, a database is provided having a database structure to receive input from the nodes (transferred data), and at least one processor coupled with memory to act on the database for performing calculations, transforming measured data and storing the measured data and statistical data associated with it; the database structure is further designed, constructed and configured to derive the geolocation of nodes from saved data and/or from real-time data that is measured by the units; also, the database and application of systems and methods of the present invention provide for geolocation of more than one node at a time. Additionally, software is operable to generate a visual representation of the geolocation of the nodes as a point on a map location. Errors in measurements due to imperfect knowledge of the transmit power or antenna gain, measurement error due to signal fading (multipath), interference, thermal noise, no line of sight (NLOS) propagation error (shadowing effect), and/or unknown propagation model, are overcome using differential RSS measurements, which eliminate the need for transmit power knowledge, and can incorporate TDOA and FDOA techniques to help improve measurements. The systems and methods of the present invention are further operable to use statistical approximations to remove error causes from noise, timing and power measurements, multipath, and NLOS measurements. By way of example, the following methods are used for geolocation statistical approximations and variances: maximum likelihood (nearest neighbor or Kalman filter); least squares approximation; Bayesian filter if prior knowledge data is included; and the like. Also, TDOA and FDOA equations are derived to help solve inconsistencies in distance calculations. Several methods or combinations of these methods may be used with the present invention, since geolocation will be performed in different environments, including but not limited to indoor environments, outdoor environments, hybrid (stadium) environments, inner city environments, etc. Geolocation Using Deployable Large Scale Arrays Typically, prior art arrays are more localized and deployed in a symmetrical fashion to reduce the complexity of mathematics and the equipment. The problem with localized fixed arrays are twofold: they require a large footprint for assembly and operation to gain accuracy in directional measurements. Conversely, smaller footprint arrays of geometric antenna systems can lose significant accuracy of the directional measurements. To avoid these limitations, a large variable array is used with fixed or mobile sites to allow greater accuracy. In one embodiment of the present invention, geolocation using angle of arrival is provided by a fixed position antenna system constructed and configured with a four-pole array in a close proximity to each other. The antenna system is a unique combination of a half (½) Adcock antenna array positioned at each unit. The antenna system is fixed and is operable to be deployed with a switching device to a low-cost full Adcock system. The use of a phase difference on the dual receiver input allows the local unit to determine a hemisphere of influence in a full Adcock configuration or a group of the deployed units as a full space diversity Adcock antenna system. This embodiment advantageously functions to eliminate directions in the vector-based math calculation, thereby eliminating a large group of false positives. The antenna system used with the geolocation systems and methods of the present invention includes three or more deployed units where none of the units is a full-time master nor slave. Each unit can be set to scan independently for target profiles. Once acquisition is obtained from one unit, the information is automatically disseminated to the other units within the cluster, i.e., the information is communicated wirelessly through a network. Preferably, the unit array is deployed in an asymmetrical configuration. The antenna system in the present invention utilizes Normalized Earth Centered Earth Fixed vectors. Two additional vector attributes of the monitoring station are selected from the following: pitch, yaw, velocity, altitude (positive and negative) and acceleration. Once a target acquisition from a single unit is acquired, a formatted message is broadcast to the deployed monitoring array stations. The formatted message includes but is not limited to the following: center frequency, bandwidth, modulation schema, average power and phase lock loop time adjustment from the local antenna system. The monitoring units include a GPS receiver to aid in high resolution clocks for timing of signal processing and exact location of the monitoring unit. This is key to determine an exact location of the monitoring units, either fixed or mobile, to simulate mathematically the variable large scale antenna array. The phased-locked inputs determine the orientation of the incoming target signal into hemispheres of influence. For this example,FIG.47is a North-South/East-West orientation of a local small diversity array. If the time difference between antenna1and antenna2is positive, the direction of travel is from North to South. If they are near equal, we are in the East-West plane. Another station with the local antenna on an east-west plane for the monitoring unit is operable to measure and determine if the incoming target is in the eastern hemisphere of the array. Since no site is a master to acquisition and measurement, the processing of any or all measurements can be done on a single monitoring unit. Preferably, the unit that originally captured the unknown target or an external processor processes the measurements. The next step in the process is to determine for each target measurement the delays of arrival at each location. This will further reveal the direction of travel to the target or additionally if the target is within the large-scale variable array's own footprint. Once the unit processing the data has received information from the other units in the array, processing of the information begins. First, the unit automatically sorts the array time of arrival at each location of the at least three units to construct mathematically a synthesis of the array. This is crucial to the efficiency and accuracy of the very large scale array, since no single monitoring unit is the point of reference. The point of reference is established by mathematical precedence involving time of arrival and the physical location of each monitoring unit at that point in time. An aperture is synthesized between any two points on the array using the difference in the arrival time. Establishing a midpoint between two monitoring units establishes a locus for the bearing measurement along the synthesized aperture. The aperture is given in radians by the following equation, where λ is the wavelength in meters, and Distance is the arc length in meters. ApertureLength=2·π·Distanceλ Distance is calculated by the following equations, where R is the radius of the earth in kilometers, and Lat and Lon refer to the points on installation for latitude and longitude in radians. ΔLat=Lat2-Lat1ΔLon=Lon2-Lon1a1=sin(ΔLat2)2+cos(Lat1)·cos(Lat2)·sin(ΔLon2)2k1=2·atan2(a1,(1-a1))Distance=1000·R·k1 The radial distance directly related to the angle of arrival across the aperture is given by the equation representing the radial time between monitor unit1and monitor unit2divided by Aperture Length: RadialDistance=TOA1-TOA2ApertureLength Using fundamental logic, two possible angles of arrival between the units defining the synthetic aperture for a bearing from the midpoint as illustrated inFIG.48. The use of a second component to establish a synthetic aperture yields another bearing as illustrated inFIG.49. Thus, as illustrated by the present invention, providing a point and additional elements to the array increases accuracy. The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art the order of steps in the foregoing embodiments may be performed in any order. Words such as “thereafter,” “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Further, any reference to claim elements in the singular, for example, using the articles “a,” “an” or “the” is not to be construed as limiting the element to the singular. The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. The hardware used to implement the various illustrative logics, logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function. In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable medium or non-transitory processor-readable medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module which may reside on a non-transitory computer-readable or processor-readable storage medium. Non-transitory computer-readable or processor-readable storage media may be any storage media that may be accessed by a computer or a processor. By way of example but not limitation, such non-transitory computer-readable or processor-readable media may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and BLU-RAY disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product. Certain modifications and improvements will occur to those skilled in the art upon a reading of the foregoing description. The above-mentioned examples are provided to serve the purpose of clarifying the aspects of the invention and it will be apparent to one skilled in the art that they do not serve to limit the scope of the invention. All modifications and improvements have been deleted herein for the sake of conciseness and readability but are properly within the scope of the present invention. | 155,242 |
11943738 | DETAILED DESCRIPTION Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure. The words “exemplary” and/or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and/or “example” is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. Those of skill in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description below may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc. Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action. As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer or consumer asset tracking device, wearable (e.g., smartwatch, glasses, augmented reality (AR)/virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or UT, a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and/or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE 802.11, etc.) and so on. A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. In addition, in some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions. In some systems, a base station may correspond to a Customer Premise Equipment (CPE) or a road-side unit (RSU). In some designs, a base station may correspond to a high-powered UE (e.g., a vehicle UE or VUE) that may provide limited certain infrastructure functionality. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an UL/reverse or DL/forward traffic channel. The term “base station” may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term “base station” refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference RF signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station. An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. According to various aspects,FIG.1illustrates an exemplary wireless communications system100. The wireless communications system100(which may also be referred to as a wireless wide area network (WWAN)) may include various base stations102and various UEs104. The base stations102may include macro cell base stations (high power cellular base stations) and/or small cell base stations (low power cellular base stations). In an aspect, the macro cell base station may include eNBs where the wireless communications system100corresponds to an LTE network, or gNBs where the wireless communications system100corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc. The base stations102may collectively form a RAN and interface with a core network170(e.g., an evolved packet core (EPC) or next generation core (NGC)) through backhaul links122, and through the core network170to one or more location servers172. In addition to other functions, the base stations102may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations102may communicate with each other directly or indirectly (e.g., through the EPC/NGC) over backhaul links134, which may be wired or wireless. The base stations102may wirelessly communicate with the UEs104. Each of the base stations102may provide communication coverage for a respective geographic coverage area110. In an aspect, one or more cells may be supported by a base station102in each coverage area110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI)) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both the logical communication entity and the base station that supports it, depending on the context. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas110. While neighboring macro cell base station102geographic coverage areas110may partially overlap (e.g., in a handover region), some of the geographic coverage areas110may be substantially overlapped by a larger geographic coverage area110. For example, a small cell base station102′ may have a coverage area110′ that substantially overlaps with the coverage area110of one or more macro cell base stations102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links120between the base stations102and the UEs104may include UL (also referred to as reverse link) transmissions from a UE104to a base station102and/or downlink (DL) (also referred to as forward link) transmissions from a base station102to a UE104. The communication links120may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links120may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL). The wireless communications system100may further include a wireless local area network (WLAN) access point (AP)150in communication with WLAN stations (STAs)152via communication links154in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs152and/or the WLAN AP150may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available. The small cell base station102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station102′ may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP150. The small cell base station102′, employing LTE/5G in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire. The wireless communications system100may further include a millimeter wave (mmW) base station180that may operate in mmW frequencies and/or near mmW frequencies in communication with a UE182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band have high path loss and a relatively short range. The mmW base station180and the UE182may utilize beamforming (transmit and/or receive) over a mmW communication link184to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations102may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein. Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while canceling to suppress radiation in undesired directions. Transmit beams may be quasi-collocated, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically collocated. In NR, there are four types of quasi-collocation (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel. In receive beamforming, the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and/or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction. Receive beams may be spatially related. A spatial relation means that parameters for a transmit beam for a second reference signal can be derived from information about a receive beam for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam. Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam. In 5G, the frequency spectrum in which wireless nodes (e.g., base stations102/180, UEs104/182) operate is divided into multiple frequency ranges, FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE104/182and the cell in which the UE104/182either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE104and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs104/182in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE104/182at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency/component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably. For example, still referring toFIG.1, one of the frequencies utilized by the macro cell base stations102may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations102and/or the mmW base station180may be secondary carriers (“SCells”). The simultaneous transmission and/or reception of multiple carriers enables the UE104/182to significantly increase its data transmission and/or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier. The wireless communications system100may further include one or more UEs, such as UE190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the example ofFIG.1, UE190has a D2D P2P link192with one of the UEs104connected to one of the base stations102(e.g., through which UE190may indirectly obtain cellular connectivity) and a D2D P2P link194with WLAN STA152connected to the WLAN AP150(through which UE190may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links192and194may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on. The wireless communications system100may further include a UE164that may communicate with a macro cell base station102over a communication link120and/or the mmW base station180over a mmW communication link184. For example, the macro cell base station102may support a PCell and one or more SCells for the UE164and the mmW base station180may support one or more SCells for the UE164. According to various aspects,FIG.2Aillustrates an example wireless network structure200. For example, an NGC210(also referred to as a “5GC”) can be viewed functionally as control plane functions214(e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions212, (e.g., UE gateway function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U)213and control plane interface (NG-C)215connect the gNB222to the NGC210and specifically to the control plane functions214and user plane functions212. In an additional configuration, an eNB224may also be connected to the NGC210via NG-C215to the control plane functions214and NG-U213to user plane functions212. Further, eNB224may directly communicate with gNB222via a backhaul connection223. In some configurations, the New RAN220may only have one or more gNBs222, while other configurations include one or more of both eNBs224and gNBs222. Either gNB222or eNB224may communicate with UEs204(e.g., any of the UEs depicted inFIG.1). Another optional aspect may include location server230, which may be in communication with the NGC210to provide location assistance for UEs204. The location server230can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The location server230can be configured to support one or more location services for UEs204that can connect to the location server230via the core network, NGC210, and/or via the Internet (not illustrated). Further, the location server230may be integrated into a component of the core network, or alternatively may be external to the core network. According to various aspects,FIG.2Billustrates another example wireless network structure250. For example, an NGC260(also referred to as a “5GC”) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF)/user plane function (UPF)264, and user plane functions, provided by a session management function (SMF)262, which operate cooperatively to form the core network (i.e., NGC260). User plane interface263and control plane interface265connect the eNB224to the NGC260and specifically to SMF262and AMF/UPF264, respectively. In an additional configuration, a gNB222may also be connected to the NGC260via control plane interface265to AMF/UPF264and user plane interface263to SMF262. Further, eNB224may directly communicate with gNB222via the backhaul connection223, with or without gNB direct connectivity to the NGC260. In some configurations, the New RAN220may only have one or more gNBs222, while other configurations include one or more of both eNBs224and gNBs222. Either gNB222or eNB224may communicate with UEs204(e.g., any of the UEs depicted inFIG.1). The base stations of the New RAN220communicate with the AMF-side of the AMF/UPF264over the N2 interface and the UPF-side of the AMF/UPF264over the N3 interface. The functions of the AMF include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between the UE204and the SMF262, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE204and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF also interacts with the authentication server function (AUSF) (not shown) and the UE204, and receives the intermediate key that was established as a result of the UE204authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF retrieves the security material from the AUSF. The functions of the AMF also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF also includes location services management for regulatory services, transport for location services messages between the UE204and the location management function (LMF)270, as well as between the New RAN220and the LMF270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE204mobility event notification. In addition, the AMF also supports functionalities for non-3GPP access networks. Functions of the UPF include acting as an anchor point for intra-/inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to the data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., UL/DL rate enforcement, reflective QoS marking in the DL), UL traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the UL and DL, DL packet buffering and DL data notification triggering, and sending and forwarding of one or more “end markers” to the source RAN node. The functions of the SMF262include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF262communicates with the AMF-side of the AMF/UPF264is referred to as the N11 interface. Another optional aspect may include a LMF270, which may be in communication with the NGC260to provide location assistance for UEs204. The LMF270can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The LMF270can be configured to support one or more location services for UEs204that can connect to the LMF270via the core network, NGC260, and/or via the Internet (not illustrated). FIGS.3A,3B, and3Cillustrate several sample components (represented by corresponding blocks) that may be incorporated into a UE302(which may correspond to any of the UEs described herein), a base station304(which may correspond to any of the base stations described herein), and a network entity306(which may correspond to or embody any of the network functions described herein, including the location server230and the LMF270) to support the file transmission operations as taught herein. It will be appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to provide similar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies. The UE302and the base station304each include wireless wide area network (WWAN) transceiver310and350, respectively, configured to communicate via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and/or the like. The WWAN transceivers310and350may be connected to one or more antennas316and356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time/frequency resources in a particular frequency spectrum). The WWAN transceivers310and350may be variously configured for transmitting and encoding signals318and358(e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals318and358(e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the transceivers310and350include one or more transmitters314and354, respectively, for transmitting and encoding signals318and358, respectively, and one or more receivers312and352, respectively, for receiving and decoding signals318and358, respectively. The UE302and the base station304also include, at least in some cases, wireless local area network (WLAN) transceivers320and360, respectively. The WLAN transceivers320and360may be connected to one or more antennas326and366, respectively, for communicating with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, etc.) over a wireless communication medium of interest. The WLAN transceivers320and360may be variously configured for transmitting and encoding signals328and368(e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals328and368(e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the transceivers320and360include one or more transmitters324and364, respectively, for transmitting and encoding signals328and368, respectively, and one or more receivers322and362, respectively, for receiving and decoding signals328and368, respectively. Transceiver circuitry including a transmitter and a receiver may comprise an integrated device (e.g., embodied as a transmitter circuit and a receiver circuit of a single communication device) in some implementations, may comprise a separate transmitter device and a separate receiver device in some implementations, or may be embodied in other ways in other implementations. In an aspect, a transmitter may include or be coupled to a plurality of antennas (e.g., antennas316,336, and376), such as an antenna array, that permits the respective apparatus to perform transmit “beamforming,” as described herein. Similarly, a receiver may include or be coupled to a plurality of antennas (e.g., antennas316,336, and376), such as an antenna array, that permits the respective apparatus to perform receive beamforming, as described herein. In an aspect, the transmitter and receiver may share the same plurality of antennas (e.g., antennas316,336, and376), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless communication device (e.g., one or both of the transceivers310and320and/or350and360) of the apparatuses302and/or304may also comprise a network listen module (NLM) or the like for performing various measurements. The apparatuses302and304also include, at least in some cases, satellite positioning systems (SPS) receivers330and370. The SPS receivers330and370may be connected to one or more antennas336and376, respectively, for receiving SPS signals338and378, respectively, such as global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. The SPS receivers330and370may comprise any suitable hardware and/or software for receiving and processing SPS signals338and378, respectively. The SPS receivers330and370request information and operations as appropriate from the other systems, and performs calculations necessary to determine the apparatus'302and304positions using measurements obtained by any suitable SPS algorithm. The base station304and the network entity306each include at least one network interfaces380and390for communicating with other network entities. For example, the network interfaces380and390(e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wire-based or wireless backhaul connection. In some aspects, the network interfaces380and390may be implemented as transceivers configured to support wire-based or wireless signal communication. This communication may involve, for example, sending and receiving: messages, parameters, or other types of information. The apparatuses302,304, and306also include other components that may be used in conjunction with the operations as disclosed herein. The UE302includes processor circuitry implementing a processing system332for providing functionality relating to, for example, false base station (FBS) detection as disclosed herein and for providing other processing functionality. The base station304includes a processing system384for providing functionality relating to, for example, FBS detection as disclosed herein and for providing other processing functionality. The network entity306includes a processing system394for providing functionality relating to, for example, FBS detection as disclosed herein and for providing other processing functionality. In an aspect, the processing systems332,384, and394may include, for example, one or more general purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGA), or other programmable logic devices or processing circuitry. The apparatuses302,304, and306include memory circuitry implementing memory components340,386, and396(e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). In some cases, the apparatuses302,304, and306may include positioning modules342,388and389, respectively. The positioning modules342,388and389may be hardware circuits that are part of or coupled to the processing systems332,384, and394, respectively, that, when executed, cause the apparatuses302,304, and306to perform the functionality described herein. Alternatively, the positioning modules342,388and389may be memory modules (as shown inFIGS.3A-C) stored in the memory components340,386, and396, respectively, that, when executed by the processing systems332,384, and394, cause the apparatuses302,304, and306to perform the functionality described herein. The UE302may include one or more sensors344coupled to the processing system332to provide movement and/or orientation information that is independent of motion data derived from signals received by the WWAN transceiver310, the WLAN transceiver320, and/or the GPS receiver330. By way of example, the sensor(s)344may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and/or any other type of movement detection sensor. Moreover, the sensor(s)344may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s)344may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in 2D and/or 3D coordinate systems. In addition, the UE302includes a user interface346for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the apparatuses304and306may also include user interfaces. Referring to the processing system384in more detail, in the downlink, IP packets from the network entity306may be provided to the processing system384. The processing system384may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The processing system384may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization. The transmitter354and the receiver352may implement Layer-1 functionality associated with various signal processing functions. Layer-1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The transmitter354handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE302. Each spatial stream may then be provided to one or more different antennas356. The transmitter354may modulate an RF carrier with a respective spatial stream for transmission. At the UE302, the receiver312receives a signal through its respective antenna(s)316. The receiver312recovers information modulated onto an RF carrier and provides the information to the processing system332. The transmitter314and the receiver312implement Layer-1 functionality associated with various signal processing functions. The receiver312may perform spatial processing on the information to recover any spatial streams destined for the UE302. If multiple spatial streams are destined for the UE302, they may be combined by the receiver312into a single OFDM symbol stream. The receiver312then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station304on the physical channel. The data and control signals are then provided to the processing system332, which implements Layer-3 and Layer-2 functionality. In the UL, the processing system332provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The processing system332is also responsible for error detection. Similar to the functionality described in connection with the DL transmission by the base station304, the processing system332provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization. Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station304may be used by the transmitter314to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter314may be provided to different antenna(s)316. The transmitter314may modulate an RF carrier with a respective spatial stream for transmission. The UL transmission is processed at the base station304in a manner similar to that described in connection with the receiver function at the UE302. The receiver352receives a signal through its respective antenna(s)356. The receiver352recovers information modulated onto an RF carrier and provides the information to the processing system384. In the UL, the processing system384provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE302. IP packets from the processing system384may be provided to the core network. The processing system384is also responsible for error detection. For convenience, the apparatuses302,304, and/or306are shown inFIGS.3A-Cas including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated blocks may have different functionality in different designs. The various components of the apparatuses302,304, and306may communicate with each other over data buses334,382, and392, respectively. The components ofFIGS.3A-Cmay be implemented in various ways. In some implementations, the components ofFIGS.3A-Cmay be implemented in one or more circuits such as, for example, one or more processors and/or one or more ASICs (which may include one or more processors). Here, each circuit may use and/or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks310to346may be implemented by processor and memory component(s) of the UE302(e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks350to388may be implemented by processor and memory component(s) of the base station304(e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks390to396may be implemented by processor and memory component(s) of the network entity306(e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed “by a UE,” “by a base station,” “by a positioning entity,” etc. However, as will be appreciated, such operations, acts, and/or functions may actually be performed by specific components or combinations of components of the UE, base station, positioning entity, etc., such as the processing systems332,384,394, the transceivers310,320,350, and360, the memory components340,386, and396, the positioning modules342,388and389, etc. FIG.4Ais a diagram400illustrating an example of a DL frame structure, according to aspects of the disclosure.FIG.4Bis a diagram430illustrating an example of channels within the DL frame structure, according to aspects of the disclosure. Other wireless communications technologies may have a different frame structures and/or different channels. LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively. LTE supports a single numerology (subcarrier spacing, symbol length, etc.). In contrast NR may support multiple numerologies, for example, subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, 120 kHz and 204 kHz or greater may be available. Table 1 provided below lists some various parameters for different NR numerologies. TABLE 1Max. nominalSubcarrierslots/Symbolsystem BWspacingSymbols/sub-slots/slotduration(MHz) with(kHz)slotframeframe(ms)(μs)4K FFT size1514110166.75030142200.533.310060144400.2516.7100120148800.1258.3340024014161600.06254.17800 In the examples ofFIGS.4A and4B, a numerology of 15 kHz is used. Thus, in the time domain, a frame (e.g., 10 ms) is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot. InFIGS.4A and4B, time is represented horizontally (e.g., on the X axis) with time increasing from left to right, while frequency is represented vertically (e.g., on the Y axis) with frequency increasing (or decreasing) from bottom to top. A resource grid may be used to represent time slots, each time slot including one or more time concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology ofFIGS.4A and4B, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols (for DL, OFDM symbols; for UL, SC-FDMA symbols) in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme. As illustrated inFIG.4A, some of the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include demodulation reference signals (DMRS) and channel state information reference signals (CSI-RS), exemplary locations of which are labeled “R” inFIG.4A. FIG.4Billustrates an example of various channels within a DL subframe of a frame. The physical downlink control channel (PDCCH) carries DL control information (DCI) within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The DCI carries information about UL resource allocation (persistent and non-persistent) and descriptions about DL data transmitted to the UE. Multiple (e.g., up to 8) DCIs can be configured in the PDCCH, and these DCIs can have one of multiple formats. For example, there are different DCI formats for UL scheduling, for non-MIMO DL scheduling, for MIMO DL scheduling, and for UL power control. A primary synchronization signal (PSS) is used by a UE to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a PCI. Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH), which carries an MIB, may be logically grouped with the PSS and SSS to form an SSB (also referred to as an SS/PBCH). The MIB provides a number of RBs in the DL system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages. In some cases, the DL RS illustrated inFIG.4Amay be positioning reference signals (PRS).FIG.5illustrates an exemplary PRS configuration500for a cell supported by a wireless node (such as a base station102).FIG.5shows how PRS positioning occasions are determined by a system frame number (SFN), a cell specific subframe offset (ΔPRS)552, and the PRS periodicity (TPRS)520. Typically, the cell specific PRS subframe configuration is defined by a “PRS Configuration Index” IPRSincluded in observed time difference of arrival (OTDOA) assistance data. The PRS periodicity (TPRS)520and the cell specific subframe offset (ΔPRS) are defined based on the PRS configuration index IPRS, as illustrated in Table 2 below. TABLE 2PRSPRS periodicityPRS subframeconfigurationTPRSoffset ΔPRSIndex IPRS(subframes)(subframes)0-159160IPRS160-479320IPRS- 160480-1119640IPRS- 4801120-23991280IPRS- 11202400-24045IPRS- 24002405-241410IPRS- 24052415-243420IPRS- 24152435-247440IPRS- 24352475-255480IPRS- 24752555-4095Reserved A PRS configuration is defined with reference to the SFN of a cell that transmits PRS. PRS instances, for the first subframe of the NPRSdownlink subframes comprising a first PRS positioning occasion, may satisfy: (10×nf+└ns/2┘−ΔPRS)modTPRS=0, Equation (1) where nfis the SFN with 0≤nf≤1023, nsis the slot number within the radio frame defined by nfwith 0≤ns≤19, TPRSis the PRS periodicity520, and ΔPRSis the cell-specific subframe offset552. As shown inFIG.5, the cell specific subframe offset ΔPRS552may be defined in terms of the number of subframes transmitted starting from system frame number 0 (Slot ‘Number 0’, marked as slot550) to the start of the first (subsequent) PRS positioning occasion. In the example inFIG.5, the number of consecutive positioning subframes (NPRS) in each of the consecutive PRS positioning occasions518a,518b, and518cequals 4. That is, each shaded block representing PRS positioning occasions518a,518b, and518crepresents four subframes. In some aspects, when a UE receives a PRS configuration index IPRSin the OTDOA assistance data for a particular cell, the UE may determine the PRS periodicity TPRS520and PRS subframe offset ΔPRSusing Table 2. The UE may then determine the radio frame, subframe, and slot when a PRS is scheduled in the cell (e.g., using Equation (1)). The OTDOA assistance data may be determined by, for example, the location server (e.g., location server230, LMF270), and includes assistance data for a reference cell, and a number of neighbor cells supported by various base stations. Typically, PRS occasions from all cells in a network that use the same frequency are aligned in time and may have a fixed known time offset (e.g., cell-specific subframe offset552) relative to other cells in the network that use a different frequency. In SFN-synchronous networks, all wireless nodes (e.g., base stations102) may be aligned on both frame boundary and system frame number. Therefore, in SFN-synchronous networks, all cells supported by the various wireless nodes may use the same PRS configuration index for any particular frequency of PRS transmission. On the other hand, in SFN-asynchronous networks, the various wireless nodes may be aligned on a frame boundary, but not system frame number. Thus, in SFN-asynchronous networks the PRS configuration index for each cell may be configured separately by the network so that PRS occasions align in time. A UE may determine the timing of the PRS occasions of the reference and neighbor cells for OTDOA positioning, if the UE can obtain the cell timing (e.g., SFN) of at least one of the cells, e.g., the reference cell or a serving cell. The timing of the other cells may then be derived by the UE based, for example, on the assumption that PRS occasions from different cells overlap. A collection of resource elements that are used for transmission of PRS is referred to as a “PRS resource.” The collection of resource elements can span multiple PRBs in the frequency domain and N (e.g., 1 or more) consecutive symbol(s)460within a slot430in the time domain. In a given OFDM symbol460, a PRS resource occupies consecutive PRBs. A PRS resource is described by at least the following parameters: PRS resource identifier (ID), sequence ID, comb size-N, resource element offset in the frequency domain, starting slot and starting symbol, number of symbols per PRS resource (i.e., the duration of the PRS resource), and QCL information (e.g., QCL with other DL reference signals). In some designs, one antenna port is supported. The comb size indicates the number of subcarriers in each symbol carrying PRS. For example, a comb-size of comb-4 means that every fourth subcarrier of a given symbol carries PRS. A “PRS resource set” is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same transmission-reception point (TRP). A PRS resource ID in a PRS resource set is associated with a single beam transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource of a PRS resource set may be transmitted on a different beam, and as such, a “PRS resource” can also be referred to as a “beam.” Note that this does not have any implications on whether the TRPs and the beams on which PRS are transmitted are known to the UE. A “PRS occasion” is one instance of a periodically repeated time window (e.g., a group of one or more consecutive slots) where PRS are expected to be transmitted. A PRS occasion may also be referred to as a “PRS positioning occasion,” a “positioning occasion,” or simply an “occasion.” Note that the terms “positioning reference signal” and “PRS” may sometimes refer to specific reference signals that are used for positioning in LTE or NR systems. However, as used herein, unless otherwise indicated, the terms “positioning reference signal” and “PRS” refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS signals in LTE or NR, navigation reference signals (NRSs) in 5G, transmitter reference signals (TRSs), cell-specific reference signals (CRSs), channel state information reference signals (CSI-RSs), primary synchronization signals (PSSs), secondary synchronization signals (SSSs), SSB, etc. An SRS is an uplink-only signal that a UE transmits to help the base station obtain the channel state information (CSI) for each user. Channel state information describes how an RF signal propagates from the UE to the base station and represents the combined effect of scattering, fading, and power decay with distance. The system uses the SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc. Several enhancements over the previous definition of SRS have been proposed for SRS for positioning (SRS-P), such as a new staggered pattern within an SRS resource, a new comb type for SRS, new sequences for SRS, a higher number of SRS resource sets per component carrier, and a higher number of SRS resources per component carrier. In addition, the parameters “SpatialRelationInfo” and “PathLossReference” are to be configured based on a DL RS from a neighboring TRP. Further still, one SRS resource may be transmitted outside the active bandwidth part (BWP), and one SRS resource may span across multiple component carriers. Lastly, the UE may transmit through the same transmit beam from multiple SRS resources for UL-AoA. All of these are features that are additional to the current SRS framework, which is configured through RRC higher layer signaling (and potentially triggered or activated through MAC control element (CE) or downlink control information (DCI)). As noted above, SRSs in NR are UE-specifically configured reference signals transmitted by the UE used for the purposes of the sounding the uplink radio channel. Similar to CSI-RS, such sounding provides various levels of knowledge of the radio channel characteristics. On one extreme, the SRS can be used at the gNB simply to obtain signal strength measurements, e.g., for the purposes of UL beam management. On the other extreme, SRS can be used at the gNB to obtain detailed amplitude and phase estimates as a function of frequency, time and space. In NR, channel sounding with SRS supports a more diverse set of use cases compared to LTE (e.g., downlink CSI acquisition for reciprocity-based gNB transmit beamforming (downlink MIMO); uplink CSI acquisition for link adaptation and codebook/non-codebook based precoding for uplink MIMO, uplink beam management, etc.). The SRS can be configured using various options. The time/frequency mapping of an SRS resource is defined by the following characteristics.Time duration NsymbSRS—The time duration of an SRS resource can be 1, 2, or 4 consecutive OFDM symbols within a slot, in contrast to LTE which allows only a single OFDM symbol per slot.Starting symbol location l0—The starting symbol of an SRS resource can be located anywhere within the last 6 OFDM symbols of a slot provided the resource does not cross the end-of-slot boundary.Repetition factor R—For an SRS resource configured with frequency hopping, repetition allows the same set of subcarriers to be sounded in R consecutive OFDM symbols before the next hop occurs (as used herein, a “hop” refers to specifically to a frequency hop). For example, values of R are 1, 2, 4 where R≤NsymbSRS.Transmission comb spacing KTCand comb offset kTC—An SRS resource may occupy resource elements (REs) of a frequency domain comb structure, where the comb spacing is either 2 or 4 REs like in LTE. Such a structure allows frequency domain multiplexing of different SRS resources of the same or different users on different combs, where the different combs are offset from each other by an integer number of REs. The comb offset is defined with respect to a PRB boundary, and can take values in the range 0,1, . . . , KTC−1 REs. Thus, for comb spacing KTC=2, there are 2 different combs available for multiplexing if needed, and for comb spacing KTC=4, there are 4 different available combs.Periodicity and slot offset for the case of periodic/semi-persistent SRS.Sounding bandwidth within a bandwidth part. For low latency positioning, a gNB may trigger a UL SRS-P via a DCI (e.g., transmitted SRS-P may include repetition or beam-sweeping to enable several gNBs to receive the SRS-P). Alternatively, the gNB may send information regarding aperiodic PRS transmission to the UE (e.g., this configuration may include information about PRS from multiple gNBs to enable the UE to perform timing computations for positioning (UE-based) or for reporting (UE-assisted). While various embodiments of the present disclosure relate to DL PRS-based positioning procedures, some or all of such embodiments may also apply to UL SRS-P-based positioning procedures. Note that the terms “sounding reference signal”, “SRS” and “SRS-P” may sometimes refer to specific reference signals that are used for positioning in LTE or NR systems. However, as used herein, unless otherwise indicated, the terms “sounding reference signal”, “SRS” and “SRS-P” refer to any type of reference signal that can be used for positioning, such as but not limited to, SRS signals in LTE or NR, navigation reference signals (NRSs) in 5G, transmitter reference signals (TRSs), random access channel (RACH) signals for positioning (e.g., RACH preambles, such as Msg-1 in 4-Step RACH procedure or Msg-A in 2-Step RACH procedure), etc. 3GPP Rel. 16 introduced various NR positioning aspects directed to increase location accuracy of positioning schemes that involve measurement(s) associated with one or more UL or DL PRSs (e.g., higher bandwidth (BW), FR2 beam-sweeping, angle-based measurements such as Angle of Arrival (AoA) and Angle of Departure (AoD) measurements, multi-cell Round-Trip Time (RTT) measurements, etc.). If latency reduction is a priority, then UE-based positioning techniques (e.g., DL-only techniques without UL location measurement reporting) are typically used. However, if latency is less of a concern, then UE-assisted positioning techniques can be used, whereby UE-measured data is reported to a network entity (e.g., location server230, LMF270, etc.). Latency associated UE-assisted positioning techniques can be reduced somewhat by implementing the LMF in the RAN. Layer-3 (L3) signaling (e.g., RRC or Location Positioning Protocol (LPP)) is typically used to transport reports that comprise location-based data in association with UE-assisted positioning techniques. L3 signaling is associated with relatively high latency (e.g., above 100 ms) compared with Layer-1 (L1, or PHY layer) signaling or Layer-2 (L2, or MAC layer) signaling. In some cases, lower latency (e.g., less than 100 ms, less than 10 ms, etc.) between the UE and the RAN for location-based reporting may be desired. In such cases, L3 signaling may not be capable of reaching these lower latency levels. L3 signaling of positioning measurements may comprise any combination of the following:One or multiple TOA, TDOA, RSRP or Rx-Tx measurements,One or multiple AoA/AoD (e.g., currently agreed only for gNB→LMF reporting DL AoA and UL AoD) measurements,One or multiple Multipath reporting measurements, e.g., per-path ToA, RSRP, AoA/AoD (e.g., currently only per-path ToA allowed in LTE)One or multiple motion states (e.g., walking, driving, etc.) and trajectories (e.g., currently for UE), and/orOne or multiple report quality indications. More recently, L1 and L2 signaling has been contemplated for use in association with PRS-based reporting. For example, L1 and L2 signaling is currently used in some systems to transport CSI reports (e.g., reporting of Channel Quality Indications (CQIs), Precoding Matrix Indicators (PMIs), Layer Indicators (Lis), L1-RSRP, etc.). CSI reports may comprise a set of fields in a pre-defined order (e.g., defined by the relevant standard). A single UL transmission (e.g., on PUSCH or PUCCH) may include multiple reports, referred to herein as ‘sub-reports’, which are arranged according to a pre-defined priority (e.g., defined by the relevant standard). In some designs, the pre-defined order may be based on an associated sub-report periodicity (e.g., aperiodic/semi-persistent/periodic (A/SP/P) over PUSCH/PUCCH), measurement type (e.g., L1-RSRP or not), serving cell index (e.g., in carrier aggregation (CA) case), and reportconfigID. With 2-part CSI reporting, the part 1s of all reports are grouped together, and the part 2s are grouped separately, and each group is separately encoded (e.g., part 1 payload size is fixed based on configuration parameters, while part 2 size is variable and depends on configuration parameters and also on associated part 1 content). A number of coded bits/symbols to be output after encoding and rate-matching is computed based on a number of input bits and beta factors, per the relevant standard. Linkages (e.g., time offsets) are defined between instances of RSs being measured and corresponding reporting. In some designs, CSI-like reporting of PRS-based measurement data using L1 and L2 signaling may be implemented. FIG.6illustrates an exemplary wireless communications system600according to various aspects of the disclosure. In the example ofFIG.6, a UE604, which may correspond to any of the UEs described above with respect toFIG.1(e.g., UEs104, UE182, UE190, etc.), is attempting to calculate an estimate of its position, or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its position. The UE604may communicate wirelessly with a plurality of base stations602a-d(collectively, base stations602), which may correspond to any combination of base stations102or180and/or WLAN AP150inFIG.1, using RF signals and standardized protocols for the modulation of the RF signals and the exchange of information packets. By extracting different types of information from the exchanged RF signals, and utilizing the layout of the wireless communications system600(i.e., the base stations locations, geometry, etc.), the UE604may determine its position, or assist in the determination of its position, in a predefined reference coordinate system. In an aspect, the UE604may specify its position using a two-dimensional coordinate system; however, the aspects disclosed herein are not so limited, and may also be applicable to determining positions using a three-dimensional coordinate system, if the extra dimension is desired. Additionally, whileFIG.6illustrates one UE604and four base stations602, as will be appreciated, there may be more UEs604and more or fewer base stations602. To support position estimates, the base stations602may be configured to broadcast reference RF signals (e.g., Positioning Reference Signals (PRS), Cell-specific Reference Signals (CRS), Channel State Information Reference Signals (CSI-RS), synchronization signals, etc.) to UEs604in their coverage areas to enable a UE604to measure reference RF signal timing differences (e.g., OTDOA or reference signal time difference (RSTD)) between pairs of network nodes and/or to identify the beam that best excite the LOS or shortest radio path between the UE604and the transmitting base stations602. Identifying the LOS/shortest path beam(s) is of interest not only because these beams can subsequently be used for OTDOA measurements between a pair of base stations602, but also because identifying these beams can directly provide some positioning information based on the beam direction. Moreover, these beams can subsequently be used for other position estimation methods that require precise ToA, such as round-trip time estimation based methods. As used herein, a “network node” may be a base station602, a cell of a base station602, a remote radio head, an antenna of a base station602, where the locations of the antennas of a base station602are distinct from the location of the base station602itself, or any other network entity capable of transmitting reference signals. Further, as used herein, a “node” may refer to either a network node or a UE. A location server (e.g., location server230) may send assistance data to the UE604that includes an identification of one or more neighbor cells of base stations602and configuration information for reference RF signals transmitted by each neighbor cell. Alternatively, the assistance data can originate directly from the base stations602themselves (e.g., in periodically broadcasted overhead messages, etc.). Alternatively, the UE604can detect neighbor cells of base stations602itself without the use of assistance data. The UE604(e.g., based in part on the assistance data, if provided) can measure and (optionally) report the OTDOA from individual network nodes and/or RSTDs between reference RF signals received from pairs of network nodes. Using these measurements and the known locations of the measured network nodes (i.e., the base station(s)602or antenna(s) that transmitted the reference RF signals that the UE604measured), the UE604or the location server can determine the distance between the UE604and the measured network nodes and thereby calculate the location of the UE604. The term “position estimate” is used herein to refer to an estimate of a position for a UE604, which may be geographic (e.g., may comprise a latitude, longitude, and possibly altitude) or civic (e.g., may comprise a street address, building designation, or precise point or area within or nearby to a building or street address, such as a particular entrance to a building, a particular room or suite in a building, or a landmark such as a town square). A position estimate may also be referred to as a “location,” a “position,” a “fix,” a “position fix,” a “location fix,” a “location estimate,” a “fix estimate,” or by some other term. The means of obtaining a location estimate may be referred to generically as “positioning,” “locating,” or “position fixing.” A particular solution for obtaining a position estimate may be referred to as a “position solution.” A particular method for obtaining a position estimate as part of a position solution may be referred to as a “position method” or as a “positioning method.” The term “base station” may refer to a single physical transmission point or to multiple physical transmission points that may or may not be co-located. For example, where the term “base station” refers to a single physical transmission point, the physical transmission point may be an antenna of the base station (e.g., base station602) corresponding to a cell of the base station. Where the term “base station” refers to multiple co-located physical transmission points, the physical transmission points may be an array of antennas (e.g., as in a MIMO system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical transmission points, the physical transmission points may be a Distributed Antenna System (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a Remote Radio Head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical transmission points may be the serving base station receiving the measurement report from the UE (e.g., UE604) and a neighbor base station whose reference RF signals the UE is measuring. Thus,FIG.6illustrates an aspect in which base stations602aand602bform a DAS/RRH620. For example, the base station602amay be the serving base station of the UE604and the base station602bmay be a neighbor base station of the UE604. As such, the base station602bmay be the RRH of the base station602a. The base stations602aand602bmay communicate with each other over a wired or wireless link622. To accurately determine the position of the UE604using the OTDOAs and/or RSTDs between RF signals received from pairs of network nodes, the UE604needs to measure the reference RF signals received over the LOS path (or the shortest NLOS path where an LOS path is not available), between the UE604and a network node (e.g., base station602, antenna). However, RF signals travel not only by the LOS/shortest path between the transmitter and receiver, but also over a number of other paths as the RF signals spread out from the transmitter and reflect off other objects such as hills, buildings, water, and the like on their way to the receiver. Thus,FIG.6illustrates a number of LOS paths610and a number of NLOS paths612between the base stations602and the UE604. Specifically,FIG.6illustrates base station602atransmitting over an LOS path610aand an NLOS path612a, base station602btransmitting over an LOS path610band two NLOS paths612b, base station602ctransmitting over an LOS path610cand an NLOS path612c, and base station602dtransmitting over two NLOS paths612d. As illustrated inFIG.6, each NLOS path612reflects off some object630(e.g., a building). As will be appreciated, each LOS path610and NLOS path612transmitted by a base station602may be transmitted by different antennas of the base station602(e.g., as in a MIMO system), or may be transmitted by the same antenna of a base station602(thereby illustrating the propagation of an RF signal). Further, as used herein, the term “LOS path” refers to the shortest path between a transmitter and receiver, and may not be an actual LOS path, but rather, the shortest NLOS path. In an aspect, one or more of base stations602may be configured to use beamforming to transmit RF signals. In that case, some of the available beams may focus the transmitted RF signal along the LOS paths610(e.g., the beams produce highest antenna gain along the LOS paths) while other available beams may focus the transmitted RF signal along the NLOS paths612. A beam that has high gain along a certain path and thus focuses the RF signal along that path may still have some RF signal propagating along other paths; the strength of that RF signal naturally depends on the beam gain along those other paths. An “RF signal” comprises an electromagnetic wave that transports information through the space between the transmitter and the receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, as described further below, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. Where a base station602uses beamforming to transmit RF signals, the beams of interest for data communication between the base station602and the UE604will be the beams carrying RF signals that arrive at UE604with the highest signal strength (as indicated by, e.g., the Received Signal Received Power (RSRP) or SINR in the presence of a directional interfering signal), whereas the beams of interest for position estimation will be the beams carrying RF signals that excite the shortest path or LOS path (e.g., an LOS path610). In some frequency bands and for antenna systems typically used, these will be the same beams. However, in other frequency bands, such as mmW, where typically a large number of antenna elements can be used to create narrow transmit beams, they may not be the same beams. As described below with reference toFIG.7, in some cases, the signal strength of RF signals on the LOS path610may be weaker (e.g., due to obstructions) than the signal strength of RF signals on an NLOS path612, over which the RF signals arrive later due to propagation delay. FIG.7illustrates an exemplary wireless communications system700according to various aspects of the disclosure. In the example ofFIG.7, a UE704, which may correspond to UE604inFIG.6, is attempting to calculate an estimate of its position, or to assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its position. The UE704may communicate wirelessly with a base station702, which may correspond to one of base stations602inFIG.6, using RF signals and standardized protocols for the modulation of the RF signals and the exchange of information packets. As illustrated inFIG.7, the base station702is utilizing beamforming to transmit a plurality of beams711-715of RF signals. Each beam711-715may be formed and transmitted by an array of antennas of the base station702. AlthoughFIG.7illustrates a base station702transmitting five beams711-715, as will be appreciated, there may be more or fewer than five beams, beam shapes such as peak gain, width, and side-lobe gains may differ amongst the transmitted beams, and some of the beams may be transmitted by a different base station. A beam index may be assigned to each of the plurality of beams711-715for purposes of distinguishing RF signals associated with one beam from RF signals associated with another beam. Moreover, the RF signals associated with a particular beam of the plurality of beams711-715may carry a beam index indicator. A beam index may also be derived from the time of transmission, e.g., frame, slot and/or OFDM symbol number, of the RF signal. The beam index indicator may be, for example, a three-bit field for uniquely distinguishing up to eight beams. If two different RF signals having different beam indices are received, this would indicate that the RF signals were transmitted using different beams. If two different RF signals share a common beam index, this would indicate that the different RF signals are transmitted using the same beam. Another way to describe that two RF signals are transmitted using the same beam is to say that the antenna port(s) used for the transmission of the first RF signal are spatially quasi-collocated with the antenna port(s) used for the transmission of the second RF signal. In the example ofFIG.7, the UE704receives an NLOS data stream723of RF signals transmitted on beam713and an LOS data stream724of RF signals transmitted on beam714. AlthoughFIG.7illustrates the NLOS data stream723and the LOS data stream724as single lines (dashed and solid, respectively), as will be appreciated, the NLOS data stream723and the LOS data stream724may each comprise multiple rays (i.e., a “cluster”) by the time they reach the UE704due, for example, to the propagation characteristics of RF signals through multipath channels. For example, a cluster of RF signals is formed when an electromagnetic wave is reflected off of multiple surfaces of an object, and reflections arrive at the receiver (e.g., UE704) from roughly the same angle, each traveling a few wavelengths (e.g., centimeters) more or less than others. A “cluster” of received RF signals generally corresponds to a single transmitted RF signal. In the example ofFIG.7, the NLOS data stream723is not originally directed at the UE704, although, as will be appreciated, it could be, as are the RF signals on the NLOS paths612inFIG.6. However, it is reflected off a reflector740(e.g., a building) and reaches the UE704without obstruction, and therefore, may still be a relatively strong RF signal. In contrast, the LOS data stream724is directed at the UE704but passes through an obstruction730(e.g., vegetation, a building, a hill, a disruptive environment such as clouds or smoke, etc.), which may significantly degrade the RF signal. As will be appreciated, although the LOS data stream724is weaker than the NLOS data stream723, the LOS data stream724will arrive at the UE704before the NLOS data stream723because it follows a shorter path from the base station702to the UE704. As noted above, the beam of interest for data communication between a base station (e.g., base station702) and a UE (e.g., UE704) is the beam carrying RF signals that arrives at the UE with the highest signal strength (e.g., highest RSRP or SINR), whereas the beam of interest for position estimation is the beam carrying RF signals that excite the LOS path and that has the highest gain along the LOS path amongst all other beams (e.g., beam714). That is, even if beam713(the NLOS beam) were to weakly excite the LOS path (due to the propagation characteristics of RF signals, even though not being focused along the LOS path), that weak signal, if any, of the LOS path of beam713may not be as reliably detectable (compared to that from beam714), thus leading to greater error in performing a positioning measurement. While the beam of interest for data communication and the beam of interest for position estimation may be the same beams for some frequency bands, for other frequency bands, such as mmW, they may not be the same beams. As such, referring toFIG.7, where the UE704is engaged in a data communication session with the base station702(e.g., where the base station702is the serving base station for the UE704) and not simply attempting to measure reference RF signals transmitted by the base station702, the beam of interest for the data communication session may be the beam713, as it is carrying the unobstructed NLOS data stream723. The beam of interest for position estimation, however, would be the beam714, as it carries the strongest LOS data stream724, despite being obstructed. FIG.8Ais a graph800A showing the RF channel response at a receiver (e.g., UE704) over time according to aspects of the disclosure. Under the channel illustrated inFIG.8A, the receiver receives a first cluster of two RF signals on channel taps at time T1, a second cluster of five RF signals on channel taps at time T2, a third cluster of five RF signals on channel taps at time T3, and a fourth cluster of four RF signals on channel taps at time T4. In the example ofFIG.8A, because the first cluster of RF signals at time T1arrives first, it is presumed to be the LOS data stream (i.e., the data stream arriving over the LOS or the shortest path), and may correspond to the LOS data stream724. The third cluster at time T3is comprised of the strongest RF signals, and may correspond to the NLOS data stream723. Seen from the transmitter's side, each cluster of received RF signals may comprise the portion of an RF signal transmitted at a different angle, and thus each cluster may be said to have a different angle of departure (AoD) from the transmitter.FIG.8Bis a diagram800B illustrating this separation of clusters in AoD. The RF signal transmitted in AoD range802amay correspond to one cluster (e.g., “Cluster1”) inFIG.8A, and the RF signal transmitted in AoD range802bmay correspond to a different cluster (e.g., “Cluster3”) inFIG.8A. Note that although AoD ranges of the two clusters depicted inFIG.8Bare spatially isolated, AoD ranges of some clusters may also partially overlap even though the clusters are separated in time. For example, this may arise when two separate buildings at same AoD from the transmitter reflect the signal towards the receiver. Note that althoughFIG.8Aillustrates clusters of two to five channel taps (or “peaks”), as will be appreciated, the clusters may have more or fewer than the illustrated number of channel taps. RAN1 NR may define UE measurements on DL reference signals (e.g., for serving, reference, and/or neighboring cells) applicable for NR positioning, including DL reference signal time difference (RSTD) measurements for NR positioning, DL RSRP measurements for NR positioning, and UE Rx-Tx (e.g., a hardware group delay from signal reception at UE receiver to response signal transmission at UE transmitter, e.g., for time difference measurements for NR positioning, such as RTT). RAN1 NR may define gNB measurements based on UL reference signals applicable for NR positioning, such as relative UL time of arrival (RTOA) for NR positioning, UL AoA measurements (e.g., including Azimuth and Zenith Angles) for NR positioning, UL RSRP measurements for NR positioning, and gNB Rx-Tx (e.g., a hardware group delay from signal reception at gNB receiver to response signal transmission at gNB transmitter, e.g., for time difference measurements for NR positioning, such as RTT). FIG.9is a diagram900showing exemplary timings of RTT measurement signals exchanged between a base station902(e.g., any of the base stations described herein) and a UE904(e.g., any of the UEs described herein), according to aspects of the disclosure. In the example ofFIG.9, the base station902sends an RTT measurement signal910(e.g., PRS, NRS, CRS, CSI-RS, etc.) to the UE904at time t1. The RTT measurement signal910has some propagation delay TPropas it travels from the base station902to the UE904. At time t2(the ToA of the RTT measurement signal910at the UE904), the UE904receives/measures the RTT measurement signal910. After some UE processing time, the UE904transmits an RTT response signal920at time t3. After the propagation delay TProp, the base station902receives/measures the RTT response signal920from the UE904at time t4(the ToA of the RTT response signal920at the base station902). In order to identify the ToA (e.g., t2) of a reference signal (e.g., an RTT measurement signal910) transmitted by a given network node (e.g., base station902), the receiver (e.g., UE904) first jointly processes all the resource elements (REs) on the channel on which the transmitter is transmitting the reference signal, and performs an inverse Fourier transform to convert the received reference signals to the time domain. The conversion of the received reference signals to the time domain is referred to as estimation of the channel energy response (CER). The CER shows the peaks on the channel over time, and the earliest “significant” peak should therefore correspond to the ToA of the reference signal. Generally, the receiver will use a noise-related quality threshold to filter out spurious local peaks, thereby presumably correctly identifying significant peaks on the channel. For example, the receiver may choose a ToA estimate that is the earliest local maximum of the CER that is at least X dB higher than the median of the CER and a maximum Y dB lower than the main peak on the channel. The receiver determines the CER for each reference signal from each transmitter in order to determine the ToA of each reference signal from the different transmitters. In some designs, the RTT response signal920may explicitly include the difference between time t3and time t2(i.e., TRx→Tx912). Using this measurement and the difference between time t4and time t1(i.e., TTx→Rx922), the base station902(or other positioning entity, such as location server230, LMF270) can calculate the distance to the UE904as: d=12c(TTx→Rx-TRx→Tx)=12c(t2-t1)-12c(t4-t3) where c is the speed of light. While not illustrated expressly inFIG.9, an additional source of delay or error may be due to UE and gNB hardware group delay for position location. Various parameters associated with positioning can impact power consumption at the UE. Knowledge of such parameters can be used to estimate (or model) the UE power consumption. By accurately modeling the power consumption of the UE, various power saving features and/or performance enhancing features can be utilized in a predictive manner so as to improve the user experience. An additional source of delay or error is due to UE and gNB hardware group delay for position location.FIG.10illustrates a diagram1000showing exemplary timings of RTT measurement signals exchanged between a base station (gNB) (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein), according to aspects of the disclosure.FIG.10is similar in some respects toFIG.9. However, inFIG.10, the UE and gNB hardware group delay (which is primarily due to internal hardware delays between a baseband (BB) component and antenna (ANT) at the UE and gNB) is shown with respect1002-1008. As will be appreciated, both Tx-side and Rx-side path-specific or beam-specific delays impact the RTT measurement. Hardware group delays such as1002-1008can contribute to timing errors and/or calibration errors that can impact RTT as well as other measurements such as TDOA, RSTD, and so on, which in turn can impact positioning performance. For example, in some designs, 10 nsec of error will introduce the 3 meter of error in the final fix. FIG.11illustrates an exemplary wireless communications system1100according to aspects of the disclosure. In the example ofFIG.11, a UE1104(which may correspond to any of the UEs described herein) is attempting to calculate an estimate of its position, or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its position, via a multi-RTT positioning scheme. The UE1104may communicate wirelessly with a plurality of base stations1102-1,1102-2, and1102-3(collectively, base stations1102, and which may correspond to any of the base stations described herein) using RF signals and standardized protocols for the modulation of the RF signals and the exchange of information packets. By extracting different types of information from the exchanged RF signals, and utilizing the layout of the wireless communications system1100(i.e., the base stations' locations, geometry, etc.), the UE1104may determine its position, or assist in the determination of its position, in a predefined reference coordinate system. In an aspect, the UE1104may specify its position using a two-dimensional coordinate system; however, the aspects disclosed herein are not so limited, and may also be applicable to determining positions using a three-dimensional coordinate system, if the extra dimension is desired. Additionally, whileFIG.11illustrates one UE1104and three base stations1102, as will be appreciated, there may be more UEs1104and more base stations1102. To support position estimates, the base stations1102may be configured to broadcast reference RF signals (e.g., PRS, NRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to UEs1104in their coverage area to enable a UE1104to measure characteristics of such reference RF signals. For example, the UE1104may measure the ToA of specific reference RF signals (e.g., PRS, NRS, CRS, CSI-RS, etc.) transmitted by at least three different base stations1102and may use the RTT positioning method to report these ToAs (and additional information) back to the serving base station1102or another positioning entity (e.g., location server230, LMF270). In an aspect, although described as the UE1104measuring reference RF signals from a base station1102, the UE1104may measure reference RF signals from one of multiple cells supported by a base station1102. Where the UE1104measures reference RF signals transmitted by a cell supported by a base station1102, the at least two other reference RF signals measured by the UE1104to perform the RTT procedure would be from cells supported by base stations1102different from the first base station1102and may have good or poor signal strength at the UE1104. In order to determine the position (x, y) of the UE1104, the entity determining the position of the UE1104needs to know the locations of the base stations1102, which may be represented in a reference coordinate system as (xk, yk), where k=1, 2, 3 in the example ofFIG.11. Where one of the base stations1102(e.g., the serving base station) or the UE1104determines the position of the UE1104, the locations of the involved base stations1102may be provided to the serving base station1102or the UE1104by a location server with knowledge of the network geometry (e.g., location server230, LMF270). Alternatively, the location server may determine the position of the UE1104using the known network geometry. Either the UE1104or the respective base station1102may determine the distance (dk, where k=1, 2, 3) between the UE1104and the respective base station1102. In an aspect, determining the RTT1110of signals exchanged between the UE1104and any base station1102can be performed and converted to a distance (dk). As discussed further below, RTT techniques can measure the time between sending a signaling message (e.g., reference RF signals) and receiving a response. These methods may utilize calibration to remove any processing delays. In some environments, it may be assumed that the processing delays for the UE1104and the base stations1102are the same. However, such an assumption may not be true in practice. Once each distance dkis determined, the UE1104, a base station1102, or the location server (e.g., location server230, LMF270) can solve for the position (x, y) of the UE1104by using a variety of known geometric techniques, such as, for example, trilateration. FromFIG.11, it can be seen that the position of the UE1104ideally lies at the common intersection of three semicircles, each semicircle being defined by radius dkand center (xk, yk), where k=1, 2, 3. In some instances, additional information may be obtained in the form of an angle of arrival (AoA) or angle of departure (AoD) that defines a straight line direction (e.g., which may be in a horizontal plane or in three dimensions) or possibly a range of directions (e.g., for the UE1104from the location of a base station1102). The intersection of the two directions at or near the point (x, y) can provide another estimate of the location for the UE1104. A position estimate (e.g., for a UE1104) may be referred to by other names, such as a location estimate, location, position, position fix, fix, or the like. A position estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of a location. A position estimate may further be defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). A position estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default level of confidence). FIG.12illustrates is a diagram1200showing exemplary timings of RTT measurement signals exchanged between a base station (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein), according to other aspects of the disclosure. In particular,1202-1204ofFIG.12denote portions of frame delay that are associated with a Rx-Tx differences as measured at the gNB and UE, respectively. As will be appreciated from the disclosure above, NR native positioning technologies supported in 5G NR include DL-only positioning schemes (e.g., DL-TDOA, DL-AoD, etc.), UL-only positioning schemes (e.g., UL-TDOA, UL-AoA), and DL+UL positioning schemes (e.g., RTT with one or more neighboring base stations, or multi-RTT). In addition, Enhanced Cell-ID (E-CID) based on radio resource management (RRM) measurements is supported in 5G NR Rel-16. Differential RTT is another positioning scheme, whereby a difference between two RTT measurements (or measurement ranges) is used to generate a positioning estimate for a UE. As an example, RTT can be estimated between a UE and two gNBs. The positioning estimate for the UE can then be narrowed to the intersection of a geographic range that maps to these two RTTs (e.g., to a hyperbola). RTTs to additional gNBs (or to particular TRPs of such gNBs) can further narrow (or refine) the positioning estimate for the UE. In some designs, a positioning engine (e.g., at the UE, base station, or server/LMF) can select between whether RTT measurements are to be used to compute a positioning estimate using typical RTT or differential RTT. For example, if the positioning engine receives RTTs that are known to have already accounted for hardware group delays, then typical RTT positioning is performed (e.g., as shown inFIGS.6-7). Otherwise, in some designs, differential RTT is performed so that the hardware group delay can be canceled out. In some designs where the positioning engine is implemented at the network-side (e.g., gNB/LMU/eSMLC/LMF), the group hardware delay at the UE is not known (and vice versa). FIG.13illustrates a diagram1300depicting a satellite-based positioning scheme. InFIG.13, a GPS satellite1302, a GPS receiver1306and a GPS receiver1308are depicted. GPS satellite1302transmits a GPS signal on a respective path1310with phase Paq(t1) to GPS receiver1306, and on a respective path1312with phase Par(t1) to GPS receiver1308, whereby Δp=Δρ+Δdρ−cΔdT+Δdion+Δdtrop+εΔpEquation (2) Δφ=Δρ+dρ+cΔdT+λΔN−Δdion+Δdtrop+εΔφEquation (3) whereby dt denotes satellite clock error, dρ denotes satellite orbital error, diondenotes an ionospheric effect and dtropdenotes a tropospheric effect. InFIG.13, GPS receiver1306may correspond to a base station and GPS receiver1308may correspond to a rover station. In this case, the base station measurement is subtracted from the rover station measurement for the same satellite1302so as to eliminate satellite clock error dt, reduce the satellite orbital error dρ as a function baseline length, and reduce the ionospheric and tropospheric effect, dionand dtropas a function of baseline length. FIG.14illustrates a diagram1400depicting another satellite-based positioning scheme. InFIG.14, a GPS satellite1402, a GPS satellite1404, and a GPS receiver1406are depicted. GPS satellite1402transmits a GPS signal on a respective path1410with phase Paq(t1) to GPS receiver1406, and GPS satellite1404transmits a GPS signal on a respective path1414with phase Pbq(t1) to GPS receiver1406, whereby ∇p=∇ρ+∇dρ+c∇dt+∇dion+∇dtrop+ε∇pEquation (4) ∇φ=∇ρ+∇dρ+c∇dt+λ∇N−∇dion+∇dtrop+ε∇φEquation (5) InFIG.14, a satellite measurement may be subtracted from a base satellite measurement for the same GPS receiver so as to eliminate satellite clock error dT, and to reduce a common hardware bias in the GPS receiver1406. FIG.15illustrates a diagram1500depicting another satellite-based positioning scheme. InFIG.15, a GPS satellite1502, a GPS satellite1504, a GPS receiver1506and a GPS receiver1508are depicted. GPS satellite1502transmits a GPS signal on a first path1510with phase Paq(t1) to GPS receiver1506, and on a second path1512with phase Par(t1) to GPS receiver1508. GPS satellite1504transmits a GPS signal on a first path1514with phase Pbq(t1) to GPS receiver1506, and on a second path1516with phase Pbr(t1) to GPS receiver1508, whereby ∇Δp=∇Δρ+∇Δdρ+∇Δdion+∇Δdtrop+ε∇ΔpEquation (4) ∇Δφ=∇Δρ+∇Δdρ−∇Δdion+∇Δdtrop+λ∇ΔN+ε∇ΔφEquation (5) InFIG.15, a base station measurement (e.g., GPS receiver1506) may be subtracted from a rover station measurement (e.g., GPS receiver1508) for the same satellite, and the difference between these measurements may then be taken from a base satellite (e.g., GPS satellite1502) and measurements at other satellites (e.g., GPS satellite1508), which may function to eliminate the satellite clock error dt and receiver clock error dT, and reduce the satellite orbital error dρ, the ionospheric and tropospheric effect, dionand dtrop. ∇ΔN denotes the double differenced integer ambiguity. For a 20-30 km baseline, the residual error may typically be less than ½ cycle. While the UE hardware group delay cancels out with differential RTT, the residual gNB group delay (which may be denoted as GDdiff,gNB_2_1for gNBs 1 and 2, where gNB 1 may correspond to a reference gNB) may remain, which limits the accuracy of RTT-based positioning, e.g.: GDdiff,gNB_2_1=GDgNB_2−GDgNB_1Equation (6) whereby GDgNB_2is the residual group delay at gNB 2, GDgNB_1is the residual group delay at the reference gNB (or gNB 1). GDgNB_1is common for all differential RTTs. Aspects of the disclosure are directed to a double-differential timing (e.g., RTT or TDOA) scheme, whereby two (or more) differential timing (e.g., RTT or TDOA) measurements are obtained for positioning of a target UE. For example, one of the differential timing (e.g., RTT or TDOA) measurements may be used to cancel out (or at least reduce) UE hardware group delay, while another one of the differential timing (e.g., RTT or TDOA) measurements between the UE and wireless nodes (e.g., gNBs, or anchor UEs, or a combination thereof) may be used to cancel out (or at least reduce) residual hardware group delay on the side of the wireless nodes (e.g., gNBs, or anchor UEs, or a combination thereof). Such aspects may provide various technical advantages, such as more accurate UE position estimation. Moreover, as used herein, a “hardware group delay” includes a timing group delay that is at least partially attributable to hardware (e.g., which may vary based on environmental conditions such as temperature, humidity, etc.), but may optionally include other timing delay(s) attributable to factors such as software, firmware, etc. A double-differential (DD) RTT (DD-RTT) scheme is described below with respect toFIGS.16-19. FIG.16illustrates an exemplary process1600of wireless communication, according to aspects of the disclosure. In an aspect, the process1600may be performed by a position estimation entity, which may correspond to a UE such as UE302(e.g., for UE-based positioning), a BS or gNB such as BS304(e.g., for LMF integrated in RAN), or a network entity306(e.g., core network component such as LMF). At1610, the position estimation entity (e.g., receiver312or322or352or362, data bus382, network interface(s)380or390, etc.) obtains a first differential RTT measurement based on a first RTT measurement between a UE and a first wireless node and a second RTT measurement between the UE and a second wireless node. In this case, the UE corresponds to a target UE for which a positioning estimate is desired, and the first and second wireless nodes have known locations. In some designs, the first and/or second wireless nodes correspond to gNBs, and in other designs, the first and/or second wireless nodes correspond to UEs (e.g., anchor UEs or reference UEs which are static or semi-static and/or for which an accurate positioning estimate have been recently acquired). At1620, the position estimation entity (e.g., receiver312or322or352or362, data bus382, network interface(s)380or390, etc.) obtains a second differential RTT measurement based on a third RTT measurement between a third wireless node and the first wireless node and a fourth RTT measurement between the third wireless node and the second wireless node. In some designs, the third wireless node need not be in wireless communication range with the UE. In some designs, the third wireless node corresponds to a gNB, and in other designs, the third wireless node may correspond to a UE (e.g., anchor UE or reference UE which is static or semi-static and/or for which an accurate positioning estimate has been recently acquired). At1630, the position estimation entity (e.g., positioning module342or388or389, processing system332or384or394, etc.) determines a positioning estimate of the UE based at least in part on the first and second differential RTT measurements. Algorithmic examples of the determination of1630are explained in more detail below. FIG.17illustrates an example implementation1700of the process1600ofFIG.16in accordance with an aspect of the disclosure. InFIG.17, a first wireless node1702, a second wireless node1704, a UE1706and a third wireless node1708are depicted. The first wireless node1702, the second wireless node1704, the third wireless node1708may alternatively be denoted as wireless nodes1,2and3, respectively, and correspond to the first, second and third wireless nodes as referenced with respect to the process1600ofFIG.16. InFIG.17, a first RTT measurement1710between the first wireless node1702and UE1706is denoted as RTT1_UE, a second RTT measurement1712between the second wireless node1704and UE1706is denoted as RTT2_UE, a third RTT measurement1714between the third wireless node1708and the first wireless node1702is denoted as RTT1_3, and a fourth RTT measurement1716between the third wireless node1708and the second wireless node1704is denoted as RTT2_3. The first through fourth RTT measurements1710-1716correspond to examples of the first through fourth RTT measurements described above with respect to the process16ofFIG.16. FIG.18illustrates an example implementation1800of the process1600ofFIG.16in accordance with another aspect of the disclosure.1802-1816ofFIG.18are similar to1702-1716ofFIG.17, respectively, except that the first wireless node1702, the second wireless node1704, and the third wireless node1708are more specifically illustrated as gNBs1802,1804and1808, respectively, inFIG.18.FIGS.17and18are otherwise the same, and as suchFIG.18will not be discussed further for the sake of brevity. FIG.19illustrates an example implementation1900of the process1600ofFIG.16in accordance with another aspect of the disclosure.1902-1916ofFIG.19are similar to1702-1716ofFIG.17, except that the first wireless node1702and the second wireless node1704are more specifically illustrated as gNBs1802and1804, respectively, inFIG.18, and the third wireless node1708is more specifically illustrated as UE1908inFIG.19.FIGS.17and19otherwise the same, and as suchFIG.19will not be discussed further for the sake of brevity. An example implementation of calculations that may be performed as part of the determination of1630ofFIG.16will now be described in more detail. In the example algorithms described below, position estimation is described with respect to a two-dimensional (2D) coordinate system including x and y coordinates for convenience of explanation, and other aspects may instead map to a three-dimensional (3D) coordinate system that further includes a z coordinate in other aspects. A differential hardware group delay between the first and second wireless nodes may be derived as follows: GDdiff,2_1=GD2−GD1=RTT2_UE−RTT1_UE−(T2_UE) Equation (7) whereby GD2denotes the hardware group delay of the second wireless node, GD1denotes the hardware group delay of the first wireless node (e.g., a reference wireless node, such as a reference gNB), and T2_UEdenotes a differential between a double propagation time between the second wireless node and the UE and a double propagation time between the first wireless node and the UE, e.g.: T2_UE=2*√{square root over ((x2−xUE)2+(y2−yUE)2)}/c−2*√{square root over ((x1−xUE)2+(y1−yUE)2)}/cEquation (8) whereby c corresponds to the speed of light, x2denotes an x location coordinate of the second wireless node, xUEdenotes an x location coordinate of the UE, y2denotes a y location coordinate of the second wireless node, yUEdenotes a y location coordinate of the UE, x1denotes an x location coordinate of the first wireless node, and y1denotes a y location coordinate of the first wireless node. GDdiff,2_1may further be expressed as follows: GDdiff,2_1=GD2−GD1=RTT2_3−RTT1_3−(T2_3) Equation (9) whereby T2_3denotes a differential between a double propagation time between the second wireless node and the third wireless node and a double propagation time between the first wireless node and the third wireless node, e.g.: T2_3=2*√{square root over ((x2−x3)2+(y2−y3)2)}/c−2*√{square root over ((x1−x3)2+(y1−y3)2)}/cEquation (10) whereby x3denotes an x location coordinate of the third wireless node, and y3denotes a y location coordinate of the third wireless node. The hardware group delay of the first and second wireless nodes can then be canceled out, as follows: T2_UE−T2_3=RTT2_UE−RTT1_UE−(RTT2_3−RTT1_3) Equation (11) Referring toFIG.16, in some designs, the first differential RTT measurement may be triggered by the position estimation entity separately from the second differential RTT measurement. In other words, RTT1_3and RTT2_3need not be performed jointly with RTT1_UEand RTT2_UE. In other designs, RTT1_3and RTT2_3may be performed jointly (or contemporaneously) with RTT1_UEand RTT2_UE. For example, if the third wireless node is static or semi-static, then older values for RTT1_3and RTT2_3can be leveraged for position estimation of the UE since the third wireless node is unlikely to have moved much (if at all) since those measurements were taken. Accordingly, in some designs, the first differential RTT measurement may be triggered at a first frequency or based on a first triggering event, and the second differential RTT measurement may be triggered at a second frequency or based on a second triggering event. In some designs, the first differential RTT measurement may be triggered in response to a determination to perform the positioning estimate of the UE, and the second differential RTT measurement is triggered in response to a determination to calibrate a hardware group delay of the first wireless node, the second wireless node, or both. In other designs, the second differential RTT measurement may be triggered by the determination to perform the positioning estimate of the UE (or put another way, the second differential RTT measurement may be triggered by the first differential RTT measurement). As noted above, the hardware group delay of the first and/or second wireless nodes need not necessarily be calibrated for each UE position estimation (e.g., especially if the third wireless node is static or semi-static). Referring toFIG.16, in some designs, the first, second and third wireless nodes are associated with respective known locations before the determination of the position estimate. In some designs, the first, second and third wireless nodes comprise one or more base stations, one or more anchor UEs, or a combination thereof. In some designs, the first, second and third wireless nodes each correspond to a respective base station (e.g., as shown inFIG.18). In an example where the first, second and third wireless nodes are fixed nodes such as base stations, the third RTT measurement may be based on one or more PRSs exchanged between the first and third wireless nodes on one or more fixed (or default) beams, and the fourth RTT measurement is based on at least one PRS exchanged between the second and third wireless nodes on at least one fixed (or default) beam, or a combination thereof. In other designs, the first, second and third wireless nodes may each correspond to a respective UE. In other designs, the first and second wireless nodes corresponds to base stations and the third wireless node corresponds to an anchor UE associated with a known location (e.g., as shown inFIG.19). In some designs, positioning resources allocated for determination of a location of the anchor UE are greater than positioning resources used for determination of the positioning estimate of the UE (e.g., to ensure that the anchor UE has a very accurate position estimate since this position estimate is then leveraged for positioning of other UEs). Referring toFIG.16, in some designs, the third RTT measurement may be based on a first PRS from the third wireless node to the first wireless node and a second PRS from the first wireless node to the third wireless node. In some designs, the first and second PRSs are associated with the same PRS type. In some designs, the first and second PRSs comprise at least one single symbol PRS, at least one multi-symbol PRS (e.g., such as a legacy PRS), or a combination thereof. In some designs, the fourth RTT measurement is based on a third PRS from the third wireless node to the second wireless and a fourth PRS from the second wireless node to the third wireless node. The first PRS may either be the same or different from the third PRS (e.g., in other words, in some cases, the same PRS can be measured by both the first and second wireless nodes), while the first and second PRSs are different. In some designs, the position estimation entity may transmit a message to the first and third wireless nodes that indicates whether the first PRS follows the second PRS or whether the second PRS follows the first PRS. In some designs, the position estimation entity may transmit a message to the first and third wireless nodes that indicates a PRS resource to be used for an initial PRS of the third RTT measurement (e.g., since each PRS may be associated with a specific Tx gNB and one or multiple Rx gNB). In some designs, the same type of PRS could be used in the bidirectional transmission, e.g., one class of PRS defined, rather PRS and SRS as in the Uu interface. Referring toFIG.16, in some designs, each PRS (e.g., PRS ID) may be associated with a pair of gNBs (TRP IDs), e.g., each PRS is associated with specific Tx/Rx gNB. In a further example, each PRS may be configured from a specific frequency layer, which is associated with specific common parameters (e.g., center frequency, Start PRB, BW, SCS, CP type and comb size). Each PRS may be associated with one Tx gNB and one or multiple Rx gNB. In some designs, there may be an association between multiple PRS resources for the RTT measurement(s). In some designs, at least one PRS is for the transmission from gNB1 to gNB2, another PRS is for the transmission between gNB2 and gNB1. These pairs of PRS resources may be associated with one or multiple RTT measurement/report. In some designs, if the PRS is associated with one Tx gNB and one Rx gNB. In some designs, the PRS may be associated with a fixed narrow beam (e.g., as the gNBs may be fixed). In some designs, if the Rx gNB knows the relative direction between the two gNBs, the Rx gNB may derive the Rx beam based on that information, hence the beam management related search could be reduced or eliminated. Referring toFIG.16, in some designs, the first, second, third and fourth RTT measurements and/or the first and second differential RTT measurements are received at the position estimation entity via one or more measurement reports. In some designs, the one or more measurement reports each indicate, for a respective measurement, a transmission reception point (TRP) identifier a PRS source identifier, a PRS resource set ID, a frequency layer ID (e.g., indicating a respective BW and frequency on which the respective PRS measurement is conducted), a time stamp, or a combination thereof. Referring toFIG.16, in some designs, the first differential RTT measurement is based on at least one additional RTT measurement between the UE and at least one additional wireless node, the second differential RTT measurement is based on one or more additional RTT measurements between the third wireless node and one or more additional wireless nodes, or a combination thereof. For example, additional RTT(s) such as RTT4_UE, RTT5_UE, etc. can be used to derive the differential RTT measurement for UE 1, and/or additional RTT(s) such as RTT4_3, RTT5_3, etc. can be used to derive the differential RTT measurement for the third wireless node. Referring toFIG.16, in some designs, the position estimation entity may obtain a third differential RTT measurement based on a fifth RTT measurement between a fourth wireless node and the first wireless node and a sixth RTT measurement between the fourth wireless node and the second wireless node, the positioning estimate is further determined based at least in part on the third differential RTT measurement. In this case, the positioning estimate can be based on yet another double differential RTT measurements involving two other differential RTT measurements for a different pair of wireless nodes (e.g., a different pair of gNBs). Referring toFIG.16, in some designs, the position estimation entity may receive, from the first wireless node, the second wireless node, or both, an indication of a first hardware group delay calibration capability, and the second differential RTT measurement is performed in response to the first hardware group delay calibration capability. For example, the first hardware group delay calibration capability may be a dynamic indication or a static or semi-static indication. In some designs, another positioning estimate for another UE may be determined based on a single differential RTT measurement based on wireless nodes involved with the another positioning estimate being associated with a second hardware group delay calibration capability that is more accurate than the first hardware group delay calibration capability. In other words, in some designs, multiple differential RTT measurements are used specifically for scenarios where some degree of hardware group delay calibration is desired between the first and second wireless nodes, and can be skipped in other scenarios (e.g., recent hardware group delay calibration is already known, etc.). Referring toFIG.16, the hardware group delay calibration capability may be indicated via a one-time capability report. For example, a respective wireless node (e.g., gNB) may report a high-accuracy group delay calibration capability, which may prompt the position estimation entity to skip a differential RTT measurement for hardware group delay calibration involving that respective wireless node. In another example, the hardware group delay calibration capability may be dynamically indicated. For example, the hardware group delay calibration error could change over some factors, for example, time, frequency, BW, temperature, etc. Hence, a respective wireless node (e.g., gNB) may dynamically indicate a respective accuracy level of hardware group delay calibration. In some designs, multiple levels of hardware group delay calibration accuracy may be defined, and a respective wireless node (e.g., gNB) may dynamically report a hardware group calibration accuracy level. For example, if a respective hardware group delay calibration error is large (e.g., above threshold), a respective wireless node may indicate that the LMF should include this respective wireless node in the double-differential RTT procedure. In another example, a respective wireless node (e.g., gNB) may dynamically indicate whether a double-differential RTT is needed without reporting its respective hardware group delay calibration accuracy level. In some designs, the position estimation entity (e.g., LMF) may classify two group of wireless nodes (e.g., gNBs) based on their capability of hardware group delay calibration. For example, a wireless node (e.g., gNB) with high accuracy hardware group delay calibration may conduct regular RTT or differential RTT based UE positioning, and a wireless node (e.g., gNB) with low accuracy hardware group delay calibration may conduct double-differential RTT-based UE positioning. Referring toFIG.16, in some designs, the position estimation entity may receive, from the first wireless node, the second wireless node, or both, a request to trigger the second differential RTT measurement for hardware group delay calibration. Referring toFIG.16, in some designs, the position estimation entity may select the third wireless node for hardware group delay calibration of the first and second wireless nodes via the second RTT differential measurement based on one or more parameters. In some designs, the one or more parameters may include channel conditions between the third wireless node and the first and second wireless nodes. In some designs, the selection of the third wireless node is predetermined if each of the first, second and third wireless node are stationary nodes. In other designs, the selection of the third wireless node is dynamic if one or more of the first, second and third wireless node are mobile nodes. However, such parameters can be used for wireless node selection even for fixed gNBs in addition to more mobile anchor UEs in some designs. For example, in a scenario where the first, second and third wireless node correspond to fixed gNBs in a dense deployment (e.g., urban environment), there could be blockage between the gNBs, especially in FR2. As noted above, the third wireless node (which may be deemed a “reference” wireless node which may be used to calibrate hardware group delay of two other wireless nodes) can correspond to any wireless node type (e.g., gNB or UE) with a known location. In case of a UE implementation for the third wireless node, this “reference UE” may be mobile and will generally remain less fixed in location as other wireless node types such as gNBs. Hence, compared to using gNBs as the third wireless node, reference UEs used for the third wireless node may be associated with more residual positioning error (e.g., due to a varying channel condition over time). WhileFIGS.16-19relate generally to DD-RTT schemes, in other designs, DD-TDOA schemes may also be implemented. In DD-TDOA, two single differences (SDs) (or RSTD if a single difference is taken at the receiver side) may be used to potentially eliminate or mitigate all timing errors (sync errors, group delays). DD-TDOA requires the measurements from the reference node(s) and prior knowledge of reference node(s)' location(s). FIG.20illustrates an example network configuration2000for a DD-TDOA scheme in accordance with an aspect of the disclosure. InFIG.20, a first wireless node2002, a second wireless node2004, a UE2006and a third wireless node2008are depicted. The first wireless node2002, the second wireless node2004, the third wireless node2008may alternatively be denoted as wireless nodes1,2and3, respectively. InFIG.20, a PRS2010is transmitted from wireless node1(2002) to UE2006, a PRS2012is transmitted from wireless node2(2004) to UE2006, a PRS2014is transmitted from wireless node1(2002) to wireless node3(2008), and a PRS2016is transmitted from wireless node2(2004) to wireless node3(2008). Referring toFIG.20, in some designs, SDs may be measured relative to the transmitter. For example, a first SD may be taken between TOAs of PRSs2010and2014and a second SD may be taken between TOAs of PRSs2012and2016. An SD may then be taken between the first and second SDs to derive the DD-TDOA offset. SDs relative to the transmitter side be used to eliminate or mitigate TRP synchronization errors, chip implementation discrepancies (e.g., manufacturer, reference, algorithms), BB to RF group delay (unknown), etc. Referring toFIG.20, in other designs, SDs may be measured relative to the receiver. For example, a first SD may be taken between TOAs of PRSs2010and2012and a second SD may be taken between TOAs of PRSs2014and2016. An SD may then be taken between the first and second SDs to derive the DD-TDOA offset. SDs relative to the receive side be used to eliminate or mitigate UE clock offsets, chip implementation discrepancies (e.g., manufacturer, reference, algorithms), BB to RF group delay (unknown), etc. In an example: mes_RSTD1,2UE−mes_RSTD1,2ref+genie_RSTD1,2ref=mes_RSTD1,2UE−TC1,2=genie_RSTD1,2UE+n where mes_RSTD1,2UEdenotes RSTD between PRSs2010-2012as measured at UE2006, mes_RSTD1,2refdenotes RSTD between PRSs2014-2016as measured at wireless node3(2008), genie_RSTD1,2refdenotes RSTD based on prior knowledge of locations of the wireless nodes1,2and3, TC1,2denotes a timing correction offset, genie_RSTD1,2UEdenotes corrected UE measurement, and n denotes measurement noise (e.g., TOA estimation noise, without timing error). WhileFIG.20depicts a DL-TDOA DD-TDOA procedure, in other designs, a sidelink TDOA (SL-TDOA) or UL-TDOA procedure may be implemented, depending on the device types of the wireless nodes1,2and/or3(e.g., if implemented as UEs, the RS-Ps may be characterized as SL RS-Ps or SL-PRS or SRS-P). To mitigate or eliminate timing errors, the timing measurements would ideally be aligned (e.g., both in time and RF chains). For example, timing errors for wireless nodes1and2(e.g., gNBs) might be different (due to clock drift or jitter) if wireless node3and the target UE perform their respective timing measurements at different times with a large time gap. In this case, the transmitter (Tx) timing correction may not be precise. In another example, the receiver (Rx) timing errors at the wireless node3and the target UE may be reduced or eliminated if the reception (and transmission) is performed with the same panel/beam or RF chain (e.g., in some time difference, the time difference may or may not be different across beams). Otherwise, the cancelation of Rx timing error may not be precise. Aspects of the disclosure are thereby directed to implementing at least one shared requirement for both of a first differential timing (DT) procedure of a double differential timing (DDT) procedure and a second DT procedure of the DDT procedure. As will be described below in more detail, the at least one shared requirement may correspond to a timing requirement, an RF chain requirement, or a combination thereof. Such aspects may provide various technical advantages, such as improved accuracy for positioning estimates of UEs. FIG.21illustrates an exemplary process2100of wireless communication, according to aspects of the disclosure. In an aspect, the process2100may be performed by a position estimation entity, which may correspond to a UE such as UE302(e.g., for UE-based positioning), a BS or gNB such as BS304(e.g., for LMF integrated in RAN), or a network entity306(e.g., core network component such as LMF). Referring toFIG.21, at2110, the position estimation entity (e.g., processing system332or384or394, positioning module342or388or398, etc.) determines at least one shared requirement for both of a first differential timing (DT) procedure of a double differential timing (DDT) procedure and a second DT procedure of the DDT procedure, the first DT procedure based on timing measurements between a target user equipment (UE) and first and second wireless nodes, and the second DT procedure based on timing measurements between a reference wireless node and the first and second wireless nodes. Referring toFIG.21, at2120, the position estimation entity (e.g., transmitter314or324or354or364, data bus334or382, network interface(s)380or390, etc.) transmits, to at least the target UE and the reference wireless node, requests to perform the DDT procedure along with an indication of the at least one shared requirement for the DDT procedure. In some designs (e.g., for DD-RRT or DD-TDOA where the first and second wireless nodes are not already configured to transmit RS-Ps), requests to perform the DDT procedure may further be sent to the first and second wireless nodes (e.g., to prompt the first and second wireless nodes to measure RS-Ps from the target UE and reference wireless for RTT measurements in DD-RTT, or to transmit RS-Ps for TDOA measurement in case of DD-TDOA, or to measure RS-Ps for TDOA measurement in case of UL-TDOA). However, in other designs, the first and second wireless nodes may already be configured to transmit RS-Ps suitable for DL-TDOA measurement by the target UE and reference wireless node (e.g., periodic RS-P, SPS RS-P, etc.). In this case, the requests at2120need not be sent to the first and second wireless nodes because the first and second wireless nodes are already scheduled to transmit the RS-Ps. In some designs, the position estimation entity may correspond to the target UE, the reference wireless node, or one of the first and second wireless nodes. In this case, the transmission at2120to this particular component may correspond to an internal transmission of data between logical components over a respective data bus, etc., rather than an external wireless or backhaul transmission. Referring toFIG.21, in some designs, the IE NR-DL-TDOA-RequestLocationInformation is used by the position estimation entity (e.g., LMF) to request NR DL-TDOA location measurements from a target device. In an example, the IE NR-DL-TDOA-RequestLocationInformation may be used to implement some or all of the requests at2120. Referring toFIG.21, in some designs, the DDT procedure corresponds to a DD time difference of arrival (DD-TDOA) procedure, the first and second DT procedures correspond to first and second differential TDOA procedures, respectively, and the respective timing measurements associated with the first and second differential TDOA procedures correspond to TDOA measurements. In an example, the DD-TDOA procedure may correspond to UL-TDOA, DL-TDOA or SL-TDOA-based DD-TDOA procedure. Referring toFIG.21, in some designs (e.g., as inFIGS.16-19), the DDT procedure corresponds to a DD round trip time (DD-RTT) procedure, the first and second DT procedures correspond to first and second differential RTT procedures, respectively, and the respective timing measurements associated with the first and second differential RTT procedures correspond to RTT measurements Referring toFIG.21, in some designs, the at least one shared requirement includes a timing requirement. For example, the timing requirement may include:one or more reference signals for positioning (RS-Ps) to be measured within one or more timing windows (e.g., designations of specific RS-P(s) and specific timing window(s)), ora duration of the one or more timing windows (e.g., defined in ms, or a number of slots, or a number of symbols, etc.), orin a scenario where the one or more timing windows includes multiple periodic timing windows, a periodicity of the multiple periodic timing windows (e.g., in other designs, multiple aperiodic timing windows may be defined without such a periodicity), oran instance or range of instances associated with multiple RS-P repetitions (e.g., PRS instance, SRS-P instance, etc.), orone or more specific reference signal timing difference (RSTDs) associated with one or more specific RS-Ps (e.g., such that the same measurements are made at both the target UE and the reference wireless node for DL-TDOA or RTT, etc.), ora combination thereof. Referring toFIG.21, in some designs, the at least one shared requirement includes a radio frequency (RF) chain requirement. For example, for beams associated with the first and second wireless nodes, the RF chain requirement may include the same reference signal timing difference (RSTD) pair being based on the same set of RS-P resources, resource set, and/or set of panels for both the first and second DT procedures, or the same receive-transmit (Rx-Tx) time difference being based on the same set of RS-P resources, resource set, and/or set of panels for both the first and second DT procedures, or a combination thereof. In another example, for beams associated with the target UE and the reference wireless node, the RF chain requirement includes a list of reference signal timing difference (RSTD) and/or receive-transmit (Rx-Tx) measurements required to be measured with a particular RF chain and/or consistency group that includes components associated with the same group delay or with group delays that fall inside of a group delay range. Referring toFIG.21, in a more specific example, for specific RSTD or RTT Rx-Tx timing errors, the position estimation entity (e.g., LMF) can send measurement requests to the target UE and the reference wireless node ref with constraints of gNB beam (e.g., DL-PRS resources) and the beams of the target UE and reference wireless node, respectively. For example, these constraints may include designation of the gNB beam (e.g., PRS resources), a requirement that both the target UE and reference wireless node should measure the same RSTD pair or Rx-Tx time difference based on same PRS resource(s), resource-set, and/or panels (e.g., this could guarantee that Tx/Rx beams and associated calibration errors at gNB sides are the same across reference wireless node and the target UE and UEs), and designation of the beams of the target UE and reference wireless node, respectively. With respect to the beam designation, the constraints may further include a list of RSTD/Rx-Tx measurements required to be measured with one specific RF chain (e.g., one panel, one Rx beam, one consistency group which may include any grouping of components associated with the same or similar calibration errors, although the consistency group may alternatively be determined and selected at the target UE and reference wireless node rather than designated as a constraint by the LMF, etc.). Referring toFIG.21, in some designs, at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds to a base station, or wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds a reference UE associated with a known location, or a combination thereof (e.g., a mixture of UE(s) and gNB(s) participate in the DDT procedure). In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause. Implementation examples are described in the following numbered clauses: Clause 1. A method of operating a position estimation entity, comprising: determining at least one shared requirement for both of a first differential timing (DT) procedure of a double differential timing (DDT) procedure and a second DT procedure of the DDT procedure, the first DT procedure based on timing measurements between a target user equipment (UE) and first and second wireless nodes, and the second DT procedure based on timing measurements between a reference wireless node and the first and second wireless nodes; and transmitting, to at least the target UE and the reference wireless node, requests to perform the DDT procedure along with an indication of the at least one shared requirement for the DDT procedure. Clause 2. The method of clause 1, wherein the DDT procedure corresponds to a DD time difference of arrival (DD-TDOA) procedure, the first and second DT procedures correspond to first and second differential TDOA procedures, respectively, and the respective timing measurements associated with the first and second differential TDOA procedures correspond to TDOA measurements, or wherein the DDT procedure corresponds to a DD round trip time (DD-RTT) procedure, the first and second DT procedures correspond to first and second differential RTT procedures, respectively, and the respective timing measurements associated with the first and second differential RTT procedures correspond to RTT measurements. Clause 3. The method of any of clauses 1 to 2, wherein the at least one shared requirement comprises a timing requirement. Clause 4. The method of clause 3, wherein the timing requirement comprises: one or more reference signals for positioning (RS-Ps) to be measured within one or more timing windows, or a duration of the one or more timing windows, or in a scenario where the one or more timing windows includes multiple periodic timing windows, a periodicity of the multiple periodic timing windows, or an instance or range of instances associated with multiple RS-P repetitions, or one or more specific reference signal timing difference (RSTDs) associated with one or more specific RS-Ps, or a combination thereof. Clause 5. The method of any of clauses 1 to 4, wherein the at least one shared requirement comprises a radio frequency (RF) chain requirement. Clause 6. The method of clause 5, wherein, for beams associated with the first and second wireless nodes, the RF chain requirement comprises: the same reference signal timing difference (RSTD) pair being based on the same set of RS-P resources, resource set, and/or set of panels for both the first and second DT procedures, or the same receive-transmit (Rx-Tx) time difference being based on the same set of RS-P resources, resource set, and/or set of panels for both the first and second DT procedures, or a combination thereof. Clause 7. The method of any of clauses 5 to 6, wherein, for beams associated with the target UE and the reference wireless node, the RF chain requirement comprises: a list of reference signal timing difference (RSTD) and/or receive-transmit (Rx-Tx) measurements required to be measured with a particular RF chain and/or consistency group comprised of components associated with the same group delay or with group delays that fall inside of a group delay range. Clause 8. The method of any of clauses 1 to 7, wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds to a base station, or wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds a reference UE associated with a known location, or a combination thereof. Clause 9. The method of any of clauses 1 to 8, further comprising: receiving measurement information associated with the DDT procedure; and determining a positioning estimate of the target UE based on the measurement information. Clause 10. The method of any of clauses 1 to 9, wherein the position estimation entity corresponds to the target UE or another UE, a base station, a core network component, a location server, a location management function, or a combination thereof. Clause 11. A position estimation entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine, by the at least one processor, at least one shared requirement for both of a first differential timing (DT) procedure of a double differential timing (DDT) procedure and a second DT procedure of the DDT procedure, the first DT procedure based on timing measurements between a target user equipment (UE) and first and second wireless nodes, and the second DT procedure based on timing measurements between a reference wireless node and the first and second wireless nodes; and cause the at least one transceiver to transmit, to at least the target UE and the reference wireless node, requests to perform the DDT procedure along with an indication of the at least one shared requirement for the DDT procedure. Clause 12. The position estimation entity of clause 11, wherein the DDT procedure corresponds to a DD time difference of arrival (DD-TDOA) procedure, the first and second DT procedures correspond to first and second differential TDOA procedures, respectively, and the respective timing measurements associated with the first and second differential TDOA procedures correspond to TDOA measurements, or wherein the DDT procedure corresponds to a DD round trip time (DD-RTT) procedure, the first and second DT procedures correspond to first and second differential RTT procedures, respectively, and the respective timing measurements associated with the first and second differential RTT procedures correspond to RTT measurements. Clause 13. The position estimation entity of any of clauses 11 to 12, wherein the at least one shared requirement comprises a timing requirement. Clause 14. The position estimation entity of clause 13, wherein the timing requirement comprises: one or more reference signals for positioning (RS-Ps) to be measured within one or more timing windows, or a duration of the one or more timing windows, or in a scenario where the one or more timing windows includes multiple periodic timing windows, a periodicity of the multiple periodic timing windows, or an instance or range of instances associated with multiple RS-P repetitions, or one or more specific reference signal timing difference (RSTDs) associated with one or more specific RS-Ps, or a combination thereof. Clause 15. The position estimation entity of any of clauses 11 to 14, wherein the at least one shared requirement comprises a radio frequency (RF) chain requirement. Clause 16. The position estimation entity of clause 15, wherein, for beams associated with the first and second wireless nodes, the RF chain requirement comprises: the same reference signal timing difference (RSTD) pair being based on the same set of RS-P resources, resource set, and/or set of panels for both the first and second DT procedures, or the same receive-transmit (Rx-Tx) time difference being based on the same set of RS-P resources, resource set, and/or set of panels for both the first and second DT procedures, or a combination thereof. Clause 17. The position estimation entity of any of clauses 15 to 16, wherein, for beams associated with the target UE and the reference wireless node, the RF chain requirement comprises: a list of reference signal timing difference (RSTD) and/or receive-transmit (Rx-Tx) measurements required to be measured with a particular RF chain and/or consistency group comprised of components associated with the same group delay or with group delays that fall inside of a group delay range. Clause 18. The position estimation entity of any of clauses 11 to 17, wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds to a base station, or wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds a reference UE associated with a known location, or a combination thereof. Clause 19. The position estimation entity of any of clauses 11 to 18, wherein the at least one processor is further configured to: receive, via the at least one transceiver, measurement information associated with the DDT procedure; and determine a positioning estimate of the target UE based on the measurement information. Clause 20. The position estimation entity of any of clauses 11 to 19, wherein the position estimation entity corresponds to the target UE or another UE, a base station, a core network component, a location server, a location management function, or a combination thereof Clause 21. A position estimation entity, comprising: means for determining at least one shared requirement for both of a first differential timing (DT) procedure of a double differential timing (DDT) procedure and a second DT procedure of the DDT procedure, the first DT procedure based on timing measurements between a target user equipment (UE) and first and second wireless nodes, and the second DT procedure based on timing measurements between a reference wireless node and the first and second wireless nodes; and means for transmitting, to at least the target UE and the reference wireless node, requests to perform the DDT procedure along with an indication of the at least one shared requirement for the DDT procedure. Clause 22. The position estimation entity of clause 21, wherein the DDT procedure corresponds to a DD time difference of arrival (DD-TDOA) procedure, the first and second DT procedures correspond to first and second differential TDOA procedures, respectively, and the respective timing measurements associated with the first and second differential TDOA procedures correspond to TDOA measurements, or wherein the DDT procedure corresponds to a DD round trip time (DD-RTT) procedure, the first and second DT procedures correspond to first and second differential RTT procedures, respectively, and the respective timing measurements associated with the first and second differential RTT procedures correspond to RTT measurements. Clause 23. The position estimation entity of any of clauses 21 to 22, wherein the at least one shared requirement comprises a timing requirement. Clause 24. The position estimation entity of any of clauses 21 to 23, wherein the at least one shared requirement comprises a radio frequency (RF) chain requirement. Clause 25. The position estimation entity of any of clauses 21 to 24, wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds to a base station, or wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds a reference UE associated with a known location, or a combination thereof. Clause 26. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to: determine at least one shared requirement for both of a first differential timing (DT) procedure of a double differential timing (DDT) procedure and a second DT procedure of the DDT procedure, the first DT procedure based on timing measurements between a target user equipment (UE) and first and second wireless nodes, and the second DT procedure based on timing measurements between a reference wireless node and the first and second wireless nodes; and transmit, to at least the target UE and the reference wireless node, requests to perform the DDT procedure along with an indication of the at least one shared requirement for the DDT procedure. Clause 27. The non-transitory computer-readable medium of clause 26, wherein the DDT procedure corresponds to a DD time difference of arrival (DD-TDOA) procedure, the first and second DT procedures correspond to first and second differential TDOA procedures, respectively, and the respective timing measurements associated with the first and second differential TDOA procedures correspond to TDOA measurements, or wherein the DDT procedure corresponds to a DD round trip time (DD-RTT) procedure, the first and second DT procedures correspond to first and second differential RTT procedures, respectively, and the respective timing measurements associated with the first and second differential RTT procedures correspond to RTT measurements. Clause 28. The non-transitory computer-readable medium of any of clauses 26 to 27, wherein the at least one shared requirement comprises a timing requirement. Clause 29. The non-transitory computer-readable medium of any of clauses 26 to 28, wherein the at least one shared requirement comprises a radio frequency (RF) chain requirement. Clause 30. The non-transitory computer-readable medium of any of clauses 26 to 29, wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds to a base station, or wherein at least one of the first wireless node, the second wireless node and/or the reference wireless node corresponds a reference UE associated with a known location, or a combination thereof. Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The methods, sequences and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. | 155,806 |
11943739 | DETAILED DESCRIPTION The configuration, operation, and other features of the present disclosure will readily be understood with embodiments of the present disclosure described with reference to the attached drawings. Embodiments of the present disclosure as set forth herein are examples in which the technical features of the present disclosure are applied to a 3rd generation partnership project (3GPP) system. While embodiments of the present disclosure are described in the context of long term evolution (LTE) and LTE-advanced (LTE-A) systems, they are purely exemplary. Therefore, the embodiments of the present disclosure are applicable to any other communication system as long as the above definitions are valid for the communication system. The term, base station (BS) may be used to cover the meanings of terms including remote radio head (RRH), evolved Node B (eNB or eNode B), transmission point (TP), reception point (RP), relay, and so on. The 3GPP communication standards define downlink (DL) physical channels corresponding to resource elements (REs) carrying information originated from a higher layer, and DL physical signals which are used in the physical layer and correspond to REs which do not carry information originated from a higher layer. For example, physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), physical multicast channel (PMCH), physical control format indicator channel (PCFICH), physical downlink control channel (PDCCH), and physical hybrid ARQ indicator channel (PHICH) are defined as DL physical channels, and reference signals (RSs) and synchronization signals (SSs) are defined as DL physical signals. An RS, also called a pilot signal, is a signal with a predefined special waveform known to both a gNode B (gNB) and a user equipment (UE). For example, cell specific RS, UE-specific RS (UE-RS), positioning RS (PRS), and channel state information RS (CSI-RS) are defined as DL RSs. The 3GPP LTE/LTE-A standards define uplink (UL) physical channels corresponding to REs carrying information originated from a higher layer, and UL physical signals which are used in the physical layer and correspond to REs which do not carry information originated from a higher layer. For example, physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), and physical random access channel (PRACH) are defined as UL physical channels, and a demodulation reference signal (DMRS) for a UL control/data signal, and a sounding reference signal (SRS) used for UL channel measurement are defined as UL physical signals. In the present disclosure, the PDCCH/PCFICH/PHICH/PDSCH refers to a set of time-frequency resources or a set of REs, which carry downlink control information (DCI)/a control format indicator (CFI)/a DL acknowledgement/negative acknowledgement (ACK/NACK)/DL data. Further, the PUCCH/PUSCH/PRACH refers to a set of time-frequency resources or a set of REs, which carry UL control information (UCI)/UL data/a random access signal. In the present disclosure, particularly a time-frequency resource or an RE which is allocated to or belongs to the PDCCH/PCFICH/PHICH/PDSCH/PUCCH/PUSCH/PRACH is referred to as a PDCCH RE/PCFICH RE/PHICH RE/PDSCH RE/PUCCH RE/PUSCH RE/PRACH RE or a PDCCH resource/PCFICH resource/PHICH resource/PDSCH resource/PUCCH resource/PUSCH resource/PRACH resource. Hereinbelow, if it is said that a UE transmits a PUCCH/PUSCH/PRACH, this means that UCI/UL data/a random access signal is transmitted on or through the PUCCH/PUSCH/PRACH. Further, if it is said that a gNB transmits a PDCCH/PCFICH/PHICH/PDSCH, this means that DCI/control information is transmitted on or through the PDCCH/PCFICH/PHICH/PDSCH. Hereinbelow, an orthogonal frequency division multiplexing (OFDM) symbol/carrier/subcarrier/RE to which a CRS/DMRS/CSI-RS/SRS/UE-RS is allocated to or for which the CRS/DMRS/CSI-RS/SRS/UE-RS is configured is referred to as a CRS/DMRS/CSI-RS/SRS/UE-RS symbol/carrier/subcarrier/RE. For example, an OFDM symbol to which a tracking RS (TRS) is allocated or for which the TRS is configured is referred to as a TRS symbol, a subcarrier to which a TRS is allocated or for which the TRS is configured is referred to as a TRS subcarrier, and an RE to which a TRS is allocated or for which the TRS is configured is referred to as a TRS RE. Further, a subframe configured to transmit a TRS is referred to as a TRS subframe. Further, a subframe carrying a broadcast signal is referred to as a broadcast subframe or a PBCH subframe, and a subframe carrying a synchronization signal (SS) (e.g., a primary synchronization signal (PSS) and/or a secondary synchronization signal (SSS)) is referred to as an SS subframe or a PSS/SSS subframe. An OFDM symbol/subcarrier/RE to which a PSS/SSS is allocated or for which the PSS/SSS is configured is referred to as a PSS/SSS symbol/subcarrier/RE. In the present disclosure, a CRS port, a UE-RS port, a CSI-RS port, and a TRS port refer to an antenna port configured to transmit a CRS, an antenna port configured to transmit a UE-RS, an antenna port configured to transmit a CSI-RS, and an antenna port configured to transmit a TRS, respectively. Antenna port configured to transmit CRSs may be distinguished from each other by the positions of REs occupied by the CRSs according to CRS ports, antenna ports configured to transmit UE-RSs may be distinguished from each other by the positions of REs occupied by the UE-RSs according to UE-RS ports, and antenna ports configured to transmit CSI-RSs may be distinguished from each other by the positions of REs occupied by the CSI-RSs according to CSI-RS ports. Therefore, the term CRS/UE-RS/CSI-RS/TRS port is also used to refer to a pattern of REs occupied by a CRS/UE-RS/CSI-RS/TRS in a predetermined resource area. FIG.1is a view illustrating an example of a network architecture of an NR system. The structure of the NR system broadly includes a next-generation radio access network (NG-RAN) and a next-generation core (NGC) network. The NGC is also referred to as a 5GC. Referring toFIG.1, the NG-RAN includes gNBs that provide a UE with user plane protocol (e.g., SDAP, PDCP, RLC, MAC, and PHY) and control plane protocol (e.g., RRC, PDCP, RLC, MAC, and PHY) terminations. The gNBs are interconnected through an Xn interface. The gNBs are connected to the NGC through an NG interface. For example, the gNBs are connected to a core network node having an access and mobility management function (AMF) through an N2 interface, which is one of interfaces between the gNBs and the NGC and to a core network node having a user plane function (UPF) through an N3 interface, which is another interface between the gNB and the NGC. The AMF and the UPF may be implemented by different core network devices or may be implemented by one core network device. In the RAN, signal transmission/reception between a BS and a UE is performed through a radio interface. For example, signal transmission/reception between the BS and the UE in the RAN is performed through a physical resource (e.g., a radio frequency (RF)). In contrast, signal transmission/reception between the gNB and the network functions (e.g., AMF and UPF) in the core network may be performed through physical connection (e.g., optical cable) between the core network nodes or through logical connection between the core network functions, rather than through the radio interface. The various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure described in this document may be applied to, but not limited to, various fields that require wireless communication/connections (e.g., 5G communication/connections) between devices. Hereinafter, description will be given in detail with reference to the accompanying drawings. In the following drawings/description, the same reference numerals may denote the same or corresponding hardware blocks, software blocks, or functional blocks unless specified otherwise. FIG.2illustrates a communication system1applicable to the present disclosure. Referring toFIG.2, the communication system1applicable to the present disclosure includes wireless devices, BSs, and a network. Herein, the wireless device represents a device performing communication based on a radio access technology (e.g., 5G NR, LTE, etc.) and may be referred to as a communication/radio/5G device. The wireless devices may include, but not limited to, a robot100a, vehicles100b-1and100b-2, an extended reality (XR) device100c, a hand-held device100d, a home appliance100e, an Internet of things (IoT) device100f, and an artificial intelligence (AI) device/server400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality/virtual reality/mixed reality (AR/VR/MR) device and be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in vehicles, a television (TV), a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smart meter. For example, the network and BSs may be implemented as wireless devices, and a specific wireless device200amay operate as a BS/network node for other wireless devices. The wireless devices100ato100fmay be connected to the network300via the BSs200. An AI technology may be applied to the wireless devices100ato100f, and the wireless devices100ato100fmay be connected to the AI server400via the network300. The network300may include a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices100ato100fmay communicate with each other through the BSs/network200/300, the wireless devices100ato100fmay perform direct communication (e.g., sidelink communication) with each other without assistance from the BSs/network200/300. For example, the vehicles100b-1and100b-2may perform direct communication (e.g. vehicle-to-vehicle/vehicle-to-everything (V2V/V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices100ato100f. Wireless communication/connections150a,150b, or150cmay be established between the wireless devices100ato100fand BSs200or between one BS200and another BS200. Herein, the wireless communication/connections may be established through various radio access technologies (e.g., 5G NR) such as UL/DL communication150a, sidelink communication150b(or device-to-device (D2D) communication), or inter-BS communication (e.g. relay, integrated access backhaul (IAB), etc.). The wireless devices and BSs may transmit/receive radio signals to/from each other through the wireless communication/connections150ato150c. For example, signals may be transmitted/received over various physical channels for the wireless communication/connections150ato150c. To this end, at least a part of various configuration information configuring processes, signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), and resource allocating processes for radio signal transmission/reception may be performed based on various proposals of the present disclosure. FIG.3illustrates control-plane and user-plane protocol stacks in a radio interface protocol architecture conforming to a 3GPP wireless access network standard between a UE and an evolved UMTS terrestrial radio access network (E-UTRAN). The control plane is a path in which the UE and the E-UTRAN transmit control messages to manage calls, and the user plane is a path in which data generated from an application layer, for example, voice data or Internet packet data is transmitted. A physical (PHY) layer at layer 1 (L1) provides information transfer service to its higher layer, a medium access control (MAC) layer. The PHY layer is connected to the MAC layer via transport channels. The transport channels deliver data between the MAC layer and the PHY layer. Data is transmitted on physical channels between the PHY layers of a transmitter and a receiver. The physical channels use time and frequency as radio resources. Specifically, the physical channels are modulated in orthogonal frequency division multiple access (OFDMA) for downlink (DL) and in single carrier frequency division multiple access (SC-FDMA) for uplink (UL). The MAC layer at layer 2 (L2) provides service to its higher layer, a radio link control (RLC) layer via logical channels. The RLC layer at L2 supports reliable data transmission. RLC functionality may be implemented in a function block of the MAC layer. A packet data convergence protocol (PDCP) layer at L2 performs header compression to reduce the amount of unnecessary control information and thus efficiently transmit Internet protocol (IP) packets such as IP version 4 (IPv4) or IP version 6 (IPv6) packets via an air interface having a narrow bandwidth. A radio resource control (RRC) layer at the lowest part of layer 3 (or L3) is defined only on the control plane. The RRC layer controls logical channels, transport channels, and physical channels in relation to configuration, reconfiguration, and release of radio bearers. A radio bearer refers to a service provided at L2, for data transmission between the UE and the E-UTRAN. For this purpose, the RRC layers of the UE and the E-UTRAN exchange RRC messages with each other. If an RRC connection is established between the UE and the E-UTRAN, the UE is in RRC Connected mode and otherwise, the UE is in RRC Idle mode. A Non-Access Stratum (NAS) layer above the RRC layer performs functions including session management and mobility management. DL transport channels used to deliver data from the E-UTRAN to UEs include a broadcast channel (BCH) carrying system information, a paging channel (PCH) carrying a paging message, and a shared channel (SCH) carrying user traffic or a control message. DL multicast traffic or control messages or DL broadcast traffic or control messages may be transmitted on a DL SCH or a separately defined DL multicast channel (MCH). UL transport channels used to deliver data from a UE to the E-UTRAN include a random access channel (RACH) carrying an initial control message and a UL SCH carrying user traffic or a control message. Logical channels that are defined above transport channels and mapped to the transport channels include a broadcast control channel (BCCH), a paging control channel (PCCH), a Common Control Channel (CCCH), a multicast control channel (MCCH), a multicast traffic channel (MTCH), etc. FIG.4illustrates physical channels and a general method for transmitting signals on the physical channels in the 3GPP system. When a UE is powered on or enters a new cell, the UE performs initial cell search (S401). The initial cell search involves acquisition of synchronization to an eNB. Specifically, the UE synchronizes its timing to the eNB and acquires a cell identifier (ID) and other information by receiving a primary synchronization channel (P-SCH) and a secondary synchronization channel (S-SCH) from the eNB. Then the UE may acquire information broadcast in the cell by receiving a physical broadcast channel (PBCH) from the eNB. During the initial cell search, the UE may monitor a DL channel state by receiving a downlink reference signal (DL RS). After the initial cell search, the UE may acquire detailed system information by receiving a physical downlink control channel (PDCCH) and receiving a physical downlink shared channel (PDSCH) based on information included in the PDCCH (S402). If the UE initially accesses the eNB or has no radio resources for signal transmission to the eNB, the UE may perform a random access procedure with the eNB (S403to S406). In the random access procedure, the UE may transmit a predetermined sequence as a preamble on a physical random access channel (PRACH) (S403and S405) and may receive a response message to the preamble on a PDCCH and a PDSCH associated with the PDCCH (S404and S406). In the case of a contention-based RACH, the UE may additionally perform a contention resolution procedure. After the above procedure, the UE may receive a PDCCH and/or a PDSCH from the eNB (S607) and transmit a physical uplink shared channel (PUSCH) and/or a physical uplink control channel (PUCCH) to the eNB (S208), which is a general DL and UL signal transmission procedure. Particularly, the UE receives downlink control information (DCI) on a PDCCH. Herein, the DCI includes control information such as resource allocation information for the UE. Different DCI formats are defined according to different usages of DCI. Control information that the UE transmits to the eNB on the UL or receives from the eNB on the DL includes a DL/UL acknowledgment/negative acknowledgment (ACK/NACK) signal, a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI), etc. In the 3GPP LTE system, the UE may transmit control information such as a CQI, a PMI, an RI, etc. on a PUSCH and/or a PUCCH. In the NR system, a method of using an ultra-high frequency band, that is, a millimeter frequency band at or above 6 GHz has been considered to transmit data to a plurality of users at a high transmission rate in a wide frequency band. In 3GPP, such a technology is called “NR”. In the present disclosure, it is referred to as the NR system. The NR system employs an OFDM transmission scheme or a similar transmission scheme. Specifically, the NR system may follow OFDM parameters different from those of LTE. The NR system may follow the legacy LTE/LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Further, one cell may support a plurality of numerologies. That is, UEs operating with different numerologies may coexist within one cell. Discontinuous Reception (DRX) Operation While the UE performs the above-described/proposed procedures and/or methods, the UE may perform the DRX operation. The UE for which DRX is configured may reduce power consumption by discontinuously receiving a DL signal. DRX may be performed in a radio resource control (RRC)_IDLE state, an RRC_INACTIVE state, or an RRC_CONNECTED state. DRX in the RRC_IDLE state and the RRC_INACTIVE state is used to discontinuously receive a paging signal. Hereinafter, DRX performed in the RRC_CONNECTED state will be described (RRC_CONNECTED DRX). FIG.5illustrates a DRX cycle (RRC_CONNECTED state). Referring toFIG.5, the DRX cycle includes an On-duration and an opportunity for DRX. The DRX cycle defines a time interval at which the On-duration is cyclically repeated. The On-Duration indicates a time duration that the UE monitors to receive a PDCCH. If DRX is configured, the UE performs PDCCH monitoring during the On-duration. If the PDCCH is successfully detected during PDCCH monitoring, the UE operates an inactivity timer and maintains an awoken state. On the other hand, if there is no PDCCH which has been successfully detected during PDCCH monitoring, the UE enters a sleep state after the On-duration is ended. Therefore, when DRX is configured, the UE may discontinuously perform PDCCH monitoring/reception in the time domain upon performing the above-described/proposed procedures and/or methods. For example, when DRX is configured, a PDCCH reception occasion (e.g., a slot having a PDCCH search space) in the present disclosure may be discontinuously configured according to DRX configuration. when DRX is not configured, PDCCH monitoring/reception may be continuously performed in the time domain. For example, when DRX is not configured, the PDCCH reception occasion (e.g., the slot having the PDCCH search space) in the present disclosure may be continuously configured. Meanwhile, PDCCH monitoring may be restricted in a time duration configured as a measurement gap regardless of whether DRX is configured or not. Table 1 illustrates a UE procedure related to DRX (RRC_CONNECTED state). Referring to Table 1, DRX configuration information is received through higher layer (e.g., RRC) signaling. Whether DRX is ON or OFF is controlled by a DRX command of a MAC layer. If DRX is configured, the UE may discontinuously perform PDCCH monitoring upon performing the above-described/proposed procedures and/or methods in the present disclosure, as illustrated inFIG.5. TABLE 1Type of signalsUE procedure1ststepRRC signallingReceive DRX configuration information(MAC-CellGroupConfig)2ndStepMAC CEReceive DRX command((Long) DRXcommand MACCE)3rdStep—Monitor a PDCCH during an on-durationof a DRX cycle Herein, MAC-CellGroupConfig includes configuration information needed to configure a MAC parameter for a cell group. MAC-CellGroupConfig may also include configuration information regarding DRX. For example, MAC-CellGroupConfig may include information for defining DRX as follows. —Value of drx-OnDurationTimer: defines the length of a starting duration of a DRX cycle.Value of drx-InactivityTimer: defines the length of a starting duration in which the UE is in an awoken state, after a PDCCH occasion in which a PDCCH indicating initial UL or DL data is detected.Value of drx-HARQ-RTT-TimerDL: defines the length of a maximum time duration until DL retransmission is received, after DL initial transmission is received.Value of drx-HARQ-RTT-TimerDL: defines the maximum duration until a grant for UL retransmission is received after reception of a grant for initial UL transmission.drx-LongCycleStartOffset: defines a time length and a starting time point of a DRX cycledrx-ShortCycle (optional): defines a time length of a short DRX cycle. Herein, if any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is operating, the UE performs PDCCH monitoring in every PDCCH occasion while maintaining an awoken state. Positioning Reference Signal (PRS) in LTE System Positioning may refer to determining the geographical position and/or velocity of the UE based on measurement of radio signals. Location information may be requested by and reported to a client (e.g., an application) associated with to the UE. The location information may also be requested by a client within or connected to a core network. The location information may be reported in standard formats such as formats for cell-based or geographical coordinates, together with estimated errors of the position and velocity of the UE and/or a positioning method used for positioning. For such positioning, a positioning reference signal (PRS) may be used. The PRS is a reference signal used to estimate the position of the UE. For example, in the LTE system, the PRS may be transmitted only in a DL subframe configured for PRS transmission (hereinafter, “positioning subframe”). If both a multimedia broadcast single frequency network (MBSFN) subframe and a non-MBSFN subframe are configured as positioning subframes, OFDM symbols of the MBSFN subframe should have the same cyclic prefix (CP) as subframe #0. If only MBSFN subframes are configured as the positioning subframes within a cell, OFDM symbols configured for the PRS in the MBSFN subframes may have an extended CP. The sequence of the PRS may be defined by Equation 1 below. rl,ns(m)=12(1-2·c(2m))+j12(1-2·c(2m+1)),m=0,1,…,2NRBmax,DL-1[Equation1] where nsdenotes a slot number in a radio frame and 1 denotes an OFDM symbol number in a slot. NRBmax,DLis represented as an integer multiple of NSCRBas the largest value among DL bandwidth configurations. NSCRBdenotes the size of a resource block (RB) in the frequency domain, for example, 12 subcarriers. c(i) denotes a pseudo-random sequence and may be initialized by Equation 2 below. cinit=228·└NIDPRS/512┘+210·(7·(ns+1)+l+1)·(NIDPRSmod 512)+1)+2·(NIDPRSmod 512)+NCP[Equation 2] Unless additionally configured by higher layers, NIDPRSis equal to NIDcell, and NCPis 1 for a normal CP and 0 for an extended CP. FIG.8illustrates an exemplary pattern to which a PRS is mapped in a subframe. As illustrated inFIG.8, the PRS may be transmitted through an antenna port6.FIG.8(a)illustrates mapping of the PRS in the normal CP andFIG.8(b)illustrates mapping of the PRS in the extended CP. The PRS may be transmitted in consecutive subframes grouped for position estimation. The subframes grouped for position estimation are referred to as a positioning occasion. The positioning occasion may consist of 1, 2, 4 or 6 subframe. The positioning occasion may occur periodically with a periodicity of 160, 320, 640 or 1280 subframes. A cell-specific subframe offset value may be defined to indicate the starting subframe of PRS transmission. The offset value and the periodicity of the positioning occasion for PRS transmission may be derived from a PRS configuration index as listed in Table 2 below. TABLE 2PRS configurationPRS periodicityPRS subframe offsetIndex (IPRS)(subframes)(subframes)0-159160IPRS160-479320IPRS-160480-1119640IPRS-4801120-23991280IPRS-11202400-24045IPRS-24002405-241410IPRS-24052415-243420IPRS-24152435-247440IPRS-24352475-255480IPRS-24752555-4095Reserved A PRS included in each positioning occasion is transmitted with constant power. A PRS in a certain positioning occasion may be transmitted with zero power, which is referred to as PRS muting. For example, when a PRS transmitted by a serving cell is muted, the UE may easily detect a PRS of a neighbor cell. The PRS muting configuration of a cell may be defined by a periodic muting sequence consisting of 2, 4, 8 or 16 positioning occasions. That is, the periodic muting sequence may include 2, 4, 8, or 16 bits according to a positioning occasion corresponding to the PRS muting configuration and each bit may have a value “0” or “1”. For example, PRS muting may be performed in a positioning occasion with a bit value of “0”. The positioning subframe is designed as a low-interference subframe so that no data is transmitted in the positioning subframe. Therefore, the PRS is not subjected to interference due to data transmission although the PRS may interfere with PRSs of other cells. UE Positioning Architecture in NR system FIG.7illustrates architecture of a 5G system applicable to positioning of a UE connected to an NG-RAN or an E-UTRAN. Referring toFIG.7, an AMF may receive a request for a location service associated with a particular target UE from another entity such as a gateway mobile location center (GMLC) or the AMF itself decides to initiate the location service on behalf of the particular target UE. Then, the AMF transmits a request for a location service to a location management function (LMF). Upon receiving the request for the location service, the LMF may process the request for the location service and then returns the processing result including the estimated position of the UE to the AMF. In the case of a location service requested by an entity such as the GMLC other than the AMF, the AMF may transmit the processing result received from the LMF to this entity. A new generation evolved-NB (ng-eNB) and a gNB are network elements of the NG-RAN capable of providing a measurement result for positioning. The ng-eNB and the gNB may measure radio signals for a target UE and transmits a measurement result value to the LMF. The ng-eNB may control several transmission points (TPs), such as remote radio heads, or PRS-only TPs for support of a PRS-based beacon system for E-UTRA. The LMF is connected to an enhanced serving mobile location center (E-SMLC) which may enable the LMF to access the E-UTRAN. For example, the E-SMLC may enable the LMF to support observed time difference of arrival (OTDOA), which is one of positioning methods of the E-UTRAN, using DL measurement obtained by a target UE through signals transmitted by eNBs and/or PRS-only TPs in the E-UTRAN. The LMF may be connected to an SUPL location platform (SLP). The LMF may support and manage different location services for target UEs. The LMF may interact with a serving ng-eNB or a serving gNB for a target UE in order to obtain position measurement for the UE. For positioning of the target UE, the LMF may determine positioning methods, based on a location service (LCS) client type, required quality of service (QoS), UE positioning capabilities, gNB positioning capabilities, and ng-eNB positioning capabilities, and then apply these positioning methods to the serving gNB and/or serving ng-eNB. The LMF may determine additional information such as accuracy of the location estimate and velocity of the target UE. The SLP is a secure user plane location (SUPL) entity responsible for positioning over a user plane. The UE may measure the position thereof using DL RSs transmitted by the NG-RAN and the E-UTRAN. The DL RSs transmitted by the NG-RAN and the E-UTRAN to the UE may include a SS/PBCH block, a CSI-RS, and/or a PRS. Which DL RS is used to measure the position of the UE may conform to configuration of LMF/E-SMLC/ng-eNB/E-UTRAN etc. The position of the UE may be measured by an RAT-independent scheme using different global navigation satellite systems (GNSSs), terrestrial beacon systems (TBSs), WLAN access points, Bluetooth beacons, and sensors (e.g., barometric sensors) installed in the UE. The UE may also contain LCS applications or access an LCS application through communication with a network accessed thereby or through another application contained therein. The LCS application may include measurement and calculation functions needed to determine the position of the UE. For example, the UE may contain an independent positioning function such as a global positioning system (GPS) and report the position thereof, independent of NG-RAN transmission. Such independently obtained positioning information may be used as assistance information of positioning information obtained from the network. Operation for UE Positioning FIG.8illustrates an implementation example of a network for UE positioning. When an AMF receives a request for a location service in the case in which the UE is in connection management (CM)-IDLE state, the AMF may make a request for a network triggered service in order to establish a signaling connection with the UE and to assign a specific serving gNB or ng-eNB. This operation procedure is omitted inFIG.8. In other words, inFIG.8, it may be assumed that the UE is in a connected mode. However, the signaling connection may be released by an NG-RAN as a result of signaling and data inactivity while a positioning procedure is still ongoing. An operation procedure of the network for UE positioning will now be described in detail with reference toFIG.8. In step1a, a 5GC entity such as GMLC may transmit a request for a location service for measuring the position of a target UE to a serving AMF. Here, even when the GMLC does not make the request for the location service, the serving AMF may determine the need for the location service for measuring the position of the target UE according to step1b. For example, the serving AMF may determine that itself will perform the location service in order to measure the position of the UE for an emergency call. In step2, the AMF transfers the request for the location service to an LMF. In step3a, the LMF may initiate location procedures with a serving ng-eNB or a serving gNB to obtain location measurement data or location measurement assistance data. For example, the LMF may transmit a request for location related information associated with one or more UEs to the NG-RAN and indicate the type of necessary location information and associated QoS. Then, the NG-RAN may transfer the location related information to the LMF in response to the request. In this case, when a location determination method according to the request is an enhanced cell ID (E-CID) scheme, the NG-RAN may transfer additional location related information to the LMF in one or more NR positioning protocol A (NRPPa) messages. Here, the “location related information” may mean all values used for location calculation such as actual location estimate information and radio measurement or location measurement. Protocol used in step3amay be an NRPPa protocol which will be described later. Additionally, in step3b, the LMF may initiate a location procedure for DL positioning together with the UE. For example, the LMF may transmit the location assistance data to the UE or obtain a location estimate or location measurement value. For example, in step3b, a capability information transfer procedure may be performed. Specifically, the LMF may transmit a request for capability information to the UE and the UE may transmit the capability information to the LMF. Here, the capability information may include information about a positioning method supportable by the LFM or the UE, information about various aspects of a particular positioning method, such as various types of assistance data for an A-GNSS, and information about common features not specific to any one positioning method, such as ability to handle multiple LPP transactions. In some cases, the UE may provide the capability information to the LMF although the LMF does not transmit a request for the capability information. As another example, in step3b, a location assistance data transfer procedure may be performed. Specifically, the UE may transmit a request for the location assistance data to the LMF and indicate particular location assistance data needed to the LMF. Then, the LMF may transfer corresponding location assistance data to the UE and transfer additional assistance data to the UE in one or more additional LTE positioning protocol (LPP) messages. The location assistance data delivered from the LMF to the UE may be transmitted in a unicast manner. In some cases, the LMF may transfer the location assistance data and/or the additional assistance data to the UE without receiving a request for the assistance data from the UE. As another example, in step3b, a location information transfer procedure may be performed. Specifically, the LMF may send a request for the location (related) information associated with the UE to the UE and indicate the type of necessary location information and associated QoS. In response to the request, the UE may transfer the location related information to the LMF. Additionally, the UE may transfer additional location related information to the LMF in one or more LPP messages. Here, the “location related information” may mean all values used for location calculation such as actual location estimate information and radio measurement or location measurement. Typically, the location related information may be a reference signal time difference (RSTD) value measured by the UE based on DL RSs transmitted to the UE by a plurality of NG-RANs and/or E-UTRANs. Similarly to the above description, the UE may transfer the location related information to the LMF without receiving a request from the LMF. The procedures implemented in step3bmay be performed independently but may be performed consecutively. Generally, although step3bis performed in order of the capability information transfer procedure, the location assistance data transfer procedure, and the location information transfer procedure, step3bis not limited to such order. In other words, step3bis not required to occur in specific order in order to improve flexibility in positioning. For example, the UE may request the location assistance data at any time in order to perform a previous request for location measurement made by the LMF. The LMF may also request location information, such as a location measurement value or a location estimate value, at any time, in the case in which location information transmitted by the UE does not satisfy required QoS. Similarly, when the UE does not perform measurement for location estimation, the UE may transmit the capability information to the LMF at any time. In step3b, when information or requests exchanged between the LMF and the UE are erroneous, an error message may be transmitted and received and an abort message for aborting positioning may be transmitted and received. Protocol used in step3bmay be an LPP protocol which will be described later. Step3bmay be performed additionally after step3abut may be performed instead of step3a. In step4, the LMF may provide a location service response to the AMF. The location service response may include information as to whether UE positioning is successful and include a location estimate value of the UE. If the procedure ofFIG.8has been initiated by step1a, the AMF may transfer the location service response to a 5GC entity such as a GMLC. If the procedure ofFIG.8has been initiated by step1b, the AMF may use the location service response in order to provide a location service related to an emergency call. Protocol for Location Measurement LTE Positioning Protocol (LPP) FIG.9illustrates an exemplary protocol layer used to support LPP message transfer between an LMF and a UE. An LPP protocol data unit (PDU) may be carried in a NAS PDU between an AMF and the UE. Referring toFIG.11, LPP is terminated between a target device (e.g., a UE in a control plane or an SUPL enabled terminal (SET) in a user plane) and a location server (e.g., an LMF in the control plane or an SLP in the user plane). LPP messages may be carried as transparent PDUs cross intermediate network interfaces using appropriate protocols, such an NGAP over an NG-C interface and NAS/RRC over LTE-Uu and NR-Uu interfaces. LPP is intended to enable positioning for NR and LTE using various positioning methods. For example, a target device and a location server may exchange, through LPP, capability information therebetween, assistance data for positioning, and/or location information. The target device and the location server may exchange error information and/or indicate abort of an LPP procedure, through an LPP message. (2) NR Positioning Protocol A (NRPPa) FIG.10illustrates an exemplary protocol layer used to support NRPPa PDU transfer between an LMF and an NG-RAN node. NRPPa may be used to carry information between an NG-RAN node and an LMF. Specifically, NRPPa may carry an E-CID for measurement transferred from an ng-eNB to an LMF, data for support of an OTDOA positioning method, and a cell-ID and a cell position ID for support of an NR cell ID positioning method. An AMF may route NRPPa PDUs based on a routing ID of an involved LMF over an NG-C interface without information about related NRPPa transaction. An NRPPa procedure for location and data collection may be divided into two types. The first type is a UE associated procedure for transfer of information about a particular UE (e.g., location measurement information) and the second type is a non-UE-associated procedure for transfer of information applicable to an NG-RAN node and associated TPs (e.g., gNB/ng-eNB/TP timing information). The two types may be supported independently or may be supported simultaneously. Positioning Measurement Method Positioning methods supported in the NG-RAN may include a GNSS, an OTDOA, an E-CID, barometric sensor positioning, WLAN positioning, Bluetooth positioning, a TBS, uplink time difference of arrival (UTDOA) etc. Although any one of the positioning methods may be used for UE positioning, two or more positioning methods may be used for UE positioning. Observed Time Difference Of Arrival (OTDOA) FIG.11is a view illustrating an OTDOA positioning method. The OTDOA positioning method uses time measured for DL signals received from multiple TPs including an eNB, an ng-eNB, and a PRS-only TP by the UE. The UE measures time of received DL signals using location assistance data received from a location server. The position of the UE may be determined based on such a measurement result and geographical coordinates of neighboring TPs. The UE connected to the gNB may request measurement gaps to perform OTDOA measurement from a TP. If the UE is not aware of an SFN of at least one TP in OTDOA assistance data, the UE may use autonomous gaps to obtain an SFN of an OTDOA reference cell prior to requesting measurement gaps for performing reference signal time difference (RSTD) measurement. Here, the RSTD may be defined as the smallest relative time difference between two subframe boundaries received from a reference cell and a measurement cell. That is, the RSTD may be calculated as the relative time difference between the start time of a subframe received from the measurement cell and the start time of a subframe from the reference cell that is closest to the subframe received from the measurement cell. The reference cell may be selected by the UE. For accurate OTDOA measurement, it is necessary to measure time of arrival (ToA) of signals received from geographically distributed three or more TPs or BSs. For example, ToA for each of TP1, TP2, and TP3may be measured, and RSTD for TP1and TP2, RSTD for TP2and TP3, and RSTD for TP3and TP1are calculated based on three ToA values. A geometric hyperbola is determined based on the calculated RSTD values and a point at which curves of the hyperbola cross may be estimated as the position of the UE. In this case, accuracy and/or uncertainty for each ToA measurement may occur and the estimated position of the UE may be known as a specific range according to measurement uncertainty. For example, RSTD for two TPs may be calculated based on Equation 3 below. RSTDi,1=(xt-xi)2+(yt-yi)2c-(xt-xi)2+(yt-y1)2c+(Ti-T1)+(ni-n1)[Equation3] where c is the speed of light, {xt, yt} are (unknown) coordinates of a target UE, {xi, yi} are (known) coordinates of a TP, and {x1, y1} are coordinates of a reference TP (or another TP). Here, (Ti-T1) is a transmission time offset between two TPs, referred to as “real time differences” (RTDs), and niand n1are UE ToA measurement error values. (2) Enhanced Cell ID (E-CID) In a cell ID (CID) positioning method, the position of the UE may be measured based on geographical information of a serving ng-eNB, a serving gNB, and/or a serving cell of the UE. For example, the geographical information of the serving ng-eNB, the serving gNB, and/or the serving cell may be acquired by paging, registration, etc. The E-CID positioning method may use additional UE measurement and/or NG-RAN radio resources in order to improve UE location estimation in addition to the CID positioning method. Although the E-CID positioning method partially may utilize the same measurement methods as a measurement control system on an RRC protocol, additional measurement only for UE location measurement is not generally performed. In other words, an additional measurement configuration or measurement control message may not be provided for UE location measurement. The UE does not expect that an additional measurement operation only for location measurement will be requested and the UE may report a measurement value obtained by generally measurable methods. For example, the serving gNB may implement the E-CID positioning method using an E-UTRA measurement value provided by the UE. Measurement elements usable for E-CID positioning may be, for example, as follows. UE measurement: E-UTRA reference signal received power (RSRP), E-UTRA reference signal received quality (RSRQ), UE E-UTRA reception (RX)-transmission (TX) time difference, GERAN/WLAN reference signal strength indication (RSSI), UTRAN common pilot channel (CPICH) received signal code power (RSCP), and/or UTRAN CPICH Ec/Io E-UTRAN measurement: ng-eNB RX-TX time difference, timing advance (Taw), and/or AoA Here, TADVmay be divided into Type 1 and Type 2 as follows. TADVType 1=(ng-eNB RX-TX time difference)+(UE E-UTRA RX-TX time difference) TADVType 2=ng-eNB RX-TX time difference AoA may be used to measure the direction of the UE. AoA is defined as the estimated angle of the UE counterclockwise from the eNB/TP. In this case, a geographical reference direction may be north. The eNB/TP may use a UL signal such as an SRS and/or a DMRS for AoA measurement. The accuracy of measurement of AoA increases as the arrangement of an antenna array increases. When antenna arrays are arranged at the same interval, signals received at adjacent antenna elements may have constant phase rotate. (3) Uplink Time Difference of Arrival (UTDOA) UTDOA is to determine the position of the UE by estimating the arrival time of an SRS. When an estimated SRS arrival time is calculated, a serving cell is used as a reference cell and the position of the UE may be estimated by the arrival time difference with another cell (or an eNB/TP). To implement UTDOA, an E-SMLC may indicate the serving cell of a target UE in order to indicate SRS transmission to the target UE. The E-SMLC may provide configurations such as periodic/non-periodic SRS, bandwidth, and frequency/group/sequence hopping. FIG.12illustrates an SSB structure. The UE may perform cell search, system information acquisition, beam alignment for initial access, DL measurement, etc. based on the SSB. The SSB and synchronization signal/physical broadcast channel (SS/PBCH) block are interchangeably used. Referring toFIG.12, an SSB includes a PSS, an SSS, and a PBCH. The SSB is configured over four consecutive OFDM symbols, and the PSS, PBCH, SSS/PBCH, and PBCH are transmitted on the respective OFDM symbols. The PSS and SSS may each consist of 1 OFDM symbol and 127 subcarriers, and the PBCH may consist of 3 OFDM symbols and 576 subcarriers. Polar coding and quadrature phase shift keying (QPSK) are applied to the PBCH. The PBCH may have a data RE and a demodulation reference signal (DMRS) RE for each OFDM symbol. There may be three DMRS REs for each RB, and there may be three data REs between DMRS REs. The cell search refers to a procedure in which the UE acquires time/frequency synchronization of a cell and detects a cell ID (e.g., physical layer cell ID (PCID)) of the cell. The PSS may be used in detecting a cell ID within a cell ID group, and the SSS may be used in detecting a cell ID group. The PBCH may be used in detecting an SSB (time) index and a half-frame. The cell search procedure of the UE may be summarized as shown in Table 3 below. TABLE 3Type ofSignalsOperations1ststepPSSSS/PBCH block (SSB) symbol timingacquisition Cell ID detection within a cellID group (3 hypothesis)2ndStepSSS* Cell ID group detection (336 hypothesis)3rdStepPBCHSSB index and Half frame (HF) indexDMRS(Slot and frame boundary detection)4thStepPBCHTime information (80 ms, System FrameNumber (SFN), SSB index, HF)* Remaining Minimum System Information(RMSI) Control resource set (CORESET)/Search space configuration5thStepPDCCH andCell access informationPDSCH* RACH configuration There may be 336 cell ID groups, and each cell ID group may have three cell IDs. There may be 1008 cell IDs in total. Information about a cell ID group to which a cell ID of a cell belongs may be provided/acquired through the SSS of the cell, and information about the cell ID among 336 cells in the cell ID may be provided/acquired through the PSS. FIG.15illustrates SSB transmission. Referring toFIG.15, the SSB is periodically transmitted in accordance with the SSB periodicity. The basic SSB periodicity assumed by the UE in the initial cell search is defined as 20 ms. After cell access, the SSB periodicity may be set to one of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms} by the network (e.g., the BS). A SSB burst set may be configured at the beginning of the SSB periodicity. The SSB burst set may be configured with a 5 ms time window (i.e., half-frame), and the SSB may be repeatedly transmitted up to L times within the SS burst set. The maximum number of transmissions of the SSB, L, may be given according to the frequency band of the carrier wave as follows. One slot includes up to two SSBs.For frequency range up to 3 GHz, L=4For frequency range from 3 GHz to 6 GHz, L=8For frequency range from 6 GHz to 52.6 GHz, L=64 The time position of an SSB candidate in the SS burst set may be defined according to the SCS as follows. The time position of the SSB candidate is indexed from 0 to L−1 in temporal order within the SSB burst set (i.e., half-frame) (SSB index).Case A—15 kHz SCS: The index of the start symbol of a candidate SSB is given as {2, 8}+14*n. When the carrier frequency is lower than or equal to 3 GHz, n=0, 1. When the carrier frequency is 3 GHz to 6 GHz, n=0, 1, 2, 3.Case B—30 kHz SCS: The index of the start symbol of a candidate SSB is given as {4, 8, 16, 20}+28*n. When the carrier frequency is lower than or equal to 3 GHz, n=0. When the carrier frequency is 3 GHz to 6 GHz, n=0, 1.Case C—30 kHz SCS: The index of the start symbol of a candidate SSB is given as {2, 8}+14*n. When the carrier frequency is lower than or equal to 3 GHz, n=0. When the carrier frequency is 3 GHz to 6 GHz, n=0, 1, 2, 3.Case D—120 kHz SCS: The index of the start symbol of a candidate SSB is given as {4, 8, 16, 20}+28*n. When the carrier frequency is higher than 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18.Case E—240 kHz SCS: The index of the start symbol of a candidate SSB is given as {8, 12, 16, 20, 32, 36, 40, 44}+56*n. When the carrier frequency is higher than 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8. CSI Related Behavior In a new radio (NR) system, a CSI-RS is used for time and/or frequency tracking, CSI computation, RSRP calculation, and mobility. Here, CSI computation is related to CSI acquisition, and RSRP computation is related to beam management (BM). FIG.14is a flowchart illustrating an exemplary CSI related procedure. To perform one of the above purposes of the CSI-RS, the UE receives configuration information related to CSI from the BS through RRC signaling (S1401). The CSI related configuration information may include at least one of CSI-interference management (IM) resource related information, CSI measurement configuration related information, CSI resource configuration related information, CSI-RS resource related information, or CSI report configuration related information. The CSI-IM resource related information may include CSI-IM resource information, CSI-IM resource set information, etc. A CSI-IM resource set is identified by a CSI-IM resource set identifier (ID), and one resource set includes at least one CSI-IM resource. Each CSI-IM resource is identified by a CSI-IM resource ID. The CSI resource configuration related information may be expressed as a CSI-ResourceConfig information element (IE). The CSI resource configuration related information defines a group including at least one of a non-zero power (NZP) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the CSI resource configuration related information includes a CSI-RS resource set list. The CSI-RS resource set list may include at least one of an NZP CSI-RS resource set list, a CSI-IM resource set list, or a CSI-SSB resource set list. The CSI-RS resource set is identified by a CSI-RS resource set ID, and one resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID. RRC parameters (e.g., a BM related “repetition” parameter and a tracking related “trs-Info” parameter) indicating usage of a CSI-RS for each NZP CSI-RS resource set may be configured. iii) The CSI report configuration related information includes a report configuration type parameter (reportConfigType) indicative of a time domain behavior and a report quantity parameter (reportQuantity) indicative of a CSI related quantity to be reported. The time domain behavior may be periodic, aperiodic, or semi-persistent. The UE measures CSI based on the CSI related configuration information (S1403). Measuring the CSI may include (1) receiving a CSI-RS by the UE (S1405) and (2) computing the CSI based on the received CSI-RS (S1407). For the CSI-RS, RE mapping of CSI-RS resources is configured in time and frequency domains by an RRC parameter CSI-RS-ResourceMapping. The UE reports the measured CSI to the BS (S1409). CSI Measurement The NR system supports more flexible and dynamic CSI measurement and reporting. The CSI measurement may include receiving a CSI-RS, and acquiring CSI by computing the received CSI-RS. As time domain behaviors of CSI measurement and reporting, channel measurement (CM) and interference measurement (IM) are supported. A CSI-IM-based interference measurement resource (IMR) of NR has a design similar to CSI-IM of LTE and is configured independent of ZP CSI-RS resources for PDSCH rate matching. At each port of a configured NZP CSI-RS-based IMR, the BS transmits an NZP CSI-RS to the UE. If there is no PMI or RI feedback for a channel, a plurality of resources is configured in a set and the BS or network indicates, through DCI, a subset of NZP CSI-RS resources for CM/IM. Resource setting and resource setting configuration will be described in more detail. Resource Setting Each CSI resource setting “CSI-ResourceConfig” includes configuration of S(≥1) CSI resource sets (which are given by RRC parameter csi-RS-ResourceSetList). A CSI resource setting corresponds to CSI-RS-resourcesetlist. Here, S represents the number of configured CSI-RS resource sets. Configuration of S(≥1) CSI resource sets includes each CSI resource set including CSI-RS resources (composed of NZP CSI-RS or CSI-IM), and an SS/PBCH block (SSB) resource used for RSRP computation. Each CSI resource setting is positioned at a DL bandwidth part (BWP) identified by RRC parameter bwp-id. All CSI resource settings linked to a CSI reporting setting have the same DL BWP. In a CSI resource setting included in a CSI-ResourceConfig IE, a time domain behavior of a CSI-RS resource may be indicated by RRC parameter resourceType and may be configured to be aperiodic, periodic, or semi-persistent. One or more CSI resource settings for CM and IM are configured through RRC signaling. A channel measurement resource (CMR) may be an NZP CSI-RS for CSI acquisition, and an interference measurement resource (IMR) may be an NZP CSI-RS for CSI-IM and for IM. Here, CSI-IM (or a ZP CSI-RS for IM) is mainly used for inter-cell interference measurement. An NZP CSI-RS for IM is mainly used for intra-cell interference measurement from multiple users. The UE may assume that CSI-RS resource(s) for CM and CSI-IM/NZP CSI-RS resource(s) for IM configured for one CSI reporting are “QCL-TypeD” for each resource. Resource Setting Configuration A resource setting may represent a resource set list. When one resource setting is configured, a resource setting (given by RRC parameter resourcesForChannelMeasurement) is about channel measurement for RSRP computation. When two resource settings are configured, the first resource setting (given by RRC parameter resourcesForChannelMeasurement) is for channel measurement and the second resource setting (given by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference) is for CSI-IM or for interference measurement performed on an NZP CSI-RS. When three resource settings are configured, the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement, the second resource setting (given by csi-IM-ResourcesForInterference) is for CSI-IM based interference measurement, and the third resource setting (given by nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS based interference measurement. When one resource setting (given by resourcesForChannelMeasurement) is configured, the resource setting is about channel measurement for RSRP computation. When two resource settings are configured, the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement, and the second resource setting (given by RRC parameter csi-IM-ResourcesForInterference) is used for interference measurement performed on CSI-IM. CSI Computation If interference measurement is performed on CSI-IM, each CSI-RS resource for channel measurement is associated with a CSI-RS resource in order of CSI-RS resources and CSI-IM resources in a corresponding resource set. The number of CSI-RS resources for channel measurement is the same as the number of CSI-IM resources. For CSI measurement, the UE assumes the following. Each NZP CSI-RS port configured for interference measurement corresponds to an interference transmission layer. Every interference transmission layer of NZP CSI-RS ports for interference measurement considers an energy per resource element (EPRE) ratio. Different interference signals are assumed on RE(s) of an NZP CSI-RS resource for channel measurement, an NZP CSI-RS resource for interference measurement, or a CSI-IM resource for interference measurement. CSI Reporting For CSI reporting, time and frequency resources available for the UE are controlled by the BS. Regarding a CQI, PMI, CSI-RS resource indicator (CRI), SS/PBCH block resource indicator (SSBRI), layer indicator (LI), RI, or L1-RSRP, the UE receives RRC signaling including N(≥1) CSI-ReportConfig reporting settings, M(≥1) CSI-ResourceConfig resource settings, and a list of one or two trigger states (provided by aperiodicTriggerStateList and semiPersistentOnPUSCH-TriggerStateList). In aperiodicTriggerStateList, each trigger state includes a channel and optionally a list of associated CSI-ReportConfigs indicative of resource set IDs for interference. In semiPersistentOnPUSCH-TriggerStateList, each trigger state includes one associated CSI-ReportConfig. That is, for each CSI-RS resource setting, the UE transmits CSI reporting indicated by CSI-ReportConfigs associated with the CSI-RS resource setting to the BS. For example, the UE may report at least one of the CQI, PMI, CRI, SSBRI, LI, RI, or RSRP as indicated by CSI-ReportConfigs associated with the CSI resource setting. However, if CSI-ReportConfigs associated with the CSI resource setting indicates “none”, the UE may skip reporting of the CSI or RSRP associated with the CSI resource setting. The CSI resource setting may include a resource for an SS/PBCH block. FIG.15illustrates a structure of a radio frame used in NR. In NR, UL and DL transmissions are configured in frames. The radio frame has a length of 10 ms and is defined as two 5 ms half-frames (HF). The half-frame is defined as five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on subcarrier spacing (SCS). Each slot includes 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP). When a normal CP is used, each slot includes 14 symbols. When an extended CP is used, each slot includes 12 symbols. Here, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or DFT-s-OFDM symbols). Table 4 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when the normal CP is used. TABLE 4SCS (15*2{circumflex over ( )}u)NsymbslotNslotframe, uNslotsubframe, u15 KHz (u = 0)1410130 KHz (u = 1)1420260 KHz (u = 2)14404120 KHz (u = 3)14808240 KHz (u = 4)1416016Nsymbslot: Number of symbols in a slotNslotframe, u: Number of slots in a frameNslotsubframe, u: Number of slots in a subframe Table 5 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when the extended CP is used. TABLE 5SCS (15*2{circumflex over ( )}u)NsymbslotNslotframe, uNslotsubframe, u60 KHz (u = 2)12404 In the NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) may be configured differently among a plurality of cells merged for one UE. Thus, the (absolute time) duration of a time resource (e.g., SF, slot or TTI) (referred to as a time unit (TU) for simplicity) composed of the same number of symbols may be set differently among the merged cells. FIG.16illustrates a slot structure of an NR frame. A slot includes a plurality of symbols in the time domain. For example, in the case of the normal CP, one slot includes seven symbols. On the other hand, in the case of the extended CP, one slot includes six symbols. A carrier includes a plurality of subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers (e.g., 12 consecutive subcarriers) in the frequency domain. A bandwidth part (BWP) is defined as a plurality of consecutive (P)RBs in the frequency domain and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., five) BWPs. Data communication is performed through an activated BWP, and only one BWP may be activated for one UE. In the resource grid, each element is referred to as a resource element (RE), and one complex symbol may be mapped thereto. FIG.17illustrates a structure of a self-contained slot. In the NR system, a frame has a self-contained structure in which a DL control channel, DL or UL data, a UL control channel, and the like may all be contained in one slot. For example, the first N symbols (hereinafter, DL control region) in the slot may be used to transmit a DL control channel, and the last M symbols (hereinafter, UL control region) in the slot may be used to transmit a UL control channel. N and M are integers greater than or equal to 0. A resource region (hereinafter, a data region) that is between the DL control region and the UL control region may be used for DL data transmission or UL data transmission. For example, the following configuration may be considered. Respective sections are listed in a temporal order. 1. DL only configuration 2. UL only configuration 3. Mixed UL-DL configurationDL region+Guard period (GP)+UL control regionDL control region+GP+UL regionDL region: (i) DL data region, (ii) DL control region+DL data regionUL region: (i) UL data region, (ii) UL data region+UL control region The PDCCH may be transmitted in the DL control region, and the PDSCH may be transmitted in the DL data region. The PUCCH may be transmitted in the UL control region, and the PUSCH may be transmitted in the UL data region. Downlink control information (DCI), for example, DL data scheduling information, UL data scheduling information, and the like, may be transmitted on the PDCCH. Uplink control information (UCI), for example, ACK/NACK information about DL data, channel state information (CSI), and a scheduling request (SR), may be transmitted on the PUCCH. The GP provides a time gap in the process of the UE switching from the transmission mode to the reception mode or from the reception mode to the transmission mode. Some symbols at the time of switching from DL to UL within a subframe may be configured as the GP. Hereinafter, embodiments of the present disclosure will be described in detail based on the above technical idea. The aforementioned details may be applied to the following embodiments of the present disclosure. For example, operations, functions and terms that are not defined in the following embodiments of the present disclosure may be performed and explained based on the aforementioned details. The following symbols/abbreviations/terms are used in the embodiments of the present disclosure.AOA (AoA): angle of arrivalAOD (AoD): angle of departureCSI-RS: channel state information reference signalECID: enhanced cell identifierGPS: global positioning systemGNSS: global navigation satellite systemLMF: location management functionNRPPa: NR positioning protocol aOTDOA (OTDoA): observed time difference of arrivalPRS: positioning reference signalRAT: radio access technologyRS: reference signalRTT: round trip timeRSTD: reference signal time difference/relative signal time differenceSRS: sounding reference signalTDOA (TDoA): time difference of arrivalTOA (ToA): time of arrivalTRP: transmission reception pointUTDOA (UTDoA): uplink time difference of arrival To estimate the location of a UE based on UE positioning methods such as an OTDOA, a multi-cell RTT, etc., it is necessary to obtain a ToA measurement based on a DL RS such as a PRS, a CSI-RS, and an SS/PBCH block. However, the reliability and/or accuracy of the measured ToA may vary depending on the presence or absence of a line of sight (LoS) component or the signal strength/power of a first path. In some cases, the measured ToA may not correspond to the first arrival path. When the UE measures a ToA for an RS such as a PRS, a CSI-RS, and an SS/PBCH block transmitted from a specific TP/BS, all channel taps may be lower than or similar to a specific threshold (e.g., noise level) as shown inFIG.18. As a result, the ToA measurement may be practically impossible, or the measurement reliability may be quite low. The measurement reliability/quality may be similarly considered not only for the ToA measurement but also for various measurements such an RSTD, an angle-related measurement (AoA), a UE RX-TX time difference, etc. in a similar way. Thus, the UE may declare/define detection failure for the measurement such as the ToA/RSTD/AoA/UE RX-TX time difference obtained from the RS (e.g., PRS) transmitted by the specific TP/BS/cell and report the detection failure to the BS/LMF. The UE may request/recommend to the BS/LMF to reconfigure RS resources for re-measurement/re-acquisition of the ToA/RSTD/AoA/UE RX-TX time difference measurement. Here, reporting the detection failure to the BS/LMF may correspond to an operation by which the UE informs the BS/LMF that the reliability or quality of the ToA/RSTD/AoA/UE RX-TX time difference measurement is considerably low or not valid. UE operations with the same functionality or related BS/LMF operations may be included in the spirit of the present disclosure. The following embodiments may be configured/instructed for the detection failure operation. (1) The LMF/BS may configure/instruct the UE to define a very large value as one of the error values of “OTDOA-MeasQuality”, which is a higher layer parameter indicating OTDOA measurement quality, and then report the detection failure. For example, if the UE reports “infinity” as the error value to the LMF/BS, the LMF/BS may recognize that the ToA value is not valid. (2) A parameter may be introduced to indicate the quality of the AoA/RSTD/UE RX-TX time difference measurement. The quality of the AoA/RSTD/UE RX-TX time difference measurement may also be included as an error value. The UE may be configured to define a very large value as one of the error values reported by the UE. The operation in which the UE declares/reports the detection failure or the operation in which the UE reports that the ToA/RSTD/UE RX-TX time difference value is not valid may be performed for a specific TP/cell/BS, but the operation may also be performed for a specific PRS resource and/or a specific PRS resource set. For example, the UE may not know which TP/BS transmits the specific PRS resource and/or PRS resource set in an explicit or implicit way. In other words, if the UE is not configured with the identification (ID) of the TP/BS associated with the specific PRS, the UE may not know the TP/BS that has transmitted the specific PRS resource, and only the LMF/BS may know the TP/BS. In the above situation, the following embodiments may be considered for the detection failure operation. (1) The BS/LMF may configure/indicate to the UE a specific RS (e.g., PRS, CSI-RS, or SS/PBCH block) resource and/or a specific RS (e.g., PRS, CSI-RS, or SS/PBCH block) resource set. In addition, the configured RS resource and/or resource set may be used for UE positioning. When the measurements (e.g., ToA/RSTD/AoA/UE RX-TX time difference) measured by the UE for all RS resources included in the specific RS resource set are less than or equal to a specific threshold, the UE may report the detection failure to the BS/LMF. (2) When the ToA/RSTD/AOA/UE RX-TX time difference measurement obtained for some X (>0) RS resource sets among a plurality of RS (e.g., PRS, CSI-RS, or SS/PBCH block) resource sets or the quality of the measurement is less than or equal to the specific threshold, the UE may report the detection failure to the BS/LMF. (3) When the ToA/RSTD/AOA/UE RX-TX time difference measurement obtained for some Y (>0) RS resources among configured RS (e.g., PRS, CSI-RS, or SS/PBCH block) resources or the quality of the measurement is less than or equal to the specific threshold, the UE may report the detection failure to the BS/LMF. The above-described threshold may be defined/set/used as a default value, and the BS/LMF may separately configure/indicate the specific threshold to the UE. In addition, based on the above-described detection failure operation, the UE may declare the detection failure for each RS resource and/or RS resource set and then report the detection failure to the BS/LMF. For example, when the measurement for a specific RS resource is less than or equal to the specific threshold, the UE may report the detection failure to the BS/LMF, instead of reporting the measurement. In other words, if the measurement of an RS resource is more than the specific threshold, the UE may report the corresponding measurement. On the other hand, if the measurement of an RS resource is less than or equal to the specific threshold, the UE may report the detection failure state. The BS/LMF may select measurements to be used for positioning based on the received report in order to improve the accuracy of the UE positioning and may strategically determine a positioning method to be used for the UE positioning. Hereinafter, the embodiments of the present disclosure will be described in detail. All or some of the following embodiments of the present disclosure may be combined to implement another embodiment of the present disclosure unless they are mutually exclusive, which will be clearly understood by those of ordinary skill in the art. FIG.19is a diagram schematically illustrating an operation method for a UE and network nodes according to the present disclosure. Referring toFIG.19, for example, in operation1901, a location server and/or LMF may transmit information on a plurality of PRSs to a TP, and the TP may receive the information. For example, in operation1903, the TP may forward the information on the plurality of PRSs to a UE, and the UE may receive the information. For example, in operation1905, the location server and/or LMF may transmit the information on the plurality of PRSs to the UE, and the UE may receive the information. In this case, for example, operation1901and/or operation1903may be omitted. As a contrary example, operation1905may be omitted. In this case, for example, operation1901and/or operation1903may be performed. That is, operation1901and/or operation1903and operation1905may be alternate. For example, in operation1907, the TP may transmit a PRS to the UE, and the UE may receive the plurality of PRSs from a plurality of TPs including the TP. For example, the plurality of PRSs may be related to a plurality of PRS resources. For example, in operation1909, the UE may transmit a measurement report to the TP, and the TP may receive the measurement report. For example, in operation1911, the TP may forward the measurement report to the location server and/or LMF, and the location server and/or LMF may receive measurement report. For example, in operation1913, the UE may transmit the measurement report to the location server and/or LMF, and the location server and/or LMF may receive the measurement report. In this case, for example, operation1909and/or operation1911may be omitted. As a contrary example, operation1913may be omitted. In this case, for example, operation1909and/or operation1913may be performed. That is, operation1909and/or operation1911and operation1913may be alternate. For example, the measurement report may be related to the plurality of PRS resources. For example, the measurement report may include information on one or more RSTDs measured based on one or more PRS resources among the plurality of PRS resources. For example, the measurement report may include information on one or more PRS indices related to the one or more PRS resources. For example, the one or more RSTDs may be related to an OTDOA. For example, the one or more PRS indices may be related to an AOD. For example, in operation1915, the location server and/or LMF may obtain information on the location (and/or positioning) of the UE. For example, the location server and/or LMF may obtain information on a first estimated location (and/or positioning) of the UE based on the OTDOA related to the one or more RSTDs. For example, the location server and/or LMF may obtain information on a second estimated location (and/or positioning) of the UE based on the AOD related to the one or more PRS indices. For example, the location server and/or LMF may obtain the information on the location of the UE based on the information on the first estimated location of the UE and the information on the second estimated location of the UE. FIG.20is a flowchart illustrating an operation method for a UE according to the present disclosure. Referring toFIG.20, for example, in operation2001, the UE may receive information on a plurality of PRSs. For example, the plurality of PRSs may be related to a plurality of PRS resources. For example, in operation2003, the UE may receive the plurality of PRSs. For example, in operation2005, the UE may transmit a measurement report. For example, the measurement report may be related to the plurality of PRS resources. For example, the measurement report may include information on one or more RSTDs measured based on one or more PRS resources among the plurality of PRS resources. For example, the measurement report may include information on one or more PRS indices related to the one or more PRS resources. For example, the one or more RSTDs may be related to an OTDOA. For example, the one or more PRS indices may be related to an AOD. FIG.21is a flowchart illustrating an operation method for a TP according to the present disclosure. Referring toFIG.21, for example, in operation2101, the TP may receive information on a plurality of PRSs from a location server and/or LMF and forward the corresponding information to a UE. However, for example, when the location server and/or LMF transmits the information on the plurality of PRSs to the UE, operation2101may be omitted. For example, the plurality of PRSs may be related to a plurality of PRS resources. For example, in operation2103, the TP may transmit a PRS to the UE. For example, the plurality of PRSs may be transmitted to the UE from a plurality of TPs. For example, in operation2105, the TP may receive a measurement report from the UE and forward the measurement report to the location server and/or LMF. However, for example, when the UE transmits the measurement report to the location server and/or LMF, operation2105may be omitted. For example, the measurement report may be related to the plurality of PRS resources. For example, the measurement report may include information on one or more RSTDs measured based on one or more PRS resources among the plurality of PRS resources. For example, the measurement report may include information on one or more PRS indices related to the one or more PRS resources. For example, the one or more RSTDs may be related to an OTDOA. For example, the one or more PRS indices may be related to an AOD. FIG.22is a flowchart illustrating an operation method for a network node according to the present disclosure. For example, the network node may be a location server and/or LMF. Referring toFIG.22, for example, in operation2201, the location server and/or LMF may transmit information on a plurality of PRSs. For example, the plurality of PRSs may be related to a plurality of PRS resources. For example, in operation2203, the location server and/or LMF may receive a measurement report. For example, the measurement report may be related to the plurality of PRS resources. For example, the measurement report may include information on one or more RSTDs measured based on one or more PRS resources among the plurality of PRS resources. For example, the measurement report may include information on one or more PRS indices related to the one or more PRS resources. For example, the one or more RSTDs may be related to an OTDOA. For example, the one or more PRS indices may be related to an AOD. For example, in operation2205, the location server and/or LMF may obtain information on the location (and/or positioning) of the UE. For example, the location server and/or LMF may obtain information on a first estimated location (and/or positioning) of the UE based on the OTDOA related to the one or more RSTDs. For example, the location server and/or LMF may obtain information on a second estimated location (and/or positioning) of the UE based on the AOD related to the one or more PRS indices. For example, the location server and/or LMF may obtain the information on the location of the UE based on the information on the first estimated location of the UE and the information on the second estimated location of the UE. Particular operations, functions, and terms in the above description may be performed and explained based on the embodiments of the present disclosure, which will be described later. The UE may report the detection failure for the above-described UE measurements (e.g., ToA/RSTD/AoA/UE RX-TX time difference) in order to inform the BS/LMF that even if the UE reports the measurements by performing configured/indicated measurement, the measurements are not helpful for UE positioning due to significant measurement errors. Thus, when using a specific UE positioning method, the BS/LMF may exclude the measurements corresponding to the detection failure or change PRS resources used for the measurements and allocate the PRS resources to other PRSs. In the LTE system, when the LMF configures/indicates PRS resources to the UE, the LMF may configure/indicate information about a reference cell/TP and neighboring cells/TPs together. When the UE receives PRSs from a plurality of cells/TPs, if the quality of a ToA/ToF measurement received from the reference cell/TP is low, the UE may change the reference cell/TP and transmit to the LMF/BS information about the changed reference cell/TP and information about neighboring cells/TPs together with an RSTD report. In the NR system, since each BS/TP transmits PRSs on a plurality of transmission beams, a different ToA/ToF measurement may be obtained for a PRS transmitted on each beam. Among PRS resources transmitted on the plurality of transmission beams, a specific PRS resource related to a minimum propagation time and/or ToA may be a criterion for obtaining/calculating an RSTD measurement. Therefore, in the NR system, when configuring PRSs, the BS may set the specific PRS resource as a reference resource for RSTD acquisition/calculation, instead of setting a reference cell as the criterion for obtaining/calculating the RSTD measurement. For example, a PRS resource set including a plurality of PRS resources may be associated with a specific BS/TP, and each of the plurality of PRS resources may be associated with each of a plurality of transmission beams used by the specific BS/TP. Thus, if the specific PRS resource is set as the reference resource, the UE may know a reference BS/TP and a reference transmission beam and obtain/calculate the RSTD based thereon. However, when one PRS resource is included in a plurality of PRS resource sets, a reference PRS resource set may need to be configured for the UE. When the BS/LMF configures a PRS resource and/or a PRS resource set to the UE, if the BS/LMF configures/indicates only information about a reference cell/TP and information about neighboring cells/TPs, the UE may provide information a reference PRS resource and/or information about a reference cell together with the information the reference PRS resource to the LMF/BS while reporting an RSTD For example, the BS/LMF may configure information on at least one of a reference cell/TP, a reference PRS resource, or a reference PRS resource set to the UE. In addition, the UE may report information on at least one of a reference cell/TP, a reference PRS resource, and a reference PRS resource set actually used for RSTD measurement. For example, even if the BS/LMF configures information on only a reference cell/TP, the UE may report to the BS/LMF information about a reference cell/TP actually used for RSTD measurement and information about a reference PRS resource corresponding to a reference beam. To improve the accuracy of UE positioning, the UE may report information on a reference PRS resource and/or a reference PRS resource set actually used by the UE to the BS/LMF regardless of the configuration of BS/LMF Additionally, when reporting an RSTD to the LMF/BS, the UE may transmit information on a PRS resource with the smallest ToA/ToF and propagation delay time among a plurality of PRS resources transmitted from each neighboring cell. The PRS resource obtained from the above information may be used to determine a beam to be used when each BS/TP receives a UL reference signal, or the PRS resource may be used to measure AoD information for UE positioning. Meanwhile, each of a plurality of transmission beams used by one BS/TP may have a different PRS resource and/or a different PRS resource set. For example, one transmission beam may be associated with one PRS resource, and thus, a different PRS resource may be configured for each transmission beam. For OTDOA-based UE positioning, the UE needs to perform RSTD measurement and reporting. In this case, the accuracy/reliability of a ToA for a PRS transmitted from a reference TP/BS/cell, which corresponds to a reference to measure time differences, is very important. Therefore, when configuring PRSs, the BS/LMF may instruct the UE to receive PRSs from a plurality of cells and measure the ToA without distinguishing a reference cell and neighboring cells, instead of configuring/indicting the reference cell and neighboring cells to the UE in order to receive an RSTD measurement from the UE. The UE may use a specific PRS resource and/or a specific PRS resource index showing the best quality based on the measurement quality of the measured ToA as a reference for the RSTD measurement and reporting. On the other hand, a two-step PRS transmission/reporting procedure may be considered based on the indication/configuration of the LMF/BS. In the first step, a rough UE location, a reference cell, a reference PRS resource, and/or a reference PRS resource set may be configured. In the first step, the UE may report to the BS/LMF a PRS resource, a PRS resource set, and/or a TP/BS/cell index with the best ToA/propagation delay time measurement quality. In the second step, the BS/LMF may transmit a PRS by allocating more resources such as power/time/frequency to the high-quality PRS resource based on the PRS resource information reported to the BS/LMF. In the second step, the UE may measure an RSTD based on the PRS transmitted by the BS and a reference TP/cell/PRS resources, which are configured by the BS or selected by the UE and report the RSTD to the BS/LMF. The UE may request to allocate additional resources to a PRS transmitted from a specific TP/cell and/or on a specific transmission beam based on the quality of an acquired/measured ToA/ToF/OTDOTA measurement. In addition, if the quality/reliability of a ToF/ToA measurement for a PRS transmitted from a reference cell and/or neighboring cell is significantly low, the UE may request/recommend the LMF/BS to change the reference cell and/or neighboring cell. For example, if among N (>>1) PRSs received from TPs/cells, the quality of PRSs transmitted from K (<N) TPs/cells is good and the quality of the remaining PRSs is too low so that the remaining PRSs are not helpful for improving the positioning accuracy, the UE may request to allocate more power/time/frequency/space resources to the high-quality PRSs transmitted from the K TPs/cells. In addition, the UE may request the LMF/BS to change a low-quality neighboring TP/cell and/or serving TP/cell to another TP/cell. Since the ToA measurement quality for a reference cell is the most important in calculating an RSTD value with a neighboring cell, the RSTD measurement quality for a plurality of neighboring cells is inevitably lowered if the ToA measurement quality of the reference cell is low. Therefore, in this case, if the reference cell is changed and more resources are allocated by the LMF to a PRS transmitted from a specific BS/TP, it is possible to increase the ToA measurement quality of the reference cell and increase the RSTD measurement quality. To measure the location of the UE based on the OTDOA method, it is necessary to obtain ToA information from at least three or more cells/BSs/TPs and report an RSTD to the LMF based on the ToA information. If the RSRP/SNR of a PRS received from another cell/TP/BS other than the serving cell/TP/BS is too low or if there is a directivity problem between the PRS transmission beam direction of a neighboring cell and the reception beam of the UE, the UE may not perform the detection. In this case, the UE may determine that there occur significant errors if the BS/LMF measures the location of the UE based the OTDOA method or that it is impossible to apply the OTDOA method. Therefore, if the UE is configured to request/recommend the LMF/BS to use other UE positioning methods, it may be useful for UE positioning. Accordingly, a method by which the UE requests the BS/LMF to change the positioning method will be described in Embodiment 2. When the reliability and/or quality of a measurement obtained for a PRS resource and/or a PRS resource set configured by the BS/LMF is less than or equal to a specific threshold, the UE may recommend/request/report to the BS/LMF that UE positioning based on reporting contents currently configured/indicated to the UE is not suitable. For example, when the UE reports to the BS/LMF a specific value and/or specific information which means that “UE positioning is not suitable”, the BS/LMF may interpret the specific value and/or specific information to mean that even if the UE positioning is executed, the UE positioning has low reliability or significant positioning errors. For example, if the UE is instructed to report a ToA/RSTD value, if the quality of an RSTD or ToA measurement is less than or equal to a threshold, the UE may request/recommend/report to LMF/BS that the OTDOA-based UE positioning it is not suitable. When the reliability and/or quality of a measurement for a PRS resource and/or a PRS resource set configured by the BS/LMF is less than or equal to a threshold, the UE may recommend/request/report to the BS/LMF to use another UE positioning method instead of a UE positioning method based on the currently configured/indicated reporting contents. In addition, the UE may recommend/request/report to use another UE positioning method in addition to the UE positioning method that uses the reporting contents currently configured/indicated to the UE. If different positioning methods are used together, the UE positioning accuracy may be improved. For example, when the UE is configured to report a ToA/RSTD value, if the quality of an RSTD and/or ToA measurement is below a threshold but the quality of an RSRP measurement measured with the same PRS is guaranteed to be above a certain level, the UE may request/recommend/report to the LMF/BS to use an AoD-based UE positioning method and/or a UE positioning method based on the signal strength of a reference signal in addition to the OTDOA method. Here, the quality of an RSTD measurement may be replaced with the SNR/RSRP. However, considering that the RSTD is basically calculated based on a difference between ToA measurements for PRSs transmitted from a plurality of cells, if the ToA measurement reliability of a reference cell is high but the reliability of a ToA measurement measured for a PRS received from another cell/BS is quite low, the RSTD measurement quality may be low. Thus, even if the RSRP of the reference cell is sufficiently large, the RSTD quality may be significantly low. Therefore, for example, even if the UE is configured to report a ToA/RSTD value, if the quality of a ToA/RSTD measurement is not sufficiently high, the UE may recommend/request to the BS to use a UE positioning method based on angles such as an AoD/AoA or a specific RAT-independent positioning method based on the GNSS or UE sensors together. When the reliability and/or quality of a measurement obtained for a PRS resource and/or a PRS resource set configured by the BS/LMF is less than or equal to a specific threshold, the UE may report other measurement information more appropriate for UE positioning in addition to the currently configured/indicated reporting contents. The above-described UE operation may be indicated/configured by the BS/LMF to the UE. For example, when the reliability and/or quality of a ToA/RSTD measurement obtained based on a PRS resource is less than or equal to a threshold or the error range of the ToA/RSTD measurement is too large, that is, more than or equal to a specific threshold, the UE may report the index of the PRS resource and/or the RSRP of the corresponding PRS resource to assist in obtaining the location of the UE based on the direction (e.g., angle) of a PRS transmission beam transmitted by the TP/BS and signal strength, instead of reporting the ToA/RSTD measurement. The above UE operation may be configured/instructed by the BS/LMF to the UE, or the UE may determine by itself and perform the above operation. For example, when the UE determines that the OTDOA-based UE positioning is not suitable, the UE may request the BS/LMF to estimate the location of the UE based on a PRS beam direction, a PRS resource index related to the PRS beam direction, and/or an RSRP according to a single-cell or multi-cell based E-CID method. In this case, the BS/LMF may determine the location of the UE based on information on the direction and angle of a transmission beam transmitted from each TP/BS and RSRP information. Meanwhile, the PRS resource index reported by the UE may be the index of one PRS resource among PRS resources included in a specific PRS resource set or the index of one specific PRS resource among PRS resources transmitted by one specific TP/BS. For example, when the UE reports a PRS resource with the maximum RSRP value among PRS resources transmitted by each TP/BS, the BS/LMF may obtain the AoD of a PRS transmission beam from each TP/BS to determine the location of the UE. The threshold mentioned in the present embodiment may be configured/indicated by the BS/LMF to the UE or defined by default. In the above-described embodiment, the BS/LMF may more effectively determine/change the positioning method for estimating the location of the UE according to the recommendation/request from the UE. For example, if the BS/LMF intends to perform the OTDOA-based UE positioning, the UE may operate as follows. When the UE determines that it is difficult to use the OTDOA method that requires three or more cells/TPs/BSs at a specific time or that another UE positioning method based on two or less cells/TPs/BS is more suitable than the OTDOA method, based on measurements obtained from PRSs, the UE may request/recommend/report to the BS/LMF/location server to estimate the location of the UE according to a specific RAT-dependent and/or RAT-independent UE positioning method based on a single cell/TP and/or two cells/TPs. For example, when the UE determines, based on PRS measurement results, that the OTDOA method is not suitable, the UE may request/report to introduce a single cell-based E-CID method. The above-described UE operation may be configured/instructed by the BS/LMF/location server. The operation by which the UE determines that another UE positioning method based on two or less cells/TPs/BS is more suitable than the OTDOA method may be defined/configured in various ways. Specifically, the following examples may be defined/configured. In addition, the following UE operations may be configured/instructed by the BS/LMF. (1) The UE may perform measurement on an RS such as a PRS, a CSI-RS and an SS/PBCH block transmitted from the BS/LMF. If it is difficult to guarantee minimum ToA/RSTD quality, that is, quality above a specific threshold for three or more ToAs/RSTDs based on the measurement result, the UE may determine that the OTDOA method is not suitable for UE positioning. The ToA/RSTD quality may be defined as the error range of an expected ToA/RSTD and/or a distance error range corresponding to the ToA/RSTD. (2) The UE may define/configure a very large value such as a positive infinite value among ToA/RSTD report values. Then, by reporting the ToA/RSTD value, the UE may inform the LMF/BS that the ToA/RSTD value for a PRS is not valid. This reporting operation may be considered as signaling that the UE requests/recommends to the LMF/BS to use another UE positioning method other than (or besides) the OTDOA method. In other words, when the BS/LMF receives a very large ToA/RSTD value, the BS/LMF may consider/recognize that the UE requests/recommends use another method other than (or besides) the OTDOA method. (3) The UE may define/configure a very small value such as a negative infinite value among ToA/RSTD quality report values. Then, by reporting the ToA/RSTD value, the UE may inform the LMF/BS that the ToA/RSTD for a PRS has very low quality and many errors. This reporting operation may be considered as signaling that the UE requests/recommends to the LMF/BS to use another UE positioning method other than (or besides) the OTDOA method. In other words, when the BS/LMF receives a very small ToA/RSTD value, the BS/LMF may consider/recognize that the UE requests/recommends use another method other than (or besides) the OTDOA method. (4) The UE may perform measurement on an RS such as a PRS, a CSI-RS and an SS/PBCH block transmitted from the BS/LMF. If the UE is incapable of measuring or reporting ToA/RSTD values for three or more TPs/cells/BSs and/or RS resources and/or RS resource sets related thereto, the UE may determine that it is more suitable to use another positioning method than the OTDOA method. As described above, a polarity of positioning methods may be simultaneously used to estimate the location of the UE instead of using only one positioning method, thereby further improving the UE positioning accuracy. If the location of the UE is estimated by using a positioning method that uses angle information such as an AoD and information such as a ToA together rather than using only the OTDOA method in which the UE reports only an RSTD value for location estimation, the UE positioning accuracy may be further improved. When a plurality of positioning methods are used to estimate the location of the UE, the UE needs to transmit report values for carrying AoD information together with an RSTD. For example, the UE may report the ID of a PRS resource and the RSRP value for the PRS resource to transmit the AoD information. In other words, if the UE includes all of the PRS resource ID, RSRP value, and RSTD value in parameters for reporting PRS-related measurements to the location server, it may be interpreted to mean that the UE requests more advanced positioning from the location server or the location server requests the UE to report a variety of information for the more advanced positioning. Upon receiving the PRS resource ID, RSRP value for the corresponding PRS resource, and RSTD value reported by the UE, the location server may estimate the location of the UE by using all the information in combination. The UE may additionally report the following examples in addition to the RSTD for the above-described complex location estimation (1) PRS resource index+RSRP Here, the PRS resource index may be related to a PRS resource with a maximum RSRP value. The PRS resource index may be used for UE positioning based on the AoD of a PRS beam. (2) PRS resource index+ToA/RSTD Here, the PRS resource index may be related to a PRS resource having a minimum ToA value. If the method of measuring the location of the UE based on the AoD of a PRS transmission beam of a TP/BS and the OTDOA-based UE positioning method based on the ToA/RSTD are used together, the UE may be configured/instructed to report the PRS resource index independently for each method. For example, the LMF/BS may configure/instruct the UE to report the ToA/RSTD and the PRS resource index related to the ToA/RSTD and the RSRP and the PRS resource index related to the RSRP. The configuration/instruction related to the PRS resource index reporting may vary depending on whether the location of the UE is measured based on the AoD of the PRS transmission beam of the TP/BS or the location of the UE is measured based on the ToA/RSTD. For example, when the LMF/BS configures/instructs the UE to report the ToA/RSTD and the PRS resource index, the LMF/BS may configure/instruct the UE to report the index of the PRS resource having the minimum ToA value among PRS resources transmitted from one TP/BS. In addition, when the LMF/BS configures/instructs the UE to report the RSRP and the PRS resource index, the LMF/BS may configure/instruct the UE to report the index of the PRS resource having the maximum RSRP value among PRS resources transmitted from one TP/BS. Meanwhile, even if there is no separate indication/configuration, the UE may automatically report the PRS resource index according to the reporting configuration for the RSRP or ToA/RSTD. For example, the UE may determine whether the PRS resource index to be reported is related to the minimum ToA/RSTD or the maximum RSRP depending on whether PRS measurement is used for the OTDOA-based UE positioning or the AoD-based UE positioning. The above-described UE operation may be defined as default UE operation even though there is no separate instruction/configuration from the BS/LMF, or the UE may automatically configure/execute the UE operation. For the OTDOA-based UE positioning, the BS/LMF may configure/instruct the UE to report the ToA/RSTD and/or the PRS resource index together with the ToA/RSTD to the BS/LMF. At the same time, the BS/LMF may configure/instruct the UE to report the RSRP and PRS resource index rather than the ToA/RSTD and PRS resource index if the quality of a ToA/RSTD measurement measured by the UE is less than or equal to a threshold. If the UE reports the ToA/RSTD and PRS resource index, the corresponding PRS resource index may be the index of the PRS resource having the minimum ToA/RSTD value. If the UE reports the RSRP and PRS resource index, the corresponding PRS resource index may be the index of the PRS resource having the maximum RSRP value. The above-described UE operation may be separately configured/instructed by the BS/LMF to the UE, or the UE may automatically perform the above-described operation. Alternatively, the UE operation may be defined by default. FIG.23illustrates wireless devices applicable to the present disclosure. Referring toFIG.23, a first wireless device100and a second wireless device200may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, {the first wireless device100and the second wireless device200} may correspond to {the wireless device100xand the BS200} and/or {the wireless device100xand the wireless device100x} ofFIG.26. The first wireless device100may include one or more processors102and one or more memories104and additionally further include one or more transceivers106and/or one or more antennas108. The processor(s)102may control the memory(s)104and/or the transceiver(s)106and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s)102may process information within the memory(s)104to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s)106. The processor(s)102may receive radio signals including second information/signals through the transceiver106and then store information obtained by processing the second information/signals in the memory(s)104. The memory(s)104may be connected to the processor(s)102and may store a variety of information related to operations of the processor(s)102. For example, the memory(s)104may store software code including commands for performing a part or the entirety of processes controlled by the processor(s)102or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s)102and the memory(s)104may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)106may be connected to the processor(s)102and transmit and/or receive radio signals through one or more antennas108. Each of the transceiver(s)106may include a transmitter and/or a receiver. The transceiver(s)106may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip. Specifically, commands and/or operations controlled by the processor(s)102and stored in the memory(s)104in the wireless device100according to an embodiment of the present disclosure will be described below. While the operations are described in the context of control operations of the processor(s)102from the perspective of the processor(s)102, software code for performing these operations may be stored in the memory(s)104. The processor(s)102may be configured to control the transceiver(s)106to receive a PRS configuration. The processor(s)102may be configured to control the transceiver(s)106to receive PRSs based on the PRS configuration. In addition, the processor(s)102may be configured to measure an RSRP and/or RSTD for each of a plurality of PRS resources included in the PRS configuration based on the received PRSs and control the transceiver(s)106to report information on the RSTD and a PRS resource index related to the RSTD and/or information on the RSRP and a PRS resource index related to the RSRP, based on the measurement. The processor(s)102may perform the above operations according to the above-described embodiments. Hereinafter, description will be given of instructions and/or operations controlled by processor(s)202and stored in memory(s)204of the second wireless device200according to an embodiment of the present disclosure. While the following operations are described in the context of control operations of the processor(s)202from the perspective of the processor(s)202, software code for performing the operations may be stored in the memory(s)204. The processor(s)202may be configured to control transceiver(s)206to transmit information including that an SS/PBCH block and/or a CSI-RS are used as a PRS resource or to determine a transmission/reception beam for transmitting and receiving the PRS resource to a location server90ofFIG.27. The processor(s)202may be configured to control the transceiver(s)206to transmit a PRS configuration to the first wireless device100. The processor(s)202may be configured to control the transceiver(s)206to transmit PRSs based on the PRS configuration. In addition, the processor(s)202may be configured to control the transceiver(s)206to receive information on RSTDs measured based on the PRSs and PRS resource indices related to the RSTDs and/or information on RSRPs and PRS resource indices related to the RSRPs. The processor(s)202may perform the above operations according to the above-described embodiments. Hereinafter, hardware elements of the wireless devices100and200will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors102and202. For example, the one or more processors102and202may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors102and202may generate one or more protocol data units (PDUs) and/or one or more service data units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers106and206. The one or more processors102and202may receive the signals (e.g., baseband signals) from the one or more transceivers106and206and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors102and202may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors102and202or stored in the one or more memories104and204so as to be driven by the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands. The one or more memories104and204may be connected to the one or more processors102and202and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories104and204may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories104and204may be located at the interior and/or exterior of the one or more processors102and202. The one or more memories104and204may be connected to the one or more processors102and202through various technologies such as wired or wireless connection. The one or more transceivers106and206may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers106and206may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers106and206may be connected to the one or more processors102and202and transmit and receive radio signals. For example, the one or more processors102and202may perform control so that the one or more transceivers106and206may transmit user data, control information, or radio signals to one or more other devices. The one or more processors102and202may perform control so that the one or more transceivers106and206may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers106and206may be connected to the one or more antennas108and208and the one or more transceivers106and206may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas108and208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers106and206may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors102and202. The one or more transceivers106and206may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors102and202from the base band signals into the RF band signals. To this end, the one or more transceivers106and206may include (analog) oscillators and/or filters. In the present disclosure, the at least one memory104or204may store instructions or programs, and the instructions or programs may cause, when executed, at least one processor operably connected to the at least one memory to perform operations according to the above-described embodiments or implementations of the present disclosure. In the present disclosure, a computer-readable storage medium may store at least one instruction or computer program, and the at least one instruction or computer program may cause, when executed by at least one processor, the at least one processor to perform operations according to the above-described embodiments or implementations of the present disclosure. In the present disclosure, a processing device or apparatus may include at least one processor and at least one computer memory which is connectable to the at least one processor. The at least one computer memory may store instructions or programs, and the instructions or programs may cause, when executed, the at least one processor operably connected to the at least one memory to perform operations according to the above-described embodiments or implementations of the present disclosure. FIG.24illustrates another example of a wireless device applied to the present disclosure. The wireless device may be implemented in various forms according to a use-case/service (refer toFIG.26) Referring toFIG.24, wireless devices100and200may correspond to the wireless devices100and200ofFIG.27and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices100and200may include a communication unit110, a control unit120, a memory unit130, and additional components140. The communication unit may include a communication circuit112and transceiver(s)114. For example, the communication circuit112may include the one or more processors102and202and/or the one or more memories104and204ofFIG.27. For example, the transceiver(s)114may include the one or more transceivers106and206and/or the one or more antennas108and208ofFIG.27. The control unit120is electrically connected to the communication unit110, the memory130, and the additional components140and controls overall operation of the wireless devices. For example, the control unit120may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit130. The control unit120may transmit the information stored in the memory unit130to the exterior (e.g., other communication devices) via the communication unit110through a wireless/wired interface or store, in the memory unit130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit110. Accordingly, the detailed operating procedures of the control unit120and the programs/code/commands/information stored in the memory unit130may correspond to at least one operation of the processors102and202ofFIG.27and at least one operation of the memories104and204ofFIG.27. The additional components140may be variously configured according to types of wireless devices. For example, the additional components140may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100aofFIG.26), the vehicles (100b-1and100b-2ofFIG.26), the XR device (100cofFIG.26), the hand-held device (100dofFIG.26), the home appliance (100eofFIG.26), the IoT device (100fofFIG.26), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a fintech device (or a finance device), a security device, a climate/environment device, the AI server/device (400ofFIG.26), the BSs (200ofFIG.26), a network node, etc. The wireless device may be used in a mobile or fixed place according to a use-example/service. InFIG.24, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices100and200may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit110. For example, in each of the wireless devices100and200, the control unit120and the communication unit110may be connected by wire and the control unit120and first units (e.g.,130and140) may be wirelessly connected through the communication unit110. Each element, component, unit/portion, and/or module within the wireless devices100and200may further include one or more elements. For example, the control unit120may be configured by a set of one or more processors. As an example, the control unit120may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory130may be configured by a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof. Hereinafter, the embodiment ofFIG.24will be described in detail with reference to the drawings. FIG.25illustrates an exemplary portable device to which various embodiments of the present disclosure are applied. The portable device may be any of a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smart glasses), and a portable computer (e.g., a laptop). A portable device may also be referred to as mobile station (MS), user terminal (UT), mobile subscriber station (MSS), subscriber station (SS), advanced mobile station (AMS), or wireless terminal (WT). Referring toFIG.25, a hand-held device100may include an antenna unit108, a communication unit110, a control unit120, a memory unit130, a power supply unit140a, an interface unit140b, and an I/O unit140c. The antenna unit108may be configured as a part of the communication unit110. Blocks110to130/140ato140ccorrespond to the blocks110to130/140ofFIG.23, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit120may perform various operations by controlling constituent elements of the hand-held device100. The control unit120may include an Application Processor (AP). The memory unit130may store data/parameters/programs/code/commands needed to drive the hand-held device100. The memory unit130may store input/output data/information. The power supply unit140amay supply power to the hand-held device100and include a wired/wireless charging circuit, a battery, etc. The interface unit140bmay support connection of the hand-held device100to other external devices. The interface unit140bmay include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit140cmay input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit140cmay include a camera, a microphone, a user input unit, a display unit140d, a speaker, and/or a haptic module. As an example, in the case of data communication, the I/O unit140cmay acquire information/signals (e.g., touch, text, voice, images, or video) input by a user and the acquired information/signals may be stored in the memory unit130. The communication unit110may convert the information/signals stored in the memory into radio signals and transmit the converted radio signals to other wireless devices directly or to a BS. The communication unit110may receive radio signals from other wireless devices or the BS and then restore the received radio signals into original information/signals. The restored information/signals may be stored in the memory unit130and may be output as various types (e.g., text, voice, images, video, or haptic) through the I/O unit140c. FIG.26illustrates a vehicle or an autonomous driving vehicle applied to the present disclosure. The vehicle or autonomous driving vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aerial Vehicle (AV), a ship, etc. Referring toFIG.26, a vehicle or autonomous driving vehicle100may include an antenna unit108, a communication unit110, a control unit120, a driving unit140a, a power supply unit140b, a sensor unit140c, and an autonomous driving unit140d. The antenna unit108may be configured as a part of the communication unit110. The blocks110/130/140ato140dcorrespond to the blocks110/130/140ofFIG.30, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit120may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle100. The control unit120may include an Electronic Control Unit (ECU). The driving unit140amay cause the vehicle or the autonomous driving vehicle100to drive on a road. The driving unit140amay include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit140bmay supply power to the vehicle or the autonomous driving vehicle100and include a wired/wireless charging circuit, a battery, etc. The sensor unit140cmay acquire a vehicle state, ambient environment information, user information, etc. The sensor unit140cmay include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit140dmay implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like. For example, the communication unit110may receive map data, traffic information data, etc. from an external server. The autonomous driving unit140dmay generate an autonomous driving path and a driving plan from the obtained data. The control unit120may control the driving unit140asuch that the vehicle or the autonomous driving vehicle100may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit110may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit140cmay obtain a vehicle state and/or surrounding environment information. The autonomous driving unit140dmay update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit110may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous driving vehicles and provide the predicted traffic information data to the vehicles or the autonomous driving vehicles. To perform the embodiments of the present disclosure, there may be provided the location server90as illustrated inFIG.27. The location server90may be logically or physically connected to a wireless device70and/or a network node80. The wireless device70may be the first wireless device100ofFIG.27and/or the wireless device100or200ofFIG.28. The network node80may be the second wireless device100ofFIG.27and/or the wireless device100or200ofFIG.28. The location server90may be, without being limited to, an AMF, an LMF, an E-SMLC, and/or an SLP and may be any device only if the device serves as the location server90for implementing the embodiments of the present disclosure. Although the location server90has used the name of the location server for convenience of description, the location server90may be implemented not as a server type but as a chip type. Such a chip type may be implemented to perform all functions of the location server90which will be described below. Specifically, the location server90includes a transceiver91for communicating with one or more other wireless devices, network nodes, and/or other elements of a network. The transceiver91may include one or more communication interfaces. The transceiver91communicates with one or more other wireless devices, network nodes, and/or other elements of the network connected through the communication interfaces. The location server90includes a processing chip92. The processing chip92may include at least one processor, such as a processor93, and at least one memory device, such as a memory94. The processing chip92may control one or more processes to implement the methods described in this specification and/or embodiments for problems to be solved by this specification and solutions for the problems. In other words, the processing chip92may be configured to perform at least one of the embodiments described in this specification. That is, the processor93includes at least one processor for performing the function of the location server90described in this specification. For example, one or more processors may control the one or more transceivers91ofFIG.32to transmit and receive information. The processing chip92includes a memory94configured to store data, programmable software code, and/or other information for performing the embodiments described in this specification. In other words, according to an embodiment of the present disclosure, the memory95may be configured to store software code95including instructions that, when executed by at least one processor such as the processor93, cause the processor93to perform some or all of the processes controlled by the processor93ofFIG.27or the embodiments of the present disclosure Hereinafter, description will be given of instructions and/or operations controlled by the processor93of the location server90and stored in the memory94according to an embodiment of the present disclosure. While the following operations will be described in the context of control operations of the processor93from the perspective of the processor93, software code for performing the operations may be stored in the memory94. The processor93may be configured to control the transceiver91to transmit a PRS configuration to the second wireless device200ofFIG.23and/or the first wireless device100ofFIG.23. In addition, the processor93may be configured to control the transceiver91to receive information on RSTDs measured based on the PRS configuration and PRS resource indices related to the RSTDs and/or information on RSRPs and PRS resource indices related to the RSRPs. The processor93may be configured to determine the location of a UE based on the information on the RSTDs and PRS resource indices related to the RSTDs and/or the information on the RSRPs and PRS resource indices related to the RSRPs. The processor93may perform the above operations according to the above-described embodiments. FIG.28illustrates a signal process circuit for a transmission signal. Referring toFIG.28, a signal processing circuit1000may include scramblers1010, modulators1020, a layer mapper1030, a precoder1040, resource mappers1050, and signal generators1060. An operation/function ofFIG.31may be performed, without being limited to, the processors102and202and/or the transceivers106and206ofFIG.27. Hardware elements ofFIG.31may be implemented by the processors102and202and/or the transceivers106and206ofFIG.27. For example, blocks1010to1060may be implemented by the processors102and202ofFIG.27. Alternatively, the blocks1010to1050may be implemented by the processors102and202ofFIG.27and the block1060may be implemented by the transceivers106and206ofFIG.27. Codewords may be converted into radio signals via the signal processing circuit1000ofFIG.31. Herein, the codewords are encoded bit sequences of information blocks. The information blocks may include transport blocks (e.g., a UL-SCH transport block, a DL-SCH transport block). The radio signals may be transmitted through various physical channels (e.g., a PUSCH and a PDSCH). Specifically, the codewords may be converted into scrambled bit sequences by the scramblers1010. Scramble sequences used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of a wireless device. The scrambled bit sequences may be modulated to modulation symbol sequences by the modulators1020. A modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complex modulation symbol sequences may be mapped to one or more transport layers by the layer mapper1030. Modulation symbols of each transport layer may be mapped (precoded) to corresponding antenna port(s) by the precoder1040. Outputs z of the precoder1040may be obtained by multiplying outputs y of the layer mapper1030by an N*M precoding matrix W. Herein, N is the number of antenna ports and M is the number of transport layers. The precoder1040may perform precoding after performing transform precoding (e.g., DFT) for complex modulation symbols. Alternatively, the precoder1040may perform precoding without performing transform precoding. The resource mappers1050may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generators1060may generate radio signals from the mapped modulation symbols and the generated radio signals may be transmitted to other devices through each antenna. For this purpose, the signal generators1060may include Inverse Fast Fourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters, Digital-to-Analog Converters (DACs), and frequency up-converters. Signal processing procedures for a signal received in the wireless device may be configured in a reverse manner of the signal processing procedures1010to1060ofFIG.31. For example, the wireless devices (e.g.,100and200ofFIG.28) may receive radio signals from the exterior through the antenna ports/transceivers. The received radio signals may be converted into baseband signals through signal restorers. To this end, the signal restorers may include frequency downlink converters, Analog-to-Digital Converters (ADCs), CP remover, and Fast Fourier Transform (FFT) modules. Next, the baseband signals may be restored to codewords through a resource demapping procedure, a postcoding procedure, a demodulation processor, and a descrambling procedure. The codewords may be restored to original information blocks through decoding. Therefore, a signal processing circuit (not illustrated) for a reception signal may include signal restorers, resource demappers, a postcoder, demodulators, descramblers, and decoders. The implementations described above are those in which the elements and features of the present disclosure are combined in a predetermined form. Each component or feature shall be considered optional unless otherwise expressly stated. Each component or feature may be implemented in a form that is not combined with other components or features. It is also possible to construct implementations of the present disclosure by combining some of the elements and/or features. The order of the operations described in the implementations of the present disclosure may be changed. Some configurations or features of certain implementations may be included in other implementations, or may be replaced with corresponding configurations or features of other implementations. It is clear that the claims that are not expressly cited in the claims may be combined to form an implementation or be included in a new claim by an amendment after the application. The specific operation described herein as being performed by the base station may be performed by its upper node, in some cases. That is, it is apparent that various operations performed for communication with a terminal in a network including a plurality of network nodes including a base station can be performed by the base station or by a network node other than the base station. A base station may be replaced by terms such as a fixed station, a Node B, an eNode B (eNB), an access point, and the like. It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the spirit of the disclosure. Accordingly, the above description should not be construed in a limiting sense in all respects and should be considered illustrative. The scope of the present disclosure should be determined by rational interpretation of the appended claims, and all changes within the scope of equivalents of the present disclosure are included in the scope of the present disclosure. While the present disclosure has been described in the context of a 5G New RAT system, the method and apparatus are also applicable to various other wireless communication systems. | 132,044 |
11943740 | DETAILED DESCRIPTION The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts. Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. FIG.1is a diagram illustrating an example of a wireless communications system and an access network100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations102, UEs104, an Evolved Packet Core (EPC)160, and another core network190(e.g., a 5G Core (5GC)). The base stations102may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells. The base stations102configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC160through first backhaul links132(e.g., S1 interface). The base stations102configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network190through second backhaul links184. In addition to other functions, the base stations102may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations102may communicate directly or indirectly (e.g., through the EPC160or core network190) with each other over third backhaul links134(e.g., X2 interface). The third backhaul links134may be wired or wireless. The base stations102may wirelessly communicate with the UEs104. Each of the base stations102may provide communication coverage for a respective geographic coverage area110. There may be overlapping geographic coverage areas110. For example, the small cell102′ may have a coverage area110′ that overlaps the coverage area110of one or more macro base stations102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links120between the base stations102and the UEs104may include uplink (UL) (also referred to as reverse link) transmissions from a UE104to a base station102and/or downlink (DL) (also referred to as forward link) transmissions from a base station102to a UE104. The communication links120may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations102/UEs104may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell). Certain UEs104may communicate with each other using device-to-device (D2D) communication link158. The D2D communication link158may use the DL/UL WWAN spectrum. The D2D communication link158may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR. The wireless communications system may further include a Wi-Fi access point (AP)150in communication with Wi-Fi stations (STAs)152via communication links154in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs152/AP150may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available. The small cell102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell102′ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP150. The small cell102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. A base station102, whether a small cell102′ or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB180may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE104. When the gNB180operates in mmW or near mmW frequencies, the gNB180may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band (e.g., 3 GHz-300 GHz) has extremely high path loss and a short range. The mmW base station180may utilize beamforming182with the UE104to compensate for the extremely high path loss and short range. The base station180and the UE104may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming. The base station180may transmit a beamformed signal to the UE104in one or more transmit directions182′. The UE104may receive the beamformed signal from the base station180in one or more receive directions182″. The UE104may also transmit a beamformed signal to the base station180in one or more transmit directions. The base station180may receive the beamformed signal from the UE104in one or more receive directions. The base station180/UE104may perform beam training to determine the best receive and transmit directions for each of the base station180/UE104. The transmit and receive directions for the base station180may or may not be the same. The transmit and receive directions for the UE104may or may not be the same. The EPC160may include a Mobility Management Entity (MME)162, other MMES164, a Serving Gateway166, a Multimedia Broadcast Multicast Service (MBMS) Gateway168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway172. The MME162may be in communication with a Home Subscriber Server (HSS)174. The MME162is the control node that processes the signaling between the UEs104and the EPC160. Generally, the MME162provide s bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway166, which itself is connected to the PDN Gateway172. The PDN Gateway172provides UE IP address allocation as well as other functions. The PDN Gateway172and the BM-SC170are connected to the IP Services176. The IP Services176may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a packet switched (P S) Streaming Service, and/or other IP services. The BM-SC170may provide functions for MBMS user service provisioning and delivery. The BM-SC170may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway168may be used to distribute MBMS traffic to the base stations102belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information. The core network190may include an Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. The AMF192may be in communication with a Unified Data Management (UDM)196. The AMF192is the control node that processes the signaling between the UEs104and the core network190. Generally, the AMF192provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF195. The UPF195provides UE IP address allocation as well as other functions. The UPF195is connected to the IP Services197. The IP Services197may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station102provides an access point to the EPC160or core network190for a UE104. Examples of UEs104include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs104may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE104may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. Referring again toFIG.1, in certain aspects, the UE104may include a reception component198configured to monitor for a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message. Reception component198may also be configured to receive the PBCH, where the PBCH indicates a paging control resource set (CORESET) configuration. Reception component198may also be configured to receive remaining minimum system information (RMSI) or other system information (OSI). Reception component198may also be configured to monitor for a paging physical downlink control channel (PDCCH) and a paging message. Reception component198may also be configured to receive the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message. Reception component198may also be configured to decode the paging DCI, where the decoded paging DCI schedules the paging message. Reception component198may also be configured to receive the paging message, where at least one of the paging DCI or the paging message is received more than once. Referring again toFIG.1, in certain aspects, the base station180may include a transmission component199configured to transmit a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message. Transmission component199may also be configured to transmit remaining minimum system information (RMSI) or other system information (OSI). Transmission component199may also be configured to encode paging DCI, where the encoded paging DCI schedules the paging message. Transmission component199may also be configured to transmit a paging physical downlink control channel (PDCCH) including paging downlink control information (DCI), where the paging DCI is associated with a paging message. Transmission component199may also be configured to transmit the paging message, where at least one of the paging DCI or the paging message is transmitted more than once. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. FIG.2Ais a diagram200illustrating an example of a first subframe within a 5G/NR frame structure.FIG.2Bis a diagram230illustrating an example of DL channels within a 5G/NR subframe.FIG.2Cis a diagram250illustrating an example of a second subframe within a 5G/NR frame structure.FIG.2Dis a diagram280illustrating an example of UL channels within a 5G/NR subframe. The 5G/NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided byFIGS.2A,2C, the 5G/NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and X is flexible for use between DL/UL, and subframe 3 being configured with slot format 34 (with mostly UL). While subframes 3, 4 are shown with slot formats 34, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G/NR frame structure that is TDD. Other wireless communication technologies may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies μ 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology there are 14 symbols/slot and 2μslots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2μ*15 kHz, where μ is the numerology 0 to 5. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=5 has a subcarrier spacing of 480 kHz. The symbol length/duration is inversely related to the subcarrier spacing.FIGS.2A-2Dprovide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. As illustrated inFIG.2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as Rxfor one particular configuration, where 100× is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS). FIG.2Billustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. A primary synchronization signal (PSS) may be within symbol2of particular subframes of a frame. The PSS is used by a UE104to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol4of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages. As illustrated inFIG.2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL. FIG.2Dillustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) ACK/NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI. FIG.3is a block diagram of a base station310in communication with a UE350in an access network. In the DL, IP packets from the EPC160may be provided to a controller/processor375. The controller/processor375implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor375provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization. The transmit (TX) processor316and the receive (RX) processor370implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor316handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator374may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE350. Each spatial stream may then be provided to a different antenna320via a separate transmitter318TX. Each transmitter318TX may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission. At the UE350, each receiver354RX receives a signal through its respective antenna352. Each receiver354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor356. The TX processor368and the RX processor356implement layer 1 functionality associated with various signal processing functions. The RX processor356may perform spatial processing on the information to recover any spatial streams destined for the UE350. If multiple spatial streams are destined for the UE350, they may be combined by the RX processor356into a single OFDM symbol stream. The RX processor356then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station310. These soft decisions may be based on channel estimates computed by the channel estimator358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station310on the physical channel. The data and control signals are then provided to the controller/processor359, which implements layer 3 and layer 2 functionality. The controller/processor359can be associated with a memory360that stores program codes and data. The memory360may be referred to as a computer-readable medium which may store computer executable code for wireless communication of a user equipment (UE), the code when executed by a processor (e.g., one or more of RX processor356, TX processor368, and/or controller/processor359) instructs the processor to perform aspects ofFIGS.9,10, and/or11. In the UL, the controller/processor359provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC160. The controller/processor359is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations. Similar to the functionality described in connection with the DL transmission by the base station310, the controller/processor359provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization. Channel estimates derived by a channel estimator358from a reference signal or feedback transmitted by the base station310may be used by the TX processor368to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor368may be provided to different antenna352via separate transmitters354TX. Each transmitter354TX may modulate an RF carrier with a respective spatial stream for transmission. The UL transmission is processed at the base station310in a manner similar to that described in connection with the receiver function at the UE350. Each receiver318RX receives a signal through its respective antenna320. Each receiver318RX recovers information modulated onto an RF carrier and provides the information to a RX processor370. The controller/processor375can be associated with a memory376that stores program codes and data. The memory376may be referred to as a computer-readable medium which may store computer executable code for wireless communication of base station, the code when executed by a processor (e.g., one or more of RX processor370, TX processor316, and/or controller/processor375) instructs the processor to perform aspects ofFIGS.9,10, and/or11. In the UL, the controller/processor375provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE350. IP packets from the controller/processor375may be provided to the EPC160. The controller/processor375is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations. At least one of the TX processor368, the RX processor356, and the controller/processor359may be configured to perform aspects in connection with198ofFIG.1. At least one of the TX processor316, the RX processor370, and the controller/processor375may be configured to perform aspects in connection with199ofFIG.1. Some aspects of wireless communications, e.g., 5G new radio (NR), utilize paging communication, which may limit the coverage of certain transmissions, e.g., millimeter wave (mmW) transmissions. Also, the transmission of paging may be similar to other broadcast channels for mmW transmissions. One reason for the limited coverage of paging is that abase station may use wide broadcast beams, which may be similar to synchronization signal block (SSB) beams. So the base station may use wide SSB beams that may not have large gains, which may make the coverage inadequate. Unicast beams may be more narrow and refined compared to other beams, as unicast beams may be used for direct communication between a base station and a UE. However, for broadcast channels, the base station uses SSB beams that are wider and may have less coverage compared to other beams, e.g., unicast beams. In some instances, the base station may transmit or broadcast SSB beams. The SSB beams may include a physical broadcast channel (PBCH), which carries system information. The PBCH may inform the UE where the control information is located for remaining minimum system information (RMSI) or other system information (OSI). The PBCH may also indicate a control resource set (CORESET) configuration for RMSI and paging communication. Additionally, a physical downlink control channel (PDCCH) may be transmitted by the base station, which may schedule the RMSI. The RMSI may contain additional system information, which may contain information about paging occasions, time offsets, periodicity, and/or search space configuration. Also, the RMSI or OSI may contain information regarding monitoring occasions for paging. In some aspects, monitoring occasions may be indicated by RMSI, but the scheduling may be performed by the paging PDCCH. In some instances, the paging PDCCH and the paging may be in the same slot. And each slot may be an amount of symbols, e.g., 14 symbols. Also, a CORESET may be used for the PDCCH scheduling. A variety of paging parameters may be explicitly signaled in the corresponding RMSI or OSI. For instance, a paging occasion configuration, e.g., time offset, duration, periodicity, may be signaled in RMSI or OSI. A PDCCH configuration may provide a search space configuration including monitoring occasions within the paging occasion. For paging CORESET configurations, the same configuration may be reused for an RMSI CORESET, e.g., as indicated in the PBCH. Also, the paging CORESET may schedule the paging. In some aspects, a transmission of a paging DCI, e.g., via a paging PDCCH, may be followed by a transmission of a paging message. Further, paging DCI may be the content that is transmitted by the PDCCH. In some instances, paging DCI and a paging message may be sent in the same slot. Additionally, a UE grouping may be utilized, where the UE is configured of its paging occasions per slot. Short paging messages, e.g., systemInfoModification, cmas-Indication, and etws-Indication messages, may be transmitted in the paging DCI. Moreover, a UE may assume quasi co-location (QCL) between SSBs, paging DCIs, and paging messages. So paging DCIs and paging messages may be transmitted using the same beams as SSBs. When the UE receives one SSB, it may follow the same beam for the paging DCIs and paging messages. In some aspects, a UE may not combine multiple paging DCIs within one paging occasion (PO). So there may be a single paging DCI or a paging message in a paging PDCCH. Based on the above, it may be beneficial to improve the coverage of paging. As such, it may be beneficial to include the repetition of paging DCI and/or paging messages. So it may be beneficial to combine multiple paging DCIs within one paging occasion (PO), such that there is repetition of paging DCIs and a corresponding increase in paging coverage. Aspects of the present disclosure may improve the coverage of paging DCIs and/or paging messages. For instance, aspects of the present disclosure may include the repetition of paging DCI and/or the repetition of paging messages. For example, the present disclosure may combine multiple paging DCIs within one paging occasion (PO), such that there is repetition of paging DCIs and a corresponding increase in paging coverage. In some aspects, the base station may schedule and transmit repeated paging DCI and/or repeated paging messages. Scheduling of the repeated paging PDCCH and/or paging messages and/or its corresponding resources may be implicitly indicated by a PBCH. As indicated above, the PBCH may include the CORESET configuration for the RMSI and paging. Scheduling of paging PDCCH repetition may be indicated by an alternative interpretation of some bit fields (bitfields) or tables in a PBCH that are used for configuration of a CORESET, e.g., CORESET0. For instance, legacy UEs may use a previous interpretation of the CORESET, e.g., CORESET0, as well as a configuration of bitfields or tables. For these bitfields, it may be indicated that there is paging DCI or paging repetition. For instance, a new column may be added to the configuration tables of PDCCH monitoring occasions for a certain search space, e.g., Type0-PDCCH common search space, to indicate a paging PDCCH repetition. For example, SS or PBCH block and a control resource set may include a certain multiplexing pattern, e.g., multiplexing pattern 1, and frequency range, e.g., frequency range 2. The resources and parameters of the repetition may be dependent on the parameters of the search space, e.g., Type0-PDCCH common search space. Further, additional details may be indicated based on a separate table in a specification, or based on a corresponding RMSI or OSI configuration. So extra information in the bitfields or tables in the PDCCH may indicate that there is a repetition of the paging DCI or paging message. The location of the repetition may be indicated via additional bitfields or tables. Also, the additional information may be transmitted over the corresponding RMSI. So UEs may interpret new information from these bitfields or tables, such as by adding rows or columns to the bitfields or tables. In some aspects, because legacy UEs may use the tables, the tables may not be altered. Newer UEs may interpret new information from the same tables, in addition to old information in the tables. Based on these bitfields, the new UEs may receive the configuration of a CORESET, e.g., CORESET0, and based on the new details that are added for these tables, the new UEs may interpret that for a certain selection of the bitfields, the UEs may also include repetition of the paging DCI or paging message. For certain CORESET configurations, the UEs may interpret paging repetitions based on added information in a bitfield or table, as well as added information in the RMSI or OSI. In some instances, scheduling of repeated paging PDCCH and/or a paging message and its corresponding resources may be indicated by its corresponding RMSI or OSI. Additionally, PDCCH monitoring aggregation may be indicated in the search space configuration of the paging PDCCH in the corresponding RMSI or OSI. The paging monitoring aggregation may also be indicated in the paging occasion configuration in the corresponding RMSI or OSI. So the RMSI may indicate the amount of paging repetitions and the location of the paging repetitions. The PBCH may indicate the configuration of a CORESET, and the RMSI may indicate all of the information regarding the paging repetitions and/or the location of the paging repetitions. So there may be added information in the RMSI that may also indicate the details for paging repetition. As indicated above, the repeated paging may be implicitly indicated by the PBCH. In some instances, the content of the PBCH may not change, so the indication may be implicit. For instance, additional columns in tables or bitfields may correspond to additional interpretation. The repeated paging may also be explicitly indicated by the RMSI or OSI. In some instances, an order of transmission from a base station to a UE may be as follows: PBCH, RMSI PDCCH (which may be a small amount of control information that schedules the RMSI), RMSI, paging PDCCH, and paging message. As indicated herein, the repetition of paging may be indicated by paging DCI. Repetition numbers for paging DCI and paging messages may be different. For example, the base station may configure a number of repetitions, e.g., four repetitions, via monitoring aggregation for paging DCI and two repetitions for a paging message. The set of slots containing paging DCI repetitions may include one slot that has both paging DCI and paging. This slot may be used by some UEs to monitor paging. Also, this slot may be the last slot among the slots that contain copies of paging DCI and the first slot among the slots that contain copies of a paging message. FIG.4is a diagram400illustrating example paging communication in accordance with one or more techniques of the present disclosure. As shown inFIG.4, diagram400includes a number of slots, e.g., slot410, slot411, slot412, and slot413, CORESET420, paging PDCCH430, and paging message440.FIG.4displays that the paging DCI may be repeated via monitoring aggregation. Also, the paging DCI and the paging message440may be monitored by some UEs, e.g., legacy UEs. Further, there may be a repetition of paging message440. As shown in slots410and411, the paging DCI is transmitted over the paging PDCCH430within the CORESET420. Accordingly, the CORESET420and the paging PDCCH430may be transmitted in the same slots. Also, the paging message440may be scheduled in the same slot410. As shown in slots412and413, aspects of the present disclosure may also include repetitions of paging DCI and repetitions of paging message440. In some aspects, repetitions of paging DCI or a paging message may be indicated via a PBCH. Also, repetitions of paging DCI or a paging message may be indicated by RMSI or OSI. Further, repetitions of paging DCI may be indicated via RMSI, and repetitions of paging may be indicated by paging DCI, as paging DCI may schedule the paging message. In some instances, a set of slots including the paging DCI repetition may include at least one slot that includes both the paging DCI repetition and the paging message repetition. FIG.5is a diagram500illustrating example communication between a UE502and a base station504. At510, UE502may monitor for a physical broadcast channel (PBCH), the PBCH indicating at least one of a repetition of a paging DCI or a repetition of a paging message. At520, base station504may transmit a PBCH, e.g., PBCH524, the PBCH indicating at least one of a repetition of a paging DCI or a repetition of a paging message. At522, UE502may receive the PBCH, e.g., PBCH524, where the PBCH indicates a paging control resource set (CORESET) configuration. In some aspects, the paging CORESET configuration may implicitly indicate at least one of a repetition of the paging DCI or a repetition of the paging message. Further, the paging CORESET configuration may include one or more tables or one or more bit fields associated with the repetition of the paging DCI or the repetition of the paging message. At530, base station504may transmit remaining minimum system information (RMSI) or other system information (OSI), e.g., RMSI or OSI534. At532, UE502may receive RMSI or OSI, e.g., RMSI or OSI534. In some aspects, the RMSI or the OSI may indicate at least one of the repetition of the paging DCI or the repetition of the paging message. Also, the RMSI or the OSI may indicate a search space for the paging PDCCH or the paging DCI. At540, base station504may encode paging DCI, where the encoded paging DCI schedules the paging message. At550, UE502may monitor for a paging physical downlink control channel (PDCCH) and a paging message. At560, base station504may transmit a paging PDCCH including paging downlink control information (DCI), e.g., paging PDCCH564, where the paging DCI may be associated with a paging message. At562, UE502may receive the paging PDCCH including paging downlink control information (DCI), e.g., paging PDCCH564, where the paging DCI is associated with the paging message. In some instances, the paging PDCCH may correspond to at least one of a paging CORESET configuration or a search space. Also, the paging DCI may be included in a paging occasion (PO). At570, UE502may decode the paging DCI, where the decoded paging DCI schedules the paging message. In some aspects, the paging DCI may indicate the repetition of the paging message. Also, the paging DCI may schedule the paging message. At580, base station504may transmit a paging message, e.g., paging message584, where at least one of the paging DCI or the paging message is transmitted more than once. At582, UE502may receive the paging message, e.g., paging message584, where at least one of the paging DCI or the paging message is received more than once. In some aspects, repetition of the paging DCI may correspond to the paging DCI being transmitted or received more than once, and repetition of the paging message may correspond to the paging message being transmitted or received more than once. Also, at least one of the paging DCI or the paging message may be transmitted or received in one or more slots or transmitted or received via multiple monitoring occasions. Moreover, the paging message and the paging DCI may be transmitted or received in a same slot of the one or more slots. FIG.6is a flowchart600of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the UE104,350,502; an apparatus1002; a processing system, which may include the memory360and which may be the entire UE or a component of the UE, such as the TX processor368, the controller/processor359, transmitter354TX, antenna(s)352, and/or the like). The methods described herein may provide a number of benefits, such as improving communication signaling, resource utilisation, and/or power savings. At608, the apparatus may monitor for a paging physical downlink control channel (PDCCH) and a paging message, as described in connection with the examples inFIGS.4and5. For example, UE502may monitor for a paging physical downlink control channel (PDCCH) and a paging message, as described in connection with550inFIG.5. Further,608may be performed by determination component1040inFIG.10. At610, the apparatus may receive the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message, as described in connection with the examples inFIGS.4and5. For example, UE502may receive the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message, as described in connection with562inFIG.5. Further,610may be performed by determination component1040inFIG.10. In some instances, the paging PDCCH may correspond to at least one of a paging CORESET configuration or a search space, as described in connection with the examples inFIGS.4and5. Also, the paging DCI may be included in a paging occasion (PO), as described in connection with the examples inFIGS.4and5. At614, the apparatus may receive the paging message, where at least one of the paging DCI or the paging message is received more than once, as described in connection with the examples inFIGS.4and5. For example, UE502may receive the paging message, where at least one of the paging DCI or the paging message is received more than once, as described in connection with582inFIG.5. Further,614may be performed by determination component1040inFIG.10. In some aspects, repetition of the paging DCI may correspond to the paging DCI being received more than once, and repetition of the paging message may correspond to the paging message being received more than once, as described in connection with the examples inFIGS.4and5. Also, at least one of the paging DCI or the paging message may be received in one or more slots or received via multiple monitoring occasions, as described in connection with the examples inFIGS.4and5. Moreover, the paging message and the paging DCI may be received in a same slot of the one or more slots, as described in connection with the examples inFIGS.4and5. FIG.7is a flowchart700of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the UE104,350,502; an apparatus1002; a processing system, which may include the memory360and which may be the entire UE or a component of the UE, such as the TX processor368, the controller/processor359, transmitter354TX antenna(s)352, and/or the like). The methods described herein may provide a number of benefits, such as improving communication signaling, resource utilisation, and/or power savings. At702, the apparatus may monitor for a physical broadcast channel (PBCH), the PBCH indicating at least one of a repetition of the paging DCI or a repetition of the paging message, as described in connection with the examples inFIGS.4and5. For example, UE502may monitor for a physical broadcast channel (PBCH), the PBCH indicating at least one of a repetition of the paging DCI or a repetition of the paging message, as described in connection with510inFIG.5. Further,702may be performed by determination component1040inFIG.10. At704, the apparatus may receive the PBCH, where the PBCH indicates a paging control resource set (CORESET) configuration, as described in connection with the examples inFIGS.4and5. For example, UE502may receive the PBCH, where the PBCH indicates a paging control resource set (CORESET) configuration, as described in connection with522inFIG.5. Further,704may be performed by determination component1040inFIG.10. In some aspects, the paging CORESET configuration may implicitly indicate at least one of a repetition of the paging DCI or a repetition of the paging message, as described in connection with the examples inFIGS.4and5. Further, the paging CORESET configuration may include one or more tables or one or more bit fields associated with the repetition of the paging DCI or the repetition of the paging message, as described in connection with the examples inFIGS.4and5. At706, the apparatus may receive RMSI or OSI, as described in connection with the examples inFIGS.4and5. For example, UE502may receive RMSI or OSI, as described in connection with532inFIG.5. Further,706may be performed by determination component1040inFIG.10. In some aspects, the RMSI or the OSI may indicate at least one of the repetition of the paging DCI or the repetition of the paging message, as described in connection with the examples inFIGS.4and5. Also, the RMSI or the OSI may indicate a search space for the paging PDCCH or the paging DCI, as described in connection with the examples inFIGS.4and5. At708, the apparatus may monitor for a paging physical downlink control channel (PDCCH) and a paging message, as described in connection with the examples inFIGS.4and5. For example, UE502may monitor for a paging physical downlink control channel (PDCCH) and a paging message, as described in connection with550inFIG.5. Further,708may be performed by determination component1040inFIG.10. At710, the apparatus may receive the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message, as described in connection with the examples inFIGS.4and5. For example, UE502may receive the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message, as described in connection with562inFIG.5. Further,710may be performed by determination component1040inFIG.10. In some instances, the paging PDCCH may correspond to at least one of a paging CORESET configuration or a search space, as described in connection with the examples inFIGS.4and5. Also, the paging DCI may be included in a paging occasion (PO), as described in connection with the examples inFIGS.4and5. At712, the apparatus may decode the paging DCI, where the decoded paging DCI schedules the paging message, as described in connection with the examples inFIGS.4and5. For example, UE502may decode the paging DCI, where the decoded paging DCI schedules the paging message, as described in connection with570inFIG.5. Further,712may be performed by determination component1040inFIG.10. In some aspects, the paging DCI may indicate the repetition of the paging message, as described in connection with the examples inFIGS.4and5. Also, the paging DCI may schedule the paging message, as described in connection with the examples inFIGS.4and5. At714, the apparatus may receive the paging message, where at least one of the paging DCI or the paging message is received more than once, as described in connection with the examples inFIGS.4and5. For example, UE502may receive the paging message, where at least one of the paging DCI or the paging message is received more than once, as described in connection with582inFIG.5. Further,714may be performed by determination component1040inFIG.10. In some aspects, repetition of the paging DCI may correspond to the paging DCI being received more than once, and repetition of the paging message may correspond to the paging message being received more than once, as described in connection with the examples inFIGS.4and5. Also, at least one of the paging DCI or the paging message may be received in one or more slots or received via multiple monitoring occasions, as described in connection with the examples inFIGS.4and5. Moreover, the paging message and the paging DCI may be received in a same slot of the one or more slots, as described in connection with the examples inFIGS.4and5. FIG.8is a flowchart800of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., the base station102,180,310,504; an apparatus1102; a processing system, which may include the memory376and which may be the entire base station or a component of the base station, such as the antenna(s)320, receiver318RX, the RX processor370, the controller/processor375, and/or the like). The methods described herein may provide a number of benefits, such as improving communication signaling, resource utilisation, and/or power savings. At808, the apparatus may transmit a paging PDCCH including paging downlink control information (DCI), where the paging DCI may be associated with a paging message, as described in connection with the examples inFIGS.4and5. For example, base station504may transmit a paging PDCCH including paging downlink control information (DCI), where the paging DCI may be associated with a paging message, as described in connection with560inFIG.5. Further,808may be performed by determination component1140inFIG.11. In some instances, the paging PDCCH may correspond to at least one of a paging CORESET configuration or a search space, as described in connection with the examples inFIGS.4and5. Also, the paging DCI may be included in a paging occasion (PO), as described in connection with the examples inFIGS.4and5. In some aspects, the paging DCI may indicate the repetition of the paging message, as described in connection with the examples inFIGS.4and5. Also, the paging DCI may schedule the paging message, as described in connection with the examples inFIGS.4and5. At810, the apparatus may transmit a paging message, where at least one of the paging DCI or the paging message is transmitted more than once, as described in connection with the examples inFIGS.4and5. For example, base station504may transmit a paging message, where at least one of the paging DCI or the paging message is transmitted more than once, as described in connection with580inFIG.5. Further,810may be performed by determination component1140inFIG.11. In some aspects, repetition of the paging DCI may correspond to the paging DCI being transmitted more than once, and repetition of the paging message may correspond to the paging message being transmitted more than once, as described in connection with the examples inFIGS.4and5. Also, at least one of the paging DCI or the paging message may be transmitted in one or more slots or transmitted via multiple monitoring occasions, as described in connection with the examples inFIGS.4and5. Moreover, the paging message and the paging DCI may be transmitted in a same slot of the one or more slots, as described in connection with the examples inFIGS.4and5. FIG.9is a flowchart900of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., the base station102,180,310,504; an apparatus1102; a processing system, which may include the memory376and which may be the entire base station or a component of the base station, such as the antenna(s)320, receiver318RX, the RX processor370, the controller/processor375, and/or the like). The methods described herein may provide a number of benefits, such as improving communication signaling, resource utilisation, and/or power savings. At902, the apparatus may transmit a PBCH, the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message, as described in connection with the examples inFIGS.4and5. For example, base station504may transmit a PBCH, the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message, as described in connection with520inFIG.5. Further,902may be performed by determination component1140inFIG.11. In some aspects, the paging CORESET configuration may implicitly indicate atleast one of a repetition of the paging DCI or a repetition of the paging message, as described in connection with the examples inFIGS.4and5. Further, the paging CORESET configuration may include one or more tables or one or more bit fields associated with the repetition of the paging DCI or the repetition of the paging message, as described in connection with the examples inFIGS.4and5. At904, the apparatus may transmit remaining minimum system information (RMSI) or other system information (OSI), as described in connection with the examples inFIGS.4and5. For example, base station504may transmit remaining minimum system information (RMSI) or other system information (OSI), as described in connection with530inFIG.5. Further,904may be performed by determination component1140inFIG.11. In some aspects, the RMSI or the OSI may indicate at least one of the repetition of the paging DCI or the repetition of the paging message, as described in connection with the examples inFIGS.4and5. Also, the RMSI or the OSI may indicate a search space for the paging PDCCH or the paging DCI, as described in connection with the examples inFIGS.4and5. At906, the apparatus may encode paging DCI, where the encoded paging DCI schedules the paging message, as described in connection with the examples in FIGS.4and5. For example, base station504may encode paging DCI, where the encoded paging DCI schedules the paging message, as described in connection with540inFIG.5. Further,906may be performed by determination component1140inFIG.11. At908, the apparatus may transmit a paging PDCCH including paging downlink control information (DCI), where the paging DCI may be associated with a paging message, as described in connection with the examples inFIGS.4and5. For example, base station504may transmit a paging PDCCH including paging downlink control information (DCI), where the paging DCI may be associated with a paging message, as described in connection with560inFIG.5. Further,908may be performed by determination component1140inFIG.11. In some instances, the paging PDCCH may correspond to at least one of a paging CORESET configuration or a search space, as described in connection with the examples inFIGS.4and5. Also, the paging DCI may be included in a paging occasion (PO), as described in connection with the examples inFIGS.4and5. In some aspects, the paging DCI may indicate the repetition of the paging message, as described in connection with the examples inFIGS.4and5. Also, the paging DCI may schedule the paging message, as described in connection with the examples inFIGS.4and5. At910, the apparatus may transmit a paging message, where at least one of the paging DCI or the paging message is transmitted more than once, as described in connection with the examples inFIGS.4and5. For example, base station504may transmit a paging message, where at least one of the paging DCI or the paging message is transmitted more than once, as described in connection with580inFIG.5. Further,910may be performed by determination component1140inFIG.11. In some aspects, repetition of the paging DCI may correspond to the paging DCI being transmitted more than once, and repetition of the paging message may correspond to the paging message being transmitted more than once, as described in connection with the examples inFIGS.4and5. Also, at least one of the paging DCI or the paging message may be transmitted in one or more slots or transmitted via multiple monitoring occasions, as described in connection with the examples inFIGS.4and5. Moreover, the paging message and the paging DCI may be transmitted in a same slot of the one or more slots, as described in connection with the examples inFIGS.4and5. FIG.10is a diagram1000illustrating an example of a hardware implementation for an apparatus1002. The apparatus1002is a UE and includes a cellular baseband processor1004(also referred to as a modem) coupled to a cellular RF transceiver1022and one or more subscriber identity modules (SIM) cards1020, an application processor1006coupled to a secure digital (SD) card1008and a screen1010, a Bluetooth module1012, a wireless local area network (WLAN) module1014, a Global Positioning System (GPS) module1016, and a power supply1018. The cellular baseband processor1004communicates through the cellular RF transceiver1022with the UE104and/or BS102/180. The cellular baseband processor1004may include a computer-readable medium/memory. The computer-readable medium/memory may be non-transitory. The cellular baseband processor1004is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor1004, causes the cellular baseband processor1004to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor1004when executing software. The cellular baseband processor1004further includes a reception component1030, a communication manager1032, and a transmission component1034. The communication manager1032includes the one or more illustrated components. The components within the communication manager1032may be stored in the computer-readable medium/memory and/or configured as hardware within the cellular baseband processor1004. The cellular baseband processor1004may be a component of the UE350and may include the memory360and/or at least one of the TX processor368, the RX processor356, and the controller/processor359. In one configuration, the apparatus1002may be a modem chip and include just the baseband processor1004, and in another configuration, the apparatus1002may be the entire UE (e.g., see350ofFIG.3) and include the aforediscussed additional modules of the apparatus1002. The communication manager1032includes a determination component1040that is configured to monitor for a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message, e.g., as described in connection with step702inFIG.7. Determination component1040may be further configured to receive the PBCH, where the PBCH indicates a paging control resource set (CORESET) configuration, e.g., as described in connection with step704inFIG.7. Determination component1040may be further configured to receive remaining minimum system information (RMSI) or other system information (OSI), e.g., as described in connection with step706inFIG.7. Determination component1040may be further configured to monitor for a paging physical downlink control channel (PDCCH) and a paging message, e.g., as described in connection with step708inFIG.7. Determination component1040may be further configured to receive the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message, e.g., as described in connection with step710inFIG.7. Determination component1040may be further configured to decode the paging DCI, where the decoded paging DCI schedules the paging message, e.g., as described in connection with step712inFIG.7. Determination component1040may be further configured to receive the paging message, where at least one of the paging DCI or the paging message is received more than once, e.g., as described in connection with step714inFIG.7. The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts ofFIGS.5,6, and7. As such, each block in the aforementioned flowcharts ofFIGS.5,6, and7may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. In one configuration, the apparatus1002, and in particular the cellular baseband processor1004, includes means for monitoring for a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message; means for receiving the PBCH, where the PBCH indicates a paging control resource set (CORESET) configuration; means for receiving remaining minimum system information (RMSI) or other system information (OSI); means for monitoring for a paging physical downlink control channel (PDCCH) and a paging message; means for receiving the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message; means for decoding the paging DCI, where the decoded paging DCI schedules the paging message; and means for receiving the paging message, where at least one of the paging DCI or the paging message is received more than once. The aforementioned means may be one or more of the aforementioned components of the apparatus1002configured to perform the functions recited by the aforementioned means. As described supra, the apparatus1002may include the TX Processor368, the RX Processor356, and the controller/processor359. As such, in one configuration, the aforementioned means may be the TX Processor368, the RX Processor356, and the controller/processor359configured to perform the functions recited by the aforementioned means. FIG.11is a diagram1100illustrating an example of a hardware implementation for an apparatus1102. The apparatus1102is a base station (BS) and includes a baseband unit1104. The baseband unit1104may communicate through a cellular RF transceiver1122with the UE104. The baseband unit1104may include a computer-readable medium/memory. The baseband unit1104is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the baseband unit1104, causes the baseband unit1104to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit1104when executing software. The baseband unit1104further includes a reception component1130, a communication manager1132, and a transmission component1134. The communication manager1132includes the one or more illustrated components. The components within the communication manager1132may be stored in the computer-readable medium/memory and/or configured as hardware within the baseband unit1104. The baseband unit1104may be a component of the BS310and may include the memory376and/or at least one of the TX processor316, the RX processor370, and the controller/processor375. The communication manager1132includes a determination component1140that is configured to transmit a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message, e.g., as described in connection with step902inFIG.9. Determination component1140may be further configured to transmit remaining minimum system information (RMSI) or other system information (OSI), e.g., as described in connection with step904inFIG.9. Determination component1140may be further configured to encode the paging DCI, where the encoded paging DCI schedules the paging message, e.g., as described in connection with step906inFIG.9. Determination component1140may be further configured to transmit a paging physical downlink control channel (PDCCH) including paging downlink control information (DCI), where the paging DCI is associated with a paging message, e.g., as described in connection with step908inFIG.9. Determination component1140may be further configured to transmit the paging message, where at least one of the paging DCI or the paging message is transmitted more than once, e.g., as described in connection with step910inFIG.9. The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts ofFIGS.5,8, and9. As such, each block in the aforementioned flowcharts ofFIGS.5,8, and9may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. In one configuration, the apparatus1102, and in particular the baseband unit1104, includes means for transmitting a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message; means for transmitting remaining minimum system information (RMSI) or other system information (OSI); means for encoding the paging DCI, where the encoded paging DCI schedules the paging message; means for transmitting a paging physical downlink control channel (PDCCH) including paging downlink control information (DCI), where the paging DCI is associated with a paging message; and means for transmitting the paging message, where at least one of the paging DCI or the paging message is transmitted more than once. The aforementioned means may be one or more of the aforementioned components of the apparatus1102configured to perform the functions recited by the aforementioned means. As described supra, the apparatus1102may include the TX Processor316, the RX Processor370, and the controller/processor375. As such, in one configuration, the aforementioned means may be the TX Processor316, the RX Processor370, and the controller/processor375configured to perform the functions recited by the aforementioned means. It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.” The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation. Aspect 1 is an apparatus for wireless communication at a UE including at least one processor coupled to a memory and configured to: monitor for a paging physical downlink control channel (PDCCH) and a paging message; receive the paging PDCCH including paging downlink control information (DCI), where the paging DCI is associated with the paging message; and receive the paging message, where at least one of the paging DCI or the paging message is received more than once. Aspect 2 is the apparatus of aspect 1, where repetition of the paging DCI corresponds to the paging DCI being received more than once, and repetition of the paging message corresponds to the paging message being received more than once. Aspect 3 is the apparatus of any of aspects 1 and 2, where the at least one processor is further configured to: monitor for a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message. Aspect 4 is the apparatus of any of aspects 1 to 3, where the at least one processor is further configured to: receive the PBCH, where the PBCH indicates a paging control resource set (CORESET) configuration. Aspect 5 is the apparatus of any of aspects 1 to 4, where the paging CORESET configuration implicitly indicates at least one of the repetition of the paging DCI or the repetition of the paging message. Aspect 6 is the apparatus of any of aspects 1 to 5, where the paging CORESET configuration includes one or more tables or one or more bit fields associated with the repetition of the paging DCI or the repetition of the paging message. Aspect 7 is the apparatus of any of aspects 1 to 6, where the at least one processor is further configured to: receive remaining minimum system information (RMSI) or other system information (OSI). Aspect 8 is the apparatus of any of aspects 1 to 7, where the RMSI or the OSI indicates at least one of the repetition of the paging DCI or the repetition of the paging message. Aspect 9 is the apparatus of any of aspects 1 to 8, where the RMSI or the OSI indicate s a search space for the paging PDCCH or the paging DCI. Aspect 10 is the apparatus of any of aspects 1 to 9, where at least one of the paging DCI or the paging message is received in one or more slots or received via multiple monitoring occasions. Aspect 11 is the apparatus of any of aspects 1 to 10, where the paging message and the paging DCI are received in a same slot of the one or more slots. Aspect 12 is the apparatus of any of aspects 1 to 11, where the paging DCI indicates the repetition of the paging message. Aspect 13 is the apparatus of any of aspects 1 to 12, where the paging DCI schedules the paging message. Aspect 14 is the apparatus of any of aspects 1 to 13, where the at least one processor is further configured to: decode the paging DCI, where the decoded paging DCI schedules the paging message. Aspect 15 is the apparatus of any of aspects 1 to 14, where the paging PDCCH corresponds to at least one of a paging CORESET configuration or a search space. Aspect 16 is the apparatus of any of aspects 1 to 15, where the paging DCI is included in a paging occasion (PO). Aspect 17 is the apparatus of any of aspects 1 to 16, further including a transceiver coupled to the at least one processor. Aspect 18 is a method of wireless communication for implementing any of aspects 1 to 17. Aspect 19 is an apparatus for wireless communication including means for implementing any of aspects 1 to 17. Aspect 20 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 17. Aspect 21 is an apparatus for wireless communication at a base station including at least one processor coupled to a memory and configured to: transmit a paging physical downlink control channel (PDCCH) including paging downlink control information (DCI), where the paging DCI is associated with a paging message; and transmit the paging message, where at least one of the paging DCI or the paging message is transmitted more than once. Aspect 22 is the apparatus of aspect 21, where repetition of the paging DCI corresponds to the paging DCI being transmitted more than once, and repetition of the paging message corresponds to the paging message being transmitted more than once. Aspect 23 is the apparatus of any of aspects 21 and 22, where the at least one processor is further configured to: transmit a physical broadcast channel (PBCH), the PBCH indicating at least one of the repetition of the paging DCI or the repetition of the paging message. Aspect 24 is the apparatus of any of aspects 21 to 23, where the PBCH indicates a paging control resource set (CORESET) configuration. Aspect 25 is the apparatus of any of aspects 21 to 24, where the paging CORESET configuration implicitly indicates at least one of the repetition of the paging DCI or the repetition of the paging message. Aspect 26 is the apparatus of any of aspects 21 to 25, where the paging CORESET configuration includes one or more tables or one or more bit fields associated with the repetition of the paging DCI or the repetition of the paging message. Aspect 27 is the apparatus of any of aspects 21 to 26, where the at least one processor is further configured to: transmit remaining minimum system information (RMSI) or other system information (OSI). Aspect 28 is the apparatus of any of aspects 21 to 27, where the RMSI or the OSI indicates at least one of the repetition of the paging DCI or the repetition of the paging message. Aspect 29 is the apparatus of any of aspects 21 to 28, where the RMSI or the OSI indicates a search space for the paging PDCCH or the paging DCI. Aspect 30 is the apparatus of any of aspects 21 to 29, where at least one of the paging DCI or the paging message is transmitted in one or more slots or transmitted via multiple monitoring occasions. Aspect 31 is the apparatus of any of aspects 21 to 30, where the paging message and the paging DCI are transmitted in a same slot of the one or more slots. Aspect 32 is the apparatus of any of aspects 21 to 31, where the paging DCI indicates the repetition of the paging message. Aspect 33 is the apparatus of any of aspects 21 to 32, where the paging DCI schedules the paging message. Aspect 34 is the apparatus of any of aspects 21 to 33, where the at least one processor is further configured to: encode the paging DCI, where the encoded paging DCI schedules the paging message. Aspect 35 is the apparatus of any of aspects 21 to 34, where the paging PDCCH corresponds to at least one of a paging CORESET configuration or a search space. Aspect 36 is the apparatus of any of aspects 21 to 35, where the paging DCI is included in a paging occasion (PO). Aspect 37 is the apparatus of any of aspects 21 to 36, further including a transceiver coupled to the at least one processor. Aspect 38 is a method of wireless communication for implementing any of aspects 21 to 37. Aspect 39 is an apparatus for wireless communication including means for implementing any of aspects 21 to 37. Aspect 40 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 21 to 37. | 82,046 |
11943741 | DETAILED DESCRIPTION Various example embodiments will now be described more fully with reference to the accompanying drawings in which some example embodiments are shown. Detailed example embodiments are disclosed herein. However, specific structural and functional details disclosed herein are merely representative for purposes of describing the example embodiments. The embodiments may, however, may be embodied in many alternate forms and should not be construed as limited to only the example embodiments set forth herein. It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments of the present invention. As used herein, the term “and/or,” includes any and all combinations of one or more of the associated listed items. It will be understood that when an element is referred to as being “connected,” or “coupled,” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected,” or “directly coupled,” to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between,” versus “directly between,” “adjacent,” versus “directly adjacent,” etc.). The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments of the invention. As used herein, the singular forms “a,” “an,” and “the,” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Specific details are provided in the following description to provide a thorough understanding of the example embodiments. However, it will be understood by one of ordinary skill in the art that example embodiments may be practiced without these specific details. For example, systems may be shown in block diagrams in order not to obscure the example embodiments in unnecessary detail. In other instances, well-known processes, structures and techniques may be shown without unnecessary detail in order to avoid obscuring example embodiments. Also, it is noted that example embodiments may be described as a process depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. A process may be terminated when its operations are completed, but may also have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function. Moreover, as disclosed herein, the term “memory” may represent one or more devices for storing data, including random access memory (RAM), magnetic RAM, core memory, and/or other machine readable mediums for storing information. The term “storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information. The term “computer-readable medium” may include, but is not limited to, portable or fixed storage devices, optical storage devices, wireless channels, and various other mediums capable of storing, containing or carrying instruction(s) and/or data. Furthermore, example embodiments may be implemented by hardware circuitry and/or software, firmware, middleware, microcode, hardware description languages, etc., in combination with hardware (e.g., software executed by hardware, etc.). When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the desired tasks may be stored in a machine or computer readable medium such as a non-transitory computer storage medium, and loaded onto one or more processors to perform the desired tasks. A code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc. As used in this application, the term “circuitry” and/or “hardware circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementation (such as implementations in only analog and/or digital circuitry); (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware, and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. For example, the circuitry more specifically may include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, application-specific integrated circuit (ASIC), etc. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. At least one example embodiment refers to a network system capable of reducing and/or optimizing the transmission of signaling messages from at least one core network element and at least one RAN node based on a connection mode of the at least one RAN node. While the various example embodiments of the present disclosure are discussed in connection with the 5G wireless communication standard for the sake of clarity and convenience, the example embodiments are not limited thereto, and one of ordinary skill in the art would recognize the example embodiments may be applicable to, included in, and/or integrated into other wireless communication standards, such as the 4G wireless protocol, a WLAN wireless protocol, a future 6G wireless protocol, a future 7G wireless protocol, etc. FIG.1illustrates a wireless communication system according to at least one example embodiment. As shown inFIG.1, a wireless communication system includes at least one user equipment (UE) device (UEs or UE devices)110, a first radio access network (RAN) node120and a second RAN node130, a core network140, and one or more core network elements (e.g., one or more core network servers, core network devices, etc.), such as AMF150and UPF160, etc., but the example embodiments are not limited thereto and the example embodiments may include a greater or lesser number of constituent elements. For example, the wireless communication system may include a plurality of UE devices, a single RAN node, a plurality of RAN nodes greater than two, and/or a plurality of core network elements, core network servers, etc. The UE110may connect to one or more of the RAN nodes120and/or130, and/or the core network server140over a wireless network, such as a cellular wireless access network (e.g., a 3G wireless access network, a 4G-Long Term Evolution (LTE) network, a 5G-New Radio (e.g., 5G) wireless network, a WLAN network, a future 6G network, etc.), but is not limited thereto. The UE110may receive user plane communication (e.g., data communication packets, voice communication packets, etc.), from a user plane function (UPF) core network element160via the RAN nodes120and/or130, etc. The UE110may be any one of, but not limited to, a mobile device, a tablet, a laptop computer, a wearable device, an Internet of Things (IoT) device, a desktop computer and/or any other type of stationary or portable device capable of operating according to the 4G communication standard, the 5G NR communication standard, the WLAN standard, a future 6G standard, a future 7G standard, or other wireless communication standard. Each of the RAN nodes120and130may be a network device, such as a base station (BS), an access point, a router, a switch, a cell tower, etc. The RAN nodes120and130may connect to each other, at least one core network140(e.g., a 4G core network, a 5G core network, a 6G core network, etc.), and/or one or more elements of the core network, such as a core network server150and/or160, etc., over a wired and/or wireless network. Each of the RAN nodes120and130may operate according to at least one underlying cellular and/or wireless network communications protocol, such as the 4G long term evolution (LTE) communication protocol, the 5G new radio (NR) communication protocol, a WLAN communication protocol, a future 6G communication protocol, a future 7G communication protocol, etc. For example, the RAN node120may be an E-UTRA next-generation evolved NodeB (ng-eNB) node (e.g., a RAN node which communicates with a 5G-enabled UE over a 4G LTE air interface), and the RAN node130may be a 5G generation NodeB (gNB) node (e.g., a RAN node which communicates with a UE over a 5G NR air interface), etc., but the example embodiments are not limited thereto, and both RAN nodes may be gNB nodes, both RAN nodes may be ng-eNB nodes, and/or or may be other types of nodes, etc. Further, the RAN nodes120and130may be single connectivity nodes (e.g., capable of supporting a single connection mode), dual-connectivity nodes (e.g., capable of supporting two connection modes), and/or multi-connectivity nodes (e.g., capable of supporting more than two connection modes). For example, the RAN nodes120and130may be capable of operating in a standalone architecture (SA) connection mode and/or a non-standalone architecture (NSA) connection mode, but are not limited thereto. If a RAN node operates in SA mode, the RAN node acts as a main node for connected UE devices, e.g., a node which performs control plane processing and user plane processing for UE devices connected to the main node. If a RAN node is in NSA mode, the RAN node acts as a secondary node for connected UE devices, e.g., a node which only performs user plane processing for UE devices connected to the secondary node, with the UE devices needing to connect to another RAN node (e.g., a main RAN node) to perform the control plane processing for these UE devices. However, the example embodiments are not limited thereto, and for example, there may be additional connection modes possible for the RAN nodes. Referring toFIG.1, each of the RAN nodes120and130may include at least one processor121or131, a memory123or133, at least one wireless antenna122or132for connecting to one or more UEs, such as the UE110, and/or a core network interface124or134for connecting to the core network140and/or core network elements, such as an Access and Mobility Management Function (AMF)150, a User Plane Function (UPF)160, etc., but the example embodiments are not limited thereto. The memories123and133may include various program code including computer executable instructions, and may store various data and/or configuration settings associated with each RAN node, such as a connection mode configuration, etc., configuration settings associated with each connected UE device, etc. In at least one example embodiment, the at least one processors121and131of the RAN nodes120and130may be a processor, processing circuitry, processor cores, distributed processors, networked processors, etc., which may be configured to control one or more elements of the RAN node. The at least one processors121and131are configured to execute processes by retrieving program code (e.g., computer readable instructions) and/or data from the memories123and133, thereby executing special purpose control and functions of the entire RAN node120or130. Once the special purpose program instructions are loaded into the at least one processors121and131, the at least one processors121and131execute the special purpose program instructions, thereby transforming the at least one processors121and131into special purpose processors. In at least one example embodiment, the memories123and133may be non-transitory computer-readable storage mediums, and each may include a random access memory (RAM), a read only memory (ROM), and/or a permanent mass storage device such as a disk drive, or a solid state drive, etc. Stored in the memories123and133are program code (i.e., computer readable instructions) related to operating the respective RAN node, the wireless antennas122and132, and/or the core network interfaces124and134, etc. Such software elements may be loaded from a non-transitory computer-readable storage medium independent of the memories123and133, using a drive mechanism (not shown) connected to the RAN120or130, or via the wireless antennas122and132, and/or core network interfaces124and134. The RAN nodes120and130may also include wireless antennas122and132. The wireless antennas122and132each may include an associated radio unit (not shown) and may be used to transmit wireless signals, e.g., 4G LTE wireless signals, 5G NR wireless signals, etc., to at least one UE device, such as UE110, etc. For example, the wireless antenna122of the ng-eNB node120may be a 4G air radio interface, and the wireless antenna132of the gNB node130may be a 5G air radio interface, etc. According to some example embodiments, the wireless antenna122and132each may be a single antenna, or may be a plurality of antennas, etc. The RAN nodes120and130may each include at least one core network interface124or134, each of which may be a wired and/or wireless network interface. The core network interfaces124and134may enable the RAN nodes120and130to communicate with and/or transmit data to and from core network elements and/or servers, etc., such as core network elements150and160, on the core network140. Examples of core network elements may include a network gateway (not shown), a core network server, a core network device, etc. The core network interfaces124and134allow the UEs connected to the RAN node120and/or RAN node130to communicate with and/or transmit data using the core network140to other networks, such as a Data Network (DN), the Internet, telephone networks, VoIP networks, intranets, LANs, etc. The RAN nodes120and130may be connected to and/or communicate with other core network elements, such as an Operations Administration & Management Configuration (O&M) element, a Session Management Function (SMF) element, an Authentication Server Function (AUSF) element, etc. Each of the core network elements of the core network140, including AMF150and UPF160, may be embodied as a server, a processing device, a node, a router, a network device, etc. Additionally, one or more of the core network elements may be combined into one or more servers, processing devices, nodes, routers, network devices, etc. For example, the AMF150and UPF160may be incorporated into a single core network server, etc. According to at least one example embodiment, the AMF150may be configured to provide functions and capabilities relating to control plane operations, such as security of the wireless network, access management, authorization of UE devices, etc. The AMF150may transmit signaling traffic (e.g., signaling messages, control packets, etc.) to and/or from network equipment, such as RAN nodes, BSs, routers, switches, etc., to which the AMF150has established a control plane connection. Examples of signaling traffic may include paging messages, public warning messages, overload messages, etc. The UPF160may be configured to provide functions and capabilities to facilitate user plane (e.g., data plane, forwarding plane, carrier plane, etc.) operation, such as carrying network user traffic (e.g., data and/or voice packets, etc.) destined for UEs, packet routing and forwarding, interconnection between UEs and a DN (e.g., the Internet, etc.), policy enforcement, data buffering, etc. For example, the UPF160may receive data or voice packets destined for UE110from the DN, and forward the data or voice packets to the RAN node that UE110is connected with, such as ng-eNB node120and/or gNB node130, or vice versa. According to some example embodiments, each of the core network elements, such as AMF150and UPF160, may include at least one processors151or161, memories153or163, and/or wireless antennas152or162, etc. Additionally, each of the core network elements may further include at least one core network interface, such as core network interfaces154and164, for connecting to one or more RAN nodes, such as RAN nodes120and130, one or more other core network elements, etc., but the example embodiments are not limited thereto. The memories153and163may include various program code including computer executable instructions, such as program code for operating the core network element, etc., and may also store various data and/or configuration settings associated with each core network element, each connected RAN node, and/or each UE device operating in at least one cell serving area and/or at least one tracking area, etc., served by the core element, such as signaling message configurations, O&M configurations, account configurations, etc. According to at least one example embodiment, the memories153and163may store a database for storing configuration setting values associated with each RAN node connected to the core network element, such as RAN nodes120and130, etc., and/or each UE that is operating within and/or associated with a territorial area associated with the core network element. For example, the database may store connection mode configuration values and/or signaling message configuration values associated with each RAN node, etc. The at least one processors151and161, memories153and163, wireless antennas152and162, and/or core network interfaces154and164, of the AMF150and UPF160may be substantially similar to and/or the same as the processors121and131, memories123and133, wireless antennas122and132, and core network interfaces124and134, of the RAN nodes120and130. Accordingly, further discussion of these components will be omitted for the sake of brevity. While certain elements of the cellular wireless network are shown as part of the wireless communication system ofFIG.1, the example embodiments are not limited thereto, and the cellar wireless network may include components other than that shown inFIG.1, which are desired, necessary, and/or beneficial for operation of the underlying networks within the communication system100, such as access points, switches, routers, nodes, servers, etc. Additionally, whileFIG.1depicts an example embodiment of the RAN nodes ng-eNB node120and gNB node130, and the core network elements AMF150and UPF160, the example embodiments are not limited thereto, and one or more of these elements may include additional components and/or alternative architectures that may be suitable for the purposes demonstrated. FIGS.2A to4are transmission flow diagrams between at least one core network element and a plurality of RAN nodes connected to the core network according to some example embodiments. For each of the example embodiments ofFIGS.2A to4, it is assumed that the AMF150is not initially aware of the connection mode configuration status of the ng-eNB node120and the gNB node130. Additionally, it is assumed that the ng-eNB node120is initially configured to operate in “NSA only mode,” and the gNB node130is initially configured to operate in “SA mode.” However, the example embodiments are not limited thereto, and both the ng-eNB node120and the gNB node130may operate in any of the connection modes, e.g., SA connection mode, NSA connection mode, etc. Further, while the example embodiments are discussed in the context of only two connection modes, the example embodiments are not limited thereto and there may be more than two connection modes. FIG.2Ais a first transmission flow diagram between at least one core network element and a plurality of RAN nodes connected to the core network illustrating a method of semi-statically learning and/or obtaining the connection mode configuration statuses of the plurality of RAN nodes according to at least one example embodiment. Referring toFIG.2A, one or more RAN nodes, such as ng-eNB node120and gNB node130, may be initialized and/or connected to a core network, such as core network140. In operation S2001, the gNB node130may transmit a control plane connection request to the AMF150, such as a NG setup request. The control plane connection request may include an indication of the connection mode of the gNB node130, e.g., an indication that the gNB node130is in SA mode. According to some example embodiments, the connection mode indication may also be referred to as a cause value, connection mode configuration information, connection mode configuration status value, signaling message configuration value, etc. Thus, the AMF150learns and/or obtains the connection mode configuration status of the gNB node130in a semi-static manner. In operation S2002, a control plane connection (e.g., NG-C connection, etc.) is established between the gNB node130and the AMF150, and the AMF150transmits a response to the gNB node130's control plane connection request, e.g., a NG setup response. Additionally, the AMF150may create and/or update a record associated with the gNB130in a database, including storing the gNB node130's connection mode configuration status and/or setting a signaling message configuration value associated with the gNB node130corresponding to the connection mode configuration status. The signaling message configuration value may indicate whether future signaling messages should be enabled (e.g., allowed, permitted, etc.) to the RAN node, or if future signaling messages should be restricted (e.g., denied, prohibited, etc.) to the RAN node, etc. In operation S2003, the ng-eNB node120may transmit a control plane connection request, e.g., a NG setup request, etc., to the AMF150. The control plane connection request may include an indication of the connection mode of the ng-eNB node120, e.g., an indication that the ng-eNB node120is in NSA mode or NSA only mode. Thus, the AMF150learns and/or obtains the connection mode configuration status of the ng-eNB node120in a semi-static manner. In operation S2004, a control plane connection (e.g., NG-C connection, etc.) is established between the ng-eNB node120and the AMF150, and the AMF150transmits a response to the ng-eNB node120's control plane connection request, e.g., a NG setup response, etc. Additionally, the AMF150may create and/or update a record associated with the ng-eNB120in the database, including storing the ng-eNB node120's connection mode configuration status and/or setting a signaling message configuration value associated with the ng-eNB node120corresponding to the connection mode configuration status. Next, in operation S2005, the AMF150may decide to transmit a signaling message, e.g., a paging message, etc., to UEs associated with (e.g., operating within, located within, connected to a RAN node connected to the AMF150, etc.) the territorial area assigned to the AMF150, such as the UEs connected to ng-eNB node120and gNB node130, etc. The AMF150may determine which RAN node(s) to transmit the signaling message to based on the received connection mode indications included in the control plane connection requests from the ng-eNB node120and gNB node130, etc. In the example ofFIG.2A, in operation S2006, the AMF150transmits a paging message to the gNB node130because the gNB node130is in SA connection mode (e.g., a desired connection mode). The gNB node130then forwards the paging message to the appropriate UE device, such as UE110. Additionally, in operation S2006B, the AMF150does not transmit the paging message to ng-eNB node120because the ng-eNB node120is in NSA only mode (e.g., a non-desired connection mode), thereby reducing the number of signaling messages transmitted across the network, and increasing the efficiency of network resource usage. Referring now toFIGS.2B to4, for each of these example embodiments it is assumed that the AMF150has already established a control plane connection, e.g., NG-control (NG-C) control connection, etc., with both the ng-eNB node120and the gNB node130as described in connection withFIG.2A, however the example embodiments are not limited thereto and other methods for establishing a control plane connection may be used, such as establishing a control plane connection between a core network element and a RAN node without the RAN node transmitting a connection mode indication within the control plane request, etc. FIG.2Bis a second transmission flow diagram between at least one core network element and a plurality of RAN nodes connected to the core network illustrating a first method of dynamically configuring the connection modes of the plurality of RAN nodes according to at least one example embodiment. In operation S2011, the ng-eNB node120, which was previously configured to operate in NSA connection mode, may transmit a RAN configuration update message to the AMF150. The RAN configuration update message may include an indication stating the ng-eNB node120is now operating in SA connection mode, along with any other configuration changes made to the ng-eNB node120, and the AMF150thereby learns and/or obtains the connection mode configuration status of the ng-eNB node120in a dynamic manner. In operation S2012, the AMF150may update its records associated with the ng-eNB node120, including updating the AMF150's records regarding the ng-eNB node120's connection mode configuration and/or setting a signaling message configuration value associated with the ng-eNB node120corresponding to the connection mode configuration status. Then, the AMF150transmits a RAN configuration update response to the ng-eNB node120. In operation S2013, the AMF150may decide to transmit a paging message to UEs within the AMF150's territorial area, such as the UEs connected to ng-eNB node120and gNB node130, etc. The AMF150may determine to transmit the signaling message to the ng-eNB node120based on the received RAN configuration update message. In the example ofFIG.2B, and in contrast to the example ofFIG.2A, in operations S2014and S2014B, the AMF150transmits paging messages to both the gNB node130and the ng-eNB node120because both the gNB node130and the ng-eNB node120are in SA connection mode (e.g., a desired connection mode). The gNB node130and the ng-eNB node120then forward the paging message(s) to the appropriate UE devices, such as UE110, etc. Thus, the AMF150correctly transmits signaling messages to the connected RAN nodes that are in SA connection mode. FIG.3is a third transmission flow diagram between at least one core network element and a plurality of RAN nodes connected to the core network illustrating a second method of dynamically configuring the connection modes of the plurality of RAN nodes according to at least one example embodiment. In operations S3001and S3001B, the AMF150transmits a first signaling message, e.g., a paging message, to both the ng-eNB node120and the gNB node130, without having knowledge as to whether the ng-eNB node120and gNB node130are in SA mode or NSA mode. For example, the ng-eNB node120and the gNB node130may have established a control plane connection with the AMF150without having transmitted an indication of their respective connection mode statuses, etc. In operation S3002, because the gNB node130is in SA mode, the gNB node130forwards the paging message to the appropriate UEs, such as UE110, and then forwards a paging response to the AMF150. Because the AMF150has received a successful paging response from the gNB node130, the AMF150is able to dynamically determine the gNB node130is operating in SA mode, and the AMF150may update its records associated with the gNB node130, including updating the AMF150's records regarding the gNB node130's connection mode configuration status and/or setting a signaling message configuration value associated with the gNB node130corresponding to the connection mode configuration status. In operation S3002B, because the ng-eNB node120is operating in NSA mode, the ng-eNB node120transmits an error message to the AMF150in response to the paging message. The error message may include a cause value indicating the connection mode configuration of the ng-eNB node120, e.g., an indication that the ng-eNB node120is operating in NSA mode. Because the AMF150has received an unsuccessful response (e.g., error message) from the ng-eNB node120, the AMF150is able to dynamically determine the ng-eNB node120is operating in NSA mode, and the AMF150may update its records associated with the ng-eNB node120, including updating the AMF150's records regarding the ng-eNB node120's connection mode configuration status and/or setting a signaling message configuration value associated with the ng-eNB node120corresponding to the connection mode configuration status. Next, in operation S3003, the AMF150may decide to transmit a signaling message, e.g., a paging message, etc., to UEs within its territorial area, such as UEs connected to ng-eNB node120and gNB node130. The AMF150may determine which RAN node(s) to transmit the signaling message to using the connection mode indications determined from the first signaling message responses sent by the ng-eNB node120and gNB node130, etc. In operation S3004, the AMF150transmits a second paging message to the gNB node130because the gNB node130is in SA connection mode (e.g., a desired connection mode). The gNB node130then forwards the paging message to the appropriate UE device, such as UE110. Additionally, in operation S3004B, the AMF150does not transmit a second paging message to ng-eNB node120because the ng-eNB node120is in NSA only mode (e.g., a non-desired connection mode), thereby reducing the number of signaling messages transmitted across the network, and increasing the efficiency of network resource usage. FIG.4is a fourth transmission flow diagram between at least one core network element and a plurality of RAN nodes connected to the core network illustrating a static method of configuring the connection modes of the plurality of RAN nodes according to at least one example embodiment. In operations S4001and S4002, the AMF150obtains O&M configuration values corresponding to the ng-eNB node120and the gNB node130from a O&M core network element (not shown). In this scenario, the O&M configuration values indicate that the ng-eNB node120is set to operate in SA mode and the gNB node130is set to operate in NSA mode. Accordingly, the AMF150statically determines the connection mode statuses of the ng-eNB node120and gNB node130, and the AMF150may update its records associated with the ng-eNB node120and the gNB node130, including updating the AMF150's records regarding the ng-eNB node120's and the gNB node130's connection mode configuration statuses and/or setting signaling message configuration values associated with the RAN nodes corresponding to their respective connection mode configuration statuses. In operation S4003, the AMF150then transmits a paging message to the ng-eNB node120based on the O&M configuration values associated with the ng-eNB node120. In operation S4001B, the AMF150does not transmit a paging message to the gNB node130based on the O&M configuration values associated with the gNB node130, thereby reducing the network usage, and increasing the efficiency of network resource usage. FIG.5Ais a flowchart illustrating a method for reducing signaling messages between at least one core network server and at least one RAN according to at least one example embodiment. In operation S510, a core network server (e.g., core network element, core network device, etc.), such as AMF150, may establish a control plane connection (e.g., NG-C connection, etc.) to at least one RAN node, such as RAN nodes120and130, etc. The control plane connection allows the AMF150to transmit signaling messages, control plane messages, etc., destined for the RAN node to the RAN node, and/or signaling messages destined for one or more UE devices associated with and/or connected to the at least one RAN node through the RAN node. In operation S520, the core network server may determine the connection mode of the at least one RAN node. For example, the at least one RAN node may be capable of two or more connection modes, such as a SA mode or a NSA mode, etc. In operation S530A, in response to the core network server determining that the at least one RAN node is in a desired connection mode, e.g., determines the at least one RAN node is in SA mode, the core network server may set a signaling message configuration value corresponding to the at least one RAN node to enable and/or allow transmission of signaling messages to the at least one RAN node. Examples of the signaling messages may include NGAP messages (e.g., paging messages, public warning messages, overload messages, etc.), but are not limited thereto. In operation S530B, in response to the core network server determining that the at least one RAN node is not in the desired connection mode, e.g., the at least one RAN node is in NSA mode, the core network server may set the signaling message configuration value corresponding to the at least one RAN node to restrict and/or prohibit transmission of signaling messages to the at least one RAN node. In optional operation S540, the core network server may transmit future signaling messages to the at least one RAN node based on the signaling message configuration value of the at least one RAN node. For example, the core network server may transmit future signaling messages in response to the signaling message configuration value corresponding to the at least one RAN node indicating the RAN node is in a desired connection mode, such as SA mode, etc. WhileFIG.5Aillustrates one method for reducing signaling messages between at least one core network server and at least one RAN, the example embodiments are not limited thereto, and other methods may be used. For example, according to at least one example embodiment, the RAN nodes may be capable of operating in three or more connection modes, and the desired connection mode may be a subset of the entire set of possible connection modes (e.g., a first connection mode and a second connection mode, etc.), and the non-desired connection mode may be a remaining subset of the entire set of possible connection modes (e.g., a third connection mode, etc.). FIG.5Bis a flowchart illustrating a first method for determining whether a RAN node is a desired connection mode in association with the method ofFIG.5Aaccording to at least one example embodiment. Referring now toFIGS.5A and5B, in operation S511, the core network server may determine the connection mode of the at least one RAN node by receiving a message from the at least one RAN node including a cause value and/or information indicating the connection mode (e.g., SA mode, NSA mode, etc.) of the at least one RAN node. The message may be a NG setup request message, a RAN configuration update message, etc., but the example embodiments are not limited thereto. In operation S521, the core network server may determine whether the message received from the at least one RAN node indicates the RAN node is in the desired connection mode. In operation S531A, in response to the received message indicating the RAN node is in the desired connection mode (e.g., SA mode), the core network server sets the signaling message configuration value corresponding to the RAN node to enable and/or allow transmission of at least one future signaling message to the RAN node. For example, the core network server may create or update a database record stored in its memory corresponding to the at least one RAN node indicating transmission of future signaling messages to the at least one RAN node should be enabled/permitted and/or indicating the connection mode configuration value of the at least one RAN node is the desired connection mode, etc., but the example embodiments are not limited thereto. In operation S531B, in response to the received message indicating the RAN node is in the non-desired connection mode (e.g., NSA mode), the core network server sets the signaling message configuration value corresponding to the RAN node to restrict and/or disable transmission of at least one future signaling message to the RAN node. For example, the core network server may create or update a database record stored in its memory corresponding to the at least one RAN node indicating transmission of future signaling messages to the at least one RAN node is restricted/disabled and/or indicating the connection mode configuration value of the at least one RAN node is the non-desired connection mode, etc., but the example embodiments are not limited thereto. FIG.5Cis a flowchart illustrating a second method for determining whether a RAN node is a desired connection mode in association with the method ofFIG.5Aaccording to at least one example embodiment. Referring now toFIGS.5A and5C, in operation S522, the core network server may determine the connection mode of the at least one RAN node by transmitting at least a first signaling message to the at least one RAN node. The first signaling message may be a paging message, a public warning message, an overload message, etc. In operation S523, the core network server may receive a response message corresponding to the first signaling message from the at least one RAN node. For example, the response message may be an acknowledgement message, an error message including a cause value and/or information indicating the RAN node is in a non-desired connection mode (e.g., the RAN node is in NSA mode or otherwise does not support SA mode functionality), etc. In operation S524, the core network server determines whether the response message is an error message indicating the at least one RAN node is not in the desired connection mode by analyzing the contents of the response message, such as the cause value (e.g., error cause value), etc. In operation S532A, in response to the core network server determining the response message is not an error message indicating the RAN node is in the non-desired connection mode (e.g., the RAN node is in SA mode), the core network server sets the signaling message configuration value corresponding to the RAN node to enable and/or allow transmission of at least one future signaling message to the RAN node. In operation S532B, in response to the core network server determining the response message was an error message indicating the RAN node is not in the desired connection mode (e.g., the RAN node is in NSA mode), the core network server sets the signaling message configuration value corresponding to the RAN node to restrict and/or disable transmission of at least one future signaling message to the RAN node. FIG.5Dis a flowchart illustrating a third method for determining whether a RAN node is a desired connection mode in association with the method ofFIG.5Aaccording to at least one example embodiment. Referring now toFIGS.5A and5D, in operation S525, the core network server accesses a local configuration database including configuration information (e.g., O&M configuration values, etc.) associated with the at least one RAN node. In operation S526, the core network server determines whether the local configuration setting for the RAN node indicates the RAN node is in the desired connection mode or the non-desired connection mode. In operation S533A, the core network server sets the signaling message configuration value of the at least one RAN node to enable and/or allow transmission of future signaling messages to the at least one RAN node if the local configuration setting indicates the at least one RAN node is in the desired connection mode. In operation S533B, the core network server sets the signaling message configuration value of the at least one RAN node to restrict transmission of future signaling messages to the at least one RAN node if the local configuration setting indicates the at least one RAN node is in the non-desired connection mode. FIG.6is a flowchart illustrating a method for operating a RAN node to reduce signaling messages between the RAN node and a core network according to at least one example embodiment. In operation S610, the RAN node (e.g., ng-eNB node120, gNB node130, etc.) may set its connection mode to be at least a first connection mode (e.g., SA mode), a second connection mode (e.g., NSA mode), or a different connection mode. In operation S620, the RAN node may establish a control plane connection (e.g., a NG-C connection, etc.) with at least one core network server (e.g., AMF150, etc.). In operation S630, the RAN node may transmit at least one message (e.g., a control plane connection request, a NG setup request, a RAN configuration update request, an error message in response to a signaling message trigger (e.g. a paging trigger, etc.), etc.) to the at least one core network server, the at least one message including an indication of the connection mode of the RAN node. According to at least one example embodiment, operations S620and S630may occur simultaneously and/or may be combined, but the example embodiments are not limited thereto. For example, the RAN node may transmit a control plane connection request including an indication of the connection mode of the RAN node, etc. In response to the RAN node transmitting the at least one message, the core network server may be caused to selectively restrict transmission of at least one future signaling message to the RAN node based on the indication of the RAN node's connection mode. For example, if the at least one message indicates the RAN node is in NSA mode, the AMF150may be caused to restrict transmission of at least one future signaling message to the RAN node by setting a signaling message configuration value corresponding to the RAN node to restrict transmission of future signaling messages to the RAN node, etc. However, if the at least one message indicates the RAN node is in SA mode, the AMF150may be caused to enable and/or allow transmission of future signaling messages to the RAN node by setting the signaling message configuration value corresponding to the RAN node to enable transmission of future signaling messages to the RAN node, etc. WhileFIGS.5A to6illustrate various methods for reducing signaling messages between at least one core network server and at least one RAN, the example embodiments are not limited thereto, and other methods may be used to reducing signaling messages between at least one core network server and at least one RAN. Additionally, one of ordinary skill in the art will recognize that one or more of these methods may be combined into a single method, and/or one or more of the recited method operations may be combined, rearranged, omitted, and/or repeated, etc., without deviating from the scope of the example embodiments. Moreover, one of ordinary skill in the art will also recognize that one or more method operation may be executed simultaneously and/or in parallel with other method operations without deviating from the scope of the example embodiments. Various example embodiments are directed towards a wireless network system capable of reducing and/or optimizing the transmission of signaling messages from at least one core network element and at least one RAN node based on a connection mode of the at least one RAN node. By determining the connection mode of the at least one RAN node prior to transmitting signaling messages to the RAN nodes connected to the core network element, the core network element may reduce and/or optimize the number of signaling messages transmitted to the RAN nodes, thereby reducing the usage of network resources. This written description uses examples of the subject matter disclosed to enable any person skilled in the art to practice the same, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the subject matter is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims. | 46,775 |
11943742 | DETAILED DESCRIPTION In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and/or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and/or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments. Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols. A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology. In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of”, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of” provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and/or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C. If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state. In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages. Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features. Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module. FIG.1Aillustrates an example of a mobile communication network100in which embodiments of the present disclosure may be implemented. The mobile communication network100may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated inFIG.1A, the mobile communication network100includes a core network (CN)102, a radio access network (RAN)104, and a wireless device106. The CN102may provide the wireless device106with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the CN102may set up end-to-end connections between the wireless device106and the one or more DNs, authenticate the wireless device106, and provide charging functionality. The RAN104may connect the CN102to the wireless device106through radio communications over an air interface. As part of the radio communications, the RAN104may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN104to the wireless device106over the air interface is known as the downlink and the communication direction from the wireless device106to the RAN104over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and/or some combination of the two duplexing techniques. The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle road side unit (RSU), relay node, automobile, and/or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and/or wireless communication device. The RAN104may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and/or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and/or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and/or 5G standards), an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard), and/or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU). A base station included in the RAN104may include one or more sets of antennas for communicating with the wireless device106over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device106over a wide geographic area to support wireless device mobility. In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN104may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN104may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and/or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same/similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal. The RAN104may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN104may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations. The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network100inFIG.1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN104inFIG.1A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies. FIG.1Billustrates another example mobile communication network150in which embodiments of the present disclosure may be implemented. Mobile communication network150may be, for example, a PLMN run by a network operator. As illustrated inFIG.1B, mobile communication network150includes a 5G core network (5G-CN)152, an NG-RAN154, and UEs156A and156B (collectively UEs156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect toFIG.1A. The 5G-CN152provides the UEs156with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the 5G-CN152may set up end-to-end connections between the UEs156and the one or more DNs, authenticate the UEs156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN152may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN152may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN152may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform). As illustrated inFIG.1B, the 5G-CN152includes an Access and Mobility Management Function (AMF)158A and a User Plane Function (UPF)158B, which are shown as one component AMF/UPF158inFIG.1Bfor ease of illustration. The UPF158B may serve as a gateway between the NG-RAN154and the one or more DNs. The UPF158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink/downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF158B may serve as an anchor point for intra-/inter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and/or a branching point to support a multi-homed PDU session. The UEs156may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN. The AMF158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and/or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN. The 5G-CN152may include one or more additional network functions that are not shown inFIG.1Bfor the sake of clarity. For example, the 5G-CN152may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and/or an Authentication Server Function (AUSF). The NG-RAN154may connect the 5G-CN152to the UEs156through radio communications over the air interface. The NG-RAN154may include one or more gNBs, illustrated as gNB160A and gNB160B (collectively gNBs160) and/or one or more ng-eNBs, illustrated as ng-eNB162A and ng-eNB162B (collectively ng-eNBs162). The gNBs160and ng-eNBs162may be more generically referred to as base stations. The gNBs160and ng-eNBs162may include one or more sets of antennas for communicating with the UEs156over an air interface. For example, one or more of the gNBs160and/or one or more of the ng-eNBs162may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs160and the ng-eNBs162may provide radio coverage to the UEs156over a wide geographic area to support UE mobility. As shown inFIG.1B, the gNBs160and/or the ng-eNBs162may be connected to the 5G-CN152by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and/or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs160and/or the ng-eNBs162may be connected to the UEs156by means of a Uu interface. For example, as illustrated inFIG.1B, gNB160A may be connected to the UE156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements inFIG.1Bto exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements. The gNBs160and/or the ng-eNBs162may be connected to one or more AMF/UPF functions of the 5G-CN152, such as the AMF/UPF158, by means of one or more NG interfaces. For example, the gNB160A may be connected to the UPF158B of the AMF/UPF158by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB160A and the UPF158B. The gNB160A may be connected to the AMF158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and/or warning message transmission. The gNBs160may provide NR user plane and control plane protocol terminations towards the UEs156over the Uu interface. For example, the gNB160A may provide NR user plane and control plane protocol terminations toward the UE156A over a Uu interface associated with a first protocol stack. The ng-eNBs162may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs156over a Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocol terminations towards the UE156B over a Uu interface associated with a second protocol stack. The 5G-CN152was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF/UPF158is shown inFIG.1B, one gNB or ng-eNB may be connected to multiple AMF/UPF nodes to provide redundancy and/or to load share across the multiple AMF/UPF nodes. As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements inFIG.1Bmay be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements. FIG.2AandFIG.2Brespectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE210and a gNB220. The protocol stacks illustrated inFIG.2AandFIG.2Bmay be the same or similar to those used for the Uu interface between, for example, the UE156A and the gNB160A shown inFIG.1B. FIG.2Aillustrates a NR user plane protocol stack comprising five layers implemented in the UE210and the gNB220. At the bottom of the protocol stack, physical layers (PHYs)211and221may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs211and221comprise media access control layers (MACs)212and222, radio link control layers (RLCs)213and223, packet data convergence protocol layers (PDCPs)214and224, and service data application protocol layers (SDAPs)215and225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model. FIG.3illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top ofFIG.2AandFIG.3, the SDAPs215and225may perform QoS flow handling. The UE210may receive services through a PDU session, which may be a logical connection between the UE210and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and/or error rate). The SDAPs215and225may perform mapping/de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping/de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP225at the gNB220. The SDAP215at the UE210may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB220. For reflective mapping, the SDAP225at the gNB220may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP215at the UE210to determine the mapping/de-mapping between the QoS flows and the data radio bearers. The PDCPs214and224may perform header compression/decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering/deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs214and224may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-gNB handover. The PDCPs214and224may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability. Although not shown inFIG.3, PDCPs214and224may perform mapping/de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs214and224as a service to the SDAPs215and225, is handled by cell groups in dual connectivity. The PDCPs214and224may map/de-map the split radio bearer between RLC channels belonging to cell groups. The RLCs213and223may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs212and222, respectively. The RLCs213and223may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. As shown inFIG.3, the RLCs213and223may provide RLC channels as a service to PDCPs214and224, respectively. The MACs212and222may perform multiplexing/demultiplexing of logical channels and/or mapping between logical channels and transport channels. The multiplexing/demultiplexing may include multiplexing/demultiplexing of data units, belonging to the one or more logical channels, into/from Transport Blocks (TBs) delivered to/from the PHYs211and221. The MAC222may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB220(at the MAC222) for downlink and uplink. The MACs212and222may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE210by means of logical channel prioritization, and/or padding. The MACs212and222may support one or more numerologies and/or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. As shown inFIG.3, the MACs212and222may provide logical channels as a service to the RLCs213and223. The PHYs211and221may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding/decoding and modulation/demodulation. The PHYs211and221may perform multi-antenna mapping. As shown inFIG.3, the PHYs211and221may provide one or more transport channels as a service to the MACs212and222. FIG.4Aillustrates an example downlink data flow through the NR user plane protocol stack.FIG.4Aillustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TB s at the gNB220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted inFIG.4A. The downlink data flow ofFIG.4Abegins when SDAP225receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. InFIG.4A, the SDAP225maps IP packets n and n+1 to a first radio bearer402and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” inFIG.4A) is added to an IP packet. The data unit from/to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to/from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown inFIG.4A, the data unit from the SDAP225is an SDU of lower protocol layer PDCP224and is a PDU of the SDAP225. The remaining protocol layers inFIG.4Amay perform their associated functionality (e.g., with respect toFIG.3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP224may perform IP-header compression and ciphering and forward its output to the RLC223. The RLC223may optionally perform segmentation (e.g., as shown for IP packet m inFIG.4A) and forward its output to the MAC222. The MAC222may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated inFIG.4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled. FIG.4Billustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use. FIG.4Bfurther illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC223or MAC222. For example,FIG.4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown inFIG.4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation/deactivation MAC CEs, such as those for activation/deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE. Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below. FIG.5AandFIG.5Billustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;a common control channel (CCCH) for carrying control messages together with random access;a dedicated control channel (DCCH) for carrying control messages to/from a specific the UE to configure the UE; anda dedicated traffic channel (DTCH) for carrying user data to/from a specific the UE. Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:a paging channel (PCH) for carrying paging messages that originated from the PCCH;a broadcast channel (BCH) for carrying the MIB from the BCCH;a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; anda random access channel (RACH) for allowing a UE to contact the network without any prior scheduling. The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1/L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:a physical broadcast channel (PBCH) for carrying the MIB from the BCH;a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below;a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR); anda physical random access channel (PRACH) for random access. Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown inFIG.5AandFIG.5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below. FIG.2Billustrates an example NR control plane protocol stack. As shown inFIG.2B, the NR control plane protocol stack may use the same/similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs211and221, the MACs212and222, the RLCs213and223, and the PDCPs214and224. Instead of having the SDAPs215and225at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs)216and226and NAS protocols217and237at the top of the NR control plane protocol stack. The NAS protocols217and237may provide control plane functionality between the UE210and the AMF230(e.g., the AMF158A) or, more generally, between the UE210and the CN. The NAS protocols217and237may provide control plane functionality between the UE210and the AMF230via signaling messages, referred to as NAS messages. There is no direct path between the UE210and the AMF230through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols217and237may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management. The RRCs216and226may provide control plane functionality between the UE210and the gNB220or, more generally, between the UE210and the RAN. The RRCs216and226may provide control plane functionality between the UE210and the gNB220via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE210and the RAN using signaling radio bearers and the same/similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control-plane and user-plane data into the same transport block (TB). The RRCs216and226may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE210and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and/or NAS message transfer. As part of establishing an RRC connection, RRCs216and226may establish an RRC context, which may involve configuring parameters for communication between the UE210and the RAN. FIG.6is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device106depicted inFIG.1A, the UE210depicted inFIG.2AandFIG.2B, or any other wireless device described in the present disclosure. As illustrated inFIG.6, a UE may be in at least one of three RRC states: RRC connected602(e.g., RRC_CONNECTED), RRC idle604(e.g., RRC_IDLE), and RRC inactive606(e.g., RRC_INACTIVE). In RRC connected602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN104depicted inFIG.1A, one of the gNBs160or ng-eNBs162depicted inFIG.1B, the gNB220depicted inFIG.2AandFIG.2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session); security information; and/or PHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. While in RRC connected602, mobility of the UE may be managed by the RAN (e.g., the RAN104or the NG-RAN154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected602to RRC idle604through a connection release procedure608or to RRC inactive606through a connection inactivation procedure610. In RRC idle604, an RRC context may not be established for the UE. In RRC idle604, the UE may not have an RRC connection with the base station. While in RRC idle604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle604to RRC connected602through a connection establishment procedure612, which may involve a random access procedure as discussed in greater detail below. In RRC inactive606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected602with reduced signaling overhead as compared to the transition from RRC idle604to RRC connected602. While in RRC inactive606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive606to RRC connected602through a connection resume procedure614or to RRC idle604though a connection release procedure616that may be the same as or similar to connection release procedure608. An RRC state may be associated with a mobility management mechanism. In RRC idle604and RRC inactive606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle604and RRC inactive606is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle604and RRC inactive606may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle604and RRC inactive606track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI). Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN102or the 5G-CN152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new the UE registration area. RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive606state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE's RAN notification area. A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and/or during a period of time that the UE stays in RRC inactive606. A gNB, such as gNBs160inFIG.1B, may be split in two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY. In NR, the physical signals and physical channels (discussed with respect toFIG.5AandFIG.5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols. FIG.7illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot. The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerologies with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3 μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs. A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe.FIG.7illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown inFIG.7for ease of illustration). A subframe in NR may be used as a numerology-independent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions. FIG.8illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown inFIG.8. An RB spans twelve consecutive REs in the frequency domain as shown inFIG.8. An NR carrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit. FIG.8illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier. NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and/or for other purposes, a UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation. NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier. For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP. For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP. For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP). One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions. A base station may semi-statically configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH. A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP. In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and/or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP). Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and/or an initiation of random access. FIG.9illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated inFIG.9, the BWPs include: a BWP902with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP904with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902may be an initial active BWP, and the BWP904may be a default BWP. The UE may switch between BWPs at switching points. In the example ofFIG.9, the UE may switch from the BWP902to the BWP904at a switching point908. The switching at the switching point908may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and/or in response to receiving a DCI indicating BWP904as the active BWP. The UE may switch at a switching point910from active BWP904to BWP906in response to receiving a DCI indicating BWP906as the active BWP. The UE may switch at a switching point912from active BWP906to BWP904in response to an expiry of a BWP inactivity timer and/or in response receiving a DCI indicating BWP904as the active BWP. The UE may switch at a switching point914from active BWP904to BWP902in response to receiving a DCI indicating BWP902as the active BWP. If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same/similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same/similar manner as the UE would use these values for a primary cell. To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to/from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain. FIG.10Aillustrates the three CA configurations with two CCs. In the intraband, contiguous configuration1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration1006, the two CCs are located in frequency bands (frequency band A and frequency band B). In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink. When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and/or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC). Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells may be activated and deactivated using a MAC CE with respect toFIG.4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell). Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self-scheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and/or RI) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups. FIG.10Billustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group1010and a PUCCH group1050may include one or more downlink CCs, respectively. In the example ofFIG.10B, the PUCCH group1010includes three downlink CCs: a PCell1011, an SCell1012, and an SCell1013. The PUCCH group1050includes three downlink CCs in the present example: a PCell1051, an SCell1052, and an SCell1053. One or more uplink CCs may be configured as a PCell1021, an SCell1022, and an SCell1023. One or more other uplink CCs may be configured as a primary SCell (PSCell)1061, an SCell1062, and an SCell1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group1010, shown as UCI1031, UCI1032, and UCI1033, may be transmitted in the uplink of the PCell1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI1071, UCI1072, and UCI1073, may be transmitted in the uplink of the PSCell1061. In an example, if the aggregated cells depicted inFIG.10Bwere not divided into the PUCCH group1010and the PUCCH group1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell1021and the PSCell1061, overloading may be prevented. A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and/or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same/similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated. In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment/grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell. In the downlink, a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown inFIG.5A). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and/or SRS, as shown inFIG.5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and the SSS may be provided in a synchronization signal (SS)/physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS/PBCH blocks. FIG.11Aillustrates an example of an SS/PBCH blocks structure and location. A burst of SS/PBCH blocks may include one or more SS/PBCH blocks (e.g., 4 SS/PBCH blocks, as shown inFIG.11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood thatFIG.11Ais an example, and that these parameters (number of SS/PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS/PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS/PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing. The SS/PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example ofFIG.11A) and may span one or more subcarriers in the frequency domain (e.g.,240contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers. The location of the SS/PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS/PBCH block, the locations of the SSS and the PBCH, respectively. The SS/PBCH block may be a cell-defining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection/search and/or reselection may be based on the CD-SSB. The SS/PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS/PBCH block. For example, the SS/PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS/PBCH block in the transmission pattern is a known distance from the frame boundary. The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and/or a SS/PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS/PBCH block at the frequency to which the UE is pointed. The UE may assume that one or more SS/PBCH blocks transmitted with a same SS/PBCH block index are quasi co-located (QCLed) (e.g., having the same/similar Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCH block transmissions having different SS/PBCH block indices. SS/PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS/PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS/PBCH block may be transmitted in a second spatial direction using a second beam. In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS/PBCH blocks. In an example, a first PCI of a first SS/PBCH block of the plurality of SS/PBCH blocks may be different from a second PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks. The PCIs of SS/PBCH blocks transmitted in different frequency locations may be different or the same. The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and/or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation. The base station may semi-statically configure the UE with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and/or deactivate a CSI-RS resource. The base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and/or deactivated. The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and/or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling. The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS/PBCH blocks. Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and/or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MIMO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation/channel estimation of the PDSCH. In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG). A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH. Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and/or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and/or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and/or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time/frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver. The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and/or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and/or the PUCCH, which the UE may use to schedule a single-symbol DMRS and/or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence for the DMRS may be the same or different. A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH. Uplink PT-RS (which may be used by a base station for phase tracking and/or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and/or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and/or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time/frequency duration for the UE. SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in an SRS resource set of the one or more SRS resource sets (e.g., with the same/similar time domain behavior, periodic, aperiodic, and/or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and/or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS. The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/or subframe level periodicity; offset for a periodic and/or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and/or an SRS sequence ID. An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and/or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and/or spatial Receiving (Rx) parameters. Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station. FIG.11Billustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown inFIG.11Bmay span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and/or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resource parameters. The three beams illustrated inFIG.11Bmay be configured for a UE in a UE-specific configuration. Three beams are illustrated inFIG.11B(beam #1, beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs. CSI-RSs such as those illustrated inFIG.11B(e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and/or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE. In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and/or a rank indicator (RI). FIG.12Aillustrates examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and/or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). The UE and/or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE. FIG.12Billustrates examples of three uplink beam management procedures: U1, U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and/or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and/or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam. A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and/or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and/or the like). The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS/PBCH blocks, one or more CSI-RS resources, and/or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and/or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and/or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE. A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE may initiate a random access procedure. A UE in an RRC_IDLE state and/or an RRC_INACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and/or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and/or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and/or for establishing time alignment for an SCell addition. FIG.13Aillustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message1310to the UE. The procedure illustrated inFIG.13Acomprises transmission of four messages: a Msg 11311, a Msg 21312, a Msg 31313, and a Msg 41314. The Msg 11311may include and/or be referred to as a preamble (or a random access preamble). The Msg 21312may include and/or be referred to as a random access response (RAR). The configuration message1310may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and/or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and/or in an RRC_INACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and/or an uplink transmit power for transmission of the Msg 11311and/or the Msg 31313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 21312and the Msg 41314. The one or more RACH parameters provided in the configuration message1310may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 11311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS/PBCH blocks and/or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS/PBCH blocks mapped to a PRACH occasion and/or a number of preambles mapped to a SS/PBCH blocks. The one or more RACH parameters provided in the configuration message1310may be used to determine an uplink transmit power of Msg 11311and/or Msg 31313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and/or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 11311and the Msg 31313; and/or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and/or CSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier). The Msg 11311may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and/or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and/or a size of the Msg 31313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and/or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and/or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message. The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and/or a size of the Msg 31313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and/or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and/or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 11311based on the association. The Msg 11311may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and/or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals. The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and/or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and/or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and/or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax). The Msg 21312received by the UE may include an RAR. In some scenarios, the Msg 21312may include multiple RARs corresponding to multiple UEs. The Msg 21312may be received after or in response to the transmitting of the Msg 11311. The Msg 21312may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312may indicate that the Msg 11311was received by the base station. The Msg 21312may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 31313, and/or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 21312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and/or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0<t_id<80), f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0<f_id<8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier). The UE may transmit the Msg 31313in response to a successful reception of the Msg 21312(e.g., using resources identified in the Msg 21312). The Msg 31313may be used for contention resolution in, for example, the contention-based random access procedure illustrated inFIG.13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 31313and the Msg 41314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 31313(e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 21312, and/or any other suitable identifier). The Msg 41314may be received after or in response to the transmitting of the Msg 31313. If a C-RNTI was included in the Msg 31313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 31313(e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 41314will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 31313, the UE may determine that the contention resolution is successful and/or the UE may determine that the random access procedure is successfully completed. The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 11311and/or the Msg 31313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 11311and the Msg 31313) in one or more cases. For example, the UE may determine and/or switch an uplink carrier for the Msg 11311and/or the Msg 31313based on a channel clear assessment (e.g., a listen-before-talk). FIG.13Billustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated inFIG.13A, a base station may, prior to initiation of the procedure, transmit a configuration message1320to the UE. The configuration message1320may be analogous in some respects to the configuration message1310. The procedure illustrated inFIG.13Bcomprises transmission of two messages: a Msg 11321and a Msg 21322. The Msg 11321and the Msg 21322may be analogous in some respects to the Msg 11311and a Msg 21312illustrated inFIG.13A, respectively. As will be understood fromFIGS.13A and13B, the contention-free random access procedure may not include messages analogous to the Msg 31313and/or the Msg 41314. The contention-free random access procedure illustrated inFIG.13Bmay be initiated for a beam failure recovery, other SI request, SCell addition, and/or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 11321. The UE may receive, from the base station via PDCCH and/or RRC, an indication of a preamble (e.g., ra-PreambleIndex). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and/or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated inFIG.13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 11321and reception of a corresponding Msg 21322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and/or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request. FIG.13Cillustrates another two-step random access procedure. Similar to the random access procedures illustrated inFIGS.13A and13B, a base station may, prior to initiation of the procedure, transmit a configuration message1330to the UE. The configuration message1330may be analogous in some respects to the configuration message1310and/or the configuration message1320. The procedure illustrated inFIG.13Ccomprises transmission of two messages: a Msg A1331and a Msg B1332. Msg A1331may be transmitted in an uplink transmission by the UE. Msg A1331may comprise one or more transmissions of a preamble1341and/or one or more transmissions of a transport block1342. The transport block1342may comprise contents that are similar and/or equivalent to the contents of the Msg 31313illustrated inFIG.13A. The transport block1342may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like). The UE may receive the Msg B1332after or in response to transmitting the Msg A1331. The Msg B1332may comprise contents that are similar and/or equivalent to the contents of the Msg 21312(e.g., an RAR) illustrated inFIGS.13A and13Band/or the Msg 41314illustrated inFIG.13A. The UE may initiate the two-step random access procedure inFIG.13Cfor licensed spectrum and/or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and/or the like); whether the UE has valid TA or not; a cell size; the UE's RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and/or any other suitable factors. The UE may determine, based on two-step RACH parameters included in the configuration message1330, a radio resource and/or an uplink transmit power for the preamble1341and/or the transport block1342included in the Msg A1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and/or a power control for the preamble1341and/or the transport block1342. A time-frequency resource for transmission of the preamble1341(e.g., a PRACH) and a time-frequency resource for transmission of the transport block1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and/or receiving Msg B1332. The transport block1342may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and/or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B1332as a response to the Msg A1331. The Msg B1332may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and/or an MCS); a UE identifier for contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B1332is matched to a preamble transmitted by the UE; and/or the identifier of the UE in Msg B1332is matched to the identifier of the UE in the Msg A1331(e.g., the transport block1342). A UE and a base station may exchange control signaling. The control signaling may be referred to as L1/L2 control signaling and may originate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and/or uplink control signaling transmitted from the UE to the base station. The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and/or a transport format; a slot format information; a preemption indication; a power control command; and/or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs. A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI). DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and/or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and/or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 31313illustrated inFIG.13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and/or the like. Depending on the purpose and/or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and/or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size. After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and/or QPSK modulation. A base station may map the coded and modulated DCI on resource elements used and/or configured for a PDCCH. Based on a payload size of the DCI and/or a coverage of the base station, the base station may transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of the contiguous CCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/or any other suitable number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping). FIG.14Aillustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a time-frequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example ofFIG.14A, a first CORESET1401and a second CORESET1402occur at the first symbol in a slot. The first CORESET1401overlaps with the second CORESET1402in the frequency domain A third CORESET1403occurs at a third symbol in the slot. A fourth CORESET1404occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain. FIG.14Billustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and/or frequency-selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET. The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and/or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI). As shown inFIG.14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and/or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and/or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and/or the like). The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats. There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code. The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to “1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”. After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI. FIG.15illustrates an example of a wireless device1502in communication with a base station1504in accordance with embodiments of the present disclosure. The wireless device1502and base station1504may be part of a mobile communication network, such as the mobile communication network100illustrated inFIG.1A, the mobile communication network150illustrated inFIG.1B, or any other communication network. Only one wireless device1502and one base station1504are illustrated inFIG.15, but it will be understood that a mobile communication network may include more than one UE and/or more than one base station, with the same or similar configuration as those shown inFIG.15. The base station1504may connect the wireless device1502to a core network (not shown) through radio communications over the air interface (or radio interface)1506. The communication direction from the base station1504to the wireless device1502over the air interface1506is known as the downlink, and the communication direction from the wireless device1502to the base station1504over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and/or some combination of the two duplexing techniques. In the downlink, data to be sent to the wireless device1502from the base station1504may be provided to the processing system1508of the base station1504. The data may be provided to the processing system1508by, for example, a core network. In the uplink, data to be sent to the base station1504from the wireless device1502may be provided to the processing system1518of the wireless device1502. The processing system1508and the processing system1518may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect toFIG.2A,FIG.2B,FIG.3, andFIG.4A. Layer 3 may include an RRC layer as with respect toFIG.2B. After being processed by processing system1508, the data to be sent to the wireless device1502may be provided to a transmission processing system1510of base station1504. Similarly, after being processed by the processing system1518, the data to be sent to base station1504may be provided to a transmission processing system1520of the wireless device1502. The transmission processing system1510and the transmission processing system1520may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect toFIG.2A,FIG.2B,FIG.3, andFIG.4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and/or the like. At the base station1504, a reception processing system1512may receive the uplink transmission from the wireless device1502. At the wireless device1502, a reception processing system1522may receive the downlink transmission from base station1504. The reception processing system1512and the reception processing system1522may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect toFIG.2A,FIG.2B,FIG.3, andFIG.4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and/or the like. As shown inFIG.15, a wireless device1502and the base station1504may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit/receive diversity, and/or beamforming. In other examples, the wireless device1502and/or the base station1504may have a single antenna. The processing system1508and the processing system1518may be associated with a memory1514and a memory1524, respectively. Memory1514and memory1524(e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system1508and/or the processing system1518to carry out one or more of the functionalities discussed in the present application. Although not shown inFIG.15, the transmission processing system1510, the transmission processing system1520, the reception processing system1512, and/or the reception processing system1522may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities. The processing system1508and/or the processing system1518may comprise one or more controllers and/or one or more processors. The one or more controllers and/or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system1508and/or the processing system1518may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device1502and the base station1504to operate in a wireless environment. The processing system1508and/or the processing system1518may be connected to one or more peripherals1516and one or more peripherals1526, respectively. The one or more peripherals1516and the one or more peripherals1526may include software and/or hardware that provide features and/or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and/or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and/or the like). The processing system1508and/or the processing system1518may receive user input data from and/or provide user output data to the one or more peripherals1516and/or the one or more peripherals1526. The processing system1518in the wireless device1502may receive power from a power source and/or may be configured to distribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system1508and/or the processing system1518may be connected to a GPS chipset1517and a GPS chipset1527, respectively. The GPS chipset1517and the GPS chipset1527may be configured to provide geographic location information of the wireless device1502and the base station1504, respectively. FIG.16Aillustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated byFIG.16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. FIG.16Billustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-HWA or CP-OFDM baseband signal for an antenna port and/or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission. FIG.16Cillustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and/or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. FIG.16Dillustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission. A wireless device may receive from a base station one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g. primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g. two or more base stations in dual-connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels. A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running A timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period/window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period/window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window. A base station may transmit one or more MAC PDUs to a wireless device. In an example, a MAC PDU may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, bit strings may be represented by tables in which the most significant bit is the leftmost bit of the first line of the table, and the least significant bit is the rightmost bit on the last line of the table. More generally, the bit string may be read from left to right and then in the reading order of the lines. In an example, the bit order of a parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit. In an example, a MAC SDU may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, a MAC SDU may be included in a MAC PDU from the first bit onward. A MAC CE may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. A MAC subheader may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, a MAC subheader may be placed immediately in front of a corresponding MAC SDU, MAC CE, or padding. A MAC entity may ignore a value of reserved bits in a DL MAC PDU. In an example, a MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs may comprise: a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. The MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding. In an example, when a MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may comprise: an R field with a one bit length; an F field with a one-bit length; an LCID field with a multi-bit length; an L field with a multi-bit length, or a combination thereof. FIG.17Ashows an example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader ofFIG.17A, the LCID field may be six bits in length, and the L field may be eight bits in length.FIG.17Bshows example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader shown inFIG.17B, the LCID field may be six bits in length, and the L field may be sixteen bits in length. When a MAC subheader corresponds to a fixed sized MAC CE or padding, the MAC subheader may comprise: an R field with a two-bit length and an LCID field with a multi-bit length.FIG.17Cshows an example of a MAC subheader with an R field and an LCID field. In the example MAC subheader shown inFIG.17C, the LCID field may be six bits in length, and the R field may be two bits in length. FIG.18Ashows an example of a DL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. A MAC subPDU, comprising a MAC CE, may be placed before: a MAC subPDU comprising a MAC SDU, or a MAC subPDU comprising padding.FIG.18Bshows an example of a UL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. In an embodiment, a MAC subPDU comprising a MAC CE may be placed after all MAC subPDUs comprising a MAC SDU. In addition, the MAC subPDU may be placed before a MAC subPDU comprising padding. In an example, a MAC entity of a base station may transmit one or more MAC CEs to a MAC entity of a wireless device.FIG.19shows an example of multiple LCIDs that may be associated with the one or more MAC CEs. The one or more MAC CEs comprise at least one of: a SP ZP CSI-RS Resource Set Activation/Deactivation MAC CE, a PUCCH spatial relation Activation/Deactivation MAC CE, a SP SRS Activation/Deactivation MAC CE, a SP CSI reporting on PUCCH Activation/Deactivation MAC CE, a TCI State Indication for UE-specific PDCCH MAC CE, a TCI State Indication for UE-specific PDSCH MAC CE, an Aperiodic CSI Trigger State Subselection MAC CE, a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE, a UE contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a Long DRX command MAC CE, an SCell activation/deactivation MAC CE (1 Octet), an SCell activation/deactivation MAC CE (4 Octet), and/or a duplication activation/deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by a MAC entity of a base station to a MAC entity of a wireless device, may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a long DRX command MAC CE. In an example, the MAC entity of the wireless device may transmit to the MAC entity of the base station one or more MAC CEs.FIG.20shows an example of the one or more MAC CEs. The one or more MAC CEs may comprise at least one of: a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single entry PHR MAC CE, a multiple entry PHR MAC CE, a short truncated BSR, and/or a long truncated BSR. In an example, a MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a short-truncated command MAC CE. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may simultaneously receive or transmit on one or more CCs, depending on capabilities of the wireless device, using the technique of CA. In an embodiment, a wireless device may support CA for contiguous CCs and/or for non-contiguous CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, a wireless device may have one RRC connection with a network. During an RRC connection establishment/re-establishment/handover, a cell providing NAS mobility information may be a serving cell. During an RRC connection re-establishment/handover procedure, a cell providing a security input may be a serving cell. In an example, the serving cell may denote a PCell. In an example, a base station may transmit, to a wireless device, one or more messages comprising configuration parameters of a plurality of one or more SCells, depending on capabilities of the wireless device. When configured with CA, a base station and/or a wireless device may employ an activation/deactivation mechanism of an SCell to improve battery or power consumption of the wireless device. When a wireless device is configured with one or more SCells, a base station may activate or deactivate at least one of the one or more SCells. Upon configuration of an SCell, the SCell may be deactivated unless an SCell state associated with the SCell is set to “activated” or “dormant.” A wireless device may activate/deactivate an SCell in response to receiving an SCell Activation/Deactivation MAC CE. In an example, a base station may transmit, to a wireless device, one or more messages comprising an SCell timer (e.g., sCellDeactivationTimer). In an example, a wireless device may deactivate an SCell in response to an expiry of the SCell timer. When a wireless device receives an SCell Activation/Deactivation MAC CE activating an SCell, the wireless device may activate the SCell. In response to the activating the SCell, the wireless device may perform operations comprising SRS transmissions on the SCell; CQI/PMI/RI/CRI reporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; and/or PUCCH transmissions on the SCell. In response to the activating the SCell, the wireless device may start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in the slot when the SCell Activation/Deactivation MAC CE activating the SCell has been received. In an example, in response to the activating the SCell, the wireless device may (re-)initialize one or more suspended configured uplink grants of a configured grant Type 1 associated with the SCell according to a stored configuration. In an example, in response to the activating the SCell, the wireless device may trigger PHR. When a wireless device receives an SCell Activation/Deactivation MAC CE deactivating an activated SCell, the wireless device may deactivate the activated SCell. In an example, when a first SCell timer (e.g., sCellDeactivationTimer) associated with an activated SCell expires, the wireless device may deactivate the activated SCell. In response to the deactivating the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In an example, in response to the deactivating the activated SCell, the wireless device may clear one or more configured downlink assignments and/or one or more configured uplink grants of a configured uplink grant Type 2 associated with the activated SCell. In an example, in response to the deactivating the activated SCell, the wireless device may: suspend one or more configured uplink grants of a configured uplink grant Type 1 associated with the activated SCell; and/or flush HARQ buffers associated with the activated SCell. When an SCell is deactivated, a wireless device may not perform operations comprising: transmitting SRS on the SCell; reporting CQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell; transmitting on RACH on the SCell; monitoring at least one first PDCCH on the SCell; monitoring at least one second PDCCH for the SCell; and/or transmitting a PUCCH on the SCell. When at least one first PDCCH on an activated SCell indicates an uplink grant or a downlink assignment, a wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when at least one second PDCCH on a serving cell (e.g., a PCell or an SCell configured with PUCCH, i.e., PUCCH SCell) scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, a wireless device may restart the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when an SCell is deactivated, if there is an ongoing random access procedure on the SCell, a wireless device may abort the ongoing random access procedure on the SCell. FIG.21Ashows an example of an SCell Activation/Deactivation MAC CE of one octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’ as shown inFIG.19) may identify the SCell Activation/Deactivation MAC CE of one octet. The SCell Activation/Deactivation MAC CE of one octet may have a fixed size. The SCell Activation/Deactivation MAC CE of one octet may comprise a single octet. The single octet may comprise a first number of C-fields (e.g., seven) and a second number of R-fields (e.g., one). FIG.21Bshows an example of an SCell Activation/Deactivation MAC CE of four octets. A second MAC PDU subheader with a second LCID (e.g., ‘111001’ as shown inFIG.19) may identify the SCell Activation/Deactivation MAC CE of four octets. The SCell Activation/Deactivation MAC CE of four octets may have a fixed size. The SCell Activation/Deactivation MAC CE of four octets may comprise four octets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g.,1). InFIG.21Aand/orFIG.21B, a Ci field may indicate an activation/deactivation status of an SCell with an SCell index i if an SCell with SCell index i is configured. In an example, when the Ci field is set to one, an SCell with an SCell index i may be activated. In an example, when the Ci field is set to zero, an SCell with an SCell index i may be deactivated. In an example, if there is no SCell configured with SCell index i, the wireless device may ignore the Ci field. InFIG.21AandFIG.21B, an R field may indicate a reserved bit. The R field may be set to zero. A base station may configure a wireless device with uplink (UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation is configured, the base station may further configure the wireless device with at least DL BWP(s) (i.e., there may be no UL BWPs in the UL) to enable BA on an SCell. For the PCell, an initial active BWP may be a first BWP used for initial access. For the SCell, a first active BWP may be a second BWP configured for the wireless device to operate on the SCell upon the SCell being activated. In paired spectrum (e.g., FDD), a base station and/or a wireless device may independently switch a DL BWP and an UL BWP. In unpaired spectrum (e.g., TDD), a base station and/or a wireless device may simultaneously switch a DL BWP and an UL BWP. In an example, a base station and/or a wireless device may switch a BWP between configured BWPs by means of a DCI or a BWP inactivity timer. When the BWP inactivity timer is configured for a serving cell, the base station and/or the wireless device may switch an active BWP to a default BWP in response to an expiry of the BWP inactivity timer associated with the serving cell. The default BWP may be configured by the network. In an example, for FDD systems, when configured with BA, one UL BWP for each uplink carrier and one DL BWP may be active at a time in an active serving cell. In an example, for TDD systems, one DL/UL BWP pair may be active at a time in an active serving cell. Operating on the one UL BWP and the one DL BWP (or the one DL/UL pair) may improve wireless device battery consumption. BWPs other than the one active UL BWP and the one active DL BWP that the wireless device may work on may be deactivated. On deactivated BWPs, the wireless device may: not monitor PDCCH; and/or not transmit on PUCCH, PRACH, and UL-SCH. In an example, a serving cell may be configured with at most a first number (e.g., four) of BWPs. In an example, for an activated serving cell, there may be one active BWP at any point in time. In an example, a BWP switching for a serving cell may be used to activate an inactive BWP and deactivate an active BWP at a time. In an example, the BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink grant. In an example, the BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). In an example, the BWP switching may be controlled by a MAC entity in response to initiating a Random Access procedure. Upon addition of an SpCell or activation of an SCell, one BWP may be initially active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP for a serving cell may be indicated by RRC and/or PDCCH. In an example, for unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common for both UL and DL. FIG.22shows an example of BWP switching on a cell (e.g., PCell or SCell). In an example, a wireless device may receive, from a base station, at least one RRC message comprising parameters of a cell and one or more BWPs associated with the cell. The RRC message may comprise: RRC connection reconfiguration message (e.g., RRCReconfiguration); RRC connection reestablishment message (e.g., RRCReestablishment); and/or RRC connection setup message (e.g., RRCSetup). Among the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), one BWP as the default BWP (e.g., BWP 0). The wireless device may receive a command (e.g., RRC message, MAC CE or DCI) to activate the cell at an nth slot. In case the cell is a PCell, the wireless device may not receive the command activating the cell, for example, the wireless device may activate the PCell once the wireless device receives RRC message comprising configuration parameters of the PCell. The wireless device may start monitoring a PDCCH on BWP 1 in response to activating the cell. In an example, the wireless device may start (or restart) a BWP inactivity timer (e.g., bwp-InactivityTimer) at an mth slot in response to receiving a DCI indicating DL assignment on BWP 1. The wireless device may switch back to the default BWP (e.g., BWP 0) as an active BWP when the BWP inactivity timer expires, at sth slot. The wireless device may deactivate the cell and/or stop the BWP inactivity timer when the sCellDeactivationTimer expires (e.g., if the cell is a SCell). In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer on the PCell. In an example, a MAC entity may apply normal operations on an active BWP for an activated serving cell configured with a BWP comprising: transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH; transmitting PUCCH; receiving DL-SCH; and/or (re-) initializing any suspended configured uplink grants of configured grant Type 1 according to a stored configuration, if any. In an example, on an inactive BWP for each activated serving cell configured with a BWP, a MAC entity may: not transmit on UL-SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignment and configured uplink grant of configured grant Type 2; and/or suspend any configured uplink grant of configured Type 1. In an example, if a MAC entity receives a PDCCH for a BWP switching of a serving cell while a Random Access procedure associated with this serving cell is not ongoing, a wireless device may perform the BWP switching to a BWP indicated by the PDCCH. In an example, if a bandwidth part indicator field is configured in DCI format 1_1, the bandwidth part indicator field value may indicate the active DL BWP, from the configured DL BWP set, for DL receptions. In an example, if a bandwidth part indicator field is configured in DCI format 0_1, the bandwidth part indicator field value may indicate the active UL BWP, from the configured UL BWP set, for UL transmissions. In an example, for a primary cell, a wireless device may be provided by a higher layer parameter Default-DL-BWP a default DL BWP among the configured DL BWPs. If a wireless device is not provided a default DL BWP by the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In an example, a wireless device may be provided by higher layer parameter bwp-InactivityTimer, a timer value for the primary cell. If configured, the wireless device may increment the timer, if running, every interval of 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 if the wireless device may not detect a DCI format 1_1 for paired spectrum operation or if the wireless device may not detect a DCI format 1_1 or DCI format 0_1 for unpaired spectrum operation during the interval. In an example, if a wireless device is configured for a secondary cell with higher layer parameter Default-DL-BWP indicating a default DL BWP among the configured DL BWPs and the wireless device is configured with higher layer parameter bwp-InactivityTimer indicating a timer value, the wireless device procedures on the secondary cell may be same as on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell. In an example, if a wireless device is configured by higher layer parameter Active-BWP-DL-SCell a first active DL BWP and by higher layer parameter Active-BWP-UL-SCell a first active UL BWP on a secondary cell or carrier, the wireless device may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier. In an example, a set of PDCCH candidates for a wireless device to monitor is defined in terms of PDCCH search space sets. A search space set comprises a CSS set or a USS set. A wireless device monitors PDCCH candidates in one or more of the following search spaces sets: a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI, a MsgB-RNTI, or a TC-RNTI on the primary cell, a Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG, a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType=common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s), and a USS set configured by SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI. In an example, a wireless device determines a PDCCH monitoring occasion on an active DL BWP based on one or more PDCCH configuration parameters (e.g., based on example embodiment ofFIG.27) comprising: a PDCCH monitoring periodicity, a PDCCH monitoring offset, and a PDCCH monitoring pattern within a slot. For a search space set (SS s), the wireless device determines that a PDCCH monitoring occasion(s) exists in a slot with number ns,fμin a frame with number nfif (nf·Nslotframe,μ+ns,fμ−os)mod ks=0. Nslotframe,μis a number of slots in a frame when numerology μ is configured. osis a slot offset indicated in the PDCCH configuration parameters (e.g., based on example embodiment ofFIG.27). ksis a PDCCH monitoring periodicity indicated in the PDCCH configuration parameters (e.g., based on example embodiment ofFIG.27). The wireless device monitors PDCCH candidates for the search space set for Tsconsecutive slots, starting from slot ns,fμ, and does not monitor PDCCH candidates for search space set s for the next ks-Tsconsecutive slots. In an example, a USS at CCE aggregation level L∈{1, 2, 4, 8, 16} is defined by a set of PDCCH candidates for CCE aggregation level L. In an example, a wireless device decides, for a search space set s associated with CORESET p, CCE indexes for aggregation level L corresponding to PDCCH candidate ms,nCIof the search space set in slot ns,fμfor an active DL BWP of a serving cell corresponding to carrier indicator field value nCIas L·{(Yp,ns,fμ+⌊ms,nCI·NCCE,pL·MS,max(L)⌋+nCI)mod⌊NCCE,p/L⌋}+i, where, Yp,ns,fμ=0 for any CSS; Yp,ns,fμ=(Ap·Yp,ns,fμ−1) mod D for a USS, Yp,−1=nRNTI≠0, Ap=39827 for p mod 3=0, Ap=39829 for p mod 3=1, Ap=39839 for p mod 3=2, and D=65537; i=0, . . . , L−1; NCCE,pis the number of CCEs, numbered from 0 to NCCE,p−1, in CORESET p; nCIis the carrier indicator field value if the wireless device is configured with a carrier indicator field by CrossCarrierSchedulingConfig for the serving cell on which PDCCH is monitored; otherwise, including for any CSS, nCI=0; ms,nCI=0, . . . , Ms,nCI(L)−1, where Ms,nCI(L)is the number of PDCCH candidates the wireless device is configured to monitor for aggregation level L of a search space set s for a serving cell nCIcorresponding to nCI; for any CSS, Ms,max(L)=Ms,0(L); for a USS, Ms,max(L)is the maximum of Ms,nCI(L)over all configured cCIvalues for a CCE aggregation level L of search space set s; and the RNTI value used for RNTI is the C-RNTI. In an example, a wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set comprising a plurality of search spaces (SSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. A CORESET may be configured based on example embodiment ofFIG.26. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common SSs, and/or number of PDCCH candidates in the UE-specific SSs) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The possible DCI formats may be based on example embodiments ofFIG.23. FIG.23shows examples of DCI formats which may be used by a base station transmit control information to a wireless device or used by the wireless device for PDCCH monitoring. Different DCI formats may comprise different DCI fields and/or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In an example, DCI format may be used to schedule PUSCH in one cell. DCI format 0_1 may be used to schedule one or multiple PUSCH in one cell or indicate CG-DFI (configured grant-Downlink Feedback Information) for configured grant PUSCH, etc. The DCI format(s) which the wireless device may monitor in a SS may be configured. FIG.24Ashows an example of configuration parameters of a master information block (MIB) of a cell (e.g., PCell). In an example, a wireless device, based on receiving primary synchronization signal (PSS) and/or secondary synchronization signal (SSS), may receive a MIB via a PBCH. The configuration parameters of a MIB may comprise six bits (systemFrameNumber) of system frame number (SFN), subcarrier spacing indication (subCarrierSpacingCommon), a frequency domain offset (ssb-SubcarrierOffset) between SSB and overall resource block grid in number of subcarriers, an indication (cellBarred) indicating whether the cell is bared, a DMRS position indication (dmrs-TypeA-Position) indicating position of DMRS, parameters of CORESET and SS of a PDCCH (pdcch-ConfigSIB1) comprising a common CORESET, a common search space and necessary PDCCH parameters, etc. In an example, a pdcch-ConfigSIB1 may comprise a first parameter (e.g., controlResourceSetZero) indicating a common ControlResourceSet (CORESET) with ID #0 (e.g., CORESET #0) of an initial BWP of the cell. controlResourceSetZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify a configuration of CORESET #0. FIG.24Bshows an example of a configuration of CORESET #0. As shown inFIG.24B, based on a value of the integer of controlResourceSetZero, a wireless device may determine a SSB and CORESET #0 multiplexing pattern, a number of RBs for CORESET #0, a number of symbols for CORESET #0, an RB offset for CORESET #0. In an example, a pdcch-ConfigSIB1 may comprise a second parameter (e.g., searchSpaceZero) indicating a common search space with ID #0 (e.g., SS #0) of the initial BWP of the cell. searchSpaceZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify a configuration of SS #0. FIG.24Cshows an example of a configuration of SS #0. As shown inFIG.24C, based on a value of the integer of searchSpaceZero, a wireless device may determine one or more parameters (e.g., O, M) for slot determination of PDCCH monitoring, a first symbol index for PDCCH monitoring and/or a number of search spaces per slot. In an example, based on receiving a MIB, a wireless device may monitor PDCCH via SS #0 of CORESET #0 for receiving a DCI scheduling a system information block1(SIB1). A SIB1 message may be implemented based on example embodiment ofFIG.25. The wireless device may receive the DCI with CRC scrambled with a system information radio network temporary identifier (SI-RNTI) dedicated for receiving the SIB1. FIG.25shows an example of RRC configuration parameters of system information block (SIB). A SIB (e.g., SIB1) may be transmitted to all wireless devices in a broadcast way. The SIB may contain information relevant when evaluating if a wireless device is allowed to access a cell, information of paging configuration and/or scheduling configuration of other system information. A SIB may contain radio resource configuration information that is common for all wireless devices and barring information applied to a unified access control. In an example, a base station may transmit to a wireless device (or a plurality of wireless devices) one or more SIB information. As shown inFIG.25, parameters of the one or more SIB information may comprise: one or more parameters (e.g., cellSelectionInfo) for cell selection related to a serving cell, one or more configuration parameters of a serving cell (e.g., in ServingCellConfigCommonSIB IE), and one or more other parameters. The ServingCellConfigCommonSIB IE may comprise at least one of: common downlink parameters (e.g., in DownlinkConfigCommonSIB IE) of the serving cell, common uplink parameters (e.g., in UplinkConfigCommonSIB IE) of the serving cell, and other parameters. In an example, a DownlinkConfigCommonSIB IE may comprise parameters of an initial downlink BWP (initialDownlinkBWP IE) of the serving cell (e.g., SpCell). The parameters of the initial downlink BWP may be comprised in a BWP-DownlinkCommon IE (as shown inFIG.26). The BWP-DownlinkCommon IE may be used to configure common parameters of a downlink BWP of the serving cell. The base station may configure the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET #0 of this serving cell in the frequency domain. The wireless device may apply the locationAndBandwidth upon reception of this field (e.g., to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET #0 until after reception of RRCSetup/RRCResume/RRCReestablishment. In an example, the DownlinkConfigCommonSIB IE may comprise parameters of a paging channel configuration. The parameters may comprise a paging cycle value (T, by defaultPagingCycle IE), a parameter (nAndPagingFrameOffset IE) indicating total number N) of paging frames (PFs) and paging frame offset (PF_offset) in a paging DRX cycle, a number (Ns) for total paging occasions (POs) per PF, a first PDCCH monitoring occasion indication parameter (firstPDCCH-MonitoringOccasionofPO IE) indicating a first PDCCH monitoring occasion for paging of each PO of a PF. The wireless device, based on parameters of a PCCH configuration, may monitor PDCCH for receiving paging message, e.g., based on example embodiments ofFIG.28Aand/orFIG.28B. In an example, the parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in SIB1 for paging in initial DL BWP. For paging in a DL BWP other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in the corresponding BWP configuration. FIG.26shows an example of RRC configuration parameters (e.g., BWP-DownlinkCommon IE) in a downlink BWP of a serving cell. A base station may transmit to a wireless device (or a plurality of wireless devices) one or more configuration parameters of a downlink BWP (e.g., initial downlink BWP) of a serving cell. As shown inFIG.26, the one or more configuration parameters of the downlink BWP may comprise: one or more generic BWP parameters of the downlink BWP, one or more cell specific parameters for PDCCH of the downlink BWP (e.g., in pdcch-ConfigCommon IE), one or more cell specific parameters for the PDSCH of this BWP (e.g., in pdsch-ConfigCommon IE), and one or more other parameters. A pdcch-ConfigCommon IE may comprise parameters of COESET #0 (e.g., controlResourceSetZero) which can be used in any common or UE-specific search spaces. A value of the controlResourceSetZero may be interpreted like the corresponding bits in MIB pdcch-ConfigSIB1. A pdcch-ConfigCommon IE may comprise parameters (e.g., in commonControlResourceSet) of an additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESET #0. A pdcch-ConfigCommon IE may comprise parameters (e.g., in commonSearchSpaceList) of a list of additional common search spaces. Parameters of a search space may be implemented based on example ofFIG.27. A pdcch-ConfigCommon IE may indicate, from a list of search spaces, a search space for paging (e.g., pagingSearchSpace), a search space for random access procedure (e.g., ra-SearchSpace), a search space for SIB1 message (e.g., searchSpaceSIB1), a common search space #0 (e.g., searchSpaceZero), and one or more other search spaces. As shown inFIG.26, a control resource set (CORESET) may be associated with a CORESET index (e.g., ControlResourceSetId). The CORESET index with a value of 0 may identify a common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and may not be used in the ControlResourceSet IE. The CORESET index with other values may identify CORESETs configured by dedicated signaling or in SIB1. The controlResourceSetId is unique among the BWPs of a serving cell. A CORESET may be associated with coresetPoolIndex indicating an index of a CORESET pool for the CORESET. A CORESET may be associated with a time duration parameter (e.g., duration) indicating contiguous time duration of the CORESET in number of symbols. In an example, as shown inFIG.26, configuration parameters of a CORESET may comprise at least one of: frequency resource indication (e.g., frequencyDomainResources), a CCE-REG mapping type indicator (e.g., cce-REG-MappingType), a plurality of TCI states, an indicator indicating whether a TCI is present in a DCI, and the like. The frequency resource indication, comprising a number of bits (e.g., 45 bits), may indicate frequency domain resources, each bit of the indication corresponding to a group of 6 RBs, with grouping starting from the first RB group in a BWP of a cell (e.g., SpCell, SCell). The first (left-most/most significant) bit may correspond to the first RB group in the BWP, and so on. A bit that is set to 1 may indicate that an RB group, corresponding to the bit, belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the BWP within which the CORESET is configured may be set to zero. FIG.27shows an example of configuration of a search space (e.g., SearchSpace IE). In an example, one or more search space configuration parameters of a search space may comprise at least one of: a search space ID (searchSpaceId), a control resource set ID (controlResourceSetId), a monitoring slot periodicity and offset parameter (monitoringSlotPeriodicityAndOffset), a search space time duration value (duration), a monitoring symbol indication (monitoringSymbolsWithinSlot), a number of candidates for an aggregation level (nrofCandidates), and/or a SS type indicating a common SS type or a UE-specific SS type (searchSpaceType). The monitoring slot periodicity and offset parameter may indicate slots (e.g., in a radio frame) and slot offset (e.g., related to a starting of a radio frame) for PDCCH monitoring. The monitoring symbol indication may indicate on which symbol(s) of a slot a wireless device may monitor PDCCH on the SS. The control resource set ID may identify a control resource set on which a SS may be located. In an example, a wireless device, in RRC_IDLE or RRC_INACTIVE state, may periodically monitor paging occasions (POs) for receiving paging message for the wireless device. Before monitoring the POs, the wireless device, in RRC_IDLE or RRC_INACTIVE state, may wake up at a time before each PO for preparation and/or turn all components in preparation of data reception (warm up). The gap between the waking up and the PO may be long enough to accommodate all the processing requirements. The wireless device may perform, after the warming up, timing acquisition from SSB and coarse synchronization, frequency and time tracking, time and frequency offset compensation, and/or calibration of local oscillator. After that, the wireless device may monitor a PDCCH for a paging DCI in one or more PDCCH monitoring occasions based on configuration parameters of the PCCH configuration configured in SIB1. The configuration parameters of the PCCH configuration may be implemented based on example embodiments described above with respect toFIG.25. FIG.28Ashows an example of paging reception (or monitoring). In an example, a wireless device may use DRX for paging monitoring in RRC_IDLE and RRC_INACTIVE state in order to reduce power consumption. The wireless device may monitor a PO per DRX cycle. As shown inFIG.28A, a DRX cycle may have a length (T) of radio frames, which may be configured in the PCCH configuration. A PO may comprise a set of PDCCH monitoring occasions. A PO may consist of multiple time slots (e.g., subframe or OFDM symbol) where paging DCI can be sent. One Paging Frame (PF) may be one Radio Frame and may contain one or multiple PO(s) or starting point of a PO. In an example, a wireless device may determine a radio frame for a PF based on configuration parameters (e.g., T, N, PF_offset) of the PCCH configuration and an identifier (UE_ID) of the wireless device. The wireless device may determine whether a radio frame with a radio frame number (SFN) comprises a PF, for the wireless device, based on whether (SFN+PF_offset) mod T=(T div N)*(UE_ID mod N). In an example, a wireless device, in each PF, may determine an index (i_s) of a PO based on configuration parameters (e.g., N, Ns) of the PCCH configuration and the identifier (UE_ID) of the wireless device. The wireless device may determine the index (i_s) of the PO as floor(UE_ID/N) mod Ns. In an example, a UE_ID of a wireless device may be determined based on 5G-S-TMSI of the wireless device. 5G-S-TMSI may be a 48 bit long bit string. In the formulae above (PF calculation and PO calculation), 5G-S-TMSI may be interpreted as a binary number where the left most bit represents the most significant bit. If the wireless device has no 5G-S-TMSI, e.g., when the wireless device has not yet registered onto the network, the wireless device may use UE_ID=0 as default identity in determination of the PF and i_s. In an example, after determining the PO and the PF in a DRX cycle, the wireless device may determine PDCCH monitoring occasions. The wireless device may determine the PDCCH monitoring occasions for paging based on PDCCH configuration parameters for the paging in SIB1. The PDCCH configuration parameters for the paging may comprise at least one of: pagingSearchSpace, firstPDCCH-MonitoringOccasionOfPO and nrofPDCCH-MonitoringOccasionPerSSB-InPO, etc. In an example, When SearchSpaceId=0 is configured for pagingSearchSpace, the PDCCH monitoring occasions for paging may be same as for other system information (e.g., RMSI) reception. When SearchSpaceId=0 is configured for pagingSearchSpace, Ns is either 1 or 2. For Ns=1, there is only one PO which starts from the first PDCCH monitoring occasion for paging in the PF. For Ns=2, PO is either in the first half frame (i_s=0) or the second half frame (i_s=1) of the PF. In an example, When SearchSpaceId other than 0 is configured for pagingSearchSpace, the wireless device may monitor the (i_s+1)th PO, wherein i_s is determined based on example embodiments described above. In an example, a PO may comprise a set of ‘S*X’ consecutive PDCCH monitoring occasions where's′ is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is the nrofPDCCH-MonitoringOccasionPerSSB-InP0 if configured or is equal to 1 otherwise. In an example, a [x*S+K]th PDCCH monitoring occasion for paging in the PO may correspond to the Kth transmitted SSB, where x=0, 1 . . . , X−1, K=1, 2 . . . , S. In an example, the PDCCH monitoring occasions for paging which do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) may be sequentially numbered from zero starting from the first PDCCH monitoring occasion for paging in the PF. When firstPDCCH-MonitoringOccasionOfPO is present, the starting PDCCH monitoring occasion number of (i_s+1)th PO may be the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it is equal to i_s*S*X. If X>1, when the wireless device detects a PDCCH transmission addressed to P-RNTI within its PO, the wireless device may be not required to monitor the subsequent PDCCH monitoring occasions for this PO. In an example, in multi-beam operations, the wireless device may determine that the same paging message and the same Short Message are repeated in all transmitted beams. The selection of the beam(s) for the reception of the paging message and Short Message may be up to UE implementation. The paging message may be same for both RAN initiated paging and CN initiated paging. In an example, after determining the PDCCH monitoring occasions for a PO of a PF, the wireless device may monitor PDCCH for receiving a DCI scheduling a paging message. In response to receiving the DCI scheduling the paging message, the wireless device may retrieve the paging information. If the UE ID of the wireless device is comprised in the paging message, the wireless device may perform the subsequent processing. The wireless device may initiate RRC Connection Resume procedure upon receiving RAN initiated paging. If the wireless device receives a CN initiated paging in RRC_INACTIVE state, the wireless device may move to RRC_IDLE and inform NAS. If the UE ID of the wireless device is not comprised in the paging message, the wireless device may go back to sleep, e.g., without RRC state change (staying in RRC_IDLE and/or RRC_INACTIVE state). FIG.28Bshows an example of paging monitoring for different wireless devices. In an example, the configuration parameters of a PCCH may indicate that T=64 frames, N=32 frames (e.g., half frame), PF_offset=1 and Ns=2. As shown inFIG.28B, there may be four wireless devices (e.g., UE1 with ID=40, UE2 with ID=41, UE3 with ID=104, UE4 with ID=105). Based on the example embodiments ofFIG.28A, each wireless device may determine a PO of a PF in each DRX cycle. In an example, UE1 may monitor PO in SFN=16 of a first DRX cycle and PO in SFN=78 of a second DRX cycle. UE 2 may monitor PO in SFN=18 of the first DRX cycle and PO in SFN=80 of the second DRX cycle. As shown inFIG.28B, UE3 may share the same PO with UE1, UE4 may share the same PO with UE2, based on the PO and PF calculation formulas as shown above. Sharing a same PO of a PF with multiple wireless devices grouped based on UE_IDs and PCCH configuration parameters may reduce signaling overhead of paging PDCCH transmission. Each wireless device within the same group (e.g., sharing the same PO in the same PF) may further check whether the wireless device is paged based on whether the paging message, scheduled by the paging DCI received in the PO, comprises the UE ID of the wireless device. In an example, based on PF and PO determination formula shown above, a wireless device may wake up to monitor a PO (e.g., comprising time/frequency synchronization, blind PDCCH decoding, PDSCH reception for paging message, etc.) periodically for each DRX cycle, even if the base station has not paging message for the wireless device. In some system, a possibility of a wireless device being paged may be as low as 10%. In such cases, the wireless device, in most time of paging monitoring occasions, may waste power for waking up although there is no paging message for the wireless device. Some technologies may improve the power consumption for paging monitoring by introducing a paging early indication (PEI) before the actual PO. The PEI may be a signal sequence, e.g., SSB/CSI-RS/TRS, etc. The PEI may be comprised in a DCI via a PDCCH. The PEI may indicate whether the wireless device shall wake up to monitor a paging PDCCH in a PO. In response to the PEI indicating that the wireless device shall monitor the PO, the wireless device may wake up to monitor the PO. Otherwise, the wireless device may skip monitoring the PO. Based on this technology, the base station may dynamically indicate whether a wireless device shall monitor a PO. The wireless device may reduce power consumption for receiving a paging message. In an example, a wireless device may have different behavior when the wireless device does not detect the PEI. FIG.29Ashows an example of PEI processing. In an example, a wireless device may monitor a PEI (e.g., a signal sequence, or a PDCCH) in a monitoring occasion before a PO (e.g., the PO may be determined based on example embodiments described above with respect toFIG.28Aand/orFIG.28B). In response to receiving the PEI indicating that the wireless device shall monitor the PO (e.g., in case the base station decides that the wireless device is paged), the wireless device may monitor the PO according to the PCCH configuration. In an example, the wireless device may not receive the PEI, e.g., in case the base station decides not to page the wireless device. In response to not detecting/receiving the PEI, the wireless device may skip monitoring the PO. Not transmitting the PEI (or skipping the PEI on purpose), in case that there is no wireless device to be paged, may reduce signal overhead of the base station and/or reduce collision of the PEI transmission with other downlink signal (PDCCH/PDSCH) transmission. Not monitoring the PO (or skipping monitoring the PO), in case no PEI is detected, by the wireless device, may reduce power consumption of the wireless device. FIG.29Bshows an example of PEI processing. In an example, a wireless device may monitor a PEI (e.g., a signal sequence, or a PDCCH) in a monitoring occasion before a PO (e.g., the PO may be determined based on example embodiments described above with respect toFIG.28Aand/orFIG.28B). In response to receiving the PEI indicating that the wireless device shall monitor the PO (e.g., in case the base station decides that the wireless device is paged), the wireless device may monitor the PO according to the PCCH configuration. In response to receiving the PEI indicating that the wireless device shall not monitor the PO (e.g., in case the base station decides that the wireless device is not paged), the wireless device may skip monitoring the PO. In an example, the wireless device may not receive the PEI, e.g., in case the base station decides to drop the transmission of the PEI due to collision with other channels. In response to not detecting/receiving the PEI, the wireless device may monitor the PO according to the PCCH configuration. Not transmitting, by the base station, the PEI in case that there is collision of the PEI transmission with other downlink signal (PDCCH/PDSCH) transmission, may reduce collision of the PEI transmission with the other downlink signals. Monitoring the PO, in case the PEI is not detected, may reduce paging latency for the wireless device. In a 5G system, a base station may transmit SSBs with multiple beams. For each SSB transmission of a plurality of SSB transmissions, a base station may transmit a paging DCI over a plurality of PDCCH monitoring occasions, to increase reliability of the delivery of the paging DCI to a wireless device. A SSB transmission may be implemented based on example embodiments described above with respectFIG.11A,FIG.11B,FIG.24A,FIG.24Band/orFIG.25. To facilitate the wireless device to monitor the paging PDCCH correctly, the base station may configure (e.g., in SIB1 message) a first number (e.g., X) indicating a quantity of PDCCH monitoring occasions per SSB, of the plurality of SSBs, in a paging occasion (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPO IE as shown inFIG.25) and a second number (e.g., S) of actual transmitted SSBs (e.g., ssb-PositionsInBurst IE as shown inFIG.25). Based on the first number and the second number, the wireless device may determine the total number of PDCCH monitoring occasions in the paging occasion as X*S. In addition, the base station may further indicate a time offset (e.g., firstPDCCH-MonitoringOccasionOfPO as shown inFIG.25) indicating the starting PDCCH monitoring occasion, of the total number of PDCCH monitoring occasions, related to the starting frame of the paging occasion. Based on the nrofPDCCH-MonitoringOccasionPerS SB-InPO, ssb-PositionsInBurst and firstPDCCH-MonitoringOccasionOfPO, the wireless device may determine correct PDCCH monitoring occasions for receiving the paging DCI scheduling a paging message for the wireless device. In an example, to further reduce power consumption of a wireless device for monitoring a paging PDCCH for receiving a paging message, there are some proposals (e.g., as shown inFIG.29Aand/orFIG.29B) introducing a paging early indication (PEI), before the paging occasion, indicating whether the wireless device may skip monitoring the paging PDCCH. For improving reliability of the PEI transmission in high frequency scenarios, the base station may transmit the PEI with multiple beams. In this disclosure, a PDCCH monitoring occasion (MO) for receiving the PEI (comprised in a DCI) may be referred to as a PEI PDCCH MO. A PDCCH MO for receiving the paging DCI may be referred to as a paging PDCCH MO. In an example, a base station may configure a starting PEI PDCCH MO (e.g., firstPDCCH-MonitoringOccasionOfPEI) of a plurality of PEI PDCCH MOs for receiving a PEI in a PEI occasion. The starting PEI PDCCH MO may be separately configured from the starting paging PDCCH MO (e.g., firstPDCCH-MonitoringOccasionOfPO) of a plurality of paging PDCCH MOs for receiving a paging DCI in a paging occasion. Each PEI PDCCH MO corresponds to a respective SSB of a plurality of SSBs. However, existing technologies may not support multiple PEI PDCCH MOs being configured in a single SSB. Existing technologies may reduce transmission opportunities of a PEI in a SSB and therefore increase PEI transmission latency. In an example, implementing existing technologies, a base station may configure (e.g., in SIB1 message) a first number (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPEI) indicating a quantity of PEI PDCCH MOs, per SSB of a plurality of SSBs, for receiving a PEI in a PEI occasion. The first number may be separately configured from a second number (e.g., nrofPDCCH-MonitoringOccasionPerS SB-InPO) indicating a quantity of paging PDCCH MOs, per SSB of a plurality of SSBs, for receiving a paging DCI in a paging occasion. However, separately configuring two values, comprising first value indicating a quantity of PEI PDCCH MOs per SSB for the PEI and second value indicating a quantity of paging PDCCH MOs per SSB for the paging, may increase signaling overhead for SIB1 message transmission, since the SIB1 message is broadcasted to all wireless devices in the cell and is transmitted with a limited amount of radio resources. Existing technologies may increase signaling overhead and/or increase power consumption of a wireless device for detecting the SIB1 message. Therefore, there is a need to improve reliability of PEI transmission when multiple SSBs are configured and/or improve signaling overhead for SIB1 transmission for configuring the PEI parameters and/or reduce power consumption of a wireless device for receiving the SIB1 message. Example embodiments may comprise receiving by a wireless device and/or transmitting by a base station, SIB1 messages comprising configuration parameters for a PEI. The configuration parameters may comprise a first number indicating a quantity of PDCCH MOs, per SSB of SSBs, in a paging occasion. The configuration parameters may comprise a first location of a starting PDCCH MO of PDCCH MOs of a PEI occasion and a second location of a starting PDCCH MO of PDCCH MOs of the paging occasion. The wireless device may monitor, starting from the first location and over a second number of the PDCCH MOs of the PEI occasion, a first PDCCH (e.g., a PEI PDCCH). The second number is determined based on the first number and a quantity of the SSBs. For example, the second number may be a product of the first number by the quantity. The wireless device may receive a PEI based on monitoring the first PDCCH. In an example, the wireless device, in response to receiving the PEI indicating to monitor the paging occasion (or indicating to monitor a second PDCCH for receiving a paging DCI), may monitor, starting from the second location and over the second number of the PDCCH MOs of the paging occasion, a second PDCCH. The wireless device may receive a DCI scheduling a paging message for the wireless device, during monitoring the second PDCCH. In an example, the wireless device, in response to receiving the PEI indicating not to monitor the paging occasion, may skip monitoring, starting from the second location and over the second number of the PDCCH MOs of the paging occasion, the second PDCCH. In the example embodiment, the wireless device may determine that the total number of the PEI PDCCH MOs in a PEI occasion is same as the total number of paging PDCCH MOs in a paging occasion, when multiple PDCCH MOs are supported in a single SSB of a plurality of SSBs. In the example embodiment, the base station may determine that the total number of the PEI PDCCH MOs in the PEI occasion is same as the total number of the paging PDCCH MOs in the paging occasion, when multiple PDCCH MOs are supported in a single SSB of a plurality of SSBs. In the example embodiment, the total number of the PDCCH MOs for the PEI occasion or for the paging occasion are determined as a multiplication of a number (S) of SSBs and a number (X) of PDCCH MOs per SSB, wherein S and X are configured in SIB1 message. By implementing example embodiments, the base station may reduce signaling overhead for configuring parameters of PEI, e.g., by configuring a single value (X) for both the PEI and the paging, therefore reducing power consumption of a wireless device for receiving the SIB1 message. By implementing example embodiments, the base station may configure separate starting PDCCH MOs for the PEI occasion and the paging occasion to flexibly adjust the transmission time of the PEI and the paging DCI in different radio frames. FIG.30shows an example embodiment of PEI transmission for power saving. In an example, a base station may transmit to a wireless device a RRC message (e.g., MIB/SIB1/SIB2 message) comprising configuration parameters of a PEI occasion and a paging occasion. The configuration parameters may comprise a first number (e.g., S inFIG.30) indicating a quantity of PDCCH MOs per SSB of a plurality of SSBs in a paging occasion. The first number may be implemented based on example embodiment ofFIG.25(e.g., nrofPDCCH-MonitoringOccasionPerS SB-InPO). The configuration parameters may comprise a second number (e.g., X inFIG.30) indicating a total number of actually transmitted SSBs. The wireless device may use S and X for determining a total number of PDCCH MOs both for the PEI occasion and the paging occasion (although the first number is configured only for the paging occasion). In the example ofFIG.30, based on S and X, the wireless device may determine M PEI PDCCH MOs in the PEI occasion and N paging PDCCH MOs in the paging occasion, wherein M=N=S*X. In an example, the configuration parameters may further comprise a location indication (e.g., firstPDCCH-MonitoringOccasionOfPEI as shown inFIG.30) of the starting PDCCH MO of the M PEI PDCCH MOs. The configuration parameters may further comprise a location indication (e.g., firstPDCCH-MonitoringOccasionOfPO as shown inFIG.30) of the starting PDCCH MO of the N paging PDCCH MOs. In an example, the configuration parameters may further comprise a time offset (e.g., PEI-F_offset as shown inFIG.30) between a staring frame of the paging occasion and a starting frame of the PEI occasion. In an example, the configuration parameters may further comprise configuration parameters of a PEI search space and a paging search space. A search space may be implemented based on example embodiments described above with respect toFIG.27. In an example, the configuration parameters may further comprise parameters (e.g., T indicating paging/DRX cycle, PF_offset indicating paging frame offset, etc.) of the paging occasion, e.g., based on example embodiments described above with respect toFIG.25. In an example, based on the configuration parameters, the wireless device may determine the M PEI PDCCH MOs starting from the location indicated by the firstPDCCH-MonitoringOccasionOfPEI, as M=S*X. The wireless device may monitor the PEI PDCCH (or a PDCCH for receiving the PEI) via the PEI search space over the M PEI PDCCH MOs for receiving the PEI. The wireless device may receive a DCI comprising the PEI. In an example, based on the configuration parameters, in response to receiving the PEI indicating to monitor the paging occasion (or monitor the paging PDCCH), the wireless device may determine the N paging PDCCH MOs starting from the location indicated by the firstPDCCH-MonitoringOccasionOfPO, as N=S*X. The wireless device may monitor the paging PDCCH (or a PDCCH for receiving the paging DCI) via the paging search space over the N paging PDCCH MOs for receiving the paging DCI. The wireless device may receive a DCI scheduling a paging message for the wireless device. By implementing example embodiments, configuring a single value indicating a number of PDCCH MOs per SSB for a PEI occasion and a paging occasion and configuring two separate values for a starting PDCCH MO of PEI PDCCH MOs and a starting PDCCH MO of paging PDCCH MOs may enable the wireless device to correctly locate PEI PDCCH MOs and paging PDCCH MOs when multiple PDCCH MOs are supported in an SSB and when the base station has different signal (DL/UL, PDCCH/PDSCH/CSI-RS/SSBs) configurations in a PEI frame (where a PEI occasion occurs) and a paging frame. In an example, when different radio frames are configured with different TDD formats, a PEI PDCCH occasion may overlap with uplink transmissions on a first symbol in the PEI frame. In an example, a paging PDCCH occasion may overlap with uplink transmission on a second symbol in the paging frame. The first symbol may not be at the same location within a PEI frame as the second symbol within a paging frame. In order to save power consumption of the wireless device for receiving the PEI when configured with TDD formats in a plurality of radio frames, there is a need to define the behavior of the wireless device for PDCCH monitoring for receiving the PEI. In an example, based on the determined M PDCCH MOs of the PEI occasion (e.g., by implementing example embodiments described above with respect toFIG.30), the wireless device may further determine whether a first PDCCH MO, among the M PDCCH MOs of the PEI occasion in the PEI radio frame, overlaps with first uplink transmissions according to TDD configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon as shown inFIG.25) indicated by RRC messages. In response to the first PDCCH MO overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon), the wireless device may skip monitoring the first PDCCH MO of the M PDCCH MOs. The wireless device may sequentially number, the M PDCCH MOs after excluding PDCCH MOs overlapping with UL symbols, from zero starting from the starting PDCCH monitoring occasion (indicated by firstPDCCH-MonitoringOccasionOfPED for the PEI in the PEI occasion. The wireless device may, based on numbering the M PDCCH MOs, monitor the PDCCH for the PEI. In an example, based on the determined N PDCCH MOs of the paging occasion (e.g., by implementing example embodiments described above with respect toFIG.30), the wireless device may further determine whether a second PDCCH MO, among the N PDCCH MOs of the paging occasion in the paging radio frame, overlaps with second uplink transmissions according to TDD configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon as shown inFIG.25) indicated by RRC messages. In response to the second PDCCH MO overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon), the wireless device may skip monitoring the second PDCCH MO of the N PDCCH MOs. The wireless device may sequentially number, the N PDCCH MOs after excluding PDCCH MOs overlapping with UL symbols, from zero starting from the starting PDCCH monitoring occasion (indicated by firstPDCCH-MonitoringOccasionOfPO) for the paging in the paging occasion. The wireless device may, based on numbering the N PDCCH MOs, monitor the paging PDCCH for the paging DCI in response to receiving the PEI indicating to monitor the paging PDCCH. By implementing the example embodiments, the wireless device may determine whether a PEI PDCCH MO overlaps with UL symbols in a PEI occasion and separately and/or independently determine whether a paging PDCCH MO overlaps with UL symbols in a paging occasion, based on TDD configuration parameters of SIB1 message. Example embodiments may allow the base station to change TDD configurations in different radio frames (e.g., a first frame comprising the PEI occasion and a second frame comprising the paging occasion) and allow the wireless device to correctly locate PEI PDCCH MOs in the PEI frame (e.g., by omitting/skipping PDCCH monitoring on PEI PDCCH MO(s) overlapping with UL symbols) and correctly locate paging PDCCH MOs (e.g., by omitting/skipping PDCCH monitoring on paging PDCCH MO(s) overlapping with UL symbols) in the paging frame. Otherwise, by implementing existing technologies where the wireless device may perform the checking of whether a paging PDCCH MO overlaps with UL symbols in a paging frame comprising a paging occasion, the wireless device may incorrectly locate PEI PDCCH MOs in a PEI frame which may have different TDD configuration parameter from the paging frame. The existing technologies may not require the wireless device to perform the checking of whether a PEI PDCCH MO overlaps with UL symbols in the PEI frame comprising the PEI occasion. In an example, 5G system may be used in connected industries which may require high flexibility, high productivity and efficiency, low maintenance cost, and high operational safety. Wireless devices in such environment may comprise pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc. The requirements for these services may be higher than LPWA (e.g., LTE-MTC/NB-IoT) but lower than URLLC and eMBB in current 5G system. In an example, a smart city vertical may cover data collection and processing to more efficiently monitor and control city resources, and to provide services to city residents. Surveillance cameras may be an essential part of the smart city, factories and/or industries. Wearables use case may comprise smart watches, eHealth related devices, personal protection equipment (PPE), and medical monitoring devices for use in public safety applications, etc. One characteristic for the use case may be that the device is small in size. A wireless device, deployed in connected industries, smart city vertical and/or wearable use cases, etc., may have limited capability compared with a normal wireless device (e.g., a wireless device capable of processing URLLC and/or eMBB). In this specification, a wireless device (e.g., used in connected industries, smart city vertical, wearable use cases, etc.) with limited capabilities, compared with a wireless device with normal capabilities, may be referred to as a reduced capability (RedCap) UE. The wireless device with normal capabilities may be referred to as a non-RedCap UE, or a NorCap UE equivalently. FIG.31shows an example of capability comparison between a RedCap UE and a Non-RedCap UE. A RedCap UE may support a limited set of configurations due to implementation cost and power consumption consideration. In an example, a RedCap UE may be configured with at most one reception antenna, compared with a Non-RedCap UE configured with 2 or 4 reception antennas. A RedCap UE may support working within 20 MHz (e.g., in FR1), or 50 MHz (e.g., in PR2), in contrast to a Non-RedCap UE supporting 100 MHz (in FR1) or 200 MHz (in PR2). A RedCap UE may be capable of relaxed processing PDSCH/PUSCH within 1620 symbols, compared with the non-RedCap UE being capable of tightly processing PDSCH/PUSCH within 8-10 symbols. A RedCap UE may support at most 2 layers of MIMO transmission, compared with the non-RedCap UE being supporting at most 4 layers of MIMO transmission. A RedCap UE may support half duplex FDD transmission in which case the UE is not able to transmit at a first frequency band and receive at a second frequency band simultaneously, compared with a non-RedCap UE supporting full duplex FDD transmission in which case the UE is able to transmit at a first frequency band and receive at a second frequency band simultaneously, etc. In existing technologies, paging configuration (e.g., search space, CORESET, PCCH configuration) may be broadcasted to all wireless devices (e.g., via SIB1 as shown inFIG.25,FIG.26and/orFIG.27). A wireless device, in RRC_INACTIVE state or in RRC_IDLE state different from an RRC_CONNECTED state, is not connected to a base station, in which case, the base station may not be able to transmit wireless device specific messages to the wireless device. A wireless device, in RRC_INACTIVE state or in RRC_IDLE state, may periodically monitor PO in each DRX cycle based on the paging configuration and a UE_ID of the wireless device. To save power consumption for monitoring the PO, some existing technologies disclosed a paging early indication (PEI) based power saving mechanism. In some existing technologies, a base station may transmit a PEI before transmitting a paging DCI scheduling a paging message for a wireless device or a group of wireless devices. The PEI may indicate that there is a paging message for the wireless device or the group of wireless devices. Based on receiving a PEI transmitted by a base station and before starting to monitor the PO, a wireless device may determine whether to skip monitoring the PO. The PEI may be transmitted as a signal sequence (e.g., SSB/CSI-RS/TRS), or in a DCI via a PDCCH. In an example, the base station may transmit common RRC message (e.g., in SIB1) indicating configuration parameters (e.g., search space, CORESET, DCI format, etc.) of the PDCCH dedicated for the PEI. Due to the common RRC message being broadcasted, the configuration parameters of the PEI may be applied for all wireless devices in RRC_IDLE state or in RRC_INACTIVE state. The PEI configuration may be different from a wakeup (or power saving) configuration for a wireless device in RRC_CONNECTED state. The wakeup configuration for the wireless device in RRC_CONNECTED state may be transmitted in a wireless device specific RRC message. In an example, a RedCap wireless device may be more power limited than a non-RedCap wireless device. The RedCap wireless device may implement a power saving operation for paging monitoring in RRC_INACTIVE state or in RRC_IDLE state. The RedCap wireless device may implement the PEI based power saving operation for paging monitoring. However, due to limited capability of the RedCap wireless device, the RedCap wireless device, based on existing PEI based power saving operation, may not be able to receive the PEI. In an example, if the PEI is transmitted in frequency resources spread on a bandwidth greater than the maximum bandwidth supported by the RedCap wireless device, the RedCap wireless device may not receive/detect the PEI. In an example, if the PEI is transmitted in a search space with small aggregation level, the RedCap wireless device may not receive/detect the PEI due to reduced reception diversity gain caused by one reception antenna configured for the RedCap wireless device. In an example, if the gap between the PEI and the PO is shorter than the processing capability of the RedCap wireless device, the RedCap wireless device may not process quick enough to monitor the PO after receiving the PEI. Given the capability differences of a RedCap wireless device and a non-RedCap wireless device, a single PEI configuration, e.g., broadcasted blindly to all wireless devices in RRC_IDLE state or RRC_INACTIVE state, may not be received by both the RedCap wireless device and the non-RedCap wireless device. The RedCap wireless device, based on existing PEI technologies, may miss-detect the PEI. Miss-detecting the PEI may increase latency of paging message delivery if the RedCap wireless device skips PO monitoring when the RedCap wireless device miss-detects the PEI and the PEI notifies the RedCap wireless device that there is a paging message for it. Miss-detecting the PEI may increase power consumption of the wireless device if the RedCap wireless device monitors the PO when the RedCap wireless devices miss-detects the PEI and the PEI notifies the RedCap wireless device that there is no paging message for it. There is a need to reduce power consumption and/or paging message latency for a RedCap wireless device when monitoring paging occasion(s). In an example embodiment, for PEI transmission, a base station may configure separate initial BWPs on a cell, e.g., comprising a first initial BWP for configuration of PEI and paging for a RedCap wireless device and a second initial BWP for configuration of PEI and paging for a non-Redcap wireless device. A Redcap wireless device may receive both PEI and paging DCI on the first initial BWP of the cell. A non-Redcap wireless device may receive both PEI and paging DCI on the second initial BWP of the cell. The Redcap wireless device may not switch from the first initial BWP to the second initial BWP for receiving the PEI. The RedCap wireless device may not switch from the second initial BWP for receiving a paging DCI after receiving the PEI in the second initial BWP. A PEI search space may be configured on both the first initial BWP and the second initial BWP. When a wireless device is a RedCap wireless device, the wireless device may monitor a PEI PDCCH according to configuration parameters of the PEI search space on the first initial BWP. When a wireless device is a non-RedCap wireless device, the wireless device may monitor a PEI PDCCH according to configuration parameters of the PEI search space on the second initial BWP. In an example embodiment, a base station may separate PEI configurations (search space, CORESET, DCI format, RNTI, etc.) for a RedCap wireless device and a non-RedCap wireless device. A RedCap wireless device may monitor a PEI based on a PEI configuration dedicated for the RedCap wireless device. In an example, a RedCap wireless device may be with lower paging rate than a non-RedCap wireless device, e.g., when the RedCap wireless device (e.g., sensor, camera, wearable device, etc.) has more uplink data transmission than downlink data transmission (or is uplink data centric). Example embodiment may improve power consumption of the RedCap wireless device. In an example embodiment, a base station may configure different gaps between a PEI and a PO for different wireless device types (e.g., RedCap type, non-RedCap, etc.), e.g., based on different capabilities of the different wireless device types. Example embodiments may reduce possibility of miss-detecting a paging DCI after receiving a PEI for a RedCap wireless device. In an example embodiment, a base station may configure different processing behaviors, when not detecting a PEI, for a RedCap type and a non-RedCap type. The base station may indicate that a RedCap wireless device skips monitoring a PO (or any PO in a PF) in response to not detecting a PEI. The RedCap wireless device, by skipping monitoring the PO in response to not detecting a PEI, may reduce power consumption for paging, e.g., when the RedCap wireless device is power limited and/or is uplink data centric. The base station may indicate that a non-RedCap wireless device monitors a PO (or any PO in a PF) in response to not detecting a PEI. A non-RedCap wireless device, by monitoring a PO (in a PF) in response to not detecting a PEI, may reduce latency of paging message delivery. FIG.32shows an example embodiment of PEI based power saving for paging a wireless device. In an example embodiment, a base station may transmit to a wireless device (or a plurality of wireless devices), one or more RRC messages comprising configuration parameters of PEI configurations. The one or more RRC messages may be cell common messages comprising MIB, SIB1, SIB2, etc. The one or more RRC messages may be broadcasted to the plurality of wireless devices comprising the wireless device. The wireless device (or the plurality of wireless devices) may be in RRC_INACTIVE state or in RRC_IDLE state, based on example embodiments described above with respect toFIG.6. In an example embodiment, the PEI configurations may comprise at least a first PEI configuration dedicated for a RedCap wireless device type (or wireless device category) and second at least a second PEI configuration dedicated for a non-RedCap wireless device type (or wireless device category). In an example embodiment, the configuration parameters of the at least first PEI configuration (dedicated for the RedCap wireless device type) may, for transmission of a first DCI comprising a first PEI, indicate: a first CORESET for a first PDCCH, one or more first SSBs associated with the first CORESET, one or more first search spaces, a first DCI format, a first PEI-RNTI dedicated for receiving the first PEI, a first time offset between the first PEI and a first PO. The first PO may be configured for the RedCap wireless device type. In an example, the first CORESET of the at least first PEI configuration may be predefined (or configured) as CORESET #0, e.g., to ensure that the RedCap wireless device, with limited capability on supported bandwidth, receives the first PEI. The first PEI may comprise a plurality of indications, each indication being associated with a group of wireless devices of the RedCap type and indicating whether the group of wireless devices shall monitor a PO. In an example embodiment, the configuration parameters of the at least second PEI configuration (dedicated for the non-RedCap wireless device type) may, for transmission of a second DCI comprising a second PEI, indicate: a second CORESET for a second PDCCH, one or more second SSBs associated with the second CORESET, one or more second search spaces, a second DCI format, a second PEI-RNTI dedicated for receiving the second PEI, a second time offset between the second PEI and a second PO. The second PO may be configured for the non-RedCap wireless device type. The second PEI may comprise a plurality of indications, each indication being associated with a group of wireless devices of the non-RedCap type and indicating whether the group of wireless devices shall monitor a PO. In an example embodiment, the one or more first search spaces may be associated with higher aggregation level (e.g., 8, 16, 32 etc.), compared with the one or more second search spaces. The one or more first search spaces may be configured with longer monitoring periodicity than the one or more second search spaces. The first PEI-RNTI may be different from the second PEI-RNTI. In an example embodiment, by configuring two PEI configurations, one for RedCap wireless device type, another one for non-RedCap wireless device type, a base station may flexibly transmit a first PEI based on a first PEI configuration dedicated for the RedCap wireless device type, when the base station determines to page a RedCap wireless device, and/or transmit a second PEI based on a second PEI configuration dedicated for the non-RedCap wireless device type, when the base station determines to page a non-RedCap wireless device. The first PEI configuration may be configured such that the RedCap wireless device may receive/detect the first PEI. The second PEI configuration may be configured such that the non-RedCap wireless device may receive/detect the second PEI. The first PEI configuration and the second PEI configuration may be separately and/or independently configured. Example embodiments may improve PEI transmission robustness for a RedCap wireless device and/or PEI transmission efficiency for a non-RedCap wireless device. Based on the example embodiment ofFIG.32, separating the PEI configurations between the RedCap wireless device and the non-RedCap wireless device may improve power consumption of the RedCap wireless device. A RedCap wireless device may have lower paging rate than a non-RedCap wireless device, e.g., when the RedCap wireless device (e.g., sensor, camera, wearable device, etc.) has more uplink data transmission than downlink data transmission. The RedCap wireless device, by implementing existing technologies, may unnecessarily monitor the PEI with a same monitoring periodicity as a non-RedCap wireless device even though the RedCap wireless device has lower paging rate than the non-RedCap wireless device. In an example embodiment, based on the RRC messages, the wireless device may determine which one of the PEI configurations the wireless device shall monitor the PEI based on. In response to the wireless device being a RedCap wireless device, the wireless device may determine to monitor a first PEI based on the first PEI configuration. In response to the wireless device being a non-RedCap wireless device, the wireless device may determine to monitor a second PEI based on the second PEI configuration. In an example, monitoring a PEI based on a PEI configuration may comprise monitoring a PDCCH, for receiving a DCI comprising the PEI, on one or more search spaces of a CORESET. The RRC messages may indicate, in the PEI configurations, the DCI format and the RNTI associated with the DCI, the one or more search spaces and/or the CORESET. In this specification, a PDCCH, on which a DCI comprising a PEI is received, may be referred to as a PEI PDCCH. A PDCCH, on which a DCI scheduling paging message is received, may be referred to as a paging PDCCH. A PEI PDCCH and a paging PDCCH may be separately and independently configured. In an example, a PEI PDCCH may be associated with a paging PDCCH. In an example, the wireless device may monitor the PEI PDCCH in a PEI PDCCH monitoring occasion of a plurality of PEI PDCCH monitoring occasions associated with a PF. The PEI PDCCH monitoring occasions for PEI may be sequentially numbered from zero starting from the first PEI PDCCH monitoring occasion for PEI in the PF. A total number of the PEI PDCCH monitoring occasions in a PF may be determined based on PDCCH configuration parameters of the first PEI configuration. An index of the PEI PDCCH monitoring occasion, from the plurality of PEI PDCCH monitoring occasions, may correspond to an index (i_s) of a PO associated with the wireless device. The index (i_s) of the PO may be determined based on example embodiments described above withFIG.28Aand/orFIG.28B. In an example embodiment, the base station may transmit RRC messages comprising starting (or first) PEI PDCCH monitoring occasion indications (firstPDCCH-MonitoringOccasionOfPED for a plurality of POs in a PF, each PO being associated with a respective one of the indications. The wireless device may determine that a starting PEI PDCCH monitoring occasion number of (i_s+1)th PO may be the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPEI. The firstPDCCH-MonitoringOccasionOfPEI may be separately and independently configured from the firstPDCCH-MonitoringOccasionOfPO, e.g., based on example embodiments described above with respect toFIG.30. The firstPDCCH-MonitoringOccasionOfPO, configured in a PCCH IE, may be used to determine a staring paging PDCCH monitoring occasion number. In an example embodiment, a [x*S+K]th PEI PDCCH monitoring occasion for PEI corresponding to a PO may correspond to the Kth transmitted SSB, where x=0, 1 . . . , X−1, K=1, 2 . . . , S. S may be the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1. X may be the nrofPDCCH-MonitoringOccasionPerSSB-InPO if configured or may be equal to 1 otherwise. S and X may be implemented based on example embodiments described above with respect toFIG.25andFIG.30. In an example, in response to receiving the PEI indicating to monitor a paging PDCCH, the wireless device may monitor the paging PDCCH over a number of PDCCH monitoring occasions of a paging occasion, e.g., based on example embodiments described above with respect toFIG.25,FIG.28A,FIG.28B, and/orFIG.30. In an example, in response to receiving the PEI indicating not to monitor a paging PDCCH, the wireless device may skip monitoring the paging PDCCH over the number of PDCCH monitoring occasions of a paging occasion, e.g., based on example embodiments described above with respect toFIG.25,FIG.28A,FIG.28B,FIG.29A,FIG.29B, and/orFIG.30. In an example embodiment, the wireless device may reuse firstPDCCH-MonitoringOccasionOfPO to determine the starting PEI PDCCH monitoring occasion and the starting paging PDCCH monitoring occasion. The wireless device may determine the starting PEI PDCCH monitoring occasion number, from a plurality of PEI PDCCH monitoring occasions, of (i_s+1)th PO may be the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter. The wireless device may determine the starting paging PDCCH monitoring occasion number, from a plurality of paging PDCCH monitoring occasions, of (i_s+1)th PO may be the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter. In an example embodiment, as shown inFIG.31, based on the determined PEI PDCCH monitoring occasion(s), search space(s), CORESET, DCI format and/or PEI-RNTI, the wireless device may monitor the PEI PDCCH for receiving the first PEI dedicated for the RedCap wireless device type. The wireless device, based on the wireless device being the RedCap wireless device type, may skip monitoring the second PEI dedicated for the non-RedCap wireless device type. In response to detecting the first PEI indicating that the wireless device shall monitor the PO (or indicating that there is a paging message for the wireless device), the wireless device may monitor the paging PDCCH for receiving a paging DCI in a corresponding PO (e.g., 1st PO, dedicated for the RedCap wireless device type) associated with the first PEI. The wireless device may skip monitoring the second PO dedicated for the non-RedCap wireless device type. In an example, the wireless device may receive the paging DCI during monitoring the paging PDCCH in the first PO. The wireless device may receive the paging message comprising the UE_ID of the wireless device, based on the paging DCI. In an example, a wireless device may be a non-RedCap wireless device type. Based on the wireless device being the non-RedCap wireless device type, the wireless device may monitor the second PEI dedicated for the non-RedCap wireless device type and/or may skip monitoring the first PEI dedicated for the RedCap wireless device type. In response to detecting the second PEI indicating that the wireless device shall monitor the PO (or indicating that there is a paging message for the wireless device), the wireless device may monitor the paging PDCCH for receiving a paging DCI in a corresponding PO (e.g., 2nd PO, dedicated for the non-RedCap wireless device type) associated with the second PEI. The wireless device may skip monitoring the first PO dedicated for the RedCap wireless device type. In an example, the wireless device may receive the paging DCI during monitoring the paging PDCCH in the second PO. The wireless device may receive the paging message comprising the UE_ID of the wireless device, based on the paging DCI. Based on example embodiments ofFIG.32, separating PEI configurations for a RedCap wireless device type (or a RedCap type) and a non-RedCap wireless device type (or a non-RedCap type) may allow a base station to flexibly allocate radio resources for PEI and paging. In an example, when there are small number of RedCap wireless devices, the base station may configure same parameters of PEI (and/or paging) configuration for a RedCap type and a non-RedCap type, which may be referred to as shared PEI with shared paging configuration. In an example, when PEI signaling overhead is a consideration of the base station, the base station may configure same parameters of PEI for both RedCap type and a non-RedCap type and different parameters of paging for a RedCap type and a non-RedCap type, which may be referred to as shared PEI with separated paging. In an example, when paging signaling overhead is a consideration of the base station, the base station may configure separate parameters of PEI for a RedCap type and a non-RedCap type and same parameters of paging for a RedCap type and a non-RedCap type, which may be referred to as separated PEI with shared paging. In an example, when there are large number of RedCap wireless devices, the base station may configure different parameters of PEI (and/or paging) configuration for a RedCap type and a non-RedCap type, which may be referred to as separated PEI with separated paging configurations.FIG.33A,FIG.33B,FIG.33CandFIG.33Dshow various PEI and paging configurations based on example embodiment ofFIG.32. FIG.33Ashows an example embodiment of shared PEI with shared paging for a RedCap type and a non-RedCap type. In an example, a base station may transmit RRC messages (e.g., MIB, SIB1, etc.) comprising configuration parameters of first PEI/paging configuration for a RedCap type and second PEI/paging configuration for a non-RedCap type. The first PEI/paging configuration may be associated with same parameters as the second PEI/paging configuration. In an example, PEI PDCCH configuration of the first PEI may be same as PEI PDCCH configuration of the second PEI. In an example, PDCCH candidates for the first PEI may be different from PDCCH candidates for the second PEI, when configured with same CORESET and same search spaces. In an example, paging PDCCH configuration of the first paging may be same as paging PDCCH configuration of the second paging. In an example, when the base station determines shared PEI with shared paging for a RedCap type and a non-RedCap type, the base station may determine not to transmit the configuration parameters of the first PEI/paging configuration dedicated for the RedCap type. When the configuration parameters of the first PEI/paging configuration are absent in the RRC message, a wireless device may determine to use the configuration parameter of the second PEI/paging configuration regardless of whether the wireless device is a RedCap type or a non-RedCap type. Configuration of shared PEI with shared paging, based on example embodiment ofFIG.33A, may improve signaling overhead of the base station for PEI and paging. FIG.33Bshows an example embodiment of shared PEI with separate paging for a RedCap type and a non-RedCap type. In an example, a base station may transmit RRC messages (e.g., MIB, SIB1, etc.) comprising configuration parameters of first PEI/paging configuration for a RedCap type and second PEI/paging configuration for a non-RedCap type. The first PEI configuration may be associated with same parameters as the second PEI configuration. In an example, PEI PDCCH configuration of the first PEI may be same as PEI PDCCH configuration of the second PEI. The first paging configuration may be associated with different parameters as the second paging configuration. Paging PDCCH configuration of the first paging may be different from paging PDCCH configuration of the second paging. A wireless device may monitor the PEI PDCCH based on the PEI configuration regardless of whether the wireless device is a RedCap type or a non-RedCap type. Based on receiving the PEI indicating that there is a paging message for the wireless device, the wireless device may determine whether to monitor the first paging PDCCH or the second paging PDCCH based on whether the wireless device is a RedCap type or a non-RedCap type. Configuration of shared PEI with separated paging, based on example embodiment ofFIG.33B, may improve paging message delivery efficiency. FIG.33Cshows an example embodiment of separated PEI with shared paging for a RedCap type and a non-RedCap type. In an example, a base station may transmit RRC messages (e.g., MIB, SIB1, etc.) comprising configuration parameters of first PEI/paging configuration for a RedCap type and second PEI/paging configuration for a non-RedCap type. The first PEI configuration may be associated with different parameters from the second PEI configuration. In an example, PEI PDCCH configuration of the first PEI may be different from PEI PDCCH configuration of the second PEI. The first paging configuration may be associated with same parameters as the second paging configuration. Paging PDCCH configuration of the first paging may be same as paging PDCCH configuration of the second paging. A wireless device may determine to monitor the first PEI or the second PEI based on whether the wireless device is a RedCap type or a non-RedCap type. Based on receiving the PEI indicating that there is a paging message for the wireless device, the wireless device may determine monitor the paging PDCCH regardless of whether the wireless device is a RedCap type or a non-RedCap type. Configuration of separated PEI with shared paging, based on example embodiment ofFIG.33C, may improve power consumption of a RedCap UE for monitoring PEI. FIG.33Dshows an example embodiment of separated PEI with separated paging for a RedCap type and a non-RedCap type. In an example, a base station may transmit RRC messages (e.g., MIB, SIB1, etc.) comprising configuration parameters of first PEI/paging configuration for a RedCap type and second PEI/paging configuration for a non-RedCap type. The first PEI configuration may be associated with different parameters from the second PEI configuration. In an example, PEI PDCCH configuration of the first PEI may be different from PEI PDCCH configuration of the second PEI. The first paging configuration may be associated with different parameters from the second paging configuration. Paging PDCCH configuration of the first paging may be different from paging PDCCH configuration of the second paging. A wireless device may determine whether to monitor the first PEI or the second PEI based on whether the wireless device is a RedCap type or a non-RedCap type. Based on receiving the PEI indicating that there is a paging message for the wireless device, the wireless device may determine whether to monitor the first paging PDCCH or the second paging PDCCH based on whether the wireless device is a RedCap type or a non-RedCap type. Configuration of separated PEI with separated paging, based on example embodiment ofFIG.33D, may improve power consumption of a RedCap UE for monitoring PEI and PO. In existing technologies, a first initial BWP of a cell may be configured for a RedCap wireless device for paging (e.g., paging search space, paging occasion, etc.) and RACH procedure, separately from a second initial BWP, which may be used for non-RedCap wireless device, of the cell. In existing technologies, PEI (associated with PEI search space, PEI MO etc.), different from paging and/or RACH procedure, may be configured only on the second initial BWP, of the cell, for non-RedCap wireless device. PEI and paging may be implemented based on example embodiments above with respect toFIG.29A,FIG.29Band/orFIG.30. However, regarding PEI, by implementing existing technologies, a wireless device may not be able to determine whether PEI is separately transmitted on different initial BWPs of the cell. In an example, by implementing existing technologies, a RedCap wireless device may determine PEI (e.g., search space, PEI occasion, etc.) is configured on the second initial BWP of the cell, in which case, the RedCap wireless device may be required to monitor the PEI on the second initial BWP and then switch to the first initial BWP for receiving the paging DCI in response to receiving the PEI on the second initial BWP. Existing technologies may result in unnecessary power consumption for the RedCap wireless device for receiving a paging message. In an example, by implementing existing technologies, a RedCap wireless device may determine PEI is configured on both the initial BWP and the second initial BWP of the cell, in which case, the RedCap wireless device and a non-RedCap wireless device may monitor (automatically) the PEI on both initial BWPs for receiving the PEI. Existing technologies may increase power consumption of a wireless device. In an example, by implementing existing technologies, a RedCap wireless device may determine PEI and paging are configured on both the first initial BWP and the second initial BWP of the cell, e.g., without differentiation between RedCap and non-Redcap, in which case, the Redcap wireless device may monitor paging PDCCH on both the first initial BWP and the second initial BWP in response to receiving a PEI. Existing technologies may increase power consumption of a wireless device. There is a need to reduce power consumption for PEI and paging reception when multiple initial BWPs are configured on a cell for RedCap wireless devices and non-RedCap wireless devices. Example embodiments ofFIG.32,FIG.33A,FIG.33B,FIG.33C, and/orFIG.33Dmay be extended to improve power consumption of a RedCap UE for paging, when initial BWP of a cell is configured for paging. FIG.34Ashows an example embodiment of PEI configurations (and/or paging configurations) for a RedCap type and a non-RedCap type on a same initial DL BWP of a cell (e.g., PCell, or PSCell). In an example embodiment, the base station may transmit RRC message (e.g., MIB, SIB1, etc.) comprising first PEI configuration (and/or paging configurations) for a RedCap type and second PEI configuration (and/or paging configurations) for a non-RedCap type on a same initial DL BWP. The SIB1 message may comprise a DownlinkConfigCommonSIB IE. The DownlinkConfigCommonSIB IE may comprise two PCCH-Config IEs. The first PEI configuration (and/or paging configurations) for a RedCap type may be comprised in a first PCCH configuration (e.g., 1st PCCH-Config IE). The second PEI configuration (and/or paging configurations) for a non-RedCap type may be comprised in a second PCCH configuration (e.g., 2nd PCCH-Config IE). 1st PCCH-Config IE and 2nd PCCH-Config IE may be comprised in SIB1 message. PEI-RNTI (configured or predefined) for the first PEI configuration may be different from PEI-RNTI (configured or predefined) for the second PEI. The base station may indicate that the 1st PCCH-Config IE is present based on indication parameters of the MIB. The base station may indicate that the 1st PCCH-Config IE is present based on one or more bit fields (e.g., a spare bit), of the MIB message, being set to a predefined value. FIG.34Bshows an example embodiment of PEI configurations (and/or paging configurations) for a RedCap type and a non-RedCap type on different initial DL BWPs of a cell (e.g., PCell, or PSCell). In an example embodiment, the base station may transmit RRC message (e.g., MIB, SIB1, etc.) comprising first PEI configuration (and/or paging configurations) for a RedCap type and second PEI configuration (and/or paging configurations) for a non-RedCap type on different initial DL BWPs of the cell. In an example, the SIB1 message may comprise two DownlinkConfigCommonSIB IEs. A first DownlinkConfigCommonSIB IE, of the two DownlinkConfigCommonSIB IEs, may indicate a first initial DL BWP for the RedCap type. In an example, on the first initial DL BWP of the cell, the first DownlinkConfigCommonSIB IE may further indicate a first PCCH-Config IE for the RedCap type. The first PCCH-Config IE may comprise the first PEI configuration for the RedCap type. In an example, a second DownlinkConfigCommonSIB IE, of the two DownlinkConfigCommonSIB IEs, may indicate a second initial DL BWP for the non-RedCap type. In an example, on the second initial DL BWP of the cell, the second DownlinkConfigCommonSIB IE may further indicate a second PCCH-Config IE for the non-RedCap type. The second PCCH-Config IE may comprise the second PEI configuration for the non-RedCap type. In an example, the first initial BWP for the RedCap type wireless device may be smaller than the second initial BWP for the non-RedCap type wireless device. In an example, PEI-RNTI (configured or predefined) for the first PEI configuration may be same from PEI-RNTI (configured or predefined) for the second PEI configuration when the first PEI configuration and the second PEI configuration are on different initial DL BWPs. In an example, the base station may indicate that the DownlinkConfigCommonSIB dedicated for the RedCap type is present based on indication parameters of the MIB. The base station may indicate that the DownlinkConfigCommonSIB dedicated for the RedCap type is present based on one or more bit fields (e.g., a spare bit), of the MIB message, being set to a predefined value. In an example, in response to a wireless device being of the RedCap type, the wireless device may determine to use the first initial DL BWP for receiving a PEI and a corresponding paging DCI and paging message. In response to a wireless device being of the non-RedCap type, the wireless device may determine to use the second initial DL BWP for receiving a PEI and a corresponding paging DCI and paging message. In an example, a non-RedCap wireless device may not switch to the first initial DL BWP for receiving a PEI and/or a paging DCI/message. A RedCap wireless device may not switch to the second initial DL BWP for receiving a PEI and/or a paging DCI/message. In the example embodiment, a wireless device may receive message indicating a first initial BWP of a cell comprising BWPs and a second initial BWP of the cell, wherein the first initial BWP is associated with a first wireless device type and the second initial BWP is associated with a second wireless device type. The wireless device may determine one of the first initial BWP and the second initial BWP based on a type of the wireless device, wherein the type is one of the first wireless device type and the second wireless device type. The wireless device may receive, via the determined initial BWP, both a PEI based on monitoring a PEI search space and a DCI scheduling a paging message in response to the PEI (e.g., indicating to monitor a paging PDCCH). In the example embodiment, a wireless device may receive messages indicating configuration parameters of a PEI search space, a first initial BWP of a cell comprising BWPs and a second initial BWP of the cell, wherein the first initial BWP is associated with a first wireless device type and the second initial BWP is associated with a second wireless device type. The wireless device may determine one of the first initial BWP and the second initial BWP based on a type of the wireless device, wherein the type is one of the first wireless device type and the second wireless device type. The wireless device may, based on the type of the wireless device and via the determined initial BWP, receive a PEI based on monitoring the PEI search space according to the configuration parameters and receive, in response to the PEI, a DCI scheduling a paging message. By implementing the example embodiments, based on a base station configuring PEI and paging on a same initial BWP and configuring different initial BWPs for different types (RedCap, non-RedCap, etc.) of wireless devices, a wireless device may stick to (e.g., without switching to another initial DL BWP) a same initial DL BWP for receiving a PEI and/or receiving a paging DCI scheduling a paging message for the wireless device in response to the PEI indicating to monitor a paging PDCCH. Example embodiments may allow the base station to transmit different PEIs on different initial DL BWPs for different types of wireless devices, without requesting the wireless devices to switch DL BWPs for receiving PEI and/or paging DCI/paging message. Example embodiments may increase PEI transmission overhead on different initial BWPs. With the increased PEI transmission overhead, example embodiments may reduce power consumption for RedCap wireless devices for receiving a paging message, given that the RedCap wireless devices are more power limited than non-RedCap wireless devices or the base station. Example embodiments ofFIG.30,FIG.32,FIG.33A,FIG.33B,FIG.33C,FIG.33D,FIG.34Aand/orFIG.34Bmay be extended to improve power consumption of a RedCap UE for paging. FIG.35shows an example embodiment of configuration of gap between a PEI and a PO for a RedCap type and a non-RedCap type. In an example, a base station may transmit (not shown inFIG.35) RRC message (e.g., MIB, SIB1, etc.) comprising first PEI configuration (and/or paging configurations) for a RedCap type and second PEI configuration (and/or paging configurations) for a non-RedCap type. The first PEI (and/or paging) configuration and the second PEI (and/or paging) configuration may be implemented based on example embodiments described above with respect toFIG.30,FIG.32,FIG.33A,FIG.33B,FIG.33C,FIG.33D,FIG.34Aand/orFIG.34B. In an example, a PEI configuration (the first PEI or the second PEI) may further indicate a gap between a PEI and a corresponding PO. The gap may be a number of slots (or symbols) between the last symbol of the last PEI PDCCH monitoring occasion and a first symbol of the starting paging PDCCH monitoring occasion. In an example, the base station may configure a first gap, for a RedCap type, between a PEI and a corresponding PO, in the first PEI configuration. The base station may configure a second gap, for a non-RedCap type, between a PEI and a corresponding PO, in the second PEI configuration. In an example, the first gap may be greater than the second gap, e.g., due to limited processing capability of the RedCap type. In an example, as shown inFIG.35, a wireless device (e.g., UE1 with RedCap, or UE2 with non-RedCap) may warm up for preparing to monitor a PEI. The wireless device may warm up based on example embodiments described above withFIG.28Aand/orFIG.28B. The wireless device may perform synchronization based on SSB(s). The wireless device may monitor the PEI based on the PEI configuration (e.g., the first PEI configuration or the second PEI configuration). The wireless device may monitor the PEI based on example embodiments described above with respect toFIG.30,FIG.32,FIG.33A,FIG.33B,FIG.33C,FIG.33D,FIG.34Aand/orFIG.34B. In response to receiving a PEI at a first slot, the wireless device may determine whether to apply the first gap or the second gap, for monitoring the PO, based on whether the wireless device is a RedCap type or a non-RedCap type. In response to the wireless device being the RedCap type (e.g., UE1 with RedCap), the wireless device may apply the first gap for monitoring the PO. The wireless device may monitor the PO starting at a second slot, wherein the time offset between the first slot and the second slot may be equal or greater than the first gap. In response to the wireless device being the non-RedCap type (e.g., UE2 with non-RedCap), the wireless device may apply the second gap for monitoring the PO. The wireless device may monitor the PO starting at a third slot, wherein the time offset between the first slot and the third slot may be equal or greater than the second gap. Based on example embodiments ofFIG.35, a base station may flexibly configure different gaps between a PEI and a PO for different wireless device types (e.g., RedCap type, non-RedCap, etc.), e.g., based on different capabilities of the different wireless device types. Example embodiments may reduce possibility of miss-detecting a paging DCI after receiving a PEI for a RedCap wireless device. Example embodiments ofFIG.30,FIG.32,FIG.33A,FIG.33B,FIG.33C,FIG.33D,FIG.34A,FIG.34Band/orFIG.35may be extended to improve power consumption of a RedCap UE for paging. FIG.36shows an example embodiment of PEI detection for a RedCap type and a non-RedCap type. In an example, a base station may transmit (not shown inFIG.36) RRC message (e.g., MIB, SIB1, etc.) comprising first PEI configuration (and/or paging configurations) for a RedCap type and second PEI configuration (and/or paging configurations) for a non-RedCap type. The first PEI (and/or paging) configuration and the second PEI (and/or paging) configuration may be implemented based on example embodiments described above with respect toFIG.30,FIG.32,FIG.33A,FIG.33B,FIG.33C,FIG.33D,FIG.34A,FIG.34B, and/orFIG.35. In an example, the first PEI configuration may comprise a first parameter indicating whether the RedCap wireless device may skip monitoring a PO in response to not detecting a PEI. The second PEI configuration may comprise a second parameter indicating whether the non-RedCap wireless device may skip monitoring a PO in response to not detecting a PEI. The first parameter may be separately and/or independently configured from the second parameter. Configuring the wireless device's behavior of not detecting a PEI may align the base station with the wireless device regarding whether to monitor a PO in response to not detecting a PEI. In an example, the base station may, based on a first value of the first parameter, indicate that the RedCap wireless device may skip monitoring a PO in response to not detecting a PEI (or any PEI before the corresponding PO), in the first PEI configuration. The base station may, based on a second value of the second parameter, indicate that the non-RedCap wireless device may monitor a PO in response to not detecting a PEI (or any PEI before the corresponding PO), in the second PEI configuration. Configuring different behaviors, when not detecting a PEI, for a RedCap type and a non-RedCap type, may improve power consumption and/or paging latency for a wireless device. In an example embodiment, as shown inFIG.36, a wireless device (e.g., UE1 with RedCap, or UE2 with non-RedCap) may warm up for preparing to monitor a PEI. The wireless device may warm up based on example embodiments described above withFIG.28Aand/orFIG.28B. The wireless device may perform synchronization based on SSB(s). The wireless device may monitor the PEI based on the PEI configuration (e.g., the first PEI configuration or the second PEI configuration). The wireless device may monitor the PEI based on example embodiments described above with respect toFIG.30,FIG.32,FIG.33A,FIG.33B,FIG.33C,FIG.33D,FIG.34A,FIG.34B, and/orFIG.35. In an example embodiment, in response to not detecting the PEI, the wireless device may determine whether to skip monitoring a PO (or all POs in a PF) or monitor the PO based on whether the wireless device is a RedCap type or a non-RedCap type and based on RRC message. In response to the wireless device being a RedCap type (e.g., UE 1 with RedCap inFIG.36), the wireless device may skip monitoring the PO(s) based on the RRC message indicating that a RedCap type wireless device shall skip monitoring the PO(s) in response to not detecting the PEI. In response to the wireless device being a non-RedCap type (e.g., UE 2 with non-RedCap inFIG.36), the wireless device may monitor the PO(s) based on the RRC message indicating that a non-RedCap type wireless device shall monitor the PO in response to not detecting the PEI. In an example embodiment, the base station may not configure the first parameter for a RedCap wireless device type. The first parameter may be absent in the RRC message. A RedCap wireless device may determine a default behavior, regarding monitoring PO, in response to not detecting a PEI, e.g., when the first parameter is absent in the RRC message. In an example embodiment, the RedCap wireless device may determine a first default behavior comprising skipping monitoring a PO (or any PO in a PF) in response to not detecting a PEI. In an example embodiment, the RedCap wireless device may determine a second default behavior comprising monitoring a PO (or any PO in a PF) in response to not detecting a PEI. The RedCap wireless device may determine to apply the first default behavior or the second default behavior by a predefined rule, or by configuration of the base station. In an example embodiment, the base station may not configure the second parameter for a non-RedCap wireless device type. The second parameter may be absent in the RRC message. A non-RedCap wireless device may determine a default behavior, regarding monitoring PO, in response to not detecting a PEI, e.g., when the second parameter is absent in the RRC message. In an example embodiment, the non-RedCap wireless device may determine a default behavior comprising skipping monitoring a PO (or any PO in a PF) in response to not detecting a PEI. In an example embodiment, the non-RedCap wireless device may determine a default behavior comprising monitoring a PO (or any PO in a PF) in response to not detecting a PEI. The default behavior of the non-RedCap wireless device may be same as or different from the default behavior of the RedCap wireless device. The non-RedCap wireless device may determine to apply the first default behavior or the second default behavior by a predefined rule, or by configuration of the base station. Based on the example embodiment ofFIG.36, a RedCap wireless device, by skipping monitoring a PO (or any PO in a PF) in response to not detecting a PEI, may reduce power consumption for paging, e.g., when the RedCap wireless device is power limited and/or is uplink data centric. Based on the example embodiment, a non-RedCap wireless device, by monitoring a PO (in a PF) in response to not detecting a PEI, may reduce latency of paging message delivery. In an example embodiment, a base station may transmit, and/or a wireless device may receive, message indicating first parameters of a first PEI associated with a first wireless device type and second parameters of a second PEI associated with a second wireless device type. In response to the wireless device being the first wireless device type and based on the first parameters, the wireless device may monitor a first PDCCH for the first PEI. The wireless device may monitor, based on the first PEI, a first PO for a paging message. In response to the wireless device being the second wireless device type and based on the second parameters, the wireless device may monitor a second PDCCH for the second PEI. The wireless device, based on the second PEI, monitors a second PO for a paging message. The wireless device may receive the paging message comprising an identification of the wireless device. In an example embodiment, the first parameters may indicate that the first PEI is configured with the wireless device in a RRC IDLE state or a RRC INACTIVE state. The message may comprise at least one of a MIB message and a SIB1 message. In an example embodiment, the first parameters may indicate at least one of: a first control resource set for the first PDCCH associated with the first PEI, one or more first search spaces for the first PDCCH and a first time offset between the first PEI and the first PO. In an example embodiment, the first control resource set may be associated with a control resource set index identifying the first control resource set. The first control resource set may be associated with at least one of: a frequency resource indication, a time domain duration indication and an indication of CCE to REG mapping type. In an example embodiment, each of the one or more first search spaces may be associated with at least one of: a search space index identifying the search space, a control resource set index identifying a control resource set associated with the search space, one or more time domain resource allocation parameters of the search space, a search space type and a number of aggregation levels for the search space. The one or more time domain resource allocation parameters may comprise at least one of: a periodicity value of the first PDCCH, a slot offset of a starting point of the first PDCCH and a number of symbols of the first PDCCH. In an example embodiment, the second parameters may comprise at least one of: a second control resource set for the second PDCCH associated with the second PEI, one or more second search spaces for the second PDCCH and a second time offset between the second PEI and the second PO. In an example embodiment, the first control resource set may be same as the second control resource set. The one or more first search spaces may be same as the one or more second search spaces. The first time offset may be same as the second time offset. In an example embodiment, the message may further comprise first parameters of the first PO associated with a first wireless device type and second parameters of the second PO associated with a second wireless device type. In an example embodiment, the first parameters may comprise at least one of: a paging cycle, a number of paging frames in the paging cycle, a paging frame offset in the paging cycle, a number of total POs comprising the first PO in a paging frame, and a first PDCCH monitoring occasion for the first PO. In an example embodiment, the first parameters of the first PO may comprise at least one of: a first control resource set for a second PDCCH for monitoring the first PO and one or more first search spaces for the second PDCCH. In an example embodiment, the second parameters of the second PO may comprise at least one of: a second control resource set for a second PDCCH for monitoring the second PO and one or more second search spaces for the second PDCCH. In an example embodiment, the first control resource set may be same as the second control resource set. The first control resources set and the second control resource set being same comprises the two control resource sets being with same configuration parameters. The one or more first search spaces may be same as the one or more second search spaces. The one or more first search spaces and the one or more second search spaces being same comprises the two search spaces being with same configuration parameters. In an example embodiment, the first parameters may indicate that the first PDCCH is transmitted in a first initial bandwidth part (BWP), of a cell, associated with the first wireless device type. In an example embodiment, the second parameters may indicate that the second PDCCH is transmitted in a second initial BWP, of the cell, associated with the second wireless device type. In an example, the first initial BWP may be different from the second initial BWP. In an example, the first initial BWP may be same as the second initial BWP. In an example embodiment, the wireless device may monitor the first PDCCH (e.g., on the first initial BWP of the cell) with a first RNTI associated with the first PEI (PEI-RNTI) in response to the wireless device being the first wireless device type. In an example, the first PEI-RNTI may be predefined as a fixed value or may be configured in the RRC message. The first PEI-RNTI may be same as a P-RNTI used for receiving a DCI scheduling a paging message. The first PEI-RNTI may be different from the P-RNTI. P-RNTI may be predefined with different values for different wireless device types (e.g., a RedCap type, a non-RedCap type). P-RNTI may be predefined with a same value for different wireless device types (e.g., a RedCap type, a non-RedCap type). In an example embodiment, the wireless device may monitor the second PDCCH (e.g., in the second initial BWP of the cell) with a second PEI-RNTI in response to the wireless device being the second wireless device type. In an example, the second PEI-RNTI may be predefined as a fixed value or may be configured in the RRC message. The second PEI-RNTI may be different from the first PEI-RNTI or may be same as the first PEI-RNTI. The second PEI-RNTI may be same as a P-RNTI used for receiving a DCI scheduling a paging message. The second PEI-RNTI may be different from the P-RNTI. In an example embodiment, the wireless device, in response to belonging to the first wireless device type, may be configured with a first number of reception antenna. The wireless device, in response to belonging to the second wireless device type, may be configured with a second number of reception antenna, wherein the second number is greater than the first number. In an example embodiment, the wireless device, in response to belonging to the first wireless device type, may be capable of operating within a first bandwidth. The wireless device, in response to belonging to the second wireless device type, may be capable of operating within a second bandwidth, wherein the second bandwidth is greater than the first bandwidth. In an example embodiment, the wireless device may monitor the first PO (e.g., on the first initial BWP) in response to receiving the first PEI indicating that the wireless device monitors the first PO. Monitoring the first PO may comprise monitoring a second PDCCH for a DCI with a paging RNTI. The paging RNTI may be different from the first PEI-RNTI or the second PEI-RNTI. The DCI may indicate scheduling information of the paging message. In an example embodiment, the wireless device may monitor the second PO (e.g., on the second initial BWP) in response to receiving the second PEI indicating that the wireless device monitors the second PO. In an example embodiment, a base station may transmit a SIB message comprising first parameters of a first PEI associated with a first wireless device type and second parameters of a second PEI associated with a second wireless device type. The base station may transmit, based on the first parameters, the first PEI via a first PDCCH for a first wireless device with the first wireless device type. The base station may transmit, in a first PO, a first DCI to the first wireless device based on the transmitting the first PEI. The base station may transmit, based on the first DCI, a first paging message to the first wireless device. The base station may transmit, based on the second parameters, the second PEI via a second PDCCH for a second wireless device with the second wireless device type. The base station may transmit, in a second PO, a second DCI to the second wireless device based on the transmitting the second PEI. The base station may transmit, based on the second DCI, a second paging message to the second wireless device. In an example embodiment, a wireless device may receive, from a base station, message comprising parameters of a PO and a plurality of time offsets, each time offset being associated with a respective one of a plurality of wireless device types. Each time offset may indicate a time offset value between a PEI and the PO. The wireless device may monitor the PEI at a first slot occurring at a first time offset before a second slot. The first time offset may be determined, from the plurality of time offsets, based on the wireless device being a first wireless device type of the plurality of wireless device types. The second slot may be determined based on the parameters of the PO. The second slot may be determined based on an identifier of the wireless device. The wireless device may monitor, at the second slot, based on the PEI indicating to monitor the PO, the PO for receiving a downlink control information scheduling the paging message. The wireless device may receive, based on receiving the downlink control information, the paging message. In an example embodiment, a wireless device may receive message comprising parameters of a PEI and a PO, a first parameter associated with a first wireless device type and indicating to monitor the PO in response to not detecting the PEI, and a second parameter associated with a second wireless device type and indicating to skip monitoring the PO in response to not detecting the PEI. The wireless device may monitor a first PDCCH for receiving the PEI based on the parameters. The wireless device may monitor the PO for receiving a DCI scheduling the paging message based on not detecting the PEI and the wireless device being the first wireless device type. The wireless device may receive, based on receiving the downlink control information, the paging message. | 256,635 |
11943743 | DETAILED DESCRIPTION OF EMBODIMENTS Example embodiments of the present disclosure enable operation of communication network(s). Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems. More particularly, the embodiments of the technology disclosed herein may relate to radio access network(s) in multicarrier communication systems. The following Acronyms are used throughout the present disclosure: 3GPP 3rd Generation Partnership Project 5GC 5G Core Network ACK Acknowledgement AMF Access and Mobility Management Function ARQ Automatic Repeat Request AS Access Stratum ASIC Application-Specific Integrated Circuit BA Bandwidth Adaptation BCCH Broadcast Control Channel BCH Broadcast Channel BPSK Binary Phase Shift Keying BWP Bandwidth Part CA Carrier Aggregation CC Component Carrier CCCH Common Control CHannel CDMA Code Division Multiple Access CN Core Network CP Cyclic Prefix CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex C-RNTI Cell-Radio Network Temporary Identifier CS Configured Scheduling CSI Channel State Information CSI-RS Channel State Information-Reference Signal CQI Channel Quality Indicator CSS Common Search Space CU Central Unit DC Dual Connectivity DCCH Dedicated Control CHannel DCI Downlink Control Information DL Downlink DL-SCH Downlink Shared CHannel DM-RS DeModulation Reference Signal DRB Data Radio Bearer DRX Discontinuous Reception DTCH Dedicated Traffic CHannel DU Distributed Unit EPC Evolved Packet Core E-UTRA Evolved UMTS Terrestrial Radio Access E-UTRAN Evolved-Universal Terrestrial Radio Access Network FDD Frequency Division Duplex FPGA Field Programmable Gate Arrays F1-C F1-Control plane F1-U F1-User plane gNB next generation Node B HARQ Hybrid Automatic Repeat Request HDL Hardware Description Languages IE Information Element IP Internet Protocol LCID Logical Channel IDentifier LTE Long Term Evolution MAC Media Access Control MCG Master Cell Group MCS Modulation and Coding Scheme MeNB Master evolved Node B MIB Master Information Block MME Mobility Management Entity MN Master Node NACK Negative Acknowledgement NAS Non-Access Stratum NG CP Next Generation Control Plane NGC Next Generation Core NG-C NG-Control plane ng-eNB next generation evolved Node B NG-U NG-User plane NR New Radio NR MAC New Radio MAC NR PDCP New Radio PDCP NR PHY New Radio PHYsical NR RLC New Radio RLC NR RRC New Radio RRC NSSAI Network Slice Selection Assistance Information O&M Operation and Maintenance OFDM Orthogonal Frequency Division Multiplexing PBCH Physical Broadcast CHannel PCC Primary Component Carrier PCCH Paging Control CHannel PCell Primary Cell PCH Paging CHannel PDCCH Physical Downlink Control CHannel PDCP Packet Data Convergence Protocol PDSCH Physical Downlink Shared CHannel PDU Protocol Data Unit PHICH Physical HARQ Indicator CHannel PHY PHYsical PLMN Public Land Mobile Network PMI Precoding Matrix Indicator PRACH Physical Random Access CHannel PRB Physical Resource Block PSCell Primary Secondary Cell PSS Primary Synchronization Signal pTAG primary Timing Advance Group PT-RS Phase Tracking Reference Signal PUCCH Physical Uplink Control CHannel PUSCH Physical Uplink Shared CHannel QAM Quadrature Amplitude Modulation QFI Quality of Service Indicator QoS Quality of Service QPSK Quadrature Phase Shift Keying RA Random Access RACH Random Access CHannel RAN Radio Access Network RAT Radio Access Technology RA-RNTI Random Access-Radio Network Temporary Identifier RB Resource Blocks RBG Resource Block Groups RI Rank Indicator RLC Radio Link Control RRC Radio Resource Control RS Reference Signal RSRP Reference Signal Received Power SCC Secondary Component Carrier SCell Secondary Cell SCG Secondary Cell Group SC-FDMA Single Carrier-Frequency Division Multiple Access SDAP Service Data Adaptation Protocol SDU Service Data Unit SeNB Secondary evolved Node B SFN System Frame Number S-GW Serving GateWay SI System Information SIB System Information Block SMF Session Management Function SN Secondary Node SpCell Special Cell SRB Signaling Radio Bearer SRS Sounding Reference Signal SS Synchronization Signal SSS Secondary Synchronization Signal sTAG secondary Timing Advance Group TA Timing Advance TAG Timing Advance Group TAI Tracking Area Identifier TAT Time Alignment Timer TB Transport Block TC-RNTI Temporary Cell-Radio Network Temporary Identifier TDD Time Division Duplex TDMA Time Division Multiple Access TTI Transmission Time Interval UCI Uplink Control Information UE User Equipment UL Uplink UL-SCH Uplink Shared CHannel UPF User Plane Function UPGW User Plane Gateway VHDL VHSIC Hardware Description Language Xn-C Xn-Control plane Xn-U Xn-User plane Example embodiments of the disclosure may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed. Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement Quadrature Amplitude Modulation (QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions. FIG.1is an example Radio Access Network (RAN) architecture as per an aspect of an embodiment of the present disclosure. As illustrated in this example, a RAN node may be a next generation Node B (gNB) (e.g.120A,120B) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g.110A). In an example, a RAN node may be a next generation evolved Node B (ng-eNB) (e.g.124A,124B), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g.110B). The first wireless device may communicate with a gNB over a Uu interface. The second wireless device may communicate with an ng-eNB over a Uu interface. In this disclosure, wireless device110A and110B are structurally similar to wireless device110. Base stations120A and/or120B may be structurally similarly to base station120. Base station120may comprise at least one of a gNB (e.g.122A and/or122B), ng-eNB (e.g.124A and/or124B), and or the like. A gNB or an ng-eNB may host functions such as: radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at User Equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originated from the AMF), scheduling and transmission of system broadcast information (originated from the AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport level packet marking in the uplink, session management, support of network slicing, Quality of Service (QoS) flow management and mapping to data radio bearers, support of UEs in RRC_INACTIVE state, distribution function for Non-Access Stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA. In an example, one or more gNBs and/or one or more ng-eNBs may be interconnected with each other by means of Xn interface. A gNB or an ng-eNB may be connected by means of NG interfaces to 5G Core Network (5GC). In an example, 5GC may comprise one or more AMF/User Plan Function (UPF) functions (e.g.130A or130B). A gNB or an ng-eNB may be connected to a UPF by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g. non-guaranteed delivery) of user plane Protocol Data Units (PDUs) between a RAN node and the UPF. A gNB or an ng-eNB may be connected to an AMF by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, configuration transfer and/or warning message transmission, combinations thereof, and/or the like. In an example, a UPF may host functions such as anchor point for intra-/inter-Radio Access Technology (RAT) mobility (when applicable), external PDU session point of interconnect to data network, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, traffic usage reporting, uplink classifier to support routing traffic flows to a data network, branching point to support multi-homed PDU session, QoS handling for user plane, e.g. packet filtering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering and/or downlink data notification triggering. In an example, an AMF may host functions such as NAS signaling termination, NAS signaling security, Access Stratum (AS) security control, inter Core Network (CN) node signaling for mobility between 3rdGeneration Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, support of intra-system and inter-system mobility, access authentication, access authorization including check of roaming rights, mobility management control (subscription and policies), support of network slicing and/or Session Management Function (SMF) selection. FIG.2Ais an example user plane protocol stack, where Service Data Adaptation Protocol (SDAP) (e.g.211and221), Packet Data Convergence Protocol (PDCP) (e.g.212and222), Radio Link Control (RLC) (e.g.213and223) and Media Access Control (MAC) (e.g.214and224) sublayers and Physical (PHY) (e.g.215and225) layer may be terminated in wireless device (e.g.110) and gNB (e.g.120) on the network side. In an example, a PHY layer provides transport services to higher layers (e.g. MAC, RRC, etc.). In an example, services and functions of a MAC sublayer may comprise mapping between logical channels and transport channels, multiplexing/demultiplexing of MAC Service Data Units (SDUs) belonging to one or different logical channels into/from Transport Blocks (TBs) delivered to/from the PHY layer, scheduling information reporting, error correction through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization, and/or padding. A MAC entity may support one or multiple numerologies and/or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. In an example, an RLC sublayer may supports transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM) transmission modes. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. In an example, Automatic Repeat Request (ARQ) may operate on any of the numerologies and/or TTI durations the logical channel is configured with. In an example, services and functions of the PDCP layer for the user plane may comprise sequence numbering, header compression and decompression, transfer of user data, reordering and duplicate detection, PDCP PDU routing (e.g. in case of split bearers), retransmission of PDCP SDUs, ciphering, deciphering and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, and/or duplication of PDCP PDUs. In an example, services and functions of SDAP may comprise mapping between a QoS flow and a data radio bearer. In an example, services and functions of SDAP may comprise mapping Quality of Service Indicator (QFI) in DL and UL packets. In an example, a protocol entity of SDAP may be configured for an individual PDU session. FIG.2Bis an example control plane protocol stack where PDCP (e.g.233and242), RLC (e.g.234and243) and MAC (e.g.235and244) sublayers and PHY (e.g.236and245) layer may be terminated in wireless device (e.g.110) and gNB (e.g.120) on a network side and perform service and functions described above. In an example, RRC (e.g.232and241) may be terminated in a wireless device and a gNB on a network side. In an example, services and functions of RRC may comprise broadcast of system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between the UE and RAN, security functions including key management, establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of the reporting, detection of and recovery from radio link failure, and/or NAS message transfer to/from NAS from/to a UE. In an example, NAS control protocol (e.g.231and251) may be terminated in the wireless device and AMF (e.g.130) on a network side and may perform functions such as authentication, mobility management between a UE and a AMF for 3GPP access and non-3GPP access, and session management between a UE and a SMF for 3GPP access and non-3GPP access. In an example, a base station may configure a plurality of logical channels for a wireless device. A logical channel in the plurality of logical channels may correspond to a radio bearer and the radio bearer may be associated with a QoS requirement. In an example, a base station may configure a logical channel to be mapped to one or more TTIs/numerologies in a plurality of TTIs/numerologies. The wireless device may receive a Downlink Control Information (DCI) via Physical Downlink Control CHannel (PDCCH) indicating an uplink grant. In an example, the uplink grant may be for a first TTI/numerology and may indicate uplink resources for transmission of a transport block. The base station may configure each logical channel in the plurality of logical channels with one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. The one or more parameters may comprise priority, prioritized bit rate, etc. A logical channel in the plurality of logical channels may correspond to one or more buffers comprising data associated with the logical channel. The logical channel prioritization procedure may allocate the uplink resources to one or more first logical channels in the plurality of logical channels and/or one or more MAC Control Elements (CEs). The one or more first logical channels may be mapped to the first TTI/numerology. The MAC layer at the wireless device may multiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel) in a MAC PDU (e.g., transport block). In an example, the MAC PDU may comprise a MAC header comprising a plurality of MAC sub-headers. A MAC sub-header in the plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a Logical Channel IDentifier (LCID). In an example, LCID for a logical channel or a MAC CE may be fixed/pre-configured. In an example, LCID for a logical channel or MAC CE may be configured for the wireless device by the base station. The MAC sub-header corresponding to a MAC CE or a MAC SDU may comprise LCID associated with the MAC CE or the MAC SDU. In an example, a base station may activate and/or deactivate and/or impact one or more processes (e.g., set values of one or more parameters of the one or more processes or start and/or stop one or more timers of the one or more processes) at the wireless device by employing one or more MAC commands. The one or more MAC commands may comprise one or more MAC control elements. In an example, the one or more processes may comprise activation and/or deactivation of PDCP packet duplication for one or more radio bearers. The base station may transmit a MAC CE comprising one or more fields, the values of the fields indicating activation and/or deactivation of PDCP duplication for the one or more radio bearers. In an example, the one or more processes may comprise Channel State Information (CSI) transmission of on one or more cells. The base station may transmit one or more MAC CEs indicating activation and/or deactivation of the CSI transmission on the one or more cells. In an example, the one or more processes may comprise activation or deactivation of one or more secondary cells. In an example, the base station may transmit a MA CE indicating activation or deactivation of one or more secondary cells. In an example, the base station may transmit one or more MAC CEs indicating starting and/or stopping one or more Discontinuous Reception (DRX) timers at the wireless device. In an example, the base station may transmit one or more MAC CEs indicating one or more timing advance values for one or more Timing Advance Groups (TAGs). FIG.3is a block diagram of base stations (base station1,120A, and base station2,120B) and a wireless device110. A wireless device may be called an UE. A base station may be called a NB, eNB, gNB, and/or ng-eNB. In an example, a wireless device and/or a base station may act as a relay node. The base station1,120A, may comprise at least one communication interface320A (e.g. a wireless modem, an antenna, a wired modem, and/or the like), at least one processor321A, and at least one set of program code instructions323A stored in non-transitory memory322A and executable by the at least one processor321A. The base station2,120B, may comprise at least one communication interface320B, at least one processor321B, and at least one set of program code instructions323B stored in non-transitory memory322B and executable by the at least one processor321B. A base station may comprise many sectors for example: 1, 2, 3, 4, or 6 sectors. A base station may comprise many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At Radio Resource Control (RRC) connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g. Tracking Area Identifier (TAI)). At RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, a carrier corresponding to the PCell may be a DL Primary Component Carrier (PCC), while in the uplink, a carrier may be an UL PCC. Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with a PCell a set of serving cells. In a downlink, a carrier corresponding to an SCell may be a downlink secondary component carrier (DL SCC), while in an uplink, a carrier may be an uplink secondary component carrier (UL SCC). An S Cell may or may not have an uplink carrier. A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to one cell. The cell ID or cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used). In the disclosure, a cell ID may be equally referred to a carrier ID, and a cell index may be referred to a carrier index. In an implementation, a physical cell ID or a cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted on a downlink carrier. A cell index may be determined using RRC messages. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same concept may apply to, for example, carrier activation. When the disclosure indicates that a first carrier is activated, the specification may equally mean that a cell comprising the first carrier is activated. A base station may transmit to a wireless device one or more messages (e.g. RRC messages) comprising a plurality of configuration parameters for one or more cells. One or more cells may comprise at least one primary cell and at least one secondary cell. In an example, an RRC message may be broadcasted or unicasted to the wireless device. In an example, configuration parameters may comprise common parameters and dedicated parameters. Services and/or functions of an RRC sublayer may comprise at least one of: broadcast of system information related to AS and NAS; paging initiated by 5GC and/or NG-RAN; establishment, maintenance, and/or release of an RRC connection between a wireless device and NG-RAN, which may comprise at least one of addition, modification and release of carrier aggregation; or addition, modification, and/or release of dual connectivity in NR or between E-UTRA and NR. Services and/or functions of an RRC sublayer may further comprise at least one of security functions comprising key management; establishment, configuration, maintenance, and/or release of Signaling Radio Bearers (SRBs) and/or Data Radio Bearers (DRBs); mobility functions which may comprise at least one of a handover (e.g. intra NR mobility or inter-RAT mobility) and a context transfer; or a wireless device cell selection and reselection and control of cell selection and reselection. Services and/or functions of an RRC sublayer may further comprise at least one of QoS management functions; a wireless device measurement configuration/reporting; detection of and/or recovery from radio link failure; or NAS message transfer to/from a core network entity (e.g. AMF, Mobility Management Entity (MME)) from/to the wireless device. An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state and/or an RRC_Connected state for a wireless device. In an RRC_Idle state, a wireless device may perform at least one of: Public Land Mobile Network (PLMN) selection; receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a paging for mobile terminated data initiated by 5GC; paging for mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In an RRC_Inactive state, a wireless device may perform at least one of: receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-based notification area (RNA) managed by NG-RAN; or DRX for RAN/CN paging configured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (both C/U-planes) for the wireless device; and/or store a UE AS context for the wireless device. In an RRC_Connected state of a wireless device, a base station (e.g. NG-RAN) may perform at least one of: establishment of 5GC-NG-RAN connection (both C/U-planes) for the wireless device; storing a UE AS context for the wireless device; transmit/receive of unicast data to/from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In an RRC_Connected state of a wireless device, an NG-RAN may know a cell that the wireless device belongs to. System information (SI) may be divided into minimum SI and other SI. The minimum SI may be periodically broadcast. The minimum SI may comprise basic information required for initial access and information for acquiring any other SI broadcast periodically or provisioned on-demand, i.e. scheduling information. The other SI may either be broadcast, or be provisioned in a dedicated manner, either triggered by a network or upon request from a wireless device. A minimum SI may be transmitted via two different downlink channels using different messages (e.g. MasterInformationBlock and SystemInformationBlockType1). Another SI may be transmitted via SystemInformationBlockType2. For a wireless device in an RRC_Connected state, dedicated RRC signaling may be employed for the request and delivery of the other SI. For the wireless device in the RRC_Idle state and/or the RRC_Inactive state, the request may trigger a random-access procedure. A wireless device may report its radio access capability information which may be static. A base station may request what capabilities for a wireless device to report based on band information. When allowed by a network, a temporary capability restriction request may be sent by the wireless device to signal the limited availability of some capabilities (e.g. due to hardware sharing, interference or overheating) to the base station. The base station may confirm or reject the request. The temporary capability restriction may be transparent to 5GC (e.g., static capabilities may be stored in 5GC). When CA is configured, a wireless device may have an RRC connection with a network. At RRC connection establishment/re-establishment/handover procedure, one serving cell may provide NAS mobility information, and at RRC connection re-establishment/handover, one serving cell may provide a security input. This cell may be referred to as the PCell. Depending on the capabilities of the wireless device, SCells may be configured to form together with the PCell a set of serving cells. The configured set of serving cells for the wireless device may comprise one PCell and one or more SCells. The reconfiguration, addition and removal of SCells may be performed by RRC. At intra-NR handover, RRC may also add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signaling may be employed to send all required system information of the SCell i.e. while in connected mode, wireless devices may not need to acquire broadcasted system information directly from the SCells. The purpose of an RRC connection reconfiguration procedure may be to modify an RRC connection, (e.g. to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS dedicated information may be transferred from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g. RBs, MAC main configuration and physical channel configuration) comprising any associated dedicated NAS information and security configuration. If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the wireless device may perform SCell additions or modification. An RRC connection establishment (or reestablishment, resume) procedure may be to establish (or reestablish, resume) an RRC connection. An RRC connection establishment procedure may comprise SRB1 establishment. The RRC connection establishment procedure may be used to transfer the initial NAS dedicated information/message from a wireless device to E-UTRAN. The RRCConnectionReestablishment message may be used to re-establish SRB1. A measurement report procedure may be to transfer measurement results from a wireless device to NG-RAN. The wireless device may initiate a measurement report procedure after successful security activation. A measurement report message may be employed to transmit measurement results. The wireless device110may comprise at least one communication interface310(e.g. a wireless modem, an antenna, and/or the like), at least one processor314, and at least one set of program code instructions316stored in non-transitory memory315and executable by the at least one processor314. The wireless device110may further comprise at least one of at least one speaker/microphone311, at least one keypad312, at least one display/touchpad313, at least one power source317, at least one global positioning system (GPS) chipset318, and other peripherals319. The processor314of the wireless device110, the processor321A of the base station1120A, and/or the processor321B of the base station2120B may comprise at least one of a general-purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, and the like. The processor314of the wireless device110, the processor321A in base station1120A, and/or the processor321B in base station2120B may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device110, the base station1120A and/or the base station2120B to operate in a wireless environment. The processor314of the wireless device110may be connected to the speaker/microphone311, the keypad312, and/or the display/touchpad313. The processor314may receive user input data from and/or provide user output data to the speaker/microphone311, the keypad312, and/or the display/touchpad313. The processor314in the wireless device110may receive power from the power source317and/or may be configured to distribute the power to the other components in the wireless device110. The power source317may comprise at least one of one or more dry cell batteries, solar cells, fuel cells, and the like. The processor314may be connected to the GPS chipset318. The GPS chipset318may be configured to provide geographic location information of the wireless device110. The processor314of the wireless device110may further be connected to other peripherals319, which may comprise one or more software and/or hardware modules that provide additional features and/or functionalities. For example, the peripherals319may comprise at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, and the like. The communication interface320A of the base station1,120A, and/or the communication interface320B of the base station2,120B, may be configured to communicate with the communication interface310of the wireless device110via a wireless link330A and/or a wireless link330B respectively. In an example, the communication interface320A of the base station1,120A, may communicate with the communication interface320B of the base station2and other RAN and core network nodes. The wireless link330A and/or the wireless link330B may comprise at least one of a bi-directional link and/or a directional link. The communication interface310of the wireless device110may be configured to communicate with the communication interface320A of the base station1120A and/or with the communication interface320B of the base station2120B. The base station1120A and the wireless device110and/or the base station2120B and the wireless device110may be configured to send and receive transport blocks via the wireless link330A and/or via the wireless link330B, respectively. The wireless link330A and/or the wireless link330B may employ at least one frequency carrier. According to some of various aspects of embodiments, transceiver(s) may be employed. A transceiver may be a device that comprises both a transmitter and a receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Example embodiments for radio technology implemented in the communication interface310,320A,320B and the wireless link330A,330B are illustrated inFIG.4A,FIG.4B,FIG.4C,FIG.4D,FIG.6,FIG.7A,FIG.7B,FIG.8, and associated text. In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) may comprise one or more communication interfaces, one or more processors, and memory storing instructions. A node (e.g. wireless device, base station, AMF, SMF, UPF, servers, switches, antennas, and/or the like) may comprise one or more processors, and memory storing instructions that when executed by the one or more processors causes the node to perform certain processes and/or functions. Example embodiments may enable operation of single-carrier and/or multi-carrier communications. Other example embodiments may comprise a non-transitory tangible computer readable media comprising instructions executable by one or more processors to cause operation of single-carrier and/or multi-carrier communications. Yet other example embodiments may comprise an article of manufacture that comprises a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a node to enable operation of single-carrier and/or multi-carrier communications. The node may include processors, memory, interfaces, and/or the like. An interface may comprise at least one of a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may comprise connectors, wires, electronic devices such as drivers, amplifiers, and/or the like. The software interface may comprise code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. The firmware interface may comprise a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like. FIG.4A,FIG.4B,FIG.4CandFIG.4Dare example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present disclosure.FIG.4Ashows an example uplink transmitter for at least one physical channel A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated byFIG.4A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. An example structure for modulation and up-conversion to the carrier frequency of the complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or the complex-valued Physical Random Access CHannel (PRACH) baseband signal is shown inFIG.4B. Filtering may be employed prior to transmission. An example structure for downlink transmissions is shown inFIG.4C. The baseband signal representing a downlink physical channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and/or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. In an example, a gNB may transmit a first symbol and a second symbol on an antenna port, to a wireless device. The wireless device may infer the channel (e.g., fading gain, multipath delay, etc.) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. In an example, a first antenna port and a second antenna port may be quasi co-located if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: delay spread; doppler spread; doppler shift; average gain; average delay; and/or spatial Receiving (Rx) parameters. An example modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for an antenna port is shown inFIG.4D. Filtering may be employed prior to transmission. FIG.5Ais a diagram of an example uplink channel mapping and example uplink physical signals.FIG.5Bis a diagram of an example downlink channel mapping and a downlink physical signals. In an example, a physical layer may provide one or more information transfer services to a MAC and/or one or more higher layers. For example, the physical layer may provide the one or more information transfer services to the MAC via one or more transport channels. An information transfer service may indicate how and with what characteristics data are transferred over the radio interface. In an example embodiment, a radio network may comprise one or more downlink and/or uplink transport channels. For example, a diagram inFIG.5Ashows example uplink transport channels comprising Uplink-Shared CHannel (UL-SCH)501and Random Access CHannel (RACH)502. A diagram inFIG.5Bshows example downlink transport channels comprising Downlink-Shared CHannel (DL-SCH)511, Paging CHannel (PCH)512, and Broadcast CHannel (BCH)513. A transport channel may be mapped to one or more corresponding physical channels. For example, UL-SCH501may be mapped to Physical Uplink Shared CHannel (PUSCH)503. RACH502may be mapped to PRACH505. DL-SCH511and PCH512may be mapped to Physical Downlink Shared CHannel (PDSCH)514. BCH513may be mapped to Physical Broadcast CHannel (PBCH)516. There may be one or more physical channels without a corresponding transport channel. The one or more physical channels may be employed for Uplink Control Information (UCI)509and/or Downlink Control Information (DCI)517. For example, Physical Uplink Control CHannel (PUCCH)504may carry UCI509from a UE to a base station. For example, Physical Downlink Control CHannel (PDCCH)515may carry DCI517from a base station to a UE. NR may support UCI509multiplexing in PUSCH503when UCI509and PUSCH503transmissions may coincide in a slot at least in part. The UCI509may comprise at least one of CSI, Acknowledgement (ACK)/Negative Acknowledgement (NACK), and/or scheduling request. The DCI517on PDCCH515may indicate at least one of following: one or more downlink assignments and/or one or more uplink scheduling grants In uplink, a UE may transmit one or more Reference Signals (RSs) to a base station. For example, the one or more RSs may be at least one of Demodulation-RS (DM-RS)506, Phase Tracking-RS (PT-RS)507, and/or Sounding RS (SRS)508. In downlink, a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more RSs to a UE. For example, the one or more RSs may be at least one of Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS)521, CSI-RS522, DM-RS523, and/or PT-RS524. In an example, a UE may transmit one or more uplink DM-RSs506to a base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH503and/or PUCCH504). For example, a UE may transmit a base station at least one uplink DM-RS506with PUSCH503and/or PUCCH504, wherein the at least one uplink DM-RS506may be spanning a same frequency range as a corresponding physical channel. In an example, a base station may configure a UE with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to transmit at one or more symbols of a PUSCH and/or PUCCH. A base station may semi-statistically configure a UE with a maximum number of front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UE may schedule a single-symbol DM-RS and/or double symbol DM-RS based on a maximum number of front-loaded DM-RS symbols, wherein a base station may configure the UE with one or more additional uplink DM-RS for PUSCH and/or PUCCH. A new radio network may support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be same or different. In an example, whether uplink PT-RS507is present or not may depend on a RRC configuration. For example, a presence of uplink PT-RS may be UE-specifically configured. For example, a presence and/or a pattern of uplink PT-RS507in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or association with one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)) which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS507may be associated with one or more DCI parameters comprising at least MCS. A radio network may support plurality of uplink PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be less than a number of DM-RS ports in a scheduled resource. For example, uplink PT-RS507may be confined in the scheduled time/frequency duration for a UE. In an example, a UE may transmit SRS508to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation. For example, SRS508transmitted by a UE may allow for a base station to estimate an uplink channel state at one or more different frequencies. A base station scheduler may employ an uplink channel state to assign one or more resource blocks of good quality for an uplink PUSCH transmission from a UE. A base station may semi-statistically configure a UE with one or more SRS resource sets. For an SRS resource set, a base station may configure a UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, a SRS resource in each of one or more SRS resource sets may be transmitted at a time instant. A UE may transmit one or more SRS resources in different SRS resource sets simultaneously. A new radio network may support aperiodic, periodic and/or semi-persistent SRS transmissions. A UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats (e.g., at least one DCI format may be employed for a UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH503and SRS508are transmitted in a same slot, a UE may be configured to transmit SRS508after a transmission of PUSCH503and corresponding uplink DM-RS506. In an example, a base station may semi-statistically configure a UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier, a number of SRS ports, time domain behavior of SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot (mini-slot, and/or subframe) level periodicity and/or offset for a periodic and/or aperiodic SRS resource, a number of OFDM symbols in a SRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID. In an example, in a time domain, an SS/PBCH block may comprise one or more OFDM symbols (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprise PSS/SSS521and PBCH516. In an example, in the frequency domain, an SS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239) within the SS/PBCH block. For example, a PSS/SSS521may occupy 1 OFDM symbol and 127 subcarriers. For example, PBCH516may span across 3 OFDM symbols and 240 subcarriers. A UE may assume that one or more SS/PBCH blocks transmitted with a same block index may be quasi co-located, e.g., with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. A UE may not assume quasi co-location for other SS/PBCH block transmissions. A periodicity of an SS/PBCH block may be configured by a radio network (e.g., by an RRC signaling) and one or more time locations where the SS/PBCH block may be sent may be determined by sub-carrier spacing. In an example, a UE may assume a band-specific sub-carrier spacing for an SS/PBCH block unless a radio network has configured a UE to assume a different sub-carrier spacing. In an example, downlink CSI-RS522may be employed for a UE to acquire channel state information. A radio network may support periodic, aperiodic, and/or semi-persistent transmission of downlink CSI-RS522. For example, a base station may semi-statistically configure and/or reconfigure a UE with periodic transmission of downlink CSI-RS522. A configured CSI-RS resources may be activated ad/or deactivated. For semi-persistent transmission, an activation and/or deactivation of CSI-RS resource may be triggered dynamically. In an example, CSI-RS configuration may comprise one or more parameters indicating at least a number of antenna ports. For example, a base station may configure a UE with 32 ports. A base station may semi-statistically configure a UE with one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated from one or more CSI-RS resource sets to one or more UEs. For example, a base station may semi-statistically configure one or more parameters indicating CSI RS resource mapping, for example, time-domain location of one or more CSI-RS resources, a bandwidth of a CSI-RS resource, and/or a periodicity. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS522and control resource set (coreset) when the downlink CSI-RS522and coreset are spatially quasi co-located and resource elements associated with the downlink CSI-RS522are the outside of PRBs configured for coreset. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS522and SSB/PBCH when the downlink CSI-RS522and SSB/PBCH are spatially quasi co-located and resource elements associated with the downlink CSI-RS522are the outside of PRBs configured for SSB/PBCH. In an example, a UE may transmit one or more downlink DM-RSs523to a base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variable and/or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). A base station may semi-statistically configure a UE with a maximum number of front-loaded DM-RS symbols for PDSCH514. For example, a DM-RS configuration may support one or more DM-RS ports. For example, for single user-MIMO, a DM-RS configuration may support at least 8 orthogonal downlink DM-RS ports. For example, for multiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlink DM-RS ports. A radio network may support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be same or different. In an example, whether downlink PT-RS524is present or not may depend on a RRC configuration. For example, a presence of downlink PT-RS524may be UE-specifically configured. For example, a presence and/or a pattern of downlink PT-RS524in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or association with one or more parameters employed for other purposes (e.g., MCS) which may be indicated by DCI. When configured, a dynamic presence of downlink PT-RS524may be associated with one or more DCI parameters comprising at least MCS. A radio network may support plurality of PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be less than a number of DM-RS ports in a scheduled resource. For example, downlink PT-RS524may be confined in the scheduled time/frequency duration for a UE. FIG.6is a diagram depicting an example frame structure for a carrier as per an aspect of an embodiment of the present disclosure. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 carriers, in case of carrier aggregation, or ranging from 1 to 64 carriers, in case of dual connectivity. Different radio frame structures may be supported (e.g., for FDD and for TDD duplex mechanisms).FIG.6shows an example frame structure. Downlink and uplink transmissions may be organized into radio frames601. In this example, radio frame duration is 10 ms. In this example, a 10 ms radio frame601may be divided into ten equally sized subframes602with 1 ms duration. Subframe(s) may comprise one or more slots (e.g. slots603and605) depending on subcarrier spacing and/or CP length. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz and 480 kHz subcarrier spacing may comprise one, two, four, eight, sixteen and thirty-two slots, respectively. InFIG.6, a subframe may be divided into two equally sized slots603with 0.5 ms duration. For example, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in a 10 ms interval. Uplink and downlink transmissions may be separated in the frequency domain. Slot(s) may include a plurality of OFDM symbols604. The number of OFDM symbols604in a slot605may depend on the cyclic prefix length. For example, a slot may be 14 OFDM symbols for the same subcarrier spacing of up to 480 kHz with normal CP. A slot may be 12 OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP. A slot may contain downlink, uplink, or a downlink part and an uplink part and/or alike. FIG.7Ais a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present disclosure. In the example, a gNB may communicate with a wireless device with a carrier with an example channel bandwidth700. Arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use technology such as OFDM technology, SC-FDMA technology, and/or the like. In an example, an arrow701shows a subcarrier transmitting information symbols. In an example, a subcarrier spacing702, between two contiguous subcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz, etc. In an example, different subcarrier spacing may correspond to different transmission numerologies. In an example, a transmission numerology may comprise at least: a numerology index; a value of subcarrier spacing; a type of cyclic prefix (CP). In an example, a gNB may transmit to/receive from a UE on a number of subcarriers703in a carrier. In an example, a bandwidth occupied by a number of subcarriers703(transmission bandwidth) may be smaller than the channel bandwidth700of a carrier, due to guard band704and705. In an example, a guard band704and705may be used to reduce interference to and from one or more neighbor carriers. A number of subcarriers (transmission bandwidth) in a carrier may depend on the channel bandwidth of the carrier and the subcarrier spacing. For example, a transmission bandwidth, for a carrier with 20 MHz channel bandwidth and 15 KHz subcarrier spacing, may be in number of1024subcarriers. In an example, a gNB and a wireless device may communicate with multiple CCs when configured with CA. In an example, different component carriers may have different bandwidth and/or subcarrier spacing, if CA is supported. In an example, a gNB may transmit a first type of service to a UE on a first component carrier. The gNB may transmit a second type of service to the UE on a second component carrier. Different type of services may have different service requirement (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carrier having different subcarrier spacing and/or bandwidth.FIG.7Bshows an example embodiment. A first component carrier may comprise a first number of subcarriers706with a first subcarrier spacing709. A second component carrier may comprise a second number of subcarriers707with a second subcarrier spacing710. A third component carrier may comprise a third number of subcarriers708with a third subcarrier spacing711. Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers. FIG.8is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present disclosure. In an example, a carrier may have a transmission bandwidth801. In an example, a resource grid may be in a structure of frequency domain802and time domain803. In an example, a resource grid may comprise a first number of OFDM symbols in a subframe and a second number of resource blocks, starting from a common resource block indicated by higher-layer signaling (e.g. RRC signaling), for a transmission numerology and a carrier. In an example, in a resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element805. In an example, a subframe may comprise a first number of OFDM symbols807depending on a numerology associated with a carrier. For example, when a subcarrier spacing of a numerology of a carrier is 15 KHz, a subframe may have 14 OFDM symbols for a carrier. When a subcarrier spacing of a numerology is 30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacing of a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. In an example, a second number of resource blocks comprised in a resource grid of a carrier may depend on a bandwidth and a numerology of the carrier. As shown inFIG.8, a resource block806may comprise 12 subcarriers. In an example, multiple resource blocks may be grouped into a Resource Block Group (RBG)804. In an example, a size of a RBG may depend on at least one of: a RRC message indicating a RBG size configuration; a size of a carrier bandwidth; or a size of a bandwidth part of a carrier. In an example, a carrier may comprise multiple bandwidth parts. A first bandwidth part of a carrier may have different frequency location and/or bandwidth from a second bandwidth part of the carrier. In an example, a gNB may transmit a downlink control information comprising a downlink or uplink resource block assignment to a wireless device. A base station may transmit to or receive from, a wireless device, data packets (e.g. transport blocks) scheduled and transmitted via one or more resource blocks and one or more slots according to parameters in a downlink control information and/or RRC message(s). In an example, a starting symbol relative to a first slot of the one or more slots may be indicated to the wireless device. In an example, a gNB may transmit to or receive from, a wireless device, data packets scheduled on one or more RBGs and one or more slots. In an example, a gNB may transmit a downlink control information comprising a downlink assignment to a wireless device via one or more PDCCHs. The downlink assignment may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to DL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a Cell-Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible allocation when its downlink reception is enabled. The wireless device may receive one or more downlink data package on one or more PDSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs. In an example, a gNB may allocate Configured Scheduling (CS) resources for down link transmission to a wireless device. The gNB may transmit one or more RRC messages indicating a periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CS resources. The DCI may comprise parameters indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages, until deactivated. In an example, a gNB may transmit a downlink control information comprising an uplink grant to a wireless device via one or more PDCCHs. The uplink grant may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to UL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible resource allocation. The wireless device may transmit one or more uplink data package via one or more PUSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs. In an example, a gNB may allocate CS resources for uplink data transmission to a wireless device. The gNB may transmit one or more RRC messages indicating a periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to a CS-RNTI activating the CS resources. The DCI may comprise parameters indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC message, until deactivated. In an example, a base station may transmit DCI/control signaling via PDCCH. The DCI may take a format in a plurality of formats. A DCI may comprise downlink and/or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), request for CSI (e.g., aperiodic CQI reports), request for SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmission/reception timing, HARQ feedback timing, etc.), etc. In an example, a DCI may indicate an uplink grant comprising transmission parameters for one or more transport blocks. In an example, a DCI may indicate downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a DCI may be used by base station to initiate a contention-free random access at the wireless device. In an example, the base station may transmit a DCI comprising slot format indicator (SFI) notifying a slot format. In an example, the base station may transmit a DCI comprising pre-emption indication notifying the PRB(s) and/or OFDM symbol(s) where a UE may assume no transmission is intended for the UE. In an example, the base station may transmit a DCI for group power control of PUCCH or PUSCH or SRS. In an example, a DCI may correspond to an RNTI. In an example, the wireless device may obtain an RNTI in response to completing the initial access (e.g., C-RNTI). In an example, the base station may configure an RNTI for the wireless (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, and TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI (e.g., the wireless device may compute RA-RNTI based on resources used for transmission of a preamble). In an example, an RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device may monitor a group common search space which may be used by base station for transmitting DCIs that are intended for a group of UEs. In an example, a group common DCI may correspond to an RNTI which is commonly configured for a group of UEs. In an example, a wireless device may monitor a UE-specific search space. In an example, a UE specific DCI may correspond to an RNTI configured for the wireless device. A NR system may support a single beam operation and/or a multi-beam operation. In a multi-beam operation, a base station may perform a downlink beam sweeping to provide coverage for common control channels and/or downlink SS blocks, which may comprise at least a PSS, a SSS, and/or PBCH. A wireless device may measure quality of a beam pair link using one or more RSs. One or more SS blocks, or one or more CSI-RS resources, associated with a CSI-RS resource index (CRI), or one or more DM-RSs of PBCH, may be used as RS for measuring quality of a beam pair link. Quality of a beam pair link may be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate whether an RS resource, used for measuring a beam pair link quality, is quasi-co-located (QCLed) with DM-RSs of a control channel A RS resource and DM-RSs of a control channel may be called QCLed when a channel characteristics from a transmission on an RS to a wireless device, and that from a transmission on a control channel to a wireless device, are similar or same under a configured criterion. In a multi-beam operation, a wireless device may perform an uplink beam sweeping to access a cell. In an example, a wireless device may be configured to monitor PDCCH on one or more beam pair links simultaneously depending on a capability of a wireless device. This may increase robustness against beam pair link blocking. A base station may transmit one or more messages to configure a wireless device to monitor PDCCH on one or more beam pair links in different PDCCH OFDM symbols. For example, a base station may transmit higher layer signaling (e.g. RRC signaling) or MAC CE comprising parameters related to the Rx beam setting of a wireless device for monitoring PDCCH on one or more beam pair links. A base station may transmit indication of spatial QCL assumption between a DL RS antenna port(s) (for example, cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RS antenna port(s) for demodulation of DL control channel. Signaling for beam indication for a PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or specification-transparent and/or implicit method, and combination of these signaling methods. For reception of unicast DL data channel, a base station may indicate spatial QCL parameters between DL RS antenna port(s) and DM-RS antenna port(s) of DL data channel. The base station may transmit DCI (e.g. downlink grants) comprising information indicating the RS antenna port(s). The information may indicate RS antenna port(s) which may be QCL-ed with the DM-RS antenna port(s). Different set of DM-RS antenna port(s) for a DL data channel may be indicated as QCL with different set of the RS antenna port(s). FIG.9AandFIG.9Bshow packet flows employing a multi connectivity (e.g. dual connectivity, multi connectivity, tight interworking, and/or the like).FIG.9Ais an example diagram of a protocol structure of a wireless device110(e.g. UE) with CA and/or multi connectivity as per an aspect of an embodiment.FIG.9Bis an example diagram of a protocol structure of multiple base stations with CA and/or multi connectivity as per an aspect of an embodiment. The multiple base stations may comprise a master node, MN1130(e.g. a master node, a master base station, a master gNB, a master eNB, and/or the like) and a secondary node, SN1150(e.g. a secondary node, a secondary base station, a secondary gNB, a secondary eNB, and/or the like). A master node1130and a secondary node1150may co-work to communicate with a wireless device110. When multi connectivity is configured for a wireless device110, the wireless device110, which may support multiple reception/transmission functions in an RRC connected state, may be configured to utilize radio resources provided by multiple schedulers of a multiple base stations. Multiple base stations may be inter-connected via a non-ideal or ideal backhaul (e.g. Xn interface, X2 interface, and/or the like). A base station involved in multi connectivity for a certain wireless device may perform at least one of two different roles: a base station may either act as a master base station or as a secondary base station. In multi connectivity, a wireless device may be connected to one master base station and one or more secondary base stations. In an example, a master base station (e.g. the MN1130) may provide a master cell group (MCG) comprising a primary cell and/or one or more secondary cells for a wireless device (e.g. the wireless device110). A secondary base station (e.g. the SN1150) may provide a secondary cell group (SCG) comprising a primary secondary cell (PSCell) and/or one or more secondary cells for a wireless device (e.g. the wireless device110). In multi connectivity, a radio protocol architecture that a bearer employs may depend on how a bearer is setup. In an example, three different type of bearer setup options may be supported: an MCG bearer, an SCG bearer, and/or a split bearer. A wireless device may receive/transmit packets of an MCG bearer via one or more cells of the MCG, and/or may receive/transmits packets of an SCG bearer via one or more cells of an SCG. Multi-connectivity may also be described as having at least one bearer configured to use radio resources provided by the secondary base station. Multi-connectivity may or may not be configured/implemented in some of the example embodiments. In an example, a wireless device (e.g. Wireless Device110) may transmit and/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC1118); packets of a split bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP1112), one of a master or secondary RLC layer (e.g. MN RLC1115, SN RLC1116), and one of a master or secondary MAC layer (e.g. MN MAC1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP1113), an RLC layer (e.g. SN RLC1117), and a MAC layer (e.g. MN MAC1119). In an example, a master base station (e.g. MN1130) and/or a secondary base station (e.g. SN1150) may transmit/receive: packets of an MCG bearer via a master or secondary node SDAP layer (e.g. SDAP1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC1124, MN RLC1125), and a master node MAC layer (e.g. MN MAC1128); packets of an SCG bearer via a master or secondary node SDAP layer (e.g. SDAP1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP1122, NR PDCP1143), a secondary node RLC layer (e.g. SN RLC1146, SN RLC1147), and a secondary node MAC layer (e.g. SN MAC1148); packets of a split bearer via a master or secondary node SDAP layer (e.g. SDAP1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP1123, NR PDCP1141), a master or secondary node RLC layer (e.g. MN RLC1126, SN RLC1144, SN RLC1145, MN RLC1127), and a master or secondary node MAC layer (e.g. MN MAC1128, SN MAC1148). In multi connectivity, a wireless device may configure multiple MAC entities: one MAC entity (e.g. MN MAC1118) for a master base station, and other MAC entities (e.g. SN MAC1119) for a secondary base station. In multi-connectivity, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and SCGs comprising serving cells of a secondary base station. For an SCG, one or more of following configurations may be applied: at least one cell of an SCG has a configured UL CC and at least one cell of a SCG, named as primary secondary cell (PSCell, PCell of SCG, or sometimes called PCell), is configured with PUCCH resources; when an SCG is configured, there may be at least one SCG bearer or one Split bearer; upon detection of a physical layer problem or a random access problem on a PSCell, or a number of NR RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a wireless device of a SCG failure type, for split bearer, a DL data transfer over a master base station may be maintained; an NR RLC acknowledged mode (AM) bearer may be configured for a split bearer; PCell and/or PSCell may not be de-activated; PS Cell may be changed with a SCG change procedure (e.g. with security key change and a RACH procedure); and/or a bearer type change between a split bearer and a SCG bearer or simultaneous configuration of a SCG and a split bearer may or may not supported. With respect to interaction between a master base station and a secondary base stations for multi-connectivity, one or more of the following may be applied: a master base station and/or a secondary base station may maintain RRM measurement configurations of a wireless device; a master base station may (e.g. based on received measurement reports, traffic conditions, and/or bearer types) may decide to request a secondary base station to provide additional resources (e.g. serving cells) for a wireless device; upon receiving a request from a master base station, a secondary base station may create/modify a container that may result in configuration of additional serving cells for a wireless device (or decide that the secondary base station has no resource available to do so); for a UE capability coordination, a master base station may provide (a part of) an AS configuration and UE capabilities to a secondary base station; a master base station and a secondary base station may exchange information about a UE configuration by employing of RRC containers (inter-node messages) carried via Xn messages; a secondary base station may initiate a reconfiguration of the secondary base station existing serving cells (e.g. PUCCH towards the secondary base station); a secondary base station may decide which cell is a PSCell within a SCG; a master base station may or may not change content of RRC configurations provided by a secondary base station; in case of a SCG addition and/or a SCG SCell addition, a master base station may provide recent (or the latest) measurement results for SCG cell(s); a master base station and secondary base stations may receive information of SFN and/or subframe offset of each other from OAM and/or via an Xn interface, (e.g. for a purpose of DRX alignment and/or identification of a measurement gap). In an example, when adding a new SCG SCell, dedicated RRC signaling may be used for sending required system information of a cell as for CA, except for a SFN acquired from a MIB of a PSCell of a SCG. FIG.10is an example diagram of a random access procedure. One or more events may trigger a random access procedure. For example, one or more events may be at least one of following: initial access from RRC_IDLE, RRC connection re-establishment procedure, handover, DL or UL data arrival during RRC_CONNECTED when UL synchronization status is non-synchronized, transition from RRC_Inactive, and/or request for other system information. For example, a PDCCH order, a MAC entity, and/or a beam failure indication may initiate a random access procedure. In an example embodiment, a random access procedure may be at least one of a contention based random access procedure and a contention free random access procedure. For example, a contention based random access procedure may comprise, one or more Msg11220transmissions, one or more Msg21230transmissions, one or more Msg31240transmissions, and contention resolution1250. For example, a contention free random access procedure may comprise one or more Msg11220transmissions and one or more Msg21230transmissions. In an example, a base station may transmit (e.g., unicast, multicast, or broadcast), to a UE, a RACH configuration1210via one or more beams. The RACH configuration1210may comprise one or more parameters indicating at least one of following: available set of PRACH resources for a transmission of a random access preamble, initial preamble power (e.g., random access preamble initial received target power), an RSRP threshold for a selection of a SS block and corresponding PRACH resource, a power-ramping factor (e.g., random access preamble power ramping step), random access preamble index, a maximum number of preamble transmission, preamble group A and group B, a threshold (e.g., message size) to determine the groups of random access preambles, a set of one or more random access preambles for system information request and corresponding PRACH resource(s), if any, a set of one or more random access preambles for beam failure recovery request and corresponding PRACH resource(s), if any, a time window to monitor RA response(s), a time window to monitor response(s) on beam failure recovery request, and/or a contention resolution timer. In an example, the Msg11220may be one or more transmissions of a random access preamble. For a contention based random access procedure, a UE may select a SS block with a RSRP above the RSRP threshold. If random access preambles group B exists, a UE may select one or more random access preambles from a group A or a group B depending on a potential Msg31240size. If a random access preambles group B does not exist, a UE may select the one or more random access preambles from a group A. A UE may select a random access preamble index randomly (e.g. with equal probability or a normal distribution) from one or more random access preambles associated with a selected group. If a base station semi-statistically configures a UE with an association between random access preambles and SS blocks, the UE may select a random access preamble index randomly with equal probability from one or more random access preambles associated with a selected SS block and a selected group. For example, a UE may initiate a contention free random access procedure based on a beam failure indication from a lower layer. For example, a base station may semi-statistically configure a UE with one or more contention free PRACH resources for beam failure recovery request associated with at least one of SS blocks and/or CSI-RSs. If at least one of SS blocks with a RSRP above a first RSRP threshold amongst associated SS blocks or at least one of CSI-RSs with a RSRP above a second RSRP threshold amongst associated CSI-RSs is available, a UE may select a random access preamble index corresponding to a selected SS block or CSI-RS from a set of one or more random access preambles for beam failure recovery request. For example, a UE may receive, from a base station, a random access preamble index via PDCCH or RRC for a contention free random access procedure. If a base station does not configure a UE with at least one contention free PRACH resource associated with SS blocks or CSI-RS, the UE may select a random access preamble index. If a base station configures a UE with one or more contention free PRACH resources associated with SS blocks and at least one SS block with a RSRP above a first RSRP threshold amongst associated SS blocks is available, the UE may select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If a base station configures a UE with one or more contention free PRACH resources associated with CSI-RSs and at least one CSI-RS with a RSRP above a second RSPR threshold amongst the associated CSI-RSs is available, the UE may select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS. A UE may perform one or more Msg11220transmissions by transmitting the selected random access preamble. For example, if a UE selects an SS block and is configured with an association between one or more PRACH occasions and one or more SS blocks, the UE may determine a PRACH occasion from one or more PRACH occasions corresponding to a selected SS block. For example, if a UE selects a CSI-RS and is configured with an association between one or more PRACH occasions and one or more CSI-RSs, the UE may determine a PRACH occasion from one or more PRACH occasions corresponding to a selected CSI-RS. A UE may transmit, to a base station, a selected random access preamble via a selected PRACH occasions. A UE may determine a transmit power for a transmission of a selected random access preamble at least based on an initial preamble power and a power-ramping factor. A UE may determine a RA-RNTI associated with a selected PRACH occasions in which a selected random access preamble is transmitted. For example, a UE may not determine a RA-RNTI for a beam failure recovery request. A UE may determine an RA-RNTI at least based on an index of a first OFDM symbol and an index of a first slot of a selected PRACH occasions, and/or an uplink carrier index for a transmission of Msg11220. In an example, a UE may receive, from a base station, a random access response, Msg21230. A UE may start a time window (e.g., ra-Response Window) to monitor a random access response. For beam failure recovery request, a base station may configure a UE with a different time window (e.g., bfr-Response Window) to monitor response on beam failure recovery request. For example, a UE may start a time window (e.g., ra-ResponseWindow or bfr-Response Window) at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a preamble transmission. If a UE transmits multiple preambles, the UE may start a time window at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a first preamble transmission. A UE may monitor a PDCCH of a cell for at least one random access response identified by a RA-RNTI or for at least one response to beam failure recovery request identified by a C-RNTI while a timer for a time window is running In an example, a UE may consider a reception of random access response successful if at least one random access response comprises a random access preamble identifier corresponding to a random access preamble transmitted by the UE. A UE may consider the contention free random access procedure successfully completed if a reception of random access response is successful. If a contention free random access procedure is triggered for a beam failure recovery request, a UE may consider a contention free random access procedure successfully complete if a PDCCH transmission is addressed to a C-RNTI. In an example, if at least one random access response comprises a random access preamble identifier, a UE may consider the random access procedure successfully completed and may indicate a reception of an acknowledgement for a system information request to upper layers. If a UE has signaled multiple preamble transmissions, the UE may stop transmitting remaining preambles (if any) in response to a successful reception of a corresponding random access response. In an example, a UE may perform one or more Msg31240transmissions in response to a successful reception of random access response (e.g., for a contention based random access procedure). A UE may adjust an uplink transmission timing based on a timing advanced command indicated by a random access response and may transmit one or more transport blocks based on an uplink grant indicated by a random access response. Subcarrier spacing for PUSCH transmission for Msg31240may be provided by at least one higher layer (e.g. RRC) parameter. A UE may transmit a random access preamble via PRACH and Msg31240via PUSCH on a same cell. A base station may indicate an UL BWP for a PUSCH transmission of Msg31240via system information block. A UE may employ HARQ for a retransmission of Msg31240. In an example, multiple UEs may perform Msg11220by transmitting a same preamble to a base station and receive, from the base station, a same random access response comprising an identity (e.g., TC-RNTI). Contention resolution1250may ensure that a UE does not incorrectly use an identity of another UE. For example, contention resolution1250may be based on C-RNTI on PDCCH or a UE contention resolution identity on DL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UE may perform contention resolution1250based on a reception of a PDCCH transmission that is addressed to the C-RNTI. In response to detection of a C-RNTI on a PDCCH, a UE may consider contention resolution1250successful and may consider a random access procedure successfully completed. If a UE has no valid C-RNTI, a contention resolution may be addressed by employing a TC-RNTI. For example, if a MAC PDU is successfully decoded and a MAC PDU comprises a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg31250, a UE may consider the contention resolution1250successful and may consider the random access procedure successfully completed. FIG.11is an example structure for MAC entities as per an aspect of an embodiment. In an example, a wireless device may be configured to operate in a multi-connectivity mode. A wireless device in RRC_CONNECTED with multiple RX/TX may be configured to utilize radio resources provided by multiple schedulers located in a plurality of base stations. The plurality of base stations may be connected via a non-ideal or ideal backhaul over the Xn interface. In an example, a base station in a plurality of base stations may act as a master base station or as a secondary base station. A wireless device may be connected to one master base station and one or more secondary base stations. A wireless device may be configured with multiple MAC entities, e.g. one MAC entity for master base station, and one or more other MAC entities for secondary base station(s). In an example, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and one or more SCGs comprising serving cells of a secondary base station(s).FIG.13illustrates an example structure for MAC entities when MCG and SCG are configured for a wireless device. In an example, at least one cell in a SCG may have a configured UL CC, wherein a cell of at least one cell may be called PSCell or PCell of SCG, or sometimes may be simply called PCell. A PSCell may be configured with PUCCH resources. In an example, when a SCG is configured, there may be at least one SCG bearer or one split bearer. In an example, upon detection of a physical layer problem or a random access problem on a PSCell, or upon reaching a number of RLC retransmissions associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a UE of a SCG failure type and DL data transfer over a master base station may be maintained. In an example, a MAC sublayer may provide services such as data transfer and radio resource allocation to upper layers (e.g.1310or1320). A MAC sublayer may comprise a plurality of MAC entities (e.g.1350and1360). A MAC sublayer may provide data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels may be defined. A logical channel may support transfer of a particular type of information. A logical channel type may be defined by what type of information (e.g., control or data) is transferred. For example, BCCH, PCCH, CCCH and DCCH may be control channels and DTCH may be a traffic channel. In an example, a first MAC entity (e.g.1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH and MAC control elements. In an example, a second MAC entity (e.g.1320) may provide services on BCCH, DCCH, DTCH and MAC control elements. A MAC sublayer may expect from a physical layer (e.g.1330or1340) services such as data transfer services, signaling of HARQ feedback, signaling of scheduling request or measurements (e.g. CQI). In an example, in dual connectivity, two MAC entities may be configured for a wireless device: one for MCG and one for SCG. A MAC entity of wireless device may handle a plurality of transport channels. In an example, a first MAC entity may handle first transport channels comprising a PCCH of MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one or more first UL-SCHs of MCG and one or more first RACHs of MCG. In an example, a second MAC entity may handle second transport channels comprising a second BCH of SCG, one or more second DL-SCHs of SCG, one or more second UL-SCHs of SCG and one or more second RACHs of SCG. In an example, if a MAC entity is configured with one or more SCells, there may be multiple DL-SCHs and there may be multiple UL-SCHs as well as multiple RACHs per MAC entity. In an example, there may be one DL-SCH and UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero or one UL-SCH and zero or one RACH for an SCell. A DL-SCH may support receptions using different numerologies and/or TTI duration within a MAC entity. A UL-SCH may also support transmissions using different numerologies and/or TTI duration within the MAC entity. In an example, a MAC sublayer may support different functions and may control these functions with a control (e.g.1355or1365) element. Functions performed by a MAC entity may comprise mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g.1352or1362) of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels (e.g., in uplink), demultiplexing (e.g.1352or1362) of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction through HARQ in uplink or downlink (e.g.1363), and logical channel prioritization in uplink (e.g.1351or1361). A MAC entity may handle a random access process (e.g.1354or1364). FIG.12is an example diagram of a RAN architecture comprising one or more base stations. In an example, a protocol stack (e.g. RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at a node. A base station (e.g.120A or120B) may comprise a base station central unit (CU) (e.g. gNB-CU1420A or1420B) and at least one base station distributed unit (DU) (e.g. gNB-DU1430A,1430B,1430C, or1430D) if a functional split is configured. Upper protocol layers of a base station may be located in a base station CU, and lower layers of the base station may be located in the base station DUs. An F1 interface (e.g. CU-DU interface) connecting a base station CU and base station DUs may be an ideal or non-ideal backhaul. F1-C may provide a control plane connection over an F1 interface, and F1-U may provide a user plane connection over the F1 interface. In an example, an Xn interface may be configured between base station CUs. In an example, a base station CU may comprise an RRC function, an SDAP layer, and a PDCP layer, and base station DUs may comprise an RLC layer, a MAC layer, and a PHY layer. In an example, various functional split options between a base station CU and base station DUs may be possible by locating different combinations of upper protocol layers (RAN functions) in a base station CU and different combinations of lower protocol layers (RAN functions) in base station DUs. A functional split may support flexibility to move protocol layers between a base station CU and base station DUs depending on service requirements and/or network environments. In an example, functional split options may be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or with other granularities. In per base station CU split, a base station CU may have a fixed split option, and base station DUs may be configured to match a split option of a base station CU. In per base station DU split, a base station DU may be configured with a different split option, and a base station CU may provide different split options for different base station DUs. In per UE split, a base station (base station CU and at least one base station DUs) may provide different split options for different wireless devices. In per bearer split, different split options may be utilized for different bearers. In per slice splice, different split options may be applied for different slices. FIG.13is an example diagram showing RRC state transitions of a wireless device. In an example, a wireless device may be in at least one RRC state among an RRC connected state (e.g. RRC Connected1530, RRC_Connected), an RRC idle state (e.g. RRC Idle1510, RRC_Idle), and/or an RRC inactive state (e.g. RRC Inactive1520, RRC_Inactive). In an example, in an RRC connected state, a wireless device may have at least one RRC connection with at least one base station (e.g. gNB and/or eNB), which may have a UE context of the wireless device. A UE context (e.g. a wireless device context) may comprise at least one of an access stratum context, one or more radio link configuration parameters, bearer (e.g. data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, and/or the like) configuration information, security information, PHY/MAC/RLC/PDCP/SDAP layer configuration information, and/or the like configuration information for a wireless device. In an example, in an RRC idle state, a wireless device may not have an RRC connection with a base station, and a UE context of a wireless device may not be stored in a base station. In an example, in an RRC inactive state, a wireless device may not have an RRC connection with a base station. A UE context of a wireless device may be stored in a base station, which may be called as an anchor base station (e.g. last serving base station). In an example, a wireless device may transition a UE RRC state between an RRC idle state and an RRC connected state in both ways (e.g. connection release1540or connection establishment1550; or connection reestablishment) and/or between an RRC inactive state and an RRC connected state in both ways (e.g. connection inactivation1570or connection resume1580). In an example, a wireless device may transition its RRC state from an RRC inactive state to an RRC idle state (e.g. connection release1560). In an example, an anchor base station may be a base station that may keep a UE context (a wireless device context) of a wireless device at least during a time period that a wireless device stays in a RAN notification area (RNA) of an anchor base station, and/or that a wireless device stays in an RRC inactive state. In an example, an anchor base station may be a base station that a wireless device in an RRC inactive state was lastly connected to in a latest RRC connected state or that a wireless device lastly performed an RNA update procedure in. In an example, an RNA may comprise one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs. In an example, a wireless device may transition a UE RRC state from an RRC connected state to an RRC inactive state in a base station. A wireless device may receive RNA information from the base station. RNA information may comprise at least one of an RNA identifier, one or more cell identifiers of one or more cells of an RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a resume identifier, and/or the like. In an example, an anchor base station may broadcast a message (e.g. RAN paging message) to base stations of an RNA to reach to a wireless device in an RRC inactive state, and/or the base stations receiving the message from the anchor base station may broadcast and/or multicast another message (e.g. paging message) to wireless devices in their coverage area, cell coverage area, and/or beam coverage area associated with the RNA through an air interface. In an example, when a wireless device in an RRC inactive state moves into a new RNA, the wireless device may perform an RNA update (RNAU) procedure, which may comprise a random access procedure by the wireless device and/or a UE context retrieve procedure. A UE context retrieve may comprise: receiving, by a base station from a wireless device, a random access preamble; and fetching, by a base station, a UE context of the wireless device from an old anchor base station. Fetching may comprise: sending a retrieve UE context request message comprising a resume identifier to the old anchor base station and receiving a retrieve UE context response message comprising the UE context of the wireless device from the old anchor base station. In an example embodiment, a wireless device in an RRC inactive state may select a cell to camp on based on at least a measurement result for one or more cells, a cell where a wireless device may monitor an RNA paging message and/or a core network paging message from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to resume an RRC connection and/or to transmit one or more packets to a base station (e.g. to a network). In an example, if a cell selected belongs to a different RNA from an RNA for a wireless device in an RRC inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if a wireless device in an RRC inactive state has one or more packets, in a buffer, to transmit to a network, the wireless device may initiate a random access procedure to transmit one or more packets to a base station of a cell that the wireless device selects. A random access procedure may be performed with two messages (e.g. 2 stage random access) and/or four messages (e.g. 4 stage random access) between the wireless device and the base station. In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state may fetch a UE context of a wireless device by transmitting a retrieve UE context request message for the wireless device to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a resume identifier, and/or a cell identifier received from the wireless device. In response to fetching a UE context, a base station may transmit a path switch request for a wireless device to a core network entity (e.g. AMF, MME, and/or the like). A core network entity may update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity (e.g. UPF, S-GW, and/or the like) and a RAN node (e.g. the base station), e g changing a downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station. A gNB may communicate with a wireless device via a wireless network employing one or more new radio technologies. The one or more radio technologies may comprise at least one of: multiple technologies related to physical layer; multiple technologies related to medium access control layer; and/or multiple technologies related to radio resource control layer. Example embodiments of enhancing the one or more radio technologies may improve performance of a wireless network. Example embodiments may increase the system throughput, or data rate of transmission. Example embodiments may reduce battery consumption of a wireless device. Example embodiments may improve latency of data transmission between a gNB and a wireless device. Example embodiments may improve network coverage of a wireless network. Example embodiments may improve transmission efficiency of a wireless network. In an example embodiment, a wireless device of the 5G network may stay in at least one RRC state among an RRC connected state, an RRC idle state, and an RRC inactive state. In an example, in an RRC connected state, a wireless device may have at least one RRC connection with at least one base station, which may have a UE context of the wireless device. A UE context (a wireless device context) may comprise at least one of an AS context, a bearer configuration information, a security information, a PDCP configuration information, and/or other configuration information for a wireless device. In an example, in an RRC idle state, a wireless device may not have a RRC connection with a base station, and a UE context of a wireless device may not be stored in a base station. In an example, in an RRC inactive state, a wireless device may not have a RRC connection with a base station, but a UE context of a wireless device may be stored in a base station, which may be called as an anchor base station. In an example embodiment, a wireless device may transition its RRC state between an RRC idle state and an RRC connected state in both ways, and between an RRC inactive state and an RRC connected state in both ways, and from an RRC inactive state to an RRC idle state in one direction. In an example embodiment, an anchor base station may be a base station that may keep a UE context (a wireless device context) at least as long as a wireless device associated of the UE context stays in an RNA (RAN notification area) of the anchor base station. In an example, an anchor base station, in a UE specific anchor case, may be a base station that a wireless device in an RRC inactive state was lastly connected to in the latest RRC connected state or that a wireless device lastly performed a RNA update procedure in. In an example, an anchor base station, in a common anchor case, may be a base station determined to keep UE contexts of wireless devices in an RRC inactive state staying in an RNA of the anchor base station. In common anchor case, one or more anchor base stations may exist in an RNA. In an example embodiment, an RNA may comprise one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs. In an example, an anchor base station may broadcast a message to base stations in an RNA to reach to a wireless device in an RRC inactive state, and base stations receiving a broadcasted message from an anchor base station may broadcast and/or multicast another message to wireless devices in their coverage area, cell coverage area, and/or beam coverage area associated with the RNA through an air interface. In an example, when a wireless device in an RRC inactive state moves into a new RNA, it may perform an RNA update (RNAU) procedure, which may comprise a random access procedure by the wireless device and/or a UE context retrieve procedure, by a base station receiving a random access preamble message from the wireless device, fetching a UE context of the wireless device from an old anchor base station of an old RNA to a new anchor base station of the new RNA. In an example embodiment, a wireless device may transition its RRC state from an RRC connected state to an RRC inactive state in a first base station. In an example, the wireless device may receive an RNA information from the first base station. In case that the first base station is an anchor base station for the wireless device (i.e. in a UE specific anchor case or if the first base station is an anchor base station in a common anchor case), the RNA information may comprise at least one of an RNA identifier, a cell identifier, a base station identifier, an IP address of the first base station, and/or an AS context identifier of the wireless device. In case that the first base station is not an anchor base station for the wireless device (i.e. if the first base station is not an anchor base station in a common anchor case), the RNA information may comprise at least one of an RNA identifier, a cell identifier of the first base station, a base station identifier of an anchor base station, an IP address of an anchor base station, and/or an AS context identifier. In an example, in case that the first base station is an anchor base station for the wireless device, the first base station may keep a UE context of the wireless device at least during a period when the wireless device stays in an RNA associated with the wireless device. In case that the first base station is not an anchor base station for the wireless device, the first base station may transfer one or more elements of a UE context of the wireless device to an anchor base station, and the anchor base station may keep one or more elements of the UE context of the wireless device at least during a period when the wireless device stays in an RNA associated with the wireless device. In an example embodiment, a wireless device in an RRC inactive state may select a cell where the wireless device receives an RNA paging message and/or a core network paging message from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to establish an RRC connection and/or to transmit one or more packets. In an example, if the selected cell belongs to a different RNA than an RNA associated with the wireless device, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if a wireless device in an RRC inactive state has one or more packets, in its buffer, to transmit to the network, the wireless device may initiate a random access procedure to transmit the one or more packets to a base station of a cell that the wireless device selected. The random access procedure may be performed with two messages and/or four messages between the wireless device and the base station. In an example, one or more uplink packets of a wireless device in an RRC inactive state may be PDCP protocol layer packets. In an example embodiment, one or more uplink packets from a wireless device in an RRC inactive state may be transmitted to a core network entity. In an example, a first base station receiving one or more uplink packets from a wireless device in an RRC inactive state may transmit the one or more uplink packets to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, and/or a cell identifier received from the wireless device. In an example, the anchor base station may transmit the uplink data packets to a core network entity at least based on a UE context retrieved at least based on an AS context identifier and/or a wireless device identifier received from the first base station. In an example embodiment, a first base station receiving one or more uplink packets from a wireless device in an RRC inactive state may transmit a UE context fetch request for the wireless device to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, and/or a cell identifier received from the wireless device. In an example, the anchor base station may transmit a UE context for the wireless device to the first base station based on at least one of an AS context identifier and/or a wireless device identifier received from the first base station. The first base station receiving the UE context may transmit a path switch request for the wireless device to a core network entity, and the core network entity may update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity and a RAN node, e g changing a downlink tunnel endpoint identifier from an address of the anchor base station to an address of the first base station. In an example, the first base station may transmit the one or more uplink packets to the user plane core network entity based on at least one of the UE context and/or the updated one or more bearers between the user plane core network entity and the first base station. In an example, the anchor base station may remove the UE context for the wireless device. In addition to the CN tracking areas, a UE in RRC_INACTIVE may be tracked on a “RAN based notification area” (called “RAN area” herein) wherein the UE may move freely without notifying the network. Once the UE moves outside the RAN area, it may perform a RAN area update. As the RAN areas are only applicable to UEs in RRC_INACTIVE, the RAN area updates may be performed with the RRCConnectionResumeRequest message (e.g. the message may be used to transition from RRC_INACTIVE to RRC_CONNECTED) with a causeValue equal to e.g. “ranNotificationAreaUpdateRequest”. The motivation for using this message may be that there may be DL data waiting so the network may have the possibility to order the UE to RRC_CONNECTED (and complete the “resume” procedure). When the network receives the RRCConnectionResumeRequest message, if it finds the UE context, it may relocate the UE context and the CN/RAN connection and then directly may suspend the UE with an updated RAN notification Area using the RRCConnectionSuspend message. If there are DL data for the UE at this point, the network may respond with an RRCConnectionResume message transitioning the UE to RRC_CONNECTED. If there is no UL or DL data, the UE may return to RRC_INACTIVE as soon as possible. The UE may need to be given a new resume Identity when it is suspended to RRC_INACTIVE in order to indicate the new location of the UE context. The UE specific RAN area may be updated with the ranAreaInformation included in the RRCConnectionSuspend message. The ranAreaInformation may either indicate the entire new RAN area using a list of cells, or use delta-signalling to inform which cells may be added/removed from the RAN area. In addition, the ranAreaInformation may also indicate whether the UE may use its old RAN area, or if the RAN area may consist of the UE's TAI-list. Since the UE may be assigned with a new RAN area and a new Resume ID (resume identity) when the connection is suspended it may be important that the RRCConnectionSuspend message may be encrypted and integrity protected. In LTE, this may be achieved by providing the UE with the Next Hop Chaining Counter (NCC) in the RRCConnectionSetup message and transition into RRC_CONNECTED where security may be enabled. In order to optimize the RAN area update procedure, and allow the UE to be directly suspended to RRC_INACTIVE as a response to the RRCConnectionResumeRequest, it may be necessary that the UE may have already derived the encryption keys at MSG3. This may be achieved by providing the UE with the NCC already in the RRCConnectionSuspend message. This may also allow for integrity protection of the RRCConnectionResumeRequest. In addition, there may be cases where the RAN cannot retrieve the old UE context, e.g. if it is lost or discarded, or resides in a gNB from which it cannot fetch the context. In this case, it may not be possible to complete the RAN area update without first re-building the RAN context. In that case, when the UE transmit the RRCConnectionResumeRequest message, the RAN may respond with an RRCConnectionSetup which may trigger the UE to initiate NAS level procedure causing the CN to rebuild the UE context in the RAN. Since the RAN may be aware that the UE wanted to perform a RAN notification area update, and that there may be no UL or DL data available, it may quickly re-suspend the UE to RRC_INACTIVE once the AS context has been rebuilt as can be seen inFIG.3. If the RAN decides that the UE may not be re-suspended to RRC_INACTIVE after the RAN Notification Area Update, it may respond with an RRCConnectionReject which may cause the UE to transition to RRC_IDLE. Additional signalling may be needed on the network side to trigger the removal of the RAN context. In LTE, a UE in RRC_IDLE may perform periodic TAU (Tracking Area Update) when the TA update timer (T3412) expires in order for the CN to ascertain the UE location on a Tracking Area level and to check if UE is still attached to the network. For instance, if a UE is turned off, the absence of a periodic TAU may indicate to the CN that the UE may no longer inside the attached and that the network context may be removed. In RRC_CONNECTED, there may no need to perform the periodic TAU as the network may know the UE location on a cell level and it may be the responsibility of the RAN layer to ensure UE is still connected. For RRC_INACTIVE, the motivation to perform periodic area updates may remain the same as for periodic TAUs in RRC_IDLE, i.e. the network may need to be able to ascertain that a UE may not disappeared from the network, without informing the network (e.g. power off). The UE in an RRC inactive state may perform periodic TAU, RAN area updates, or both. As the periodic area updates are mainly intended to inform the network that the UE may remain in the same area as before, this signalling may be performed as lightweight as possible. If a periodic TAU is performed from RRC_INACTIVE, the UE may enter RRC_CONNECTED to transmit the NAS message “TAU Request” and may await the NAS message “TAU Accept” from the CN before it may return to RRC_INACTIVE. On the other hand, a successful periodic RAN area update may consist of an RRCConnectionResumeRequest message with e.g. a causeValue “ranNotificationAreaUpdateRequest”. If the periodic RAN area update is performed in same gNB as the UE may have been suspended in, the UE context may be already available in the gNB and the UE may directly be suspended to RRC_INACTIVE. The RRCConnectionSuspend message from the gNB may contain a new resumeId (resume identity), a “ranAreaInformation” (e.g. a cell list, or an indication to use the old RAN area, or an indication to use the TA-list as RAN area), as well as the Next Hop Chaining Counter (NCC). The new Resume ID (resume identity) may indicate the updated UE context, the RAN area information may ensure that the UE may maintain an up-to-date RAN area, while the NCC may ensure that the UE can resume the connection with encryption enabled already in message three of random access procedure, even in a different gNB. If the UE resumes the connection in another gNB inside the RAN area, the UE context may be fetched from the old gNB using similar procedure as for RAN area updates based on mobility. In addition, the RAN may decide to release the UE to RRC_IDLE during the periodic RAN area update, e.g. if it may have performed multiple periodic RAN area updates within the same area without any UP activity. If the UE resumes the connection in the old gNB, the RAN may respond to the RRCConnectionResumeRequest with an RRCConnectionRelease as seen inFIG.5. When the RAN releases the UE context, it may be necessary to inform the CN so that it can release the CN context and/or the UE context stored in another gNB. The periodic TA update timer (T3412) may be set by the CN and may have a default value of 54 minutes in LTE. However, in some cases as the RAN may want to have a different periodicity of the periodic location update than the periodic TAU. Therefore, the RAN may be able to configure an independent timer for the RAN area updates. If the periodic RAN area update fails, e.g. if the UE context cannot be retrieved, the RAN may decide to respond with an RRCConnectionSetup to transition the UE to RRC_CONNECTED so that the CN is also updated as can be seen inFIG.6. Updating the CN may be important in case the CN thinks the UE may be in RRC_IDLE and may have started the periodic TAU timer. As the RAN area update may be more lightweight than the TAU, a UE may only perform periodic RAN area updates in RRC_INACTIVE. Example of Inactive State Data Forwarding In an existing RAN paging procedure, base stations exchanges backhaul signaling to transmit a downlink packets to a wireless device in an RRC inactive state. An anchor base station may transmit paging messages via its cells and/or to its neighboring base stations of a RAN notification area associated with the wireless device. Implementation of existing backhaul signaling when a RAN paging procedure is failed may result in increased packet loss rate and/or increased call drop rate due to inefficient packet forwarding to the wireless device. A failure of a RAN paging procedure may introduce a need for further enhancement in communication among network nodes (e.g. base stations, core network entity, and wireless device). In an example, failure rate in receiving downlink user plane or control plane packets (e.g. data packets, NAS/RRC signaling packets) may increase for RRC inactive state wireless devices. Increased packet loss rate may degrade network system reliability. There is a need to improve backhaul signaling mechanism for RRC inactive state wireless devices. Example embodiments enhance information exchange among network nodes to improve network communication reliability when a wireless device is in an RRC inactive state or an RRC idle state. Example may enhance signaling procedures when a RAN paging procedure is failed. In an existing network signaling, when a RAN paging procedure initiated for packet transmissions is failed, an anchor base station may discard packets received from a core network entity. In an example embodiment as shown inFIG.14andFIG.15, when receiving packets for a wireless device (e.g. UE) in an RRC inactive state from a user plane core network entity (e.g. UPF), a first base station (e.g. gNB) may initiate a RAN paging procedure by transmitting one or more first paging messages to one or more second base stations. If the first base station fails in the RAN paging procedure, the first base station may transmit a paging failure indication to a control plane core network entity (e.g. AMF). The core network entity may initiate a core network paging (e.g. tracking area based paging procedure) for the wireless device. A third base station may receive a response from the wireless device for the core network paging procedure, and the third base station may send a tunnel endpoint identifier (e.g. IP address) of the third base station to the first base station, for example, via the core network entity. The first base station may transmit the packets received from the user plane core network entity to the third base station based on the tunnel endpoint identifier. Example embodiments may enhance system reliability by enabling network nodes to share tunnel information for packet forwarding to a wireless device when a RAN paging procedure is failed. Example embodiments may enable network nodes to reduce packet loss rate or call drop rate for an RRC inactive and/or idle state wireless device in RAN paging failure cases. In an example, a first base station may receive, from a first core network entity, one or more packets for a wireless device in a radio resource control (RRC) inactive state. The first base station may be an anchor base station of the wireless device, and/or a base station that initiated a state transition of the wireless device to an RRC inactive state. The first base station may keep a UE context of the wireless device. The UE context may comprise at least one of PDU session configurations, security configurations, radio bearer configurations, logical channel configurations, resume identifier associated with the RRC inactive state, RAN notification area information (e.g. a RAN area identifier, a cell identifier, a base station identifier of a RAN notification area of the wireless device). The first core network entity may comprise a user-plane core network entity (e.g. UPF), a control-plane core network entity (e.g. AMF), and/or an application server when the first base station employs a base station-core network collocated structure (e.g. selected IP traffic offload, SIPTO). The one or more packets may comprise downlink data packets for an RRC inactive state wireless device. In an example, the downlink data packets may be associated with a certain service, e.g. a vehicle communication downlink packet transmission, an ultra reliable low latency (URLLC) service, machine type communication (MTC) services, and/or the like. The one or more packets may comprise control signaling packets, for example, one or more NAS layer messages transmitted by the AMF. In an example, the first base station may initiate a RAN paging procedure comprising sending at least one RAN paging message to at least one second base station. The at least one RAN paging message may comprise a first identifier of the wireless device. The RAN paging procedure may be initiated to page the wireless device being in the RRC inactive state for forwarding the one or more packets received from the first core network entity. The at least one paging message may comprise at least one of a UE identifier of the wireless device, a UE paging identifier associated with the RAN paging procedure for the wireless device, a paging DRX information for transmission of radio paging indication to the wireless device (e.g. the at least one second base station may transmit a paging message via a radio interface based on the paging DRX information indicating when the wireless device monitors radio signaling), RAN paging area information of a RAN paging area (e.g. RAN notification area, RAN area identifiers, cell identifiers associated with the RAN paging procedure), a RAN paging priority, and/or the like. In an example, the at least one second base station may serve at least one cell associated with the RAN paging area (e.g. RAN notification area(s), RAN area(s), cell(s)). In an example, when the at least one second base station receives the at least one RAN paging message, the at least one second base station may transmit/broadcast/multicast one or more paging indications via one or more cells associated with the RAN paging area (e.g. RAN notification area(s), RAN area(s), cell(s)) for the wireless device. The one or more paging indications may be transmitted via one or more beams of the one or more cells. In an example, the first base station may transmit the at least one RAN paging message (e.g. RRC paging indication) via its one or more serving cells associated with the RAN paging area of the wireless device In an example, the first base station may determine a failure of the RAN paging procedure in response to not receiving a response of the at least one RAN paging message. In an example, the first base station may determine the failure based on no response for the at least one RAN paging message within a certain time period. When the first base station receives a message indicating a UE context retrieve request for the wireless device from at least one of the at least one second base station in response to the at least one RAN paging message, the first base station may consider the RAN paging procedure is successful (e.g. not failed). When the first base station receives a random access preamble and/or a RRC connection resume request message from the wireless device in response to the at least one RAN paging message, the first base station may consider the RAN paging procedure is successful (e.g. not failed). In an example, the first base station may send, to a second core network entity, a first message in response to the failure of the RAN paging procedure. In an example, the second core network entity may be a control plane core network entity (e.g. AMF). The first message, for example, may comprise a UE context release request message and/or a RAN paging failure indication message. In an example, the first message may indicate a RAN paging failure for the wireless device. In an example, the first message may be a UE context release request message comprising a cause information element indicating that a reason of a UE context release request comprises a failure of a RAN paging procedure for the wireless device. In an example, the second core network entity may transmit, to one or more base stations of a tracking area of the wireless device, one or more core network paging messages (e.g. tracking area paging message) in response to the first message. The one or more base station may comprise a third base station. The third message may transmit paging messages via one or more serving cells of the tracking area, and may receive a response for at least one of the paging message from the wireless device. The response may comprise a random access preamble and/or a RRC connection request/resume message. In an example, the one or more core network paging messages and/or the paging messages may comprise an indication parameter indicating that the wireless device is in an RRC inactive state or that a RAN paging procedure for the wireless device was failed. In an example, the one or more core network paging messages and/or the paging messages may comprise an indication parameter indicating that an anchor base station (e.g. the first base station) has a UE context of the wireless device. In an example, the indication parameter may comprise a resume identifier (ID) of the wireless device for the RRC inactive state. In response to receiving the response from the wireless device, the third base station may transmit a tunnel endpoint identifier (e.g. tunnel identifier) of a tunnel for data forwarding to the second core network entity. The data forwarding may comprise transmitting the one or more packets from the first base station to the third base station. The tunnel endpoint identifier may comprise an IP address of the third base station. The tunnel may comprise a logical IP tunneling between the first base station and the third base station. The transmitting of the tunnel endpoint identifier may be based on the indication parameter (of the one or more core network paging messages) indicating that an anchor base station (e.g. the first base station) has a UE context of the wireless device. In an example, the first base station may receive, from the second core network entity and in response to the first message, a second message comprising the tunnel endpoint identifier of the third base station for forwarding the one or more packets. In an example, the second message may comprise a UE context release request complete message (e.g. a response message for the UE context release request message) and/or a path switch message. In an example, the first base station may send, to the third base station, the one or more packets based on the tunnel endpoint identifier. The third base station may forward the one or more packets to the wireless device via a radio interface. In an example, the sending of the one or more packets from the first base station to the third base station may employ a GTP-U protocol. In an example, the first base station may send a packet sequence number (e.g. PDCP packet sequence number) for a packet reordering at the third base station and/or at the wireless device. In an example embodiment, the first base station may forward the one or more packets to a new serving base station (e.g. the third base station) of the wireless device when the RAN paging procedure for transmission of the one or more packets is failed. The example embodiment may enhance transmission reliability of packets (e.g. data packets and/or control plane packets, NAS messages) for an RRC inactive state wireless device and/or an RRC idle state wireless device by enabling forwarding downlink packets received by an anchor base station to a new serving base station. In an example embodiment, there is a need to implement processes for transmitting downlink packets to a wireless device in an RRC inactive state when RAN paging process fails. Example embodiments describe how a base station initiates a core network paging procedure and forwards downlink packets to a new base station that receives a response to a paging message of the core network paging procedure from the wireless device when the base station fails to complete an RNA paging procedure for downlink packets. In an example, there may be two potential options to transmit one or more downlink packets to a wireless device in an RRC inactive state: paging in an RNA along with the wireless device (OPTION1), and/or transmitting after the wireless device is located (OPTION2). OPTION1 benefit from lower latency at the cost of more radio resource since data is transmitted in all cells in RNA. From the power consumption point of view, other wireless devices in RRC inactive state in the same paging occasion may have to decode more data to check if it is the target UE. As for OPTION2: The anchor gNB (base station) with connection to the CN should initiate paging in the whole RAN based area. The one or more downlink packets may be only transmitted after UE response to save air resources. In legacy LTE, UE may send paging response via random access procedure carrying RRC messages (RRC request/RRC resume) to identification and initiate protocol setup/resume, asFIG.7illustrated. In legacy system, 4 steps RA may be needed to identify the UE identity and RRC messages may be involved as well. For small data transmitting case, legacy procedure may be not efficient in terms of signalling overhead and latency. In this case, RRC messages may be used for 3 main reasons: 1). UE resolution. 2). Configure related parameters/protocols 3) state transit to Connected for better scheduling data. Since UE in inactive state has already stored AS contexts and DL data packet size is limited, while UE resolution can be handled by other schemes, direct small data transmitting without RRC message involvement may be possible for inactive state. For example, as illustrated inFIG.8, such procedure may significantly reduce signalling overhead and latency. In an example, paging may carry the message indicating direct small data transmission in inactive other than state transition which may make difference on UE behaviors. A UE receiving the paging may send UE ID on pre-configured contention based resources (e.g. grant free/preamble+UE ID, wherein UE ID used here may be valid at least in RAN notification area). The gNB receiving may confirm the UE location upon the reception of UE ID, and then, if needed, may fetch the UE context and schedule DL data transmission on a pre-configured receiving window along with UL grant for ACK. Latency may be further reduced by forwarding UE context along with paging message on Xn interface. Acknowledgement may be sent using UL grant received. If the UE position is known at cell level, direct DL transmission without paging may be considered. Since the UE may be monitoring paging, one possibility may be to schedule data transmission with unique UE ID directly during a UE paging occasion. UE ID may be S-TMSI/long UE ID valid in RAN notification area or C-RNTI in INACTIVE state. If DL data is scheduled based on common RNTI and long UE ID is indicated in MAC CE then other INACTVE UEs receiving the data may need to further check long UE ID, it may require more potential power consumption. If there is valid C_RNTI then C-RNTI may be preferred which may be similar as UMTS CELL_FACH. Upon data reception, the UE may need to send feedback to RAN side. The data transmission may include an indication whether the UE continues monitor PDCCH for subsequent data reception or not. If the UE does not monitor PDCCH subsequently, the network may wait until the next paging occasion to send data. Using UL based mobility, the network may have enough information so that, instead of paging the UE in one or multiple cell, a dedicated transmission to the UE may be possible, even using beam forming, which greatly may enhance transmission efficiency. For a UE with DL based mobility, i.e. cell reselection, the time interval since last interaction between the UE and the network may be considered. If interactions are frequent, e.g. when DL acknowledgement arrives soon after UL transmission, the network may assume that the UE is still camping on the same cell. DL data may be forwarded directly to this cell to be transmitted. If ACK is not received, then the network may forward the information to its neighbors or start paging. In an example, when a wireless device is in an RRC inactive state, a core network entity may transmit downlink packets for the wireless device to an anchor base station, which has a wireless device context of the wireless device, and the anchor base station may initiate an RNA paging procedure to forward the downlink packets. In an example, the downlink packets may require an RRC connected state of the wireless device, and/or may be transmitted to the wireless device staying in the RRC inactive state. The RNA paging procedure may comprise transmitting a first RNA paging message to a plurality of base stations belonging to an RNA associated with the wireless device by the anchor base station and/or broadcasting a second RNA paging message via a radio interface by base stations that receives the first RNA paging message. In an example, if the wireless device receives the second RNA paging message, it may transmit a first RNA paging response to the base station that transmitted the second RNA paging message. After receiving the first RNA paging response, the base station may transmit a second RNA paging response to the anchor base station. In an example, the first RNA paging message may comprise at least one of an RNA identifier, an AS context identifier, a wireless device identifier, and/or a reason of the RNA paging. A base station receiving the first RNA message may broadcast/multicast the second RNA paging message in one or more beam coverage area and/or in one or more cell coverage area at least based on the RNA identifier. In an example, the second RNA paging message may comprise at least one of an AS context identifier, a wireless device identifier, and/or a reason of the RNA paging. The wireless device, which is a target of the RNA paging, may recognize the second RNA paging message based on at least one of the AS context identifier and/or a wireless device identifier, and may perform a random access procedure to transmit the first RNA paging response at least based on the reason of the RNA paging, wherein the random access procedure may be one of a 2-stage random access and/or a 4-stage random access. In an example, the first RNA paging response may comprise an RRC connection request. In an example, the second RNA paging response may comprise a wireless device context fetch request. In an example, if an anchor base station does not receive a second RNA paging response after initiating an RNA paging procedure for downlink packets, the anchor base station may transmit a core network paging request message to a core network entity. The core network paging request message may be configured to initiate a core network paging procedure by the core network entity. The core network paging procedure may comprise transmitting a first core network paging message to a plurality of base stations belonging to a tracking area associated with the wireless device by the core network entity and/or broadcasting/multicasting a second core network paging message via a radio interface by base stations that receives the first core network paging message. In an example, if the wireless device receives the second core network paging message, it may transmit a first core network paging response to the base station that transmitted the first core network paging message. In an example, the first core network paging response may be one of messages of a 2-stage random access and/or a 4-stage random access procedure. In an example, the first core network paging response may comprise an RRC connection request. In an example, the first core network paging message may comprise a base station identifier of the anchor base station. A first base station receiving a first core network paging response may determine whether there is a direct interface (e.g. Xn interface) between the anchor base station and the first base station at least based on the base station identifier of the anchor base station. In an example, the first base station in response to receiving the first core network paging response may transmit a tunnel endpoint identifier of the first base station to a core network entity, and the core network entity may forward the tunnel endpoint identifier of the first base station to the anchor base station. In an example, the anchor base station may forward one or more downlink packets for the wireless device to the first base station at least based on the tunnel endpoint identifier of the first base station. In an example, the first base station may forward the one or more downlink packets to the wireless device via a radio signaling. In an example, the radio signaling may be one or more messages of a random access procedure, and/or may be a packet transmission through a radio bearer established between the first base station and the wireless device in an RRC connected state. In an example, the first base station may transmit a tunnel endpoint identifier of the first base station to the anchor base station, and the anchor base station may forward one or more downlink packets for the wireless device to the first base station at least based on the tunnel endpoint identifier. In an example, the first base station may forward the one or more downlink packets to the wireless device via a radio signaling. In an example, the radio signaling may be one or more messages of a random access procedure, and/or may be a packet transmission through a radio bearer established between the first base station and the wireless device in an RRC connected state. In an example, the first base station may transmit a first tunnel endpoint identifier of the first base station to the core network entity, and the core network entity may transmit a second tunnel endpoint identifier of a user plane core network entity to the anchor base station. In an example, the anchor base station may forward one or more downlink packets for the wireless device to the user plane core network entity at least based on the second tunnel endpoint identifier, and the user plane core network entity may forward the one or more downlink packets to the first base station at least based on the first tunnel endpoint identifier received from the core network entity. In an example, the first base station may forward the one or more downlink packets to the wireless device via a radio signaling. In an example, the radio signaling may be one or more messages of a random access procedure, and/or may be a packet transmission through a radio bearer established between the first base station and the wireless device in an RRC connected state. In an example, the tunnel endpoint identifier of the first base station may be an IP address of the first base station, and the tunnel endpoint identifier of the user plane core network entity may be an IP address of the user plane core network entity. In an example, the first base station in response to receiving the first core network paging response may transmit a wireless device context request message to the anchor base station via an Xn interface, and the anchor base station may transmit a wireless device context to the first base station. In an example, the first base station in response to receiving the first core network paging response may transmit a wireless device context request message to an anchor base station indirectly through a core network entity, and the anchor base station may transmit a wireless device context to the first base station through the core network entity. In an example, a base station may receive, from a first network entity, one or more packets for a wireless device in RRC inactive state. The first base station may perform an RNA paging procedure, comprising transmitting to one or more second base stations a first message. The first message may comprise an identifier of the wireless device. The first base station may determine that the RNA procedure is unsuccessful. The first base station may transmit, to a second network entity and in response to the determining that that the RNA paging procedure is unsuccessful, a second message, wherein the second message initiates a core network paging procedure. The first base station may receive a third message indicating a data forwarding procedure in response to the core network paging procedure determining that the wireless device may be in the coverage area of a second base station. The first base station may forward the one or more packets to the second base station. In an example, the first network entity may be the second network entity. In an example, the forwarding, by the first base station to the second base station, may employs a direct tunnel between the first base station and the second base station, and/or may transmit the one or more packets to a core network node. The first base station may transmit a PDCP sequence number of one of the one or more downlink data packets. The second message may comprise the PDCP sequence number. Example of Radio Access Network Area Information In an example embodiment, an issue with respect to exchanging an RNA information between base stations is how a base station gets an RNA information of its neighbor cells or its neighbor base stations and employs the information when the base station initiates a RNA paging procedure for a wireless device in an RRC inactive state. In an existing RAN paging procedure, a base station may configure a wireless device with one or more RAN area (e.g. RAN notification area, RAN paging area, one or more cells associated with the RAN area) for an RRC inactive state. The base station may initiate a RAN paging procedure when the base station has packets, control signaling, and/or state transition cause for the wireless device by transmitting a RAN paging message to one or more base stations. The wireless device in the RRC inactive state may receive paging indications from the one or more base stations and/or from the base station based on the one or more RAN areas. Implementation of existing signaling when paging an RRC inactive state wireless device may result in increased network resource utilization, increased paging delay, increased packet loss rate, and/or increased call drop rate due to inefficient paging procedure for a wireless device in an RRC inactive state. An existing RAN area coordination may need further enhancements in communication among network nodes (e.g. base stations, core network entity, wireless device). In an example, failure rate in transmitting a RAN paging message (e.g. for data packets, NAS/RRC signaling packets) may increase for RRC inactive state wireless devices. Increased RAN paging failure rate may degrade network system reliability. There is a need to improve backhaul signaling for RRC inactive state wireless devices. Example embodiments enhance information exchange mechanism among network nodes to improve network communication reliability and/or efficiency when a wireless device is in an RRC inactive state. Example embodiments may enhance signaling procedures for exchanging RAN area information among base stations. In an example embodiment as shown inFIG.16andFIG.17, a base station may transmit its RAN area information (e.g. RAN area identifier, RAN notification identifier, one or more cell information of a RAN area). Based on the RAN area information of neighbor base stations (or neighbor cells), a base station may enhance a RAN paging reliability for an RRC inactive state wireless device by sending a RAN paging message to neighboring base station associated with a RAN area of the RRC inactive state wireless device. Example embodiments may increase backhaul signaling efficiency by limiting a RAN paging message transmission to a corresponding base stations that is associated with a RAN area of a RAN paging target wireless device. In an example, a base station may perform an Xn setup procedure to setup an Xn interface with its neighbor base station. The Xn setup procedure may comprise a first message received by a first base station from a second base station and/or a second message transmitted by the first base station to the second base station in response to the first message. In an example, the first message may be an Xn setup request message, and the second message may be an Xn setup response message. The first message may comprise at least one of a gNB identifier of the second base station, a cell identifier of a cell served by the second base station, and/or an RNA identifier, wherein the RNA identifier may be associated with the second base station and/or a cell of the second base station. The second message may comprise at least one of a gNB identifier of the first base station, a cell identifier of a cell served by the first base station, and/or an RNA identifier associated with the first base station and/or a cell of the first base station. In an example, a base station may perform a gNB configuration update procedure to update configuration information of its neighbor base station. In an example, at least if a cell is added, modified, and/or removed in a base station, and/or if an RNA information for a base station or for a cell of a base station is changed, the base station may initiate a gNB configuration update procedure. The gNB configuration update procedure may comprise a first message received by a first base station from a second base station and/or a second message transmitted by the first base station to the second base station in response to the first message. In an example, the first message may be a gNB configuration update message, and the second message may be a gNB configuration update acknowledge message. The first message may comprise at least one of a gNB identifier of the second base station, a cell identifier of a cell served by the second base station, and/or an RNA identifier, wherein the RNA identifier may be associated with the second base station and/or a cell of the second base station. The second message may comprise an acknowledgement of the first message. In an example, the RNA identifier may comprise RAN notification area information, RAN area information (e.g. RAN area identifier), one or more cell identifiers of one or more cells associated with a RAN notification area (e.g. RAN area, RAN paging area). In an example embodiment, an RNA identifier may be identifiable globally and/or in a PLMN. In an example, an RNA identifier exchanged through an Xn setup procedure and/or a gNB configuration update procedure may be employed by a base station to determine a paging area for an RNA paging procedure, which may be used to inform a wireless device in an RRC inactive state that at least one of following events occurred: that the base station received one or more packets for the wireless device; that the wireless device is required to transition its RRC state from the RRC inactive state to an RRC idle state; and/or that that the wireless device is required to transition its RRC state from the RRC inactive state to an RRC connected state. In an example the one or more packets may comprise data packets from a user plane core network entity (e.g. UPF) and/or control signaling (e.g. NAS message) from a control plane core network entity (e.g. AMF). In an example, a base station may transmit, to a wireless device, a RAN notification area information (e.g. RAN area identifier of a RAN area, RAN paging area identifier of a RAN paging area, and/or one or more cell identifier of one or more cells of the RAN notification area, of the RAN paging area, and/or of the RAN area). The base station may indicate, to the wireless device, a state transition from an RRC connected state to an RRC inactive state by transmitting an RRC message (e.g. an RRC connection release message, an RRC connection suspend message). In an example, the RRC message may comprise the RAN notification area information for the wireless device. When the wireless device stays in the RRC inactive state, the wireless device may move around one or more cells of the RAN notification area. When the wireless device stays in the RRC inactive state, the wireless device may move out of the RAN notification area, and may initiate a RAN notification area update procedure informing, to the base station, that the wireless device moved to a different RAN notification area from the RAN notification area. The RAN notification area may comprise a RAN area of the neighboring base station, information of the RAN area received from the neighboring base station via the Xn setup request/response message and/or the gNB configuration update message. In an example, the RNA paging procedure may comprise transmitting a first RNA paging message by a first base station to a plurality of second base stations belonging to an RNA associated with the wireless device and/or broadcasting/multicasting a second RNA paging message via a radio interface by a plurality of the second base stations that receives the first RNA paging message, wherein the first base station may be an anchor base station of the wireless device. In an example, if the wireless device receives the second RNA paging message, it may transmit a first RNA paging response to the base station that it received the second RNA paging message from. After receiving the first RNA paging response, the base station may transmit a second RNA paging response to the first base station, an anchor base station of the wireless device. In an example, the second RNA paging response may comprise a wireless device context request. In an example embodiment, during an RNA paging procedure, a first RNA paging message transmitted from a first base station to a plurality of second base stations may comprise at least one of an identifier of a wireless device, an AS context identifier for a wireless device, an RNA identifier, and/or a reason of the RNA paging for the wireless device to notify a plurality of second base station of at least one of downlink packets for the wireless device, an RRC state transition required from an RRC inactive state to an RRC idle state, and/or an RRC state transition required from an RRC inactive station to an RRC connected state. In an example, a first RNA paging message may be transmitted to one or more base stations that serve at least one cell belonging to an RNA associated with a wireless device, a target device of an RNA paging procedure. The first base station may determine the one or more base stations (e.g. RAN paging target base station) based on the RNA information received from the one or more base stations. In an example, when the RNA information comprises a cell and/or a RAN area that was configured to the wireless device (e.g. when transitioning an RRC state to the RRC inactive state), the first base station transmit an RAN paging message to a base station that transmitted the RNA information. In an example embodiment, during an RNA paging procedure, a second RNA paging message broadcasted/multicasted by a second base station may comprise at least one of an AS context identifier for a wireless device, an identifier of a wireless device, and/or a reason of the RNA paging to notify the wireless device of at least one event of downlink packets for the wireless device, an RRC state transition required from an RRC inactive state to an RRC idle state, and/or an RRC state transition required from an RRC inactive station to an RRC connected state. In an example, a second RNA paging message may be broadcasted and/or multicasted in a coverage area of the second base station, in a coverage area of a cell belonging to an RNA, and/or a coverage area of a beam of a cell belonging to an RNA. In an example embodiment, after an RNA paging procedure, if an anchor base station receives a second RNA paging response from a base station that received a first RNA paging response from a wireless device in an RRC inactive state, which is a target device of the RNA paging procedure, the anchor base station may forward one or more packets to the base station that transmitted the second RNA paging response in case that the reason of the RNA paging is to transmit the one or more packets for the wireless device. In an example, the second RNA paging response may comprise a UE context retrieve request message for the wireless device. In an example, the second RNA paging response message may comprise a resume identifier for the wireless device, and the anchor base station may retrieve a UE context based on the resume identifier. In an example, the first RNA paging response may comprise a RRC context resume/setup request message. The first RNA paging response may comprise the resume identifier of the wireless device for the RRC inactive state. The base station receiving the first RNA paging response may identify the anchor base station based on the resume identifier, and may transmit the second RNA paging response message. In an example, the anchor base station receiving the second RNA paging response may release a UE context of the wireless device in case that the reason of the RNA paging procedure is to initiate an RRC state transition of the wireless device. If the RRC state transition is transitioning to an RRC connected state, the anchor base station may transmit one or more elements of the UE context of the wireless device to the base station that transmitted the second RNA paging response before release the UE context. If the RRC state transition is transitioning to an RRC idle state, the anchor base station may release the UE context without transmitting at least one element of the UE context to a base station. In an example, a first base station may receive, from a second base station, a first message comprising a first radio access network notification area (RNA) identifier associated with the second base station. The first base station may transmit to the second base station a second message comprising an identifier of a wireless device when the first base station is also associated with the first RNA identifier. In an example, a first base station may receive, from a second base station, a first message comprising a first radio access network notification area (RNA) identifier associated with the second base station. The first base station may transmit to a wireless device, one or more third messages comprising radio configuration parameters, wherein the radio configuration parameters may comprise the RNA identifier, and the wireless device may be in a radio resource control (RRC) connected state. The first base station may initiate a procedure to transition the wireless device from the RRC connected state to an RRC inactive state. The first base station may transmit to the second base station a second message comprising an identifier of the wireless device when the first base station is also associated with the first RNA identifier, wherein the wireless device may be in a radio resource control (RRC) inactive state and configured with the first RNA identifier. The second message may be configured to initiate broadcasting and/or multicasting, by the second base station, a third message comprising an indication. The second message may be configured to initiate broadcasting or multicasting, by the second base station and in a coverage area or a beam area of the second base station, a third message comprising an indication. In an example, the second message may be a paging message. The indication may be a paging indication. The first base station may further transmit to one or more third base stations one or more third messages comprising the identifier of the wireless device. The indication may be configured to cause the wireless device to change from an RRC inactive state to an RRC idle state. The indication may be configured to cause the wireless device to change from an RRC inactive state to an RRC connected state. The indication may indicate one or more downlink data packets for the wireless device. The wireless device and/or at least one base station may release a wireless device context. The second base station may receive a fourth message comprising an RRC connection request from the wireless device. The second base station may transmit, to the first base station, a fifth message comprising a request of a wireless device context for the wireless device. The second base station may receive a sixth message comprising the wireless device context from the first base station. In an example, at least one base station may have a wireless device context of the wireless device in an RRC inactive station, and the wireless device may have no RRC connection with the at least one base station having the wireless device context. A wireless device context may comprise at least one of a bearer configuration information, a logical channel information, a security information, a PDCP configuration information, AS context, and one or more parameters for the wireless device. The RNA identifier may be associated with a cell of the second base station. The first base station may be also associated with the first RNA identifier when at least one cell in the first base station is associated with the first RNA identifier. The first base station may be associated with a plurality of RNA identifier. The first base station may transmit a message comprising the first RNA identifier to the second base station. The first base station may transmit the second message in response to receiving at least one data or control packet from a core network entity. The first base station may receive a message from a network entity comprising the first RNA identifier. Example of Radio Access Network Paging Area Configuration In an example embodiment, an issue with respect to determining an area for an RNA paging is how a base station transmits a paging message to a wireless device in an RRC inactive state by broadcasting a paging message in a limited area for signaling efficiency. In an existing RAN paging procedure, base stations exchanges backhaul signaling to transmit a downlink packets to a wireless device in an RRC inactive state. A base station may transmit paging messages via its cells and/or to its neighboring base stations of a RAN notification area associated with the wireless device. Implementation of existing backhaul signaling may result in increased network resource utilization due to inefficient RAN paging message transmission. An inefficient RAN paging procedure may need further enhancement in communication and/or controlling mechanism of network nodes (e.g. base stations, core network entity, and wireless device). In an example, increased signaling load for RAN paging procedure to wake up an RRC inactive state wireless device may increase backhaul signaling delay and may decrease signaling reliability. Increased packet loss rate caused due to signaling overhead may degrade network system reliability. There is a need to improve backhaul signaling mechanism of a RAN paging procedure for RRC inactive state wireless devices. Example embodiments enhance RAN paging mechanism by enabling a base station to employ a time duration since a signaling with a RAN paging target wireless device in an RRC inactive state, in selecting a RAN paging target base station. In an example, by transmitting a RAN paging message to a neighbor base station that communicated with the wireless device recent, a base station may avoid unnecessary signaling for RAN paging messages to other base stations, which are unlikely to be selected by the RAN paging target wireless device. In an example embodiment as shown inFIG.18andFIG.19, a base station (e.g. an anchor base station, gNB) may determine a time duration between receiving/transmitting recent packets from/to a wireless device and receiving packets from a core network entity (e.g. AMF) for the wireless device. In an example, the packets form the core network entity may cause the base station initiates a RAN paging procedure. Based on the time duration, the base station may select a target base station to which the base station transmits a RAN paging message for the wireless device. In an example, when the time duration is smaller than and/or equal to a first time value, the base station may transmit a RAN paging message to a second base station that sent/received the recent packets to/from the base station. In an example, when the time duration is larger than the first time value, the base station may transmit RAN paging messages to third base stations belonging to a RAN notification area associated with the wireless device. In an example, the third base stations may comprise the second base station. In an example, as shown inFIG.20andFIG.21, if the base station receives/transmit recent packets from the wireless device via its cell, the base station may transmit RAN paging messages (e.g. radio interface paging) via its cell when the time duration is smaller than and/or equal to a first time value, and the base station may transmit RAN paging messages to second base stations belonging to a RAN notification area associated with the wireless device when the time duration is larger than the first time value. In an example embodiment, by limiting a RAN paging area based on a time duration since a recent communication with a wireless device, a base station may reduce signaling overhead for unnecessary RAN paging message transmissions. In an example embodiment, a first base station may determine a paging area for an RNA paging procedure and/or a core network paging procedure targeting a wireless device in an RRC inactive state at least based on a time duration between a latest signaling with the wireless device and an occurrence of an event requiring a paging message transmission, and the first base station may transmit a paging message in the determined paging area. A first paging timer may be configured in the base station. The base station may restart the first paging timer in response to receiving and/or transmitting a paging message and/or a pre-defined signaling between the first base station and wireless device (e.g. uplink data transmission, random access preamble, downlink data transmission, ACK, etc.). For example, the base station may consider a previous location of the wireless device if the paging process is started when the first paging timer is running. The base station may page the wireless device in the RNA area or core TA area when the paging process starts after the timer is expired. In an example, a first base station may determine a paging area based on at least one of a moving speed of a paging target wireless device, a service type (e.g. a logical channel type, a bearer type, a slice type, and etc.) of a paging target wireless device, a subscription information of a paging target wireless device, a establish cause of a paging target wireless device, a mobility information of a paging target wireless device, and/or a mobility estimation information of a paging target wireless device. In an example, the determined paging area may be at least one of one or more base stations in an RNA, one or more cells of a base station in an RNA, and/or one or more beams of a cell operated by a base station in an RNA. In an example, if the determined paging area completely or partially belongs to coverage areas of one or more second base stations, the first base station that determined the paging area may transmit a first paging message to the one or more second base stations, and the one or more second base stations may broadcast and/or multicast a second paging message in their coverage area. In an example, if the determined paging area completely or partially belongs to a coverage area of the first base station that determined the paging area, the first base station may broadcast and/or multicast a second paging message in its coverage area. In an example, if the determined paging area only belongs to a coverage area of the first base station, the first base station may not transmit a first paging message. In an example, if the determined paging area belongs to a coverage area of a first cell of the first base station, the first base station may broadcast and/or multicast a second paging message in the first cell. In an example, if the determined paging area belongs to a coverage area of a first beam in a first cell of the first base station, the first base station may broadcast and/or multicast a second paging message in the first beam. In an example, the first paging message transmitted from the first base station to the one or more second base stations may comprise at least one of a wireless device identifier of a wireless device targeted for a paging and/or an RNA identifier, and the second paging message broadcasted and/or multicasted by the first base station and/or the one or more second base stations may comprise the wireless device identifier. In an example, a base station receiving the first paging message with an RNA identifier may broadcast and/or multicast the second paging message in a coverage area of a cell associated with an RNA identified by the RNA identifier. In an example, the latest signaling with the wireless device may be a signaling message transmitted for at least following procedures: a random access procedure for uplink and/or downlink packet transmission for the wireless device (e.g. data and/or control packets), a uplink and/or downlink packet transmission and/or acknowledge signaling, an RNA update and/or tracking area update procedure initiated by the wireless device, an RRC state transition from an RRC connected state to the RRC inactive state, and/or a paging and/or response procedure. In an example, the event requiring a paging message transmission may be one of at least following events: a downlink packet reception for the wireless device (e.g. data and/or control packets), an event requiring an RRC state transition of the wireless device to an RRC connected state (e.g. receiving one or more downlink packets for a service requiring an RRC connected state, receiving a command from a core network entity that requests an RRC connected state of the wireless device, a timer expiration for an RRC inactive state, a high load of random access procedure attempts, and/or other abnormal events), and/or an event requiring an RRC state transition of the wireless device to an RRC idle state (e.g. receiving a command from a core network entity that requests an RRC idle state of the wireless device, a timer expiration for an RRC inactive state, a high load of random access procedure attempts, and/or other abnormal events). In an example, the random access procedure for uplink and/or downlink packet transmission may be initiated by a wireless device in an RRC inactive state at least when its buffer has one or more packets to transmit and/or when the wireless device receives a paging message for one or more downlink packets from a base station. In an example, the random access procedure may be performed with two messages (e.g. 2-stage random access) and/or four messages (e.g. 4-stage random access). In a 2-stage random access procedure, a first message may be transmitted by a wireless device to a base station, and the first message may comprise at least one of a random access preamble and/or one or more uplink packets. A second message of the 2-stage random access procedure may be transmitted to the wireless device by the base station receiving the first message, and the second message may comprise an acknowledgement of a reception of the one or more uplink packets. In an example, the second message of the 2-stage random access procedure may further comprise a resource grant for further uplink packet transmission, and the wireless device may transmit a third message comprising one or more packets at least based on the resource grant. The base station receiving the third message may transmit an acknowledgement and/or further resource grant for further uplink packet transmission. In an example, further resource grants by the base station and associating uplink packet transmissions by the wireless device may be continued through further messages. In a 4-stage random access procedure, a first message may be transmitted by a wireless device to a base station, and the first message may comprise at least one of a random access preamble and/or one or more uplink packets. A second message of the 4-stage random access procedure may be transmitted to the wireless device by the base station receiving the first message, and the second message may comprise a resource grant for uplink packet transmission. A third message of the 4-stage random access procedure may be transmitted by the wireless device to the base station at least based on the resource grant in the second message, and may comprise one or more uplink packets. A fourth message transmitted by the base station to the wireless device may comprise an acknowledgement of a reception of the one or more uplink packets. In an example, the fourth message of the 4-stage random access procedure may further comprise a further resource grant for further uplink packet transmission, and the wireless device may transmit a fifth message comprising one or more packets at least based the further resource grant in the fourth message. The base station receiving the fifth message may transmit an acknowledgement and/or further resource grant for further uplink packet transmission. In an example, further resource grants by the base station and associating uplink packet transmissions by the wireless device may be continued through further messages. In an example, the RNA update procedure may be initiated by a wireless device in an RRC inactive state at least when the wireless device selects a cell belonging to a new RNA and/or when a time threshold for a periodic RNA update is expired. In an example, a base station may configure a wireless device to perform an RNA update periodically when the time threshold is expired. In an example, a cell may broadcast one or more RNA identifier for one or more RNA associated with the cell, and a wireless device may determine whether one of the broadcasted one or more RNA identifier is same to its RNA identifier assigned in at least one of a cell in which the wireless device performed the latest RNA update procedure, a cell in which the wireless device performed the latest uplink and/or downlink packet transmission, and/or a cell in which the wireless device was in an RRC connected state most recently. In an example, the RNA update procedure may comprise at least one of a random access procedure initiated by a wireless device in an RRC inactive state, a wireless device context fetch procedure initiated by a new base station, a path switch procedure initiated by a new base station, and/or storing a RNA identifier of a new RNA by a wireless device. In an example, the wireless device context fetch procedure may comprise requesting, by the new base station to an old anchor base station of a wireless device, a wireless device context for the wireless device initiating the RNA update procedure, and/or receiving, by the new base station from the old anchor base station, the wireless device context. In an example, the wireless device context may comprise at least one of an AS context, a bearer configuration information, a security information, a PDCP configuration information, and/or other configuration information for the wireless device. In an example, the path switch procedure may comprise requesting, by the new base station to a core network entity, to update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity and a RAN node (e g changing a downlink tunnel endpoint identifier from an address of the old anchor base station to an address of the new base station). In an example, the tracking area update procedure may be initiated by a wireless device in an RRC inactive state (and/or in an RRC idle state) at least when the wireless device selects a cell belonging to a new tracking area and/or when a time threshold for a periodic tracking area update is expired. In an example, a core network entity may configure a wireless device to perform a tracking area update periodically when the time threshold is expired. In an example, a cell may broadcast one or more tracking area identifier for one or more tracking area associated with the cell, and a wireless device may determine whether one of the broadcasted one or more tracking area identifier is same to its tracking area identifier assigned in at least one of a cell in which the wireless device performed the latest tracking area update procedure, (a cell in which the wireless device performed the latest uplink and/or downlink packet transmission,) and/or a cell in which the wireless device was in an RRC connected state most recently. In an example, the RRC state transition from an RRC connected state to the RRC inactive state may be completed by a first RRC message transmitted by a base station to a wireless device in an RRC connected state. The first RRC message may comprise a command for the RRC state transition of the wireless device. In an example, the wireless device may transmit an acknowledgement via a second RRC message, a MAC layer message, and/or a physical layer message. In an example, the paging and response procedure may comprise a paging message broadcasted/multicasted by a base station for an RNA paging and/or a core network paging, and/or a random access procedure. The random access procedure may be a 2-stage random access procedure and/or a 4-stage random access procedure. In an example, the downlink packet reception for the wireless device may be a reception of one or more packets for the wireless device from a core network entity and/or an anchor base station. The downlink packet reception for the wireless device may require an RNA paging procedure. In an example, a base station that received the one or more packets may measure a time duration from a latest signaling with the wireless device and an occurrence of the downlink packet reception, and may determine a paging area for an RNA paging. In an example, the event requiring an RRC state transition of the wireless device to an RRC connected state in a base station may be at least one of receiving one or more downlink packets for the wireless device, receiving an RRC state transition request for the wireless device from a core network entity, and/or a decision by the base station of the RRC state transition. In an example, the base station may measure a time duration from a latest signaling with the wireless device and an occurrence of the event requiring an RRC state transition, and may determine a paging area for an RNA paging and/or a core network paging. In an example, the event requiring an RRC state transition of the wireless device to an RRC idle state in a base station may be one of receiving an RRC state transition request for the wireless device from a core network entity and/or a decision by the base station of the RRC state transition. In an example, the base station may measure a time duration from a latest signaling with the wireless device and an occurrence of the event requiring an RRC state transition, and may determine a paging area for an RNA paging and/or a core network paging. In an example, a first base station may receive or transmit a first message associated with a wireless device in an RRC inactive state. The first base station may determine which selected base station is selected by the wireless device. The first base station may receive, from a core network node, a downlink data packet for the wireless device. The first base station may determine whether a time duration between a reception of the first messages and a reception of the downlink data packet is smaller than a first time period. When the first base station is the same as the selected base station and when the determination indicates the time duration is smaller than the first time period, the first base station may transmit one or more second messages comprising at least one of a downlink data indication and at least one of the one or more downlink data packets. In an example, when the first base station is the same as the selected base station and when the determination indicates the time duration is not smaller that the first time period, the first base station may transmit, to a plurality of base stations, one or more third messages comprising an indication of a downlink data. When the first base station is different from the selected base station and when the determination indicates the time duration is smaller than the first time period, the first base station may transmit, to a second base station, one or more second messages comprising at least one of a downlink data indication and at least one of the one or more downlink data packets. When the first base station is different from the selected base station and when the determination indicates the time duration is not smaller that the first time period, the first base station may transmit, to a plurality of base stations, one or more third messages comprising an indication of a downlink data. In an example, the first message may be at least one uplink signaling transmission of: an uplink data transmission procedure in the RRC inactive state, a downlink data transmission procedure in the RRC inactive state, an RNA update procedure, and/or a procedure of an RRC state transition from an RRC connected state to the RRC inactive state. The first time period may be defined at least based on a moving speed of the wireless device. The limited area may be determined at least based on one of: a moving speed of the wireless device, a size of the cell where the one or more first messages were transmitted, and/or a size of the beam area where the one or more first messages were transmitted. At least one base station may have a UE context of the wireless device in the RRC inactive state, and the wireless device in the RRC inactive state may not have an RRC connection with the at least one base station having the UE context. Example of Cell Selection of Inactive State Wireless Device In an example embodiment, an issue with respect to selecting a cell by a wireless device in an RRC inactive state or an RRC idle state is how a wireless device determines a cell that supports a service that the wireless device may likely receive, the determination to reduce further signaling to assign a cell providing the service. In an existing network mechanism, a wireless device being in an RRC inactive state may select/reselect cell to camp on based on a received power and/or quality from one or more cells. The wireless device may employ a certain type of services (e.g. network slice, bearer, logical channel, QoS flow, PDU session). In an example, a cell may not support a specific type of services. For example, a cell may support different types of numerologies, TTIs, subcarrier spacing configurations, and/or licensed/unlicensed spectrums. The different types of numerologies, TTIs, subcarrier spacing configurations, and/or licensed/unlicensed spectrums may be employed for a specific type of services. In an example, a small TTI configuration may support a URLLC type service (network slice) for a low latency requirement, and/or an unlicensed spectrum may not support the URLLC type service due to its less reliability. In an example, some limited cells may support a configured grant type1(e.g. grant-free uplink resources), which may be required for a URLLC services and/or an IoT (e.g. MTC) service. In an example, if a wireless device select/reselect a cell that does not support a service type required by the wireless device, the wireless device may require increased signaling with a base station to reselect a cell supporting the service type and/or to perform a handover or a secondary cell addition procedure to employ a cell supporting the service type. The increased signaling caused by selecting a cell that does not support a required service type may increase communication delay, packet loss, and/or communication reliability. Example embodiment enhance a cell selection/reselection procedure by enabling a base station to configure associations between a cell (e.g. cell type, registration area, numerology, TTI, subcarrier spacing, spectrum band) and a service type (e.g. network slice, bearer, logical channel, QoS flow, PDU session) for a wireless device in an RRC inactive state (and/or an RRC idle state). In an example, in an RRC idle state, a wireless device may not have a logical channel (and/or a bearer) activated, and the wireless device may need a RRC connection to transmit/receive data for a service. Unlike the RRC idle state, in an RRC inactive state, a wireless device may be configured with one or more logical channels (and/or one or more bearers), and the wireless device may have a configured buffer to queue packets associated with the one or more logical channels in the RRC inactive state (without transitioning to an RRC connected state). In an example embodiment, as shown inFIG.22,FIG.23, andFIG.24, a cell may or may not support a service to a wireless device. The service may be associated with at least one of a logical channel, a bearer, a slice, a UE type, and/or a categorized type for packet transmission. In an example, a base station may configure a wireless device to employ one or more cells and/or cell types to transmit a packet for a logical channel. The configuration may be provided to the wireless device via one or more dedicated RRC messages and/or one or more broadcasted/multicasted system information messages. In an example, a base station may broadcast/multicast a cell identifier and/or a cell type information via a system information message of a cell. In an example, a cell of a base station may broadcast/multicast a restricted and/or allowed service list (e.g. a logical channel type list, a bearer type list, and/or a slice list). In an example, the wireless device in an RRC inactive state and/or an RRC idle state may select a cell, at least based on the broadcasted/multicasted information by a cell, for at least one of purposes: to receive a paging message for an RNA paging and/or a core network paging (e.g. a tracking area paging) for reception of one or more downlink packets and/or an RRC state transition command, to transmit one or more uplink packets, and/or to initiate an RRC state transition to an RRC connected state. In an example, when the wireless device in an RRC inactive state gets data for a first logical channel (e.g. first bearer) in corresponding buffer, the wireless device may select/reselect a cell configured, by a base station, for the first logical channel (or the first bearer), and may transmit the data to the base station via the cell. In an example, when the wireless device in an RRC inactive state gets data for a first service type (e.g. first network slice) in corresponding buffer, the wireless device may select/reselect a cell configured, by a base station, for the first service type (or the first network slice), and may transmit the data to the base station via the cell. The cell may be configured as a registration area, a cell type (e.g. numerology, TTI, subcarrier spacing, spectrum band), and/or the like. In an example, a wireless device may receive/transmit, from/to a base station, one or more packets via one or more logical channels and/or one or more bearers for one or more services. When a base station establishes a radio bearer and/or a logical channel for a wireless device, the base station may provide, to the wireless device, a list of cells and/or cell types that may be employed to transmit one or more packets associated with a logical channel and/or a bearer. In an example, if the wireless device is in an RRC connected state, the list of cells and/or cell types for a logical channel and/or a bearer may be transmitted via one or more RRC message. In an example, the list of cells and/or cell types for a logical channel and/or a bearer may be transmitted via one or more MAC CEs. In an example, a cell may broadcast/multicast a list of one or more restricted and/or allowed logical channel types, bearer types, and or slice types, wherein the list may be transmitted via one or more system information messages. In an example, a wireless device in an RRC inactive state may select a cell to further receive an RNA paging message or a core network paging message. The RNA paging message or the core network paging message may be transmitted by a base station to transmit one or more downlink packets to the wireless device, the one or more downlink packets associated with a logical channel and/or a bearer. If the wireless device selects a cell that does not support the logical channel and/or the bearer, a base station may assign another cell to the wireless device to transmit the one or more downlink packets after the wireless device response to the paging message. In an example, if the wireless device selects a cell that may support the logical channel and/or the bearer, the base station may not need to assign another cell to transmit the one or more downlink packets. In an example, if a first logical channel and/or bearer is established for a wireless device and if one or more cells and/or cell types are configured by a base station for the first logical channel and/or bearer, the wireless device in an RRC inactive state may select one of the one or more cells and/or cell types for further downlink packet reception associated with the first logical channel and/or bearer at least based on a broadcasted/multicasted cell identifier and/or cell type in a cell. In an example, the wireless device may not select a cell where the first logical channel and/or bearer is associated with a list of one or more restricted logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, the wireless device may select a cell where the first logical channel and/or bearer is associated with a list of one or more allowed logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, a wireless device in an RRC idle state may select a cell to further receive a core network paging message. The core network paging message may be transmitted by a base station to transmit one or more downlink packets to the wireless device, the one or more downlink packets associated with a logical channel type and/or a bearer type. In an example, if a wireless device in an RRC idle state selects a cell that may support the logical channel and/or the bearer for a service that the wireless device may receive, a base station may not need to assign another cell to transmit the one or more downlink packets after the wireless device response to a core network paging message. In an example, if one or more cells and/or cell types are configured by a base station for a first logical channel type and/or bearer type, the wireless device after transitioning to an RRC idle state may select one of the one or more cells and/or cell types for further downlink packet reception associated with the first logical channel type and/or bearer type at least based on a broadcasted/multicasted cell identifier and/or cell type in a cell. In an example, the wireless device may not select a cell where the first logical channel type and/or bearer type is associated with a list of one or more restricted logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, the wireless device may select a cell where the first logical channel type and/or bearer type is associated with a list of one or more allowed logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, a wireless device in an RRC inactive state may select a cell to further transmit one or more uplink packets to a network. In an example, a wireless device may transmit one or more uplink packets to a base station via one or more random access procedure in a selected cell, the one or more uplink packets associated with a logical channel and/or a bearer. If the wireless device selects a cell that does not support the logical channel and/or the bearer, a base station may assign another cell to the wireless device to receive the one or more uplink packets. In an example, if the wireless device selects a cell that may support the logical channel and/or the bearer, the base station may not need to assign another cell to receive the one or more uplink packets. In an example, if a first logical channel and/or bearer is established for a wireless device and if one or more cells and/or cell types are configured by a base station for the first logical channel and/or bearer, the wireless device in an RRC inactive state may select one of the one or more cells and/or cell types for further uplink packet transmission associated with the first logical channel and/or bearer at least based on a broadcasted/multicasted cell identifier and/or cell type in a cell. In an example, the wireless device may not select a cell where the first logical channel and/or bearer is associated with a list of one or more restricted logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, the wireless device may select a cell where the first logical channel and/or bearer is associated with a list of one or more allowed logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, a wireless device in an RRC inactive state and/or an RRC idle state may select a cell to initiate an RRC state transition to an RRC connected state. The wireless device may perform a random access procedure to make an RRC connection in the selected cell. After completing the RRC state transition, the wireless device may transmit and/or receive one or more packets associated with a logical channel and/or a bearer. In an example, if the wireless device selects a cell that does not support the logical channel and/or the bearer, a base station may assign another cell to the wireless device to transmit and/or receive the one or more packets after completing the RRC state transition. In an example, if the wireless device selects a cell that may support the logical channel and/or the bearer, the base station may not need to assign another cell to transmit and/or receive the one or more packets. In an example, if a first logical channel and/or bearer is established for a wireless device and if one or more cells and/or cell types are configured by a base station for the first logical channel and/or bearer, the wireless device in an RRC inactive state may select one of the one or more cells and/or cell types for further packet transmission and/or reception associated with the first logical channel and/or bearer, after completing an RRC state transition to an RRC connected state, at least based on a broadcasted/multicasted cell identifier and/or cell type in a cell. In an example, the wireless device may not select a cell where the first logical channel and/or bearer is associated with a list of one or more restricted logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, the wireless device may select a cell where the first logical channel and/or bearer is associated with of a list of one or more allowed logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, if one or more cells and/or cell types are configured by a base station for a first logical channel type and/or bearer type, the wireless device after transitioning to an RRC idle state may select one of the one or more cells and/or cell types for further packet transmission and/or reception associated with the first logical channel type and/or bearer type at least based on a broadcasted/multicasted cell identifier and/or cell type in a cell. In an example, the wireless device may not select a cell where the first logical channel type and/or bearer type is associated with a list of one or more restricted logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, the wireless device may select a cell where the first logical channel type and/or bearer type is associated with a list of one or more allowed logical channel types, bearer types, and or slice types at least based on broadcasted/multicasted information from a cell. In an example, a wireless device may receive, from a base station, a first messages comprising configuration parameters, wherein the configuration parameters may indicate association of a bearer or logical channel with one or more cells for the wireless device in a RRC connected state. The wireless device may receive, from a base station, a second message comprising an RRC state transition command configured to cause an RRC state transition of the wireless device from the RRC connected state to an RRC inactive state. The wireless device in the RRC inactive state may select a first cell at least based on one or more criteria, wherein the one or more criteria may employ at least the configuration parameters. The wireless device may transmit to the base station a random access preamble message via the first cell. The wireless device in the RRC connected state may have an RRC connection with at least one base station. When the wireless device is in the RRC inactive state, at least one base station may have a wireless device context of the wireless device, and/or the wireless device may not have an RRC connection with the at least one base station having the wireless device context. The wireless device context may comprise at least one of a bearer configuration information, a logical channel information, a security information, an AS context, a PDCP configuration information, and other information for the wireless device. The transmitting the random access preamble message may be in response to at least one of the following: an uplink buffer including one or more data packets, the wireless device receiving a paging indication, and/or the wireless device detecting moving to a new RNA or TA. The association of the bearer or logical channel with one or more cells may comprise association of the bearer or logical channel with a cell type and/or cells in a frequency band. Example of Radio Access Network Notification Area Update Failure Example embodiments provide methods and system for determining a periodic RNA update failure in a base station and a wireless device. Example embodiment provides mechanisms for a base station to transmit a notification of the failure to a core network entity. Example embodiment provides processes in a wireless device when a periodic RNA update process fails. In an existing RAN notification area update (RNAU) procedure, base station(s) and/or a wireless device may exchange signaling to update a location information of the wireless device being in an RRC inactive state. A wireless device may transmit a RNAU indication to a base station to update its RAN notification area, which may be employed by the base station (e.g. anchor base station) to page the wireless device in an RRC inactive state. Implementation of existing signaling may result in increased communication delay, increased packet loss rate, and/or increased call drop rate due to inefficient packet transmission for the wireless device of an RRC inactive state and/or an RRC idle state. In an RRC idle state of a wireless device, a core network entity may recognize that the wireless device is unreachable by a base station, and the core network entity may not transmit packets for the wireless device to a base station before initiating a core network paging procedure. Unlike the RRC idle state, when a wireless device is in an RRC inactive state, a core network entity may consider that the wireless device has an RRC connection with a base station, and may transmit packets for the wireless device to a base station when the wireless device is not reachable by the base station. In an existing network signaling, when a RAN notification area update procedure is failed, a core network entity may keep sending, to an anchor base station, packets for an RRC inactive state wireless device though the anchor base station is uncertain whether the wireless device is reachable. Example embodiments may prevent packet transmission of a core network entity towards a base station when a wireless device is unreachable by informing a wireless device state to the core network entity. There is a need for further enhancement in communication among network nodes (e.g. base stations, core network entity, and wireless device), for example, when there is a failure in a periodic RNAU procedure. In an example, in some scenarios a periodic RNAU update procedure of a wireless device may increase a failure rate in transmitting downlink user plane or control plane packets (e.g. data packets, NAS/RRC signaling packets) for RRC inactive state wireless devices. Increased packet loss rate and/or increased transmission delay may degrade network system reliability. There is a need to improve backhaul signaling mechanism for RRC inactive state wireless devices. Example embodiments enhance information exchange among network nodes to improve network communication reliability when a wireless device is in an RRC inactive state. Example embodiments may enhance signaling procedures when a RAN notification area update procedure is failed. In an example embodiment, after transitioning an RRC station from an RRC connected state to an RRC inactive state, a wireless device may periodically perform a RAN notification area update (RNAU) procedure by sending a RNAU indication to an anchor base station. The anchor base station receiving the RNAU indication may consider that the wireless device in the RRC inactive state stays in an RAN notification area associated with the anchor base station, and/or may consider that the wireless device is in a reliable service area (e.g. reachable) of a cell of the RAN notification area. During the RRC inactive state, a core network entity (e.g. AMF and/or UPF) may consider that the wireless device has a RRC connection with the anchor base station, and may send downlink packets (e.g. data packets and/or control signaling packets, NAS messages) to the anchor base station. In an example embodiment, when an anchor base station recognizes a RNAU procedure (e.g. periodic RNAU procedure) failure of an RRC inactive state wireless device, the anchor base station may indicate that an RNAU of the wireless device is failed and/or that the wireless device is not reachable (e.g. UE context release request indicating a state transition of the wireless device to an RRC idle state). Example embodiments may enhance system reliability by enabling a base station to inform a core network entity of a wireless device state when a RAN notification area update procedure of the wireless device in an RRC inactive state is failed. Example embodiments may enable network nodes to reduce packet loss rate or call drop rate for an RRC inactive and/or RRC idle state wireless device in a RAN notification area update failure. In legacy LTE, a NAS identifier (typically S-TMSI) may be used to address the UE (wireless device) in a paging procedure. With the Rel-14 Light connection WI and the introduction of RAN initiated paging, it may have been agreed that a RAN allocated UE identity (Resume identity) may be used in the RRC Paging message when the paging is initiated in the RAN. One of the reasons behind this agreement may the potential security issue if the NAS identity (S-TMSI) may be exposed on the radio interface without the CN being in control of this. In NR (new radio), a similar security issue by exposing the NAS identity on the radio interface may be likely to appear. Furthermore, using a NAS identifier at RAN initiated paging may probably also lead to additional signalling between the RAN and the CN since mechanisms for frequent updates of the NAS identity may be needed. It may be also likely that the update mechanism may be more complex since recovery procedures may be needed if re-allocation of the NAS identity fails. For the reasons above, the UE may be addressed with a RAN allocated UE identity (resume identity) at RAN initiated paging. A UE in RRC_INACTIVE may be normally paged from the RAN, however for robustness purposes a UE in RRC_INACTIVE also may need to be reached by a CN initiated page. To resolve from a state inconsistency situation in which the UE is in RRC_INACTIVE while the network considers the UE to be in IDLE (e.g. if the UE was temporarily out of coverage at the time the release message was sent), the UE in RRC_INACTIVE may need to respond on a CN initiated page containing its NAS identifier. A UE may need to monitor and respond to a RAN initiated paging as well as to a CN initiated paging while in RRC_INACTIVE. A RAN initiated paging message may include a RAN allocated UE identity whereas a CN initiated paging message is sent with a CN allocated (NAS) identity. At reception of the RRC Paging message while in RRC_INACTIVE the UE may however behave the same regardless if the paging procedure is triggered in the RAN or in the CN, i.e. independently of the UE identifier included in the message. That is, the UE may take advantage of the stored AS context and may attempt to resume the RRC connection by sending an RRC Connection Resume Request message (or equivalent) to the gNB, identifying itself with the RAN allocated UE identity sent to the UE once it may be transited to RRC_INACTIVE. When the AS context is successfully retrieved in the network, the UE may be transited to RRC_CONNECTED as part of the Resume procedure, seeFIG.16below. If the AS context for some reason cannot be retrieved in the network, thus the resumption of the RRC connection fails, a fall-back procedure may be proposed in which the gNB triggers an RRC Connection Establishment procedure as a result of the failed resumption. The signalling flow for this scenario may be shown inFIG.17below. In an example, if the resumption attempt fails it may not add any additional roundtrip costs between the UE and the network compared to a normal RRC Connection Establishment procedure triggered from RRC_IDLE (the UE may send a RRC Connection Request message instead of the RRC Connection Resume Request message). The fact that the UE may keep the AS context until informed by the network (inFIG.14at the reception of the RRC Connection Setup message) may also be considered as a more secure solution compared to a solution where the AS context may be simply released at reception of a paging message. The Paging procedure inFIG.14andFIG.15may also be initiated from the CN if, for example, the UE may be temporarily out of coverage at the time the release message was sent. The following are example call flows. There may be additional messages (not shown in the call flow) that are communicated among the network nodes. In an example embodiment as shown inFIG.25andFIG.26, a first base station may transmit, to a wireless device, at least one first message indicating a radio resource control (RRC) state transition of the wireless device from an RRC connected state to an RRC inactive state. The at least one first message may comprise a parameter indicating a value associated with a wireless device radio access network (RAN) notification area update timer for a periodic RAN notification area update procedure. In an example, the first base station may be an anchor base station of the wireless device. The first base station may keep a UE context of the wireless device. The UE context may comprise at least one of PDU session configurations, security configurations, radio bearer configurations, logical channel configurations, resume identifier associated with the RRC inactive state, RAN notification area information (e.g. a RAN area identifier, a cell identifier, a base station identifier of a RAN notification area of the wireless device). In an example, a wireless device in an RRC inactive state may perform an RNA update procedure when a UE RNA update timer (a periodic RAN notification area update timer value) is expired. Periodic RNA may be configured by a base station for a wireless device. The UE RNA update timer may be configured and/or (re)started when the wireless device makes an RRC connection, when performs an RNA update procedure, and/or via one or more signaling message between the wireless device and the base station. In an example the UE RNA update timer may be configured based on a moving speed, a network slice, a UE type, an established bearer type, and/or a service type of the wireless device. The base station may transmit one or more message comprising configuration parameters, e.g. an RNA timer value, and/or an RNA counter. An RNA timer and/or counter may be restarted when the UE successfully transmits an RNA update to a base station. In an example, a wireless device may not be able to initiate an RNA update procedure when a UE RNA update timer is expired for a plurality of reasons (e.g. a plurality of system errors, moving to out of network coverage, and/or a power off). In an example, a first base station may determine that a periodic RNA update is unsuccessful if a network RNA update timer is expired without receiving an RNA update message from a wireless device in an RRC inactive state and/or if the first base station does not receive an RNA update message more than the number of a periodic RNA update counter. In an example, the base station may consider that a periodic RNA update is unsuccessful, when a first number of (e.g. subsequent) expected periodic RNA update messages have not been received. In an example, the network RNA update timer may be longer than the UE RNA update timer. When one or more periodic RNA update procedures of a wireless device fail, the base station (e.g. anchor base station) may determine a failure of a periodic RNA update of the wireless device. The determining, by the base station, the periodic RNA update failure may be based on expiration of a network RNA update timer (e.g. RAN notification area update guard timer). In an example, the first base station may start the network RNA update timer in response receiving a RNA update indication from the wireless device. The RNA update indication may comprise an RRC connection resume message from the wireless device, a UE context retrieve request message from a base station where the wireless device camps on, an Xn message indicating an RNA update of the wireless device, and/or the like. In an example, the first base station may start the network RNA update timer in response to communicating with the wireless device (e.g. transmitting/receiving one or more packets to/from the wireless device). In an example, the first base station may stop the network RNA update timer in response to communicating with the wireless device. After determining that a periodic RNA update is unsuccessful, the first base station may transmit a first message to a core network entity. The first message may comprise at least one of a wireless device identifier of the wireless device that failed in a periodic RNA update, an AS context identifier of the wireless device, an RNA update failure indication for the wireless device, a wireless device context release indication for the wireless device in the first base station, an RRC state transition indication informing that a RRC state of the wireless device transitions to an RRC idle state, a Resume ID of the wireless device and/or a core network paging request for the wireless device. In an example, after transmitting the first message, the first base station may release a wireless device context (a UE context). In an example, the first message may comprise a UE context release request message for the wireless device. The first message may comprise a cause information element indicating that the wireless device is unreachable, that the wireless device is in an RRC idle state, and/or that a periodic RAN notification area update of the wireless device is failed. In an example, the core network entity may release a UE context of the wireless device in response to receiving the first message from the base station (e.g. anchor base station). In an example, the core network entity, receiving the first message for the failure of a periodic RNA update of the wireless device from the first base station, may configure an RRC state of the wireless device as an RRC idle state. In an example, the core network entity may keep an RRC state of the wireless device as an RRC inactive state. In an example, the core network entity receiving the first message may transmit a first core network paging message to a plurality of base stations. The first core network paging message may comprise at least one of a wireless device identifier, an AS context identifier of the wireless device, a tracking area identifier (and/or a tracking area code), a base station identifier of the first base station, an RNA identifier associated with the wireless device, a reason of the core network paging, resume ID of the wireless device and/or an action indication for the wireless device. In an example, the action indication may be configured for the wireless device to perform an RRC state transition to an RRC idle state, an RRC state transition to an RRC connected state, an RNA update procedure, and/or a random access procedure. In an example, a second base station receiving a first core network paging message may determine whether there is a direct interface (e.g. Xn interface) between the first base station and the second base station at least based on the base station identifier of the first base station. In an example, a second base station that receives the first core network paging message may broadcast/multicast a second core network paging message comprising the wireless device identifier, e.g., Resume ID, S-TMSI, or IMSI. In an example, the second core network paging message may further comprise the AS context identifier, the RNA identifier, the reason of the core network paging, and/or the action indication for the wireless device. The second core network paging message may be configured to initiate a random access procedure by the wireless device. In an example, the wireless device may recognize the second core network paging message based on at least one of the wireless device identifier, the AS context identifier, and/or the RNA identifier. In an example, after receiving the second core network paging message, the wireless device may initiate a random access procedure by transmitting a preamble message to the second base station. In an example, the random access procedure may be a 2-stage random access procedure and/or a 4-stage random access procedure. In an example, during the random access procedure, the second base station may inform the wireless device of an action to take at least based on the action indication for the wireless device, wherein the action may be at least one of transitioning an RRC state to an RRC connected state, transitioning an RRC state to an RRC idle state, staying in an RRC inactive state, and/or initiating an RNA update procedure. In an example, after receiving the preamble message for the random access from the wireless device, the second base station may transmit a core network paging acknowledge message for the first core network paging message to the core network entity. The core network paging acknowledge message may comprise a wireless device context request for the wireless device. In an example, the core network entity may transmit an acknowledge message to the first base station for the first message received form the first base station. The acknowledge message to the first base station may comprise a wireless device context request for the wireless device. In an example, after receiving the preamble message for the random access from the wireless device, the second base station may transmit a wireless device context request message to the first base station via a direct interface (e.g. an Xn interface) between the first base station and the second base station at least based on the base station identifier of the first base station included in the first core network paging message. In an example, the first base station may transmit a wireless device context to the second base station indirectly via the core network entity and/or directly via the direct interface. In an example, after transmitting the wireless device context to the second base station, the first base station may release a wireless device context (a UE context). In an example, in case that the second base station fetches the wireless device context from the first base station via a direct interface, the second base station may transmit a path switch request for the wireless device to a core network entity, and the core network entity may update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity and a RAN node, e g changing a downlink tunnel endpoint identifier from an address of the first base station to an address of the second base station. In an example, after the successful core network paging procedure, the wireless device may stay in an RRC inactive state, transition to an RRC connected state, and/or transition to an RRC idle state. In case that the wireless device stays in an RRC inactive state or transitions to an RRC connected state, the second base station may keep a wireless device context of the wireless device and may maintain one or more bearers for the wireless device between the second base station and a user plane core network entity. If the wireless device stays in an RRC inactive state, the second base station may become an anchor base station for the wireless device. If the wireless device transitions to an RRC connected state, the second base station may initiate an RRC state transition of the wireless device to an RRC inactive state, and the second base station may become an anchor base station. In case that the wireless device transitions to an RRC idle state, the second base station may not request a wireless device context to the first base station and/or to the core network entity. In an example, if a wireless device in an RRC inactive state does not perform an RNA update procedure before a UE RNA update timer (a periodic RAN notification area update timer value) is expired, the wireless device may determine that a periodic RNA update is failed. The may UE may start an RNA update timer in response to an RRC message configuring periodic RNA timer in the UE and the UE transitioning to inactive RRC state. The UE may restart the UE RNA timer when the UE transmits an RNA update. In an example, if the periodic RNA update failure occurs, the wireless device may transition its RRC state to an RRC idle state immediately, after an expiration of another timer, and/or after failing in performing an RNA update procedure more than a number of a periodic RNA update counter. For example, when a UE RNA update procedure is unsuccessful a first number of (e.g. consecutive) times, the UE may determine that the periodic RNA update failed. In an example, a base station may transmit to the wireless device a configuration message comprising periodic RNA update timer and/or counter values. In an example, a first base station may determine, for a wireless device, a periodic RNA failure based on one or more criteria comprising expiry of a periodic RAN notification area update timer. The first base station may transmit, to a core network entity, a first message in response to determining the periodic RNA failure, wherein the first message may comprise a first wireless device identifier of the wireless device, and/or the first message may indicate the periodic RNA failure for the wireless device. The first message further may comprise a first indication indicating that the first base station releases a wireless device context. The first base station may further release a wireless device context of the wireless device. The first message may further comprise a second indication indicating that a first time duration associated with RNA update period is elapsed and no RNA update is received. The second base station may further receive, from the core network entity, a second message comprising a first paging and a second wireless device identifier of the wireless device. The second base station may broadcast and/or multicast a third message comprising a second paging and the second wireless device identifier. The second base station may receive, from the wireless device, a fourth message comprising an acknowledgement of the second paging, wherein the wireless device may recognize the second paging request at least based on the second wireless device identifier. The second base station may transmit, to the core network entity, a fifth message indicating a response to the second message. In an example, the first base station may further receive a fifth message comprising a request of a wireless device context for the wireless device. The first base station may transmit a sixth message comprising the wireless device context. The first base station may release the wireless device context. The wireless device may further transition a radio resource control state to a radio resource control idle state in response to a paging message from a base station. The wireless device may further transition a radio resource control state to a radio resource control idle state after receiving the paging message. The wireless device may be in a radio resource control RRC inactive state after receiving the paging message. The second base station may further transmit to the wireless device at least one of the following: a message comprising a radio resource control state transition indication completing a radio resource control state transition from a radio resource control connected state to a radio resource control inactive state, a message comprising a radio access network notification area update accept, and/or one of one or more packets. The second base station may receive, from the wireless device, at least one of the following: a message comprising a radio access network notification area update request, one of one or more packets received by the first base station from the wireless device, and/or a message comprising an acknowledgement of a radio access network notification area paging. In an example, the first base station may further release a RAN context of the wireless device. The first base station and/or the core network entity may transition a radio resource control state from an RRC inactive state to an RRC idle state. In an example, the wireless device may transition to an RRC idle state from an RRC inactive state if a second criteria is met. The first base station may transmit to the wireless device one or more messages comprising one or more configuration parameters of an RNA, the one or more configuration parameter comprising a parameter indicating a value for a periodic RAN notification area update timer value. In an example, the first base station may transmit to the wireless device one or more criteria comprising reaching a periodic RAN notification area update counter. If a number of failing in an RNA update reaches the periodic RAN notification area update counter, the wireless device may transition to an RRC idle state. In an example, a wireless device may receive, from a base station, one or more first messages comprising one or more configuration parameters of an RNA, the one or more configuration parameter comprising a parameter indicating a value for a periodic RAN notification area update timer value. The wireless device may determine a periodic RNA update failure based on one or more criteria comprising expiry of the periodic RAN notification area update timer. The wireless device may transition to an RRC idle state in response to determining the periodic RNA update failure. Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols. According to various embodiments, a device such as, for example, a wireless device, off-network wireless device, a base station, and/or the like, may comprise one or more processors and memory. The memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions. Embodiments of example actions are illustrated in the accompanying figures and specification. Features from various embodiments may be combined to create yet further embodiments. FIG.27is an example flow diagram as per an aspect of an embodiment of the present disclosure. At2710, a first base station may receive from a first core network entity, one or more packets for a wireless device in a radio resource control (RRC) inactive state. At2720, the first base station may initiate a radio access network (RAN) paging procedure comprising sending at least one RAN paging message to at least one second base station. The at least one RAN paging message may comprise a first identifier of the wireless device. At2730, the first base station may determine a failure of the RAN paging procedure in response to not receiving a response of the at least one RAN paging message. At2740, the first base station may send a first message to a second core network entity in response to the failure of the RAN paging procedure. At2750, the first base station may receive a second message from the second core network entity in response to the first message. The second message may comprise a tunnel endpoint identifier of a third base station for forwarding the one or more packets. At2760, the first base station may send to the third base station, the one or more packets based on the tunnel endpoint identifier. According to an embodiment, the second core network entity may initiate, in response to receiving the first message, a core network paging procedure. The core network paging procedure may comprise sending a first paging message to the third base station. The first paging message may comprise a second identifier of the wireless device. The second core network entity may receive from the third base station, a third message in response to the first paging message. The third message may comprise the tunnel endpoint identifier of the third base station. According to an embodiment, the first core network entity may comprise a control plane core network node. The second core network entity may comprise a user plane core network node. According to an embodiment, the sending of the one or more packets may be via a direct tunnel between the first base station and the third base station. The direct tunnel may be associated with the tunnel endpoint identifier. According to an embodiment, the tunnel endpoint identifier may comprise an internet protocol (IP) address of the third base station. According to an embodiment, the first message may indicate the failure of the RAN paging procedure. According to an embodiment, the at least one RAN paging message may comprise at least one of: a RAN notification information; a context identifier of the wireless device; a reason of initiating the RAN paging procedure; and/or the like. According to an embodiment, the at least one second base station may transmit a second RAN paging message via a radio interface in response to receiving the at least one RAN paging message. FIG.28is an example flow diagram as per an aspect of an embodiment of the present disclosure. At2810, a third base station may receive from a second core network entity, a first paging message for a wireless device. The first paging message may comprise a second identifier of the wireless device. At2820, the third base station may transmit, in response to receiving the first paging message, a second paging message for the wireless device via a radio interface. At2830, the third base station may receive from the wireless device, in response to the first paging message, a random access preamble for a radio resource control (RRC) connection. At2840, the third base station may transmit to the second core network entity, in response to the RRC connection, a third message comprising a tunnel endpoint identifier of the third base station. At2850, the third base station may receive from a first base station, one or more packets based on the tunnel endpoint identifier. According to an embodiment, the second core network entity may comprise a user plane core network node. According to an embodiment, the receiving of the one or more packets may be via a direct tunnel between the first base station and the third base station. The direct tunnel may be associated with the tunnel endpoint identifier. According to an embodiment, the tunnel endpoint identifier may comprise an internet protocol (IP) address of the third base station. FIG.29is an example flow diagram as per an aspect of an embodiment of the present disclosure. At2910, a first base station may receive from a first core network entity, one or more packets for a wireless device. At2920, the first base station may initiate a paging procedure. The paging procedure may comprise sending at least one paging message to at least one second base station. The at least one paging message may comprise a first identifier of the wireless device. At2930, the first base station may send a first message to a second core network entity in response to determining a failure of the paging procedure. At2940, the first base station may receive a second message from the second core network entity in response to the first message. The second message may comprise a tunnel identifier of a third base station for forwarding the one or more packets. At2950, the first base station may send to the third base station, the one or more packets based on the tunnel identifier. According to an embodiment, the paging procedure may comprise a radio access network (RAN) paging procedure. According to an embodiment, the tunnel identifier may comprise a tunnel endpoint identifier. According to an embodiment, the wireless device may be in a radio resource control inactive state. According to an embodiment, the determining the failure may be in response to not receiving a response of the at least one paging message. According to an embodiment, the first message may indicate the failure of the paging procedure. FIG.30is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3010, a first base station may transmit to a second base station, a first message comprising a first radio access network (RAN) area identifier of the first base station. At3020, the first base station may receive from the second base station, a second message comprising a second RAN area identifier of the second base station. At3030, the first base station may transmit to a wireless device, at least one radio resource control (RRC) message. The at least one RRC message may comprise the first RAN area identifier. The at least one RRC message may indicate a state transition of the wireless device to an RRC inactive state. At3040, the first base station may receive one or more packets for the wireless device. At3050, the first base station may transmit to the second base station, and in response to receiving the one or more packets, a RAN paging message when the first RAN area identifier is identical to the second RAN area identifier. The RAN paging message may comprise an identifier of the wireless device and the first RAN area identifier. According to an embodiment, the first message may further comprise a first cell identifier of a first cell of the first base station. The first cell may be associated with the first RAN area identifier. According to an embodiment, the second message may further comprise a second cell identifier of a second cell of the second base station. The second cell may be associated with the second RAN area identifier. According to an embodiment, the transmitting of the RAN paging message may be in response to the wireless device being in the RRC inactive state. According to an embodiment, the first base station may further receive from the second base station, a third message in response to the RAN paging message. According to an embodiment, the first base station may further transmit to the second base station, the one or more packets for the wireless device in response to the third message. According to an embodiment, the first base station may keep a wireless device context of the wireless device at least during a time in which the wireless device is in the RRC inactive state. The wireless device context may comprise at least one of: a bearer configuration information; a logical channel configuration information; a security information; and/or the like. According to an embodiment, the first message may comprise at least one of: an interface setup request message; an interface setup response message; a base station configuration update message; and/or the like. According to an embodiment, the first base station may receive the one or more packets from a core network entity. According to an embodiment, the first base station may further transmit one or more RAN paging messages to one or more third base stations associated with the first RAN identifier. FIG.31is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3110, a second base station may receive from a first base station, a first message comprising a first radio access network (RAN) area identifier of the first base station. At3120, the second base station may transmit to the first base station, a second message comprising a second RAN area identifier of the second base station. At3130, the second base station may receive from the first base station, a RAN paging message for a wireless device when the first RAN area identifier is identical to the second RAN area identifier. The wireless device may be: in a radio resource control (RRC) inactive state; and assigned with the first RAN area identifier. According to an embodiment, the RAN paging message may comprise an identifier of the wireless device and the first RAN area identifier. FIG.32is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3210, a first base station may receive from a second base station, a second message comprising a second radio access network (RAN) area identifier of the second base station. At3220, the first base station may transmit to a wireless device, at least one third message comprising a first RAN area identifier. The at least one third message may indicate a state transition of the wireless device to a radio resource control inactive state. At3230, the first base station may receive one or more packets for the wireless device. At3240, the first base station may transmit to the second base station and in response to receiving the one or more packets, a RAN paging message when the first RAN area identifier is identical to the second RAN area identifier. The RAN paging message may comprise an identifier of the wireless device and the first RAN area identifier. According to an embodiment, the first base station may further transmit to the second base station, a first message comprising a first RAN area identifier of the first base station. FIG.33is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3310, a first base station may receive from a second base station, at least one first packet associated with a wireless device. At3320, the first base station may receive from a core network entity, at least one second packet for the wireless device when the wireless device is in a radio resource control (RRC) inactive state. At3330, the first base station may transmit a first RAN paging message to a third base station of a radio access network (RAN) area associated with the wireless device and in response to a first time duration being larger than a first time value. The first time duration may comprise a time duration between the receiving of the at least one first packet and the receiving of the at least one second packet. At3340, the first base station may transmit a second RAN paging message to the second base station regardless of the first time duration being smaller or larger than the first time value. At3350, the first base station may transmit at least one second packet to one of the second base station or the third base station based on a response received for one of the first RAN paging message or the second RAN paging message. According to an embodiment, the RAN area may be associated with a RAN notification area. According to an embodiment, the first RAN paging message or the second RAN paging message may comprise: an identifier of the wireless device; and a RAN area information of the RAN area. According to an embodiment, the at least one first packet may be associated with at least one of: an uplink data transmission of the wireless device being in the RRC inactive state; a data transmission; a RAN notification area update procedure; or a state transition of the wireless device from a RRC inactive state connected state to the RRC inactive state. According to an embodiment, the first time value may be based on moving speed of the wireless device. According to an embodiment, the first base station may keep a wireless device context of the wireless device at least during a time in which the wireless device is in the RRC inactive state. The wireless device context may comprise at least one of: a bearer configuration information; a logical channel configuration information; a packet data convergence protocol configuration information; or a security information. According to an embodiment, the first base station may be associated with the RAN area. According to an embodiment, the first base station may further transmit to the wireless device, at least one RRC message comprising RAN area information of the RAN area. The at least one RRC message may indicate a state transition of the wireless device to the RRC inactive state. According to an embodiment, the second base station may transmit a first paging message via a first cell of the RAN area associated with the wireless device in response to: receiving the second RAN paging message; and a second time duration being larger than a second time value. The second time duration may comprise a time duration between receiving the at least one first packet from the wireless device and the receiving of the second RAN paging message. The second base station may transmit a second paging message via a second cell regardless of the second time duration being smaller or larger than the second time value wherein the second base station may have received the at least one first packet from the wireless device via the second cell. According to an embodiment, the second base may further transmit the at least one second packet via one of the first cell or the second cell based on a response received for one of the first paging message or the second paging message. FIG.34is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3410, a first base station may receive from a second base station, at least one first packet associated with a wireless device. At3420, the first base station may receive from a core network entity, at least one second packet for the wireless device when the wireless device is in a radio resource control (RRC) inactive state. At3430, the first base station may determine whether a time duration between the receiving of the at least one first packet and the receiving of the at least one second packet is larger than a first time value. When the time duration is larger than the first time value (3440), the first base station may transmit a first RAN paging message to a third base station of a radio access network (RAN) area associated with the wireless device at3445. When the time duration is smaller than or equal to the first time value (3450), the first base station may transmit a second RAN paging message to the second base station at3455. At3460, the first base station may transmit at least one second packet to one of the second base station or the third base station based on a response received for one of the first RAN paging message or the second RAN paging message. FIG.35is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3510, a first base station may receive from a wireless device, at least one first packet via a first cell of the first base station. At3520, the first base station may receive from a core network entity, at least one second packet for the wireless device when the wireless device is in a radio resource control inactive state. At3530, the first base station may transmit a first RAN paging message to a second base station of a radio access network (RAN) area associated with the wireless device and in response to a first time duration being larger than a first time value. The first time duration may comprise a time duration between the receiving of the at least one first packet and the receiving of the at least one second packet. At3540, the first base station may transmit a second RAN paging message via one or more second cells of the RAN area regardless of the first time duration being smaller or larger than the first time value. The one or more second cells may comprise the first cell. At3550, the first base station may transmit the at least one second packet to the wireless device via one of the one or more second cells or the second base station based on a response received for one of the first RAN paging message or the second RAN paging message. FIG.36is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3610, a wireless device may receive from a base station, at least one first message comprising configuration parameters of at least one of: at least one logical channel; or at least one radio bearer. At3620, the wireless device may receive from the base station, a second message indicating a radio resource control (RRC) state transition of the wireless device from an RRC connected state to an RRC inactive state. At3630, the wireless device being in the RRC inactive state may select a first cell based on the configuration parameters. At3640, the wireless device may transmit to the base station, a random access preamble via the first cell. According to an embodiment, the configuration parameters may further comprises at least one of: a first cell identifier of the first cell; at least one logical channel identifier of the at least one logical channel; or at least one radio bearer identifier of the at least one radio bearer. According to an embodiment, the configuration parameters may indicate association of the at least one logical channel or the at least one radio bearer with the first cell. According to an embodiment, the configuration parameters may indicate association of the at least one logical channel or the at least one radio bearer with at least one of: one or more cell types; or one or more frequency bands. According to an embodiment, the configuration parameters may further indicate association of a first network slice with at least one of: the first cell; one or more cell types; or one or more frequency bands. According to an embodiment, the at least one logical channel or the at least one radio bearer may be associated with a first network slice. According to an embodiment, the base station may keep a wireless device context of the wireless device at least during a time in which the wireless device is in the RRC inactive state. The wireless device context may comprising at least one of: a bearer configuration information; a logical channel configuration information; a packet data convergence protocol configuration information; a security information; and/or the like. According to an embodiment, the selecting of the first cell may be in response to an uplink buffer comprising one or more packets associated with at least one of: the at least one logical channel; or the at least one radio bearer. According to an embodiment, the transmitting of the random access preamble message may be in response to at least one of: an uplink buffer comprising one or more packets; a paging indication from the base station; moving to a first radio access network notification area; or moving to a first tracking area. FIG.37is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3710, a base station may transmit to a wireless device, at least one first message. The at least one first message may comprise configuration parameters of at least one of: at least one logical channel; or at least one radio bearer. At3720, the base station may transmit to the wireless device, a second message indicating a radio resource control (RRC) state transition of the wireless device from an RRC connected state to an RRC inactive state. At3730, the base station may receive from the wireless device, a random access preamble via the first cell selected by the wireless device based on the configuration parameters. The wireless device may be in the RRC inactive state. According to an embodiment, the configuration parameters may further comprises at least one of: a first cell identifier of the first cell; at least one logical channel identifier of the at least one logical channel; or at least one radio bearer identifier of the at least one radio bearer. FIG.38is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3810, a first base station may transmit to a wireless device, at least one first message indicating a radio resource control (RRC) state transition of the wireless device from an RRC connected state to an RRC inactive state. The at least one first message may comprise a parameter indicating a value associated with a wireless device radio access network (RAN) notification area update timer for a periodic RAN notification area update procedure. At3820, the first base station may receive a second message indicating a RAN notification area update by the wireless device in response to expiry of the wireless device RAN notification area update timer. At3830, the first base station may start a network RAN notification area update timer in response to the receiving of the second message. At3840, the first base station may transmit to a core network entity and in response to an expiration of the network RAN notification area update timer, a third message indicating a wireless device context release request for the wireless device. The third message may comprise an identifier of the wireless device. According to an embodiment, the at least one first message may further comprise a RAN notification area information associated with the wireless device. The RAN notification area information may comprise at least one of: a RAN area identifier; or a cell identifier. According to an embodiment, the first base station may further release a wireless device context of the wireless device based on the expiration of the network RAN notification area update timer. According to an embodiment, the third message may further indicate that the wireless device fails in a period RAN notification area update. According to an embodiment, the core network entity may determine the wireless device as being in an idle state in response to receiving the third message. According to an embodiment, the first base station may keep a wireless device context of the wireless device at least during a time in which the wireless device is in the RRC inactive state. The wireless device context may comprise at least one of: a bearer configuration information; a logical channel configuration information; a packet data convergence protocol configuration information; a security information, and/or the like. According to an embodiment, the wireless device RAN notification area update timer may be configured based on at least one of: a moving speed of the wireless device; a wireless device type of the wireless device; a network slice of the wireless device; a bearer of the wireless device; and/or the like. According to an embodiment, the core network entity may further transmit to a second base station, a paging message for the wireless device based on the third message. The core network entity may further receive from the second base station, a response message to the paging message. According to an embodiment, the wireless device may transition a RRC state from the RRC inactive state to a RRC idle state in response to failing in a period RAN notification area update. According to an embodiment, the second message may comprise an RRC connection resume request message. FIG.39is an example flow diagram as per an aspect of an embodiment of the present disclosure. At3910, a first base station may transmit to a wireless device, at least one first message indicating a radio resource control (RRC) state transition of the wireless device from an RRC connected state to an RRC inactive state. At3920, the first base station may receive from the wireless device, a second message indicating a RAN notification area update by the wireless device. At3930, the first base station may start a network radio access network (RAN) notification area update timer in response to the receiving of the second message. At3940, the first base station may transmit to a core network entity and in response to an expiration of the network RAN notification area update timer, a third message indicating a wireless device context release request for the wireless device. The third message may comprise an identifier of the wireless device. FIG.40is an example flow diagram as per an aspect of an embodiment of the present disclosure. At4010, a first base station may transmit to a wireless device, at least one first message indicating a radio resource control (RRC) state transition of the wireless device from an RRC connected state to an RRC inactive state. The at least one first message may comprise a parameter indicating a value associated with a wireless device radio access network (RAN) notification area update timer for a periodic RAN notification area update procedure. At4020, the first base station may receive a second message indicating a RAN notification area update by the wireless device in response to expiry of the wireless device RAN notification area update timer. At4030, the first base station may transmit to a core network entity and in response to not receiving a RAN notification area update within a time duration, a third message indicating a wireless device context release request for the wireless device. The time period may be longer than the value associated with the wireless device RAN notification area update timer. According to an embodiment, the third message may comprise an identifier of the wireless device. FIG.41is an example flow diagram as per an aspect of an embodiment of the present disclosure. At4110, a first base station may transmit to a wireless device, at least one first message indicating a radio resource control (RRC) state transition of the wireless device from an RRC connected state to an RRC inactive state. The at least one first message may comprise a parameter indicating a first value associated with a wireless device radio access network (RAN) notification area update timer for a periodic RAN notification area update procedure. At4120, the wireless device may start a RAN notification area update timer in response to the RRC state transition. At4130, the first base station may receive a second message indicating a RAN notification area update with a second value by the wireless device in response to expiry of the wireless device RAN notification area update timer. At4140, the first base station may start a network RAN notification area update timer in response to the receiving of the second message. At4140, the first base station may transmit to a core network entity and in response to an expiration of the network RAN notification area update timer, a third message indicating a wireless device context release request for the wireless device. The third message may comprise an identifier of the wireless device. The second value of the network RAN notification area update timer may be larger than the first value of the wireless device RAN notification area update timer. A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). A base station may comprise multiple sectors. When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices or base stations perform based on older releases of LTE or 5G technology. In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state In this disclosure, various embodiments are disclosed. Limitations, features, and/or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages. Furthermore, many features presented above are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. However, the present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven different ways, namely with just one of the three possible features, with any two of the three possible features or with all three of the three possible features. Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e. hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, FORTRAN, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The above mentioned technologies are often used in combination to achieve the result of a functional module. The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for the limited purposes required by law, but otherwise reserves all copyright rights whatsoever. While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments. In addition, it should be understood that any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments. Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope in any way. Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 112. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 112. | 258,510 |
11943744 | DESCRIPTION OF EMBODIMENTS The following describes technical solutions of this application with reference to accompanying drawings. The technical solutions in the embodiments of this application may be applied to a plurality of communications systems, for example, a 5th generation (5th Generation, 5G) system, a new radio (NR) system, or a communications system that has a same architecture as the 5G system. A terminal device in this application may also be referred to as a terminal, user equipment (UE), a mobile station (MS), a mobile terminal (MT), or the like. The terminal device herein may be specifically a mobile phone, a tablet (pad), a computer having a wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city (smart city), a wireless terminal in a smart home, or a vehicle, a vehicle-mounted device, or a vehicle-mounted module in an internet of vehicles system. A network device in this application may be an access device accessed by a terminal device in the mobile communications system in a wireless manner, or may be a base station NodeB, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communications system, a base station in a future mobile communications system, or an access node in a wireless fidelity (WiFi) system, or may be a radio controller in a cloud radio access network (CRAN) scenario, or a roadside unit (RSU) in an internet of vehicles system, or may be a relay station, a network device in a future evolved PLMN network, or the like. FIG.1is a schematic architectural diagram of a mobile communications system to which an embodiment of this application is applied. The mobile communications system shown inFIG.1includes a core network device101, a network device102, a terminal device103, and a terminal device104(where the two terminal devices are shown inFIG.1). The terminal device103and the terminal device104may be connected to the network device102in a wireless manner. The network device102may be connected to the core network device101in a wireless or wired manner. The core network device101and the network device102may be different physical devices independent of each other, or functions of the core network device101and logical functions of the network device102may be integrated into a same physical device, or some functions of the core network device101and some functions of the network device102may be integrated into one physical device. The terminal device may be in a fixed position, or may be movable. It should be understood that the network device102may be an access network device. In the system shown inFIG.1, in addition to normal communication with the network device102, the terminal device103may further perform sidelink communication with the terminal device104. It should be understood thatFIG.1is only a schematic diagram of the mobile communications system according to this embodiment of this application, and the mobile communications system may further include another device. For example, the mobile communications system shown inFIG.1may further include a wireless relay device and a wireless backhaul device (not shown inFIG.1). Quantities of core network devices, network devices, and terminal devices included in the mobile communications system are not limited in this embodiment of this application. It should be understood thatFIG.1is only a schematic diagram of the mobile communications system to which this embodiment of this application may be applied to. This embodiment of this application may be further applied to another mobile communications system that can implement communication between a network device and a terminal device. A specific form of the mobile communications system that can be applied to is not limited in this embodiment of this application. As used herein, sidelink communication may also be referred to as sidelink communication (which may be briefly referred to as SL communication). FIG.2is a schematic flowchart of a sidelink communication method according to an embodiment of this application. The method shown inFIG.2may be performed by a terminal device. The method shown inFIG.2includes step110to step130. The following describes step110to step130in detail. 110. A network device sends resource configuration information to a terminal device, and the terminal device receives the resource configuration information. The resource configuration information may be used to configure a common resource for the terminal device. The common resource is a resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication. In other words, the common resource is a time-frequency resource configured by the network device for all the terminal devices within the coverage of the network device, and all the terminal devices within the coverage of the network device need to use the common resource to perform sidelink communication. 120. The network device sends sidelink BWP indication information to the terminal device, and the terminal device receives the sidelink BWP indication information. The sidelink BWP indication information is used to indicate N sidelink bandwidth parts SL-BWPs, the N SL-BWPs are bandwidth parts BWPs used by the terminal device to perform sidelink communication, and the N SL-BWPs include a frequency domain resource corresponding to the common resource, where N is a positive integer. Further, the sidelink BWP indication information may alternatively be activation information sent by the network device. The activation information may be carried in radio resource control (RRC) signaling, and the activation information is used to activate the N SL-BWPs, to obtain activated N SL-BWPs. The activated N SL-BWPs may be used for subsequent sidelink communication. The common resource may be a common resource pool. In some embodiments, that the N SL-BWPs include the frequency domain resource corresponding to the common resource may mean that at least one SL-BWP in the N SL-BWPs includes the frequency domain resource corresponding to the common resource. The common resource may include K common sub-resources, where K is a positive integer greater than 1. For example, the network device configures the common resource for the terminal device by using the resource configuration information, and the common resource includes three common sub-resources. Assuming that the sidelink BWP indication information indicates three SL-BWPs, one SL-BWP in the three SL-BWPs may include frequency domain resources corresponding to all of the three common sub-resources, or two SL-BEPs in the three SL-BWPs may include frequency domain resources corresponding to all of the three common sub-resources, or each of the three SL-BWPs may include a frequency domain resource corresponding to one common sub-resource. 130. The terminal device performs sidelink communication with another terminal device in the N SL-BWPs. As shown inFIG.2, the another terminal device may include at least one terminal device such as a terminal device 1 to a terminal device i (where i is a positive integer). In other words, in the method shown inFIG.2, the terminal device may perform sidelink communication with one or more other terminal devices in the N SL-BWPs. The sidelink communication may be that the terminal device sends sidelink control information and/or sidelink data to the another terminal device, or may be that the terminal device receives sidelink acknowledgement information or sidelink feedback information from the another terminal device. In this application, the N SL-BWPs are configured for the terminal device, and the configured N SL-BWPs include the frequency domain resource corresponding to the common resource, so that the terminal device can perform sidelink communication with the another terminal device in the N SL-BWPs. In some embodiments, the method shown inFIG.2further includes step140. It should be understood that step140may occur after step110. The following describes step140in detail. 140. The network device sends sidelink BWP configuration information to the terminal device, and the terminal device receives the sidelink BWP configuration information. The sidelink BWP configuration information is used to configure M SL-BWPs for the terminal device, the M SL-BWPs are BWPs available for sidelink communication, and the N SL-BWPs belong to the M SL-BWPs, where M is a positive integer greater than or equal to N. The N SL-BWPs may be SL-BWPs activated in the configured M SL-BWPs. Further, the N SL-BWPs may be SL-BWPs that are activated in the M SL-BWPs and that include the frequency domain resource corresponding to the common resource. In some embodiments, the method shown inFIG.2further includes step150. It should be understood that step150may occur before step140, or may occur after step140, or step150and step140may occur simultaneously. A sequence of step110to step150is not strictly limited in this application, provided that the sequence of these steps complies with communication logic and sidelink communication can be normally performed. The following describes step150in detail. 150. The network device sends uplink BWP indication information to the terminal device, and the terminal device receives the uplink BWP indication information. The uplink BWP indication information is used to indicate Y uplink bandwidth parts UL-BWPs, and Y is a positive integer. When configuring the SL-BWP, the UL-BWP may also be configured for the terminal device, so that the terminal device can communicate with the network device based on the UL-BWP. It should be understood that the Y UL-BWPs and the N SL-BWPs may be located on a same carrier, or may be located on different carriers. In addition, when the Y UL-BWPs and the N SL-BWPs are located on a same carrier, some resources of the Y UL-BWPs may be reused in the N SL-BWPs. Distribution of an SL-BWP and a UL-BWP on a carrier is described in detail below with reference toFIG.3toFIG.5. It should be understood that the SL-BWP shown inFIG.3toFIG.5refers to the N SL-BWPs, and the UL-BWP shown inFIG.3toFIG.5refers to the Y UL-BWPs. For brevity, when the Y UL-BWPs and the N SL-BWPs are described below with reference toFIG.3toFIG.5, the UL-BWP shown inFIG.3toFIG.5is used to represent the Y UL-BWPs, and the SL-BWP shown inFIG.3toFIG.5is used to represent the N SL-BWPs. As shown inFIG.3, an SL-BWP and a UL-BWP are located on a same carrier (where the SL-BWP and the UL-BWP are located on a shared carrier), and a frequency domain resource occupied by the SL-BWP is a subset of a frequency domain resource occupied by the UL-BWP. The UL-BWP and the SL-BWP are configured on the same carrier, so that utilization efficiency of spectrum resources can be improved. It should be understood that when the UL-BWP and the SL-BWP are located on the same carrier, the frequency domain resource occupied by the UL-BWP may only be partially the same as the frequency domain resource occupied by the SL-BWP. As shown inFIG.4, an SL-BWP and a UL-BWP are located on a same carrier, but the SL-BWP and the UL-BWP include different frequency domain resources. In this case, sidelink communication and uplink communication may be completely independent, and do not interfere with each other. As shown inFIG.5, an SL-BWP is located on a carrier1, and a UL-BWP is located on a carrier2. The UL-BWP and the SL-BWP are configured on the different carriers, so that sidelink communication and uplink communication that is between a terminal device and a network device can be performed on the different carriers, thereby avoiding mutual interference between the sidelink communication and the uplink communication. In some embodiments, in an embodiment, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the common resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. For example, for a sidelink service having an ultra-low latency requirement, time division multiplexing may be configured for sidelink data and sidelink control information in a same slot (slot), and for a sidelink service having a high reliability requirement, frequency division multiplexing may be configured for sidelink data and sidelink control information in a same slot. The network device configures the multiplexing format for the common resource, so that requirements in sidelink communication of different services of the terminal device can be met. The network device may flexibly configure sidelink resources based on a service type or another requirement, to improve system performance. It should be understood that, in addition to carrying the multiplexing format indication information, the resource configuration information may further carry transmission mode indication information and numerology (numerology) indication information, to indicate a transmission mode and a numerology that are used when sidelink communication is performed on the common resource. In some embodiments, the resource configuration information carries the transmission mode indication information, the transmission mode indication information is used to indicate the transmission mode used when the terminal device performs sidelink communication on the common resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information carries the numerology indication information, the numerology indication information is used to indicate the numerology (numerology) used when the terminal device performs sidelink communication on the common resource, and the numerology includes a subcarrier spacing (SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. It should be understood that sidelink communication may be performed between terminal devices on the common resource. In some cases, some terminal devices have a relatively high requirement on service reliability, or have a relatively high requirement on data confidentiality in sidelink communication. In this case, a dedicated resource may be configured for some terminal devices, so that these terminal devices perform sidelink communication on the dedicated resource. Therefore, in addition to configuring the common resource for the terminal device by using the resource configuration information, the network device may further configure a dedicated resource for the terminal device by using the resource configuration information. In some embodiments, the resource configuration information is further used to configure the dedicated resource for the terminal device, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the dedicated resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. In some embodiments, the resource configuration information further carries transmission mode indication information, the transmission mode indication information is used to indicate a transmission mode used when the terminal device performs sidelink communication on the dedicated resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). Therefore, the network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information further carries numerology indication information, the numerology indication information is used to indicate a numerology used when the terminal device performs sidelink communication on the dedicated resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. The dedicated resource may be specifically a dedicated resource pool. The network device may configure dedicated resources for some terminal devices based on characteristics of sidelink communication and requirements in sidelink communication, so that the some terminal devices perform sidelink communication by using the configured dedicated resources, thereby improving system performance. In some embodiments, when the network device configures the dedicated resource for the terminal device by using the resource configuration information, the resource configuration information may further carry multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the dedicated resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. The network device configures the multiplexing format for the dedicated resource, so that requirements in sidelink communication of different services of the terminal device can be met. The foregoing describes the sidelink communication method in the embodiments of this application in detail with reference toFIG.2toFIG.5. To better understand the sidelink communication method in the embodiments of this application, the following describes in detail a process of performing sidelink communication between a terminal device 1 and a terminal device 2 with reference to an example 1 (corresponding toFIG.6toFIG.8). In the example 1, the network device configures an SL-BWP including a common resource for the terminal devices, where the common resource may be a common resource pool, so that the terminal devices can perform sidelink communication by using a resource pool of the SL-BWP including the common resource. With reference toFIG.6, the following uses an example in which the common resource is the common resource pool, to describe in detail a complete process of sidelink communication between the terminal device 1 and the terminal device 2 in the example 1. A method shown inFIG.6includes step1001to step1007. The following describes the steps in detail.1001. The network device configures a resource pool for the terminal device 1.1002. The network device configures a resource pool for the terminal device 2. It should be understood that step1002may be performed before step1001, or may be performed after step1001, or step1002and step1001may be simultaneously performed. In step1001and step1002, the network device may configure resource information for the terminal device 1 and the terminal device 2 by using a system message block (system information block, SIB), cell-specific (cell-specific) RRC signaling, or UE-specific (UE-specific) RRC signaling. The resource information is equivalent to the foregoing resource configuration information, and a resource can be configured for the terminal device by using the resource information. Specifically, the resource information may be used to configure a resource pool for the terminal device. In this case, the resource information may also be referred to as resource pool information (or resource pool configuration information). The resource information indicates N resource pools, and the N resource pools include at least M common resource pools (Common Resource Pool) and N-M dedicated resource pools (Dedicated Resource Pool), where N≥1, and 1≤M≤N. As shown inFIG.7, the network device configures two common resource pools for the terminal device 1 and the terminal device 2. The two common resource pools are a common resource pool 1 (CommonResourcePool #1) and a common resource pool 2 (CommonResourcePool #2). In addition to the common resource pools, the network device further configures two dedicated resource pools for the terminal device 1 and the terminal device 2. The two dedicated resource pools are a dedicated resource pool 1 (DedicatedResourcePool #1) and a dedicated resource pool 2 (DedicatedResourcePool #2). The common resource pool is common to all terminal users, and all the terminal users can perform sidelink communication by using the common resource pool, including sending and receiving SL data. Some terminal users can perform sidelink communication by using the dedicated resource pool, which depends on a configuration of the network device and capabilities and requirements of the terminal users.1003. The network device configures M SL-BWPs for the terminal device 1.1004. The network device configures M SL-BWPs for the terminal device 2. In step1003and step1004, the network device may configure the SL-BWPs for the terminal devices through RRC signaling.1005. The network device activates N SL-BWPs for the terminal device 1.1006. The network device activates N SL-BWPs for the terminal device 2. In step1005and step1006, the network device may activate the N SL-BWPs by sending activation signaling to the terminal device 1 and the terminal device 2. For the terminal device 1, the activated N SL-BWPs include the common resource pool 1 and the common resource pool 2, that is, include all common resource pools. For the terminal device 2, the activated N SL-BWPs also include the common resource pool 1 and the common resource pool 2. Using the terminal device 1 as an example, that the N SL-BWPs include all common resource pools means that at least one of the N SL-BWPs includes all the common resource pools. For example, as shown inFIG.7, in the N SL-BWPs, both the first SL-BWP and an NthSL-BWP include the common resource pool 1 and the common resource pool 2. It should be understood that the terminal device 1 and the terminal device 2 may include different quantities of activated SL-BWPs, and sidelink communication can be performed between the terminal device 1 and the terminal device 2 provided that at least one SL-BWP in the activated SL-BWPs includes all the common resource pools.1007. The terminal device 1 performs sidelink communication with the terminal device 2 by using the resource pools in the activated N SL-BWPs. It should be understood that the method shown inFIG.6may further include the following steps.1008. The network device configures X BWPs for the terminal device 1.1009. The network device configures X BWPs for the terminal device 2. In step1008and step1009, the terminal device may specifically configure the BWPs for the terminal device 1 and the terminal device 2 through RRC signaling. For a same terminal device, at least one BWP may be activated at a same moment for communication transmission. A BWP configured in bandwidth used for downlink communication is a DL-BWP, and a BWP configured in bandwidth used for uplink communication is a UL-BWP. It should be understood that, actions of configuring the BWPs in step1008and step1009and actions of configuring the SL-BWPs in step1003and step1004may be performed simultaneously, or may be performed in a sequence (where the BWPs are configured before the SL-BWPs, or the SL-BWPs are configured before the BWPs). It should be understood that in the example 1, the terminal device 1 or the terminal device 2 may simultaneously perform sidelink communication and uplink communication (communication through a Uu air interface), where the sidelink communication and the uplink communication may occur on a shared carrier (shared carrier), that is, the SL-BWP and the UL-BWP are located on a same carrier. As shown inFIG.3, the SL-BWP may be inside the UL-BWP and a resource of the UL-BWP is reused in the SL-BWP. In addition, as shown inFIG.4, sidelink communication and uplink communication occur on a shared carrier (shared carrier), but the SL-BWP and the UL-BWP do not overlap, that is, different resources are used on an SL and a UL. In some embodiments, sidelink communication and uplink communication alternatively occur on independent carriers (shared carrier), and the SL-BWP and the UL-BWP do not overlap. That is, different resources are used on an SL and a UL. In the foregoing process, the SL-BWPs are all configured by the network device. When the network device does not perform control, the SL-BWPs may be configured by the terminal device. In the example 1, the terminal device may not only perform sidelink communication with another terminal device on a time-frequency resource in a common resource pool, but also perform sidelink communication with another terminal device on a time-frequency resource in a dedicated resource pool. Different from the common resource pool, the dedicated resource pool is usually a resource configured by the network device based on a capability or a requirement of the terminal device or selected by a user based on a pre-configured resource or by performing sensing (sensing), and is configured for SL-BWPs of some terminal devices. With reference toFIG.8, the following describes in detail a process of performing sidelink communication on resources in a common resource pool and a dedicated resource pool. As shown inFIG.8, the network device configures two common resource pools and three dedicated resource pools, which are a common resource pool 1 (CommonResourcePool #1), a common resource pool 2 (CommonResourcePool #2), a dedicated resource pool 1 (DedicatedResourcePool #1), a dedicated resource pool 2 (DedicatedResourcePool #2), and a dedicated resource pool 3 (DedicatedResourcePool #3). Assuming that a cell has four terminals, and the four terminals are UE-A, UE-B, UE-C, and UE-D, the network device configures SL-BWPs for the four UEs through RRC signaling, and the SL-BWPs of the UEs are: UE-A: UE-A SL-BWP #1 and UE-A SL-BWP #2; UE-B: UE-B SL-BWP #1; UE-C: UE-C SL-BWP #1 and UE-C SL-BWP #2; and UE-D: UE-D SL-BWP #1, UE-D SL-BWP #2, and UE-D SL-BWP #3. Each UE has one SL-BWP that covers the common resource pool 1 and the common resource pool 2. Further, the dedicated resource pool 1 and the dedicated resource pool 2 are covered by the UE-A SL-BWP #1 and the UE-D SL-BWP #1. In addition to performing sidelink communication on time-frequency resources in the common resource pool 1 and in the common resource pool 2, the UE-A and the UE-D may also perform sidelink communication on a time-frequency resource in the dedicated resource pool 1 or the dedicated resource pool 2. In addition, the dedicated resource pool 3 is covered by the UE-C SL-BWP #2 and the UE-D SL-BWP #3. Therefore, in addition to performing sidelink communication by using the common resource pool 1 and the common resource pool 2, the UE-C and the UE-D may also perform sidelink communication by using the dedicated resource pool 3. In addition, in the example 1, when the network device configures the resource pools, configuration information may further include at least one of the following information: (1) Multiplexing format indication information of sidelink control information (sidelink scheduling assignment, SA) and sidelink data A multiplexing format of the sidelink control information and the sidelink data may be represented by using a bit value of one bit in the multiplexing format indication information. For example, when the value of the bit is 1, it indicates that the sidelink control information and the sidelink data are time division multiplexed; when the value of the bit is 0, it indicates that the sidelink control information and the sidelink data are frequency division multiplexed. (2) Transmission mode in the sidelink communication, where the transmission mode includes unicast transmission, groupcast transmission, and broadcast transmission. In the sidelink communication, the transmission mode may be represented by using a bit value of two bits. For example, 00 indicates unicast, 01 indicates groupcast, and 10 indicates broadcast. (3) Subcarrier spacing indication information The subcarrier spacing indication information may include 3-bit information, and indicate at least subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. (4) Cyclic prefix (cyclic prefix, CP) indication information The CP indication information may include 1-bit information. When a value of the bit is 1, it indicates a normal cyclic prefix (normal cyclic prefix, NCP); when a value of the bit is 0, it indicates an extended cyclic prefix (extended cyclic prefix, ECP). FIG.9is a schematic block diagram of a terminal device according to an embodiment of this application. The terminal device10000inFIG.9corresponds to the foregoing methods shown inFIG.2andFIG.6. The terminal device10000can perform the steps performed by the terminal device in the method shown inFIG.2. The terminal device10000may further perform the steps performed by the terminal device 1 in the method shown inFIG.6. Limitations and explanations of the steps in the sidelink communication methods in the embodiments of this application inFIG.2andFIG.6are also applicable to steps performed by the terminal device10000shown inFIG.9. For brevity, repeated descriptions are appropriately omitted in the following description of the terminal device10000shown inFIG.9. The terminal device10000shown inFIG.9includes: a receiving unit10010, configured to receive resource configuration information sent by a network device, where the resource configuration information is used to configure a common resource for the terminal device, and the common resource is a resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication, where the receiving unit10010is further configured to receive sidelink BWP indication information sent by the network device, where the sidelink BWP indication information is used to indicate N sidelink bandwidth parts SL-BWPs, the N SL-BWPs are bandwidth parts BWPs used by the terminal device to perform sidelink communication, and the N SL-BWPs include a frequency domain resource corresponding to the common resource, where N is a positive integer; and a sidelink communication unit10020, configured to perform sidelink communication with another terminal device in the N SL-BWPs. In this application, the N SL-BWPs including the frequency domain resource corresponding to the common resource are configured for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device in the N SL-BWPs. In some embodiments, the common resource is specifically a common resource pool. In some embodiments, in an embodiment, the receiving unit10010is further configured to receive sidelink BWP configuration information sent by the network device, where the sidelink BWP configuration information is used to configure M SL-BWPs for the terminal device, the M SL-BWPs are BWPs available for sidelink communication, and the N SL-BWPs belong to the M SL-BWPs, where M is a positive integer greater than or equal to N. In some embodiments, in an embodiment, the receiving unit10010is further configured to receive uplink BWP indication information sent by the network device, where the uplink BWP indication information is used to indicate Y uplink bandwidth parts UL-BWPs, and Y is a positive integer. When configuring the SL-BWP, the network device may also configure the UL-BWP for the terminal device, so that the terminal device can perform uplink communication with the network device based on the UL-BWP. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on a same carrier. The UL-BWP and the SL-BWP are configured on the same carrier, so that utilization efficiency of spectrum resources can be improved. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs include a first frequency domain resource, the first frequency domain resource belongs to the Y UL-BWPs, and the first frequency domain resource belongs to the N SL-BWPs. When the SL-BWP and the UL-BWP include the same frequency domain resource, some resources of the UL-BWP may be reused in the SL-BWP for sidelink communication, so that utilization efficiency of spectrum resources can be optimized. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs do not include a same frequency domain resource. Different frequency domain resources are configured for the UL-BWP and the SL-BWP, so that sidelink communication and uplink communication are independent of each other and do not interfere with each other. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on different carriers. The UL-BWP and the SL-BWP are configured on different carriers, so that sidelink communication and uplink communication can be performed on the different carriers, thereby avoiding mutual interference between the sidelink communication and the uplink communication. In some embodiments, in an embodiment, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the common resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. It should be understood that, in addition to carrying the multiplexing format indication information, the resource configuration information may further carry transmission mode indication information and numerology (numerology) indication information, to indicate a transmission mode and a numerology that are used when sidelink communication is performed on the common resource. In some embodiments, the resource configuration information carries the transmission mode indication information, the transmission mode indication information is used to indicate the transmission mode used when the terminal device performs sidelink communication on the common resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information carries the numerology indication information, the numerology indication information is used to indicate the numerology used when the terminal device performs sidelink communication on the common resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. It should be understood that sidelink communication may be performed between terminal devices on the common resource. In some cases, some terminal devices have a relatively high requirement on service reliability, or have a relatively high requirement on data confidentiality in sidelink communication. In this case, a dedicated resource may be configured for some terminal devices, so that these terminal devices perform sidelink communication on the dedicated resource. The dedicated resource may be specifically a dedicated resource pool. Therefore, in addition to configuring the common resource for the terminal device by using the resource configuration information, the network device may further configure a dedicated resource for the terminal device by using the resource configuration information. In some embodiments, the resource configuration information is further used to configure the dedicated resource for the terminal device, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the dedicated resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. In some embodiments, the resource configuration information further carries transmission mode indication information, the transmission mode indication information is used to indicate a transmission mode used when the terminal device performs sidelink communication on the dedicated resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). Therefore, the network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information further carries numerology indication information, the numerology indication information is used to indicate a numerology used when the terminal device performs sidelink communication on the dedicated resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. FIG.10is a schematic block diagram of a network device according to an embodiment of this application. The network device20000inFIG.10corresponds to the foregoing methods shown inFIG.2andFIG.6. The network device20000can perform the steps performed by the network device in the methods shown inFIG.2andFIG.6. It should be understood that, limitations and explanations of the steps in the sidelink communication methods in the embodiments of this application inFIG.2andFIG.6are also applicable to steps performed by the network device20000shown inFIG.9. For brevity, repeated descriptions are appropriately omitted in the following description of the network device20000shown inFIG.10. The network device20000shown inFIG.10includes: a sending unit20010, configured to send resource configuration information to a terminal device, where the resource configuration information is used to configure a common resource for the terminal device, and the common resource is a resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication, where the sending unit20010is further configured to send sidelink BWP indication information to the terminal device, where the sidelink BWP indication information is used to indicate N sidelink bandwidth parts SL-BWPs, the N SL-BWPs include a frequency domain resource corresponding to the common resource, and the N SL-BWPs are used by the terminal device to perform sidelink communication with another terminal device, where N is a positive integer. In this application, the network device configures the N SL-BWPs including the frequency domain resource corresponding to the common resource for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device in the N SL-BWPs. In some embodiments, in an embodiment, the sending unit20010is further configured to send sidelink BWP configuration information to the terminal device, where the sidelink BWP configuration information is used to configure M SL-BWPs for the terminal device, the M SL-BWPs are BWPs available for sidelink communication, and the N SL-BWPs belong to the M SL-BWPs, where M is a positive integer greater than or equal to N. In some embodiments, in an embodiment, the sending unit20010is further configured to send uplink BWP indication information to the terminal device, where the uplink BWP indication information is used to indicate Y uplink bandwidth parts UL-BWPs, and Y is a positive integer. When configuring the SL-BWP, the network device may also configure the UL-BWP for the terminal device, so that the terminal device can perform uplink communication with the network device based on the UL-BWP. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on a same carrier. The UL-BWP and the SL-BWP are configured on the same carrier, so that utilization efficiency of spectrum resources can be improved. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs include a first frequency domain resource, the first frequency domain resource belongs to the Y UL-BWPs, and the first frequency domain resource belongs to the N SL-BWPs. When the SL-BWP and the UL-BWP include the same frequency domain resource, some resources of the UL-BWP may be reused in the SL-BWP for sidelink communication, so that utilization efficiency of spectrum resources can be optimized. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs do not include a same frequency domain resource. Different frequency domain resources are configured for the UL-BWP and the SL-BWP, so that sidelink communication and uplink communication are independent of each other and do not interfere with each other. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on different carriers. The UL-BWP and the SL-BWP are configured on different carriers, so that sidelink communication and uplink communication can be performed on the different carriers, thereby avoiding mutual interference between the sidelink communication and the uplink communication. In some embodiments, in an embodiment, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the common resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. It should be understood that, in addition to carrying the multiplexing format indication information, the resource configuration information may further carry transmission mode indication information and numerology (numerology) indication information, to indicate a transmission mode and a numerology that are used when sidelink communication is performed on the common resource. In some embodiments, the resource configuration information carries the transmission mode indication information, the transmission mode indication information is used to indicate the transmission mode used when the terminal device performs sidelink communication on the common resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information carries the numerology indication information, the numerology indication information is used to indicate the numerology used when the terminal device performs sidelink communication on the common resource, and the numerology includes a subcarrier spacing (SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. It should be understood that sidelink communication may be performed between terminal devices on the common resource. In some cases, some terminal devices have a relatively high requirement on service reliability, or have a relatively high requirement on data confidentiality in sidelink communication. In this case, a dedicated resource may be configured for some terminal devices, so that these terminal devices perform sidelink communication on the dedicated resource. Therefore, in addition to configuring the common resource for the terminal device by using the resource configuration information, the network device may further configure a dedicated resource for the terminal device by using the resource configuration information. In some embodiments, the resource configuration information is further used to configure the dedicated resource for the terminal device, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the dedicated resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. In some embodiments, the resource configuration information further carries transmission mode indication information, the transmission mode indication information is used to indicate a transmission mode used when the terminal device performs sidelink communication on the dedicated resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). Therefore, the network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information further carries numerology indication information, the numerology indication information is used to indicate a numerology used when the terminal device performs sidelink communication on the dedicated resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. The dedicated resource may be specifically a dedicated resource pool. It should be understood that the terminal device10000and the network device20000may be configured to jointly perform the sidelink communication methods shown inFIG.2andFIG.6: The network device20000configures a resource for the terminal device10000by using resource configuration information, so that N SL-BWPs configured for the terminal device10000include a frequency domain resource corresponding to a common resource, and further the terminal device10000can perform sidelink communication with another terminal device in the N SL-BWPs. In addition, when the terminal device includes a memory, a transceiver, and a processor, the receiving unit10010in the terminal device10000is equivalent to the transceiver, and the sidelink communication unit10020is equivalent to the transceiver and the processor. When the network device includes a memory, a transceiver, and a processor, the sending unit20010in the network device20000is equivalent to the transceiver. The foregoing describes in detail the sidelink communication method, the terminal device, and the network device in the embodiments of this application with reference toFIG.2toFIG.10. In the methods shown inFIG.2toFIG.10, a dedicated SL-BWP is set for the terminal device for sidelink communication. Actually, an existing UL-BWP may alternatively be reused for sidelink communication. With reference toFIG.11toFIG.14, the following describes in detail another sidelink communication method according to the embodiments of this application. FIG.11is a schematic flowchart of a sidelink communication method according to an embodiment of this application. The method shown inFIG.11may be performed by a terminal device. The method shown inFIG.11includes step210to step230. The following describes step210to step230in detail. 210. A network device sends resource configuration information to the terminal device, and the terminal device receives the resource configuration information, where the resource configuration information is used to configure a common resource for the terminal device, and the common resource is a resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication. The common resource is the resource that is configured by the network device for all the terminal devices within the coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication. In some embodiments, the common resource is specifically a common resource pool. 220. The network device sends uplink BWP indication information to the terminal device, and the terminal device receives the uplink BWP indication information, where the uplink BWP indication information is used to indicate Y UL-BWPs, and the Y UL-BWPs include a frequency domain resource corresponding to the common resource, where Y is a positive integer. 230. The terminal device performs sidelink communication with another terminal device in the Y UL-BWPs. As shown inFIG.11, the another terminal device may include at least one terminal device such as a terminal device 1 to a terminal device i (where i is a positive integer). In other words, in the method shown inFIG.11, the terminal device may communicate with one or more other terminal devices in the N SL-BWPs. In this application, the Y SL-BWPs including the frequency domain resource corresponding to the common resource are configured for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device by reusing the Y UL-BWPs. It should be understood that, that the Y UL-BWPs include the frequency domain resource corresponding to the common resource may mean that at least one UL-BWP in the Y UL-BWPs includes the frequency domain resource corresponding to the common resource. In some embodiments, the common resource includes K common sub-resources, and K is a positive integer greater than 1. For example, the common resource is configured by using the resource configuration information, and the common resource includes three common sub-resources. Assuming that the uplink BWP indication information indicates three UL-BWPs, only one UL-BWP in the three UL-BWPs may include frequency domain resources corresponding to all of the three common sub-resources, or two UL-BEPs in the three UL-BWPs may include frequency domain resources corresponding to all of the three common sub-resources, or each of the three UL-BWPs may include a frequency domain resource corresponding to one common sub-resource. In some embodiments, the method shown inFIG.11further includes step240. Step240includes: The network device sends uplink BWP configuration information to the terminal device, and the terminal device receives the uplink BWP configuration information, where the uplink BWP configuration information is used to configure X UL-BWPs for the terminal device. The Y UL-BWPs belong to the X UL-BWPs, and X is a positive integer greater than or equal to Y. The Y UL-BWPs may be BWPs activated by the network device in the X UL-BWPs. In some embodiments, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the common resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. It should be understood that, in addition to carrying the multiplexing format indication information, the resource configuration information may further carry transmission mode indication information and numerology (numerology) indication information, to indicate a transmission mode and a numerology that are used when sidelink communication is performed on the common resource. In some embodiments, the resource configuration information carries the transmission mode indication information, the transmission mode indication information is used to indicate the transmission mode used when the terminal device performs sidelink communication on the common resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information carries the numerology indication information, the numerology indication information is used to indicate the numerology used when the terminal device performs sidelink communication on the common resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. It should be understood that sidelink communication may be performed between terminal devices on the common resource. In some cases, some terminal devices have a relatively high requirement on service reliability, or have a relatively high requirement on data confidentiality in sidelink communication. In this case, a dedicated resource may be configured for some terminal devices, so that these terminal devices perform sidelink communication on the dedicated resource. Therefore, in addition to configuring the common resource for the terminal device by using the resource configuration information, the network device may further configure a dedicated resource for the terminal device by using the resource configuration information. In some embodiments, the resource configuration information is further used to configure the dedicated resource for the terminal device, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the dedicated resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. In some embodiments, the resource configuration information further carries transmission mode indication information, the transmission mode indication information is used to indicate a transmission mode used when the terminal device performs sidelink communication on the dedicated resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). Therefore, the network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information further carries numerology indication information, the numerology indication information is used to indicate a numerology used when the terminal device performs sidelink communication on the dedicated resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. The dedicated resource may be specifically a dedicated resource pool. The network device may configure dedicated resources for some terminal devices based on characteristics of sidelink communication and requirements in sidelink communication, so that the some terminal devices perform sidelink communication by using the configured dedicated resources, thereby improving system performance. The foregoing describes the sidelink communication method in the embodiments of this application in detail with reference toFIG.11. To better understand the sidelink communication method in the embodiments of this application, the following describes in detail a process of performing sidelink communication between a terminal device 1 and a terminal device 2 with reference to an example 2 (corresponding toFIG.12toFIG.14). In the example 2, the network device configures a UL-BWP including a common resource (where the common resource may be a common resource pool) for the terminal device, so that the terminal device can perform sidelink communication by reusing the resource pool of the UL-BWP. With reference toFIG.12, the following describes in detail a complete process of sidelink communication between the terminal device 1 and the terminal device 2 in the example 2. With reference toFIG.12, the following uses an example in which the common resource is the common resource pool, to describe in detail the complete process of sidelink communication between the terminal device 1 and the terminal device 2 in the example 2. A method shown inFIG.12includes step2001to step2006. The following describes the steps in detail.2001. The network device configures a resource pool for the terminal device 1.2002. The network device configures a resource pool for the terminal device 2. It should be understood that step2002may be performed before step2001, or may be performed after step2001, or step2002and step2001are simultaneously performed. In step2001and step2002, the network device may configure resource pool information for the terminal device 1 and the terminal device 2 by using a SIB, cell-specific RRC signaling, or UE-specific RRC signaling. The resource pool information indicates N resource pools, and the N resource pools include at least M common resource pools and N-M dedicated resource pools, where N≥1, and 1≤M≤N. For example, as shown inFIG.13, the network device configures two common resource pools and two dedicated resource pools, which are a common resource pool 1 (CommonResourcePool #1), a common resource pool 2 (CommonResourcePool #2), a dedicated resource pool 1 (DedicatedResourcePool #1), and a dedicated resource pool 2 (DedicatedResourcePool #2).2003. The network device configures X UL-BWPs for the terminal device 1.2004. The network device configures X UL-BWPs for the terminal device 2. In step2003and step2004, the network device may configure the BWPs for the terminal devices through RRC signaling.2005. The network device activates Y UL-BWPs for the terminal device 1.2006. The network device activates Y UL-BWPs for the terminal device 2. In step2005and step2006, the network device may activate the Y BWPs by sending activation signaling to the terminal device 1 and the terminal device 2. For the terminal device 1, the activated Y UL-BWPs include the common resource pool 1 and the common resource pool 2, that is, include all common resource pools. For the terminal device 2, the activated Y UL-BWPs also include the common resource pool 1 and the common resource pool 2. Using the terminal device 1 as an example, that the N UL-BWPs include all common resource pools means that at least one of the N UL-BWPs includes all the common resource pools. It should be understood that the terminal device 1 and the terminal device 2 may include different quantities of activated UL-BWPs, and sidelink communication can be performed between the terminal device 1 and the terminal device 2 provided that at least one UL-BWP in the activated UL-BWPs includes all the common resource pools. 2007. The terminal device 1 performs sidelink communication with the terminal device 2 in the activated UL-BWPs. In the example 2, the terminal device may not only perform sidelink communication with another terminal device on a time-frequency resource in a common resource pool, but also perform sidelink communication with another terminal device on a time-frequency resource in a dedicated resource pool. Different from the common resource pool, the dedicated resource pool is usually a resource configured by the network device based on a capability or a requirement of the terminal device or selected by a user based on a pre-configured resource or by performing sensing (sensing), and is configured for UL-BWPs of some terminal devices. With reference toFIG.14, the following describes in detail a process of performing sidelink communication on resources in a common resource pool and a dedicated resource pool. For example, as shown inFIG.14, the network device configures two common resource pools and two dedicated resource pools, which are a common resource pool 1 (CommonResourcePool #1), a common resource pool 2 (CommonResourcePool #2), a dedicated resource pool 1 (DedicatedResourcePool #1), and a dedicated resource pool 2 (DedicatedResourcePool #2). Assuming that a cell has four terminal users, which are UE-A, UE-B, UE-C, and UE-D, the network device configures UL-BWPs for the four UEs through RRC signaling, and the UL-BWPs of the UEs are: UE-A: UE-A UL-BWP; UE-B: UE-B UL-BWP; UE-C: UE-C UL-BWP; and UE-D: UE-D UL-BWP. Each UE has one UL-BWP that covers the common resource pool 1 and the common resource pool 2. Further, the UE-B UL-BWP covers only the common resource pool 1 and the common resource pool 2. Therefore, the UE-B can perform sidelink communication only on a time-frequency resource in the common resource pool 1 and the common resource pool 2. The UE-C UL-BWP not only covers the common resource pool 1 and the common resource pool 2, but also covers the dedicated resource pool 2. The UE-A UL-BWP not only covers the common resource pool 1 and the common resource pool 2, but also covers the dedicated resource pool 1. The UE-D UL-BWP covers all common resource pools and all dedicated resource pools. Therefore, in addition to performing sidelink communication with the other three UEs on time-frequency resources in the dedicated resource pool 1 and the dedicated resource pool 2, the UE-D may further communicate with the UE-A on a resource in the dedicated resource pool 1, and may further communicate with the UE-C on a time-frequency resource in the dedicated resource pool 2. In addition, in the example 2, when the network device configures the resource pools, configuration information may further include at least one of the following information: (1) Multiplexing format indication information of sidelink control information (SA) and sidelink data (2) Transmission mode in sidelink communication (2) Subcarrier spacing (SCS) indication information (3) Cyclic prefix (CP) indication information For a specific indication manner of the indication information, refer to related content in the example 1. Details are not described herein again. FIG.15is a schematic block diagram of a terminal device according to an embodiment of this application. The terminal device30000inFIG.15corresponds to the foregoing methods shown inFIG.11andFIG.12. The terminal device30000can perform steps performed by the terminal device in the method shown inFIG.11, and the terminal device30000may further perform steps performed by the terminal device 1 in the method shown inFIG.12. Limitations and explanations of the steps in the sidelink communication methods in the embodiments of this application inFIG.11andFIG.12are also applicable to steps performed by the terminal device30000shown inFIG.15. For brevity, repeated descriptions are appropriately omitted in the following description of the terminal device30000shown inFIG.15. The terminal device30000shown inFIG.15includes: a receiving unit30010, configured to receive resource configuration information sent by a network device, where the resource configuration information is used to configure a common resource for the terminal device, and the common resource is a resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication, where the receiving unit30010is further configured to receive uplink BWP indication information sent by the network device, where the uplink BWP indication information is used to indicate Y UL-BWPs, and the Y UL-BWPs include a frequency domain resource corresponding to the common resource, where Y is a positive integer; and a sidelink communication unit30020, configured to perform sidelink communication with another terminal device in the Y UL-BWPs. When the sidelink communication is that the terminal device sends sidelink control information or sidelink data to the another terminal device, the sidelink communication unit30020may be a transceiver unit or a sending unit. When the sidelink communication is that the terminal device receives sidelink acknowledgement information or feedback information from the another terminal device, the sidelink communication unit30020may be a transceiver unit or the receiving unit30010. In some embodiments, the common resource is specifically a common resource pool. In this application, the Y SL-BWPs including the frequency domain resource corresponding to the common resource are configured for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device by reusing the Y UL-BWPs. In some embodiments, the receiving unit30010is further configured to receive uplink BWP configuration information sent by the network device, where the uplink BWP configuration information is used to configure X UL-BWPs for the terminal device, and the Y UL-BWPs belong to the X UL-BWPs, where X is a positive integer greater than or equal to Y. In some embodiments, in an embodiment, the uplink BWP configuration information carries X pieces of multiplexing format indication information, the X pieces of multiplexing format indication information are in a one-to-one correspondence with the X UL-BWPs, any one piece of multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication by using a UL-BWP corresponding to the multiplexing format indication information, and the multiplexing format includes frequency division multiplexing and time division multiplexing. The network device may flexibly configure sidelink resources based on a service type or another requirement, to improve system performance. FIG.16is a schematic block diagram of a network device according to an embodiment of this application. The network device40000inFIG.16corresponds to the foregoing methods shown inFIG.11andFIG.12. The network device40000can perform the steps performed by the network device in the methods shown inFIG.11andFIG.12. It should be understood that, limitations and explanations of the steps in the sidelink communication methods in the embodiments of this application inFIG.11andFIG.12are also applicable to steps performed by the network device40000shown inFIG.16. For brevity, repeated descriptions are appropriately omitted in the following description of the network device40000shown inFIG.16. The network device40000shown inFIG.16includes: a sending unit40010, configured to send resource configuration information to a terminal device, where the resource configuration information is used to configure a common resource for the terminal device, and the common resource is a resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication, where the sending unit40010is further configured to send uplink BWP indication information to the terminal device, where the uplink BWP indication information is used to indicate Y UL-BWPs, the Y UL-BWPs include a frequency domain resource corresponding to the common resource, and the Y UL-BWPs are used by the terminal device to perform sidelink communication with another terminal device, where Y is a positive integer. In some embodiments, the common resource is specifically a common resource pool. In this application, the network device configures the Y SL-BWPs including the frequency domain resource corresponding to the common resource for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device by reusing the Y SL-BWPs. In some embodiments, the sending unit40010is further configured to send uplink BWP configuration information to the terminal device, where the uplink BWP configuration information is used to configure X UL-BWPs for the terminal device, and the Y UL-BWPs belong to the X UL-BWPs, where X is a positive integer greater than or equal to Y. In some embodiments, the uplink BWP configuration information carries X pieces of multiplexing format indication information, the X pieces of multiplexing format indication information are in a one-to-one correspondence with the X UL-BWPs, any one piece of multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication by using a UL-BWP corresponding to the multiplexing format indication information, and the multiplexing format includes frequency division multiplexing and time division multiplexing. In some embodiments, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the common resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. It should be understood that, in addition to carrying the multiplexing format indication information, the resource configuration information may further carry transmission mode indication information and numerology (numerology) indication information, to indicate a transmission mode and a numerology that are used when sidelink communication is performed on the common resource. In some embodiments, the resource configuration information carries the transmission mode indication information, the transmission mode indication information is used to indicate the transmission mode used when the terminal device performs sidelink communication on the common resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information carries the numerology indication information, the numerology indication information is used to indicate the numerology (numerology) used when the terminal device performs sidelink communication on the common resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (cyclic prefix, CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. It should be understood that sidelink communication may be performed between terminal devices on the common resource. In some cases, some terminal devices have a relatively high requirement on service reliability, or have a relatively high requirement on data confidentiality in sidelink communication. In this case, a dedicated resource may be configured for some terminal devices, so that these terminal devices perform sidelink communication on the dedicated resource. Therefore, in addition to configuring the common resource for the terminal device by using the resource configuration information, the network device may further configure a dedicated resource for the terminal device by using the resource configuration information. In some embodiments, the resource configuration information is further used to configure the dedicated resource for the terminal device, the resource configuration information carries multiplexing format indication information, the multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent by the terminal device when the terminal device performs sidelink communication on the dedicated resource, and the multiplexing format includes frequency division multiplexing and time division multiplexing. In some embodiments, the resource configuration information further carries transmission mode indication information, the transmission mode indication information is used to indicate a transmission mode used when the terminal device performs sidelink communication on the dedicated resource, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). Therefore, the network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the resource configuration information further carries numerology indication information, the numerology indication information is used to indicate a numerology used when the terminal device performs sidelink communication on the dedicated resource, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. The dedicated resource may be specifically a dedicated resource pool. The network device may flexibly configure sidelink resources based on a service type or another requirement, to improve system performance. It should be understood that the terminal device30000and the network device40000may be configured to jointly perform the sidelink communication methods shown inFIG.11andFIG.12: The network device40000configures a resource for the terminal device30000by using resource configuration information, so that Y UL-BWPs configured for the terminal device30000include a frequency domain resource corresponding to a common resource, and further the terminal device30000can perform sidelink communication with another terminal device in the Y UL-BWPs. In addition, when the terminal device includes a memory, a transceiver, and a processor, the receiving unit30010in the terminal device30000is equivalent to the transceiver, and the sidelink communication unit30020is equivalent to the transceiver and the processor. When the network device includes a memory, a transceiver, and a processor, the sending unit40010in the network device40000is equivalent to the transceiver. The foregoing describes in detail the sidelink communication method, the terminal device, and the network device in the embodiments of this application with reference toFIG.11toFIG.16. In the methods shown inFIG.11toFIG.16, the UL-BWPs including the common resource are set for the terminal device, and sidelink communication is performed by reusing the UL-BWPs. Actually, N SL-BWPs including a common SL-BWP may alternatively be configured for the terminal device, so that the terminal device can perform sidelink communication with another terminal device in the N SL-BWPs. With reference toFIG.17andFIG.18, the following describes in detail another sidelink communication method according to the embodiments of this application. FIG.17is a schematic flowchart of a sidelink communication method according to an embodiment of this application. The method shown inFIG.17may be performed by a terminal device. The method shown inFIG.17includes step310and step320. The following describes step310and step320in detail. 310. A network device sends sidelink BWP indication information, and the terminal device receives the sidelink BWP indication information. The sidelink BWP indication information is used to indicate N sidelink bandwidth parts SL-BWPs, the N SL-BWPs are bandwidth parts BWPs used by the terminal device to perform sidelink communication, the N SL-BWPs include a common SL-BWP, and the common SL-BWP is a frequency domain resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication. 320. The terminal device performs sidelink communication with another terminal device in the N SL-BWPs. As shown inFIG.17, the another terminal device may include at least one terminal device such as a terminal device 1 to a terminal device i (where i is a positive integer). In other words, in the method shown inFIG.17, the terminal device may communicate with one or more other terminal devices in the N SL-BWPs. In this application, the N SL-BWPs including the common SL-BWP are configured for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device in the N SL-BWPs. In some embodiments, the method shown inFIG.17further includes step330, and step330includes: The terminal device receives sidelink BWP configuration information sent by the network device, where the sidelink BWP configuration information is used to configure M SL-BWPs for the terminal device, the M SL-BWPs are BWPs available for sidelink communication, and the N SL-BWPs belong to the M SL-BWPs, where M is a positive integer greater than or equal to N. The N SL-BWPs may be SL-BWPs activated by the network device in the M SL-BWPs. For example, for a sidelink service having an ultra-low latency requirement, time division multiplexing may be configured for sidelink data and sidelink control information in a same slot (slot), and for a sidelink service having a high reliability requirement, frequency division multiplexing may be configured for sidelink data and sidelink control information in a same slot. Therefore, the network device may flexibly configure sidelink resources based on a service type or another requirement, to improve system performance. In some embodiments, Y UL-BWPs and the N SL-BWPs are located on a same carrier. The UL-BWP and the SL-BWP are configured on the same carrier, so that utilization efficiency of spectrum resources can be improved. In some embodiments, the Y UL-BWPs and the N SL-BWPs include a first frequency domain resource, the first frequency domain resource belongs to the Y UL-BWPs, and the first frequency domain resource belongs to the N SL-BWPs. That is, the Y UL-BWPs and the N SL-BWPs include a same frequency domain resource (where there is an intersection between frequency domain resources of the Y UL-BWPs and frequency domain resources of the N SL-BWPs). When the SL-BWP and the UL-BWP include the same frequency domain resource, some resources of the UL-BWP may be reused in the SL-BWP for sidelink communication, so that utilization efficiency of spectrum resources can be optimized. In some embodiments, the Y UL-BWPs and N SL-BWPs do not include a same frequency domain resource. Different frequency domain resources are configured for the UL-BWP and the SL-BWP, so that sidelink communication and uplink communication are independent of each other and do not interfere with each other. In some embodiments, the Y UL-BWPs and the N SL-BWPs are located on different carriers. The UL-BWP and the SL-BWP are configured on different carriers, so that sidelink communication and uplink communication can be performed on the different carriers, thereby avoiding mutual interference between the sidelink communication and the uplink communication. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. For example, for a sidelink service having an ultra-low latency requirement, time division multiplexing may be configured for sidelink data and sidelink control information in a same slot (slot), and for a sidelink service having a high reliability requirement, frequency division multiplexing may be configured for sidelink data and sidelink control information in a same slot. Therefore, the network device may flexibly configure sidelink resources based on a service type or another requirement, to improve system performance. In some embodiments, the sidelink BWP configuration information carries M pieces of multiplexing format indication information, the M pieces of multiplexing format indication information are in a one-to-one correspondence with the M SL-BWPs, any one piece of multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the multiplexing format indication information, and the multiplexing format available for the sidelink data and the sidelink control information includes frequency division multiplexing and time division multiplexing. For example, for a sidelink service having an ultra-low latency requirement, time division multiplexing may be configured for sidelink data and sidelink control information in a same slot (slot), and for a sidelink service having a high reliability requirement, frequency division multiplexing may be configured for sidelink data and sidelink control information in a same slot. In some embodiments, the sidelink BWP configuration information carries M pieces of transmission mode information, the M pieces of transmission mode information are in a one-to-one correspondence with the M SL-BWPs, any one piece of transmission mode information is used to indicate a transmission mode of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the transmission mode information, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the sidelink BWP configuration information carries M pieces of numerology (numerology) information, the M pieces of numerology information are in a one-to-one correspondence with the M SL-BWPs, any one piece of numerology information is used to indicate a numerology of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the numerology information, and the numerology includes a subcarrier spacing (SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. The foregoing describes the sidelink communication method in the embodiments of this application in detail with reference toFIG.17. To better understand the sidelink communication method in the embodiments of this application, the following describes in detail a process of performing sidelink communication between a terminal device 1 and a terminal device 2 with reference to an example 3 (corresponding toFIG.18). In the example 3, the network device does not configure a resource pool, but directly configures SL-BWPs for a plurality of terminal devices. The configured SL-BWPs include a common BWP. The common SL-BWP is a frequency domain resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication. The following uses the terminal device 1 and the terminal device 2 as an example to describe in detail a complete process of sidelink communication between the terminal device 1 and the terminal device 2 in the example 3 with reference toFIG.18. The method shown inFIG.18includes step3001to step3007, and the following describes these steps in detail.3001. The network device configures M SL-BWPs for the terminal device 1.3002. The network device configures M SL-BWPs for the terminal device 2. In step3001and step3002, the network device may configure the SL-BWPs for the terminal devices through RRC signaling.3003. The network device activates N SL-BWPs for the terminal device 1.3004. The network device activates N SL-BWPs for the terminal device 2. In step3003and step3004, the network device may activate the N SL-BWPs by sending activation signaling to the terminal device 1 and the terminal device 2. For the terminal device 1, the activated N SL-BWPs include a common BWP, and the common SL-BWP is a frequency domain resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication. It should be understood that there may be one or more common SL-BWPs. Similarly, for the terminal device 2, the activated N SL-BWPs also include the common BWP. 3005. The terminal device 1 performs sidelink communication with the terminal device 2 by using resource pools in the activated N SL-BWPs. It should be understood that the method shown inFIG.18may further include the following steps.3006. The network device configures X BWPs for the terminal device 1.3007. The network device configures X BWPs for the terminal device 2. In step3006and step3007, the terminal device may specifically configure the BWPs for the terminal device 1 and the terminal device 2 through RRC signaling. For a same terminal device, at least one BWP may be activated at a same moment for communication transmission. A BWP configured in bandwidth used for downlink communication is a DL-BWP, and a BWP configured in bandwidth used for uplink communication is a UL-BWP. It should be understood that, actions of configuring the BWPs in step3006and step3007and actions of configuring the SL-BWPs in step3001and step3002may be performed simultaneously, or may be performed in a sequence (where the BWPs are configured before the SL-BWPs, or the SL-BWPs are configured before the BWPs). It should be understood that in the example 3, the terminal device 1 or the terminal device 2 may simultaneously perform sidelink communication and uplink communication, where the sidelink communication and the uplink communication may occur on a shared carrier (shared carrier), that is, the SL-BWP and the UL-BWP are located on a same carrier. When the SL-BWP and the UL-BWP are located on a same carrier, the SL-BWP and the L-BWP may include a same frequency domain resource. Further, the SL-BWP may be all located in the UL-BWP, that is, all frequency domain resources of the UL-BWP can be reused in the SL-BWP. In addition, when the SL-BWP and the UL-BWP are located on a same carrier, a frequency domain resource of the SL-BWP may alternatively have no intersection with a frequency domain resource of the UL-BWP. In some embodiments, sidelink communication and uplink communication alternatively occur on independent carriers (shared carrier), and the SL-BWP and the UL-BWP do not overlap. That is, different resources are used on an SL and a UL. In addition, in the example 3, when the network device configures resource pools, configuration information may further include at least one of the following information: (1) Multiplexing format indication information of sidelink control information (SA) and sidelink data (2) Transmission mode in sidelink communication (2) Subcarrier spacing (SCS) indication information (3) Cyclic prefix (CP) indication information For a specific indication manner of the indication information, refer to related content in the example 1. Details are not described herein again. FIG.19is a schematic block diagram of a terminal device according to an embodiment of this application. The terminal device50000inFIG.19corresponds to the methods shown inFIG.17andFIG.18. The terminal device50000can perform steps performed by the terminal device in the method shown inFIG.17, and the terminal device50000may further perform steps performed by the terminal device 1 in the method shown inFIG.18. Limitations and explanations of the steps in the sidelink communication methods in the embodiments of this application inFIG.17andFIG.18are also applicable to steps performed by the terminal device50000shown inFIG.19. For brevity, repeated descriptions are appropriately omitted in the following description of the terminal device50000shown inFIG.19. The terminal device50000shown inFIG.19includes: a receiving unit50010, configured to receive sidelink BWP indication information sent by the network device, where the sidelink BWP indication information is used to indicate N sidelink bandwidth parts SL-BWPs, the N SL-BWPs are bandwidth parts BWPs used by the terminal device to perform sidelink communication, the N SL-BWPs include a common SL-BWP, and the common SL-BWP is a frequency domain resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication; and a sidelink communication unit50020, configured to perform sidelink communication with another terminal device in the N SL-BWPs. In this application, the N SL-BWPs including the common SL-BWP are configured for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device in the N SL-BWPs. In some embodiments, in an embodiment, the receiving unit50010is further configured to receive sidelink BWP configuration information sent by the network device, where the sidelink BWP configuration information is used to configure M SL-BWPs for the terminal device, the M SL-BWPs are BWPs available for sidelink communication, and the N SL-BWPs belong to the M SL-BWPs, where M is a positive integer greater than or equal to N. In some embodiments, in an embodiment, the receiving unit50010is further configured to receive uplink BWP indication information sent by the network device, where the uplink BWP indication information is used to indicate Y uplink bandwidth parts UL-BWPs, and Y is a positive integer. The network device may flexibly configure sidelink resources based on a service type or another requirement, to improve system performance. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on a same carrier. The UL-BWP and the SL-BWP are configured on the same carrier, so that utilization efficiency of spectrum resources can be improved. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs include a first frequency domain resource, the first frequency domain resource belongs to the Y UL-BWPs, and the first frequency domain resource belongs to the N SL-BWPs. That is, the Y UL-BWPs and the N SL-BWPs include a same frequency domain resource (where there is an intersection between frequency domain resources of the Y UL-BWPs and frequency domain resources of the N SL-BWPs). When the SL-BWP and the UL-BWP include the same frequency domain resource, some resources of the UL-BWP may be reused in the SL-BWP for sidelink communication, so that utilization efficiency of spectrum resources can be optimized. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs do not include a same frequency domain resource. Different frequency domain resources are configured for the UL-BWP and the SL-BWP, so that sidelink communication and uplink communication are independent of each other and do not interfere with each other. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on different carriers. The UL-BWP and the SL-BWP are configured on different carriers, so that sidelink communication and uplink communication can be performed on the different carriers, thereby avoiding mutual interference between the sidelink communication and the uplink communication. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. In some embodiments, in an embodiment, the sidelink BWP configuration information carries M pieces of multiplexing format indication information, the M pieces of multiplexing format indication information are in a one-to-one correspondence with the M SL-BWPs, any one piece of multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the multiplexing format indication information, and the multiplexing format available for the sidelink data and the sidelink control information includes frequency division multiplexing and time division multiplexing. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. For example, for a sidelink service having an ultra-low latency requirement, time division multiplexing may be configured for sidelink data and sidelink control information in a same slot (slot), and for a sidelink service having a high reliability requirement, frequency division multiplexing may be configured for sidelink data and sidelink control information in a same slot. In some embodiments, the sidelink BWP configuration information carries M pieces of transmission mode information, the M pieces of transmission mode information are in a one-to-one correspondence with the M SL-BWPs, any one piece of transmission mode information is used to indicate a transmission mode of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the transmission mode information, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the sidelink BWP configuration information carries M pieces of numerology information, the M pieces of numerology information are in a one-to-one correspondence with the M SL-BWPs, any one piece of numerology information is used to indicate a numerology of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the numerology information, and the numerology includes a subcarrier spacing (subcarrier spacing, SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. FIG.20is a schematic block diagram of a network device according to an embodiment of this application. The network device60000inFIG.20corresponds to the foregoing methods shown inFIG.17andFIG.18. The network device60000can perform steps performed by the network device in the methods shown inFIG.17andFIG.18. It should be understood that, limitations and explanations of the steps in the sidelink communication methods in the embodiments of this application inFIG.17andFIG.18are also applicable to steps performed by the network device60000shown inFIG.20. For brevity, repeated descriptions are appropriately omitted in the following description of the network device60000shown inFIG.20. The network device60000shown inFIG.20includes: a generation unit60010, configured to generate sidelink BWP indication information, where the sidelink BWP indication information is used to indicate N sidelink bandwidth parts SL-BWPs, the N SL-BWPs include a common SL-BWP, and the common SL-BWP is a frequency domain resource that is configured by the network device for all terminal devices within coverage of the network device and that is to be used by all the terminal devices to perform sidelink communication; and a sending unit60020, configured to send the sidelink BWP indication information to a terminal device, where the N SL-BWPs are used by the terminal device to perform sidelink communication with another terminal device. In this application, the network device configures the N SL-BWPs including the common SL-BWP for the terminal device, so that the terminal device can perform sidelink communication with the another terminal device in the N SL-BWPs. In some embodiments, in an embodiment, the sending unit60020is further configured to send sidelink BWP configuration information to the terminal device, where the sidelink BWP configuration information is used to configure M SL-BWPs for the terminal device, the M SL-BWPs are BWPs available for sidelink communication, and the N SL-BWPs belong to the M SL-BWPs, where M is a positive integer greater than or equal to N. In some embodiments, in an embodiment, the sending unit60020is further configured to send uplink BWP indication information to the terminal device, where the uplink BWP indication information is used to indicate Y uplink bandwidth parts UL-BWPs, and Y is a positive integer. The network device may flexibly configure sidelink resources based on a service type or another requirement, to improve system performance. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on a same carrier. The UL-BWP and the SL-BWP are configured on the same carrier, so that utilization efficiency of spectrum resources can be improved. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs include a first frequency domain resource, the first frequency domain resource belongs to the Y UL-BWPs, and the first frequency domain resource belongs to the N SL-BWPs. That is, the Y UL-BWPs and the N SL-BWPs include a same frequency domain resource (where there is an intersection between frequency domain resources of the Y UL-BWPs and frequency domain resources of the N SL-BWPs). When the SL-BWP and the UL-BWP include the same frequency domain resource, some resources of the UL-BWP may be reused in the SL-BWP for sidelink communication, so that utilization efficiency of spectrum resources can be optimized. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs do not include a same frequency domain resource. Different frequency domain resources are configured for the UL-BWP and the SL-BWP, so that sidelink communication and uplink communication are independent of each other and do not interfere with each other. In some embodiments, in an embodiment, the Y UL-BWPs and the N SL-BWPs are located on different carriers. The UL-BWP and the SL-BWP are configured on different carriers, so that sidelink communication and uplink communication can be performed on the different carriers, thereby avoiding mutual interference between the sidelink communication and the uplink communication. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. In some embodiments, in an embodiment, the sidelink BWP configuration information carries M pieces of multiplexing format indication information, the M pieces of multiplexing format indication information are in a one-to-one correspondence with the M SL-BWPs, any one piece of multiplexing format indication information is used to indicate a multiplexing format of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the multiplexing format indication information, and the multiplexing format available for the sidelink data and the sidelink control information includes frequency division multiplexing and time division multiplexing. The network device configures the multiplexing format, so that requirements in sidelink communication of different services of the terminal device can be met. For example, for a sidelink service having an ultra-low latency requirement, time division multiplexing may be configured for sidelink data and sidelink control information in a same slot (slot), and for a sidelink service having a high reliability requirement, frequency division multiplexing may be configured for sidelink data and sidelink control information in a same slot. In some embodiments, the sidelink BWP configuration information carries M pieces of transmission mode information, the M pieces of transmission mode information are in a one-to-one correspondence with the M SL-BWPs, any one piece of transmission mode information is used to indicate a transmission mode of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the transmission mode information, and the transmission mode includes unicast transmission (unicast), groupcast transmission (groupcast), and broadcast transmission (broadcast). The network device can flexibly configure sidelink resources based on different requirements in sidelink communication, so that an effect of sidelink communication can be improved, and system performance can be improved. In some embodiments, the sidelink BWP configuration information carries M pieces of numerology information, the M pieces of numerology information are in a one-to-one correspondence with the M SL-BWPs, any one piece of numerology information is used to indicate a numerology of sidelink data and sidelink control information that are sent when sidelink communication is performed by using an SL-BWP corresponding to the numerology information, and the numerology includes a subcarrier spacing (SCS) and a cyclic prefix (CP). The network device may flexibly configure numerologies based on different requirements in sidelink communication, to further flexibly configure sidelink resources, thereby improving an effect of sidelink communication. In addition, when the terminal device includes a memory, a transceiver, and a processor, the receiving unit50010in the terminal device50000is equivalent to the transceiver, and the sidelink communication unit50020is equivalent to the transceiver and the processor. When the network device includes a memory, a transceiver, and a processor, the generation unit60010in the network device60000is equivalent to the processor, and the sending unit60020is equivalent to the transceiver. A person of ordinary skill in the art may be aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application. It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, refer to a corresponding process in the foregoing method embodiments, and details are not described herein again. In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus embodiments are merely an example. For example, the unit division is merely logical function division and may be other division during actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms. The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments. In addition, functional units in the embodiments of this application may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit. When the functions are implemented in the form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in a form of a software product. The software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the methods described in the embodiments of this application. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc. The foregoing descriptions are merely specific implementations of this application, but are not intended to limit the protection scope of this application. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims. | 110,461 |
11943745 | DESCRIPTION OF THE EMBODIMENTS The technical scheme of the present disclosure is described below in further details in conjunction with the drawings. It should be noted that the embodiments of the present disclosure and the characteristics of the embodiments may be arbitrarily combined if no conflict is caused. Embodiment 1 Embodiment 1 illustrates a flowchart of a third radio signal and a first radio signal set according to one embodiment of the present disclosure, as shown inFIG.1. In Embodiment 1, the first node100in the present disclosure receives a third radio signal and a first radio signal set in step101, the third radio signal comprising first information; herein, the first information comprises a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; one of the Q node IDs is used for identifying a transmitter of the third radio signal; the first parameter set is used for configuring a Radio Bearer for the first node; a transmitter of the first radio signal set is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs, Q1being a positive integer greater than 1 and no greater than the Q; the first radio signal set comprises a first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set. In one embodiment, the first node receives a third radio signal and a first radio signal set. In one embodiment, a transmitter of the third radio signal is the third node in the present disclosure. In one embodiment, the third radio signal is transmitted through a PC5 interface. In one embodiment, the third radio signal is transmitted through SL. In one embodiment, the third radio signal is a Physical Sidelink Shared Channel (P S SCH). In one embodiment, the third radio signal is transmitted through a SL-Signaling Radio Bearer (SL-SRB). In one embodiment, the third radio signal is transmitted through a SL-SRB3. In one embodiment, time-frequency resources occupied by the third radio signal belong to a V2X resource pool. In one embodiment, time-frequency resources occupied by the third radio signal are reserved for sidelink transmission. In one embodiment, the first radio signal set are transmitted by a transmitter. In one embodiment, the first radio signal set comprises at least two radio signals; and the at least two radio signals in the first radio signal set are transmitted by different transmitters. In one embodiment, the first radio signal set comprises at least one radio signal. In one embodiment, the first radio signal set comprises the twelfth radio signal. In one embodiment, the first radio signal set is transmitted via a radio interface. In one embodiment, the first radio signal set is transmitted via a PC5 interface. In one embodiment, the first radio signal set is transmitted through SL. In one embodiment, any radio signal in the first radio signal set occupies a PSSCH. In one embodiment, any radio signal in the first radio signal set occupies a physical layer channel. In one embodiment, any radio signal in the first radio signal set is transmitted through a Data Radio Bearer (DRB). In one embodiment, the first radio signal set comprises at least two radio signals; and any two radio signals in the first radio signal set are received in different sidelink slots. In one embodiment, the first radio signal set comprises at least two radio signals; and at least two radio signals in the first radio signal set are received in a same sidelink slot. In one embodiment, the first radio signal set comprises at least two radio signals; and any two radio signals in the first radio signal set carry different information bits. In one embodiment, the first radio signal set comprises at least two radio signals; and any two radio signals in the first radio signal set carry different Transport Blocks (TBs). In one embodiment, time-frequency resources occupied by the first radio signal set belong to a V2X resource pool. In one embodiment, time-frequency resources occupied by the first radio signal set are reserved for sidelink transmission. In one embodiment, the third radio signal and any radio signal comprised in the first radio signal set are received in different sidelink slots. In one embodiment, the first information comprises Radio Resource Control (RRC) information. In one embodiment, the first information comprises PC5-RRC information. In one embodiment, the first information comprises all or part of Information Elements (IEs) in a piece of RRC information. In one embodiment, the first information comprises all or part of fields of an IE in a piece of RRC information. In one embodiment, the first information comprises RRCReconfigurationSidelink. In one embodiment, the first information comprises RRCReconfigurationResponseSidelink. In one embodiment, the first information comprises RRCReconfigurationRequestSidelink. In one embodiment, the first information comprises SL-ConfigDedicatedNR. In one embodiment, the first information comprises PC5-Signaling (PC5-S) information. In one embodiment, the first information is processed by higher layer protocols to generate a first bit block. In one embodiment, all or part of the first bit block is used to generate the third radio signal. In one embodiment, all or part of the first bit block is used together with a reference signal to generate the third radio signal. In one embodiment, the third radio signal is obtained by all or part of bits in the first bit block sequentially through CRC Calculation, Channel Coding, Rate matching, Scrambling, and Modulation, Layer Mapping, Antenna Port Mapping, Mapping to Virtual Resource Blocks, and Mapping from Virtual to Physical Resource Blocks, OFDM Baseband Signal Generation and Modulation and Up conversion. In one embodiment, the first information comprises a node ID group and a first configuration. In one embodiment, the node ID group is a field in the first information. In one embodiment, the node ID group is a RelayList field in the first information. In one embodiment, the node ID group is a SL-RelayList field in the first information. In one embodiment, the node ID group comprises Q node IDs, Q being a positive integer greater than 1 and no greater than 64. In one embodiment, the number of bits comprised by any of the Q node IDs is a positive integral multiple of 8. In one embodiment, the number of bits comprised by any of the Q node IDs is 8. In one embodiment, the number of bits comprised by any of the Q node IDs is 24. In one embodiment, any of the Q node IDs is a link layer ID. In one embodiment, any of the Q node IDs is a Layer 2 Identity. In one embodiment, the Q node IDs respectively indicate Q relay nodes. In one embodiment, any of the Q node IDs indicates a node. In one embodiment, a transmitter of the third radio signal comprises a node identified by a node ID out of the Q node IDs; the third radio signal comprises part of bits in the said node ID; scheduling information of the third radio signal comprises the remaining part of bits in the said node ID. In one embodiment, a transmitter of the third radio signal comprises a node identified by a node ID out of the Q node IDs; the third radio signal comprises upper 16 bits in the said node ID; scheduling information of the third radio signal comprises lower 8 bits in the said node ID. In one embodiment, the scheduling information of the third radio signal is comprised in a physical layer signaling. In one embodiment, the scheduling information of the third radio signal comprises Sidelink Control Information (SCI). In one embodiment, the first configuration is a field in the first information. In one embodiment, the first configuration is a SLRB-Config field in the first information. In one embodiment, the first configuration is a slrb-ConfigToAddModList field in the first information. In one embodiment, the first parameter set comprises at least one of a Service Data Adaptation Protocol (SDAP) configuration parameter, a Packet Data Convergence Protocol (PDCP) configuration parameter, a Radio Link Control (RLC) configuration parameter, or a Medium Access Control (MAC) configuration parameter. In one embodiment, the first parameter set is used for configuring a Radio Bearer for the first node. In one embodiment, the Radio Bearer for the first node is bi-directional. In one embodiment, the first parameter set comprises a first radio bearer ID, the first radio bearer ID indicating the Radio Bearer for the first node. In one embodiment, the first radio bearer ID indicates a Peer-to-Peer radio bearer. In one embodiment, the first parameter set comprises an LCID corresponding to the Radio Bearer for the first node. In one embodiment, the Radio Bearer for the first node corresponds to a higher layer entity of the first node. In one embodiment, the LCID corresponding to the Radio Bearer for the first node is used to determine a higher layer entity processing a packet that belongs to the Radio Bearer. In one embodiment, the LCID corresponding to the Radio Bearer for the first node is used to determine an RLC entity processing a MAC SDU that belongs to the Radio Bearer. In one embodiment, the first parameter set is used for configuring the higher layer entity corresponding to the Radio Bearer for the first node. In one embodiment, the higher layer entity corresponding to the Radio Bearer for the first node comprises at least one of an SDAP entity, a PDCP entity, an RLC entity or a MAC entity. In one embodiment, the Radio Bearer for the first node is used for transmitting traffics to which the first MAC SDU set belongs. In one embodiment, the Radio Bearer for the first node is used for transmitting Quality of Service (QoS) streams to which the first MAC SDU set belongs. In one embodiment, the Radio Bearer for the first node is used for transmitting PC5 QoS streams to which the first MAC SDU set belongs. In one embodiment, the Radio Bearer for the first node is a DRB. In one embodiment, the Radio Bearer for the first node is a SL-SRB. In one embodiment, the Radio Bearer for the first node is a SL-RLC Bearer. In one embodiment, the Radio Bearer for the first node is a PDCP Bearer. In one embodiment, the Radio Bearer for the first node is an SDAP Bearer. In one embodiment, the first parameter set is applicable to the first MAC SDU set. In one embodiment, the first MAC SDU set is processed in the SDAP entity, the PDCP entity and the RLC entity of the first node. In one embodiment, the first MAC SDU set is processed in the PDCP entity and the RLC entity of the first node. In one embodiment, a transmitter of the first radio signal set is identified by one of the Q node IDs. In one embodiment, a transmitter of the first radio signal set and a transmitter of the third radio signal are identified by a same node ID of the Q node IDs. In one embodiment, a transmitter of any radio signal in the first radio signal set is identified by a node ID of the Q node IDs; the said radio signal comprises part of bits in the said node ID; scheduling information of the said radio signal comprises the remaining part of bits in the said node ID; the scheduling information of the said radio signal comprises SCI. In one embodiment, transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs; any two of the Q1node IDs are different. In one embodiment, any two radio signals of the Q1radio signals in the first radio signal set are received in different sidelink slots. In one embodiment, at least two radio signals of the Q1radio signals in the first radio signal set are received in a same sidelink slot. In one embodiment, a transmitter that transmits any radio signal in the first radio signal set other than the Q1radio signals is identified by a node ID of the Q node IDs other than the Q1node IDs. In one embodiment, a transmitter that transmits at least one radio signal in the first radio signal set other than the Q1radio signals is identified by one of the Q1node IDs of the Q node IDs. In one embodiment, the first radio signal set comprises a first MAC SDU set. In one embodiment, the first MAC SDU set comprises at least one MAC SDU. In one embodiment, the first radio signal set comprises at least two radio signals; and any two radio signals in the first radio signal set comprise different MAC SDUs. In one embodiment, the first radio signal set comprises at least two radio signals; and at least two radio signals in the first radio signal set comprise a same MAC SDU. Embodiment 2 Embodiment 2 illustrates a schematic diagram of a network architecture according to one embodiment of the present disclosure, as shown inFIG.2.FIG.2is a diagram illustrating a V2X communication architecture of NR 5G, Long-Term Evolution (LTE), and Long-Term Evolution Advanced (LTE-A) systems. The NR 5G or LTE, or LTE-A network architecture may be called a 5G System/Evolved Packet System (5GS/EPS)200or other appropriate terms. The V2X communication architecture in Embodiment 2 may comprise a UE201, a UE241in communication with UE201, an NG-RAN202, a 5G Core Network/Evolved Packet Core (5GC/EPC)210, a Home Subscriber Server (HSS)/Unified Data Management (UDM)220, a ProSe feature250and a ProSe application server230. The V2X communication architecture may be interconnected with other access networks. For simple description, the entities/interfaces are not shown. As shown inFIG.2, the V2X communication architecture provides packet switching services. Those skilled in the art will readily understand that various concepts presented throughout the present disclosure can be extended to networks providing circuit switching services. The NG-RAN202comprises an NR node B (gNB)203and other gNBs204. The gNB203provides UE201-oriented user plane and control plane protocol terminations. The gNB203may be connected to other gNBs204via an Xn interface (for example, backhaul). The gNB203may be called a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Base Service Set (BSS), an Extended Service Set (ESS), a Transmitter Receiver Point (TRP) or some other applicable terms. The gNB203provides an access point of the 5GC/EPC210for the UE201. Examples of UE201include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, Personal Digital Assistant (PDA), Satellite Radios, Global Positioning Systems (GPS), multimedia devices, video devices, digital audio players (for example, MP3 players), cameras, games consoles, unmanned aerial vehicles, air vehicles, narrow-band physical network equipment, machine-type communication equipment, land vehicles, automobiles, vehicle-mounted communication units, wearables, or any other devices having similar functions. Those skilled in the art also can call the UE201a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a radio communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user proxy, a mobile client, a client or some other appropriate terms. The gNB203is connected to the 5GC/EPC210via an S/NG interface. The 5GC/EPC210comprises a Mobility Management Entity (MME)/Authentication Management Field (AMF)/Session Management Function (SMF)211, other MMES/AMFs/SMFs214, a Service Gateway (S-GW)/User Plane Function (UPF)212and a Packet Date Network Gateway (P-GW)/UPF213. The MME/AMF/SMF211is a control node for processing a signaling between the UE201and the 5GC/EPC210. Generally, the MME/AMF/SMF211provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW/UPF212. The S-GW/UPF212is connected to the P-GW/UPF213. The P-GW213provides UE IP address allocation and other functions. The P-GW/UPF213is connected to the Internet Service230. The Internet Service230comprises operator-compatible IP services, specifically including Internet, Intranet, IP Multimedia Subsystem (IMS) and Packet Switching (PS) Streaming services. The ProSe feature250refers to logical functions of network-related actions needed for Proximity-based Service (ProSe), including Direct Provisioning Function (DPF), Direct Discovery Name Management Function and EPC-level Discovery ProSe Function. The ProSe application server230is featured with functions like storing EPC ProSe user ID, and mapping between an application-layer user ID and an EPC ProSe user ID as well as allocating ProSe-restricted code-suffix pool. In one embodiment, the UE201corresponds to the first node in the present disclosure, and the UE241corresponds to the third node in the present disclosure. In one embodiment, the UE201corresponds to the second node in the present disclosure, and the UE241corresponds to the third node in the present disclosure. In one embodiment, the UE201and the UE241respectively support transmissions in SL. In one embodiment, the UE201and the UE241respectively support PC5 interfaces. In one embodiment, the UE201and the UE241respectively support Vehicle-to-Everything (V2X). In one embodiment, the UE201and the UE241respectively support V2X services. In one embodiment, the UE201and the UE241respectively support D2D services. In one embodiment, the UE201and the UE241respectively support public safety services. In one embodiment, the gNB203supports Vehicle-to-Everything (V2X). In one embodiment, the gNB203supports V2X services. In one embodiment, the gNB203supports D2D services. In one embodiment, the gNB203supports public safety services. In one embodiment, the gNB203is a Macro Cell base station. In one embodiment, the gNB203is a Micro Cell base station. In one embodiment, the gNB203is a Pico Cell base station. In one embodiment, the gNB203is a Femtocell. In one embodiment, the gNB203is a base station supporting large time-delay difference. In one embodiment, the gNB203is a flight platform. In one embodiment, the gNB203is satellite equipment. In one embodiment, a radio link from the UE201to the gNB203is uplink. In one embodiment, a radio link from the gNB203to the UE201is downlink. In one embodiment, a radio link between the UE201and the UE241corresponds to the sidelink in the present disclosure. In one embodiment, the UE201and the gNB203are connected by a Uu interface. In one embodiment, the UE201and the UE241are connected by a PC5 Reference Point. In one embodiment, the ProSe feature250is connected to the UE201and the UE241respectively by PC3 Reference Points. In one embodiment, the ProSe feature250is connected to the ProSe application server230by a PC2 Reference Point. In one embodiment, the ProSe application server230is respectively connected to the ProSe applications of the UE201and the UE241by PC1 Reference Points. Embodiment 3 Embodiment 3 illustrates a schematic diagram of a radio protocol architecture of a user plane and a control plane according to one embodiment of the present disclosure, as shown inFIG.3.FIG.3is a schematic diagram illustrating an embodiment of a radio protocol architecture of a user plane350and a control plane300. InFIG.3, the radio protocol architecture for a control plane300between a UE and a gNB is represented by three layers, which are a layer 1, a layer 2 and a layer 3, respectively. The layer 1 (L1) is the lowest layer which performs signal processing functions of various PHY layers. The L1 is called PHY301in the present disclosure. The layer 2 (L2)305is above the PHY301, and is in charge of the link between the UE and the gNB via the PHY301. The L2305comprises a Medium Access Control (MAC) sublayer302, a Radio Link Control (RLC) sublayer303and a Packet Data Convergence Protocol (PDCP) sublayer304. All the three sublayers terminate at the gNBs of the network side. The PDCP sublayer304provides data encryption and integrity protection, and also support for handover of a UE between gNBs. The RLC sublayer303provides segmentation and reassembling of a packet, retransmission of a lost packet through ARQ, and detection of duplicate packets and protocol errors. The MAC sublayer302provides mappings between a logical channel and a transport channel as well as multiplexing of logical channel ID. The MAC sublayer302is also responsible for allocating between UEs various radio resources (i.e., resource block) in a cell. The MAC sublayer302is also in charge of Hybrid Automatic Repeat Request (HARM) operation. In the control plane300, The Radio Resource Control (RRC) sublayer306in the L3 layer is responsible for acquiring radio resources (i.e., radio bearer) and configuring the lower layer using an RRC signaling between the gNB and the UE. Although not shown in the figure, above the RRC sublayer306in the control plane300of the UE there can be a V2X layer, which is in charge of generating a PC5 QoS parameter group and a QoS rule according to received traffic data or traffic requests, generating a PC5 QoS flow corresponding to the PC5 QoS parameter group and sending a PC5 QoS flow ID and the corresponding PC5 QoS parameter group to a Access Stratum (AS) to be used for QoS processing of a packet that belongs to the PC5 QoS flow ID; the V2X layer is also responsible for indicating whether each transmission in the AS layer is a PC5-Signaling (PC5-S) Protocol transmission or a V2X traffic data transmission. The radio protocol architecture of the user plane350comprises a layer 1 (L1) and a layer 2 (L2). In the user plane350, the radio protocol architecture used for a PHY layer351, a PDCP sublayer354of the L2 layer355, an RLC sublayer353of the L2 layer355and a MAC sublayer352of the L2 layer355is almost the same as the radio protocol architecture used for corresponding layers and sublayers in the control plane300, but the PDCP sublayer354also provides header compression used for higher-layer packet to reduce radio transmission overhead. The L2 layer355in the user plane350also comprises a Service Data Adaptation Protocol (SDAP) sublayer356, which is in charge of the mapping between QoS streams and a Data Radio Bearer (DRB), so as to support diversified traffics. The radio protocol architecture of UE in the user plane350may comprise all or part of protocol sublayers of a SDAP sublayer356, a PDCP sublayer354, a RLC sublayer353and a MAC sublayer352. Although not described inFIG.3, the UE may comprise several higher layers above the L2355, such as a network layer (i.e., IP layer) terminated at a P-GW213of the network side and an application layer terminated at the other side of the connection (i.e., a peer UE, a server, etc.). In one embodiment, the ninth radio signal in the present disclosure is generated by the PHY301or the PHY351. In one embodiment, the tenth radio signal in the present disclosure is generated by the PHY301or the PHY351. In one embodiment, the eleventh radio signal in the present disclosure is generated by the PHY301or the PHY351. In one embodiment, the twelfth radio signal in the present disclosure is generated by the PHY301or the PHY351. In one embodiment, the first information in the present disclosure is generated by the RRC306. In one embodiment, the first information in the present disclosure is generated by the PC5-S. In one embodiment, the second information in the present disclosure is generated by the RRC306. In one embodiment, the second information in the present disclosure is generated by the PC5-S. In one embodiment, the third information in the present disclosure is generated by the RRC306. In one embodiment, the third information in the present disclosure is generated by the PC5-S. In one embodiment, the fourth information set in the present disclosure is generated by the RRC306. In one embodiment, the fourth information set in the present disclosure is generated by the PC5-S. In one embodiment, the fifth information in the present disclosure is generated by the RRC306. In one embodiment, the fifth information in the present disclosure is generated by the PC5-S. In one embodiment, the sixth information in the present disclosure is generated by the RRC306. In one embodiment, the sixth information in the present disclosure is generated by the PC5-S. In one embodiment, the seventh information in the present disclosure is generated by the RRC306. In one embodiment, the seventh information in the present disclosure is generated by the PC5-S. In one embodiment, the eighth information set in the present disclosure is generated by the RRC306. In one embodiment, the eighth information set in the present disclosure is generated by the PC5-S. In one embodiment, the ninth information in the present disclosure is generated by the RRC306. In one embodiment, the ninth information in the present disclosure is generated by the PC5-S. In one embodiment, the L2305belongs to a higher layer. In one embodiment, the RRC sublayer306in the L3 belongs to a higher layer. In one embodiment, the V2X layer belongs to a Non-Access Stratum (NAS). In one embodiment, the V2X layer belongs to an upper layer. In one embodiment, the PC5-S in the V2X layer belongs to an upper layer. Embodiment 4 Embodiment 4 illustrates a schematic diagram of hardcore modules in a communication device according to one embodiment of the present disclosure, as shown inFIG.4.FIG.4is a block diagram of a first communication device450and a third communication device410in communication with each other in an access network. The first communication device450comprises a controller/processor459, a memory460, a data source467, a transmitting processor468, a receiving processor456, a multi-antenna transmitting processor457, a multi-antenna receiving processor458, a transmitter/receiver454and an antenna452. The third communication device410comprises a controller/processor475, a memory476, a data source477, a receiving processor470, a transmitting processor416, a multi-antenna receiving processor472, a multi-antenna transmitting processor471, a transmitter/receiver418and an antenna420. In a transmission from the third communication device410to the first communication device450, at the third communication device410, a higher layer packet from a core network or a data source477is provided to the controller/processor475. The core network and the data source477represent all protocol layers above the L2. The controller/processor475implements the functionality of the L2 layer. In the transmission from the third communication device410to the first communication device450, the controller/processor475provides header compression, encryption, packet segmentation and reordering, multiplexing between a logical channel and a transport channel and radio resource allocation of the first communication device450based on various priorities. The controller/processor475is also in charge of a retransmission of a lost packet and a signaling to the first communication device450. The transmitting processor416and the multi-antenna transmitting processor471perform various signal processing functions used for the L1 layer (i.e., PHY). The transmitting processor416performs coding and interleaving so as to ensure a Forward Error Correction (FEC) at the third communication device410side and the mapping of signal clusters corresponding to each modulation scheme (i.e., BPSK, QPSK, M-PSK, and M-QAM, etc.). The multi-antenna transmitting processor471performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on encoded and modulated symbols to generate one or more spatial streams. The transmitting processor416then maps each spatial stream into a subcarrier. The mapped symbols are multiplexed with a reference signal (i.e., pilot frequency) in time domain and/or frequency domain, and then they are assembled through Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying time-domain multicarrier symbol streams. After that the multi-antenna transmitting processor471performs transmission analog precoding/beamforming on the time-domain multicarrier symbol streams. Each transmitter418converts a baseband multicarrier symbol stream provided by the multi-antenna transmitting processor471into a radio frequency (RF) stream, which is later provided to antennas420. In a transmission from the third communication device410to the first communication device450, at the first communication device450, each receiver454receives a signal via a corresponding antenna452. Each receiver454recovers information modulated onto the RF carrier, and converts the radio frequency stream into a baseband multicarrier symbol stream to be provided to the receiving processor456. The receiving processor456and the multi-antenna receiving processor458perform signal processing functions of the L1 layer. The multi-antenna receiving processor458performs reception analog precoding/beamforming on a baseband multicarrier symbol stream provided by the receiver454. The receiving processor456converts the processed baseband multicarrier symbol stream from time domain into frequency domain using FFT. In frequency domain, a physical layer data signal and a reference signal are de-multiplexed by the receiving processor456, wherein the reference signal is used for channel estimation, while the data signal is subjected to multi-antenna detection in the multi-antenna receiving processor458to recover any first communication device450-targeted spatial stream. Symbols on each spatial stream are demodulated and recovered in the receiving processor456to generate a soft decision. Then the receiving processor456decodes and de-interleaves the soft decision to recover the higher-layer data and control signal transmitted by the third communication device410. Next, the higher-layer data and control signal are provided to the controller/processor459. The controller/processor459performs functions of the L2 layer. The controller/processor459can be associated with a memory460that stores program code and data. The memory460can be called a computer readable medium. In the transmission from the third communication device410to the first communication device450, the controller/processor459provides demultiplexing between a transport channel and a logical channel, packet reassembling, decrypting, header decompression and control signal processing so as to recover a higher-layer packet from the third communication device410. The higher-layer packet is later provided to all protocol layers above the L2 layer, or various control signals can be provided to the L3 layer for processing. In a transmission from the first communication device450to the third communication device410, at the first communication device450, the data source467is configured to provide a higher-layer packet to the controller/processor459. The data source467represents all protocol layers above the L2 layer. Similar to a transmitting function of the third communication device410described in the transmission from the third communication device410to the first communication device450, the controller/processor459performs header compression, encryption, packet segmentation and reordering, and multiplexing between a logical channel and a transport channel based on radio resource allocation so as to provide the L2 layer functions used for the user plane and the control plane. The controller/processor459is also responsible for a retransmission of a lost packet, and a signaling to the third communication device410. The transmitting processor468performs modulation and mapping, as well as channel coding, and the multi-antenna transmitting processor457performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming. The transmitting processor468then modulates generated spatial streams into multicarrier/single-carrier symbol streams. The modulated symbol streams, after being subjected to analog precoding/beamforming in the multi-antenna transmitting processor457, are provided from the transmitter454to each antenna452. Each transmitter454first converts a baseband symbol stream provided by the multi-antenna transmitting processor457into a radio frequency symbol stream, and then provides the radio frequency symbol stream to the antenna452. In a transmission from the first communication device450to the third communication device410, the function of the third communication device410is similar to the receiving function of the first communication device450described in the transmission from the third communication device410to the first communication device450. Each receiver418receives a radio frequency signal via a corresponding antenna420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna receiving processor472and the receiving processor470. The receiving processor470and the multi-antenna receiving processor472jointly provide functions of the L1 layer. The controller/processor475provides functions of the L2 layer. The controller/processor475can be associated with the memory476that stores program code and data. The memory476can be called a computer readable medium. In the transmission from the first communication device450to the third communication device410, the controller/processor475provides de-multiplexing between a transport channel and a logical channel, packet reassembling, decrypting, header decompression, control signal processing so as to recover a higher-layer packet from the first communication device450. The higher-layer packet coming from the controller/processor475may be provided to the core network, or all protocol layers above the L2, or, various control signals can be provided to the core network or L3 for processing. In one embodiment, the first communication device450comprises at least one processor and at least one memory. The at least one memory comprises computer program codes; the at least one memory and the computer program codes are configured to be used in collaboration with the at least one processor. The first communication device450at least receives a third radio signal and a first radio signal set, the third radio signal comprising first information; herein, the first information comprises a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; one of the Q node IDs is used for identifying a transmitter of the third radio signal; the first parameter set is used for configuring a Radio Bearer for the first node; a transmitter of the first radio signal set is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs, Q1being a positive integer greater than 1 and no greater than the Q; the first radio signal set comprises a first MAC Service Data Unit (SDU) set, and the first parameter set is applicable to the first MAC SDU set. In one embodiment, the first communication device450comprises a memory that stores a computer readable instruction program. The computer readable instruction program generates actions when executed by at least one processor. The actions include: receiving a third radio signal and a first radio signal set, the third radio signal comprising first information; herein, the first information comprises a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; one of the Q node IDs is used for identifying a transmitter of the third radio signal; the first parameter set is used for configuring a Radio Bearer for the first node; a transmitter of the first radio signal set is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs, Q1being a positive integer greater than 1 and no greater than the Q; the first radio signal set comprises a first MAC Service Data Unit (SDU) set, and the first parameter set is applicable to the first MAC SDU set. In one embodiment, the third communication device410comprises at least one processor and at least one memory. The at least one memory comprises computer program codes; the at least one memory and the computer program codes are configured to be used in collaboration with the at least one processor. The third communication device410at least receives a fourth radio signal and an eleventh radio signal, the eleventh radio signal belonging to a second radio signal set; transmits a third radio signal and a twelfth radio signal, the twelfth radio signal belonging to a first radio signal set; herein, the third radio signal and the fourth radio signal respectively comprise first information, the first information comprising a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; the first parameter set is used for configuring a Radio Bearer for a target receiver of the twelfth radio signal; the third node is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs and the third node is identified by one of the Q1node IDs, Q1being a positive integer greater than 1 and no greater than the Q; the first radio signal set and the second radio signal set respectively comprise a first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set. In one embodiment, the third communication device410comprises a memory that stores a computer readable instruction program. The computer readable instruction program generates actions when executed by at least one processor. The actions include: receiving a fourth radio signal and an eleventh radio signal, the eleventh radio signal belonging to a second radio signal set; transmitting a third radio signal and a twelfth radio signal, the twelfth radio signal belonging to a first radio signal set; herein, the third radio signal and the fourth radio signal respectively comprise first information, the first information comprising a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; the first parameter set is used for configuring a Radio Bearer for a target receiver of the twelfth radio signal; the third node is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs and the third node is identified by one of the Q1node IDs, Q1being a positive integer greater than 1 and no greater than the Q; the first radio signal set and the second radio signal set respectively comprise a first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set. In one embodiment, the first communication device450corresponds to a first node in the present disclosure. In one embodiment, the third communication device410corresponds to a third node in the present disclosure. In one embodiment, the first communication device450is a UE. In one embodiment, the first communication device450is a UE supporting V2X. In one embodiment, the first communication device450is a UE supporting D2D. In one embodiment, the first communication device450is vehicle-mounted equipment. In one embodiment, the first communication device450is an RSU. In one embodiment, the third communication device410is a UE. In one embodiment, the third communication device410is a UE supporting V2X. In one embodiment, the third communication device410is a UE supporting D2D. In one embodiment, the third communication device410is vehicle-mounted equipment. In one embodiment, the third communication device410is an RSU. In one embodiment, the third communication device410is a UE. In one embodiment, at least one of the antenna420, the transmitter418, the multi-antenna transmitting processor471, the transmitting processor416or the controller/processor475is used for transmitting a third radio signal in the present disclosure. In one embodiment, at least one of the antenna452, the receiver454, the multi-antenna receiving processor458, the receiving processor456or the controller/processor459is used for receiving a third radio signal in the present disclosure. In one embodiment, at least one of the antenna452, the receiver454, the multi-antenna receiving processor458, the receiving processor456or the controller/processor459is used for receiving a first radio signal set in the present disclosure. In one embodiment, at least one of the antenna420, the transmitter418, the multi-antenna transmitting processor471, the transmitting processor416or the controller/processor475is used for transmitting a twelfth radio signal in the present disclosure. In one embodiment, at least one of the antenna452, the transmitter454, the multi-antenna transmitting processor457, the transmitting processor468or the controller/processor459is used for transmitting a fifth radio signal in the present disclosure. In one embodiment, at least one of the antenna420, the receiver418, the multi-antenna receiving processor472, the receiving processor470or the controller/processor475is used for receiving a fifth radio signal in the present disclosure. In one embodiment, at least one of the antenna452, the transmitter454, the multi-antenna transmitting processor457, the transmitting processor468or the controller/processor459is used for transmitting third information in the present disclosure. In one embodiment, at least one of the antenna420, the receiver418, the multi-antenna receiving processor472, the receiving processor470or the controller/processor475is used for receiving third information in the present disclosure. In one embodiment, at least one of the antenna452, the receiver454, the multi-antenna receiving processor458, the receiving processor456or the controller/processor459is used for receiving a fourth information set in the present disclosure. In one embodiment, at least one of the antenna420, the transmitter418, the multi-antenna transmitting processor471, the transmitting processor416or the controller/processor475is used for transmitting seventh information in the present disclosure. In one embodiment, at least one of the antenna452, the transmitter454, the multi-antenna transmitting processor457, the transmitting processor468or the controller/processor459is used for transmitting a seventh radio signal in the present disclosure. In one embodiment, at least one of the antenna420, the receiver418, the multi-antenna receiving processor472, the receiving processor470or the controller/processor475is used for receiving a seventh radio signal in the present disclosure. In one embodiment, at least one of the antenna452, the transmitter454, the multi-antenna transmitting processor457, the transmitting processor468or the controller/processor459is used for transmitting a ninth radio signal in the present disclosure. In one embodiment, at least one of the antenna420, the receiver418, the multi-antenna receiving processor472, the receiving processor470or the controller/processor475is used for receiving a ninth radio signal in the present disclosure. Embodiment 5 Embodiment 5 illustrates another schematic diagram of hardcore modules in a communication device according to one embodiment of the present disclosure, as shown inFIG.5.FIG.5is a block diagram of a second communication device550and a third communication device510in communication with each other in an access network. The second communication device550comprises a controller/processor559, a memory560, a data source567, a transmitting processor568, a receiving processor556, a multi-antenna transmitting processor557, a multi-antenna receiving processor558, a transmitter/receiver554and an antenna552. The third communication device510comprises a controller/processor575, a memory576, a data source577, a receiving processor570, a transmitting processor516, a multi-antenna receiving processor572, a multi-antenna transmitting processor571, a transmitter/receiver518and an antenna520. In a transmission from the third communication device510to the second communication device550, at the third communication device510, a higher layer packet from a core network or a data source577is provided to the controller/processor575. The core network and the data source577represent all protocol layers above the L2. The controller/processor575implements the functionality of the L2 layer. In the transmission from the third communication device510to the second communication device550, the controller/processor575provides header compression, encryption, packet segmentation and reordering, multiplexing between a logical channel and a transport channel and radio resource allocation of the second communication device550based on various priorities. The controller/processor575is also in charge of a retransmission of a lost packet and a signaling to the second communication device550. The transmitting processor516and the multi-antenna transmitting processor571perform various signal processing functions used for the L1 layer (i.e., PHY). The transmitting processor516performs coding and interleaving so as to ensure a Forward Error Correction (FEC) at the third communication device510side and the mapping of signal clusters corresponding to each modulation scheme (i.e., BPSK, QPSK, M-PSK, and M-QAM, etc.). The multi-antenna transmitting processor571performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on encoded and modulated symbols to generate one or more spatial streams. The transmitting processor516then maps each spatial stream into a subcarrier. The mapped symbols are multiplexed with a reference signal (i.e., pilot frequency) in time domain and/or frequency domain, and then they are assembled through Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying time-domain multicarrier symbol streams. After that the multi-antenna transmitting processor571performs transmission analog precoding/beamforming on the time-domain multicarrier symbol streams. Each transmitter518converts a baseband multicarrier symbol stream provided by the multi-antenna transmitting processor571into a radio frequency (RF) stream, which is later provided to antennas520. In a transmission from the third communication device510to the second communication device550, at the second communication device550, each receiver554receives a signal via a corresponding antenna552. Each receiver554recovers information modulated onto the RF carrier, and converts the radio frequency stream into a baseband multicarrier symbol stream to be provided to the receiving processor556. The receiving processor556and the multi-antenna receiving processor558perform signal processing functions of the L1 layer. The multi-antenna receiving processor558performs reception analog precoding/beamforming on a baseband multicarrier symbol stream provided by the receiver554. The receiving processor556converts the processed baseband multicarrier symbol stream from time domain into frequency domain using FFT. In frequency domain, a physical layer data signal and a reference signal are de-multiplexed by the receiving processor556, wherein the reference signal is used for channel estimation, while the data signal is subjected to multi-antenna detection in the multi-antenna receiving processor558to recover any second communication device550-targeted spatial stream. Symbols on each spatial stream are demodulated and recovered in the receiving processor556to generate a soft decision. Then the receiving processor556decodes and de-interleaves the soft decision to recover the higher-layer data and control signal transmitted by the third communication device510. Next, the higher-layer data and control signal are provided to the controller/processor559. The controller/processor559performs functions of the L2 layer. The controller/processor559can be associated with a memory560that stores program code and data. The memory560can be called a computer readable medium. In the transmission from the third communication device510to the second communication device550, the controller/processor559provides demultiplexing between a transport channel and a logical channel, packet reassembling, decrypting, header decompression and control signal processing so as to recover a higher-layer packet from the third communication device510. The higher-layer packet is later provided to all protocol layers above the L2 layer, or various control signals can be provided to the L3 layer for processing. In a transmission from the second communication device550to the third communication device510, at the second communication device550, the data source567is configured to provide a higher-layer packet to the controller/processor559. The data source567represents all protocol layers above the L2 layer. Similar to a transmitting function of the third communication device510described in the transmission from the third communication device510to the second communication device550, the controller/processor559performs header compression, encryption, packet segmentation and reordering, and multiplexing between a logical channel and a transport channel based on radio resource allocation so as to provide the L2 layer functions used for the user plane and the control plane. The controller/processor559is also responsible for a retransmission of a lost packet, and a signaling to the third communication device510. The transmitting processor568performs modulation and mapping, as well as channel coding, and the multi-antenna transmitting processor557performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming. The transmitting processor568then modulates generated spatial streams into multicarrier/single-carrier symbol streams. The modulated symbol streams, after being subjected to analog precoding/beamforming in the multi-antenna transmitting processor557, are provided from the transmitter554to each antenna552. Each transmitter554first converts a baseband symbol stream provided by the multi-antenna transmitting processor557into a radio frequency symbol stream, and then provides the radio frequency symbol stream to the antenna552. In a transmission from the second communication device550to the third communication device510, the function of the third communication device510is similar to the receiving function of the second communication device550described in the transmission from the third communication device510to the second communication device550. Each receiver518receives a radio frequency signal via a corresponding antenna520, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna receiving processor572and the receiving processor570. The receiving processor570and the multi-antenna receiving processor572jointly provide functions of the L1 layer. The controller/processor575provides functions of the L2 layer. The controller/processor575can be associated with the memory576that stores program code and data. The memory576can be called a computer readable medium. In the transmission from the second communication device550to the third communication device510, the controller/processor575provides de-multiplexing between a transport channel and a logical channel, packet reassembling, decrypting, header decompression, control signal processing so as to recover a higher-layer packet from the second communication device550. The higher-layer packet coming from the controller/processor575may be provided to the core network, or all protocol layers above the L2, or, various control signals can be provided to the core network or L3 for processing. In one embodiment, the second communication device550comprises at least one processor and at least one memory. The at least one memory comprises computer program codes; the at least one memory and the computer program codes are configured to be used in collaboration with the at least one processor. The second communication device550at least transmits a fourth radio signal and a second radio signal set, the fourth radio signal comprising first information; herein, the first information comprises a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; one of the Q node IDs is used for identifying a target receiver of the fourth radio signal; the second radio signal set comprises a first MAC SDU set, the first MAC SDU set being used to generate a first radio signal set; the first parameter set is used for configuring a Radio Bearer for a target receiver of the first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set; a transmitter of the first radio signal set is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs, Q1being a positive integer greater than 1 and no greater than the Q. In one embodiment, the second communication device550comprises a memory that stores a computer readable instruction program. The computer readable instruction program generates actions when executed by at least one processor. The actions include: transmitting a fourth radio signal and a second radio signal set, the fourth radio signal comprising first information; herein, the first information comprises a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; one of the Q node IDs is used for identifying a target receiver of the fourth radio signal; the second radio signal set comprises a first MAC SDU set, the first MAC SDU set being used to generate a first radio signal set; the first parameter set is used for configuring a Radio Bearer for a target receiver of the first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set; a transmitter of the first radio signal set is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs, Q1being a positive integer greater than 1 and no greater than the Q. In one embodiment, the second communication device550corresponds to a second node in the present disclosure. In one embodiment, the third communication device510corresponds to a third node in the present disclosure. In one embodiment, the second communication device550is a UE. In one embodiment, the second communication device550is a UE supporting V2X. In one embodiment, the second communication device550is a UE supporting D2D. In one embodiment, the second communication device550is vehicle-mounted equipment. In one embodiment, the second communication device550is an RSU. In one embodiment, at least one of the antenna552, the transmitter554, the multi-antenna transmitting processor557, the transmitting processor568or the controller/processor559is used for transmitting a fourth radio signal in the present disclosure. In one embodiment, at least one of the antenna520, the receiver518, the multi-antenna receiving processor572, the receiving processor570or the controller/processor575is used for receiving a fourth radio signal in the present disclosure. In one embodiment, at least one of the antenna552, the transmitter554, the multi-antenna transmitting processor557, the transmitting processor568or the controller/processor559is used for transmitting a second radio signal set in the present disclosure. In one embodiment, at least one of the antenna520, the receiver518, the multi-antenna receiving processor572, the receiving processor570or the controller/processor575is used for receiving an eleventh radio signal set in the present disclosure. In one embodiment, at least one of the antenna520, the transmitter518, the multi-antenna transmitting processor571, the transmitting processor516or the controller/processor575is used for transmitting a sixth radio signal in the present disclosure. In one embodiment, at least one of the antenna552, the receiver554, the multi-antenna receiving processor558, the receiving processor556or the controller/processor559is used for receiving a sixth radio signal in the present disclosure. In one embodiment, at least one of the antenna520, the transmitter518, the multi-antenna transmitting processor571, the transmitting processor516or the controller/processor575is used for transmitting an eighth radio signal in the present disclosure. In one embodiment, at least one of the antenna552, the receiver554, the multi-antenna receiving processor558, the receiving processor556or the controller/processor559is used for receiving an eighth radio signal in the present disclosure. In one embodiment, at least one of the antenna520, the transmitter518, the multi-antenna transmitting processor571, the transmitting processor516or the controller/processor575is used for transmitting a tenth radio signal in the present disclosure. In one embodiment, at least one of the antenna552, the receiver554, the multi-antenna receiving processor558, the receiving processor556or the controller/processor559is used for receiving a tenth radio signal in the present disclosure. In one embodiment, at least one of the antenna552, the transmitter554, the multi-antenna transmitting processor557, the transmitting processor568or the controller/processor559is used for transmitting an eighth information set in the present disclosure. In one embodiment, at least one of the antenna520, the receiver518, the multi-antenna receiving processor572, the receiving processor570or the controller/processor575is used for receiving ninth information in the present disclosure. Embodiment 6 Embodiment 6 illustrates a flowchart of radio signal transmission according to one embodiment of the present disclosure, as shown inFIG.6. InFIG.6, a second node U1and a third node U2are in communication via a sidelink interface, while the third node U2and a first node U3are in communication through the sidelink. It should be particularly noted that the sequence illustrated herein does not set a limit on the orders of signal transmissions and implementations in the present disclosure. As shown inFIG.6, steps marked by the dotted-line box FO are optional. The first node U3transmits third information in step S31; and receives a fourth information set in step S32, the fourth information set comprising seventh information; transmits a seventh radio signal in step S33; receives a third radio signal in step S34; and transmits a fifth radio signal in step S35; receives a first radio signal set in step S36, the first radio signal set comprising a twelfth radio signal. The second node U1receives an eighth radio signal in step S11; transmits a fourth radio signal in step S12; and transmits an eighth information set in step S13, the eighth information set comprising ninth information; receives a sixth radio signal in step S14; and transmits a second radio signal set in step S15, the second radio signal set comprising an eleventh radio signal. It should be noted that the step S12can be implemented before the step S13, or can be implemented after the step S13and before the step S14. The third node U2receives third information in step S21; transmits seventh information in step S22; and receives a seventh radio signal in step S23; transmits an eighth radio signal in step S24; receives a fourth radio signal in step S25; and transmits a third radio signal in step S26; receives ninth information in step S27; receives a fifth radio signal in step S28; and transmits a sixth radio signal in step S29; receives an eleventh radio signal in step S210; and transmits a twelfth radio signal in step S211. It should be noted that the step S27can be implemented before the step S25, or can be implemented after the step S25and before the step S210. In one embodiment, the third information is transmitted via a PC5 interface. In one embodiment, the third information is transmitted by broadcast. In one embodiment, the third information is transmitted through SL. In one embodiment, the third information is transmitted in a Physical Sidelink Discovery Channel (PSDCH). In one embodiment, the third information is transmitted in a PSSCH. In one embodiment, the third information is transmitted through a SL-SRB. In one embodiment, the third information is transmitted through a SL-SRB0. In one embodiment, the third information comprises PC5-Signaling (PC5-S) information. In one embodiment, the third information comprises a discovery message, the discovery message being used to discover a candidate relay node. In one embodiment, the discovery message comprises a first PC5 DISCOVERY message, and a type of the first PC5 DISCOVERY message is Discovery announcement. In one embodiment, the first PC5 DISCOVERY message can adopt a PC5 DISCOVERY message structure defined in Chapter 11.2.5 of 3GPP TS24.334. In one embodiment, the third information comprises a node ID of the second node. In one embodiment, a MAC PDU transmitting the third information comprises part of bits in a node ID of the first node; scheduling information of the MAC PDU transmitting the third information comprises the rest of the bits in the node ID of the first node. In one embodiment, a node ID of the second node is a link layer ID. In one embodiment, a node ID of the second node is a L2 ID. In one embodiment, a node ID of the second node is a source layer 2 ID. In one embodiment, the fourth information set comprises at least one piece of information. In one embodiment, the fourth information set is transmitted via a PC5 interface. In one embodiment, any piece of information in the fourth information set is transmitted by broadcast. In one embodiment, the fourth information set is transmitted through SL. In one embodiment, any piece of information in the fourth information set is transmitted in a PSDCH. In one embodiment, any piece of information in the fourth information set is transmitted in a PSSCH. In one embodiment, the fourth information set is transmitted through a SL-SRB. In one embodiment, the fourth information set is transmitted through a SL-SRB0. In one embodiment, the fourth information set comprises PC5-Signaling (PC5-S) information. In one embodiment, any piece of information in the fourth information set comprises second PC5_DISCOVERY message, and a type of the second PC5_DISCOVERY message is Discovery response. In one embodiment, the second PC5 DISCOVERY message can adopt a PC5_DISCOVERY message structure defined in Chapter 11.2.5 of 3GPP TS24.334. In one embodiment, any piece of information in the fourth information set comprises the node ID of the second node. In one embodiment, any piece of information in the fourth information set carries a node ID of a source transmitter that transmits the information. In one embodiment, a MAC PDU transmitting any piece of information in the fourth information set comprises part of bits in a node ID of a transmitter of the MAC PDU; scheduling information of the MAC PDU transmitting the any piece of information in the fourth information set comprises the rest of the bits in the node ID of the transmitter of the MAC PDU. In one embodiment, any piece of information in the fourth information set comprises a response to the third information. In one embodiment, the fourth information set comprises at least two pieces of information; among source transmitters that transmit the fourth information set, any two source transmitters are not co-located. In one embodiment, source transmitters that transmit the fourth information set are candidate relay nodes. In one embodiment, the fourth information set at least comprises P pieces of information. In one embodiment, the source transmitters that transmit the fourth information set at least comprise P relay nodes. In one embodiment, the first node determining P candidate node IDs according to the fourth information set received comprises: selecting P candidate nodes from the group of source transmitters that transmit the fourth information set in a descending order, according to a Reference Signal Received Power (RSRP) of a received radio signal set carrying the fourth information set, and then generating a first sequence; the P candidate nodes are respectively identified by the P candidate node IDs; the first sequence comprises the P candidate node IDs; a firstly selected candidate node is arranged in the first place among the first sequence; and a secondly selected candidate node is arranged in the second place among the first sequence, and so on, till a P-th candidate node is selected and arranged in a P-th place among the first sequence. In one embodiment, the P candidate node IDs are determined according to part of bits in a node ID of a transmitter of a MAC PDU comprised by the MAC PDU carrying a piece of information in the fourth information set and the remaining bits in the node ID of the transmitter of the MAC PDU comprised by scheduling information of the MAC PDU carrying the piece of information in the fourth information set having been received. In one embodiment, the P candidate node IDs respectively indicate P candidate relay nodes. In one embodiment, the P candidate node IDs comprise the Q node IDs; P being a positive integer no less than Q. In one embodiment, a source transmitter of the fifth information is the first node; the third node receives the seventh radio signal, recovers the fifth information and forwards the fifth information via the eighth radio signal; a target receiver of the fifth information is the second node. In one embodiment, a transmitter of the seventh radio signal and a target receiver of the eighth radio signal are not co-located. In one embodiment, the seventh radio signal and the eighth radio signal are respectively transmitted via radio interfaces. In one embodiment, the seventh radio signal and the eighth radio signal are respectively transmitted via PC5 interfaces. In one embodiment, the seventh radio signal and the eighth radio signal are respectively transmitted through SL. In one embodiment, the seventh radio signal and the eighth radio signal are respectively transmitted through Physical Sidelink Shared Channels (PSSCHs). In one embodiment, the seventh radio signal and the eighth radio signal are respectively transmitted through SRBs. In one embodiment, the seventh radio signal and the eighth radio signal are respectively transmitted by unicast. In one embodiment, time-frequency resources occupied by the seventh radio signal and time-frequency resources occupied by the eighth radio signal respectively belong to a V2X resource pool. In one embodiment, time-frequency resources occupied by the seventh radio signal and time-frequency resources occupied by the eighth radio signal are respectively reserved for sidelink transmissions. In one embodiment, the seventh radio signal and the eighth radio signal respectively comprise the fifth information. In one embodiment, the fifth information comprises RRC information. In one embodiment, the fifth information comprises PC5-RRC information. In one embodiment, the fifth information comprises all or part of Information Elements (IEs) in a piece of RRC information. In one embodiment, the fifth information comprises a CandidateRelayList IE in a piece of RRC information. In one embodiment, the fifth information comprises all or part of fields of an IE in a piece of RRC information. In one embodiment, the fifth information comprises RRCReconfigurationRequestSidelink. In one embodiment, the fifth information comprises PC5-Signaling (PC5-S) information. In one embodiment, the fifth information comprises the P candidate node IDs. In one embodiment, the fifth information comprises the first sequence. In one embodiment, the second node receives the eighth radio signal, recovers the fifth information from the eighth radio signal, and selects the Q node IDs out of the P candidate node IDs comprised by the fifth information. In one embodiment, a source transmitter of the first information is the second node; the third node receives the fourth radio signal, recovers the first information and forwards the first information via the third radio signal; a target receiver of the first information is the first node. In one embodiment, a transmitter of the fourth radio signal is the second node in the present disclosure. In one embodiment, the fourth radio signal is transmitted via a radio interface. In one embodiment, the fourth radio signal is transmitted via a PC5 interface. In one embodiment, the fourth radio signal is transmitted through SL. In one embodiment, the fourth radio signal is a PSSCH. In one embodiment, the fourth radio signal is transmitted through a SL-SRB. In one embodiment, the fourth radio signal is transmitted through a SL-SRB3. In one embodiment, time-frequency resources occupied by the fourth radio signal belong to a V2X resource pool. In one embodiment, time-frequency resources occupied by the fourth radio signal are reserved for sidelink transmission. In one embodiment, the fourth radio signal comprises the first information. In one embodiment, the second node randomly selects Q node IDs from the first sequence to generate the node ID group. In one embodiment, the second node selects the first Q node IDs from the first sequence to generate the node ID group. In one embodiment, a transmitter of the fourth radio signal and a target receiver of the third radio signal are not co-located. In one embodiment, a source transmitter of the second information is the first node; the third node receives the fifth radio signal, recovers the second information, and forwards the second information through the sixth radio signal; a target receiver of the second information is the second node. In one embodiment, a transmitter of the fifth radio signal and a target receiver of the sixth radio signal are not co-located. In one embodiment, the fifth radio signal and the sixth radio signal are respectively transmitted via radio interfaces. In one embodiment, the fifth radio signal and the sixth radio signal are respectively transmitted via PC5 interfaces. In one embodiment, the fifth radio signal and the sixth radio signal are respectively transmitted through SL. In one embodiment, the fifth radio signal and the sixth radio signal are respectively transmitted through PSSCHs. In one embodiment, the fifth radio signal and the sixth radio signal are respectively transmitted through SL-SRBs. In one embodiment, the fifth radio signal and the sixth radio signal are respectively transmitted through SL-SRB3 s. In one embodiment, time-frequency resources occupied by the fifth radio signal and time-frequency resources occupied by the sixth radio signal respectively belong to a V2X resource pool. In one embodiment, time-frequency resources occupied by the fifth radio signal and time-frequency resources occupied by the sixth radio signal are respectively reserved for sidelink transmissions. In one embodiment, the fifth radio signal and the sixth radio signal respectively comprise the second information. In one embodiment, the second information comprises RRC information. In one embodiment, the second information comprises PC5-RRC information. In one embodiment, the second information comprises all or part of IEs in a piece of RRC information. In one embodiment, the second information comprises all or part of fields of an IE in a piece of RRC information. In one embodiment, the second information comprises RRCReconfigurationcompleteSidelink. In one embodiment, the second information comprises a response to the first information. In one embodiment, a target receiver of the fifth radio signal is the transmitter of the third radio signal. In one embodiment, the second information comprises RRCReconfigurationcompleteSidelin; a MAC PDU comprising the RRCReconfigurationcompleteSidelink comprises a UE ID in a MAC PDU carried by the third radio signal; SCI for scheduling the RRCReconfigurationcompleteSidelink comprises a UE ID in SCI scheduling the third radio signal. In one embodiment, the second node transmits the eighth information set; target receivers that receive the eighth information set are Q nodes identified by the Q node IDs. In one embodiment, the eighth information set comprises the ninth information, and a receiver of the ninth information is the third node in the present disclosure. In one embodiment, the fourth radio signal comprises the ninth information, the ninth information being received by a higher layer of the third node. In one embodiment, each piece of information in the eighth information set is transmitted by unicast. In one embodiment, each piece of information in the eighth information set comprises RRC information. In one embodiment, each piece of information in the eighth information set comprises PC5-RRC information. In one embodiment, each piece of information in the eighth information set comprises all or part of IEs in a piece of RRC information. In one embodiment, each piece of information in the eighth information set comprises all or part of fields of an IE in a piece of RRC information. In one embodiment, each piece of information in the eighth information set comprises RRCReconfigurationSidelink. In one embodiment, any piece of information in the eighth information set comprises the second configuration. In one embodiment, the second configuration is a field of any piece of information in the eighth information set. In one embodiment, the second configuration is a SLRB-Config field of any piece of information in the eighth information set. In one embodiment, the second configuration is a slrb-ConfigToAddModList field of any piece of information in the eighth information set. In one embodiment, the second parameter set comprises at least a former of a MAC sublayer configuration parameter and an RLC sublayer configuration parameter. In one embodiment, the second parameter set comprises the first radio bearer ID. In one embodiment, the second parameter set is used for configuring RLC Bearers for the third node. In one embodiment, the RLC Bearers for the third node comprises a RLC bearer for the third node corresponding to transmission of the second node and a RLC bearer for the third node corresponding to transmission of the first node. In one embodiment, the RLC Bearers for the third node constitutes a peer-to-peer radio bearer indicated by the first radio bearer ID. In one embodiment, the second parameter set is used for configuring RLC bearers for Q nodes identified by the Q node IDs. In one embodiment, the second parameter set is used for configuring a higher-layer entity corresponding to the RLC bearers for the Q nodes identified by the Q node IDs. In one embodiment, the higher-layer entity corresponding to the RLC bearers for the Q nodes includes at least a former of a MAC entity and an RLC entity. In one embodiment, the second parameter set comprises a LCID corresponding to the RLC bearers for the Q nodes. In one embodiment, the LCID comprised by the second parameter set is the same as the LCID comprised by the first parameter set. In one embodiment, any one of the RLC bearers for the Q nodes can be used for transmitting traffics to which the first MAC SDU set belongs. In one embodiment, any one of the RLC bearers for the Q nodes can be used for transmitting PC5 QoS streams to which the first MAC SDU set belongs. In one embodiment, after transmitting the eighth information set the second node receives a tenth information set; the tenth information set is a response to the eighth information set; source transmitters of the tenth information set are Q nodes identified by the Q node IDs. In one embodiment, each piece of information in the tenth information set is transmitted by unicast. In one embodiment, each piece of information in the tenth information set comprises PC5-RRC information. In one embodiment, each piece of information in the tenth information set comprises RRCReconfigurationcompleteSidelink. In one embodiment, the second node transmits the second radio signal set. In one embodiment, the second radio signal set comprises at least one radio signal. In one embodiment, the second radio signal set comprises the eleventh radio signal. In one embodiment, the second radio signal set is transmitted via a radio interface. In one embodiment, the second radio signal set is transmitted via a PC5 interface. In one embodiment, the second radio signal set is transmitted through SL. In one embodiment, any radio signal in the second radio signal set occupies a PSSCH. In one embodiment, any radio signal in the second radio signal set occupies a physical channel. In one embodiment, any radio signal in the second radio signal set is transmitted through a DRB. In one embodiment, the second radio signal set comprises at least two radio signals; any two radio signals in the second radio signal set are transmitted in different sidelink slots. In one embodiment, the second radio signal set comprises at least two radio signals; any two radio signals in the second radio signal set carry different information bits. In one embodiment, the second radio signal set comprises at least two radio signals; any two radio signals in the second radio signal set carry different TBs. In one embodiment, the second radio signal set comprises at least two radio signals; any two radio signals in the second radio signal set are received by a same target receiver. In one embodiment, the second radio signal set comprises at least two radio signals; at least two radio signals in the second radio signal set are received by different target receivers. In one embodiment, time-frequency resources occupied by the second radio signal set belong to a V2X resource pool. In one embodiment, time-frequency resources occupied by the second radio signal set are reserved for sidelink transmission. In one embodiment, the fourth radio signal and any radio signal in the second radio signal set are transmitted in different sidelink slots. In one embodiment, the fourth radio signal is transmitted earlier than the second radio signal set. In one embodiment, a target receiver of the second radio signal set comprises a node identified by any node ID of the Q node IDs. In one embodiment, a number of radio signals comprised by the second radio signal set is no smaller than a number of radio signals comprised by the first radio signal set. In one embodiment, a target signaling comprises physical layer signalings respectively corresponding to each of the Q node IDs; the first receiver monitors the target signaling in a first time-frequency resource pool. In one embodiment, the target signaling is used for indicating time-frequency resources occupied by a target radio signal and a Modulation and Coding Scheme (MC S) employed by the target radio signal. In one embodiment, the target signaling is monitored in each slot in the first time-frequency resource pool. In one embodiment, the target signaling is monitored in some slots in the first time-frequency resource pool. In one embodiment, the target signaling is monitored in each slot on which wireless transmission is not performed in the first time-frequency resource pool. In one embodiment, the target signaling is monitored in each slot on which sidelink wireless transmission is not performed in the first time-frequency resource pool. In one embodiment, the target signaling is monitored in each slot on which wireless reception is performed in the first time-frequency resource pool. In one embodiment, the target signaling is monitored in each slot on which sidelink wireless reception is performed in the first time-frequency resource pool. In one embodiment, the phrase of monitoring a target signaling in the first time-frequency resource pool comprises performing energy detection for the target signaling in the first time-frequency resource pool. In one embodiment, the phrase of monitoring a target signaling in the first time-frequency resource pool comprises performing blind decoding for the target signaling in the first time-frequency resource pool. In one embodiment, the phrase of monitoring a target signaling in the first time-frequency resource pool comprises performing blind decoding for the target signaling and energy detection on the target radio signal in the first time-frequency resource pool. In one embodiment, the phrase of monitoring a target signaling in the first time-frequency resource pool comprises performing blind decoding for the target signaling and energy detection on a reference signal of the target radio signal in the first time-frequency resource pool. In one embodiment, the phrase of monitoring a target signaling in the first time-frequency resource pool comprises performing blind decoding for the target signaling, performing energy detection on a reference signal of the target radio signal and performing decoding on the target radio signal in the first time-frequency resource pool. In one embodiment, the phrase of monitoring a target signaling in the first time-frequency resource pool comprises performing Cyclic Redundancy Check (CRC) for the target signaling in the first time-frequency resource pool. In one embodiment, the first time-frequency resource pool is reserved for sidelink transmission. In one embodiment, the first time-frequency resource pool belongs to a V2X resource pool. In one embodiment, when the physical layer signaling corresponding to any of the Q node IDs is successfully decoded, the physical layer signaling is detected. In one embodiment, when the physical layer signaling corresponding to any of the Q node IDs passes CRC, the physical layer signaling is detected. In one embodiment, with Q2being greater than 1, any two physical layer signalings of the Q2physical layer signalings are detected in different sidelink slots. In one embodiment, with Q2being greater than 1, at least two physical layer signalings of the Q2physical layer signalings are detected in a same sidelink slot. In one embodiment, any of the Q2physical layer signalings comprises part of bits in a node ID of the Q node IDs. In one embodiment, transmitters that transmit the Q2physical layer signalings are identified by a node ID of the Q node IDs. In one embodiment, with Q2being greater than 1, transmitters that transmit at least two physical layer signalings of the Q2physical layer signalings are identified by two different node IDs of the Q node IDs. In one embodiment, the Q2physical layer signalings respectively comprise Q2pieces of SCI. In one embodiment, the first radio signal set comprises Q2radio signals, and the Q2physical layer signalings respectively comprise scheduling information of the Q2radio signals. In one embodiment, a source transmitter of the first MAC SDU set is the second node. In one embodiment, a target receiver of the first MAC SDU set is the first node. In one embodiment, a MAC subheader corresponding to any MAC SDU in the first MAC SDU set comprises an LCID; the LCID is used for indicating a higher layer entity that processes any MAC SDU in the first MAC SDU set. In one embodiment, any MAC SDU is distributed to a target RLC entity of the first node according to an LCID of any MAC SDU in the first MAC SDU set. In one embodiment, the first MAC SDU set comprises at least two MAC SDUs; any two MAC SDUs in the first MAC SDU set share a same LCID. In one embodiment, the phrase that the target RLC entity of the first node is unrelated to a node ID of a transmitter of the MAC SDU comprises: any MAC SDU in the first MAC SDU set is distributed to the target RLC entity of the first node. In one embodiment, the phrase that the target RLC entity of the first node is unrelated to a node ID of a transmitter of the MAC SDU comprises: the first MAC SDU set comprises at least two MAC SDUs, and transmitters that transmit the at least two MAC SDUs in the first MAC SDU set are identified by at least two node IDs of the Q node IDs. In one embodiment, the phrase that the target RLC entity of the first node is unrelated to a node ID of a transmitter of the MAC SDU comprises: each MAC SDU in the first MAC SDU set correspond to the same LCID; the LCID is associated with the target RLC entity of the first node. Embodiment 7 Embodiment 7 illustrates another flowchart of radio signal procedure according to one embodiment of the present disclosure, as shown inFIG.7. A second node U4and a third node U5are in communication via a sidelink interface, and the third node U5and a first node U6are in communication through the sidelink. It should be particularly noted that the sequence illustrated herein does not set a limit on the orders of signal transmissions and implementations in the present disclosure. The first node U6transmits a ninth radio signal in step S61. The second node U4receives a tenth radio signal in step S41. The third node U5receives a ninth radio signal in step S51; and transmits a tenth radio signal in step S52. In one embodiment, the first transmitter determines a first radio link failure; and, as a response to the first radio link failure, transmits a ninth radio signal. In one embodiment, the first radio link comprises a node identified by the first node ID, the first node ID belonging to the Q node IDs. In one embodiment, the first radio link comprises at least one of the RLC bearer for the third node corresponding to transmission of the second node or the RLC bearer for the third node corresponding to transmission of the first node. In one embodiment, the phrase that the target RLC entity of the first node is unrelated to a node ID of a transmitter of the MAC SDU comprises: the first radio link comprises a node identified by the first node ID, the first node ID belonging to the Q node IDs; the first radio link failure does not trigger the release of the target RLC entity. In one embodiment, the first node ID identifies a relay node. In one embodiment, a node identified by the first node ID and the third node in the present disclosure are not co-located. In one embodiment, when the target RLC entity of the first node indicates that a number of RLC retransmissions for the first node ID has reached a maximum value, the first radio link failure is determined. In one subembodiment, the maximum number of RLC retransmissions is pre-configured. In one subembodiment, the maximum number of RLC retransmissions is configured by networks. In one embodiment, when a timer T400of the first node is expired, the first radio link failure is determined. In one embodiment, when a timer T400of the first node for the first node ID is expired, the first radio link failure is determined. In one embodiment, when a MAC entity of the first node indicates that HARQ Discontinuous Transmissions (DTX) for the first node ID have reached a maximum value, the first radio link failure is determined. In one subembodiment, the maximum value of HARQ DTX is pre-configured. In one subembodiment, the maximum value of HARQ DTX is configured by networks. In one embodiment, when a PDCP entity corresponding to the Radio Bearer for the first node indicates that Integrity check of a SL-SRB2 or a SL-SRB3 is failed, the first radio link failure is determined. In one embodiment, a target receiver of the ninth radio signal is a node identified by any of the Q node IDs other than the first node ID. In one embodiment, the target receiver of the ninth radio signal is a node identified by a node ID which ranks only second to the first node ID among the first sequence. In one embodiment, a transmitter of the ninth radio signal and a target receiver of the tenth radio signal are not co-located. In one embodiment, the ninth radio signal and the tenth radio signal are respectively transmitted via air interfaces. In one embodiment, the ninth radio signal and the tenth radio signal are respectively transmitted via radio interfaces. In one embodiment, the ninth radio signal and the tenth radio signal are respectively transmitted via PC5 interfaces. In one embodiment, the ninth radio signal and the tenth radio signal are respectively transmitted through SL. In one embodiment, the ninth radio signal and the tenth radio signal are respectively PSSCHs. In one embodiment, the ninth radio signal and the tenth radio signal are respectively transmitted through SL-SRBs. In one embodiment, the ninth radio signal and the tenth radio signal are respectively transmitted through SL-SRB3 s. In one embodiment, time-frequency resources occupied by the ninth radio signal and time-frequency resources occupied by the tenth radio signal respectively belong to a V2X resource pool. In one embodiment, time-frequency resources occupied by the ninth radio signal and time-frequency resources occupied by the tenth radio signal are respectively reserved for sidelink transmissions. In one embodiment, the ninth radio signal and the tenth radio signal respectively comprise sixth information. In one embodiment, the third node in the present disclosure receives the ninth radio signal, recovers the sixth information and forwards the sixth information through the tenth radio signal. In one embodiment, a source transmitter of the sixth information is the first node. In one embodiment, a target receiver of the sixth information is the second node. In one embodiment, the second node receives the sixth information, the sixth information indicating the first radio link failure. In one embodiment, the sixth information comprises the first node ID. In one embodiment, the sixth information comprises an updated candidate node ID, the updated candidate node ID not comprising the first node ID. In one embodiment, the sixth information comprises PC5-RRC information. In one embodiment, the sixth information comprises all or part of IEs in a piece of RRC information. In one embodiment, the sixth information comprises all or part of fields of an IE in a piece of RRC information. In one embodiment, the sixth information comprises RRCReconfigurationSidelink. In one embodiment, the sixth information comprises a FailureRelayList IE in a piece of RRC information. In one embodiment, the sixth information comprises a UpdateRelayList IE in a piece of RRC information. In one embodiment, the second receiver receives the sixth information; as a response to receiving the sixth information, the second transmitter transmits eleventh information; the eleventh information is forwarded via the third node to the first node; a target receiver of the eleventh information is the first node. In one embodiment, the eleventh information comprises RRC information. In one embodiment, the eleventh information comprises PC5-RRC information. In one embodiment, the eleventh information comprises all or part of IEs in a piece of RRC information. In one embodiment, the eleventh information comprises all or part of fields of an IE in a piece of RRC information. In one embodiment, the eleventh information comprises RRCReconfigurationcompleteSidelink. In one embodiment, the eleventh information comprises RRCReconfigurationcompleteSidelink; a MAC PDU comprising the RRCReconfigurationcompleteSidelink comprises a UE ID in a MAC PDU carried by the tenth radio signal; SCI for scheduling the RRCReconfigurationcompleteSidelink comprises a UE ID in SCI scheduling the tenth radio signal. In one embodiment, upon reception of the sixth information by the second node, a target receiver of the second radio signal set does not comprise a node identified by the first node ID. In one embodiment, after receiving the sixth information, the second node transmits twelfth information, a target receiver of the twelfth information being a node identified by the first node ID; the twelfth information indicates the release of RLC bearers for the node identified by the first node ID. In one embodiment, after transmitting the sixth information, the first node transmits thirteenth information, a target receiver of the thirteenth information being a node identified by the first node ID; the thirteenth information indicates the release of RLC bearers for the node identified by the first node ID. Embodiment 8 Embodiment 8 illustrates a schematic diagram of a source transmitter, a transmitter, a receiver and a target receiver according to one embodiment of the present disclosure, as shown inFIG.8. In one embodiment, a source transmitter that transmits the first MAC SDU set refers to: generating the first MAC SDU set based on an RLC SDU set on an RLC sublayer to be transmitted on an air interface. In one embodiment, a source transmitter that transmits the first MAC SDU set refers to: generating the first MAC SDU set based on a PDCP SDU set on a PDCP sublayer to be transmitted on an air interface. In one embodiment, a target receiver that receives the first MAC SDU set refers to: receiving the first MAC SDU set through an air interface, and not forwarding the first MAC SDU set through an air interface. In one embodiment, a target receiver that receives the first MAC SDU set refers to: receiving the first MAC SDU set through an air interface, and delivering data carried in the first MAC SDU set to an RLC sublayer. In one embodiment, a target receiver that receives the first MAC SDU set refers to: receiving the first MAC SDU set through an air interface, and delivering data carried in the first MAC SDU set to a PDCP sublayer. In one embodiment, a source transmitter of the first information refers to: generating the first information on an RRC layer to be transmitted by an air interface. In one embodiment, a source transmitter of the first information refers to: generating first information on an RRC layer based on data received from NAS, which is to be transmitted by an air interface. In one embodiment, a target receiver of the first information refers to: receiving the first information through an air interface, and not forwarding the first information through an air interface. In one embodiment, a target receiver of the first information refers to: receiving the first information through an air interface, and delivering data carried in the first information to RRC. In one embodiment, a target receiver of the first information refers to: receiving the first information through an air interface, and delivering data carried in the first information to NAS. As illustrated in Case A inFIG.8, the first information is generated by the second node, the second node being a source transmitter of the first information; the first information is cancelled by the first node, the first node being a target receiver of the first information; transmission of the first information from the second node to the first node is relayed by the third node as a relay node, respectively dividing into a first hop transmission and a second hop transmission; during the first hop transmission, the third node serves as a receiver of the first information; during the second hop transmission, the third node serves as a transmitter of the first information. In one embodiment, take the first information as an example in Case A inFIG.8, for transmissions of the second information, the fifth information, the sixth information and the eleventh information in the present disclosure, the descriptions about the source transmitter, transmitter, receiver and target receiver of information above are also applicable, hence no further details given here. As illustrated in Case B inFIG.8, the fourth radio signal is generated by the second node, the second node being a transmitter of the fourth radio signal; the fourth radio signal is cancelled by the third node, the third node being a target receiver of the third radio signal. In one embodiment, take the fourth radio signal as an example in Case B inFIG.8, for the first radio signal, the second radio signal set, the third radio signal, the fourth radio signal, the fifth radio signal, the sixth radio signal, the seventh radio signal, the eighth radio signal, the ninth radio signal, the tenth radio signal, the eleventh radio signal and the twelfth radio signal in the present disclosure, descriptions about above transmitters and target receivers of radio signals are also applicable, hence no further details given here. Embodiment 9 Embodiment 9 illustrates a format diagram of a first MAC SDU and a first MAC PDU according to one embodiment of the present disclosure, as shown inFIG.9. In one embodiment, the eleventh radio signal comprises a first MAC PDU, as shown inFIG.9, the first MAC PDU comprises a SL-SCH subheader and a first MAC subPDU, the first MAC subPDU comprising a MAC subheader and the first MAC SDU; a V field comprised by a SL-SCH subheader is used for indicating a version number; an R field comprised by the SL-SCH subheader is a reserved field; a SRC field comprised by the SL-SCH subheader comprises higher 16 bits in a node ID of a transmitter of the eleventh radio signal; a DST field comprised by the SL-SCH subheader comprises higher 8 bits in a node ID of a target receiver of the eleventh radio signal; an R field comprised by the MAC subheader is a reserved field; an F field comprised by the MAC subheader indicates a length contained by an L field comprised by the MAC subheader; an L field comprised by the MAC subheader indicates a number of bytes comprised by the first MAC SDU. In one embodiment, the MAC subheader comprises an LCD, the LCID being used to indicate a RLC Bearer to which the first MAC SDU belongs. In one embodiment, the first MAC SDU is distributed to an RLC entity of the third node according to the LCID of the first MAC SDU. In one embodiment, the first MAC SDU is distributed to the target RLC entity of the first node according to the LCID of the first MAC SDU. In one embodiment, the first MAC SDU is used by the third node for generating the twelfth radio signal. In one embodiment, the first MAC subPDU is used by the third node for generating the twelfth radio signal. In one embodiment, the RLC entity of the third node buffers the first MAC SDU. In one embodiment, the RLC entity of the third node buffers the first MAC subPDU. In one embodiment, the LCIDs of the first MAC SDUs respectively comprised by the eleventh radio signal and the twelfth radio signal are the same. In one embodiment, any MAC PDU corresponding to any MAC SDU in the first MAC SDU set comprises at least part of bits in the node ID of a transmitter of the said MAC PDU. In one embodiment, any MAC PDU corresponding to any MAC SDU in the first MAC SDU set comprises at least part of bits in the node ID of a receiver of the said MAC PDU. Embodiment 10 Embodiment 10 illustrates a schematic diagram of a radio protocol architecture of user planes of a first node, a second node and a third node according to one embodiment of the present disclosure, as shown inFIG.10. In one embodiment, a PHY layer1001and a PHY layer1003comprised by the third node, a PHY layer1051comprised by the second node and a PHY layer1091comprised by the first node comprise the PHY351in the user plane350inFIG.3of the present disclosure. In one embodiment, a L21052comprised by the second node and a L2 layer1092comprised by the first node respectively comprise the MAC sublayer352, the RLC sublayer353, the PDCP sublayer354and the SDAP sublayer356in the L2355. In one embodiment, a L21002comprised by the third node comprises a MAC sublayer352in the L2355comprised in the user plane inFIG.3of the present disclosure. In one embodiment, the L21002comprised by the third node comprises an RLC sublayer353in the L2355comprised in the user plane inFIG.3of the present disclosure; the RLC sublayer in the L21002comprised by the third node performs ARQ retransmission, duplicate packet checking and protocol error detection to the RLC sublayer in the L21052comprised by the second node; the RLC sublayer in the L21002comprised by the third node drops performing packet segmentation and reassembling on the RLC sublayer in the L21052comprised by the second node. In one embodiment, a L21004comprised by the third node comprises a MAC sublayer352in the L2355comprised in the user plane inFIG.3of the present disclosure. In one embodiment, the L21004comprised by the third node comprises an RLC sublayer353in the L2355comprised in the user plane inFIG.3of the present disclosure; the RLC sublayer in the L21004comprised by the third node performs ARQ retransmission, duplicate packet checking and protocol error detection to the RLC sublayer in the L21092comprised by the first node; the RLC sublayer in the L21004comprised by the third node drops performing packet segmentation and reassembling on the RLC sublayer in the L21092comprised by the first node. In one embodiment, the third node comprises an adaptation sublayer905; the adaptation sublayer in charge of relay-related control plane functionality. In one embodiment, the adaptation sublayer1005is located below or above any protocol sublayer in the L21002and the L21004comprised by the third node. In one embodiment, the adaptation sublayer1005is located above an RLC sublayer in the L21002and an RLC sublayer in the L21004comprised by the first node. In one embodiment, the third node and the second node being connected via a PC5 interface, the PHY1001comprised by the third node correspond to the PHY layer1051comprised by the second node. In one embodiment, the third node and the first node being connected via a PC5 interface, the PHY1003comprised by the third node correspond to the PHY layer1091comprised by the first node. In one embodiment, the first MAC SDU set is generated by the L21052comprised by the second node. In one embodiment, the first MAC SDU set is received by the L21092comprised by the first node. In one embodiment, the first MAC SDU is buffered in the L21002comprised by the third node. In one embodiment, the first MAC SDU is buffered in the L21004comprised by the third node. In one embodiment, the third node buffers the first MAC SDU received in the L21002; when the third node transmits a control message to the second node to indicate successful reception of the first MAC SDU, the first MAC SDU is delivered by the L21002to the L21004. In one embodiment, the third node buffers the first MAC SDU received in the L21002; when scheduling the first MAC SDU to be transmitted to the first node, the first MAC SDU is delivered by the L21002to the L21004. In one embodiment, the second parameter set comprises configuration parameters for the L21002and the L21004. Embodiment 11 Embodiment 11 illustrates a structure block diagram of a processing device in a first node according to one embodiment of the present disclosure, as shown inFIG.11. InFIG.11, a first node's processing device1100comprises a first receiver1101and a first transmitter1102. The first receiver1101comprises at least one of the transmitter/receiver454(comprising the antenna452), the receiving processor456, the multi-antenna receiving processor458or the controller/processor459inFIG.4of the present disclosure; the first transmitter1102comprises at least one of the transmitter/receiver454(comprising the antenna452), the transmitting processor468, the multi-antenna transmitting processor457or the controller/processor459inFIG.4of the present disclosure. In Embodiment 11, the first receiver1101receives a third radio signal and a first radio signal set in step101, the third radio signal comprising first information; herein, the first information comprises a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; one of the Q node IDs is used for identifying a transmitter of the third radio signal; the first parameter set is used for configuring a Radio Bearer for the first node; a transmitter of the first radio signal set is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs, Q1being a positive integer greater than 1 and no greater than the Q; the first radio signal set comprises a first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set. In one embodiment, the first transmitter1102transmits a fifth radio signal as a response to the first information, the fifth radio signal comprising second information; herein, a target receiver of the fifth radio signal is a transmitter of the third radio signal. In one embodiment, the first receiver1101monitors a corresponding physical layer signaling for each node ID of the Q node IDs in a first time-frequency resource pool; herein, Q2physical layer signaling(s) is(are) detected, the first radio signal set comprises Q2radio signal(s), and the Q2physical layer signaling(s) comprises (respectively comprise) scheduling information of the Q2radio signal(s), Q2being a positive integer. In one embodiment, the first transmitter1102transmits third information, the third information comprising a discovery message; the first receiver1101receives a fourth information set, and determines P candidate node IDs according to the fourth information set; the first transmitter1102transmits a seventh radio signal, the seventh radio signal comprising fifth information, the fifth information comprising the P candidate node IDs; herein, any piece of information in the fourth information set comprises a response to the third information; the P candidate node IDs comprise the Q node IDs; P is a positive integer no less than Q. In one embodiment, the first transmitter1102determines a first radio link failure; and as a response to the first radio link failure, transmits a ninth radio signal, the ninth radio signal comprising sixth information, the sixth information indicating the first radio link failure; herein, the Q node IDs comprise a first node ID; the first radio link comprises a node identified by the first node ID; a target receiver of the ninth radio signal comprises a node identified by one of the Q node IDs other than the first node ID. In one embodiment, the first receiver1101, for any MAC SDU comprised by the first MAC SDU set, distributes the MAC SDU to a target RLC entity of the first node according to a LCD of the MAC SDU; herein, the target RLC entity of the first node is unrelated to a node ID of a transmitter of the MAC SDU. Embodiment 12 Embodiment 12 illustrates a structure block diagram of a processing device in a second node according to one embodiment of the present disclosure, as shown inFIG.12. InFIG.12, a second node's processing device1200comprises a second receiver1201and a second transmitter1202. The second receiver1201comprises at least one of the transmitter/receiver554(comprising the antenna552), the receiving processor556, the multi-antenna receiving processor558or the controller/processor559inFIG.5of the present disclosure; the second transmitter1202comprises at least one of the transmitter/receiver554(comprising the antenna552), the transmitting processor568, the multi-antenna transmitting processor557or the controller/processor559inFIG.5of the present disclosure. In Embodiment 12, the second transmitter1202transmits a fourth radio signal and a second radio signal set, the fourth radio signal comprising first information; herein, the first information comprises a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; one of the Q node IDs is used for identifying a target receiver of the fourth radio signal; the second radio signal set comprises a first MAC SDU set, the first MAC SDU set being used to generate a first radio signal set; the first parameter set is used for configuring a Radio Bearer for a target receiver of the first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set; a transmitter of the first radio signal set is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs, Q1being a positive integer greater than 1 and no greater than the Q In one embodiment, the second receiver1201receives a sixth radio signal, the sixth radio signal comprising second information; herein, the second information comprises a response to the first information; a transmitter of the sixth radio signal is a target receiver of the fourth radio signal. In one embodiment, a corresponding physical layer signaling for each node ID of the Q node IDs is monitored in a first time-frequency resource pool; herein, Q2physical layer signaling(s) is(are) detected, the first radio signal set comprises Q2radio signal(s), and the Q2physical layer signaling(s) comprises (respectively comprise) scheduling information of the Q2radio signal(s), Q2being a positive integer. In one embodiment, the second receiver1201receives an eighth radio signal, the eighth radio signal comprising fifth information, the fifth information comprising P candidate node IDs; herein, the P candidate node IDs comprise the Q node IDs; P is a positive integer no less than Q. In one embodiment, the second receiver1201receives a tenth radio signal, the tenth radio signal comprising sixth information; herein, the sixth information indicates a first radio link failure; the Q node IDs comprise a first node ID; the first radio link comprises a node identified by the first node ID; a transmitter of the tenth radio signal comprises a node identified by one of the Q node IDs other than the first node ID. In one embodiment, any MAC SDU comprised by the first MAC SDU set is from an RLC entity of the second node, any two said MAC SDUs share a same LCID; herein, the RLC entity of the second node is unrelated to a node ID of a receiver of the MAC SDU. In one embodiment, the second transmitter1202transmits an eighth information set, the eighth information set comprising a second configuration, the second configuration comprising a second parameter set; herein, the second parameter set is used for configuring RLC Bearers for Q nodes identified by the Q node IDs. Embodiment 13 Embodiment 13 illustrates a structure block diagram of a processing device in a third node according to one embodiment of the present disclosure, as shown inFIG.13. InFIG.13, a third node's processing device1300comprises a third receiver1301and a third transmitter1302. The third receiver1301comprises at least one of the transmitter/receiver418(comprising the antenna420), the receiving processor470, the multi-antenna receiving processor472or the controller/processor475inFIG.4of the present disclosure; the third transmitter1302comprises at least one of the transmitter/receiver418(comprising the antenna420), the transmitting processor416, the multi-antenna transmitting processor471or the controller/processor475inFIG.4of the present disclosure. In Embodiment 13, the third receiver1301receives a fourth radio signal and an eleventh radio signal, the eleventh radio signal belonging to a second radio signal set; the third transmitter1302transmits a third radio signal and a twelfth radio signal, the twelfth radio signal belonging to a first radio signal set; herein, the third radio signal and the fourth radio signal respectively comprise first information, the first information comprising a node ID group and a first configuration; the node ID group comprises Q node IDs, Q being a positive integer greater than 1; the first configuration comprises a first parameter set; the first parameter set is used for configuring a Radio Bearer for a target receiver of the twelfth radio signal; the third node is identified by one of the Q node IDs, or transmitters of Q1radio signals in the first radio signal set are respectively identified by Q1node IDs of the Q node IDs and the third node is identified by one of the Q1node IDs, Q1being a positive integer greater than 1 and no greater than the Q; the first radio signal set and the second radio signal set respectively comprise a first MAC SDU set, and the first parameter set is applicable to the first MAC SDU set. In one embodiment, the third receiver1301receives a fifth radio signal; the third transmitter1302transmits a sixth radio signal; herein, the fifth radio signal and the sixth radio signal respectively comprise second information; the second information comprises a response to the first information. In one embodiment, a corresponding physical layer signaling for each node ID of the Q node IDs is monitored in a first time-frequency resource pool; herein, Q2physical layer signaling(s) is(are) detected, the first radio signal set comprises Q2radio signal(s), and the Q2physical layer signaling(s) comprises (respectively comprise) scheduling information of the Q2radio signal(s), Q2being a positive integer. In one embodiment, the third receiver1301receives third information and a seventh radio signal, the third information comprising a discovery message; transmits seventh information and an eighth radio signal, the seventh information belonging to a fourth information set; herein, the fourth information set is used for determining P candidate node IDs; the seventh information comprises a response to the third information; the seventh radio signal and the eighth radio signal respectively comprise fifth information, the fifth information comprising the P candidate node IDs; the P candidate node IDs comprise the Q node IDs; P is a positive integer no less than Q. In one embodiment, the third receiver1301receives a ninth radio signal; and the third transmitter1302transmits a tenth radio signal; herein, the ninth radio signal and the tenth radio signal respectively comprise sixth information, the sixth information indicating a first radio link failure; the Q node IDs comprise a first node ID; the first radio link comprises a node identified by the first node ID; the third node is a node identified by one of the Q node IDs other than the first node ID. In one embodiment, for a first MAC SDU comprised by the eleventh radio signal, the first MAC SDU is distributed to an RLC entity of the third node according to an LCD of the first MAC SDU; the first MAC SDU is used for generating the twelfth radio signal; herein, the RLC entity of the third node buffers the first MAC SDU; the first MAC SDU belongs to the first MAC SDU set. In one embodiment, the third receiver1301receives ninth information, the ninth information belonging to an eighth information set; the ninth information comprising a second configuration, the second configuration comprising a second parameter set; herein, the second parameter set is used for configuring a RLC Bearers for the third node. The ordinary skill in the art may understand that all or part of steps in the above method may be implemented by instructing related hardware through a program. The program may be stored in a computer readable storage medium, for example Read-Only-Memory (ROM), hard disk or compact disc, etc. Optionally, all or part of steps in the above embodiments also may be implemented by one or more integrated circuits. Correspondingly, each module unit in the above embodiment may be implemented in the form of hardware, or in the form of software function modules. The present disclosure is not limited to any combination of hardware and software in specific forms. The first-type communication node or UE or terminal in the present disclosure includes but is not limited to mobile phones, tablet computers, notebooks, network cards, low-consumption equipment, enhanced MTC (eMTC) terminals, NB-IOT terminals, vehicle-mounted communication equipment, aircrafts, diminutive airplanes, unmanned aerial vehicles, telecontrolled aircrafts, etc. The second-type communication node or base station or system device in the present disclosure includes but is not limited to macro-cellular base stations, micro-cellular base stations, home base stations, relay base station, eNB, gNB, Transmitter Receiver Point (TRP), relay satellite, satellite base station, airborne base station and other radio communication equipment. The above are merely the preferred embodiments of the present disclosure and are not intended to limit the scope of protection of the present disclosure. Any modification, equivalent substitute and improvement made within the spirit and principle of the present disclosure are intended to be included within the scope of protection of the present disclosure. | 117,980 |
11943746 | DESCRIPTION OF EXEMPLARY EMBODIMENTS In the present disclosure, “A or B” may mean “only A”, “only B” or “both A and B.” In other words, in the present disclosure, “A or B” may be interpreted as “A and/or B”. For example, in the present disclosure, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”. A slash (/) or comma used in the present disclosure may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”. In the present disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present disclosure, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”. In addition, in the present disclosure, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”. In addition, a parenthesis used in the present disclosure may mean “for example”. Specifically, when indicated as “control information (PDCCH)”, it may mean that “PDCCH” is proposed as an example of the “control information”. In other words, the “control information” of the present disclosure is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., PDCCH)”, it may also mean that “PDCCH” is proposed as an example of the “control information”. A technical feature described individually in one figure in the present disclosure may be individually implemented, or may be simultaneously implemented. The technology described below may be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and so on. The CDMA may be implemented with a radio technology, such as universal terrestrial radio access (UTRA) or CDMA-2000. The TDMA may be implemented with a radio technology, such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE). The OFDMA may be implemented with a radio technology, such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), and so on. IEEE 802.16m is an evolved version of IEEE 802.16e and provides backward compatibility with a system based on the IEEE 802.16e. The UTRA is part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is part of an evolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA in a downlink and uses the SC-FDMA in an uplink. LTE-advanced (LTE-A) is an evolution of the LTE. 5G NR is a successive technology of LTE-A corresponding to a new Clean-slate type mobile communication system having the characteristics of high performance, low latency, high availability, and so on. 5G NR may use resources of all spectrum available for usage including low frequency bands of less than 1 GHz, middle frequency bands ranging from 1 GHz to 10 GHz, high frequency (millimeter waves) of 24 GHz or more, and so on. For clarity in the description, the following description will mostly focus on LTE-A or 5G NR. However, technical features according to an embodiment of the present disclosure will not be limited only to this. FIG.2shows a structure of an NR system, based on an embodiment of the present disclosure. The embodiment ofFIG.2may be combined with various embodiments of the present disclosure. Referring toFIG.2, a next generation-radio access network (NG-RAN) may include a BS20providing a UE10with a user plane and control plane protocol termination. For example, the BS20may include a next generation-Node B (gNB) and/or an evolved-NodeB (eNB). For example, the UE10may be fixed or mobile and may be referred to as other terms, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), wireless device, and so on. For example, the BS may be referred to as a fixed station which communicates with the UE10and may be referred to as other terms, such as a base transceiver system (BTS), an access point (AP), and so on. The embodiment ofFIG.2exemplifies a case where only the gNB is included. The BSs20may be connected to one another via Xn interface. The BS20may be connected to one another via 5th generation (5G) core network (5GC) and NG interface. More specifically, the BSs20may be connected to an access and mobility management function (AMF)30via NG-C interface, and may be connected to a user plane function (UPF)30via NG-U interface. FIG.3shows a functional division between an NG-RAN and a 5GC, based on an embodiment of the present disclosure. The embodiment ofFIG.3may be combined with various embodiments of the present disclosure. Referring toFIG.3, the gNB may provide functions, such as Inter Cell Radio Resource Management (RRM), Radio Bearer (RB) control, Connection Mobility Control, Radio Admission Control, Measurement Configuration & Provision, Dynamic Resource Allocation, and so on. An AMF may provide functions, such as Non Access Stratum (NAS) security, idle state mobility processing, and so on. A UPF may provide functions, such as Mobility Anchoring, Protocol Data Unit (PDU) processing, and so on. A Session Management Function (SMF) may provide functions, such as user equipment (UE) Internet Protocol (IP) address allocation, PDU session control, and so on. Layers of a radio interface protocol between the UE and the network can be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system. Among them, a physical (PHY) layer belonging to the first layer provides an information transfer service by using a physical channel, and a radio resource control (RRC) layer belonging to the third layer serves to control a radio resource between the UE and the network. For this, the RRC layer exchanges an RRC message between the UE and the BS. FIG.4shows a radio protocol architecture, based on an embodiment of the present disclosure. The embodiment ofFIG.4may be combined with various embodiments of the present disclosure. Specifically,FIG.4(a)shows a radio protocol architecture for a user plane, andFIG.4(b)shows a radio protocol architecture for a control plane. The user plane corresponds to a protocol stack for user data transmission, and the control plane corresponds to a protocol stack for control signal transmission. Referring toFIG.4, a physical layer provides an upper layer with an information transfer service through a physical channel. The physical layer is connected to a medium access control (MAC) layer which is an upper layer of the physical layer through a transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. The transport channel is classified according to how and with what characteristics data is transmitted through a radio interface. Between different physical layers, i.e., a physical layer of a transmitter and a physical layer of a receiver, data are transferred through the physical channel. The physical channel is modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and utilizes time and frequency as a radio resource. The MAC layer provides services to a radio link control (RLC) layer, which is a higher layer of the MAC layer, via a logical channel. The MAC layer provides a function of mapping multiple logical channels to multiple transport channels. The MAC layer also provides a function of logical channel multiplexing by mapping multiple logical channels to a single transport channel. The MAC layer provides data transfer services over logical channels. The RLC layer performs concatenation, segmentation, and reassembly of Radio Link Control Service Data Unit (RLC SDU). In order to ensure diverse quality of service (QoS) required by a radio bearer (RB), the RLC layer provides three types of operation modes, i.e., a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). An AM RLC provides error correction through an automatic repeat request (ARQ). A radio resource control (RRC) layer is defined only in the control plane. The RRC layer serves to control the logical channel, the transport channel, and the physical channel in association with configuration, reconfiguration and release of RBs. The RB is a logical path provided by the first layer (i.e., the physical layer or the PHY layer) and the second layer (i.e., the MAC layer, the RLC layer, and the packet data convergence protocol (PDCP) layer) for data delivery between the UE and the network. Functions of a packet data convergence protocol (PDCP) layer in the user plane include user data delivery, header compression, and ciphering. Functions of a PDCP layer in the control plane include control-plane data delivery and ciphering/integrity protection. A service data adaptation protocol (SDAP) layer is defined only in a user plane. The SDAP layer performs mapping between a Quality of Service (QoS) flow and a data radio bearer (DRB) and QoS flow ID (QFI) marking in both DL and UL packets. The configuration of the RB implies a process for specifying a radio protocol layer and channel properties to provide a particular service and for determining respective detailed parameters and operations. The RB can be classified into two types, i.e., a signaling RB (SRB) and a data RB (DRB). The SRB is used as a path for transmitting an RRC message in the control plane. The DRB is used as a path for transmitting user data in the user plane. When an RRC connection is established between an RRC layer of the UE and an RRC layer of the E-UTRAN, the UE is in an RRC_CONNECTED state, and, otherwise, the UE may be in an RRC_IDLE state. In case of the NR, an RRC_INACTIVE state is additionally defined, and a UE being in the RRC_INACTIVE state may maintain its connection with a core network whereas its connection with the BS is released. Data is transmitted from the network to the UE through a downlink transport channel. Examples of the downlink transport channel include a broadcast channel (BCH) for transmitting system information and a downlink-shared channel (SCH) for transmitting user traffic or control messages. Traffic of downlink multicast or broadcast services or the control messages can be transmitted on the downlink-SCH or an additional downlink multicast channel (MCH). Data is transmitted from the UE to the network through an uplink transport channel. Examples of the uplink transport channel include a random access channel (RACH) for transmitting an initial control message and an uplink SCH for transmitting user traffic or control messages. Examples of logical channels belonging to a higher channel of the transport channel and mapped onto the transport channels include a broadcast channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), a multicast traffic channel (MTCH), etc. The physical channel includes several OFDM symbols in a time domain and several sub-carriers in a frequency domain. One sub-frame includes a plurality of OFDM symbols in the time domain. A resource block is a unit of resource allocation, and consists of a plurality of OFDM symbols and a plurality of sub-carriers. Further, each subframe may use specific sub-carriers of specific OFDM symbols (e.g., a first OFDM symbol) of a corresponding subframe for a physical downlink control channel (PDCCH), i.e., an L1/L2 control channel. A transmission time interval (TTI) is a unit time of subframe transmission. FIG.5shows a structure of an NR system, based on an embodiment of the present disclosure. The embodiment ofFIG.5may be combined with various embodiments of the present disclosure. Referring toFIG.5, in the NR, a radio frame may be used for performing uplink and downlink transmission. A radio frame has a length of 10 ms and may be defined to be configured of two half-frames (HFs). A half-frame may include five 1 ms subframes (SFs). A subframe (SF) may be divided into one or more slots, and the number of slots within a subframe may be determined based on subcarrier spacing (SCS). Each slot may include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP). In case of using a normal CP, each slot may include 14 symbols. In case of using an extended CP, each slot may include 12 symbols. Herein, a symbol may include an OFDM symbol (or CP-OFDM symbol) and a Single Carrier-FDMA (SC-FDMA) symbol (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol). Table 1 shown below represents an example of a number of symbols per slot (Nslotsymb), a number slots per frame (Nframe,uslot), and a number of slots per subframe (Nsubframe,uslot) based on an SCS configuration (u), in a case where a normal CP is used. TABLE 1SCS (15*2u)NsvmbslotNslotframe,uNslotsubframe,u15 KHz (u = 0)1410130 KHz (u = 1)1420260 KHz (u = 2)14404120 KHz (u = 3)14808240 KHz (u = 4)1416016 Table 2 shows an example of a number of symbols per slot, a number of slots per frame, and a number of slots per subframe based on the SCS, in a case where an extended CP is used. TABLE 2SCS (15*2u)NsvmbslotNslotframe,uNslotsubframe,u60 KHz (u = 2)12404 In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, and so on) between multiple cells being integrate to one UE may be differently configured. Accordingly, a (absolute time) duration (or section) of a time resource (e.g., subframe, slot or TTI) (collectively referred to as a time unit (TU) for simplicity) being configured of the same number of symbols may be differently configured in the integrated cells. In the NR, multiple numerologies or SCSs for supporting diverse 5G services may be supported. For example, in case an SCS is 15 kHz, a wide area of the conventional cellular bands may be supported, and, in case an SCS is 30 kHz/60 kHz a dense-urban, lower latency, wider carrier bandwidth may be supported. In case the SCS is 60 kHz or higher, a bandwidth that is greater than 24.25 GHz may be used in order to overcome phase noise. An NR frequency band may be defined as two different types of frequency ranges. The two different types of frequency ranges may be FR1 and FR2. The values of the frequency ranges may be changed (or varied), and, for example, the two different types of frequency ranges may be as shown below in Table 3. Among the frequency ranges that are used in an NR system, FR1 may mean a “sub 6 GHz range”, and FR2 may mean an “above 6 GHz range” and may also be referred to as a millimeter wave (mmW). TABLE 3Frequency RangeCorrespondingSubcarrierdesignationfrequency rangeSpacing (SCS)FR1450 MHz-6000 MHz15, 30, 60 kHzFR224250 MHz-52600 MHz60, 120, 240 kHz As described above, the values of the frequency ranges in the NR system may be changed (or varied). For example, as shown below in Table 4, FR1 may include a band within a range of 410 MHz to 7125 MHz. More specifically, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher being included in FR1 mat include an unlicensed band. The unlicensed band may be used for diverse purposes, e.g., the unlicensed band for vehicle-specific communication (e.g., automated driving). TABLE 4Frequency RangeCorrespondingSubcarrierdesignationfrequency rangeSpacing (SCS)FR1410 MHz-7125 MHz15, 30, 60 kHzFR224250 MHz-52600 MHz60, 120, 240 kHz FIG.6shows a structure of a slot of an NR frame, based on an embodiment of the present disclosure. The embodiment ofFIG.6may be combined with various embodiments of the present disclosure. Referring toFIG.6, a slot includes a plurality of symbols in a time domain. For example, in case of a normal CP, one slot may include 14 symbols. However, in case of an extended CP, one slot may include 12 symbols. Alternatively, in case of a normal CP, one slot may include 7 symbols. However, in case of an extended CP, one slot may include 6 symbols. A carrier includes a plurality of subcarriers in a frequency domain. A Resource Block (RB) may be defined as a plurality of consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A Bandwidth Part (BWP) may be defined as a plurality of consecutive (Physical) Resource Blocks ((P)RBs) in the frequency domain, and the BWP may correspond to one numerology (e.g., SCS, CP length, and so on). A carrier may include a maximum of N number BWPs (e.g., 5 BWPs). Data communication may be performed via an activated BWP. Each element may be referred to as a Resource Element (RE) within a resource grid and one complex symbol may be mapped to each element. Meanwhile, a radio interface between a UE and another UE or a radio interface between the UE and a network may consist of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present disclosure, the L1 layer may imply a physical layer. In addition, for example, the L2 layer may imply at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. In addition, for example, the L3 layer may imply an RRC layer. Hereinafter, a bandwidth part (BWP) and a carrier will be described. The BWP may be a set of consecutive physical resource blocks (PRBs) in a given numerology. The PRB may be selected from consecutive sub-sets of common resource blocks (CRBs) for the given numerology on a given carrier. When using bandwidth adaptation (BA), a reception bandwidth and transmission bandwidth of a UE are not necessarily as large as a bandwidth of a cell, and the reception bandwidth and transmission bandwidth of the BS may be adjusted. For example, a network/BS may inform the UE of bandwidth adjustment. For example, the UE receive information/configuration for bandwidth adjustment from the network/BS. In this case, the UE may perform bandwidth adjustment based on the received information/configuration. For example, the bandwidth adjustment may include an increase/decrease of the bandwidth, a position change of the bandwidth, or a change in subcarrier spacing of the bandwidth. For example, the bandwidth may be decreased during a period in which activity is low to save power. For example, the position of the bandwidth may move in a frequency domain. For example, the position of the bandwidth may move in the frequency domain to increase scheduling flexibility. For example, the subcarrier spacing of the bandwidth may be changed. For example, the subcarrier spacing of the bandwidth may be changed to allow a different service. A subset of a total cell bandwidth of a cell may be called a bandwidth part (BWP). The BA may be performed when the BS/network configures the BWP to the UE and the BS/network informs the UE of the BWP currently in an active state among the configured BWPs. For example, the BWP may be at least any one of an active BWP, an initial BWP, and/or a default BWP. For example, the UE may not monitor downlink radio link quality in a DL BWP other than an active DL BWP on a primary cell (PCell). For example, the UE may not receive PDCCH, physical downlink shared channel (PDSCH), or channel state information-reference signal (CSI-RS) (excluding RRM) outside the active DL BWP. For example, the UE may not trigger a channel state information (CSI) report for the inactive DL BWP. For example, the UE may not transmit physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH) outside an active UL BWP. For example, in a downlink case, the initial BWP may be given as a consecutive RB set for a remaining minimum system information (RMSI) control resource set (CORESET) (configured by physical broadcast channel (PBCH)). For example, in an uplink case, the initial BWP may be given by system information block (SIB) for a random access procedure. For example, the default BWP may be configured by a higher layer. For example, an initial value of the default BWP may be an initial DL BWP. For energy saving, if the UE fails to detect downlink control information (DCI) during a specific period, the UE may switch the active BWP of the UE to the default BWP. Meanwhile, the BWP may be defined for SL. The same SL BWP may be used in transmission and reception. For example, a transmitting UE may transmit a SL channel or a SL signal on a specific BWP, and a receiving UE may receive the SL channel or the SL signal on the specific BWP. In a licensed carrier, the SL BWP may be defined separately from a Uu BWP, and the SL BWP may have configuration signaling separate from the Uu BWP. For example, the UE may receive a configuration for the SL BWP from the BS/network. The SL BWP may be (pre-)configured in a carrier with respect to an out-of-coverage NR V2X UE and an RRC_IDLE UE. For the UE in the RRC_CONNECTED mode, at least one SL BWP may be activated in the carrier. FIG.7shows an example of a BWP, based on an embodiment of the present disclosure. The embodiment ofFIG.7may be combined with various embodiments of the present disclosure. It is assumed in the embodiment ofFIG.7that the number of BWPs is 3. Referring toFIG.7, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other end thereof. In addition, the PRB may be a resource block numbered within each BWP. A point A may indicate a common reference point for a resource block grid. The BWP may be configured by a point A, an offset NstartBWPfrom the point A, and a bandwidth NsizeBWP. For example, the point A may be an external reference point of a PRB of a carrier in which a subcarrier 0 of all numerologies (e.g., all numerologies supported by a network on that carrier) is aligned. For example, the offset may be a PRB interval between a lowest subcarrier and the point A in a given numerology. For example, the bandwidth may be the number of PRBs in the given numerology. Hereinafter, V2X or SL communication will be described. FIG.8shows a radio protocol architecture for a SL communication, based on an embodiment of the present disclosure. The embodiment ofFIG.8may be combined with various embodiments of the present disclosure. More specifically,FIG.8(a)shows a user plane protocol stack, andFIG.8(b)shows a control plane protocol stack. Hereinafter, a sidelink synchronization signal (SLSS) and synchronization information will be described. The SLSS may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS), as a SL-specific sequence. The PSSS may be referred to as a sidelink primary synchronization signal (S-PSS), and the SSSS may be referred to as a sidelink secondary synchronization signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 gold sequences may be used for the S-SSS. For example, a UE may use the S-PSS for initial signal detection and for synchronization acquisition. For example, the UE may use the S-PSS and the S-SSS for acquisition of detailed synchronization and for detection of a synchronization signal ID. A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for transmitting default (system) information which must be first known by the UE before SL signal transmission/reception. For example, the default information may be information related to SLSS, a duplex mode (DM), a time division duplex (TDD) uplink/downlink (UL/DL) configuration, information related to a resource pool, a type of an application related to the SLSS, a subframe offset, broadcast information, or the like. For example, for evaluation of PSBCH performance, in NR V2X, a payload size of the PSBCH may be 56 bits including 24-bit cyclic redundancy check (CRC). The S-PSS, the S-SSS, and the PSBCH may be included in a block format (e.g., SL synchronization signal (SS)/PSBCH block, hereinafter, sidelink-synchronization signal block (S-SSB)) supporting periodical transmission. The S-SSB may have the same numerology (i.e., SCS and CP length) as a physical sidelink control channel (PSCCH)/physical sidelink shared channel (PSSCH) in a carrier, and a transmission bandwidth may exist within a (pre-)configured sidelink (SL) BWP. For example, the S-SSB may have a bandwidth of 11 resource blocks (RBs). For example, the PSBCH may exist across 11 RBs. In addition, a frequency position of the S-SSB may be (pre-)configured. Accordingly, the UE does not have to perform hypothesis detection at frequency to discover the S-SSB in the carrier. FIG.9shows a UE performing V2X or SL communication, based on an embodiment of the present disclosure. The embodiment ofFIG.9may be combined with various embodiments of the present disclosure. Referring toFIG.9, in V2X or SL communication, the term ‘UE’ may generally imply a UE of a user. However, if a network equipment such as a BS transmits/receives a signal according to a communication scheme between UEs, the BS may also be regarded as a sort of the UE. For example, a UE1may be a first apparatus100, and a UE2may be a second apparatus200. For example, the UE1may select a resource unit corresponding to a specific resource in a resource pool which implies a set of series of resources. In addition, the UE1may transmit a SL signal by using the resource unit. For example, a resource pool in which the UE1is capable of transmitting a signal may be configured to the UE2which is a receiving UE, and the signal of the UE1may be detected in the resource pool. Herein, if the UE1is within a connectivity range of the BS, the BS may inform the UE1of the resource pool. Otherwise, if the UE1is out of the connectivity range of the BS, another UE may inform the UE1of the resource pool, or the UE1may use a pre-configured resource pool. In general, the resource pool may be configured in unit of a plurality of resources, and each UE may select a unit of one or a plurality of resources to use it in SL signal transmission thereof. Hereinafter, resource allocation in SL will be described. FIG.10shows a procedure of performing V2X or SL communication by a UE based on a transmission mode, based on an embodiment of the present disclosure. The embodiment ofFIG.10may be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be called a mode or a resource allocation mode. Hereinafter, for convenience of explanation, in LTE, the transmission mode may be called an LTE transmission mode. In NR, the transmission mode may be called an NR resource allocation mode. For example,FIG.10(a)shows a UE operation related to an LTE transmission mode 1 or an LTE transmission mode 3. Alternatively, for example,FIG.10(a)shows a UE operation related to an NR resource allocation mode 1. For example, the LTE transmission mode 1 may be applied to general SL communication, and the LTE transmission mode 3 may be applied to V2X communication. For example,FIG.10(b)shows a UE operation related to an LTE transmission mode 2 or an LTE transmission mode 4. Alternatively, for example,FIG.10(b)shows a UE operation related to an NR resource allocation mode 2. Referring toFIG.10(a), in the LTE transmission mode 1, the LTE transmission mode 3, or the NR resource allocation mode 1, a BS may schedule a SL resource to be used by the UE for SL transmission. For example, the BS may perform resource scheduling to a UE1through a PDCCH (more specifically, downlink control information (DCI)), and the UE1may perform V2X or SL communication with respect to a UE2according to the resource scheduling. For example, the UE1may transmit a sidelink control information (SCI) to the UE2through a physical sidelink control channel (PSCCH), and thereafter transmit data based on the SCI to the UE2through a physical sidelink shared channel (PSSCH). Referring toFIG.10(b), in the LTE transmission mode 2, the LTE transmission mode 4, or the NR resource allocation mode 2, the UE may determine a SL transmission resource within a SL resource configured by a BS/network or a pre-configured SL resource. For example, the configured SL resource or the pre-configured SL resource may be a resource pool. For example, the UE may autonomously select or schedule a resource for SL transmission. For example, the UE may perform SL communication by autonomously selecting a resource within a configured resource pool. For example, the UE may autonomously select a resource within a selective window by performing a sensing and resource (re)selection procedure. For example, the sensing may be performed in unit of subchannels. In addition, the UE1which has autonomously selected the resource within the resource pool may transmit the SCI to the UE2through a PSCCH, and thereafter may transmit data based on the SCI to the UE2through a PSSCH. FIG.11shows three cast types, based on an embodiment of the present disclosure. The embodiment ofFIG.11may be combined with various embodiments of the present disclosure. Specifically,FIG.11(a)shows broadcast-type SL communication,FIG.11(b)shows unicast type-SL communication, andFIG.11(c)shows groupcast-type SL communication. In case of the unicast-type SL communication, a UE may perform one-to-one communication with respect to another UE. In case of the groupcast-type SL transmission, the UE may perform SL communication with respect to one or more UEs in a group to which the UE belongs. In various embodiments of the present disclosure, SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, or the like. Hereinafter, sidelink (SL) congestion control will be described. If a UE autonomously determines an SL transmission resource, the UE also autonomously determines a size and frequency of use for a resource used by the UE. Of course, due to a constraint from a network or the like, it may be restricted to use a resource size or frequency of use, which is greater than or equal to a specific level. However, if all UEs use a relatively great amount of resources in a situation where many UEs are concentrated in a specific region at a specific time, overall performance may significantly deteriorate due to mutual interference. Accordingly, the UE may need to observe a channel situation. If it is determined that an excessively great amount of resources are consumed, it is preferable that the UE autonomously decreases the use of resources. In the present disclosure, this may be defined as congestion control (CR). For example, the UE may determine whether energy measured in a unit time/frequency resource is greater than or equal to a specific level, and may adjust an amount and frequency of use for its transmission resource based on a ratio of the unit time/frequency resource in which the energy greater than or equal to the specific level is observed. In the present disclosure, the ratio of the time/frequency resource in which the energy greater than or equal to the specific level is observed may be defined as a channel busy ratio (CBR). The UE may measure the CBR for a channel/frequency. Additionally, the UE may transmit the measured CBR to the network/BS. FIG.12shows a resource unit for CBR measurement, based on an embodiment of the present disclosure. The embodiment ofFIG.12may be combined with various embodiments of the present disclosure. Referring toFIG.12, CBR may denote the number of sub-channels in which a measurement result value of a received signal strength indicator (RSSI) has a value greater than or equal to a pre-configured threshold as a result of measuring the RSSI by a UE on a sub-channel basis for a specific period (e.g., 100 ms). Alternatively, the CBR may denote a ratio of sub-channels having a value greater than or equal to a pre-configured threshold among sub-channels for a specific duration. For example, in the embodiment ofFIG.12, if it is assumed that a hatched sub-channel is a sub-channel having a value greater than or equal to a pre-configured threshold, the CBR may denote a ratio of the hatched sub-channels for a period of 100 ms. Additionally, the UE may report the CBR to the BS. Further, congestion control considering a priority of traffic (e.g., packet) may be necessary. To this end, for example, the UE may measure a channel occupancy ratio (CR). Specifically, the UE may measure the CBR, and the UE may determine a maximum value CRlimitk of a channel occupancy ratio k (CRk) that can be occupied by traffic corresponding to each priority (e.g., k) based on the CBR. For example, the UE may derive the maximum value CRlimitk of the channel occupancy ratio with respect to a priority of each traffic, based on a predetermined table of CBR measurement values. For example, in case of traffic having a relatively high priority, the UE may derive a maximum value of a relatively great channel occupancy ratio. Thereafter, the UE may perform congestion control by restricting a total sum of channel occupancy ratios of traffic, of which a priority k is lower than i, to a value less than or equal to a specific value. Based on this method, the channel occupancy ratio may be more strictly restricted for traffic having a relatively low priority. In addition thereto, the UE may perform SL congestion control by using a method of adjusting a level of transmit power, dropping a packet, determining whether retransmission is to be performed, adjusting a transmission RB size (Modulation and Coding Scheme (MCS) coordination), or the like. Hereinafter, a hybrid automatic repeat request (HARQ) procedure will be described. An error compensation scheme is used to secure communication reliability. Examples of the error compensation scheme may include a forward error correction (FEC) scheme and an automatic repeat request (ARQ) scheme. In the FEC scheme, errors in a receiving end are corrected by attaching an extra error correction code to information bits. The FEC scheme has an advantage in that time delay is small and no information is additionally exchanged between a transmitting end and the receiving end but also has a disadvantage in that system efficiency deteriorates in a good channel environment. The ARQ scheme has an advantage in that transmission reliability can be increased but also has a disadvantage in that a time delay occurs and system efficiency deteriorates in a poor channel environment. A hybrid automatic repeat request (HARQ) scheme is a combination of the FEC scheme and the ARQ scheme. In the HARQ scheme, it is determined whether an unrecoverable error is included in data received by a physical layer, and retransmission is requested upon detecting the error, thereby improving performance. In case of SL unicast and groupcast, HARQ feedback and HARQ combining in the physical layer may be supported. For example, when a receiving UE operates in a resource allocation mode 1 or 2, the receiving UE may receive the PSSCH from a transmitting UE, and the receiving UE may transmit HARQ feedback for the PSSCH to the transmitting UE by using a sidelink feedback control information (SFCI) format through a physical sidelink feedback channel (PSFCH). For example, the SL HARQ feedback may be enabled for unicast. In this case, in a non-code block group (non-CBG) operation, if the receiving UE decodes a PSCCH of which a target is the receiving UE and if the receiving UE successfully decodes a transport block related to the PSCCH, the receiving UE may generate HARQ-ACK. In addition, the receiving UE may transmit the HARQ-ACK to the transmitting UE. Otherwise, if the receiving UE cannot successfully decode the transport block after decoding the PSCCH of which the target is the receiving UE, the receiving UE may generate the HARQ-NACK. In addition, the receiving UE may transmit HARQ-NACK to the transmitting UE. For example, the SL HARQ feedback may be enabled for groupcast. For example, in the non-CBG operation, two HARQ feedback options may be supported for groupcast. (1) Groupcast option 1: After the receiving UE decodes the PSCCH of which the target is the receiving UE, if the receiving UE fails in decoding of a transport block related to the PSCCH, the receiving UE may transmit HARQ-NACK to the transmitting UE through a PSFCH. Otherwise, if the receiving UE decodes the PSCCH of which the target is the receiving UE and if the receiving UE successfully decodes the transport block related to the PSCCH, the receiving UE may not transmit the HARQ-ACK to the transmitting UE. (2) Groupcast option 2: After the receiving UE decodes the PSCCH of which the target is the receiving UE, if the receiving UE fails in decoding of the transport block related to the PSCCH, the receiving UE may transmit HARQ-NACK to the transmitting UE through the PSFCH. In addition, if the receiving UE decodes the PSCCH of which the target is the receiving UE and if the receiving UE successfully decodes the transport block related to the PSCCH, the receiving UE may transmit the HARQ-ACK to the transmitting UE through the PSFCH. For example, if the groupcast option 1 is used in the SL HARQ feedback, all UEs performing groupcast communication may share a PSFCH resource. For example, UEs belonging to the same group may transmit HARQ feedback by using the same PSFCH resource. For example, if the groupcast option 2 is used in the SL HARQ feedback, each UE performing groupcast communication may use a different PSFCH resource for HARQ feedback transmission. For example, UEs belonging to the same group may transmit HARQ feedback by using different PSFCH resources. For example, when the SL HARQ feedback is enabled for groupcast, the receiving UE may determine whether to transmit the HARQ feedback to the transmitting UE based on a transmission-reception (TX-RX) distance and/or RSRP. For example, in the groupcast option 1, in case of the TX-RX distance-based HARQ feedback, if the TX-RX distance is less than or equal to a communication range requirement, the receiving UE may transmit HARQ feedback for the PSSCH to the transmitting UE. Otherwise, if the TX-RX distance is greater than the communication range requirement, the receiving UE may not transmit the HARQ feedback for the PSSCH to the transmitting UE. For example, the transmitting UE may inform the receiving UE of a location of the transmitting UE through SCI related to the PSSCH. For example, the SCI related to the PSSCH may be second SCI. For example, the receiving UE may estimate or obtain the TX-RX distance based on a location of the receiving UE and the location of the transmitting UE. For example, the receiving UE may decode the SCI related to the PSSCH and thus may know the communication range requirement used in the PSSCH. For example, in case of the resource allocation mode 1, a time (offset) between the PSFCH and the PSSCH may be configured or pre-configured. In case of unicast and groupcast, if retransmission is necessary on SL, this may be indicated to a BS by an in-coverage UE which uses the PUCCH. The transmitting UE may transmit an indication to a serving BS of the transmitting UE in a form of scheduling request (SR)/buffer status report (BSR), not a form of HARQ ACK/NACK. In addition, even if the BS does not receive the indication, the BS may schedule an SL retransmission resource to the UE. For example, in case of the resource allocation mode 2, a time (offset) between the PSFCH and the PSSCH may be configured or pre-configured. For example, from a perspective of UE transmission in a carrier, TDM between the PSCCH/PSSCH and the PSFCH may be allowed for a PSFCH format for SL in a slot. For example, a sequence-based PSFCH format having a single symbol may be supported. Herein, the single symbol may not an AGC duration. For example, the sequence-based PSFCH format may be applied to unicast and groupcast. For example, in a slot related to a resource pool, a PSFCH resource may be configured periodically as N slot durations, or may be pre-configured. For example, N may be configured as one or more values greater than or equal to 1. For example, N may be 1, 2, or 4. For example, HARQ feedback for transmission in a specific resource pool may be transmitted only through a PSFCH on the specific resource pool. For example, if the transmitting UE transmits the PSSCH to the receiving UE across a slot #X to a slot #N, the receiving UE may transmit HARQ feedback for the PSSCH to the transmitting UE in a slot #(N+A). For example, the slot #(N+A) may include a PSFCH resource. Herein, for example, A may be a smallest integer greater than or equal to K. For example, K may be the number of logical slots. In this case, K may be the number of slots in a resource pool. Alternatively, for example, K may be the number of physical slots. In this case, K may be the number of slots inside or outside the resource pool. For example, if the receiving UE transmits HARQ feedback on a PSFCH resource in response to one PSSCH transmitted by the transmitting UE to the receiving UE, the receiving UE may determine a frequency domain and/or code domain of the PSFCH resource based on an implicit mechanism in a configured resource pool. For example, the receiving UE may determine the frequency domain and/or code domain of the PSFCH resource, based on at least one of a slot index related to PSCCH/PSSCH/PSFCH, a sub-channel related to PSCCH/PSSCH, and/or an identifier for identifying each receiving UE in a group for HARQ feedback based on the groupcast option 2. Additionally/alternatively, for example, the receiving UE may determine the frequency domain and/or code domain of the PSFCH resource, based on at least one of SL RSRP, SINR, L1 source ID, and/or location information. For example, if HARQ feedback transmission through the PSFCH of the UE and HARQ feedback reception through the PSFCH overlap, the UE may select any one of HARQ feedback transmission through the PSFCH and HARQ feedback reception through the PSFCH based on a priority rule. For example, the priority rule may be based on at least priority indication of the related PSCCH/PSSCH. For example, if HARQ feedback transmission of a UE through a PSFCH for a plurality of UEs overlaps, the UE may select specific HARQ feedback transmission based on the priority rule. For example, the priority rule may be based on at least priority indication of the related PSCCH/PSSCH. Meanwhile, in the present disclosure, for example, a transmitting UE (TX UE) may be a UE which transmits data to a (target) receiving UE (RX UE). For example, the TX UE may be a UE which performs PSCCH transmission and/or PSSCH transmission. For example, the TX UE may be a UE which transmits SL CSI-RS(s) and/or a SL CSI report request indicator to the (target) RX UE. For example, the TX UE may be a UE which transmits (pre-defined) reference signal(s) (e.g., PSSCH demodulation reference signal (DM-RS)) and/or a SL (L1) RSRP report request indicator, to the (target) RX UE, to be used for SL (L1) RSRP measurement. For example, the TX UE may be a UE which transmits a (control) channel (e.g., PSCCH, PSSCH, etc.) and/or reference signal(s) on the (control) channel (e.g., DM-RS, CSI-RS, etc.), to be used for a SL RLM operation and/or a SL RLF operation of the (target) RX UE. Meanwhile, in the present disclosure, for example, a receiving UE (RX UE) may be a UE which transmits SL HARQ feedback to a transmitting UE (TX UE) based on whether decoding of data received from the TX UE is successful and/or whether detection/decoding of a PSCCH (related to PSSCH scheduling) transmitted by the TX UE is successful. For example, the RX UE may be a UE which performs SL CSI transmission to the TX UE based on SL CSI-RS(s) and/or a SL CSI report request indicator received from the TX UE. For example, the RX UE is a UE which transmits a SL (L1) RSRP measurement value, to the TX UE, measured based on (pre-defined) reference signal(s) and/or a SL (L1) RSRP report request indicator received from the TX UE. For example, the RX UE may be a UE which transmits data of the RX UE to the TX UE. For example, the RX UE may be a UE which performs a SL RLM operation and/or a SL RLF operation based on a (pre-configured) (control) channel and/or reference signal(s) on the (control) channel received from the TX UE. Meanwhile, in the present disclosure, for example, the TX UE may transmit at least one of the following information to the RX UE through SCI(s). Herein, for example, the TX UE may transmit at least one of the following information to the RX UE through a first SCI and/or a second SCI.PSSCH (and/or PSCCH) related resource allocation information (e.g., the location/number of time/frequency resources, resource reservation information (e.g., period))SL CSI report request indicator or SL (L1) RSRP (and/or SL (L1) RSRQ and/or SL (L1) RSSI) report request indicatorSL CSI transmission indicator (or SL (L1) RSRP (and/or SL (L1) RSRQ and/or SL (L1) RSSI) information transmission indicator) (on a PSSCH)Modulation and Coding Scheme (MCS) informationTX power informationL1 destination ID information and/or L1 source ID informationSL HARQ process ID informationNew Data Indicator (NDI) informationRedundancy Version (RV) information(Transmission traffic/packet related) QoS information (e.g., priority information)SL CSI-RS transmission indicator or information on the number of antenna ports for (transmitting) SL CSI-RSTX UE location information or location (or distance range) information of the target RX UE (for which SL HARQ feedback is requested)Reference signal (e.g., DM-RS, etc.) information related to decoding (and/or channel estimation) of data transmitted through a PSSCH. For example, information related to a pattern of (time-frequency) mapping resources of DM-RS(s), RANK information, antenna port index information, etc. Meanwhile, in the present disclosure, for example, a PSCCH may be replaced/substituted with a SCI and/or a first SCI and/or a second SCI, or vice versa. For example, the SCI may be replaced/substituted with the PSCCH and/or the first SCI and/or the second SCI, or vice versa. For example, since the TX UE may transmit the second SCI to the RX UE through a PSSCH, the PSSCH may be replaced/substituted with the second SCI, or vice versa. For example, if SCI configuration fields are divided into two groups in consideration of a (relatively) high SCI payload size, the first SCI including a first SCI configuration field group may be referred to as a 1stSCI or 1st-stage SCI, and the second SCI including a second SCI configuration field group may be referred to as a 2ndSCI or 2nd-stage SCI. For example, the first SCI may be transmitted through a PSCCH. For example, the second SCI may be transmitted through a (independent) PSCCH. For example, the second SCI may be piggybacked and transmitted together with data through a PSSCH. Meanwhile, in the present disclosure, for example, the term “configure/configured” or the term “define/defined” may refer to (pre)configuration from a base station or a network (through pre-defined signaling (e.g., SIB, MAC, RRC, etc.)) (for each resource pool). For example, “that A is configured” may mean “that the base station/network transmits information related to A to the UE”. Meanwhile, in the present disclosure, for example, an RB may be replaced/substituted with a subcarrier, or vice versa. For example, a packet or a traffic may be replaced/substituted with a transport block (TB) or a medium access control protocol data unit (MAC PDU) based on a transmission layer, or vice versa. For example, a code block group (CBG) may be replaced/substituted with a TB, or vice versa. For example, a source ID may be replaced/substituted with a destination ID, or vice versa. For example, an L1 ID may be replaced/substituted with an L2 ID, or vice versa. For example, the L1 ID may be an L1 source ID or an L1 destination ID. For example, the L2 ID may be an L2 source ID or an L2 destination ID. Meanwhile, in the present disclosure, for example, an operation of the transmitting UE to reserve/select/determine retransmission resource(s) may include: an operation of the transmitting UE to reserve/select/determine potential retransmission resource(s) for which actual use will be determined based on SL HARQ feedback information received from the receiving UE. Meanwhile, in the present disclosure, a sub-selection window may be replaced/substituted with a selection window and/or a pre-configured number of resource sets within the selection window, or vice versa. Meanwhile, in the present disclosure, SL MODE 1 may refer to a resource allocation method or a communication method in which a base station directly schedules SL transmission resource(s) for a TX UE through pre-defined signaling (e.g., DCI or RRC message). For example, SL MODE 2 may refer to a resource allocation method or a communication method in which a UE independently selects SL transmission resource(s) in a resource pool pre-configured or configured from a base station or a network. For example, a UE performing SL communication based on SL MODE 1 may be referred to as a MODE 1 UE or MODE 1 TX UE, and a UE performing SL communication based on SL MODE 2 may be referred to as a MODE 2 UE or MODE 2 TX UE. Meanwhile, in the present disclosure, for example, a dynamic grant (DG) may be replaced/substituted with a configured grant (CG) and/or a semi-persistent scheduling (SPS) grant, or vice versa. For example, the DG may be replaced/substituted with a combination of the CG and the SPS grant, or vice versa. For example, the CG may include at least one of a configured grant (CG) type 1 and/or a configured grant (CG) type 2. For example, in the CG type 1, a grant may be provided by RRC signaling and may be stored as a configured grant. For example, in the CG type 2, a grant may be provided by a PDCCH, and may be stored or deleted as a configured grant based on L1 signaling indicating activation or deactivation of the grant. For example, in the CG type 1, a base station may allocate periodic resource(s) to a TX UE through an RRC message. For example, in the CG type 2, a base station may allocate periodic resource(s) to a TX UE through an RRC message, and the base station may dynamically activate or deactivate the periodic resource(s) through a DCI. Meanwhile, in the present disclosure, a channel may be replaced/substituted with a signal, or vice versa. For example, transmission/reception of a channel may include transmission/reception of a signal. For example, transmission/reception of a signal may include transmission/reception of a channel. For example, cast may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa. For example, a cast type may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa. Meanwhile, in the present disclosure, a resource may be replaced/substituted with a slot or a symbol, or vice versa. For example, the resource may include a slot and/or a symbol. For example, a PSSCH may be replaced/substituted with a PSCCH, or vice versa. Meanwhile, in the present disclosure, blind retransmission may refer that the TX UE performs retransmission without receiving SL HARQ feedback information from the RX UE. For example, SL HARQ feedback-based retransmission may refer that the TX UE determines whether to perform retransmission based on SL HARQ feedback information received from the RX UE. For example, if the TX UE receives NACK and/or DTX information from the RX UE, the TX UE may perform retransmission to the RX UE. Meanwhile, in the present disclosure, time may be replaced/substituted with frequency, or vice versa. Meanwhile, in the present disclosure, for example, for convenience of description, a (physical) channel used when a RX UE transmits at least one of the following information to a TX UE may be referred to as a PSFCH.SL HARQ feedback, SL CSI, SL (L1) RSRP Meanwhile, in the present disclosure, a Uu channel may include a UL channel and/or a DL channel. For example, the UL channel may include a PUSCH, a PUCCH, a sounding reference Signal (SRS), etc. For example, the DL channel may include a PDCCH, a PDSCH, a PSS/SSS, etc. For example, a SL channel may include a PSCCH, a PSSCH, a PSFCH, a PSBCH, a PSSS/SSSS, etc. Meanwhile, in the present disclosure, sidelink information may include at least one of a sidelink message, a sidelink packet, a sidelink service, sidelink data, sidelink control information, and/or a sidelink transport block (TB). For example, sidelink information may be transmitted through a PSSCH and/or a PSCCH. Meanwhile, in the present disclosure, a high priority may mean a small priority value, and a low priority may mean a large priority value. For example, Table 5 shows an example of priorities. TABLE 5service or logical channelpriority valueservice A or logical channel A1service B or logical channel B2service C or logical channel C3 Referring to Table 5, for example, service A or logical channel A related to the smallest priority value may have the highest priority. For example, service C or logical channel C related to the largest priority value may have the lowest priority. Meanwhile, in NR V2X communication or NR sidelink communication, a transmitting UE may reserve/select one or more transmission resources for sidelink transmission (e.g., initial transmission and/or retransmission), and the transmitting UE may transmit information on the location of the one or more transmission resources to receiving UE(s). Meanwhile, when performing sidelink communication, a method for a transmitting UE to reserve or pre-determine transmission resource(s) for receiving UE(s) may be representatively as follows. For example, the transmitting UE may perform a reservation of transmission resource(s) based on a chain. Specifically, for example, if the transmitting UE reserves K transmission resources, the transmitting UE may transmit location information for less than K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, for example, the SCI may include location information for less than the K transmission resources. Alternatively, for example, if the transmitting UE reserves K transmission resources related to a specific TB, the transmitting UE may transmit location information for less than K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for less than the K transmission resources. In this case, for example, it is possible to prevent performance degradation due to an excessive increase in payloads of the SCI, by signaling only the location information for less than K transmission resources to the receiving UE(s) through one SCI transmitted at any (or specific) transmission time or the time resource by the transmitting UE. FIG.13shows a method in which a UE that has reserved transmission resource(s) informs another UE of the transmission resource(s), based on an embodiment of the present disclosure. The embodiment ofFIG.13may be combined with various embodiments of the present disclosure. Specifically, for example, (a) ofFIG.13shows a method for performing by a transmitting UE chain-based resource reservation by transmitting/signaling location information of (maximum) 2 transmission resources to receiving UE(s) through one SCI, in the case of a value of K=4. For example, (b) ofFIG.13shows a method for performing by a transmitting UE chain-based resource reservation by transmitting/signaling location information of (maximum) 3 transmission resources to receiving UE(s) through one SCI, in the case of a value of K=4. For example, referring to (a) and (b) ofFIG.11, the transmitting UE may transmit/signal only location information of the fourth transmission-related resource to the receiving UE(s) through the fourth (or last) transmission-related PSCCH. For example, referring to (a) ofFIG.11, the transmitting UE may transmit/signal to the receiving UE(s) not only location information of the fourth transmission-related resource but also location information of the third transmission-related resource additionally through the fourth (or last) transmission-related PSCCH. For example, referring to (b) ofFIG.11, the transmitting UE may transmit/signal to the receiving UE(s) not only location information of the fourth transmission-related resource but also location information of the second transmission-related resource and location information of the third transmission-related resource additionally through the fourth (or last) transmission-related PSCCH. In this case, for example, in (a) and (b) ofFIG.11, if the transmitting UE may transmit/signal to the receiving UE(s) only location information of the fourth transmission-related resource through the fourth (or last) transmission-related PSCCH, the transmitting UE may set or designate a field/bit of location information of unused or remaining transmission resource(s) to a pre-configured value (e.g., 0). For example, in (a) and (b) ofFIG.11, if the transmitting UE may transmit/signal to the receiving UE(s) only location information of the fourth transmission-related resource through the fourth (or last) transmission-related PSCCH, the transmitting UE may be set or designate a field/bit of location information of unused or remaining transmission resource(s) to a pre-configured status/bit value indicating/representing the last transmission (among 4 transmissions). Meanwhile, for example, the transmitting UE may perform a reservation of transmission resource(s) based on a block. Specifically, for example, if the transmitting UE reserves K transmission resources, the transmitting UE may transmit location information for K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for K transmission resources. For example, if the transmitting UE reserves K transmission resources related to a specific TB, the transmitting UE may transmit location information for K transmission resources to receiving UE(s) through a SCI transmitted to the receiving UE(s) at any (or specific) transmission time or a time resource. That is, the SCI may include location information for K transmission resources. For example, (c) ofFIG.13shows a method for performing by the transmitting UE block-based resource reservation, by signaling location information of 4 transmission resources to receiving UE(s) through one SCI, in the case of a value of K=4. Meanwhile, for example, if the UE performs mode 1-based SL communication, the maximum number of retransmissions related to one TB of the UE may be limited. For example, if the UE performs mode 1-based SL communication, the maximum number of retransmissions related to a SL HARQ process of the UE may be limited. For example, if the UE performs mode 1-based SL communication, the maximum number of retransmissions related to a mode 1 configured grant (CG) of the UE may be limited. For example, if the UE performs mode 1-based SL communication, the maximum number of retransmissions related to a mode 1 dynamic grant (DG) of the UE may be limited. For example, the base station may limit the maximum number of retransmissions of the UE through pre-defined signaling (e.g., SIB, RRC, DCI, etc.). For example, the base station may transmit information related to the maximum number of retransmissions to the UE through pre-defined signaling. Hereinafter, for convenience of description, the maximum number of retransmissions may be referred to as MAX_RETXNUM. Hereinafter, for convenience of description, the UE performing mode 1-based SL communication may be referred to as a MODE 1 TX UE. For example, the MAX_RETXNUM may be the number of transmissions including both initial transmission and retransmission. Alternatively, for example, the MAX_RETXNUM may be the number of transmissions including only retransmissions, excluding initial transmissions. For example, if the MAX_RETXNUM of the MODE 1 TX UE is limited, the MODE 1 TX UE may use resource(s) allocated by specific (one) mode 1 CG or mode 1 DG without distinguishing the initial/retransmission purpose related to one TB. And/or, for example, if the MAX_RETXNUM of the MODE 1 TX UE is limited, the MODE 1 TX UE may use resource(s) allocated by specific (one) mode 1 CG or mode 1 DG without distinguishing the initial/retransmission purpose related to a SL HARQ process. For example, as described above, if the MODE 1 TX UE does not distinguish the allocated resource(s) for the initial transmission purpose and the retransmission purpose and use it, it may be difficult for the base station to accurately determine how many retransmissions have already been performed by the (corresponding) MODE 1 TX UE or the number of remaining retransmissions with respect to (corresponding) one TB and/or a SL HARQ process when the MODE 1 TX UE requests additional retransmission resource allocation through a (pre-configured) PUCCH resource (e.g., a resource for the MODE 1 TX UE to report SL HARQ feedback information received from the RX UE to the base station) to the base station. In other words, for example, when the base station allocates additional retransmission resource(s) based on the PUCCH transmitted by the MODE 1 TX UE, it may be difficult for the base station to adjust the number of resources to be allocated for retransmission so as not to exceed the MAX_RETXNUM of the UE with respect to one TB and/or the SL HARQ process (described above). For example, the total number of retransmission resources allocated by the base station to the UE with respect to the specific TB and/or the SL HARQ may be greater than the MAX_RETXNUM. Based on various embodiments of the present disclosure, a method for efficiently alleviating the above-described problem and an apparatus supporting the same are proposed. For example, whether or not to apply all or part of the methods and/or procedures proposed according to various embodiments of the present disclosure may be configured or determined differently or limitedly according to at least one of a resource pool, a service type, a service priority, a cast type, a destination UE, a (L1 or L2) destination ID, a (L1 or L2) source ID, a (service) QoS parameter (e.g. reliability, latency), a (resource pool) congestion level, a SL mode (e.g., mode 1, mode 2), a grant type (e.g., CG, DG), and/or a size of a packet/message (e.g., TB). For example, whether or not to apply all or part of the methods and/or procedures proposed according to various embodiments of the present disclosure may be configured or determined differently or limitedly for at least one of a chain-based resource reservation operation of the TX UE, a block-based resource reservation operation of the TX UE, a blind retransmission operation of the TX UE, s SL HARQ feedback-based retransmission operation of the TX UE, a CG-based resource selection/reservation/determination operation of the TX UE, and/or a DG-based resource selection/reservation/determination operation of the TX UE. For example, parameter(s) according to various embodiments of the present disclosure may be configured or determined differently or limitedly according to at least one of a resource pool, a service type, a service priority, a cast type, a destination UE, a (L1 or L2) destination ID, a (L1 or L2) source ID, a (service) QoS parameter (e.g. reliability, latency), a (resource pool) congestion level, a SL mode (e.g., mode 1, mode 2), a grant type (e.g., CG, DG), and/or a size of a packet/message (e.g., TB). For example, parameter(s) according to various embodiments of the present disclosure may be configured or determined differently or limitedly for at least one of a chain-based resource reservation operation of the TX UE, a block-based resource reservation operation of the TX UE, a blind retransmission operation of the TX UE, s SL HARQ feedback-based retransmission operation of the TX UE, a CG-based resource selection/reservation/determination operation of the TX UE, and/or a DG-based resource selection/reservation/determination operation of the TX UE. For example, the following (some) rules (e.g., OPTION B) may be limitedly applied only to a service with a relatively lower reliability requirement (than a pre-configured threshold value). For example, the following (some) rules (e.g., OPTION B) may be limitedly applied only to a service with a relatively high error rate requirement. For example, the following (some) rules (e.g., OPTION B) may be limitedly applied only to a service with an error rate requirement. For example, the error rate may be a block error rate (BLER). Based on an embodiment of the present disclosure, even if the number of retransmissions related to a specific TB of the MODE 1 TX UE reaches the MAX_RETXNUM, the MODE 1 TX UE may receive NACK information from the RX UE. For example, even if the number of retransmissions related to a specific SL HARQ process of the MODE 1 TX UE reaches the MAX_RETXNUM, the MODE 1 TX UE may receive NACK information from the RX UE. For example, even if the number of retransmissions related to a specific TB of the MODE 1 TX UE reaches the MAX_RETXNUM, the MODE 1 TX UE may not receive SL HARQ feedback information from the RX UE. For example, even if the number of retransmissions related to a specific SL HARQ process of the MODE 1 TX UE reaches the MAX_RETXNUM, the MODE 1 TX UE may not receive SL HARQ feedback information from the RX UE. For example, if the RX UE fails to decode/receive a PSCCH, or if the TX UE fails to receive/detect a PSFCH, the MODE 1 TX UE may not receive SL HARQ feedback information from the RX UE. For example, if the MODE 1 TX UE transmits a TB for which HARQ feedback is disabled to the RX UE, the MODE 1 TX UE may not receive SL HARQ feedback information from the RX UE. For example, as described above, if the MODE 1 TX UE receives NACK information from the RX UE, or if the MODE 1 TX UE does not receive SL HARQ feedback information from the RX UE, the MODE 1 TX UE may be configured to report ACK information or pre-configured state/indicator information to the base station through a (pre-configured) PUCCH resource. For example, the MODE 1 TX UE may report the ACK information or the pre-configured state/indicator information to the base station through the (pre-configured) PUCCH resource. For example, as described above, if the MODE 1 TX UE receives NACK information from the RX UE, or if the MODE 1 TX UE does not receive SL HARQ feedback information from the RX UE, the MODE 1 TX UE may be configured to report NACK information or DTX information to the base station through a (pre-configured) PUCCH resource. For example, the MODE 1 TX UE may report the NACK information or the DTX information to the base station through the (pre-configured) PUCCH resource. Hereinafter, for convenience of description, the operation in which the MODE 1 TX UE reports ACK information, pre-configured state/indicator information, NACK information, or DTX information to the base station through the (pre-configured) PUCCH resource may be referred to as OPTION A. Alternatively, for example, as described above, if the MODE 1 TX UE receives NACK information from the RX UE, or if the MODE 1 TX UE does not receive SL HARQ feedback information from the RX UE, the MODE 1 TX UE may be configured not to perform PUCCH transmission to the base station. For example, the MODE 1 TX UE may not perform PUCCH transmission to the base station. Hereinafter, for convenience of description, the operation in which the MODE 1 TX UE does not perform PUCCH transmission to the base station may be referred to as OPTION B. Herein, for example, the OPTION A may be applied or configured only if SL HARQ feedback information reported by the MODE 1 TX UE to the base station through the (pre-configured) PUCCH resource is SL HARQ feedback information for a plurality of TBs. For example, the OPTION A may be applied or configured only if SL HARQ feedback information reported by the MODE 1 TX UE to the base station through the (pre-configured) PUCCH resource is SL HARQ feedback information for a plurality of SL HARQ processes. For example, the OPTION A may be applied or configured only if SL HARQ feedback information, reported by the MODE 1 TX UE to the base station through the (pre-configured) PUCCH resource, includes SL HARQ feedback information for a TB and/or a HARQ process in which the number of retransmissions has reached the MAX_RETXNUM and SL HARQ feedback information for a TB and/or a HARQ process in which the number of retransmissions has not reached the MAX_RETXNUM. For example, based on the OPTION A, the base station may receive ACK information or pre-configured state/indicator information from the MODE 1 TX UE. For example, if the total number of retransmission-related resources allocated by the base station to the MODE 1 TX UE is greater than the MAX_RETXNUM, the base station may receive ACK information or pre-configured state/indicator information from the MODE 1 TX UE. Through this, retransmission resource(s) not to be actually used by the MODE 1 TX UE may be utilized for other purposes (e.g., UL communication) (by the base station). For example, the base station may allocate retransmission resource(s) not to be actually used by the MODE 1 TX UE as SL resource(s) of other UEs. For example, the base station may allocate retransmission resource(s) not to be actually used by the MODE 1 TX UE as UL resource(s) of other UEs. For example, the base station may allocate retransmission resource(s) not to be actually used by the MODE 1 TX UE as UL resource(s) of the MODE 1 TX UE. Based on an embodiment of the present disclosure, if the MODE 1 TX UE reports SL HARQ feedback information to the base station through the (pre-configured) PUCCH resource, the MODE 1 TX UE may transmit identifier information of a SL HARQ process associated with (each) SL HARQ feedback information together with SL HARQ feedback information to the base station. For example, the SL HARQ feedback information may be SL HARQ feedback information received from the RX UE. For example, if the SL HARQ feedback information is not received from the RX UE, the SL HARQ feedback information reported to the base station through the PUCCH resource may be generated by the MODE 1 TX UE. For example, if the MODE 1 TX UE reports SL HARQ feedback information to the base station through the (pre-configured) PUCCH resource, the MODE 1 TX UE may transmit index information of a mode 1 CG associated with (each) SL HARQ feedback information together with SL HARQ feedback information to the base station. For example, if the MODE 1 TX UE reports SL HARQ feedback information to the base station through the (pre-configured) PUCCH resource, the MODE 1 TX UE may transmit TB information associated with (each) SL HARQ feedback information together with SL HARQ feedback information to the base station. For example, if the MODE 1 TX UE reports SL HARQ feedback information to the base station through the (pre-configured) PUCCH resource, the MODE 1 TX UE may transmit information on the number of retransmissions performed with respect to the SL HARQ process associated with (each) SL HARQ feedback information together with SL HARQ feedback information to the base station. For example, if the MODE 1 TX UE reports SL HARQ feedback information to the base station through the (pre-configured) PUCCH resource, the MODE 1 TX UE may transmit information on the number of retransmissions performed with respect to the TB associated with (each) SL HARQ feedback information together with SL HARQ feedback information to the base station. For example, if the MODE 1 TX UE reports SL HARQ feedback information to the base station through the (pre-configured) PUCCH resource, the MODE 1 TX UE may transmit information on the number of remaining retransmissions related to the SL HARQ process associated with (each) SL HARQ feedback information together with SL HARQ feedback information to the base station. For example, if the MODE 1 TX UE reports SL HARQ feedback information to the base station through the (pre-configured) PUCCH resource, the MODE 1 TX UE may transmit information on the number of remaining retransmissions related to the TB associated with (each) SL HARQ feedback information together with SL HARQ feedback information to the base station. FIG.14shows a procedure for a TX UE to report HARQ feedback information to a base station, based on an embodiment of the present disclosure. The embodiment ofFIG.14may be combined with various embodiments of the present disclosure. Referring toFIG.14, in step S1410, the TX UE may receive information related to a SL resource and/or information related to a PUCCH resource from the base station. For example, the SL resource may include a PSCCH resource and/or a PSSCH resource. For example, the PUCCH resource may be a resource related to the SL resource. For example, the PUCCH resource may be a resource used to report HARQ feedback to the base station. Additionally, for example, the TX UE may receive information related to the maximum number of transmissions from the base station. For example, the maximum number of transmissions may include initial transmission and retransmission. For example, the maximum number of transmissions may be the maximum number of transmissions related to a specific TB. For example, the maximum number of transmissions may be the maximum number of transmissions related to a specific MAC PDU. In step S1420, the TX UE may transmit a PSCCH and/or a PSSCH to the RX UE. For example, the TX UE may transmit the PSCCH and/or the PSSCH to the RX UE based on the SL resource. For example, the TX UE may transmit a medium access control (MAC) packet data unit (PDU) for which HARQ feedback is disabled to the RX UE based on the SL resource. The MAC PDU for which HARQ feedback is disabled may be transmitted through the PSSCH. For example, the TX UE may perform blind retransmission for the MAC PDU based on the SL resource. In this case, since HARQ feedback is disabled for the MAC PDU, HARQ feedback for the MAC PDU may not be transmitted by the RX UE. That is, in the case of the blind retransmitted MAC PDU, the RX UE may not transmit HARQ feedback for the MAC PDU. In step S1430, if HARQ feedback is disabled for the MAC PDU and retransmission of the MAC PDU is not required, the TX UE may generate ACK information related to transmission of the MAC PDU. For example, if the number of transmissions for the MAC PDU reaches the maximum number of transmissions, retransmission of the MAC PDU may not be required for the TX UE. For example, if the number of transmissions for the MAC PDU reaches the maximum number of transmissions, the TX UE may not be allowed to retransmit the MAC PDU. In step S1440, the TX UE may transmit the ACK information to the base station based on the PUCCH resource. For example, the base station may not allocate additional (re)transmission resource(s) to the TX UE based on the ACK information. Based on an embodiment of the present disclosure, the MODE 1 TX UE does not successfully transmit a TB to the RX UE or fails to successfully complete a SL HARQ process by using (re)transmission resource(s) previously allocated/scheduled, the MODE 1 TX UE may request allocation/scheduling of additional retransmission resource(s) for the TB and/or the SL HARQ process from the base station. For this, the MODE 1 TX UE may report SL HARQ feedback information to the base station through a (pre-configured) PUCCH resource. For example, the SL HARQ feedback information may be SL HARQ feedback information received from the RX UE. For example, if the SL HARQ feedback information is not received from the RX UE, the SL HARQ feedback information reported to the base station through the PUCCH resource may be generated by the MODE 1 TX UE. FIG.15shows a procedure for a TX UE to report HARQ feedback information to a base station, based on an embodiment of the present disclosure. The embodiment ofFIG.15may be combined with various embodiments of the present disclosure. Referring toFIG.15, in step S1510, the TX UE may receive information related to a SL resource and/or information related to a PUCCH resource from the base station. In step S1520, the TX UE may transmit a PSCCH and/or a PSSCH to the RX UE. In step S1530, the TX UE may receive a PSFCH related to the PSCCH and/or the PSSCH from the RX UE. Alternatively, for example, the RX UE may skip/omit transmission of the PSFCH. Alternatively, for example, the TX UE may skip/omit reception of the PSFCH. In step S1540, the TX UE may transmit a PUCCH and/or a PUSCH to the base station. For example, the TX UE may report HARQ feedback information to the base station through the PUCCH and/or the PUSCH. For example, HARQ feedback information reported by the TX UE through the PUCCH and/or the PUSCH may be determined based on the CASE A to the CASE D. For example, whether or not the TX UE skips/omits PUCCH transmission and/or PUSCH transmission may be determined based on the CASE A to the CASE D. For convenience of description, the CASE A to the CASE D may be defined as below. Herein, for example, the PSCCH/PSSCH may be a PSCCH/PSSCH related to a (specific) TB. For example, the PSCCH/PSSCH may be a PSCCH/PSSCH related to a (specific) SL HARQ process. For example, a TB to be transmitted may be a TB to be transmitted by the TX UE in relation to a (specific) SL HARQ process. 1) CASE A For example, in case the TX UE transmits a PSCCH/PSSCH to the RX UE, and the RX UE does not transmit a PSFCH (e.g., SL HARQ feedback information) to the TX UE due to the failure of decoding the PSCCH, and/or For example, in case the TX UE transmits a PSCCH/PSSCH to the RX UE, and the RX UE does not transmit a PSFCH related to the PSCCH/PSSCH to the TX UE based on a (pre-configured) priority-based dropping rule. 2) CASE B For example, in case the TX UE transmits a PSCCH/PSSCH to the RX UE, and the RX UE which has received the PSCCH/PSSCH transmits a PSFCH (e.g., SL HARQ feedback information) related to the PSCCH/PSSCH to the TX UE, and the TX UE fails to receive the (corresponding) PSFCH, and/or For example, in case the TX UE transmits a PSCCH/PSSCH to the RX UE, and the RX UE which has successfully decoded the PSCCH/PSSCH transmits a PSFCH (e.g., SL HARQ feedback information) related to the PSCCH/PSSCH to the TX UE, and the TX UE fails to receive the (corresponding) PSFCH, and/or For example, in case the TX UE transmits a PSCCH/PSSCH to the RX UE, and the RX UE which has received the PSCCH/PSSCH transmits a PSFCH (e.g., SL HARQ feedback information) related to the PSCCH/PSSCH to the TX UE, and the TX UE does not receive the PSFCH related to the PSCCH/PSSCH based on a (pre-configured) priority-based dropping rule, and/or For example, in case the TX UE transmits a PSCCH/PSSCH to the RX UE, and the RX UE which has successfully decoded the PSCCH/PSSCH transmits a PSFCH (e.g., SL HARQ feedback information) related to the PSCCH/PSSCH to the TX UE, and the TX UE does not receive the PSFCH related to the PSCCH/PSSCH based on a (pre-configured) priority-based dropping rule 3) CASE C For example, in case the TX UE does not transmit a PSCCH/PSSCH to the RX UE because a TB to be transmitted by the TX UE to the RX UE does not exist in a buffer of the TX UE 4) CASE D For example, in case a TB to be transmitted by the TX UE to the RX UE is in a buffer of the TX UE, and the TX UE does not transmit a PSCCH/PSSCH based on a (pre-configured) priority-based dropping rule, and/or For example, in case a TB to be transmitted by the TX UE to the RX UE is in a buffer of the TX UE, and the TX UE does not transmit a PSCCH/PSSCH based on congestion control-based physical layer parameter restriction (e.g., (maximum) CR value restriction) For example, if a TB to be transmitted by the TX UE to the RX UE is (still) exist in a buffer of the TX UE, the TX UE may transmit NACK information to the base station through a PUCCH to request additional retransmission resource allocation/scheduling from the base station. For example, if a TB to be transmitted by the TX UE to the RX UE is (still) exist in a buffer of the TX UE, the TX UE may transmit DTX information to the base station through a PUCCH to request additional retransmission resource allocation/scheduling from the base station. For example, if a TB to be transmitted by the TX UE to the RX UE is (still) exist in a buffer of the TX UE, the TX UE may transmit pre-configured state/indicator information to the base station through a PUCCH to request additional retransmission resource allocation/scheduling from the base station. For example, the case in which the TB to be transmitted by the TX UE to the RX UE is (still) exist in the buffer of the TX UE may be at least one of the CASE A, the CASE B and/or the CASE D. For example, if the TX UE does not (actually) transmit a TB to the RX UE, the TX UE may transmit NACK information to the base station through a PUCCH to request additional retransmission resource allocation/scheduling from the base station. For example, if the TX UE does not (actually) transmit a TB to the RX UE, the TX UE may transmit DTX information to the base station through a PUCCH to request additional retransmission resource allocation/scheduling from the base station. For example, if the TX UE does not (actually) transmit a TB to the RX UE, the TX UE may transmit pre-configured state/indicator information to the base station through a PUCCH to request additional retransmission resource allocation/scheduling from the base station. For example, the case in which the TX UE does not (actually) transmit the TB to the RX UE may be the CASE D. For example, if a TB to be transmitted by the TX UE to the RX UE does not exist in a buffer of the TX UE, the TX UE may transmit ACK information to the base station through a PUCCH. For example, if a TB to be transmitted by the TX UE to the RX UE does not exist in a buffer of the TX UE, the TX UE may not transmit a PUCCH to the base station. In this case, the base station may not perform additional retransmission resource allocation/scheduling for the TX UE. For example, the case in which the TB to be transmitted by the TX UE to the RX UE does not exist in the buffer of the TX UE may be the CASE C. For example, if the TX UE receives ACK information for the PSCCH/PSSCH transmitted by the TX UE from the RX UE, the TX UE may transmit ACK information to the base station through a PUCCH. For example, if the TX UE receives ACK information for the PSCCH/PSSCH transmitted by the TX UE from the RX UE, the TX UE may not transmit a PUCCH to the base station. In this case, the base station may not perform additional retransmission resource allocation/scheduling for the TX UE. Based on an embodiment of the present disclosure, if at least one of the first to third conditions is satisfied, the MODE 1 TX UE may designate/set a (pre-defined) SL HARQ feedback request field included in a SCI to “disabled”. For example, the SCI may be a first SCI transmitted through a PSCCH. For example, the SCI may be a second SCI transmitted through a PSSCH. For example, if a SL HARQ feedback operation is enabled (in advance) for a resource pool, and if at least one of the first to third conditions is satisfied, the MODE 1 TX UE may designate/set the (pre-defined) SL HARQ feedback request field included in the SCI to “disabled”. For example, if the SL HARQ feedback operation is enabled (in advance) between the TX UE and the RX UE for the resource pool, and if at least one of the first to third conditions is satisfied, the MODE 1 TX UE may designate/set the (pre-defined) SL HARQ feedback request field included in the SCI to “disabled”. For example, if the SL HARQ feedback operation is enabled for a specific MAC PDU, and if at least one of the first to third conditions is satisfied, the MODE 1 TX UE may designate/set the (pre-defined) SL HARQ feedback request field included in the SCI related to the MAC PDU to “disabled”. For example, the network may configure or pre-configure the first to third conditions to the UE. For example, the network may be a base station or an RSU. For example, if at least one of the first to third conditions is satisfied, the MODE 1 TX UE which transmits a PSCCH/PSSCH may instruct or inform the RX UE not to transmit SL HARQ feedback for the PSCCH/PSSCH. For example, based on whether or not pre-configured condition(s) is satisfied, the TX UE may (independently) change (dynamically) a value of the SL HARQ feedback request field related to PSCCH/PSSCH transmission. 1) First condition: if a (resource pool-related) congestion level measured by the TX UE is higher than a pre-configured first threshold, or if the (resource pool-related) congestion level measured by the TX UE is lower than a pre-configured second threshold, and/or 2) Second condition: if the number of PSFCH resources necessary for and/or required for PSCCH/PSSCH transmission of the TX UE is less than a pre-configured threshold (in a resource pool), and/or 3) Third condition: if the TX UE transmits SL information having a priority lower than a pre-configured priority (i.e., a large priority value), or if the TX UE transmits SL information having a requirement lower than a pre-configured criterion (e.g., low reliability, high latency) Meanwhile, if the rule and/or the operation described above is applied, for example, when the TX UE transmits a PSCCH/PSSCH to the RX UE, it may be difficult for the base station to determine (accurately) a state/value of a (pre-defined) SL HARQ feedback request field included in a SCI indicated by the TX UE. In consideration of this, for example, if the TX UE transmits the PSCCH/PSSCH to the RX UE by designating/setting the SL HARQ feedback request field to “disabled”, the TX UE may report ACK information to the base station through a PUCCH. For example, if the TX UE transmits the PSCCH/PSSCH to the RX UE by designating/setting the SL HARQ feedback request field to “disabled”, the TX UE may not perform PUCCH transmission. For example, if the TX UE transmits the PSCCH/PSSCH to the RX UE by designating/setting the SL HARQ feedback request field to “disabled”, the TX UE may report NACK information to the base station through a PUCCH. For example, if the TX UE transmits the PSCCH/PSSCH to the RX UE by designating/setting the SL HARQ feedback request field to “disabled”, the TX UE may report pre-configured state/indicator information to the base station through a PUCCH. Based on an embodiment of the present disclosure, in the case of a pre-configured specific cast type (e.g., groupcast), a SL HARQ feedback transmission operation (of the RX UE) based on a distance between the TX UE and the RX UE may be configured. For convenience of description, the SL HARQ feedback operation based on the distance between the TX UE and the RX UE may be referred to as a distance-based HARQ feedback operation. For example, in the distance-based HARQ feedback operation, if the distance between the TX UE and the RX UE is less than or equal to a communication range requirement, (i) the RX UE which has failed to decode a PSSCH may transmit NACK information to the TX UE, and (ii) the RX UE which has succeeded in decoding a PSSCH may not transmit ACK information to the TX UE. That is, the RX UE may perform NACK only feedback. On the other hand, for example, in the distance-based HARQ feedback operation, if the distance between the TX UE and the RX UE is greater than a communication range requirement, the RX UE may not transmit HARQ feedback information to the TX UE. That is, the RX UE may not perform HARQ feedback. For example, if the distance-based HARQ feedback operation is configured/applied, the TX UE may transmit/signal location information (e.g., zone ID) of the TX UE to the RX UE through a pre-defined field (hereinafter, TXLO_FLD) included in a SCI (e.g., 2ndSCI) transmitted by the TX UE. In this case, for example, only if the RX UE fails to decode/receive a PSSCH, the RX UE may be configured to transmit NACK information to the TX UE. For convenience of description, this may be referred to as OPTION 1. On the other hand, for example, an operation in which the RX UE transmits ACK information if the RX UE succeeds in decoding/receiving a PSSCH but the RX UE transmits NACK information if the RX UE fails to decode/receive a PSSCH may be configured/applied. For convenience of description, this may be referred to as OPTION 2. For example, if the OPTION 2 is configured/applied, the TX UE may not transmit the above-described location information (e.g., zone ID) of the TX UE through TXLO_FLD included in the SCI (e.g., 2ndSCI). That is, if the OPTION 2 is configured/applied, the TX UE does not need to transmit the above-described location information (e.g., zone ID) of the TX UE through TXLO_FLD included in the SCI (e.g., 2ndSCI). For example, if the distance-based HARQ feedback operation is not configured, the TX UE may not transmit the above-described location information (e.g., zone ID) of the TX UE through TXLO_FLD included in the SCI (e.g., 2nd SCI). That is, if the distance-based HARQ feedback operation is not configured, the TX UE does not need to transmit the above-described location information (e.g., zone ID) of the TX UE through TXLO_FLD included in the SCI (e.g., 2ndSCI). Herein, for example, in order to reduce the (implementation) complexity required for the RX UE to decode the large number of SCIs (e.g., 2ndSCI, 1stSCI) having different payload sizes, if the OPTION 2 is configured/applied, the TX UE may pad TXLO_FLD with a pre-configured bit value (e.g., 0). For example, in order to reduce the (implementation) complexity required for the RX UE to decode the large number of SCIs (e.g., 2ndSCI, 1stSCI) having different payload sizes, if the OPTION 2 is configured/applied, the TX UE may repeatedly transmit (some) bits related to a specific field included in a pre-configured SCI (e.g., 2ndSCI) (through TXLO_FLD). In this case, for example, the payload size of the SCI (e.g., 2ndSCI) may be the same between the OPTION 1 and the OPTION 2. For example, the payload size of the SCI (e.g., 2ndSCI) may be the same between a case for which the SL HARQ feedback transmission operation according to the distance between the TX UE and the RX UE (i.e., distance-based HARQ feedback operation) is enabled and a case for which the distance-based HARQ feedback operation is disabled. For example, the TX UE may be configured to omit TXLO_FLD. For example, the payload sizes of the SCIs (e.g., 2ndSCI) may be different between the OPTION 1 and the OPTION 2. For example, the payload sizes of the SCIs (e.g., 2ndSCI) may be different between a case for which the SL HARQ feedback transmission operation according to the distance between the TX UE and the RX UE (i.e., distance-based HARQ feedback operation) is enabled and a case for which the distance-based HARQ feedback operation is disabled. For example, SCI formats may be defined differently based on the OPTION 1 and the OPTION 2. For example, SCI formats may be defined differently based on whether the SL HARQ feedback transmission operation according to the distance between the TX UE and the RX UE is enabled or disabled. FIG.16shows a procedure for a RX UE to perform a HARQ feedback operation based on a different SCI format, based on an embodiment of the present disclosure. The embodiment ofFIG.16may be combined with various embodiments of the present disclosure. Referring toFIG.16, in step S1610, the TX UE may transmit a first SCI to the RX UE through a PSCCH. In step S1620, the TX UE may transmit a second SCI to the RX UE through a PSSCH. Additionally, the TX UE may transmit a MAC PDU to the RX UE through the PSSCH. For example, the MAC PDU may be a MAC PDU for which HARQ feedback is enabled. For example, a format of the second SCI may be (i) SCI format 2-A not including location information of the TX UE or (ii) SCI format 2-B including location information of the TX UE. For example, the SCI format 2-A may be defined as below. SCI format 2-A is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes ACK or NACK, when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. The following information is transmitted by means of the SCI format 2-A:HARQ process number—4 bitsNew data indicator—1 bitRedundancy version—2 bitsSource ID—8 bitsDestination ID—16 bitsHARQ feedback enabled/disabled indicator—1 bitCast type indicator—2 bits as defined in Table 6CSI request—1 bit TABLE 6Value of Casttype indicatorCast type00Broadcast01Groupcastwhen HARQ-ACK informationincludes ACK or NACK10Unicast11Groupcastwhen HARQ-ACK informationincludes only NACK For example, the SCI format 2-B may be defined as below. SCI format 2-B is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. The following information is transmitted by means of the SCI format 2-B:HARQ process number—4 bitsNew data indicator—1 bitRedundancy version—2 bitsSource ID—8 bitsDestination ID—16 bitsHARQ feedback enabled/disabled indicator—1 bitZone ID—12 bitsCommunication range requirement—4 bits In step S1630, the RX UE may determine whether to transmit a PSFCH to the TX UE. For example, the RX UE may determine whether to perform the distance-based HARQ feedback operation based on the format of the second SCI. For example, if the format of the second SCI is the SCI format 2-A which does not include the location information of the TX UE, the RX UE may not perform the distance-based HARQ feedback operation. In this case, for example, the distance-based HARQ feedback operation may be disabled. For example, if the format of the second SCI is the SCI format 2-B which includes the location information of the TX UE, the RX UE may perform the distance-based HARQ feedback operation. In this case, for example, the distance-based HARQ feedback operation may be enabled. Based on an embodiment of the present disclosure, in order to reduce a resource collision probability (between different UEs) for TB-related initial transmission, the TX UE may transmit a pre-reservation signal (e.g., including a PSCCH and/or a PSSCH) (before initial transmission). For example, the pre-reservation signal may include information related to initial transmission and/or information related to retransmission following the pre-reservation signal. For example, the information related to initial transmission and/or the information related to retransmission following the pre-reservation signal may include location information and/or priority information related to resource(s) reserved/selected by the TX UE. For example, the resource may include a time resource and/or a frequency resource. For example, the priority information may be priority information of a packet/message associated with resource(s) reserved/selected by the TX UE. For example, the TX UE may be configured to pad pre-configured bits (e.g., 0) and/or following TB-related (some) bits on the remaining RE(s) except for the 2ndSCI in PSSCH resources related to the (corresponding) pre-reservation (hereinafter referred to as ALT 1). For example, the TX UE may pad pre-configured bits (e.g., 0) and/or following TB-related (some) bits on the remaining RE(s) except for the 2ndSCI in PSSCH resources related to the (corresponding) pre-reservation, and may transmit it to the RX UE. For example, the TX UE may be configured to transmit (repeatedly) the 2ndSCI (by rate-matching) on the remaining RE(s) except for the 2ndSCI in PSSCH resources related to the (corresponding) pre-reservation (hereinafter referred to as ALT 2). For example, the TX UE may transmit (repeatedly) the 2ndSCI (by rate-matching) to the TX UE on the remaining RE(s) except for the 2ndSCI in PSSCH resources related to the (corresponding) pre-reservation. Herein, for example, in this case, the transmission of the pre-reservation signal may be counted as the pre-configured maximum number of retransmissions related to the TB. For example, in particular in the case of ALT 2, the transmission of the pre-reservation signal may be counted as the pre-configured maximum number of retransmissions related to the TB. Alternatively, the transmission of the pre-reservation signal may not be counted as the pre-configured maximum number of retransmissions related to the TB. For example, the maximum number of retransmissions related to the TB may be configured differently or independently for the TX UE for each resource pool. For example, the maximum number of retransmissions related to the TB may be configured differently or independently for the TX UE for each congestion level. For example, the maximum number of retransmissions related to the TB may be configured differently or independently for the TX UE for each service type. For example, the maximum number of retransmissions related to the TB may be configured differently or independently for the TX UE for each service priority. For example, the maximum number of retransmissions may be the maximum number of transmissions including initial transmission and retransmission. For example, the maximum number of retransmissions may be the maximum number of transmissions including only retransmissions, excluding initial transmissions. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on whether or not the size of a packet/message to be transmitted by the TX UE exceeds a pre-configured threshold. For example, if the TX UE transmits a TB having a size greater than a threshold, transmission/use of the pre-reservation signal may be (limitedly) enabled for the TX UE. For example, if the TX UE transmits a TB having a size greater than a threshold, the TX UE may transmit the pre-reservation signal to the RX UE. For example, if the TX UE transmits a TB having a size less than or equal to a threshold, transmission/use of the pre-reservation signal may be (limitedly) disabled for the TX UE. For example, if the TX UE transmits a TB having a size less than or equal to a threshold, the TX UE may not be allowed to transmit the pre-reservation signal. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on whether or not the size of a resource for the TX UE to transmit a packet/message exceeds a pre-configured threshold, compared with the size of a resource for the TX UE to transmit the pre-reservation signal. For example, the number of subchannels for the TX UE to transmit the pre-reservation signal may be pre-configured. For example, in order for the TX UE to transmit the pre-reservation signal, one subchannel may be pre-configured. For example, compared with the size of a resource for the TX UE to transmit the pre-reservation signal, if the size of a resource for the TX UE to transmit a packet/message is greater than a pre-configured threshold, transmission/use of the pre-reservation signal may be (limitedly) enabled for the TX UE. For example, compared with the size of a resource for the TX UE to transmit the pre-reservation signal, if the size of a resource for the TX UE to transmit a packet/message is less than or equal to a pre-configured threshold, transmission/use of the pre-reservation signal may be (limitedly) disabled for the TX UE. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on the size of a subchannel. For example, the size of the subchannel may be the size of one subchannel related to a resource pool. For example, if a subchannel having the number of RBs greater than a pre-configured threshold is configured for the TX UE, transmission/use of the pre-reservation signal may be (limitedly) enabled for the TX UE. For example, if a subchannel having the number of RBs equal to or less than a pre-configured threshold is configured for the TX UE, transmission/use of the pre-reservation signal may be (limitedly) disabled for the TX UE. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on whether or not the number of subchannels related to initial transmission (and/or retransmission) following the pre-reservation signal exceeds a pre-configured threshold. For example, if the number of subchannels related to initial transmission (and/or retransmission) following the pre-reservation signal exceeds a pre-configured threshold, transmission/use of the pre-reservation signal may be (limitedly) enabled for the TX UE. For example, if the number of subchannels related to initial transmission (and/or retransmission) following the pre-reservation signal is less than or equal to a pre-configured threshold, transmission/use of the pre-reservation may be (limitedly) disabled for the TX UE. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on at least one of a SL HARQ feedback option (e.g., the OPTION 1, the OPTION 2, the blind retransmission scheme, the HARQ feedback-based retransmission scheme) (described above), a cast type, a service type, a service priority, a resource pool, a congestion level (e.g., CBR), and/or a QoS requirement (e.g., reliability, latency). For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on whether or not the size of a packet/message to be transmitted by the TX UE exceeds a pre-configured threshold. For example, if the TX UE transmits a TB having a size greater than a threshold, transmission/use of the pre-reservation signal may be (limitedly) disabled for the TX UE. For example, if the TX UE transmits a TB having a size less than or equal to a threshold, transmission/use of the pre-reservation signal may be (limitedly) enabled for the TX UE. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on whether or not the size of a resource for the TX UE to transmit a packet/message exceeds a pre-configured threshold, compared with the size of a resource for the TX UE to transmit the pre-reservation signal. For example, the number of subchannels for the TX UE to transmit the pre-reservation signal may be pre-configured. For example, in order for the TX UE to transmit the pre-reservation signal, one subchannel may be pre-configured. For example, compared with the size of a resource for the TX UE to transmit the pre-reservation signal, if the size of a resource for the TX UE to transmit a packet/message is greater than a pre-configured threshold, transmission/use of the pre-reservation signal may be (limitedly) disabled for the TX UE. For example, compared with the size of a resource for the TX UE to transmit the pre-reservation signal, if the size of a resource for the TX UE to transmit a packet/message is less than or equal to a pre-configured threshold, transmission/use of the pre-reservation signal may be (limitedly) enabled for the TX UE. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on the size of a subchannel. For example, the size of the subchannel may be the size of one subchannel related to a resource pool. For example, if a subchannel having the number of RBs greater than a pre-configured threshold is configured for the TX UE, transmission/use of the pre-reservation signal may be (limitedly) disabled for the TX UE. For example, if a subchannel having the number of RBs equal to or less than a pre-configured threshold is configured for the TX UE, transmission/use of the pre-reservation signal may be (limitedly) enabled for the TX UE. For example, whether or not the TX UE can transmit/use the pre-reservation signal may be configured differently based on whether or not the number of subchannels related to initial transmission (and/or retransmission) following the pre-reservation signal exceeds a pre-configured threshold. For example, if the number of subchannels related to initial transmission (and/or retransmission) following the pre-reservation signal exceeds a pre-configured threshold, transmission/use of the pre-reservation signal may be (limitedly) disabled for the TX UE. For example, if the number of subchannels related to initial transmission (and/or retransmission) following the pre-reservation signal is less than or equal to a pre-configured threshold, transmission/use of the pre-reservation may be (limitedly) enabled for the TX UE. Based on an embodiment of the present disclosure, the number of (maximum or minimum) resources that can be signaled by (resource) reservation/selection information included in one SCI (hereinafter, N_MAX) may be configured differently based on whether or not the size of a packet/message exceeds a pre-configured threshold. For example, in the case of a packet/message having a size greater than a threshold, the N_MAX value may be configured to a relatively large value (compared to the case otherwise). For example, the N_MAX included in one SCI may be configured differently based on a SL HARQ feedback option. For example, the SL HARQ feedback option may include the OPTION 1, the OPTION 2, the blind retransmission scheme, the HARQ feedback-based retransmission scheme, (described above) etc. For example, in the case of the blind retransmission scheme, the N_MAX value may be configured to a relatively large value (compared to other cases). For example, the N_MAX included in one SCI may be configured differently based on a cast type. For example, the N_MAX included in one SCI may be configured differently based on a service type. For example, the N_MAX included in one SCI may be configured differently based on a service priority. For example, the N_MAX included in one SCI may be configured differently based on a resource pool. For example, the N_MAX included in one SCI may be configured differently based on a congestion level (e.g., CBR). For example, the N_MAX included in one SCI may be configured differently based on a QoS requirement (e.g., reliability, latency). For example, the N_MAX included in one SCI may be configured differently based on the size of a subchannel. For example, the size of the subchannel may be the size of one subchannel related to the resource pool. Based on an embodiment of the present disclosure, the TX UE may transmit the pre-reservation signal by using a frequency resource of a specific size. For example, the pre-reservation signal may be transmitted to one or more RX UEs. For example, the pre-reservation signal may be transmitted in the form of PSCCH and PSSCH. For example, the pre-reservation signal may be transmitted in the form of PSCCH and/or PSSCH. For example, the pre-reservation signal may be transmitted in the form shown inFIG.17. FIG.17shows a pre-reservation signal based on an embodiment of the present disclosure. The embodiment ofFIG.17may be combined with various embodiments of the present disclosure. Referring toFIG.17, the TX UE may transmit a pre-reservation signal by using one slot and one subchannel. For example, transmitting the pre-reservation signal by the TX UE may include transmitting dummy information by the TX UE on the remaining resources except for resources on which the 2ndSCI is transmitted among PSSCH resources. For example, the TX UE may rate-match dummy information of a pre-configured (bit) value on the remaining resources except for the resources on which the 2ndSCI is transmitted among the PSSCH resources, and may transmit it. For example, the frequency resource of the specific size may be a single sub-channel. For example, the frequency resource and/or the size of the frequency resource through which the pre-reservation signal is transmitted may be pre-configured for the TX UE. For example, the base station may transmit, to the TX UE, information related to the frequency resource through which the pre-reservation signal is transmitted and/or information related to the size of the frequency resource through which the pre-reservation signal is transmitted. For example, if the TX UE transmits the pre-reservation signal on the frequency resource of the specific size, the TX UE may transmit/signal information related to a time gap between the location/time of a subsequent initial transmission-related reservation resource and the location/time of a resource related to a PSCCH, through the PSCCH (e.g., 1stSCI). For example, the subsequent initial transmission-related reservation resource may be an initial transmission-related reservation resource for the TX UE to perform (actual) transmission. For example, if the TX UE transmits the pre-reservation signal on the frequency resource of the specific size, the TX UE may transmit/signal information related to a time gap between the location/time of a subsequent initial transmission and/or retransmission-related reservation resource and the location/time of a resource related to a PSCCH, through the PSCCH (e.g., 1stSCI). For example, the initial transmission-related reservation resource and/or the retransmission-related reservation resource may be resource(s) for actual TB transmission. Herein, for example, based on a value of information related to the (corresponding) time gap included in the PSCCH (e.g., 1stSCI) transmitted by the TX UE, the RX UE may distinguish or determine whether the single subchannel transmission (described above) is transmission related to the pre-reservation signal or transmission related to general TB transmission. For example, if the TX UE transmits a PSCCH and/or a PSSCH to the RX UE, the RX UE may distinguish or determine whether transmission of the PSCCH and/or the PSSCH is transmission related to the pre-reservation signal or transmission related to general TB transmission, based on information related to the time gap included in the PSCCH (e.g., 1stSCI). For example, if the TX UE sets the time gap to a pre-configured specific value and transmits it to the RX UE, the RX UE may consider or determine PSCCH and/or PSSCH transmission by the TX UE as general TB transmission. For example, if the TX UE sets the time gap to zero and transmits it to the RX UE, the RX UE may consider or determine PSCCH and/or PSSCH transmission by the TX UE as general TB transmission. For example, if the TX UE sets the time gap to a value other than the pre-configured specific value and transmits it to the RX UE, the RX UE may consider or determine PSCCH and/or PSSCH transmission by the TX UE as transmission of the pre-reservation signal. For example, if the TX UE sets the time gap to a value other than zero and transmits it to the RX UE, the RX UE may consider or determine PSCCH and/or PSSCH transmission by the TX UE as transmission of the pre-reservation signal. Herein, for example, based on the above-described embodiment, the number of resources related to transmission of the pre-reservation signal may be excluded from the maximum number of transmission resources that the TX UE can signal/reserve through a SCI. For example, if the TX UE transmits dummy information (of a pre-configured bit value) (by rate-matching) on the remaining resources except for resources on which the 2ndSCI is transmitted among PSSCH resources related to transmission of the pre-reservation signal, the number of resources related to transmission of the pre-reservation signal may be excluded from the maximum number of transmission resources that the TX UE can signal/reserve through the SCI. For example, the transmission resource may include a resource related to initial transmission and/or resource(s) related to retransmission. For example, the number of transmission resources that the TX UE can signal/reserve through the SCI may include only the number of resources that the TX UE uses for actual TB transmission. For example, if transmission of the pre-reservation signal is configured for the TX UE, the TX UE may transmit information related to a time gap through a PSCCH related to transmission of the pre-reservation signal. For example, if transmission of the pre-reservation signal is not configured for the TX UE, information/field related to a time gap may not exist in a PSCCH (e.g., 1stSCI) transmitted by the TX UE. For example, if transmission of the pre-reservation signal is configured specifically for a resource pool for the TX UE, the TX UE may transmit information related to a time gap through a PSCCH related to transmission of the pre-reservation signal on a specific resource pool. For example, if transmission of the pre-reservation signal is configured specifically for a service type for the TX UE, the TX UE desiring to transmit a specific type of a service may transmit information related to a time gap through a PSCCH related to transmission of the pre-reservation signal. For example, if the transmission of the pre-reservation signal is configured specifically for a service priority for the TX UE, the TX UE desiring to transmit a service of a specific priority may transmit information related to a time gap through a PSCCH related to transmission of the pre-reservation signal. For example, if transmission of the pre-reservation signal is configured specifically for a QoS requirement for the TX UE, the TX UE desiring to transmit a service having a specific QoS requirement may transmit information related to a time gap through a PSCCH related to transmission of the pre-reservation signal. For example, due to a processing time necessary/required for the RX UE to decode the pre-reservation signal (hereinafter, PRC_TIME), the RX UE may not (actually) use some values among (candidate) values indicatable by information related to a time gap transmitted through a PSCCH related to transmission of the pre-reservation signal. For example, the RX UE may not use a time gap value smaller than the PRC_TIME. For example, the RX UE may not use a time gap value smaller than the PRC_TIME other than zero. Taking this into account, for example, the size of information related to the time gap may be reduced. For example, the size of the field related to the time gap may be reduced. For example, the TX UE may select or determine a resource related to transmission of the pre-reservation signal and a resource related to subsequent initial transmission in consideration of the PRC_TIME (described above). For example, the resource related to the subsequent initial transmission may be a resource related to initial transmission for the TX UE to transmit a (actual) TB. For example, the TX UE may select or determine a resource related to transmission of the pre-reservation signal, a resource related to subsequent initial transmission, and a resource related to subsequent retransmission in consideration of the PRC_TIME (described above). For example, the resource related to the subsequent retransmission may be a resource related to retransmission for the TX UE to transmit a (actual) TB. For example, the TX UE may preferentially select or determine a resource related to initial transmission and/or a resource related to retransmission (within a selection window) based on sensing, and the TX UE may select or determine a resource related to transmission of the pre-reservation signal from among selectable candidate resources before the PRC_TIME from the selected resource related to the initial transmission. For example, the resource related to the initial transmission may be a resource related to initial transmission for the TX UE to transmit a (actual) TB. For example, the TX UE may preferentially select or determine a resource related to initial transmission and/or a resource related to retransmission (within a selection window) based on sensing, and the TX UE may select or determine a resource related to transmission of the pre-reservation signal from among selectable candidate resources before a pre-configured value from the selected resource related to the initial transmission. For example, the pre-configured value may be a value greater than the PRC_TIME. For example, the pre-configured value may be a value less than the PRC_TIME. For example, the TX UE may preferentially select or determine a resource related to initial transmission and/or a resource related to retransmission (within a selection window) based on sensing, and the TX UE may select or determine a resource related to transmission of the pre-reservation signal from among (selectable) candidate resources on the (remaining) selection window before the PRC_TIME from the selected resource related to the initial transmission. For example, the resource related to the initial transmission may be a resource related to initial transmission for the TX UE to transmit a (actual) TB. For example, the TX UE may preferentially select or determine a resource related to initial transmission and/or a resource related to retransmission (within a selection window) based on sensing, and the TX UE may select or determine a resource related to transmission of the pre-reservation signal from among (selectable) candidate resources on the (remaining) selection window before a pre-configured value from the selected resource related to the initial transmission. For example, the pre-configured value may be a value greater than the PRC_TIME. For example, the pre-configured value may be a value less than the PRC_TIME. For example, the selection window size used by the TX UE to select or determine a resource related to transmission of the pre-reservation signal may be configured (independently) for the TX UE. For example, the maximum selection window size used by the TX UE to select or determine a resource related to transmission of the pre-reservation signal may be configured (independently) for the TX UE. For example, the minimum selection window size used by the TX UE to select or determine a resource related to transmission of the pre-reservation signal may be configured (independently) for the TX UE. Herein, for example, the TX UE may select a resource related to transmission of the pre-reservation signal within the selection window determined according to the above-described embodiment. For example, if a resource related to transmission of the pre-reservation signal does not exist within the selection window, the TX UE may not transmit the pre-reservation signal. For example, if a resource related to transmission of the pre-reservation signal does not exist within the selection window, transmission of the pre-reservation signal may be disabled for the TX UE. For example, although the TX UE performs a PSSCH DMRS RSRP threshold increase operation based on a pre-configured offset value by the maximum allowed number, if the TX UE cannot secure/select a resource related to transmission of the pre-reservation signal within the selection window, the TX UE may not transmit the pre-reservation signal. For example, the maximum allowed number may be pre-configured for the TX UE. For example, the pre-configured offset value may be 3 [dB]. FIG.18shows a method for a first device to report SL HARQ feedback information to a base station, based on an embodiment of the present disclosure. The embodiment of FIG.18may be combined with various embodiments of the present disclosure. Referring toFIG.18, in step S1810, the first device may transmit SL HARQ feedback information to the base station through a first resource. For example, the first resource may be a PUCCH resource. For example, if the number of retransmissions related to first sidelink information performed by the first device reaches the MAX_RETXNUM, and if the first device determines that the first sidelink information is not successfully transmitted, the first device may report ACK information or pre-configured state/indicator information to the base station through the first resource. For example, based on various embodiments of the present disclosure, the first device may transmit SL HARQ feedback information to the base station through the first resource. For example, if the first device transmits SL HARQ feedback information to the base station through the first resource, at least one of identifier information of a SL HARQ process associated with the SL HARQ feedback information, an index of a mode 1 CG associated with the SL HARQ feedback information, TB information associated with the SL HARQ feedback information, information on the number of retransmissions related to a SL HARQ process associated with the SL HARQ feedback information, information on the number of retransmissions related to a TB associated with the SL HARQ feedback information, information on the number of remaining retransmissions related to a SL HARQ process associated with the SL HARQ feedback information, and/or information on the remaining number of retransmissions related to a TB associated with the SL HARQ feedback information may be transmitted to the base station through the first resource. FIG.19shows a method for a base station to receive SL HARQ feedback information from a first device, based on an embodiment of the present disclosure. The embodiment ofFIG.19may be combined with various embodiments of the present disclosure. Referring toFIG.19, in step S1910, the base station may receive SL HARQ feedback information from the first device through a first resource. For example, the first resource may be a PUCCH resource. For example, if the number of retransmissions related to first sidelink information performed by the first device reaches the MAX_RETXNUM, and if the first device determines that the first sidelink information is not successfully transmitted, the base station may receive ACK information or pre-configured state/indicator information from the first device through the first resource. For example, based on various embodiments of the present disclosure, the base station may receive SL HARQ feedback information from the first device through the first resource. For example, if the base station receives the SL HARQ feedback information from the first device through the first resource, at least one of identifier information of a SL HARQ process associated with the SL HARQ feedback information, an index of a mode 1 CG associated with the SL HARQ feedback information, TB information associated with the SL HARQ feedback information, information on the number of retransmissions related to a SL HARQ process associated with the SL HARQ feedback information, information on the number of retransmissions related to a TB associated with the SL HARQ feedback information, information on the number of remaining retransmissions related to a SL HARQ process associated with the SL HARQ feedback information, and/or information on the remaining number of retransmissions related to a TB associated with the SL HARQ feedback information may be received from the first device through the first resource. FIG.20shows a method for a first device to perform wireless communication, based on an embodiment of the present disclosure. The embodiment ofFIG.20may be combined with various embodiments of the present disclosure. Referring toFIG.20, in step S2010, the first device may receive, from a second device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH). In step S2020, the first device may receive, from the second device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH. In step S2030, the first device may determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH. In step S2040, the first device may determine whether or not to transmit hybrid automatic repeat request (HARQ) feedback information for the PSSCH to the second device on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. For example, based on the format of the second SCI being the second format which includes the location information of the second device, the HARQ feedback information may include only NACK. For example, based on successful decoding of a transport block (TB) on the PSSCH by the first device, the HARQ feedback information may not be transmitted to the second device, and based on a failure of the first device to decode the TB on the PSSCH, the HARQ feedback information including the NACK may be transmitted to the second device. Additionally, for example, the first device may obtain a distance between the first device and the second device, based on the location information of the second device and location information of the first device. For example, the distance between the first device and the second device may be smaller than or equal to a communication range requirement. For example, information related to the communication range requirement may be included in the second SCI, and the format of the second SCI including the information related to the communication range requirement may be the second format. For example, based on the format of the second SCI being the first format which does not include the location information of the second device, the HARQ feedback information may include the ACK or the NACK. For example, based on successful decoding of a transport block (TB) on the PSSCH by the first device, the HARQ feedback information including the ACK may be transmitted to the second device, and based on a failure of the first device to decode the TB on the PSSCH, the HARQ feedback information including the NACK may be transmitted to the second device. For example, based on successful decoding of a transport block (TB) on the PSSCH by the first device, the HARQ feedback information may not be transmitted to the second device, and based on a failure of the first device to decode the TB on the PSSCH, the HARQ feedback information including the NACK may be transmitted to the second device. Additionally, for example, the first device may determine whether or not to perform a distance-based HARQ feedback operation, based on the format of the second SCI. For example, based on the format of the second SCI being the second format including the location information of the second device, the first device may determine to perform the distance-based HARQ feedback operation. For example, based on successful decoding of a transport block (TB) on the PSSCH by the first device, the HARQ feedback information may not be transmitted to the second device, and based on a failure of the first device to decode the TB on the PSSCH and a distance between the first device and the second device being smaller than or equal to a communication range requirement, the HARQ feedback information including the NACK may be transmitted to the second device. For example, based on the format of the second SCI being the first format which does not include the location information of the second device, the first device may determine not to perform the distance-based HARQ feedback operation. For example, the location information of the second device may include an ID of a zone to which the second device belongs. The proposed method can be applied to the device(s) described in the various embodiments of the present disclosure. First, the processor102of the first device100may control the transceiver106to receive, from a second device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH). In addition, the processor102of the first device100may control the transceiver106to receive, from the second device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH. In addition, the processor102of the first device100may determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH. In addition, the processor102of the first device100may determine whether or not to transmit hybrid automatic repeat request (HARQ) feedback information for the PSSCH to the second device on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. Based on an embodiment of the present disclosure, a first device configured to perform wireless communication may be provided. For example, the first device may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: receive, from a second device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH; determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH; and determine whether or not to transmit hybrid automatic repeat request (HARQ) feedback information for the PSSCH to the second device on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. Based on an embodiment of the present disclosure, an apparatus configured to control a first user equipment (UE) performing wireless communication may be provided. For example, the apparatus may comprise: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: receive, from a second UE, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH); receive, from the second UE, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH; determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH; and determine whether or not to transmit hybrid automatic repeat request (HARQ) feedback information for the PSSCH to the second UE on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. Based on an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. For example, the instructions, when executed, may cause a first device to: receive, from a second device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH); receive, from the second device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH; determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH; and determine whether or not to transmit hybrid automatic repeat request (HARQ) feedback information for the PSSCH to the second device on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. FIG.21shows a method for a second device to perform wireless communication, based on an embodiment of the present disclosure. The embodiment ofFIG.21may be combined with various embodiments of the present disclosure. Referring toFIG.21, in step S2110, the second device may transmit, to a first device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH). In step S2120, the second device may transmit, to the first device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH. In step S2130, the second device may determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH. In step S2140, the second device may receive, from the first device, hybrid automatic repeat request (HARQ) feedback information for the PSSCH on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. The proposed method can be applied to the device(s) described in the various embodiments of the present disclosure. First, the processor202of the second device200may control the transceiver206to transmit, to a first device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH). In addition, the processor202of the second device200may control the transceiver206to transmit, to the first device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH. In addition, the processor202of the second device200may determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH. In addition, the processor202of the second device200may control the transceiver206to receive, from the first device, hybrid automatic repeat request (HARQ) feedback information for the PSSCH on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. Based on an embodiment of the present disclosure, a second device configured to perform wireless communication may be provided. For example, the second device may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: transmit, to a first device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH); transmit, to the first device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH; determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH; and receive, from the first device, hybrid automatic repeat request (HARQ) feedback information for the PSSCH on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. Based on an embodiment of the present disclosure, an apparatus configured to control a second user equipment (UE) performing wireless communication may be provided. For example, the apparatus may comprise: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: transmit, to a first UE, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH); transmit, to the first UE, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH; determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH; and receive, from the first UE, hybrid automatic repeat request (HARQ) feedback information for the PSSCH on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. Based on an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. For example, the instructions, when executed, may cause a second device to: transmit, to a first device, a first sidelink control information (SCI) through a physical sidelink control channel (PSCCH); transmit, to the first device, a second SCI through a physical sidelink shared channel (PSSCH) related to the PSCCH; determine a physical sidelink feedback channel (PSFCH) resource, based on an index of a slot and an index of a subchannel related to the PSSCH; and receive, from the first device, hybrid automatic repeat request (HARQ) feedback information for the PSSCH on the PSFCH resource. For example, a format of the second SCI may be a first format which does not include location information of the second device or a second format which includes location information of the second device. For example, based on the format of the second SCI, the HARQ feedback information may include ACK or NACK, or may include only NACK. FIG.22shows a method for a first device to perform wireless communication, based on an embodiment of the present disclosure. The embodiment ofFIG.22may be combined with various embodiments of the present disclosure. Referring toFIG.22, in step S2210, the first device may receive, from a base station, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource. In step S2220, the first device may transmit, to a second device, a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled, based on the SL resource. In step S2230, the first device may generate ACK information related to transmission of the MAC PDU, based on the MAC PDU for which the HARQ feedback is disabled and retransmission of the MAC PDU not being required. In step S2240, the first device may transmit, to the base station, the ACK information based on the PUCCH resource. Additionally, for example, the first device may receive, from the base station, information related to a maximum number of transmissions. For example, based on a number of transmissions of the MAC PDU which reaches the maximum number of transmissions, the retransmission of the MAC PDU may not be required. For example, based on a number of SL resources allocated by the base station being greater than the maximum number of transmissions, among the SL resources, a resource after the transmission of the ACK information may be released by the base station. For example, based on blind retransmission of the MAC PDU being performed, the HARQ feedback may be disabled for the MAC PDU. For example, a retransmission resource for the MAC PDU may not be allocated for the first device by the base station based on the ACK information. For example, information related to a number of transmissions of the MAC PDU may be transmitted to the base station based on the PUCCH resource with the ACK information. Additionally, for example, the first device may generate NACK information related to the transmission of the MAC PDU, based on the MAC PDU for which the HARQ feedback is disabled and the retransmission of the MAC PDU being required and no SL grant available for the retransmission of the MAC PDU, and the first device may transmit, to the base station, the NACK information based on the PUCCH resource. For example, a retransmission resource for the MAC PDU may be allocated to the first device by the base station based on the NACK information. Additionally, for example, the first device may transmit, to the second device, a sidelink control information (SCI) including HARQ feedback disabled information representing disable of the HARQ feedback for the MAC PDU. For example, based on the HARQ feedback disabled information, the HARQ feedback for the MAC PDU may not be transmitted by the second device. Additionally, for example, the first device may measure a congestion level for a resource pool, and based on the congestion level being greater than a threshold, the HARQ feedback disabled information may be transmitted through the SCI. For example, based on a priority of the MAC PDU being lower than a pre-configured priority, the HARQ feedback disabled information may be transmitted through the SCI. The proposed method can be applied to the device(s) described in the various embodiments of the present disclosure. First, the processor102of the first device100may control the transceiver106to receive, from a base station, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource. In addition, the processor102of the first device100may control the transceiver106to transmit, to a second device, a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled, based on the SL resource. In addition, the processor102of the first device100may generate ACK information related to transmission of the MAC PDU, based on the MAC PDU for which the HARQ feedback is disabled and retransmission of the MAC PDU not being required. In addition, the processor102of the first device100may control the transceiver106to transmit, to the base station, the ACK information based on the PUCCH resource. Based on an embodiment of the present disclosure, a second device configured to perform wireless communication may be provided. For example, the second device may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: receive, from a base station, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource; transmit, to a second device, a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled, based on the SL resource; generate ACK information related to transmission of the MAC PDU, based on the MAC PDU for which the HARQ feedback is disabled and retransmission of the MAC PDU not being required; and transmit, to the base station, the ACK information based on the PUCCH resource. Based on an embodiment of the present disclosure, an apparatus configured to control a second user equipment (UE) performing wireless communication may be provided. For example, the apparatus may comprise: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: receive, from a base station, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource; transmit, to a second UE, a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled, based on the SL resource; generate ACK information related to transmission of the MAC PDU, based on the MAC PDU for which the HARQ feedback is disabled and retransmission of the MAC PDU not being required; and transmit, to the base station, the ACK information based on the PUCCH resource. Based on an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. For example, the instructions, when executed, may cause a second device to: receive, from a base station, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource; transmit, to a second device, a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled, based on the SL resource; generate ACK information related to transmission of the MAC PDU, based on the MAC PDU for which the HARQ feedback is disabled and retransmission of the MAC PDU not being required; and transmit, to the base station, the ACK information based on the PUCCH resource. FIG.23shows a method for a base station to perform wireless communication, based on an embodiment of the present disclosure. The embodiment ofFIG.23may be combined with various embodiments of the present disclosure. Referring toFIG.23, in step S2310, the base station may transmit, to a first device, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource. In step S2320, the base station may receive, from the first device, ACK information on the PUCCH resource, based on a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled being transmitted by the first device based on the SL resource, and based on retransmission of the MAC PDU not being required. The proposed method can be applied to the device(s) described in the various embodiments of the present disclosure. First, the processor202of the base station200may control the transceiver206to transmit, to a first device, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource. In addition, the processor202of the base station200may control the transceiver206to receive, from the first device, ACK information on the PUCCH resource, based on a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled being transmitted by the first device based on the SL resource, and based on retransmission of the MAC PDU not being required. Based on an embodiment of the present disclosure, a base station configured to perform wireless communication may be provided. For example, the base station may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: transmit, to a first device, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource; and receive, from the first device, ACK information on the PUCCH resource, based on a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled being transmitted by the first device based on the SL resource, and based on retransmission of the MAC PDU not being required. Based on an embodiment of the present disclosure, an apparatus configured to control a base station performing wireless communication may be provided. For example, the apparatus may comprise: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: transmit, to a first user equipment (UE), information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource; and receive, from the first UE, ACK information on the PUCCH resource, based on a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled being transmitted by the first UE based on the SL resource, and based on retransmission of the MAC PDU not being required. Based on an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing instructions may be provided. For example, the instructions, when executed, may cause a base station to: transmit, to a first device, information related to a sidelink (SL) resource and information related to a physical uplink control channel (PUCCH) resource; and receive, from the first device, ACK information on the PUCCH resource, based on a medium access control (MAC) packet data unit (PDU) for which hybrid automatic repeat request (HARQ) feedback is disabled being transmitted by the first device based on the SL resource, and based on retransmission of the MAC PDU not being required. Various embodiments of the present disclosure may be combined with each other. Hereinafter, device(s) to which various embodiments of the present disclosure can be applied will be described. The various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure described in this document may be applied to, without being limited to, a variety of fields requiring wireless communication/connection (e.g., 5G) between devices. Hereinafter, a description will be given in more detail with reference to the drawings. In the following drawings/description, the same reference symbols may denote the same or corresponding hardware blocks, software blocks, or functional blocks unless described otherwise. FIG.24shows a communication system1, based on an embodiment of the present disclosure. Referring toFIG.24, a communication system1to which various embodiments of the present disclosure are applied includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot100a, vehicles100b-1and100b-2, an eXtended Reality (XR) device100c, a hand-held device100d, a home appliance100e, an Internet of Things (IoT) device100f, and an Artificial Intelligence (AI) device/server400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. For example, the BSs and the network may be implemented as wireless devices and a specific wireless device200amay operate as a BS/network node with respect to other wireless devices. Here, wireless communication technology implemented in wireless devices100ato100fof the present disclosure may include Narrowband Internet of Things for low-power communication in addition to LTE, NR, and 6G. In this case, for example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented as standards such as LTE Cat NB1, and/or LTE Cat NB2, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices100ato100fof the present disclosure may perform communication based on LTE-M technology. In this case, as an example, the LTE-M technology may be an example of the LPWAN and may be called by various names including enhanced Machine Type Communication (eMTC), and the like. For example, the LTE-M technology may be implemented as at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-Bandwidth Limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices100ato100fof the present disclosure may include at least one of Bluetooth, Low Power Wide Area Network (LPWAN), and ZigBee considering the low-power communication, and is not limited to the name described above. As an example, the ZigBee technology may generate personal area networks (PAN) related to small/low-power digital communication based on various standards including IEEE 802.15.4, and the like, and may be called by various names. The wireless devices100ato100fmay be connected to the network300via the BSs200. An AI technology may be applied to the wireless devices100ato100fand the wireless devices100ato100fmay be connected to the AI server400via the network300. The network300may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices100ato100fmay communicate with each other through the BSs200/network300, the wireless devices100ato100fmay perform direct communication (e.g., sidelink communication) with each other without passing through the BS s/network. For example, the vehicles100b-1and100b-2may perform direct communication (e.g. Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices100ato100f. Wireless communication/connections150a,150b, or150cmay be established between the wireless devices100ato100f/BS200, or BS200/BS200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication150a, sidelink communication150b(or, D2D communication), or inter BS communication (e.g., relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections150aand150b. For example, the wireless communication/connections150aand150bmay transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure. FIG.25shows wireless devices, based on an embodiment of the present disclosure. Referring toFIG.25, a first wireless device100and a second wireless device200may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, {the first wireless device100and the second wireless device200} may correspond to {the wireless device100xand the BS200} and/or {the wireless device100xand the wireless device100x} ofFIG.24. The first wireless device100may include one or more processors102and one or more memories104and additionally further include one or more transceivers106and/or one or more antennas108. The processor(s)102may control the memory(s)104and/or the transceiver(s)106and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s)102may process information within the memory(s)104to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s)106. The processor(s)102may receive radio signals including second information/signals through the transceiver106and then store information obtained by processing the second information/signals in the memory(s)104. The memory(s)104may be connected to the processor(s)102and may store a variety of information related to operations of the processor(s)102. For example, the memory(s)104may store software code including commands for performing a part or the entirety of processes controlled by the processor(s)102or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s)102and the memory(s)104may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)106may be connected to the processor(s)102and transmit and/or receive radio signals through one or more antennas108. Each of the transceiver(s)106may include a transmitter and/or a receiver. The transceiver(s)106may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip. The second wireless device200may include one or more processors202and one or more memories204and additionally further include one or more transceivers206and/or one or more antennas208. The processor(s)202may control the memory(s)204and/or the transceiver(s)206and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s)202may process information within the memory(s)204to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s)206. The processor(s)202may receive radio signals including fourth information/signals through the transceiver(s)106and then store information obtained by processing the fourth information/signals in the memory(s)204. The memory(s)204may be connected to the processor(s)202and may store a variety of information related to operations of the processor(s)202. For example, the memory(s)204may store software code including commands for performing a part or the entirety of processes controlled by the processor(s)202or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s)202and the memory(s)204may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)206may be connected to the processor(s)202and transmit and/or receive radio signals through one or more antennas208. Each of the transceiver(s)206may include a transmitter and/or a receiver. The transceiver(s)206may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip. Hereinafter, hardware elements of the wireless devices100and200will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors102and202. For example, the one or more processors102and202may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors102and202may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers106and206. The one or more processors102and202may receive the signals (e.g., baseband signals) from the one or more transceivers106and206and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors102and202may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors102and202or stored in the one or more memories104and204so as to be driven by the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands. The one or more memories104and204may be connected to the one or more processors102and202and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories104and204may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories104and204may be located at the interior and/or exterior of the one or more processors102and202. The one or more memories104and204may be connected to the one or more processors102and202through various technologies such as wired or wireless connection. The one or more transceivers106and206may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers106and206may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers106and206may be connected to the one or more processors102and202and transmit and receive radio signals. For example, the one or more processors102and202may perform control so that the one or more transceivers106and206may transmit user data, control information, or radio signals to one or more other devices. The one or more processors102and202may perform control so that the one or more transceivers106and206may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers106and206may be connected to the one or more antennas108and208and the one or more transceivers106and206may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas108and208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers106and206may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors102and202. The one or more transceivers106and206may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors102and202from the base band signals into the RF band signals. To this end, the one or more transceivers106and206may include (analog) oscillators and/or filters. FIG.26shows a signal process circuit for a transmission signal, based on an embodiment of the present disclosure. Referring toFIG.26, a signal processing circuit1000may include scramblers1010, modulators1020, a layer mapper1030, a precoder1040, resource mappers1050, and signal generators1060. An operation/function ofFIG.26may be performed, without being limited to, the processors102and202and/or the transceivers106and206ofFIG.25. Hardware elements ofFIG.26may be implemented by the processors102and202and/or the transceivers106and206ofFIG.25. For example, blocks1010to1060may be implemented by the processors102and202ofFIG.25. Alternatively, the blocks1010to1050may be implemented by the processors102and202ofFIG.25and the block1060may be implemented by the transceivers106and206ofFIG.25. Codewords may be converted into radio signals via the signal processing circuit1000ofFIG.26. Herein, the codewords are encoded bit sequences of information blocks. The information blocks may include transport blocks (e.g., a UL-SCH transport block, a DL-SCH transport block). The radio signals may be transmitted through various physical channels (e.g., a PUSCH and a PDSCH). Specifically, the codewords may be converted into scrambled bit sequences by the scramblers1010. Scramble sequences used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of a wireless device. The scrambled bit sequences may be modulated to modulation symbol sequences by the modulators1020. A modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complex modulation symbol sequences may be mapped to one or more transport layers by the layer mapper1030. Modulation symbols of each transport layer may be mapped (precoded) to corresponding antenna port(s) by the precoder1040. Outputs z of the precoder1040may be obtained by multiplying outputs y of the layer mapper1030by an N*M precoding matrix W. Herein, N is the number of antenna ports and M is the number of transport layers. The precoder1040may perform precoding after performing transform precoding (e.g., DFT) for complex modulation symbols. Alternatively, the precoder1040may perform precoding without performing transform precoding. The resource mappers1050may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generators1060may generate radio signals from the mapped modulation symbols and the generated radio signals may be transmitted to other devices through each antenna. For this purpose, the signal generators1060may include Inverse Fast Fourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters, Digital-to-Analog Converters (DACs), and frequency up-converters. Signal processing procedures for a signal received in the wireless device may be configured in a reverse manner of the signal processing procedures1010to1060ofFIG.26. For example, the wireless devices (e.g.,100and200ofFIG.25) may receive radio signals from the exterior through the antenna ports/transceivers. The received radio signals may be converted into baseband signals through signal restorers. To this end, the signal restorers may include frequency downlink converters, Analog-to-Digital Converters (ADCs), CP remover, and Fast Fourier Transform (FFT) modules. Next, the baseband signals may be restored to codewords through a resource demapping procedure, a postcoding procedure, a demodulation processor, and a descrambling procedure. The codewords may be restored to original information blocks through decoding. Therefore, a signal processing circuit (not illustrated) for a reception signal may include signal restorers, resource demappers, a postcoder, demodulators, descramblers, and decoders. FIG.27shows another example of a wireless device, based on an embodiment of the present disclosure. The wireless device may be implemented in various forms according to a use-case/service (refer toFIG.24). Referring toFIG.27, wireless devices100and200may correspond to the wireless devices100and200ofFIG.25and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices100and200may include a communication unit110, a control unit120, a memory unit130, and additional components140. The communication unit may include a communication circuit112and transceiver(s)114. For example, the communication circuit112may include the one or more processors102and202and/or the one or more memories104and204ofFIG.25. For example, the transceiver(s)114may include the one or more transceivers106and206and/or the one or more antennas108and208ofFIG.25. The control unit120is electrically connected to the communication unit110, the memory130, and the additional components140and controls overall operation of the wireless devices. For example, the control unit120may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit130. The control unit120may transmit the information stored in the memory unit130to the exterior (e.g., other communication devices) via the communication unit110through a wireless/wired interface or store, in the memory unit130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit110. The additional components140may be variously configured according to types of wireless devices. For example, the additional components140may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100aofFIG.24), the vehicles (100b-1and100b-2ofFIG.24), the XR device (100cofFIG.24), the hand-held device (100dofFIG.24), the home appliance (100eofFIG.24), the IoT device (100fofFIG.24), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a fintech device (or a finance device), a security device, a climate/environment device, the AI server/device (400ofFIG.24), the BSs (200ofFIG.24), a network node, etc. The wireless device may be used in a mobile or fixed place according to a use-example/service. InFIG.27, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices100and200may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit110. For example, in each of the wireless devices100and200, the control unit120and the communication unit110may be connected by wire and the control unit120and first units (e.g.,130and140) may be wirelessly connected through the communication unit110. Each element, component, unit/portion, and/or module within the wireless devices100and200may further include one or more elements. For example, the control unit120may be configured by a set of one or more processors. As an example, the control unit120may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory130may be configured by a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof. Hereinafter, an example of implementingFIG.27will be described in detail with reference to the drawings. FIG.28shows a hand-held device, based on an embodiment of the present disclosure. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), or a portable computer (e.g., a notebook). The hand-held device may be referred to as a mobile station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). Referring toFIG.28, a hand-held device100may include an antenna unit108, a communication unit110, a control unit120, a memory unit130, a power supply unit140a, an interface unit140b, and an I/O unit140c. The antenna unit108may be configured as a part of the communication unit110. Blocks110to130/140ato140ccorrespond to the blocks110to130/140ofFIG.27, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit120may perform various operations by controlling constituent elements of the hand-held device100. The control unit120may include an Application Processor (AP). The memory unit130may store data/parameters/programs/code/commands needed to drive the hand-held device100. The memory unit130may store input/output data/information. The power supply unit140amay supply power to the hand-held device100and include a wired/wireless charging circuit, a battery, etc. The interface unit140bmay support connection of the hand-held device100to other external devices. The interface unit140bmay include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit140cmay input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit140cmay include a camera, a microphone, a user input unit, a display unit140d, a speaker, and/or a haptic module. As an example, in the case of data communication, the I/O unit140cmay acquire information/signals (e.g., touch, text, voice, images, or video) input by a user and the acquired information/signals may be stored in the memory unit130. The communication unit110may convert the information/signals stored in the memory into radio signals and transmit the converted radio signals to other wireless devices directly or to a BS. The communication unit110may receive radio signals from other wireless devices or the BS and then restore the received radio signals into original information/signals. The restored information/signals may be stored in the memory unit130and may be output as various types (e.g., text, voice, images, video, or haptic) through the I/O unit140c. FIG.29shows a vehicle or an autonomous vehicle, based on an embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aerial Vehicle (AV), a ship, etc. Referring toFIG.29, a vehicle or autonomous vehicle100may include an antenna unit108, a communication unit110, a control unit120, a driving unit140a, a power supply unit140b, a sensor unit140c, and an autonomous driving unit140d. The antenna unit108may be configured as a part of the communication unit110. The blocks110/130/140ato140dcorrespond to the blocks110/130/140ofFIG.27, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit120may perform various operations by controlling elements of the vehicle or the autonomous vehicle100. The control unit120may include an Electronic Control Unit (ECU). The driving unit140amay cause the vehicle or the autonomous vehicle100to drive on a road. The driving unit140amay include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit140bmay supply power to the vehicle or the autonomous vehicle100and include a wired/wireless charging circuit, a battery, etc. The sensor unit140cmay acquire a vehicle state, ambient environment information, user information, etc. The sensor unit140cmay include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit140dmay implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like. For example, the communication unit110may receive map data, traffic information data, etc. from an external server. The autonomous driving unit140dmay generate an autonomous driving path and a driving plan from the obtained data. The control unit120may control the driving unit140asuch that the vehicle or the autonomous vehicle100may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit110may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit140cmay obtain a vehicle state and/or surrounding environment information. The autonomous driving unit140dmay update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit110may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous vehicles and provide the predicted traffic information data to the vehicles or the autonomous vehicles. Claims in the present description can be combined in a various way. For instance, technical features in method claims of the present description can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. | 181,556 |
11943747 | DETAILED DESCRIPTION Preferred embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals shown in different drawings are used to designate the same or similar components. For clarity and conciseness, a detailed description of the known functions and structures contained herein will be omitted to avoid obscuring the subject matter of the present disclosure. In order to make the objects, technical solutions and advantages of the present disclosure more clear, the present disclosure will be described in detail with reference to the accompanying drawings. In V2X communication, the participating UEs can be classified into a variety of types, such as vehicles (VUEs), pedestrians (PUEs), and roadside units (RSUs). It is assumed that the data transmission mechanism of a UE is as follows. First, the UE transmits a control channel (hereinafter referred to as scheduling assignment signaling (SA)) for indicating the coding modulation scheme (MCS) and the time-frequency resource occupied by the data channel. The UE transmits data on the scheduled data channel thereafter. For LTE D2D/V2X systems, the SA is also called PSCCH, and the data channel is also called PSSCH. For a device, since its data is generated periodically over a period of time, the device can reserve resources periodically according to a specific reservation interval; and, each data may be transmitted repeatedly K times, accordingly it requires to reserve K resources, where K is greater than or equal to 1, so as to avoid the case that a part of the devices cannot receive the data due to the half-duplex operation order to increase the transmission rate of the UE and enhance the transmission performance, the UE may select resources and transmit data on a plurality of carriers. In step301, scheduling assignment signaling SA of another UE is detected within a sensing window of each of a plurality of carriers, a received power of a scheduled data channel is measured based on the SA, and a received energy of each subchannel of each sub-frame is detected. In step302, a resource for data transmission is selected on the plurality of carriers based on the detected SA, the received power, and the received energy. The resource selection on a plurality of carriers may be performed independently or may be operated jointly to better coordinate the data transmission over multiple carriers. In addition, depending on the measurement of the congestion control, a portion of the resources selected on the plurality of carriers may be discarded, i.e., not used to transmit data, thereby reducing system interference levels. In step303, the selected resource is used for data transmission. For example, the UE may set the SA and the transmission power of a corresponding data channel, transmit the SA to indicate the selected resource, and transmits data over the resource. The transmission power of a data channel corresponding to the SA on the different carriers may be set independently or may be jointly set to better coordinate the data transmission over multiple carriers. In the following, the resource selection process and the data transmission on a plurality of carriers according to the present disclosure will be described in detail in accordance with the following specific embodiments provided by the present disclosure. First Embodiment Assuming that the UE can perform data transmission on N carriers, and the N carriers may be perfectly equal to each other. When the UE has relatively small traffic, the UE may choose to use a carrier or a portion of the carrier at the same probability. Alternatively, it is assumed that the UE can perform data transmission on N carriers, and the UE uses the N carriers for data transmission in a specific priority order. When the UE has relatively small traffic, the UE may preferentially use a specific carrier. For example, the carrier is similar to the primary carrier of the LTE CA system. When the traffic of the UE is increased, the UE can add other carriers that can be used in a certain order. The order of adding carriers may be pre-defined, configured by higher level signaling or pre-configured. For example, the UE may preferentially use a carrier with a smaller carrier index according to indexes of the carriers and add additional carriers for data transmission in the order of increasing the index when the traffic increases. When the UE can perform data transmission on N carriers, in the case that the UE performs resource selection on one sub-frame, the UE may select resources only on M carriers, M being less than or equal to N, and it is necessary to determine the transmission parameters of each carrier. For example, the transmission parameter may be a reservation interval on a specific carrier, a modulation scheme, a number of occupied consecutive subchannels, a number of transmissions, and a traffic priority. The transmission parameters on the M carriers may be the same or different. A first multi-carrier resource selection method is as follows. The UE first determines a resource selection scheme, i.e., selecting M carriers out of the N carriers and further determining the transmission parameters of the i-th carrier, for example, including a number niof occupied continuous subchannels and a traffic priority, i=0, 1, M−1. The traffic priorities of the M carriers may be the same or different. Next, the UE selects channel resources based on the transmission parameters of the respective carriers according to the detection results on the M carriers. For example, selecting a number niof continuous subchannel on the i-th carrier. The selection of the M carriers and the transmission parameters of each carrier may be determined according to some other conditions, such as the amount of traffic currently required to be transmitted and the congestion level of each carrier, etc. Assuming that the UE needs to transmit traffic having multiple priorities, the UE may determine the priority parameters for resource selection of a carrier according to the priority of the traffic to be transmitted on the carrier. The present disclosure does not limit the specific determination method, and the metric of the congestion level may be a channel busy proportion (CBR). The resource selection of the UE on the M carriers may be performed independently or may be jointly operated to better coordinate the data transmission over multiple carriers. In particular, assuming that M is constantly equal to N, the UE only needs to determine the transmission parameters for each carrier of the N carriers. Since the relative positions between UEs in one region change and the position change is relatively fast when the vehicle speed is relatively high, and the traffic on each carrier also change, the UE may not be able to accurately determine the M carriers that are currently suitable for transmission and the transmission parameters of each carrier, for example, including a number of occupied consecutive subchannels and the traffic priority. As shown inFIG.4, a second multi-carrier resource selection method may be as follows. The UE may first determine a resource selection scheme (401), and then select the resource (402) using the first multi-carrier resource selection method. The UE may also determine whether the resources selected on the M carriers and the corresponding transmission parameters are suitable for data transmission (403). If the selected resource is not suitable for transmission, the UE may adjust the resource selection scheme, i.e., adjust carriers selected on the N carriers and the corresponding transmission parameters, and trigger the resource selection again. The method for determining whether the selected resource is suitable for transmission may include using at least one of the following parameters: 1) whether the PSSCH-RSRP threshold is increased when it is determined whether or not the resource is available based on the PSSCH-RSRP of the data channel scheduled by the received SA and/or the times of increasing the PSSCH-RSRP threshold; 2) the ratio of the number of remaining resources to the total number of resources when it is determined whether the resource is available based on the PSSCH-RSRP of the data channel scheduled by the received SA; 3) the maximum or average value of the S-RSSI of the resources reserved according to the average received energy (S-RSSI) of each subchannel; 4) S-RSSI of the selected resources; 5) the number of selected resources, which number is less than or equal to K. The present disclosure does not limit the specific method of determining whether the selected resource is suitable for transmission. As shown inFIG.5, a third multi-carrier resource selection method is as follows. The UE first determines a number P of resource selection schemes (501), where P is greater than or equal to 1, and each scheme includes a plurality of selected carriers and transmission parameters of each selected carrier. Then the UE performs resource selection (502) based on the selected carriers and its transmission parameters of each scheme, respectively, according to the detection results on the respective carriers. Then the UE compares the schemes and selects suitable one (503). Comparing the number P of resource selection schemes includes using at least one of the following parameters: 1) whether the PSSCH-RSRP threshold is increased when it is determined whether or not the resource is available based on the PSSCH-RSRP of the data channel scheduled by the received SA and/or the times of increasing the PSSCH-RSRP threshold; 2) the ratio of the number of remaining resources to the total number of resources when it is determined whether the resource is available based on the PSSCH-RSRP of the data channel scheduled by the received SA; 3) the maximum or average value of the S-RSSI of the resources reserved according to the average received energy (S-RSSI) of each subchannel; 4) S-RSSI of the selected resources; 5) the number of selected resources, which number is less than or equal to K. The present disclosure does not limit the specific method of comparing the number P of resource selection schemes. It is assumed that the p-th scheme includes a number Mpof carriers to be selected and transmission parameters of the i-th selected carrier, for example, including the number ni,pof occupied consecutive subchannels, traffic priority, etc., i=0, 1, Mp−1. The traffic priorities of the Mpcarriers may be the same or different. The number P of candidate resource selection schemes, the selected Mpcarriers of each scheme, and the transmission parameters on each carrier can be determined according to some other criteria, for example, the traffic required to be transmitted and the congestion level of each carrier. The present disclosure does not limit the specific determination method. For each resource selection scheme, the resource selection on the Mpcarriers may be performed independently or may be operated jointly to better coordinate the data transmission over multiple carriers. In particular, assuming that M is constantly equal to N, the same carrier is used for the P resource selection schemes, but the transmission parameters of the respective carriers may not be exactly the same. Second Embodiment When the UE performs detection in the sensing window of a plurality of carriers, selects channel resources and conducts data transmission, a limiting factor is a half-duplex operation. Specifically, when the UE conducts transmission on a sub-frame of a carrier, the UE cannot perform a reception operation on the sub-frame of the carrier, and the UE cannot perform a reception operation on the sub-frame of an adjacent carrier. As shown inFIG.6, it is assumed that the UE transmits data by using two adjacent carriers, i.e., data is transmitted on sub-frames601and603of carrier1, and data is transmitted on sub-frames612and614of carrier2. Due to the half-duplex limitation, the UE cannot perform the detection on sub-frames602and604of carrier1and on sub-frames611and613of carrier2. Since the UE cannot perform the detection on the sub-frames602,604,611, and613, sub-frames within the selection window corresponding to these sub-frames cannot be used for data transmission of the UE, thereby reducing the number of resources available for selection within the selection window. This increases the collision probability between UEs to a certain extent. In order to avoid the half-duplex problem as shown inFIG.6, when it performs a resource selection on a plurality of carriers, the resources selected for the respective carriers may be located within the same sub-frame. When data is transmitted a plurality of times (including initial transmission and retransmission), the resources for the initial transmission and retransmission on the plurality of carriers are located within the same sub-frame, respectively. It is assumed that the plurality of carriers allocate resource pools for data transmission, respectively. If the sets of sub-frames from the resource pools of the plurality of carriers are identical, the resources may be selected from all sub-frames of the resource pool. Alternatively, if the sets of sub-frame from the resource pools of the plurality of carrier are not identical, resources may be only selected from the intersection of the sets of sub-frames of the resource pools of the plurality of carriers so that the resources selected on the plurality of carriers are located in the same sub-frames. It is assumed that the sets of sub-frames of the resources that can be selected on the plurality of carriers are denoted by B. The UE performs detection on a plurality of carriers, including receiving the SA and measuring the received power of the data channel scheduled by the correctly received SA, and measuring the received energy of each subchannel. Next, the UE may conduct the resource selection based on the detection of the resources on the sub-frame within the set B. As shown inFIG.7, the UE first determines M carriers to be selected and the transmission parameters of each carrier (701). For example, if the method of the first embodiment is used, the M carriers and the transmission parameters of each carrier are obtained for a resource selection scheme. It is assumed that the number of subchannels of the resource to be selected on the i-th carrier is ni, the priority is ri, i=0, 1, M−1, and M is the number of carriers on which the UE performs data transmission. A combined resource may include M resources and correspond to the M carriers. The resource corresponding to the i-th carrier contains a number niof consecutive subchannels. If the number of resources composed of niconsecutive subchannels contained in one sub-frame of the i-th carrier is Ni, the total number of resources in the combined resource in one sub-frame is ∏i=0NCC-1Ni, in which Π0represents the multiplication operation. Assuming that the total number of sub-frames within the set B is NB, the total number of resources in the combined resource in the set B is NB·∏i=0NCC-1Ni. The UE may then conduct the resource selection by detecting SA of another device on each earlier and the PSSCH-RSRP of the data channel scheduled by the SA (702). For the i-th carrier, assuming that a resource contains niconsecutive subchannels and the priority is ri, it is possible to exclude the unavailable resources for each carrier independently according to the detection of SA of the other device. For example, based on step202of the resource selection method ofFIG.2, it is assumed that the UE detects the SA of the other device and resource Y is scheduled or reserved by the SA, and Rx,yrepresents a resource of a single sub-frame in the selection window and is located in the sub-frame y, and contains one or more consecutive subchannels starting from the subchannel x. When Rx,y+j·PAoverlaps the resource Y and the received power of the resource scheduled by the SA exceeds the PSSCH-RSRP threshold, where j is a non-negative integer, Rx,yis unavailable to device A. According to the method, for the i-th carrier, when the ratio of the remaining available resources is lower than the threshold the threshold may be increased and the process of excluding resources is executed repeatedly until the ratio of the remaining available resources is no lower than Ri. For example, the PSSCH-RSRP threshold is increased by a step of 3 dB based on the resource selection method ofFIG.2. The threshold Rimay be a fixed value, for example, 20%, or the threshold Rimay be configured for each carrier, respectively, or the threshold Rimay be determined for each carrier based on the amount of traffic to be transmitted currently and the load of each carrier, respectively. According to the method, for a sub-frame in the set B, there is no available combined resource within this sub-frame if there is no available resource on at least one carrier. Alternatively, for the set B, it is also possible to directly determine whether the combined resource is available. For example, on a carrier, it is assumed that the UE detects SA of the other device and resource Y is scheduled or reserved by the SA, and Ryrepresents a combined resource of a single sub-frame in the selection window and is located in the sub-frame y. When Ry+j·PAoverlaps the resource Y and the received power of the resource scheduled by the SA exceeds the PSSCH-RSRP threshold, j being a non-negative integer, Ryis unavailable to device A According to the method, the PSSCH-RSRP threshold on each carrier can be increased at the same time when the ratio of the remaining available combined resources is below the threshold R, and the process of excluding resources is executed repeatedly until the ratio of the remaining available resources is no lower than the threshold R. For example, the PSSCH-RSRP threshold is increased by a step of 3 dB based on the resource selection method ofFIG.2. The threshold R may be a fixed value, for example, 20%, or the threshold R may be configured by the higher layer signaling, or the threshold R may be determined based on the amount of traffic to be transmitted currently and the load of each carrier. Next, the UE may conduct the resource selection according to the received energy (S-RSSI) of each subchannel on each carrier (703). For the combined resource, the combined S-RSSI corresponding to the combined resource may be calculated from the S-RSSI corresponding to the resources on each carrier. For example, the S-RSSI of the resources on each carrier may be weighted according to the number niof subchannels of the resources on each carrier, i.e., the combined S-RSSI is equal to ∏i=0NCC-1(ni·SRSSIi)/∏i=0NCC-1(ni). The present disclosure does not limit the method of obtaining a combined S-RSSI. For the remaining combined resources of the set B after step702, the combined resource with the smallest combined S-RSSI is moved to the set SBuntil the ratio of the combined resources of SBis R2. The threshold R2may be a fixed value, for example, 20%, or the threshold R2may be configured by the higher layer signaling, or the threshold R2may be determined based on the amount of traffic to be transmitted currently and the load of each carrier. The threshold R2may be the same as or different from the threshold R selected in conducting the resource selection based on the SA and the received power. Finally, the UE randomly selects the combined resource for data transmission in the combined resource of the set SB(704). In the method of performing a resource selection on M carriers shown inFIG.7, before the resource selection is performed, the UE determines whether the resource of the M carrier that is currently selected shall be kept or shall be re-selected according to a specific probability p. The UE may generate a count value C and the resources selected by the UE on each carrier are reserved for C cycles consecutively. Third Embodiment When transmitting data over N carriers, the following solution can also be used to increase the flexibility of the resource allocation and reduce collisions and interference between UEs. When it is necessary to select a plurality of carriers in the same sub-frame, the configuration flexibility of the set of sub-frames of the resource pools of the respective carriers may be limited. When two UEs collide with each other on a sub-frame of one carrier, the probability of collision on other carriers is high since the two UEs occupy the same sub-frame on other carriers. In order to improve the flexibility of resource allocation and resource selection and take into account the effects of collision, interference and half-duplex operation, another method of selecting resources on a plurality of carriers is described below. The UE performs detection on a plurality of carriers, including receiving the SA and measuring the received power of the data channel scheduled by the correctly received SA, and measuring the received energy of each subchannel. Next, the UE may exclude the unavailable resources for each carrier according to the detection result. The resources selected on each carrier may be determined independently; alternatively, when selecting a resource, it may preferentially select resources located in the same sub-frame for the plurality of carriers. As shown inFIG.8, the UE first determines M carriers to be selected and the transmission parameters of each carrier (801), where M is greater than or equal to one. For example, if the method of the first embodiment is used, the M carrier and the transmission parameters of each carrier are obtained for a resource selection scheme. Alternatively, the UE may perform the resource selection only on a portion of the carriers, and the selected and reserved resources on the other portion of the carriers are still in use. In such a case, the M carriers belong to the portion of the carriers from which the resource is to be selected currently. The number of subchannels of the resource to be selected on the i-th carrier is ni, the priority is ri, i=0, 1, M−1, and M is the number of carriers on which the UE performs the resource selection. The UE may then detect the SA of the other device on each carrier, measure the PSSCH-RSRP of the data channel scheduled by the SA, and perform resource selection on each carrier, respectively (802). For example, according to step202of the resource selection method ofFIG.2, for the i-th carrier, assuming that a resource contains niconsecutive subchannels and the priority is ri, it is possible to exclude the unavailable resources according to the SA and PSSCH-RSRP of the other device. According to the method, for the i-th carrier, when the ratio of the remaining available resources is lower than the threshold Ri, the PSSCH-RSRP threshold may be increased and the process of excluding resources is executed repeatedly until the ratio of the remaining available resources is no lower than Ri. For example, the PSSCH-RSRP threshold is increased by a step of 3 dB based on the resource selection method ofFIG.2. The threshold Rimay be a fixed value, for example, 20%, or the threshold Rimay be configured for each carrier, respectively, or the threshold Rimay be determined for each carrier based on the amount of traffic to be transmitted currently and the load of each carrier, respectively. Next, the UE may perform the resource selection for each carrier according to the received energy (S-RSSI) of each subchannel on each carrier (803). For example, according to step205of the resource selection method ofFIG.2, for the i-th carrier, assuming that a resource contains niconsecutive subchannels, the resource with the smallest S-RSSI in accordance with the S-RSSI of respective remaining resources after step802is moved to the set SB,iuntil the ratio of resources of SB,iis R′i. The threshold R′imay be a fixed value, for example, 20%, or the threshold R′imay be determined for each carrier based on the amount of traffic to be transmitted currently and the load of each carrier, respectively. The threshold R′imay be the same as or different from the threshold value Riselected in conducting the resource selection based on the SA and the received power. Finally, the UE selects the resource for data transmission on the M carriers based on the set SB,iof the M carriers (804). The resources may be selected independently from the set SB,ifor the i-th carrier. Alternatively, the UE may jointly select resources for data transmission on the M carriers in step804. For example, factors such as the half-duplex problem shown inFIG.6may be taken into account in resource selection. When a resource is selected for the i-th carrier, it may preferentially select resources located in the same sub-frame for a plurality of carriers. Alternatively, when a resource is selected for the i-th carrier, it may preferentially select resources located in the same sub-frame for a plurality of carriers at a specific probability. For example, the UE generates a random number r evenly distributed between [0, 1]. If r is less than or equal to the threshold P, the UE preferentially selects resources located in the same sub-frame for a plurality of carriers; otherwise, it select resources independently for each carrier. The threshold P may be pre-defined, configured by higher layer signaling, or determined dynamically by the UE. For example, the UE determines the threshold P according to the congestion state and the traffic type of the M carriers. In particular, except for the M carriers, assuming that the resource selected and reserved by the UE on a portion of the carriers is still in use, the UE may preferentially select or preferentially select a resource that is located in the same sub-frame as that of other carriers of the resource in use at a specific probability. Alternatively, when selecting a resource, it may be such that the number of sub-frames occupied by the resource selected by the UE on the M carriers does not exceed a certain threshold in the selection window. Alternatively, when selecting a resource, it may be such that the number of sub-frames occupied by the resource selected by the UE does not exceed a certain threshold in the selection window on a plurality of carriers including the M carriers and the carriers on which the resource in use is located. Alternatively, when selecting a resource, it may be such that the number of sub-frames occupied by the resource selected by the UE on the N carriers does not exceed a certain threshold in the selection window. The selection window may refer to a selection window on each carrier, or may be a superset of selection windows of the M carriers. The threshold may be pre-defined, configured by higher level signaling, or determined dynamically by the UE. For example, the UE determines the threshold based on the congestion state and traffic type of the M carriers. In some special cases, the UE may fail to select resources that satisfy the threshold on the set SB,iof M carriers. In this case, the threshold may be adjusted to relax the restriction on resource selection. Or the UE may not be limited by the threshold. That is, the resource is selected from the set SB,iindependently for each carrier. In step804, for the M carriers, the UE may successively select resources for each carrier in a specific order. The UE may prioritize the primary carrier to other carriers; or the UE may process the respective carriers in the order in which the carrier index increases; or the UE may preferentially process a carrier with a higher priority according to the priorities of traffic on the respective carriers, so as to ensure the transmission of traffic with a high priority. If the UE does not have resources that have been selected and reserved on any carrier, for a specific carrier, for example, the carrier with the smallest index, the carrier with the highest traffic priority, or the primary carrier (assuming that the index of the carrier is x), the UE may randomly select K resources from the set SB,x, and K is the number of times the data needs to be transmitted. For a carrier on which no resource is selected, assume that the index of the carrier is y. Corresponding to the sub-frame occupied by the resource selected on the carrier on which the resource has been selected, if there is available resources in the set SB,y, the UE preferentially selects such a resource for the carrier y; or the UE preferentially selects such a resource for the carrier y at a specific probability; or it may be such that the number of sub-frames occupied by the resource selected by the UE on the M carriers does not exceed a certain threshold in the selection window; or, it may be such that the number of sub-frames occupied by the resource selected by the UE, does not exceed a certain threshold in the selection window on a plurality of carriers including the M carriers and the carriers on which the resource in use is located; or it may be such that the number of sub-frames occupied by the resource selected by the UE on the N carriers does not exceed a certain threshold in the selection window. The plurality of resources selected on one carrier is within the sub-frame range on which the same data are transmitted as indicated by the SA, and satisfy the traffic latency requirements. Alternatively, the UE may first exclude resources of a portion of sub-frames based on the set SB,iof M carriers in selecting resources in step804. For a sub-frame that is excluded, it satisfies xs≤x if resources belonging to the set SB,iare present in xscarriers. The threshold x may be pre-defined, configured by higher level signaling, or determined dynamically by the UE. For example, the UE may determine the threshold based on the congestion state and the traffic type of the carriers. For example, x is equal to 1. When it is to exclude the resource of sub-frames, the UE may preferentially exclude the sub-frames with a smaller xs. When there are multiple sub-frames with the same xsand only a portion of the multiple sub-frames is to be excluded, the UE may randomly exclude a portion of the sub-frames. In addition, the number or ratio of sub-frames and/or resources excluded by the UE does not exceed a certain threshold y. This avoids the reduction in the randomness of the resources finally selected by the UE due to the exclusion of too many sub-frame resources. The threshold y may be the maximum number of sub-frames that can be excluded; or the threshold y may be the maximum ratio of the number of sub-frames that can be excluded to the total number of sub-frames within the selection window; or the threshold y may be the maximum ratio of the number of sub-frames that can be excluded to the total number of sub-frames on which carries in the set SB,iare located; or the threshold y may be the maximum number of resources in sub-frames that can be excluded, or the threshold y may be the maximum ratio of the number of resources in the sub-frames that can be excluded to the total number of resources in the selection window; or the threshold y may be the maximum ratio of the number of resources in sub-frames that can be excluded to the total number of resources in the set SB,i. The threshold y may be pre-defined, configured by higher level signaling, or dynamically determined by the UE. After excluding a portion of the sub-frames, resources are selected independently from the remaining resources of the set SB,ion the i-th carrier. Here, the number of carriers that can be transmitted simultaneously by the UE within a sub-frame may be limited due to the limitation of the UE transmission capability or the maximum transmission power limit. Therefore, it is possible to introduce a parameter xmaxso that the number of carriers that can be transmitted simultaneously by the UE in one sub-frame is less than or equal to xmax. xmaxmay be pre-defined, configured by higher level signaling, or dynamically determined by the UE. For example, the UE determines the threshold xmaxbased on the congestion state and traffic type of the M carriers. For example, xmaxis less than or equal to the number of simultaneous transmitted carriers supported by the UE. For example, if the UE has selected resource(s) on the xmaxcarriers within a sub-frame, when selecting resources for the i-th carrier from the remaining resources of the set SB,i, the UE excludes the resources located in the sub-frame from the remaining resources of the set SB,i, and then selects the resource. In some special cases, if there is not enough candidate resources for one or more carriers in the remaining resources of the set SB,iof the M carriers, the UE may relax the restriction of the factors on the resource selection. For example, the UE may relax the restriction on the resource selection by reducing the number of sub-frames to be excluded, or the UE may select resource independently from the set SB,ifor each carrier without having to satisfy the constraint of the factors. In the method of performing a resource selection on M carriers shown inFIG.8, before the resource selection is performed, the UE determines whether the resource of the M carriers that is currently selected shall be kept or shall be re-selected according to a specific probability p; alternatively, before the resource selection is performed, the UE determines whether the resource that is currently selected shall be kept or shall be re-selected according to a specific probability pifor the i-th carrier. The parameters p and pimay be pre-defined, configured by higher level signaling, or determined dynamically by the UE. For example, the UE determines p and piaccording to the congestion state and traffic type of the M carriers. In the method of performing a resource selection on M carriers shown inFIG.8, if it re-selects resources of a plurality of carriers, the UE may generate a count value C and the resources selected by the UE on each carrier are reserved for C cycles consecutively; alternatively, the UE may generate a count value C for the i-th carrier, and the resources selected by the UE on the carrier are reserved for Cicycles consecutively. The parameters C and Cimay be pre-defined, configured by higher level signaling, or determined dynamically by the UE. For example, the UE determines C and Ciaccording to the congestion state and traffic type of the M carriers. According to the method, the same probability p and the parameter C are applied to the M carriers so that the resource selection of the M carriers is always completed at the same time, which is advantageous for avoiding or reducing the half-duplex problem ofFIG.6. For example, if carrier A and carrier B perform resource selection at different times, and UE selects the resource located in sub-frame a on carrier A and performs data transmission, the UE cannot detect resources located in sub-frame a on carrier B due to the half-duplex limitation. When it is necessary to perform resource selection at the carrier B, the sub-frame corresponding to the sub-frame a in the selection window of the carrier B is not available. This causes the resource selected on carrier B to be different from the resource selected on carrier A, which deteriorates the half-duplex problem. After the UE selects the resource for data transmission on the M carriers based on the set of the M carriers in step804, the data transmission on the selected resource for the M carriers may cause the UE to fail to detect sufficient resources, and thus cannot effectively perform the next resource selection. In this case, the UE may be triggered to perform step804again. For example, the UE may perform step804again when the UE cannot detect enough resources on at least one carrier. Or in general, the UE may perform step804again when the UE cannot detect enough resources on at least x carriers. x may be a predefined constant, a value configured by higher layer signaling, or a preconfigured value. x may have a value greater than or equal to 1. In some examples, a metric may be calculated in conjunction with resources that the UE cannot detect on the M carriers, and the UE performs step804again when the metric indicates that the UE cannot detect enough resources. In some special cases, for example, in the case that the data transmission of the UE at the selected resources of the M carriers may still cause the UE not able to detect enough resources even after one or more re-execution of step804, the UE may directly keep the resources selected on the M carriers, or the UE may independently select resources from the set SB,ifor each carrier. The resources that cannot be detected may be resources that cannot be detected by the UE for various reasons in the art, and will not be described here for simplicity. In some examples, for a carrier, the UE cannot detect enough resources may be the cases: when the number of sub-frames actually can be detected by the UE on a carrier is less than a certain threshold, or the ratio of the number of sub-frames actually can be detected by the UE on a carrier to the total number of sub-frames in the sensing window is less than a certain threshold, the UE may consider that it cannot detect enough resources on this carrier. Or in other examples, on a carrier, it is determined that some of the sub-frames within the UE's selection window are not available based on the sub-frames that are not detected by the UE within the sensing window. In this case, the UE cannot detect enough resources may be the cases: when the number of remaining available sub-frames in the UE's selection window (other than the unavailable sub-frame) is less than a certain threshold, or when the ratio of the number of remaining available sub-frames in the UE's selection window to the total number of sub-frames in the selection window is less than a certain threshold, the UE may consider that it cannot detect enough resources on this carrier. Fourth Embodiment For a UE supporting transmission of data over N carriers, the number NTof carriers supporting simultaneous transmission is generally less than or equal to the number NRof carriers supporting simultaneous reception. The number of carriers that the UE actually uses to transmit data can exceed NT. The UE can only transmit data on up to NTcarriers in a sub-frame at the same time, but the UE can transmit data on different carriers in different sub-frames. That is, after the UE completes transmission on a carrier within a sub-frame, it is possible to switch the transmission device to another carrier and transmit data on the carrier. it takes a switching time for the UE to switch carriers. During the period of the switching time, the UE cannot transmit data; further, the UE may not be able to receive data at some or all of the period of the switching time. The parameter NTmay be a UE specific parameter, i.e., each TX chain of the UE can be used for each frequency supported by the UE; or, the parameter NTmay be a parameter related to a band or a band combination. That is, a TX chain of the UE is only used for a portion of the band or the band combination supported by the UE. The carrier switching time may be a UE specific parameter, or a parameter related to a band or a band combination. For example, assuming that NTis a UE specific parameter and the UE transmits on the NTcarrier in sub-frame n, the UE cannot transmit until subframe n+k on a carrier other than the NTcarriers due to the carrier switching time. When the UE does not transmit within consecutive k sub-frames following the sub-frame n, the UE may transmit on the subframe n+k+1 on a carrier other than the NTcarriers. The value of k depends on the carrier switching time of the UE, for example, k is equal to 1 or 0. Since the last symbol of a sub-frame is not used for transmission, when the carrier switching time is faster, for example less than 30 us, the length of one symbol is sufficient to switch between carriers, and k can be equal to 0 in such case. When the carrier switching time is relatively long, for example, up to several hundred us, the length of one symbol is not enough to complete the switch, and k can be equal to 1 in such case. In the resource selection, considering the parameter NTand the carrier switching time, it is necessary to ensure or to ensure that the selected resource satisfies the parameter NTand the carrier switching time as much as possible. When the UE transmits data on multiple carriers, the total transmission power in one sub-frame cannot exceed the maximum transmission power of the UE. Accordingly, when the UE performs a resource selection, it shall ensure that the transmission power on a plurality of carriers on which data are transmitted simultaneously in one sub-frame does not exceed the maximum transmission power. Assuming that the transmission power of the UE is related to the pathloss (PL) of the UE to the base station, the transmission power P of the UE on one carrier varies with time since PL is variable. In the resource selection, the UE may calculate the transmission power for a certain period of time in the future based on the current PL as P=ƒ(PL). The UE may also obtain a transmission power of the UE P=ƒ(PL)+Δ by adding a specific offset value to the transmission power calculated from the current PL. For example, if Δ is greater than 0, the total transmission power may not exceed the maximum transmission power when the UE increases transmission power at subsequent transmissions. When the UE makes a resource selection on a plurality of carriers, as shown inFIG.9, the UE first determines M carriers to be selected and the transmission parameters for each carrier (901), where M is greater than or equal to one. For example, if the method of the first embodiment is used, the M carriers and the transmission parameters of each carrier are obtained for a resource selection scheme. Alternatively, the UE may perform the resource selection only on a portion of the carriers, and the selected and reserved resources on the other portion of the carriers are still in use. In such a case, the M carriers belong to the portion of the carriers from which the resource is to be selected currently. The number of subchannels of the resource to be selected on the i-th carrier is ni, the priority is ri, i=0, 1, M−1, and M is the number of carriers on which the UE performs the resource selection. The UE performs detection on the plurality of carriers, including receiving the SA and measuring the received power of the data channel scheduled by the correctly received SA, and measuring the received energy of each subchannel. Next, the UE may exclude the unavailable resources for each carrier according to the detection result (902). The set of remaining resources after exclusion of the unavailable resources is denoted by SB,i. In step902, the UE may exclude unavailable resources for each carrier independently according to, for example, steps802and803of the third embodiment. Alternatively, at step902, the UE may also exclude the unavailable resources for each carrier by considering jointly the M carriers. For example, the UE may first exclude the unavailable resource based on factors such as the parameter NT, the carrier switching time, the maximum transmission power and the like; the UE may then exclude the unavailable resource for each carrier according to the detection result according to, for example, steps802and803of the third embodiment. For the M carriers, the UE may randomly determine the order in which the respective carriers are to be processed. Alternatively, the UE may successively select resources for each carrier in a specific order. The UE may prioritize the primary carrier to other carriers; or the UE may process the respective carriers in the order in which the carrier index increases; or the UE may preferentially process a carrier with a higher priority according to the priorities of traffic on the respective carriers, so as to ensure the transmission of traffic with a high priority. Considering the parameter NTand the carrier switching time, it is assumed that for a carrier, there are x1 consecutive sub-frames and other NTcarriers. The UE excludes the x1 consecutive sub-frames from the selection window of the carrier if the UE has selected a resource on at least one of the x1 consecutive sub-frames on each of the other NTcarriers and there is no consecutive k idle sub-frames in the x1 consecutive sub-frames on the other NTcarriers, where k is greater than or equal to 1. The above restriction is applicable to all carriers of the UE if the parameter NTand the carrier switching time are UE specific parameter. The above restriction is applicable to all carriers belong to one band or a band combination if the parameter NTand the carrier switching time are related to the band or the band combination. Alternatively, to be general, the above restriction is applicable to one set of carriers of the UE. Alternatively, it is assumed that the UE selects a resource on at least one carrier of each of x consecutive sub-frames. It is also assumed that there are only y carriers, the UE selects a resource on at least one sub-frame of each carrier on the x consecutive sub-frames, y is less than or equal to NT. If y is equal to NT, for a carrier other than the y carriers, the UE excludes the x consecutive sub-frame from the selection window of the carrier. If there are at least k idle sub-frames after the x consecutive sub-frames and no resource in the idle sub-frames has been selected, the UE can select a resource on the carrier on a sub-frame which is after the k idle sub-frames on the carrier. The above restriction is applicable to all carriers of the UE if the parameter NTand the carrier switching time are UE specific parameter. The above restriction is applicable to all carriers belong to one band or a band combination if the parameter NTand the carrier switching time are related to the band or the band combination. Alternatively, to be general, the above restriction is applicable to one set of carriers of the UE. Considering the parameter NTand the carrier switching time, it is assumed that the NTand the carrier switching time are UE specific parameters. For a carrier, if the UE selects a resource on at least other NTcarriers of sub-frame n, the UE may exclude the sub-frame located in the range [n−k1, n+k2] in the selection window of the carrier. Alternatively, it is assumed that the parameter NTand the carrier switching time are related to a band or a band combination. For a carrier, it is assumed that the UE has selected resource in subframe n on at least other NTcarriers related to the band or the band combination to which it belongs. The UE may exclude sub-frames within the range [n−k1, n+k2] in the selection window on the carrier. Alternatively, for a carrier out of a set of carriers, based on the number NTof simultaneous transmitted carriers in the set of carriers and the carrier switching time supported by the UE, if the UE selects resources on other NTcarriers of the set of carriers in sub-frame n, the UE may exclude sub-frames within the range [n−k1, n+k2] in the selection window of the carrier. The values of k1 and k2 depend on the carrier switching time of the UE. For example, k1 and k2 are equal to 1 or 0. For example, since the last symbol of the sub-frame is not used for transmission, the length of one symbol is sufficient when the carrier switching time is faster, and k1 and/or k2 may be equal to zero. When k1 and k2 are equal to 0, the range [n−k1, n+k2] actually includes only sub-frame n. Alternatively, assuming that the parameter NTand the carrier switching time are UE specific parameters, and that for a carrier there are consecutive k+1 sub-frames and at least other NTcarriers such that the UE selects resources in at least one sub-frame of each of the at least other NTcarriers, the UE may exclude the k+1 sub-frames within the selection window of the carrier. Alternatively, assuming that the parameter NTand the carrier switching time are related to a band or a band combination, and that for a carrier there are continuous k+1 sub-frames and at least other NTcarriers in a band or a band combination such that the UE selects resources on at least one sub-frame of each of the at least other NTcarriers, the UE may exclude the k+1 sub-frames within the selection window of the carrier. Alternatively, for a carrier out of a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, it is assumed that there are consecutive k+1 sub-frames and at least other NTcarriers of the set of carriers such that the UE selects resources on at least one sub-frame of each of the at least other NTcarriers, the UE may exclude the k+1 sub-frames within the selection window of the carrier. When k is equal to 0, the consecutive k+1 sub-frames are actually one sub-frame. Alternatively, consider a case where k is greater than or equal to 1, and the parameter NTand the carrier switching time are UE specific parameters. For consecutive q sub-frames and at least other NTcarriers for a carrier, where q is a positive integer, if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers and selects resources on at least one carrier of each sub-frame that belongs to the at least other NTcarriers, the UE may exclude the resources of the q sub-frames within the selection window of the carrier. Alternatively, consider the case that the parameter NTand the carrier switching time are related to a band or a band combination. In a band or a band combination, assuming that for a carrier there are consecutive q sub-frames and at least other NTcarriers, if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers and selects resources on at least one earner of each sub-frame that belongs to the at least other NTcarriers, the UE may exclude the resources of the q sub-frames within the selection window of the carrier. Alternatively, for a carrier out of a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, if there are consecutive q sub-frames and at least other NTcarriers of the set of carriers and the UE selects resources on at least one sub-frame of each of the at least other NTcarriers and selects resources on at least one carrier of each sub-frame that belongs to the at least other NTcarriers, the UE may exclude the resources of the q sub-frames within the selection window of the carrier. Regarding the maximum transmission power, the UE may exclude the sub-frame n in the selection window of the other carriers if the transmission power on the plurality of carriers on which data are transmitted on sub-frame n has reached or exceeded the maximum transmit power. For a carrier, if a transmission on a sub-frame results in a power exceeding the maximum transmission power, resources of the sub-frame in the selection window of the carrier is excluded. The UE may consider the factors in a specific order. For example, the resource selected by the UE shall satisfy the effect of the parameter NTand the carrier switching time, which otherwise may cause the UE to discard the data on a portion of the carriers in one sub-frame. Secondly, the UE may preferentially take the maximum transmission power into account. Finally, the UE selects the resources for data transmission on the M carriers based on the available resource sets SB,iof the M carriers (903). In step903, the UE may independently select resources from the set SB,ifor each carrier. With this method, the independently selected resources on each carrier may not be able to satisfy the parameter NTand the carrier switching time, and/or the maximum transmission power, in which case the UE may be triggered to re-execute step903. For example, regarding the parameter NTand the carrier switching time, assuming that k is greater than or equal to 1 and there are x1 consecutive sub-frames and more than NTcarriers, if the UE selects resources on at least one sub-frame of each carrier, and there is no consecutive k idle sub-frames in the x1 consecutive sub-frames, i.e., there is no enough carrier switching time to support transmissions over NTcarriers, the UE may be triggered to re-execute step903. The above restriction is applicable to all carriers of the UE if the parameter NTand the carrier switching time are UE specific parameter. The above restriction is applicable to all carriers belong to one band or a band combination if the parameter NTand the carrier switching time are related to the band or the band combination. Alternatively, to be general, the above restriction is applicable to one set of carriers of the UE. Alternatively, regarding the parameter NTand the carrier switching time, it is assumed that the NTand the carrier switching time are UE specific parameters. If the UE selects a resource on at least other NTcarriers of the sub-frame n, and the UE also selects sub-frames in the range [n−k1, n+k2] on other carriers, the UE may be triggered to re-execute step903. Alternatively, it is assumed that the parameter NTand the carrier switching time are related to a band or a band combination. For a carrier, it is assumed that the UE has selected resource in subframe n on at least other NTcarriers related to the band or the band combination to which it belongs, and the UE also selects sub-frames within the range [n−k1, n+k2] on the carrier; the UE may be triggered to re-execute step903. Alternatively, for a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, if the UE selects resources on at least NTcarriers of the sub-frame n and the UE also selects sub-frames in the range [n−k1, n+k2] on other carriers, the UE may be triggered to re-execute step903. Alternatively, assuming that the parameter NTand the carrier switching time are UE specific parameters, and that there are consecutive k+1 sub-frames and more than NTcarriers such that the UE selects resources in at least one sub-frame of each carrier; the UE may be triggered to re-execute step903. Alternatively, assuming that the parameter NTand the carrier switching time are related to a band or a band combination, and that there are continuous k+1 sub-frames and more than NTcarriers in a band or a band combination such that the UE selects resources in at least one sub-frame of each carrier, the UE may be triggered to re-execute step903. Alternatively, for a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, it is assumed that there are consecutive k+1 sub-frames and more than NTcarriers such that the UE selects resources in at least one sub-frame of each carrier; the UE may be triggered to re-execute step903. Alternatively, consider a case where k is greater than or equal to 1, and the parameter NTand the carrier switching time are UE specific parameters. For consecutive q sub-frames and more than NTcarriers, where q is a positive integer, if the UE selects resources in at least one sub-frame of each carrier and selects resources in at least one carrier of each sub-frame, the UE may be triggered to re-execute step903. Alternatively, consider the case that the parameter NTand the carrier switching time are related to a band or a band combination. In a band or a band combination, for consecutive q sub-frames and more than NTcarriers, if the UE selects resources in at least one sub-frame of each carrier and selects resources on at least one carrier of each sub-frame, the UE may be triggered to re-execute step903. Alternatively, for a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, if there are consecutive q sub-frames and more than NTcarriers and the UE selects resources in at least one sub-frame of each carrier and selects resources on at least one carrier of each sub-frame, the UE may be triggered to re-execute step903. Regarding the maximum transmission power, if there is a sub-frame in which the transmission power on the plurality of carriers on which data are simultaneously transmitted exceeds the maximum transmission power, the UE may be triggered to re-execute step903. In some special cases, for example, the parameter NTand the carrier switching time and/or the maximum transmission power cannot be satisfied after one or more re-execution of step903, and the UE can directly keep the resource currently selected on the M carriers. Alternatively the UE may select resource independently from the set SB,ifor each carrier without having to satisfy the constraint of the factors. Alternatively, in step903, based on the set SB,iof M carriers, the UE may also jointly select resources for data transmission on the M carriers. For example, in step903, the UE may select resources for data transmission on the M carriers by taking one or more of the factors such as the parameter NTand the carrier switching time, the maximum transmission power, and the half-duplex problem shown inFIG.6into account. In the resource selection, considering the parameter NTand the carrier switching time, it is necessary to ensure or to ensure that the selected resource satisfies the parameter NTand the carrier switching time as much as possible. Considering the parameter NTand the carrier switching time, it is assumed that for a carrier there are x1 consecutive sub-frames and other NTcarriers. The UE cannot select the x1 consecutive sub-frames of the carrier if the UE has selected a resource one at least one of the x1 consecutive sub-frames on each of the other NTcarriers and there is no consecutive k idle sub-frames in the x1 consecutive sub-frames on the other NTcarriers, where k is greater than or equal to 1. The above restriction is applicable to all carriers of the UE if the parameter NTand the carrier switching time are UE specific parameter. The above restriction is applicable to all carriers belong to one band or a band combination if the parameter NTand the carrier switching time are related to the band or the band combination. Alternatively, to be general, the above restriction is applicable to one set of carriers of the UE. Alternatively. consider the case that k is greater than or equal to one, and for x consecutive sub-frames, the UE selects a resource on at least one carrier of each sub-frame. In the x consecutive sub-frames, there exists only y carriers, if the LYE selects a resource in at least one sub-frame of each carrier, it shall satisfy that y is less than or equal to NT. When y is equal to NT, for a carrier other than the v carriers, the UE cannot select the x consecutive sub-frame on that carrier. Also, only in the case that there are at least k idle sub-frames following the x consecutive sub-frames and no resources are selected in the idle sub-frames, the UE may select a resource on sub-frames after the k idle sub-frames on the carrier. The above restriction is applicable to all carriers of the UE if the parameter NTand the carrier switching time are UE specific parameter. The above restriction is applicable to all carriers belong to one band or a band combination if the parameter NTand the carrier switching time are related to the band or the band combination. Alternatively, to be general, the above restriction is applicable to one set of carriers of the UE. Alternatively, regarding the parameter NTand the carrier switching time, it is assumed that the NTand the carrier switching time are UE specific parameters. If for a carrier, the UE selects a resource on at least other NTcarriers of sub-frame n, the UE cannot select sub-frames in the range [n−k1, n+k2] on the carrier. Alternatively, it is assumed that the parameter NTand the carrier switching time are related to a band or a band combination. For a carrier, if the UE has selected resource in subframe n on at least other NTcarriers related to the band or the band combination to which it belongs, the UE cannot select sub-frames in the range [n−k1, n+k2] on the carrier. Alternatively, for a carrier out of a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, if the UE selects resources on at least other NTcarriers of the set of carriers of the sub-frame n, the UE cannot select sub-frames in the range [n−k1, n+k2] on the carrier. Alternatively, assuming that the parameter NTand the carrier switching time are UE specific parameters, if for a carrier there are k+1 consecutive sub-frames and at least other NTcarriers, the UE cannot select the k+1 consecutive sub-frames on the carrier if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers. Alternatively, assuming that the parameter NTand the carrier switching time are related to a band or a band combination, if for a carrier there are k+1 continuous sub-frames and at least other NTcarriers in a band or a band combination, the UE cannot select the k+1 consecutive sub-frames on the carrier if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers. Alternatively, for a carrier out of a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, if there are consecutive k+1 sub-frames and at least other NTcarriers of the set of carriers, the UE cannot select the k+1 consecutive sub-frames on the carrier if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers. Alternatively, consider a case where k is greater than or equal to 1, and the parameter NTand the carrier switching time are UE specific parameters. If for a carrier there are q consecutive sub-frames and at least other NTcarriers, the LE cannot select the q consecutive sub-frames on the carrier if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers and selects resources on at least carrier of each sub-frame that belongs to the at least other NTcarriers. Alternatively, consider the case that the parameter NTand the carrier switching time are related to a band or a band combination. In a band or a band combination, if for a carrier there are q consecutive sub-frames and at least other NTcarriers, the UE cannot select the q consecutive sub-frames on the carrier if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers and selects resources on at least carrier of each sub-frame that belongs to the at least other NTcarriers. Alternatively, for a carrier out of a set of carriers, based on the number NTof simultaneously transmitted carriers and the carrier switching time supported by the UE on the set of carriers, for consecutive q sub-frames and other NTcarriers of the set of carriers, the UE cannot select the q consecutive sub-frames on the carrier if the UE selects resources on at least one sub-frame of each of the at least other NTcarriers and selects resources on at least carrier of each sub-frame that belongs to the at least other NTcarriers. The maximum transmission power can be taken into account in resource selection. It shall ensure or ensure that the transmission power on multiple carriers on which data are transmitted simultaneously in one sub-frame does not exceed the maximum transmit power as much as possible. For a carrier, if a transmission on a sub-frame results in a power exceeding the maximum transmission power, the sub-frame of the carrier cannot be selected. The half-duplex problem shown inFIG.6can be taken into account in resource selection. The UE may preferentially selects or preferentially selects a resource that is located in the same sub-frame at a specific probability; or it may be such that the number of sub-frames occupied by the resource selected by the UE on the M carriers does not exceed a certain threshold in the selection window; or it may be such that the number of sub-frames occupied by the resource selected by the UE does not exceed a certain threshold in the selection window on a plurality of carriers including the M carriers and the carriers on which the resource in use is located; or it may be such that the number of sub-frames occupied by the resource selected by the UE on the N carriers does not exceed a certain threshold in the selection window. For example, it may deal with the half-duplex problem according to step804of the third embodiment. Alternatively, the UE may first exclude resources of a portion of sub-frames based on the set SB,iof M carriers in dealing with the half-duplex problem shown inFIG.6. For a sub-frame s that is excluded, it satisfies xs≤x if resources belonging to the set SB,iare present in xscarriers. The threshold x may be pre-defined, configured by higher level signaling, or determined dynamically by the LE. For example, the UE may determine the threshold based on the congestion state and the traffic type of the carriers. For example, x is equal to 1. When it is to exclude the resource of sub-frames, the UE may preferentially exclude the sub-frames with a smaller xs. When there are multiple sub-frames with the same xsand only a portion of the multiple sub-frames is to be excluded, the UE may randomly exclude a portion of the sub-frames. In addition, the number or ratio of sub-frames and/or resources excluded by the UE does exceed a certain threshold y. This avoids the reduction in the randomness of the resources finally selected by the UE due to the exclusion of too many sub-frame resources. The threshold y may be the maximum number of sub-frames that can be excluded; or the threshold y may be the maximum ratio of the number of sub-frames that can be excluded to the total number of sub-frames within the selection window; or the threshold y may be the maximum ratio of the number of sub-frames that can be excluded to the total number of sub-frames on which carries in the set SB,iare located; or the threshold y may be the maximum number of resources in sub-frames that can be excluded, or the threshold y may be the maximum ratio of the number of resources in sub-frames that can be excluded to the total number of resources in the selection window; or the threshold y may be the maximum ratio of the number of resources in sub-frames that can be excluded to the total number of resources in the set SB,i. The threshold y may be pre-de fined, configured by higher level signaling, or dynamically determined by the UE. After excluding a portion of the sub-frames, resources are selected independently from the remaining resources of the set SB,ion the i-th carrier. For example, it mat deal with the half-duplex problem according to step804of the third embodiment. In resource selection, it is possible to introduce a parameter xmaxso that the number of carriers that can be transmitted simultaneously by the UE in one sub-frame is less than or equal to xmax. xmaxmay be pre-defined, configured by higher level signaling, or dynamically, determined by the UE. For example, the UE determines the threshold xmaxbased on the congestion state and traffic type of the M carriers. For example, xmaxis less than or equal to the number of simultaneous transmitted carriers supported by the UE. For example, if the UE has selected a resource on the xmaxcarriers within a sub-frame, when selecting resources for the i-th carrier from the remaining resources of the set SB,i, the UE excludes the resources located in the sub-frame from the remaining resources of the set SB,i, and then selects the resource. In some special cases, based on the set SB,iof the M carriers, if there is no enough candidate resources for one or more carriers in the set SB,iof the M carriers by taking one or more of the factors such as the parameter NTand the carrier switching time, the maximum transmission power, and the half-duplex problem shown inFIG.6into account, the UE may relax the restriction of the factors on the resource selection. For example, the UE may relax the restriction on the resource selection by reducing the number of sub-frames to be excluded in dealing with the half-duplex problem, or the UE may select resource independently from the set SB,ifor each carrier without having to satisfy the constraint of the factors. The UE may consider the factors in a specific order. For example, the resource selected by the UE shall satisfy the effect of the parameter NTand the carrier switching time, which otherwise may cause the UE to discard the data on a portion of the carriers in one sub-frame. Second, the UE may preferentially take the maximum transmission power into account. The UE may only select resources on a plurality of carriers in one sub-frame if the total power of the plurality of carriers is not limited. Otherwise, if the UE preferentially selects resources on a plurality of carriers in one sub-frame, which may cause the total power of the UE within a sub-frame to exceed the maximum transmission power. For example, based on the set SB,iof M carriers, the UE may exclude unavailable resources of the SB,iof M carriers according to a specific carrier priority by taking the parameter NT, the carrier conversion time, and/or the maximum transmission power into account. Then, the UE may further exclude resources of a part of sub-frames of the set SB,iwhen the half-duplex problem shown inFIG.6is taken into account. For a sub-frame s that is excluded, it is assumed that there are resources on xscarriers that belong to the set SB,i, and xsis lower or equal to a threshold x. Finally, the UE may select resources from remaining resources of the set SB,iindependently for ithcarrier. Alternatively, based on the set SB,iof M carriers, the UE may exclude resources of a part of sub-frames of the set SB,iwhen the half-duplex problem shown inFIG.6is taken into account. For a sub-frame s that is excluded, it is assumed that there are resources on xscarriers that belong to the set SB,i, and xsis lower or equal to a threshold x. The UE then may select resources from remaining resources of the set SB,iindependently for ithcarrier. If the independently selected resources do not satisfy the parameter NTand the carrier conversion time and/or the maximum transmission power, the UE repeats the selection of resources from remaining resources of the set SB,iindependently for ithcarrier. Alternatively, the UE may repeat the selection starting from the operation of excluding resources of a part of sub-frames of the set SB,iwhere the amount of resources of a part of sub-frames of the set SB,ithat are excluded shall be changed. In particular, in addition to the M carriers, assuming that the resource selected and reserved by the UE on a portion of the carriers is still in use, the UE needs to consider other carriers that have resources in use when dealing with the factors. For the M carriers, the UE may successively select resources for each carrier in a specific order. The UE may prioritize the primary carrier to other carriers; or the UE may process the respective carriers in the other in which the carrier index increases; or the UE may preferentially process a carrier with a higher priority according to the priorities of traffic on the respective carriers, so as to ensure the transmission of traffic with a high priority. If the UE does not have resources that have been selected and reserved on any carrier, for a specific carrier, for example, the carrier with the smallest index, the carrier with the highest traffic priority, or the primary carrier (assuming that the index of the carrier is x), the UE may randomly selects K resources from the set SB,i, and K is the number of times the data needs to be transmitted. For a carrier on which no resource is selected, assume that the index of the carrier is y. Corresponding to the sub-frame occupied by the resource selected on the carrier on which the resource has been selected, the UE may select resources on carrier y by taking one or more of the factors such as the parameter NTand the carrier switching time, the maximum transmission power, and the half-duplex problem shown inFIG.6into account. Preferably, in step902, the UE may not take the factors such as the parameter NTand the carrier switching time, the maximum transmission power, and the half-duplex problem shown inFIG.6into account; and in step903, the UE may select resources for data. transmission on the M carriers by taking one or more of the factors such as the parameter NTand the carrier switching time, the maximum transmission power, and the half-duplex problem shown inFIG.6into account. Preferably, in step902, the UE may take the factors such as the parameter NTand the carrier switching time, and the maximum transmission power into account; and in step903, the resource is independently selected for each carrier, or by taking the half-duplex problem shown inFIG.6into account, for example, according to step804of the third embodiment. After step903, the data transmission on the selected resource for the M carriers may cause the UE to fail to detect sufficient resources, and thus cannot effectively perform the next resource selection. In this case, the UE may be triggered to perform step903again. For example, the UE may perform step903again when the UE cannot detect enough resources on at least one carrier. Or in general, the UE may perform step903again when the UE cannot detect enough resources on at least x carriers. x may be a predefined constant, a value configured by higher layer signaling, or a preconfigured value. x may have a value greater than or equal to 1. In some examples, a metric may be calculated in conjunction with resources that the UE cannot detect on the M carriers, and the UE performs step903again when the metric indicates that the UE cannot detect enough resources. The present disclosure does not limit the specific calculation of the metric. In some special cases, for example, in the case that the data transmission of the UE at the selected resources of the M carriers may still cause the UE not able to detect enough resources even after one or more re-execution of step903, the UE may directly keep the resources selected on the M carriers, or the UE may independently select resources from the set SB,ifor each carrier. The resources that cannot be detected may be resources that cannot be detected by the UE for various reasons in the art, and will not be described here for simplicity. In some examples, for a carrier, the UE cannot detect enough resources may be the cases: according to the resources selected on the M carriers by the UE, when the number of sub-frames actually can be detected by the UE on a carrier is less than a certain threshold, or the ratio of the number of sub-frames actually can be detected by the UE on a carrier to the total number of sub-frames in the sensing window is less than a certain threshold, the UE may consider that it cannot detect enough resources on this carrier. Or in other examples, according to the resources selected on the M carriers by the UE, on a carrier, it is determined that some of the sub-frames within the UE's selection window are not available based on the sub-frames that are not detected by the UE within the sensing window. In this case, the UE cannot detect enough resources may be the cases: when the number of remaining available sub-frames in the UE's selection window (other than the unavailable sub-frame) is less than a certain threshold, or when the ratio of the number of remaining available sub-frames in the UE's selection window to the total number of sub-frames in the selection window is less than a certain threshold, the UE may consider that it cannot detect enough resources on this carrier. In the method of performing a resource selection on M carriers shown inFIG.9, before the resource selection is performed, the UE determines whether the resource of the M carriers that is currently selected shall be kept or shall be re-selected according to a specific probability p; alternatively, before the resource selection is performed, the UE determines whether the resource that is currently selected shall be kept or shall be re-selected according to a specific probability pifor the i-th carrier. The parameters p and pimay be pre-defined, configured by higher level signaling, or determined dynamically by the UE. For example, the UE determines p and piaccording to the congestion state and traffic type of the M carriers. In the method of performing a resource selection on M carriers shown inFIG.9, if it re-selects resources of a plurality of carriers, the UE may generate a count value C and the resources selected by the UE on each carrier are reserved for C cycles consecutively; alternatively, the UE may generate a count value Cifor the i-th carrier, and the resources selected by the UE on the carrier are reserved for Cicycles consecutively. The parameters C and Cimay be pre-defined, configured by higher level signaling, or determined dynamically by the UE. For example, the UE determines C and Ciaccording to the congestion state and traffic type of the M carriers. According to the method, the same probability p and the parameter C are applied to the M carriers so that the resource selection of the M carriers is always completed at the same time, which is advantageous for avoiding or reducing the half-duplex problem ofFIG.6. Preferably, it is assumed that neither the parameter NTnor the carrier switching time is considered in steps902and903. For example, it performs resource selection independently on the K carriers, which may lead to a case that the resources selected on the M carriers cannot satisfy the parameter NTand the carrier switching time. When such case occurs, the UE has to discard data on one or more carriers. In the case, the UE may preferentially transmit data within the sub-frame that is precedent in time. Alternatively, in the case, the UE may preferentially transmit data within sub-frames with the higher priority, depending on the priorities of data of the respective sub-frames of the respective carriers. If the data transmission in a plurality of sub-frames affects each other and the data of the plurality of sub-frames have the same highest priority, the UE may randomly select one of the plurality of sub-frames and transmit data in the selected sub-frame; or the UE may transmit data in a sub-frame which has a larger number or a larger amount of data; or the UE may select such a sub-frame of the plurality of sub-frames that the number or amount of data to be discarded due to the transmission of the sub-frame is smallest; or, the UE determines a sub-frame on which data is to be transmitted by taking the number or amount of data in the sub-frame and the number or amount of data to be discarded due to the transmission of the sub-frame both into account. For example, as shown inFIG.10, it is assumed that k2 is greater than or equal to 1, and the UE can only support simultaneous data transmission on two carriers. On sub-frame n, the UE allocates resource1001on carrier1and resource1002on carrier2. On the sub-frame n+1, the UE allocates resource1003on the carrier3. The UE cannot transmit either data of the sub-frame n or data of the sub-frame n+1 due to the effect of the carrier switching time. Assuming that the data on resource1003has a higher priority than that on the resources1001and1002, the UE may discard the data on resources1001and1002, and transmit only the data on resource1003. Fifth Embodiment It is assumed that the total number of Sidelink Process that the UE can use on a carrier is NSL, where NSLis greater than or equal to 1; for example, NSLis equal to 2. The Sidelink Process means that the UE periodically reserves resources at a certain reservation interval and can perform transmission K times over a period of time, where K is greater than or equal to 1, for example, K is equal to 2. When the traffic of the UE is relatively large, it may exceed the carrying capacity of a Sidelink Process on one carrier. In this case, a first method may include enabling by the UE more than one Sidelink Process on one or more carriers, thereby increasing the amount of traffic being transmitted. When a carrier has occupied NSLSidelink Processes, the UE can increase the number of the carriers to transmit more data. Alternatively, a second method may include that the UE increases the number of the carriers to transmit data and transmit data over a plurality of carriers. When the number of the carriers cannot be increased; for example, it is limited by the number of carriers supported by the UE, or a certain type of traffic can only be transmitted on a particular set of carriers, the UE may, by adding a Sidelink Process occupied by a carrier to transmit more data. It may be predefined, configured by higher level signaling or preconfigured, or even dynamically determined by the UE regarding the UE using either of the two methods. For example, the UE determines the method to be used based on information such as congestion state and traffic type of each carrier. Alternatively, a priority strategy may be defined regarding usage of the two methods. For example, the UE preferentially selects the second method as long as the UE has a multi-carrier transmission capability and the multiple carriers have sufficiently good detection results; otherwise, the UE selects the first method. The method is beneficial to reduce the load of a resource pool for a single carrier. Depending on the type of traffic, some traffic may be limited to a portion of the carriers. Each of the portion of the carriers can transmit data by using up to NSLSidelink Processes. The UE may prioritize the transmission of data on one or more Sidelink Processes on carriers whose CBR is less than a threshold; otherwise, the UE may transmit data on other carriers. The threshold may be pre-defined, configured by higher level signaling, or preconfigured. The UE may prioritize the transmission of data on a carrier with the smallest CBR among carriers that occupy a number of Sidelink Processes with the number less than NSL. Alternatively, the UE may transmit data on the carrier with the smallest CBR, while ensuring that the number of Sidelink Processes on the respective carriers is less than NSLand the difference between numbers does not exceed one. The size of data D of the traffic may exceed the carrying capacity of a carrier. For example, for a 20 MHz bandwidth, the maximum transport block size (TBS) that can be transmitted on a sub-frame is 31704 bits. In the case, the data D needs to be divided into a plurality of smaller blocks so as to be mapped onto X carriers. The resource selection of the UE on the X carriers may include equalizing the number of times data is transmitted on each carrier. According to the method, the data transmission performances on the X carriers are close to each other, and the reliability of the data D is improved. For example, when a small block transmitted on a carrier is transmitted 2 times (initial and retransmission), the other blocks need to be transmitted twice on a corresponding carrier, so that the performance of the individual blocks is similar. In conducting the resource selection, on a carrier, the UE may first select a first resource, and then select a second resource in a sub-frame range by taking the first resource as the center (except for the sub-frame where the first resource is located). The sub-frame range is determined by the maximum interval of the two resources that transmit the same data as indicated by the SA and the traffic latency requirement. According to such a resource selection method, if there is no second available resource within the sub-frame range, only one resource is selected for this carrier. At this point, the UE may discard the first resource, that is, re-select a resource for the carrier to obtain two available resources. It is assumed that the set SBis obtained after the exclusion of the unavailable resources according to the detection result. The UE may select only one resource for a carrier if there is no two resources whose interval is less than the maximum interval and satisfy the traffic latency requirement in the set SB; It is also possible for the UE to re-execute the resource selection and increase the number of resources in the set SBuntil there are such two resources whose interval is less than the maximum interval and satisfy the traffic latency requirements in the SB. It is assumed that the UE transmits data over multiple carriers. The congestion levels of different carriers are generally different. The UE may only adjust the transmission parameters on a carrier when the congestion level on the carrier changes, including discarding the packets. In the case that the UE transmits data D over X carriers, the UE may adjust only the transmission parameters on the resources of a portion of carriers or discard the data transmission over the resources on the portion of the carriers when the congestion level of the portion of the carriers in the X carriers changes, in order to avoid frequent resource selection on other carriers. This is advantageous in improving the efficiency of the resource selection algorithm for the other carriers, since one of the basic assumptions of the resource selection algorithm is that the UE periodically occupies the same resource. Alternatively, the UE may simultaneously adjust the transmission parameters of the resources of the X carriers or discard the data transmission over the resources of the X carriers at the same time, i.e., the respective small blocks of the data D which are transmitted on one resource on each carrier of the X carriers, or discard the data D totally. In the case of transmitting data on X carriers, where X is greater than or equal to one, the packet size of a traffic is generally not constant. The X carriers may transmit data of the same traffic, or may transmit data of a plurality of traffics. One possible situation is that the UE has selected and reserved resources, but the resources previously reserved on the X carriers are not sufficient to transmit a packet with an increased size. At this time, the UE can perform resource reselection. The UE may discard the resource reservation of the X carriers and perform a resource selection on one or more carriers, for example, to re-execute the resource selection on the X carriers, thereby increasing the data carrying capacity of the carriers. The method helps to avoid or mitigate the half-duplex problem inFIG.6because the resource selection of the X carriers is always done at the same time. For example, assuming that the UE performs resource selection on carrier A and carrier B at different times, the UE selects the resource located in sub-frame a on carrier A and performs data transmission. The UE is not able to detect resource in sub-frame a on carrier B due to the half-duplex operation. When it is necessary to perform resource selection on carrier B, a sub-frame corresponding to sub-frame a in the selection window of carrier B is not available. This results that the resource selected on carrier B is located in different sub-frames from the sub-frames in which the resource selected on carrier A is located, which deteriorates the half-duplex problem. Alternatively, the UE may discard the resource reservation of one of the X carriers or of a portion of the X carriers and perform resource selection on one or more carriers, for example, only on one of the X carriers or a portion of the X carriers for which the resource reservation is discarded, thereby increasing the date carrying capacity of the carriers. For example, the carriers on which resource selection is performed may be carriers with a relatively low congestion level, i.e., the carriers with a relatively small CBR. The UE gives up the resource reservation of the X carriers in case that the packet with an increased size cannot be transmitted even if the UE gives up the resource reservation of one of the X carriers or of a portion of the X carriers and perform resource selection. Alternatively, the UE may enable more sidelink processes on one of the carriers or a portion of the carriers in the X carriers by performing resource selection to obtain the resources of the more sidelink processes, thereby increasing the data carrying capacity. Alternatively, the UE may perform resource selection on other carriers than the X carriers to obtain additional resources, thereby improving the data carrying capacity. By using this method, it is advantageous to improve the efficiency of the resource selection algorithm by avoiding the frequent resource selection of the carriers on which resource selection is not performed in the X carriers, because one of the basic assumptions of the resource selection algorithm is that the UE periodically occupies the same resource. For a case where data is transmitted on X carriers, where X is greater than or equal to 1, the resources selected on the X carriers may be located in the same or different sub-frames. The X carriers may transmit data of the same traffic, or may transmit data of a plurality of traffics. One possible situation is that the reserved resources are not released after a number of packets have been transmitted, meanwhile the resources reserved on one or a portion of the carrier cannot meet the transmission requirements of the packet, for example, the latency, requirement, reliability requirements or other performance requirements, and resources reserved on other carriers still meet the packet transmission requirements. At this time, the UE may discard the resource reservation of the X carriers and perform resource selection on one or more carriers, for example, on the X carriers to meet the transmission requirements. Similarly, the method helps to avoid or mitigate the half-duplex problem inFIG.6because the resource selection of the X carriers is always done at the same time. Alternatively, the UE may discard the resource reservation of one of the X carriers or a portion of the X carriers and perform resource selection on one or more carriers, for example, only on one of the X carriers or a portion of the X carriers for which the resource reservation is discarded, so as to meet the transmission requirements. The UE discards the resource reservation of the X carriers only if the resources of the X carriers do not satisfy the transmission request. By using this method, it is advantageous to improve the efficiency of the resource selection algorithm by avoiding the frequent resource selection of the carriers on which resource selection is not performed in the X carriers, because one of the basic assumptions of the resource selection algorithm is that the UE periodically occupies the same resource. Assuming that the UE transmits data over multiple carriers, the resources reserved on carrier A are insufficient to transmit the data of carrier A (e.g., because of the change in congestion level of carrier A, the UE needs to adjust the transmission parameters or discard packets on carrier A), and that the UE has reserved resources on another carrier, carrier B. The traffic priority of carrier A and carrier B can be compared. When the traffic priority of carrier A is higher than that of carrier B and the reserved resources of carrier B can carry the data of the carrier A, the data of the carrier A can be transmitted on the reserved resource of the carrier B. The UE may discard the data of the carrier B; or, if the reserved resource of the carrier A can carry the data of the carrier B, the data of the carrier B may be transmitted on the reserved resource of the carrier A; or, the data of carrier B is transmitted on resources in Exception pool. It is assumed that the UE may select resources and transmit data based on detection on multiple carriers. In some cases, the UE may not have such a good detection result on one carrier (e.g., in reselection or switching cases, etc.) that it can effectively performs resource selection on the carrier. For example, when the number of sub-frames actually detected by the UE on a carrier is less than a certain threshold, or when the ratio of the total number of sub-frames actually detected by the UE on one carrier to the total number of sub-frames in the sensing window is less than a certain threshold, the UE believes that the detection result on the carrier is not good enough. Alternatively, on a carrier, some sub-frames within the selection window of the UE are not available depending on the sub-frame that are not detected by the UE within the sensing window, and when the number of remaining available sub-frames is less than a certain threshold, or when the ratio of the number of remaining available sub-frames to the total number of sub-frames in the selection window is less than a certain threshold, the UE believes that the detection result on the carrier is not good enough. In particular, consider a case where the UE transmits data in different sub-frames on a plurality of carriers. If the UE transmits data on one carrier in a sub-frame, the UE may not be able to perform detection on another carrier due to half-duplex limitation, which reducing the number of sub-frames actually detected by the UE. In the case where the detection result is reduced due to the half-duplex limitation among the plurality of carriers, the resource may be selected on the carrier based on the available detection result; or, in such a case, the UE may believe that the detection result on the carrier is not good enough to select resources on the carrier; or, in such a case, when the number of sub-frames that cannot be detected due to the half-duplex limitation among the plurality of carriers or the ratio exceeds the specific threshold, the UE considers that the detection result on the carrier is not good enough, otherwise the UE still selects resources on the carrier based on the available detection results. When the UE may not have an enough good detection result on carrier A, a first method is to map the data D of carrier A to an Exception pool for transmission. A second method is that, the UE select resources on another carrier, carrier B to transmit the data D if the UE has an enough good detection result on carrier B, and no data is transmitted on carrier B; or, the UE may select resources of a second Sidelink process on carrier B to transmit the data D if only a sidelink process is used to transmit data on carrier B. A third method is to compare the traffic priority of carrier A and carrier B if the UE has reserved resources on carrier B; and when the traffic priority of carrier A is higher than that of carrier B and the reserved resources of carrier B can carry the data of the carrier A, the data of the carrier A can be transmitted on the reserved resource of the carrier B. The UE may discard the data of the carrier B; or, the data of carrier B is transmitted on resources in Exception pool. Sixth Embodiment The synchronization sources of the UEs on multiple carriers may be different, which may result in different transmission timings on different carriers. As shown inFIG.11, assuming that the UE transmits data on two carriers and the timing offset between the two carriers is high, when the UE transmits data in the sub-frame1101of carrier2, the UE cannot perform the detection on sub-frames1111and1112of carrier1. That is, the half-duplex problem of UE is more serious in the multi-carrier case. In addition, when the timing offset between the two carriers is relatively high, the data transmission in sub-frame n on one carrier may overlap with the data transmission in sub-frame n+1 or n−1 on the other carrier, resulting in an increase in the complexity of power allocation. It is assumed that the LE supports transmission of data over multiple carriers, which may limit the UE to transmit data on a plurality of carriers only if the timing offset is within a certain range. This can mitigate or completely avoid the multi-carrier half-duplex problem and power control problem. Here, it is possible to limit the timing offset to T us. For example, similarly as in the LTE CA system, T can be approximately equal to T0, T0 is equal to 32.47; or the last OFDM symbol is punctured in sub-frames of the sidelink transmission, so that T can be equal to the length of an OFDM symbol, approximately equal to 71 us, such a timing offset would not result in a coincidence of data transmission in adjacent sub-frames on multiple carriers; alternatively, T may be equal to the length of an OFDM symbol minus the tx-rx switching time; if the switching time is 20 us, is approximately equal to 51 us, such a timing offset would not result in a coincidence of data transmission in adjacent sub-frames on multiple carriers and can provide the tx-rx switching time; alternatively, T can be equal to the length of an OFDM symbol plus T0; that is, T is approximately equal to 101 us, which allows the data transmission in adjacent sub-frames on multiple carriers to overlap by no more than T0 us. Alternatively, the timing offset of the UE on a plurality of carriers may not be limited, and the data transmission of the UE over a plurality of carriers is always allowed. In fact, in LTE CA systems, it is necessary to limit the timing offset among carriers due to the need of defining the timing of cross-carrier scheduling and the timing of HARQ-ACK feedback. However, in sidelink systems, there is no problem regarding scheduling and HARQ-ACK feedback, so it is possible not to limit the timing offset of carriers. However, it is necessary to control the multi-carrier half-duplex problem. Seventh Embodiment In LTE V2X systems, the total transmission power A of the UE (including PSCCH and PSSCH) is A=min{PCMAX,10log10(MPSSCH+10310×MPSCCH)+PO_PSSCH,4+αPSSCH,4·PL}·PO_PSSCH,4 and αPSSCH,4are power control parameters configured by higher level, 10 log10(MPSSCH+103/10×MPSCCH) is a parameter that adjusts the transmission power according to the number of PRB occupied by the UE, and is the pathless between the UE and the base station. The power control method is independent of MCS used by the UE for transmission data. Therefore, when the UE uses a relatively low MCS (e.g., QPSK), the coverage of the data transmission of the UE is relatively large; when the UE uses a relatively high MCS (e.g., 16 QAM or 64 QAM), the coverage of the data transmission of the UE is relatively small. When the size of data D of the traffic is relatively large that may exceed the carrying capacity on one carrier. For example, for a 20 MHz bandwidth, the maximum transport block size (TBS) that can be transmitted on a sub-frame is 31704 bits. In the case, the data D needs to be divided into a plurality of smaller blocks so as to be mapped onto X carriers. Since the X carriers actually transmit the same data D, the small blocks shall have the same or similar transmission performance. According to the power control method of the UE V2X, the transmission power of the UE is independent of the MCS. When the MCSs used by the UE are different in the X carriers, the coverage of the respective carriers may be different. Since the receiving party needs to receive all of the small blocks on the X carriers so that the data D can be obtained, the coverage of the UE is actually determined by the carrier having a. relatively small coverage in the X carriers. The carrier with a large coverage in the X carriers actually wastes the transmission power and increases the interference level of the carrier. A method of addressing the problem of the UE on the different coverage of a plurality of carriers is described below. A first method is to introduce an item ƒ(MCS) related to MCS of the UE in the power control formula. That is, A=min{PCMAX,10log10(MPSSCH+10310×MPSCCH)+PO_PSSCH,4+αPSSCH,4·PL+f(MCS)}. For example, ƒ(MCS) may have a form that is consistent with the MCS related parameter ΔTF,c(i) in the PUSCH control method of LTE. A second method is to introduce an item Δifrelated to the interference level detected by the UE in the power control formula. That is, A=min{PCMAX,10log10(MPSSCH+10310×MPSCCH)+PO_PSSCH,4+αPSSCH,4·PL+Δif}. The interference level may be determined based on factors such as the congestion state of the carrier, the PSSCH-RSRP of the data channel scheduled by the received SA, and/or the S-RSSI measured on the subchannel. Generally speaking, when the interference level is relatively low, UE can transmit at a lower power, i.e., Δifbeing relatively small; when the interference level is relatively high, the UE needs to transmit at a higher power to ensure coverage, i.e., Δifbeing relatively large. PO_PSSCH,4is used to compensate the long-term link state of the UE, and Δifis used to compensate the dynamic change of the link. A third method is to introduce an item ƒ(MCS,inferferencelevel) related to MCS of the UE and the interference level detected by the UE in the power control formula. That is, A=min{PCMAX,10log10(MPSSCH+10310×MPSCCH)+PO_PSSCH,4+αPSSCH,4·PL+f(MCS,interferencelevel)}. In this way, the UE can determine its transmission power according to the MCS and the detected interference level both. With the three methods of modifying the power control formula, the UE can reasonably set the transmission power on each carrier, thus optimizing the transmission performance of the UE on each carrier. When the UE is power limited, the UE needs to adjust the transmission power of each carrier so that the total transmission power of the UE does not exceed the maximum transmission power. Here, the transmission power of the carriers before the adjustment may be determined according to the three methods; alternatively, it is also possible to use an existing method to determine the transmission power, for example, by A=min{PCMAX,10log10(MPSSCH+10310×MPSCCH)+PO_PSSCH,4+αPSSCH,4·PL}. A first method of dealing with UE power limitation may include weighting the transmission powers on respective carriers with equal weighting coefficients so that the total transmission power of the respective carriers does not exceed the maximum transmission power. In a second method of dealing with UE power limitation, the UE may preferentially guarantee the power for data transmission on a carrier with a higher traffic priority and allocate the remaining power to a carrier with a lower traffic priority. For example, the power for data transmission is allocated for the carriers in descending order of the traffic priorities of the carriers. When there are multiple carriers having the same priority, the transmission power of the multiple carriers can be weighted with equal weighting coefficients so that the total transmission power of the respective carriers does not exceed the maximum transmission power. In a third method of dealing with UE power limitation, the UE may determine the weighting coefficients according to the traffic priorities of the respective carriers. Generally speaking, the weighting coefficient of the traffic with a high priority is relatively high. The proportions of weighting coefficients of the respective carriers may be constant, and the total transmission power of the respective carriers does not exceed the maximum transmission power by adjusting the values of the weighting coefficients. For a UE that transmits data over multiple carriers, when the UE is power limited, the effect of coverage of each carrier of the UE may be taken into account when adjusting the transmission power of each carrier of the UE. For example, the transmission powers of the respective carriers can be reduced in descending order of the coverage of the respective carriers. The UE may first reduce the transmission power of the carrier with a relatively large coverage, such as the data transmission of the carrier with a low MCS and/or a low interference level. When the coverage of each of multiple carriers is close to each other, the UE further adjusts the transmission power of each of the carriers if the power is still limited. For example, the three methods of dealing with UE power limitation may be used to deal with the transmission power. According to the method, the present application also discloses a UE which can be used to implement the method. As shown inFIG.12, the UE comprises a detection module, a resource selection module and a transceiver module, wherein: the detection module is configured to detect a scheduling assignment signal SA of another UE in a sensing window of each of a plurality of carriers, measure a received power of a scheduled data channel based on the SA, and detect a received energy of each subchannel of each sub-frame in the sensing window; the resource selection module is configured to select a resource for data transmission on the plurality of carriers based on the SA, the received power, and the received energy; the transceiver module is configured to perform data transmission by using the selected resource. It will be understood by those of skilled in the art that all or a portion of the steps of the method of the embodiments described above may be implemented by an associated hardware with a program stored in a computer readable storage medium. When executed, the program causes the hardware to implement steps including one of the steps of the method embodiment or a combination thereof. In addition, the functional units in the various embodiments of the present application may be integrated in a processing module, or each unit may be a physical unit, or two or more units may be integrated in one module. The integrated module can be implemented in the form of hardware, or in the form of software function modules. The integrated module may also be stored in a computer-readable storage medium if it is implemented in the form of a software function module and is sold or used as a separate product. The storage medium may be a read-only memory, a magnetic disk, or an optical disk. The foregoing is only a preferred embodiment of the present application and is not intended to limit the present application, and any modifications, equivalent substitutions, improvements, and the like within the spirit and principles of the present application are intended to be included in the scope of protection. | 106,968 |
11943748 | DETAILED DESCRIPTION Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. It should be noted that while aspects may be described herein using terminology commonly associated with a 5G or NR radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G). FIG.1is a diagram illustrating an example of a wireless network100, in accordance with the present disclosure. The wireless network100may be or may include elements of a 5G (NR) network and/or an LTE network, among other examples. The wireless network100may include a number of base stations110(shown as BS110a,BS110b,BS110c,and BS110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and may also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), or the like. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used. A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown inFIG.1, a BS110amay be a macro BS for a macro cell102a,a BS110bmay be a pico BS for a pico cell102b,and a BS110cmay be a femto BS for a femto cell102c.A BS may support one or multiple (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” may be used interchangeably herein. In some aspects, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some aspects, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network100through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network. Wireless network100may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown inFIG.1, a relay BS110dmay communicate with macro BS110aand a UE120din order to facilitate communication between BS110aand UE120d.A relay BS may also be referred to as a relay station, a relay base station, a relay, or the like. Wireless network100may be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts). A network controller130may couple to a set of BSs and may provide coordination and control for these BSs. Network controller130may communicate with the BSs via a backhaul. The BSs may also communicate with one another, directly or indirectly, via a wireless or wireline backhaul. UEs120(e.g.,120a,120b,120c) may be dispersed throughout wireless network100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, or the like. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags, that may communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE). UE120may be included inside a housing that houses components of UE120, such as processor components and/or memory components. In some aspects, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled. In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, or the like. A frequency may also be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed. In some aspects, two or more UEs120(e.g., shown as UE120aand UE120e) may communicate directly using one or more sidelink channels (e.g., without using a base station110as an intermediary to communicate with one another). For example, the UEs120may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol or a vehicle-to-infrastructure (V2I) protocol), and/or a mesh network. In this case, the UE120may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station110. Devices of wireless network100may communicate using the electromagnetic spectrum, which may be subdivided based on frequency or wavelength into various classes, bands, channels, or the like. For example, devices of wireless network100may communicate using an operating band having a first frequency range (FR1), which may span from 410 MHz to 7.125 GHz, and/or may communicate using an operating band having a second frequency range (FR2), which may span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” band. Similarly, FR2 is often referred to as a “millimeter wave” band despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. Thus, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies less than 6 GHz, frequencies within FR1, and/or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies within the EHF band, frequencies within FR2, and/or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and techniques described herein are applicable to those modified frequency ranges. As indicated above,FIG.1is provided as an example. Other examples may differ from what is described with regard toFIG.1. FIG.2is a diagram illustrating an example200of a base station110in communication with a UE120in a wireless network100, in accordance with the present disclosure. Base station110may be equipped with T antennas234athrough234t,and UE120may be equipped with R antennas252athrough252r,where in general T≥1 and R≥1. At base station110, a transmit processor220may receive data from a data source212for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor220may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor220may also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor230may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs)232athrough232t.Each modulator232may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator232may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators232athrough232tmay be transmitted via T antennas234athrough234t,respectively. At UE120, antennas252athrough252rmay receive the downlink signals from base station110and/or other base stations and may provide received signals to demodulators (DEMODs)254athrough254r,respectively. Each demodulator254may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator254may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector256may obtain received symbols from all R demodulators254athrough254r,perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor258may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE120to a data sink260, and provide decoded control information and system information to a controller/processor280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some aspects, one or more components of UE120may be included in a housing284. Network controller130may include communication unit294, controller/processor290, and memory292. Network controller130may include, for example, one or more devices in a core network. Network controller130may communicate with base station110via communication unit294. Antennas (e.g., antennas234athrough234tand/or antennas252athrough252r) may include, or may be included within, one or more antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include a set of coplanar antenna elements and/or a set of non-coplanar antenna elements. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include antenna elements within a single housing and/or antenna elements within multiple housings. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components ofFIG.2. On the uplink, at UE120, a transmit processor264may receive and process data from a data source262and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from controller/processor280. Transmit processor264may also generate reference symbols for one or more reference signals. The symbols from transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by modulators254athrough254r(e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station110. In some aspects, a modulator and a demodulator (e.g., MOD/DEMOD254) of the UE120may be included in a modem of the UE120. In some aspects, the UE120includes a transceiver. The transceiver may include any combination of antenna(s)252, modulators and/or demodulators254, MIMO detector256, receive processor258, transmit processor264, and/or TX MIMO processor266. The transceiver may be used by a processor (e.g., controller/processor280) and memory282to perform aspects of any of the methods described herein (for example, as described with reference toFIGS.3-8). At base station110, the uplink signals from UE120and other UEs may be received by antennas234, processed by demodulators232, detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by UE120. Receive processor238may provide the decoded data to a data sink239and the decoded control information to controller/processor240. Base station110may include communication unit244and communicate to network controller130via communication unit244. Base station110may include a scheduler246to schedule UEs120for downlink and/or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD/DEMOD232) of the base station110may be included in a modem of the base station110. In some aspects, the base station110includes a transceiver. The transceiver may include any combination of antenna(s)234, modulators and/or demodulators232, MIMO detector236, receive processor238, transmit processor220, and/or TX MIMO processor230. The transceiver may be used by a processor (e.g., controller/processor240) and memory242to perform aspects of any of the methods described herein (for example, as described with reference toFIGS.3-8). Controller/processor240of base station110, controller/processor280of UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with dynamic determination of available slots for transmission of sounding reference signal (SRS) information, as described in more detail elsewhere herein. For example, controller/processor240of base station110, controller/processor280of UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, process700ofFIG.7and/or other processes as described herein. Memories242and282may store data and program codes for base station110and UE120, respectively. In some aspects, memory242and/or memory282may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station110and/or the UE120, may cause the one or more processors, the UE120, and/or the base station110to perform or direct operations of, for example, process700ofFIG.7and/or other processes as described herein. In some aspects, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples. In some aspects, the UE (e.g., UE120) includes means for receiving, from a base station, configuration information regarding one or more available slots associated with transmitting SRS information; means for receiving, from the base station, dynamic downlink communication including slot information for determining a select available slot from among the one or more available slots; and/or means for transmitting, to the base station, the SRS information during the select available slot, determined based at least in part on the slot information and the configuration information. The means for the UE to perform operations described herein may include, for example, one or more of antenna252, demodulator254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, modulator254, controller/processor280, or memory282. In some aspects, the UE includes means for determining the select available slot based at least in part on a slot factor, associated with a format related to a given slot, and an initial available slot value, the slot factor being received via the dynamic downlink communication and the initial available slot value being received via the configuration information. While blocks inFIG.2are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor264, the receive processor258, and/or the TX MIMO processor266may be performed by or under the control of controller/processor280. As indicated above,FIG.2is provided as an example. Other examples may differ from what is described with regard toFIG.2. A UE may conduct data communication with a BS in a wireless network such as an LTE network or a 5G/NR network. The data communication may include downlink communications from the BS to the UE and uplink communications from the UE to the BS. The UE may receive the downlink communications during a slot reserved for downlink communications (e.g., a downlink slot) and may transmit the uplink communications during a slot reserved for uplink communications (e.g., an uplink slot). To adequately receive the uplink communications from the UE, the BS may estimate a measure of quality associated with the uplink communications. To enable the BS to estimate the measure of quality, the UE may transmit SRS information to the BS. Based on receiving the SRS information, the BS may estimate the measure of quality associated with the uplink communications. The SRS information may include SRS resources configured by the BS to enable the UE to perform, for example, antenna switching operations, codebook-based operations, non-codebook-based operations, beam management operations, or the like. During the data communication, as shown in example300ofFIG.3, the UE may receive downlink control information (DCI) to trigger the UE to transmit the SRS information. The UE may receive the DCI during a given downlink slot (D) and may transmit the SRS information during a given uplink slot (U) that occurs a fixed number of SRS offset slots after the given downlink slot. The given uplink slot may be referred to as a transmission slot. The fixed number of SRS offset slots may be preconfigured by the BS during initiation of the data communication between the BS and the UE. In some cases, after transmitting the DCI and before receiving the SRS information, the BS may reserve the transmission slot for downlink communications. In other words, the BS may convert the transmission slot from being an uplink slot U to being a downlink slot D. In this case, the UE may not be able to transmit the SRS information during the transmission slot. Also, due to the fixed number of SRS offset slots, the UE may not be able to transmit the SRS information during another uplink slot. As a result, the BS may not adequately receive the SRS information from the UE. In some cases, the BS may be communicating with a plurality of UEs. To receive respective SRS information from the plurality of UEs during a transmission slot, as shown in example400ofFIG.4, the BS may transmit a plurality of DCIs during a given downlink slot, which may occur the fixed number of SRS offset slots before the transmission slot. Transmitting the plurality of DCIs during the given downlink slot may cause DCI congestion. Additionally, transmission of the respective SRS information by the plurality of UEs during the transmission slot may result in interference among the SRS information. As a result, the BS may not adequately receive the respective SRS information from the plurality of UEs. Without adequately receiving the SRS information, the BS may not be able to adequately estimate the measure of quality associated with the uplink communications. As a result, the BS may not be able to adequately receive uplink communications, and the data communication between the UE (or the plurality of UEs) and the BS may experience an interruption or a stoppage. Resolving the interruption or stoppage may inefficiently consume UE resources (e.g., amount of processing, utilization of memory, power consumption, or the like) and network resources (e.g., bandwidth, management resources, or the like) that could be more efficiently utilized to perform other tasks related to the data communication. Various aspects of techniques and apparatuses described herein may enable dynamic determination of available slots for transmission of SRS information. In some aspects, during initiation of a data communication between a BS and a UE, the UE may receive configuration information associated with one or more available slots associated with transmitting the SRS information. During the data communication, the UE may receive dynamic signaling (e.g., medium access control (MAC) signaling including a control element (MAC CE), DCI signaling, or a combination thereof) including slot information to enable the UE to determine a select available slot, from among the one or more available slots, during which the SRS information is to be transmitted. The slot information included in the dynamic signaling may accommodate the BS having converted a transmission slot (an uplink slot) to a downlink slot. The UE may utilize the select available slot to transmit the SRS information. Additionally, the BS may transmit respective DCI to a respective plurality of UEs during different slots to trigger transmission of respective SRS information during respective select available slots, thereby avoiding DCI congestion and/or interference among the SRS information. In this way, the BS may adequately receive the SRS information and may adequately estimate a measure of quality associated with uplink communications. As a result, the BS may adequately receive the uplink communications from the UE, and the data communication between the UE and the BS may continue uninterrupted. Additionally, transmitting the SRS information during the select available slot may enable efficient utilization of UE resources (e.g., amount of processing, utilization of memory, or the like) and network resources (e.g., bandwidth, subchannels, or the like). In some aspects, a UE may receive, from a base station, configuration information regarding one or more available slots associated with transmitting SRS information; receive, from the base station, dynamic downlink communication including slot information for determining a select available slot from among the one or more available slots; and transmit, to the base station, the SRS information during the select available slot, determined based at least in part on the slot information and the configuration information. In this way, data communication between the UE and the BS may be improved. FIG.5is a diagram illustrating an example500associated with dynamic determination of available slots for transmission of SRS information, in accordance with the present disclosure.FIG.5shows a UE120and a BS110conducting data communication in, for example, an LTE network or a 5G/NR network. The data communication may include downlink communications from the BS110to the UE120and may include uplink communications from the UE120to the BS110. As shown by reference number510, the BS110may transmit, and the UE120may receive, configuration information at a beginning (e.g., during initiation) of the data communication. In some aspects, the UE120may receive the configuration information from a device other than BS110(e.g., from another base station). In some aspects, the UE120may receive the configuration information via, for example, a control channel (e.g., a physical downlink control channel (PDCCH)) between the UE120and the BS110. The configuration information may be communicated via radio resource control (RRC) signaling, MAC signaling (e.g., MAC CE), DCI signaling, or a combination thereof (e.g., RRC configuration of a set of values for a parameter and DCI indication of a selected value of the parameter). In some aspects, the configuration information may include information associated with configuring the UE120with one or more SRS resource sets, each SRS resource set comprising a respective one or more SRS resources (e.g., the configured SRS resources). The configured SRS resources may be utilized by the UE120to perform, for example, SRS signaling antenna switching operations, codebook-based operations, non-codebook-based operations, beam management operations, or the like. As shown by reference number520, the configuration information may include SRS configuration information associated with transmitting SRS information. As shown by reference number530, based at least in part on the SRS configuration information, the UE120may configure the UE120to transmit the SRS information. In some aspects, the configuration information may include an indication of, for example, one or more configuration parameters for the UE120to use to configure the UE120for the data communication. In some aspects, the SRS configuration information may include/indicate information associated with transmitting SRS information. In some aspects, the SRS configuration information may indicate a fixed number of SRS offset slots. The fixed number may be an integer value from, for example, 1 through 32. If no value for the fixed number of SRS offset slots is indicated, then the UE120may determine the value for the fixed number of SRS offset slots to be 0. Further, the SRS configuration information may indicate that the UE120is to transmit the SRS information during an uplink slot that occurs the fixed number of SRS offset slots after a reference slot. The SRS configuration information may also include information regarding one or more available slots associated with transmitting the SRS information. In some aspects, the information regarding the one or more available slots may include a list of integer values representing respective select numbers of offset slots to be used by the UE120to determine a select available slot from among the one or more available slots. For instance, the SRS configuration information may indicate that the UE120is to transmit the SRS information during the select available slot, which occurs a select number (e.g., t) of offset slots after the reference slot. Based at least in part on the SRS configuration information, the UE120may transmit the SRS information t offset slots after the reference slot. In some aspects, the UE may transmit the SRS information t+1 offset slots after the reference slot. In some aspects, as shown in example600ofFIG.6, the list of integer values (which may be referred to as “t-values”) representing the respective select numbers of offset slots may be included in one or more available-slot lists. In some aspects, for example, an available-slot list may include a plurality of t-values representing respective numbers t of offset slots to be utilized by the UE120to determine the select available slot. In some aspects, alternatively to transmitting the SRS information during the select available slot that occurs the fixed number of SRS offset slots after the reference slot, the SRS configuration information may indicate that the UE120is to transmit the SRS information during the select available slot, which occurs the select number of offset slots after the reference slot. In some aspects, a t-value may represent a number of slots between the reference slot and the select available slot. For example, a first (e.g., select) t-value of a set of t-values indicated by an available-slot list may indicate a number of slots between the reference slot and the select available slot such as in cases in which the number of slots between the reference slot and the select available slot is n−1 (where t=n). In other aspects, a t-value may represent a number of slots between the reference slot and the select available slot by corresponding to a number of offset slots to be utilized by the UE120in determining the select available slot. For instance, as shown in example600ofFIG.6, an available-slot list may include N integer values (e.g., V1, V2, V3, V4, V5, V6, V7, . . . , VN) representing respective select numbers of offset slots to be utilized by the UE120to determine the select available slot. Each integer value is associated with a respective position in the available-slot list. For instance, V1is associated with position1, V2is associated with position2, . . . , and VN is associated with position N. In some aspects, N may have an integer value from 1 through 128. In some aspects, the SRS configuration information may enable the UE120to configure the UE120to determine the select available slot and to transmit the SRS information during the select available slot. For instance, the SRS configuration information may indicate that the UE120is to determine the select available slot based at least in part on slot information and/or on the SRS configuration information. The slot information may be included in dynamic signaling (e.g., dynamic downlink communication), which may be received from the BS110during the data communication. The dynamic signaling may include the MAC CE, the DCI, or a combination thereof. In some aspects, the SRS configuration information and/or the slot information may indicate that the reference slot is a slot during which the DCI, that triggers transmission of the SRS information, is received. In some aspects, the SRS configuration information and/or the slot information may indicate that the reference slot is a given slot (e.g., a slot indicated by the legacy triggering offset) configured by the BS110. In some aspects, the slot information may indicate the respective position of an integer value in the available-slot list. Based at least in part on the indicated respective position, the UE120may determine the select number of offset slots. For instance, when the slot information indicates position3, the UE120may determine that the SRS information is to be transmitted during the select available slot, which occurs V3slots after the reference slot. Similarly, when the slot information indicates position N, the UE120may determine that the SRS information is to be transmitted during the select available slot, which occurs VN slots after the reference slot. In some aspects, the slot information may be received via the dynamic signaling (e.g., MAC CE and/or DCI) transmitted from the BS110to the UE120. When the slot information is received via DCI, one or more bits included in the DCI may indicate the respective position in the available-slot list. In some aspects, a quantity (e.g., x) of the one or more bits may be based at least in part on the integer value of N. In some aspects, x number of bits may be used when the available-slot list includes2xpositions (e.g., N=2x). For instance, when the value of N=2 (e.g., there are two integer values, V1and V2, in the available-slot list), the quantity of x may be 1; when the value of N=4 (e.g., there are four integer values, V1through V4, in the available-slot list), the quantity of x may be 2; when the value of N=8 (e.g., there are eight integer values, V1through V8, in the available-slot list), the quantity of x may be 3, and so on. In some aspects, the UE120may determine the quantity of the one or more bits that are used by the DCI to indicate the respective position in the available-slot list. The quantity of the one or more bits may be based at least in part on a maximum number of available slots associated with a set of available slots of a plurality of sets of available slots. In some aspects, the plurality of sets of available slots may be associated with at least one component carrier. For example, in some aspects, a plurality of SRS resource sets may be configured across a number of component carriers, and each SRS resource set may have a corresponding available-slot list that includes a corresponding set of t-values. Thus, the plurality of SRS resource sets may correspond to a plurality of sets of t-values. The UE120may determine the quantity of bits used by the DCI to indicate respective positions in the available-slot lists based at least in part on a scheduled component carrier configuration of t-values (offset slot values, as indicated above). For example, the UE120may determine the quantity of bits based at least in part on a set of t-values, of the plurality of sets of t-values, that has a maximum number of t-values as compared to the other sets of t-values. In some aspects, the UE120may determine the quantity of bits based at least in part on the maximum number of t-values across all configured component carriers. In some aspects, the UE120may determine the quantity of bits per component carrier based at least in part on a set of t-values having the maximum number of t-values of the sets of t-values associated with a specified component carrier. In some aspects, the SRS configuration information may indicate a plurality of available-slot lists. In this case, slot information may be received via the MAC CE, which may indicate a select available-slot list, from among the plurality of available-slot lists, to be utilized by the UE120to determine the select available slot. Further, one or more bits in the MAC CE may indicate the respective position in the select available-slot list. Based at least in part on the indicated respective position, the UE120may determine the select number of offset slots, as discussed above. Alternatively, after the select available-slot list is indicated by the MAC CE, the UE120may receive DCI including the x number of bits that indicate the respective position in the select available-slot list. Based at least in part on the indicated respective position by the MAC CE and/or DCI, the UE120may determine the select number of offset slots, as discussed above. Utilizing the MAC CE to indicate at least the select available-slot list, from among the plurality of available-slot lists, may enable the BS110to utilize a reduced number of bits in the DCI for indicating the slot information associated with transmitting the SRS information. In some aspects, the SRS configuration information may enable the UE120to configure the UE120to transmit the SRS information based at least in part on a time of receipt of the dynamic signaling (e.g., MAC CE and/or DCI). For instance, the UE120may transmit the SRS information, based at least in part on the slot information included in a MAC CE, after a MAC CE duration of time. Similarly, the UE120may transmit the SRS information, based at least in part on the slot information included in DCI, after a DCI duration of time. In some aspects, the MAC CE/DCI duration of time may be, for example,3milliseconds after receiving the MAC CE/DCI. In a situation where the UE120receives the DCI, indicating the respective position in the select available-slot list, prior to an expiration of the MAC CE duration of time, the UE120may utilize a default available-slot list, from among the plurality of available-slot lists, as the select available-slot list. In some aspects, in a situation where the UE120receives the DCI, indicating the respective position in the select available-slot list, prior to the expiration of the MAC CE duration of time, the UE120may utilize a previously utilized available-slot list, from among the plurality of available-slot lists, as the select available-slot list. In some aspects, the SRS configuration information may indicate an available-slot list including a plurality of integer values representing the respective select numbers of offset slots associated with the one or more available slots. In this case, the MAC CE and/or DCI received via downlink signaling may indicate a select subset of a plurality of integer values, from among the plurality of integer values, to be utilized by the UE120to determine the select available slot. Further, one or more bits in the MAC CE and/or DCI may indicate the respective position in the select subset of the plurality of integer values. Based at least in part on the indicated respective position, the UE120may determine the select number of offset slots, as discussed above. Utilizing the MAC CE to indicate at least the select subset of integer values, from among the plurality of integer values, may enable the BS110to avoid using the DCI for indicating the slot information associated with transmitting the SRS information, thereby avoiding DCI congestion (or PDCCH congestion). In some aspects, the SRS configuration information may enable the UE120to configure the UE120to transmit the SRS information based at least in part on a time of receipt of the dynamic signal (e.g., MAC CE and/or DCI). For instance, the UE120may transmit the SRS information, based at least in part on the slot information included in the MAC CE, after the MAC CE duration of time. Similarly, the UE120may transmit the SRS information, based at least in part on the slot information included in DCI, after a DCI duration of time. In some aspects, the MAC CE and/or DCI duration of time may be, for example, 3 milliseconds after receiving the MAC CE and/or DCI. In a situation where the UE120receives the DCI, triggering transmission of the SRS information, prior to the expiration of the MAC CE duration of time, the UE120may utilize a default subset of integer values, from among the plurality of integer values, as the select subset of integer values. In some aspects, in a situation where the UE120receives the DCI, triggering transmission of the SRS information, prior to the expiration of the MAC CE duration of time, the UE120may utilize a previously utilized subset of integer values, from among the plurality of integer values, as the select subset of integer values. In some aspects, the SRS configuration information and/or the slot information may enable the UE120to calculate (e.g., determine) the select number of offset slots. In some aspects, the SRS configuration information and/or the slot information may include a slot factor value and/or an initial available slot value, and may enable the UE120to calculate the select number (e.g., t) of offset slots based at least in part on the initial available slot value (e.g., V1, V2, . . . , VN) and the slot factor value. In some aspects, the relationship may be expressed as t=(initial available slot value*slot factor value). The UE120may transmit the SRS information during the select available slot that occurs t offset slots after the reference slot. In some aspects, the UE may transmit the SRS information during the select available slot that occurs t+1 offset slots after the reference slot. In some aspects, the slot factor value may be associated with a format related to a given slot. For instance, the slot factor may indicate whether the given slot is an uplink slot (e.g., U) reserved for uplink communications from the UE120to the BS110, or is a downlink slot (e.g., D) reserved for downlink communications from the BS110to the UE120. When the slot information indicates position2and a slot factor value of2, the UE120may calculate the select number (e.g., t) of offset slots as V2*2. In a situation where the value of V2is equal to 4, the UE120may calculate the select number of offset slots as 4*2=8. The UE120may transmit the SRS information during the select available slot that occurs 8 offset slots after the reference slot. In some aspects, the UE may transmit the SRS information during the select available slot that occurs 9 (e.g., t+1) offset slots after the reference slot. As shown by reference number540, the UE120may transmit the SRS information based at least in part on receiving the configuration information, the SRS configuration information, and/or the slot information, as discussed above. In some aspects, the UE120may utilize included transmission circuitry to transmit the SRS information and may utilize included reception circuitry to receive the configuration information, the SRS configuration information, and/or the slot information. The transmission circuitry may include, for example, one or more components (e.g., transmit processor264, TX MIMO processor266, modulator254, and/or antennas252) and the reception circuitry may include, for example, one or more components (e.g., receive processor258, MIMO detector256, demodulator254, and/or antennas252), as discussed above with respect toFIG.2. In some aspects, the UE120may include the UE120discussed with respect toFIG.2. By utilizing the dynamic determination of available slots for transmission of SRS information, as discussed herein, a UE may utilize the select (e.g., optimal) available slot to transmit the SRS information. In this way, the UE may enable the BS to adequately receive the SRS information and to adequately estimate a measure of quality associated with uplink communications. As a result, the BS may adequately receive the uplink communications from the UE and the data communication between the UE and the BS may continue uninterrupted. Additionally, transmitting the SRS information during the select available slot may enable efficient utilization of UE resources (e.g., amount of processing, utilization of memory, or the like) and network resources (e.g., bandwidth, subchannels, or the like) and data communication between the UE and the BS may be improved. As indicated above,FIGS.5and6are provided as examples. Other examples may differ from what is described with regard toFIGS.5and6. FIG.7is a diagram illustrating an example process700performed, for example, by a UE (e.g., UE120), in accordance with the present disclosure. Example process700is an example where the UE performs operations associated with dynamic determination of available slots for transmission of SRS information. As shown inFIG.7, in some aspects, process700may include receiving, from a base station, configuration information regarding one or more available slots associated with transmitting SRS information (block710). For example, the UE (e.g., using reception component802, depicted inFIG.8) may receive, from a base station, configuration information regarding one or more available slots associated with transmitting SRS information, as described above. As further shown inFIG.7, in some aspects, process700may include receiving, from the base station, dynamic downlink communication including slot information for determining a select available slot from among the one or more available slots (block720). For example, the UE (e.g., using reception component802, depicted inFIG.8) may receive, from the base station, dynamic downlink communication including slot information for determining a select available slot from among the one or more available slots, as described above. As further shown inFIG.7, in some aspects, process700may include transmitting, to the base station, the SRS information during the select available slot, determined based at least in part on the slot information and the configuration information (block730). For example, the UE (e.g., using transmission component804, depicted inFIG.8) may transmit, to the base station, the SRS information during the select available slot, determined based at least in part on the slot information and the configuration information, as described above. Process700may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein. In a first aspect, the one or more available slots are included in an available-slot list. In a second aspect, alone or in combination with the first aspect, process700includes determining the select available slot based at least in part on a slot factor, associated with a format related to a given slot, and an initial available slot value, the slot factor being received via the dynamic downlink communication and the initial available slot value being received via the configuration information. In a third aspect, alone or in combination with one or more of the first and second aspects, the slot information includes a slot factor indicating whether a given slot is an uplink slot reserved for uplink communications from the UE to the base station or is a downlink slot reserved for downlink communications from the base station to the UE. In a fourth aspect, alone or in combination with one or more of the first through third aspects, the dynamic downlink communication includes DCI received during a reference slot, the DCI including the slot information. In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the select available slot occurs a given quantity of slots after a reference slot, indicated by the configuration information. In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process700includes the dynamic downlink communication includes DCI, and one or more bits included in the DCI indicate the slot information. In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process700includes the dynamic downlink communication includes DCI, and one or more bits included in the DCI indicate the slot information, a quantity of the one or more bits being based at least in part on a quantity of the one or more available slots. In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the quantity of the one or more bits is based at least in part on a maximum number of available slots associated with a set of available slots of a plurality of sets of available slots. In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the plurality of sets of available slots are associated with at least one component carrier. In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process700includes the one or more available slots are included in a plurality of available-slot lists, and the dynamic downlink communication includes a MAC CE and DCI, the MAC CE indicating a given available-slot list from among the plurality of available-slot lists and the DCI including the slot information associated with determining the available slot from the given available-slot list indicated by the MAC CE. In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process700includes the one or more available slots are included in an available-slot list, and the dynamic downlink communication includes a MAC CE and DCI, the MAC CE indicating a subset of the one or more available slots and the DCI including the slot information associated with determining the available slot from the subset of the one or more available slots indicated by the MAC CE. AlthoughFIG.7shows example blocks of process700, in some aspects, process700may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.7. Additionally, or alternatively, two or more of the blocks of process700may be performed in parallel. FIG.8is a block diagram of an example apparatus800for wireless communication. The apparatus800may be a UE, or a UE may include the apparatus800. In some aspects, the apparatus800includes a reception component802and a transmission component804, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus800may communicate with another apparatus806(such as a UE, a base station, or another wireless communication device) using the reception component802and the transmission component804. As further shown, the apparatus800may include one or more of a determination component808, among other examples. In some aspects, the apparatus800may be configured to perform one or more operations described herein in connection withFIGS.3-6. Additionally, or alternatively, the apparatus800may be configured to perform one or more processes described herein, such as process700ofFIG.7. In some aspects, the apparatus800and/or one or more components shown inFIG.8may include one or more components of the UE described above in connection withFIG.2. Additionally, or alternatively, one or more components shown inFIG.8may be implemented within one or more components described above in connection withFIG.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component. The reception component802may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus806. The reception component802may provide received communications to one or more other components of the apparatus800. In some aspects, the reception component802may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus806. In some aspects, the reception component802may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection withFIG.2. The transmission component804may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus806. In some aspects, one or more other components of the apparatus806may generate communications and may provide the generated communications to the transmission component804for transmission to the apparatus806. In some aspects, the transmission component804may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus806. In some aspects, the transmission component804may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described above in connection withFIG.2. In some aspects, the transmission component804may be co-located with the reception component802in a transceiver. The reception component802may receive, from a base station, configuration information regarding one or more available slots associated with transmitting SRS information. The reception component802may receive, from the base station, dynamic downlink communication including slot information for determining a select available slot from among the one or more available slots. The transmission component804may transmit, to the base station, the SRS information during the select available slot, determined based at least in part on the slot information and the configuration information. The determination component808may determine the select available slot based at least in part on a slot factor, associated with a format related to a given slot, and an initial available slot value, the slot factor being received via the dynamic downlink communication and the initial available slot value being received via the configuration information. The number and arrangement of components shown inFIG.8are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.8. Furthermore, two or more components shown inFIG.8may be implemented within a single component, or a single component shown inFIG.8may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.8may perform one or more functions described as being performed by another set of components shown inFIG.8. The following provides an overview of some aspects of the present disclosure: Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a base station, configuration information regarding one or more available slots associated with transmitting sounding reference signal (SRS) information; receiving, from the base station, dynamic downlink communication including slot information for determining a select available slot from among the one or more available slots; and transmitting, to the base station, the SRS information during the select available slot, determined based at least in part on the slot information and the configuration information. Aspect 2: The method of aspect 1, wherein the one or more available slots are included in an available-slot list. Aspect 3: The method of any of aspects 1-2, further comprising: determining the select available slot based at least in part on a slot factor, associated with a format related to a given slot, and an initial available slot value, the slot factor being received via the dynamic downlink communication and the initial available slot value being received via the configuration information. Aspect 4: The method of any of aspects 1-3, wherein the slot information includes a slot factor indicating whether a given slot is an uplink slot reserved for uplink communications from the UE to the base station or is a downlink slot reserved for downlink communications from the base station to the UE. Aspect 5: The method of any of aspects 1-4, wherein the dynamic downlink communication includes downlink control information (DCI) received during a reference slot, the DCI including the slot information. Aspect 6: The method of any of aspects 1-5, wherein the select available slot occurs a given quantity of slots after a reference slot, indicated by the configuration information. Aspect 7: The method of any of aspects 1-6, wherein the dynamic downlink communication includes downlink control information (DCI), and one or more bits included in the DCI indicate the slot information. Aspect 8: The method of any of aspects 1-7, wherein the dynamic downlink communication includes downlink control information (DCI), and one or more bits included in the DCI indicate the slot information, a quantity of the one or more bits being based at least in part on a quantity of the one or more available slots. Aspect 9: The method of any of aspects 1-8, wherein the quantity of the one or more bits is based at least in part on a maximum number of available slots associated with a set of available slots of a plurality of sets of available slots. Aspect 10: The method of any of aspects 1-9, wherein the plurality of sets of available slots are associated with at least one component carrier. Aspect 11: The method of any of aspects 1-10, wherein the one or more available slots are included in a plurality of available-slot lists, and the dynamic downlink communication includes a medium access control control element (MAC CE) and downlink control information (DCI), the MAC CE indicating a given available-slot list from among the plurality of available-slot lists and the DCI including the slot information associated with determining the available slot from the given available-slot list indicated by the MAC CE. Aspect 12: The method of any of aspects 1-11, wherein the one or more available slots are included in an available-slot list, and the dynamic downlink communication includes a medium access control control element (MAC CE) and downlink control information (DCI), the MAC CE indicating a subset of the one or more available slots and the DCI including the slot information associated with determining the available slot from the subset of the one or more available slots indicated by the MAC CE. Aspect 13: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more aspects of aspects 1-12. Aspect 14: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more aspects of aspects 1-12. Aspect 15: An apparatus for wireless communication, comprising at least one means for performing the method of one or more aspects of aspects 1-12. Aspect 16: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 1-12. Aspect 17: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 1-12. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a processor is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein. As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like. Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c). No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”). | 65,794 |
11943749 | DETAILED DESCRIPTION As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or a program product. Accordingly, embodiments may take the form of an all-hardware embodiment, an all-software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects. For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Furthermore, one or more embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred to hereafter as “code”. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code. Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but is not limited to being, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the storage device may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. Reference throughout this specification to “one embodiment”, “an embodiment”, or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment”, “in an embodiment”, and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including”, “comprising”, “having”, and variations thereof mean “including but not limited to”, unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a”, “an”, and “the” also refer to “one or more” unless expressly specified otherwise. Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment. Aspects of various embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions—executed via the processor of the computer or other programmable data processing apparatus—create a means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams. The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams. The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagram. The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of different apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s). One skilled in the relevant art will recognize, however, that the flowchart diagrams need not necessarily be practiced in the sequence shown and are able to be practiced without one or more of the specific steps, or with other steps not shown. It should also be noted that, in some alternative implementations, the functions noted in the identified blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be substantially executed in concurrence, or the blocks may sometimes be executed in reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures. The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements. Enhancements of a mechanism for data transmission to BL/CE UEs should be studied to enable the legacy LTE physical control channel, which is not received/solved by the legacy BL/CE UEs, to carry data. In this way, spectrum utilization, data throughput, as well as transmission efficiency, can be increased for the new BL/CE UEs. In the present application, method and apparatus for data transmission to BL/CE UEs are disclosed, which provides a few mechanisms for mapping data into both the legacy LTE physical control channel and physical data channels. Further, the compatibility with the legacy BL/CE UEs is also considered. It should be noted that the physical channel, resource block, and physical resource block can be used alternatively in the present application. The legacy LTE physical control channel includes but is not limited to PDCCH, PHICH, PCFICH, while the physical share channel includes but is not limited to PDSCH. FIG.1is a schematic diagram illustrating data mapping into different types of physical channels. An illustrative diagram for a resource block is shown inFIG.1, in which the lateral axis represents a time domain while the vertical axis represents a frequency domain. In one embodiment, the resource block is composed of a first resource block, which can be used for PDSCH to carry data generated from transport blocks (TB), and a second resource block, which can be used for legacy control channel such as PDCCH to carry signaling in a physical layer. As shown inFIG.1, the first resource block is from a symbol with an indicated index to a symbol with an end index of the resource block, and the second resource block is from a symbol with a start index to a symbol with the indicated index minus one of the resource block. The first resource block is used for PDSCH transmission, and the second resource block is used for legacy control channel such as PDCCH. In a particular MTC case, the second resource block can also use for PDSCH/data transmission. In another aspect, a resource block composed of both the first resource block and second resource block includes a few subcarriers in frequency domain, for example, 12 subcarriers are included in one resource block. As shown inFIG.1, an example of the resource block includes a region span of 14 symbols in time domain and 12 subcarriers in frequency domain. Particularly, the first resource block includes a region span of the last 11 symbols (symbol #3˜symbol #13) in time domain and 12 subcarriers in frequency domain, and the second resource includes a region span of the first 3 symbols (symbol #0˜symbol #2) in time domain and 12 subcarriers in the frequency domain, given that the indicated index is 3. It should be understood that the first resource blocks and second resource block may include different regions determined by the indicated index, for example, the first resource block may include a region span of 12 symbols in time domain and 12 subscribers in frequency domain, in the case that the indicated index is 2. As shown inFIG.1, part A of the data in the form of symbols is mapped to the first resource block; part B of the data is mapped to the second resource block. The legacy BL/CE UEs are able to receive/resolve part A of the data in the first resource block. Correspondingly, the new BL/CE UEs are able to both receive/resolve part A of the data in the first resource block and part B of the data in the second resource block. Therefore, an extra gain for decoding can be obtained in the case that part B is a portion of part A of the data. Alternatively, spectrum utilization and/or data throughput can be increased if additional source bits are supported in the data, which will be described hereinafter. FIG.2is a simple flow illustrating data processing in the physical layer of network equipment such as an eNB or a gNB. It should be understood that the processing modules shown inFIG.2are not limited to the ones shown. Particularly, additional modules can be added for data processing in the physical layer; alternatively, some shown modules can be removed from the procedure of data processing shown inFIG.1. As shown inFIG.2, transport block containing source bits is received from the MAC layer. A size of source bits is determined based on Table 2 as a predefined table, which is shown inFIG.7B. With regard to the new BL/CE UEs, a size of source bits can be scaled based on a first scaling factor to increase data throughput, which will be described hereinafter. CRC is computed for the transport block and appended to the source block bits in order to realize error detection on the UE side. Then segmentation is performed on the transport block in the case that transport block size is more than an allowed code block size. In the case of eMTC and/or NB-IoT, in which the maximum size of transport block is 1000, the segmentation is not needed. The bits contained in segmented transport block is encoded in the module of channel coding to generate coded bits. To be more particular, the module of channel coding may include a coder such as turbo coder, and a circular buffer. The coded bits from a coder are concentrated into a circular buffer for the coder to be selected. A few mechanisms for selection of coded bits from the circular buffer are described hereinafter. In one embodiment, turbo coded bits consist of three interleaving bit streams, followed by the collection of bits into a circular buffer. The output bits from the circular buffer are determined by the particular bit-selection mechanism as described hereinafter. The coded bits are then scrambled for the purpose of interference randomization as part of the algorithm executed in the Scrambling block. The scrambled bits are modulated according to the modulation order specified by a Modulation and Coding Schema (MCS) index IMCSin Table 1 shown inFIG.7Ato generate symbols (for example, QPSK corresponding to modulation order 2, 16 QAM corresponding to modulation order 4, or 64 QAM corresponding to modulation order 6) as data as defined inFIG.1. The symbols are mapped into the resource blocks. With regard to the new BL/CE UEs, a few mechanisms for mapping data into both the first resource block and the second resource block are described hereinafter. A baseband signal is generated through Inverse fast Fourier transform (IFFT), a Cyclic Prefix (CP) is added to the signal in the time domain, and the signal is modulated to a Radio Frequency (not shown) for transmission, which is known for one skilled in the relevant art. Enhancements on the determination of transport block size, selection of bits from the circular buffer, as well as mapping data into the resource block, are functions identified in the dashed frames shown inFIG.2and further described inFIGS.3-5. FIG.3is a call flow illustrating data mapping into resource blocks according to a first embodiment. The call flow is implemented at network equipment such as eNB/gNB. It should be understood that a inverse call flow is implemented at UE. In step S301, the network equipment determines a size of source bits based on a first number of resource blocks and a predefined table. Particularly, the network equipment assigns an MCS index IMCSand a first number of resource blocks NPRBon the basis of Channel Quality Indication (CQI), which is based on values such as RSRP/RSRQ/RSSI reported from UE and other information for downlink transmission on PDSCH. Subsequently, the network equipment determines the TBS index ITBSbased on the assigned MCS index IMCSdefined in ‘Table 1 Modulation and TBS Index’ shown inFIG.7A(only a portion thereof is included herein for the purpose of brevity), which is described in 3GPP TS 36.213 and learns a corresponding modulation order which is used in the modulation module shown inFIG.2. Finally, the network equipment determines a size of source bits based on the determined ITBSand assigned NPRBdefined in ‘Table 2 Determination of Transport Block Size’ (shown inFIG.7B) as the predefined table mentioned above. This is also described in 3GPP TS 36.213 (only a portion thereof is included herein for the purpose of brevity). In step S302, the network equipment performs encoding on the source bits to generate the coded bits. In step S303, the network equipment selects the coded bits from the circular buffer for the coder. As shown inFIG.6, which is a schematic diagram illustrating a circular buffer for a coder applicable for the embodiments, coded bits stored in different sections of the circular buffer are associated with different Redundancy Versions (RV), for example marked by RV0, RV1, RV2 and RV3 and specified by a different starting address, are selected to be scrambled, modulated and then mapped into different resource blocks later. Usually, coded bits associated with RV0 are selected for initial transmission, therefore, the starting address of RV0 is also known as the starting address of the circular buffer. It should be understood that although the circular buffer has been described to have four section associated with4RVs (i.e. RV0, RV1, RV2 and RV3) are shown inFIG.6, the number of sections of the circular buffer and hence, the number of associated RVs is not limited to four. In another embodiment, in order to increase spectrum utilization/data throughput, a second portion of coded bits, which may be stored in RV section of the circular buffer described inFIG.6and marked by RVx_y. is to be scrambled, modulated, and then mapped into the second resource block later. Simultaneously, the first portion of coded bits, which is stored in RV section of the circular buffer marked by RVx, is to be scrambled, modulated and then mapped into the first resource blocks later, wherein, ‘x’ indicates a starting index of RV section of the circular buffer loaded with the first portion of coded bits, for example RV0, RV1, RV2 and RV3. On the contrary, ‘y’ indicates a different solution for selecting coded bits corresponding to the second resource block. Particularly, with regard to RVx section of the circular buffer loaded with the first portion of coded bits, there is more than one solution for selecting the second portion of coded bits. For example, in the case that coded bits stored in the portion of the circular buffer corresponding to RV1 are selected to be scrambled, modulated, and then mapped into the second resource block/PDSCH shown inFIG.1, coded bits stored in one of RV1_0, RV1_1, RV1_2 and RV1_3 portions of the circular buffer can be selected to be scrambled, modulated, and then mapped into the second resource block/PDCCH as shown inFIG.1. Further, assuming the first portion of coded bits mapping to the first resource block has a first unit length ‘M’ and the second portion of coded bits mapping to the second resource block has a second unit length ‘N’, it's possible that the start address of RVx_y is determined according to the following:the start address of RV1_0 is followed by the end address of RV1;the starting address of RV1_1 is the start address of RV1;the address offset between the starting address of RV1_2 and RV0 is multiple times M plus multiple times N;the starting address of RV1_3 is followed by the end address of RV0_1, which is corresponding to RV0. In summary, the first portion of coded bits has a first unit length, and is selected from a starting address plus zero or at least one times the first unit length of a circular buffer for a coder. That is, the starting address of the first portion of coded bits ‘Add1’ is determined according to Expression 1 below, where ‘Add0’ is the starting address of the circular buffer for the coder. For example, as mentioned above, the starting address of RV0 is usually used as the starting address of the circular buffer. ‘M’ is the length of the first portion of coded bits, which is the first unit length mentioned above. “x” is a non-negative integer, i.e. x=0, 1, 2, . . . Add1=Add0+x×MExpression 1 In another aspect, the second portion of coded bits has a second unit length and is selected from the starting address plus zero or at least one times the first unit length plus zero or at least one times the second unit length of the circular buffer. That is, the starting address of the second portion of coded bits ‘Add2’ is determined according to Expression 2, where ‘Add0’ is the starting address of the circular buffer for the coder. As mentioned above, the starting address of RV0 is usually used as the starting address of the circular buffer. ‘M’ is the length of the first portion of coded bits, which is the first unit length mentioned above. ‘N’ is the length of the second portion of coded bits, which is the second unit length mentioned above. Both ‘x’ and ‘y’ are non-negative integers, i.e. x=0, 1, 2, . . . , Add2=Add0+x×M+y×NExpression 2 Further, the first unit length ‘M’ is determined according to at least one of a type of resource block, the indicated index and a first modulation type such as QPSK, 16 QAM or 64 QAM. The second unit length ‘N’ is determined according to at least one of a type of resource block, the indicated index and a second modulation type such as QPSK, 16 QAM or 64 QAM. For example, in the case that the transport block is transmitted over DwPTS of the special subframe in frame structure type 2, the time duration for the corresponding resource block is configured by a higher layer, which is also known that different types of resource blocks may occupy different time domains and/or frequency domains. Further, the available resource elements of the first resource block is determined by the symbols with the indicated index to the symbols with the end index of the first resource block. The available resource elements of the second resource block is determined by the symbol with the start index to the symbols with the indicated index minus 1. In step S304, the coded bits are scrambled for the purpose of interference randomization. In step S305, the scramble bits are modulated according to the modulation order Qmor Q′mspecified by the Modulation and Coding Schema (MCS) index IMCSin ‘Table 1 Modulation vs. TBS Index’ shown inFIG.7A. In step S306, the network equipment maps the data into a first resource block and a second resource block. In one embodiment, the network equipment maps the data, which is scrambled and modulated from a first portion of the coded bits, into the first resource block, which is from a symbol with the indicated index to a symbol with the end index of the resource block. Then it maps the data, which is scrambled and modulated from a second portion of the coded bits, into the second resource block, which is from a symbol with the start index to a symbol with the indicated index minus one of the resource block. In this way, the legacy BL/CE UEs are still able to receive/resolve data in the first resource block according to the current mechanism, while the new BL/CE UEs are able to receive/resolve data in both the first resource block and the second resource block. Therefore, the spectrum utilization/data throughput is increased for the new BL/CE UEs. In another embodiment, the network equipment maps the data, which is scrambled and modulated from a first portion of the coded bits, into the first resource block, which is from a symbol with the indicated index to a symbol with the end index of the resource block; and maps a portion of the data in the first resource block into the second resource block, which is from a symbol with the start index to a symbol with the indicated index minus one of the resource block. In this way, the legacy BL/CE UEs are still able to receive/resolve data in PDSCH as/from the first resource block according to the current mechanism, while the new BL/CE UEs are able to receive/resolve data in both the first resource block and the second resource block to obtain extra gains for decoding. To be more specific, the network equipment maps the data, which is scrambled and modulated from the coded bits, into the first resource block, which is from a symbol of the indicated index to a symbol of an end index of the resource block; and continues to map the data into the second resource block, which is from a symbol of a start index to a symbol of the indicated index minus one of the resource block. In this way, the legacy BL/CE UEs are still able to receive/resolve data in the first resource block according to the current mechanism, while the new BL/CE UEs are able to receive/resolve data in both the first resource block and the second resource block to obtain extra gains for decoding. In a scenario for eMTC, a transport block directed to eMTC UEs is transmitted multiple times by the network equipment. Usually, the network equipment indicates a first repetition number in control signal, so that the eMTC UEs is able to expect the repetition number of the received transport block. In step S307, optionally, the network equipment indicates a first repetition number in DCI format, and configures the second scaling factor by RRC signaling or the second scaling factor is predefined. The network equipment transmits the data in the resource blocks by a second repetition number related to a second scaling factor. Then BL/CE UEs can derive the actual repetition number (i.e. the second repetition number) according to the first repetition number and the second scaling factor. To be more specific, the second repetition number is a product of the first repetition number and the scaling factor. Assuming that the indicated index is 3, the start index of the resource block is 0 and the end index of the resource block is 13, so the second resource block occupies 3 symbols and the first resource block occupies 11 symbols, yielding the second scaling factor of 11/14. In another example, assuming that the indicated index is 2, the start index of the resource block is 0 and the end index of the resource block is 13, so the second resource block occupies 2 symbols and the first resource block occupies 12 symbols, yielding the second scaling factor of 12/14. Therefore, it should be understood that the second scaling factor is related to the indicated index. However, the second scaling factor may be predefined value or may be also determined according to at least one of followings: a type of Cyclic Prefix (CP), a special subframe configuration defined in 3GPP TS36.211, and the indicated index. Particularly, the second scaling factor is 128*0.75 for special subframe configurations. Further, the calculated repetition number meets at least one of followings: not less than a fifth threshold and not more than a sixth threshold. Since the repetition number for transmission of PDSCH may be reduced, early reception of ACK/NACK for transmission of PDSCH based on HARQ can be achieved from the prospective of the network equipment. In another aspect, althoughFIG.3shows a call flow implemented at the network equipment such as eNB or gNB, it should be understood that a inverse call flow is implemented at UE. Particularly, BL/CE UEs first receives the data in a first resource block and a second resource block, both of which form a resource block, wherein the first resource block is from a symbol with an indicated index to a symbol with an end index of the resource block, the second resource block is from a symbol with a start index to a symbol with the indicated index minus one of the resource block. BL/CE UEs should obtain (demodulates and descrambles) the data in a sequence same as that described in step S306. FIG.4is a call flow illustrating data mapping into resource blocks according to a second embodiment. The enhancement of the call flow inFIG.4against that inFIG.3is that the size of resource bits is adjusted, given that the second resource block also carries user data. In step S401, the network equipment assigns a first number of resource blocks NPRB, as well as an MCS index IMCS, on the basis of Channel Quality Indication (CQI), which is based on values such as RSRP/RSRQ/RSSI reported from UE and other information for downlink transmission on PDSCH. In step S402, the network equipment determines a second number of resource blocks based on a first scaling factor and the first number of resource blocks. Particularly, the second number of resource blocks is related to the product of the first number of resource blocks and the scaling factor. To be more specific, the second number of resource blocks NPRB′ is obtained according to expression 3, given that the maximum number of (physical) resource blocks is 6 for eMTC UE NPRB′=min{max{└NPRB×α┘,1},6} expression 3 Wherein, α is the first scaling factor. Assuming that the indicated index is 3, the start index of the resource block is 0 and the end index of the resource block is 13, so the second resource block occupies 3 symbols and the first resource block occupies 11 symbols, yielding the first scaling factor of 14/11. In another example, assuming that the indicated index is 2, the start index of the resource block is 0 and the end index of the resource block is 13, so the second resource block occupies 2 symbols and the first resource block occupies 12 symbols, yielding the first scaling factor of 14/11. Therefore, it should be understood that the first scaling factor is related to the indicated index. However, the first scaling factor may be predefined value or may be also determined according to at least one of following: a type of Cyclic Prefix (CP), a special subframe configuration, and the indicated index. Particularly, the first scaling factor α may be 0.75 for special subframe configurations 9 and 10 with normal cyclic prefix or special subframe configuration 7 with extended cyclic prefix the type and is 0.375 for other special subframe configurations. According to expression 3, the second number of resource blocks has both a maximum value (i.e. 6) and a minimum value (i.e. 1). However, the second number of resource blocks may be limited by either the maximum value or the minimum value. That is, the second number of resource blocks meets at least one of following: not less than a first threshold and not more than a second threshold. In step S403, the network equipment determines a size of source bits based on a second number of resource blocks NPRB′ and ‘Table 2 Determination of Transport Block Size’ (shown inFIG.7B) as the predefined table mentioned above. For example, assuming that α is 14/11, a first number of resource blocks NPRBis 4 and MCS index is 6, then ITBSis 6 according to the MCS index with the value of 6 in Table 1 shown inFIG.7A, the second number of resource blocks NPRB′ is 5 according to expression 3. Therefore the size of source bits is 504 according to the TBS index ITBSwith a value of 6 and the second number of resource blocks NPRB′ with a value of 5 in Table 2 shown inFIG.7B. In another aspect, without the application of the bits scaling, the size of source bits is 392 according to the TBS index ITBSwith a value of 6 and the first number of resource blocks NPRBwith a value of 4 in Table 2 shown inFIG.7B. The descriptions for steps S404-S409inFIG.4are similar with that for steps S302-S307inFIG.3. Thus, the descriptions thereof are omitted for the purpose of brevity. FIG.5is a call flow illustrating data mapping into resource blocks according to a third embodiment. The enhancement of the call flow inFIG.5against that inFIG.3is that the size of resource bits is adjusted, given that the second resource block also carries user data. In step S501, the network equipment assigns a first number of resource blocks NPRB, as well as an MCS index IMCS, on the basis of Channel Quality Indication (CQI), which is based on values such as RSRP/RSRQ/RSSI reported from UE and other information for downlink transmission on PDSCH. In step S502, the network equipment determines a first size of source bits based on ‘Table 2 Determination of Transport Block Size’ (shown inFIG.7B) as the predefined table and the first number of resource blocks. In step S503, the network equipment determines a size of source bits based on the first size of source bits NTBSand a first scaling factor. Particularly, the size of source bits is related to the product of the first size of source bits and the scaling factor. To be more specific, the size of source bits NTBS′ is obtained according to expression 4, given that the maximum number of (physical) resource blocks is 6 for eMTC UE NTBS′=min{max{└NTBS×α┘,40},1000} expression 4 Wherein, α is the first scaling factor. Assuming that the indicated index is 3, the start index of the resource block is 0 and the end index of the resource block is 13, so the second resource block occupies 3 symbols and the first resource block occupies 11 symbols, yielding the first scaling factor of 14/11. In another example, assuming that the indicated index is 2, the start index of the resource block is 0 and the end index of the resource block is 13, so the second resource block occupies 2 symbols and the first resource block occupies 12 symbols, yielding the first scaling factor of 14/11. Therefore, it should be understood that the first scaling factor is related to the indicated index. However, the first scaling factor may be predefined value or may be also determined according to at least one of following: a type of Cyclic Prefix (CP), a special subframe configuration, and the indicated index. Particularly, the first scaling factor α may be 0.75 for special subframe configurations 9 and 10 with normal cyclic prefix or special subframe configuration 7 with extended cyclic prefix the type and is 0.375 for other special subframe configurations. According to expression 4, the size of source bits has both a maximum value (i.e. 1000) and a minimum value (i.e. 40). However, the size of source bits may be limited by either the maximum value or the minimum value. That is, the size of source bits meets at least one of following: not less than a third threshold and not more than a fourth threshold. In another aspect, in order to comply with the current design for size of source bits, the size of source bits NTBS′ is rounded to the nearest value in the predefined table, for example, it is rounded down to the nearest value in the predefined table. For example, assuming that a is 14/11, a first number of resource blocks NPRBis 4 and MCS index is 6, then IFBsis 6 according to the MCS index with the value of 6 in Table 1 shown inFIG.7A, the first size of source bits is 392 according to the TBS index ITBSwith a value of 6 and the first number of resource blocks NPRBwith a value of 4 in Table 2 shown inFIG.7B, which is also a size of source bits without application of the bits scaling. Therefore, the size of source bits is 498 calculated by expression 4 and then is adjusted to be 472 by rounding down 498 to the nearest value in Table 2. The descriptions for steps S504-S509inFIG.5are similar with those for steps S302-S307inFIG.3. Thus, the descriptions therein are omitted for the purpose of brevity. One skilled in the relevant art will recognize that the process described inFIGS.2-4does not need to be practiced in the sequence shown in the Figures, and may be practiced without one or more of the specific steps or with other steps not shown in the Figures. FIG.8is a schematic block diagram illustrating components of a UE such as BL/CE UEs according to one embodiment. UE800is an embodiment of the UE described fromFIG.2toFIG.4. Furthermore, UE800may include a processor802, a memory804, and a transceiver810. In some embodiments, UE800may include an input device806and/or a display808. In certain embodiments, the input device806and the display808may be combined into a single device, such as a touch screen. The processor802, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor802may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor802executes instructions stored in the memory804to perform the methods and routines described herein. The processor802is communicatively coupled to the memory804, the input device806, the display808, and the transceiver810. In some embodiments, the processor802controls the transceiver810to receive various configuration and data from Network Equipment900. In certain embodiments, the processor802may monitor DL signals received via the transceiver810for specific messages. The memory804, in one embodiment, is a computer readable storage medium. In some embodiments, the memory804includes volatile computer storage media. For example, the memory804may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory804includes non-volatile computer storage media. For example, the memory804may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory804includes both volatile and non-volatile computer storage media. In some embodiments, the memory804stores data relating to trigger conditions for transmitting the measurement report to Network Equipment800. In some embodiments, the memory804also stores program code and related data, such as an operating system or other controller algorithms operating on UE800. UE800may optionally include an input device806. The input device806, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device806may be integrated with the display808, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device806includes a touch screen such that text may be input using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, the input device806includes two or more different devices, such as a keyboard and a touch panel. In certain embodiments, the input device806may include one or more sensors for monitoring an environment of UE800. UE800may optionally include a display808. The display808, in one embodiment, may include any known electronically controllable display or display device. The display808may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display808includes an electronic display capable of outputting visual data to a user. For example, the display808may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display808may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display808may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like. In certain embodiments, the display808may include one or more speakers for producing sound. For example, the display808may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display808includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display808may be integrated with the input device806. For example, the input device806and display808may form a touch screen or similar touch-sensitive display. In other embodiments, the display808may be located near the input device806. The transceiver810, in one embodiment, is configured to communicate wirelessly with Network Equipment800. In certain embodiments, the transceiver810comprises a transmitter812and a receiver814. The transmitter812is used to transmit UL communication signals to Network Equipment900and the receiver814is used to receive DL communication signals from Network Equipment900. For example, the transmitter812may transmit a HARQ-ACK codebook including feedbacks for one or more DL transmissions. As another example, the receiver814may receive various configurations/data from Network Equipment900. The transmitter812and the receiver814may be any suitable types of transmitters and receivers. Although only one transmitter812and one receiver814are illustrated, the transceiver810may have any suitable number of transmitters812and receivers814. For example, in some embodiments, UE800includes a plurality of transmitter812and receiver814pairs for communicating on a plurality of wireless networks and/or radio frequency bands, each transmitter812and receiver814pair configured to communicate on a different wireless network and/or radio frequency band than the other transmitter812and receiver814pairs. FIG.9is a schematic block diagram illustrating components of a network equipment according to one embodiment. Network Equipment900includes one embodiment of eNB/gNB described fromFIG.2toFIG.4. Furthermore, Network Equipment900may include a processor902, a memory904, an input device906, a display908, and a transceiver910. As may be appreciated, the processor902, the memory904, the input device906, and the display908may be substantially similar to the processor902, the memory904, the input device906, and the display908of UE800, respectively. In some embodiments, the processor902controls the transceiver910to transmit DL signals/data to UE800. The processor902may also control the transceiver910to receive UL signals/data from UE800. For example, the processor902may control the transceiver910to receive a HARQ-ACK codebook including feedbacks for one or more DL transmissions. In another example, the processor902may control the transceiver910to transmit a DL signals for various configurations to UE800, as described above. The transceiver910, in one embodiment, is configured to communicate wirelessly with UE800. In certain embodiments, the transceiver910comprises a transmitter912and a receiver914. The transmitter912is used to transmit DL communication signals to UE800and the receiver914is used to receive UL communication signals from UE800. For example, the receivers914may receive a HARQ-ACK codebook from UE800. As another example, the transmitter912may transmit the various configurations/data of Network Equipment900. The transceiver910may communicate simultaneously with a plurality of UE800. For example, the transmitter912may transmit DL communication signals to UE800. As another example, the receiver914may simultaneously receive UL communication signals from UE800. The transmitter912and the receiver914may be any suitable types of transmitters and receivers. Although only one transmitter912and one receiver914are illustrated, the transceiver910may have any suitable number of transmitters912and receivers914. For example, Network Equipment800may serve multiple cells and/or cell sectors, wherein the transceiver910includes a transmitter912and a receiver914for each cell or cell sector. Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. | 43,233 |
11943750 | BEST MODE Terms used in the specification adopt general terms which are currently widely used by considering functions in the present invention, but the terms may be changed depending on an intention of those skilled in the art, customs, and emergence of new technology. Further, in a specific case, there is a term arbitrarily selected by an applicant and in this case, a meaning thereof will be described in a corresponding description part of the invention. Accordingly, it should be revealed that a term used in the specification should be analyzed based on not just a name of the term but a substantial meaning of the term and contents throughout the specification. Throughout this specification and the claims that follow, when it is described that an element is “coupled” to another element, the element may be “directly coupled” to the other element or “electrically coupled” to the other element through a third element. Further, unless explicitly described to the contrary, the word “comprise” and variations such as “comprises” or “comprising”, will be understood to imply the inclusion of stated elements but not the exclusion of any other elements. Moreover, limitations such as “or more” or “or less” based on a specific threshold may be appropriately substituted with “more than” or “less than”, respectively. This application claims priority to and the benefit of Korean Patent Application Nos. 10-2014-0063356, 10-2014-0063359 and 10-2014-0148477 filed in the Korean Intellectual Property Office and the embodiments and mentioned items described in the respective applications are included in the Detailed Description of the present application. FIG.1is a diagram illustrating a wireless LAN system according to an embodiment of the present invention. The wireless LAN system includes one or more basic service sets (BSS) and the BSS represents a set of apparatuses which are successfully synchronized with each other to communicate with each other. In general, the BSS may be classified into an infrastructure BSS and an independent BSS (IBSS) andFIG.1illustrates the infrastructure BSS between them. As illustrated inFIG.1, the infrastructure BSS (BSS1 and BSS2) includes one or more stations STA1, STA2, STA3, STA4, and STA5, access points PCP/AP-1 and PCP/AP-2 which are stations providing a distribution service, and a distribution system (DS) connecting the multiple access points PCP/AP-1 and PCP/AP-2. The station (STA) is a predetermined device including medium access control (MAC) following a regulation of an IEEE 802.11 standard and a physical layer interface for a radio medium, and includes both a non-access point (non-AP) station and an access point (AP) in a broad sense. Further, in the present specification, as a concept including all wireless LAN communication devices such as the station and the AP, a term ‘terminal’ may be used. A station for wireless communication includes a processor and a transceiver and according to the embodiment, may further include a user interface unit and a display unit. The processor may generate a frame to be transmitted through a wireless network or process a frame received through the wireless network and besides, perform various processing for controlling the station. In addition, the transceiver is functionally connected with the processor and transmits and receives frames through the wireless network for the station. The access point (AP) is an entity that provides access to the distribution system (DS) via wireless medium for the station associated therewith. In the infrastructure BSS, communication among non-AP stations is, in principle, performed via the AP, but when a direct link is configured, direct communication is enabled even among the non-AP stations. Meanwhile, in the present invention, the AP is used as a concept including a personal BSS coordination point (PCP) and may include concepts including a centralized controller, a base station (BS), a node-B, a base transceiver system (BTS), and a site controller in a broad sense. A plurality of infrastructure BSSs may be connected with each other through the distribution system (DS). In this case, a plurality of BSSs connected through the distribution system is referred to as an extended service set (ESS). FIG.2illustrates an independent BSS which is a wireless LAN system according to another embodiment of the present invention. In the embodiment ofFIG.2, duplicative description of parts, which are the same as or correspond to the embodiment ofFIG.1, will be omitted. Since a BSS3 illustrated inFIG.2is the independent BSS and does not include the AP, all stations STA6 and STA7 are not connected with the AP. The independent BSS is not permitted to access the distribution system and forms a self-contained network. In the independent BSS, the respective stations STA6 and STA7 may be directly connected with each other. FIG.3is a block diagram illustrating a configuration of a station100according to an embodiment of the present invention. As illustrated inFIG.3, the station100according to the embodiment of the present invention may include a processor110, a transceiver120, a user interface unit140, a display unit150, and a memory160. First, the transceiver120transmits and receives a radio signal such as a wireless LAN packet, or the like and may be embedded in the station100or provided as an exterior. According to the embodiment, the transceiver120may include at least one transmit/receive module using different frequency bands. For example, the transceiver120may include transmit/receive modules having different frequency bands such as 2.4 GHz, 5 GHz, and 60 GHz. According to an embodiment, the station100may include a transmit/receive module using a frequency band of 6 GHz or more and a transmit/receive module using a frequency band of 6 GHz or less. The respective transmit/receive modules may perform wireless communication with the AP or an external station according to a wireless LAN standard of a frequency band supported by the corresponding transmit/receive module. The transceiver120may operate only one transmit/receive module at a time or simultaneously operate multiple transmit/receive modules together according to the performance and requirements of the station100. When the station100includes a plurality of transmit/receive modules, each transmit/receive module may be implemented by independent elements or a plurality of modules may be integrated into one chip. Next, the user interface unit140includes various types of input/output means provided in the station100. That is, the user interface unit140may receive a user input by using various input means and the processor110may control the station100based on the received user input. Further, the user interface unit140may perform output based on a command of the processor110by using various output means. Next, the display unit150outputs an image on a display screen. The display unit150may output various display objects such as contents executed by the processor110or a user interface based on a control command of the processor110, and the like. Further, the memory160stores a control program used in the station100and various resulting data. The control program may include an access program required for the station100to access the AP or the external station. The processor110of the present invention may execute various commands or programs and process data in the station100. Further, the processor110may control the respective units of the station100and control data transmission/reception among the units. According to the embodiment of the present invention, the processor110may execute the program for accessing the AP stored in the memory160and receive a communication configuration message transmitted by the AP. Further, the processor110may read information on a priority condition of the station100included in the communication configuration message and request the access to the AP based on the information on the priority condition of the station100. The processor110of the present invention may represent a main control unit of the station100and according to the embodiment, the processor110may represent a control unit for individually controlling some component of the station100, for example, the transceiver120, and the like. The processor110controls various operations of radio signal transmission/reception of the station100according to the embodiment of the present invention. A detailed embodiment thereof will be described below. The station100illustrated inFIG.3is a block diagram according to an embodiment of the present invention, where separate blocks are illustrated as logically distinguished elements of the device. Accordingly, the elements of the device may be mounted in a single chip or multiple chips depending on design of the device. For example, the processor110and the transceiver120may be implemented while being integrated into a single chip or implemented as a separate chip. Further, in the embodiment of the present invention, some components of the station100, for example, the user interface unit140and the display unit150may be optionally provided in the station100. FIG.4is a block diagram illustrating a configuration of an AP200according to an embodiment of the present invention. As illustrated inFIG.4, the AP200according to the embodiment of the present invention may include a processor210, a transceiver220, and a memory260. InFIG.4, among the components of the AP200, duplicative description of parts which are the same as or correspond to the components of the station100ofFIG.2will be omitted. Referring toFIG.4, the AP200according to the present invention includes the transceiver220for operating the BSS in at least one frequency band. As described in the embodiment ofFIG.3, the transceiver220of the AP200may also include a plurality of transmit/receive modules using different frequency bands. That is, the AP200according to the embodiment of the present invention may include two or more transmit/receive modules among different frequency bands, for example, 2.4 GHz, 5 GHz, and 60 GHz together. Preferably, the AP200may include a transmit/receive module using a frequency band of 6 GHz or more and a transmit/receive module using a frequency band of 6 GHz or less. The respective transmit/receive modules may perform wireless communication with the station according to a wireless LAN standard of a frequency band supported by the corresponding transmit/receive module. The transceiver220may operate only one transmit/receive module at a time or simultaneously operate multiple transmit/receive modules together according to the performance and requirements of the AP200. Next, the memory260stores a control program used in the AP200and various resulting data. The control program may include an access program for managing the access of the station. Further, the processor210may control the respective units of the AP200and control data transmission/reception among the units. According to the embodiment of the present invention, the processor210may execute the program for accessing the station stored in the memory260and transmit communication configuration messages for one or more stations. In this case, the communication configuration messages may include information about access priority conditions of the respective stations. Further, the processor210performs an access configuration according to an access request of the station. The processor210controls various operations such as radio signal transmission/reception of the AP200according to the embodiment of the present invention. A detailed embodiment thereof will be described below. FIG.5is a diagram schematically illustrating a process in which a STA sets a link with an AP. Referring toFIG.5, the link between the STA100and the AP200is set through three steps of scanning, authentication, and association in a broad way. First, the scanning step is a step in which the STA100obtains access information of BSS operated by the AP200. A method for performing the scanning includes a passive scanning method in which the AP200obtains information by using a beacon message (S101) which is periodically transmitted and an active scanning method in which the STA100transmits a probe request to the AP (S103) and obtains access information by receiving a probe response from the AP (S105). The STA100that successfully receives wireless access information in the scanning step performs the authentication step by transmitting an authentication request (S107a) and receiving an authentication response from the AP200(S107b). After the authentication step is performed, the STA100performs the association step by transmitting an association request (S109a) and receiving an association response from the AP200(S109b). Meanwhile, an 802.1X based authentication step (S111) and an IP address obtaining step (S113) through DHCP may be additionally performed. InFIG.5, the authentication server300is a server that processes 802.1X based authentication with the STA100and may be present in physical association with the AP200or present as a separate server. FIG.6is a diagram illustrating a carrier sense multiple access (CSMA)/collision avoidance (CA) method used in wireless LAN communication. A terminal that performs a wireless LAN communication checks whether a channel is busy by performing carrier sensing before transmitting data. When a radio signal having a predetermined strength or more is sensed, it is determined that the corresponding channel is busy and the terminal delays the access to the corresponding channel. Such a process is referred to as clear channel assessment (CCA) and a level to decide whether the corresponding signal is sensed is referred to as a CCA threshold. When a radio signal having the CCA threshold or more, which is received by the terminal, indicates the corresponding terminal as a receiver, the terminal processes the received radio signal. Meanwhile, when a radio signal is not sensed in the corresponding channel or a radio signal having a strength smaller than the CCA threshold is sensed, it is determined that the channel is idle. When it is determined that the channel is idle, each terminal having data to be transmitted performs a backoff procedure after an interframe space (IFS) time depending on a situation of each terminal, for instance, an arbitration IFS (AIFS), a PCF IFS (PIFS), or the like elapses. According to the embodiment, the AIFS may be used as a component which substitutes for the existing DCF IFS (DIFS). Each terminal stands by while decreasing slot time(s) as long as a random number allocated to the corresponding terminal during an interval of an idle state of the channel and a terminal that completely exhausts the slot time(s) attempts to access the corresponding channel. As such, an interval in which each terminal performs the backoff procedure is referred to as a contention window interval. When a specific terminal successfully accesses the channel, the corresponding terminal may transmit data through the channel. However, when the terminal which attempts the access collides with another terminal, the terminals which collide with each other are allocated with new random numbers, respectively to perform the backoff procedure again. According to an embodiment, a random number newly allocated to each terminal may be decided within a range (2*CW) which is twice larger than a range (a contention window, CW) of a random number which the corresponding terminal is previously allocated with. Meanwhile, each terminal attempts the access by performing the backoff procedure again in a next contention window interval and in this case, each terminal performs the backoff procedure from slot time(s) which remained in the previous contention window interval. By such a method, the respective terminals that perform the wireless LAN communication may avoid a mutual collision for a specific channel. FIG.7is a diagram illustrating a method for performing a distributed coordination function using a request to send (RTS) frame and a clear to send (CTS) frame. The AP and STAs in the BSS contend in order to obtain an authority for transmitting data. When data transmission at the previous step is completed, each terminal having data to be transmitted performs a backoff procedure while decreasing a backoff counter (alternatively, a backoff timer) of a random number allocated to each terminal after an AFIS time. A transmitting terminal in which the backoff counter is expired transmits the request to send (RTS) frame to notify that corresponding terminal has data to transmit. According to an exemplary embodiment ofFIG.7, STA1 which holds a lead in contention with minimum backoff may transmit the RTS frame after the backoff counter is expired. The RTS frame includes information on a receiver address, a transmitter address, and duration. A receiving terminal (i.e., the AP inFIG.7) that receives the RTS frame transmits the clear to send (CTS) frame after waiting for a short IFS (SIFS) time to notify that the data transmission is available to the transmitting terminal STA1. The CTS frame includes the information on a receiver address and duration. In this case, the receiver address of the CTS frame may be set identically to a transmitter address of the RTS frame corresponding thereto, that is, an address of the transmitting terminal STA1. The transmitting terminal STA1 that receives the CTS frame transmits the data after a SIFS time. When the data transmission is completed, the receiving terminal AP transmits an acknowledgment (ACK) frame after a SIFS time to notify that the data transmission is completed. When the transmitting terminal receives the ACK frame within a predetermined time, the transmitting terminal regards that the data transmission is successful. However, when the transmitting terminal does not receive the ACK frame within the predetermined time, the transmitting terminal regards that the data transmission is failed. Meanwhile, adjacent terminals that receive at least one of the RTS frame and the CTS frame in the course of the transmission procedure set a network allocation vector (NAV) and do not perform data transmission until the set NAV is terminated. In this case, the NAV of each terminal may be set based on a duration field of the received RTS frame or CTS frame. In the course of the aforementioned data transmission procedure, when the RTS frame or CTS frame of the terminals is not normally transferred to a target terminal (i.e., a terminal of the receiver address) due to a situation such as interference or a collision, a subsequent process is suspended. The transmitting terminal STA1 that transmitted the RTS frame regards that the data transmission is unavailable and participates in a next contention by being allocated with a new random number. In this case, the newly allocated random number may be determined within a range (2*CW) twice larger than a previous predetermined random number range (a contention window, CW). FIG.8illustrates a wideband allocation method for wireless LAN communication. InFIG.8and drawings given below, CH1 to CH8 represent 20 MHz channels, respectively, but the number of channels and a bandwidth of the channels may be changed according to a communication scheme to which the present invention is applied. In the wireless LAN system, the terminals of each BSS perform communication by setting a specific channel as a primary channel. The primary channel is a channel used for non-AP STAs to be associated with the AP and may be extended to 40 MHz, 80 MHz, and the like from basic 20 MHz according to a transmission bandwidth. Meanwhile, a secondary channel is an adjacent channel having the same bandwidth as the primary channel and forms a channel having a double bandwidth in association with the primary channel. The terminals of the BSS perform clear channel assessment (CCA) with respect to each channel to check whether the corresponding channel is busy and perform bandwidth extension based on channel(s) determined to be idle. That is, by using 20 MHz as a basic bandwidth, the terminal may extend the transmission bandwidth to 40 MHz, 80 MHz, and 160 MHz by considering whether channels adjacent to the primary channel are idle. In more detail, referring toFIG.8, CH1 may be set as a primary 20 MHz channel of the BSS and a total 40 MHz transmission bandwidth having CH1 and CH2 as the primary channel and the secondary channel, respectively may be used when CH2 adjacent to CH1 is idle. Further, when both CH3 and CH4 adjacent to CH1 and CH2 are idle, a total 80 MHz transmission bandwidth having CH1 and CH2 as a primary 40 MHz channel and having CH3 and CH4 as a secondary 40 MHz channel may be used. Similarly, when all of CH5 to CH8 adjacent to CH1 to CH4 are idle, a total 160 MHz transmission bandwidth having CH1 to CH4 as a primary 80 MHz channel and having CH5 to CH8 as a secondary 80 MHz channel may be used. FIG.9illustrates a wideband access method of a terminal using a request to send (RTS) frame and a clear to send (CTS) frame. In the exemplary embodiment ofFIG.9, a maximum bandwidth is set to 80 MHz in the corresponding BSS. Further, as described above inFIG.7, the terminal performs a backoff procedure for the primary channel (CH1) and when a backoff counter is expired the terminal transmits RTS frames to channels (CH1 to CH4) of 80 MHz bandwidth, which include the primary channel and the secondary channels. First,FIG.9(a)illustrates a wideband access method according to a dynamic bandwidth operation. Referring toFIG.9(a), the terminal transmits the RTS frames to each of the channels CH1 to CH4 of 80 MHz bandwidth, but CTS frames are received only in CH1 and CH2 since secondary 40 MHz channels CH3 and CH4 are busy. Therefore, the terminal transmits data by using a partial bandwidth of 40 MHz as the transmission bandwidth. In this case, the transmission bandwidth has CH1 and CH2 in which the CTS frame is received as the primary channel and the secondary channel, respectively. Meanwhile, the corresponding terminal may not use CH3 and CH4 in which the CTS frame is not received until a next backoff procedure for the primary channel CH1 is performed. That is, according to the exemplary embodiment ofFIG.9(a), the terminal transmits data by using the maximum bandwidth when the primary channel and all secondary channels are idle. Further, the terminal transmits data by using only a partial bandwidth including the primary channel when at least some of secondary channels are busy. Next,FIG.9(b)illustrates a wideband access method according to a static bandwidth operation. Referring toFIG.9(b), the terminal transmits the RTS frames to each of the channels CH1 to CH4 of 80 MHz bandwidth, but CTS frames are not received through some channels CH3 and CH4 since the CH3 and CH4 are busy. Accordingly, the terminal postpones using all channels CH1 to CH4 of 80 MHz bandwidth and transmits the RTS frames for four channels again after the next backoff procedure. That is, according to the exemplary embodiment ofFIG.9(b), when at least one channel among all channels of the maximum bandwidth is busy, the terminal does not use the total bandwidth and performs a backoff procedure again for the primary channel in order to transmit data. FIG.10illustrates another exemplary embodiment of a wideband access method of a terminal. Even in the exemplary embodiment ofFIG.10, the maximum bandwidth is set to 80 MHz in the corresponding BSS and duplicated description with the exemplary embodiment ofFIG.9will be omitted. FIG.10(a)illustrates an exemplary embodiment in which data is successfully transmitted by using the set maximum bandwidth, andFIGS.10(b) and10(c)illustrate exemplary embodiments of data transmission in which some channels of the maximum bandwidth are busy. In more detail,FIG.10(b)illustrates the wideband access method according to the dynamic bandwidth operation and when the secondary 40 MHz channels CH3 and CH4 are busy, the terminal transmits data by using only the primary 40 MHz channels CH1 and CH2. Next,FIG.10(c)illustrates the wideband access method according to the static bandwidth operation and when at least some channels are busy, the terminal does not transmit data and defers by performing a backoff procedure until the maximum bandwidth of 80 MHz is totally usable. Meanwhile, in each exemplary embodiment ofFIG.10, the backoff procedure and enhanced distributed coordination access (EDCA) are performed only in the primary 20 MHz channel CH1 and in other secondary channels CH2 to CH4, it may be verified whether the corresponding channel is usable through CCA for a PIFS time before the backoff counter is expired. FIG.11illustrates yet another exemplary embodiment of a wideband access method of a terminal. In the previous exemplary embodiments, the terminal that transmits the data uses initially set channel(s) until the corresponding transmission ends, but in the exemplary embodiment ofFIG.11, when a channel which is additionally usable is sensed while transmitting the data, the terminal may use the corresponding channel. In more detail, the terminal performs a backoff procedure for the primary channel CH1 and verifies, in other secondary channels CH2 to CH4, whether each channel is usable by performing CCA for the PIFS time before the backoff counter of the backoff procedure is expired. As described in the exemplary embodiment ofFIG.11, when some secondary channels CH3 and CH4 are busy, the terminal performs data transmission by using only the channels CH1 and CH2 of a partial bandwidth, that is, 40 MHz bandwidth, which include the primary channel CH1. However, when the channels CH3 and CH4 which have been impossible to use at a wideband access time become idle and thereby usable while transmitting the data, the terminal may perform additional channel access to the corresponding channels. According to the exemplary embodiment of the present invention, the terminal may set at least one channel among the secondary channels which are usable (i.e., idle) as an alternative primary channel (APCH). Furthermore, the terminal may perform an additional channel access by using the set alternative primary channel. In the exemplary embodiment of the present invention, the alternative primary channel (APCH) is a primary channel set in addition to the basic primary channel (i.e., primary 20 MHz channel) of the corresponding BSS. The alternative primary channel may operate as a primary channel for at least one channel among secondary channels which are not associated with the basic primary channel. That is, in the aforementioned exemplary embodiment, separate bandwidth extension may be performed based on the alternative primary channel similarly to the case where the bandwidth extension for wideband data transmission is performed based on the basic primary channel. The alternative primary channel may be used for the association between the non-AP STA and the AP similarly to the basic primary channel and the backoff procedure, the enhanced distributed coordination access (EDCA), and the like may be performed. In the same BSS, the basic primary channel is set identically for each terminal, but the alternative primary channel may be set independently for each terminal. Accordingly, an alternative primary channel set in some terminals may be different from an alternative primary channel set in other terminals in the same BSS. The non-AP STA may set a new link with the AP by using the alternative primary channel and transmit data through the set link. Meanwhile, in the exemplary embodiment of the present invention, it is described that the basic primary channel is an original primary channel set in the corresponding BSS and has a bandwidth of 20 MHz, but the present invention is not limited thereto and the basic primary channel may be set with another bandwidth in some exemplary embodiments. FIG.11illustrates an exemplary embodiment in which CH3 between the usable secondary channels CH3 and CH4 is set as the alternative primary channel. When the alternative primary channel CH3 becomes idle, the terminal performs a backoff procedure for CH3 after an xIFS time. The xIFS in which the terminal waits before the backoff procedure of the alternative primary channel starts may become the aforementioned AIFS or PIFS and the present invention is not limited thereto. Meanwhile, for the PIFS time before the backoff counter for the alternative primary channel CH3 is expired, the terminal performs CCA for another secondary channel CH4 which can be associated with the alternative primary channel CH3 to verify whether the corresponding channel is usable. When the alternative primary channel CH3 is maintained to be idle and the backoff counter for the corresponding channel is thus expired, the terminal transmits data by using the alternative primary channel CH3. In this case, when the secondary channel CH4 which can be associated with the alternative primary channel CH3 is present by maintaining the idle state for the PIFS time before the backoff counter is expired, the terminal transmits data by using a wideband channel in which the alternative primary channel CH3 and the corresponding secondary channel CH4 are associated with each other. FIGS.12to15illustrate methods for setting an alternative primary channel according to an exemplary embodiment of the present invention. In the exemplary embodiments ofFIGS.12to15, a channel marked with a shade represents a channel which is busy. In the exemplary embodiment of the present invention, the busy channel includes a channel used for transmitting data by the corresponding terminal and a channel used for transmitting data by another terminal. Herein, the channel used for transmitting data by another terminal may be determined based on a CCA result of the corresponding channel and include a channel used for transmitting data by another terminal in the same BSS and a channel in which interference occurs due to a transmission signal of a terminal in another BSS. The terminal obtains basic primary channel information of the BSS with which the corresponding terminal is associated and performs CCA with respect to the basic primary channel and secondary channels. In addition, the terminal may set the alternative primary channel among one or more secondary channels determined to be idle as a result of performing the CCA. First,FIG.12illustrates a method for setting an alternative primary channel according to an exemplary embodiment of the present invention. In the exemplary embodiment ofFIG.12, CH1 is set as the basic primary channel (i.e., primary 20 MHz channel), and CH1 to CH3 are busy, and CH4 to CH8 are idle. According to the exemplary embodiment ofFIG.12, the alternative primary channel may be randomly set among usable idle secondary channels. That is, all idle secondary channels may become candidates of the alternative primary channel and the respective secondary channels may be selected as the alternative primary channel with a uniform probability distribution. In the exemplary embodiment ofFIG.12, 5 idle secondary channels of CH4 to CH8 are present, and therefore, each secondary channel may be selected as the alternative primary channel with a probability of 1/5. Meanwhile, according to an additional exemplary embodiment of the present invention, a weighted value of selecting the alternative primary channel for each secondary channel may be granted according to a channel situation, a traffic characteristic, and the like. FIG.13illustrates a method for setting an alternative primary channel according to another exemplary embodiment of the present invention. In the exemplary embodiment ofFIG.13, CH1 is set as the basic primary channel, and CH1 to CH3 and CH5 are busy, and CH4 and CH6 to CH8 are idle. According to the exemplary embodiment ofFIG.13, a channel, among the usable idle secondary channels, which may form a channel having the largest bandwidth in association with other secondary channel(s) may be set as the alternative primary channel. InFIG.13, since CH3 adjacent to CH4 is busy, a formable bandwidth of CH4 becomes a maximum of 20 MHz. Similarly, since CH5 adjacent to CH6 is busy, a formable bandwidth of CH6 becomes a maximum of 20 MHz. However, since channels CH8 and CH7 adjacent to CH7 and CH8, respectively are idle, CH7 and CH8 may form channels having the larger bandwidth in association with the adjacent channels and the formable bandwidths of CH7 and CH8 become a maximum of 40 MHz. Therefore, according to the exemplary embodiment ofFIG.13, CH7 and CH8 having the largest formable bandwidth may become the candidates of the alternative primary channel. The terminal may set one of a plurality of secondary channels which may form the channel having the largest bandwidth as the alternative primary channel. According to an exemplary embodiment, the terminal may randomly set the alternative primary channel among the plurality of secondary channels which may form the channel having the largest bandwidth by combining the exemplary embodiments ofFIGS.12and13. That is, inFIG.13, CH7 and CH8 may become the candidates of the alternative primary channel and each secondary channel may be selected as the alternative primary channel with the probability of 1/2. FIGS.14and15illustrate methods for setting an alternative primary channel according to yet another exemplary embodiment of the present invention. In the exemplary embodiment ofFIGS.14and15, CH4 is set as the basic primary channel, and CH3 to CH5 are busy, and CH1, CH2 and CH6 to CH8 are idle. According to the exemplary embodiment of the present invention, the alternative primary channel may be selected based on a frequency interval between the corresponding secondary channel and the basic primary channel among the usable idle secondary channels.FIGS.14and15illustrate an exemplary embodiment in which a secondary channel having the smallest frequency interval from the basic primary channel, that is, most adjacent to the basic primary channel is selected as the alternative primary channel. In this case, a method that selects the adjacent channel includes a method based on a physical frequency interval and a method based on a logical frequency interval. First,FIG.14illustrates an exemplary embodiment of selecting the alternative primary channel based on the physical frequency interval. The method based on the physical frequency interval means selecting the alternative primary channel by considering only an actual frequency interval. Referring toFIG.14, CH2 and CH6 which are most adjacent to the basic primary channel CH4, among the idle secondary channels may become the candidates of the alternative primary channel. The terminal may randomly set the alternative primary channel between the alternative primary channel candidates CH2 and CH6. On the contrary,FIG.15illustrates an exemplary embodiment of selecting the alternative primary channel based on the logical frequency interval. The logical frequency interval may be determined according to a merging or association order with the primary channel according to the aforementioned wideband allocation rule. Referring toFIG.15, CH1 and CH2 having the highest order of association with the basic primary channel CH4 may become the candidates of the alternative primary channel in order to form the wideband channel among the idle secondary channels. According to an exemplary embodiment, the terminal may randomly set the alternative primary channel between the alternative primary channel candidates CH1 and CH2. According to another exemplary embodiment, the terminal may set the alternative primary channel by using both the logical frequency interval and the physical frequency interval. That is, CH2 having the smallest physical frequency interval from the basic primary channel CH4, between CH1 and CH2 having the smallest logical frequency interval from CH4 may be set as the alternative primary channel. Meanwhile, in the exemplary embodiment ofFIG.15, CH6 has the same physical frequency interval from the basic primary channel as CH2, but since CH6 has the larger logical frequency interval from the basic primary channel than CH2, and as a result, CH6 is not selected as the alternative primary channel. According to an additional exemplary embodiment of the present invention, a channel having the lowest signal strength according to a result of performing CCA for each secondary channel may be set as the alternative primary channel. In this case, a channel having small interference and noise is set as the alternative primary channel to increase reliability and efficiency of the data transmission. The aforementioned methods for setting alternative primary channel describe exemplary embodiments of the present invention and the alternative primary channel may be set by combining or modifying the aforementioned exemplary embodiments. For example, the alternative primary channel may be selected even by a method opposite to the exemplary embodiments ofFIGS.14and15. In other words, the secondary channel (e.g., CH8) having the largest physical frequency interval or logical frequency interval from the basic primary channel may be set as the alternative primary channel. Further, in the exemplary embodiment ofFIG.13, among channels which may form the channel having the largest bandwidth in association with other secondary channel(s), a channel (e.g., CH7) having the smallest physical frequency interval or logical frequency interval from the basic primary channel may be selected as the alternative primary channel. FIGS.16to23illustrate various methods for operating an alternate primary channel according to an exemplary embodiment of the present invention. In the respective exemplary embodiments ofFIGS.16to23, duplicated description of parts which are the same as or correspond to the exemplary embodiment of the previous drawing will be omitted. In the exemplary embodiment ofFIGS.16to23, it is assumed that CH1 is set as the basic primary channel (i.e., primary 20 MHz channel) and CH8 is set as the alternative primary channel. Each terminal in the BSS obtains basic primary channel information and the alternative primary channel information and attempts bandwidth extension to secondary channels adjacent to the basic primary channel and the alternative primary channel, respectively. The terminal may transmit data through the channels of the secured bandwidth. In the exemplary embodiment of the present invention, ‘data’ is used as a term including concepts of a data frame, a PLCP protocol data unit (PPDU), a MAC protocol data unit (MPDU), an aggregate MPDU (A-MPDU), and the like according to the implementation. Further, in the exemplary embodiment of the present invention, a ‘basic channel group’ indicates the basic primary channel itself or a channel having an extended bandwidth, which includes the basic primary channel. In addition, an ‘alternative channel group’ is used as a term that indicates the alternative primary channel itself or a channel having an extended bandwidth, which includes the alternative primary channel. FIG.16illustrates an exemplary embodiment of a PIFS sensing based alternative primary channel operation method. According to the exemplary embodiment ofFIG.16, the terminal performs a backoff procedure for the basic primary channel CH1 in order to transmit data and performs CCA for the alternative primary channel CH8 for a PIFS time before the backoff counter of the backoff procedure is expired to verify whether the corresponding channel is usable. In this case, for the PIFS time before the backoff counter is expired, the terminal may perform CCA even with respect to other secondary channels CH2 to CH7 in addition to the alternative primary channel CH8. When the basic primary channel CH1 is maintained to be idle and the backoff counter for the corresponding channel is thus expired, the terminal transmits data through the basic channel group including the basic primary channel CH1. In order to set the basic channel group, the terminal performs the bandwidth extension based on the CCA result of each secondary channel performed for the PIFS time before the backoff counter for the basic primary channel is expired. Referring toFIG.16, the secondary 20 MHz channel CH2 of the basic primary channel CH1 is idle for the PIFS time before the backoff counter for the basic primary channel CH1 is expired, but CH4 among secondary 40 MHz channels is busy. Therefore, the terminal sets CH1 and CH2 as the basic channel group and transmits data through the channel having the 40 MHz bandwidth. According to the exemplary embodiment of the present invention, when the alternative primary channel CH8 is idle for the PIFS time, the terminal transmits the data even through the alternative channel group including the alternative primary channel CH8. In order to set the alternative channel group, the terminal performs the bandwidth extension based on the CCA result of each secondary channel performed for the PIFS time before the backoff counter for the basic primary channel is expired. That is, when secondary channel(s) which can be associated with the alternative primary channel CH8 is present by maintaining the idle state for the PIFS time before the backoff counter is expired, the terminal transmits data by using the wideband channel in which the alternative primary channel CH8 and the corresponding secondary channel(s) are associated with each other. Referring toFIG.16, the secondary 20 MHz channel CH7 of the alternative primary channel CH8 and the secondary 40 MHz channels CH5 and CH6 are all idle for the PIFS time. Therefore, the terminal sets CH5 to CH8 as the alternative channel group to transmit the data through the channel having the 80 MHz bandwidth. Meanwhile, according to another exemplary embodiment of the present invention, the terminal may perform a separate backoff procedure for the alternative primary channel to determine whether the corresponding channel is usable. In the exemplary embodiments given below, the backoff procedure for the alternative primary channel is performed to maintain fairness of channel use, while it is determined whether the alternative primary channel is usable only by the CCA for the PIFS time in the exemplary embodiment ofFIG.16. FIGS.17to19illustrate an exemplary embodiment of a common backoff based alternative primary channel operation method. That is, according to the exemplary embodiment ofFIGS.17to19, the backoff counter set in the basic primary channel CH1 is shared as the backoff counter for the alternative primary channel CH8. When the alternative primary channel CH8 is idle until the common backoff counter is expired, the terminal may transmit data through the alternative channel group including the alternative primary channel CH8. FIG.17illustrates an exemplary embodiment in which while the backoff procedure for each of the basic primary channel CH1 and the alternative primary channel CH8 is performed, both channels are idle. When the basic primary channel CH1 and the alternative primary channel CH8 are all maintained to be idle and the backoff counter is thus expired, the terminal transmits data by using both the basic channel group and the alternative channel group. In this case, based on the CCA result for each of the secondary channels for the PIFS time before the backoff counter is expired, the terminal performs the bandwidth extension based on the basic primary channel CH1 and the bandwidth extension based on the alternative primary channel CH8. Accordingly, in the exemplary embodiment ofFIG.17, the terminal transmits the data by using the basic channel group having the 40 MHz bandwidth and the alternative channel group having the 80 MHz bandwidth. FIG.18illustrates an exemplary embodiment in which while the backoff procedure for each of the basic primary channel CH1 and the alternative primary channel CH8 is performed, the basic primary channel CH1 is busy. According to the exemplary embodiment ofFIG.18, when the basic primary channel CH1 is busy, the terminal suspends the backoff procedures for the basic primary channel CH1 and the alternative primary channel CH8. When the busy state of the basic primary channel CH1 ends, the terminal resumes the backoff procedures for the basic primary channel CH1 and the alternative primary channel CH8 after an AIFS time. That is, in the exemplary embodiment ofFIG.18, the backoff procedure of the alternative primary channel CH8 is performed dependently to the backoff procedure of the basic primary channel CH1. Therefore, when the backoff procedure of the basic primary channel CH1 is suspended, the terminal also suspends the backoff procedure of the alternative primary channel CH8. In addition, when the backoff procedure of the basic primary channel CH1 is resumed, the terminal also resumes the backoff procedure of the alternative primary channel CH8. When the alternative primary channel CH8 is maintained to be idle while the backoff procedure is performed, the terminal transmits data by using both the basic channel group and the alternative channel group after the backoff counter is expired. Accordingly, in the exemplary embodiment ofFIG.18, the terminal transmits the data by using the basic channel group having the 40 MHz bandwidth and the alternative channel group having the 80 MHz bandwidth. FIG.19illustrates an exemplary embodiment in which while the backoff procedure for each of the basic primary channel CH1 and the alternative primary channel CH8 is performed, the alternative primary channel CH8 is busy. Referring toFIG.19, the backoff procedure of the alternative primary channel CH8 is performed dependently to the backoff procedure of the basic primary channel CH1, but the backoff procedure of the basic primary channel CH1 may be performed independently from the backoff procedure of the alternative primary channel CH8. That is, when the alternative primary channel CH8 is busy, the backoff procedure of the alternative primary channel CH8 is suspended, but the backoff procedure of the basic primary channel CH1 is continuously performed without suspension. As described above, when the backoff procedure of the basic primary channel CH1 is expired, the terminal may transmit the data through the basic channel group including the basic primary channel CH1. However, the data is not transmitted through the alternative primary channel CH8 in which the interference occurs during the backoff procedure. Accordingly, in the exemplary embodiment ofFIG.19, the terminal transmits the data by using the basic channel group having the 40 MHz bandwidth. FIGS.20and21illustrate an exemplary embodiment of an independent backoff based alternative primary channel operation method. That is, according to the exemplary embodiment ofFIGS.20and21, the backoff counter for the basic primary channel CH1 and the backoff counter for the alternative primary channel CH8 are set independently from each other. Therefore, a backoff counter value allocated to the alternative primary channel CH8 may be larger or smaller than a backoff counter value allocated to the basic primary channel CH1. FIG.20illustrates an exemplary embodiment in which the backoff counter for the alternative primary channel CH8 is expired earlier than the backoff counter for the basic primary channel CH1. When the backoff counter for the alternative primary channel CH8 is expired earlier, the terminal switches the alternative primary channel CH8 to an APCH ready state. In the APCH ready state, the terminal defers the data transmission using the alternative primary channel CH8 until the backoff counter for the basic primary channel CH1 is expired. When the backoff counter for the basic primary channel CH1 is expired in the APCH ready state and the alternative primary channel CH8 is maintained to be idle until the corresponding time, the terminal transmits the data by using both the basic channel group and the alternative channel group. In this case, based on the CCA result for each of the secondary channels for the PIFS time before the backoff counter for the basic primary channel CH1 is expired, the terminal performs the bandwidth extension based on the basic primary channel CH1 and the bandwidth extension based on the alternative primary channel CH8. Accordingly, in the exemplary embodiment ofFIG.20, the terminal transmits the data by using the basic channel group having the 40 MHz bandwidth and the alternative channel group having the 80 MHz bandwidth. Meanwhile, when the interference occurs in the alternative primary channel CH8 in the APCH ready state and thus the corresponding channel becomes busy, the terminal cancels the APCH ready state. In this case, the terminal is allocated with a new backoff counter for the alternative primary channel CH8 and performs a backoff procedure for the alternative primary channel CH8 by using the new backoff counter when the busy state of the alternative primary channel CH8 ends. FIG.21illustrates an exemplary embodiment in which the backoff counter for the basic primary channel CH1 is expired earlier than the backoff counter for the alternative primary channel CH8. When the backoff counter for the basic primary channel CH1 is expired earlier, the terminal transmits the data by using only the basic channel group. However, the data is not transmitted through the alternative primary channel CH8 in which the backoff counter is not expired. Accordingly, in the exemplary embodiment ofFIG.21, the terminal transmits the data by using the basic channel group having the 40 MHz bandwidth. According to an exemplary embodiment of the present invention, when the backoff counter for the basic primary channel CH1 is expired, the backoff counter for the alternative primary channel CH8 may be suspended while the data is transmitted through the basic primary channel CH1. Meanwhile, according to yet another exemplary embodiment of the present invention, the terminal may transmit the data through the alternative primary channel independently regardless of whether the data is transmitted through the basic primary channel. That is, even when the basic primary channel is busy and the terminal may not thus use the basic primary channel, the terminal may transmit the data by using the alternative primary channel. FIG.22illustrates an exemplary embodiment of independently using the alternative primary channel. According to the exemplary embodiment ofFIG.22, the backoff procedures are performed for the basic primary channel CH1 and the alternative primary channel CH8 by using the common backoff counter and in the backoff procedures of each channel, the common backoff counter is suspended only when both the basic primary channel CH1 and the alternative primary channel CH8 are busy. However, when at least one of the basic primary channel CH1 and the alternative primary channel CH8 is idle, the common backoff counter is resumed. The terminal may transmit the data by using the primary channel(s) which is idle when the common backoff counter is expired. That is, when both the basic primary channel CH1 and the alternative primary channel CH8 are idle, the terminal transmits the data by using both the basic channel group and the alternative channel group. In addition, when only any one of both channels is idle, the terminal transmits the data only through the channel group including the idle primary channel. Referring toFIG.22, the alternative primary channel CH8 becomes busy earlier while the backoff procedures for the basic primary channel CH1 and the alternative primary channel CH8 are performed, but since the basic primary channel CH1 is idle, the common backoff counter is not suspended. However, when the basic primary channel CH1 becomes additionally busy so that both channels CH1 and CH8 become busy, the common backoff counter is suspended. According to the exemplary embodiment ofFIG.22, while the common backoff counter is suspended, the alternative primary channel CH8 returns to be idle again and the common backoff counter is resumed again after an AIFS time. When the common backoff counter is expired, the basic primary channel CH1 is busy, while the alternative primary channel CH8 is idle. Therefore, the terminal transmits the data by using the alternative channel group including the idle alternative primary channel CH8. FIG.23illustrates another exemplary embodiment of independently using the alternative primary channel. According to the exemplary embodiment ofFIG.23, the backoff procedure of the alternative primary channel CH8 may be performed independently from the backoff procedure of the basic primary channel CH1. In this case, the backoff counter for the alternative primary channel CH8 may be set equal to the backoff counter for the basic primary channel CH1. Alternatively, the backoff counter for the alternative primary channel CH8 may be set as a separate backoff counter. That is, in the exemplary embodiment ofFIG.23, the terminal is separately allocated with a first backoff counter (i.e. timer) for the basic primary channel CH1 and a second backoff counter (i.e. timer) for the alternative primary channel CH8. In this case, the terminal may perform the backoff procedures for the respective primary channels CH1 and CH8 by using the allocated individual backoff counters. Referring toFIG.23, the terminal performs the backoff procedure for the basic primary channel CH1 by using the first backoff counter and suspends the first backoff counter when the basic primary channel CH1 is busy. Similarly, the terminal performs the backoff procedure for the alternative primary channel CH8 by using the second backoff counter and suspends the second backoff counter when the alternative primary channel CH8 is busy. As illustrated inFIG.23, while the second backoff counter is suspended, the alternative primary channel CH8 returns to be idle again and the terminal resumes the second backoff counter after an AIFS time. When the second backoff counter is expired, the terminal transmits the data by using the alternative channel group including the alternative primary channel CH8. The aforementioned exemplary embodiments of the present invention may be used for data transmission of the terminal through combination with Orthogonal Frequency Division Multiple Access (OFDMA). That is, the channels secured by the aforementioned exemplary embodiments may be allocated to one terminal, but alternatively allocated to a plurality of terminals in a wireless LAN system to which the OFDMA is applied. Meanwhile, when the terminal uses the wideband channel through the bandwidth extension in a dense BSS environment as described above, channel access opportunities of other adjacent BSS terminals may be deprived. Therefore, when the terminal intends to transmit the data by using the wideband channel, a method for maintaining the fairness of the data transmission opportunity with the other BSS terminals is required. FIGS.24to26are diagrams illustrating various methods for transmitting data when a terminal uses a wideband channel according to an exemplary embodiment of the present invention. In the exemplary embodiment ofFIGS.24to26, CH1 is set as the primary channel and duplicated description of parts which are the same as or correspond to the aforementioned exemplary embodiment will be omitted. First,FIG.24is a diagram illustrating an exemplary embodiment of a data transmitting method using the wideband channel. According to the exemplary embodiment ofFIG.24, when the terminal transmits the data by using the wideband channel, the terminal may adjust a transmission opportunity (TXOP) of the corresponding data. The TXOP means a guaranteed time for a terminal to continuously transmit packet(s). According to an exemplary embodiment, when the terminal transmits the data through the wideband channel including a plurality of basic channels, the terminal may transmit the data based on TXOP′ (i.e. adjusted TXOP) having a smaller value than an original TXOP. In this case, the basic channel may represent a channel having a basic bandwidth (e.g., 20 MHz) set for a data transmission. As described in the aforementioned exemplary embodiment, the terminal which intends to transmit the data performs the backoff procedure for the primary channel CH1 and performs the CCA for the secondary channels CH2 to CH4 for the PIFS time before the backoff counter of the backoff procedure is expired to determine whether each channel is usable. When at least one idle secondary channel which can be associated with the primary channel CH1 is present, the terminal transmits the data through the wideband channel in which the primary channel CH1 and the idle channel is associated with each other. In this case, the terminal may transmit the data based on the adjusted TXOP (i.e., TXOP′). Table 1 shows Enhanced Distributed Coordination Access (EDCA) parameter values set according to an access category (AC). In Table 1, the access category includes an access category AC_BK of a background state, an access category AC_BE of a best effort state, an access category AC_VI of video data, an access category AC_VO of voice data, and a legacy distributed coordination function (DCF). Further, the parameters include a minimum value CWmin of a contention window, a maximum value CWmax of a contention window, an AIFS value AIFSN, a maximum TXOP, and the adjusted TXOP (i.e. TXOP′). TABLE 1ACCWminCWmaxAIFSNMax TXOPTXOP′Background15102370A′(AC_BK)Best Effort15102330A′(AC_BE)Video71523.008 msB′ < 3.008 ms(AC_VI)Voice3721.504 msB′ < 1.504 ms(AC_VO)Legacy15102320A′DCF As shown in Table 1, a TXOP′ of data transmitted through the wideband channel may be determined to be a predetermined value A′ or a value B′ smaller than an original TXOP in the corresponding access category. According to an exemplary embodiment of the present invention, the TXOP′ of the data transmitted through the associated wideband channel may have a relationship with the predetermined TXOP as shown in an equation given below. TXOP′=βTXOP [Equation 1] Where, β is a constant value which is inverse proportional to the number of basic channels occupied by the corresponding terminal. For example, if the bandwidth of the basic channel is 20 MHz, β is set to 1/2 when the terminal transmits data with the bandwidth of 40 MHz, and β may be set to 1/3 when the terminal transmits data with the bandwidth of 60 MHz. That is, when the terminal transmits data by using a bandwidth which is n times larger than the basic channel, the TXOP′ value may be adjusted to 1/n of the predetermined TXOP. However, in the present invention, a method for setting the TXOP′ is not limited thereto and as the bandwidth of the wideband channel used by the terminal is larger, the TXOP′ may be set to a smaller value. According to an additional exemplary embodiment of the present invention, secondary channel(s) separated from the primary channel in addition to secondary channel(s) adjacent to the primary channel may be associated with the primary channel to be used for transmitting the data. In this case, the bandwidth which can be occupied by the terminal may be set to a value which is integer times larger than the basic channel as 20 MHz, 40 MHz, 60 MHz, 80 MHz, 100 MHz, 120 MHz, 140 MHz, 160 MHz, and the like. Similarly even in this case, the terminal may set the TXOP′ of the data based on the number of secondary channels associated with the primary channel. That is, as the number of secondary channels associated with the primary channel is larger, the TXOP′ may be set to be smaller. Meanwhile, according to another exemplary embodiment, a channel having the smaller bandwidth than the basic channel may be used for the data transmission according to a design of the communication system. When the data is transmitted through a channel having the smaller bandwidth than the basic channel as described above, β is set to a value larger than 1 to allocate a TXOP′ having the larger value than the predetermined TXOP to the corresponding data. Meanwhile, according to the exemplary embodiment of the present invention, β which is a constant for determining the TXOP′ may be determined by reflecting an additional weighted value as well as the wideband channel used by terminal. According to an exemplary embodiment, the terminal may determine an available situation of the channel by using information such as a control frame received during a predetermined interval before the present time, and the like and adjust the weighed value for the constant β based on the determined channel available situation. The weighted value may determine a change amount of the TXOP′ depending on a change in the number of basic channels occupied by the terminal. For example, the weighted value may be determined as 1/β under a situation in which the terminal may sufficiently exclusively occupy the wideband channel and in this case, the TXOP′ depending on the use of the wideband channel may be set to the same value as the original TXOP. FIG.25illustrates another exemplary embodiment of the data transmitting method using the wideband channel. According to the exemplary embodiment ofFIG.25, when the terminal transmits the data by using the wideband channel, the terminal may increase the size of the backoff counter used in the backoff procedure of the corresponding terminal. As described above, the backoff counter for the backoff procedure of the primary channel is determined as the random number value within the contention window (CW) range set in the corresponding terminal. Herein, the contention window (CW) of each terminal is determined between the minimum value CWmin of the contention window and the maximum value CWmax of the contention window. That is, the contention window (CW) of each terminal is initialized to the minimum value CWmin of the contention window and a terminal in which a collision occurs in the backoff procedure increases the contention window (CW) in a range within the maximum value CWmax of the contention window (for example, two times larger than the previous contention window). As the contention window (CW) set for the terminal increases, the corresponding terminal has the higher probability to be allocated with the backoff counter having the larger value. According to an exemplary embodiment of the present invention, when the terminal transmits data by using the wideband channel, the value of the contention window (CW) set for the corresponding terminal may increase. For example, the minimum value CWmin of the contention window and the maximum value CWmax of the contention window may be basically set as enumerated in Table 1 according to a traffic type. In this case, as the bandwidth of the wideband channel used by the terminal increases, at least one of the minimum value CWmin of the contention window and the maximum value CWmax of the contention window set for the corresponding terminal may increase. According to another exemplary embodiment of the present invention, when the terminal transmits the data by using the wideband channel, the corresponding terminal may extract a plurality of backoff counter candidate values within the set contention window (CW) range and allocate the largest value among the extracted backoff counter candidate values to the backoff counter for the corresponding terminal. For example, when the terminal transmits the data by using the bandwidth which is n times larger than the basic channel, n backoff counter candidate values may be randomly extracted within the contention window (CW) range set for the corresponding terminal. In this case, the terminal may set the largest value among n extracted backoff counter candidate values as the backoff counter for the primary channel of the corresponding terminal. A probability that a value z will be randomly extracted within the set contention window value CW is 1/CW. However, as described above, f(z) which is a probability that n values being randomly extracted within the contention window value CW and z become the largest value among n extracted values is shown in an equation given below. f(z)=nCW(zCW)n-1[Equation2] Accordingly, as n which is the number of times of extracting the backoff counter candidate value increases, a probability that z which is the largest value among the backoff counter candidate values will become a value close to the contention window value CW increases. Meanwhile, the terminal may determine an available situation of the channel by using the information such as the control frame received during the predetermined interval before the present time, and the like and adjust the increase probability of the backoff counter based on the determined channel available situation. For example, the terminal may decrease an increase amount of the contention window (CW) value set for the corresponding terminal as the channel available situation is better. To this end, the terminal may decrease the increase amounts of the minimum value CWmin of the contention window and the maximum value CWmax of the contention window. Similarly, the terminal may decrease n which is the number of times of extracting the backoff counter candidate value for the corresponding terminal as the channel available situation is better. As such, when the channel available situation is better, an unnecessary backoff procedure in a non-contention state may be prevented by decreasing the increase amount of the contention window (CW) and n which is the number of times of extracting the backoff counter candidate value. As such, according to the exemplary embodiment of the present invention, when the terminal transmits the data by using the wideband channel, the additional backoff counter is derived to be used in the backoff procedure to maintain the fairness of the data transmission opportunity with the terminals of another BSS. FIG.26illustrates yet another exemplary embodiment of the data transmitting method using the wideband channel. According to the exemplary embodiment ofFIG.26, when the terminal transmits the data by using the wideband channel, the bandwidth extension from the primary channel may be gradually performed. As described in the aforementioned exemplary embodiment, the terminal which intends to transmit the data performs the backoff procedure for the primary channel CH1 and when the backoff counter is expired, the terminal transmits the data by using the primary channel CH1. However, unlike the previous exemplary embodiments, the terminal performs the CCA for the secondary channel for the xIFS time after the backoff counter is expired to determine whether the corresponding channel is usable. In this case, the xIFS may be set to PIFS as described in the previous exemplary embodiments regarding the bandwidth extension or alternatively set to another value. When the corresponding secondary channel is idle for the set xIFS time, the terminal transmits the data by using the corresponding secondary channel together with the primary channel CH1. The terminal repeats the same process with respect to an additional secondary channel for the xIFS time after starting the occupation of the secondary channel. The terminal may extend the bandwidth by the unit of one channel while performing the bandwidth extension, and alternatively extend the bandwidth by the unit of a predetermined number of channels. Further, an order to add the secondary channel for the bandwidth extension may be determined based on a merging or association order with the primary channel according to the wideband allocation rule, but the present invention is not limited thereto. As such, according to the exemplary embodiment ofFIG.26, when the terminal performs channel extension for using the wideband channel, the terminal may gradually extend the channel with a time difference of the predetermined xIFS to grant an opportunity in which other communication terminals may start the communication. Although the present invention is described by using the wireless LAN communication as an example, the present invention is not limited thereto and the present invention may be similarly applied even to other communication systems such as cellular communication, and the like. Further, the method, the apparatus, and the system of the present invention are described in association with the specific embodiments, but some or all of the components and operations of the present invention may be implemented by using a computer system having universal hardware architecture. The detailed described embodiments of the present invention may be implemented by various means. For example, the embodiments of the present invention may be implemented by a hardware, a firmware, a software, or a combination thereof. In case of the hardware implementation, the method according to the embodiments of the present invention may be implemented by one or more of Application Specific Integrated Circuits (ASICSs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, micro-controllers, micro-processors, and the like. In case of the firmware implementation or the software implementation, the method according to the embodiments of the present invention may be implemented by a module, a procedure, a function, or the like which performs the operations described above. Software codes may be stored in a memory and operated by a processor. The processor may be equipped with the memory internally or externally and the memory may exchange data with the processor by various publicly known means. The description of the present invention is used for exemplification and those skilled in the art will be able to understand that the present invention can be easily modified to other detailed forms without changing the technical idea or an essential feature thereof. Thus, it is to be appreciated that the embodiments described above are intended to be illustrative in every sense, and not restrictive. For example, each component described as a single type may be implemented to be distributed and similarly, components described to be distributed may also be implemented in an associated form. The scope of the present invention is represented by the claims to be described below rather than the detailed description, and it is to be interpreted that the meaning and scope of the claims and all the changes or modified forms derived from the equivalents thereof come within the scope of the present invention. MODE FOR INVENTION As above, related features have been described in the best mode. INDUSTRIAL APPLICABILITY Various exemplary embodiments of the present invention have been described with reference to an IEEE 802.11 system, but the present invention is not limited thereto and the present invention can be applied to various types of mobile communication apparatus, mobile communication system, and the like. | 71,286 |
11943751 | DESCRIPTION OF EXEMPLARY EMBODIMENTS In the present specification, “A or B” may mean “only A”, “only B” or “both A and B”. In other words, in the present specification, “A or B” may be interpreted as “A and/or B”. For example, in the present specification, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”. A slash (/) or comma used in the present specification may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”. In the present specification, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”. In addition, in the present specification, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”. In addition, a parenthesis used in the present specification may mean “for example”. Specifically, when indicated as “control information (EHT-signal)”, it may mean that “EHT-signal” is proposed as an example of the “control information”. In other words, the “control information” of the present specification is not limited to “EHT-signal”, and “EHT-signal” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., EHT-signal)”, it may also mean that “EHT-signal” is proposed as an example of the “control information”. Technical features described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented. The following example of the present specification may be applied to various wireless communication systems. For example, the following example of the present specification may be applied to a wireless local area network (WLAN) system. For example, the present specification may be applied to the IEEE 802.11a/g/n/ac standard or the IEEE 802.11ax standard. In addition, the present specification may also be applied to the newly proposed EHT standard or IEEE 802.11be standard. In addition, the example of the present specification may also be applied to a new WLAN standard enhanced from the EHT standard or the IEEE 802.11be standard. In addition, the example of the present specification may be applied to a mobile communication system. For example, it may be applied to a mobile communication system based on long term evolution (LTE) depending on a 3rd generation partnership project (3GPP) standard and based on evolution of the LTE. In addition, the example of the present specification may be applied to a communication system of a 5G NR standard based on the 3GPP standard. Hereinafter, in order to describe a technical feature of the present specification, a technical feature applicable to the present specification will be described. FIG.1shows an example of a transmitting apparatus and/or receiving apparatus of the present specification. In the example ofFIG.1, various technical features described below may be performed.FIG.1relates to at least one station (STA). For example, STAs110and120of the present specification may also be called in various terms such as a mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, or simply a user. The STAs110and120of the present specification may also be called in various terms such as a network, a base station, a node-B, an access point (AP), a repeater, a router, a relay, or the like. The STAs110and120of the present specification may also be referred to as various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, or the like. For example, the STAs110and120may serve as an AP or a non-AP. That is, the STAs110and120of the present specification may serve as the AP and/or the non-AP. In the present specification, the AP may be indicated as an AP STA. The STAs110and120of the present specification may support various communication standards together in addition to the IEEE 802.11 standard. For example, a communication standard (e.g., LTE, LTE-A, 5G NR standard) or the like based on the 3GPP standard may be supported. In addition, the STA of the present specification may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, or the like. In addition, the STA of the present specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving (autonomous-driving), or the like. The STAs110and120of the present specification may include a medium access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for a radio medium. The STAs110and120will be described below with reference to a sub-figure (a) ofFIG.1. The first STA110may include a processor111, a memory112, and a transceiver113. The illustrated process, memory, and transceiver may be implemented individually as separate chips, or at least two blocks/functions may be implemented through a single chip. The transceiver113of the first STA performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be, etc.) may be transmitted/received. For example, the first STA110may perform an operation intended by an AP. For example, the processor111of the AP may receive a signal through the transceiver113, process a reception (RX) signal, generate a transmission (TX) signal, and provide control for signal transmission. The memory112of the AP may store a signal (e.g., RX signal) received through the transceiver113, and may store a signal (e.g., TX signal) to be transmitted through the transceiver. For example, the second STA120may perform an operation intended by a non-AP STA. For example, a transceiver123of a non-AP performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be packet, etc.) may be transmitted/received. For example, a processor121of the non-AP STA may receive a signal through the transceiver123, process an RX signal, generate a TX signal, and provide control for signal transmission. A memory122of the non-AP STA may store a signal (e.g., RX signal) received through the transceiver123, and may store a signal (e.g., TX signal) to be transmitted through the transceiver. For example, an operation of a device indicated as an AP in the specification described below may be performed in the first STA110or the second STA120. For example, if the first STA110is the AP, the operation of the device indicated as the AP may be controlled by the processor111of the first STA110, and a related signal may be transmitted or received through the transceiver113controlled by the processor111of the first STA110. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory112of the first STA110. In addition, if the second STA120is the AP, the operation of the device indicated as the AP may be controlled by the processor121of the second STA120, and a related signal may be transmitted or received through the transceiver123controlled by the processor121of the second STA120. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory122of the second STA120. For example, in the specification described below, an operation of a device indicated as a non-AP (or user-STA) may be performed in the first STA110or the second STA120. For example, if the second STA120is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor121of the second STA120, and a related signal may be transmitted or received through the transceiver123controlled by the processor121of the second STA120. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory122of the second STA120. For example, if the first STA110is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor111of the first STA110, and a related signal may be transmitted or received through the transceiver113controlled by the processor111of the first STA110. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory112of the first STA110. In the specification described below, a device called a (transmitting/receiving) STA, a first STA, a second STA, an STA1, an STA2, an AP, a first AP, a second AP, an AP1, an AP2, a (transmitting/receiving) terminal, a (transmitting/receiving) device, a (transmitting/receiving) apparatus, a network, or the like may imply the STAs110and120ofFIG.1. For example, a device indicated as, without a specific reference numeral, the (transmitting/receiving) STA, the first STA, the second STA, the STA1, the STA2, the AP, the first AP, the second AP, the AP1, the AP2, the (transmitting/receiving) terminal, the (transmitting/receiving) device, the (transmitting/receiving) apparatus, the network, or the like may imply the STAs110and120ofFIG.1. For example, in the following example, an operation in which various STAs transmit/receive a signal (e.g., a PPDU) may be performed in the transceivers113and123ofFIG.1. In addition, in the following example, an operation in which various STAs generate a TX/RX signal or perform data processing and computation in advance for the TX/RX signal may be performed in the processors111and121ofFIG.1. For example, an example of an operation for generating the TX/RX signal or performing the data processing and computation in advance may include: 1) an operation of determining/obtaining/configuring/computing/decoding/encoding bit information of a sub-field (SIG, STF, LTF, Data) included in a PPDU; 2) an operation of determining/configuring/obtaining a time resource or frequency resource (e.g., a subcarrier resource) or the like used for the sub-field (SIG, STF, LTF, Data) included the PPDU; 3) an operation of determining/configuring/obtaining a specific sequence (e.g., a pilot sequence, an STF/LTF sequence, an extra sequence applied to SIG) or the like used for the sub-field (SIG, STF, LTF, Data) field included in the PPDU; 4) a power control operation and/or power saving operation applied for the STA; and 5) an operation related to determining/obtaining/configuring/decoding/encoding or the like of an ACK signal. In addition, in the following example, a variety of information used by various STAs for determining/obtaining/configuring/computing/decoding/decoding a TX/RX signal (e.g., information related to a field/subfield/control field/parameter/power or the like) may be stored in the memories112and122ofFIG.1. The aforementioned device/STA of the sub-figure (a) ofFIG.1may be modified as shown in the sub-figure (b) ofFIG.1. Hereinafter, the STAs110and120of the present specification will be described based on the sub-figure (b) ofFIG.1. For example, the transceivers113and123illustrated in the sub-figure (b) ofFIG.1may perform the same function as the aforementioned transceiver illustrated in the sub-figure (a) ofFIG.1. For example, processing chips114and124illustrated in the sub-figure (b) ofFIG.1may include the processors111and121and the memories112and122. The processors111and121and memories112and122illustrated in the sub-figure (b) ofFIG.1may perform the same function as the aforementioned processors111and121and memories112and122illustrated in the sub-figure (a) ofFIG.1. A mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, a user, a user STA, a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, a receiving unit, a transmitting unit, a receiving STA, a transmitting STA, a receiving device, a transmitting device, a receiving apparatus, and/or a transmitting apparatus, which are described below, may imply the STAs110and120illustrated in the sub-figure (a)/(b) ofFIG.1, or may imply the processing chips114and124illustrated in the sub-figure (b) ofFIG.1. That is, a technical feature of the present specification may be performed in the STAs110and120illustrated in the sub-figure (a)/(b) ofFIG.1, or may be performed only in the processing chips114and124illustrated in the sub-figure (b) ofFIG.1. For example, a technical feature in which the transmitting STA transmits a control signal may be understood as a technical feature in which a control signal generated in the processors111and121illustrated in the sub-figure (a)/(b) ofFIG.1is transmitted through the transceivers113and123illustrated in the sub-figure (a)/(b) ofFIG.1. Alternatively, the technical feature in which the transmitting STA transmits the control signal may be understood as a technical feature in which the control signal to be transferred to the transceivers113and123is generated in the processing chips114and124illustrated in the sub-figure (b) ofFIG.1. For example, a technical feature in which the receiving STA receives the control signal may be understood as a technical feature in which the control signal is received by means of the transceivers113and123illustrated in the sub-figure (a) ofFIG.1. Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers113and123illustrated in the sub-figure (a) ofFIG.1is obtained by the processors111and121illustrated in the sub-figure (a) ofFIG.1. Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers113and123illustrated in the sub-figure (b) ofFIG.1is obtained by the processing chips114and124illustrated in the sub-figure (b) ofFIG.1. Referring to the sub-figure (b) ofFIG.1, software codes115and125may be included in the memories112and122. The software codes115and126may include instructions for controlling an operation of the processors111and121. The software codes115and125may be included as various programming languages. The processors111and121or processing chips114and124ofFIG.1may include an application-specific integrated circuit (ASIC), other chipsets, a logic circuit and/or a data processing device. The processor may be an application processor (AP). For example, the processors111and121or processing chips114and124ofFIG.1may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, the processors111and121or processing chips114and124ofFIG.1may be SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or processors enhanced from these processors. In the present specification, an uplink may imply a link for communication from a non-AP STA to an SP STA, and an uplink PPDU/packet/signal or the like may be transmitted through the uplink. In addition, in the present specification, a downlink may imply a link for communication from the AP STA to the non-AP STA, and a downlink PPDU/packet/signal or the like may be transmitted through the downlink. FIG.2is a conceptual view illustrating the structure of a wireless local area network (WLAN). An upper part ofFIG.2illustrates the structure of an infrastructure basic service set (BSS) of institute of electrical and electronic engineers (IEEE) 802.11. Referring the upper part ofFIG.2, the wireless LAN system may include one or more infrastructure BSSs200and205(hereinafter, referred to as BSS). The BSSs200and205as a set of an AP and an STA such as an access point (AP)225and a station (STA1)200-1which are successfully synchronized to communicate with each other are not concepts indicating a specific region. The BSS205may include one or more STAs205-1and205-2which may be joined to one AP230. The BSS may include at least one STA, APs providing a distribution service, and a distribution system (DS)210connecting multiple APs. The distribution system210may implement an extended service set (ESS)240extended by connecting the multiple BSSs200and205. The ESS240may be used as a term indicating one network configured by connecting one or more APs225or230through the distribution system210. The AP included in one ESS240may have the same service set identification (SSID). A portal220may serve as a bridge which connects the wireless LAN network (IEEE 802.11) and another network (e.g., 802.X). In the BSS illustrated in the upper part ofFIG.2, a network between the APs225and230and a network between the APs225and230and the STAs200-1,205-1, and205-2may be implemented. However, the network is configured even between the STAs without the APs225and230to perform communication. A network in which the communication is performed by configuring the network even between the STAs without the APs225and230is defined as an Ad-Hoc network or an independent basic service set (IBSS). A lower part ofFIG.2illustrates a conceptual view illustrating the IBSS. Referring to the lower part ofFIG.2, the IBSS is a BSS that operates in an Ad-Hoc mode. Since the IBSS does not include the access point (AP), a centralized management entity that performs a management function at the center does not exist. That is, in the IBSS, STAs250-1,250-2,250-3,255-4, and255-5are managed by a distributed manner. In the IBSS, all STAs250-1,250-2,250-3,255-4, and255-5may be constituted by movable STAs and are not permitted to access the DS to constitute a self-contained network. FIG.3illustrates an example of a PPDU used in an IEEE standard. As illustrated inFIG.3, various types of PHY protocol data units (PPDUs) are used in IEEE a/g/n/ac standards. Specifically, an LTF and a STF include a training signal, a SIG-A and a SIG-B include control information for a receiving STA, and a data field includes user data corresponding to a PSDU (MAC PDU/aggregated MAC PDU). FIG.3also includes an example of an HE PPDU according to IEEE 802.11ax. The HE PPDU according toFIG.3is an illustrative PPDU for multiple users. An HE-SIG-B may be included only in a PPDU for multiple users, and an HE-SIG-B may be omitted in a PPDU for a single user. As illustrated inFIG.3, the HE-PPDU for multiple users (MUs) may include a legacy-short training field (L-STF), a legacy-long training field (L-LTF), a legacy-signal (L-SIG), a high efficiency-signal A (HE-SIG A), a high efficiency-signal-B (HE-SIG B), a high efficiency-short training field (HE-STF), a high efficiency-long training field (HE-LTF), a data field (alternatively, an MAC payload), and a packet extension (PE) field. The respective fields may be transmitted for illustrated time periods (i.e., 4 or 8 μs). Hereinafter, a resource unit (RU) used for a PPDU is described. An RU may include a plurality of subcarriers (or tones). An RU may be used to transmit a signal to a plurality of STAs according to OFDMA. Further, an RU may also be defined to transmit a signal to one STA. An RU may be used for an STF, an LTF, a data field, or the like. FIG.4illustrates a layout of resource units (RUs) used in a band of 20 MHz. As illustrated inFIG.4, resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) may be used to form some fields of an HE-PPDU. For example, resources may be allocated in illustrated RUs for an HE-STF, an HE-LTF, and a data field. As illustrated in the uppermost part ofFIG.4, a 26-unit (i.e., a unit corresponding to 26 tones) may be disposed. Six tones may be used for a guard band in the leftmost band of the 20 MHz band, and five tones may be used for a guard band in the rightmost band of the 20 MHz band. Further, seven DC tones may be inserted in a center band, that is, a DC band, and a 26-unit corresponding to 13 tones on each of the left and right sides of the DC band may be disposed. A 26-unit, a 52-unit, and a 106-unit may be allocated to other bands. Each unit may be allocated for a receiving STA, that is, a user. The layout of the RUs inFIG.4may be used not only for a multiple users (MUs) but also for a single user (SU), in which case one 242-unit may be used and three DC tones may be inserted as illustrated in the lowermost part ofFIG.4. AlthoughFIG.4proposes RUs having various sizes, that is, a 26-RU, a 52-RU, a 106-RU, and a 242-RU, specific sizes of RUs may be extended or increased. Therefore, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). FIG.5illustrates a layout of RUs used in a band of 40 MHz. Similar toFIG.4in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, and the like may be used in an example ofFIG.5. Further, five DC tones may be inserted in a center frequency, 12 tones may be used for a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 40 MHz band. As illustrated, when the layout of the RUs is used for a single user, a 484-RU may be used. The specific number of RUs may be changed similar toFIG.5. FIG.6illustrates a layout of RUs used in a band of 80 MHz. Similar toFIG.4andFIG.5in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, a 996-RU, and the like may be used in an example ofFIG.6. Further, seven DC tones may be inserted in the center frequency, 12 tones may be used for a guard band in the leftmost band of the 80 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 80 MHz band. In addition, a 26-RU corresponding to 13 tones on each of the left and right sides of the DC band may be used. As illustrated, when the layout of the RUs is used for a single user, a 996-RU may be used, in which case five DC tones may be inserted. The RU described in the present specification may be used in uplink (UL) communication and downlink (DL) communication. For example, when UL-MU communication which is solicited by a trigger frame is performed, a transmitting STA (e.g., AP) may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA through the trigger frame, and may allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA. Thereafter, the first STA may transmit a first trigger-based PPDU based on the first RU, and the second STA may transmit a second trigger-based PPDU based on the second RU. The first/second trigger-based PPDU is transmitted to the AP at the same (or overlapped) time period. For example, when a DL MU PPDU is configured, the transmitting STA (e.g., AP) may allocate the first RU (e.g., 26/52/106/242-RU. etc.) to the first STA, and may allocate the second RU (e.g., 26/52/106/242-RU, etc.) to the second STA. That is, the transmitting STA (e.g., AP) may transmit HE-STF, HE-LTF, and Data fields for the first STA through the first RU in one MU PPDU, and may transmit HE-STF, HE-LTF, and Data fields for the second STA through the second RU. Information related to a layout of the RU may be signaled through HE-SIG-B. FIG.7illustrates a structure of an HE-SIG-B field. As illustrated, an HE-SIG-B field710includes a common field720and a user-specific field730. The common field720may include information commonly applied to all users (i.e., user STAs) which receive SIG-B. The user-specific field730may be called a user-specific control field. When the SIG-B is transferred to a plurality of users, the user-specific field730may be applied only any one of the plurality of users. As illustrated, the common field720and the user-specific field730may be separately encoded. The common field720may include RU allocation information of N*8 bits. For example, the RU allocation information may include information related to a location of an RU. For example, when a 20 MHz channel is used as shown inFIG.4, the RU allocation information may include information related to a specific frequency band to which a specific RU (26-RU/52-RU/106-RU) is arranged. An example of a case in which the RU allocation information consists of 8 bits is as follows. TABLE 18 bits indices (B7 B6NumberB5 B4 B3 B2 B1 B0)#1#2#3#4#5#6#7#8#9of entries0000000026262626262626262610000000126262626262626521000000102626262626522626100000011262626262652521000001002626522626262626100000101262652262626521000001102626522652262610000011126265226525210000100052262626262626261 As shown the example ofFIG.4, up to nine 26-RUs may be allocated to the 20 MHz channel. When the RU allocation information of the common field720is set to “00000000” as shown in Table 1, the nine 26-RUs may be allocated to a corresponding channel (i.e., 20 MHz). In addition, when the RU allocation information of the common field720is set to “00000001” as shown in Table 1, seven 26-RUs and one 52-RU are arranged in a corresponding channel. That is, in the example ofFIG.4, the 52-RU may be allocated to the rightmost side, and the seven 26-RUs may be allocated to the left thereof. The example of Table 1 shows only some of RU locations capable of displaying the RU allocation information. For example, the RU allocation information may include an example of Table 2 below. TABLE 28 bits indices (B7 B6NumberB5 B4 B3 B2 B1 B0)#1#2#3#4#5#6#7#8#9of entries01000y2y1y01062626262626901001y2y1y0106262626528 “01000y2y1y0” relates to an example in which a 106-RU is allocated to the leftmost side of the 20 MHz channel, and five 26-RUs are allocated to the right side thereof. In this case, a plurality of STAs (e.g., user-STAs) may be allocated to the 106-RU, based on a MU-MIMO scheme. Specifically, up to 8 STAs (e.g., user-STAs) may be allocated to the 106-RU, and the number of STAs (e.g., user-STAs) allocated to the 106-RU is determined based on 3-bit information (y2y1y0). For example, when the 3-bit information (y2y1y0) is set to N, the number of STAs (e.g., user-STAs) allocated to the 106-RU based on the MU-MIMO scheme may be N+1. In general, a plurality of STAs (e.g., user STAs) different from each other may be allocated to a plurality of RUs. However, the plurality of STAs (e.g., user STAs) may be allocated to one or more RUs having at least a specific size (e.g.,106subcarriers), based on the MU-MIMO scheme. As shown inFIG.7, the user-specific field730may include a plurality of user fields. As described above, the number of STAs (e.g., user STAs) allocated to a specific channel may be determined based on the RU allocation information of the common field720. For example, when the RU allocation information of the common field720is “00000000”, one user STA may be allocated to each of nine 26-RUs (e.g., nine user STAs may be allocated). That is, up to 9 user STAs may be allocated to a specific channel through an OFDMA scheme. In other words, up to 9 user STAs may be allocated to a specific channel through a non-MU-MIMO scheme. For example, when RU allocation is set to “01000y2y1y0”, a plurality of STAs may be allocated to the 106-RU arranged at the leftmost side through the MU-MIMO scheme, and five user STAs may be allocated to five 26-RUs arranged to the right side thereof through the non-MU MIMO scheme. This case is specified through an example ofFIG.8. FIG.8illustrates an example in which a plurality of user STAs are allocated to the same RU through a MU-MIMO scheme. For example, when RU allocation is set to “01000010” as shown inFIG.7, a 106-RU may be allocated to the leftmost side of a specific channel, and five 26-RUs may be allocated to the right side thereof. In addition, three user STAs may be allocated to the 106-RU through the MU-MIMO scheme. As a result, since eight user STAs are allocated, the user-specific field730of HE-SIG-B may include eight user fields. The eight user fields may be expressed in the order shown inFIG.9. In addition, as shown inFIG.7, two user fields may be implemented with one user block field. The user fields shown inFIG.7andFIG.8may be configured based on two formats. That is, a user field related to a MU-MIMO scheme may be configured in a first format, and a user field related to a non-MIMO scheme may be configured in a second format. Referring to the example ofFIG.8, a user field1to a user field3may be based on the first format, and a user field4to a user field8may be based on the second format. The first format or the second format may include bit information of the same length (e.g., 21 bits). Each user field may have the same size (e.g., 21 bits). For example, the user field of the first format (the first of the MU-MIMO scheme) may be configured as follows. For example, a first bit (i.e., B0-B10) in the user field (i.e., 21 bits) may include identification information (e.g., STA-ID, partial AID, etc.) of a user STA to which a corresponding user field is allocated. In addition, a second bit (i.e., B11-B14) in the user field (i.e., 21 bits) may include information related to a spatial configuration. Specifically, an example of the second bit (i.e., B11-B14) may be as shown in Table 3 and Table 4 below. TABLE 3NSTSNSTSNSTSNSTSNSTSNSTSNSTSNSTSNuserB3 . . . B0[1][2][3][4][5][6][7][8]Total NSTSNumber of entries20000-00111-412-5100100-01102-424-60111-10003-436-7100144830000-00111-4113-6130100-01102-4215-70111-10003-4317-81001-10112-4226-81100332840000-00111-41114-7110100-01102-42116-80111331181000-10012-32217-8101022228 TABLE 4NSTSNSTSNSTSNSTSNSTSNSTSNSTSNSTSNuserB3 . . . B0[1][2][3][4][5][6][7][8]Total NSTSNumber of entries50000-00111-411115-870100-01012-321117-8011022211860000-00101-3111116-840011221111870000-00011-21111117-82800001111111181 As shown in Table 3 and/or Table 4, the second bit (e.g., B11-B14) may include information related to the number of spatial streams allocated to the plurality of user STAs which are allocated based on the MU-MIMO scheme. For example, when three user STAs are allocated to the 106-RU based on the MU-MIMO scheme as shown inFIG.8, N_user is set to “3”. Therefore, values of N_STS[1], N_STS[2], and N_STS[3] may be determined as shown in Table 3. For example, when a value of the second bit (B11-B14) is “0011”, it may be set to N_STS[1]=4, N_STS[2]=1, N_STS[3]=1. That is, in the example ofFIG.8, four spatial streams may be allocated to the user field1, one spatial stream may be allocated to the user field1, and one spatial stream may be allocated to the user field3. As shown in the example of Table 3 and/or Table 4, information (i.e., the second bit, B11-B14) related to the number of spatial streams for the user STA may consist of 4 bits. In addition, the information (i.e., the second bit, B11-B14) on the number of spatial streams for the user STA may support up to eight spatial streams. In addition, the information (i.e., the second bit, B11-B14) on the number of spatial streams for the user STA may support up to four spatial streams for one user STA. In addition, a third bit (i.e., B15-18) in the user field (i.e., 21 bits) may include modulation and coding scheme (MCS) information. The MCS information may be applied to a data field in a PPDU including corresponding SIG-B. An MCS, MCS information, an MCS index, an MCS field, or the like used in the present specification may be indicated by an index value. For example, the MCS information may be indicated by an index 0 to an index 11. The MCS information may include information related to a constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information related to a coding rate (e.g., 1/2, 2/3, 3/4, 5/6e, etc.). Information related to a channel coding type (e.g., LCC or LDPC) may be excluded in the MCS information. In addition, a fourth bit (i.e., B19) in the user field (i.e., 21 bits) may be a reserved field. In addition, a fifth bit (i.e., B20) in the user field (i.e., 21 bits) may include information related to a coding type (e.g., BCC or LDPC). That is, the fifth bit (i.e., B20) may include information related to a type (e.g., BCC or LDPC) of channel coding applied to the data field in the PPDU including the corresponding SIG-B. The aforementioned example relates to the user field of the first format (the format of the MU-MIMO scheme). An example of the user field of the second format (the format of the non-MU-MIMO scheme) is as follows. A first bit (e.g., B0-B10) in the user field of the second format may include identification information of a user STA. In addition, a second bit (e.g., B11-B13) in the user field of the second format may include information related to the number of spatial streams applied to a corresponding RU. In addition, a third bit (e.g., B14) in the user field of the second format may include information related to whether a beamforming steering matrix is applied. A fourth bit (e.g., B15-B18) in the user field of the second format may include modulation and coding scheme (MCS) information. In addition, a fifth bit (e.g., B19) in the user field of the second format may include information related to whether dual carrier modulation (DCM) is applied. In addition, a sixth bit (i.e., B20) in the user field of the second format may include information related to a coding type (e.g., BCC or LDPC). FIG.9illustrates an operation based on UL-MU. As illustrated, a transmitting STA (e.g., AP) may perform channel access through contending (e.g., a backoff operation), and may transmit a trigger frame930. That is, the transmitting STA may transmit a PPDU including the trigger frame930. Upon receiving the PPDU including the trigger frame, a trigger-based (TB) PPDU is transmitted after a delay corresponding to SIFS. TB PPDUs941and942may be transmitted at the same time period, and may be transmitted from a plurality of STAs (e.g., user STAs) having AIDs indicated in the trigger frame930. An ACK frame950for the TB PPDU may be implemented in various forms. FIG.10illustrates an example of a channel used/supported/defined within a 2.4 GHz band. The 2.4 GHz band may be called in other terms such as a first band. In addition, the 2.4 GHz band may imply a frequency domain in which channels of which a center frequency is close to 2.4 GHz (e.g., channels of which a center frequency is located within 2.4 to 2.5 GHz) are used/supported/defined. A plurality of 20 MHz channels may be included in the 2.4 GHz band. 20 MHz within the 2.4 GHz may have a plurality of channel indices (e.g., an index 1 to an index 14). For example, a center frequency of a 20 MHz channel to which a channel index 1 is allocated may be 2.412 GHz, a center frequency of a 20 MHz channel to which a channel index 2 is allocated may be 2.417 GHz, and a center frequency of a 20 MHz channel to which a channel index N is allocated may be (2.407+0.005*N) GHz. The channel index may be called in various terms such as a channel number or the like. Specific numerical values of the channel index and center frequency may be changed. FIG.10exemplifies 4 channels within a 2.4 GHz band. Each of 1st to 4th frequency domains1010to1040shown herein may include one channel. For example, the 1st frequency domain1010may include a channel 1 (a 20 MHz channel having an index 1). In this case, a center frequency of the channel 1 may be set to 2412 MHz. The 2nd frequency domain1020may include a channel 6. In this case, a center frequency of the channel 6 may be set to 2437 MHz. The 3rd frequency domain1030may include a channel 11. In this case, a center frequency of the channel 11 may be set to 2462 MHz. The 4th frequency domain1040may include a channel 14. In this case, a center frequency of the channel 14 may be set to 2484 MHz. FIG.11illustrates an example of a channel used/supported/defined within a 5 GHz band. The 5 GHz band may be called in other terms such as a second band or the like. The 5 GHz band may imply a frequency domain in which channels of which a center frequency is greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz) are used/supported/defined. Alternatively, the 5 GHz band may include a plurality of channels between 4.5 GHz and 5.5 GHz. A specific numerical value shown inFIG.11may be changed. A plurality of channels within the 5 GHz band include an unlicensed national information infrastructure (UNII)-1, a UNII-2, a UNII-3, and an ISM. The INII-1 may be called UNII Low. The UNII-2 may include a frequency domain called UNII Mid and UNII-2Extended. The UNII-3 may be called UNII-Upper. A plurality of channels may be configured within the 5 GHz band, and a bandwidth of each channel may be variously set to, for example, 20 MHz, 40 MHz, 80 MHz, 160 MHz, or the like. For example, 5170 MHz to 5330 MHz frequency domains/ranges within the UNII-1 and UNII-2 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domains/ranges may be divided into four channels through a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domains/ranges may be divided into two channels through an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domains/ranges may be divided into one channel through a 160 MHz frequency domain. FIG.12illustrates an example of a channel used/supported/defined within a 6 GHz band. The 6 GHz band may be called in other terms such as a third band or the like. The 6 GHz band may imply a frequency domain in which channels of which a center frequency is greater than or equal to 5.9 GHz are used/supported/defined. A specific numerical value shown inFIG.12may be changed. For example, the 20 MHz channel ofFIG.12may be defined starting from 5.940 GHz. Specifically, among 20 MHz channels ofFIG.12, the leftmost channel may have an index 1 (or a channel index, a channel number, etc.), and 5.945 GHz may be assigned as a center frequency. That is, a center frequency of a channel of an index N may be determined as (5.940+0.005*N) GHz. Accordingly, an index (or channel number) of the 2 MHz channel ofFIG.12may be 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. In addition, according to the aforementioned (5.940+0.005*N) GHz rule, an index of the 40 MHz channel ofFIG.13may be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227. Although 20, 40, 80, and 160 MHz channels are illustrated in the example ofFIG.12, a 240 MHz channel or a 320 MHz channel may be additionally added. Hereinafter, a PPDU transmitted/received in an STA of the present specification will be described. FIG.13illustrates an example of a PPDU used in the present specification. The PPDU ofFIG.13may be called in various terms such as an EHT PPDU, a TX PPDU, an RX PPDU, a first type or N-th type PPDU, or the like. For example, in the present specification, the PPDU or the EHT PPDU may be called in various terms such as a TX PPDU, a RX PPDU, a first type or N-th type PPDU, or the like. In addition, the EHT PPDU may be used in an EHT system and/or a new WLAN system enhanced from the EHT system. The PPDU ofFIG.13may indicate the entirety or part of a PPDU type used in the EHT system. For example, the example ofFIG.13may be used for both of a single-user (SU) mode and a multi-user (MU) mode. In other words, the PPDU ofFIG.13may be a PPDU for one receiving STA or a plurality of receiving STAs. When the PPDU ofFIG.14is used for a trigger-based (TB) mode, the EHT-SIG ofFIG.13may be omitted. In other words, an STA which has received a trigger frame for uplink-MU (UL-MU) may transmit the PPDU in which the EHT-SIG is omitted in the example ofFIG.13. InFIG.13, an L-STF to an EHT-LTF may be called a preamble or a physical preamble, and may be generated/transmitted/received/obtained/decoded in a physical layer. A subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields ofFIG.13may be determined as 312.5 kHz, and a subcarrier spacing of the EHT-STF, EHT-LTF, and Data fields may be determined as 78.125 kHz. That is, a tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields may be expressed in unit of 312.5 kHz, and a tone index (or subcarrier index) of the EHT-STF, EHT-LTF, and Data fields may be expressed in unit of 78.125 kHz. In the PPDU ofFIG.13, the L-LTF and the L-STF may be the same as those in the conventional fields. The L-SIG field ofFIG.13may include, for example, bit information of 24 bits. For example, the 24-bit information may include a rate field of 4 bits, a reserved bit of 1 bit, a length field of 12 bits, a parity bit of 1 bit, and a tail bit of 6 bits. For example, the length field of 12 bits may include information related to a length or time duration of a PPDU. For example, the length field of 12 bits may be determined based on a type of the PPDU. For example, when the PPDU is a non-HT, HT, VHT PPDU or an EHT PPDU, a value of the length field may be determined as a multiple of 3. For example, when the PPDU is an HE PPDU, the value of the length field may be determined as “a multiple of 3”+1 or “a multiple of 3”+2. In other words, for the non-HT, HT, VHT PPDI or the EHT PPDU, the value of the length field may be determined as a multiple of 3, and for the HE PPDU, the value of the length field may be determined as “a multiple of 3”+1 or “a multiple of 3”+2. For example, the transmitting STA may apply BCC encoding based on a 1/2 coding rate to the 24-bit information of the L-SIG field. Thereafter, the transmitting STA may obtain a BCC coding bit of 48 bits. BPSK modulation may be applied to the 48-bit coding bit, thereby generating 48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols to positions except for a pilot subcarrier{subcarrier index −21, −7, +7, +21} and a DC subcarrier{subcarrier index 0}. As a result, the 48 BPSK symbols may be mapped to subcarrier indices −26 to −22, −20 to −8, −6 to −1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map a signal of {−1, −1, −1, 1} to a subcarrier index{−28, −27, +27, +28}. The aforementioned signal may be used for channel estimation on a frequency domain corresponding to {−28, −27, +27, +28}. The transmitting STA may generate an RL-SIG generated in the same manner as the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving STA may know that the RX PPDU is the HE PPDU or the EHT PPDU, based on the presence of the RL-SIG. A universal SIG (U-SIG) may be inserted after the RL-SIG ofFIG.13. The U-SIG may be called in various terms such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, a first (type) control signal, or the like. The U-SIG may include information of N bits, and may include information for identifying a type of the EHT PPDU. For example, the U-SIG may be configured based on two symbols (e.g., two contiguous OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG may have a duration of 4 us. Each symbol of the U-SIG may be used to transmit the 26-bits information. For example, each symbol of the U-SIG may be transmitted/received based on 52 data tomes and 4 pilot tones. Through the U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 un-coded bits) may be transmitted. A first symbol of the U-SIG may transmit first X-bit information (e.g., 26 un-coded bits) of the A-bit information, and a second symbol of the U-SIG may transmit the remaining Y-bit information (e.g. 26 un-coded bits) of the A-bit information. For example, the transmitting STA may obtain 26 un-coded bits included in each U-SIG symbol. The transmitting STA may perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1/2 to generate 52-coded bits, and may perform interleaving on the 52-coded bits. The transmitting STA may perform BPSK modulation on the interleaved 52-coded bits to generate 52 BPSK symbols to be allocated to each U-SIG symbol. One U-SIG symbol may be transmitted based on 65 tones (subcarriers) from a subcarrier index −28 to a subcarrier index+28, except for a DC index 0. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) except for pilot tones, i.e., tones −21, −7, +7, +21. For example, the A-bit information (e.g., 52 un-coded bits) generated by the U-SIG may include a CRC field (e.g., a field having a length of 4 bits) and a tail field (e.g., a field having a length of 6 bits). The CRC field and the tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on 26 bits allocated to the first symbol of the U-SIG and the remaining 16 bits except for the CRC/tail fields in the second symbol, and may be generated based on the conventional CRC calculation algorithm. In addition, the tail field may be used to terminate trellis of a convolutional decoder, and may be set to, for example, ‘000000’. The A-bit information (e.g., 52 un-coded bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-independent bits and version-dependent bits. For example, the version-independent bits may have a fixed or variable size. For example, the version-independent bits may be allocated only to the first symbol of the U-SIG, or the version-independent bits may be allocated to both of the first and second symbols of the U-SIG. For example, the version-independent bits and the version-dependent bits may be called in various terms such as a first control bit, a second control bit, or the like. For example, the version-independent bits of the U-SIG may include a PHY version identifier of 3 bits. For example, the PHY version identifier of 3 bits may include information related to a PHY version of a TX/RX PPDU. For example, a first value of the PHY version identifier of 3 bits may indicate that the TX/RX PPDU is an EHT PPDU. In other words, when the transmitting STA transmits the EHT PPDU, the PHY version identifier of 3 bits may be set to a first value. In other words, the receiving STA may determine that the RX PPDU is the EHT PPDU, based on the PHY version identifier having the first value. For example, the version-independent bits of the U-SIG may include a UL/DL flag field of 1 bit. A first value of the UL/DL flag field of 1 bit relates to UL communication, and a second value of the UL/DL flag field relates to DL communication. For example, the version-independent bits of the U-SIG may include information related to a TXOP length and information related to a BSS color ID. For example, when the EHT PPDU is divided into various types (e.g., various types such as an EHT PPDU related to an SU mode, an EHT PPDU related to a MU mode, an EHT PPDU related to a TB mode, an EHT PPDU related to extended range transmission, or the like), information related to the type of the EHT PPDU may be included in the version-dependent bits of the U-SIG. For example, the U-SIG may include: 1) a bandwidth field including information related to a bandwidth; 2) a field including information related to an MCS scheme applied to EHT-SIG; 3) an indication field including information regarding whether a dual subcarrier modulation (DCM) scheme is applied to EHT-SIG; 4) a field including information related to the number of symbol used for EHT-SIG; 5) a field including information regarding whether the EHT-SIG is generated across a full band; 6) a field including information related to a type of EHT-LTF/STF; and 7) information related to a field indicating an EHT-LTF length and a CP length. Preamble puncturing may be applied to the PPDU ofFIG.14. The preamble puncturing implies that puncturing is applied to part (e.g., a secondary 20 MHz band) of the full band. For example, when an 80 MHz PPDU is transmitted, an STA may apply puncturing to the secondary 20 MHz band out of the 80 MHz band, and may transmit a PPDU only through a primary 20 MHz band and a secondary 40 MHz band. For example, a pattern of the preamble puncturing may be configured in advance. For example, when a first puncturing pattern is applied, puncturing may be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when a second puncturing pattern is applied, puncturing may be applied to only any one of two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when a third puncturing pattern is applied, puncturing may be applied to only the secondary 20 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band). For example, when a fourth puncturing is applied, puncturing may be applied to at least one 20 MHz channel not belonging to a primary 40 MHz band in the presence of the primary 40 MHz band included in the 80 MHz band within the 160 MHz band (or 80+80 MHz band). Information related to the preamble puncturing applied to the PPDU may be included in U-SIG and/or EHT-SIG. For example, a first field of the U-SIG may include information related to a contiguous bandwidth, and second field of the U-SIG may include information related to the preamble puncturing applied to the PPDU. For example, the U-SIG and the EHT-SIG may include the information related to the preamble puncturing, based on the following method. When a bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be configured individually in unit of 80 MHz. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, a first field of the first U-SIG may include information related to a 160 MHz bandwidth, and a second field of the first U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the first 80 MHz band. In addition, a first field of the second U-SIG may include information related to a 160 MHz bandwidth, and a second field of the second U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the second 80 MHz band. Meanwhile, an EHT-SIG contiguous to the first U-SIG may include information related to a preamble puncturing applied to the second 80 MHz band (i.e., information related to a preamble puncturing pattern), and an EHT-SIG contiguous to the second U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) applied to the first 80 MHz band. Additionally or alternatively, the U-SIG and the EHT-SIG may include the information related to the preamble puncturing, based on the following method. The U-SIG may include information related to a preamble puncturing (i.e., information related to a preamble puncturing pattern) for all bands. That is, the EHT-SIG may not include the information related to the preamble puncturing, and only the U-SIG may include the information related to the preamble puncturing (i.e., the information related to the preamble puncturing pattern). The U-SIG may be configured in unit of 20 MHz. For example, when an 80 MHz PPDU is configured, the U-SIG may be duplicated. That is, four identical U-SIGs may be included in the 80 MHz PPDU. PPDUs exceeding an 80 MHz bandwidth may include different U-SIGs. The EHT-SIG ofFIG.13may include control information for the receiving STA. The EHT-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 us. Information related to the number of symbols used for the EHT-SIG may be included in the U-SIG. The EHT-SIG may include a technical feature of the HE-SIG-B described with reference toFIG.7andFIG.8. For example, the EHT-SIG may include a common field and a user-specific field as in the example ofFIG.7. The common field of the EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users. As in the example ofFIG.7, the common field of the EHT-SIG and the user-specific field of the EHT-SIG may be individually coded. One user block field included in the user-specific field may include information for two users, but a last user block field included in the user-specific field may include information for one user. That is, one user block field of the EHT-SIG may include up to two user fields. As in the example ofFIG.8, each user field may be related to MU-MIMO allocation, or may be related to non-MU-MIMO allocation. As in the example ofFIG.7, the common field of the EHT-SIG may include a CRC bit and a tail bit. A length of the CRC bit may be determined as 4 bits. A length of the tail bit may be determined as 6 bits, and may be set to ‘000000’. As in the example ofFIG.7, the common field of the EHT-SIG may include RU allocation information. The RU allocation information may imply information related to a location of an RU to which a plurality of users (i.e., a plurality of receiving STAs) are allocated. The RU allocation information may be configured in unit of 8 bits (or N bits), as in Table 1. The example of Table 5 to Table 7 is an example of 8-bit (or N-bit) information for various RU allocations. An index shown in each table may be modified, and some entries in Table 5 to Table 7 may be omitted, and entries (not shown) may be added. TABLE 5NumberIndices#1#2#3#4#5#6#7#8#9of entries026262626262626262611262626262626265212262626262652262613262626262652521426265226262626261526265226262652162626522652262617262652265252185226262626262626195226262626265211052262626522626111522626265252112525226262626261135252262626521145252265226261155252265252116262626262610611726265226106118522626261061195252261061 TABLE 6NumberIndices#1#2#3#4#5#6#7#8#9of entries20106262626262612110626262652122106265226261231062652521245252—5252125242-tone RU empty (with zero users)12610626106127-34242835-42484843-50996851-582 * 966859262626262652 + 26261602626 + 5226262626261612626 + 52262626521622626 + 52265226261632626522652 + 26261642626 + 522652 + 26261652626 + 522652521 TABLE 7665226262652 + 262616752522652 + 26261685252 + 2652521692626262626 + 1061702626 + 522610617126265226 + 1061722626 + 5226 + 10617352262626 + 106174525226 + 106175106 + 2626262626176106 + 26262652177106 + 265226261781062652 + 2626179106 + 2652 + 2626180106 + 265252181106 + 2610618210626 + 1061 The example of Table 5 to Table 7 relates to information related to a location of an RU allocated to a 20 MHz band. For example, ‘an index 0’ of Table 5 may be used in a situation where nine 26-RUs are individually allocated (e.g., in a situation where nine 26-RUs shown inFIG.5are individually allocated). Meanwhile, a plurality or RUs may be allocated to one STA in the EHT system. For example, regarding ‘an index 60’ of Table 6, one 26-RU may be allocated for one user (i.e., receiving STA) to the leftmost side of the 20 MHz band, one 26-RU and one 52-RU may be allocated to the right side thereof, and five 26-RUs may be individually allocated to the right side thereof. A mode in which the common field of the EHT-SIG is omitted may be supported. The mode in which the common field of the EHT-SIG is omitted may be called a compressed mode. When the compressed mode is used, a plurality of users (i.e., a plurality of receiving STAs) may decode the PPDU (e.g., the data field of the PPDU), based on non-OFDMA. That is, the plurality of users of the EHT PPDU may decode the PPDU (e.g., the data field of the PPDU) received through the same frequency band. Meanwhile, when a non-compressed mode is used, the plurality of users of the EHT PPDU may decode the PPDU (e.g., the data field of the PPDU), based on OFDMA. That is, the plurality of users of the EHT PPDU may receive the PPDU (e.g., the data field of the PPDU) through different frequency bands. The EHT-SIG may be configured based on various MCS schemes. As described above, information related to an MCS scheme applied to the EHT-SIG may be included in U-SIG. The EHT-SIG may be configured based on a DCM scheme. For example, among N data tones (e.g., 52 data tones) allocated for the EHT-SIG, a first modulation scheme may be applied to half of consecutive tones, and a second modulation scheme may be applied to the remaining half of the consecutive tones. That is, a transmitting STA may use the first modulation scheme to modulate specific control information through a first symbol and allocate it to half of the consecutive tones, and may use the second modulation scheme to modulate the same control information by using a second symbol and allocate it to the remaining half of the consecutive tones. As described above, information (e.g., a 1-bit field) regarding whether the DCM scheme is applied to the EHT-SIG may be included in the U-SIG. An HE-STF ofFIG.13may be used for improving automatic gain control estimation in a multiple input multiple output (MIMO) environment or an OFDMA environment. An HE-LTF ofFIG.13may be used for estimating a channel in the MIMO environment or the OFDMA environment. A PPDU (e.g., EHT-PPDU) ofFIG.13may be configured based on the example ofFIG.4andFIG.5. For example, an EHT PPDU transmitted on a 20 MHz band, i.e., a 20 MHz EHT PPDU, may be configured based on the RU ofFIG.4. That is, a location of an RU of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined as shown inFIG.4. An EHT PPDU transmitted on a 40 MHz band, i.e., a 40 MHz EHT PPDU, may be configured based on the RU ofFIG.5. That is, a location of an RU of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined as shown inFIG.5. Since the RU location ofFIG.5corresponds to 40 MHz, a tone-plan for 80 MHz may be determined when the pattern ofFIG.6is repeated twice. That is, an 80 MHz EHT PPDU may be transmitted based on a new tone-plan in which not the RU ofFIG.6but the RU ofFIG.5is repeated twice. When the pattern ofFIG.5is repeated twice, 23 tones (i.e., 11 guard tones+12 guard tones) may be configured in a DC region. That is, a tone-plan for an 80 MHz EHT PPDU allocated based on OFDMA may have 23 DC tones. Unlike this, an 80 MHz EHT PPDU allocated based on non-OFDMA (i.e., a non-OFDMA full bandwidth 80 MHz PPDU) may be configured based on a 996-RU, and may include 5 DC tones, 12 left guard tones, and 11 right guard tones. A tone-plan for 160/240/320 MHz may be configured in such a manner that the pattern ofFIG.5is repeated several times. The PPDU ofFIG.13may be determined (or identified) as an EHT PPDU based on the following method. A receiving STA may determine a type of an RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the EHT PPDU: 1) when a first symbol after an L-LTF signal of the RX PPDU is a BPSK symbol; 2) when RL-SIG in which the L-SIG of the RX PPDU is repeated is detected; and 3) when a result of applying “module3” to a value of a length field of the L-SIG of the RX PPDU is detected as “0”. When the RX PPDU is determined as the EHT PPDU, the receiving STA may detect a type of the EHT PPDU (e.g., an SU/MU/Trigger-based/Extended Range type), based on bit information included in a symbol after the RL-SIG ofFIG.13. In other words, the receiving STA may determine the RX PPDU as the EHT PPDU, based on: 1) a first symbol after an L-LTF signal, which is a BPSK symbol; 2) RL-SIG contiguous to the L-SIG field and identical to L-SIG; 3) L-SIG including a length field in which a result of applying “modulo 3” is set to “0”; and 4) a 3-bit PHY version identifier of the aforementioned U-SIG (e.g., a PHY version identifier having a first value). For example, the receiving STA may determine the type of the RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the HE PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; 2) when RL-SIG in which the L-SIG is repeated is detected; and 3) when a result of applying “module3” to a value of a length field of the L-SIG is detected as “1” or “2.” For example, the receiving STA may determine the type of the RX PPDU as a non-HT, HT, and VHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the non-HT, HT, and VHT PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; and 2) when RL-SIG in which L-SIG is repeated is not detected. In addition, even if the receiving STA detects that the RL-SIG is repeated, when a result of applying “modulo 3” to the length value of the L-SIG is detected as “0,” the RX PPDU may be determined as the non-HT, HT, and VHT PPDU. In the following example, a signal represented as a (TX/RX/UL/DL) signal, a (TX/RX/UL/DL) frame, a (TX/RX/UL/DL) packet, a (TX/RX/UL/DL) data unit, (TX/RX/UL/DL) data, or the like may be a signal transmitted/received based on the PPDU ofFIG.13. The PPDU ofFIG.13may be used to transmit/receive frames of various types. For example, the PPDU ofFIG.13may be used for a control frame. An example of the control frame may include a request to send (RTS), a clear to send (CTS), a power save-poll (PS-poll), BlockACKReq, BlockAck, a null data packet (NDP) announcement, and a trigger frame. For example, the PPDU ofFIG.14may be used for a management frame. An example of the management frame may include a beacon frame, a (re-)association request frame, a (re-)association response frame, a probe request frame, and a probe response frame. For example, the PPDU ofFIG.13may be used for a data frame. For example, the PPDU ofFIG.13may be used to simultaneously transmit at least two or more of the control frame, the management frame, and the data frame. FIG.14illustrates an example of a modified transmission device and/or receiving device of the present specification. Each device/STA of the sub-figure (a)/(b) ofFIG.1may be modified as shown inFIG.15. A transceiver630ofFIG.14may be identical to the transceivers113and123ofFIG.1. The transceiver630ofFIG.14may include a receiver and a transmitter. A processor610ofFIG.14may be identical to the processors111and121ofFIG.1. Alternatively, the processor610ofFIG.14may be identical to the processing chips114and124ofFIG.1. A memory620ofFIG.14may be identical to the memories112and122ofFIG.1. Alternatively, the memory620ofFIG.14may be a separate external memory different from the memories112and122ofFIG.1. Referring toFIG.14, a power management module611manages power for the processor610and/or the transceiver630. A battery612supplies power to the power management module611. A display613outputs a result processed by the processor610. A keypad614receives inputs to be used by the processor610. The keypad614may be displayed on the display613. A SIM card615may be an integrated circuit which is used to securely store an international mobile subscriber identity (IMSI) and its related key, which are used to identify and authenticate subscribers on mobile telephony devices such as mobile phones and computers. Referring toFIG.14, a speaker640may output a result related to a sound processed by the processor610. A microphone641may receive an input related to a sound to be used by the processor610. Hereinafter, technical features applicable to the EHT standard may be described. According to an embodiment, in the EHT standard, a PPDU of a 320 MHz bandwidth may be supported. In addition, 240 MHz and 160+80 MHz transmission may be supported. The 240 MHz and 160+80 MHz may be configured by applying preamble puncturing of 320 MHz to 80 MHz. For example, the 240 MHz and 160+80 MHz bandwidths may be configured based on three 80 MHz channels including the primary 80 MHz. According to an embodiment, in the EHT standard, an flax standard tone plan may be used for a 20/40/80/160 MHz PPDU. According to an embodiment, a 160 MHz OFDMA tone plan of the flax standard may be duplicated and used for a 320 MHz PPDU. According to an embodiment, the 240 MHz and 160+80 MHz transmission may be composed of three 80 MHz segments. According to an embodiment, the 160 MHz tone plan may be duplicated and used for the non-OFDMA tone plan of the 320 MHz PPDU. According to an embodiment, in each 160 MHz segment for the non-OFDMA tone plan of the 320 MHz PPDU, 12 and 11 null tones may be configured on the leftmost and rightmost sides, respectively. According to an embodiment of the present specification, the data part of the EHT PPDU may use the same subcarrier spacing as the data part of the IEEE 802.11ax standard. Hereinafter, technical features of a resource unit (RU) applicable to the EHT standard will be described. According to an embodiment of the present specification, in the EHT standard, one or more RUs may be allocated to a single STA. For example, coding and interleaving schemes for multiple RUs allocated to a single STA may be variously set. According to an embodiment of the present specification, small-size RUs may be aggregated with other small-size RUs. According to an embodiment of the present specification, large-size RUs may be aggregated with other large-size RUs. For example, RUs of 242 tones or more may be defined/set as ‘large size RUs’. For another example, RUs of less than 242 tones may be defined/configured as ‘small size RUs’. According to an embodiment of the present specification, there may be one PSDU per STA for each link. According to an embodiment of the present specification, for LDPC encoding, one encoder may be used for each PSDU. Small-Size RUs According to an embodiment of the present specification, an aggregation of small-size RUs may be set so as not to cross a 20 MHz channel boundary. For example, RU106+RU26 and RU52+RU26 may be configured as an aggregation of small-size RUs. According to an embodiment of the present specification, in PPDUs of 20 MHz and 40 MHz, contiguous RU26 and RU106 may be aggregated/combined within a 20 MHz boundary. According to an embodiment of the present specification, in PPDUs of 20 MHz and 40 MHz, RU26 and RU52 may be aggregated/combined. For example, in 20 MHz (or 20 MHz PPDU), an example of contiguous RU26 and RU52 may be shown throughFIG.21. FIG.15shows an example of an aggregation of RU26 and RU52 in 20 MHz. Referring toFIG.15, shaded RU26 and RU52 may be aggregated. For example, the second RU26 and the second RU52 may be aggregated. For another example, the seventh RU and the third RU52 may be aggregated. For example, in 40 MHz, an example of contiguous RU26 and RU52 is described inFIG.15. FIG.16shows an example of an aggregation of RU26 and RU52 in 40 MHz. Referring toFIG.16, shaded RU26 and RU52 may be aggregated. For example, the second RU26 and the second RU52 may be aggregated. For another example, the eighth RU26 and the third RU52 may be aggregated. For another example, the eleventh RU26 and the sixth RU52 may be aggregated. For another example, the seventeenth RU26 and the seventh RU52 may be aggregated. According to an embodiment of the present specification, RU26 and RU52 may be aggregated/combined in a PPDU of 80 MHz. For example, an example of contiguous RU26 and RU52 in 80 MHz may be shown byFIG.17. FIG.17shows an example of an aggregation of RU26 and RU52 in 80 MHz. Referring toFIG.17, 80 MHz may be divided into the first 40 MHz and the second 40 MHz. For example, within the first 40 MHz, the 8th RU26 and the 3rd RU52 may be aggregated. For another example, within the first 40 MHz, the 11th RU26 and the 6th RU52 may be aggregated. For another example, within the second 40 MHz, the 8th RU26 and the 3rd RU52 may be aggregated. For another example, within the second 40 MHz, the 11th RU26 and the 6th RU52 may be aggregated. According to an embodiment, when LDPC coding is applied, a single tone mapper may be used for RUs having less than 242 tones. Large-Size RUs According to an embodiment, in OFDMA transmission of 320 MHz for a single STA, an aggregation of a large-size RUs may be allowed only within a primary 160 MHz or a secondary 160 MHz. For example, the primary 160 MHz (channel) may consist of a primary 80 MHz (channel) and a secondary 80 MHz (channel). The secondary 160 MHz (channel) can be configured with channels other than the primary 160 MHz. According to an embodiment, in OFDMA transmission of 240 MHz for a single STA, an aggregated of large-size RUs may be allowed only within 160 MHz (band/channel), and the 160 MHz may consist of two adjacent 80 MHz channels. According to an embodiment, in OFDMA transmission of 160+80 MHz for a single STA, an aggregation of large-size RUs may be allowed only within a continuous 160 MHz (band/channel) or within the remaining 80 MHz (band/channel). In 160 MHz OFDMA, an aggregation of large-size RUs configured as shown in Table 8 may be supported. TABLE 8RU sizeAggregate BWNotes484 + 996120 MHz4 options In 80 MHz OFDMA, an aggregation of large-size RUs configured as shown in Table 9 may be supported. TABLE 9RU sizeAggregate BWNotes484 + 24260 MHz4 options In 80 MHz non-OFDMA, an aggregation of large-size RUs configured as shown in Table 10 may be supported. In 80 MHz non-OFDMA, puncturing can be applied. For example, one of four 242 RUs may be punctured. TABLE 10RU sizeAggregate BWNotes484 + 24260 MHz4 options In 160 MHz non-OFDMA, an aggregation of large-size RUs configured as shown in Table 11 may be supported. In 160 MHz non-OFDMA, puncturing can be applied. For example, one of eight 242 RUs may be punctured. For another example, one of four 484 RUs may be punctured. TABLE 1180 MHz80 MHzRU SizeRU sizeAggregate BWNotes484996120 MHz4 options484 + 242996140 MHz8 options In 240 MHz non-OFDMA, an aggregation of large-size RUs configured as shown in Table 12 may be supported. In 240 MHz non-OFDMA, puncturing can be applied. For example, one of six 484 RUs may be punctured. For another example, one of three 996 RUs may be punctured. TABLE 1280 MHz80 MHz80 MHzRU sizeRU sizeRU sizeAggregate BWNotes484996996200 MHz6 options—996996460 MHz3 options In 320 MHz non-OFDMA, an aggregation of large-size RUs configured as shown in Table 13 may be supported. In 320 MHz non-OFDMA, puncturing can be applied. For example, one of eight 484 RUs may be punctured. For another example, one of four 996 RUs may be punctured. TABLE 1380 MHz80 MHz80 MHz80 MHzRU sizeRU sizeRU sizeRU sizeAggregate BWNotes484996996996280 MHz8 options—996996996240 MHz4 options Hereinafter, technical features related to the operating mode will be described. According to an embodiment, a station (STA) supporting the EHT standard STA (hereinafter, “EHT STA”) or a station (STA) supporting the EHT standard STA (hereinafter, “HE STA”) may operate in a 20 MHz channel width mode. In the 20 MHz channel width mode, the EHT STA may operate by reducing the operating channel width to 20 MHz using an operating mode indication (OMI). According to an embodiment, the EHT STA (or HE STA) may operate in an 80 MHz channel width mode. For example, in the 80 MHz channel width mode, the EHT STA may operate by reducing the operating channel width to 80 MHz using an operating mode indication (OMI). According to an embodiment, the EHT STA may support sub-channel selective transmission (SST). An STA supporting the SST can quickly select (and switch to) another channel between transmissions to cope with fading in a narrow sub-channel. The 802.11be standard (i.e., the EHT standard) can provide a higher data rate than the 802.11ax standard. The EHT (i.e., extreme high throughput) standard can support wide bandwidth (up to 320 MHz), 16 streams, and multi-band operation. In the EHT standard, various preamble puncturing or multiple RU allocation may be supported in wide bandwidth (up to 320 MHz) and SU/MU transmission. In addition, in the EHT standard, a signal transmission/reception method through 80 MHz segment allocation is considered in order to support an STA with low end capability (e.g., 80 MHz only operating STA). Accordingly, in the following specification, a method of configuring/transmitting an EHT-SIG for the MU transmission in consideration of sub-channel selective transmission (SST) defined in the flax standard and Multi-RU aggregation may be proposed. For example, the EHT-SIG may be configured as a self-contained EHT-SIG. When the self-contained EHT-SIG is used, a technical feature for signaling RU allocation may be proposed in the present specification. EHT PPDU Configuration In order to support a transmission method based on the EHT standard, a new frame format may be used. When transmitting a signal through the 2.4/5/6 GHz band based on the new frame format, conventional Wi-Fi receivers (or STAs) (e.g., 802.11n) as well as receivers supporting the EHT standard receivers in compliance with the 802.11n/ac/ax standard) can also receive EHT signals transmitted through the 2.4/5/6 GHz band. The preamble of the PPDU based on the EHT standard can be set in various ways. Hereinafter, an embodiment of configuring the preamble of the PPDU based on the EHT standard will be described. Hereinafter, a PPDU based on the EHT standard may be described as an EHT PPDU. However, the EHT PPDU is not limited to the EHT standard. The EHT PPDU may include not only the 802.11be standard (i.e., the EHT standard), but also a PPDU based on a new standard that is improved/evolved/extended with the 802.11be standard. FIG.18shows an example of an EHT PPDU. Referring toFIG.18, an EHT PPDU1800may include an L-part1810and an EHT-part1820. The EHT PPDU1800may be configured in a format to support backward compatibility. In addition, the EHT PPDU1800may be transmitted to a single STA and/or multiple STAs. The EHT PPDU1800may be an example of an MU-PPDU of the EHT standard. The EHT PPDU1800may include the L-part1810preceding the EHT-part1820for coexistence or backward compatibility with a legacy STA (e.g., STA in compliance with the 802.11n/ac/ax standard). For example, the L-part1810may include L-STF, L-LTF, and L-SIG. For example, phase rotation may be applied to the L-part1810. According to an embodiment, the EHT part1820may include RL-SIG, U-SIG1821, EHT-SIG1822, EHT-STF, EHT-LTF, and data fields. Similar to the 11ax standard, RL-SIG may be included in the EHT part1820for L-SIG reliability and range extension. The RL-SIG may be transmitted immediately after the L-SIG, and may be configured to repeat the L-SIG. For example, four additional subcarriers may be applied to L-SIG and RL-SIG. The extra subcarriers may be configured at subcarrier indices [−28, −27, 27, 28]. The extra subcarriers may be modulated in a BPSK scheme. In addition, coefficients of [−1−1 −1 1] may be mapped to the extra subcarriers. For example, the EHT-LTF may be one of 1×EHT-LTF, 2× EHT-LTF, or 4× EHT-LTF. The EHT standard may support EHT-LTF for 16 spatial streams. Each field inFIG.18may be the same as the corresponding field described inFIG.13. Hereinafter, technical features that can be further improved in the present specification will be described. In a wireless LAN system, a 6 GHz band may be newly established. The 6 GHz band may include 20/40/80/160/320 MHz channels in the frequency domain described with reference toFIG.12. For example, when transmitting and receiving a signal in an indoor environment through the 6 GHz band, low power transmission may have to be performed. That is, for the existing transceiver used in the 6 GHz band, the transmission power of the wireless LAN signal may be limited. As a result, when a PPDU (for example, the EHT PPDU) is transmitted/received through a 6 GHz band, a problem in that a transmission range is shortened due to the low power transmission may occur. Accordingly, the present specification proposes a transmission/reception technique for range extension. On the other hand, although the example of the present specification is preferably applied to PPDU transmission/reception in the 6 GHz band, it may be used in other bands in which a problem of a short transmission range may occur. The present specification proposes various technical features for range extension. The various technical features proposed in the present specification are preferably applied to the transmission/reception PPDU. In other words, an example of the present specification proposes various transmission/reception PPDUs for range extension. An example of the transmitting/receiving PPDU may include various fields described inFIGS.3,7,8,13,18, and19. More specifically, an example of the transmission/reception PPDU may include at least one legacy field (for example, L-STF, L-LTF, L-SIG, and RL-SIG inFIG.18). In addition, an example of the transmission/reception PPDU includes a first control signal field (for example, U-SIG field) and a second control signal field (for example, EHT-SIG field) for the transmission/reception PPDU. For example, the first control signal field may be the U-SIG1821ofFIG.18, and the second control signal field may be the EHT-SIG1822ofFIG.18. In addition, an example of the transmitting/receiving PPDU may include an STF (for example, EHT-STF), an LTF (for example, EHT-LTF), and a data field. Various technical features for range extension may be applied to the first control signal field (for example, U-SIG field), the second control signal field (for example, EHT-SIG field), an STF (for example, EHT-STF), an LTF (for example, EHT-LTF), and/or data field. Hereinafter, the first control signal field (for example, U-SIG field) and the second control signal field (for example, EHT-SIG field) will be described in detail. Control information not included in the first control signal field (for example, U-SIG field) may be referred to by various names such as overflowed information or overflow information. The second control signal field (for example, EHT-SIG field) may include a common field and a user specific field. Each of the common field and the user specific field may include at least one encoding block (for example, a binary convolutional code (BCC) encoding block). One encoding block may be transmitted/received through at least one symbol, and one encoding block is not necessarily transmitted through one symbol. Meanwhile, one symbol for transmitting the encoding block may have a symbol length of 4 μs. The transmission/reception PPDU proposed in the present specification may be used for communication for at least one user. For example, the technical features of the present specification may be applied to an MU-PPDU (for example, EHT MU PPDU) according to the 11be standard. FIG.19shows an example of the first control signal field or the U-SIG field of the present specification. As illustrated, the first control signal field (for example, U-SIG field) may include a version independent field1910and a version dependent field1920. For example, the version independent field1910may include control information that is continuously included regardless of the version of the WLAN (for example, IEEE 802.11be and the next-generation standards of 11be). For example, the version dependent field1920may include control information dependent on a corresponding Version (for example, IEEE 802.11be standard). For example, the version independent field1910may include a 3-bit version identifier indicating 11be and a Wi-Fi version after 11be, a 1-bit DL/UL field BSS color, and/or information related to TXOP duration. For example, the version dependent field1920may include information related to PPDU format type and/or Bandwidth, and MCS. For example, in the first control signal field (for example, U-SIG field) shown inFIG.19, two symbols (for example, two consecutive 4 μs-long symbols) may be jointly encoded. In addition, the field ofFIG.19may be configured based on 52 data tones and 4 pilot tones for each 20 MHz band/channel. In addition, the field ofFIG.19may be modulated in the same manner as the HE-SIG-A of the conventional 1 lax standard. In other words, the field ofFIG.19may be modulated based on the BPSK 1/2 code rate. For example, the second control signal field (for example, EHT-SIG field) may be divided into a common field and a user specific field, and may be encoded based on various MCS levels. For example, the common field may include indication information related to a spatial stream used in a transmission/reception PPDU (for example, a data field) and indication information related to an RU. For example, the user specific field may include ID information used by at least one specific user (or receiving STA), MCS, and indication information related to coding. In other words, the user specific field may include decoding information for a data field (for example, STA ID information allocated to the RU, MSC information, and/or channel coding type/rate information) transmitted through at least one RU indicated by an RU allocation sub-field included in the common field. An example of an information field/bit that may be included in the first control signal field (for example, U-SIG field) is shown in table 14 below. As will be described below, since there is a restriction on the length of the first control signal field (for example, U-SIG field), some of the fields in table 14 may overflow into other fields. That is, the bit lengths described in the table below may be changed, and at least one of the individual fields/bits listed in the table below may be omitted. Also, other fields/bits may be added. TABLE 14fieldbitsPHY version Identifier3TXOP7BSS Color6DL/UL1BW3PPDU format2# of EHT-SIG symbol5EHT-SIG MCS2GI + LTF2NSTS4Coding1LDPC Extra symbol1Beamformed1Pre-FEC padding2PE Disambiguity1doppler1spatial reuse4beam change1DCM1HARQ1Multi-AP1Compression½Puncturing pattern of 80 MHz segment/BW¾CRC4Tail6 The first control signal field (for example, U-SIG field) may consist of two consecutive symbols. In this case, the maximum number of bits that can be included in the first control signal field (for example, U-SIG field) may be fixed or preset (for example, fixed to 48/52 bits or preset). Accordingly, information that is not included in the first control signal field (for example, U-SIG field) may exist, and such information may be referred to by various names such as overflowed information, overflow information, U-SIG overflow, and U-SIG overflow information/field. According to an example of the present specification, the overflowed information is preferably included in the second control signal field (for example, EHT-SIG field). In addition, since the overflowed information may not be user specific information, the corresponding information is preferably included in the Common field of the second control signal field (for example, EHT-SIG field). The bandwidth of the first control signal field (for example, U-SIG field) may be 20 MHz. For example, in an 80 MHz PPDU, the U-SIG field may be duplicated 4 times on a frequency. The U-SIG field may include information about a pattern of preamble puncturing applied to the 80 MHz band. For example, the 160 MHz PPDU may include a first U-SIG field for the first 80 MHz band and a second U-SIG field for the second 80 MHz band. The first U-SIG field may include information on a pattern of preamble puncturing applied to the first 80 MHz band. The second U-SIG field may include information on a pattern of preamble puncturing applied to the second 80 MHz band. For example, the 320 MHz PPDU may include first to fourth U-SIG fields, and each U-SIG field may include information about a corresponding 80 MHz puncturing pattern. The PPDU according to the present specification may be configured based on various modes. For example, the PPDU may be configured based on a plurality of modes (or transmission modes) including the first mode and the second mode. Mode used herein may be replaced by various terms. For example, the mode may be replaced with various expressions such as format, type, PPDU format, PPDU type, preamble format, preamble type, transmission format, and transmission type. The structure of the PPDU of the present specification may be configured differently according to the mode. For example, the PPDU configured based on the first mode may include a control signal field (for example, U-SIG field) having the first structure or may include a payload (that is, data field) having the first structure. For example, the PPDU configured based on the second mode may include a control signal field (for example, U-SIG field) having the second structure or may include a payload (that is, data field) having the second structure. The control signal field (for example, U-SIG field) having the first structure and the control signal field (for example, U-SIG field) having the second structure may include some identical fields and different fields. Some of the plurality of (transmission) modes (for example, the first/second mode) may be related to range extension. A wireless LAN (WLAN) system may support a new 6 GHz band in addition to the conventional 2.4 GHz band and 5 GHz band. However, in consideration of the existing 6 GHz equipment, there is a restriction on the transmission power of the WLAN signal related to the 6 GHz band. Due to the limitation of the transmission power, the transmission/reception range of the 6 GHz wireless LAN signal may be reduced. The range extension is related to a technical feature that increases the transmission/reception range of a wireless LAN signal. The range extension is preferably related to communication in the 6 GHz band, but may also be related to the 2.4 GHz band and/or the 5 GHz band. The range extension may be related to various communication and may be related only to single user (SU) communication. In the present specification, the first mode may be referred to as various expressions such as an Extended Range Single User (ER SU) mode. In the present specification, the second mode may be referred to as various expressions such as a duplicate (DUP) transmission mode, an EHT DUP transmission mode, or a SU DUP mode. For example, a control signal field (for example, U-SIG field) included in the PPDU configured based on the first mode may include the following control fields (or subfields). Specifically, the U-SIG field configured based on the first mode may include a U-SIG1 part and a U-SIG2 part. In this case, each of the U-SIG1 part and the U-SIG2 part may include 26-bits information. For example, bits B0 to B2 of the U-SIG1 part may include a field related to PHY Version Identifier, bits B3 to B5 of the U-SIG1 part may include a field related to the bandwidth of the PPDU, the B6 bit of the U-SIG1 part may include a field regarding whether the PPDU is used for UL communication or this communication, bits B7 to B12 of the U-SIG1 part may include a field related to a 6-bit identifier for BSS color, bits B13 to B19 of the U-SIG1 part may include information on the TXOP duration for the PPDU, and bits B20 to B25 of the U-SIG1 part may include a reserved field. For example, bits B0 to B15 of the U-SIG2 part may include a reserved field, and bits B16 to B19 of the U-SIG2 part may include CRC information. The CRC information may be generated based on bits B0 to B25 of the U-SIG1 part and bits B0 to B15 of the U-SIG2 part. Bits B20 to B25 of the U-SIG2 part are tail bits and may be set to 0 for the initialization of the convolutional decoder. For example, a control signal field (for example, U-SIG field) included in a PPDU configured based on the second mode may include the following control fields (or subfields). Specifically, the U-SIG field configured based on the second mode may include a U-SIG1 part and a U-SIG2 part. In this case, each of the U-SIG1 part and the U-SIG2 part may include 26-bits information. For example, bits B0 to B2 of the U-SIG1 part may include a field related to PHY Version Identifier, bits B3 to B5 of the U-SIG1 part may include a field related to the bandwidth of the PPDU, bit B6 of the U-SIG1 part may include a field related to whether the PPDU is used for UL communication or this communication, bits B7 to B12 of the U-SIG1 part may include a field related to a 6-bit identifier related to BSS color, bits B13 to B19 of the U-SIG1 part may include information about the TXOP duration for the PPDU, bits B20 to B24 of the U-SIG1 part may include a reserved field, and bit B25 of the U-SIG1 part may include a validate field. For example, bits B0 to B1 of the U-SIG2 part may include information about the type and compression mode of the PPDU, B2 bit of the U-SIG2 part may include a validate field, bits B3 to B7 of the U-SIG2 part may include a field related to Punctured Channel Information applied to the PPDU, B8 bit of the U-SIG2 part may include a validate field, bits B9 to B10 of the U-SIG2 part may include a field related to MCS applied to a second control signal (for example, EHT-SIG) included in the PPDU, bits B11 to B15 of the U-SIG2 part may include a field related to how many symbols the second control signal (for example, EHT-SIG) included in the PPDU is transmitted, and bits B16 to B19 of the U-SIG2 part may include CRC information. The CRC information may be generated based on bits B0 to B25 of the U-SIG1 part and bits B0 to B15 of the U-SIG2 part. Bits B20 to B25 of the U-SIG2 part may be tail bits and may be set to 0 for the initialization of the convolutional decoder. A PPDU configured based on the second mode (for example, EHT DUP or SU DUP mode) may have the following technical features. For example, the PPDU related to the second mode may have a bandwidth of 80/160/320 MHz, and preamble puncturing may not be applied. The payload (that is, data field) of the PPDU related to the second mode is modulated based on BPSK, and a DCM scheme may be applied. The payload (that is, data field) of the PPDU related to the second mode may support only one Spatial Stream (SS). When the PPDU related to the second mode has an 80 MHz bandwidth, the corresponding data field may include a first 484-tone RU and a second 484-tone RU in which the first 484-tone RU is duplicated. That is, the first and second 484-tone RUs may be transmitted through different frequency domains in the same time interval. When the PPDU related to the second mode has a bandwidth of 160 MHz, the payload may include two duplicated 996-tone RUs. When the PPDU related to the second mode has a 320 MHz bandwidth, the payload may include two duplicated 2*996-tone RUs. A PPDU based on the present specification may include a first control signal field (for example, U-SIG field) having the following technical characteristics. Various technical features described below may be applied to various modes including the first/second mode. For example, various technical features described below may be applied to the first mode (that is, ER SU mode). Technical features 1. The PPDU configured based on the first mode may be referred to by various names such as an 11be extended range (ER) PPDU. Examples of various technical features applied to the 11be ER PPDU may be as follows. Technical features 1.a. The first control signal field (for example, U-SIG field) of the PPDU includes Common information. In order to increase the robustness of the U-SIG, the U-SIG may be transmitted through a repeated symbol (for example, four repeated symbols) in a time domain. Technical features 1.a.i. A method of configuring a symbol that is repeated in the time domain for the U-SIG may be determined in various ways. For example, it is possible that the symbol for the U-SIG is simply repeated. FIG.20shows an example of a symbol for a control signal field according to the present specification. Technical features 1.a.i.1. As in the example ofFIG.20, the U-SIG may be transmitted through a total of 4 symbols (for example, a total of 4 OFDM symbols). In other words, the U-SIG may be repeated in units of one symbol. That is, as shown inFIG.20, the U-SIG may be transmitted through U-SIG1, RU-SIG1 (that is, the repeated signal of U-SIG1), U-SIG2, and RU-SIG2 (that is, the repeated signal of U-SIG2). U-SIG1 shown inFIG.20may correspond to U-SIG1 including bits B0 to B25 as described above, U-SIG2 shown inFIG.20may correspond to U-SIG2 including bits B0 to B25 as described above. Technical features 1.a.ii. The example ofFIG.20may be variously modified. That is, the example ofFIG.20may be variously modified as follows. Technical features 1.a.ii.1. For example, interleaving may not be applied to repeated U-SIG symbols (that is, RU-SIG1 and/or RU-SIG2 ofFIG.20). Additionally or alternatively, the repeated U-SIG symbol (that is, RU-SIG1 and/or RU-SIG2 ofFIG.20) may be further multiplied by a bipolar value/sequence or a preset sequence. In other words, RU-SIG1 (or RU-SIG2) ofFIG.20may be generated in such a way that ‘-1’ or a preset sequence is multiplied by U-SIG1 (or U-SIG2). Technical features 1.a.ii.2. In the example ofFIG.20, interleaving is applied to U-SIG1 and U-SIG2, but interleaving may be omitted for repeated U-SIG symbols (that is, RU-SIG1 and/or RU-SIG2 inFIG.20). Technical features 1.a.ii.3. BPSK may be applied to U-SIG1 and U-SIG2 shown in the example ofFIG.20. In addition, QBPSK may be applied to RU-SIG1 and/or RU-SIG2 shown in the example ofFIG.20. The PPDU based on the present specification may include a second control signal field (for example, EHT-SIG field) for allocation of a resource unit (RU). The following technical features may be applied to a PPDU (for example, 11be ER PPDU) configured based on the first mode. Technical features 1.b. The second control signal field (for example, EHT-SIG field) of the present specification may be transmitted through a symbol that is repeated in the time domain. That is, the symbol for the EHT-SIG of the present specification may be repeated in the time domain for range extension. Additionally or alternatively, a dual carrier modulation (DCM) scheme may be applied to the symbol for the EHT-SIG of the present specification. FIG.21shows another example of a symbol for a control signal field according to the present specification. Technical features 1.b.i. The EHT-SIG symbol may be repeated in the time domain based on the example ofFIG.21. Technical features 1.b.i.1. As shown inFIG.21, the EHT-SIG may consist of 2 symbols and the entire EHT-SIG field may be transmitted through a total of 4 symbols. Technical features 1.b.i.1.a. For example, as shown inFIG.21, the EHT-SIG may be transmitted based on a structure that is repeated in symbol units on the time domain. Specifically, the EHT-SIG field may consist of EHT-SIG1 and EHT-SIG2, the EHT-SIG1 may be repeated on the time domain as in the example ofFIG.21, the EHT-SIG2 may also be repeated in the time domain. That is, as the example ofFIG.21, REHT-SIG1 in which the EHT-SIG1 is repeated and REHT-SIG2 in which the EHT-SIG2 is repeated may be configured. Technical features 1.b.i.1.b. In the example ofFIG.21, the application of interleaving may be omitted for repeated symbols. Specifically, in the example ofFIG.21, interleaving may be applied to EHT-SIG1 and EHT-SIG2, and interleaving may be omitted for REHT-SIG1 and REHT-SIG2. Technical features 1.b.i.1.c. The above-described technical features may be variously changed. For example, in the example ofFIG.21, repeated symbols (that is, REHT-SIG1 and/or REHT-SIG2) may be configured by a method of applying phase rotation to non-repeated symbols (that is, EHT-SIG1 and/or EHT-SIG2). For example, a repeated symbol (that is, REHT-SIG1 and/or REHT-SIG2) may be configured by multiplying a non-repeated symbol (that is, EHT-SIG1 and/or EHT-SIG2) by a value of −1, −j, +j, or the like. For example, it may be possible to configure the non-repeated symbols (that is, EHT-SIG1 and/or EHT-SIG2) based on the BPSK scheme, and it may be also possible to configure the repeated symbols (that is, REHT-SIG1 and/or REHT-SIG2) based on the QBPSK scheme. FIG.22shows another example of a symbol for a control signal field according to the present specification. Technical features 1.b.i.1.d. The above-described example may be variously modified. For example, the EHT-SIG may be configured through one encoding block, and common information and identification information about a single user may be included in the one encoding block. In this case, in order to be repeated in units of encoding blocks, the EHT-SIG composed of 2 symbols may be repeated and included in the PPDU. In other words, as shown inFIG.22, one encoding block for EHT-SIG may be transmitted through 2 symbols. As shown inFIG.22, the EHT-SIG may include the first two symbols and two repeated symbols (that is, REHT-SIG). Technical features 1.b.i.1.e. In the example ofFIG.22, interleaving may be omitted for a repeated symbol (that is, EHT-SIG2symbol). Technical features 1.b.i.2. The control signal field (that is, EHT-SIG) according to the present specification may be variously configured. That is, as in the examples ofFIGS.21and22, the EHT-SIG may consist of one symbol. FIG.23shows another example of a symbol for a control signal field according to the present specification. As in the example ofFIG.23, the EHT-SIG may consist of one symbol and may be repeated in the time domain. Technical features 1.b.i.2.a. When the EHT-SIG is configured through one symbol, the EHT-SIG may not include STA-ID information and/or user specific information. Technical features 1.b.i.2.b. In an example ofFIG.23, REHT-SIG indicates a repeated signal of an EHT-SIG symbol composed of one symbol. Technical Features 1.b.i.2.c. In the example ofFIG.23, interleaving may be omitted for REHT-SIG. Additionally or alternatively, the EHT-SIG may be configured based on BPSK, and the REHT-SIG may be configured based on QPBSK. Technical features 1.b.i.3. In the above-described example, whether the DCM scheme is applied to the EHT-SIG may be indicated. In this case, it is preferable that the indication information about the DCM scheme is included in the control field in the U-SIG. The above technical features are mainly related to the control signal field (that is, U-SIG and EHT-SIG) of the PPDU. Hereinafter, technical features related to the payload (that is, data field) of a PPDU (for example, 11be ER PPDU) configured based on the first mode will be described. Technical features 1.c. The PPDU (for example, 11be ER PPDU) configured based on the first mode may have various bandwidths, but preferably may have a 20 MHz bandwidth. This is because power boosting is easy when a 20 MHz bandwidth is used. In this case, the following technical features may be applied to RUs and multiple RUs (MRUs) used for the payload (that is, data field) of the PPDU. Technical features 1.c.i. A PPDU (for example, 11be ER PPDU) configured based on the first mode may include the RU shown inFIG.4. Specifically, the PPDU of the present specification may include a 52+26-tone MRU, a 106+26-tone MRU, and the like, along with the 26-tone RU, 52-tone RU, and 106-tone RU shown inFIG.4. Technical features 1.c.ii. The PPDU of the present specification may include a combination of various RUs according to two methods described below for an extended range. Technical features 1.c.ii.1. For example, the 11be ER PPDU according to the first method may use RUs of any size. For example, a total of 6 RU sizes (or RU types) such as 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 52+26-tone MRU, and 106+26-tone MRU may be used. Technical features 1.c.ii.1.a. For example, the 11be ER PPDU may include a payload (that is, a data field) configured based on any one of the six RU sizes (or types) described above. Technical features 1.c.ii.1.b. The RU (or MRU) used for the payload (that is, data field) of the 11be ER PPDU may be a fixed RU/MRU as follows. For example, the RU index may start from a low or high frequency region in the tone plan (that is, RU location) shown inFIG.4.i. 26 RU-26 RU index1ii. 52 RU-52 RU index1iii. 26+52 RU-26 RU index2+52 RU index2iv. 106 RU-106 RU index 1v. 26+106 RU-106 RU index 1+26 RU index5vi. 242 RU Technical features 1.c.ii.2. In the first method described above, a total of 6 RU sizes/types are used, but according to the second method described below, only RUs of 106-tone or more can be used. Technical features 1.c.ii.2.a. For example, only one of 106-tone RU, 106+26-tone RU, and 242-tone RU may be used for the payload (that is, data field) of the 11be ER PPDU. Technical features 1.c.ii.2.b. As another example, it is possible to use only 106-tone RU and 242-tone RU except for the 106+26-tone RU. Technical features 1.c.ii.2.c. For the RUs of the above-described Technical features 1.c.ii.2.a and Technical features 1.c.ii.2.b, the RU location may be determined based on the above-described technical characteristic 1.c.ii.1.b. Technical features 1.c.ii.3. Since the bandwidth of the 11be ER PPDU can be fixed to 20 MHz, the BW field (for example, 3 bits) included in the U-SIG of the 11be ER PPDU can be used for other purposes. Technical features 1.c.ii.3.a. For example, the BW field (for example, 3 bits) included in the U-SIG may include information indicating RU information, not bandwidth. Technical features 1.c.ii.3.a.i. For example, when a method using a total of six RU sizes/types is used, the 3-bit BW field included in the U-SIG may include information about the RU size/type according to the method shown in Table 15 below. TABLE 15BW 3 bitsRU size026152252 + 2631064106 + 2652426~7Reserved Technical features 1.c.ii.3.a.ii. For example, when a method using a total of three RU sizes/types is used, the 3-bit BW field included in the U-SIG may include information on the RU size/type according to the method shown in Table 16 below. TABLE 16BW 3 bitsRU size01061106 + 2622423~7Reserved Technical features 1.c.ii.3.a.iii. For example, when a method using a total of two RU sizes/types is used, the 3-bit BW field included in the U-SIG may include information on the RU size/type according to the method shown in Table 17 below. TABLE 17BW 3 bitsRU size010612422~7Reserved Various technical features described below may be additionally applied to the PPDU of the present specification. Technical features 2. For example, one Spatial Stream (SS) may be used for the payload (that is, data field) of the PPDU used for the extended range. In addition, MCSO (that is, a BPSK scheme and a channel coding scheme based on 1/2 code rate) may be applied to the counter PPDU. Technical features 3. As described above, since the EHT-SIG included in the PPDU of the present specification may be repeated in the time domain, it may be preferable that the control field of the U-SIG included in the corresponding PPDU include information about the EHT-SIG symbol. Technical features 3.a. For example, the control field of the U-SIG may indicate the total number of EHT-SIG symbols. For example, indication information related to a total of two symbols or a total of four symbols may be included in the U-SIG. Technical features 3.b. For another example, the control field of the U-SIG may indicate the number of symbols of the non-repeated EHT-SIG, not the entire EHT-SIG. Since the receiving STA already knows that the EHT-SIG is repeated, the total number of EHT-SIG symbols may not need to be indicated. For example, it may be indicated that one or two EHT-SIG symbols are used. A new WLAN system such as the 11be system may support different types of mode/transmission. For example, in the 11be system, both ER SU transmission, and SU-DUP mode for obtaining robustness of data transmission may be considered. In other words, the system of the present specification may support multiple modes including a first mode and a second mode, the first mode may be called various expressions such as ER SU mode, the second mode may be referred to as various expressions such as a duplicate (DUP) transmission mode, an EHT DUP transmission mode, or a SU DUP mode. As described above, the PPDU of the present specification may be individually configured according to the first mode and the second mode. Technical features 4. The PPDU configured based on the first mode (for example, ER SU mode) and the second mode (for example, SU DUP mode) may include the same technical feature. For example, technical features related to the above-described U-SIG and/or EHT-SIG may be equally applied to the first mode and the second mode. In other words, the symbol for transmitting the U-SIG and/or EHT-SIG of the PPDU configured based on the first mode (for example, ER SU mode) may be repeated in the time domain, and a symbol for transmitting the U-SIG and/or EHT-SIG of the PPDU configured based on the second mode (for example, SU DUP mode) may also be repeated in the time domain. Therefore, since the PHY preamble related to the first mode (for example, ER SU mode) and the PHY preamble related to the second mode (for example, SU DUP mode) may have the same configuration, an additional Technical features capable of distinguishing or discriminating the first mode and the second mode may be proposed. Technical features 4.a. For example, the first/second modes may be distinguished using constellation mapping or the phase of the U-SIG symbol. Technical features 4.a.i. For example, both the PPDU related to the first mode and the PPDU related to the second mode may include a U-SIG consisting of two parts (that is, U-SIG1 and U-SIG2), RU-SIG1 in which the U-SIG1 is repeated may be located after the U-SIG1, RU-SIG2 in which the U-SIG2 is repeated may be located after the U-SIG2. In this case, the constellation mapping and/or the phase of the U-SIG1 and the RU-SIG1 may be determined as one of tables 18 to 23 below. According to the following example, the first mode (for example, ER SU mode) and the second mode (for example, SU DUP mode) may be identified based on the U-SIG1 and RU-SIG1. For example, according to the example of Table 18 below, the U-SIG of the PPDU configured based on the first mode (for example, ER SU mode) is transmitted through a total of four symbols consisting of U-SIG1, RU-SIG1, U-SIG2, and RU-SIG2. In this case, a constellation mapping of U-SIG1 and RU-SIG1 related to the first mode may be determined as BPSK and QBPSK. In addition, constellation mapping of U-SIG1 and RU-SIG1 related to the second mode may be QBPSK and BPSK. In the following example, constellation mapping of U-SIG2 and RU-SIG2 may be BPSK. TABLE 18IndexU-SIG1RU-SIG11BPSKQBPSKER-SU2QBPSKBPSKSU-DUP TABLE 19IndexU-SIG1RU-SIG11BPSKQBPSKER-SU2QBPSKQBPSKSU-DUP TABLE 20IndexU-SIG1RU-SIG11QBPSKBPSKER-SU2BPSKQBPSKSU-DUP TABLE 21IndexU-SIG1RU-SIG11QBPSKBPSKER-SU2QBPSKQBPSKSU-DUP TABLE 22IndexU-SIG1RU-SIG11QBPSKQBPSKER-SU2BPSKQBPSKSU-DUP TABLE 23IndexU-SIG1RU-SIG11QBPSKQBPSKER-SU2QBPSKBPSKSU-DUP Technical features 4.b. The above-described technical features may be variously modified. For example, in the above example, both U-SIG1 related to the first mode and U-SIG1 related to the second mode have the same constellation mapping, but it is also possible that the RU-SIG1 related to the first mode and the RU-SIG1 related to the second mode have different constellation mappings and/or phases. Technical features 4.c. For example, it is also possible to distinguish the first mode and the second mode by multiplying any one symbol for U-SIG (for example, RU-SIG1) by different phase values (for example, −l, +j, −j). FIG.24is a flowchart illustrating an operation performed by a receiving STA. The receiving STA may be an AP STA or a user STA. The receiving STA may receive and decode the PPDU configured according to the above-described technical features. Based on S2410ofFIG.24, the receiving STA may receive a PPDU. For example, the PPDU may be received through a 6 GHz band. For example, the PPDU may be configured based on the first mode (for example, the above-described ER SU mode) or the second mode (for example, the above-described SU DUP mode). For example, the first mode may be expressed as a transmission mode related to an extended range (ER) preamble. For example, the second mode may be expressed as a transmission mode related to duplicate transmission. The PPDU may include a legacy signal (L-SIG) field, a repeated L-SIG (RL-SIG) field in which the L-SIG field is repeated, and a Universal Signal (U-SIG) field contiguous to the RL-SIG field. For example, the PPDU may include the L-SIG, RL-SIG, and U-SIG shown inFIGS.20to23. For example, the PPDU may further include the EHT-SIG shown inFIGS.20to23. The U-SIG field of the PPDU may be transmitted/received through consecutive first to fourth symbols. The first to fourth symbols may be U-SIG1, RU-SIG1, U-SIG2, and RU-SIG2 shown inFIGS.20to23. The first to fourth symbols may be contiguous with each other in the time domain. Among the first to fourth symbols, the second symbol may include information in which bit information of the first symbol is repeated. For example, the bit information of the first symbol may mean 26-bits information of the U-SIG1 (that is, information composed of bits B0 to B25 of the above-described U-SIG1). For example, the second symbol may include the same 26-bits information of the U-SIG1. For example, the first and second symbols may include the same information bit (that is, 26-bits information of the U-SIG1) and may have different constellation mappings. Among the first to fourth symbols, the fourth symbol may include information in which bit information of the third symbol is repeated. For example, the bit information of the third symbol may mean 26-bits information of the U-SIG2 (that is, information composed of B0 to B25 bits of the above-described U-SIG2). For example, the third and fourth symbols may include the same information bit (that is, 26-bits information of the U-SIG2). Based on S2420ofFIG.24, the receiving STA may determine the transmission mode of the PPDU based on the constellation mapping pattern of the first and second symbols. For example, the constellation mapping pattern for the first mode may have a first mapping pattern, and the constellation mapping pattern for the second mode may have a second mapping pattern. For example, the first mapping pattern may mean a constellation mapping pattern indicated by index 1 in Tables 18 to 23. For example, the second mapping pattern may mean a constellation mapping pattern indicated by index 2 in Tables 18 to 23. Based on S2430ofFIG.24, the receiving STA may decode the PPDU. Through the S2420, the receiving STA can know the transmission mode of the PPDU. Accordingly, the receiving STA decodes the U-SIG and EHT-SIG configured according to the first mode or the second mode, and through this, may decode the payload (that is, data field) of the PPDU. The operation ofFIG.24may be performed by the apparatus ofFIGS.1and/or14. For example, the transmitting STA may be implemented with the apparatus ofFIGS.1and/or14. The processor ofFIGS.1and/or14may perform the above-described operation ofFIG.24. In addition, the transceiver ofFIG.1and/orFIG.14may perform the operation described inFIG.24. FIG.25is a flowchart illustrating an operation performed by a transmitting STA. The transmitting STA may be an AP STA or a user STA. The transmitting STA may configure a PPDU according to the above-described technical features, and may perform an operation of transmitting the configured PPDU to the receiving STA. The technical features related toFIG.24may be equally applied toFIG.25. Based on S2510ofFIG.25, the transmitting STA may configure a PPDU. As described above, the PPDU may be configured based on the first mode (for example, the above-described ER SU mode) or the second mode (for example, the above-described SU DUP mode). The technical features of the PPDU ofFIG.25may be the same as those of the PPDU ofFIG.24. Based on S2520ofFIG.25, the transmitting STA may transmit the PPDU to the receiving STA. The operation ofFIG.25may be performed by the apparatus ofFIGS.1and/or14. For example, the transmitting STA may be implemented with the apparatus ofFIGS.1and/or14. The processor ofFIGS.1and/or14may perform the above-described operation ofFIG.25. In addition, the transceiver ofFIG.1and/orFIG.14may perform the operation described inFIG.25. The apparatus (for example, a transmitting STA and a receiving STA) proposed in the present specification may not necessarily include a transceiver, and may be implemented in the form of a chip including a processor and a memory. Such a device may generate/store a transmit/receive PPDU according to the above-described example. Such a device may be connected to a separately manufactured transceiver to support actual transmission and reception. The present specification proposes a computer readable recording medium implemented in various forms. A computer readable medium according to the present specification may be encoded with at least one computer program including instructions. The instructions stored in the medium may control the processor described inFIGS.1and/or14. That is, the instructions stored in the medium control the processor presented herein to perform the above-described operations of the transmitting and receiving STAs (for example,FIGS.24to25). The foregoing technical features of this specification are applicable to various applications or business models. For example, the foregoing technical features may be applied for wireless communication of a device supporting artificial intelligence (AI). Artificial intelligence refers to a field of study on artificial intelligence or methodologies for creating artificial intelligence, and machine learning refers to a field of study on methodologies for defining and solving various issues in the area of artificial intelligence. Machine learning is also defined as an algorithm for improving the performance of an operation through steady experiences of the operation. An artificial neural network (ANN) is a model used in machine learning and may refer to an overall problem-solving model that includes artificial neurons (nodes) forming a network by combining synapses. The artificial neural network may be defined by a pattern of connection between neurons of different layers, a learning process of updating a model parameter, and an activation function generating an output value. The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses that connect neurons. In the artificial neural network, each neuron may output a function value of an activation function of input signals input through a synapse, weights, and deviations. A model parameter refers to a parameter determined through learning and includes a weight of synapse connection and a deviation of a neuron. A hyper-parameter refers to a parameter to be set before learning in a machine learning algorithm and includes a learning rate, the number of iterations, a mini-batch size, and an initialization function. Learning an artificial neural network may be intended to determine a model parameter for minimizing a loss function. The loss function may be used as an index for determining an optimal model parameter in a process of learning the artificial neural network. Machine learning may be classified into supervised learning, unsupervised learning, and reinforcement learning. Supervised learning refers to a method of training an artificial neural network with a label given for training data, wherein the label may indicate a correct answer (or result value) that the artificial neural network needs to infer when the training data is input to the artificial neural network. Unsupervised learning may refer to a method of training an artificial neural network without a label given for training data. Reinforcement learning may refer to a training method for training an agent defined in an environment to choose an action or a sequence of actions to maximize a cumulative reward in each state. Machine learning implemented with a deep neural network (DNN) including a plurality of hidden layers among artificial neural networks is referred to as deep learning, and deep learning is part of machine learning. Hereinafter, machine learning is construed as including deep learning. The foregoing technical features may be applied to wireless communication of a robot. Robots may refer to machinery that automatically process or operate a given task with own ability thereof. In particular, a robot having a function of recognizing an environment and autonomously making a judgment to perform an operation may be referred to as an intelligent robot. Robots may be classified into industrial, medical, household, military robots and the like according uses or fields. A robot may include an actuator or a driver including a motor to perform various physical operations, such as moving a robot joint. In addition, a movable robot may include a wheel, a brake, a propeller, and the like in a driver to run on the ground or fly in the air through the driver. The foregoing technical features may be applied to a device supporting extended reality. Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphic technology of providing a real-world object and background only in a CG image, AR technology is a computer graphic technology of providing a virtual CG image on a real object image, and MR technology is a computer graphic technology of providing virtual objects mixed and combined with the real world. MR technology is similar to AR technology in that a real object and a virtual object are displayed together. However, a virtual object is used as a supplement to a real object in AR technology, whereas a virtual object and a real object are used as equal statuses in MR technology. XR technology may be applied to a head-mount display (HMD), a head-up display (HUD), a mobile phone, a tablet PC, a laptop computer, a desktop computer, a TV, digital signage, and the like. A device to which XR technology is applied may be referred to as an XR device. | 118,863 |
11943752 | BEST MODE FOR CARRYING OUT THE INVENTION Now, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Embodiment 1 The configuration of base station100according to this embodiment is shown inFIG.1. Base station100divides a plurality of subcarriers comprised of an OFDM symbol that is a multicarrier signal into a plurality of RBs, and uses a Dch and Lch on an RB-by-RB basis in that plurality of RBs. Also, either a Dch or an Lch is allocated to one mobile station in the same subframe. Base station100is equipped with n encoding and modulation sections101-1through101-neach comprising encoding section11and modulation section12for Dch data, n encoding and modulation sections102-1through102-neach comprising encoding section21and modulation section22for Lch data, and n demodulation and decoding sections115-1through115-neach comprising demodulation section31and decoding section32, where n is a number of mobile stations (MSs) with which base station100can communicate. In encoding and modulation sections101-1through101-n, encoding section11performs turbo encoding or suchlike encoding processing on Dch data #1 through #n of mobile stations #1 through #n, and modulation section12performs modulation processing on post-encoding Dch data to generate a Dch data symbol. In encoding and modulation sections102-1through102-n, encoding section21performs turbo encoding or suchlike encoding processing on Lch data #1 through #n of mobile stations #1 through #n, and modulation section22performs modulation processing on post-encoding Lch data to generate an Lch data symbol. The coding rate and modulation scheme used at this time are in accordance with MCS (Modulation and Coding Scheme) information input from adaptive control section116. Allocation section103allocates a Dch data symbol and Lch data symbol to subcarriers comprised of an OFDM symbol in accordance with control from adaptive control section116, and performs output to multiplexing section104. At this time, allocation section103allocates a Dch data symbol and Lch data symbol collectively on an RB-by-RB basis. Also, when using a plurality of Dch's for a Dch data symbol of one mobile station, allocation section103uses Dch's with consecutive channel numbers. That is to say, allocation section103allocates a plurality of different Dch's with consecutive channel numbers to a Dch data symbol of one mobile station. In each RB, Dch and Lch arrangement positions are mutually mapped in advance. That is to say, allocation section103holds in advance an arrangement pattern constituting an association of a Dch, Lch, and RB, and allocates a Dch data symbol and Lch data symbol to each RB in accordance with the arrangement pattern. Dch arrangement methods according to this embodiment will be described in detail later herein. Allocation section103also outputs Dch data symbol allocation information (information indicating which mobile station's Dch data symbol has been allocated to which RB) and Lch data symbol allocation information (information indicating which mobile station's Lch data symbol has been allocated to which RB) to control information generation section105. For example, only the first channel number and last channel number of consecutive channel numbers are included in Dch data symbol allocation information. Control information generation section105generates control information comprising Dch data symbol allocation information, Lch data symbol allocation information, and MCS information input from adaptive control section116, and outputs this control information to encoding section106. Encoding section106performs encoding processing on the control information, and modulation section107performs modulation processing on the post-encoding control information and outputs the control information to multiplexing section104. Multiplexing section104multiplexes control information with data symbols input from allocation section103, and outputs the resulting signals to IFFT (Inverse Fast Fourier Transform) section108. Control information multiplexing is performed on a subframe-by-subframe basis, for example. In this embodiment, either time domain multiplexing or frequency domain multiplexing may be used for control information multiplexing. IFFT section108performs IFFT processing on a plurality of subcarriers comprising a plurality of RBs to which control information and a data symbol are allocated, to generate an OFDM symbol that is a multicarrier signal. CP (Cyclic Prefix) adding section109adds a signal identical to the end part of an OFDM symbol to the start of the OFDM symbol as a CP. Radio transmission section110performs transmission processing such as D/A conversion, amplification, and up-conversion on a post-CP-addition OFDM symbol, and transmits it to each mobile station from antenna111. Meanwhile, radio reception section112receives n OFDM symbols transmitted simultaneously from a maximum of n mobile stations via antenna111, and performs reception processing such as down-conversion and A/D conversion on these OFDM symbols. CP removal section113removes a CP from a post-reception-processing OFDM symbol. FFT (Fast Fourier Transform) section114performs FFT processing on a post-CP-removal OFDM symbol, to obtain per-mobile-station signals multiplexed in the frequency domain. Here, mobile stations transmit signals using mutually different subcarriers or mutually different RBs, and per-mobile-station signals each include per-RB received quality information reported from the respective mobile station. Each mobile station can perform received quality measurement by means of a received SNR, received SIR, received SINR, received CINR, received power, interference power, bit error rate, throughput, an MCS that enables a predetermined error rate to be achieved, or the like. Received quality information may be expressed as a CQI (Channel Quality Indicator), CSI (Channel State Information), or the like. In demodulation and decoding sections115-1through115-n, each demodulation section31performs demodulation processing on a post-FFT signal, and each decoding section32performs decoding processing on a post-demodulation signal. By this means, received data is obtained. Received quality information within the received data is input to adaptive control section116. Adaptive control section116performs adaptive control on transmit data for Lch data based on per-RB received quality information reported from each mobile station. That is to say, based on per-RB received quality information, adaptive control section116performs selection of an MCS capable of satisfying a required error rate for encoding and modulation sections102-1through102-n, and outputs MCS information. Also, adaptive control section116performs frequency scheduling that decides for allocation section103to which RB each of Lch data #1 through #n is allocated using a Max SIR method, Proportional Fairness method, or suchlike scheduling algorithm. Furthermore, adaptive control section116outputs per-RB MCS information to control information generation section105. The configuration of mobile station200according to this embodiment is shown inFIG.2. Mobile station200receives a multicarrier signal that is an OFDM symbol comprising a plurality of subcarriers divided into a plurality of RBs from base station100(FIG.1). In the plurality of RBs, a Dch and Lch are used on an RB-by-RB basis. Also, in the same subframe, either a Dch or Lch is allocated to mobile station200. In mobile station200, radio reception section202receives an OFDM symbol transmitted from base station100via antenna201, and performs reception processing such as up-conversion and A/D conversion on the OFDM symbol. CP removal section203removes a CP from a post-reception-processing OFDM symbol. FFT section204performs FFT processing on a post-CP-removal OFDM symbol, to obtain a received signal in which control information and a data symbol are multiplexed. Demultiplexing section205demultiplexes a post-FFT received signal into a control signal and data symbol. Then demultiplexing section205outputs the control signal to demodulation and decoding section206, and outputs the data symbol to demapping section207. In demodulation and decoding section206, demodulation section41performs demodulation processing on the control signal, and decoding section42performs decoding processing on the post-demodulation signal. Here, control information includes Dch data symbol allocation information, Lch data symbol allocation information, and MCS information. Then demodulation and decoding section206outputs Dch data symbol allocation information and Lch data symbol allocation information within the control information to demapping section207. Based on allocation information input from demodulation and decoding section206, demapping section207extracts a data symbol allocated to that station from a plurality of RBs to which a data symbol input from demultiplexing section205has been allocated. In the same way as base station100(FIG.1), Dch and Lch arrangement positions are mutually mapped in advance for each RB. That is to say, demapping section207holds in advance the same arrangement pattern as allocation section103of base station100, and extracts a Dch data symbol and Lch data symbol from a plurality of RBs in accordance with the arrangement pattern. Also, as described above, when allocation section103of base station100(FIG.1) uses a plurality of Dch's for a Dch data symbol of one mobile station, Dch's with consecutive channel numbers are used. Also, only the first channel number and last channel number of consecutive channel numbers are indicated in allocation information included in control information from base station100. Thus, demapping section207identifies a Dch used in a Dch data symbol allocated to that station based on the first channel number and last channel number indicated in the allocation information. Then demapping section207extracts an RB mapped to the channel number of an identified Dch, and outputs a data symbol allocated to the extracted RB to demodulation and decoding section208. In demodulation and decoding section208, demodulation section51performs demodulation processing on a data symbol input from demapping section207, and decoding section52performs decoding processing on the post-demodulation signal. By this means, received data is obtained. Meanwhile, in encoding and modulation section209, encoding section61performs turbo encoding or suchlike encoding processing on transmission data, and modulation section62performs modulation processing on post-encoding transmission data to generate a data symbol. Here, mobile station200transmits transmission data using different subcarriers or different RBs from other mobile stations, and per-RB received quality information is included in the transmission data. IFFT section210performs IFFT processing on a plurality of subcarriers comprising a plurality of RBs to which a data symbol input from encoding and modulation section209is allocated, to generate an OFDM symbol that is a multicarrier signal. CP adding section211adds a signal identical to the end part of an OFDM symbol to the start of the OFDM symbol as a CP. Radio transmission section212performs transmission processing such as D/A conversion, amplification, and up-conversion on a post-CP-addition OFDM symbol, and transmits it to base station100(FIG.1) from antenna201. Next, Dch channel arrangement methods according to this embodiment will be described. In the following description, a case in which a plurality of subcarriers comprised of one OFDM symbol are divided equally among 12 RBs— RB #1 through #12— will be taken as an example. Also, Lch #1 through #12 and Dch #1 through #12 are formed by respective RBs, and a channel used by each mobile station is controlled by adaptive control section116. The Lch configuration for RBs shown inFIG.3and the Dch configuration for RBs shown below are mutually assigned in advance by allocation section103. Here, frequency scheduling for Lch's is performed in RB units, and therefore an Lch data symbol for one mobile station only is included in each RB used for an Lch. That is to say, one Lch for one mobile station is formed by one RB. Therefore, Lch #1 through #12 are arranged by means of RB #1 through #12 as shown inFIG.3. That is to say, the allocation unit of each Lch is “1 RB×1 subframe.” On the other hand, frequency diversity transmission is performed for Dch's, and therefore a plurality of Dch data symbols are included in an RB used for a Dch. Here, each RB used for a Dch is time-divided into two subblocks, and a different Dch is arranged in each subblock. That is to say, a plurality of different Dch's are time-domain-multiplexed in one RB. Also, one Dch is formed by two different RB subblocks. That is to say, the allocation unit of each Dch is “(1 RB×1/2 subframe)×2,” the same as the allocation unit of each Lch. <Arrangement Method 1 (FIG.4)> With this arrangement method, Dch's with consecutive channel numbers are arranged in one RB. First, a relational expression for a Dch channel number and the RB number of an RB in which that Dch is arranged will be shown. When the number of subblock divisions per RB is Nd, RB number j of an RB in which Dch #(Nd(k−1)+1), Dch #(Nd(k−1)+2), Dch #(Ndk) with consecutive channel numbers are arranged is given by Equation (1) below. [1] j=+floor(Nrb/Nd)·p, p=0,1, . . . ,Nd−1 (Equation 1) where k=1, 2, . . . , floor(Nrb/Nd), operator floor(x) represents the largest integer that does not exceed x, and Nrb is the number of RBs. Here, floor(Nrb/Nd) is the RB interval at which the same Dch is arranged. That is to say, quantity Nd of Dch's comprising Dch #(Nd·(k−1)+1), Dch #(Nd·(k−1)+2), Dch #(Ndk) that are arranged in the same RB and have consecutive channel numbers are distributively arranged in quantity Nd of RBs, RB #(j), separated by a floor(Nrb/Nd) RB interval, in the frequency domain. Here, since Nrb=12 and Nd=2, above Equation (1) gives j=k+6p (p=0, 1), where k=1, 2, . . . , 6. Thus, two Dch's with consecutive channel numbers, Dch #(2k−1) and Dch #(2k), are distributively arranged in two RBs, RB #(k) and RB #(k+6), separated by a 6 (=12/2) RB interval in the frequency domain. Specifically, as shown inFIG.4, Dch #1 and #2 are arranged in RB #1 (RB #7), Dch #3 and #4 are arranged in RB #2 (RB #8), Dch #5 and #6 are arranged in RB #3 (RB #9), Dch #7 and #8 are arranged in RB #4 (RB #10), Dch #9 and #10 are arranged in RB #5 (RB #11), and Dch #11 and #12 are arranged in RB #6 (RB #12). An example of allocation by allocation section103of base station100(FIG.1) when four Dch's, Dch #1 through #4, are used for a Dch data symbol of one mobile station is shown inFIG.5. Here, allocation section103holds the Dch arrangement pattern shown inFIG.4, and allocates a Dch data symbol to RBs in accordance with the arrangement pattern shown inFIG.4. As shown inFIG.5, allocation section103allocates a Dch data symbol to an RB #1 subblock and RB #7 subblock forming Dch #1, an RB #1 subblock and RB #7 subblock forming Dch #2, an RB #2 subblock and RB #8 subblock forming Dch #3, and an RB #2 subblock and RB #8 subblock forming Dch #4. That is to say, as shown inFIG.5, a Dch data symbol is allocated to RB #1, #2, #7, #8. Also, as shown inFIG.5, allocation section103allocates an Lch data symbol to remaining RB #3 through #6 and RB #9 through #12 other than the RBs to which a Dch data symbol has been allocated. That is to say, Lch #3 through #6 and Lch #9 through #12 shown inFIG.3are used for an Lch data symbol. Next, an example of extraction by demapping section207of mobile station200(FIG.2) will be described for a case in which a Dch data symbol using four consecutive Dch's, Dch #1 through #4, is allocated to mobile station200. Here, demapping section207holds the Dch arrangement pattern shown inFIG.4, the same as allocation section103, and extracts a Dch data symbol from a plurality of RBs in accordance with the arrangement pattern shown inFIG.4. First channel number Dch #1 and last channel number Dch #4 are indicated in Dch data symbol allocation information reported to mobile station200from base station100. Since the Dch channel numbers indicated in the Dch data symbol allocation information are Dch #1 and Dch #4, demapping section207identifies the fact that Dch's used for a Dch data symbol addressed to that station are the four consecutive Dch's Dch #1 through #4. Then, following a similar procedure to allocation section103, demapping section207extracts Dch #1 formed by an RB #1 subblock and RB #7 subblock, Dch #2 formed by an RB #1 subblock and RB #7 subblock, Dch #3 formed by an RB #2 subblock and RB #8 subblock, and Dch #4 formed by an RB #2 subblock and RB #8 subblock, as shown inFIG.5. That is to say, demapping section207extracts a Dch data symbol allocated to RB #1, #2, #7, #8, as shown inFIG.5, as a data symbol addressed to that station. Thus, with this arrangement method, Dch's with consecutive channel numbers are arranged in one RB, and therefore when one mobile station uses a plurality of Dch's, all the subblocks of one RB are used, and then subblocks of another RB are used. By this means, it is possible to minimize the allocation of a data symbol to some subblocks among a plurality of subblocks forming one RB while other subblocks are not used. Therefore, according to this arrangement method, a fall in the resource utilization efficiency of a channel for performing frequency diversity transmission can be prevented when simultaneously performing frequency scheduling transmission in an Lch and frequency diversity transmission in a Dch. Also, according to this arrangement method, a fall in the utilization efficiency of an RB communication resource used for a Dch can be prevented, increasing the number of RBs that can be used for Lch's, and enabling frequency scheduling to be performed for more frequency bands. Also, according to this arrangement method, when one mobile station uses a plurality of Dch's, a plurality of Dch's with consecutive channel numbers are arranged in RBs that are consecutive in the frequency domain. Consequently, RBs that can be used for Lch's—that is, remaining RBs other than RBs used by a Dch—are also consecutive in terms of frequency. For example, when frequency selectivity of a channel is moderate or when the bandwidth of each RB is narrow, RB bandwidth becomes narrow with respect to a frequency selective fading correlation bandwidth. At this time, RBs with good channel quality are consecutive in a frequency band with high channel quality. Therefore, when RB bandwidth becomes narrow with respect to a frequency selective fading correlation bandwidth, use of this arrangement method enables RBs that are consecutive in the frequency domain to be used for Lch's, enabling a frequency scheduling effect to be further improved. Furthermore, according to this arrangement method, a plurality of Lch's with consecutive channel numbers can be allocated. Consequently, when a base station allocates a plurality of Lch's to one mobile station, it is sufficient for only the first channel number and last channel number of consecutive channel numbers to be reported to a mobile station from the base station. Therefore, control information for reporting an Lch allocation result can be reduced in the same way as when a Dch allocation result is reported. With this arrangement method, a case has been described in which one RB is divided into two when using Dch's, but the number of divisions of one RB is not limited to two, and one RB may also be divided into three or more divisions. For example, an allocation method for a case in which one RB is divided into three when using Dch's is shown inFIG.6. As shown inFIG.6, three consecutive Dch's are arranged in one RB, enabling the same kind of effect to be obtained as with this arrangement method. Also, since one Dch is formed by distribution among three RBs as shown inFIG.6, a diversity effect can be improved to a greater extent than in the case of division into two. <Arrangement Method 2 (FIG.8)> With this arrangement method, the fact that a plurality of different Dch's with consecutive channel numbers are arranged in one RB is the same as in Arrangement Method 1, but a difference from Arrangement Method 1 is that a lowest-numbered or highest-numbered Dch and a Dch with a consecutive channel number among the plurality of Dch's are arranged in the above-described one RB and RBs distributively arranged in the frequency domain. With this arrangement method, as with Arrangement Method 1 (FIG.4), Dch's with consecutive channel numbers are arranged in the same RB. That is to say, of Dch #1 through #12 shown inFIG.8, (Dch #1, #2), (Dch #3, #4), (Dch #5, #6), (Dch #7, #8), (Dch #9, #10), and (Dch #11, #12) are Dch combinations each formed by the same RB. Of the above plurality of combinations, combinations in which a lowest-numbered or highest-numbered Dch included in one combination and a Dch with a consecutive channel number are included are arranged in RBs distributed in the frequency domain. That is to say, (Dch #1, #2) and (Dch #3, #4) in which Dch #2 and Dch #3 with consecutive channel numbers are respectively included are arranged in different distributed RBs, (Dch #3, #4) and (Dch #5, #6) in which Dch #4 and Dch #5 with consecutive channel numbers are respectively included are arranged in different distributed RBs, (Dch #5, #6) and (Dch #7, #8) in which Dch #6 and Dch #7 with consecutive channel numbers are respectively included are arranged in different distributed RBs, (Dch #7, #8) and (Dch #9, #10) in which Dch #8 and Dch #9 with consecutive channel numbers are respectively included are arranged in different distributed RBs, and (Dch #9, #10) and (Dch #11, #12) in which Dch #10 and Dch #11 with consecutive channel numbers are respectively included are arranged in different distributed RB s. Here, as with Arrangement Method 1, a relational expression for a Dch channel number and the RB number of an RB in which that Dch is arranged will be shown. RB number j of an RB in which Dch #(Nd·(k−1)+1), Dch #(Nd·(k−1)+2), Dch #(Ndk) with consecutive channel numbers included in combination k are arranged is given by Equation (2) below. [2] j=q(k)+floor(Nrb/Nd)p, p=0,1, . . . ,Nd−1 (Equation 2) where q(k) is given by a 2-row×(floor(Nrb/Nd)/2)-column block interleaver. The number of rows of the block interleaver has been assumed to be 2, but may be any positive integer less than or equal to floor(Nrb/Nd). By this means, combination k and a combination in which a lowest-numbered or highest-numbered Dch included in combination k and a Dch with a consecutive channel number (combination k−1 or combination k+1) are arranged in distributed RBs with different RB numbers. Here, since Nrb=12 and Nd=2, above Equation (2) gives j=q(k)+6p (p=0, 1), where q(k) is given by a 2-row×3-column block interleaver as shown inFIG.7. That is to say, as shown inFIG.7, q(k)=1, 4, 2, 5, 3, 6 is obtained for k=1, 2, 3, 4, 5, 6. Thus, two Dch's with consecutive channel numbers, Dch #(2k−1) and Dch #(2k), are distributively arranged in two RBs, RB #(q(k)) and RB #(q(k)+6), separated by a 6 (=12/2) RB interval in the frequency domain. Specifically, for example, as shown inFIG.8, Dch #1 and #2 are arranged in RB #1 (RB #7), Dch #5 and #6 are arranged in RB #2 (RB #8), Dch #9 and #10 are arranged in RB #3 (RB #9), Dch #3 and #4 are arranged in RB #4 (RB #10), Dch #7 and #8 are arranged in RB #5 (RB #11), and Dch #11 and #12 are arranged in RB #6 (RB #12). As with Arrangement Method 1, an example of allocation by allocation section103of base station100(FIG.1) when four consecutive Dch's, Dch #1 through #4, are used for a Dch data symbol of one mobile station is shown inFIG.9. Here, allocation section103holds the Dch arrangement pattern shown inFIG.8, and allocates a Dch data symbol to RBs in accordance with the arrangement pattern shown inFIG.8. As shown inFIG.9, allocation section103allocates a Dch data symbol to an RB #1 subblock and RB #7 subblock forming Dch #1, an RB #1 subblock and RB #7 subblock forming Dch #2, an RB #4 subblock and RB #10 subblock forming Dch #3, and an RB #4 subblock and RB #10 subblock forming Dch #4. That is to say, as shown inFIG.9, a Dch data symbol is allocated to RB #1, #4, #7, #10. Also, as shown inFIG.9, allocation section103allocates an Lch data symbol to remaining RB #2, #3, #5, #6, #8, #9, #11, #12 other than the RBs to which a Dch data symbol has been allocated. That is to say, Lch #2, #3, #5, #6, #8, #9, #11, #12 shown inFIG.3are used for an Lch data symbol. Next, as with Arrangement Method 1, an example of extraction by demapping section207of mobile station200(FIG.2) will be described for a case in which a Dch data symbol using four consecutive Dch's, Dch #1 through #4, is allocated to mobile station200. Here, demapping section207holds the Dch arrangement pattern shown inFIG.8, the same as allocation section103, and extracts a Dch data symbol from a plurality of RBs in accordance with the arrangement pattern shown inFIG.8. As with Arrangement Method 1, first channel number Dch #1 and last channel number Dch #4 are indicated in Dch data symbol allocation information reported to mobile station200from base station100. Since the Dch channel numbers indicated in the Dch data symbol allocation information are Dch #1 and Dch #4, demapping section207identifies the fact that Dch's used for a Dch data symbol addressed to that station are the four consecutive Dch's Dch #1 through #4. Then, following a similar procedure to allocation section103, demapping section207extracts Dch #1 formed by an RB #1 subblock and RB #7 subblock, Dch #2 formed by an RB #1 subblock and RB #7 subblock, Dch #3 formed by an RB #4 subblock and RB #10 subblock, and Dch #4 formed by an RB #4 subblock and RB #10 subblock, as shown inFIG.9. That is to say, demapping section207extracts a Dch data symbol allocated to RB #1, #4, #7, #10, as shown inFIG.9, as a data symbol addressed to that station. With this arrangement method, as with Arrangement Method 1, a Dch data symbol is allocated to four RBs, and an Lch data symbol is allocated to eight RBs. However, with this arrangement method, a Dch data symbol is distributively allocated every three RBs, to RB #1, RB #4, RB #7, and RB #10, as shown inFIG.9, enabling a frequency diversity effect to be improved to a greater extent than with Arrangement Method 1 (FIG.5). Also, as shown inFIG.9, having a Dch data symbol allocated to distributed RBs also means that an Lch data symbol is distributed, making it possible to perform frequency scheduling using RBs across a wider band. Thus, with this arrangement method, a lowest-numbered or highest-numbered Dch and a Dch with a consecutive channel number among a plurality of different Dch's are arranged in one RB in which the plurality of different Dch's with consecutive channel numbers are arranged and RBs distributed in the frequency domain. Consequently, even if a plurality of Dch's are used for a data symbol of one mobile station, it is possible to prevent non-use of some RB subblocks, and allocate a data symbol distributed across a wide band. Therefore, according to this arrangement method, the same kind of effect can be obtained as with Arrangement Method 1, and furthermore, a frequency diversity effect can be improved. Also, with this arrangement method, RBs used for Dch's are distributed, enabling remaining RBs other than RBs used for Dch's—that is, RBs used for Lch's to be distributed as well. As a result, according to this arrangement method a frequency scheduling effect can be improved. With this arrangement method, a case has been described in which one RB is divided into two when using Dch's, but the number of divisions of one RB is not limited to two, and one RB may also be divided into three or more divisions. For example, an allocation method for a case in which one RB is divided into three when using Dch's is shown inFIG.10. As shown inFIG.10, different RBs including consecutive Dch's are distributed in the frequency domain, enabling the same kind of effect to be obtained as with this arrangement method. Also, since one Dch is formed by distribution among three RBs as shown inFIG.10, a diversity effect can be improved to a greater extent than in the case of division into two. <Arrangement Method 3 (FIG.11)> With this arrangement method, Dch's with consecutive channel numbers are arranged in different RBs, and Dch's with channel numbers within a predetermined number are arranged in one RB. This is described in concrete terms below. Here, the predetermined number is assumed to be 2. That is to say, the difference in channel numbers of mutually different Dch's included in the same RB does not exceed 2. First, a relational expression for a Dch channel number and the RB number of an RB in which that Dch is arranged will be shown. RB number j of an RB in which mutually different Dch's included in combination k are arranged is given by Equation (2), in the same way as with Arrangement Method 2. However, whereas with Arrangement Method 2 Dch channel numbers included in combination k are consecutive, with this arrangement method Dch channel numbers included in combination k are separated by a predetermined number. Also, combination number k is assigned a smaller value for a combination of Dch's with smaller channel numbers. Here, since Nrb=12 and Nd=2, j=q(k)+6p (p=0, 1) in the same way as with Arrangement Method 2, where q(k) is given by the 2-row×3-column block interleaver shown inFIG.7, also as with Arrangement Method 2. Thus, Dch's included in combination k are distributively arranged in two RBs, RB #(q(k)) and RB #(q(k)+6), separated by a 6 (=12/2) RB interval in the frequency domain. However, since the predetermined number is 2, combination 1 (k=1) becomes (Dch #1, #3) and combination 2 (k=2) becomes (Dch #2, #4). The above explanation can be applied to combinations 3 through 6. Therefore, as shown inFIG.11, Dch #1 and #3 are arranged in RB #1 (RB #7), Dch #5 and #7 are arranged in RB #2 (RB #8), Dch #9 and #11 are arranged in RB #3 (RB #9), Dch #2 and #4 are arranged in RB #4 (RB #10), Dch #6 and #8 are arranged in RB #5 (RB #11), and Dch #10 and #12 are arranged in RB #6 (RB #12). An example of allocation by allocation section103of base station100(FIG.1) when two consecutive Dch's, Dch #1 and #2, are used for a Dch data symbol of one mobile station—that is, when the number of Dch's used for a Dch data symbol of one mobile station is small—is shown inFIG.12. Here, allocation section103holds the Dch arrangement pattern shown inFIG.11, and allocates a Dch data symbol to RBs in accordance with the arrangement pattern shown inFIG.11. As shown inFIG.12, allocation section103allocates a Dch data symbol to an RB #1 subblock and RB #7 subblock forming Dch #1, and an RB #4 subblock and RB #10 subblock forming Dch #2. That is to say, as shown inFIG.12, a Dch data symbol is allocated to RB #1, #4, #7, #10 distributed in the frequency domain. Next, an example of extraction by demapping section207of mobile station200(FIG.2) will be described for a case in which a Dch data symbol using two consecutive Dch's, Dch #1 and #2, is allocated to mobile station200. Here, demapping section207holds the Dch arrangement pattern shown inFIG.11, the same as allocation section103, and extracts a Dch data symbol from a plurality of RBs in accordance with the arrangement pattern shown inFIG.11. First channel number Dch #1 and last channel number Dch #2 are indicated in Dch data symbol allocation information reported to mobile station200from base station100. Since the Dch channel numbers indicated in the Dch data symbol allocation information are Dch #1 and Dch #2, demapping section207identifies the fact that Dch's used for a Dch data symbol addressed to that station are the two consecutive Dch's Dch #1 and #2. Then, following a similar procedure to allocation section103, demapping section207extracts Dch #1 formed by an RB #1 subblock and RB #7 subblock, and Dch #2 formed by an RB #4 subblock and RB #10 subblock, as shown inFIG.12. That is to say, demapping section207extracts a Dch data symbol allocated to RB #1, #4, #7, #10 distributed in the frequency domain, as shown inFIG.12, as a data symbol addressed to that station. Thus, when the number of Dch's used for a Dch data symbol of one mobile station is small that is, when there are few allocated RBs—the effect of a fall in communication resource utilization efficiency for the entire band is small. Therefore, a frequency diversity effect can be obtained preferentially even though there is a possibility of subblocks other than subblocks allocated within RBs not being used. On the other hand, an example of allocation by allocation section103of base station100(FIG.1) when four consecutive Dch's, Dch #1 through #4, are used for a Dch data symbol of one mobile station—that is, when the number of Dch's used for a Dch data symbol of one mobile station is large—is shown inFIG.13. Here, allocation section103holds the Dch arrangement pattern shown inFIG.11, and allocates a Dch data symbol to RBs in accordance with the arrangement pattern shown inFIG.11. As shown inFIG.13, allocation section103allocates a Dch data symbol to an RB #1 subblock and RB #7 subblock forming Dch #1, an RB #4 subblock and RB #10 subblock forming Dch #2, an RB #1 subblock and RB #7 subblock forming Dch #3, and an RB #4 subblock and RB #10 subblock forming Dch #4. That is to say, as shown inFIG.13, a Dch data symbol is allocated to RB #1, #4, #7, #10, distributed in the frequency domain, in the same way as inFIG.12. Also, inFIG.13, a Dch data symbol is allocated to all the subblocks of RB #1, #4, #7, #10. Next, an example of extraction by demapping section207of mobile station200(FIG.2) will be described for a case in which a Dch data symbol using four consecutive Dch's, Dch #1 through #4, is allocated to mobile station200. Here, demapping section207holds the Dch arrangement pattern shown inFIG.11, the same as allocation section103, and extracts a Dch data symbol from a plurality of RBs in accordance with the arrangement pattern shown inFIG.11. First channel number Dch #1 and last channel number Dch #4 are indicated in Dch data symbol allocation information reported to mobile station200from base station100. Since the Dch channel numbers indicated in the Dch data symbol allocation information are Dch #1 and Dch #4, demapping section207identifies the fact that Dch's used for a Dch data symbol addressed to that station are the four consecutive Dch's Dch #1 through #4. Then, following a similar procedure to allocation section103, demapping section207extracts Dch #1 formed by an RB #1 subblock and RB #7 subblock, Dch #2 formed by an RB #4 subblock and RB #10 subblock, Dch #3 formed by an RB #1 subblock and RB #7 subblock, and Dch #4 formed by an RB #4 subblock and RB #10 subblock, as shown inFIG.13. That is to say, demapping section207extracts a Dch data symbol allocated to all the subblocks of RB #1, #4, #7, #10, as shown inFIG.13, as a data symbol addressed to that station. Thus, even when the number of Dch's used for a Dch data symbol of one mobile station is large—that is, when there are many allocated RBs— all subblocks within RBs can be used while obtaining a frequency diversity effect. Thus, with this arrangement method, Dch's with consecutive channel numbers are arranged in different RBs, and Dch's with channel numbers within a predetermined number are arranged in one RB. By this means, a frequency diversity effect can be improved when the number of Dch's used for a Dch data symbol of one mobile station is small. Also, even when the number of Dch's used for a Dch data symbol of one mobile station is large, a frequency diversity effect can be improved without lowering communication resource utilization efficiency. With this arrangement method, a case has been described in which one RB is divided into two when using Dch's, but the number of divisions of one RB is not limited to two, and one RB may also be divided into three or more divisions. For example, an allocation method for a case in which one RB is divided into three when using Dch's is shown inFIG.14. As shown inFIG.14, Dch's with consecutive channel numbers are arranged in different RBs, and Dch's with channel numbers within a predetermined number of 2 are arranged in one RB, enabling the same kind of effect to be obtained as with this arrangement method. Also, since one Dch is formed by distribution among three RBs as shown inFIG.14, a diversity effect can be improved to a greater extent than in the case of division into two. <Arrangement Method 4 (FIG.15)> With this arrangement method, the fact that a plurality of different Dch's with consecutive channel numbers are arranged in one RB is the same as in Arrangement Method 1, but a difference from Arrangement Method 1 is that RBs in which the same Dch is arranged are allocated in order from both ends of a band. With this arrangement method, as with Arrangement Method 1 (FIG.4), Dch's with consecutive channel numbers are arranged in the same RB. That is to say, of Dch #1 through #12 shown inFIG.15, (Dch #1, #2), (Dch #3, #4), (Dch #5, #6), (Dch #7, #8), (Dch #9, #10), and (Dch #11, #12) are Dch combinations each formed by the same RB. Two RBs in which Dch's of the above combinations are arranged are allocated in order from both ends of a band. That is to say, as shown inFIG.15, combination (Dch #1, #2) is arranged in RB #1 and RB #12, and combination (Dch #3, #4) is arranged in RB #2 and RB #11. Similarly, (Dch #5, #6) is arranged in RB #3 and RB #10, (Dch #7, #8) is arranged in RB #4 and RB #9, (Dch #9, #10) is arranged in RB #5 and RB #8, and (Dch #11, #12) is arranged in RB #6 and RB #7. As with Arrangement Method 1, an example of allocation by allocation section103of base station100(FIG.1) when four consecutive Dch's, Dch #1 through #4, are used for a Dch data symbol of one mobile station is shown inFIG.16. Here, allocation section103holds the Dch arrangement pattern shown inFIG.15, and allocates a Dch data symbol to RBs in accordance with the arrangement pattern shown inFIG.15. As shown inFIG.16, allocation section103allocates a Dch data symbol to an RB #1 subblock and RB #12 subblock forming Dch #1, an RB #1 subblock and RB #12 subblock forming Dch #2, an RB #2 subblock and RB #11 subblock forming Dch #3, and an RB #2 subblock and RB #11 subblock forming Dch #4. That is to say, as shown inFIG.16, a Dch data symbol is allocated to RB #1, #2, #11, #12. Also, as shown inFIG.16, allocation section103allocates an Lch data symbol to remaining RB #3, #4, #5, #6, #7, #8, #9, #10 other than the RBs to which a Dch data symbol has been allocated. That is to say, Lch #3, #4, #5, #6, #7, #8, #9, #10 shown inFIG.3are used for an Lch data symbol. Next, as with Arrangement Method 1, an example of extraction by demapping section207of mobile station200(FIG.2) will be described for a case in which a Dch data symbol using four consecutive Dch's, Dch #1 through #4, is allocated to mobile station200. Here, demapping section207holds the Dch arrangement pattern shown inFIG.15, the same as allocation section103, and extracts a Dch data symbol from a plurality of RBs in accordance with the arrangement pattern shown inFIG.15. As with Arrangement Method 1, first channel number Dch #1 and last channel number Dch #4 are indicated in Dch data symbol allocation information reported to mobile station200from base station100. Since the Dch channel numbers indicated in the Dch data symbol allocation information are Dch #1 and Dch #4, demapping section207identifies the fact that Dch's used for a Dch data symbol addressed to that station are the four consecutive Dch's Dch #1 through #4. Then, following a similar procedure to allocation section103, demapping section207extracts Dch #1 formed by an RB #1 subblock and RB #12 subblock, Dch #2 formed by an RB #1 subblock and RB #12 subblock, Dch #3 formed by an RB #2 subblock and RB #11 subblock, and Dch #4 formed by an RB #2 subblock and RB #11 subblock, as shown inFIG.16. That is to say, demapping section207extracts a Dch data symbol allocated to RB #1, #2, #11, #12 as shown inFIG.16, as a data symbol addressed to that station. With this arrangement method, as with Arrangement Method 1 and Arrangement Method 2, a Dch data symbol is allocated to four RBs, and an Lch data symbol is allocated to eight RBs. However, with this arrangement method, a Dch data symbol is allocated to RBs at both ends of a band, as shown inFIG.16. Since the RB interval at which a Dch data symbol is allocated is wider than in the case of Arrangement Method 1 (FIG.5) or Arrangement Method 2 (FIG.9), a frequency diversity effect can be improved. Also, as shown inFIG.16, having a Dch data symbol allocated to RBs at both ends of a band also means that an Lch data symbol is distributed, making it possible to perform frequency scheduling using RBs across a wider band. Also, according to this arrangement method, RBs that can be used for Lch's—that is, remaining RBs other than RBs used by a Dch—are all consecutive in terms of frequency. For example, when frequency selectivity of a channel is moderate or when the bandwidth of each RB is narrow, RB bandwidth becomes narrow with respect to a frequency selective fading correlation bandwidth. At this time, RBs with good channel quality are consecutive in a frequency band with high channel quality. Therefore, when RB bandwidth becomes narrow with respect to a frequency selective fading correlation bandwidth, use of this arrangement method enables RBs that are consecutive in the frequency domain to be used for Lch's, enabling a frequency scheduling effect to be further improved. Furthermore, according to this arrangement method, a plurality of Lch's with consecutive channel numbers can be allocated. Consequently, when a base station allocates a plurality of Lch's to one mobile station, it is sufficient for only the first channel number and last channel number of consecutive channel numbers to be reported to a mobile station from the base station. With this arrangement method, all RBs that can be used for Lch's are consecutive in the frequency domain, and consequently even when all Lch's are allocated to one mobile station, enabling above reporting method to be used. Therefore, control information for reporting an Lch allocation result can be reduced in the same way as when a Dch allocation result is reported. With this arrangement method, a case has been described in which one RB is divided into two when using Dch's, but the number of divisions of one RB is not limited to two, and one RB may also be divided into three or more divisions. For example, allocation methods for cases in which one RB is divided into three and into four when using Dch's are shown inFIG.17andFIG.18respectively. As shown inFIG.17andFIG.18, different RBs including consecutive Dch's are arranged preferentially from both ends of a band, enabling the same kind of effect to be obtained as with this arrangement method. Also, since one Dch is formed by distribution among three RBs or four RBs as shown inFIG.17andFIG.18respectively, a diversity effect can be improved to a greater extent than in the case of division into two. This concludes a description of Arrangement Methods 1 through 4 according to this embodiment. Thus, according to this embodiment, a fall in the communication resource utilization efficiency of a channel for performing frequency diversity transmission can be prevented when simultaneously performing frequency scheduling transmission in an Lch and frequency diversity transmission in a Dch. Also, according to this embodiment, a fall in the utilization efficiency of an RB used for a Dch can be prevented, increasing the number of RBs that can be used for Lch's, and enabling frequency scheduling to be performed for more frequency bands. Embodiment 2 In this embodiment a case will be described in which switching between use of Arrangement Method 1 and Arrangement Method 2 of Embodiment 1 is performed according to the communication environment. As described above, Arrangement Method 1 enables more RBs consecutive in the frequency domain that can be used for Lch's to be secured than Arrangement Method 2, while Arrangement Method 2 has a greater frequency diversity effect than Arrangement Method 1. Specifically, when four consecutive Dch's, Dch #1 through #4, are used for a Dch data symbol of one mobile station, with Arrangement Method 1 (FIG.5) four RBs consecutive in the frequency domain, RB #3 through #6 and RB #9 through #12, can be used for an Lch, while a Dch data symbol is allocated to two RBs consecutive in the frequency domain, RB #1, #2 and RB #7, #8. On the other hand, with Arrangement Method 2 (FIG.9) only two RBs consecutive in the frequency domain, RB #2, #3, RB #5, #6, RB #8, #9, and RB #11, #12, can be used for an Lch, while a Dch data symbol is distributively allocated every three RBs, to RB #1, #4, #7, #10. Thus, with Arrangement Method 1 and Arrangement Method 2, there is a trade-off between a frequency diversity effect and the number of RBs consecutive in the frequency domain that can be used for Lch's. Allocation section103according to this embodiment (FIG.1) switches between Arrangement Method 1 and Arrangement Method 2 of Embodiment 1 according to the communication environment, and allocates a Dch data symbol and Lch data symbol to an RB respectively. Next, Switching Methods 1 through 3 used by allocation section103of this embodiment will be described. <Switching Method 1> With this switching method, the arrangement method is switched according to the number of subblock divisions per RB. In the following description, the number of subblock divisions per RB is indicated by Nd. The larger the value of Nd, the larger is the number of different RBs in which the same Dch is arranged. For example, with Arrangement Method 1, when Nd=2 the same Dch is distributively arranged in two different RBs as shown inFIG.4, whereas when Nd=4 the same Dch is distributively arranged in four different RBs as shown inFIG.19. Thus, the larger the value of Nd, the larger is the number of different RBs in which the same Dch is distributively arranged, and therefore the greater is the frequency diversity effect. In other words, the smaller the value of Nd, the smaller is the frequency diversity effect. At the same time, the smaller the value of Nd, the larger is the frequency interval between different RBs in which the same Dch is arranged. For example, with Arrangement Method 1, when Nd=2 the frequency interval of subblocks forming the same Dch is six RBs as shown inFIG.4, whereas when Nd=4 the frequency interval of subblocks forming the same Dch is three RBs. Thus, the smaller the value of Nd, the larger is the frequency interval of subblocks forming the same Dch, and correspondingly more RBs consecutive in terms of frequency can be secured for Lch's. In other words, the larger the value of Nd, the smaller is the number of RBs consecutive in the frequency domain that can be used for Lch's. Thus, allocation section103allocates Dch's using Arrangement Method 1 when the value of Nd is large—that is, when the number of RBs consecutive in the frequency domain that can be used for Lch's is small—and allocates Dch's using Arrangement Method 2 when the value of Nd is small—that is, when the frequency diversity effect is small. Specifically, allocation section103performs arrangement method switching based on a comparison between Nd and a preset threshold value. That is to say, allocation section103switches to Arrangement Method 1 when Nd is greater than or equal to the threshold value, and switches to Arrangement Method 2 when Nd is less than the threshold value. As in Embodiment 1, an example of allocation when four consecutive Dch's, Dch #1 through #4, are used for a Dch data symbol of one mobile station is shown inFIG.20. Here, a case in which Nd=4 (when the number of divisions is large), and a case in which Nd=2 (when the number of divisions is small), will be described when the preset threshold value is 3. When Nd=2, the situation is the same as with Arrangement Method 2 of Embodiment 1 (FIG.9), and therefore a description thereof is omitted here. When Nd=4, as shown inFIG.20, allocation section103allocates a Dch data symbol to an RB #1 subblock, RB #4 subblock, RB #7 subblock, and RB #10 subblock forming Dch #1, an RB #1 subblock, RB #4 subblock, RB #7 subblock, and RB #10 subblock forming Dch #2, an RB #1 subblock, RB #4 subblock, RB #7 subblock, and RB #10 subblock forming Dch #3, and an RB #1 subblock, RB #4 subblock, RB #7 subblock, and RB #10 subblock forming Dch #4, in accordance with Arrangement Method 1 (FIG.19). That is to say, as shown inFIG.20, a Dch data symbol is allocated to RB #1, #4, #7, #10. Also, as shown inFIG.20, allocation section103allocates an Lch data symbol to remaining RB #2, #3, #5, #6, #8, #9, #11, #12 other than the RBs to which a Dch data symbol has been allocated. That is to say, Lch #2, #3, #5, #6, #8, #9, #11, #12 shown inFIG.3are used for an Lch data symbol. Thus, with this switching method, both when Nd=4 (FIG.20) and when Nd=2 (FIG.9), a Dch data symbol is allocated to RB #1, RB #4, RB #7, and RB #10, and an Lch data symbol is allocated to RB #2, #3, #5, #6, #8, #9, #11, #12. That is to say, when the value of Nd is large (when the number of RBs consecutive in the frequency domain that can be used for Lch's is small), using Arrangement Method 1 enables the number of RBs consecutive in the frequency domain that can be used for Lch's to be maximized while obtaining a frequency diversity effect. On the other hand, when the value of Nd is small (when the frequency diversity effect is small), using Arrangement Method 2 enables the frequency diversity effect to be improved while securing RBs consecutive in the frequency domain that can be used for Lch's. Thus, according to this switching method, when the number of subblock divisions per RB is large, switching is performed to an arrangement method whereby RBs consecutive in the frequency domain that can be used for Lch's are obtained preferentially, whereas when the number of subblock divisions per RB is small, switching is performed to an arrangement method whereby a frequency diversity effect is obtained preferentially. By this means, in both cases regarding the number of subblock divisions per RB, a frequency diversity effect and a frequency scheduling effect can both be improved. Also, according to this switching method, Lch's used in frequency scheduling transmission are secured in RBs that are consecutive in the frequency domain, enabling control information for reporting an Lch allocation result to be reduced. Also, according to this switching method, the larger the number of mobile stations or the number of Dch's, the larger is the value of Nd that may be used. Consequently, when the number of mobile stations or the number of a plurality of mutually different Dch's is larger, the same Dch is allocated to a larger number of different RBs, enabling a frequency diversity effect for one Dch to be further improved. On the other hand, when the number of mobile stations or the number of a plurality of mutually different Dch's is smaller, the number of a plurality of mutually different Dch's per RB decreases, enabling the occurrence of vacancies occurring in some per-RB subblocks to be prevented, and enabling a fall in communication resource utilization efficiency to be prevented. For example, when Nd=4, vacancies occur in some subblocks of one RB when the number of a plurality of mutually different Dch's is less than four. However, making the value of Nd less than 4 results in a higher possibility of all of a plurality of subblocks included in one RB being used, enabling a fall in communication resource utilization efficiency to be prevented. <Switching Method 2> With this switching method, the arrangement method is switched according to a channel state, such as channel frequency selectivity, for example. When frequency selectivity is moderate, RBs with high channel quality tend to be consecutive in the frequency domain, making this situation suitable for frequency scheduling transmission. On the other hand, when frequency selectivity is significant, RBs with high channel quality tend to be distributed in the frequency domain, making this situation suitable for frequency diversity transmission. Thus, allocation section103allocates Dch's using Arrangement Method 1 when frequency selectivity is moderate, and allocates Dch's using Arrangement Method 2 when frequency selectivity is significant. When frequency selectivity is moderate (when RBs with high channel quality are consecutive in the frequency domain), using Arrangement Method 1 enables RBs consecutive in the frequency domain to be used for Lch's, enabling a frequency scheduling effect to be improved. Also, since Lch's are secured in RBs that are consecutive in the frequency domain, control information for reporting an Lch allocation result can be reduced. On the other hand, when frequency selectivity is significant (when RBs with high channel quality are distributed in the frequency domain), using Arrangement Method 2 results in Lch's being distributively allocated in the frequency domain, enabling frequency scheduling to be performed using RBs with high channel quality that are distributed across a wide band. Thus, according to this switching method, arrangement method switching is performed according to frequency selectivity, and therefore whatever the frequency selectivity situation, a frequency scheduling effect for Lch's can be improved while obtaining a frequency diversity effect for Dch's. Frequency selectivity used in this switching method can be measured by means of channel delay dispersion (delayed wave spread), for example. Also, since frequency selectivity differs according to cell size and cell conditions, this switching method may be applied on a cell-by-cell basis, and the arrangement method may be switched on a cell-by-cell basis. Furthermore, since frequency selectivity also differs for each mobile station, this switching method may be applied on an individual mobile station basis. <Switching Method 3> With this switching method, the arrangement method is switched according to system bandwidth—that is, a bandwidth in which RBs are allocated. The narrower the system bandwidth, the smaller is the frequency interval between RBs used for Dch's. Consequently, a frequency diversity effect is not improved however many Dch's are distributively arranged in the frequency domain. On the other hand, the wider the system bandwidth, the larger is the frequency interval between RBs used for Dch's. Consequently, when a plurality of Dch's are distributively arranged in the frequency domain, a large number of RBs consecutive in the frequency domain, proportional to the frequency interval between RBs used for Dch's, can be secured for Lch's, enabling a frequency scheduling effect to be obtained. Thus, allocation section103allocates Dch's using Arrangement Method 1 when system bandwidth is narrow, and allocates Dch's using Arrangement Method 2 when system bandwidth is wide. In this way, when system bandwidth is narrow, using Arrangement Method 1 enables RBs consecutive in the frequency domain that can be used for Lch's to be secured preferentially, rather than obtaining a frequency diversity effect. On the other hand, when system bandwidth is wide, using Arrangement Method 2 enables a frequency diversity effect to be improved without impairing a frequency scheduling effect. Thus, according to this switching method, the arrangement method is switched according to system bandwidth, and therefore an optimal frequency scheduling effect can always be obtained whatever the system bandwidth. Also, since Lch's are secured in RBs that are consecutive in the frequency domain, control information for reporting an Lch allocation result can be reduced. This concludes a description of Switching Methods 1 through 3 used by allocation section103of this embodiment. Thus, according to this embodiment, switching between Dch arrangement methods is performed according to the communication environment, enabling Lch frequency scheduling transmission and Dch frequency diversity transmission to be performed optimally at all times according to the communication environment. In this embodiment, cases have been described in which arrangement method switching is performed by allocation section103(FIG.1), but arrangement method switching need not be performed by allocation section103. For example, an arrangement method switching section (not shown) may perform arrangement method switching according to the communication environment, and issue an arrangement method directive to allocation section103. Also, in this embodiment, cases have been described in which allocation section103(FIG.1) switches between Arrangement Method 1 and Arrangement Method 2, but allocation section103can obtain the same kind of effect as described above, and the effect explained in the description of Arrangement Method 3 of Embodiment 1, by using Arrangement Method 3 of Embodiment 1 instead of Arrangement Method 2. Allocation section103may also switch among Arrangement Methods 1 through 3 according to the communication environment. Furthermore, in this embodiment, when performing arrangement method switching, relational expressions Equation (1) and Equation (2) showing a relationship between a Dch channel number and the RB number of an RB in which that Dch is arranged, or a relational expression variable such as q(k), may be switched. Also, in this embodiment, these relational expression variables may be reported to a mobile station. By this means, a mobile station can switch to an appropriate arrangement method each time arrangement method switching is performed, and can thus determine a Dch allocated to it. Embodiment 3 In this embodiment a case will be described in which only one Dch is arranged in one RB (the number of subblock divisions per RB is one). First, a relational expression for a Dch channel number and the RB number of an RB in which that Dch is arranged will be shown. RB number j of an RB in which a Dch with channel number k is arranged is given by Equation (3) below. (Equation 3) j=q(k) [3] where k=1, 2, . . . , Nrb, and q(k) is given by an M-row×(Nrb/M)-column block interleaver where M is an arbitrary positive integer. If it is assumed here that Nrb=12 and M=4, q(k) is given by the 4-row×3-column block interleaver shown inFIG.21. That is to say, as shown inFIG.21, q(k)=1, 7, 4, 10, 2, 8, 5, 11, 3, 9, 6, 12 is obtained for k=1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12. Thus, Dch #(k) is distributively arranged in RB #(q(k)). Specifically, as shown inFIG.22, Dch #1 is arranged in RB #1, Dch #5 is arranged in RB #2, Dch #9 is arranged in RB #3, Dch #3 is arranged in RB #4, Dch #7 is arranged in RB #5, Dch #11 is arranged in RB #6, Dch #2 is arranged in RB #7, Dch #6 is arranged in RB #8, Dch #10 is arranged in RB #9, Dch #4 is arranged in RB #10, Dch #8 is arranged in RB #11, and Dch #12 is arranged in RB #12. Thus, when using Lch's (FIG.3), Lch #1 through #12 with consecutive channel numbers are arranged in order in RB #1 through #12, whereas when using Dch's (FIG.22), Dch's with consecutive channel numbers are arranged in RBs that are distributively arranged in terms of frequency. That is to say, different channel numbers are set for each RB of RB #1 through #12 when Lch's are used and when Dch's are used. As in Embodiment 1, an example of allocation by allocation section103of base station100(FIG.1) when four consecutive Dch's, Dch #1 through #4, are used for a Dch data symbol of one mobile station is shown inFIG.23. Here, allocation section103holds the Dch arrangement pattern shown inFIG.22, and allocates a Dch data symbol to RBs in accordance with the arrangement pattern shown inFIG.22. As shown inFIG.23, allocation section103allocates a Dch data symbol to RB #1 in which Dch #1 is arranged, RB #7 in which Dch #2 is arranged, RB #4 in which Dch #3 is arranged, and RB #10 in which Dch #4 is arranged. That is to say, as shown inFIG.23, a Dch data symbol is allocated to RB #1, #4, #7, #10. Also, as shown inFIG.23, allocation section103allocates an Lch data symbol to remaining RB #2, #3, #5, #6, #8, #9, #11, #12 other than the RBs to which a Dch data symbol has been allocated. That is to say, Lch #2, #3, #5, #6, #8, #9, #11, #12 shown inFIG.3are used for an Lch data symbol. Next, as in Embodiment 1, an example of extraction by demapping section207of mobile station200(FIG.2) will be described for a case in which a Dch data symbol using four consecutive Dch's, Dch #1 through #4, is allocated to mobile station200. Here, demapping section207holds the Dch arrangement pattern shown inFIG.22, the same as allocation section103, and extracts a Dch data symbol from a plurality of RBs in accordance with the arrangement pattern shown inFIG.22. First channel number Dch #1 and last channel number Dch #4 are indicated in Dch data symbol allocation information reported to mobile station200from base station100. Since the Dch channel numbers indicated in the Dch data symbol allocation information are Dch #1 and Dch #4, demapping section207identifies the fact that Dch's used for a Dch data symbol addressed to that station are the four consecutive Dch's Dch #1 through #4. Then, following a similar procedure to allocation section103, demapping section207extracts Dch #1 arranged in RB #1, Dch #2 arranged in RB #7, Dch #3 arranged in RB #4, and Dch #4 arranged in RB #10, as shown inFIG.23. That is to say, demapping section207extracts a Dch data symbol allocated to RB #1, #4, #7, #10, as shown inFIG.23, as a data symbol addressed to that station. In this embodiment, as with Arrangement Methods 1 through 3 of Embodiment 1, a Dch data symbol is allocated to four RBs, and an Lch data symbol is allocated to eight RBs. Also, in this embodiment, a Dch data symbol is distributively allocated every three RBs, to RB #1, RB #4, RB #7, and RB #10, as shown inFIG.23, enabling a frequency diversity effect to be improved. Furthermore, as shown inFIG.23, having a Dch data symbol allocated to distributively arranged RBs also means that an Lch data symbol is distributed, making it possible to perform frequency scheduling using RBs across a wider band. Thus, in this embodiment, only one Dch is arranged in one RB, and a plurality of different Dch's with consecutive channel numbers are arranged in RBs that are distributively arranged in the frequency domain. By this means, when a plurality of Dch's are allocated to one mobile station, non-use of some RBs is completely eliminated, and a frequency diversity effect can be obtained. Also, according to this embodiment, Dch's with consecutive channel numbers are arranged in RBs that are distributively arranged in the frequency domain, but Dch channel numbers and RB numbers are mutually mapped in advance, enabling control information for reporting a Dch allocation result to be reduced in the same way as in Embodiment 1. Embodiment 4 In this embodiment a case will be described in which switching between use of Arrangement Method 1 and Arrangement Method 4 of Embodiment 1 is performed according to per-RB number of subblock divisions Nd. As described above, Arrangement Method 4 enables more RBs consecutive in the frequency domain that can be used for Lch's to be secured than Arrangement Method 1. On the other hand, when a large number of Dch's are used, with Arrangement Method 4 the interval between RBs in which Dch's are arranged differs greatly according to the Dch, and therefore a frequency diversity effect due to Dch's is non-uniform. Specifically, inFIG.15Dch #1 is arranged in RB #1 and #12, and therefore the RB interval is 11 RBs and a large frequency diversity effect is obtained, but Dch #12 is arranged in RB #6 and #7, and therefore the RB interval is 1 and the frequency diversity effect is small. On the other hand, with Arrangement Method 1 the interval between RBs in which one Dch is arranged is uniform, enabling a uniform frequency diversity effect to be obtained irrespective of the Dch. Also, as stated above, by using a larger value of Nd the larger the number of mobile stations or the number of Dch's used, a frequency diversity effect can be further improved while preventing a fall in communication resource utilization efficiency. Thus, in this embodiment, allocation section103allocates Dch's using Arrangement Method 1 when the value of Nd is large—that is, when more Dch's are allocated—and allocates Dch's using Arrangement Method 4 when the value of Nd is small—that is, when fewer Dch's are allocated. Specifically, allocation section103performs arrangement method switching based on a comparison between Nd and a preset threshold value. That is to say, allocation section103switches to Arrangement Method 1 when Nd is greater than or equal to the threshold value, and switches to Arrangement Method 4 when Nd is less than the threshold value. For example, the Dch arrangement shown inFIG.15is used when Nd=2, and the kind of arrangement shown inFIG.19is used when Nd=4. By this means, a frequency diversity effect can be improved whether the number of Dch's is large or small. That is to say, when the value of Nd is large (when the number of Dch's is large), an arrangement is adopted that allows uniformly good frequency diversity to be obtained for all Dch's, and when the value of Nd is small (when the number of Dch's is small), an arrangement is adopted that enables a frequency diversity effect to be improved for a specific Dch. Here, when the number of Dch's is small, nonuniformity of a frequency diversity effect with Arrangement Method 4 is not a problem if Dch's in the vicinity of both ends of the band (that is, low-numbered Dch's inFIG.15) are used preferentially. Using Arrangement Method 4 when the value of Nd is small (when the number of Dch's is small) enables more consecutive Lch RBs to be secured, and enables a consecutive RB allocation reporting method to be used for more Lch's. When the number of mobile stations is small, one mobile station often occupies a large number of RBs when communicating, and there is consequently a large communication efficiency improvement effect. Using Arrangement Method 1 when the value of Nd is large (when the number of Dch's is large) enables more distributed Lch RBs to be secured. When the number of mobile stations is large, the more distributed Lch's are for use of resources by a plurality of mobile stations, the greater is a frequency scheduling effect, and consequently the more communication efficiency improves. Since the ratio between the number of mobile stations using Dch's and the number of mobile stations using Lch's is generally constant irrespective of the total number of mobile stations, this embodiment is effective. Thus, according to this embodiment, a good frequency diversity effect is obtained irrespective of the number of mobile stations, and communication efficiency can be improved. Embodiment 5 In this embodiment, the fact that Dch's with consecutive channel numbers are arranged in different RBs and Dch's with channel numbers within a predetermined number are arranged in one RB is the same as in Arrangement Method 3 of Embodiment 1, but Dch's are arranged using a different block interleaver from that in Arrangement Method 3 of Embodiment 1. This is described in concrete terms below. Here, as with Arrangement Method 3 of Embodiment 1, it is assumed that Nrb=12, Nd=2, and the predetermined number is 2. Also, Lch #1 through #12 or Dch #1 through #12 are formed by means of RBs. In this embodiment, Dch channel numbers are given by the 3-row×4-column block interleaver shown inFIG.24. Specifically, Dch channel numbers k=1, 2, . . . , Nrb are input to the block interleaver shown inFIG.24, and Dch channel numbers j(k) are output. That is to say, Dch channel numbers are rearranged by the block interleaver shown inFIG.24. Then, if k≤floor(Nrb/Nd), the RB numbers of RBs in which Dch #(j(k)) is arranged become RB #(k) and RB #(k+floor(Nrb/Nd)). On the other hand, if k>floor(Nrb/Nd), the RB numbers of RBs in which Dch #(j(k)) is arranged become RB #(k) and RB #(k-floor(Nrb/Nd)). Here, floor(Nrb/Nd) represents an interval between RBs in which one Dch is arranged. Here, since Nrb=12 and Nd=2, floor(Nrb/Nd)=6. Also, as regards j(k), j(k)=1, 5, 9, 2, 6, 10, 3, 7, 11, 4, 8, 12 is obtained for k=1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, as shown inFIG.24. Thus, when k≤6, Dch #(j(k)) is distributively arranged in two RBs, RB #(k) and RB #(k+6), separated by a 6 (=floor(12/2)) RB interval in the frequency domain, and when k>6, Dch #(j(k)) is distributively arranged in two RBs, RB #(k) and RB #(k−6), separated by a 6 RB interval in the frequency domain. Specifically, when k=1, j(k)=1, and therefore Dch #1 is distributively arranged in RB #1 and RB #7 (=1+6), and when k=2, j(k)=5, and therefore Dch #5 is distributively arranged in RB #2 and RB #8 (=2+6). The above explanation can be applied when k=3 through 6. Also, when k=7, j(k)=3, and therefore Dch #3 is distributively arranged in RB #7 and RB #1 (=7-6), and when k=8, j(k)=7, and therefore Dch #7 is distributively arranged in RB #8 and RB #2 (=8-6). The above explanation can be applied when k=9 through 12. By this means, as shown inFIG.11, Dch #1 and #3 are arranged in RB #1 (RB #7), Dch #5 and #7 are arranged in RB #2 (RB #8), Dch #9 and #11 are arranged in RB #3 (RB #9), Dch #2 and #4 are arranged in RB #4 (RB #10), Dch #6 and #8 are arranged in RB #5 (RB #11), and Dch #10 and #12 are arranged in RB #6 (RB #12), in the same way as in Arrangement Method 3 of Embodiment 1. That is to say, Dch's with consecutive channel numbers are arranged in different RBs, and Dch's with channel numbers within a predetermined number (here, 2) are arranged in one RB. Thus, the same kind of effect as in Arrangement Method 3 of Embodiment 1 can also be obtained when Dch channel numbers are interleaved using the block interleaver shown inFIG.24. Here, channel numbers j(k)=1, 5, 9, 2, 6, and 10 of the first half of the block interleaver output shown inFIG.24(that is, the first and second columns of the block interleaver), and channel numbers j(k)=3, 7, 11, 4, 8, and 12 of the second half of the block interleaver output shown inFIG.24(that is, the third and fourth columns of the block interleaver), are arranged in the same RBs as shown inFIG.11. That is to say, channel numbers located at the same position in the 3-row×2-column first half of the block interleaver shown inFIG.24comprising the first and second columns, and the 3-row×2-column second half of the block interleaver shown inFIG.24comprising the third and fourth columns, have a correspondence relationship of being arranged in the same RBs. For example, channel number 1 located in the first column of the first row of the first half (the first column of the first row of the block interleaver shown inFIG.24), and channel number 3 located in the first column of the first row of the second half (the third column of the first row of the block interleaver shown inFIG.24), are arranged in the same RBs (RB #1 and #7 shown inFIG.11). Similarly, channel number 5 located in the first column of the second row of the first half (the first column of the second row of the block interleaver shown inFIG.24), and channel number 7 located in the first column of the second row of the second half (the third column of the second row of the block interleaver shown inFIG.24), are arranged in the same RBs (RB #2 and #8 shown inFIG.11). The above explanation can be applied to other positions. Also, channel numbers located at the same position in the first half and second half of the block interleaver output are channel numbers separated by (number of columns/Nd). Therefore, by making the number of columns of the block interleaver4, as shown inFIG.24, Dch's with channel numbers separated by only two channel numbers are arranged in the same RB. That is to say, Dch's with channel numbers within a predetermined number (number of columns/Nd) are arranged in the same RB. In other words, the difference between channel numbers of Dch's arranged in one RB can be kept within a predetermined number by making the number of columns of a block interleaver [predetermined number×Nd]. Next, a channel arrangement method will be described for a case in which the number of Dch channels (corresponding here to number of RBs Nrb) is not divisible by the number of columns of the block interleaver. This is described in concrete terms below. It is assumed here that Nrb=14, Nd=2, and the predetermined number is 2. Also, Lch #1 through #14 or Dch #1 through #14 are formed by means of RBs. Since Nd=2 and the predetermined number is 2, the number of columns of the block interleaver is 4. Thus, with regard to the block interleaver size, the number of columns is fixed at 4, and the number of rows is calculated as ceil(Nrb/number of columns), where operator ceil(x) represents the smallest integer that exceeds x. That is to say, a 4 (=ceil(14/4))-row×4-column block interleaver such as shown inFIG.25is used here. While the size of the block interleaver shown inFIG.25is 16 (=4 rows×4 columns), Dch channel numbers k=1, 2, . . . , Nrb that are input to the block interleaver are only 14 in number. That is to say, the number of Dch channels is smaller than the size of the block interleaver, and the number of Dch channels (14) is not divisible by the number of columns of the block interleaver (4). Thus, in this embodiment, a number of Nulls equivalent to the difference between the size of the block interleaver and the number of Dch channels are inserted in the block interleaver. That is to say, two (=16-14) Nulls are inserted in the block interleaver as shown inFIG.25. Specifically, two Nulls are inserted uniformly in the last fourth-row of the block interleaver. In other words, two Nulls are inserted at every other position in the last fourth-row of the block interleaver. That is to say, as shown inFIG.25, Nulls are inserted in the second column and fourth column of the fourth row within the 4-row×4-column block interleaver. Thus, as shown inFIG.25, Dch channel numbers k=1 through 14 are input in the column direction at positions other than those of the Nulls in the second column and fourth column of the last fourth-row. That is to say, in the last row of the block interleaver, Dch channel numbers k=13 and 14 are inserted at every other position in the column direction. When Nd=2, two mutually different Dch's are distributively arranged in each subblock of two RBs, and therefore the total number of Dch channels is an even number. Consequently, only cases in which the number of Nulls inserted in a block interleaver in which the number of columns is 4 is 0 or 2 are possible. Here, since Nrb=14 and Nd=2, floor(Nrb/Nd)=7. Also, j(k) is given by a 4-row×4-column block interleaver as shown inFIG.25. The Nulls inserted in the block interleaver shown inFIG.25are skipped when block interleaver output is performed, and are not output as j(k). That is to say, j(k)=1, 5, 9, 13, 2, 6, 10, 3, 7, 11, 14, 4, 8, 12 is obtained for k=1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, as shown inFIG.25. Thus, when k≤7, Dch #(j(k)) is distributively arranged in two RBs, RB #(k) and RB #(k+7), separated by a 7 (=floor(14/2)) RB interval in the frequency domain, and when k>7, Dch #(j(k)) is distributively arranged in two RBs, RB #(k) and RB #(k−7), separated by a 7 RB interval in the frequency domain. Specifically, when k=1, j(k)=1, and therefore Dch #1 is distributively arranged in RB #1 and RB #8 (=1+7), and when k=2, j(k)=5, and therefore Dch #5 is distributively arranged in RB #2 and RB #9 (=2+7). The above explanation can be applied when k=3 through 7. Also, when k=8, j(k)=3, and therefore Dch #3 is distributively arranged in RB #8 and RB #1 (=8−7), and when k=9, j(k)=7, and therefore Dch #7 is distributively arranged in RB #9 and RB #2 (=9−7). The above explanation can be applied when k=10 through 14. By this means, as shown inFIG.26, Dch #1 and #3 are arranged in RB #1 (RB #8), Dch #5 and #7 are arranged in RB #2 (RB #9), Dch #9 and #11 are arranged in RB #3 (RB #10), Dch #13 and #14 are arranged in RB #4 (RB #11), Dch #2 and #4 are arranged in RB #5 (RB #12), Dch #6 and #8 are arranged in RB #6 (RB #13), and Dch #10 and #12 are arranged in RB #7 (RB #14). That is to say, two Dch's with channel numbers within predetermined number 2 are arranged in all RBs, as shown inFIG.26. Similarly to the case of the block interleaver shown inFIG.24, channel numbers j(k)=1, 5, 9, 13, 2, 6, and 10 of the first half of the block interleaver output shown inFIG.25(that is, the first and second columns of the block interleaver), and channel numbers j(k)=3, 7, 11, 14, 4, 8, and 12 of the second half of the block interleaver output (that is, the third and fourth columns of the block interleaver), are arranged in the same RBs as shown inFIG.26. Here, one of the two Nulls inserted in the block interleaver shown inFIG.25is inserted in the 4-row×2-column first half of the block interleaver shown inFIG.25comprising the first and second columns, and the other of the two Nulls is inserted in the 4-row×2-column second half of the block interleaver comprising the third and fourth columns. The positions at which the two Nulls are inserted are the second column of the fourth row of the first half of block interleaver output (the second column of the fourth row of the block interleaver shown inFIG.25), and the second column of the fourth row of the second half of block interleaver output (the fourth column of the fourth row of the block interleaver shown inFIG.25). That is to say, the two Nulls are inserted at the same positions in the first half and second half of the block interleaver shown inFIG.25. That is to say, the two Nulls are inserted at positions that can be arranged in the same RB in the block interleaver. Consequently, for Dch channel numbers input at positions other than positions at which a Null is inserted, also, a correspondence relationship whereby channel numbers within a predetermined number (number of columns/Nd) are arranged in the same RB is maintained. Therefore, Dch's with channel numbers within a predetermined number (number of columns/Nd) are arranged in the same RB even if the number of Dch channels is smaller than the size of the block interleaver. Next, the input/output processing flow of the block interleaver shown inFIG.25will be described usingFIG.27. Here, the number of rows of the block interleaver is fixed at 4. In step (hereinafter referred to as “ST”)101, the size of the block interleaver is decided as ceil(Nrb/4) rows×4 columns. In ST102, it is determined whether or not number of RBs Nrb is divisible by 4. Here, operator mod shown inFIG.27indicates a modulo operator. If number of RBs Nrb is determined to be divisible by 4 in ST102(ST102: YES), in ST103Dch channel numbers (k) are written consecutively to the block interleaver in the column direction. In ST104, Dch channel numbers (j(k)) are read consecutively from the block interleaver in the row direction. On the other hand, if number of RBs Nrb is determined not to be divisible by 4 in ST102(ST102: NO), in ST105Dch channel numbers (k) are written consecutively to the block interleaver in the column direction, in the same way as in ST103. However, a Null is inserted in every other column in the last row (for example, the fourth row shown inFIG.25) of the block interleaver. In ST106, Dch channel numbers (j(k)) are read consecutively from the block interleaver in the row direction in the same way as in ST104. However Dch channel numbers (j(k)) are read in which Nulls inserted at the time of block interleaver writing (for example, the second column and fourth column of the fourth row shown inFIG.25) are skipped. Thus, if the number of Dch channels is not divisible by the number of columns of the block interleaver, at the time of block interleaver input Dch channel numbers k are written with Nulls inserted, and at the time of block interleaver output Dch channel numbers (k) are read with the Nulls skipped. By this means, even if the number of Dch channels is not divisible by the number of columns of the block interleaver, Dch's with consecutive channel numbers can be arranged in different RBs, and Dch's with channel numbers within a predetermined number can be arranged in one RB, in the same way as in Arrangement Method 3 of Embodiment 1. In base station100and mobile station200, Dch's with consecutive channel numbers are arranged in different RBs by means of the above-described Dch channel arrangement method, and RBs for which Dch's with channel numbers within a predetermined number are arranged in one RB, and Dch's, are mutually mapped in advance. That is to say, allocation section103of base station100(FIG.1) and demapping section207of mobile station200(FIG.2) hold the Dch arrangement pattern shown inFIG.26associating RBs with Dch's. Then, in the same way as in Arrangement Method 3 of Embodiment 1, allocation section103of base station100allocates a Dch data symbol to RBs in accordance with the Dch arrangement pattern shown inFIG.26. On the other hand, demapping section207of mobile station200, following a similar procedure to allocation section103, extracts a Dch data symbol addressed to that station from a plurality of RBs in accordance with the Dch arrangement pattern shown inFIG.26. By this means, in the same way as in Arrangement Method 3 of Embodiment 1, when the number of Dch's used for a Dch data symbol of one mobile station is small, although there is a possibility of subblocks other than subblocks allocated within RBs not being used, a frequency diversity effect can be obtained preferentially. Also, even when the number of Dch's used for a Dch data symbol of one mobile station is large—that is, when the number of allocated RBs is large it is possible to use all subblocks within RBs while obtaining a frequency diversity effect. Thus, in this embodiment, by interleaving Dch channel numbers, Dch's with consecutive channel numbers are arranged in different RBs, and Dch's with channel numbers within a predetermined number are arranged in one RB. By this means, in the same way as in Arrangement Method 3 of Embodiment 1, when the number of Dch's used for a Dch data symbol of one mobile station is small, a frequency diversity effect can be improved. Also, even when the number of Dch's used for a Dch data symbol of one mobile station is large, a frequency diversity effect can be improved without reducing communication resource utilization efficiency. Also, in this embodiment, even if the number of Dch channels and the size of the block interleaver do not match and the number of Dch channels is not divisible by the number of columns of the block interleaver, Dch's with consecutive channel numbers can be arranged in different RBs, and Dch's with channel numbers within a predetermined number can be arranged in one RB, by inserting Nulls in the block interleaver. Furthermore, according to this embodiment, it is possible to apply the same block interleaver configuration—that is, the same channel arrangement method—to systems with different numbers of Dch channels simply by inserting Nulls in the block interleaver. In this embodiment, a case has been described in which number of RBs Nrb is an even number (for example, Nrb=14). However, the same kind of effect as in this embodiment can also be obtained when number of RBs Nrb is an odd number by replacing Nrb with the maximum even number not exceeding Nrb. Also, in this embodiment, a case has been described in which positions at which two Nulls are inserted are the second column of the fourth row of the first half of block interleaver output (the second column of the fourth row of the block interleaver shown inFIG.25), and the fourth column of the fourth row of the second half of block interleaver output (the fourth column of the fourth row of the block interleaver shown inFIG.25). However, in the present invention, it is only necessary for positions at which two Nulls are inserted to be the same position in the first half and second half of block interleaver output. Thus, for example, positions at which two Nulls are inserted may be the first column of the fourth row of the first half of block interleaver output (the first column of the fourth row of the block interleaver shown inFIG.25), and the first column of the fourth row of the second half of block interleaver output (the third column of the fourth row of the block interleaver shown inFIG.25). Also, positions at which two Nulls are inserted are not limited to the last row of the block interleaver (for example, the fourth row shown inFIG.25), but may be in a different row (for example, the first, second, or third row shown inFIG.25). This concludes a description of embodiments of the present invention. In the above embodiments, a channel arrangement method whereby Dch's are arranged in RBs depends on a total number of RBs (Nrb) decided by the system bandwidth. Thus, provision may be made for a base station and mobile station to hold a Dch channel number/RB number correspondence table (such as shown inFIG.4,FIG.8,FIG.11,FIG.15, orFIG.26, for example) for each system bandwidth, and at the time of Dch data symbol allocation, to reference a correspondence table corresponding to a system bandwidth to which a Dch data symbol is allocated. In the above embodiments, a signal received by a base station (that is, a signal transmitted in an uplink by a mobile station) has been described as being transmitted by means of an OFDM scheme, but this signal may also be transmitted by means of a transmitting scheme other than an OFDM scheme, such as a single-carrier scheme or CDMA scheme, for example. In the above embodiments, a case has been described in which an RB is comprised of a plurality of subcarriers comprised of an OFDM symbol, but the present invention is not limited to this, and it is only necessary for a block to be comprised of consecutive frequencies. In the above embodiments, a case has been described in which RBs are comprised consecutively in the frequency domain, but RBs may also be comprised consecutively in the time domain. In the above embodiments, cases have been described that apply to a signal transmitted by a base station (that is, a signal transmitted in a downlink by a base station), but the present invention may also be applied to a signal received by a base station (that is, a signal transmitted in an uplink by a mobile station). In this case, the base station performs adaptive control of RB allocation and so forth for an uplink signal. In the above embodiments, adaptive modulation is performed only for an Lch, but adaptive modulation may also be similarly performed for a Dch. At this time, a base station may perform adaptive modulation for Dch data based on total-band average received quality information reported from each mobile station. In the above embodiments, an RB used for a Dch has been described as being divided into a plurality of subblocks in the time domain, but an RB used for a Dch may also be divided into a plurality of subblocks in the frequency domain, or may be divided into a plurality of subblocks in the time domain and the frequency domain. That is to say, in one RB, a plurality of Dch's may be frequency-domain-multiplexed, or may be time-domain-multiplexed and frequency-domain-multiplexed. In these embodiments, a case has been described in which, when a plurality of different Dch's with consecutive channel numbers are allocated to one mobile station, only a first channel number and last channel number are indicated to a mobile station from a base station, but, for example, a first channel number and a number of channels may also be indicated to a mobile station from a base station. In these embodiments, a case has been described in which one Dch is arranged in RBs distributively arranged at equal intervals in the frequency domain, but one Dch need not be arranged in RBs distributively arranged at equal intervals in the frequency domain. In the above embodiments, a Dch has been used as a channel for performing frequency diversity transmission, but a channel used is not limited to a Dch, and need only be a channel that is distributively arranged in a plurality of RBs or a plurality of subcarriers in the frequency domain, and enables a frequency diversity effect to be obtained. Also, an Lch has been used as a channel for performing frequency scheduling transmission, but a channel used is not limited to an Lch, and need only be a channel that enables a multi-user diversity effect to be obtained. A Dch is also referred to as a DVRB (Distributed Virtual Resource Block), and an Lch is also referred to as an LVRB (Localized Virtual Resource Block). Furthermore, an RB used for a Dch is also referred to as a DRB or DPRB (Distributed Physical Resource Block), and an RB used for an Lch is also referred to as an LRB or LPRB (Localized Physical Resource Block), where the DPRB and the LPRB are collectively referred to as a PRB (Physical Resource Block). A mobile station is also referred to as UE, a base station apparatus as Node B, and a subcarrier as a tone. An RB is also referred to as a subchannel, a subcarrier block, a subcarrier group, a subband, or a chunk. A CP is also referred to as a Guard Interval (GI). A subframe is also referred to as a slot or frame. In the above embodiments, a case has been described by way of example in which the present invention is configured as hardware, but it is also possible for the present invention to be implemented by software. The function blocks used in the descriptions of the above embodiments are typically implemented as LSIs, which are integrated circuits. These may be implemented individually as single chips, or a single chip may incorporate some or all of them. Here, the term LSI has been used, but the terms IC, system LSI, super LSI, and ultra LSI may also be used according to differences in the degree of integration. The method of implementing integrated circuitry is not limited to LSI, and implementation by means of dedicated circuitry or a general-purpose processor may also be used. An FPGA (Field Programmable Gate Array) for which programming is possible after LSI fabrication, or a reconfigurable processor allowing reconfiguration of circuit cell connections and settings within an LSI, may also be used. In the event of the introduction of an integrated circuit implementation technology whereby LSI is replaced by a different technology as an advance in, or derivation from, semiconductor technology, integration of the function blocks may of course be performed using that technology. The application of biotechnology or the like is also a possibility. The disclosures of Japanese Patent Application No. 2007-161958, filed on Jun. 19, 2007, Japanese Patent Application No. 2007-211545, filed on Aug. 14, 2007, and Japanese Patent Application No. 2008-056561, filed on Mar. 6, 2008, including the specifications, drawings and abstracts, are incorporated herein by reference in their entirety. INDUSTRIAL APPLICABILITY The present invention is suitable for use in a mobile communication system or the like. | 92,059 |
11943753 | DETAILED DESCRIPTION FIGS.1A to1Cconsider three different modes of deployment for NB-IoT technology: in-band, guard-band, and standalone, according to examples. FIG.1Aschematically shows an example of in-band deployment. A frequency band is schematically shown at100. The NB-IoT carrier frequencies are schematically represented “in-band” at102. The “in-band” deployment efficiently utilises spectrum resources. However, the in-band deployment may introduce interference. It has been considered that in-band deployment may be used in an LTE context as no guard band is required between LTE and NB-IoT carriers and no interference is expected. In-band operation may require sharing of some of the NB-IoT resource blocks with LTE rendering them unavailable to NB-IoT at specific times. FIG.1Bschematically shows a stand-alone deployment. A frequency band is schematically shown at104. The NB-IoT carrier frequencies are schematically represented at106, protected on either side by guard-intervals108and110. It has been considered that stand-alone deployment may be used in a GSM context leaving guard interval of 10 kHz on both sides of the NB-IoT carrier. FIG.1Cschematically shows a guard band deployment. A frequency band is schematically shown at112. The NB-IoT carrier frequencies are schematically represented at114, utilizing the unused resource blocks in the radio carrier or overlay radio carrier's112guard-band. It has been considered that guard-band deployment may be used in an LTE context. When deployed, NR (5G) may use either frequency spectrum taken from LTE (i.e. refarming of LTE spectrum), or new NR spectrum may be used. For greenfield (i.e. new) NB-IoT deployments, it may be possible to use the standalone mode shown inFIG.1B. In other deployment scenarios, particularly where NB-IoT is already deployed, in-band deployment of NB-IoT within an NR carrier may be the best approach. Table 1 below shows some NR numerology options based on a subcarrier spacing of 15*2NkHz. TABLE 1Subcarrier spacing (kHz)153060120240Symbol duration (us)66.733.316.78.334.17Nominal Normal CP (us)4.72.31.20.590.29Min scheduling interval1414141428(symbols)Min scheduling interval (slots)11112Min scheduling interval (ms)10.50.250.1250.125 15 kHz subcarrier spacing (SCS) is similar to LTE. This spacing may be considered good for a wide area on traditional cellular bands. 30 kHz subcarrier spacing may be more suitable for urban and dense urban environments, as it provides e.g. lower latency and wider carrier bandwidth with given FFT size. 60 kHz subcarrier spacing (or higher) may be needed e.g. for greater than 10 GHz bands, to combat phase noise. 60 kHz SCS is supported also for bands below 10 GHz. Typically, LTE supports NB-IoT with the following design options:Only Frequency Division Duplex (FDD) mode with normal cyclic prefix (CP) length180 kHz UE RF bandwidth for both downlink (DL) and uplink (UL)DL utilises Orthogonal Frequency-Division Multiple Access (OFDMA) with 15 kHz subcarrier spacing: 12 subcarriers are available in one NB-IoT carrierUL utilizes single-carrier frequency division multiple access (SC-FDMA) and supports:Single tone transmission with 3.75 kHz SCSSingle tone transmission with 15 kHZ SCSMulti-tone (3, 6, 12) tone transmission with 15 kHz SCS. The legacy NB-IoT physical layer is based on LTE numerology, and is inherently designed for the in-band mode without any issues for coexistence with the LTE carrier in which it is deployed, other than matching NB-IoT channel raster with selected LTE channel. The channel raster may be considered a list of carrier centre frequencies that a communication device scans to find a carrier. For both NB-IoT and LTE, the carrier centre frequency is an integer multiple of 100 kHz. In some examples the centre frequency of the NB-IoT carrier can deviate slightly from the raster. For example, when considering available NB-IoT carrier locations corresponding to the centres of the PRBs (physical resource blocks) within the LTE channel, they may not exactly match with NB-IoT channel raster (LTE PRBs do not have centre frequency of 100 kHz multiple, only the LTE carrier has). NB-10T carrier may be off the 100 kHz raster by 2.5 or 7.5 kHz depending on LTE carrier bandwidth. This may be deemed acceptable. When the NB-IoT carrier is deployed in-band within a bandwidth part (BWP) of an NR carrier, however, there are potential issues when the numerology of the BWP does not match that of LTE. In particular, the size of the NR PRB may be larger than that of LTE when the sub-carrier spacing (SCS) is larger (the SCS can be as high as 60 kHz in sub-6-GHz deployments). A large SCS corresponds to a larger PRB in frequency, a shorter slot length and wider channel bandwidth (with given FFT size), therefore, the NB-IoT carrier occupies a bandwidth that is smaller than the NR PRB. Here the placement of the NB-IoT carrier or the NR carrier needs to be specified considering the channel rasters. Furthermore, considering the mismatched FFT (fast fourier transform) grids between the NB-IoT carrier and the NR carrier, matching channel rasters may not alone be enough as improper placement of the NB-IoT carrier may create mutual interference. On the other hand, a large guard-band between the NB-IoT carrier and the adjacent NR PRB would lead to wastage of spectrum. In legacy systems, LTE and NB-IoT channel raster is 100 kHz. The NB-IoT carrier is aligned with LTE PRB. As a result there is a frequency offset from the LTE channel raster to the centre frequency of the NB-IoT carrier. The anchor carrier can only be deployed in the PRB locations shown in the Table 2 below (from 0 to #PRBs−1). TABLE 2LTE system bandwidth3 MHz5 MHz10 MHz15 MHz20 MHzPRB indices for2, 122, 7, 17, 224, 9, 14, 19,2, 7, 12, 17,4, 9, 14, 19,NPSS (NB-IoT30, 35, 40,22, 27, 32,24, 29, 34,Primary4542, 47, 52,39, 44, 55,Synchronization57, 62, 67,60, 65, 70,Signal)/NSSS (NB-7275, 80, 85,IoT Secondary90, 95Synchronizationsignal)transmission The anchor carrier may be considered the carrier where synchronization channels (NPSS, NSSS) and broadcast channel NBPCH exist, and what the UE is scanning for. NB-IoT may also include non-anchor carriers for data transfer (multi-carrier support) in connected mode. In legacy systems the frequency offset is typically ±2.5 kHz for 10 MHz/20 MHz (even number of PRBs), ±7.5 kHz for 3 MHz/5/MHz/15 MHz (odd number of PRBs). If more than one PRB is allocated in the in-band operation, only the anchor PRB needs to satisfy 100 kHz channel raster requirements. Legacy systems do not disclose how an NB-IoT carrier may be deployed in-band within an NR carrier. The numerology, channel raster, and bandwidths of NR may differ from LTE. The NR channel raster depends on the RF channel frequency range. The NR channel raster range may be 5 kHz up to 3 GHz. The prior art does not disclose static configuration of sub-PRB resources for uplink or downlink. FIG.2shows configuration of an NB-IoT carrier206according to an example. A frequency band or radio carrier is shown schematically at200. The radio carrier200may be a 5G new radio (NR) carrier or a bandwidth part of the NR carrier. According to NR Rel-15, bandwidth part is a contiguous set of physical resource blocks, selected from a contiguous subset of the common resource blocks for a given numerology on a given carrier. For conciseness and ease of explanation three PRBs of carrier200are shown inFIG.2, namely PRBs220,222and224. Of course, in typical examples the carrier200may comprise more PRBs. For example the carrier200or bandwidth part may comprise twelve PRBs. PRB222is located between PRB220and PRB224. An NB-IoT carrier206is configured within the single PRB222. That is, the NB-IoT carrier206is configured “in-band” in the radio carrier200, in the example ofFIG.2. The NB-IoT carrier206is located between a first guard band208and a second guard band210. The NB-IoT carrier206and the first and second guard bands208and210are configured so that together they fill PRB222. In some examples the first guard band208is of equal size or near-equal size to second guard band210. In some examples the first guard band (or guard interval)208is of a different size (e.g. larger or smaller) than the second guard band (or guard interval). Where the guard bands are of a different size to each other, there may be configured a maximum allowable difference between the guard band sizes. In some examples the maximum allowable difference is 20 kHz. In some examples there is a specified minimum size for the guard bands, such that the guard bands208and210are equal to are larger than the specified minimum size. In some examples the size of the guard bands208and210may be constrained by a sub-carrier spacing (SCS). In some examples the SCS may be 30 kHz. That is in some examples the minimum guard band size may be 30 kHz. In some examples the minimum guard band size may be dependent on the SCS of the bandwidth part (BWP) of the radio carrier. In some examples the minimum guard-band size may be specified in terms of a number of subcarriers (e.g. n subcarriers), rather than a bandwidth size (e.g. X kHz). In examples the PRB222has a bandwidth that is greater than a bandwidth of NB-IoT carrier206. In some examples the PRB222has a bandwidth that is equal to 180 kHz (e.g. when using 15 kHz SCS). In some examples the PRB222has a bandwidth that is equal to or greater than 360 kHz (e.g. when using 30 kHz SCS). In some examples the PRB222has a bandwidth that is equal to or greater than 720 kHz (e.g. when using 60 kHz or higher SCS). Therefore in some examples the NB-IoT carrier has available bandwidth equal to 180 kHz. In some examples the NB-IoT carrier has available bandwidth equal or less than 360 kHz. In some examples the NB-IoT carrier has a bandwidth equal or less than 720 kHz. According to some examples the PRB222is blank or not used for NR UEs prior to, or during, deployment of the NB-IoT carrier206therein. Accordingly, in some examples the method comprises determining or selecting a blank PRB in a radio carrier for deployment or configuration in the blank PRB of an NB-IoT carrier. According to some examples, there may be an allocation of a portion of bandwidth of a PRB containing the NB-IoT carrier206. For example, it may be determined that there is sufficient bandwidth in the PRB222for NB-IoT carrier206, the guard bands208and210, and bandwidth for allocation to one or more entities or apparatus. For example any spare or residual bandwidth may be allocated to one or more user equipment. It will be understood that in examples the NB-IoT carrier is configured relative to the radio carrier. In one example, the NR PRB grid is fixed, and the NB-IoT carrier is configured relative to the NR PRB grid. That is in an example, the NR (5G) carrier location and PRBs may be defined, and the NB-IoT carrier is configured relative to the fixed NR carrier location and PRBs. In another example the NB-IoT carrier is fixed, and the NR PRB grid is adjusted around the NR PRB grid. That is in an example the NB-IoT carrier already exists, and the NR carrier location and/or NR BWP are defined so as to optimize the location of the NB-IoT carrier (for example, inside a single PRB with adequate guards). It will also be understood that although in some examples the NB-IoT carrier is shown as placed in a single PRB, in some examples the NB-IoT carrier may overlap two or more PRBs. In such examples the two or more PRBs together have a bandwidth greater than the NB-IoT carrier. According to some examples the configuring the NB-IoT carrier in the PRB comprises a comparison determination. According to some examples the comparison comprises a comparison between a frequency characteristic of the NB-IoT carrier and a frequency characteristic of the radio carrier in which the NB-IoT carrier is to be configured or deployed. According to some examples the frequency characteristic of the NB-IoT anchor carrier comprises a channel raster of the NB-IoT carrier. According to some examples the frequency characteristic of the radio carrier comprises a channel raster of the radio carrier. As discussed above the channel raster may comprise one or more steps or frequencies that are available. According to some examples the NB-IoT carrier, and the radio carrier in which the NB-IoT carrier is deployed are within a specified frequency offset relative to each other. More particularly, in some examples the NB-IoT carrier, and the PRB in which the NB-IoT carrier is deployed are within a specified offset relative to each other. According to some examples the NB-IoT carrier location is within a maximum offset relative to the NB-IoT channel raster. According to an example the maximum offset comprises 7.5 kHz. In some examples, the frequency offset of the NB-IoT carrier is dependent on the SCS and/or PRB of the NR in which the NB-IoT carrier is deployed. According to some examples the NB-IoT carrier can be deployed in different operation modes within the NR carrier depending on the frequency characteristic of the NB-IoT carrier and the frequency characteristic of the NR carrier. For example, NB-IoT can be deployed using a different frequency offset in guard-band or in-band operation mode compared to in stand-alone operation mode. Therefore, NB-IoT carrier may be deployed in guard-band operation mode within the NR carrier if the frequency offset is more suitable based on placement of NB-IoT carrier within the NR PRB. According to some examples the frequency characteristic of the NB-IoT carrier comprises a central frequency or carrier frequency of the narrowband internet of things carrier, and the frequency characteristic of the radio carrier comprises a central frequency or carrier frequency of the radio carrier. According to some examples the narrowband internet of things carrier is deployed in the radio carrier in a manner such that a central frequency of the NB-IoT carrier does not align with a PRB of the radio carrier. According to some examples, two or more NB-IoT carriers may be deployed within a same PRB (for example anchor carrier and one or more non-anchor carriers). According to some examples the two or more NB-IoT carriers are deployed adjacent each other within the same PRB. This is schematically shown inFIG.3which shows an NB-IoT anchor carrier306adjacent to an NB-IoT non-anchor carrier307, within PRB322. Guard bands are shown at308and310. Adjacent PRBs are shown at320and324. In some examples the radio carrier300may be adjusted on the raster so that an already deployed NB-IoT anchor carrier306is located as required within the PRB322that is reserved for NB-IoT. In other examples, the location or width of the BWP of the radio carrier300containing the PRB322is adjusted so that an already deployed NB-IoT anchor carrier306is located as required within the PRB322. As discussed above, the NR PRB can be quite large (such as 720 kHz when using 60 kHz SCS or 360 kHz when using 30 kHz SCS), and the NB-IoT carrier (e.g. 180 kHz) may cover only a portion of the NR PRB. In order to improve spectrum, in some examples the NR resource allocation may optimize the current coexistence scenario. According to some examples this is achieved by means of partial PRB allocation. According to an example, an apparatus such as a base station (e.g. gNB) may configure a partial PRB for allocation to NR UEs within the PRB reserved for NB-IoT deployment on the uplink and/or downlink. That is the base station may allocate a partial portion of a PRB to one or more user equipment. According to some examples, the partial portion of the physical resource block comprises a residual portion of the physical resource block after the narrowband internet of things carrier and guard bands have been accommodated in the physical resource block. A size of the partial or residual PRB resource may be determined such that the minimum guard band size with the NB-IoT carrier is provided. According to some examples the supported partial PRB sizes are predefined. For example a partial PRB size may be e.g. ¼ PRB (3 subcarriers); ⅓ PRB (4 subcarriers), and/or ½ PRB (6 subcarriers); or dynamically assigned (N subcarriers). According to an example the NR PRB index with a partial resource may be indicated through higher layer signaling. In some examples, where the sub-carriers allotted for NB-IoT are indicated to the UE as invalid via higher layer signalling, then they shall remain invalid independent of the DCI instructions. Information of a size of the partial PRB and its location within the PRB may be comprised in the indication. According to some examples a new DCI (Downlink Control Information) format is not defined for allocation of partial PRB resources. In such examples when DCI assigns a UE resources in a PRB configured as a partial PRB, the resource allocation is understood to correspond to the configured part. In some examples a DCI is defined to indicate what is assigned. According to some examples, from a NR (5G) point of view, the guard band portion of the PRB can be seen as a reserved resource. According to some examples the UE may perform rate matching around reserved subcarriers. Therefore, according to some examples a UE is assigned only a partial PRB. According to some examples a UE may be assigned a partial PRB together with other or full PRBs. According to some examples a transport block size (TBS) includes support for a partial PRB allocation According to some examples a base station (e.g. gNB) may indicate dynamically, whether to use a certain PRB as partial PRB or full (normal) PRB. Some of these concepts are explained with respect toFIG.4which schematically shows a radio carrier400comprising PRBs420,422and424(more PRBs may be provided in examples). PRB422comprises NB-IoT carrier406, with guard bands408and410. NB-IoT carrier406, plus guard bands408and410do not fill PRB422. Accordingly, to improve spectrum utilization, a partial portion411of PRB422may be allocated to one or more UEs. According to some examples, the method of configuring of the NB-IoT carrier relative to a radio carrier is carried out by a control apparatus of a network.FIG.5shows an example of a control apparatus for a communication system, for example to be coupled to and/or for controlling a station of an access system, such as a RAN node, e.g. a base station, gNB, a central unit of a cloud architecture or a node of a core network such as an MME or S-GW, a scheduling entity such as a spectrum management entity, or a server or host. In some examples the gNB controls scheduling. Static configuration of the location of NB-IoT may be received via O&M. The control apparatus may be integrated with or external to a node or module of a core network or RAN. In some embodiments, base stations comprise a separate control apparatus unit or module. In other embodiments, the control apparatus can be another network element such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such a control apparatus as well as a control apparatus being provided in a radio network controller. The control apparatus500can be arranged to provide control on communications in the service area of the system. The control apparatus500comprises at least one memory501, at least one data processing unit502,503and an input/output interface504. Via the interface the control apparatus can be coupled to a receiver and a transmitter of a base station. The receiver and/or the transmitter may be implemented as a radio front end or a remote radio head. For example the control apparatus500or processor501can be configured to execute an appropriate software code to provide the control functions. The control apparatus500may communicate with one or more wireless communication devices. A wireless communication device may be for example a mobile device, that is, a device not fixed to a particular location, or it may be a stationary device. The wireless device may need human interaction for communication, or may not need human interaction for communication. In the present teachings the terms UE or “user” are used to refer to any type of wireless communication device. FIG.6schematically shows an example of a wireless device600, such as a user equipment (UE). A UE may be configured to use the NB-IoT carrier relative to the radio carrier. For example, the UE may be configured to use the NB-IoT carrier relative to the radio carrier in response to a configuration provided by a base station. The wireless device600may receive signals over an air or radio interface607via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. InFIG.6transceiver apparatus is designated schematically by block606. The transceiver apparatus606may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the wireless device. A wireless device is typically provided with at least one data processing entity601, at least one memory602and other possible components603for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference604. The user may control the operation of the wireless device by means of a suitable user interface such as key pad605, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display608, a speaker and a microphone can be also provided. Furthermore, a wireless communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto. FIG.7is a flow chart showing a method according to an example, viewed from the perspective of e.g. a base station. At S1the method comprises configuring an NB-IoT carrier. This may comprise configuring a narrowband internet of things carrier relative to one or more physical resource blocks of a radio carrier, the one or more physical resource blocks having a bandwidth that is greater than a bandwidth of the narrowband internet of things carrier. At S2, the method comprises configuring guard bands. This may comprise configuring the narrowband internet of things carrier relative to the one or more physical resource blocks such that there is a first guard band between the narrowband internet of things carrier and a first adjacent physical resource block, and a second guard band between the narrowband internet of things carrier and a second adjacent physical resource block FIG.8is a flow chart showing a method according to an example, viewed from the perspective of e.g. a UE. The method ofFIG.8may be carried out in response to receiving a configuration from a base station, for example. At S1the method comprises using an NB-IoT carrier. This may comprise using a narrowband internet of things carrier relative to one or more physical resource blocks of a radio carrier, the one or more physical resource blocks having a bandwidth that is greater than a bandwidth of the narrowband internet of things carrier. At S2the method comprises using guard bands. This may comprise using the narrowband internet of things carrier relative to the one or more physical resource blocks such that there is a first guard band between the narrowband internet of things carrier and a first adjacent physical resource block, and a second guard band between the narrowband internet of things carrier and a second adjacent physical resource block. It will be understood that the described examples may enable in-band deployment of an NB-IoT carrier within a NR carrier for all supported NR SCSs while ensuring coexistence. The NB-IoT or NR carrier location can be tuned to ensure a minimum guard band as well as symmetric/asymmetric guard bands as desired. The described support of partial PRB usage reduces wastage of resources. Some examples relate to semi-static configuration of a partial PRB depending on available resources and dynamic allocation of the configured partial PRB to UEs. From a base station implementation point of view (e.g. gNB), examples may provide smooth coexistence between NB-IoT and NR. This may be at least in part because NB-IoT (using potentially different numerology compared to NR) can be “localized” within predefined NR PRBs having self-contained guard bands between NB-IoT and NR. In general, the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. The embodiments of this invention may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and/or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it. Further in this regard it should be noted that any blocks of the logic flow as in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples. Embodiments of the inventions may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate. The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary embodiment of this invention. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this invention will still fall within the scope of this invention as defined in the appended claims. Indeed there is a further embodiment comprising a combination of one or more embodiments with any of the other embodiments previously discussed. | 30,108 |
11943754 | DETAILED DESCRIPTION The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims. This disclosure includes several mini proposals to solve problems from several aspects include tone plan, small multi-RU (M-RU), EHT-SIG coding. The protocol has not been discussed so far in extremely high throughput (EHT). Example embodiments of the present disclosure relate to systems, methods, and devices for an EHT RU allocation table. In one or more embodiments, an EHT RU allocation system may facilitate changes to the null tones based on a new tone plan, facilitate the definition of the combination of 52+26 multi-RU (M-RU) for bandwidth (BW) greater than or equal to 80 MHz. In one or more embodiments, an EHT RU allocation system may facilitate aspects of EHT-SIG coding including 320 MHz uncompressed mode and unique RU indication from either compressed or uncompressed. In one or more embodiments, an EHT RU allocation system may facilitate an MU-MIMO user field coding of specific bits to indicate to a receiving device the number of users in an MU-MIMO transmission. The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures. FIG.1is a network diagram illustrating an example network environment of EHT RU allocation, according to some example embodiments of the present disclosure. Wireless network100may include one or more user devices120and one or more access points(s) (AP)102, which may communicate in accordance with IEEE 802.11 communication standards. The user device(s)120may be mobile devices that are non-stationary (e.g., not having fixed locations) or may be stationary devices. In some embodiments, the user devices120and the AP102may include one or more computer systems similar to that of the functional diagram ofFIG.3and/or the example machine/system ofFIG.4. One or more illustrative user device(s)120and/or AP(s)102may be operable by one or more user(s)110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s)120and the AP(s)102may be STAs. The one or more illustrative user device(s)120and/or AP(s)102may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user device(s)120(e.g.,124,126, or128) and/or AP(s)102may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device. For example, user device(s)120and/or AP(s)102may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an “origami” device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list. As used herein, the term “Internet of Things (IoT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.). The user device(s)120and/or AP(s)102may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3GPP standards. Any of the user device(s)120(e.g., user devices124,126,128), and AP(s)102may be configured to communicate with each other via one or more communications networks130and/or135wirelessly or wired. The user device(s)120may also communicate peer-to-peer or directly with each other with or without the AP(s)102. Any of the communications networks130and/or135may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks130and/or135may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, any of the communications networks130and/or135may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof. Any of the user device(s)120(e.g., user devices124,126,128) and AP(s)102may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s)120(e.g., user devices124,126and128), and AP(s)102. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices120and/or AP(s)102. Any of the user device(s)120(e.g., user devices124,126,128), and AP(s)102may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network. Any of the user device(s)120(e.g., user devices124,126,128), and AP(s)102may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions. Any of the user device(s)120(e.g., user devices124,126,128), and AP(s)102may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s)120(e.g., user devices124,126,128), and AP(s)102may be configured to perform any given directional reception from one or more defined receive sectors. MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, user devices120and/or AP(s)102may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming. Any of the user devices120(e.g., user devices124,126,128), and AP(s)102may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s)120and AP(s)102to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. In certain example embodiments, the radio component, in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g., 802.11b, 802.11g, 802.11n, 802.11ax), 5 GHz channels (e.g., 802.11n, 802.11ac, 802.11ax), or 60 GHZ channels (e.g., 802.11ad, 802.11ay). 800 MHz channels (e.g., 802.11ah). The communications antennas may operate at 28 GHz and 40 GHz. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list and that other 802.11 standards may be used (e.g., Next Generation Wi-Fi, or other standards). In some embodiments, non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g., IEEE 802.11af, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband. In one embodiment, and with reference toFIG.1, AP102may facilitate EHT RU allocation142with one or more user devices120. In one or more embodiments, the EHT RU allocation142may facilitate changes to the null tones based on new tone plan, facilitate the definition of the combination of 52+26 multi-RU (M-RU) for bandwidth (BW) greater than or equal to 80 MHz. In one or more embodiments, the EHT RU allocation142may facilitate aspects of EHT-SIG coding including 320 MHz uncompressed mode and unique RU indication from either compressed or uncompressed. In one or more embodiments, the EHT RU allocation142may facilitate an MU-MIMO user field coding of specific bits to indicate to a receiving device the number of users in an MU-MIMO transmission. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. FIG.1depicts an illustrative schematic diagram for EHT RU allocation, in accordance with one or more example embodiments of the present disclosure. In one or more embodiments, an EHT RU allocation system may facilitate changing the 80 MHz tone plan to align RUs with 20 MHz physical boundaries. The pilot tones will shift together with the new tone plan. However, null tones have not been discussed. In one or more embodiments, an EHT RU allocation system may facilitate changes in table 1 to the null tone table defined in IEEE 802.11ax (“1 lax”). Note that the underlined are the new nulls for 80 MHz. The crossed through are the ones removed by comparison to flax. TABLE 1802.11be Null tones80 MHz26, 52±258, ±259, ±312, ±313, ±366, ±393, ±446,±447, ±500, ±200, ±199, ±146, ±119, ±66,±65, −11:-2, 2:11.106±258, ±259, ±366, ±393, ±500, ±257,±256, ±255, ±254, ±253, ±146,±119, −11:-2, 2:11.242, 484−258:-254, 254:258, −11:-2, 2:11.996−11:-2, 2:11. Definition for 52+26 MRU for BW>80 MHz: The current specification framework document (SFD) defines 52+26 MRU up to 80 MHz, and the larger BW definitions are missed. In one or more embodiments, in the case of a frequency band greater than 80 MHz, an EHT RU allocation system may facilitate that each 80 MHz segment in 80, 160, 240, and 320 MHz BW, is comprised of a 52+26-tone RU combination defined for 80 MHz. For example, 80 MHz comprises one 80 MHz segment, 160 MHz comprises two 80 MHz segments, 240 MHz comprises three 80 MHz segments, 320 MHz comprises four 80 MHz segments. Each of those segments a combination of two tone RUs 52-tone RU and 26-tone RU are used when transmitting a frame. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. EHT-SIG Common Field Coding for Uncompressed Mode in 320 MHz: For 320 MHz PPDU, the EHT RU allocation fields in EHT-SIG have 9*8=72 bits per content channel (CC), which is −88 bits/CC including U-SIG overflow bits. But the user field block has ˜44 bits. There was a proposal to split the 88 bits into two codewords (CWs). However, the performance may be evaluated between one CW and two CWs as shown below inFIG.1. The observation is marginal gap between these two options (0.4-0.8 dB). Considering the overhead of two CWs, the proposal is to encode the common field with one CW for 320 MHz to align with the other BW. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. Unique RU Indication from Either Compressed or Uncompressed: 1 lax allows the same EHT RU allocation to be indicated by both compressed and uncompressed modes. This introduces a significant overhead increase, especially for larger BW. For example, for non-OFDMA transmission, the compressed mode requires 0 bits in the common field, but the uncompressed mode requires 144 bits in total. So this disclosure proposes that in 11 be the non-OFDMA RU allocation shall only be indicated by the compressed mode. MU-MIMO User Field to Enabled Pre-EHT Padding: In one or more embodiments, an EHT RU allocation may add a new field or use specific bits in the U-SIG field or EHT-SIG field of an EHT frame to indicate the number of users in MU-MIMO instead of repurposing the number of EHT-SIG symbol subfield to indicate the number of MU-MIMO user. For example, the common field for a non-OFDMA transmission to a single user and non-OFDMA transmission to multiple users (e.g., an MU-MIMO transmission) may be included in the U-SIG or the EHT-SIG field. The common field may comprise one or more bit that may be used for encoding information that may be used by a receiving device (e.g., an STA) to decode the information for processing. The bit location of each information is important since the receiving device would expect the information to be located at that location. Here, the EHT RU allocation system may encode information associated with a number of MU-MIMO users in three bits at bits17,18, and19(B17-19). It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. FIG.2illustrates a flow diagram of illustrative process200for an EHT RU allocation system, in accordance with one or more example embodiments of the present disclosure. At block202, a device (e.g., the user device(s)120and/or the AP102ofFIG.1) may utilize a tone plan to generate an extremely high throughput (EHT) frame to be sent using an 80 MHz frequency band, wherein the tone plan comprises a plurality of null tones. At block204, the device may encode one or more resource units (RUs) for the EHT frame, wherein the one or more RUs comprise at least one of a 26-tone RU, a 52-tone RU, a 106-tone RU, a 242-tone RU, a 484-tone RU, or a 996-tone RU, wherein the 106-tone RU, the 242-tone RU, and the 484-tone RU comprise null tones located at least at subcarriers ±258, ±257, ±256, ±255, and ±254. The 996-tone RU comprises null tones located at least at subcarriers at a first range of −11 to −2 and a second range of +2 to +11, with a subcarrier increment of 1. The 26-tone RU and the 52-tone RU comprise null tones located at least at subcarriers ±258, ±259, ±312, ±313, ±366, ±393, ±446, ±447, ±500, ±200, ±199, ±146, ±119, ±66, ±65, and −11:−2, 2:11. The 106-tone RU further comprises null tones located at least at subcarriers ±259, ±366, ±393, ±500, ±253, ±146, ±119, and −11:−2, 2:11. At block206, the device may cause to send the EHT frame to a first station device using the 80 MHz frequency band. Each 80 MHz segment of a frequency band greater than or equal to 80 MHz, a multi-RU (M-RU) is used comprising a combination of a 52-tone RU and a 26-tone RU. The EHT frame comprises an EHT signaling (EHT-SIG) field, wherein the EHT-SIG field includes a common field that comprises an indication of a number of users in a multi-user multiple-input multiple-output (MU-MIMO) communication. The indication of the number of users in the MU-MIMO communication is encoded using bits17,18, and19of the EHT-SIG field. The indication indicates to station devices that receive the frame to decode the number of users in the MU-MIMO communication using bits17,18, and19of the EHT-SIG field. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. FIG.3shows a functional diagram of an exemplary communication station300, in accordance with one or more example embodiments of the present disclosure. In one embodiment,FIG.3illustrates a functional block diagram of a communication station that may be suitable for use as an AP102(FIG.1) or a user device120(FIG.1) in accordance with some embodiments. The communication station300may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device. The communication station300may include communications circuitry302and a transceiver310for transmitting and receiving signals to and from other communication stations using one or more antennas301. The communications circuitry302may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station300may also include processing circuitry306and memory308arranged to perform the operations described herein. In some embodiments, the communications circuitry302and the processing circuitry306may be configured to perform operations detailed in the above figures, diagrams, and flows. In accordance with some embodiments, the communications circuitry302may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry302may be arranged to transmit and receive signals. The communications circuitry302may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry306of the communication station300may include one or more processors. In other embodiments, two or more antennas301may be coupled to the communications circuitry302arranged for sending and receiving signals. The memory308may store information for configuring the processing circuitry306to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory308may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory308may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media. In some embodiments, the communication station300may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly. In some embodiments, the communication station300may include one or more antennas301. The antennas301may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station. In some embodiments, the communication station300may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen. Although the communication station300is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station300may refer to one or more processes operating on one or more processing elements. Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, the communication station300may include one or more processors and may be configured with instructions stored on a computer-readable storage device. FIG.4illustrates a block diagram of an example of a machine400or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine400may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine400may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine400may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. The machine400may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations. Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating. A module includes hardware. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating. In this example, the execution units may be a member of more than one module. For example, under operation, the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time. The machine (e.g., computer system)400may include a hardware processor402(e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory404and a static memory406, some or all of which may communicate with each other via an interlink (e.g., bus)408. The machine400may further include a power management device432, a graphics display device410, an alphanumeric input device412(e.g., a keyboard), and a user interface (UI) navigation device414(e.g., a mouse). In an example, the graphics display device410, alphanumeric input device412, and UI navigation device414may be a touch screen display. The machine400may additionally include a storage device (i.e., drive unit)416, a signal generation device418(e.g., a speaker), an EHT RU allocation device419, a network interface device/transceiver420coupled to antenna(s)430, and one or more sensors428, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine400may include an output controller434, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)). The operations in accordance with one or more example embodiments of the present disclosure may be carried out by a baseband processor. The baseband processor may be configured to generate corresponding baseband signals. The baseband processor may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with the hardware processor402for generation and processing of the baseband signals and for controlling operations of the main memory404, the storage device416, and/or the EHT RU allocation device419. The baseband processor may be provided on a single radio card, a single chip, or an integrated circuit (IC). The storage device416may include a machine readable medium422on which is stored one or more sets of data structures or instructions424(e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions424may also reside, completely or at least partially, within the main memory404, within the static memory406, or within the hardware processor402during execution thereof by the machine400. In an example, one or any combination of the hardware processor402, the main memory404, the static memory406, or the storage device416may constitute machine-readable media. The EHT RU allocation device419may carry out or perform any of the operations and processes (e.g., process200) described and shown above. It is understood that the above are only a subset of what the EHT RU allocation device419may be configured to perform and that other functions included throughout this disclosure may also be performed by the EHT RU allocation device419. While the machine-readable medium422is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions424. Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc. The term “machine-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine400and that cause the machine400to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media. In an example, a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass. Specific examples of massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The instructions424may further be transmitted or received over a communications network426using a transmission medium via the network interface device/transceiver420utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others. In an example, the network interface device/transceiver420may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network426. In an example, the network interface device/transceiver420may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine400and includes digital or analog communications signals or other intangible media to facilitate communication of such software. The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed. FIG.5is a block diagram of a radio architecture105A,105B in accordance with some embodiments that may be implemented in any one of the example AP102and/or the example STA120ofFIG.1. Radio architecture105A,105B may include radio front-end module (FEM) circuitry504a-b, radio IC circuitry506a-band baseband processing circuitry508a-b. Radio architecture105A,105B as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited. In this disclosure, “WLAN” and “Wi-Fi” are used interchangeably. FEM circuitry504a-bmay include a WLAN or Wi-Fi FEM circuitry504aand a Bluetooth (BT) FEM circuitry504b. The WLAN FEM circuitry504amay include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas501, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry506afor further processing. The BT FEM circuitry504bmay include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas501, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry506bfor further processing. FEM circuitry504amay also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry506afor wireless transmission by one or more of the antennas501. In addition, FEM circuitry504bmay also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry506bfor wireless transmission by the one or more antennas. In the embodiment ofFIG.5, although FEM504aand FEM504bare shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals. Radio IC circuitry506a-bas shown may include WLAN radio IC circuitry506aand BT radio IC circuitry506b. The WLAN radio IC circuitry506amay include a receive signal path which may include circuitry to down-convert WLAN RF signals received from the FEM circuitry504aand provide baseband signals to WLAN baseband processing circuitry508a. BT radio IC circuitry506bmay in turn include a receive signal path which may include circuitry to down-convert BT RF signals received from the FEM circuitry504band provide baseband signals to BT baseband processing circuitry508b. WLAN radio IC circuitry506amay also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry508aand provide WLAN RF output signals to the FEM circuitry504afor subsequent wireless transmission by the one or more antennas501. BT radio IC circuitry506bmay also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry508band provide BT RF output signals to the FEM circuitry504bfor subsequent wireless transmission by the one or more antennas501. In the embodiment ofFIG.5, although radio IC circuitries506aand506bare shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals. Baseband processing circuitry508a-bmay include a WLAN baseband processing circuitry508aand a BT baseband processing circuitry508b. The WLAN baseband processing circuitry508amay include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry508a. Each of the WLAN baseband circuitry508aand the BT baseband circuitry508bmay further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry506a-b, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry506a-b. Each of the baseband processing circuitries508aand508bmay further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with a device for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry506a-b. Referring still toFIG.5, according to the shown embodiment, WLAN-BT coexistence circuitry513may include logic providing an interface between the WLAN baseband circuitry508aand the BT baseband circuitry508bto enable use cases requiring WLAN and BT coexistence. In addition, a switch503may be provided between the WLAN FEM circuitry504aand the BT FEM circuitry504bto allow switching between the WLAN and BT radios according to application needs. In addition, although the antennas501are depicted as being respectively connected to the WLAN FEM circuitry504aand the BT FEM circuitry504b, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM504aor504b. In some embodiments, the front-end module circuitry504a-b, the radio IC circuitry506a-b, and baseband processing circuitry508a-bmay be provided on a single radio card, such as wireless radio card502. In some other embodiments, the one or more antennas501, the FEM circuitry504a-band the radio IC circuitry506a-bmay be provided on a single radio card. In some other embodiments, the radio IC circuitry506a-band the baseband processing circuitry508a-bmay be provided on a single chip or integrated circuit (IC), such as IC512. In some embodiments, the wireless radio card502may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, the radio architecture105A,105B may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel. The OFDM or OFDMA signals may comprise a plurality of orthogonal subcarriers. In some of these multicarrier embodiments, radio architecture105A,105B may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these embodiments, radio architecture105A,105B may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.11 ay and/or 802.11ax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect. Radio architecture105A,105B may also be suitable to transmit and/or receive communications in accordance with other techniques and standards. In some embodiments, the radio architecture105A,105B may be configured for high-efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.11ax standard. In these embodiments, the radio architecture105A,105B may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect. In some other embodiments, the radio architecture105A,105B may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect. In some embodiments, as further shown inFIG.6, the BT baseband circuitry508bmay be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 8.0 or Bluetooth 6.0, or any other iteration of the Bluetooth Standard. In some embodiments, the radio architecture105A,105B may include other radio cards, such as a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE-Advanced or 7G communications). In some IEEE 802.11 embodiments, the radio architecture105A,105B may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160 MHz) (with non-contiguous bandwidths). In some embodiments, a 920 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however. FIG.6illustrates WLAN FEM circuitry504ain accordance with some embodiments. Although the example ofFIG.6is described in conjunction with the WLAN FEM circuitry504a, the example ofFIG.6may be described in conjunction with the example BT FEM circuitry504b(FIG.5), although other circuitry configurations may also be suitable. In some embodiments, the FEM circuitry504amay include a TX/RX switch602to switch between transmit mode and receive mode operation. The FEM circuitry504amay include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry504amay include a low-noise amplifier (LNA)606to amplify received RF signals603and provide the amplified received RF signals607as an output (e.g., to the radio IC circuitry506a-b(FIG.5)). The transmit signal path of the circuitry504amay include a power amplifier (PA) to amplify input RF signals609(e.g., provided by the radio IC circuitry506a-b), and one or more filters612, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals615for subsequent transmission (e.g., by one or more of the antennas501(FIG.5)) via an example duplexer614. In some dual-mode embodiments for Wi-Fi communication, the FEM circuitry504amay be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these embodiments, the receive signal path of the FEM circuitry504amay include a receive signal path duplexer604to separate the signals from each spectrum as well as provide a separate LNA606for each spectrum as shown. In these embodiments, the transmit signal path of the FEM circuitry504amay also include a power amplifier610and a filter612, such as a BPF, an LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer604to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas501(FIG.5). In some embodiments, BT communications may utilize the 2.4 GHz signal paths and may utilize the same FEM circuitry504aas the one used for WLAN communications. FIG.7illustrates radio IC circuitry506ain accordance with some embodiments. The radio IC circuitry506ais one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry506a/506b(FIG.5), although other circuitry configurations may also be suitable. Alternatively, the example ofFIG.7may be described in conjunction with the example BT radio IC circuitry506b. In some embodiments, the radio IC circuitry506amay include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuitry506amay include at least mixer circuitry702, such as, for example, down-conversion mixer circuitry, amplifier circuitry706and filter circuitry708. The transmit signal path of the radio IC circuitry506amay include at least filter circuitry712and mixer circuitry714, such as, for example, up-conversion mixer circuitry. Radio IC circuitry506amay also include synthesizer circuitry704for synthesizing a frequency705for use by the mixer circuitry702and the mixer circuitry714. The mixer circuitry702and/or714may each, according to some embodiments, be configured to provide direct conversion functionality. The latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation.FIG.7illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component. For instance, mixer circuitry714may each include one or more mixers, and filter circuitries708and/or712may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs. For example, when mixer circuitries are of the direct-conversion type, they may each include two or more mixers. In some embodiments, mixer circuitry702may be configured to down-convert RF signals607received from the FEM circuitry504a-b(FIG.5) based on the synthesized frequency705provided by synthesizer circuitry704. The amplifier circuitry706may be configured to amplify the down-converted signals and the filter circuitry708may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals707. Output baseband signals707may be provided to the baseband processing circuitry508a-b(FIG.5) for further processing. In some embodiments, the output baseband signals707may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry702may comprise passive mixers, although the scope of the embodiments is not limited in this respect. In some embodiments, the mixer circuitry714may be configured to up-convert input baseband signals711based on the synthesized frequency705provided by the synthesizer circuitry704to generate RF output signals609for the FEM circuitry504a-b. The baseband signals711may be provided by the baseband processing circuitry508a-band may be filtered by filter circuitry712. The filter circuitry712may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect. In some embodiments, the mixer circuitry702and the mixer circuitry714may each include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively with the help of synthesizer704. In some embodiments, the mixer circuitry702and the mixer circuitry714may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry702and the mixer circuitry714may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry702and the mixer circuitry714may be configured for super-heterodyne operation, although this is not a requirement. Mixer circuitry702may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths). In such an embodiment, RF input signal607fromFIG.7may be down-converted to provide I and Q baseband output signals to be sent to the baseband processor. Quadrature passive mixers may be driven by zero and ninety-degree time-varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as LO frequency705of synthesizer704(FIG.7). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero and ninety-degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect. In some embodiments, the LO signals may differ in duty cycle (the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at an 80% duty cycle, which may result in a significant reduction in power consumption. The RF input signal607(FIG.6) may comprise a balanced signal, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to low-noise amplifier, such as amplifier circuitry706(FIG.7) or to filter circuitry708(FIG.7). In some embodiments, the output baseband signals707and the input baseband signals711may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals707and the input baseband signals711may be digital baseband signals. In these alternate embodiments, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry. In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect. In some embodiments, the synthesizer circuitry704may be a fractional-N synthesizer or a fractional N/N+1 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 circuitry704may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuitry704may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry. In some embodiments, frequency input into synthesizer circuitry704may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. A divider control input may further be provided by either the baseband processing circuitry508a-b(FIG.5) depending on the desired output frequency705. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the example application processor510. The application processor510may include, or otherwise be connected to, one of the example secure signal converter101or the example received signal converter103(e.g., depending on which device the example radio architecture is implemented in). In some embodiments, synthesizer circuitry704may be configured to generate a carrier frequency as the output frequency705, while in other embodiments, the output frequency705may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency705may be a LO frequency (fLO). FIG.8illustrates a functional block diagram of baseband processing circuitry508ain accordance with some embodiments. The baseband processing circuitry508ais one example of circuitry that may be suitable for use as the baseband processing circuitry508a(FIG.5), although other circuitry configurations may also be suitable. Alternatively, the example ofFIG.7may be used to implement the example BT baseband processing circuitry508bofFIG.5. The baseband processing circuitry508amay include a receive baseband processor (RX BBP)802for processing receive baseband signals709provided by the radio IC circuitry506a-b(FIG.5) and a transmit baseband processor (TX BBP)804for generating transmit baseband signals711for the radio IC circuitry506a-b. The baseband processing circuitry508amay also include control logic806for coordinating the operations of the baseband processing circuitry508a. In some embodiments (e.g., when analog baseband signals are exchanged between the baseband processing circuitry508a-band the radio IC circuitry506a-b), the baseband processing circuitry508amay include ADC810to convert analog baseband signals809received from the radio IC circuitry506a-bto digital baseband signals for processing by the RX BBP802. In these embodiments, the baseband processing circuitry508amay also include DAC812to convert digital baseband signals from the TX BBP804to analog baseband signals811. In some embodiments that communicate OFDM signals or OFDMA signals, such as through baseband processor508a, the transmit baseband processor804may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor802may be configured to process received OFDM signals or OFDMA signals by performing an FFT. In some embodiments, the receive baseband processor802may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble. The preambles may be part of a predetermined frame structure for Wi-Fi communication. Referring back toFIG.5, in some embodiments, the antennas501(FIG.5) may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result. Antennas501may each include a set of phased-array antennas, although embodiments are not so limited. Although the radio architecture105A,105B is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary. As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit. As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner. The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards. Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like. Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi-standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like. Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra-wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks. The following examples pertain to further embodiments. Example 1 may include a device comprising processing circuitry coupled to storage, the processing circuitry configured to: utilize a tone plan to generate an extremely high throughput (EHT) frame to be sent using an 80 MHz frequency band, wherein the tone plan comprises a plurality of null tones; encode one or more resource units (RUs) for the EHT frame, wherein the one or more RUs comprise at least one of a 26-tone RU, a 52-tone RU, a 106-tone RU, a 242-tone RU, a 484-tone RU, or a 996-tone RU, wherein the 106-tone RU, the 242-tone RU, and the 484-tone RU comprise null tones located at least at subcarriers ±258, ±257, ±256, ±255, and ±254; and cause to send the EHT frame to a first station device using the 80 MHz frequency band. Example 2 may include the device of example 1 and/or some other example herein, wherein the 996-tone RU comprises null tones located at least at subcarriers at a first range of −11 to −2 and a second range of +2 to +11, with subcarrier increment of 1. Example 3 may include the device of example 1 and/or some other example herein, wherein the 26-tone RU and the 52-tone RU comprise null tones located at least at subcarriers ±258, ±259, ±312, ±313, ±366, ±393, ±446, ±447, ±500, ±200, ±199, ±146, ±119, ±66, ±65, and −11:−2, 2:11. Example 4 may include the device of example 1 and/or some other example herein, wherein the 106-tone RU further comprises null tones located at least at subcarriers ±259, ±366, ±393, ±500, ±253, ±146, ±119, and −11:−2, 2:11. Example 5 may include the device of example 1 and/or some other example herein, wherein each 80 MHz segment of a frequency band greater than or equal to 80 MHz, an multi-RU (M-RU) may be used comprising a combination of a 52-tone RU and a 26-tone RU. Example 6 may include the device of example 1 and/or some other example herein, wherein the EHT frame comprises an EHT signaling (EHT-SIG) field, wherein the EHT-SIG field may include a common field that comprises an indication of a number of users in a multi-user multiple-input multiple-output (MU-MIMO) communication. Example 7 may include the device of example 6 and/or some other example herein, wherein indication of the number of users in the MU-MIMO communication may be encoded using bits17,18, and19of the EHT-SIG field. Example 8 may include the device of example 6 and/or some other example herein, wherein the indication indicates to station devices that receive the frame to decode the number of users in the MU-MIMO communication using bits17,18, and19of the EHT-SIG field. Example 9 may include the device of example 1 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals. Example 10 may include the device of example 4 and/or some other example herein, further comprising an antenna coupled to the transceiver to cause to send the EHT frame. Example 11 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: utilizing a tone plan to generate an extremely high throughput (EHT) frame to be sent using an 80 MHz frequency band, wherein the tone plan comprises a plurality of null tones; encoding one or more resource units (RUs) for the EHT frame, wherein the one or more RUs comprise at least one of a 26-tone RU, a 52-tone RU, a 106-tone RU, a 242-tone RU, a 484-tone RU, or a 996-tone RU, wherein the 106-tone RU, the 242-tone RU, and the 484-tone RU comprise null tones located at least at subcarriers ±258, ±257, ±256, ±255, and ±254; and causing to send the EHT frame to a first station device using the 80 MHz frequency band. Example 12 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the 996-tone RU comprises null tones located at least at subcarriers at a first range of −11 to −2 and a second range of +2 to +11, with subcarrier increment of 1. Example 13 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the 26-tone RU and the 52-tone RU comprise null tones located at least at subcarriers ±258, ±259, ±312, ±313, ±366, ±393, ±446, ±447, ±500, ±200, ±199, ±146, ±119, ±66, ±65, and −11:−2, 2:11. Example 14 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the 106-tone RU further comprises null tones located at least at subcarriers ±259, ±366, ±393, ±500, ±253, ±146, ±119, and −11:−2, 2:11. Example 15 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein each 80 MHz segment of a frequency band greater than or equal to 80 MHz, an multi-RU (M-RU) may be used comprising a combination of a 52-tone RU and a 26-tone RU. Example 16 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the EHT frame comprises an EHT signaling (EHT-SIG) field, wherein the EHT-SIG field may include a common field that comprises an indication of a number of users in a multi-user multiple-input multiple-output (MU-MIMO) communication. Example 17 may include the non-transitory computer-readable medium of example 16 and/or some other example herein, wherein indication of the number of users in the MU-MIMO communication may be encoded using bits17,18, and19of the EHT-SIG field. Example 18 may include the non-transitory computer-readable medium of example 16 and/or some other example herein, wherein the indication indicates to station devices that receive the frame to decode the number of users in the MU-MIMO communication using bits17,18, and19of the EHT-SIG field. Example 19 may include a method comprising: utilizing a tone plan to generate an extremely high throughput (EHT) frame to be sent using an 80 MHz frequency band, wherein the tone plan comprises a plurality of null tones; encoding one or more resource units (RUs) for the EHT frame, wherein the one or more RUs comprise at least one of a 26-tone RU, a 52-tone RU, a 106-tone RU, a 242-tone RU, a 484-tone RU, or a 996-tone RU, wherein the 106-tone RU, the 242-tone RU, and the 484-tone RU comprise null tones located at least at subcarriers ±258, ±257, ±256, ±255, and ±254; and causing to send the EHT frame to a first station device using the 80 MHz frequency band. Example 20 may include the method of example 19 and/or some other example herein, wherein the 996-tone RU comprises null tones located at least at subcarriers at a first range of −11 to −2 and a second range of +2 to +11, with subcarrier increment of 1. Example 21 may include the method of example 19 and/or some other example herein, wherein the 26-tone RU and the 52-tone RU comprise null tones located at least at subcarriers ±258, ±259, ±312, ±313, ±366, ±393, ±446, ±447, ±500, ±200, ±199, ±146, ±119, ±66, ±65, and −11:−2, 2:11. Example 22 may include the method of example 19 and/or some other example herein, wherein the 106-tone RU further comprises null tones located at least at subcarriers ±259, ±366, ±393, ±500, ±253, ±146, ±119, and −11:−2, 2:11. Example 23 may include the method of example 19 and/or some other example herein, wherein each 80 MHz segment of a frequency band greater than or equal to 80 MHz, an multi-RU (M-RU) may be used comprising a combination of a 52-tone RU and a 26-tone RU. Example 24 may include the method of example 19 and/or some other example herein, wherein the EHT frame comprises an EHT signaling (EHT-SIG) field, wherein the EHT-SIG field may include a common field that comprises an indication of a number of users in a multi-user multiple-input multiple-output (MU-MIMO) communication. Example 25 may include the method of example 24 and/or some other example herein, wherein indication of the number of users in the MU-MIMO communication may be encoded using bits17,18, and19of the EHT-SIG field. Example 26 may include the method of example 24 and/or some other example herein, wherein the indication indicates to station devices that receive the frame to decode the number of users in the MU-MIMO communication using bits17,18, and19of the EHT-SIG field. Example 27 may include an apparatus comprising means for: utilizing a tone plan to generate an extremely high throughput (EHT) frame to be sent using an 80 MHz frequency band, wherein the tone plan comprises a plurality of null tones; encoding one or more resource units (RUs) for the EHT frame, wherein the one or more RUs comprise at least one of a 26-tone RU, a 52-tone RU, a 106-tone RU, a 242-tone RU, a 484-tone RU, or a 996-tone RU, wherein the 106-tone RU, the 242-tone RU, and the 484-tone RU comprise null tones located at least at subcarriers ±258, ±257, ±256, ±255, and ±254; and causing to send the EHT frame to a first station device using the 80 MHz frequency band. Example 28 may include the apparatus of example 27 and/or some other example herein, wherein the 996-tone RU comprises null tones located at least at subcarriers at a first range of −11 to −2 and a second range of +2 to +11, with subcarrier increment of 1. Example 29 may include the apparatus of example 27 and/or some other example herein, wherein the 26-tone RU and the 52-tone RU comprise null tones located at least at subcarriers ±258, ±259, ±312, ±313, ±366, ±393, ±446, ±447, ±500, ±200, ±199, ±146, ±119, ±66, ±65, and −11:−2, 2:11. Example 30 may include the apparatus of example 27 and/or some other example herein, wherein the 106-tone RU further comprises null tones located at least at subcarriers ±259, ±366, ±393, ±500, ±253, ±146, ±119, and −11:−2, 2:11. Example 31 may include the apparatus of example 27 and/or some other example herein, wherein each 80 MHz segment of a frequency band greater than or equal to 80 MHz, an multi-RU (M-RU) may be used comprising a combination of a 52-tone RU and a 26-tone RU. Example 32 may include the apparatus of example 27 and/or some other example herein, wherein the EHT frame comprises an EHT signaling (EHT-SIG) field, wherein the EHT-SIG field may include a common field that comprises an indication of a number of users in a multi-user multiple-input multiple-output (MU-MIMO) communication. Example 33 may include the apparatus of example 32 and/or some other example herein, wherein indication of the number of users in the MU-MIMO communication may be encoded using bits17,18, and19of the EHT-SIG field. Example 34 may include the apparatus of example 32 and/or some other example herein, wherein the indication indicates to station devices that receive the frame to decode the number of users in the MU-MIMO communication using bits17,18, and19of the EHT-SIG field. Example 35 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-34, or any other method or process described herein Example 36 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-34, or any other method or process described herein. Example 37 may include a method, technique, or process as described in or related to any of examples 1-34, or portions or parts thereof. Example 38 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-34, or portions thereof. Example 39 may include a method of communicating in a wireless network as shown and described herein. Example 40 may include a system for providing wireless communication as shown and described herein. Example 41 may include a device for providing wireless communication as shown and described herein. Embodiments according to the invention are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject-matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims. 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. Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations. These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks. Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation. Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. | 83,530 |
11943755 | DETAILED DESCRIPTION Described herein are apparatuses and methods for monitoring network health, including in particular, the health of an access point (AP). The health may be determined and presented as a graphic metric that quickly and usefully informs (at a glance) a network operator (e.g., administer, WISP provider, etc.) of other provider servicing a network, information about the overall and specific efficiency of the network (e.g., AP). For example, described herein are systems and methods for preparing and displaying a metric, including graphical metrics, of the health of the network. A system may include, for example, non-transitory computer-readable storage medium storing a set of instructions capable of being executed by a processor that cause the processor to present the metrics described. In general, the metrics described herein present a selected and relevant subset of information from the network that is most relevant to overall health as may be required by a network operator. This information is generally determined in a periodic basis and updated, and may include or incorporate both the most recent (e.g., within the last few seconds to minutes) as well as recent historical information (e.g., from the previous minutes, hours, days, weeks, months, etc.). Part I: Devices (e.g., CPE) Network Ranking As mentioned, the overall network (or partial network) health, including in particular the health of one more access point of a network, may be monitored by providing information to/from each (e.g., all or most) of the stations communicating with the access point within a predetermined period of time (e.g., hours, days, weeks, months, years) and using a sub-set of these stations (e.g., the “top” stations) to present with information about their impact on the network/access point. Generally, the information used to determine these metrics may be monitored at the access point and at the station and exchanged between them. This information may be stored and otherwise manipulated to determine estimates for overall efficiency of each station as well as actual usage information. In general, this information may include the most recent time period/interval (e.g., sample period of 30 seconds) and/or it may include (or may not include) historical information, which may be weighted so that current data is either emphasized or de-emphasized. Also, in any of the variations described herein the efficiency and activity time for each station may be empirically determined and/or may be compared with ideal or projected information, based on equipment speculations, For example, in general, the transmit air-time of a packet between each station and access point may be tracked. This is the actual air-time used by a packet, including all retries. This is calculated after the transmission is complete. For each packet, the following may be used: Total packet transmit duration: Dt; Duration of failed attempts: Df; Duration of successful attempts: Ds. In general, Dt=Df+Ds. An example Merlin and WASP (Qualcomm Atheros Wifi chipsets) code is shown inFIG.3, that returns the actual transmit duration and also returns the duration of the successful attempt (which can be 0 for a total failure), and the total duration of the failed attempts. Per-STA TX packet air-time and error-rate accounting may also be determined between access point and each station. This may be done using simple accumulate and average mechanism. For example, Dt value for the packet may be accumulated on a per-STA basis into a “totalaccumairtime” variable. This may be done over time ‘Ai’ which is the averaging interval. Similarly, the Df and Ds values may be accumulated on a per-STA basis (totalaccumfail and totalaccumsucc). Once we have accumulated for more than Ai amount of time, i.e., elapsed duration De>Ai, the airtime-usage percentage for the current elapsed period may be calculated, e.g., as follows: airtime=(totalaccumairtime*100)/De. Similarly, the packet error rate for the current elapsed period may be computed as: per=(totalaccumfail*100)/(totalaccumsucc+totalaccumfail). Note that this automatically adds more weight to the packets that are longer in duration as compared to simply counting successful and failed attempts. The airtime and PER for the current elapsed period may then be added, into an average. In one example, using exponential average: avg_airtime=(avg_airtime+airtime)/2 avg_per=(avg_per+per)/2. After the averaging, accumulation variables may be reset: totalaccumairtime=totalaccumfail=totalaccumsucc=0. The procedure for accumulation-reset may also need to be called when a remote (e.g., cloud) agent accesses these values to construct a heartbeat if there were no further transmissions to the STA that causes the accounting function to execute. Example Merlin and WASP code is shown inFIGS.4Aand B, showing an exemplary function (_do_sta_packet_accounting) that accounts for the airtime used by each packet, and a function (_do_sta_tx_stats_refresh) that resets the accumulation after an elapsed interval and does the averaging. For example, _do_sta_packet_accounting may generally be called only during a TXDONE operation. But in the event where there were some transmissions to the station and none after that, the _do_sta_tx_stats_refresh function must be invoked at the time when the cloud agent sends the heartbeat. The downlink and uplink airtimes may also be determined. For example, on an AP, the routines described above will account for the ‘DOWLINK’ portion of the airtime and packet-error-rate for each station. On the STA, the routines will account for the ‘UPLINK’ portion of the airTime and packet-error-rate for the STA->AP direction. Polling protocol modifications are required for AP and STA to communicate these values to each other so that total airTime can be determined As mentioned, polling protocol modifications may be made. As part of the polling protocol in the poll response packet's statistics section (sent by the station) a system may communicate the station's airtime and packet-error-rate to the AP. The statistics portion may typically already contain the current rate-control's PHY rate in Kbps and the max possible PHY rate according to chain-mask. For example, in some systems the AP already evaluates the statistics of each STA. As part of that process, the AP updates the stations TX airtime and per into corresponding RX fields. For example, sta->rx_airtime_avg and sta->rx_per_avg. In the same way, as part of the poll request packet's statistics section (sent by the AP), a system may communicate the station's TX airtime and packet-error-rate to the STA. The STA may also update the TX airtime and PER into corresponding TX fields. In general, downlink/uplink isolated capacity may be determined. For example, ISOLATED_CAPACITY may be determined as ISOLATED_CAPACITY=(PHYRATE*MAC_EFFICIENCY_PERCENT*(100−PER))/10000. Since we may have PHYRATE and PER in both directions we will have two separate values Downlink-Isolated-Capacity and Uplink-Isolated-Capacity. MAC_EFFICIENCY_PERCENT may be a system based constant. For example, in an 802.11ac system, 75% may be used and/or may be empirically determined. In other words, these values may indicate potential throughput if the station were using the network alone (i.e., isolated). This value may be confirmed to confirm that a Subscriber is not RF limited, i.e., the operator may oversubscribe his AP but the RF characteristics may be fine, and in this case the actual throughput may be lower, but it is not lower because of RF for which he may need to take some action. Total airtime and isolated capacity may be determined. The TOTAL_AIRTIME may be the sum of DOWNLINK and UPLINK airtimes. The TOTAL_ISOLATED_CAPACITY is typically the average of DOWNLINK and UPLINK isolated capacity. As mentioned above, in general, the methods and systems described herein may be operated, refreshed and/or updated during a remote (e.g., cloud) agent “heartbeat”. In general the heartbeat is the transmission of operational parameters from the stations and/or AP to a remote site (e.g., a cloud server or the like) and/or to the AP or another AP. This heartbeat is transmitted at regular intervals, such as every 30 seconds (or any other appropriate time period). The cloud heartbeat may communicate the average-airtime (both directions), average-per, phy-rate, max-phy-rate, downlink-capacity, uplink-capacity to the cloud. Computations may be performed remotely, including on the cloud. On the cloud, the following computations may be done at each heartbeat (in addition to storing the current heartbeat values into storage): IF HEARTBEATS_SINCE_RESET > WINDOW_SIZE THENACTIVE_AIRTIME_COUNTER /= 2ACTIVE_AIRTIME_ACCUMULATION /= 2HEARTBEATS_SINCE_RESET = 0ENDIFIF TOTAL_AIRTIME > Y THENACTIVE_AIRTIME_ACCUMULATION += TOTAL_AIRTIMEACTIVE_AIRTIME_COUNTER++AVG_ACTIVE_AIRTIME = (AVG_ACTIVE_AIRTIME +TOTAL_AIRTIME)/2ENDIFHEARTBEATS_SINCE_RESET++ WINDOW_SIZE may be defined based on the normal heartbeat interval to prevent any overflows. For a 30-second heartbeat, there will be 2880 heartbeats in a 24-hour window. Hence WINDOW_SIZE can be defined as 2880. The above code accumulates the periods of air-time when the station's activity was greater than Y. Y should ideally be defined as the 100/NUMBER_OF_STATIONS_ON_CONNECTED_AP. So for an AP with 50 stations, Y would be 2% for fair-sharing the network. And in such a case we accumulate airtimes for times-when the usage is above the 2%. The Accumulation is reset by half after we cross the window-size. This will essentially use ½ weight for past data. Station efficiency may also be estimated or calculated. For example, the efficiency of the STATION is computed by a simple ratio of its total isolated capacity to the AP_MAX_CAPACITY as a percent: STA_EFFICIENCY=(TOTAL_ISOLATED_CAPACITY*100)/AP_MAX_CAPACITY Where: AP_MAX_CAPACITY=(MAX_PHY_RATE_OF_AP*MAC_EFFICIENCY_PERCENT)/100 As mentioned above, when preparing to determine the visual display (and the analysis of network/AP health), the “top” users may be determined. In some variations these top users may be determined on the cloud. For a given AP, the method (or a processor, including a remote or “cloud” server) may get a station list, listing all of the stations communicating with the AP during the predetermined time interval (e.g., hours, days, weeks, months, etc.). For each station, the system (or method) may compute a Usage-Index (“Ui”) as follows: Ui=ACTIVE_AIRTIME_ACCUMULATION/ACTIVE_AIRTIME_COUNTER The stations may then be sorted as follows: (1) by HIGHER Ui value; (2) if two stations have the same Ui value, sort by LOWER TOTAL_ISOLATED_CAPACITY. From this sorted list selected the first N. This will be the TOP-N users over the last 24 hours. The ‘TOPNESS’ is not necessarily according to just airTime, but also according to lower-capacity and airTime, and by clients that are bursty. For example, n may be 10 (though any appropriate number may be chosen). Graphical Display In preparing a display, the method or system may present a “TDMA window” graph, as shown inFIG.1. In this example, the image is formed by sorting the TOP-N stations determined above by the STA_EFFICIENCY in descending order. The AVG_ACTIVE_AIRTIME value is used for the horizontal axis, and the STA_EFFICIENCY for the vertical axis. The maximum value for the vertical axis is the AP's maximum possible capacity value=AP_MAX_CAPACITY. InFIG.1, the maximum value of the horizontal axis is the SUM_OF_TOP_N(AVG_ACT_AIRTIME) value. The AP efficiency may be immediately and intuitively determined fromFIG.1based on the overall amount of shading102. For example, the efficiency of the AP can be considered as the area of this shaded102(colored) area, compared with the unshaded105region. InFIG.1, each station may be uniquely identified by a color; the stations may also be labeled or identified when clicking on or “mouseing over” the shaded region corresponding to the station. As a consequence of the technique/system described above, only the TOP-N stations selected above are considered in determining the efficiency of the AP. Thus: AIRTIME_SUM=SUM_OF_TOP_N(AVG_ACT_AIRTIME) WEIGHTED_AIRTIME_EFF=SUM_OF_TOP_N(AVG_ACT_AIRTIME*STA_EFFICIENCY) AP_EFFICIENCY=(WEIGHTED_AIRTIME_EFF*100)/(AIRTIME_SUM*AP_MAX_CAPACITY) As mentioned above, any appropriate graphical presentation or technique may be used to display this information. For example,FIG.2illustrates another graphical depiction of the network health, in which a radial axis is used. In this example, the AVG_ACTIVE_AIRTIME value is shown as the angular distance (portion of the circle), while the STA_EFFICIENCY is shown for the radius of each segment of the circle corresponding to the individual stations (ranked by top stations). AP efficiency may be immediately and intuitively determined fromFIG.2, as above forFIG.1, based on the overall amount of shading202compared to non-shaded regions205. Estimating and Displaying Error Vector Magnitude Any of the systems described herein may generate a histogram and/or constellation diagram based on the Error Vector Magnitude (EVM). An EVM, sometimes also called receive constellation error or RCE, is traditionally a measure used to quantify the performance of a digital radio transmitter and/or receiver. As described above, a signal sent by an ideal transmitter or received by a receiver would have all constellation points precisely at the ideal locations (depending on the modulation type), however imperfections such as carrier leakage, low image rejection ratio, phase noise etc., may cause the actual constellation points to deviate from these ideal locations. EVM may be thought of as a measure of how far the points are from the ideal locations. Noise, distortion, spurious signals, and phase noise all degrade EVM, and therefore EVM provides a measure of the quality of the radio receiver or transmitter for use in digital communications. Although traditionally transmitter EVM is measured by specialized equipment, which demodulates the received signal in a similar way to how a real radio demodulator does it, it would be helpful to provide a measure of EVM (and graphical presentation of EVM) that may be quickly and easily determined and displayed during normal operation of a radio (transmitter and/or receiver). An error vector is a vector in the I-Q plane between the ideal constellation point and the point received by the receiver. In other words, it is the difference between actual received symbols and ideal symbols. The EVM may be thought of as the average power of the error vector, normalized to signal power. For the percentage format, root mean square (RMS) average may be used. The EVM may be equal to the ratio of the power of the error vector to the root mean square (RMS) power of the reference. EVM, as conventionally defined for single carrier modulations, is a ratio of a mean power to a peak power. Because the relationship between the peak and mean signal power is dependent on constellation geometry, different constellation types (e.g., 16-QAM and 64-QAM), subject to the same mean level of interference, will report different EVM values. EVM, as defined for multi carrier modulations, may be a ratio of two mean powers regardless of the constellation geometry. In this form, EVM is related to Modulation error ratio, the ratio of mean signal power to mean error power. As used herein, carrier to interference noise ratio (CINR) is an excellent proxy for EVM. For example, in implementation, sounding packets specific to two or more known (predetermined) modulation types may be transmitted and received between devices (e.g., between AP and CPE). The receiving hardware may detect the received packet, and analyze the descriptors in the packet to determine an estimate for EVM based on the carrier to interference noise ratio. For example, the hardware may detect a particular sounding packet (corresponding to a particular modulation type), and may analyze descriptors from the packet, and this info may be is embedded in an EVM signal that is reported for concurrent (immediate or slightly delayed) or later (historical) display, e.g., as a histogram and/or constellation diagram. This determination of EVM (using predetermined sounding packets) may be performed by all or some of the radios in the network (e.g., and may be designed and/or built-in to the chipset of the radio). The EVM determined in this way (and described in more detail below) may provide an approximate estimate of the EVM for the connection between devices, and may be displayed/presented or used as an indication of the transmission quality, which may be measured by the device that demodulates the signal and calculates the noise. For example, the EVM that the device reports (e.g., and this report may be made to a node, such as an AP and/or may be transmitted to a remote location, such as a server), may be more of than just SNR information. The EVM may make use of pilot signals embedded in the packet; the device(s) typically detect the pilot (sounding) signal and know what it should be, and may then calculate the SNR of the pilot signal. This may be reported as the EVM (e.g., CINR, or carrier to interference noise ratio). As mentioned above, the EVM estimates (EVM) measured over a period of time as described herein may be shown using a histogram. For example, an EVM measurement may be determined between a two (or in some cases more) devices for each sounding packet or set of sounding packets (where a set may correspond to a complete set of predetermined modulation types, e.g., MCS 3, 5, and 8, in reference to the table ofFIG.10, described below, in which MCS 3 corresponds to modulation type and coding rate BPSK, MCS 5 is 64 QAM, and MCS 8 is 256 QAM. For example, a histogram may take 64 samples of measured EVM and use them to display histogram (CINR histogram or EVM histogram) that visually shows the EVM (based on this window of time needed to accumulate the 64 samples). As will be illustrated below, these histograms, which aggregate the estimated/approximated EVM based on sounding packets for two or more (e.g., three or more, e.g., four or more) modulation-specific sounding packets, for a window of time corresponding to x received EVM estimates. E.g., the histogram for CINR (estimated EVM) may indicate that the link has better than 20 dB CINR/EVM, but also indicates a cluster near the low 10-20 dB range. As mentioned, in general, the use of these modulation type-specific sounding packets may allow estimation of EVM. Because of this, the estimated EVMs described herein may also be referred to as SNR at the receiver, which may include distortion in the transmitter in the transmitted signal, and may also include thermal noise at receiver and interference channel. Although it may be desirable to eliminate the transmission distortion (depending on the MCS that was transmitted), in general, different MCS (modulations) transmit with different distortions, because of a tradeoff in power and mode. Transmitting at lower power may result in clearer transmission for high QAM (less distortion). For example, a device (e.g., an AP) may periodically send test packets (sounding packets) at different MCS rates for the clients measuring the EVM, and vice-versa. These test (sounding) packets are typically not data packets. When a sounding packet is received by the device (e.g., AP) from another device (e.g., a CPE), the first device may receive it and/or broadcast it (or the information received from it. As mentioned, the sounding packets may cycle through all or a subset of the different modes used between the devices. See, e.g.,FIG.10. For example, in some variations, three modulations are use (e.g., BPSK, 64 QAM and 256 QAM). If a packet is sent at high MCS (e.g., 256 QAM), a relatively high SNR may be needed in the link for the receiver to receive it. If the devices in the link are too far apart, for example, the receiver may not be able to receive it, though a lower MCS may be needed to receive e.g., BPSK. However, as mentioned, at this low MCS, the packets may be heavily distorted. For example when transmitting at BPSK, the packet may never be received at an EVM in excess of 15 dB; there may be lots of noise coming from the transmitter. Thus in general, BPSK may be transmitted at high power and allow more distortion. The system(s) may deliberately allow transmission to be distorted at the transmitter to get high transmission power, as a tradeoff between the MCS rate and the EVM that the system estimates. In practice, in some variations only a subset of the possible modulations (MCS) may be measured for the purposes of measuring EVM (CIPC) as described herein. For example, three MCS types may be used. Examples of exemplary EVM packets (e.g., sounding packets/EVM measure requests and EVM reports) are shown inFIGS.11A and11B. For example, a sounding packet may include a normal preamble and then may have basic information in the MAC layer (e.g., MAC ID of the device sending the packet, and ID to the MCS, and identify the MAC layer that also identifies that it's a sounding, e.g., test, packet). An EVM sounding packet may be communicated at regular intervals (e.g., every 5 sec) and the device may determine from the sounding packets an estimate of CINR (which may be used to estimate EVM). As will be described in greater detail below, this estimate may be displayed, e.g., in a user interface as either or both a histogram or as an estimate of a constellation diagram. This display me be static/average, or it may be dynamic (and updated periodically). In some variation the display, and in particular, the displayed constellation diagram, does not show actual measured points, but an approximation of these points based on the statistical distribution of the values for the estimated EVM. Thus, the actual point location on the constellation diagram may be a pseudo-representation of the actual point, so that the actual position of the points on the constellation diagram (relative to the ideal locations) is false, but the overall distribution of points is accurate. Thus, the general impression (familiar look and feel) provided by the constellation diagram is correct, even if the specific locations of the points are estimated. The use of the histogram to display estimate EVM (e.g., CINR) may be particularly helpful as interference may be transient. These histograms may be shown with (e.g., alongside) a constellation diagram. Either or both the histogram and constellation diagram may be displayed as (showing the I and Q components) as an animation. As mentioned, the constellation diagram may be a dynamic recreation of what a more precise EVM testing equipment would show, using pseudo-locations for EVM based on the estimates provided by the sounding packets. Thus, the user interface (UI) may create a real-time animation displaying the estimated EVM. In general, a connection between two or more devices (radio devices) forming a link may estimate EVM and this information may be displayed as one or more constellation diagram and/or histogram. For example, each device forming the link may send sounding packets to seatmate EVM (CINR). Sounding packets maybe sent at particular MCSs to measure the range of EMVs. For example, an AP may broadcast the sounding packets to one or more CPE; the CPE may transmit sounding packets (and information gleamed from the received sounding packets) to the AP. The information received and/or determined from the sounding packets may be held locally (e.g., at the AP) and accessed from the AP directly, and/or transmitted to a remote site (e.g., a cloud location) that may be remotely accessed. The devices and/or the system may use the statistics from the EVM estimates based on the sounding packets to build an EVM histogram and/or constellation diagram. Because the method uses “standard” sounding packets, the result is a reliable indicator, because it does not report raw (e.g., I and Q) samples. Instead, the devices/system may use statistics provided by the radio. The sounding packets chosen may be selected to span the range (dB) of EVM for the link(s), and thus the sounding packets chosen may be used to determine a minimum number to span the entire EVM range. For example, a BPSK sounding packet may only measure/reflect a range of 0-10 dB, and may not measure outside of this range because BPSK is inherently distortive. If a sounding packet is based on 16 QAM, the range may be good from 0-20 dB, but the sounding packet may not be heard by all of the clients (e.g., if transmitting by AP). In practice, the analysis (e.g., at an AP) may use the “best” sounding packet from the set of MSC packets; typically the highest MCS sounding packet that was able to receive for a link. The CINR may include the transmission distortion, which may be loudest in low MCS packets. The transmission distortion may mask the SNR. As will be described in more detail below, a user interface may data (histogram and/or constellation diagrams) for one or more links or ends of the link. For example, a user logging into a user interface may be presented with the histogram and/or constellation diagram for the EVM (CINR) at the access point; however the user may select displays of one or more CPEs that a particular AP is communicating with. Additional information, such as link capacity, signal to noise ratio, remote and/or local signal strength, thermal noise, etc., may also or alternatively be shown, on the same, or a different, screen. FIGS.5-6and9A-9Cillustrate examples of histograms of EVM (CINR). In these examples, the histogram looks at the frequency distribution of different EVMs. This distribution in this example is a rolling window of (e.g., 64) different values of EVMs reported by the device(s). For example, a sounding packet may be received at predetermined intervals, e.g., every 5 seconds. Thus, the histogram and/or constellation diagram may update every time a new sounding packet (or new set of sounding packets spanning the set of MSCs examined) is received. For example, a histogram may update every 5 sec, when a new sample in the sliding window of 64 samples is generated. If the device/system does not receive a test packet, it may assume that there is interference at that MCS. When a full set of test packet includes 3 MSCs (e.g., BPSK, 16 QAM, 256 QAM), the device/system may determine that there are 3 types of test packets transmitted as different MCSs, and if they do not receive one, it may assume that thee was interference; when it does not receive the packet, the device/system may update it as a 0 dB EVM (minimum possible EVM). The device/system typically keeps track of the sequence number and determines if one or more packets was not received, and uses this information to estimate/determine the EVM. Thus this information may be used as interference metric, which may be particularly helpful in detecting and/or indicating transient interference. For example, three MSC types of sounding packets may be used (e.g., a BPSK sounding packet reflecting the 0-10 dB range, a 64 QAM packet reflecting the 0-15 dB range, and a 256 QAM packet reflecting the Odb-30 dB range). The apparatus/system may use the information for the highest modulation used. For example, if the apparatus/system receives the 256 QAM packet, it may use only this member of the set (rather than the BPSK or 64 QAM packets), assuming that this most accurately reflects the CINR (e.g., the other packets may be discarded). For example, if they get the 64 QAM packet, it may use just the 64 QAM packet (as the frequency number for the packet is typically known). In some variations, multiple histograms may be generated based on the different sounding packets (e.g., different MCSs). For example, where three modulation types are used, three histograms may be generated; the CINR between them may change due to interference. The system may choose the appropriate MCS level based on the range, e.g., the distance between the ends of the link (e.g., between the AP and CPE). This may be accomplished over time by looking at the best MCS (sounding packet) that is consistently received. For example,FIG.5schematically illustrates on example of a histogram (top) and constellation diagram for a single stream of one link.FIG.10illustrates exemplary parameters and variables that may be used in estimating the EVM/CINR and generating the histogram and/or constellation diagram. InFIG.5, the constellation diagram shows an approximated (pseudo-valued) distribution of EVM points (solid dots) around ideal locations (circles) for each of the 16 locations in a 16 QAM modulation. An EVM histogram (which may also be referred to as a CINR histogram) may be generated for each end of a link. For example, the firmware/hardware (e.g., driver) of a radio apparatus may be configured to provide a block of EVM samples (“EVM_samples”) that are obtained as described above, e.g., from received packet descriptors corresponding to special EVM measurement packets (sounding packets). In one example, the block length of the EVM samples is NUM_EVM_SAMP (with default value of 64). The histogram may be generated by first generating EVM_hist[NUM_EVM_BINS] which represents the histogram of EVM values measured. More precisely: EVM_hist[i_EVM_bin] may correspond to the number of occurrences of the EVM values MIN_EVM+(i_EVM_bin-1)*DEL_EVM in the samples set EVM_samples. The EVM histogram may be plotted as shown inFIG.6, where probabilities are represented by different shades (which may be displayed in color shades). We show NUM_EVM_BINS number of patches where the color of the i_evm_bin-th patch is given by the index evm_hist_idx(i_evm_bin), computed as follows:Percent (%) convert to probability: EVM_prob=EVM_hist/NUM_EVM_SAMPPercent (%) compute evm_hist_idx: evm_hist_idx=place_in_bins(EVM_prob, NUM_PRB_BINS,MIN_PRB,DEL_PRB) FIG.15illustrates one example of a method (shows as Matlab code) that may be used to calculate bin placement (e.g., “place_in_bins”). The estimate EMV information (CIRM) may also be used to generate a constellation diagram, as illustrated inFIGS.5and7-8. As mentioned above, this constellation diagram may be a pseudo-EVM constellation diagram, because the EVM is not directly measured, but is instead shown on the constellation diagram based on statistical approximations that may accurately reflect the distribution of EVM values, but not actual measured EVM values. The ability to rapidly and accurately generate estimated constellation diagrams in this manner is advantageous, because these plots, which may be familiar to those using traditional constellation diagrams, may be generated without requiring rigorously generated EVM values (e.g., using dedicated systems necessary to correctly measure EVM). For example, a single frame of a constellation diagram is shown inFIG.5and also inFIG.7. As mentioned, the constellation diagram may be an animation, which may be updated at actual update rates (e.g., refreshing as new estimated EVM/CINR is determined), or it may be updated/animated/refreshed more often, by generating new pseudo-EVM points using the same distribution information, as described herein. InFIG.7, the constellation diagram includes: “clean” constellation points shown as open circles (representing the ideal values), and “clouds” of noisy samples associated to each constellation point, shown as solid dots.FIG.8shows a close-up of a single constellation point and its associated noisy sample cloud. The distribution cloud points may be generated as described below, from the estimated EVM (CINR) data. For example, the x,y coordinates of the j-th constellation point may be given by:x_pts(j): x-coordinate of the j-th constellation pointy_pts(j): y-coordinate of the j-th constellation point A total of NUM_NZY_SAMPS noisy samples may be plotted around each constellation point. In the above examples, NUM_NZY_SAMPS=7. For the j-th constellation point, NUM_NZY_SAMPS noisy samples may be plotted, which form a “cloud” around it. The x,y coordinate of i-th point in this cloud may be given by:x_cld_j(i): x-coordinate of the i-th noisy sample cloud pointy_cld_j(i): y-coordinate of the i-th noisy sample cloud point Example of one variation of a method for computing these values are shown below and exemplary code for performing these methods is shown inFIGS.12-15. For example, the standard deviation of the noise samples may be determined. The standard deviation of noise samples, sigma, may be given by: sigma_average=sqrt(½)*[10{circumflex over ( )}(EVM_samples[i_samp]/20) If computing power of 10 is computationally intensive, a look up table may be used. Exemplary code for this is provided inFIG.12, showing exemplary Matlab code (though other code performing similar or equivalent functions may be used, as is generally true for the exemplary code provided herein), described as “look_up_sigma,” for converting a single estimated EVM value into a single sigma value. Using such a function it is possible to calculate: sigma_average=look_up_sigma(pilot_EVM[1]) Clean constellation points may be generated (QAM constellation points) for each type of modulation. These points may be stored and looked up. For example, exemplary Matlab code is provided inFIGS.13A-C(lookup_qam_constellation). In this example, vectors of x and y coordinates of the constellation points may be given by: [x_pts,y_pts]=lookup_qam_constellation(mod_type) In the constellation diagram, both “clean” constellation points and clouds of noisy sample corresponding to each constellation point are shown. Each of these “clouds” of points representing the distribution of EVM values may include NUM_NZY_SAMPS number of noise samples. For example, noisy samples (in x and y coordinates) may be generated as follows: x_nze_j=sigma*get_gaussian_noise_samples(NUM_NZY_SAMPS); y_nze_j=sigma*get_gaussian_noise_samples(NUM_NZY_SAMPS); An example of a method (encoded as Matlab code) for generating these coordinates is illustrated inFIGS.14A-C(“get_gaussian_noise_samples”). The noise samples may be added to the constellation points to generate the “noise sample cloud”. For example, for the j-th constellation point samples may be estimated as: x_cld_j=x_pts(j)+x_nze y_cld_j=y_pts(j)+y_nze FIGS.9A to9Cshow examples of user interfaces that may include pseudo-EVM information in the display, including constellation plots and/or histograms, as well as (in some variations) additional information about the connectivity of a device (or between the device and one or more other devices). For example, inFIG.9A, the user interface includes a series of panels or regions (“device”, “wireless” and “RF environment”) describing the status of one or more devices in a network. In this example, the device is described as an exemplary radio (transmitter/receiver), corresponding to a model no. “Rocket 5AC PTP”. This device is configured as an access point, and the device tab provides characteristic information, including model, device name, version, network mode, memory, CPU, cable length, cable SNR, airtime, LAN speed, date and uptime. More or less such information may be included. In some variations the device may be selected from a menu of available devices, which may include other (connected) devices. In general this user interface may be accessed either directly, e.g., by connecting to a device such as the AP via a plug, cord or local wireless (e.g., Bluetooth, etc.) connection, or indirectly, via a connection to a remote server (e.g., cloud server) that communicates with the device and/or aggregates the information from the device. InFIG.9A, the middle region (tab) may include information specific to the wireless system for the particular device, such as the wireless mode (e.g., access point, CPE, etc.), SSID, MAC identification information, security, distance of link, frequency, channel width, signal, transmission rate, receive rate, etc. This information may be specific to a particular link or more than one link; thus, for example, an access point may communicate with multiple other devices (CPEs, etc.), and a user may toggle between these different links, or the information may be generic to all of the links. The user interface (including the wireless display portion) may include a graphical illustration of the capacity of the link throughput, as shown inFIG.9Ain the middle right. The graph shown indicates a running (showing the time axis) value of the capacity of the link. The bottom region of the user interface shown inFIG.9Aindicates the properties of the RF environment, including a pair of constellation diagrams (local and remote) as discussed herein, and EVM (or CINR) histograms adjacent to the constellation diagrams. In this example, the RF environment also shows a running (time axis) view of the signal to noise ratio of the connection, inFIG.9Athe local SNR values are shown (though the remote values may be selected for display, as shown inFIG.9C). In the examples shown inFIG.9A-9C, the local device may refer to the device that you are logged into (e.g., when connected either remotely or directly), while the remote device typically refers to the other device in the particular link you are observing. For example, inFIG.9B, the signal to noise ratio illustration on the bottom right may be at least partially determined from the EVM data, and also shows the noise floor (thermal noise floor) between the two devices. The signal level may be visualized as the gap between the signal (top trace) and the interference+noise (middle) traces. The lower trace is the thermal noise floor. Large SNR is visualized by the gap between the signal and interference+noise traces. The constellation diagrams shown inFIGS.9A-9Cmay be regularly updated (e.g., animated) either as fast or faster than the actual EVM data is transmitted between the link. This is because the pseudo-EVM data may be graphed by re-calculating new coordinates for the cloud of EVM points around the ideal points in the constellation plots. For example, the plots may be updated approximately 10× per minute or more often (e.g., 10× second, etc.). InFIGS.9A-9C, the local constellation diagram is shown as a 16 QAM constellation (having 16 ideal points) for local reception, while the remote constellation diagram is a 256 QAM diagram. In any of the examples described herein, the user interface may include a display of colored symbols, shapes (e.g., boxes), etc., representing the values for the various devices in the device list, and may also indicate device detail in a panel that will help communicate to the user where inefficiencies lie. In some variations, this information will be associated with a particularly access point (AP). For example, displayed colored boxes may represent the top number (e.g., top 10) airtime clients in the list, and the user interface may also show additional (e.g., the top 20) airtime clients in the detail view. Additional information provided by the detail view may include information about the parameters specific to the station (e.g., CPE) represented by the box, wedge or other representation of the value of the station. For example, the detail view may allow hovering over representation (e.g., box) for a quick tooltip, and highlighting the offending device in a list below. In some variations the detailed list view may also include a number in front to communicate total number of devices, and a percentage of efficiency. The list user interface (e.g., the list view) may have a tooltip, e.g., at the top of the column, to quickly explain what TDMA is. The detailed information (e.g., list view) may also be sortable by TDMA (and other capacity values), e.g., in this column, so efficient or inefficient devices can be shown more quickly, e.g. by bringing them to the top. In any of the variations described herein, the TDMA may be calculated for past time (historically, e.g., the past 24 hours), rather than (or in addition to) real-time. In the examples described herein, the X axis communicates time, proportionally, and the Y axis communicates throughput. Colors may also be used to indicate the quality (“goodness”) for individual stations. For example, good clients (e.g., top 33%) may be colored green, mediocre clients may be colored orange (middle 33%), and bad/inefficient clients may be colored red (bottom 33%). The remaining areas may be greyed out. EXAMPLE The techniques described herein typically relate to time division multiple access (TDMA). TDMA may refer to a channel access method for shared medium networks that allows several users to share the same frequency channel by dividing the signal into different time slots. For example, users may transmit in rapid succession, one after the other, each using its own time slot. This may allow multiple stations to share the same transmission medium (e.g. radio frequency channel) while using only a part of the channel capacity. As a simplified example, if TDMA were a party, and there were three guests, Alice, Bob, and Carol talking to the host, each guest may share time talking with the host. For example, for the first 10 seconds, Alice may talk to the host, for the next 10 seconds, its Bob's turn to talk to the host, for the next 10 seconds, its Carol's turn to talk to the host, then for the next 10 seconds, back to Alice, then Bob, and so on. Thus, the frequency-range that is being used may be divided into time-slots, and each user assigned a specific time-slot; users can only send/receive data in their own time-slot. The system may also be configured so that users (devices) may forfeit their time slot (e.g., by analogy, if a guest decides they have nothing to say, they may give up their slot and somebody may use it; thus, if there are 14 people at the party, and only one is being chatty, you avoid long awkward pauses every time that user is done with her slot). In general, Wi-Fi standards typically have a theoretical speed at which things can operate, e.g. 802.11b at 11 Mbps, 802.11g at 54 Mbps, 802.11n at 300 Mbps, 802.11ac at 1.3 Gbps etc. The reality may be quite different however, because of chipset limitations, etc., thus one can typically get only a percentage of the theoretical speed. To extend the party analogy above, if, just when Alice started to talk, a background noise (e.g., music or TV playing in the background) were turned on so loudly that nothing Alice said could be heard by the host, and as a result, she basically “wasted” her time-slot, she may have to wait until her next time-slot to make her point or points, e.g., she may be making three conversational points in her time-slot, and if the TV came on after she made her second point, she may have gotten two of her points across, but not the third in her time-slot. The next time around, she may get to make her third and final point. Thus, occasionally, Alice may have to use multiple time-slots just to get all her points across, in effect reducing here data-rate. These are effectively failures. Thus, per the limits of this analogy, a CPE, within its time-slot, may send a number of packets, and some (or all) of these packets may not make it through to the AP. This may cause the CPE to have to resend those packets, reducing the data rate. The concept of usage may also be understood by this analogy. For example, the percentage of the conversation monopolized by Alice may be thought of as her Usage. One way express this would be to take the total amount of time Alice spends talking (success and failures), and dived that by the actual time (e.g., “wall clock time”). However, the analogy becomes more complex if there are a lot of “speakers” (e.g., CPEs). For example, in our analogy, if there are 15 speakers (e.g., 14 other people talking to the host), you can still get Alice's percentage, but given the number of people speaking, the overall percentage may be small. If you're trying to troubleshoot a problem (e.g., Alice, Bob, and Carol are all complaining that the host never seems to hear them because of the background TV noise), it would be better to focus on the guests (e.g., CPEs) of interest. Thus, it may be beneficial to look at Usage for the guests (e.g., CPEs) that are of interest. In the 15 guest example above, the methods and apparatuses described herein may instead calculate the percentage of time that Alice spent speaking, only looking at the times spent by Alice, Bob, and Carol. For example, consider that over a 2 second interval, guests spoke with the host for the following durations: TABLE 1time “talking” in 2 second period“Guest”Time talking(CPE)(msec)Alice20Bob50Carol30David80Elsa40Famke90Gareth200Hector90Indigo50Jewel180Katrina200Mahesh900Lewis20Nancy50 From a strictly “wall-clock” usage perspective, Alice's usage was 1%, Bob's was 2.5%, and Carol's was 1.5% in this example. However, if only Alice, Bob and Carol are of interest (or have the highest ranking and/or are otherwise selected), they may be examined in more detail by instead looking only at usage over the total time this subset of guests (CPEs) were “speaking” with the host (AP). In this case, Alice's airtime usage is 20% (over the total of 0.1 second that they each spoke), Bob's airtime usage is 50% and Carol's airtime usage is 30%. A similar analogy may be used to understand the concept of efficiency (or isolated capacity) as described herein. For example, extending the analogy of the guests speaking at a party even further, it may be helpful to estimate of how impaired communication between Alice and the host was during the time that the background noise (e.g., when a television or radio was playing loudly in the room) by understanding how effective Alice's speaking would be if she was the only person talking (e.g., excluding the other guests). In term of a CPE communicating with an AP, given that there are some packets that need to be retransmitted, it may be helpful to estimate the maximum rate at which the CPE could upload data if there was only one CPE. In Alice's case, we already know how many failures she has in a given period of time (and conversely, how many successes). Since we also know what percentage of time Alice was speaking, her isolated capacity may be readily calculated. For example, if Alice, Bob, and Carol each get to speak for 10 seconds at a time, over a 300 second interval (e.g., each got to speak 10 times), if Alice successfully spoke 7 times, and the background noise (e.g., a loud TV) was turned on 3 times, Alice was “successful” 70% of the time, i.e., this was her efficiency (if she was the only person speaking to the host, the best she would be able to do would be to be successful 70% of the time). Similarly, for a CPE, if there are three CPEs, each of which get to upload data 10 seconds at a time, over a 300 second interval (e.g., each got to upload data 10 times), the first CPE (“Alice”) uploaded data successfully 7 times, and failed to upload data 3 times. So, in this case, the CPE “Alice” has an efficiency of 70% for uploads. For a slightly more realistic example, consider an 802.11g CPE that can transmit at 54 Mbps. This means that CPE “Alice” may at best, transmit at 40.5 Mbps in this paradigm. Thus, the isolated capacity of CPE “Alice” is 0.7*40.5=28.35 Mbps (since CPE “Alice” was successful only 7 out of 10 times). Thus, CPE “Alice” has an upload efficiency in this example of 70% and an isolated capacity of 28.35 Mbps. Efficiency indicates how efficient the CPE (Alice) is at communication, while the isolated capacity indicates a boundary on what a system (e.g., a wireless service provider) may expect from a CPE relative to uploading information. Note that although the general concepts illustrated in this example by analogy are helpful, they may not be complete. For example, (again by analogy), guest such as Alice may be talking, and the Host listening, however the host may sometimes talk as well, which may make this somewhat more complicated. However, it may be useful to assume that the same characterization made above may be applied to the host as well, including the noise analogy. Thus, wherein upload information (talking from CPE to AP) applies, there may also be a download (e.g., talking from AP to CPE). The upload may be called the Uplink, and the download may be called the Downlink. Thus, if both AP and CPEs (e.g., both Alice and the host) are communicating, (i.e., the CPE both uploads and downloads data), a slightly better picture of efficiency may take the average of the upload and download efficiencies. For example, CPE “Alice” may have an uploaded efficiency of 70% as discussed above. Similarly, a download efficiency may be determined (e.g., a download efficiency from the AP of 82%). Thus, the upload and download efficiencies may be averaged to determine Alice's efficiency (e.g., 76%) This information may be graphically displayed as described above to show efficiency versus air time usage (e.g., the percentage of the time that each CPE is actually on the air, In our example, the time Alice is talking to the host). In the analogy above, Alice has an efficiency of 76% and an air time of 20, Bob has an efficiency of 84% and an air time of 50, and Carol has an efficiency of 35% and an air time of 30. A graphical illustration of this may be provided by a TDMA chart such as that shown inFIG.16. In general a TDMA window graph may show all clients (CPE's) of an AP and their air time utilization, ordered by the clients' efficiency. The efficiency of the client may be a percentage value of the client's current performance relative to the maximum performance the AP can support, and air time may indicate the amount of time each of the clients is using on the AP, relative to other clients. The more air time an individual client uses, the less is available for other clients. Part II: Channel Frequency and Bandwidth Selection Based on Spectral and Traffic Statistics Also described herein are methods and apparatuses to improve transmission on between two or more devices (including between an AP and one or more CPEs) in the presence of noise by determining which channels from a variety of potential transmission channels are better than others. For example, described herein are methods for, and apparatuses configured to, determine a ranking of overall channel quality (“goodness”) for transmission between one or more devices. The apparatuses and methods described herein may manually or automatically use this determination (ranking) to switch between channels. In some variations the apparatuses described herein may be configured to perform these rankings at the level of the AP and/or CPEs and/or using a remote (e.g., cloud) server. A wireless network generally be considered to consist of multiple devices communicating over a single wireless channel. The wireless channel may be identified by its center frequency and its bandwidth, i.e., the amount of spectrum it occupies, as illustrated inFIG.17, showing a schematic example of a channel having a channel center frequency (fc) and a bandwidth (bw). Wireless systems may be designed to operate over a range of channel frequencies and bandwidths. For example, a wireless network can operate over channels with center frequencies 5150 MHz, 5155 MHz, 5160 MHz, etc., and bandwidths of 10 MHz, 20 MHz or 40 MHz, etc. For one example, all channels in which a wireless channel can operate may be listed as illustrated in Table 2, below: TABLE 2N exemplary channelsChannel IDCenter FrequencyBandwidthchannel[1]channel[1].fc = 5150 MHzchannel[1].bw = 10 MHzchannel[2]channel[2].fc = 5150 MHzchannel[2].bw = 20 MHzchannel[3]channel[3].fc = 5155 MHzchannel[3].bw = 10 MHz. . .. . .. . .channel[Nc]channel[Nc].fcchannel[Nc].bw The performance of a wireless network including achievable data rates, packet transmission latencies and user experience may be directly impacted by interference in the wireless channel, caused by wireless and/or other electronic devices emitting radio waves in the same or adjacent frequencies occupied by the wireless channel. In the case when a wireless network is operating in an unlicensed frequency band, the operator of that network may have no control or ownership over the wireless channel and may be required to share its use with other operators, under applicable spectral regulations and laws. Most wireless devices and networks operating in the unlicensed spectrum may have the ability to dynamically change channels. Typically, such a channel change may be triggered by detection of excessive interference or presence of, for example, radar signals in the current channel. This approach is inherently reactive and has several drawbacks, including: the performance of the network may have already degraded to a level where connections are dropped etc., before the network is able to detect that quality of the current wireless channel has, in fact, degraded; and the network typically selects the new channel based on data collected over a short time frame. In a longer time frame, this channel's quality may also degrade and another channel change is required. The decision to change from a current channel and the choice of the new channel may be based on short term observations of interference, which may be inadequate. In particular, in highly dynamic interference scenarios, which are particularly typical in unlicensed frequency bands, this approach may be ineffective. Channel changes, and particularly existing channel channels, may be extremely disruptive to data transmissions and thus reduce the efficiency and usability of the network. Furthermore, for reasons described above channel change algorithms known in prior art are ineffective. Hence, wireless network operators typically disable this feature and resort to manually choosing the channels of their network. As it is not feasible for the operator to manually change channels on a regular basis, they typically select a channel at the time of provisioning the network or when troubleshooting performance issues. In addition to lowering operator productivity, this manual channel selection methodology suffers from the same drawbacks as automated channel selection methodologies known in the prior art, highlighted above. Ambient Noise Floor and Carrier to Interference and Noise Ratio In the presence of interference, the goodness/quality of a wireless channel can be characterized by the Carrier to Interference and Noise Ratio (CINR), as mentioned above. When represented in decibels, CINR may be the difference between received signal power and interference plus noise power. We herein refer to the interference plus noise power level as the Ambient Noise Floor, as opposed to the Thermal Noise Floor which is the level of thermal noise power alone. The thermal noise floor is dependent on the receive bandwidth, which is generally static. On the other hand, the ambient noise floor varies significantly with time as it is dependent on interference signal levels, as shown inFIG.18. Methods and Apparatuses for Grading/Ranking Channels In general, described herein are methods and apparatuses for ranking channels (in some variations including any used channel currently being used by the device(s), in other variations including channels not being used by the device(s)) based on a determination of channel “goodness” calculated from an indication of the historical and/or instantaneous (including a time-specific indication) of power (noise, such as the ambient noise floor) for each channel, and in some variations one or more indicators of the capability of one or more stations (e.g., CPEs linked to an AP) specific to that channel. For example, described herein are methods and apparatuses to determine the best channel or a list of best channels to operate a wireless network based on statistical information or radio and data traffic, collected over a (e.g., long, greater than about 12 hr, greater than about 24 hour, greater than about 36 hour, greater than about 48 hours, etc.) time period. These methods and apparatuses for performing them may, for example, provide a table ranking or listing of channels available to network of APs and CPEs for communication between the two. The listing/array/table may be one-dimensional and unqualified (e.g., simply listing as best to worst, or more/less “good”, etc.), or the listing/array/table may be one-dimensional and qualified (e.g., indicating which CPEs in the network would be best/worst for this channel, etc.). In some variations the listing/array/table is multi-dimensional and qualified or unqualified, e.g., including a vector that has individual rankings for all or a sub-set of the CPEs in the network. An apparatus (generally including device and systems) configured to grade/rank channels as described herein may generally include a spectrum analyzer that is adapted specifically to monitor activity on other channels in the network (e.g., concurrent with transmitting/receiving activity in an in-use channel). For example, any of the devices described herein configured to rank or grade channels, or from part of a network that ranks/grades channels, may include a radio having a first path with a transmitter/receiver (or transceiver) that operates on a channel and may be changed (tuned) to another channel. The apparatus may include a second (in some variations parallel) path that includes a spectrum analyzer for monitoring energy on the frequency spectrum (including or excluding the frequencies currently being used by the radio to transmit/receive). The apparatus may store this information as a matrix of frequency, time and energy (e.g., the energy reading at a particular frequency at time of day). Additionally or alternatively, this information may be transmitted to a remote server and any of the apparatuses described herein may access this matrix in determining the parameters (e.g., ambient noise floor) as described herein. Using Achievable Data Rate at Channel Quality Metric In one variation, the goodness of a channel may be determined by an estimated achievable data rate of that channel, which may be specific to individual stations in the network and may therefore be determined separately, or in some variations collectively, for each station. The achievable data rate may be determined by first estimating the ambient noise floor of that channel and then translating it to an achievable data rate, as illustrated schematically inFIG.19. As shown in this example, given the received signal strength (rx_power), the CINR for that channel (channel[i].CINR) may be determined by subtracting channel[i].ambient_NF from rx_power. The channel[i].achievable_datarate may be computed, for example, from this channel[i].CINR by using a look-up table (LUT_RATE) of values that can be empirically or theoretically determined and may be specific to a device or class of devices. For example, the look up table (LUT_RATE), may include regulatory rules for EIRP in determining the achievable data rate. In another variation, the goodness (which may be expressed in Kbps/Mbps) of a channel may be measured by the estimated average achievable data rate of that channel, where ambient noise floor values measured at different time periods (and received, for example, from the spectrum analyzer information descried above), may be considered in determining the weighted average achievable data rate. The ambient noise floor may be measured at time instant j, and the channel[i].ambient_NF[j] may be converted to an estimated achievable data rate channel[i].achievable_datarate[j] for that period. The average achievable data rate may be determined by averaging channel[i].achievable_datarate[j] after weighting by a factor weight[j] values as illustrated inFIG.20. Weighting factors may be based on information specific to the station (CPE and/or AP). For example, in some variations, weighting factors may be based on receive usage. In some variations, channel usage in the receive direction may be used to compute the weighting factors. The channel receive usage at time instant j may be given by channel_usage[j] with value between 0 and 1 indicating wireless channel receive usage of the network at time j, where 0 indicates no usage and 1 indicates maximum usage. Weight [j] may be computed as follows: Weight[j]=(channel usage [j])/(channel usage [1]+channel usage[2]+ . . . +channel usage [j]) Any of the variations described above may be used with specific end-point devices of point-to-point connections (e.g., AP to single CPE), and may also be adapted for use with point-to-multipoint (AP-multiple CPEs). For example, for a point-to-point (PTP) wireless link, the apparatus or method implemented by the apparatus(s) may consider information available from both ends (e.g., master and slave, AP and CPE, etc.) of the link to determine the best channel. Similarly, for a point-to-multipoint (PMP) network, the apparatus and method may consider multiple end-points/subscriber modules (SMs) and the access-point (AP) to determine the best channel. For example, an SMs (in the case of PMP) and the slave device (in the case of PTP) may periodically send a “spectrum information” packet to the AP/master. For this example, we may refer to SMs/PTPSLAVES and the AP as a Connected Device (CD).FIG.21shows one example of the packet (Spectrum information packet) that may be transmitted between the devices (e.g., from the slave/CPE stations to the AP). In this example, the packet indicates the number of channels and periods (Nc, Np) and lists the receive usage information each Np period (“channel_rx_usage[ . . . ]”) as well as the frequency (fw), bandwidth (bw) and ambient noise floor for each channel, as illustrated. In some variations, a connected device can be considered as a 4-tuple, e.g.: (mac-address, priority, channel_rx_usage[0 . . . Np-1], spectrum_info[0 . . . Nc-1]). In this example, channel_rx_usage is a vector containing channel receive usage information for Np periods, and spectrum_info is a vector containing information for Nc channels. Each spectrum information channel can be considered as a 3-tuple, e.g.: (fc, bw, ambient_NF[0 . . . Np-1], goodness), where ambient_NF is a vector containing ambient noise floor information for Np periods, and goodness is computed by using the channel receive usage as weights for each of Np periods. This information may include priority when determining the grading/ranking. For example, seeFIG.22. In general, the AP/PTPMASTER's connected device entity may have the highest priority. Thus, in general, each device may include multi-dimensional information for each channel (or range of frequencies in the channel) in a multiple-device network (e.g., point-to-multipoint network). The apparatuses and methods described herein may simplify this multi-dimensional information into a single dimension. For example, when a channel includes multiple different frequencies, the noise information (Ambient Noise) used to calculate the goodness may be the maximum (e.g., worst case scenario) from all of the frequencies in the channel, or it may be an average, median, etc. In addition, a subset of timing ranges may be chosen, e.g., using a range of time (going backwards from the instant/current time a particular value, such as 1 hr, 2 hrs, 3 hrs, 4 hrs, 12 hrs, 24 hrs, etc. or any increment thereof), or only the most recent time values may be chosen (e.g., and selected from the matrix of energy provided by the spectral information). Thus, the apparatuses and methods described herein may determine a ranking/scoring and/or listing of the top N channels for a network for each bandwidth. For example, Nb may be set as the number of available bandwidth options. e.g. (10, 20, 30, 40, 50, 60, 80 MHz) and Nd as the number of connected devices. The apparatuses and methods described herein may split the SpectrumInfo vector by bandwidth and initialize a PerBandWidth (PBW) entity for each bandwidth k=0 . . . Nb-1. This may be determined by the equation shown below (and inFIG.22A): PBW[k]·goodness[j]=∑0Nd-1CD[i]·SpectrumInfo[f]·goodness×CD[i]·Priority∑0Nd-1CD[i]·Priority Where, for each j, where PBW[k].bw=CD[i].SpectrumInfo[j].bw and where j=0 . . . Nc-1, i=0 . . . Nd-1, k=0 . . . Nb-1. Sorting PBW[k].goodness in descending order and using the top N channels may provide the best frequencies for each available bandwidth option. The bps-per-Hz metric used herein also provides a normalized way to judge spectral usage and efficiency and for a given channel. For example, this metric may be a ratio of the PBW[k].goodness[j] and PBW[k].bw (e.g., PBW[k].goodness[j]/PBW[k].bw). For example table 3, below, shows an example of top-3 channels, with the computed goodness and the bps-per-Hz: TABLE 3exemplary ranking of bandsFrequency10 MHz20 MHz40 MHz80 MHz578562 (6.2 bps/Hz)120 (6.0 bps/Hz)150 (3.75 bps/Hz)250 (3.12 bps/Hz)520050 (5.0 bps/Hz)80 (4.0 bps/Hz)120 (3 bps/Hz)180 (2.25 bps/Hz)550070 (7.0 bps.Hz)100 (5.0 bps/Hz)90 (2.25 bps/Hz)75 (0.875 bps/Hz) In general, and operator using the apparatuses described herein can select the desired frequency, either based on absolute capacity required for that network, or the operator can optimize the network for spectral efficiency based on the computed bps/Hz. As an example: with a 80 MHz channel centered at 5785 MHz, the operator may get a capacity of 250 Mbps, but it comes at a lower spectral efficiency. Dividing this network into three RF domains (sectors), and using 20 MHz channels centered at 5785, 5200 and 5500 MHz may provide a total of 300 Mbps capacity using 60 MHz of total spectrum. In operation, any of the apparatuses described herein may be used to provide information for automatic or manual switching between channels. For example, in automatic switching, a master device (e.g., AP) may determine that it is time to switch based on any appropriate criterion, such as overall degradation of signal transmission quality, or degradation of transmission quality with one or more high-priority devices. For example, when a quality threshold is passed. This determination may be made locally (at the AP and/or CPEs) or remotely (e.g., in a cloud configuration) or both. Alternatively a user (administrator) may determine that the quality has degraded and may manually determine to switch channels. In either case, the apparatuses may apply the methods described herein to determine which one or more channels provide the best options for switching. In an automatic configuration, the system may switch to the top ranking channel, or may use a selection of the top ranked channels to compare with other factors (including nearby networks or other APs to determine what the switching should be). In manual configurations the system may present the user (administrator) with the channel options in a simple list (annotated or unannotated, as described above) so that the user may make the best decision possible in choosing the band to switch to. For example, described herein are apparatuses including a processor that holds or receives any of the information described herein and displays the ranking/grading/listing as described herein, and allows a user to select from among the listed/graded/scored bands which frequency band to change to. The apparatus may include software, hardware, firmware of the like, and is dependent upon connection to and/or receiving the information described herein (e.g., spectral information) from one or more stations in the network (and preferably all of the stations). Optimization of Channel Selection Any of the methods and apparatuses described herein may be configured to optimize channel selection and either present one or more “top” ranked channels to a user or automatically switch to the top ranked channel, by determining a ranking of frequency channels within a target frequency range by spectral efficiency. Described herein are methods of performing this optimization as well as apparatuses configured to perform these methods. These apparatuses are typically access point devices (though not limited to such devices). These devices may operate in point-to-point (PTP) or point-to-multipoint (PTMP) configurations, and may optimize in both. Any of these apparatuses (e.g., APs) may include a visual tool allowing user interaction, including display of the top (optimized) frequency channels, display of the frequency spectral information for devices communicating with the AP and/or the AP spectral frequency information, as well as selection of the channel bandwidth, the frequency range to be optimized over, etc. For example, an apparatus such as an access point may be configured to estimate the capacity for all or some of the devices communicating with the AP from the usage data (e.g., signal strength data, including RSSI). The usage data for each link (e.g., between the AP and the client devices) may allow the apparatus to estimate the capacity based on the received signal strength and to determine the capacity at both ends of each link, which may then be used to determine spectral efficiency. An apparatus, such as an access point, may be configured to implement a method of optimizing channel selection, as described herein. For example, an access point (AP) may be configured to optimize the Tx/Rx channel and/or channel width based (either automatically or manually), by determining the received signal strength at both ends of the link between the AP and a client (e.g., a CPE) that is wirelessly communicating with the AP. As descried below, the apparatus may be configured to do this for every client that is connected to the AP, or just for a subset of the clients connected to the AP, such as the top to number of clients, e.g., the top twenty (tn=20) clients using the most bandwidth in a given time period. In addition, the AP may use the historical spectral data, which gives the energy in the band from other sources, including interferers, for the previous predetermined time period (e.g., 24 hours, 7 days, etc.), and using the Tx and Rx signal strength (usage data), as well as the historical spectral data, the capacity of the link can be estimated. In estimating the capacity of the link, the worst case capacity may be determined, or an average capacity may be determined, or both, from all (or the subset of) client communicating with the AP. For example, the signal strength and interference may be used, as described above, to determine a channel capacity based on the signal to interference plus noise (SINR). For example, a lookup table may be used to calculate the data rate based on the signal strength and spectral data for each client. In practice, each client type (e.g., CPE device type) may have a slightly different lookup table for each product; in some variations a generic look-up table may be used. Thus, the signal strength and spectral information may be used to determine a data rate (e.g., per length) for each client (CPE). The method or apparatus may be configured to look at the clients with the most usage (e.g., the top to clients based on usage), and either average the data rate per length, or use some other adjusted data rate (e.g., a weighted average, a mean, median, etc.). This may provide an average or consolidated data rate for the AP and its clients, and this data rate is then typically divided by the amount of spectrum used (the channel width), such as for example, 10 MHz, 20 MHz, 40 MHz, 50 MHz, 60 MHz, 80 MHz, etc.) to give a spectral efficiency for each channel at a particular channel width (bandwidth), in bits per second per Hz. (Bps/Hz). Channels may thus be ranked by spectral efficiency. Any of the apparatuses described herein may therefore be configured to display the ranking, e.g., by listing, labeling, or otherwise showing the top (e.g., the top one, two three, four, five, etc.) channels with the highest spectral efficiencies at a particular and/or predetermined channel width. For example,FIG.23illustrates one example of a method of determining spectral efficiency rankings for each of a plurality of frequency channels. For example, initially (and optionally) a method of determining spectral efficiency rankings may collect historical frequency spectral information for one or more devices linked to an access point (AP). This information may be collected, stored, or held, in the AP2301. Usage data may also be collected, stored and/or held in the AP. For example, usage data (e.g., signal strength) for the one or more devices linked to AP may be collected in the AP2303. Thereafter, at each of a plurality of channel frequencies, an interference plus noise (SINR) may be determined for each of the one or more devices2305, and a data rate may be determined from the SINR and historical frequency spectral information specific to each of the one or more devices at each of the one channel frequencies. Once the data rates have been determined (as described above, this may be achieved by using a look-up table that is specific to each type of device) for each device, an aggregate data rate may be determined for the network; the aggregate data rate may be a function of all or a subset of the devices (e.g., average, mean, median, weighted average, maximum, minimum, etc.)2307. An aggregate data rate may be determined at each frequency channel to be examined. For example, the frequency range may be divided up into a predetermined number of channels (e.g., between 5 and 1000 channels, 5 and 500 channels, etc. a channel every 1 kHz, etc.) and a spectral efficiency determined for each channel. The aggregate data rate at each frequency may then be divided by the channel width to determine the spectral efficiency at that frequency2309. The resulting set of channels and spectral efficiencies may then be stored. In some variations (as illustrated inFIG.23), the steps may be performed iteratively, e.g., by sequentially determining the spectral efficiency at different frequencies and repeating the process at different frequencies. Alternatively, this procedure may be performed in parallel for different frequencies, or some combination of parallel and sequential, until a spectral efficiency has been determined for all of the frequency channels within the frequency range2311. An apparatus, such as an access point device, may be configured to optimize the channel selection using a method such as that described above. For example,FIG.33illustrates one example of an access point3300that is wirelessly communicating with a plurality of other devices (e.g., stations, CPEs, etc.)3350,3350′. In this example, only two other devices3350,3350′ are shown, however additional devices may be part of the network as well. The access point3350typically includes an antenna3301, wireless radio circuitry (e.g., transceiver)3303, and a controller that may include a processor, memory, and the like, including an output3309(e.g., a user interface, as described herein) for controlling operation of the access point. The control may be configured specifically to perform any of the methods described herein, including the optimization of the frequency channel. Each of the client devices (stations, CPEs, etc.)3350,3350′ may typically include a wireless antenna3351and radio circuit3353, which may be separated or integrated with a controller/processor3355′. These devices may also each include a second receiver3358that is configured as a spectrum monitor for monitoring the frequency spectrum. In some variation, this spectrum monitor is not separate from the transceiver of the radio frequency, but instead the apparatus is configured to monitor the spectrum when not otherwise receiving or transmitting. Note that althoughFIG.33is described herein in reference to an apparatus configured to optimize frequency channel, this illustration of a wireless network may be relevant to any of the apparatuses and methods described herein, including in particular, method and apparatuses or providing a ranked indicator of station efficiency and/or methods and apparatuses for monitoring a wireless network including transmitting a plurality of sounding packets and determining EVM information. In general, an apparatus of optimizing the frequency channel of an access point, and therefore of the network, may generally include a controller that is configured to generate a tool such as the tool shown inFIGS.24B and24C. For example,FIG.24Aillustrates a user interface for an access point that is communicating with one or more stations (e.g., CPEs), describing features and characteristics of the access point, the number of connections, and a graphical description of one or more link between the access point a station. In this example, the user interface includes a pair of constellation diagrams2401,2403that may be generated as described above. This user interface (as well as any associated tools, such as the tool2410shown inFIGS.24B and24Cthat may allow optimization as described herein. InFIG.24B, the tools is a portion of the user interface that acts as a pop-up window2410that includes a visual indicator (e.g., chart, table, bar) of the frequency range, as well as indicating the frequency spectral information for the AP and each (or some) of the devices wirelessly connected with the AP2423. InFIG.24C, this is indicated by the horizontal rows (labeled on the far right side of the tool) that are labeled as heat maps indicating the energy at each point of the spectrum as measured over some time period (e.g., the last 24 hours, 48 hours, 3 days, 4 days . . . etc.). A key to this heat mapping is shown in the upper right2419. The x-axis in this example is frequency, and the frequency range is shown along the bottom. Sliders may be used to adjust the upper2455′ and lower2455ends of the frequency range analyzed. The user interface tool2410may also include a listing of recommended channel widths (bandwidths)2415, as illustrated on the far left side of the tool. The recommended channel widths may include predicted spectral efficiencies and capacities for each of the different channel widths (e.g., 10, 20, 30, 40, 60, 80 MHz). Any of these channel widths may be selected (e.g., by clicking on them) using this portion of the tool and/or by using a control such as the slider2417in the upper middle of the tool. In general, the access point may be configured to provide this tool either directly (e.g., by hosting a webpage that a user may access) or indirectly, by transmitting the information to a third party controller/server that may communicate with the access point and the user. InFIGS.24B and24C, the tool also shows the optimized (e.g., top ranked) frequency channels determined by the methods described above at the selected bandwidth (e.g., 40 MHz inFIGS.24B and24C). In this example, the three channels having the highest spectral efficiency are shown in boxes above the graph of the spectral information2420,2420′,2420″. In this example, the channels having the best spectral efficiency are 5230 GHz2420, which has a spectral efficiency of 4.6 Bps/Hz (bits per second per Hz), 5380 GHz2420′ which also has a spectral efficiency of 4.6 Bps/Hz (bits per second per Hz), and 5580 GHz2420″, which has a spectral efficiency of 4.8 Bps/Hz (bits per second per Hz). The tool also allows the user to manually select a frequency and spectral efficiency is of the selected frequency is also shown at the top, and the historic spectral information is highlighted2430. In this example, the gray boxes illustrate the top three recommended channels. In this example, as mentioned above, the channel width is manually determined, however in some variations it may be automatically selected (or suggested). For example, the channel width may be optimized. The capacity for the network may be determined based on, for example, the traffic through the Ethernet port. Thus, the access point may determine how much capacity is needed to send data to each device. For example, if the access point needs only 100 Mbps per second, then, as shown in the recommended channel widths2415portion, the channel width maybe the smallest capacity to meet this requirement, e.g., 20 MHz inFIG.24C. As mentioned above, the user interface tool which may form part of the apparatus (e.g., an access point apparatus) may also allow manipulation of the optimization to determine channel frequency. InFIG.25, the tool is shown without any optimization, though a heat map of the frequency spectral information for the access point and each of 20 connected units are shown. In this example, the 20 connected devices may be a subset of the total number of selected device; for example they may represent only the 20 highest-ranked devices for station efficiency, average airtime. The user may select any channel frequency by clicking on it, as shown. FIG.26illustrates the selection of the channel width (in this example, 20 MHz) by clicking on the 20 MHz option in the recommended channel windows. Once the channel width is set, the apparatus may determine the top channel efficiencies and indicate them as described above and shown again inFIG.26. In this example, the three most spectrally efficient channels are5380(7.2 Bps/Hz),5170(7.1 Bps/Hz) and5790(6.8 Bps/Hz). FIG.27illustrates the selection of a different channel width (e.g., 60 MHz), which results in different top spectrally efficient channels (e.g.,5590, with 7.5 Bps/Hz,5250, with 6.9 Bps/Hz, and5390, with 6.4 Bps/Hz). As mentioned above, the frequency range over which the optimization is performed may also be modified, as shown inFIG.28, in which the sliders at the bottom of the frequency range may be adjusted to narrow or expand the frequency range. FIGS.24-28illustrate the tool for an access point that is configured as a point to multipoint (PTMP) device. These apparatuses, tools and methods may also be used with point to point (PTP) devices, as shown inFIG.29. In this example, the access point device may be instead configured as a PTP device and the local and remote devices properties may be displayed, including a local frequency spectral information shown as actual spectrograms. The remote device spectrogram is shown on the bottom and the local on the top. Again, a heat map may indicate the probability of the frequency having an energy level as shown by the line (which may be an average energy level, or some other metric for that frequency). The tool is otherwise the same, and functions as described above. For example, as shown inFIG.30, a 20 MHz channel bandwidth may be selected, and the resulting top three spectral efficiencies may be determined (e.g.,5810, with 7.2 Bps/Hz;5220, with 7.1 Bps/Hz; and5760with 6.8 Bps/Hz).FIG.31shows the shift to a different channel bandwidth (e.g., 30 MHz) and the resulting shift in the highest spectral efficiencies. Similarly,FIG.32illustrates the selection of a narrower range of frequencies to optimize over. When a feature or element is herein referred to as being “on” another feature or element, it can be directly on the other feature or element or intervening features and/or elements may also be present. In contrast, when a feature or element is referred to as being “directly on” another feature or element, there are no intervening features or elements present. It will also be understood that, when a feature or element is referred to as being “connected”, “attached” or “coupled” to another feature or element, it can be directly connected, attached or coupled to the other feature or element or intervening features or elements may be present. In contrast, when a feature or element is referred to as being “directly connected”, “directly attached” or “directly coupled” to another feature or element, there are no intervening features or elements present. Although described or shown with respect to one embodiment, the features and elements so described or shown can apply to other embodiments. It will also be appreciated by those of skill in the art that references to a structure or feature that is disposed “adjacent” another feature may have portions that overlap or underlie the adjacent feature. Terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. For example, as used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items and may be abbreviated as “/”. Spatially relative terms, such as “under”, “below”, “lower”, “over”, “upper” and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if a device in the figures is inverted, elements described as “under” or “beneath” other elements or features would then be oriented “over” the other elements or features. Thus, the exemplary term “under” can encompass both an orientation of over and under. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly. Similarly, the terms “upwardly”, “downwardly”, “vertical”, “horizontal” and the like are used herein for the purpose of explanation only unless specifically indicated otherwise. Although the terms “first” and “second” may be used herein to describe various features/elements (including steps), these features/elements should not be limited by these terms, unless the context indicates otherwise. These terms may be used to distinguish one feature/element from another feature/element. Thus, a first feature/element discussed below could be termed a second feature/element, and similarly, a second feature/element discussed below could be termed a first feature/element without departing from the teachings of the present invention. As used herein in the specification and claims, including as used in the examples and unless otherwise expressly specified, all numbers may be read as if prefaced by the word “about” or “approximately,” even if the term does not expressly appear. The phrase “about” or “approximately” may be used when describing magnitude and/or position to indicate that the value and/or position described is within a reasonable expected range of values and/or positions. For example, a numeric value may have a value that is +/−0.1% of the stated value (or range of values), +/−1% of the stated value (or range of values), +/−2% of the stated value (or range of values), +/−5% of the stated value (or range of values), +/−10% of the stated value (or range of values), etc. Any numerical range recited herein is intended to include all sub-ranges subsumed therein. Although various illustrative embodiments are described above, any of a number of changes may be made to various embodiments without departing from the scope of the invention as described by the claims. For example, the order in which various described method steps are performed may often be changed in alternative embodiments, and in other alternative embodiments one or more method steps may be skipped altogether. Optional features of various device and system embodiments may be included in some embodiments and not in others. Therefore, the foregoing description is provided primarily for exemplary purposes and should not be interpreted to limit the scope of the invention as it is set forth in the claims. The examples and illustrations included herein show, by way of illustration and not of limitation, specific embodiments in which the subject matter may be practiced. As mentioned, other embodiments may be utilized and derived there from, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Such embodiments of the inventive subject matter may be referred to herein individually or collectively by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept, if more than one is, in fact, disclosed. Thus, although specific embodiments have been illustrated and described herein, any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. | 89,505 |
11943756 | DETAILED DESCRIPTION The detailed description set forth below, in connection with the appended drawings, is intended as a description of various configurations and is not intended to limit the scope of the disclosure. Rather, the detailed description includes specific details for the purpose of providing a thorough understanding of the inventive subject matter. It will be apparent to those skilled in the art that these specific details are not required in every case and that, in some instances, well-known structures and components are shown in block diagram form for clarity of presentation. This disclosure relates generally to providing or participating in communication as between two or more wireless devices in one or more wireless communications systems, also referred to as wireless communications networks. In various embodiments, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5thGeneration (5G) or new radio (NR) networks (sometimes referred to as “5G NR” networks/systems/devices), as well as other communications networks. As described herein, the terms “networks” and “systems” may be used interchangeably. A CDMA network, for example, may implement a radio technology such as universal terrestrial radio access (UTRA), cdma2000, and the like. UTRA includes wideband-CDMA (W-CDMA) and low chip rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may, for example implement a radio technology such as GSM. 3GPP defines standards for the GSM EDGE (enhanced data rates for GSM evolution) radio access network (RAN), also denoted as GERAN. GERAN is the radio component of GSM/EDGE, together with the network that joins the base stations (for example, the Ater and Abis interfaces) and the base station controllers (A interfaces, etc.). The radio access network represents a component of a GSM network, through which phone calls and packet data are routed from and to the public switched telephone network (PSTN) and Internet to and from subscriber handsets, also known as user terminals or user equipments (UEs). A mobile phone operator's network may comprise one or more GERANs, which may be coupled with Universal Terrestrial Radio Access Networks (UTRANs) in the case of a UMTS/GSM network. An operator network may also include one or more LTE networks, and/or one or more other networks. The various different network types may use different radio access technologies (RATs) and radio access networks (RANs). An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of universal mobile telecommunication system (UMTS). In particular, long term evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided from an organization named “3rdGeneration Partnership Project” (3GPP), and cdma2000 is described in documents from an organization named “3rdGeneration Partnership Project 2” (3GPP2). These various radio technologies and standards are known or are being developed. For example, the 3rdGeneration Partnership Project (3GPP) is a collaboration between groups of telecommunications associations that aims to define a globally applicable third generation (3G) mobile phone specification. 3GPP long term evolution (LTE) is a 3GPP project which was aimed at improving the universal mobile telecommunications system (UMTS) mobile phone standard. The 3GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices. The present disclosure is concerned with the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond with shared access to wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces. 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. To achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for 5G NR networks. The 5G NR will be capable of scaling to provide coverage (1) to a massive Internet of things (IoTs) with an ultra-high density (e.g., ˜1M nodes/km2), ultra-low complexity (e.g., ˜10s of bits/sec), ultra-low energy (e.g., ˜10+ years of battery life), and deep coverage with the capability to reach challenging locations; (2) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., ˜99.9999% reliability), ultra-low latency (e.g., ˜1 ms), and users with wide ranges of mobility or lack thereof; and (3) with enhanced mobile broadband including extreme high capacity (e.g., ˜10 Tbps/km2), extreme data rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations. 5G NR devices, networks, and systems may be implemented to use optimized OFDM-based waveform features. These features may include scalable numerology and transmission time intervals (TTIs); a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD)/frequency division duplex (FDD) design; and advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility. Scalability of the numerology in 5G NR, with scaling of sub-carrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of less than 3 GHz FDD/TDD implementations, subcarrier spacing may occur with 15 kHz, for example over 1, 5, 10, 20 MHz, and the like bandwidth. For other various outdoor and small cell coverage deployments of TDD greater than 3 GHz, subcarrier spacing may occur with 30 kHz over 80/100 MHz bandwidth. For other various indoor wideband implementations, using a TDD over the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur with 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting with mmWave components at a TDD of 28 GHz, subcarrier spacing may occur with 120 kHz over a 500 MHz bandwidth. The scalable numerology of 5G NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTI may be used for low latency and high reliability, while longer TTI may be used for higher spectral efficiency. The efficient multiplexing of long and short TTIs to allow transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with uplink/downlink scheduling information, data, and acknowledgement in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink/downlink that may be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet the current traffic needs. For clarity, certain aspects of the apparatus and techniques may be described below with reference to exemplary LTE implementations or in an LTE-centric way, and LTE terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to LTE applications. Indeed, the present disclosure is concerned with shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces, such as those of 5G NR. Moreover, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate with any combination of licensed or unlicensed spectrum depending on loading and availability. Accordingly, it will be apparent to one of skill in the art that the systems, apparatus and methods described herein may be applied to other communications systems and applications than the particular examples provided. While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and/or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or OEM devices or systems incorporating one or more described aspects. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. It is intended that innovations described herein may be practiced in a wide variety of implementations, including both large/small devices, chip-level components, multi-component systems (e.g. RF-chain, communication interface, processor), distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution. FIG.1shows wireless network100for communication according to some embodiments. Wireless network100may, for example, comprise a 5G wireless network. As appreciated by those skilled in the art, components appearing inFIG.1are likely to have related counterparts in other network arrangements including, for example, cellular-style network arrangements and non-cellular-style-network arrangements (e.g., device to device or peer to peer or ad hoc network arrangements, etc.). Wireless network100illustrated inFIG.1includes a number of base stations105and other network entities. A base station may be a station that communicates with the UEs and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like. Each base station105may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to this particular geographic coverage area of a base station and/or a base station subsystem serving the coverage area, depending on the context in which the term is used. In implementations of wireless network100herein, base stations105may be associated with a same operator or different operators (e.g., wireless network100may comprise a plurality of operator wireless networks), and may provide wireless communications using one or more of the same frequencies (e.g., one or more frequency bands in licensed spectrum, unlicensed spectrum, or a combination thereof) as a neighboring cell. In some examples, an individual base station105or UE115may be operated by more than one network operating entity. In other examples, each base station105and UE115may be operated by a single network operating entity. A base station may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, and/or other types of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell, such as a pico cell, would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell, such as a femto cell, would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station or a home base station. In the example shown inFIG.1, base stations105dand105eare regular macro base stations, while base stations105a-105care macro base stations enabled with one of 3 dimension (3D), full dimension (FD), or massive MIMO. Base stations105a-105ctake advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station105fis a small cell base station which may be a home node or portable access point. A base station may support one or multiple (e.g., two, three, four, and the like) cells. Wireless network100may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, networks may be enabled or configured to handle dynamic switching between synchronous or asynchronous operations. UEs115are dispersed throughout the wireless network100, and each UE may be stationary or mobile. It should be appreciated that, although a mobile apparatus is commonly referred to as user equipment (UE) in standards and specifications promulgated by the 3rdGeneration Partnership Project (3GPP), such apparatus may also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, a gaming device, an augmented reality device, a vehicular component device/module, or some other suitable terminology. Within the present document, a “mobile” apparatus or UE need not necessarily have a capability to move, and may be stationary. Some non-limiting examples of a mobile apparatus, such as may comprise embodiments of one or more of UEs115, include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a laptop, a personal computer (PC), a notebook, a netbook, a smart book, a tablet, and a personal digital assistant (PDA). A mobile apparatus may additionally be an “Internet of things” (IoT) or “Internet of everything” (IoE) device such as an automotive or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a logistics controller, a drone, a multi-copter, a quad-copter, a smart energy or security device, a solar panel or solar array, municipal lighting, water, or other infrastructure; industrial automation and enterprise devices; consumer and wearable devices, such as eyewear, a wearable camera, a smart watch, a health or fitness tracker, a mammal implantable device, gesture tracking device, medical device, a digital audio player (e.g., MP3 player), a camera, a game console, etc.; and digital home or smart home devices such as a home audio, video, and multimedia device, an appliance, a sensor, a vending machine, intelligent lighting, a home security system, a smart meter, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, UEs that do not include UICCs may also be referred to as IoE devices. UEs115a-115dof the embodiment illustrated inFIG.1are examples of mobile smart phone-type devices accessing wireless network100A UE may also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. UEs115e-115killustrated inFIG.1are examples of various machines configured for communication that access wireless network100. A mobile apparatus, such as UEs115, may be able to communicate with any type of the base stations, whether macro base stations, pico base stations, femto base stations, relays, and the like. InFIG.1, a lightning bolt (e.g., communication link) indicates wireless transmissions between a UE and a serving base station, which is a base station designated to serve the UE on the downlink and/or uplink, or desired transmission between base stations, and backhaul transmissions between base stations. UEs may operate as base stations or other network nodes in some scenarios. Backhaul communication between base stations of wireless network100may occur using wired and/or wireless communication links. In operation at wireless network100, base stations105a-105cserve UEs115aand115busing 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. Macro base station105dperforms backhaul communications with base stations105a-105c, as well as small cell, base station105f. Macro base station105dalso transmits multicast services which are subscribed to and received by UEs115cand115d. Such multicast services may include mobile television or stream video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts. Wireless network100of embodiments supports mission critical communications with ultra-reliable and redundant links for mission critical devices, such UE115e, which is a drone. Redundant communication links with UE115einclude from macro base stations105dand105e, as well as small cell base station105f. Other machine type devices, such as UE115f(thermometer), UE115g(smart meter), and UE115h(wearable device) may communicate through wireless network100either directly with base stations, such as small cell base station105f, and macro base station105e, or in multi-hop configurations by communicating with another user device which relays its information to the network, such as UE115fcommunicating temperature measurement information to the smart meter, UE115g, which is then reported to the network through small cell base station105f. Wireless network100may also provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs115i-115kcommunicating with macro base station105e. FIG.2shows a block diagram of a design of a base station105and a UE115, which may be any of the base stations and one of the UEs inFIG.1. For a restricted association scenario (as mentioned above), base station105may be small cell base station105finFIG.1, and UE115may be UE115cor115D operating in a service area of base station105f, which in order to access small cell base station105f, would be included in a list of accessible UEs for small cell base station105f. Base station105may also be a base station of some other type. As shown inFIG.2, base station105may be equipped with antennas234athrough234t, and UE115may be equipped with antennas252athrough252rfor facilitating wireless communications. At the base station105, a transmit processor220may receive data from a data source212and control information from a controller/processor240. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), physical downlink control channel (PDCCH), enhanced physical downlink control channel (EPDCCH), MTC physical downlink control channel (MPDCCH), etc. The data may be for the PDSCH, etc. The transmit processor220may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor220may also generate reference symbols, e.g., for the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and cell-specific reference signal. Transmit (TX) multiple-input multiple-output (MIMO) processor230may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to modulators (MODs)232athrough232t. Each modulator232may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator232may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators232athrough232tmay be transmitted via the antennas234athrough234t, respectively. At the UE115, the antennas252athrough252rmay receive the downlink signals from the base station105and may provide received signals to the demodulators (DEMODs)254athrough254r, respectively. Each demodulator254may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator254may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector256may obtain received symbols from demodulators254athrough254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor258may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE115to a data sink260, and provide decoded control information to a controller/processor280. On the uplink, at the UE115, a transmit processor264may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source262and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller/processor280. Transmit processor264may also generate reference symbols for a reference signal. The symbols from the transmit processor264may be precoded by TX MIMO processor266if applicable, further processed by the modulators254athrough254r(e.g., for SC-FDM, etc.), and transmitted to the base station105. At base station105, the uplink signals from UE115may be received by antennas234, processed by demodulators232, detected by MIMO detector236if applicable, and further processed by receive processor238to obtain decoded data and control information sent by UE115. Receive processor238may provide the decoded data to data sink239and the decoded control information to controller/processor240. Controllers/processors240and280may direct the operation at base station105and UE115, respectively. Controller/processor240and/or other processors and modules at base station105and/or controller/processor28and/or other processors and modules at UE115may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution illustrated inFIGS.11and12, and/or other processes for the techniques described herein. Memories242and282may store data and program codes for base station105and UE115, respectively. Scheduler244may schedule UEs for data transmission on the downlink and/or uplink. Wireless communications systems operated by different network operating entities (e.g., network operators) may share spectrum. In some instances, a network operating entity may be configured to use an entirety of a designated shared spectrum for at least a period of time before another network operating entity uses the entirety of the designated shared spectrum for a different period of time. Thus, in order to allow network operating entities use of the full designated shared spectrum, and in order to mitigate interfering communications between the different network operating entities, certain resources (e.g., time) may be partitioned and allocated to the different network operating entities for certain types of communication. For example, a network operating entity may be allocated certain time resources reserved for exclusive communication by the network operating entity using the entirety of the shared spectrum. The network operating entity may also be allocated other time resources where the entity is given priority over other network operating entities to communicate using the shared spectrum. These time resources, prioritized for use by the network operating entity, may be utilized by other network operating entities on an opportunistic basis if the prioritized network operating entity does not utilize the resources. Additional time resources may be allocated for any network operator to use on an opportunistic basis. Access to the shared spectrum and the arbitration of time resources among different network operating entities may be centrally controlled by a separate entity, autonomously determined by a predefined arbitration scheme, or dynamically determined based on interactions between wireless nodes of the network operators. In some cases, UE115and base station105may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) frequency spectrum. In an unlicensed frequency portion of the shared radio frequency spectrum band, UEs115or base stations105may traditionally perform a medium-sensing procedure to contend for access to the frequency spectrum. For example, UE115or base station105may perform a listen before talk (LBT) procedure such as a clear channel assessment (CCA) prior to communicating in order to determine whether the shared channel is available. A CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that a channel is occupied. Specifically, signal power that is concentrated in a certain bandwidth and exceeds a predetermined noise floor may indicate another wireless transmitter. A CCA also may include detection of specific sequences that indicate use of the channel. For example, another device may transmit a specific preamble prior to transmitting a data sequence. In some cases, an LBT procedure may include a wireless node adjusting its own backoff window based on the amount of energy detected on a channel and/or the acknowledge/negative-acknowledge (ACK/NACK) feedback for its own transmitted packets as a proxy for collisions. Bandwidth parts (BWPs) may be used in a variety of arrangements or manners in various communication scenarios. BWPs can be used to enable flexibility in how resources are assigned (e.g., in a given carrier). BWPs may vary in size and structure. As one example, a BWP may be a subset of contiguous common physical resource blocks (PRBs) of a component carrier in which multiple, different signal types can be sent. In other scenarios, one or more BWPs may be arranged in a spaced out or non-contiguous manner. Generally BWPs can enable multiplexing of different signals and signal types, such as for better utilization and adaptation of spectrum and UE power. BWPs may also have a variety of operational characteristics. For example, each BWP may be defined with one or more of its own numerology, frequency location, bandwidth size, and control resource set (CORESET). In some scenarios, additionally or alternatively, BWPs can be configured differently and/or uniquely with its own signal characteristic(s). Generally, one defined BWP may be active in the uplink and one defined BWP may be active in the downlink at a given time. Also in some instances, for an activated cell, there is an active downlink BWP for the downlink carrier and an active uplink BWP for the uplink carrier. The active BWP can be one of the defined BWPs, and the base station can switch the active BWP to another defined BWP (e.g., timer-based, downlink control information (DCI) based, or radio resource control (RRC) signaling). Wireless devices (e.g., one or more of UEs115and/or base station105) of wireless network100may operate in half duplex mode or full duplex mode.FIGS.3A-3Cillustrate various configurations of full duplex modes in a single component carrier as may be utilized by wireless communication stations of 5G network100. Correspondingly,FIG.3Dillustrates a configuration of a half duplex mode as may be utilized by wireless communication stations of 5G network100. It should be appreciated thatFIGS.3A-3Dpresent examples with respect to duplex mode configurations that may be utilized and are not intended to be limiting with respect to the particular duplex mode configurations that may be utilized by wireless communication stations that may implement full duplex operation according to concepts of the disclosure. As can be seen inFIGS.3A-3C, uplink signals301of the full duplex modes overlap downlink signals302in time. That is, in these examples, a wireless communication station implementing a full duplex mode with respect to wireless communications transmits and receives at the same time. In contrast, a wireless communication station implementing a half duplex mode of the example ofFIG.3Dtransmits and receives at different times. Accordingly, uplink signal311of the example half duplex mode shown inFIG.3Ddoes not overlap downlink single312in time. Various configurations may be utilized with respect to a full duplex mode, as represented by the examples ofFIGS.3A-3C. For example,FIGS.3A and3Bshow examples of in-band full duplex, wherein uplink signals301of the full duplex modes overlap downlink signals302in time and frequency. That is the uplink signals and downlink signals at least partially share the same time and frequency resource (e.g., full or partial overlap of the uplink and downlink signals in the time and frequency domains). In another configuration of a full duplex mode,FIG.3Cshows an example of sub-band full duplex, wherein uplink signal301of the full duplex mode overlaps downlink signal302in time, but not in frequency. That is the uplink signals and downlink signals at least partially share the same time resource (e.g., full or partial overlap of the uplink and downlink signals in the time domain), but do not share the same frequency resource. In the example illustrated inFIG.3C, uplink signal301and downlink signal302are separated in the frequency domain by guard band303(e.g., a relatively narrow amount of frequency spectrum separating the frequency band occupied by the uplink and downlink signals). FIGS.4A-4Cillustrate example instances of the use of full and half duplex modes in wireless communications. It should be appreciated thatFIGS.4A-4Crepresent a portion of 5G network100selected for illustrating the use of full and half duplex modes and that the particular base stations and UEs depicted are not intended to be limiting with respect to the various wireless communication stations that may implement the various duplex modes according to concepts of the disclosure. In the example ofFIG.4A, base station105dis operating in a full duplex mode while UEs115cand115dare operating in a half duplex mode. In this example, base station105dreceives uplink signal401from UE115dand transmits downlink signal402to UE115cusing a shared time resource (e.g., simultaneous downlink and uplink transmission), and possibly a shared frequency resource. In the example ofFIG.4B, base station105dand UE115care each operating in a full duplex mode. In this example, UE115ctransmits uplink signal401and receives downlink signal402using a shared time resource (e.g., simultaneous downlink and uplink transmission), and possibly a shared frequency resource. In the example ofFIG.4C, UE115cis operating in a full duplex mode (e.g., implementing a multiple transmission and reception (multi-TRP) architecture). As with the example ofFIG.4B, UE115ctransmits uplink signal401and receives downlink signal402using a shared time resource (e.g., simultaneous downlink and uplink transmission), and possibly a shared frequency resource. BWP configurations supporting full duplex operation are defined according to embodiments of the present disclosure. Full duplex frequency-based BWP configurations may, for example, be configured as a subset of defined BWP resources for supporting full duplex operation by base stations (e.g., supporting full duplex communications in the examples ofFIGS.4A and4B) and/or UEs (e.g., supporting full duplex communications in the examples ofFIGS.4B and4C). Transition between configurations and modes (e.g., between full duplex frequency-based BWP configurations, between half duplex and full duplex modes, etc.) is managed according to embodiments to avoid periods in which a communication device cannot perform any uplink or downlink transmissions due to switching between defined BWP configurations, or otherwise reduces BWP switching time. In operation of wireless communication within wireless network100, some communication frame time slots can be designated as full duplex and others can be designated as half duplex. For half duplex slots, the downlink and uplink transmissions may be timewise non-overlapping (e.g., occur separated in time, like TDD operation). Component carrier bandwidth may thus be allocated for either downlink or uplink communications with respect to a half duplex time slot. For full duplex slots, the downlink and uplink transmissions may overlap in time (e.g., occur simultaneously, like FDD operation). Component carrier bandwidth may thus be divided into portions for downlink and uplink communications with respect to a full duplex time slot. In accordance with some aspects of the disclosure, full duplex frequency-based BWP configurations can provide one or more active BWPs. For example, in some scenarios, these configurations may provide two active BWPs (e.g., one for the downlink and one for the uplink). The configurations for BWPs may be provided for any particular time slot or symbol. As described above, full duplex operation according to embodiments enables and supports downlink and uplink transmissions overlapping in time (e.g., simultaneous downlink and uplink transmissions). Accordingly, the full duplex frequency-based BWP configurations of embodiments implement one or more constraints with respect to the bandwidth and frequency location, such as to define non-overlapping portions of BWP frequency resources and/or one or more guard bands. Embodiments of the present disclosure provide for full duplex frequency-based BWP configurations that include a plurality BWPs, comprising a subset of bandwidth of a corresponding defined BWP, that are usable for full duplex operation. Defined BWPs (e.g., legacy downlink and uplink half duplex BWPs) can be situated in various arrangements with respect to each other. In some scenarios, BWPs may be overlapping or non-overlapping with respect to frequency and/or time.FIGS.5A and5Billustrate examples of overlapping bandwidth with respect to defined BWPs. In the examples, downlink BWP501and uplink BWP502are defined so as to comprise a common portion (overlap551) of the component carrier bandwidth. The bandwidth overlap with respect to the defined BWPs may be partial, as shown inFIG.5A(e.g., overlap551ais less than the bandwidth of at least one of downlink BWP501aand uplink BWP502a). Alternatively or additionally, the bandwidth overlap with respect to the defined BWPs may be full, as shown inFIG.5B(e.g., overlap551bis the full bandwidth of downlink BWP501band uplink BWP502b).FIGS.5C and5Dillustrate examples of non-overlapping bandwidth with respect to defined BWPs. In the examples, downlink BWP501and uplink BWP502are defined so as to comprise no common portions of the component carrier bandwidth. The non-overlapping bandwidth with respect to the defined BWPs may be non-contiguous, as shown inFIG.5C(e.g., having gap552between the bandwidth of downlink BWP501cand the bandwidth of uplink BWP502c). Alternatively, the non-overlapping bandwidth with respect to the defined BWPs may be contiguous, as shown inFIG.5D(e.g., having no gap between the bandwidth of downlink BWP501dand the bandwidth of uplink BWP502d). Irrespective of the particular configuration of defined BWPs (e.g., partially overlapping uplink/downlink BWPs, fully overlapping uplink/downlink BWPs, non-contiguous non-overlapping uplink/downlink BWPs, or contiguous non-overlapping uplink/downlink BWPs), usable BWPs of a full duplex frequency-based BWP configuration may be defined according to embodiments of the present disclosure. These variable and varied configuration types can provide a subset of bandwidth of corresponding defined BWPs supporting full duplex operation of a full duplex frequency-based BWP configuration. Accordingly, BWPs comprising bandwidth and frequency location constrained subsets of resources from active downlink half duplex and uplink half duplex defined BWPs can be used simultaneously (e.g., in the same time slot, the same symbol, etc.) for full duplex operation of a full duplex frequency-based BWP configuration. In providing a full duplex frequency-based BWP configuration according to some aspects of the disclosure, the full duplex usable bandwidth (e.g., subsets of BWP resources) is selected from one or more defined BWPs (e.g., legacy uplink and downlink BWPs) for full duplex operation. In accordance with some embodiments, the usable bandwidth selected for a full duplex frequency-based BWP configuration can be segmented (e.g., one or more segments which are disjoint in frequency). When operating in a full duplex slot, symbol, or other epoch, a communication device may operate in the usable bandwidth of a full duplex frequency-based BWP configuration corresponding to active uplink and downlink defined BWPs. FIGS.6A and6Bshow examples of usable bandwidth for full duplex operation selected from defined downlink and uplink BWPs. In the example ofFIG.6A, the defined downlink half duplex and uplink half duplex BWPs are overlapping in frequency and the usable bandwidth for a full duplex frequency-based BWP configuration is selected as non-overlapping subsets of bandwidth of the defined downlink and uplink BWPs. In the example ofFIG.6B, the defined downlink and uplink BWPs are non-overlapping in frequency and the usable bandwidth for a full duplex frequency-based BWP configuration is selected as subsets of bandwidth of the defined downlink and uplink BWPs, as will be discussed further below. Referring first to the example ofFIG.6A, usable bandwidth is selected as BWP612in defined downlink half duplex BWP610(e.g., a legacy downlink BWP). As shown, BWP612has segments comprising upper frequency BWP612aas a first segment and lower frequency BWP612bas a second segment. Also, usable bandwidth is selected as BWP622in defined uplink half duplex BWP620(e.g., a legacy uplink BWP). As can be seen inFIG.6A, the bandwidths of BWP612and BWP622are selected so as to be non-overlapping in frequency. In accordance with aspects of the present disclosure, BWPs of full duplex frequency-based BWP configurations may be variously selected subsets of corresponding defined BWPs. For example, the frequencies, bandwidth, etc. of the BWPs of a full duplex frequency-based BWP configuration may be selected as appropriate for any scenario. It should be appreciated that, although both BWP612and BWP622of the example are each bandwidth subsets of a corresponding defined half duplex BWP, the BWPs of a full duplex frequency-based BWP configuration of some embodiments may comprise the full bandwidth of a corresponding defined BWP (e.g., in a situation where the defined BWPs are partially overlapping). Generally, these approaches and other configurations may occur so long as appropriate constraints with respect to bandwidth concerns, timing alignments, and frequency locations are met (e.g., the BWPs of a full duplex frequency-based BWP configuration are non-overlapping, guard band needs are satisfied, etc.). Moreover, as shown by the example of BWP612inFIG.6A, the bandwidth of a BWP of a full duplex frequency-based BWP configuration may be segmented (e.g., comprising upper frequency BWP612aas a first segment and lower frequency BWP612bas a second segment). The number of segments, the bandwidth of the segments, the bandwidth spacing, etc. of a particular segmented BWP may be configured based upon various aspects of the communications, such as the uplink and/or downlink data traffic, the number of communication devices engaged in the full duplex communications, guard band needs, etc. In accordance with some aspects of the disclosure, the BWPs accommodate full duplex frequency-based BWP configurations in which center frequencies of the uplink and downlink BWPs are not aligned (i.e., center frequency alignment is not provided). Bandwidth and frequency location constraints implemented with respect to BWP configurations supporting full duplex operation of embodiments provide for defining one or more guard bands between BWPs of a full duplex frequency-based BWP configuration. As an example, guard band630is defined in the example ofFIG.6Ato provide instances of bandwidth, disposed between the uplink and downlink BWPs of the full duplex frequency-based BWP configuration, that remain unused for uplink/downlink communications. In the example ofFIG.6A, BWP612for the downlink is segmented. The guard band630is provided to include guard band630aand guard band630bseparating BWP612from BWP622in the frequency domain. The bandwidth of guard bands may comprise a frequency band determined to facilitate adequate isolation (e.g., uplink/downlink interference below a predetermined threshold level). Guard band format and size may vary according to aspects of the present disclosure. In some scenarios, guard bands can be sized and/or spaced apart to enable full duplex communication using concurrent communications via an uplink BWP and a downlink BWP of a full duplex frequency-based BWP configuration. The bandwidth of a particular guard band may, for example, vary based upon attributes such as the frequencies of the corresponding uplink and downlink communications, the amount of isolation desired, the sub-carrier spacing of the uplink and downlink BWPs, the time difference between the start of uplink and downlink signals, the particular channels to be carried in the BWPs, etc. The determination of the bandwidth of guard bands630of embodiments may depend on the UE capabilities to suppress the self-interference from its uplink transmission to the downlink reception and on the UE uplink transmit power. In most scenarios, the measured power of the residual self-interference (i.e., after UE mitigation of the self-interference) is to be lower than a specified threshold such that the UE can perform proper downlink reception. Referring now to the example ofFIG.6B, usable bandwidth is selected as BWP612in defined downlink half duplex BWP610(e.g., a legacy downlink BWP). Also, usable bandwidth is selected as BWP622in defined uplink half duplex BWP620(e.g., a legacy uplink BWP). As can be seen inFIG.6A, the bandwidths of defined downlink half duplex BWP610and defined uplink half duplex BWP620are non-overlapping, however BWPs612and622of the full duplex frequency-based BWP configuration are selected subsets of the corresponding defined half duplex BWPs. For example, the usable bandwidth of the full duplex frequency-based BWP configuration may be configured to satisfy guard band needs using a bandwidth subset of either or both of the defined half duplex BWPs. In the example ofFIG.6B, although gap652is present between the bandwidth of defined downlink half duplex BWP610and the bandwidth of defined uplink half duplex BWP602, gap652may comprise insufficient bandwidth for use as a guard band. Accordingly, BWP622in defined uplink half duplex BWP620may be selected as a subset of the defined BWP bandwidth to provide guard band630which combined with gap652satisfies one or more guard band need. In accordance with aspects of the present disclosure, the BWPs of a full duplex frequency-based BWP configuration may be as large as the defined BWPs (e.g., legacy downlink and uplink BWPs), or may be some sub-portion thereof. Such subletting of the BWPs of a full duplex frequency-based BWP configuration facilitates fast adaptation between legacy TDD slots and FD slots of embodiments, where minimal impact to RF retuning and baseband processing is needed. FIG.7illustrates an example in which a full duplex frequency-based BWP configuration in accordance with concepts of the present disclosure is implemented via full duplex operation. In particular,FIG.7shows the use of various different BWP configurations (shown as BWP configurations701,702, and703) over time (shown as time slots N, N+1, N+2, and N+3). Although the example ofFIG.7illustrates a time aspect as comprising time slots (e.g., communication frame time slots), a time aspect of the BWP configurations of embodiments herein may comprise any suitable epoch (e.g., slot, symbol, etc.). BWP configuration701comprises half duplex frequency-based BWP711including full bandwidth of a corresponding defined BWP. In some scenarios, legacy downlink BWP configuration parameters of an active downlink BWP may be defined. As shown, in some examples, defined BWPs may be for a component carrier being allocated for half duplex downlink communication at slot N. Similarly, BWP configuration702of the example ofFIG.7comprises half duplex frequency-based BWP721including the full bandwidth of a corresponding defined BWP (e.g., legacy uplink BWP configuration parameters of an active downlink BWP) for a component carrier being allocated for half duplex uplink communication at slot N+3. In contrast, BWP configuration703comprises a full duplex frequency-based BWP configuration including BWP712and BWP722(e.g., as may correspond to the example ofFIG.6A). BWP712of the example inFIG.7includes a subset of the corresponding defined BWP (e.g., subset of the frequency resources of the active downlink half duplex BWP) for a component carrier being allocated for downlink communication of full duplex communications at slots N+1 and N+2. Correspondingly, BWP722includes a subset of the corresponding defined BWP (e.g., subset of the frequency resources of the active uplink BWP) for a component carrier being allocated for uplink communications of full duplex communications at slots N+1 and N+2. Using constraints with respect to the bandwidth and frequency location implemented in BWP712and BWP722of half duplex BWP configuration730, non-overlapping portions of BWP frequency resources are defined for supporting full duplex operation in which downlink and uplink transmissions overlap in time (e.g., simultaneous downlink and uplink transmissions). As shown in the example ofFIG.7, a wireless device using full duplex frequency-based BWP configurations of embodiments may transition between full duplex operation and half duplex operation. Transitions may be based on a duplexing nature of a respective slot or symbol. Transition of resources can occur using different resources of the active uplink and/or downlink defined BWPs. A wireless device may additionally or alternatively transition between full duplex operation according to a first full duplex frequency-based BWP configuration and a second full duplex frequency-based BWP configuration. BWP configurations can correspond to active uplink and downlink defined BWPs (e.g., where a plurality of uplink and downlink BWP pair sets, each including usable bandwidth selected from the active uplink and downlink defined BWPs for full duplex operation). Such intra defined BWP transitions avoids the BWP switching time which is often greater than 1 ms. That is, transitioning between full duplex operation and half duplex operation, as well as transitioning between different configurations of full duplex operation, may be accomplished with switching times of less than 1 ms according to some embodiments of the present disclosure. In accordance with aspects of the present disclosure, sets of uplink and downlink BWP pairs (e.g., BWP pairs for different full duplex frequency-based BWP configurations) may be provided to support various communication modes. For example, a first uplink and downlink BWP pair set may comprise BWP712and BWP722providing the full duplex frequency-based BWP configuration of BWP configuration703shown inFIG.7supporting full duplex operation. A second uplink and downlink BWP set may comprise different selected BWPs (e.g., the BWPs ofFIG.6B, different BWPs selected from defined half duplex downlink BWP610and defined uplink half duplex BWP620ofFIG.6A, etc.) providing a different full duplex frequency-based BWP configuration also supporting full duplex operation. In accordance with embodiments, a plurality of uplink and downlink BWP pair sets providing full duplex frequency-based BWP configurations are configured to satisfy frequency domain aspects (e.g., bandwidth and frequency) for full duplex operation. Other uplink and downlink BWP pair sets may, however, be configured for half duplex operation. For example, a third uplink and downlink BWP set may comprise a BWP including the full bandwidth of a corresponding defined BWP (e.g., half duplex frequency-based BWP711or BWP712ofFIG.7) while the other BWP of the set provides a null bandwidth. Accordingly, sets of uplink and downlink BWP pairs may be provided for various combinations of full duplex and/or half duplex operation. A plurality of sets of uplink and downlink BWP pairs may be provided with respect to different defined downlink and uplink BWPs. For example, a first set of uplink and downlink BWP pairs may be provided for first active defined downlink and uplink BWPs (e.g., active downlink BWP810aand active uplink BWP820aofFIG.8) while a second set of uplink and downlink BWP pairs may be provided for second active defined downlink and uplink BWPs (e.g., active downlink BWP810band active uplink BWP820bofFIG.8). Embodiments may utilize BWP switching methodology (e.g., BWP switching801ofFIG.8) in switching between the different sets of uplink and downlink BWP pairs, such as to switch between half duplex and full duplex operation or even to switch between different configurations of full duplex operation. Additionally or alternatively, a plurality of sets of uplink and downlink BWP pairs may be provided with respect to a particular defined downlink and uplink BWPs. For example, a first set of uplink and downlink BWP pairs and a second set of uplink and downlink BWP pairs may be provided for a defined downlink and uplink BWPs (e.g., active downlink BWP910and active uplink BWP920ofFIG.9). Implicit BWP switching based on the duplexing nature of the time slots and/or symbols may be utilized in switching between half duplex and full duplex operation or even in switching between different configurations of full duplex operation using the different sets of uplink and downlink BWP pairs of the active defined downlink and uplink BWPs.FIG.9, for example, illustrates implicit BWP switching between different full duplex frequency-based BWP configurations for switching between different configurations of full duplex operation. As should be understood from the foregoing, various options for determining the BWP to switch to for implicit BWP switch may be provided. For example, multiple sets of uplink and downlink BWP pairs for active BWPs may be defined for different duplexing modes (e.g., one or more sets of uplink and downlink BWP pairs for half duplex slots, one or more sets of uplink and downlink BWP pairs for full duplex slots, etc.). When transitioning between half duplex and full duplex slots, or when transitioning between full duplex slots having different uplink/downlink configurations, the active BWP implicitly changes to the corresponding set of uplink and downlink BWP pairs. As another example, active uplink and downlink BWP pairs may be expanded from a set of downlink and uplink half duplex frequency-based BWPs (e.g., {DL, UL}) to a set also including a downlink half duplex frequency-based BWP and an uplink half duplex frequency-based BWP (e.g., {DL-HD, UL-HD, DL-FD, UL-FD}). In this example, additionally and/or alternatively, an associated active downlink and uplink BWP supporting full duplex operation may be used when transitioning to a full duplex slot or symbol. Implicit BWP switching provided according to embodiments of the disclosure facilitates a relaxation of (i.e. faster) BWP switching delay, and thus may be utilized to improve the switch latency. Moreover, BWP configurations can be configured to support disjoint frequency ranges within a BWP, an excluded frequency range within the BWP for full duplex operation, etc. FIG.10Aillustrates an example in which BWP portions of a full duplex frequency-based BWP configuration are allocated to multiple UEs. In the example ofFIG.10A, a full duplex frequency-based BWP configuration is used with respect to wireless devices operating in a combination of full duplex and half duplex operation. For example, a base station may operate in full duplex mode while some or all of the UEs are only half duplex capable. The base station (or network node) can adjust and/or tailor its operations in light of UE capabilities.FIG.10Ashows the use of various different BWP configurations (shown as BWP configurations1001,1002, and1003) over time (shown as time slots N, N+1, N+2, and N+3) where the base station operates in full duplex mode while serving three UEs (UE1, UE2, and UE3) operating in half duplex mode. Each of the illustrated BWP configurations (1001,1002, and1003) have a number of formats and features. As one example, BWP configuration1001comprises half duplex frequency-based BWP1011. As illustrated, BWP configuration1001includes the full bandwidth of a corresponding defined BWP for a component carrier, and thus may be allocated to one or more UEs for half duplex downlink communication at slot N. Similarly, BWP configuration1002of the example ofFIG.10Acomprises half duplex frequency-based BWP1021. BWP configuration1002may include the full bandwidth of a corresponding defined BWP for a component carrier, and thus may be allocated to one or more UEs for half duplex uplink communication at slot N+3. BWP configuration1003, however, comprises a full duplex frequency-based BWP configuration including BWP1012and BWP1022. The BWPs of BWP configuration1003may be allocated to different ones of the UEs for their use in half duplex communication at slots N+1 and N+2. BWP configuration1003includes both uplink and downlink BWPs (uplink BWP1022and downlink BWP1012), and thus the base station may operate in a full duplex mode despite the individual UEs operating in half duplex mode. In the illustrated example of BWP configuration1003, BWP1022includes a subset of the corresponding defined BWP (e.g., subset of the frequency resources of the active uplink BWP) for a component carrier being allocated to UE3 for uplink communications. Further, in the illustrated example of BWP configuration1003, BWP1021includes a subset of the corresponding defined BWP (e.g., subset of the frequency resources of the active downlink BWP) for a component carrier being allocated for downlink communication. In this example, the bandwidth of BWP1021is segmented. A first segment comprising upper frequency BWP1012ais allocated to UE2 for downlink communications and a second segment comprising lower frequency BWP1012bis allocated to UE1 for downlink communications. Accordingly, BWP portions of the full duplex frequency-based BWP configuration of BWP configuration1003are allocated to different UEs, including portions for different link directions (e.g., uplink/downlink) being allocated to different UEs and portions for a same link direction (e.g., downlink, as shown, or uplink) being allocated to different UEs. Although the example ofFIG.10Ais described with reference to BWP1021being segmented as upper frequency BWP1012aand lower frequency BWP1012b, multiple independent BWPs having disjoint frequency bands may be provided according to some embodiments. Moreover, a BWP need not be segmented, or multiple independent BWPs need not be provided, in order to support allocation of portions of the full duplex frequency-based BWP configuration to different UEs for a same link direction. That is, portions within a contiguous bandwidth of a half duplex frequency-based BWP may be allocated to different UEs, or other wireless communication devices in some implementations. Continuing with the example ofFIG.10A, it can be seen that changing the slot/symbol format from half duplex to full duplex, or vice versa, may have an effect on the BWP of the half duplex UE. In accordance with some aspects, the UEs may be configured using slot configurations (e.g., a selected slot configuration from a set of different predefined half-duplex slot configurations {HD1, HD2, HD3, . . . }, or the UEs may be dynamically signaled with respect to slot/symbol format changes. UE communication operation may, for example, be defined with BWP sets that include UL/DL BWP configurations corresponding to the different HD slots configuration. In the example ofFIG.10A, the communication operation with respect to UE1, UE2, and UE3 may be configured as follows:UE1={DL-HD1=100 MHz, UL-HD1=100 Mhz, DL-HD2=40 MHz lower, UL-HD2=Null, . . . }UE2={DL-HD1=Null, UL-HD1=100 Mhz, DL-HD2=40 MHz upper, UL-HD2=Null, . . . }UE3={DL-HD1=Null, UL-HD1=100 Mhz, DL-HD2=null, UL-HD2=20 MH center, . . . } When there is a transition between HD1 and HD2 slots, the UE may change the active BWP implicitly to UL-HD2 and DL-HD2 within the BWP set. FIG.10Billustrates another example in which BWP portions of a full duplex frequency-based BWP configuration are allocated to multiple UEs. In the example ofFIG.10B, a full duplex frequency-based BWP configuration is used with respect to UEs operating in a combination of full duplex and half duplex operation. For example, in addition to a base station operating in full duplex mode, a full duplex capable UE (shown as UE2 in time slots N+1 and N+2) is operating in full duplex mode. A UE that is only half duplex capable (shown as UE1 in time slots N, N+1, and N+2) is operating in half duplex mode, as does the full duplex capable UE when operating with respect to a half duplex BWP configuration (shown as UE2 in time slot N+3), in the illustrated example. In some aspects of the disclosure, a half duplex BWP configuration (e.g., legacy downlink and/or uplink BWPs of a defined BWP) may be designated as a default BWP configuration to be used by wireless devices of wireless network100. For example, a BWP timer (e.g., inactivity timer) may be utilized with respect to BWP configuration assignments such that, when the BWP timer expires, a UE may default to operation in half duplex mode. If a slot/symbol is full duplex (e.g., implementing a full duplex frequency-based BWP configuration), a UE operating in defaulted half duplex mode may assume that the slot/symbol is a half duplex slot/symbol, or skip the slot. Transition from current active BWP to a default BWP may follow various procedures. For example, if the current active BWP configuration is in full duplex, a wireless device may transition the current active BWP configuration to half duplex, and thereafter the wireless device may transition to the default BWP configuration in half duplex. In another example, if the current active BWP configuration is in full duplex, a wireless device may transition the current active BWP configuration to the default BWP in full duplex, and thereafter the wireless device may transition to the default BWP configuration in half duplex. In the foregoing examples, separate or same inactivity timer values for a BWP timer may be utilized for the transition steps. In yet another example, if the current active BWP configuration is in full duplex, a wireless device may transition the current active BWP configuration to the default BWP configuration in half duplex. FIG.11is a block diagram illustrating example blocks executed by a wireless communication device, such as base station105, to implement aspects of the present disclosure. The example blocks will also be described with respect to base station105as illustrated inFIG.13.FIG.13is a block diagram illustrating base station105configured according to one aspect of the present disclosure. Base station105includes the structure, hardware, and components as illustrated for base station105ofFIG.2. For example, base station105includes controller/processor240, which operates to execute logic or computer instructions stored in memory242, as well as controlling the components of base station105that provide the features and functionality of base station105. Base station105, under control of controller/processor240, transmits and receives signals via wireless radios1300a-tand antennas234a-t. Wireless radios1300a-tinclude various components and hardware, as illustrated inFIG.2for base station105, including modulator/demodulators232a-t, MIMO detector236, receive processor238, transmit processor220, and TX MIMO processor230. In the example operation of flow1100ofFIG.11, base station105provides a first full duplex frequency-based BWP configuration. For example, FD frequency-based configuration logic1302shown inFIG.13may provide selection of usable bandwidth (e.g., subsets of BWP resources) from one or more defined BWPs (e.g., legacy uplink and downlink half duplex BWPs defined by respective sets of BWP configuration parameters of BWP configuration parameters1303) to define the first FD frequency-based BWP configuration for full duplex operation, at block1101. The first FD frequency-based BWP configuration may include a plurality of BWPs. Individual BWPs of the plurality of BWPs may comprise a subset of bandwidth, of a corresponding defined BWP, configured for full duplex operation (e.g., a subset of bandwidth of the defined BWP that is usable for full duplex operation selected as non-overlapping subsets of bandwidth of the defined downlink and uplink BWPs). One or more sets of BWP configuration parameters defining the first full duplex frequency-based BWP configuration and/or individual BWPs thereof may be stored as BWP configuration parameters of BWP configuration parameters1303. At block1102of flow1100, base station105assigns the first full duplex frequency-based BWP configuration to configure one or more communications devices for communication during the full duplex operation. For example, scheduler244of base station105may allocate some or all of the individual BWPs of the first full duplex frequency-based BWP configuration to one or more UE of UEs115. The full duplex operation may, for example, provide for base station105operating in a full duplex mode while one or more UEs are operating in a half duplex mode (e.g., as shown inFIG.4A), base station105and a UE each operating in a full duplex mode (e.g., as shown inFIG.4B), a UE operating in a full duplex mode with one or more base stations of base stations105, etc. FIG.12is a block diagram illustrating example blocks executed by a wireless communication device, such as UE115, to implement aspects of the present disclosure. The example blocks will also be described with respect to UE115as illustrated inFIG.14.FIG.14is a block diagram illustrating UE115configured according to one aspect of the present disclosure. UE115includes the structure, hardware, and components as illustrated for UE115ofFIG.2. For example, UE115includes controller/processor280, which operates to execute logic or computer instructions stored in memory282, as well as controlling the components of UE115that provide the features and functionality of UE115. UE115, under control of controller/processor280, transmits and receives signals via wireless radios1400a-rand antennas252a-r. Wireless radios1400a-rinclude various components and hardware, as illustrated inFIG.2for UE115, including modulator/demodulators254a-r, MIMO detector256, receive processor258, transmit processor264, and TX MIMO processor266. In the example operation of block1201of flow1200ofFIG.12, UE115obtains a first full duplex frequency-based BWP. For example, FD frequency-based configuration logic1302of UE115may be configured for various BWP configurations via DCI provided by base station105. The DCI may include BWP configuration parameters for one or more BWP configuration, identify a BWP configuration (e.g., stored in BWP configuration parameters1303), etc., as may be used by FD frequency-based configuration logic1302to configure UE115for communication during full duplex operation. The first full duplex frequency-based BWP configuration may include a plurality of BWPs. Individual BWPs of the plurality of BWPs may comprise a subset of bandwidth, of a corresponding defined BWP (e.g., legacy uplink and downlink half duplex BWPs defined by respective sets of BWP configuration parameters of BWP configuration parameters1403), configured for full duplex operation (e.g., a subset of bandwidth of the defined BWP that is usable for full duplex operation selected as non-overlapping subsets of bandwidth of the defined downlink and uplink BWPs). One or more sets of BWP configuration parameters defining the first full duplex frequency-based BWP configuration and/or individual BWPs thereof may be stored as BWP configuration parameters of BWP configuration parameters1403. At block1202of1200, UE115communicates during the full duplex operation using a first one or more BWPs of the first full duplex frequency-based BWP configuration. For example, FD frequency-based configuration logic1402may configure UE115to communicate with a base station using one or more individual BWP of the first full duplex frequency-based BWP, such as during full duplex operation. The full duplex operation may, for example, provide for a base station operating in a full duplex mode while UE115is operating in a half duplex mode (e.g., as shown inFIG.4A), a base station and UE115each operating in a full duplex mode (e.g., as shown inFIG.4B), UE115operating in a full duplex mode with one or more base stations, etc. Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. The functional blocks and modules described herein (e.g., the functional blocks and modules inFIG.2) may comprise processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof. In addition, features discussed herein relating to implementing a full duplex frequency-based BWP configuration may be implemented via specialized processor circuitry, via executable instructions, and/or combinations thereof. Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps (e.g., the logical blocks inFIGS.11and12) described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. Skilled artisans will also readily recognize that the order or combination of components, methods, or interactions that are described herein are merely examples and that the components, methods, or interactions of the various aspects of the present disclosure may be combined or performed in ways other than those illustrated and described herein. The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Computer-readable storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, a connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL), then the coaxial cable, fiber optic cable, twisted pair, or DSL, are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), hard disk, solid state disk, and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. As used herein, including in the claims, the term “and/or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, and/or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination. Also, as used herein, including in the claims, “or” as used in a list of items prefaced by “at least one of” indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any of these in any combination thereof. The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. | 74,237 |
11943757 | DETAILED DESCRIPTION Embodiments will be described below in detail with reference to the accompanying drawings. FIG.1illustrates a configuration of base station100according to an example embodiment. Base station100divides a plurality of subcarriers comprised of an OFDM symbol, which is a multicarrier signal, into a plurality of RBs and uses Dch and Lch for each RB of the plurality of RBs. Furthermore, one of Dch and Lch is allocated to one mobile station in the same subframe. Base station100is provided with n (n is the number of mobile stations (MSs) with which base station100can communicate) encoding/modulation sections101-1to101-neach comprising encoding section11and modulation section12for Dch data, n encoding/modulation sections102-1to102-neach comprising encoding section21and modulation section22for Lch data and n demodulation/decoding sections115-1to115-neach comprising demodulation section31and decoding section32. In encoding/modulation sections101-1to101-n, encoding section11performs encoding processing using a turbo code or the like on Dch data #1 to #n for each of mobile stations #1 to #n and modulation section12performs modulation processing on the encoded Dch data to thereby generate a Dch data symbol. In encoding/modulation sections102-1to102-n, encoding section21performs encoding processing using a turbo code or the like on Lch data #1 to #n for each of mobile stations #1 to #n and modulation section22performs modulation processing on the encoded Lch data to thereby generate an Lch data symbol. The coding rate and modulation scheme in this case follows MCS (Modulation and Coding Scheme: MCS) information inputted from adaptive control section116. Allocation section103allocates the Dch data symbol and Lch data symbol to each subcarrier comprised of an OFDM symbol according to the control from adaptive control section116and outputs the OFDM symbol to multiplexing section104. In this case, allocation section103collectively allocates the Dch data symbols and Lch data symbols for each RB. Furthermore, when allocating the Lch data symbols, allocation section103groups the plurality of RBs into a plurality of groups and allocates Lchs in RB group units. Furthermore, when using a plurality of Dchs for the Dch data symbol of one mobile station, allocation section103uses Dchs with continuous channel numbers. Furthermore, allocation section103allocates the Dch data symbol to a plurality of RBs to which one Dch is mapped at intervals of an integer multiple of the number of RBs constituting one RB group. In each RB, the mapping positions of Dch and Lch are associated with each other in advance. That is, allocation section103stores a mapping pattern, which is the association between Dchs and Lchs, and RBs in advance and allocates the Dch data symbol and Lch data symbol to each RB according to the mapping pattern. Details of the Dch mapping method according to the present embodiment will be described later. Furthermore, allocation section103outputs allocation information of the Dch data symbol (information indicating which mobile station's Dch data symbol is allocated to which RB s) and allocation information of the Lch data symbol (information indicating which RB s are allocated to the Lch data symbol of which mobile station) to control information generation section105. For example, the allocation information of the Dch data symbol only includes the first channel number and the last channel number of the continuous channel numbers. Control information generation section105generates control information including the allocation information of the Dch data symbol, allocation information of the Lch data symbol and MCS information inputted from adaptive control section116and outputs the control information to encoding section106. Encoding section106performs encoding processing on the control information and modulation section107performs modulation processing on the encoded control information and outputs the control information to multiplexing section104. Multiplexing section104multiplexes each data symbol inputted from allocation section103with control information and outputs the multiplexing result to IFFT (inverse Fast Fourier Transform) section108. Multiplexing of control information is performed, for example, every subframe. According to the present embodiment, multiplexing of control information may be one of time domain multiplexing and frequency domain multiplexing. IFFT section108performs IFFT on a plurality of subcarriers comprised of a plurality of RBs to which control information and data symbol are allocated, to generate an OFDM symbol, which is a multicarrier signal. CP (Cyclic Prefix) adding section109adds the same signal as the last portion of the OFDM symbol to the head of the OFDM symbol as a CP. Radio transmitting section110performs transmission processing such as D/A conversion, amplification and up-conversion on the OFDM symbol with a CP and transmits the OFDM symbol from antenna111to each mobile station. On the other hand, radio receiving section112receives n OFDM symbols at the same time transmitted from maximum n mobile stations via antenna111and performs reception processing such as down-conversion, A/D conversion on these OFDM symbols. CP removing section113removes the CP from the OFDM symbol after the reception processing. FFT (Fast Fourier Transform) section114performs FFT on the OFDM symbol without a CP to obtain a signal for each mobile station multiplexed in the frequency domain. Here, the respective mobile stations transmit signals using subcarriers different from each other or RBs different from each other and a signal for each mobile station includes received quality information for each RB reported from each mobile station. Each mobile station can measure the received quality of each RB using received SNR, received SIR, received SINR, received CINR, received power, interference power, bit error rate, throughput and MCS or the like that can achieve a certain error rate. Furthermore, the received quality information may be expressed as “CQI” (Channel Quality Indicator), “CSI” (Channel State Information) and so on. In demodulation/decoding sections115-1to115-n, demodulation section31performs demodulation processing on the signal after the FFT and decoding section32performs decoding processing on the demodulated signal. The received data is thereby obtained. Of the received data, the received quality information is inputted to adaptive control section116. Adaptive control section116performs adaptive control over Lch data based on the received quality information for each RB reported from each mobile station. That is, for encoding/modulation sections102-1to102-n, adaptive control section116selects MCS whereby a required error rate can be satisfied for each RB group based on the received quality information for each RB and outputs the MCS information, and for allocation section103, adaptive control section116performs frequency scheduling to determine to which RB group Lch data #1 to #n should be allocated respectively using a scheduling algorithm such as a Max SIR method or Proportional Fairness method. Furthermore, adaptive control section116outputs MCS information for each RB group to control information generation section105. Next, the configuration of mobile station200according to the present embodiment is shown inFIG.2. Mobile station200receives a multicarrier signal, which is an OFDM symbol comprised of a plurality of subcarriers divided into a plurality of RBs, from base station100(FIG.1). Furthermore, Dch and Lch are used for each RB in a plurality of RBs. Furthermore, one of Dch and Lch is allocated to mobile station200in the same subframe. In mobile station200, radio receiving section202receives the OFDM symbol transmitted from base station100via antenna201and performs reception processing such as down-conversion or A/D conversion on the OFDM symbol. CP removing section203removes CP from the OFDM symbol after the reception processing. FFT section204performs FFT on the OFDM symbol without a CP to obtain a received signal in which control information and data symbols are multiplexed. Demultiplexing section205demultiplexes the received signal after the FFT into a control signal and data symbol. Demultiplexing section205then outputs the control signal to demodulation/decoding section206and outputs the data symbol to demapping section207. In demodulation/decoding section206, demodulation section41performs demodulation processing on the control signal and decoding section42performs decoding processing on the demodulated signal. Here, the control information includes Dch data symbol allocation information, Lch data symbol allocation information and MCS information. Demodulation/decoding section206then outputs the Dch data symbol allocation information and the Lch data symbol allocation information out of the control information to demapping section207. Demapping section207extracts the data symbol allocated to that mobile station from among the plurality of RB s to which data symbols inputted from demultiplexing section205are allocated based on the allocation information inputted from demodulation/decoding section206. In each RB, mapping positions of Dchs and Lchs are associated with each other in advance as with base station100(FIG.1). That is, demapping section207stores the same mapping pattern as that of allocation section103of base station100and extracts Dch data symbols and Lch data symbols from a plurality of RBs according to the mapping pattern. Furthermore, when extracting the Lch data symbol, demapping section207extracts Lchs in RB group units in which a plurality of RBs are grouped into a plurality of groups. Furthermore, as described above, when a plurality of Dchs are used for a Dch data symbol of one mobile station, allocation section103of base station100(FIG.1) uses Dchs with continuous channel numbers. Furthermore, the allocation information included in the control information from base station100indicates only the first channel number and the last channel number among the continuous channel numbers of Dchs used for the Dch data symbol. Thus, demapping section207specifies Dchs used for the Dch data symbol allocated to that mobile station based on the first channel number and the last channel number indicated in the allocation information. To be more specific, demapping section207identifies a plurality of continuous Dchs from the first channel number indicated in the allocation information to the last channel number indicated in the allocation information as Dchs used for the Dch data symbol allocated to that mobile station. Demapping section207then extracts the RB associated with the specified channel number of the identified Dch and outputs the data symbol allocated to the extracted RB to demodulation/decoding section208. In demodulation/decoding section208, demodulation section51performs demodulation processing on the data symbol inputted from demapping section207and decoding section52performs decoding processing on the demodulated signal. The received data is thereby obtained. On the other hand, in encoding/modulation section209, encoding section61performs encoding processing using a turbo code or the like on the transmission data and modulation section62performs modulation processing on the encoded transmission data to generate a data symbol. Here, mobile station200transmits transmission data using subcarriers or RBs different from those of other mobile stations and the transmission data includes receiving quality information for each RB. IFFT section210performs IFFT on a plurality of subcarriers comprised of a plurality of RBs to which data symbols inputted from encoding/modulation section209are allocated, to generate an OFDM symbol, which is a multicarrier signal. CP adding section211adds the same signal as the last portion of the OFDM symbol to the head of the OFDM symbol as a CP. Radio transmitting section212performs transmission processing such as D/A conversion, amplification and up-conversion on the OFDM symbol with a CP and transmits the OFDM symbol to base station100(FIG.1) from antenna201. Next, the Dch channel mapping method according to the present embodiment will be described. In the following explanations, a case will be described as an example of configuration where a plurality of subcarriers comprised of one OFDM symbol are uniformly divided into 14 RBs of RBs #1 to #14 as shown inFIG.3. Furthermore, Lch #1 to #14 or Dch #1 to #14 is formed with each RB and adaptive control section116controls channels used by each mobile station. Furthermore, Lchs are allocated to each mobile station in RB group units. Here, as shown inFIG.3, RBs #1 to #14 are grouped into RB groups RBGs #1 to #7. Here, suppose the number of RBs constituting one RB group (hereinafter referred to as “RB group size”) is 2. Therefore, as shown inFIG.3, Lch #1 and Lch #2 mapped to RB #1 and RB #2 constituting RBG1 are always allocated at the same time and Lch #3 and Lch #4 mapped to RB #3 and RB #4 constituting RBG2 are always allocated at the same time. The same applies to Lchs #5 to #14 constituting RBGs #3 to #7 respectively. Furthermore, the Lch configuration in each RB shown inFIG.3and the Dch configuration in each RB shown below are associated with each other in advance in allocation section103. Here, since frequency scheduling is performed on Lch in RB units, each RB used for Lch includes an Lch data symbol for only one mobile station. That is, one Lch corresponding to one mobile station is formed with one RB. Therefore, as shown inFIG.3, Lchs #1 to #12 are mapped to RBs #1 to #12 respectively. That is, the allocation unit of each Lch is “1 RB×1 subframe.” On the other hand, since frequency diversity transmission is carried out for Dch, RB used for Dch includes a plurality of Dch data symbols. Here, each RB used for Dch is temporally divided into two subblocks and different Dchs are mapped to each subblock. That is, a plurality of different Dchs are time-domain-multiplexed in 1 RB. Furthermore, one Dch is formed with two different RB subblocks. That is, the allocation unit of each Dch is “(1 RB×½ subframe)×2” and is the same as the allocation unit of each Lch. Mapping Method 1 (FIG.4) In the present mapping method, one Dch is mapped at intervals of an integer multiple of the RB group size for a plurality of RBs. That is, the RB interval Gap of RBs in which one Dch is mapped is given by following equation 1, [1] Gap=floor((Nrb/Nd)/RBGsize)·RBGsize (Equation 1) where Nrb is the number of all RBs, Nd is the number of subblocks into which one RB is divided and RBGsize is the RB group size. Next, the relational expression between the channel number of Dch and an RB number of RB in which the Dch is mapped is shown. Nd RB numbers (indexes) j in which Dch #k (k=1 to 12) are mapped are given by following equation 2. [2] j=(((k−1)+Gap·p)mod(Gap·Nd))+1,p=0,1, . . . ,Nd−1 (Equation 2) Here, since Nrb=14, Nd=2, RBGsize=2, RB interval Gap is 6 (=floor((14/2)/2)×2) according to equation 1. Therefore, equation 2 above is j=(((k−1)+6·p)mod 12)+1 (p=0, 1), where k=1, 2, . . . , 12. Thus, one Dch is mapped in a distributed manner to two RBs of RB #(k) and RB #(k+6) which are 6 RBs apart in the frequency domain. In other words, one Dch is distributedly mapped to RBs 6 RBs apart which is an integer multiple (here, three times) of the RB group size (RBGsize=2) in the frequency domain. This RB interval (RB interval 6) is a maximum interval equal to or below Nrb/Nd (=14/2) among intervals of integer multiples of the RB group size (RBGsize=2). To be more specific, as shown inFIG.4, Dchs #1 and #7 are mapped to RB #1 (RB #7), Dchs #2 and #8 are mapped to RB #2 (RB #8), Dchs #3 and #9 are mapped to RB #3 (RB #9), Dchs #4 and #10 are mapped to RB #4 (RB #10), Dchs #5 and #11 are mapped to RB #5 (RB #11) and Dchs #6 and #12 are mapped to RB #6 (RB #12). That is, according to the present mapping method, the maximum number of Dchs that allocation section103can allocate to RBs is 12. Next,FIG.5illustrates an allocation example in allocation section103(FIG.1) of base station100when four Dchs are allocated to a Dch data symbol of one mobile station. Here, for simplicity of explanation, Dch #1, #2, #7 and #8 are allocated so that no odd subblocks are produced in RBs used for Dchs. Furthermore, allocation section103stores the Dch mapping pattern shown inFIG.4in advance and allocates Dch data symbols to RBs according to the mapping pattern shown inFIG.4. As shown inFIG.5, allocation section103allocates Dch data symbols to the subblock of RB #1 and subblock of RB #7 constituting Dch #1, the subblock of RB #2 and subblock of RB #8 constituting Dch #2, the subblock of RB #1 and subblock of RB #7 constituting Dch #7, and the subblock of RB #2 and subblock of RB #8 constituting Dch #8. That is, as shown inFIG.5, Dch data symbols are allocated to RBs #1, #2, #7 and #8. Therefore, four Dchs are allocated to RB subblocks RBs #1 and #2 constituting RBG1, and RBs #7 and #8 constituting RBG4 covering all RBs. Furthermore, as shown inFIG.5, allocation section103allocates Lch data symbols to the rest of the RBs other than the RBs to which Dch data symbols are allocated, that is, RBs #3 to #6 and RBs #9 to #14. As described above, each Lch is allocated to RB group units. Thus, as shown inFIG.5, allocation section103allocates Lch data symbols to RB #3 and RB #4 constituting RBG2 in which Lch #3 and Lch #4 are mapped respectively, RB #5 and RB #6 constituting RBG3 in which Lch #5 and Lch #6 are mapped respectively, RB #9 and RB #10 constituting RBG5 in which Lch #9 and Lch #10 are mapped respectively, RB #11 and RB #12 constituting RBG6 in which Lch #11 and Lch #12 are mapped respectively and RB #13 and RB #14 constituting RBG7 in which Lch #13 and Lch #14 are mapped respectively. That is, Lchs #3 to #6 and Lchs #9 to #14 shown in FIG.3are used for Lch data symbols. Thus, when Lch data symbols are allocated to RBs other than the RBs to which Dch data symbols are allocated, allocation section103can allocate Lch data symbols in RB group units covering all RBs. Next, an extraction example in demapping section207of mobile station200(FIG.2) will be described where Dch data symbols using four Dchs are allocated to mobile station200. Here, for simplicity of explanation, Dchs #1, #2, #7 and #8 are used for Dch data symbols so that no odd subblocks are produced in RBs. Furthermore, as with allocation section103, demapping section207stores the Dch mapping pattern shown inFIG.4in advance and extracts Dch data symbols from a plurality of RBs according to the mapping pattern shown inFIG.4. As with allocation section103, as shown inFIG.5, demapping section207extracts Dch #1 formed with the subblock of RB #1 and the subblock of RB #7, Dch #2 formed with the subblock of RB #2 and the subblock of RB #8, Dch #7 formed with the subblock of RB #1 and the subblock of RB #7 and Dch #8 formed with the subblock of RB #2 and the subblock of RB #8. That is, as shown inFIG.5, demapping section207extracts Dch data symbols allocated to RBs #1, #2, #7 and #8 as data symbols directed to the subject station. In other words, as shown inFIG.5, demapping section207extracts four Dchs allocated to RBG1 formed with RBs #1 and #2 and RBG4 formed with RBs #7 and #8 covering all RBs as data symbols directed to the subject station. Thus, according to the present mapping method, the RB interval of RBs to which one Dch is mapped is set to an integer multiple of the RB group size of the RB group used for Lch allocation (three times in the present mapping method). When Lchs are allocated to the rest of the RBs after Dchs are allocated, this allows the base station to allocate Lchs in RB group units without producing any RBs that cannot be used. Therefore, according to the present mapping method, even when frequency scheduling transmission and frequency diversity transmission are at the same time carried out, it is possible to prevent the system throughput from deteriorating due to deterioration of the utilization efficiency of communication resources. Furthermore, according to the present mapping method, Lchs can be allocated without producing any unoccupied RBs and the throughput of Lchs can therefore be improved. Furthermore, according to the present mapping method, Lchs are allocated to RB group units, and therefore the amount of control information for indicating the Lch allocation result can be reduced. Here, with 14 RBs (RBs #1 to #14) shown inFIG.4, a maximum of 14 Dchs can be allocated. By contrast, according to the present mapping method, a maximum of 12 Dchs can be allocated as described above. That is, according to the present mapping method, the number of Dchs that can be allocated are reduced by an amount corresponding to the RB group size (two Dchs inFIG.4) at a maximum. However, since the applications of Dchs are limited to data communication when a mobile station moves at a high speed or the like, it is extremely rare that Dchs are allocated to all RBs. Therefore, there is substantially no deterioration of system throughput due to a decrease in the number of Dchs that can be allocated using the present mapping method. Moreover, the improvement in the system throughput by allocating Lchs without producing any unoccupied RBs # using the present mapping method becomes more significant than the deterioration of system throughput. Although a case has been described in the present mapping method where one RB is divided into two portions when Dchs are used, the number of divisions is not limited to 2, and one RB may be divided into three portions. For example,FIG.6illustrates a mapping method where one RB is divided into three portions when Dchs are used. In the mapping method illustrated inFIG.6, when, for example, six Dchs are mapped, Dchs can be mapped within RB groups covering all RB subblocks, and therefore effects similar to those of the present mapping method can be obtained. Furthermore, as shown inFIG.6, since one Dch is configured distributed across three RBs, the diversity effect can be improved more than the case of division into two portions. Mapping Method 2 (FIG.7) The present mapping method is the same as mapping method 1 in that one Dch is mapped at intervals of an integer multiple of the RB group size among a plurality of RBs, but the present mapping method is different from mapping method 1 in that one Dch is mapped at the maximum interval among possible intervals of integer multiples of the RB group size. That is, RB interval Gap between RBs to which one Dch is mapped is given by following equation 3. [3] Gap=floor((Nrb−Wgap·Nd)/RBGsize)·RBGsize+Wgap (Equation 3) where, Wgap=floor((Nrb/Nd)/RBGsize)·RBGsize and is equivalent to equation 1. Nd RB numbers (indexes) j to which Dch #k (k=1 to 12) are mapped are given by equation 4. [4] j=((k−1)mod(Wgap))+1+Gap·p,p=0,1, . . . ,Nd−1 (Equation 4) where, Dchs of k=1, 2, . . . , Wgap are mapped to the first-half RB subblocks and Dchs of k=Wgap+1, Wgap+2, Wgap×Nd are mapped to the last-half RB subblocks. Here, since Nrb=14, Nd=2, RBGsize=2 and Wgap=6, the RB interval Gap is 8 (=floor((14/2)/2)×2+6) according to equation 3. Therefore, above equation 4 becomes j=((k−1)mod(6))+8×p (p=0, 1). where, k=1, 2, . . . , 12. Thus, one Dch is mapped in a distributed manner to two RBs of RB #(k) and RB #(k+8) which are 8 RBs apart in the frequency domain. In other words, one Dch is distributedly mapped to RBs 8 RBs apart which is an integer multiple (here, four times) of the RB group size (RBGsize=2) in the frequency domain. Furthermore, according to the present mapping method (Equation 3), the RB interval increases by the number of RBs of RB groups to which Dchs are not allocated compared to the RB interval (Equation 1) of mapping method 1. To be more specific, according to mapping method 1 (FIG.4), Dchs are not mapped to two RBs of RBs #13 and #14. Therefore, the RB interval Gap according to the present mapping method becomes 8 RBs which is greater by 2 RBs than the RB interval of 6 RBs according to mapping method 1. This is because, according to mapping method 1 (FIG.4), RBs in which no Dch is mapped are allocated to an end of all the RBs, whereas according to the present mapping method, RBs in which no Dch is mapped are allocated at the central part of all the RBs. To be more specific, as shown inFIG.7, Dchs #1 and #7 are mapped to RB #1 (RB #9), Dchs #2 and #8 are mapped to RB #2 (RB #10), Dchs #3 and #9 are mapped to RB #3 (RB #11), Dchs #4 and #10 are mapped to RB #4 (RB #12), Dchs #5 and #11 are mapped to RB #5 (RB #13), and Dchs #6 and #12 are mapped to RB #6 (RB #14). That is, according to the present mapping method, the maximum number of Dchs that can be allocated to RBs by allocation section103is 12 as with mapping method 1. Furthermore, according to mapping method 1 (FIG.4), RBs in which no Dch is mapped are last RBs #13 and #14 of RBs #1 to #14, whereas according to the present mapping method, RBs in which no Dch is mapped are RBs #7 and #8 as shown inFIG.7. That is, no Dch is mapped to the central part of all the RBs. Thus, two RB subblocks constituting each Dch are mapped extending to a maximum extent over RBs #1 to #6 and RBs #9 to #14 on both sides of RBs #7 and #8. That is, Dchs #1 to #12 are mapped at a maximum interval (interval of 8 RBs) among possible intervals of integer multiples of the RB group size out of 14 RBs. Next, as with mapping method 1,FIG.8illustrates a mapping example where four Dchs are used for Dch data symbols of one mobile station. Here, Dchs #1, #2, #7 and #8 are allocated as with mapping method 1. Furthermore, allocation section103stores the Dch mapping pattern shown inFIG.7in advance and allocates Dch data symbols to RBs according to the mapping pattern shown inFIG.7. As shown inFIG.8, allocation section103allocates Dch data symbols to the subblock of RB #1 and the subblock of RB #9 constituting Dch #1, the subblock of RB #2 and the subblock of RB #10 constituting Dch #2, the subblock of RB #1 and the subblock of RB #9 constituting Dch #7, and the subblock of RB #2 and the subblock of RB #10 constituting Dch #8. That is, Dch data symbols are allocated to RBs #1, #2, #9 and #10 as shown inFIG.8. That is, the four Dchs are allocated to RBs #1 and #2 constituting RBG1, and RBs #9 and #10 constituting RBG5 covering all RB subblocks. Furthermore, as shown inFIG.8, allocation section103allocates Lch data symbols to the rest of the RBs #3 to #8 and RBs #11 to #14 other than the RBs to which the Dch data symbols have been allocated. Here, allocation section103allocates Lch data symbols in RB group units as with mapping method 1. To be more specific, as shown inFIG.8, allocation section103allocates Lch data symbols to two RBs constituting RBGs #2, #3, #4, #6 and #7 respectively. That is, Lchs #3 to #8 and Lchs #11 to #14 shown inFIG.3are used for the Lch data symbols. Thus, when allocating Lch data symbols to blocks other than the RBs to which the Dch data symbols have been allocated, allocation section103can allocate the Lch data symbols in RB group units covering all RBs as with mapping method 1. Next, an extraction example in demapping section207of mobile station200(FIG.2) will be described where Dch data symbols using four Dchs are allocated to mobile station200. Here, Dchs #1, #2, #7 and #8 are used for Dch data symbols as with mapping method 1. Furthermore, demapping section207stores the Dch mapping pattern shown inFIG.7in advance as with allocation section103and extracts Dch data symbols from a plurality of RBs according to the mapping pattern shown inFIG.7. As with allocation section103, as shown inFIG.8, demapping section207extracts Dch #1 formed with the subblock of RB #1 and the subblock of RB #9, Dch #2 formed with the subblock of RB #2 and the subblock of RB #10, Dch #7 formed with the subblock of RB #1 and the subblock of RB #9, and Dch #8 formed with the subblock of RB #2 and the subblock of RB #10. That is, as shown inFIG.8, demapping section207extracts Dch data symbols allocated to RBs #1, #2, #7 and #8 as data symbols directed to the subject station. In other words, as shown inFIG.8, demapping section207extracts four Dchs allocated to RBG1 formed with RBs #1 and #2, and RBG5 formed with RBs #9 and #10 covering all RBs as data symbols directed to the subject station. Here, inFIG.8, as in the case of mapping method 1 (FIG.5), Dch data symbols are allocated to four RBs and Lch data symbols are allocated to 10 RBs. However, according to the present mapping method as shown inFIG.8, Dch data symbols are allocated in a distributed manner to RB #1, RB #2, RB #9 and RB #10, and therefore the interval thereof is longer by the RB interval where no Dch is mapped (2-RB interval of RBs #7 and #8) than by mapping method 1 (FIG.5). Therefore, the present mapping method can improve the frequency diversity effect. By this means, the present mapping method maps one Dch at a maximum interval (8-RB interval four times the RB group size inFIG.7) among possible intervals of integer multiples of the RB group size. By this means, Lchs can be allocated in RB group units while maximizing the RB interval of one Dch without producing any RB that cannot be used. Therefore, according to the present mapping method, it is possible to obtain effects similar to those of mapping method 1 and improve the frequency diversity effect compared to mapping method 1. Although a case has been described in the present mapping method where one RB is divided into two portions when Dchs are used, the number of divisions of one RB is not limited to two, but the number of divisions of one RB may be three or more as in the case of mapping method 1. Mapping Method 3 (FIG.9) The present mapping method is the same as mapping method 1 in that one Dch is mapped at intervals of an integer multiple of the RB group size among a plurality of RBs, but the present mapping method differs from mapping method 1 in that a plurality of Dchs with continuous channel numbers are mapped to one RB. Hereinafter, the present mapping method will be described more specifically. Here, one Dch is mapped to two RBs which are mapped in a distributed manner at intervals of 6 RBs as with mapping method 1 (FIG.4). As shown inFIG.9, Dchs #1 and #2 with continuous channel numbers are mapped to RB #1 (RB #7). Likewise, Dchs #3 and #4 are mapped to RB #2 (RB #8), Dchs #5 and #6 are mapped to RB #3 (RB #9), Dchs #7 and #8 are mapped to RB #4 (RB #10), Dchs #9 and #10 are mapped to RB #5 (RB #11) and Dchs #11 and #12 are mapped to RB #6 (RB #12). Thus, since one Dch is mapped to two RBs at intervals of 6 RBs, when allocating Lchs to the rest of the RBs after allocating Dchs as with mapping method 1, it is possible to allocate Lchs in RB group units without producing any RBs that cannot be used. Furthermore, since a plurality of Dchs with continuous channel numbers are mapped to one RB, when one mobile station uses a plurality of Dchs, all the one RB subblocks are used first and then the other RBs are used. Therefore, data symbols are allocated to some subblocks of a plurality of subblocks constituting one RB, and on the other hand, it is possible to minimize the possibility that other subblocks may not be further used. This makes it possible to improve the utilization efficiency of Dch resources. Furthermore, as with mapping method 1, allocation section103of base station100(FIG.1) and demapping section207of mobile station200(FIG.2) store the Dch mapping pattern shown inFIG.9, which is the correspondence between RBs and Dchs, in advance. Allocation section103of base station100then allocates Dch data symbols to RBs according to the Dch mapping pattern shown inFIG.9. On the other hand, demapping section207of mobile station200extracts Dch data symbols directed to the subject station from a plurality of RBs according to the Dch mapping pattern shown inFIG.9as with allocation section103. By this means, the present mapping method maps a plurality of Dchs with continuous channel numbers in one RB, and thereby increases the probability that data symbols may be allocated to all RB subblocks used for Dchs. Therefore, it is possible to prevent deterioration of system throughput due to deterioration of the utilization efficiency of communication resources compared to mapping method 1. As with mapping method 2 (FIG.7), the present mapping method may map one Dch at the maximum interval among possible intervals of integer multiples of the RB group size. To be more specific, as shown inFIG.10, one Dch may be mapped to RBs mapped in a distributed manner at intervals of 8 RBs. This makes it possible to achieve a diversity effect similar to that of mapping method 2 while achieving effects similar to those of the present mapping method. Mapping Method 4 (FIG.11) The present mapping method is the same as mapping method 1 in that one Dch is mapped at intervals of an integer multiple of the RB group size of a plurality of RBs, but the present mapping method is different from mapping method 1 in that a plurality of Dchs with continuous channel numbers are mapped to different RBs constituting one RB group. Hereinafter, the present mapping method will be described more specifically. Here, as with mapping method 1 (FIG.4), one Dch is mapped to two RBs mapped in a distributed manner at intervals of 6 RBs. As shown inFIG.11, Dchs #1 and #3 are mapped to RB #1 (RB #7), Dchs #2 and #4 are mapped to RB #2 (RB #8), Dchs #5 and #7 are mapped to RB #3 (RB #9), Dchs #6 and #8 are mapped to RB #4 (RB #10), Dchs #9 and #11 are mapped to RB #5 (RB #11) and Dchs #10 and #12 are mapped to RB #6 (RB #12). That is, as shown inFIG.11, Dchs #1 to #4 with continuous channel numbers are mapped to RBs #1 and #2 (RBs #7 and #8) constituting RBG1 (RBG4). Furthermore, in RBG1 (RBG4), Dch #1 (Dch #3) and Dch #2 (Dch #4) with continuous channel numbers among Dchs #1 to #4 are mapped to different RBs of RB #1 and #2 respectively. Furthermore, as shown inFIG.11, Dch #3 and Dch #2 with continuous channel numbers are also mapped to different RBs of RBs #1 and #2 respectively. The same applies to RBG2 (RBG5) and RBG3 (RBG6). Thus, since a plurality of Dchs with continuous channel numbers are mapped to one RB group, even when one mobile station uses a plurality of Dchs, RBs are used in RB group units for Dchs. Therefore, when RBs other than the RBs used for Dchs are allocated to Lchs, RBs can also be used in RB group units for Lchs. That is, since RBs can be used exhaustively, it is possible to prevent deterioration in the utilization efficiency of communication resources more than mapping method 1. Furthermore, in the RB group, Dchs with continuous channel numbers are mapped to different RBs, and therefore the diversity effect can be improved. Furthermore, as with mapping method 1, allocation section103of base station100(FIG.1) and demapping section207of mobile station200(FIG.2) store the Dch mapping pattern shown inFIG.11, which is the correspondence between RBs and Dchs, in advance. Allocation section103of base station100then allocates Dch data symbols to RB s according to the Dch mapping pattern shown inFIG.11. On the other hand, as with allocation section103, demapping section207of mobile station200extracts Dch data symbols directed to the subject station from a plurality of RBs according to the Dch mapping pattern shown inFIG.11. By this means, the present mapping method maps a plurality of Dchs with continuous channel numbers in different RBs constituting one RB group respectively. By this means, even when a plurality of Dchs are used, the plurality of Dchs are collectively allocated in RB group units. That is, even when one mobile station uses a plurality of Dchs, Dchs are allocated to RB units, and therefore Lchs can also be allocated in RB group units. Thus, the present mapping method can prevent deterioration of system throughput due to deterioration of the utilization efficiency of communication resources compared to mapping method 1. Furthermore, since different Dchs with continuous channel numbers are allocated to different RB s within one RB group, the frequency diversity effect can be further improved. As with mapping method 2 (FIG.7), the present mapping method may also map one Dch at the maximum interval among possible intervals of integer multiples of the RB group size. To be more specific, as shown inFIG.12, one Dch may be mapped to RBs mapped in a distributed manner at intervals of 8 RBs. This makes it possible to achieve a diversity effect similar to that of mapping method 2 while achieving effects similar to those of the present mapping method. Mapping Method 5 (FIG.13) The present mapping method is the same as mapping method 4 in that a plurality of Dchs with continuous channel numbers are mapped to different RBs constituting one RB group, but the present mapping method is different from mapping method 4 in that a plurality of Dchs with discontinuous channel numbers are mapped to mutually neighboring RBs among a plurality of RBs constituting mutually neighboring RB groups. Hereinafter, the present mapping method will be described more specifically. Here, as with mapping method 1 (FIG.4), one Dch is mapped to two RBs mapped in a distributed manner at intervals of 6 RBs. As shown inFIG.13, Dchs #1 and #7 are mapped to RB #1 (RB #7), Dchs #2 and #8 are mapped to RB #2 (RB #8), Dchs #5 and #11 are mapped to RB #3 (RB #9), Dchs #6 and #12 are mapped to RB #4 (RB #10), Dchs #3 and #9 are mapped to RB #5 (RB #11), and Dchs #4 and #10 are mapped to RB #6 (RB #12). That is, as shown inFIG.13, Dchs #1 and #2 (Dchs #7 and #8) with continuous channel numbers are mapped to RBs #1 and #2 constituting RBG1. Likewise, Dchs #5 and #6 (Dchs #11 and #12) with continuous channel numbers are mapped to RBs #3 and #4 constituting RBG2, and Dchs #3 and #4 (Dchs #9 and #10) with continuous channel numbers are mapped to RBs #5 and #6 constituting RBG3. Furthermore, a plurality of different Dchs with discontinuous channel numbers are mapped to RB #2 and RB #3, which are mutually neighboring RBs (that is, RBs on the boundary between RBG1 and RBG2) of RBs constituting mutually neighboring RBG1 (RBs #1 and #2) and RBG2 (RBs #3 and #4). To be more specific, as shown inFIG.13, Dch #2 and Dch #5 (Dch #8 and Dch #11) with discontinuous channel numbers are mapped to RB #2 and RB #3 respectively. Likewise, Dch #6 and Dch #3 (Dch #12 and Dch #9) with discontinuous channel numbers are mapped to mutually neighboring RB #4 and RB #5 among RB #3 and #4 constituting RBG2, and RB #5 and #6 constituting RBG3. The same applies to RBG4 to RBG6. By this means, at least one set of Dchs with continuous channel numbers is mapped to one RB group. Furthermore, channel numbers of Dchs mapped to mutually neighboring RBs among a plurality of RBs constituting mutually neighboring RB groups respectively are discontinuous. In other words, Dchs with continuous channel numbers among Dchs mapped to different RB groups are mapped to RBs distributed in the frequency domain. Thus, when one mobile station uses many Dchs, allocation section103allocates Dchs to RBs distributed in the frequency domain, and thereby provide frequency diversity effect. On the other hand, when one mobile station uses a fewer Dchs, allocation section103can collectively allocate Dchs within an RB group. By this means, when RBs other than the RBs used for Dchs are allocated to Lchs, RBs can also be used in RB group units for Lchs. That is, RBs can be used exhaustively, and it is therefore possible to prevent deterioration of the utilization efficiency of communication resources. Furthermore, as with mapping method 1, allocation section103of base station100(FIG.1) and demapping section207of mobile station200(FIG.2) store the Dch mapping pattern shown inFIG.13, which is the correspondence between RBs and Dchs, in advance. Allocation section103of base station100then allocates Dch data symbols to RBs according to the Dch mapping pattern shown inFIG.13. On the other hand, as with allocation section103, demapping section207of mobile station200extracts Dch data symbols directed to the subject station from a plurality of RBs according to the Dch mapping pattern shown inFIG.13. By this means, the present mapping method maps a plurality of Dchs with discontinuous channel numbers in mutually neighboring RBs among a plurality of RBs constituting mutually neighboring RB groups. Thus, as with mapping method 1, it is possible to prevent deterioration of system throughput due to deterioration in the utilization efficiency of communication resources when one mobile station uses a fewer Dchs, and improve the frequency diversity effect when one mobile station uses many Dchs. According to the present mapping method, one Dch may be mapped at the maximum interval among possible intervals of integer multiples of the RB group size as with mapping method 2 (FIG.7). To be more specific, as shown inFIG.14, one Dch may be mapped to RBs mapped in a distributed manner at intervals of 8 RBs. This makes it possible to achieve a diversity effect similar to that of mapping method 2 while achieving effects similar to those of the present mapping method. Mapping methods 1 to 5 according to the present embodiment have been described so far. Thus, according to the present embodiment, it is possible to prevent deterioration in the utilization efficiency of communication resources even when frequency scheduling transmission through Lchs and frequency diversity transmission through Dchs are carried out at the same time. An embodiment has been described so far. In the above described embodiment, the channel mapping method for mapping Dchs in RBs depends on the number of all RBs (Nrb) determined by the system bandwidth as shown in equation 1 or equation 3. Therefore, the base station and mobile station may be configured to have a table of correspondence between Dch channel numbers and RB numbers for each system bandwidth (e.g.,FIG.4,FIG.7,FIG.9,FIG.11andFIG.13) and look up the table of correspondence corresponding to the system bandwidth to which Dch data symbols are allocated when allocating Dch data symbols. Furthermore, a case has been described with the above-described embodiment where a signal received by the base station (that is, a signal transmitted by the mobile station over an uplink) is transmitted based on an OFDM scheme, but this signal may also be transmitted based on transmission schemes other than the OFDM scheme such as a single-carrier scheme or CDMA scheme. Furthermore, a case has been described with the above-described embodiment where an RB is formed with a plurality of subcarriers comprised of an OFDM symbol, but an RB may be any block formed with continuous frequencies. Furthermore, a case has been described with the above-described embodiment where RBs are continuously configured in the frequency domain, but RBs may also be continuously configured in the time domain. Furthermore, a case has been described with the above-described embodiment is applied to a signal transmitted by the base station (that is, a signal transmitted by the base station over a downlink), but embodiments may also be applied to a signal received by the base station (that is, a signal transmitted by the mobile station over an uplink). In this case, the base station performs adaptive control such as RB allocation on an uplink signal. Furthermore, in the above described embodiment, adaptive modulation is performed on Lchs only, but adaptive modulation may also be performed on Dchs likewise. In this case, the base station may perform adaptive modulation on Dch data based on average received quality information of an entire band reported from each mobile station. Furthermore, a case has been described with the above-described embodiment where RB used for Dch is divided into a plurality of subblocks in the time domain, but RB used for Dch may also be divided into a plurality of subblocks in the frequency domain or may also be divided into a plurality of subblocks in the time domain and frequency domain. That is, a plurality of Dchs may be frequency-domain-multiplexed in one RB or may be time-domain-multiplexed or frequency-domain-multiplexed. Furthermore, although a case has been described in the present embodiment where when a plurality of different Dchs with continuous channel numbers are allocated to one mobile station, only the first channel number and the last channel number are reported from the base station to the mobile station, the first channel number and the number of channels may be reported from the base station to the mobile station. Furthermore, although a case has been described in the present embodiment where one Dch is mapped to RB s which are mapped to be distributed uniformly in the frequency domain, RBs to which one Dch is mapped are not limited to RBs mapped to be distributed uniformly in the frequency domain. Furthermore, although a case has been described with the above-described embodiment where Dchs are used as channels for carrying out frequency diversity transmission, the channels are not limited to Dchs, but the channels may be any channels that are mapped in a distributed manner in a plurality of RBs or a plurality of subcarriers in the frequency domain and can provide frequency diversity effect. Furthermore, although Lchs are used as the channels for carrying out frequency scheduling transmission, the channels used are not limited to Lchs, but the channels may be any channels that can provide multiuser diversity effect. Furthermore, Dch may also be referred to as “DVRB” (Distributed Virtual Resource Block) and Lch may also be referred to as “LVRB” (Localized Virtual Resource Block). Furthermore, RB used for Dch may also be referred to as “DRB” or “DPRB” (Distributed Physical Resource Block) and RB used for Lch may also be referred to as “LRB” or “LPRB” (Localized Physical Resource Block). Furthermore, a mobile station may also be referred to as “UE,” a base station apparatus may also be referred to as “Node B” and a subcarrier may also be referred to as “tone.” Furthermore, an RB may also be referred to as a “subchannel,” “subcarrier block,” “subcarrier group,” “subband” or “chunk.” Furthermore, a CP may also be referred to as a “guard interval (GI)”. Furthermore, a subframe may also be referred to as a “slot” or “frame.” A subblock may also be referred to as a “slot.” Furthermore, a case has been described with the above-described embodiment where an RB is divided into two subblocks in the time domain and Dch is allocated thereto, and each divided subblock may be referred to as “RB.” In this case, encoding and adaptive control or the like are performed in two RBs in the time domain. Moreover, although cases have been described with the embodiment above configured by hardware, embodiments may be implemented by software. Each function block employed in the description of the aforementioned embodiment may typically be implemented as an LSI constituted by an integrated circuit. These may be individual chips or partially or totally contained on a single chip. “LSI” is adopted here but this may also be referred to as “IC,” “system LSI,” “super LSI” or “ultra LSI” depending on differing extents of integration. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. After LSI manufacture, utilization of an FPGA (Field Programmable Gate Array) or a reconfigurable processor where connections and settings of circuit cells within an LSI can be reconfigured is also possible. Further, if integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. Application of biotechnology is also possible. The disclosure of Japanese Patent Application No. 2008-000198, filed on Jan. 4, 2008 and Japanese Patent Application No. 2008-062970, filed on Mar. 12, 2008, including the specification, drawings and abstract, is incorporated herein by reference in its entirety. INDUSTRIAL APPLICABILITY The present disclosure is applicable to a mobile communication system or the like. | 48,590 |
11943758 | DETAILED DESCRIPTION Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details. The described features generally relate to classifying beams that are used by a node in wireless communications into classes, and using the beams based on one or more parameters associated with its class. For example, millimeter wave (mmWave) and sub-terahertz (THz) frequencies offer abundance of unlicensed spectrum bands. Transmission and reception over these bands may be directional, resulting in interference-limited wireless environment. Depending on the operating scenario, performing Listen-Before-Talk (LBT) and/or Long-Term (LT) Sensing might not be required. To resolve potential “beam collisions”, LBT and LT Sensing can be combined with other coexistence methods, such as using a narrow beam. As used herein, the term “narrow beam” can refer to a geometrical shape of the beam as being within a threshold angular spread, interference caused to or by the beam as being within a narrow space, and/or the like. Some wireless communication technologies define various beams, such as European Telecommunications Standards Institute (ETSI) European Standard (EN) 303 753 (also known as “C2”), that can be used by nodes in wireless communications. C2 beams, for example, can be applicable to mobile and fixed nodes. In addition, for C2 beams, LBT may be skipped at either side with minimum antenna gain requirements, but some mitigation technique may be used in the absence of sufficient antenna gain. 3GPP technologies define other beams as well, such as EN 302 567 (also known as “C1”) and EN 303 722 (also known as “C3”). Aspects described herein may be applied to beams, such as C2, that may not require use of LBT, but may also apply to other types of beams, such as C1 and/or C3. Aspects described herein relate to using Channel Access Classes (CACCs) for narrow beam-based channel access. In an example, for each CACC, a threshold of narrow beam-based channel access condition can be defined, which can be used to determine whether the node can access the channel using the beam (e.g., with or without LBT or otherwise). In another example, each CACC may have an associated limit on its channel occupancy time (COT) and/or may have a gap between channel access times. Aspects described herein may apply to downlink channel access, uplink channel access, sidelink channel access, or the like. In addition, for example, CACCs for narrow beam channel access may apply to transmitter and/or receiver sides of a communication link. In accordance with aspects described herein, providing CACCs and associated parameters for beams used by one or more nodes may allow for limiting interference caused by the beams, enhancing channel utilization for different traffic classes, etc. For example, providing different classes for the beams based on known beam properties can allow for maximizing usage of the beams, such that beams known to have desirable properties may be used without restriction or with lowered restrictions on COT, gap, etc., as these beams may have a lowered chance of interfering with beams from other nodes. In another example, beams known to have comparatively not as desirable properties may be used with some restrictions on COT, gap, etc. to limit interference possibly caused by the beams, lessen channel access times where other competing/possibly interfering beams desire to use the channel, etc. This can improve communication quality for multiple nodes in a wireless network. The described features will be presented in more detail below with reference toFIGS.1-5. As used in this application, the terms “component,” “module,” “system” and the like are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal. Techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms “system” and “network” may often be used interchangeably. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0 and A are commonly referred to as CDMA2000 1×, 1×, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1×EV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. The description below, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to fifth generation (5G) new radio (NR) networks or other next generation communication systems). The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in other examples. Various aspects or features will be presented in terms of systems that can include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems can include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches can also be used. FIG.1is a diagram illustrating an example of a wireless communications system and an access network100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) can include base stations102, UEs104, an Evolved Packet Core (EPC)160, and/or a 5G Core (5GC)190. The base stations102may include macro cells (high power cellular base station) and/or small cells (low power cellular base station). The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells. In an example, the base stations102may also include gNBs180, as described further herein. In one example, some nodes of the wireless communication system, such as a UE104, base station102, or other nodes, may have a modem240and communicating component242for beam-based channel access using beam classes, in accordance with aspects described herein. Though a UE104and base station102are shown as having the modem240and communicating component242, this is one illustrative example, and substantially any node or type of node may include a modem240and communicating component242for providing corresponding functionalities described herein. The base stations102configured for 4G LTE (which can collectively be referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC160through backhaul links132(e.g., using an S1 interface). The base stations102configured for 5G NR (which can collectively be referred to as Next Generation RAN (NG-RAN)) may interface with 5GC190through backhaul links184. In addition to other functions, the base stations102may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations102may communicate directly or indirectly (e.g., through the EPC160or 5GC190) with each other over backhaul links134(e.g., using an X2 interface). The backhaul links134may be wired or wireless. The base stations102may wirelessly communicate with one or more UEs104. Each of the base stations102may provide communication coverage for a respective geographic coverage area110. There may be overlapping geographic coverage areas110. For example, the small cell102′ may have a coverage area110′ that overlaps the coverage area110of one or more macro base stations102. A network that includes both small cell and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group, which can be referred to as a closed subscriber group (CSG). The communication links120between the base stations102and the UEs104may include uplink (UL) (also referred to as reverse link) transmissions from a UE104to a base station102and/or downlink (DL) (also referred to as forward link) transmissions from a base station102to a UE104. The communication links120may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations102/UEs104may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (e.g., for x component carriers) used for transmission in the DL and/or the UL direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell). In another example, certain UEs104may communicate with each other using device-to-device (D2D) communication link158. The D2D communication link158may use the DL/UL WWAN spectrum. The D2D communication link158may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR. The wireless communications system may further include a Wi-Fi access point (AP)150in communication with Wi-Fi stations (STAs)152via communication links154in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs152/AP150may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available. The small cell102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell102′ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP150. The small cell102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. A base station102, whether a small cell102′ or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or other type of base station. Some base stations, such as gNB180may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and/or near mmW frequencies in communication with the UE104. When the gNB180operates in mmW or near mmW frequencies, the gNB180may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band has extremely high path loss and a short range. The mmW base station180may utilize beamforming182with the UE104to compensate for the extremely high path loss and short range. A base station102referred to herein can include a gNB180. The EPC160may include a Mobility Management Entity (MME)162, other MMES164, a Serving Gateway166, a Multimedia Broadcast Multicast Service (MBMS) Gateway168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway172. The MME162may be in communication with a Home Subscriber Server (HSS)174. The MME162is the control node that processes the signaling between the UEs104and the EPC160. Generally, the MME162provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway166, which itself is connected to the PDN Gateway172. The PDN Gateway172provides UE IP address allocation as well as other functions. The PDN Gateway172and the BM-SC170are connected to the IP Services176. The IP Services176may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC170may provide functions for MBMS user service provisioning and delivery. The BM-SC170may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway168may be used to distribute MBMS traffic to the base stations102belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information. The 5GC190may include a Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. The AMF192may be in communication with a Unified Data Management (UDM)196. The AMF192can be a control node that processes the signaling between the UEs104and the 5GC190. Generally, the AMF192can provide QoS flow and session management. User Internet protocol (IP) packets (e.g., from one or more UEs104) can be transferred through the UPF195. The UPF195can provide UE IP address allocation for one or more UEs, as well as other functions. The UPF195is connected to the IP Services197. The IP Services197may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station102provides an access point to the EPC160or 5GC190for a UE104. Examples of UEs104include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs104may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). IoT UEs may include machine type communication (MTC)/enhanced MTC (eMTC, also referred to as category (CAT)-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. The UE104may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In an example, a communicating component242of a first node can configure a beam for communicating with a second node Turning now toFIGS.2-5, aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional. Although the operations described below inFIG.3are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation. Moreover, it should be understood that the following actions, functions, and/or described components may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions. Referring toFIG.2, one example of an implementation of node200for wireless communications is illustrated, which may include a base station102, a UE104, or another node, as described above. Node200may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors212and memory216and transceiver202in communication via one or more buses244, which may operate in conjunction with modem240and/or communicating component242for beam-based channel access using beam classes, in accordance with aspects described herein. In an aspect, the one or more processors212can include a modem240and/or can be part of the modem240that uses one or more modem processors. Thus, the various functions related to communicating component242may be included in modem240and/or processors212and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors212may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver202. In other aspects, some of the features of the one or more processors212and/or modem240associated with communicating component242may be performed by transceiver202. Also, memory216may be configured to store data used herein and/or local versions of applications275or communicating component242and/or one or more of its subcomponents being executed by at least one processor212. Memory216can include any type of computer-readable medium usable by a computer or at least one processor212, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory216may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining communicating component242and/or one or more of its subcomponents, and/or data associated therewith, when node200is operating at least one processor212to execute communicating component242and/or one or more of its subcomponents. Transceiver202may include at least one receiver206and at least one transmitter208. Receiver206may include hardware, firmware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). Receiver206may be, for example, a radio frequency (RF) receiver. In an aspect, receiver206may receive signals transmitted by at least one base station102. Additionally, receiver206may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter208may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). A suitable example of transmitter208may including, but is not limited to, an RF transmitter. Moreover, in an aspect, node200may include RF front end288, which may operate in communication with one or more antennas265and transceiver202for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one base station102or wireless transmissions transmitted by node200. RF front end288may be connected to one or more antennas265and can include one or more low-noise amplifiers (LNAs)290, one or more switches292, one or more power amplifiers (PAs)298, and one or more filters296for transmitting and receiving RF signals. In an aspect, LNA290can amplify a received signal at a desired output level. In an aspect, each LNA290may have a specified minimum and maximum gain values. In an aspect, RF front end288may use one or more switches292to select a particular LNA290and its specified gain value based on a desired gain value for a particular application. Further, for example, one or more PA(s)298may be used by RF front end288to amplify a signal for an RF output at a desired output power level. In an aspect, each PA298may have specified minimum and maximum gain values. In an aspect, RF front end288may use one or more switches292to select a particular PA298and its specified gain value based on a desired gain value for a particular application. Also, for example, one or more filters296can be used by RF front end288to filter a received signal to obtain an input RF signal. Similarly, in an aspect, for example, a respective filter296can be used to filter an output from a respective PA298to produce an output signal for transmission. In an aspect, each filter296can be connected to a specific LNA290and/or PA298. In an aspect, RF front end288can use one or more switches292to select a transmit or receive path using a specified filter296, LNA290, and/or PA298, based on a configuration as specified by transceiver202and/or processor212. As such, transceiver202may be configured to transmit and receive wireless signals through one or more antennas265via RF front end288. In an aspect, transceiver may be tuned to operate at specified frequencies such that node200can communicate with one or more other nodes, for example, one or more base stations102or one or more cells associated with one or more base stations102, one or more UEs104, etc. In an aspect, for example, modem240can configure transceiver202to operate at a specified frequency and power level based on the configuration of the node200and the communication protocol used by modem240. In an aspect, modem240can be a multiband-multimode modem, which can process digital data and communicate with transceiver202such that the digital data is sent and received using transceiver202. In an aspect, modem240can be multiband and be configured to support multiple frequency bands for a specific communications protocol. In an aspect, modem240can be multimode and be configured to support multiple operating networks and communications protocols. In an aspect, modem240can control one or more components of node200(e.g., RF front end288, transceiver202) to enable transmission and/or reception of signals from the network based on a specified modem configuration. In an aspect, the modem configuration can be based on the mode of the modem and the frequency band in use. In another aspect, the modem configuration can be based on configuration information associated with node200as provided by the network during cell selection and/or cell reselection. In an aspect, communicating component242can optionally include a beam selecting component252for selecting or otherwise configuring a beam for communicating with another node, and/or a class applying component254for applying a class (e.g., a CACC) or one or more related parameters to the beam and/or to communications using the beam, in accordance with aspects described herein. In an aspect, the processor(s)212may correspond to one or more of the processors described in connection with the UE inFIG.5. Similarly, the memory216may correspond to the memory described in connection with the UE inFIG.5. FIG.3illustrates a flow chart of an example of a method300for communicating over a wireless channel based on a channel access class of a beam, in accordance with aspects described herein. In an example, a node200can perform the functions described in method300using one or more of the components described inFIGS.1and2. In method300, at Block302, a node can configure a beam for communicating over a wireless channel. In an aspect, beam selecting component252, e.g., in conjunction with processor(s)212, memory216, transceiver202, communicating component242, etc., can configure the beam for communicating over the wireless channel. For example, beam selecting component252can obtain a configuration from another node in the wireless network indicating which beam to use. For example, node200can be a UE104that receives a configuration from a base station102indicating which beam to use, spatial properties of the beam, a transmission configuration indicator (TCI) state identifying the beam or a quasi-colocation (QCL) of the beam, etc. In another example, beam selecting component252can perform beam training with another node of the wireless network to determine a beam to use in communicating with the other node (e.g., a beam or beam pair having a most desirable or highest signal-to-noise ratio (SNR) or other metric, etc.). In yet another example, beam selecting component252can indicate to another node in the wireless network which beam it is using. In another example, beam selecting component252can receive, from another node in the wireless network, an indication of which beam the other node in the wireless network is using and can configure its beam based on the indication. In addition, in other examples, beam selecting component252can determine which beam to use based on configured properties of the beam, which may include a CACC of the beam, as described further herein. For example, given a list of beams configured by another node (e.g., where the node200is a UE104given, from a base station102, a list of beams configured for use by the UE104), beam selecting component252may configure the beam based on one or more properties described above, and/or based on a CACC or associated parameters of the beam. For example, if a beam that complies with thresholds of a CACC, as described in further detail below, is configured by the base station102, beam selecting component252may determine to configure this beam for use in communicating with the base station102. In addition, for example, beam selecting component252may determine to configure a beam from the list based on CACC of the beam and intended communications using the beam (e.g., a beam with a higher priority CACC for higher priority or reliability communications). In method300, at Block304, the node can communicate over the wireless channel using the beam and based on at least one of a COT or a gap defined for the beam. In an aspect, class applying component254, e.g., in conjunction with processor(s)212, memory216, transceiver202, communicating component242, etc., can communicate over the wireless channel using the beam and based on at least one of the COT or the gap defined for the beam. For example, one the CACC for the beam is determined, the other parameters can be determined for the CACC, such as the COT or the gap, and class applying component254can apply the one or more parameters in communicating using the beam. In one specific example, as described herein, class applying component254can determine which CACC applies to the beam based on whether the beam complies with a threshold for the CACC, and then the class applying component254can determine the COT and/or gap that applies to that CACC. For example, the CACCs and associated parameters can be defined for the node (e.g., for a UE104or base station102) to use in communicating in a wireless network. An example of a table of CACCs is shown below. ThresholdMaximumMinimum GapCACCX for Mj, iCOTGlCACC 1X1T1G1CACC 2X2T2G2. . .. . .. . .. . .CACC LXlTlGlCACC 0X0No RestrictionNo gap required In the above table, for example, Mj,1can be a metric for narrow-beam channel access (e.g., for accessing a wireless channel without performing LBT), and X can be the threshold for which the condition Mj,i>X allows a device to access the channel without LBT using beam j. For example, Mj,imetric can be considered as effective isotropic radiated power (EIRP) value (possibly with offset) that corresponds to a target kth percentile of EIRP measurements or a difference between EIRP values that correspond to two different percentiles. In this example, multiple priority classes for narrow-beam channel access can limit interference and enhance channel utilization for different traffic classes. For example, the lthnarrow-beam CACC can be characterized by its narrow beam threshold, Xl, a maximum COT duration, Tl, and/or a minimum gap, Gl, to be used between communications using the beam. The 0th narrow beam CACC can have a most stringent threshold, X0, but may have no restriction on COT duration and/or no gap requirement. In general, for example, the narrower the beam is the longer the COT duration (e.g., T1≥T2≥ . . . ≥T1for X0≥X1≥X2≥ . . . ≥XL). In an example, the narrow beam metric, say for beam j, can be defined based on the EIRP minus constant b at different percentiles (e.g., k1th, k2th, k1th, where k3<k1, k2<k1) of the distribution of radiated power measured over the full sphere around the transmitter, while the transmitter is configured with beam j. In this example, Mj,1=k1th·tile({EIRPi:i∈Ej})−k2th·tile({RIRPi:i∈Ej}) where E1is the set of EIRPs captured in spherical measurement for beam j. In addition, in this example, Mj,2=k3th·tile({EIRPi−b:i∈Ej}) where Ejis the set of EIRPs captured in spherical measurement for beam j and b is a constant (e.g., Pmax). Mj,2can indicate the gain. A device can pass the narrow beam condition for beam j, if Mj,1is greater than a predefined threshold, X. A device can pass the narrow beam condition for beam j, if Mj,1is greater than a predefined threshold, X, or Mj,2is less than a threshold, Z. The analysis of beams and associated narrow beam metrics can be performed offline or in a lab, and results can be hardcoded or stored in a memory of a device (e.g., memory216of node200). In this example, beam selecting component252can use the narrow beam metrics of various beams in mapping the beams to CACCs (e.g., based on indicated thresholds for the narrow beam metrics for the CACCs) or otherwise for selecting a beam and/or related parameters to use for wireless communications, as described herein. For example, in method300, optionally at Block306, the node can determine a channel access class associated with the beam. In an aspect, class applying component254, e.g., in conjunction with processor(s)212, memory216, transceiver202, communicating component242, etc., can determine the channel access class associated with the configured beam. In one example, this can include, at Block308, determining, from a configuration, a channel access class for the beam based on the threshold for channel access of the channel access class and a metric associated with the beam. In one example, as described, the node200can store narrow beam signal metrics (e.g., EIRP, cumulative distribution function (CDF) of EIRP, etc.) for various possible beams that can be configured at the node200(e.g., as hardcoded in memory or otherwise received in a separate configuration). In this example, class applying component254can determine CACCs for the various possible beams based on with which threshold (e.g., threshold X for Mj,i) of which CACC each of the beams complies. For example, the CACC for the beam can be based on a determination that at least one of the EIRP spherical measurement, or CDF thereof, of the beam achieves the threshold. In another example, class applying component254can determine the CACCs for beams in a configuration of beams received from another node (e.g., from a base station102, where node200is a UE104) and known or determined narrow beam signal metrics for the beams in the configuration. In an example, the configuration can include the configuration received at Block324, as described in further detail herein. In an example, the configuration can indicate a smallest gap for a highest priority CACC of the CACCs. For example, the priority can correspond to an index of the CACC (e.g., CACC 0 can be highest priority) and can be indicated based on threshold (e.g., the CACC having the highest threshold X for Mj,ican be CACC 0). In other examples, the configuration can indicate a largest gap for a highest priority CACC of the CACCs, a same gap for each of the CACCs, etc. In other examples, the configuration can indicate, for a CACC of the CACCs having a highest threshold, at least one of no limit on the defined COT or a defined gap of zero. In other examples, the configuration can indicate the defined gap as a fixed gap for multiple ones of the CACCs, or the defined gap for each of the CACCs as proportional to the defined COT for each of the CACCs, where the defined COT for each of the CACCs can be less than or equal to a defined maximum COT for each of the CACCs. In other examples, the configuration can indicates the defined gap for each of the channel access classes as a minimum or maximum of a fixed gap or a proportional gap that is proportional to the defined COT for each of the CACCs, where the defined COT for each of the CACCs can be less than or equal to a defined maximum COT for each of the CACCs. In method300, optionally at Block310, at least one of a threshold for channel access, a COT, or a gap defined for the channel access class can be determined. In an aspect, class applying component254, e.g., in conjunction with processor(s)212, memory216, transceiver202, communicating component242, etc., can determine at least one of the threshold for channel access, the COT, or the gap defined for the channel access class of the configured beam. In this example, class applying component254can use the threshold for channel access, the COT, and/or the gap for subsequent communications using the beam, in accordance with examples described in further detail below. For example, in communicating over the wireless channel at Block304, optionally at Block312, the node can determine whether the threshold for channel access is achieved by the configured beam. In an aspect, class applying component254, e.g., in conjunction with processor(s)212, memory216, transceiver202, communicating component242, etc., can determine whether the threshold for channel access is achieved by the configured beam. If so, optionally at Block314, the node can transmit communications over the wireless channel without performing LBT. In an aspect, communicating component242, e.g., in conjunction with processor(s)212, memory216, transceiver202, etc., can transmit the communications over the wireless channel without performing LBT. If the threshold is not achieved at Block312, optionally at Block316, the node can perform LBT. In an aspect, communicating component242, e.g., in conjunction with processor(s)212, memory216, transceiver202, etc., can perform LBT, which can include performing a clear channel assessment (CCA), such as by transmitting a request to send signal, receiving one or more clear to send signals, etc. Once the channel is clear, in this example, communicating component242can transmit the communications over the wireless channel (e.g., at Block314). In an example, in transmitting communications over the wireless channel at Block314, optionally at Block318, the node can transmit the communications for a time duration corresponding to the COT. In an aspect, communicating component242, e.g., in conjunction with processor(s)212, memory216, transceiver202, etc., can transmit the communications for the time duration corresponding to the COT. As described, for example, the CACC of the beam can have an associated COT (or maximum COT), and the communicating component242can transmit the communications for the COT or not to exceed a time duration of the COT for the CACC of the beam. In another example, in communicating over the wireless channel at Block304, optionally at Block320, the node can determine whether a gap is complied with in communicating over the wireless channel. In an aspect, communicating component242, e.g., in conjunction with processor(s)212, memory216, transceiver202, etc., can determine whether the gap is complied with. As described, for example, the CACC of the beam can have an associated gap that may be required between communications using a beam of the CACC. Thus, for example, communicating component242can determine whether the gap is complied with between a previous communication over the wireless channel and the current communication over the wireless channel. If the gap is complied with at Block320, optionally at Block314, the node can transmit communications over the wireless channel, as described above and/or according to the COT. If the gap is not complied with at Block320, optionally at Block322, the node can wait for a duration, which can comply with the gap. In an aspect, communicating component242, e.g., in conjunction with processor(s)212, memory216, transceiver202, etc., can wait for the duration. For example, communicating component242can determine the duration as a difference between a time since transmitting a previous communication over the wireless channel using the beam and the required minimum gap for the CACC of the configured beam. After the duration, communicating component can transmit the communication over the wireless channel (e.g., at Block314), as described above. An example is shown inFIG.4. FIG.4illustrates an example of a transmission timeline400for CACC 1 and transmission timeline402for CACC L (e.g., from the table above). In transmission timeline400for CACC 1, a first transmission, Tx 1, can occur for a COT of Ti=8 milliseconds (ms), followed by a gap G1=2 ms, followed by a second transmission, Tx 2, for a COT of Ti=16 ms, followed by a gap G1=4 ms, followed by a third transmission, Tx 3, for a COT of T1=10 ms, followed by a gap G1=5 ms. In this example, CACC 1 may have a defined maximum COT of 16 ms and a defined minimum gap of at least 2 ms. Thus, for a beam in CACC 1, the node can comply with the COT and gap for CACC 1 in transmitting over a wireless channel using the beam. In transmission timeline402for CACC L, a first transmission, Tx 1, can occur for a COT of TL=1.5 ms, followed by a gap GL=10.5 ms, followed by a second transmission, Tx 2, for a COT of TL=2 ms, followed by a gap GL=16.25 ms, followed by a third transmission, Tx 3, for a COT of TL=0.5 ms, followed by a gap GL=5.25 ms. In this example, CACC L may have a defined maximum COT of 2 ms and a defined minimum gap of at least 5.25 ms. Thus, for a beam in CACC L, the node can comply with the COT and gap for CACC L in transmitting over a wireless channel using the beam. In an example, CACC L may have a lower threshold narrow beam metric, but may have lower COT and higher gap, as compared to CACC 1, to mitigate interference, as described herein. In an example, a node can vacate the channel for the gap duration Glafter accessing the channel (this ensures channel is not occupied continuously). The gap can be configured and/or determined by the node based on various options. In one example, each CACC can have its own fixed gap requirement irrespective of COT duration {tilde over (T)}l(e.g., gap is Gl=Y seconds for the lth CACC, where Y depends on the CACC). In another example, each priority class can have its variable gap that is proportional to its COT duration {tilde over (T)}l(e.g., gap is Gl=ηl{tilde over (T)}lseconds for the lth CACC and {tilde over (T)}l≤Tl, where ηldepends on the CACC and can be above 1). In another example, each priority class can have its variable gap, where gap is Gl=min(ηlTl, Yl) seconds for the lth CACC, which can be the least conservative example. In another example, each priority class can have its variable gap, where gap is Gl=max(ηlTl, Yl) seconds for the lth CACC, which can be the most conservative example. In addition, for example, relation of gap duration among different CACCs, e.g., G1, G2, . . . , GLcan be set based on one or more objectives, such as one or more of: (1) the highest priority CACC, e.g., the one that has the narrowest beam, has the smallest max. gap, i.e., G1≤G2≤ . . . ≤GL, (2) the highest priority CACC, e.g., the one that has the narrowest beam, has the largest max. gap, i.e., G1≥G2≥ . . . ≥GL, or (3) all priority CACCs have similar gap requirement, i.e., G1=G2= . . . =GL. One specific, non-limiting, example of a CACC configuration is shown below. ThresholdMaximumCACCXCOTMinimum Gap GlCACC 112 decibel20 msmin(η1{tilde over (T)}1, Y1); η1= 2, Y1= 10 ms,(db){tilde over (T)}1≤ 20 msCACC 210 db10 msmin(η2{tilde over (T)}2, Y2); η2= 4, Y2= 15 ms,{tilde over (T)}2≤ 10 ms. . .. . .. . .. . .CACC L6 db2 msmin(ηL{tilde over (T)}L, YL); ηL= 20, YL= 20 ms,{tilde over (T)}L≤ 2 msCACC 015 dbNo RestrictionNo gap required In this example, for CACC 0, the node can access the channel using a very narrow pencil beam for unlimited COT duration, and/or COT can be limited by other factors. For CACC 1, the node can access the channel using a narrow beam that can cause some tolerable interference for 20 milliseconds COT duration (e.g., sending enhanced mobile broadband (eMBB) traffic). For CACC 2, the node can access the channel using a narrow beam that can cause some tolerable interference for 10 milliseconds COT duration (e.g., sending video/voice traffic). For CACC L, the node can access the channel using a wide beam that causes some interference for 2 milliseconds COT duration (e.g., sending low latency traffic/control messages). In method300, optionally at Block324, the node can receive a configuration indicating an association between channel access classes and at least one of a threshold for channel access, a COT, or a gap. In an aspect, class applying component254, e.g., in conjunction with processor(s)212, memory216, transceiver202, communicating component242, etc., can receive the configuration indicating the association between channel access classes and at least one of a threshold for channel access, a COT, or a gap. As described, for example, class applying component254can obtain the configuration from a hardcoding in memory216, from another node in the wireless network (e.g., from a base station102where node200is a UE104), etc. In an example, as described, class applying component254can associate beams available for communicating at the node200with CACCs specified in the configuration for accordingly determining at least a COT or gap to be associated with the beams based on CACC. In one example, class applying component254can determine the CACC for a configured beam based on comparing a narrow beam channel access metric of the beam with the threshold indicated for the CACC, as described above. FIG.5is a block diagram of a MIMO communication system500including a base station102and a UE104. The MIMO communication system500may illustrate aspects of the wireless communication access network100described with reference toFIG.1. The base station102may be an example of aspects of the base station102described with reference toFIG.1. The base station102may be equipped with antennas534and535, and the UE104may be equipped with antennas552and553. In the MIMO communication system500, the base station102may be able to send data over multiple communication links at the same time. Each communication link may be called a “layer” and the “rank” of the communication link may indicate the number of layers used for communication. For example, in a 2×2 MIMO communication system where base station102transmits two “layers,” the rank of the communication link between the base station102and the UE104is two. At the base station102, a transmit (Tx) processor520may receive data from a data source. The transmit processor520may process the data. The transmit processor520may also generate control symbols or reference symbols. A transmit MIMO processor530may perform spatial processing (e.g., precoding) on data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to the transmit modulator/demodulators532and533. Each modulator/demodulator532through533may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator/demodulator532through533may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a DL signal. In one example, DL signals from modulator/demodulators532and533may be transmitted via the antennas534and535, respectively. The UE104may be an example of aspects of the UEs104described with reference toFIGS.1-2. At the UE104, the UE antennas552and553may receive the DL signals from the base station102and may provide the received signals to the modulator/demodulators554and555, respectively. Each modulator/demodulator554through555may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator554through555may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector556may obtain received symbols from the modulator/demodulators554and555, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (Rx) processor558may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE104to a data output, and provide decoded control information to a processor580, or memory582. The processor580may in some cases execute stored instructions to instantiate a communicating component242(see e.g.,FIGS.1and2). On the uplink (UL), at the UE104, a transmit processor564may receive and process data from a data source. The transmit processor564may also generate reference symbols for a reference signal. The symbols from the transmit processor564may be precoded by a transmit MIMO processor566if applicable, further processed by the modulator/demodulators554and555(e.g., for SC-FDMA, etc.), and be transmitted to the base station102in accordance with the communication parameters received from the base station102. At the base station102, the UL signals from the UE104may be received by the antennas534and535, processed by the modulator/demodulators532and533, detected by a MIMO detector536if applicable, and further processed by a receive processor538. The receive processor538may provide decoded data to a data output and to the processor540or memory542. The processor540may in some cases execute stored instructions to instantiate a communicating component242(see e.g.,FIGS.1and3). The components of the UE104may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each of the noted modules may be a means for performing one or more functions related to operation of the MIMO communication system500. Similarly, the components of the base station102may, individually or collectively, be implemented with one or more application specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Each of the noted components may be a means for performing one or more functions related to operation of the MIMO communication system500. The following aspects are illustrative only and aspects thereof may be combined with aspects of other embodiments or teaching described herein, without limitation. Aspect 1 is a method for wireless communication of a node including configuring a beam for communicating over a wireless channel, where the beam is associated with a channel access class based on a threshold for channel access and having at least one of a defined maximum COT or a defined minimum gap between communications, and communicating over the wireless channel using the beam and based on at least one of the defined COT or the defined minimum gap. In Aspect 2, the method of claim1includes where the threshold for channel access corresponds to a threshold for narrow-beam channel access without using LBT. In Aspect 3, the method of Aspect 2 includes where the beam is associated with the channel access class based on a determination that at least one of an EIRP spherical measurement, or a CDF thereof, of the beam achieves the threshold. In Aspect 4, the method of Aspect 3 includes where at least one of the EIRP spherical measurement, or the CDF thereof, of the beam is hardcoded in a memory of the node. In Aspect 5, the method of any of Aspects 2 to 4 includes where the node stores a configuration of multiple channel access classes to thresholds for narrow-beam channel access without using LBT, and where the beam is associated with the channel access class based on determining the channel access class from the configuration for which at least one of the EIRP spherical measurement, or the CDF thereof, achieves a corresponding threshold of the thresholds. In Aspect 6, the method of Aspect 5 includes where the configuration indicates at least one of the defined COT or the defined minimum gap as associated with the channel access class. In Aspect 7, the method of any of Aspects 5 or 6 includes where the configuration indicates a smallest gap for a highest priority channel access class of the channel access classes. In Aspect 8, the method of any of Aspects 5 or 6 includes where the configuration indicates a largest gap for a highest priority channel access class of the channel access classes. In Aspect 9, the method of any of Aspects 5 or 6 includes where the configuration indicates a same gap for each of the channel access classes. In Aspect 10, the method of any of Aspects 5 to 9 includes where the configuration indicates, for a channel access class of the channel access classes having a highest threshold, at least one of no limit on the defined COT or a defined minimum gap of zero. In Aspect 11, the method of any of Aspects 5 to 10 includes where the configuration indicates the defined minimum gap as a fixed gap for multiple ones of the channel access classes. In Aspect 12, the method of any of Aspects 5 to 10 includes where the configuration indicates the defined minimum gap for each of the channel access classes as proportional to the defined COT for each of the channel access classes, wherein the defined COT for each of the channel access classes is less than or equal to a defined maximum COT for each of the channel access classes. In Aspect 13, the method of any of Aspects 5 to 10 includes where the configuration indicates the defined minimum gap for each of the channel access classes as a minimum of a fixed gap or a proportional gap that is proportional to the defined COT for each of the channel access classes, wherein the defined COT for each of the channel access classes is less than or equal to a defined maximum COT for each of the channel access classes. In Aspect 14, the method of any of Aspects 5 to 10 includes where the configuration indicates the defined minimum gap for each of the channel access classes as a maximum of a fixed gap or a proportional gap that is proportional to the defined COT for each of the channel access classes, wherein the defined COT for each of the channel access classes is less than or equal to a defined maximum COT for each of the channel access classes. In Aspect 15, the method of any of Aspects 5 to 14 includes receiving the configuration from another node. Aspect 16 is an apparatus for wireless communication including a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the memory and the transceiver, where the one or more processors are configured to execute the instructions to cause the apparatus to perform any of the methods of Aspects 1 to 15. Aspect 17 is an apparatus for wireless communication including means for performing any of the methods of Aspects 1 to 15. Aspect 18 is a computer-readable medium including code executable by one or more processors for wireless communications, the code including code for performing any of the methods of Aspects 1 to 15. The above detailed description set forth above in connection with the appended drawings describes examples and does not represent the only examples that may be implemented or that are within the scope of the claims. The term “example,” when used in this description, means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and apparatuses are shown in block diagram form in order to avoid obscuring the concepts of the described examples. Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof. The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a specially programmed device, such as but not limited to a processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. A specially programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a specially programmed processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, “or” as used in a list of items prefaced by “at least one of” indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media. The previous description of the disclosure is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the common principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Furthermore, although elements of the described aspects and/or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. | 61,914 |
11943759 | While features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION Acronyms Various acronyms are used throughout the present disclosure. Definitions of the most prominently used acronyms that may appear throughout the present disclosure are provided below:UE: User EquipmentRF: Radio FrequencyBS: Base StationGSM: Global System for Mobile CommunicationUMTS: Universal Mobile Telecommunication SystemLTE: Long Term EvolutionNR: New RadioTX: Transmission/TransmitRX: Reception/ReceiveLAN: Local Area NetworkWLAN: Wireless LANAP: Access PointRAT: Radio Access TechnologyIEEE: Institute of Electrical and Electronics EngineersWi-Fi: Wireless Local Area Network (WLAN) RAT based on the IEEE 802.11 standards Terms The following is a glossary of terms that may appear in the present application: Memory Medium—Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may comprise other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer system for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors. Carrier Medium—a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals. Computer System (or Computer)—any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term “computer system” may be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium. User Equipment (UE) (or “UE Device”)—any of various types of computer systems or devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), tablet computers (e.g., iPad™, Samsung Galaxy™), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), wearable devices (e.g., smart watch, smart glasses), laptops, PDAs, portable Internet devices, music players, data storage devices, or other handheld devices, etc. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication. Wireless Device—any of various types of computer systems or devices that perform wireless communications. A wireless device can be portable (or mobile) or may be stationary or fixed at a certain location. A UE is an example of a wireless device. Communication Device—any of various types of computer systems or devices that perform communications, where the communications can be wired or wireless. A communication device can be portable (or mobile) or may be stationary or fixed at a certain location. A wireless device is an example of a communication device. A UE is another example of a communication device. Base Station (BS)—The term “Base Station” has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system. Processing Element (or Processor)—refers to various elements or combinations of elements that are capable of performing a function in a device, e.g. in a user equipment device or in a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, individual processors, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above. Wi-Fi—The term “Wi-Fi” has the full breadth of its ordinary meaning, and at least includes a wireless communication network or RAT that is serviced by wireless LAN (WLAN) access points and which provides connectivity through these access points to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards and are marketed under the name “Wi-Fi”. A Wi-Fi (WLAN) network is different from a cellular network. Automatically—refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus the term “automatically” is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system must update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed in response to actions the user has taken. Configured to—Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits. Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112, paragraph six, interpretation for that component. FIGS.1and2—Exemplary Communication System FIG.1illustrates an exemplary (and simplified) wireless communication system in which aspects of this disclosure may be implemented, according to some embodiments. It is noted that the system ofFIG.1is merely one example of a possible system, and embodiments may be implemented in any of various systems, as desired. As shown, the exemplary wireless communication system includes a base station102which communicates over a transmission medium with one or more (e.g., an arbitrary number of) user devices106A,106B, etc. through106N. Each of the user devices may be referred to herein as a “user equipment” (UE) or UE device. Thus, the user devices106are referred to as UEs or UE devices. The base station102may be a base transceiver station (BTS) or cell site, and may include hardware and/or software that enables wireless communication with the UEs106A through106N. If the base station102is implemented in the context of LTE, it may alternately be referred to as an ‘eNodeB’ or ‘eNB’. If the base station102is implemented in the context of 5G NR, it may alternately be referred to as a ‘gNodeB’ or ‘gNB’. The base station102may also be equipped to communicate with a network100(e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station102may facilitate communication among the user devices and/or between the user devices and the network100. The communication area (or coverage area) of the base station may be referred to as a “cell.” As also used herein, from the perspective of UEs, a base station may sometimes be considered as representing the network insofar as uplink and downlink communications of the UE are concerned. Thus, a UE communicating with one or more base stations in the network may also be interpreted as the UE communicating with the network. The base station102and the user devices may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), LAA/LTE-U, 5G NR, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), Wi-Fi, etc. Base station102and other similar base stations operating according to the same or a different cellular communication standard may thus be provided as one or more networks of cells, which may provide continuous or nearly continuous overlapping service to UE106and similar devices over a geographic area via one or more cellular communication standards. Note that a UE106may be capable of communicating using multiple wireless communication standards. For example, a UE106might be configured to communicate using either or both of a 3GPP cellular communication standard or a 3GPP2 cellular communication standard. In some embodiments, the UE106may be configured to implement techniques for dynamically adapting bandwidth use using network scheduling information in a cellular communication system, at least according to the various methods as described herein. The UE106might also or alternatively be configured to communicate using WLAN, BLUETOOTH™, one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one and/or more mobile television broadcasting standards (e.g., ATSC-M/H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible. FIG.2illustrates an exemplary user equipment106(e.g., one of the devices106A through106N) in communication with the base station102, according to some embodiments. The UE106may be a device with wireless network connectivity such as a mobile phone, a hand-held device, a wearable device, a computer or a tablet, or virtually any type of wireless device. The UE106may include a processor (processing element) that is configured to execute program instructions stored in memory. The UE106may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE106may include a programmable hardware element such as an FPGA (field-programmable gate array), an integrated circuit, and/or any of various other possible hardware components that are configured to perform (e.g., individually or in combination) any of the method embodiments described herein, or any portion of any of the method embodiments described herein. The UE106may be configured to communicate using any of multiple wireless communication protocols. For example, the UE106may be configured to communicate using two or more of CDMA2000, LTE, LTE-A, 5G NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible. The UE106may include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards. In some embodiments, the UE106may share one or more parts of a receive chain and/or transmit chain between multiple wireless communication standards. The shared radio may include a single antenna, or may include multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. In some embodiments, the UE106may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE106may include one or more radios that are shared between multiple wireless communication protocols, and one or more radios that are used exclusively by a single wireless communication protocol. For example, the UE106may include a shared radio for communicating using either of LTE or CDMA2000 1×RTT (or LTE or NR, or LTE or GSM), and separate radios for communicating using each of Wi-Fi and BLUETOOTH™. Other configurations are also possible. FIG.3—Block Diagram of an Exemplary UE Device FIG.3illustrates a block diagram of an exemplary UE106, according to some embodiments. As shown, the UE106may include a system on chip (SOC)300, which may include portions for various purposes. For example, as shown, the SOC300may include processor(s)302which may execute program instructions for the UE106and display circuitry304which may perform graphics processing and provide display signals to the display360. The processor(s)302may also be coupled to memory management unit (MMU)340, which may be configured to receive addresses from the processor(s)302and translate those addresses to locations in memory (e.g., memory306, read only memory (ROM)350, NAND flash memory310) and/or to other circuits or devices, such as the display circuitry304, radio330, connector I/F320, and/or display360. The MMU340may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU340may be included as a portion of the processor(s)302. As shown, the SOC300may be coupled to various other circuits of the UE106. For example, the UE106may include various types of memory (e.g., including NAND flash310), a connector interface320(e.g., for coupling to a computer system, dock, charging station, etc.), the display360, and wireless communication circuitry330(e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH™, Wi-Fi, GPS, etc.). The UE device106may include at least one antenna (e.g.,335a), and possibly multiple antennas (e.g., illustrated by antennas335aand335b), for performing wireless communication with base stations and/or other devices. Antennas335aand335bare shown by way of example, and UE device106may include fewer or more antennas. Overall, the one or more antennas are collectively referred to as antenna335. For example, the UE device106may use antenna335to perform the wireless communication with the aid of radio circuitry330. As noted above, the UE may be configured to communicate wirelessly using multiple wireless communication standards in some embodiments. As described further subsequently herein, the UE106(and/or base station102) may include hardware and software components for implementing methods for at least UE106to dynamically adapt bandwidth use using network scheduling information in a cellular communication system. The processor(s)302of the UE device106may be configured to implement part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, processor(s)302may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Furthermore, processor(s)302may be coupled to and/or may interoperate with other components as shown inFIG.3, to implement such techniques in a cellular communication system according to various embodiments disclosed herein. Processor(s)302may also implement various other applications and/or end-user applications running on UE106. In some embodiments, radio330may include separate controllers dedicated to controlling communications for various respective RAT standards. For example, as shown inFIG.3, radio330may include a Wi-Fi controller332, a cellular controller (e.g. NR controller)334, and BLUETOOTH™ controller336, and in at least some embodiments, one or more or all of these controllers may be implemented as respective integrated circuits (ICs or chips, for short) in communication with each other and with SOC300(and more specifically with processor(s)302). For example, Wi-Fi controller332may communicate with cellular controller334over a cell-ISM link or WCI interface, and/or BLUETOOTH™ controller336may communicate with cellular controller334over a cell-ISM link, etc. While three separate controllers are illustrated within radio330, other embodiments have fewer or more similar controllers for various different RATs that may be implemented in UE device106. FIG.4—Block Diagram of an Exemplary Base Station FIG.4illustrates a block diagram of an exemplary base station102, according to some embodiments. It is noted that the base station ofFIG.4is merely one example of a possible base station. As shown, the base station102may include processor(s)404which may execute program instructions for the base station102. The processor(s)404may also be coupled to memory management unit (MMU)440, which may be configured to receive addresses from the processor(s)404and translate those addresses to locations in memory (e.g., memory460and read only memory (ROM)450) or to other circuits or devices. The base station102may include at least one network port470. The network port470may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices106, access to the telephone network as described above inFIGS.1and2. The network port470(or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices106. In some cases, the network port470may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider). The base station102may include at least one antenna434, and possibly multiple antennas. The antenna(s)434may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices106via radio430. The antenna(s)434communicates with the radio430via communication chain432. Communication chain432may be a receive chain, a transmit chain or both. The radio430may be designed to communicate via various wireless telecommunication standards, including, but not limited to, NR, LTE, LTE-A WCDMA, CDMA2000, etc. The processor404of the base station102may be configured to implement and/or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor404may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. In the case of certain RATs, for example Wi-Fi, base station102may be designed as an access point (AP), in which case network port470may be implemented to provide access to a wide area network and/or local area network (s), e.g. it may include at least one Ethernet port, and radio430may be designed to communicate according to the Wi-Fi standard. The base station102may operate according to the various methods as disclosed herein for wireless devices to dynamically adapt bandwidth use using network scheduling information in a cellular communication system. FIGS.5-6—Dynamically Adapting Bandwidth Use At least in some cellular communication systems, wideband cells may be provided by a cellular network. A wideband cell may include multiple bandwidth parts, e.g., such that it may be possible for a wireless device to be configured to utilize just a portion of the total cell bandwidth at a given time.FIG.5illustrates a possible representation of such a wideband cell including multiple possible bandwidth parts, according to some embodiments. In the illustrated example, the wideband (WB) cell may include four bandwidth parts (BWPs), i.e., BWP#0, BWP#1, BWP#2, and BWP#3. In other scenarios, different configurations (e.g., including a different number of BWPs, and/or any of various other possible differences) may also be possible for a WB (or other) cell. At least in some instances, different BWPs may include different amounts of bandwidth. In some systems (e.g., at least some 5G NR deployments), it may be the case that a wireless device can only work on one BWP at a time (e.g., per component carrier) for each of uplink and downlink, though multiple BWPs may be configured for a given wireless device. For example, a wireless device may be configured to monitor a downlink control channel and perform data transmission/reception on an activated BWP, but may be configured to not monitor the downlink control channel or perform data transmission/reception on inactive BWPs. For example, according to 3GPP Release 15, it may be the case that a maximum of 4 BWPs for downlink and a maximum of 4 BWPs for uplink can be configured as a set, with a maximum of 1 downlink BWP and 1 uplink BWP being active at a time, for each of the component carriers (serving cells). As another possibility, it may be the case that a wireless device can operate on two active uplink BWPs at a time, in at least some instances, for example in the uplink if it is configured with a supplementary uplink (SUL) carrier, such as described in 3GPP TS 38.331 version 15.3.0, p. 156. Other configurations are also possible. Any of a variety of techniques may be used for switching between active/activated BWPs. Two possible examples may include explicit and implicit activation techniques. When explicitly activating a BWP, signaling may explicitly be provided to a wireless device indicating that a certain BWP is being activated for the wireless device, for example using downlink control information. Implicitly activating a BWP may be based at least in part on a BWP inactivity timer. In such a case, a wireless device may be configured to have a default BWP, and may start the BWP inactivity timer when switching to a non-default BWP. Upon timer expiry, the wireless device may fallback to the default BWP, thus implicitly activating the default BWP. At least in some instances, it may be the case that the BWP inactivity timer can be restarted (e.g., extending the duration for which the non-default BWP is activated) when a successfully decoded downlink control information communication scheduling downlink data is received by the wireless device, and/or under one or more other conditions. Allowing a wireless device to work on a bandwidth smaller than the entire cell bandwidth using such techniques may be beneficial, at least in some instances, for example with respect to wireless device power consumption, improving support for wireless devices that have lower bandwidth capabilities, and/or for providing interference mitigation qualities, among various possibilities. However, it may be the case that there is no guarantee that such a bandwidth part framework is actually used to provide wireless device power consumption reduction benefits. For example, due to the signaling related overhead and increased complexity to network schedulers, it may be the case that bandwidth part changes may not be sufficiently dynamic to sufficiently enhance wireless device power savings. Accordingly, it may be beneficial to provide a mechanism for a wireless device to perform bandwidth adaptation, e.g., based on the wireless device's own decision-making, to improve the power consumption profile of the wireless device without necessarily requiring bandwidth part changes. Such a mechanism could also be supported by additional signaling and/or rules agreed upon between the network and the wireless device. Accordingly,FIG.6is a flowchart diagram illustrating a method for a wireless device (e.g., a wireless user equipment (UE) device) to dynamically adapt its bandwidth use using network scheduling information in a cellular communication system. Aspects of the method ofFIG.6may be implemented by a wireless device, e.g., in conjunction with a cellular base station, such as a UE106and a BS102illustrated in and described with respect to various of the Figures herein, or more generally in conjunction with any of the computer circuitry, systems, devices, elements, or components shown in the above Figures, among others, as desired. For example, a processor (and/or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and/or other method elements. Note that while at least some elements of the method ofFIG.6are described in a manner relating to the use of communication techniques and/or features associated with NR and/or 3GPP specification documents, such description is not intended to be limiting to the disclosure, and aspects of the method ofFIG.6may be used in any suitable wireless communication system, as desired. In various embodiments, some of the elements of the methods shown may be performed concurrently, in a different order than shown, may be substituted for by other method elements, or may be omitted. Additional method elements may also be performed as desired. As shown, the method ofFIG.6may operate as follows. In602, the wireless device and the cellular base station may establish a wireless link. According to some embodiments, the wireless link may include a cellular link according to 5G NR. For example, the wireless device may establish a session with an AMF entity of the cellular network by way of a gNB that provides radio access to the cellular network. Note that the cellular network may also or alternatively operate according to another cellular communication technology (e.g., LTE, UMTS, CDMA2000, GSM, etc.), according to various embodiments. Establishing the wireless link may include establishing a RRC connection with a serving cellular base station, at least according to some embodiments. Establishing the RRC connection may include configuring various parameters for communication between the wireless device and the cellular base station, establishing context information for the wireless device, and/or any of various other possible features, e.g., relating to establishing an air interface for the wireless device to perform cellular communication with a cellular network associated with the cellular base station. After establishing the RRC connection, the wireless device may operate in a RRC connected state. According to some embodiments, during RRC connection establishment, the cellular base station may provide an indication of a set of possible scheduling gap values that can be used by the cellular base station when communicating with the wireless device. Alternatively, such information could be provided in broadcast system information, or may not be provided by the cellular base station. For example, it may be the case that possible scheduling gap values are pre-agreed between the wireless device and the cellular base station, e.g., based on proprietary agreements and/or because such values are specified in cellular communication standards documents for a cellular communication technology according to which the wireless device and the cellular base station are communicating. In604, the wireless device may receive network scheduling information from the cellular base station. For example, the wireless device may monitor a control channel (e.g., a physical downlink control channel (PDCCH)) for information scheduling one or more communications between the network and the wireless device. In some instances, the wireless device may receive control information in a communication slot that indicates that downlink traffic is scheduled for the same slot in which the control information is received (e.g., if same slot scheduling is configured, and is used by the network in that communication slot). In some instances, the wireless device may receive control information in a communication slot that indicates that downlink traffic is scheduled for a different slot than the slot in which the control information is received (e.g., if cross slot scheduling is configured, and is used by the network in that communication slot). In some instances, the wireless device may determine that there is no scheduling information for the wireless device on the control channel in a given slot. Other scenarios may also be possible. In606, the wireless device may dynamically select a receive bandwidth for receiving transmissions from the cellular base station based at least in part on the network scheduling information. The receive bandwidth may be selected from multiple possible bandwidths. As one possibility, the receive bandwidth may be selected from either a bandwidth associated with a full active bandwidth part of the wireless device (e.g., which may approximate or be slightly wider than the full active bandwidth part), or a bandwidth associated with control channel resources of the active bandwidth part of the wireless device (e.g., which may approximate or be slightly wider than the portion of the bandwidth part on which control channel resources are provided). In such a case, the bandwidth associated with the control channel resources may include less bandwidth (e.g., a narrower bandwidth) than the bandwidth associated with the full active bandwidth part. The wireless device may select the full active bandwidth part bandwidth during slots when the wireless device has reason to expect that traffic that uses the full active bandwidth part may be transmitted to the wireless device by the cellular base station, and may select the bandwidth associated with the control channel resources during slots when the wireless device has reason to expect that no traffic using bandwidth beyond that of the control channel resources may be transmitted to the wireless device by the cellular base station, at least as one possibility. Thus, the wireless device may be able to operate using a reduced receive bandwidth (e.g., compared with the bandwidth of its active bandwidth part) during at least a portion of its operation, which may in turn reduce the power consumption of the wireless device (e.g., in comparison to always using a receive bandwidth at least equal to the bandwidth of the active bandwidth part when operating in connected mode). For example, according to some embodiments, the wireless device may select the bandwidth associated with the full active bandwidth part of the wireless device for slots that are scheduled by the network scheduling information, and may select the bandwidth associated with the control channel resources of the active bandwidth part for slots that are not scheduled by the network scheduling information. It should be noted, however, that a certain amount of time may be required for a wireless device to modify its receive bandwidth, such that it may not be possible to switch from the bandwidth associated with the control channel resources to the bandwidth associated with the full active bandwidth part of the wireless device within the span of time of a single slot, at least according to some embodiments. Accordingly, it may be the case that the wireless device only performs such dynamic receive bandwidth adaptation when there is at least a minimum time gap between receiving network scheduling information scheduling a downlink communication and the scheduled downlink communication that would be sufficient to adjust its receive bandwidth. One possible way to determine whether such a minimum time gap is supported may be based on network scheduling configuration information. For example, the wireless device may receive network scheduling configuration information indicating a set of values that are configured as the possible minimum time gap (e.g., in slots, or in any other denomination) between when a downlink communication is scheduled and when the downlink communication is performed. If the indicated configured minimum possible time gap is sufficient for the wireless device to adjust its receive bandwidth, then the wireless device may dynamically adapt its receive bandwidth. For example, consider a scenario in which a wireless device can adjust its receive bandwidth within the time span of one slot. In such a scenario, as long as the minimum configured time gap is at least one slot (e.g., only cross slot scheduling is configured as a possibility), the wireless device may determine to dynamically adapt its receive bandwidth, while if the minimum configured time gap can be as few as zero slots (e.g., if same slot scheduling is configured as a possibility), the wireless device may determine not to dynamically adapt its receive bandwidth. This may allow the wireless device to avoid potentially missing a downlink communication that was scheduled using same slot scheduling in a slot for which the bandwidth associated with the control channel resources of the active bandwidth part was selected. In some instances, the cellular base station may be configured to support such dynamic bandwidth adaptation by the wireless device (and possibly other wireless devices), for example by determining to use a certain minimum time gap between when a downlink communication is scheduled and when the downlink communication is performed under certain agreed-upon circumstances, which may for example correspond to periods of low traffic activity. For example, at least according to some embodiments, the cellular base station and the wireless device may maintain a discontinuous reception (DRX) inactivity timer for the RRC connection while operating in connected mode, e.g., to help determine when to transition to connected mode DRX (C-DRX). Whenever the DRX inactivity timer is relatively low, there may be a greater likelihood of packet activity than when the DRX inactivity timer is relatively high, at least in some instances. Accordingly, the cellular base station could determine to use at least a certain minimum time gap (e.g., at least one slot, as one possibility) between when a downlink communication is scheduled and when the downlink communication is performed when the value of the DRX inactivity timer is greater than a certain (e.g., predetermined) threshold. According to some embodiments, the cellular base station may provide an indication to the wireless device that it will select such a minimum time gap between providing scheduling information for a downlink communication and performing the downlink communication when the value of the DRX inactivity timer is greater than the predetermined threshold, e.g., so that the wireless device can determine whether to implement dynamic receive bandwidth adaptation based on the value of the DRX inactivity timer. Alternatively, such behavior by the cellular base station may be known to the wireless device without an explicit indication, e.g., if such behavior is specified according to a cellular communication standard according to which the wireless device and the cellular base station are communicating, or if a proprietary agreement is in place (e.g., such as between an infrastructure vendor that provided the cellular base station and a wireless device vendor that provided the wireless device), among various possibilities. As another possibility, at least according to some embodiments, the cellular base station may (e.g., after determining that the DRX inactivity timer for the RRC connection with the wireless device has expired and transitioning to C-DRX operation with the wireless device) determine to use at least a certain minimum time gap (e.g., at least one slot, as one possibility) between when a downlink communication is scheduled and when the downlink communication is performed when providing scheduling information during a C-DRX on duration. In a similar manner as previously described herein, the cellular base station may explicitly indicate its use of a minimum time gap between scheduling and performing a downlink communication during a C-DRX on duration, or such use may be implicitly understood between the cellular base station and the wireless device, e.g., based on cellular communication standard specifications, proprietary agreement, etc. Thus, if the cellular base station is known to support use of a certain minimum time gap under certain circumstances such as when a DRX inactivity timer has a value greater than a predetermined threshold or during a C-DRX on duration, the wireless device may also or alternatively determine to dynamically adapt its receive bandwidth based at least in part on whether such circumstances are occurring. For example, according to some embodiments, if network scheduling configuration information indicates that a minimum time gap between scheduling and performing downlink communications is less than the wireless device requires to modify its receive bandwidth, the wireless device may not dynamically select its receive bandwidth for receiving transmissions when the DRX inactivity timer value is below the predetermined threshold, but the wireless device may dynamically select its receive bandwidth for receiving transmissions when the DRX inactivity timer value is above the predetermined threshold. As another example, the wireless device may select the bandwidth associated with control channel resources of the active bandwidth part for C-DRX on duration operation if the cellular base station is known to support use of a sufficient minimum time gap during C-DRX on duration. Thus, according to some embodiments, the wireless device may determine to dynamically select its receive bandwidth for receiving transmissions only when a minimum time gap is configured that is sufficient to allow for modifying the receive bandwidth in time to receive all scheduled downlink transmissions. In other words, the wireless device may select a receive bandwidth that is narrower than the full active bandwidth part bandwidth only during slots when the likelihood of data traffic arrival is zero, according to such embodiments. However, according to some embodiments, it may also be possible for the wireless device to determine the likelihood of traffic arrival in each slot, and to dynamically select its receive bandwidth for receiving transmissions based at least in part on such a determined likelihood, such that the likelihood threshold for selecting a receive bandwidth that is narrower than the full active bandwidth part bandwidth is greater than zero. In other words, according to such embodiments, it may be possible for the wireless device to select a receive bandwidth that is narrower than the full active bandwidth part bandwidth for a slot even when there may be a chance that traffic arrives during that slot, e.g., as long as the likelihood of such arrival is determined to be below a certain threshold. For example, according to some embodiments, the wireless device may dynamically select a first receive bandwidth (e.g., the bandwidth associated with the control channel resources) for receiving transmissions for communication slots for which the determined likelihood of traffic arrival is low (e.g., below a predetermined or adaptive threshold), and dynamically select a second receive bandwidth (e.g., the bandwidth associated with the full active bandwidth part) for receiving transmissions for communication slots for which the determined likelihood of traffic arrival is high (e.g., above the predetermined or adaptive threshold), where the first receive bandwidth is narrower than the second receive bandwidth. The likelihood of traffic arrival may be determined in any of various ways, based on any of various considerations. Such considerations may include any or all of those considerations previously described herein, potentially including the configured minimum gap between receiving network scheduling information and performing communication scheduled by the network scheduling information as indicated by the cellular base station, the current value of the DRX inactivity timer, whether network scheduling information indicating a scheduled downlink communication has been received (and for which slot the downlink communication is scheduled, and/or if such network scheduling information has been received), whether the wireless device is in a C-DRX on-duration. Additionally or alternatively, the determination of the likelihood of traffic arrival may be based on recent traffic history (e.g., how often traffic has been arriving), active traffic type(s), device type, battery reserve levels, and/or any of various other considerations. Further, if desired, the threshold of likelihood of traffic arrival based on which the wireless device dynamically selects its receive bandwidth may also or alternatively be dynamically selected based on any or all such consideration, at least according to some embodiments. Note that when using such an approach, it may be the case that the wireless device can miss initial downlink transmissions on some occasions. For example, the wireless device may receive network scheduling information scheduling a downlink communication from the cellular base station in a certain slot, for which the wireless device had already selected a receive bandwidth that is narrower than the bandwidth of the scheduled downlink communication. In such a case, the wireless device may select a wider receive bandwidth (e.g., the bandwidth associated with the full active bandwidth part) for one or more subsequent slots based on missing the initial downlink communication, e.g., at least until a retransmission of the scheduled downlink communication is received. Thus, even if some initial transmissions may be missed by a wireless device when using a likelihood of traffic arrival based approach (e.g., and in which the likelihood-of-arrival threshold for selecting a bandwidth that is narrower than the full active bandwidth part is greater than zero) to dynamically selecting its receive bandwidth, the wireless device may still be able to receive the data during a retransmission attempt by the cellular base station. Further, in such a case, if the wireless device can receive the initial transmission partially (e.g., with its relatively narrow bandwidth), then the received partial signal could be combined with a retransmission received with a wider bandwidth to improve decoding performance. FIGS.7-12and Additional Information FIGS.7-12illustrate various aspects of possible schemes that could be used for dynamically adapting bandwidth use using network scheduling information in a cellular communication system, according to some embodiments. Note thatFIGS.7-12and the following information are provided as being illustrative of further considerations and possible implementation details relating to the method ofFIG.6, and are not intended to be limiting to the disclosure as a whole. Numerous variations and alternatives to the details provided herein below are possible and should be considered within the scope of the disclosure. FIG.7illustrates aspects of exemplary possible network scheduling approaches, according to some embodiments. In NR, the slot in which the physical downlink control channel (PDCCH) is transmitted can be different from the slot in which the corresponding physical downlink shared channel (PDSCH) is transmitted. The distance between such slots may be indicated using a scheduling parameter that may be referred to as ‘K0’. K0 may denote the distance between the PDCCH and the corresponding PDSCH in slots. Thus, when K0=0, the PDCCH scheduling a downlink transmission on the PDSCH may be transmitted in the same slot as the corresponding PDSCH is transmitted, such as illustrated in the upper portion ofFIG.7. This may also be referred to as same slot scheduling. When K0>0, the PDCCH scheduling a downlink transmission on the PDSCH may be transmitted in a different slot than the corresponding PDSCH is transmitted, such as illustrated in the lower portion ofFIG.7. This may also be referred to as cross slot scheduling. It may be generally beneficial for wireless device power saving to use K0 values greater than 0, at least according to some embodiments. For example, when the minimum K0 value is greater than 0 and aperiodic CSI-RS triggering offset is not within a certain duration, a wireless device may be able to switch to a micro sleep operation right away after PDCCH reception, as the wireless device may know that no additional PDSCH and CSI signal reception is needed within the given duration (e.g., the same slot). As previously noted herein, NR may also support wireless device channel bandwidth adaptation through the BWP framework, according to which the wireless device channel bandwidth can be changed by the network through a BWP change. However, as further previously noted, it may be the case that such a BWP framework may not be utilized in a sufficiently dynamic manner by the network to provide as much wireless device power savings as could be possible. Accordingly, mechanisms for dynamic bandwidth adaptation by wireless devices, e.g., that can be implemented at a wireless device using decision making by the wireless device, may provide additional power consumption reduction benefits to wireless devices. Such mechanisms may also potentially benefit further from network support for certain additional signaling and/or rules to improve the wireless devices' capability to effectively implement the mechanisms. One possible approach to such dynamic bandwidth adaptation may be based at least in part on possible K0 values that are configured for a wireless device. For example, if all possible K0 values that could potentially be signaled to a wireless device by downlink control information are greater than 0, this may indicate that there is a guaranteed time gap between the PDCCH and the corresponding PDSCH, which may be long enough for the wireless device to adjust its RF bandwidth for PDSCH reception. Thus, as one possible approach, when a wireless device knows that potential K0 values that can be indicated are all larger than 0, in a given slot n, if the wireless device determines that there is no PDSCH to receive, then the wireless device could reduce its channel bandwidth to the point where it can monitor the control resource set (CORESET) only, to reduce power consumption. If, however, in the given slot n, if the wireless device is supposed to receive data on the PDSCH based on previously received downlink control information and the wireless device's current channel bandwidth is smaller than the size of the configured BWP, the wireless device could open up its RF channel bandwidth to the size of the configured BWP to receive the PDSCH. Thus, the wireless device may open up its RF channel bandwidth only when there is a scheduled PDSCH.FIG.8is a time-frequency diagram illustrating how such dynamic bandwidth adaptation might proceed using such an approach in an exemplary scenario, according to some embodiments. The value of the drx-inactivityTimer in DRX mode may roughly capture the intensity of traffic arrival, e.g., since this inactivity timer may be reset every time a new packet arrives, at least according to some embodiments. When the traffic arrival rate is low, it may be beneficial to use a minimum K0>0 requirement, e.g., to give wireless devices the opportunity to operate in narrower bandwidth for power savings. Accordingly, as a further possibility, when DRX is configured (e.g., when a DRX inactivity timer is running while operating in connected mode), the network may conform to a minimum K0>0 requirement when the current drx-inactivityTimer value is greater than a certain threshold (e.g., since this time period may correspond to a window of low traffic arrival rate), but may select any K0 value configured in the network provided K0 table (e.g., a time0 domain resource allocation table) when the current drx-inactivityTimer value is less than the threshold (e.g., since this time period may correspond to a window of high traffic arrival rate). Such limiting of K0 to non-zero values during windows of low traffic arrival may increase the opportunities for wireless devices to implement dynamic bandwidth adaptation.FIGS.9-10are time-frequency diagrams illustrating how such dynamic bandwidth adaptation might proceed using such an approach in two exemplary scenarios, according to some embodiments. Additionally, when a wireless device is in C-DRX on duration (e.g., with the drx-inactivityTimer not running), there may be a high likelihood that the wireless device does not receive data actively. Thus, it may make sense to allow wireless devices to operate with narrow bandwidth while in C-DRX on duration. Accordingly, as a still further possibility, a wireless device could be configured with a K_min value, which may be greater than 0. If the drx-inactivityTimer is not running, the network may agree that the potential K0 that can be indicated is limited to K0≥K_min. In such a case, the wireless device may be able to implement dynamic bandwidth adaptation (e.g., such that a narrow bandwidth can be selected) during C-DRX on duration.FIG.11is a time-frequency diagram illustrating how such dynamic bandwidth adaptation might proceed using such an approach in an exemplary scenario, according to some embodiments. While the preceding example approaches and scenarios ofFIGS.8-11may utilize an approach to dynamic bandwidth adaptation in which an RF bandwidth that is narrower than the configured BWP is selected for a wireless device only if there is no chance of downlink traffic in a given slot, it may also be possible to use an approach to dynamic bandwidth adaptation in which an RF bandwidth that is narrower than the configured BWP can be selected for a wireless device even when there is a non-zero chance of downlink traffic in a given slot. For example, when the wireless device determines that there is a low chance of traffic arrival in a given slot, then the wireless device may choose to reduce its RF bandwidth, e.g., to monitor the CORESET only. This could potentially cause the wireless device to miss an upcoming new initial transmission which is scheduled outside of the (e.g., reduced) RF bandwidth of the wireless device. However, it may be the case that such a risk of missing a PDSCH transmission may be considered worthwhile, e.g., to reduce power consumption, particularly since the missed transport block (TB) may be retransmitted. Note that since the bandwidth reduction decision may be made by the wireless device itself, such a more flexible approach may allow the wireless device to manage its preferred trade-off between power consumption, latency, throughput, and/or other considerations in a more finely-grained manner. According to such an approach, if there is no PDSCH to receive, then the wireless device may be able to reduce its bandwidth to an extent that is wide enough to monitor its CORESET only. This reduced bandwidth may thus be smaller than the active BWP size. In this mode, the wireless device may receive PDCCH symbols only via the reduced bandwidth. The wireless device may not receive/buffer other symbols for potential PDSCH reception. Components related to PDSCH decoding could be in a low power state for this mode. Once the wireless device detects a PDCCH carrying a downlink grant, then the wireless device could miss (part of) the corresponding PDSCH, e.g., in case the PDSCH is transmitted outside of the wireless device's current reduced bandwidth. If the wireless device does detect a PDCCH carrying a grant, the wireless device may open its RF as soon as possible to cover the bandwidth of the active BWP and move to normal bandwidth mode. If the wireless device can receive the scheduled PDSCH without moving to normal bandwidth mode, the wireless device may remain in CORESET only mode. In the normal bandwidth mode, the wireless device's RF bandwidth may be wide enough to cover the full active BWP. Thus, the wireless device may be able to receive any following retransmissions for the same transport block. If the data arrival rate is determined (e.g., at a later time) to be sufficiently low, the wireless device may move back to the CORESET only mode. Note that it may be possible to support such an approach on the wireless device side without requiring any cellular standard specification changes or specific network support, though it may be possible that such support could improve the efficiency of such an approach, at least according to some embodiments.FIG.12is a time-frequency diagram illustrating how such dynamic bandwidth adaptation might proceed using such an approach in an exemplary scenario, according to some embodiments. In the following further exemplary embodiments are provided. One set of embodiments may include a wireless device, comprising: an antenna; a radio coupled to the antenna; and a processing element coupled to the radio; wherein the wireless device is configured to: establish a radio resource control (RRC) connection with a cellular base station according to a first radio access technology (RAT); receive network scheduling information from the cellular base station; and dynamically select a receive bandwidth for receiving transmissions from the cellular base station based at least in part on the network scheduling information. According to some embodiments, to dynamically select the receive bandwidth, the wireless device is further configured to select the receive bandwidth from one of: a bandwidth associated with a full active bandwidth part of the wireless device; or a bandwidth associated with control channel resources of the active bandwidth part of the wireless device, wherein the bandwidth associated with control channel resources of the active bandwidth part comprises less bandwidth than the bandwidth associated with the full active bandwidth part. According to some embodiments, the wireless device is further configured to: select the bandwidth associated with the full active bandwidth part of the wireless device for slots that are scheduled by the network scheduling information; and select the bandwidth associated with control channel resources of the active bandwidth part for slots that are not scheduled by the network scheduling information. According to some embodiments, the wireless device is further configured to: select the bandwidth associated with control channel resources of the active bandwidth part for connected mode discontinuous reception on duration operation. According to some embodiments, the network scheduling information comprises network scheduling configuration information indicating whether same slot scheduling is a configured network scheduling option, wherein the wireless device is further configured to: determine to dynamically select a receive bandwidth for receiving transmissions based at least in part on the network scheduling configuration information indicating that same slot scheduling is not a configured network scheduling option, wherein a receive bandwidth for receiving transmissions is not dynamically selected when the network scheduling configuration information indicates that same slot scheduling is a configured network scheduling option. According to some embodiments, the wireless device is further configured to: determine to dynamically select a receive bandwidth for receiving transmissions based at least in part on a discontinuous reception (DRX) inactivity timer value being above a predetermined threshold, wherein a receive bandwidth for receiving transmissions is not dynamically selected when the DRX inactivity timer value is below the predetermined threshold. According to some embodiments, the wireless device is further configured to: determine a likelihood of traffic arrival at each communication slot with the cellular base station; dynamically select a first receive bandwidth for receiving transmissions for communication slots for which the determined likelihood of traffic arrival is low; and dynamically select a second receive bandwidth for receiving transmissions for communication slots for which the determined likelihood of traffic arrival is high, wherein the first receive bandwidth is narrower than the second receive bandwidth. Another set of embodiments may include an apparatus, comprising a processing element configured to cause a wireless device to: establish a radio resource control (RRC) connection with a cellular base station according to a first radio access technology (RAT); determine a likelihood of traffic arrival at each communication slot with the cellular base station; and dynamically select a receive bandwidth for each communication slot with the cellular base station based at least in part on the determined likelihood of traffic arrival. According to some embodiments, to dynamically select the receive bandwidth, the processing element is further configured to cause the wireless device select the receive bandwidth from one of: a full bandwidth of an active bandwidth part of the wireless device; or a bandwidth associated with control channel resources of the active bandwidth part of the wireless device, wherein the bandwidth associated with control channel resources of the active bandwidth part comprises less bandwidth than the full bandwidth of the active bandwidth part. According to some embodiments, to dynamically select the receive bandwidth, the processing element is further configured to cause the wireless device to: select a narrower receive bandwidth for communication slots with determined likelihood of traffic arrival below a predetermined threshold; and select a wider receive bandwidth for communication slots with determined likelihood of traffic arrival above a predetermined threshold. According to some embodiments, the likelihood of traffic arrival is determined based at least in part on a configured minimum gap between receiving network scheduling information and performing communication scheduled by the network scheduling information. According to some embodiments, the likelihood of traffic arrival is determined based at least in part on a current value of a discontinous reception (DRX) inactivity timer. According to some embodiments, the likelihood of traffic arrival is determined based at least in part on network scheduling information indicating whether traffic is scheduled at each communication slot with the cellular base station. According to some embodiments, the likelihood of traffic arrival is determined based at least in part on whether the wireless device is in a connected-mode discontinous reception on duration. According to some embodiments, the processing element is further configured to: receive network scheduling information scheduling a downlink communication from the cellular base station in a first slot, wherein the scheduled downlink communication has a wider bandwidth than a receive bandwidth that was selected for the first slot; select a receive bandwidth that is at least as wide as the first bandwidth for one or more slots subsequent to the first slot based at least in part on the receiving the network scheduling information scheduling the downlink communication in the first slot; and receive a retransmission of the downlink communication during one of the one or more slots subsequent to the first slot. A further set of embodiments may include a cellular base station, comprising: an antenna; a radio coupled to the antenna; and a processing element coupled to the radio; wherein the cellular base station is configured to: establish a radio resource control (RRC) connection with a wireless device according to a first radio access technology (RAT); maintain a discontinuous reception (DRX) inactivity timer for the RRC connection with the wireless device; and provide scheduling information for a downlink communication to the wireless device, wherein a time gap between providing the scheduling information and performing the downlink communication is selected based at least in part on a value of the DRX inactivity timer. According to some embodiments, the cellular base station is further configured to: select a minimum time gap of at least one slot between providing scheduling information for a downlink communication and performing the downlink communication when the value of the DRX inactivity timer is greater than a predetermined threshold. According to some embodiments, the cellular base station is further configured to: provide an indication to the wireless device that the cellular base station will select a minimum time gap of at least one slot between providing scheduling information for a downlink communication and performing the downlink communication when the value of the DRX inactivity timer is greater than the predetermined threshold. According to some embodiments, the cellular base station is further configured to: determine that the DRX inactivity timer for the RRC connection with the wireless device has expired; transition to a connected-mode DRX (C-DRX) operation with the wireless device; and provide scheduling information for a downlink communication to the wireless device during a C-DRX on duration, wherein a time gap between providing the scheduling information and performing the downlink communication is selected based at least in part on scheduling information being provided during a C-DRX on duration. According to some embodiments, the cellular base station is further configured to: select a minimum time gap of at least one slot between providing scheduling information for a downlink communication and performing the downlink communication when the scheduling information is being provided during a C-DRX on duration. A still further exemplary embodiment may include a method, comprising: performing, by a wireless device, any or all parts of the preceding examples. Another exemplary embodiment may include a device, comprising: an antenna; a radio coupled to the antenna; and a processing element operably coupled to the radio, wherein the device is configured to implement any or all parts of the preceding examples. A yet further exemplary embodiment may include a non-transitory computer accessible memory medium comprising program instructions which, when executed at a device, cause the device to implement any or all parts of any of the preceding examples. A still further exemplary embodiment may include a computer program comprising instructions for performing any or all parts of any of the preceding examples. Yet another exemplary embodiment may include an apparatus comprising means for performing any or all of the elements of any of the preceding examples. Still another exemplary embodiment may include an apparatus comprising a processing element configured to cause a wireless device to perform any or all of the elements of any of the preceding examples. It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users. Embodiments of the present invention may be realized in any of various forms. For example, in some embodiments, the present invention may be realized as a computer-implemented method, a computer-readable memory medium, or a computer system. In other embodiments, the present invention may be realized using one or more custom-designed hardware devices such as ASICs. In other embodiments, the present invention may be realized using one or more programmable hardware elements such as FPGAs. In some embodiments, a non-transitory computer-readable memory medium (e.g., a non-transitory memory element) may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of a method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets. In some embodiments, a device (e.g., a UE) may be configured to include a processor (or a set of processors) and a memory medium (or memory element), where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms. Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. | 68,401 |
11943760 | DETAILED DESCRIPTION Connected vehicles may rely on their perception of the environment to make decisions about how they should navigate the environment. To have such perceptions, autonomous vehicles may include a variety of sensors, such as LIDAR sensors or RADAR sensors, to capture digital representations of the environment. A vehicle's perception of its environment may be improved by gathering more perception data from another vehicle, thereby creating a more thorough perception of the vehicle's environment. However, continuously transmitting raw data may consume too much bandwidth for the transmission to be fast enough for the vehicle to processes the data in time. The embodiments of the present disclosure include systems and methods for deep cooperative feature sharing among connected vehicles, as illustrated inFIG.1. Systems and methods presented herein focus on transmitting encoded perception features in structured data to reduce bandwidth consumption. Unlike information cropping methods based on blind zone analyses and geolocation as described above, systems and methods of the present disclosure focus on information filtering technology. Systems and methods may adaptively select layers (also referred to as “channels” in the deep learning context) that assist in a vehicle's perception of its environment. The channel selection is bi-directional, meaning that channel selection could come from the transmitter vehicle, as shown inFIG.2, and/or the receiver vehicle, as shown inFIG.4. When channel selection originates from the transmitter vehicle's side, as shown inFIG.3, the transmitter vehicle selects the information that among the highest confidence levels to improve the quality of the data for the receiver vehicle, as shown inFIG.5. When channel selection originates from the receiver vehicle's side, as shown inFIG.6, the receiver vehicle requests enough information to at least compensate for the receiver vehicle's uncertainty. The uncertainty may be based on a deep neural network associated with an information filter. Referring now toFIG.1, an example system100of deep cooperative feature sharing among connected vehicles102,104is depicted. Embodiments may be divided into two working modes: a transmitter mode and a receiver mode. For purposes ofFIG.1, the vehicle102will be a transmitter vehicle and the vehicle104will be a receiver vehicle, although both vehicles may contain the same components to operate in the other mode. It should be understood, however, that a connected vehicle may act as both a transmitter vehicle and a receiver vehicle. For example, although the vehicle102is a transmitter vehicle inFIG.1, the vehicle102may simultaneously be a receiver vehicle to a third vehicle not shown inFIG.1. Similarly, although the vehicle104is a receiver vehicle inFIG.1, the vehicle104may simultaneously be a transmitter vehicle to a fourth vehicle not shown inFIG.1. Each of the connected vehicles102,104may be a vehicle including an automobile or any other passenger or non-passenger vehicle such as, for example, a terrestrial, aquatic, and/or airborne vehicle. In some embodiments, one or more of the connected vehicles102,104may be an unmanned aerial vehicle (UAV), commonly known as a drone. WhileFIG.1depicts communication between connected vehicles, the present disclosure may apply to communication between other entities, between a connected vehicle and a road side unit, between two road side units, between a connected vehicle and a mobile device such as a smartphone, and the like. Before data is transmitted, a preparatory message may be sent between the vehicles102,104. The preparatory message may comprise a position of the vehicle102,104, a heading angle of the vehicle102,104, intrinsic parameters of the sensor of the vehicle102,104, extrinsic parameters of the sensor of the vehicle102,104, or other vehicle metadata. The preparatory message may be used to align the data of the collaborative vehicle (i.e., the transmitter vehicle102) and the ego vehicle (i.e., the receiver vehicle104). After the data alignment, the transmitter vehicle102and the receiver vehicle104may work in a pipeline as shown inFIG.1. Additionally, before data is encoded, a machine learning model may be trained to engage in channel-based attention. The machine learning model may be a convolutional neural network, multi-layer perception, or the like, capable of image semantic extraction. The machine learning model may be trained to recognize subjects of interest, such as signs, vehicles, pedestrians, and any other subjects of interest in a driving environment. The training may be based on a training dataset comprising subjects of interest, such as signs, vehicles, pedestrians, and any other object in a driving environment. The training dataset and the inputs that the machine learning model analyses may be of the same format, such as images, videos, point clouds, and any other digital representation that may be captured by the sensor of a connected vehicle. The system100is formulated as an encoder-decoder complementary structure. A feature encoder module106and a feature decoder module116may be deployed onto the transmitter vehicle102and the receiver vehicle104, respectively. As shown inFIG.1, the feature encoder module106may process raw sensor data into structured data. For example, if the sensor103is a LIDAR sensor, the structured data may be a layered structure, with each layer corresponding to a channel of the LIDAR data. When engaging in the system100to share data with another connected vehicle, the transmitter vehicle102may transmit only selected layers to the other vehicle through, for example, vehicle-to-vehicle (V2V) communications. To implement the layered data weighing, a channel attention module108is utilized. The channel attention module108is a module for channel-based attention in machine learning models, such as a convolutional neural network. The channel attention module108may generate a channel attention map by exploiting the inter-channel relationship of features identified by the channel attention module108. As each channel of a feature map is considered as a feature detector, the channel attention module108determines what is meaningful in a given input data, such as a subject of interest in an image or point cloud. Based on the determination of channel attention module108, the layer may be assigned a weight to reflect the importance of the layer based on the type of features, the importance of the features, the quality of the features, confidence of the feature determination, and/or other data quality metrics. After assigning a weight to the layers, the transmitter vehicle102may select the layers with the highest weights to transmit to the receiver vehicle104. To implement layered data selection, a channel selection module110is utilized. The channel selection module110may select one or more channels among the set of channels based on the weights corresponding to each channel in the set of channels. In some embodiments, a threshold may be determined. The threshold may be based on data certainty, network constraints, vehicle processing constraints, and/or other data and/or systems constraints. The channel selection module110selects the best layers in the feature map to send to the receiver vehicle104to provide a potentially higher quality replacement for similar data in the feature map of the receiver vehicle104. The selected channels are passed to the message modulator112of the transmitter vehicle102for transmission to the receiver vehicle104. The message modulator112may process and package the selected channels for transmission to the receiver vehicle104. Once the data from the transmitter vehicle102is received by the receiver vehicle104, the receiver vehicle104continues the collaborative data sharing by fusing the received channels with the original feature channels of the receiver vehicle104, as shown inFIG.5. The received channels are passed to the channel fusion module114of the receiver vehicle104. The channel fusion module114may process and unpack the channels to prepare the data for processing by the remaining modules for deep collaborative feature sharing. Once the channels shared from the transmitter vehicle102are received and/or processed, the shared channels may replace the corresponding channels in the feature channels of the receiver vehicle104. In some embodiments, the shared channels may only replace the corresponding channels in the feature channels of the receiver vehicle104when the shared channels are an improvement over the corresponding channels. For example, when the shared channels have a higher weight than the corresponding channels in the receiver vehicle104, the shared channels may replace the corresponding channels, assuming the channels are weighed by the same process in the vehicles' collaboration process. In some embodiments, the feature decoder module116may utilize the preparatory message from the transmitter vehicle102to modify the channels shared from the transmitter vehicle102such that it is normalized according to the channels of the receiver vehicle104. Additionally or alternatively, the receiver vehicle104may also request certain channels from the transmitter vehicle102according to the feature map of the receiver vehicle104to further the collaboration between the vehicles102,104. The indices of layers with low weights values, which may represent large degrees of uncertainty, may be requested to be shared from the transmitter vehicle102. Requesting the channels that are uncertain to the receiver vehicle104may increase the certainty of the observations of the receiver vehicle104after the requested channels have been fused into the channels of the receiver vehicle104. Requesting channels from the transmitter vehicle102may occur before and/or after fusion of the shared channels of the transmitter vehicle102into the channels of the receiver vehicle104. The feature decoder module116of the receiver vehicle104may decode the structured data to sensor data that is enhanced by the highly weighed channels shared from the transmitter vehicle102. As a result, sensing by the receiver vehicle104may be enhanced to implement an improved perception task by the detection regression module118, such as subject detection, bounding box object localization, and/or other data processing techniques. Referring now toFIG.2, a flowchart of an example method200for data sharing from a transmitter vehicle perspective is depicted. Discussion ofFIG.2will be made with reference toFIG.1. The transmitter vehicle may be the transmitter vehicle102fromFIG.1, having the feature encoder module106, the channel attention module108, the channel selection module110, and the message modulator112. The receiver vehicle may be the receiver vehicle104fromFIG.1, having the channel fusion module114, the feature decoder module116, and the detection regression module118. The process begins at block202where the transmitter vehicle102obtains sensor data. The transmitter vehicle102may contain sensors103for gathering data about the vehicle's environment, such as LIDAR sensors, RADAR sensors, imaging sensors, and other object detection sensors. The present disclosure will utilize LIDAR sensors for purposes of discussion, though it should be understood that such discussion is exemplary and non-limiting. The LIDAR sensors may gather 3D point cloud data that may be then be obtained by a processor of the vehicle. The process may then move to block204. At block204, the sensor data may be encoded into structured data. The feature encoder module106may take raw sensor data as input and output structured data having a plurality of discrete units and a plurality of features. For example, the feature encoder module106may process a 3D point cloud generated by a LIDAR sensor of the transmitter vehicle102into a layered structure, the discrete units being the layers. At block206, a channel attention map may be generated. The channel attention map may be generated by the channel attention module108of the transmitter vehicle102. The channel attention module108is a module for channel-based attention in machine learning, particularly convolution neural networks. The channel attention module108may contain a machine learning model to generate a channel attention map by exploiting the inter-channel relationship of features, where layers of the structured data may be represented as channels. Each channel of the feature map is a feature detector, focusing on what is meaningful in a given input data set, as opposed to where the meaningful data is located. What is meaningful may vary in importance, and the importance of the layer based on what is determined to be meaningful may be represented as a weight value. To determine what subjects should be identified, the machine learning model of the channel attention module108may be trained to recognize subjects of interest based on training datasets comprising sets of digital representations of subjects of interest. At block208, weights corresponding to channels may be generated. In generating the channel attention map, the layered feature maps may be weighed by the channel attention module108. To determine how subjects should be weighed, the machine learning model of the channel attention module108may be trained to weigh subjects of interest based on training datasets comprising sets of digital representations of subjects of interest as well as their corresponding weights. The output of the channel attention module108is a weighted list associated with layered data. At block210, channels may be selected to be shared with the receiver vehicle104. The channel selection module110of the transmitter vehicle102may select the channels of the data to share based on the weights calculated from the channel attention module108. For example, the channel selection module110may generate a threshold for selecting channels. The threshold may be based on factors such as type of subjects identified, degree of certainty of subject identification, available bandwidth, number of channels, and/or any other metrics for selecting channels. In some embodiment, the threshold may be received from a vehicle that requested channels. At block212, the selected channels may be shared with the receiver vehicle104. The threshold calculated at block210may be used to filter out channels that have weights that are below the threshold. Channels that have weights that meet the threshold may be transmitted to the receiver vehicle104. The selected channels are passed to the message modulator112of the transmitter vehicle102for transmission to the receiver vehicle104. The message modulator112may process and package the selected channels for transmission to the receiver vehicle104. The processing and packaging may include compression, conversion, segmentation, packetization, and/or any other processing to prepare the data for transmission by a computer network such as a V2V network as described below inFIG.7. In some embodiments, the message modulator112may receive a preparatory message from the receiver vehicle104to adjust the selected channels such that the selected channels are normalized based on the receiver vehicle104. For example, a perspective of the data may be adjusted to compensate for the positioning of the receiver vehicle104to make the channels more easily fuse into the channels of the receiver vehicle104. Referring now toFIG.3, an example of channel attention and channel selection is depicted. Discussion ofFIG.3will be made with reference toFIGS.1and2. After the transmitter vehicle102has obtained sensor data in block202and encoded sensor data into structured data in block204, a channel attention map300ais generated in block206by channel attention module108. The channel attention map300amay be visualized as a set of channels302-324. Each channel302-324may have a corresponding weight as assigned in block208. For example, the channel302is 0.98, the channel304is 0.42, the channel306is 0.37, the channel308is 0.85, the channel310is 0.56, the channel312is 0.72, the channel314is 0.35, the channel316is 0.92, the channel318is 0.94, the channel320is 0.77, the channel322is 0.88, and the channel324is 0.35. After the channel attention map300ais generated in block206and weights have been assigned in block208, channels may be selected based on their weights at block210. For example, a threshold may be determined to be 0.75. Based on the threshold, selected channels300bconsisting of channel302,308,316,318,320,322may be selected because their weights are above the threshold, and thus they are likely to be an improvement in the corresponding channels of a cooperative vehicle. Referring now toFIG.4, a flowchart of an example method400for data sharing from a receiver vehicle is depicted. Discussion ofFIG.4will be made with reference toFIG.1. The transmitter vehicle may be the transmitter vehicle102fromFIG.1, having the feature encoder module106, the channel attention module108, the channel selection module110, and the message modulator112. The receiver vehicle may be the receiver vehicle104fromFIG.1, having the channel fusion module114, the feature decoder module116, and the detection regression module118. Like the transmitter vehicle102, the receiver vehicle104may also conduct channel attention calculation and weigh its own layered data. Accordingly, the receiver vehicle104may obtain sensor data at block402similar to block204, encode sensor data into structured data at block404similar to block204, generate a channel attention map at block406similar to block206, and generate weights corresponding to channels at block408similar to block208. The feature decoder module116of the receiver vehicle104may decode the structured data to sensor data that is enhanced by the highly weighed channels shared from the transmitter vehicle102. As a result, sensing by the receiver vehicle104may be enhanced to implement an improved perception task by the detection regression module118, such as subject detection, bounding box object localization, and/or other data processing techniques. When weights are generated at block408, weights may be based on the data gathered by the sensors of receiver vehicle104and/or the data fused with the data from the transmitter vehicle102. At block410, channels may be selected to be requested from the transmitter vehicle102. The receiver vehicle104may request the channels from the transmitter vehicle102according to the weights of the channels in the receiver vehicle104. The receiver vehicle104may request channels that have low weight values according to the weights that it had generated in block408. This low weight value may be representative of a large degree of uncertainty, and requesting replacements for such data may increase the certainty of the data if the transmitter vehicle102has higher weights from the same channels. The receiver vehicle104may generate a threshold for selecting channels. The threshold may be based on factors such as type of subjects identified, degree of certainty of subject identification, available bandwidth, number of channels, and/or any other metrics for selecting channels. At block412, a request for selected channels may be transmitted to the transmitter vehicle102. The threshold calculated at block410may be used to filter out channels that have weights that are above the threshold. Channels that have weights that are below the threshold may be requested from the transmitter vehicle102. The transmitter vehicle102may receive the request, with or without a preparatory message, and share the requested channels with the receiver vehicle104in a manner similar to block212. Referring now toFIG.5, an example of channel fusion is depicted. Discussion ofFIG.5will be made with reference toFIGS.1and3. The goal of channel fusion is to improve the perception data of the receiver vehicle104by inserting better data shared from the transmitter vehicle102into the data of the receiver vehicle104. After the transmitter vehicle102has selected channels300b, the transmitter vehicle102may share the selected channels300bwith the receiver vehicle104. Receiver vehicle104may receive the transmission of selected channels500a. Selected channels500acomprise channels302,308,316,318,320,322. The received channels500aare passed to the channel fusion module114of the receiver vehicle104. The channel fusion module114may process and unpack the channels500ato prepare the data for processing by the remaining modules for deep collaborative feature sharing. Processing and unpacking may include decompression, conversion, consolidation, and/or any other processing to prepare the data for processing by the receiver vehicle104. The selected channels500amay be compared the channels500bof the receiver vehicle104. In some embodiments, the selected channels500amay replace the corresponding channels of channels500b. For example, inFIG.5, the channels500bof receiver vehicle104examined to replace channels of the channels500bwith the selected channels500afrom the transmitter vehicle102by channel fusion to arrive at fused channels500c. In other embodiments, the selected channels500amay replace the corresponding channels of channels500bif the weights of the selected channels500aare greater than the weights of the corresponding channels in channels500b. For example, if the channel302has a weight of 0.98, then the channel302will only replace the channel502(i.e., the corresponding channel in channels500b) if the channel502has a weight less than that of the channel302. Referring now toFIG.6, an example of requesting channels from a transmitter vehicle by a receiver vehicle. Discussion ofFIG.6will be made with reference toFIGS.1and4. The goal of requesting channels is to improve the perception data of the receiver vehicle104by replacing low quality data from the receiver vehicle104with better data shared from the transmitter vehicle102. After the receiver vehicle104has obtained sensor data in block402and encoded sensor data into structured data in block404, a channel attention map600ais generated in block406. The channel attention map600amay be visualized as a set of channels502-524. Each channel502-524may have a corresponding weight as assigned in block408. For example, the channel502is 0.90, the channel504is 0.42, the channel506is 0.37, the channel508is 0.85, the channel510is 0.56, the channel512is 0.92, the channel514is 0.35, the channel516is 0.92, the channel518is 0.94, the channel520is 0.77, the channel522is 0.28, and the channel524is 0.95. After the channel attention map600ais generated in block406and weights have been assigned in block408, channels may be requested based on their weights at block410. For example, a threshold may be determined to be 0.8. Based on the threshold, channels to be requested600bconsisting of channels504,506,510,514,520,522may be selected because their weights are below the threshold, and thus they are likely to be better candidates for replacement with data from corresponding channels of a cooperative vehicle. After determining which channels to request, the receiver vehicle104may generate a channel request600cincluding the channels to be requested600bfor transmission to the transmitter vehicle102. The message may be of any format and be delivered to the transmitter vehicle102by any means, including means other than which channels are shared between the transmitter vehicle102and the receiver vehicle104. Referring now toFIG.7, an example system for deep cooperative feature sharing comprising a connected vehicle700is depicted. The connected vehicle700may include a processor module704, a memory module706, a data storage714, a sensor module722, a network interface module708, a feature encoder/decoder module710, a channel attention/selection module712, a message modulator716, a channel fusion module718, and a detection regression module720. The connected vehicle700may also include a communication path702that communicatively couples the various components of the connected vehicle700. The processor module704may include one or more processors that may be any device capable of executing machine-readable and executable instructions. Accordingly, each of the one or more processors of the processor module704may be a controller, an integrated circuit, a microchip, or any other computing device. The processor module704is coupled to the communication path702that provides signal connectivity between the various components of the connected vehicle. Accordingly, the communication path702may communicatively couple any number of processors of the processor module704with one another and allow them to operate in a distributed computing environment. Specifically, each processor may operate as a node that may send and/or receive data. As used herein, the phrase “communicatively coupled” means that coupled components are capable of exchanging data signals with one another such as, e.g., electrical signals via a conductive medium, electromagnetic signals via air, optical signals via optical waveguides, and the like. Accordingly, the communication path702may be formed from any medium that is capable of transmitting a signal such as, e.g., conductive wires, conductive traces, optical waveguides, and the like. In some embodiments, the communication path702may facilitate the transmission of wireless signals, such as Wi-Fi, Bluetooth. Near-Field Communication (NFC), and the like. Moreover, the communication path702may be formed from a combination of mediums capable of transmitting signals. In one embodiment, the communication path702comprises a combination of conductive traces, conductive wires, connectors, and buses that cooperate to permit the transmission of electrical data signals to components such as processors, memories, sensors, input devices, output devices, and communication devices. Accordingly, the communication path702may comprise a vehicle bus, such as, e.g., a LIN bus, a CAN bus, a VAN bus, and the like. Additionally, it is noted that the term “signal” means a waveform (e.g., electrical, optical, magnetic, mechanical, or electromagnetic), such as DC, AC, sinusoidal-wave, triangular-wave, square-wave, vibration, and the like, capable of traveling through a medium. The memory module706is coupled to the communication path702and may contain one or more memory modules comprising RAM, ROM, flash memories, hard drives, or any device capable of storing machine-readable and executable instructions such that the machine-readable and executable instructions can be accessed by the processor module704. The machine-readable and executable instructions may comprise logic or algorithms written in any programming language of any generation (e.g., 1GL, 2GL, 3GL, 4GL, or 5GL) such as, e.g., machine language, that may be directly executed by the processor module704, or assembly language, object-oriented languages, scripting languages, microcode, and the like, that may be compiled or assembled into machine-readable and executable instructions and stored on the memory module706for execution by the processor module704. Alternatively, the machine-readable and executable instructions may be written in a hardware description language (HDL), such as logic implemented via either a field-programmable gate array (FPGA) configuration or an application-specific integrated circuit (ASIC), or their equivalents. Accordingly, the methods described herein may be implemented in any computer programming language, as pre-programmed hardware elements, or as a combination of hardware and software components. In some embodiments, the memory module706includes machine-readable and executable instructions can configure the processor module704to operate as the feature encoder/decoder module710, channel attention/selection module712, channel fusion module718, and/or detection regression module720. The sensor module722is coupled to the communication path702and communicatively coupled to the processor module704. The sensor module722may include LIDAR sensors, RADAR sensors, optical sensors (e.g., cameras), laser sensors, proximity sensors, location sensors, and the like. In embodiments, the sensor module722may capture digital representations of the environment of the connected vehicle700. The digital representations may be photos and/or videos of the environment of the connected vehicle700or other digital representations of the environment of the connected vehicle700(e.g., 3D point clouds as captured by LIDAR). The network interface module708includes network connectivity hardware for communicatively coupling the connected vehicle700to other network-connected devices. The network interface module708can be communicatively coupled to the communication path702and can be any device capable of transmitting and/or receiving data via a network or other communication mechanisms. Accordingly, the network interface module708can include a communication transceiver for sending and/or receiving any wired or wireless communication. For example, the network connectivity hardware of the network interface module708may include an antenna, a modem, an Ethernet port, a Wi-Fi card, a WiMAX card, a cellular modem, near-field communication hardware, satellite communication hardware, and/or any other wired or wireless hardware for communicating with other networks and/or devices. The connected vehicle700may connect with one or more other connected vehicles and/or external processing devices via a direct or indirect connection. The direct connection may be a vehicle-to-vehicle connection (“V2V connection”) or a vehicle-to-everything connection (“V2X connection”). The V2V or V2X connection may be established using any suitable wireless communication protocols discussed above. A connection between vehicles may utilize sessions that are time- and/or location-based. In embodiments, a connection between vehicles or between a vehicle and an infrastructure may utilize one or more networks to connect which may be in place of, or in addition to, a direct connection (such as V2V or V2X) between the vehicles or between a vehicle and an infrastructure. By way of a non-limiting example, vehicles may function as infrastructure nodes to form a mesh network and connect dynamically/ad-hoc. In this way, vehicles may enter/leave the network at will such that the mesh network may self-organize and self-modify over time. Other non-limiting examples include vehicles forming peer-to-peer networks with other vehicles or utilizing centralized networks that rely upon certain vehicles and/or infrastructure. Still, other examples include networks using centralized servers and other central computing devices to store and/or relay information between vehicles. The network interface module708may also include the message modulator716. The message modulator716is configured to at least share channels from the feature map between connected vehicles. In some embodiments, the message modulator716may send and receive preparatory messages to modulate the channels to be shared for better integration with the data of the cooperative vehicle. For example, the message modulator716of a transmitter vehicle may modulate the channels of the structured data to compensate for the difference in position of the receiver vehicle so that the shared channels may be more easily fused with the channels of the receiver vehicle. The data storage714is coupled to the communication path702and may contain one or more memory modules comprising flash memories, solid state drives, hard drives, or any device capable of persistent data storage. The data storage714may store machine-readable and executable instructions. The data storage714may be included as part of the memory module706. The data storage714may store data used by various components and applications of the connected vehicle700. For example, the data storage714may store the generate channel maps when the connected vehicle700is in transmitter mode and/or receiver mode. In addition, the data storage714may store data gathered by the sensor module722and/or received from other vehicles. For example, the data storage714may store 3D point clouds and structured data generated therefrom. The feature encoder/decoder module710is coupled to the communication path702and may process raw sensor data into structured data. For example, if the sensor is a LIDAR sensor, the structured data may be a layered structure, with each layer corresponding to a channel of the LIDAR data. In some embodiments, the feature encoder/decoder module710may exist as machine-readable instructions that may configure the processor module704to operate as a feature encoder/decoder module710. The channel attention/selection module712is coupled to the communication path702and is used to weigh and select channels in structured data generated by the feature encoder/decoder module710. A channel attention/selection module712is a module for channel-based attention in machine learning models, such as a convolutional neural network. The channel attention/selection module712determines what is meaningful in a given input data, such as a subject of interest in an image or point cloud. Based on the determination of channel attention/selection module712, the layer may be assigned a weight to reflect the importance of the channel based on the type of features, the importance of the features, the quality of the features, certainty of the feature determination, and/or other data quality metrics. After assigning a weight to the channels, the channel attention/selection module712may select the channels based on their weights to transmit to a cooperative vehicle via the network interface module708. In some embodiments, the channel attention/selection module712may exist as machine-readable instructions that may configure the processor module704to operate as a channel attention/selection module712. The channel fusion module718is coupled to the communication path702and is used to fuse the shared channels from another vehicle to the channels of the vehicle700. The shared channels are passed to the channel fusion module718of the vehicle700. The channel fusion module718may process and unpack the channels to prepare the data for processing by the remaining modules for deep collaborative feature sharing. Once the channels shared from the other vehicle are received and/or processed by the vehicle700, the shared channels may replace the corresponding channels in the vehicle700. In some embodiments, the channel fusion module718may exist as machine-readable instructions that may configure the processor module704to operate as a channel fusion module718. The detection regression module720is coupled to the communication path702and is used to detect objects in the sensor data. The feature encoder/decoder module710of the cooperative vehicle may decode the structured data to sensor data that is enhanced by the received shared channels. As a result, sensing by the vehicle700may be enhanced to implement an improved perception task by the detection regression module720, such as subject detection, bounding box object localization, and/or other data processing techniques. In some embodiments, the detection regression module720may exist as machine-readable instructions that may configure the processor module704to operate as a detection regression module720. It should now be understood that the present disclosure is directed to systems and methods for deep cooperative feature sharing among connected vehicles. A system may have a transmitter mode and a receiver mode to collaborate with another vehicle that also has a transmitter mode and a receiver mode. In a transmitter mode, a transmitter vehicle may obtain sensor data and encode the raw sensor data into structured data having a set of features and a set of channels. The transmitter vehicle may use the structured data to generate a channel attention map with a corresponding set of weights, based on a pre-trained machine learning model and the inter-channel relationships of the set of features. The transmitter vehicle may also select one or more channels among the set of channels based on the weights of the channels and transmit the selected channels to the receiver vehicle that is acting in collaboration with the transmitter vehicle. In a receiver mode, a receiver vehicle may obtain sensor data and encode the raw sensor data into structured data having a set of features and a set of channels. The receiver vehicle may use the structured data to generate a channel attention map with a corresponding set of weights, based on a pre-trained machine learning model and the inter-channel relationships of the set of features. The receiver vehicle may also select one or more channels among the set of channels based on the weights of the channels and transmit a request for the selected channels. In response to the request, the receiver vehicle may also receive a set of requested channels from the transmitter vehicle that is acting in collaboration with the receiver vehicle. It is noted that recitations herein of a component of the present disclosure being “configured” or “programmed” in a particular way, to embody a particular property, or to function in a particular manner, are structural recitations, as opposed to recitations of intended use. More specifically, the references herein to the manner in which a component is “configured” or “programmed” denotes an existing physical condition of the component and, as such, is to be taken as a definite recitation of the structural characteristics of the component. It is noted that terms like “preferably,” “commonly,” and “typically,” when utilized herein, are not utilized to limit the scope of the claimed invention or to imply that certain features are critical, essential, or even important to the structure or function of the claimed invention. Rather, these terms are merely intended to identify particular aspects of an embodiment of the present disclosure or to emphasize alternative or additional features that may or may not be utilized in a particular embodiment of the present disclosure. Having described the subject matter of the present disclosure in detail and by reference to specific embodiments thereof, it is noted that the various details disclosed herein should not be taken to imply that these details relate to elements that are essential components of the various embodiments described herein, even in cases where a particular element is illustrated in each of the drawings that accompany the present description. Further, it will be apparent that modifications and variations are possible without departing from the scope of the present disclosure, including, but not limited to, embodiments defined in the appended claims. More specifically, although some aspects of the present disclosure are identified herein as preferred or particularly advantageous, it is contemplated that the present disclosure is not necessarily limited to these aspects. | 39,091 |
11943761 | DETAILED DESCRIPTION The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts. Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. While aspects and implementations are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution. FIG.1is a diagram illustrating an example of a wireless communications system and an access network100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations102, UEs104, an Evolved Packet Core (EPC)160, and another core network190(e.g., a 5G Core (5GC)). The base stations102may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells. The base stations102configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC160through first backhaul links132(e.g.,51interface). The base stations102configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network190through second backhaul links184. In addition to other functions, the base stations102may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations102may communicate directly or indirectly (e.g., through the EPC160or core network190) with each other over third backhaul links134(e.g., X2 interface). The first backhaul links132, the second backhaul links184, and the third backhaul links134may be wired or wireless. The base stations102may wirelessly communicate with the UEs104. Each of the base stations102may provide communication coverage for a respective geographic coverage area110. There may be overlapping geographic coverage areas110. For example, the small cell102′ may have a coverage area110′ that overlaps the coverage area110of one or more macro base stations102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links120between the base stations102and the UEs104may include uplink (UL) (also referred to as reverse link) transmissions from a UE104to a base station102and/or downlink (DL) (also referred to as forward link) transmissions from a base station102to a UE104. The communication links120may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations102/UEs104may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell). Certain UEs104may communicate with each other using device-to-device (D2D) communication link158. The D2D communication link158may use the DL/UL WWAN spectrum. The D2D communication link158may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR. The wireless communications system may further include a Wi-Fi access point (AP)150in communication with Wi-Fi stations (STAs)152via communication links154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs152/AP150may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available. The small cell102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell102′ may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP150. The small cell102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz-71 GHz), FR4 (71 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band. With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR2-2, FR4, and/or FR5, or may be within the EHF band. A base station102, whether a small cell102′ or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB180may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE104. When the gNB180operates in millimeter wave or near millimeter wave frequencies, the gNB180may be referred to as a millimeter wave base station. The millimeter wave base station180may utilize beamforming182with the UE104to compensate for the path loss and short range. The base station180and the UE104may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming. The base station180may transmit a beamformed signal to the UE104in one or more transmit directions182′. The UE104may receive the beamformed signal from the base station180in one or more receive directions182″. The UE104may also transmit a beamformed signal to the base station180in one or more transmit directions. The base station180may receive the beamformed signal from the UE104in one or more receive directions. The base station180/UE104may perform beam training to determine the best receive and transmit directions for each of the base station180/UE104. The transmit and receive directions for the base station180may or may not be the same. The transmit and receive directions for the UE104may or may not be the same. The EPC160may include a Mobility Management Entity (MME)162, other MMEs164, a Serving Gateway166, a Multimedia Broadcast Multicast Service (MBMS) Gateway168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway172. The MME162may be in communication with a Home Subscriber Server (HSS)174. The MME162is the control node that processes the signaling between the UEs104and the EPC160. Generally, the MME162provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway166, which itself is connected to the PDN Gateway172. The PDN Gateway172provides UE IP address allocation as well as other functions. The PDN Gateway172and the BM-SC170are connected to the IP Services176. The IP Services176may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC170may provide functions for MBMS user service provisioning and delivery. The BM-SC170may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway168may be used to distribute MBMS traffic to the base stations102belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information. The core network190may include an Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. The AMF192may be in communication with a Unified Data Management (UDM)196. The AMF192is the control node that processes the signaling between the UEs104and the core network190. Generally, the AMF192provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF195. The UPF195provides UE IP address allocation as well as other functions. The UPF195is connected to the IP Services197. The IP Services197may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services. The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station102provides an access point to the EPC160or core network190for a UE104. Examples of UEs104include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs104may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE104may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network. Referring again toFIG.1, in certain aspects, the UE104may include a joint ARD and ATD configuration component198configured to disable at least one Tx chain for a transmission of a SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition, and transmit, to a base station, upon disabling the at least one Tx chain, the SRS-CB via an antenna associated with at least one active Tx chain. In one aspect, the base station180may include a joint ARD and ATD configuration component199configured to identify one or more of at least one DL traffic condition or at least one UL traffic condition, the at least one DL traffic condition or the at least one UL traffic condition being associated with a transmission of an SRS-CB, transmit, to a UE, an indication of one or more of the at least one DL traffic condition or the at least one UL traffic condition, and receive, from the UE, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. FIG.2Ais a diagram200illustrating an example of a first subframe within a 5G NR frame structure.FIG.2Bis a diagram230illustrating an example of DL channels within a 5G NR subframe.FIG.2Cis a diagram250illustrating an example of a second subframe within a 5G NR frame structure.FIG.2Dis a diagram280illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided byFIGS.2A,2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD. FIGS.2A-2Dillustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) and, effectively, the symbol length/duration, which is equal to 1/SCS. μSCS Δf = 2μ· 15[kHz]Cyclic prefix015Normal130Normal260Normal, Extended3120Normal4240Normal For normal CP (14 symbols/slot), different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2μslots/subframe. The subcarrier spacing may be equal to 2μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing.FIGS.2A-2Dprovide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (seeFIG.2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended). A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. As illustrated inFIG.2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS). FIG.2Billustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE104to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages. As illustrated inFIG.2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRSs). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL. FIG.2Dillustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI. FIG.3is a block diagram of a base station310in communication with a UE350in an access network. In the DL, IP packets from the EPC160may be provided to a controller/processor375. The controller/processor375implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor375provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization. The transmit (TX) processor316and the receive (RX) processor370implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor316handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator374may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE350. Each spatial stream may then be provided to a different antenna320via a separate transmitter318TX. Each transmitter318TX may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission. Here, the TX processor316may be a TX MIMO processor316, and the TX MIMO processor may perform spatial processing (e.g., precoding) on data symbols, control symbols, and/or reference symbols, if applicable, and may provide output symbol streams to the transmitters318TX. While described and labeled individually, in some embodiments, a single transmitter318TX may modulate and demodulate MIMO transmissions for the base station310. At the UE350, each receiver354RX receives a signal through its respective antenna352. Each receiver354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor356. The TX processor368and the RX processor356implement layer 1 functionality associated with various signal processing functions. The RX processor356may perform spatial processing on the information to recover any spatial streams destined for the UE350. If multiple spatial streams are destined for the UE350, they may be combined by the RX processor356into a single OFDM symbol stream. The RX processor356then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station310. These soft decisions may be based on channel estimates computed by the channel estimator358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station310on the physical channel. The data and control signals are then provided to the controller/processor359, which implements layer 3 and layer 2 functionality. Here, the Rx processor356may include a MIMO detector/processor356, and the MIMO detector/processor356may obtain received symbols from each receiver354RX, perform MIMO detection on the received symbols if applicable and process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE350to a data output, and provide decoded control information to the controller/processor359, or memory360. The controller/processor359can be associated with a memory360that stores program codes and data. The memory360may be referred to as a computer-readable medium. In the UL, the controller/processor359provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC160. The controller/processor359is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations. Similar to the functionality described in connection with the DL transmission by the base station310, the controller/processor359provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization. Channel estimates derived by a channel estimator358from a reference signal or feedback transmitted by the base station310may be used by the TX processor368to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor368may be provided to different antenna352via separate transmitters354TX. Each transmitter354TX may modulate an RF carrier with a respective spatial stream for transmission. The UL transmission is processed at the base station310in a manner similar to that described in connection with the receiver function at the UE350. Each receiver318RX receives a signal through its respective antenna320. Each receiver318RX recovers information modulated onto an RF carrier and provides the information to a RX processor370. The controller/processor375can be associated with a memory376that stores program codes and data. The memory376may be referred to as a computer-readable medium. In the UL, the controller/processor375provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE350. IP packets from the controller/processor375may be provided to the EPC160. The controller/processor375is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations. At least one of the TX processor368, the RX processor356, and the controller/processor359may be configured to perform aspects in connection with198ofFIG.1. At least one of the TX processor316, the RX processor370, and the controller/processor375may be configured to perform aspects in connection with199ofFIG.1. In some aspects, a MIMO antenna configuration may be established between a UE and a base station. MIMO antenna processing may refer to a method for multiplying the capacity of a radio link through multiple transmissions and receiving antennas to provide multipath propagation. That is, through the MIMO antenna configuration, the UE and the base station may increase the UL or DL throughput via multiple UL or DL MIMO antennas. Based on the MIMO antenna configuration, the UE and the base station may be configured with an adaptive transmit diversity (ATD) or an adaptive receive diversity (ARD). The UE or, in some examples, the base station may be configured with the ARD and reduce the number of active Rx chains to save power while minimizing or reducing negative effects to the DL performance to reduce power consumption. The UE or, in some examples, the base station may also be configured with the ATD to reduce or blank at least one of the UL antenna ports associated with a physical layer based on the communication conditions to reduce power consumption. That is, the UE configured with the ATD may switch from a first configuration with two or more layers, e.g., a spatial multiplexing dual layer (SMDL), to a second configuration with a single layer, e.g., a spatial multiplexing single layer (SMSL), to reduce the power consumption or enhance the system capacity. The UE may include at least one power amplifier (e.g., a second power amplifier associated with a second layer), and at least one digital chain (e.g., a second digital chain associated with the second layer) may be turned off to reduce the power consumption. In one aspect, the UE may be configured to drop at least one of the transmit signals to the base station without incurring a significant impact to the UL and the DL throughput. In another aspect, the UE may apply the ATD to the UL MIMO carriers. In one aspect, the UE may perform the ATD and indicate user assistance information (UAI) to the base station with a reduced amount of UL MIMO layers. That is, the UE may determine to reduce the number of the UL MIMO layers based on at least one of a low power source, a low UL PDCP watermark, or a low UL throughput and may transmit the UAI indicating the reduced amount of UL MIMO layers to the base station. In another aspect, the base station may receive the UAI indicating the reduced amount of UL MIMO layers from the UE, and may determine to reduce the number of the UL MIMO layers based on the UAI received from the UE. However, the base station may not be obligated to act in accordance to the UE's preference indicated in the UAI, and since the ATD may be performed after the base station receives the UAI and determines to act, the ATD using the UAI may have increased latency. In some aspects, the UE may be configured to autonomously determine ATD blanking, i.e., disabling at least one Tx or Rx port associated with transmission of at least one SRS. Here, the SRS may include an SRS for antenna switching (SRS-AS) or a codebook-based SRS (SRS-CB). The blanking or disabling of at least one Tx or Rx port may affect the UL throughputs or the DL throughputs, and the UE may implement interactions between the ARD and the ATD to mitigate the potential negative effect on the UL throughputs or the DL throughputs. In one aspect, the configuration of the SRS may indicate that the SRS resource may be overloaded when the same SRS resource identified with one SRS resource identifier (ID) is configured to two SRS resource sets. For example, the same SRS resource identified with the same SRS resource ID may be configured to two SRS resource sets, including the SRS-AS for antenna switching purposes and the SRS-CB for codebook-based SRS usage, and the SRS-AS resources may be overloaded with the SRS-CB resources. In some examples, when the MIMO configuration includes Tx and Rx chains configured with two Tx chains and four Rx chains (2T4R), each of the two Tx chains may have one primary port and one diversity port. For example, the first Tx chain (Tx0) may have a first primary Tx port (PTx_0) associated with a first antenna (Ant_0) that is associated with a first Rx chain (Rx0) and a first diversity Tx port (DTx_0) associated with a third antenna (Ant_2) that is associated with a third Rx chain (Rx1), and the second Tx chain (Tx1) may have a second primary Tx port (PTx_1) associated with a fourth antenna (Ant_4) that is associated with a second Rx chain (Rx1) and a second diversity Tx port (DTx_1) associated with a second antenna (Ant_1) that is associated with a fourth Rx chain (Rx3), as indicated in Table 1 below. TABLE 1UL-MIMOTx chain mappingRx chain mappingAnt_0Tx0PTx_0Rx0Ant_1DTx_1Rx3Ant_2DTx_0Rx2Ant_3Tx1PTx_1Rx1 The SRS resource overloading may allow the network to configure two SRS resources. That is, the SRS resource overloading may refer to as sharing or reusing SRS resource set across the SRS-CB and the SRS-AS. For example, first SRS resources (SRS Res_0) may be used for codebook based UL-MIMO and antenna switching and may be transmitted using the primary Tx chains, including PTx_0 and PTx_1, and second SRS resources (SRS Res_1) may be used for the antenna switching and may be transmitted using the diversity Tx chains, including DTx_0 and DTx_1. Accordingly, the network may use the SRS resource overloading to reduce the SRS overhead. For example, a first resource set 0 may be configured for the codebook (CB) usage and may contain the SRS Res_0, and a second resource set 1 may be configured for the antenna switching (AS) usage and may contain the SRS Res_0 and SRS Res_1. For non-overloading cases, the network may configure three SRS Resources, including first SRS resources (SRS Res_0) configured for the CB, second SRS resources (SRS Res_1) configured for the AS, and third SRS resources (SRS Res 2) configured for the AS. For the non-overloading cases, the network may configure the SRS resource sets as follows: the first resource set 0 may be configured for the CB usage and contain the SRS Res_0, and the second resource set 1 may be configured for the AS usage and may contain the SRS Res_1 and SRS Res 2. The ATD may be turned off when the UE initially goes from one of idle or inactive RRC mode to a connected mode. In the connected mode, if the UL-MIMO is configured, the UE may periodically evaluate a number of conditions including, but not limited to, a power level of the power source, DL traffic, UL traffic, an SRS-AS configuration, and an SRS-CB configuration. The time interval or the frequency of such a periodic evaluation may be determined based on a function of how fast the base station may measure the SRS, measure the SRS and apply it to the scheduling, etc. The UE may determine to blank, disable, or skip an SRS port to reduce the number of the SRS ports to reduce a power consumption and reserve wireless communication resources. The blanking may be a system-level operation that the UE may decide to perform, and, the base station may detect the blanking based on the reduced number of SRS ports transmitting the SRS and not receiving SRS via the blanked SRSs. Based on the nature of the SRS, the base station may detect that the base station may not expect to receive UL signals via the Tx chains of the UE associated with the blanked SRS-CB ports, and that the base station may not transmit DL signals according to the received SRS. In one aspect, the UE may disable at least one Tx chain for a transmission of the SRS. For instance, the UE may implement the blanking of the SRS port by disabling at least one Tx chain for a transmission of the SRS. In another aspect, the UE may identify at least one Tx chain to skip for the transmission of the SRS. For instance, the UE may implement the blanking of the SRS port by identifying at least one Tx chain to skip for the transmission of the SRS. In one aspect, the ATD may drop a number of the SRS ports to one TX chain associated with the SRS port based on the UE having a low power source (e.g., a voltage level of the power source being less than a power threshold). That is, the UE may determine that the ATD blanking of the SRS port may be beneficial in light of the low power source. In another aspect, the ATD may drop the number of the SRS port to one TX chain associated with the SRS port based on the UL traffic not being heavy and not being sensitive to latency when the SRS-AS is not configured or the SRS-AS resource is not overloaded with the SRS-CB resource. That is, when the SRS-AS resource is not configured or not overloaded with the SRS-CB resource, the ATD may not affect the throughput of the Rx chain associated with the SRS-AS, and therefore, the UE may perform the ATD blanking to reduce the number of the SRS port to one TX chain associated with the SRS port in consideration of the UL traffic condition. In another aspect, the ATD may drop the number of the SRS port to one TX chain associated with the SRS port based on both of the DL traffic and the UL traffic not being heavy and not being sensitive to latency when the SRS-AS resource is overloaded with the SRS-CB resource. That is, when the SRS-AS resource is overloaded with the SRS-CB resource, the ATD blanking to reduce the number of the SRS port to one TX chain associated with the SRS port may be performed in consideration of the UL traffic condition and the DL traffic condition. Here, the UL traffic condition for the ATD blanking may be based on the UL throughput being low or the UL PDCP watermark being low. The UL traffic condition for the ATD blanking may also be based on the statistics of the MAC padding in a series of UL grants. The DL traffic condition for the ATD blanking may be based on the DL traffic being in a reduced throughput state. That is, when the DL traffic is in the reduced throughput state, the ATD blanking may be acceptable even if the DL throughput may be impacted by the SRS resource overloading and the ATD blanking. In one aspect, the ATD blanking may be blocked (or disallowed) based on a bandwidth part (BWP) of the DL traffic. That is, the ATD blanking of the SRS port may be allowed based on the BWP allocated for the DL traffic being less than a threshold BW value (i.e., a small BWP), and the ATD blanking of the SRS port may be blocked based on the BWP allocated for the DL traffic being greater than or equal to the threshold BW value (i.e., a large BWP), as indicated in Table 2 below. When the blanking of the SRS port is allowed, the ATD blanking may be performed based on the UL conditions (e.g., low UL throughput and low UL PDCP watermark) and/or the condition of the power source. In case the ATD blanking and the ARD are allowed based on the small DL traffic BWP and the overloaded SRS resources, at least one Rx chain selected according to the ARD may be re-mapped to at least one physical antenna according to joint handling of the DL, which will be described in detail below. TABLE 2SRS resources not overloadedSRS resources overloaded(or AS not configured)Large BWPSRS blanking blockedSRS Blanking allowed (CB)Small BWPSRS Blanking allowedSRS Blanking allowed (CB)(CB + AS) Rx1 re-mapping In another aspect, the ATD blanking may be blocked based on a number of active Rx chains. That is, the number of active Rx chains may indicate whether the DL throughput is high since, the lower number of active Rx chains may mean that the peak DL throughput is not expected, and/or one of the antenna may have a deteriorated performance. Accordingly, the ATD blanking of the SRS port may be allowed. A higher number of active Rx may refer that the peak DL throughput may be expected with good antenna performances, the ATD blanking of the SRS port may be blocked. For example, the blanking may be blocked for SRS configured with the overloaded resources based on four (4) ARD Rx chains being configured, and the blanking may be allowed based on two (2) ARD Rx chains being configured, as indicated in Table 3 below. When the blanking of the SRS port may be allowed, the ATD blanking may be performed based on the UL conditions (e.g., low UL throughput and low UL PDCP watermark) and/or the condition of the power source. In case the ATD blanking and the ARD are allowed based on the two (2) ARD Rx chains being configured and the overloaded SRS resources, at least one Rx chain selected according to the ARD may be re-mapped according to joint handling of the DL, which will be described in detail below. TABLE 3SRS resources not overloadedSRS resources overloaded(or AS not configured)ARD 4RxSRS blanking blockedSRS Blanking allowed (CB)ARD 2RxSRS Blanking allowedSRS Blanking allowed (CB)(CB + AS) Rx1 re-mapping In another aspect, the ATD blanking may be blocked based on heavy DL traffic. That is, the ATD blanking may be blocked in the presence of heavy DL traffic since the ATD blanking because the ATD blanking may have an increased impact on the DL throughput when the DL traffic is heavy. The UE may detect whether the DL traffic is heavy, based on at least one of a density of DL grants, a configuration of supportable DL throughput, or application information of the DL (e.g., 4K video streaming is running). For example, the blanking may be blocked for SRS configured with the overloaded resources based on four (4) ARD Rx chains being configured with the heavy DL traffic, and the blanking may be allowed based on four (4) ARD Rx chains being configured with the non-heavy DL traffic or the two (2) ARD Rx chains being configured, as indicated in Table 4 below. When the blanking of the SRS port may be allowed, the ATD blanking may be performed based on the UL conditions (e.g., low UL throughput and low UL PDCP watermark) and/or the condition of the power source. In case the ATD blanking and the ARD are allowed based on the non-heavy DL traffic and the overloaded SRS resources, at least one Rx chain selected according to the ARD may be re-mapped according to joint handling of the DL, which will be described in detail below. TABLE 4SRS resources not overloadedSRS resources overloaded(or AS not configured)ARD 4RxSRS blanking blockedSRS Blanking allowed (CB)heavy DLtrafficARD 4RxSRS Blanking allowedSRS Blanking allowed (CB)non-heavy(CB + AS) Rx1 re-DL trafficmappingARD 2RxSRS Blanking allowedSRS Blanking allowed (CB)(CB + AS) Rx1 re-mapping In some aspects, the UE may support the ARD, and during the ARD state, the UE may blanking an SRS-AS. When the ARD is supported, and the number of the Rx chains is reduced, the UE may feedback or report channel state information (CSI) consistent with the reduced number of Rx chains. For example, if the number of the active Rx chain is reduced from four (4) to two (2) antennas, the UE may transmit, to the base station, the CSI report consistently with the two (2) Rx chains. The UE may not indicate to the base station that the UE is in the ARD state with the reduced number of RX chains. However, since the base station may use the SRS to estimate the DL channels, the UE may blank the SRS ports associated with the disabled Rx ports so that the UE may receive all the packets transmitted from the base station through the active Rx chains. In one case, the SRS-AS is configured, the SRS ports corresponding to the active Rx chains may be sounded, and the SRS ports corresponding to the inactive (or disabled) Rx chains may be blanked. For example, if the third and fourth Rx chains are associated with the second and third antennas based on the ARD, the SRS-AS ports corresponding to the third and fourth Rx chains associated with antenna 2 and 3 may be blanked, and the SRS-AS ports corresponding to the first and second Rx chains associated with the first and fourth antennas may be sounded. In case the UL-MIMO is configured, the SRS ports corresponding to the active Tx ports may be sounded. In cases where the SRS is overloaded between the SRS-AS and the SRS-CR, the active Rx ports and the active Tx ports may be paired, and the paired active Rx port and active Tx port may be mapped to the same physical antennas. For example, referring to Table 5, the UE may disable the Rx ports associated with the inactive Tx ports, e.g., Dtx_1 and DTx_0, and pair the two active Rx ports Rx0 and Rx1 to the two active Tx ports, Tx0 and Tx1, respectively. The UE may map the first pair of active Tx port and Rx port, e.g., Tx0 and Rx0 pair, to the first physical antenna Ant_0. The UE may also map the second pair of active Tx port and Rx port, e.g., Tx1 and Rx1 pair, to the fourth physical antenna Ant_3. Accordingly, the UE may sound full first SRS resources SRS Res_0 for the SRS-CB, and also sound the full first SRS resources SRS Res_0 for the SRS-AS. TABLE 5UL-Tx chainRx chainSRS-CBSRS-AS 2T4R forMIMOmappingmappingUL-MIMOARD 2RxAnt_0Tx0PTx_0Rx0 (active)Sound SRS Res_0Sound SRS Res_0Ant_1DTx_1Rx3 (disabled)Blank SRS Res_1Ant_2DTx_0Rx2 (disabled)Blank SRS Res_1Ant_3Tx1PTx_1Rx1 (active)Sound SRS Res_0Sound SRS Res_0 In some aspects, the UE may perform joint handling of the DL for the ATD blanking. For an SRS overloaded case, due to the ATD blanking, the second Tx chain Tx1 and the associated SRS-CB for UL-MIMO may be blanked. For example, referring to Table 6, the Tx1 mapped to the second primary Tx port PTx_1 may be blanked based on the ATD blanking. In turn, this may force the same SRS-AS associated with the Rx port to be blanked, and the base station may not receive the SRS-AS from the UE through the second Rx port, and the base station may not estimate the channel for the second Rx port, hurting the 2Rx DL throughput. Accordingly, the UE may minimize or reduce the ATD blanking impact on the DL performance in the ARD 2Rx state by re-mapping the second Rx port Rx1 to another physical antenna that is not associated with the blanked Tx port. For example, the second Rx port Rx1 may be re-mapped to the third physical antenna Ant 2 from the fourth physical antenna Ant_3. The first Rx port Rx0 and the first Tx port Tx0 may still be paired and mapped to the first physical antenna Ant_0. The UE may select, among the two remaining physical antennas, e.g., Ant_1 and Ant_2, a more optimal antenna that may have a better metric, e.g., RSRP, SNR, etc. For example, the UE may select the third physical antenna Ant_2 for having the higher metric than the second physical antenna Ant_1 and re-map the second Rx port Rx1 to the third physical antenna Ant_2. In another aspect, the UE may select one physical antenna with the worst metric, e.g., RSRP, SNR, etc., and blank the Tx port associated with the physical antenna with the worst metric. For example, the UE may determine to blank Tx1 based on the determination that the fourth physical antenna Ant_3 has the worst metric among the four physical antennas. Subsequently, the UE may select one antenna that has the second-best metric and re-map the second Rx port Rx1 to the one antenna that has the second-best metric. For example, the UE may determine that the third physical antenna Ant_2 has the second-best metric and re-map the second Rx port Rx1 to the third physical antenna Ant_2. TABLE 6UL-Tx chainRx chainSRS-CBSRS-AS 2T4R forMIMOmappingmappingUL-MIMOARD 2RxAnt_0Tx0PTx_0Rx0 (active)Sound port 0 ofSound port 0 ofSRS Res_0SRS Res_0Ant_1DTx_1Rx3 (disabled)Blank port 1 ofSRS Res_1Ant_2DTx_0Rx1 (active)Sound port 0 ofSRS Res_1Ant_3Tx1PTx_1Rx1 (disabled)Blank port 1 ofBlank port 1 of(blanked)SRS Res_0SRS Res_0 FIG.4is an example400of ATD blanking of a method of wireless communication. The example400may include an ARD controller410and an ATD controller420of a UE. The ATD blanking may be allowed or blocked based on at least one DL condition in response to the interactions between the ARD controller410and the ATD controller420at the UE. In some aspects, the SRS may be overloaded, and the ATD blanking may impact DL throughput. The ARD controller410may determine, based on at least one DL traffic condition, that the heavy DL traffic may be affected by an ATD blanking. At412, the ARD controller410may indicate the ATD controller420that ATD blanking should be blocked based on at least one DL traffic condition. Based on at least one DL traffic condition, the ATD controller420may determine whether the ATD blanking should be blocked. Here, the determination of whether the ATD blanking is allowed or blocked may be based on a number of DL traffic conditions. First, the ATD blanking may be blocked based on a bandwidth part (BWP) of the DL traffic. That is, the ATD controller420may determine that the ATD blanking of the SRS port may be allowed based on the BWP allocated for the DL traffic being less than a threshold BW value (small BWP), and may determine that the ATD blanking of the SRS port may be blocked based on the BWP allocated for the DL traffic being greater than or equal to the threshold BW value (large BWP). Second, the ATD blanking may be blocked based on a number of active Rx chains. That is, the number of active Rx chains may indicate whether the DL throughput is high since the lower number of active Rx may mean that the peak DL throughput is not expected, and/or one of the antennas may have a deteriorated performance. Accordingly, the ATD blanking of the SRS port may be allowed. A higher number of active Rx may refer that the peak DL throughput may be expected with good antenna performances, the ATD blanking of the SRS port may be blocked. Third, the ATD blanking may be blocked based on heavy DL traffic. That is, the ATD blanking may be blocked in the presence of heavy DL traffic since the ATD blanking because the ATD blanking may have an increased impact on the DL throughput when the DL traffic is heavy. The UE may detect whether the DL traffic is heavy, based on at least one of a density of DL grants, a configuration of supportable DL throughput, or application information of the DL (e.g., 4K video streaming is running). Fourth, the ATD blanking may be blocked based on a latency sensitivity for the DL traffic. That is, in case the latency specification of the DL traffic may be stringently configured, the ATD blanking may have an increased impact to the DL throughput and may be blocked. Fifth, the ATD blanking may be blocked based on the application information of the DL traffic. The UE may infer that the ATD blanking may have an increased effect on the DL throughput based on the application information (e.g., which applications are running, etc.) and determine whether to block or allow the ATD Blanking. When the ATD controller420is not blocked from performing the ATD blanking, the ATD controller420may consider the UL traffic to determine whether to perform the ATD blanking. That is, based on at least one UL traffic condition including one or more of an amount of the UL traffic being less than a UL traffic threshold or a latency sensitivity of the UL traffic being less than a latency threshold, the ATD controller420may determine to perform the ATD blanking. At422, the ATD controller420may indicate the ARD controller410of the ATD blanking, and the ARD controller410may re-map at least one active Rx chain to at least one antenna port based on the disabled at least one Tx chain, wherein the at least one active Rx chain is paired with the disabled at least one Tx chain. The ARD controller410may unrepair the at least one active Rx chain from the at least one Tx chain that was blanked or disabled, and re-map the unrepaired at least one active Rx chain to one or more antennas unassociated with an active Tx chain or the disabled at least one Tx chain. The SRS resources may be overloaded, and the ATD blanking may reduce the power consumption on UL. However, the ATD blanking may degrade the DL performance, affecting the DL energy efficiency. In one case, the blanked Tx antenna may correspond to an Rx antenna that is inactive due to ARD, and the Tx power and the Rx power may be saved from the ATD blanking. However, in general, the improved power efficiency in UL from the ATD blanking may cause power efficiency degradation in the DL, and a tradeoff between the UL energy efficiency and the DL energy efficiency may occur. The tradeoff may lead to different outcomes depending on the DL traffic, the UL traffic, or the channel condition. Accordingly, a unified framework may provide a joint decision of the ARD and ATD configuration, including the Tx and Rx antennas selection and/or blanking. FIG.5is an example of architecture500of a method of wireless communication. The example architecture500may illustrate jointly deciding the ARD and ATD configurations. The example architecture500may include an ARD hypothesis502and an ATD blanking hypothesis504. For example, the ARD hypothesis502may indicate the number of Rx ports, e.g., 4Rx or 2Rx, and the ATD blanking hypothesis may indicate whether to blank one or more ports or not to blank any port. Based on the SRS resource overloading conditions and inputs from the ARD hypothesis502and the ATD blanking hypothesis504, the impact on DL throughput506may be determined. In one aspect, a power efficiency improvement in the TX from the ATD blanking510may be determined based on the ATD blanking hypothesis504and the UL traffic information. In another aspect, a power efficiency degradation from the DL impact512may be determined based on the impact to the DL throughput506and the DL traffic information. Accordingly, based on the power efficiency improvement in the TX from the ATD blanking510and the power efficiency degradation from the DL impact512, the architecture500may choose a pair of ATD blanking and ARD hypothesis combinations that may lead to the best overall power efficiency (520) and determine the best ATD blanking and ARD hypothesis joint configuration. FIG.6is a call-flow diagram600of a method of wireless communication. The call-flow diagram600may include a UE602and a base station604. The UE602may make a joint decision of the ARD and ATD configuration, including the Tx and Rx antennas selection and/or blanking based on DL and UL traffic conditions. In one aspect, the base station604may identify at least a part of the DL and UL traffic conditions and transmit an indication of the part of the DL and UL traffic conditions to the UE602. At605, the base station604may identify one or more of at least one DL traffic condition or at least one UL traffic condition, the at least one DL traffic condition or the at least one UL traffic condition being associated with a transmission of an SRS-CB. At606, the base station604may transmit, to the UE602, an indication of one or more of the at least one DL traffic condition or the at least one UL traffic condition. The UE602may receive one or more of at least one DL traffic condition or at least one UL traffic condition. At607, the UE602may identify the at least one DL traffic condition or at least one UL traffic condition. The at least one DL traffic condition may include one or more of an SRS-AS configuration, DL traffic, a BWP allocated for DL, or an ARD. The at least one UL traffic condition may include one or more of an amount of the UL traffic being less than a UL traffic threshold or a latency sensitivity of the UL traffic being less than a latency threshold. In one aspect, the UE602may receive one or more of at least one DL traffic condition or at least one UL traffic condition. In another aspect, the UE602may identify the at least one DL traffic condition or the at least one UL traffic condition. That is, the UE602may identify the at least one DL traffic condition or the at least one UL traffic condition based on at least one of a DL scheduling, UL traffic initiated in the UE, SRS overloading condition in the RRC configuration, etc. At608, the UE602may select at least one Tx chain for the SRS-CB to be disabled, where at least one Tx chain is associated with one or more other antennas, including the metric less than the antenna threshold value. That is, the UE602may select one physical antenna with the worst metric, e.g., RSRP, SNR, etc., and blank the Tx port associated with the physical antenna with the worst metric. At609, the UE602may determine to blank at least one Tx port associated with the SRS-CB. That is, based on one or more of at least one DL traffic condition or at least one UL traffic condition, the UE602may determine to blank at least one Tx port associated with the SRS-CB, where the at least one Tx chain may be disabled for the transmission of the SRS-CB based on the determining to blank at least one Tx port associated with the SRS-CB. At610, the UE602may disable at least one Tx chain for the transmission of an SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition. In one aspect, the UE602may disable at least one Tx chain selected at608. At least one Tx chain may be disabled further based on an SRS-AS resource allocated for the SRS-AS being overloaded with an SRS CB resource. In one aspect, at least one Tx chain may be disabled further based on the BWP allocated for DL being less than a threshold BW value. In another aspect, at least one Tx chain may be disabled further based on the SRS-AS not being configured or an SRS-AS resource allocated for the SRS-AS not being overloaded with an SRS-CB resource. In another aspect, at least one Tx chain may be disabled further based on a number of Rx chains configured for the ARD being less than a threshold value. In another aspect, at least one Tx chain may be disabled further based on a number of Rx chains configured for the ARD being greater than or equal to a threshold value and an amount of the DL traffic being less than a DL traffic threshold. The amount of the DL traffic may be based on at least one of a density of DL grants, a configuration of supportable DL throughput, or application information of the DL. In another aspect, at least one Tx chain may be disabled for the transmission of the SRS-CB further based on a voltage level of a power source of the UE602being less than a power threshold. At612, the UE602may disable the transmission of SRS-AS for at least one Rx chain. In one aspect, the UE602may support the ARD and reduce the number of the Rx chains based on the ARD. In cases where the SRS is overloaded between the SRS-AS and the SRS-CR, the active Rx ports and the active Tx ports may be paired, and the paired active Rx port and active Tx port may be mapped to the same physical antennas. At614, the UE602may select one or more antennas. In one aspect, the one or more antennas include a metric greater than an antenna threshold value. In another aspect, the one or more antennas include a metric greater than other antennas. In some aspects, the UE602may perform joint handling of the DL for the ATD blanking. The UE602may minimize or reduce the ATD blanking impact on the DL performance in the ARD 2Rx state by re-mapping the second Rx port Rx1 to another physical antenna that is not associated with the blanked Tx port. The UE602may select a more optimal antenna that may have better metrics, e.g., RSRP, SNR, etc. In another aspect, the UE602may select one antenna that has the second-best metric. At616, the UE602may re-map at least one active Rx chain paired with the disabled at least one Tx chain to at least one antenna not associated with the disabled at least one Tx chain. In one aspect, each of the at least one active Rx chain may be paired with one active Tx chain, and the pair of the active Rx chain and the active Tx chain may be mapped to a same antenna. In another aspect, at least one active Rx chain may be re-mapped to one or more antennas unassociated with an active Tx chain or the disabled at least one Tx chain. For example, the UE602may re-map at least one active Rx chain to one or more antennas selected at614. At618, the UE602may transmit, to the base station604, upon disabling the at least one Tx chain, the SRS-CB via an antenna associated with at least one active Tx chain. The base station604may receive, from the UE602, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition. The base station604may use the SRS-CB to estimate the UL channels, and the UE602may transmit the UL channels via the active at least one Tx chain. FIG.7is a flowchart700of a method of wireless communication. The method may be performed by a UE (e.g., the UE104/602; the apparatus902). The UE may make a joint decision of the ARD and ATD configuration, including the Tx and Rx antennas selection and/or blanking based on DL and UL traffic conditions. At702, the UE may receive one or more of at least one DL traffic condition or at least one UL traffic condition. At703, the UE may identify the at least one DL traffic condition or at least one UL traffic condition. The at least one DL traffic condition may include one or more of an SRS-AS configuration, DL traffic, a BWP allocated for DL, or an ARD. The at least one UL traffic condition may include one or more of an amount of the UL traffic being less than a UL traffic threshold or a latency sensitivity of the UL traffic being less than a latency threshold. In one aspect, the UE may receive one or more of at least one DL traffic condition or at least one UL traffic condition. In another aspect, the UE may identify the at least one DL traffic condition or the at least one UL traffic condition. That is, the UE may identify the at least one DL traffic condition or the at least one UL traffic condition based on at least one of a DL scheduling, UL traffic initiated in the UE, SRS overloading condition in the RRC configuration, etc. For example, at606, the UE602may receive one or more of at least one DL traffic condition or at least one UL traffic condition, and at607, the UE may identify the at least one DL traffic condition or at least one UL traffic condition. Furthermore,702and703may be performed by a DL/UL traffic condition component940. At704, the UE may select at least one Tx chain for the SRS-CB to be blanked, where at least one Tx chain is associated with one or more other antennas, including the metric less than the antenna threshold value. That is, the UE may select one physical antenna with the worst metric, e.g., RSRP, SNR, etc., and blank the Tx port associated with the physical antenna with the worst metric. For example, at608, the UE602may select at least one Tx chain for the SRS-CB to be disabled, where at least one Tx chain is associated with one or more other antennas, including the metric less than the antenna threshold value. Furthermore,704may be performed by an antenna configuring component946. At705, the UE may determine to blank at least one Tx port associated with the SRS-CB. That is, based on one or more of at least one DL traffic condition or at least one UL traffic condition, the UE may determine to blank at least one Tx port associated with the SRS-CB, where the at least one Tx chain may be disabled for the transmission of the SRS-CB based on the determining to blank at least one Tx port associated with the SRS-CB. For example, at609, the UE602may determine to blank at least one Tx port associated with the SRS-CB. Furthermore,705may be performed by an ATD blanking component942. At706, the UE may disable at least one Tx chain for the transmission of an SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition. In one aspect, the UE602may disable at least one Tx chain selected at704. At least one Tx chain may be disabled further based on an SRS-AS resource allocated for the SRS-AS being overloaded with an SRS CB resource. In one aspect, at least one Tx chain may be disabled further based on the BWP allocated for DL being less than a threshold BW value. In another aspect, at least one Tx chain may be disabled further based on the SRS-AS not being configured or an SRS-AS resource allocated for the SRS-AS not being overloaded with an SRS-CB resource. In another aspect, at least one Tx chain may be disabled further based on a number of Rx chains configured for the ARD being less than a threshold value. In another aspect, at least one Tx chain may be disabled further based on a number of Rx chains configured for the ARD being greater than or equal to a threshold value and an amount of the DL traffic being less than a DL traffic threshold. The amount of the DL traffic may be determined based on at least one of a density of DL grants, a configuration of supportable DL throughput, or application information of the DL. In another aspect, at least one Tx chain may be disabled for the transmission of the SRS-CB further based on a voltage level of a power source of the UE602being less than a power threshold. For example, at610, the UE602may disable at least one Tx chain for the transmission of an SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition. Furthermore,706may be performed by an ATD blanking component942. At708, the UE may disable the transmission of SRS-AS for at least one Rx chain. In one aspect, the UE may support the ARD and reduce the number of the Rx chains based on the ARD. In cases that the SRS is overloaded between the SRS-AS and the SRS-CR, the active Rx ports and the active Tx ports may be paired, and the paired active Rx port and active Tx port may be mapped to the same physical antennas. For example, at612, the UE602may disable the transmission of SRS-AS for at least one Rx chain. Furthermore,708may be performed by an ARD component944. At710, the UE may select one or more antennas. In one aspect, the one or more antennas include a metric greater than an antenna threshold value. In another aspect, the one or more antennas include a metric greater than other antennas. In some aspects, the UE may perform joint handling of the DL for the ATD blanking. The UE may minimize or reduce the ATD blanking impact on the DL performance in the ARD 2Rx state by re-mapping the second Rx port Rx1 to another physical antenna that is not associated with the blanked Tx port. The UE may select a more optimal antenna that may have better metrics, e.g., RSRP, SNR, etc. In another aspect, the UE may select one antenna that has the second-best metric. For example, at614, the UE602may select one or more antennas. Furthermore,710may be performed by the antenna configuring component946. At712, the UE may re-map at least one active Rx chain paired with the disabled at least one Tx chain to at least one antenna not associated with the disabled at least one Tx chain. In one aspect, each of the at least one active Rx chain may be paired with one active Tx chain, and the pair of the active Rx chain and the active Tx chain may be mapped to a same antenna. In another aspect, at least one active Rx chain may be re-mapped to one or more antennas unassociated with an active Tx chain or the disabled at least one Tx chain. For example, the UE may re-map at least one active Rx chain to one or more antennas selected at710. For example, at616, the UE602may re-map at least one active Rx chain paired with the disabled at least one Tx chain to at least one antenna not associated with the disabled at least one Tx chain. Furthermore,712may be performed by the antenna configuring component946. At714, the UE may transmit, to the base station, the SRS-CB via an antenna associated with at least one active Tx chain, upon disabling the at least one Tx chain. The base station may use the SRS-CB to estimate the UL channels, and the UE may transmit the UL channels via the active at least one Tx chain. For example, at618, the UE602may transmit, to the base station604, upon disabling the at least one Tx chain, the SRS-CB via an antenna associated with at least one active Tx chain. Furthermore,714may be performed by an SRS component948. FIG.8is a flowchart800of a method of wireless communication. The method may be performed by a UE (e.g., the UE104/602; the apparatus902). The UE may make a joint decision of the ARD and ATD configuration, including the Tx and Rx antennas selection and/or blanking based on DL and UL traffic conditions. At806, the UE may disable at least one Tx chain for the transmission of an SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition. In one aspect, the UE602may disable at least one Tx chain selected at804. At least one Tx chain may be disabled further based on an SRS-AS resource allocated for the SRS-AS being overloaded with an SRS CB resource. In one aspect, at least one Tx chain may be disabled further based on the BWP allocated for DL being less than a threshold BW value. In another aspect, at least one Tx chain may be disabled further based on the SRS-AS not being configured or an SRS-AS resource allocated for the SRS-AS not being overloaded with an SRS-CB resource. In another aspect, at least one Tx chain may be disabled further based on a number of Rx chains configured for the ARD being less than a threshold value. In another aspect, at least one Tx chain may be disabled further based on a number of Rx chains configured for the ARD being greater than or equal to a threshold value and an amount of the DL traffic being less than a DL traffic threshold. The amount of the DL traffic may be determined based on at least one of a density of DL grants, a configuration of supportable DL throughput, or application information of the DL. In another aspect, at least one Tx chain may be disabled for the transmission of the SRS-CB further based on a voltage level of a power source of the UE602being less than a power threshold. For example, at610, the UE602may disable at least one Tx chain for the transmission of an SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition. Furthermore,806may be performed by an ATD blanking component942. At814, the UE may transmit, to the base station, the SRS-CB via an antenna associated with at least one active Tx chain, upon disabling the at least one Tx chain. The base station may use the SRS-CB to estimate the UL channels, and the UE may transmit the UL channels via the active at least one Tx chain. For example, at618, the UE602may transmit, to the base station604, upon disabling the at least one Tx chain, the SRS-CB via an antenna associated with at least one active Tx chain. Furthermore,814may be performed by an SRS component948. FIG.9is a diagram900illustrating an example of a hardware implementation for an apparatus902. The apparatus902may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus902may include a cellular baseband processor904(also referred to as a modem) coupled to a cellular RF transceiver922. In some aspects, the apparatus902may further include one or more subscriber identity modules (SIM) cards920, an application processor906coupled to a secure digital (SD) card908and a screen910, a Bluetooth module912, a wireless local area network (WLAN) module914, a Global Positioning System (GPS) module916, or a power supply918. The cellular baseband processor904communicates through the cellular RF transceiver922with the UE104and/or BS102/180. The cellular baseband processor904may include a computer-readable medium/memory. The computer-readable medium/memory may be non-transitory. The cellular baseband processor904is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor904, causes the cellular baseband processor904to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor904when executing software. The cellular baseband processor904further includes a reception component930, a communication manager932, and a transmission component934. The communication manager932includes the one or more illustrated components. The components within the communication manager932may be stored in the computer-readable medium/memory and/or configured as hardware within the cellular baseband processor904. The cellular baseband processor904may be a component of the UE350and may include the memory360and/or at least one of the TX processor368, the RX processor356, and the controller/processor359. In one configuration, the apparatus902may be a modem chip and include just the baseband processor904, and in another configuration, the apparatus902may be the entire UE (e.g., see350ofFIG.3) and include the additional modules of the apparatus902. The communication manager932includes a DL/UL traffic condition component940that is configured to receive or identify one or more of at least one DL traffic condition or at least one UL traffic condition, e.g., as described in connection with702and703. The communication manager932further includes an ATD blanking component942that is configured to determine to blank at least one Tx port associated with the SRS-CB, and disable at least one Tx chain for the transmission of an SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition, e.g., as described in connection with705,706, and806. The communication manager932includes an ARD component944that is configured to disable the transmission of SRS-AS for at least one Rx chain, and re-map at least one active Rx chain paired with the disabled at least one Tx chain to at least one antenna not associated with the disabled at least one Tx chain, e.g., as described in connection with708and712. The communication manager932further includes an antenna configuring component946that is configured to re-map at least one active Rx chain to at least one antenna based on the disabled at least one Tx chain, and select one or more antennas, where the one or more antennas include a metric greater than an antenna threshold value, e.g., as described in connection with704and710. The communication manager932includes an SRS component948that is configured to transmit, to the base station, the SRS-CB via an antenna associated with at least one active Tx chain, upon disabling the at least one Tx chain, e.g., as described in connection with714and814. The apparatus may include additional components that perform each of the blocks of the algorithm in the flowcharts ofFIGS.6,7, and8. As such, each block in the flowcharts ofFIGS.6,7, and8may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. As shown, the apparatus902may include a variety of components configured for various functions. In one configuration, the apparatus902, and in particular the cellular baseband processor904, includes means for disabling at least one Tx chain for a transmission of a SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition, means for transmitting, to a base station, upon disabling the at least one Tx chain, the SRS-CB via an antenna associated with at least one active Tx chain, and means for determining to blank at least one Tx port associated with the SRS-CB. The apparatus902includes means for disabling the transmission of SRS-AS for at least one Rx chain, and re-map at least one active Rx chain to at least one antenna based on the disabled at least one Tx chain, where the at least one active Rx chain is paired with the disabled at least one Tx chain. The apparatus902includes means for selecting the one or more antennas, where the one or more antennas include a metric greater than an antenna threshold value, and means for selecting the at least one Tx chain for the SRS-CB to be disabled, where the at least one Tx chain is associated with one or more other antennas including the metric less than the antenna threshold value. The means may be one or more of the components of the apparatus902configured to perform the functions recited by the means. As described supra, the apparatus902may include the TX Processor368, the RX Processor356, and the controller/processor359. As such, in one configuration, the means may be the TX Processor368, the RX Processor356, and the controller/processor359configured to perform the functions recited by the means. FIG.10is a flowchart1000of a method of wireless communication. The method may be performed by a base station (e.g., the base station102/180/604; the apparatus1102). The base station may identify the DL and UL traffic conditions and transmit an indication of the DL and UL traffic conditions to the UE, and the UE may make a joint decision of the ARD and ATD configuration, including the Tx and Rx antennas selection and/or blanking based on DL and UL traffic conditions. At1001, the base station may identify one or more of at least one DL traffic condition or at least one UL traffic condition. Here, the at least one DL traffic condition or the at least one UL traffic condition may be associated with a transmission of an SRS-CB. For example, at605, the base station604may identify one or more of at least one DL traffic condition or at least one UL traffic condition. Furthermore,1001may be performed by a DL/UL traffic condition component1140. At1002, the base station may transmit, to the UE, an indication of one or more of the at least one DL traffic condition or the at least one UL traffic condition. In one aspect, at least one DL traffic condition may include one or more of an SRS-AS configuration, DL traffic, a BWP allocated for DL, or an ARD. In another aspect, at least one UL traffic condition may include one or more of an amount of the UL traffic being less than a UL traffic threshold or a latency sensitivity of the UL traffic being less than a latency threshold. For example, at606, the base station604may transmit, to the UE602, an indication of one or more of the at least one DL traffic condition or the at least one UL traffic condition. Furthermore,1002may be performed by the DL/UL traffic condition component1140. At1014, the base station may receive, from the UE, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition. The base station may use the SRS-CB to estimate the UL channels, and the UE may transmit the UL channels via the active at least one Tx chain. For example, at618, the base station604may receive, from the UE602, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition. Furthermore,1014may be performed by an SRS component1148. FIG.11is a diagram1100illustrating an example of a hardware implementation for an apparatus1102. The apparatus1102may be a base station, a component of a base station, or may implement base station functionality. In some aspects, the apparatus1002may include a baseband unit1104. The baseband unit1104may communicate through a cellular RF transceiver1122with the UE104. The baseband unit1104may include a computer-readable medium/memory. The baseband unit1104is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the baseband unit1104, causes the baseband unit1104to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit1104when executing software. The baseband unit1104further includes a reception component1130, a communication manager1132, and a transmission component1134. The communication manager1132includes the one or more illustrated components. The components within the communication manager1132may be stored in the computer-readable medium/memory and/or configured as hardware within the baseband unit1104. The baseband unit1104may be a component of the base station310and may include the memory376and/or at least one of the TX processor316, the RX processor370, and the controller/processor375. The communication manager1132includes a DL/UL traffic condition component1140that is configured to identify one or more of at least one DL traffic condition or at least one UL traffic condition, and transmit an indication of one or more of at least one DL traffic condition or at least one UL traffic condition, e.g., as described in connection with1001and1002. The communication manager1132further includes an SRS component1148that is configured to receive, from the UE, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition, e.g., as described in connection with1014. The apparatus may include additional components that perform each of the blocks of the algorithm in the flowcharts ofFIGS.6and10. As such, each block in the flowcharts ofFIGS.6and10may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof. As shown, the apparatus1102may include a variety of components configured for various functions. In one configuration, the apparatus1102, and in particular the baseband unit1104, includes means for identifying one or more of at least one DL traffic condition or at least one UL traffic condition, the at least one DL traffic condition or the at least one UL traffic condition being associated with a transmission of an SRS-CB, means for transmitting, to a UE, an indication of one or more of the at least one DL traffic condition or the at least one UL traffic condition, and means for receiving, from the UE, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition. The means may be one or more of the components of the apparatus1102configured to perform the functions recited by the means. As described supra, the apparatus1102may include the TX Processor316, the RX Processor370, and the controller/processor375. As such, in one configuration, the means may be the TX Processor316, the RX Processor370, and the controller/processor375configured to perform the functions recited by the means. A UE may make a joint decision of ARD and ATD configurations, including the Tx and Rx antennas selection and/or blanking based on DL and UL traffic conditions. The UE may disable at least one Tx chain for a transmission of an SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition, and transmit, to a base station, upon disabling the at least one Tx chain, the SRS-CB via an antenna associated with at least one active Tx chain. The base station may identify one or more of at least one DL traffic condition or at least one UL traffic condition, the at least one DL traffic condition or the at least one UL traffic condition being associated with a transmission of an SRS-CB, transmit, to a UE, an indication of one or more of the at least one DL traffic condition or the at least one UL traffic condition, and receive, from the UE, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition. It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” should be interpreted to mean “under the condition that” rather than imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.” The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation. Aspect 1 is an apparatus for wireless communication at a UE including at least one processor coupled to a memory and configured to disable at least one Tx chain for a transmission of a SRS-CB based on one or more of at least one DL traffic condition or at least one UL traffic condition, and transmit, to a base station, upon disabling the at least one Tx chain, the SRS-CB via an antenna associated with at least one active Tx chain. Aspect 2 is the apparatus of aspect 1, where the at least one DL traffic condition includes one or more of an SRS-AS configuration, DL traffic, a BWP allocated for DL, or an ARD. Aspect 3 is the apparatus of aspect 2, where the at least one Tx chain is disabled further based on the SRS-AS not being configured or an SRS-AS resource allocated for the SRS-AS not being overloaded with an SRS-CB resource. Aspect 4 is the apparatus of any of aspects 2 and 3, where the at least one Tx chain is disabled further based on the BWP allocated for DL being less than a threshold BW value. Aspect 5 is the apparatus of any of aspects 2 to 4, where the at least one Tx chain is disabled further based on the BWP allocated for DL being less than a threshold BW value. Aspect 6 is the apparatus of any of aspects 2 to 5, where the at least one Tx chain is disabled further based on a number of Rx chains configured for the ARD being greater than or equal to a threshold value and an amount of the DL traffic being less than a DL traffic threshold. Aspect 7 is the apparatus of aspect 6, where the amount of the DL traffic is based on at least one of a density of DL grants, a configuration of supportable DL throughput, or an application information of the DL. Aspect 8 is the apparatus of any of aspects 2 and 7, where the at least one Tx chain is disabled further based on an SRS-AS resource allocated for the SRS-AS being overloaded with an SRS CB resource, and where the at least one processor and the memory are further configured to disable a transmission of SRS-AS for at least one Rx chain, and re-map at least one active Rx chain paired with the disabled at least one Tx chain to at least one antenna not associated with the disabled at least one Tx chain. Aspect 9 is the apparatus of aspect 8, where each of the at least one active Rx chain is paired with one active Tx chain, and the pair of the active Rx chain and the active Tx chain is mapped to a same antenna. Aspect 10 is the apparatus of any of aspects 8 and 9, where the at least one active Rx chain is re-mapped to one or more antennas unassociated with an active Tx chain or the disabled at least one Tx chain. Aspect 11 is the apparatus of aspect 10, where the at least one processor and the memory are further configured to select the one or more antennas, where the one or more antennas include a metric greater than an antenna threshold value. Aspect 12 is the apparatus of aspect 11, where the at least one processor and the memory are further configured to select the at least one Tx chain for the SRS-CB to be disabled, where the at least one Tx chain is associated with one or more other antennas including the metric less than the antenna threshold value. Aspect 13 is the apparatus of any of aspects 10 to 12, where the at least one processor and the memory are further configured to select the one or more antennas, wherein the one or more antennas include a metric greater than other antennas. Aspect 14 is the apparatus of any of aspects 1 to 13, where the at least one UL traffic condition includes one or more of an amount of the UL traffic being less than a UL traffic threshold or a latency sensitivity of the UL traffic being less than a latency threshold. Aspect 15 is the apparatus of any of aspects 1 to 14, where the at least one Tx chain is disabled for the transmission of the SRS-CB further based on a voltage level of a power source of the UE being less than a power threshold. Aspect 16 is the apparatus of any of aspects 1 to 15, further including a transceiver coupled to the at least one processor, where the at least one processor and the memory are further configured to determine to blank at least one Tx port associated with the SRS-CB, and the at least one Tx chain is disabled for the transmission of the SRS-CB based on the determining to blank at least one Tx port associated with the SRS-CB. Aspect 17 is a method of wireless communication for implementing any of aspects 1 to 16. Aspect 18 is an apparatus for wireless communication including means for implementing any of aspects 1 to 16. Aspect 19 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 16. Aspect 20 is an apparatus for wireless communication at a base station including at least one processor coupled to a memory and configured to identify one or more of at least one DL traffic condition or at least one UL traffic condition, the at least one DL traffic condition or the at least one UL traffic condition being associated with a transmission of an SRS-CB, transmit, to a UE, an indication of one or more of the at least one DL traffic condition or the at least one UL traffic condition, and receive, from the UE, the SRS-CB associated with the at least one DL traffic condition or the at least one UL traffic condition. Aspect 21 is a method of wireless communication for implementing aspect 20. Aspect 22 is an apparatus for wireless communication including means for implementing aspect 20. Aspect 23 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement aspect 20. | 100,842 |
11943762 | DETAILED DESCRIPTION A user equipment (UE) in a wireless communications system, such as a New Radio (NR) system or a Long Term Evolution (LTE) system, may support applications associated with high throughput and low latency. The described aspects of the disclosure relate to improved methods, systems, devices, or apparatuses that facilitate transmission batch scheduling and resource management. Specifically, wireless communications systems supporting extended reality (XR) applications may be associated with a high data rate requirement and a tight delay budget. In some example XR applications, one or more transmitted packets may be in the form of groups or files. As one example, packets in a video frame in an XR application may be included in a file. The packets of a file may be configured to be processed together. For example, a transmitting device may include one or more Internet Protocol (IP) packets in a file if the file (such as a video frame) is usable at a receiver when all IP packets of the file are successfully received. The file or group of packets may be transmitted in one or more transmissions as a batch of transmissions. In some examples, the techniques described herein provide for communication of a batch of transmissions configured to carry a file having a plurality of packets configured to be processed together. According to one or more aspects, a UE may determine a transmission direction schedule for communication of a file based on a grant (e.g., a UE-specific downlink control information (DCI), a configured grant, a group common DCI). A UE may also determine whether to process one or more transmissions carrying a file or portions of a file based on a preemption indication received from a base station. In some examples, a DCI message may be configured for scheduling resources for communication of a file. For example, a file may be scheduled using a separate DCI for each packet of a file, and each packet may be linked such that a UE may identify missed or dropped DCI signals. In some cases, a UE may monitor for a new DCI message corresponding to a file in addition to a legacy DCI message for other communications. Techniques for transmission batch scheduling and resource management may also include allocation of resources for file communication using configured grants for groups of packets (e.g., files). For example, a configured grant may include a configured grant index indication, where the index corresponds to a resource configuration for communication of a file. A resource configuration may include a number, size, and location of transport blocks. In some cases, a UE may adjust a power for transmission of a file, maintain phase continuity for transport blocks for communication of a file, and/or process a file using combined reference signals for a batch transmissions carrying a file. Particular aspects of the subject matter described herein may be implemented to realize one or more advantages. The described techniques may support improvements in file communication in high throughput and low latency communication environments. The techniques may support decreasing of signaling overhead and improving reliability by increasing the likelihood of file transmission. As such, supported techniques may include improve network operations and, in some examples, may promote network efficiencies, among other benefits. Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further described with respect to additional wireless communications systems and process flow diagrams. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to transmission batch scheduling and resource management. FIG.1illustrates an example of a wireless communications system100that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The wireless communications system100may include base stations105, UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communications system100may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof. Base stations105may be dispersed throughout a geographic area to form the wireless communications system100and may be devices in different forms or having different capabilities. Base stations105and UEs115may wirelessly communicate via one or more communication links125. Each base station105may provide a coverage area110over which UEs115and the base station105may establish communication links125. The coverage area110may be an example of a geographic area over which a base station105and a UE115support the communication of signals according to one or more radio access technologies. UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115, base stations105, and/or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown inFIG.1. Base stations105may communicate with the core network130, or with one another, or both. For example, base stations105may interface with the core network130through backhaul links120(e.g., via an S1, N2, N3, or other interface). Base stations105may communicate with one another over backhaul links120(e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations105), or indirectly (e.g., via core network130), or both. In some examples, backhaul links120may be or include one or more wireless links. One or more of base stations105described herein may include or may be referred to by a person of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology. A UE115may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE115may be stationary or mobile. A UE115may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA),), a multimedia/entertainment device (e.g., a radio, a MP3 player, a video device, etc.), a camera, a gaming device, a navigation/positioning device (e.g., GNSS (global navigation satellite system) devices based on, for example, GPS (global positioning system), Beidou, GLONASS, or Galileo, a terrestrial-based device, etc.), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot/robotic device, a vehicle, a vehicular device, a meter (e.g., parking meter, electric meter, gas meter, water meter), a monitor, a gas pump, an appliance (e.g., kitchen appliance, washing machine, dryer), a location tag, a medical/healthcare device, an implant, a sensor/actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium a personal computer, or a subscriber device. In some examples, a UE115may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a machine type communications (MTC) device, or the like, which may be implemented in various objects such as appliances, vehicles, meters, or the like. In an aspect, techniques disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UEs may include MTC/enhanced MTC (eMTC, also referred to as CAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as base stations105and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, and the like, as shown inFIG.1. UEs115and base stations105may wirelessly communicate with one another via one or more communication links125over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication links125. For example, a carrier used for a communication link125may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that is operated according to physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be positioned according to a channel raster for discovery by UEs115. A carrier may be operated in a standalone mode where initial acquisition and connection may be conducted by UEs115via the carrier, or the carrier may be operated in a non-standalone mode where a connection is anchored using a different carrier (e.g., of the same or a different radio access technology). Communication links125shown in the wireless communications system100may include uplink transmissions from a UE115to a base station105, or downlink transmissions from a base station105to a UE115. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode). A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system100. For example, the carrier bandwidth may be one of a number of predetermined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system100(e.g., base stations105, UEs115, or both) may have hardware configurations that support communications over a particular carrier bandwidth or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system100may include base stations105and/or UEs115that support simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE115may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth. Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements that a UE115receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE115. A wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE115. One or more numerologies for a carrier may be supported, where a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into BWPs having the same or different numerologies. In some examples, a UE115may be configured with multiple BWPs. In some cases, a single BWP for a carrier is active at a given time, and communications for the UE115may be restricted to active BWPs. Time intervals for base stations105or UEs115may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, where Δfmaxmay represent the maximum supported subcarrier spacing, and Nfmay represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023). Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some cases, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation. A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system100and may be referred to as a transmission time interval (TTI). In some cases, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)). Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs115. For example, UEs115may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs115and UE-specific search space sets for sending control information to a specific UE115. Each base station105may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or various combinations thereof. The term “cell” may refer to a logical communication entity used for communication with a base station105(e.g., over a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some examples, a cell may also refer to a geographic coverage area110or a portion of a geographic coverage area110(e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the base station105. For example, a cell may be or include a building, a subset of a building, exterior spaces between or overlapping with geographic coverage areas110, or the like. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs115with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered base station105, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs115with service subscriptions with the network provider or may provide restricted access to UEs115having an association with the small cell (e.g., UEs115in a closed subscriber group (CSG), UEs115associated with users in a home or office, and the like). A base station105may support one or multiple cells and may also support communications over the one or more cells using one or multiple component carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of devices. In some examples, a base station105may be movable and therefore provide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas110associated with different technologies may overlap, but the different geographic coverage areas110may be supported by the same base station105. In other examples, overlapping geographic coverage areas110associated with different technologies may be supported by different base stations105. The wireless communications system100may include, for example, a heterogeneous network in which different types of base stations105provide coverage for various geographic coverage areas110using the same or different radio access technologies. The wireless communications system100may support synchronous or asynchronous operation. For synchronous operation, the base stations105may have similar frame timings, and transmissions from different base stations105may be approximately aligned in time. For asynchronous operation, the base stations105may have different frame timings, and transmissions from different base stations105may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations. Some UEs115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station105without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program. Some UEs115may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging. In an aspect, techniques disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UEs may include MTC/enhanced MTC (eMTC, also referred to as CAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. Some UEs115may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception simultaneously). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for UEs115include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs115may be configured for operation using a narrowband protocol type that is associated with a predefined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier. The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications. UEs115may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions). Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT), mission critical video (MCVideo), or mission critical data (MCData). Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein. In some cases, a UE115may also be able to communicate directly with other UEs115over a device-to-device (D2D) communication link135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs115utilizing D2D communications may be within the geographic coverage area110of a base station105. Other UEs115in such a group may be outside the geographic coverage area110of a base station105or be otherwise unable to receive transmissions from a base station105. In some cases, groups of UEs115communicating via D2D communications may utilize a one-to-many (1:M) system in which each UE115transmits to every other UE115in the group. In some examples, a base station105facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between UEs115without the involvement of a base station105. In some systems, the D2D communication link135may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some cases, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., base stations105) using vehicle-to-network (V2N) communications, or with both. The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs115served by base stations105associated with the core network130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to the network operators IP services150. The operators IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service. Some of the network devices, such as a base station105, may include subcomponents such as an access network entity140, which may be an example of an access node controller (ANC). Each access network entity140may communicate with UEs115through a number of other access network transmission entities145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs). Each access network transmission entity145may include one or more antenna panels. In some configurations, various functions of each access network entity140or base station105may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station105). Components within a wireless communications system may be coupled (for example, operatively, communicatively, functionally, electronically, and/or electrically) to each other. The wireless communications system100may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, since the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to UEs115located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz. The wireless communications system100may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band, or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system100may support millimeter wave (mmW) communications between UEs115and base stations105, and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some cases, this may facilitate use of antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. Techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body. The wireless communications system100may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communications system100may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as base stations105and UEs115may employ carrier sensing for collision detection and avoidance. In some cases, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, or the like. A base station105or UE115may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station105or UE115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some cases, antennas or antenna arrays associated with a base station105may be located in diverse geographic locations. A base station105may have an antenna array with a number of rows and columns of antenna ports that the base station105may use to support beamforming of communications with a UE115. Likewise, a UE115may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port. Base stations105or UEs115may use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices. Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station105or a UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation). A base station105or UE115may use beam sweeping techniques as part of beam forming operations. For example, a base station105may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a base station105multiple times in different directions. For example, the base station105may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by a transmitting device, such as a base station105, or a receiving device, such as a UE115) a beam direction for subsequent transmission and/or reception by the base station105. Some signals, such as data signals associated with a particular receiving device, may be transmitted by a base station105in a single beam direction (e.g., a direction associated with the receiving device, such as a UE115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted in different beam directions. For example, a UE115may receive one or more of the signals transmitted by the base station105in different directions and may report to the base station105an indication of the signal that the UE115received with a highest signal quality, or an otherwise acceptable signal quality. In some cases, transmissions by a device (e.g., by a base station105or UE115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from a base station105to a UE115). The UE115may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across a system bandwidth or one or more sub-bands. The base station105may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. The UE115may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted in one or more directions by a base station105, a UE115may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE115) or for transmitting a signal in a single direction (e.g., for transmitting data to a receiving device). A receiving device (e.g., a UE115) may try multiple receive configurations (e.g., directional listening) when receiving various signals from the base station105, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions). The wireless communications system100may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE115and a base station105or core network130supporting radio bearers for user plane data. At the Physical layer, transport channels may be mapped to physical channels. UEs115and base stations105may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some cases, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval. Existing wireless communications systems may receive data packets as a stream of bits, and may assign the data packets to transport blocks based on the received stream of bits. For some high throughput and low latency applications (for example, XR applications), it may be beneficial to group one or more transmitted packets as a batch. As one example, packets in a video frame of an application may be included in a batch (or a file), in which each batch is associated with a separate video frame. Additionally, it is beneficial to acknowledge receipt of packets included in a batch (such as a video frame). According to one or more aspects of the present disclosure, the wireless communications system100may be configured to group data packets of the same video frame as a batch or file and perform recourse management based on the packets being associated as a file. In some cases, resources (e.g., symbols of a lot) may be determined based on one or more resource grants and/or DCI messages corresponding to file communication. For example, a DCI may be specifically configured for granting resources for communication of a file. In another example, configured grants may include a configured grant index corresponding to communication of a file. Other aspects may include configuration of a UE for responding to a preemption indication when a file is scheduled for communication, power adjustments for communication of a file, reference signal configurations for communication of a file, and/or coherent detection/transmission across two or more packets of a file. Using the described techniques, reliability and efficiency of communication (e.g., file communication) within the wireless communications system100may be enhanced. FIG.2illustrates an example of a wireless communications system200that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, wireless communications system200may implement aspects of wireless communications system100. The wireless communications system may include a base station105-aand a UE115-a, which may be examples of the corresponding devices described with respect toFIG.1. In one example, the base station105-amay be referred to as a transmitter, and the UE115-amay be referred to as a receiver. In some implementations, the UE115-aand the base station105-amay operate in a mmW spectrum and/or using NR technologies. In some wireless systems (for example, NR wireless systems, such as wireless communications system200) the UE115-aand the base station105-amay support low latency and high throughput communications. Different types of communications may entail different traffic thresholds. Table 1 represents a table showing the traffic thresholds for different types of traffic in a NR wireless system. For example, an NR wireless system, such as wireless communications system200, may support eMBB applications, ultra-reliable low latency communications (URLLC), and extended reality (XR) communications. In some implementations, one or more XR applications (for example, applications using XR traffic thresholds) may include cloud reality applications, virtual reality applications, and gaming applications. As discussed herein, XR applications are associated with high throughput (for example, throughput for rendering videos) and low latency. In some implementations, XR applications may include interactive video sessions (such as gaming or head mounted display). As described with reference to Table 1, XR applications may be associated with a packet delay budget and a packet error rate. For example, an XR application (or an XR communication session) may be associated with a packet delay budget of 10 ms and a packet error rate of 10′. TABLE 1DefaultPacketPacketMaximumTraffic5QIDelayErrorData BurstExampleTypeValueBudgetRateVolumeServiceseMBB1100 ms10−2N/AConversationalvoiceeMBB2150 ms10−3N/AConversationalvideo (forexample, livestreaming)eMBB6, 8, 9300 ms10−6N/AVideo (forexample,bufferedstreaming)TransmissionControlProtocol-basedservice (forexample, e-mail, chat, filetransferprotocol, peer-to-peer filesharing,progressivevideo). . .. . .. . .. . .. . .XR8010 ms10−6N/ALow latencyeMBBapplications(such asaugmentedreality)URLLC815 ms10−5160 BRemote control. . .. . .. . .. . .. . . Additionally, Table 2 illustrates multiple use cases for XR applications. For example, an XR application may include virtual reality split rendering (for example, gaming applications). In such implementations, a head mounted display may communicate with a server that renders a video frame. In such examples, processing of the video frame may be performed at the server. Upon successful processing of the video frame, a communication link (such as a 5G communication link) may convey the processed video frame from the server to the head mounted display. For successful delivery of the processed video frame, 5G communication link may be associated with high throughput and low latency (for example, traffic threshold for XR applications). A second use case for XR applications may include augmented reality split computation. In augmented reality applications, an entire view of a user may not be covered by a rendered video. Instead, a rendered video (such as, video rendered from a server) may be augmented over a display of a user device (for example, a camera feed). A third use case for XR applications may include cloud gaming. In some examples, cloud gaming may be associated with high throughput and low latency communication link. Thus, XR applications may be subjected to higher traffic thresholds, and it may be beneficial for the NR wireless communications system (such as wireless communications system200) to be aware of traffic associated with XR applications. TABLE 2Virtual RealityAugmented RealityCloudsplit renderingsplit computationGamingHead MountedHead-mounted withHead-mounted with5GDisplay/Device5G modem attachedUSB/BluetoothSmartphoneconnection toor Tablet“Puck” orSmartphone with5G modem5G usageQoSQoSOTT/QoSLocationEnterprise-Indoor,Enterprise-Indoor,OutdoorResidential-Indoor,OutdoorOutdoorMobilityLimited to headPedestrian, Hi-speedStatic,movements andHi-speedrestricted bodymovements, Hi-speed (VR in theback of a car) Existing wireless communications systems may be configured to treat data packets as a stream of bits without the knowledge of files associated with the packets. In some examples XR applications, one or more transmitted packets may be in the form of groups or files. As one example, packets in a video frame in an XR application may be included in a file. In some examples, the separate files may be associated with a file error rate. For example, a file error rate may be based on a number of packets in each file, a reliability threshold associated with each file (for example, whether a file includes an I-frame or a P-frame), or a combination thereof. Existing wireless communications may not have a method to support or guarantee a file error rate. According to one or more aspects of the present disclosure, the wireless communications system200may be configured to group packets205of the same video frame as a file210, and transmit the files210as packet-groups in uplink or downlink communications in accordance with file resource management techniques described herein. In some cases, base station105-amay transmit an uplink grant or a DCI message to the UE115-a, and the uplink grant or DCI message may include information for scheduling communication of a file. Traffic flow illustrated inFIG.2may include multiple Internet Protocol (IP) packets205. In some implementations, NR wireless systems (such as the wireless communications system100supporting XR applications) may be configured to group one or more IP packets205into one or more files210. The wireless communications system200may group the one or more IP packets205based on a reliability threshold, packet delivery deadline, etc. For example, a first group of packets (e.g., file210-a) may be associated with an I-frame, and a second group of packets (e.g., file210-b) may be associated with a P-frame. In such an example, the first group of packets may have a higher reliability threshold (such as high priority) than the second group of packets. Additionally or alternatively, the wireless communications system may group the one or more IP packets205based on a delivery deadline associated with each IP packet205. In some implementations, a delivery deadline of a packet205may be interpreted as a sum of a time of arrival of the packet (for example, at a base station105) and a packet delay budget associated with the packet. In some examples, a group of packets having a same (or similar) delivery deadline may be grouped together as one file210. In some examples, the wireless communications system200may implement additional signaling to convey information related to a delivery deadline and/or a packet delay budget from an application to base station105and the UE115. In some implementations, the wireless communications system may group the one or more IP packets205based on a policy of file handling. For example, the wireless communications system may include one or more IP packets205in a file if the file (such as a video frame) is usable at a receiver (such as UE115) when all IP packets of a file210are successfully received. In some examples, the wireless communications system may include one or more IP packets205in a file if the policy indicates that a continuous stream of IP packets205up to the first packet in error can be used at the receiver. In the example ofFIG.2, the wireless communications system200generates5files. In some implementations, each file may include a set of IP packets205jointly processed by an application (such as an XR application). In some examples, the wireless communications system200may determine the IP packets205associated with a file based on a maximum transmission unit (MTU) setting on an IP stack interfacing with the application. In some examples, the wireless communications system may further fragment the IP packets205into smaller IP packet fragments (not shown). In some implementations, a burst215of files may be referred to as files generated by an application at the same (or similar) time. As depicted in the example ofFIG.2, the wireless communications system generates files210-aand210-bat a same (or similar) time. Accordingly, files210-aand210-bare included in a first burst215-a(in uplink) of the traffic flow. Similarly, the UE115-a(for example, an XR application included in the wireless communications system) may generate a second burst215-bincluding files210-c,210-d, and210-e. In some wireless systems (for example, NR wireless systems, such as wireless communications system200) the UE115-aand the base station105-amay support various techniques for grants, slot structures, etc. for supporting various services provided by the wireless communications system200. For example, in a NR wireless system, the slot structure may be semi-statically indicated to the UE115-avia a an SIB1 (e.g., cell-specific) message or via a RRC (e.g., UE-specific) message. A communication slot may include symbols allocated as a flexible symbol, an uplink symbol, or a downlink symbol. A flexible symbol allocated via semi-static downlink/uplink (DL/UL) or other previous assignment may be overwritten by more dynamically-indicated signaling (for example, measurement report-driven signaling, slot format indication (SFI) data, or UE specific signaling). A symbol allocated for UL/DL by semi-static DL/UL assignment may not be overwritten (e.g., changed from UL to DL or changed from DL to UL). Further, a symbol allocated for UL/DL by semi-static DL/UL assignment may not be changed to a flexible symbol by SFI. A transmission direction (e.g., UL or DL) indicated by a cell-specific RRC configuration (for example, for secondary cell (SCell) or for a primary/secondary cell (PSCell)) or by a UE-specifically delivered RRC symbol grants may not be changed (e.g., by SFI) to the other direction. Further, in NR systems, a dynamic SFI may be indicated via a group common physical downlink control channel (PDCCH) (e.g., with DCI format 2_0), which may provide more flexible or dynamic slot structure management. In some cases, an SFI transmitted in a group common PDCCH (e.g., GC-PDCCH) may indicate a slot format for one or more slots. The GC-PDCCH may indicate information such as the number of slots and the slot format information for the slots. For symbols indicated via dynamic SFI and not allocated for DL or UL in semi-static DL/UL assignment, DL UL symbols may not be overwritten by UE specific data. When the UE specific data and a dynamic SFI imply different transmission directions, the UE115-amay determine that an error has occurred. In some cases, a flexible symbol scheduled via dynamic SFI may be overwritten by UE specific data (e.g., changed to DL or UL). In such cases, the UE115-amay use the DCI for UE-specific data transmission and reception to determine whether the flexible symbol is UL or DL. In a UE PDCCH monitoring occasion, if a direction of a flexible symbol is indicated by SFI (e.g., not overwritten) for at least one symbol also configured for UE specific PDCCH, then the UE115-amay not be expected to monitor the PDCCH. In some cases, resources may be granted via DCI for multi-slot transmission (e.g., physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), PUCCH) via semi-static DL/UL assignment. In such cases, if the assignment configuration of a slot has no direction conflict with scheduled PDSCH/PUSCH/PUCCH assigned symbols, the PDSCH/PUSCH/PUCCH in that slot may be transmitted. If the assignment configuration of a slot has a direction conflict with scheduled PDSCH/PUSCH/PUCCH assigned symbols, then the PDSCH/PUSCH/PUCCH transmission in that slot may be canceled. For DCI granted multi-slot transmission (PDSCH/PUSCH/PUCCH) that overlaps with slots scheduled via dynamic SFI, when there is no semi-static DL/UL assignment or the semi-static DL/UL assignment indicates ‘flexible,’ then the slots may follow the scheduled multi-slot transmission allocation. In some cases, resources may be allocated via configured grants. If the UE115-ais configured by higher layers to receive PDSCH or CSI-RS in the set of symbols in a slot allocated via configured grant, then the UE115-amay receive the PDSCH or the CSI-RS in the set of symbols of the slot if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slots as downlink. If the UE115-ais configured by higher layers to transmit PUCCH, PUSCH, or physical random access channel (PRACH) in the set of symbols of the slot allocated via configured grants, then the UE115-amay transmit the PUCCH, PUSCH, or PRACH in the slot if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as uplink. In NR systems, such as wireless communications system200, the devices (e.g., base station105-aand UE115-a) may support preemption indication for resource management. A downlink preemption indication may be transmitted by the base station105-ato the UE115-a, and the preemption indication may identify resources (e.g., downlink-scheduled resources) as being preempted. In some instances, the preempted resources may have already occurred, meaning that the preemption indicator may signal the UE115-ato not process data received during the preempted resources. An uplink preemption indication may be transmitted by the base station105-ato the UE115-ato indicate that the UE115-ashould not transmit during previously-scheduled uplink resources. Thus, when UE115-areceives a preemption indication, the UE115-amay be configured to respond accordingly. For example, the UE115-amay cease transmissions for UL symbols indicated as preempted, may not process DL symbols indicated as preempted, or, in some cases, may ignore the preemption indication. Different services may have different performance requirements or priorities. In particular, URLLC (or higher priority communications or channels) may be expected to be scheduled with tighter timelines due to lower latency requirements. For example, ultra-reliability may correspond to a 10−5block-error rate (BLER). In order to facilitate scheduling URLLC traffic and to maximize system efficiency, it may be important to have eMBB (or lower priority communications or channels) and URLLC resources dynamically multiplexed in the same carrier. Thus, it may be important to preempt ongoing eMBB transmissions for a newly scheduled URLLC transmission due to its urgency and ultra-reliability. For downlink preemption, preemption indication monitoring may be configured by RRC signaling, and the configuration of UE monitoring of preemption indications may be indicated per DL bandwidth part (BWP). Preempted resources may be indicated by a group common DCI (GC-DCI) carrying the preemption indication. Preemption may affect a particular time and/or frequency resources. The time duration of the reference DL resource for preemption indication may equal the monitoring periodicity of the group-common DCI carrying the preemption indication (e.g., 1 slot, 2 slots, etc.). The frequency region of the reference DL resource for preemption indication may be the active DL BWP. The periodicity to monitor group common DCI for a pre-emption indication may be UE configured. For RRC-configurable payload size of the GC-DCI carrying the downlink pre-emption indication (PI), a bitmap may be used to indicate preempted resources within the semi-statically configured DL reference resource. The bitmap may indicate preemption for one or more frequency domain parts (N>1) and/or one or more time domain parts (M>1). The combinations of {M, N}={14, 1}, {7, 2} may be supported and predefined. A combination of {M,N} from this set of possible {M,N} may be indicated in 1-bit by RRC configuration for a UE. When a preemption indication (PI) is detected by the UE115-a, the impacted time/frequency resource may be assumed to be preempted (although previously allocated), and the UE115-amay process resources accordingly. UL PIs may be indicated as described with respect to DL PIs. However, when the UL PI is detected, the UE may stop an ongoing UL transmission according to the PI. In NR systems, such as wireless communications system200, the devices may support scheduling of resources via grants for resource management. The grants may be in the form of dynamically scheduled grants via DCI or configured grants. For dynamically scheduled grants via DCI, PDSCH may be scheduled by DCI formats 1_0 and 1_1, PUSCH may be scheduled by DCI formats 0_0 and 0_1. The schedule may be for a mini-slot (e.g., 2, 4, or 7 symbols), a slot, or multiple slots. For resources scheduled via configured grants, the resources may be configured via RRC or with scheduling information partially configured by RRC and using DCI to activate/release the configured grant while the activation/deactivation DCI may provide additional scheduling information. Each grant may be allocated for a packet consisting of one transport block (for up to 4 layers MIMO) or two transport blocks (5 to 8 layers MIMO), with a specific set of frequency and time resources. Aspects of the disclosure described herein provide for resource management techniques to leverage dynamic scheduling via DCI and configured grant scheduling for file transmission. Group-based scheduled packets (e.g., files) may require high reliability and reasonably low latency (e.g., in XR services). This may be due to packet dependencies within a file. For example, if one packet of a file is dropped or fails to transmit in wireless communications system200, then the file (e.g., remaining packets) may not be useful to one or more of the devices (e.g., the UE115-aand base station105-a). As such, the techniques described herein may increase the reliability of a file transmission. Further aspects may provide techniques for handling potential interaction with slot format indication and UL/DL preemption indications, as well as power management, DM-RS management, and coherent transmission/reception. FIG.3illustrates an example of a mapping300that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, mapping300may implement aspects of wireless communications system100. In some examples, the mapping300may be implemented by aspects of wireless communications system100and the wireless communications system200as described with reference toFIG.1andFIG.2. In the example ofFIG.3, the mapping300may depict a mapping of packets (such as data packets included in one or more processing batches) to one or more transport blocks based on a processing-batch assignment for each packet for management resources. In one implementation, the packets may be mapped to one or more files (or processing batches) based on delivery deadlines associated with the packets. According to one or more aspects of the present disclosure, a transmitter (such as, a UE115or a base station105) may map a first group of packets (such as, packets associated with File 1) to a first transport block (TB 1), a second transport block (TB 2), and a third transport block (TB 3). As depicted in the example ofFIG.3, the first group of packets may be associated with a first processing batch (or file). In some cases, the first processing batch may have an urgent deadline. In some examples, the transmitter may map a second group of packets (such as packets associated with File 2) to a fourth transport block (TB 3), a fifth transport block (TB 5), a sixth transport block (TB 6), and a seventh transport block (TB 7)). In some examples, the second group of packets may be associated with a second processing batch (or file). In some cases, the second processing batch may have a non-urgent deadline. As described with reference toFIG.3, the base station105may map the packets as previously described, and the UE115may receive the mapped packets. The UE115may then optionally transmit one or more transport block (TB) acknowledgements (for TB 1, TB 2, TB 3, TB 3, TB 5, TB 6, and TB 7). According to one or more aspects of the present disclosure, the UE115may provide a processing-batch based (or file-based) acknowledgement to indicate a reception of a processing-batch. For example, the UE115may transmit a first processing-batch based acknowledgement to acknowledge the reception of File 1, and a second processing-batch based acknowledgement to acknowledge the reception of File 2. FIG.4illustrates an example of a wireless communications system400that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, wireless communications system400may implement aspects of wireless communications system100. In some examples, the wireless communications system400may implement aspects of the wireless communications systems ofFIGS.1through3. The wireless communications system400includes a base station105-band a UE115-b, which may be examples of the corresponding devices ofFIGS.1to3. The UE115-band the base station105-bmay communicate various control and data (e.g., packets430) in accordance with various grants (e.g., grant425) and on one or more communication links established between the UE115-band the base station105-b. InFIG.4, the base station105-btransmits one or more grants including grant425on downlink resources (e.g., PDCCH, PDSCH). The grant may allocate resources for communication of a packet430of a plurality of packets configured to be processed together as a file440. The grant425(or another grant) may allocate various resources, such as slot445, which may be used to communicate the packets430of the file440. For performing resource management, the UE115-bmay identify a transmission direction schedule for the slot445including a plurality of symbols. The transmission direction schedule may identify the symbols of the slot as downlink symbols410, flexible symbols415, or uplink symbols420in accordance with a grant. In accordance with the transmission direction schedule, the file may be communicated on the various symbols of the slot445. For example, if the file440is scheduled to be transmitted from the UE115-bto the base station105-b, then the UE115-bmay map the data (e.g., packets430) of the file440to the uplink symbols420of the slot for communication of a batch of transmissions including the file. In some cases, the UE115-bmay designate one or more of the flexible symbols415as uplink symbols420(e.g., in addition to the uplink symbols420) for communication of the file440as a batch of transmission. If the file440is scheduled to be transmitted from the base station105-bto the UE115-b, then the downlink symbols410of the slot445may be used to communicate the file440. In some case, the flexible symbols415may also be designated as downlink symbols for communication of the file440in a batch of transmissions. For any cell-specific and UE-specific semi-statically indicated downlink symbols410or uplink symbols420, communication of the packets430of the file440may be consistent with the indicated link direction. In other words, the downlink symbols410and the uplink symbols420may not be changed for communication of the packets430. If the file440is scheduled for communication via a UE-specific DCI (e.g., if the grant425is a UE-specific DCI), then the direction of the flexible symbols415may be determined in accordance with the UE-specific DCI. If the file440is scheduled via configured grant (e.g., the grant425is a configured grant indication), then directions of the flexible symbols415may be determined in accordance with either a group common DCI or in accordance with the configured grant (e.g., grant425). In the case of the file440being scheduled via configured grant and the group-common DCI taking precedence for flexible symbol415direction over the configured grant, then a packet430being dropped from the file440may increase the likelihood that the file440is not delivered. However, in such cases, then the UE115-band the base station105-bmay be configured to automatically retransmit a dropped packet430of the file440. In the case of the file440being scheduled via configured grant and the configured grant taking precedence for flexible symbol415direction over the configured grant, a new group common DCI may be introduced. The group common DCI may indicate a slot structure for group-scheduling (or file scheduling) such that group-scheduled packets may take precedence over legacy group common DCIs. Thus, when a file440is scheduled for transmission, then the UE115-bmay ignore the legacy DCI and monitor for the new dedicated group common DCI. In some cases, the wireless communications system400may support other resource management techniques for increasing the likelihood for successful file transmission. For example, if the file is scheduled for transmission between the UE115-band the base station105-b, then the UE115-bmay determine to increase the power for transmission of each packet of the file. For example, file and non-file based PUSCH may share the same open loop configuration and the same closed loop operation. However, for the PUSCH transmission identified to be within a file, an additional power boost (e.g., of n dB) can be applied for new & re-transmissions (or only to re-transmissions). The value of n may be pre-defined or configured or may be dependent on the file size. Another resource management technique may support coherent detection/transmission across two or more packets in the group (e.g., on the same carrier). For downlink transmissions of files DM-RS borrowing/bundling may be considered. That is, DM-RS for a first packet in a group can be used or combined with DM-RS of a second packet in the same group to improve PDSCH detection. The same precoding and energy per resource element (EPRE) may be assumed across different packets. For uplink transmission of files, uplink transmission adjustment may be prohibited during the transmission of the entire group (to maintain phase continuity). FIG.5illustrates an example of a wireless communications system500that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, wireless communications system500may implement aspects of wireless communications system100. In some examples, the wireless communications system500may implement aspects of the wireless communications systems ofFIGS.1through4. The wireless communications system500includes a base station105-cand a UE115-c, which may be examples of the corresponding devices ofFIGS.1to4. The UE115-cand the base station105-cmay communicate various control and data (e.g., packets530) in accordance with various grants and on one or more communication links established between the UE115-band the base station105-b. A file515including a plurality of packets530configured to be processed together is scheduled for transmission from the UE115-cto the base station105-cor is being received by the UE115-cfrom the base station105-caccording to a grant. The base station105-cmay transmit a preemption indication510. The preemption indication510may specify resources for preemption. In some cases, the specified resources correspond to resources being used to communicate the file515or packets530of the file. According to the preemption indication510, the UE115-cmay identify that at least a portion of the set of resource allocated for communication of a batch of transmissions (carrying the file515) is preempted. Based on one or more preemption rules, the UE115-cmay apply the preemption indication510to processing or transmission of the file515. If the file515is scheduled for downlink and the UE115-creceives the preemption indication510, then the preemption rule may designate that the indicated preempted resources are not available for the corresponding PDSCH. In other words, the UE115-cmay process the resources carrying the file515. This processing may be similar to the effect of a preemption indication to an eMBB device. If the file515is scheduled for uplink and the UE115-creceives the preemption indication510, then the preemption rule may designate that the impacted PUSCH is not to be used to transmit of the file starting from the indicated pre-empted resources (e.g., the UE115-cstop transmission on the PUSCH). In some cases, a preemption rule may designate that the UE115-cignore the preemption indication510according to various conditions. For example, a new preemption indication dedicated to file scheduling may be used for group scheduled packets530. Thus, when a file515is scheduled for transmission, the UE115-cmay ignore legacy DL preemption indications or legacy UL preemption indications and monitor for the new file or group dedicated downlink preemption indication or uplink preemption indication. FIG.6illustrates an example of a wireless communications system600that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, wireless communications system600may implement aspects of wireless communications system100. In some examples, the wireless communications system600may implement aspects of the wireless communications systems ofFIGS.1through5. The wireless communications system600includes a base station105-dand a UE115-d, which may be examples of the corresponding devices ofFIGS.1to5. The UE115-dand the base station105-dmay communicate various control and data (e.g., packets630) in accordance with various grants and on one or more communication links established between the UE115-dand the base station105-d. In some cases, resources may be granted via one or DCI messages, such as legacy DCI605and transmission batch DCI610. The transmission batch DCI610may be allocated to a first set of decoding candidates in a control channel (e.g., PDCCH) and may be configured to allocate resources for a batch of transmissions that collectively carry a file615having a plurality of packets630configured to be processed together. The legacy DCI605may be allocated to a second set of decoding candidates in the control channel and may be configured to allocate resources for communication of data not pertaining to files. The first set of decoding candidates and the second set of decoding candidates may differ by at least one decoding candidate. The UE115-dand the base station105-dmay communicate based at least in part on monitoring of the first or second set of decoding candidate by the UE115-d. The control channel carrying the first and second set of decoding candidate may be a cell-specific or a group-specific downlink control channel or a UE-specific grant In some cases, the first set if decoding candidates and the second set of decoding candidates differ by at least one decoding candidate based at least in part on a set of aggregation levels, the set of decoding candidates for a given aggregative level, or a downlink control information message size. For example, the transmission batch DCI610may have an aggregation level16instead of aggregation level8. In some cases, the transmission batch DCI610of the first set of decoding candidates includes an indication linking the downlink control information message to a previous downlink message in a previous grant (e.g., previous DCI) corresponding to the batch of transmissions (e.g., the file615). For example, a first transmission batch DCI610may schedule a first packet630of the file615, and a second transmission batch DCI may schedule a second packet630of file615. Each of the first transmission batch DCI610and the second transmission batch DCI610may indicate the presence of the other DCIs, so that if one DCI is missed, the UE115-dmay identify PDSCH transmissions scheduled by the other DCI, if the PDSCHs have one-to-one resource mappings (e.g., same resource allocation in adjacent slots). FIG.7illustrates an example of a wireless communications system700that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, wireless communications system700may implement aspects of wireless communications system100. In some examples, the wireless communications system700may implement aspects of the wireless communications systems ofFIGS.1through6. The wireless communications system700includes a base station105-eand a UE115-e, which may be examples of the corresponding devices ofFIGS.1to5. The UE115-dand the base station105-dmay communicate various control and data (e.g., packets730) in accordance with various grants and on one or more communication links established between the UE115-dand the base station105-d. The UE115-eand the base station105-emay communicate using NR wireless communication formats and may support transmission batch configured grants710for file715transmission. The UE115-emay transmit a transmission batch configured grant710to the UE115-e. The transmission batch configured grant710may include a configured grant index indicative of a resource configuration for communication of a batch of transmissions that collectively carry the file715having a plurality of packets730configured to be processed together. In a first resource configuration example, the configured grant index may indicate utilization of a single transport block in a slot. In a second resource configuration example, the configured grant index may indicate utilization of two transport blocks in two adjacent slots. In a third resource configuration example, the configured grant index may indicate utilize of four transport blocks of a first size in four adjacent slots. In a fourth resource configuration example, the configurated grant index may indicate utilization of four transport blocks of a second size in four adjacent slots. Base station105-eor UE115-emay activate a resource configuration indicated by the transmission batch configured grant710based on need. In one example, UE115-emay chose (e.g., activate) one configured grant depending in the buffer size within the UE115-eand/or quality of service requirements. Accordingly, the UE115-eand the base station105-emay determine resources for communication of the file715based on the file715and the transmission batch configured grant710. FIG.8illustrates an example of a process flow diagram800that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, process flow diagram800may implement aspects of wireless communications system100. The process flow diagram includes UE115and base station105, which may be examples of the corresponding devices ofFIGS.1through7. The devices may be operating in a NR wireless communications system. At805, the UE115identifies a transmission direction schedule for a slot. The transmission schedule may identify one or more symbols of the slot as being uplink, downlink, or flexible. In some cases, identifying the transmission direction schedule includes receiving the transmission direction schedule via a cell-specific or UE-specific radio resource control message, wherein a transmission direction of the one or more symbols, as indicated by the grant, is in accordance with the transmission direction schedule for the one or more symbols. At810, the UE115receives, from the base station105, a grant for communication, by the UE, of a packet that is one of a plurality of packets configured to be processed together as a file. In some cases, the grant is a UE-specific downlink control information message, and the transmission direction of a flexible symbol may be based at least in part on the UE-specific downlink control information message. In other cases, the grant may be a configured grant via a radio resource control message. The UE115may further receive a group common downlink control information, and the transmission direction of a flexible symbol may be based at least in part on the group common downlink control information message or on the configured grant. The group common downlink control information message may be a formatted in a file-specific format. In the case of the grant being a configured grant, the grant may include a configured grant index indicative of a resource configuration for communication, by the UE, of a batch of transmissions that collectively carry a file having a plurality of packets configured to be processed together. For example, the resource configuration may include one or more assignments for the communication of the file using two or more transport blocks, which may be transmitted or received in adjacent slots. In some cases, the UE115may activate the configured grant based on the file, quality of service requirements, or buffer size. At815, the UE115identifies, based at least in part on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet. Identification of the symbols may include identifying at least one symbol of the slot as a flexible symbol. At820, the UE115may determine a transmission power for transmitting the uplink transmission based at least in part on the grant pertaining to transmission of batches. The UE115may increase the transmission power relative to transmission not associated with transmitting the file. In such cases, the UE115may increase the likelihood that the packets of the file are received at the base station105. The transmission power amount may be determined based on a pre-defined offset, the size of the file, or an indication received in a control channel. At825, the UE115and the base station105participate in the communication of the packet on the identified one or more symbols of the slot. Participation in communication may include transmitting the packet to the base station105or receiving the packet from the base station105. In some cases, transmitting the packet may include transmitting the uplink transmission in accordance with the transmission power and the grant. In the same or alternative cases, the UE115may transmit the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based at least in part on receiving the grant for communication of the uplink transmission. When the batch of transmissions is communicated from the base station105to the UE115, a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch, and the UE115may decode the transmission in accordance with the combined reference signal. FIG.9illustrates an example of a process flow diagram900that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, process flow diagram900may implement aspects of wireless communications system100. The process flow diagram900includes UE115and base station105, which may be examples of the corresponding devices ofFIGS.1through8. The devices may be operating in a NR wireless communications system. At905, UE115receives information via a control channel from the base station105. The control channel may be a PDCCH. At910, the UE115identifies a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a plurality of packets configured to be processed together. At920, the UE115identifies a second set of decoding candidates for communications not pertaining to files, wherein the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate. The decoding candidates may correspond to resources of the control channel. In some cases, the UE115monitors a cell-specific or a group-specific downlink control channel to identify the decoding candidates. In other cases, the UE115monitors for one or more UE-specific grants to identify the decoding candidates. The first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate based at least in part on a set of aggregation levels, a set of decoding candidates for a given aggregation level, or a downlink control information message size. In some cases, a downlink control information message in one of the first set of decoding candidates includes an indication linking the downlink control information message to a previous downlink message in a previous grant corresponding to the batch of transmissions. At925, the UE115and the base station105participate in the communication by monitoring at least one of the first set of decoding candidates or the second set of decoding candidates. FIG.10illustrates an example of a process flow diagram1000that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. In some examples, process flow diagram1000may implement aspects of wireless communications system100. The process flow diagram1000includes UE115and base station105, which may be examples of the corresponding devices ofFIGS.1through9. The devices may be operating in a NR wireless communications system. At1005, the UE115identifies that a batch of transmissions has been received from a base station or is scheduled to be transmitted to the base station via a set of resources. The batch collectively comprises a file having a plurality of packets configured to be processed together. At1010, the UE115receives a preemption indication from the base station. At1015, the UE115identifies, via the preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted. At1020, the UE115applies the preemption indication to process or transmission of the batch in accordance with a rule for preemption of batches. In cases when the batch is received from the base station105, applying the preemption indication to processing the batch includes processing the batch without processing transmissions received on the portion of the set of resources indicated as preempted, in accordance with the rule for preemption of batches. In other cases where the batch is received from the base station applying the preemption indication to processing the batch includes processing the batch by ignoring the preemption indication, in accordance with the rule for preemption of batches. In cases when the batch is transmitted to the base station105, applying the preemption rule to transmission of the batch may include transmitting a first portion of the file using resources of the set of resources that precede the portion of the set of resources indicated as preempted and refraining from transmitting a second portion of the file on the portion of the set of resources indicated as preempted, in accordance with the rule for preemption of batches. In other cases when the batch is transmitted to the base station105, applying the preemption rule to transmission of the batch may include transmitting the file by ignoring the preemption indication, in accordance with the rule for preemption of batches. In some cases, the preemption indication is different from a legacy preemption indication, and the UE115ignores the legacy preemption indication based on the file being scheduled or received. FIG.11shows a block diagram1100of a device1105that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The device1105may be an example of aspects of a UE115as described herein. The device1105may include a receiver1110, a communications manager1115, and a transmitter1120. The device1105may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver1110may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission batch scheduling and resource management, etc.). Information may be passed on to other components of the device1105. The receiver1110may be an example of aspects of the transceiver1420described with reference toFIG.14. The receiver1110may utilize a single antenna or a set of antennas. The communications manager1115may identify a packet that is one of a set of packets configured to be processed together as a file, perform resource management for communicating the packet based on identifying that the packet is one of the set of packets configured to be processed together as the file, and participate in the communicating of the packet in accordance with the resource management and the packet being one of the set of packets configured to be processed together as the file. The communications manager1115may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible, receive a grant for communication, by the UE, of a packet that is one of a set of packets configured to be processed together as a file, identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet, and participate in the communication of the packet on the identified one or more symbols of the slot. The communications manager1115may also identify a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together, identify a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate, and participate in the communication by monitoring at least one of the first set of decoding candidates or the second set of decoding candidates. The communications manager1115may also receive at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication, by the UE, of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and participate in the communication based at least in part of on the configured grant. The communications manager1115may also identify that a batch of transmissions has been received from a base station or is scheduled to be transmitted to the base station via a set of resources, the batch collectively including a file having a set of packets configured to be processed together, identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted, and apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The communications manager1115may also receive a grant for communication, by the UE, of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together, determine a transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches, and transmit the uplink transmission in accordance with the transmission power and the grant. The communications manager1115may also receive a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together, receive the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch, and decode the downlink transmission in accordance with the combined reference signal. The communications manager1115may also receive a grant for communication, by the UE, of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and transmit the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The communications manager1115may be an example of aspects of the communications manager1410described herein. The communications manager1115, or its sub-components, may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager1115, or its sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations The communications manager1115, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the communications manager1115, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the communications manager1115, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure. The transmitter1120may transmit signals generated by other components of the device1105. In some examples, the transmitter1120may be collocated with a receiver1110in a transceiver module. For example, the transmitter1120may be an example of aspects of the transceiver1420described with reference toFIG.14. The transmitter1120may utilize a single antenna or a set of antennas. FIG.12shows a block diagram1200of a device1205that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The device1205may be an example of aspects of a device1105, or a UE115as described herein. The device1205may include a receiver1210, a communications manager1215, and a transmitter1270. The device1205may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver1210may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission batch scheduling and resource management, etc.). Information may be passed on to other components of the device1205. The receiver1210may be an example of aspects of the transceiver1420described with reference toFIG.14. The receiver1210may utilize a single antenna or a set of antennas. The communications manager1215may be an example of aspects of the communications manager1115as described herein. The communications manager1215may include a transmission direction identifier1220, a grant receiving interface1225, a symbol identifier1230, a communication interface1235, a batch decoding component1240, a decoding component1245, a batch transmission component1250, a resource identification component1255, a preemption processing component1260, a transmission power component1265, a packet identification component1280, and a resource management component1285. The communications manager1215may be an example of aspects of the communications manager1410described herein. The packet identification component1280may identify a packet that is one of a set of packets configured to be processed together as a file. The resource management component1285may perform resource management for communicating the packet based on identifying that the packet is one of the set of packets configured to be processed together as the file. The communication interface1235may participate in the communicating of the packet in accordance with the resource management and the packet being one of the set of packets configured to be processed together as the file. The transmission direction identifier1220may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible. The grant receiving interface1225may receive a grant for communication, by the UE, of a packet that is one of a set of packets configured to be processed together as a file. The symbol identifier1230may identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet. The communication interface1235may participate in the communication of the packet on the identified one or more symbols of the slot. The batch decoding component1240may identify a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The decoding component1245may identify a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate. The communication interface1235may participate in the communication by monitoring at least one of the first set of decoding candidates or the second set of decoding candidates. The grant receiving interface1225may receive at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication, by the UE, of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The communication interface1235may participate in the communication based at least in part of on the configured grant. The batch transmission component1250may identify that a batch of transmissions has been received from a base station or is scheduled to be transmitted to the base station via a set of resources, the batch collectively including a file having a set of packets configured to be processed together. The resource identification component1255may identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted. The preemption processing component1260may apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The grant receiving interface1225may receive a grant for communication, by the UE, of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The transmission power component1265may determine a transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches. The communication interface1235may transmit the uplink transmission in accordance with the transmission power and the grant. The grant receiving interface1225may receive a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The communication interface1235may receive the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. The decoding component1245may decode the downlink transmission in accordance with the combined reference signal. The grant receiving interface1225may receive a grant for communication, by the UE, of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The communication interface1235may transmit the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The transmitter1270may transmit signals generated by other components of the device1205. In some examples, the transmitter1270may be collocated with a receiver1210in a transceiver module. For example, the transmitter1270may be an example of aspects of the transceiver1420described with reference toFIG.14. The transmitter1270may utilize a single antenna or a set of antennas. FIG.13shows a block diagram1300of a communications manager1305that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The communications manager1305may be an example of aspects of a communications manager1115, a communications manager1215, or a communications manager1410described herein. The communications manager1305may include a transmission direction identifier1310, a grant receiving interface1315, a symbol identifier1320, a communication interface1325, a batch decoding component1330, a decoding component1335, a grant activation component1340, a batch transmission component1345, a resource identification component1350, a preemption processing component1355, a preemption interface1360, and a transmission power component1365. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses). The transmission direction identifier1310may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible. In some examples, the transmission direction identifier1310may receive the transmission direction schedule via a cell-specific or UE-specific radio resource control message, where a transmission direction of the one or more symbols, as indicated by the grant, is in accordance with the transmission direction schedule for the one or more symbols. In some examples, the transmission direction identifier1310may receive a group common downlink control information message, where a transmission direction of the flexible symbol is based on the group common downlink control information message. In some examples, the transmission direction identifier1310may receive a group common downlink control information message, where a transmission direction of the flexible symbol is based on the group common downlink control information message and where the group common downlink control information message is formatted as a file-specific format. In some cases, the configured grant is for communication of the file via uplink resources, downlink resources, or sidelink resources. The grant receiving interface1315may receive a grant for communication, by the UE, of a packet that is one of a set of packets configured to be processed together as a file. In some examples, the grant receiving interface1315may receive at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication, by the UE, of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the grant receiving interface1315may receive a grant for communication, by the UE, of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the grant receiving interface1315may receive a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the grant receiving interface1315may receive a grant for communication, by the UE, of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the grant receiving interface1315may receive the grant via a UE-specific downlink control information message, where a transmission direction of the flexible symbol is based on the grant. In some examples, the grant receiving interface1315may receive the grant as a configured grant via a radio resource control message. In some examples, the grant receiving interface1315may receive the grant as a configured grant via a radio resource control message, where a transmission direction of the flexible symbol is based on the grant. In some examples, the grant receiving interface1315may receive the configured grant including one or more assignments for the communication of the file using two or more transport blocks. In some cases, the two or more transport blocks are scheduled by the one or more assignments to be transmitted or received in two or more adjacent slots. The symbol identifier1320may identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet. In some examples, the symbol identifier1320may identify that at least one of the one or more symbols is a flexible symbol, as indicated by the transmission direction schedule. The communication interface1325may participate in the communication of the packet on the identified one or more symbols of the slot. In some examples, the communication interface1325may participate in the communication by monitoring at least one of the first set of decoding candidates or the second set of decoding candidates. In some examples, the communication interface1325may participate in the communication based at least in part of on the configured grant. In some examples, the communication interface1325may transmit the uplink transmission in accordance with the transmission power and the grant. In some examples, the communication interface1325may receive the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. In some examples, the communication interface1325may transmit the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. In some examples, the communication interface1325may process the batch by ignoring the at least one legacy preemption indication. In some examples, the communication interface1325may determine a first DM-RS pattern for a first transmission of the at least two transmissions. In some examples, the communication interface1325may determine a second DM-RS pattern for a second transmission of the at least two transmissions based on at least in part of the first DM-RS pattern. In some cases, the phase continuity is maintained based on prohibiting power adjustments within the at least two transmissions. The batch decoding component1330may identify a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The decoding component1335may identify a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate. In some examples, the decoding component1335may decode the downlink transmission in accordance with the combined reference signal. In some examples, the decoding component1335may monitor a cell-specific or a group-specific downlink control channel. In some examples, the decoding component1335may monitor for one or more UE-specific grants. In some cases, the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate based on a set of aggregation levels, a set of decoding candidates for a given aggregation level, or a downlink control information message size. In some cases, the first set of decoding candidates has a higher aggregation level than the second set of decoding candidates. In some cases, a downlink control information in the first set of decoding candidates includes an indication linking the downlink control information message to a previous downlink message in a previous grant corresponding to the batch of transmissions. In some cases, a precoding and energy per resource element are consistent across each transmission of the set of transmissions of the batch. The batch transmission component1345may identify that a batch of transmissions has been received from a base station or is scheduled to be transmitted to the base station via a set of resources, the batch collectively including a file having a set of packets configured to be processed together. The resource identification component1350may identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted. The preemption processing component1355may apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. In some examples, the preemption processing component1355may process the batch without processing transmissions received on the portion of the set of resources indicated as preempted, in accordance with the rule for preemption of batches. In some examples, the preemption processing component1355may transmit a first portion of the file using resources of the set of resources that precede the portion of the set of resources indicated as preempted. In some examples, the preemption processing component1355may refrain from transmitting a second portion of the file on the portion of the set of resources indicated as preempted, in accordance with the rule for preemption of batches. In some examples, the preemption processing component1355may process the batch by ignoring the preemption indication, in accordance with the rule for preemption of batches. In some examples, the preemption processing component1355may transmit the file by ignoring the preemption indication, in accordance with the rule for preemption of batches. The transmission power component1365may determine a transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches. In some examples, the transmission power component1365may determine an amount of the transmission power based on a size of the file. In some examples, the transmission power component1365may determine an amount of the transmission power based on an indication from a control channel. In some examples, the transmission power component1365may determine an amount of the transmission power based on a pre-defined power offset. The grant activation component1340may activate the configured grant based on the file, a buffer size, quality of service requirements, or a combination thereof. In some cases, the activation indicates a number of transport blocks for communication of the batch of transmissions. The preemption interface1360may monitor at least one legacy preemption indication. FIG.14shows a diagram of a system1400including a device1405that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The device1405may be an example of or include the components of device1105, device1205, or a UE115as described herein. The device1405may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager1410, an I/O controller1415, a transceiver1420, an antenna1425, memory1430, and a processor1440. These components may be in electronic communication via one or more buses (e.g., bus1445). The communications manager1410may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible, receive a grant for communication, by the UE, of a packet that is one of a set of packets configured to be processed together as a file, identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet, and participate in the communication of the packet on the identified one or more symbols of the slot. The communications manager1410may also identify a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together, identify a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate, and participate in the communication by monitoring at least one of the first set of decoding candidates or the second set of decoding candidates. The communications manager1410may also receive at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication, by the UE, of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and participate in the communication based at least in part of on the configured grant. The communications manager1410may also identify that a batch of transmissions has been received from a base station or is scheduled to be transmitted to the base station via a set of resources, the batch collectively including a file having a set of packets configured to be processed together, identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted, and apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The communications manager1410may also receive a grant for communication, by the UE, of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together, determine a transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches, and transmit the uplink transmission in accordance with the transmission power and the grant. The communications manager1410may also receive a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together, receive the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch, and decode the downlink transmission in accordance with the combined reference signal. The communications manager1410may also receive a grant for communication, by the UE, of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and transmit the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The I/O controller1415may manage input and output signals for the device1405. The I/O controller1415may also manage peripherals not integrated into the device1405. In some cases, the I/O controller1415may represent a physical connection or port to an external peripheral. In some cases, the I/O controller1415may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In other cases, the I/O controller1415may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller1415may be implemented as part of a processor. In some cases, a user may interact with the device1405via the I/O controller1415or via hardware components controlled by the I/O controller1415. The transceiver1420may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver1420may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1420may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas. In some cases, the wireless device may include a single antenna1425. However, in some cases the device may have more than one antenna1425, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The memory1430may include RAM and ROM. The memory1430may store computer-readable, computer-executable code1435including instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory1430may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices. The processor1440may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1440may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor1440. The processor1440may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1430) to cause the device1405to perform various functions (e.g., functions or tasks supporting transmission batch scheduling and resource management). The code1435may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code1435may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code1435may not be directly executable by the processor1440but may cause a computer (e.g., when compiled and executed) to perform functions described herein. FIG.15shows a block diagram1500of a device1505that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The device1505may be an example of aspects of a base station105as described herein. The device1505may include a receiver1510, a communications manager1515, and a transmitter1520. The device1505may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver1510may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission batch scheduling and resource management, etc.). Information may be passed on to other components of the device1505. The receiver1510may be an example of aspects of the transceiver1820described with reference toFIG.18. The receiver1510may utilize a single antenna or a set of antennas. The communications manager1515may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible, transmit, to a UE, a grant for communication of a packet that is one of a set of packets configured to be processed together as a file, identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet, and participate in the communication of the packet on the identified one or more symbols of the slot. The communications manager1515may also transmit a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together, transmit a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate, and participate in the communication based on at least one of the first set of decoding candidates or the second set of decoding candidates. The communications manager1515may also transmit at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication of a batch of transmissions that collectively carry a file having a set of packets and participate in the communication based on the configured grant. The communications manager1515may also identify that a batch of transmissions has been transmitted to a UE or is scheduled to be received from the UE via a set of resources, the batch collectively including a file having a set of packets configured to be processed together, identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted, and apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The communications manager1515may also transmit, to a UE a grant for communication of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together, determine the transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches, and transmit the uplink transmission in accordance with the increased power and the grant. The communications manager1515may also transmit, to a UE a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and transmit the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. The communications manager1515may also transmit, to a UE, a grant for communication of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and receive the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The communications manager1515may be an example of aspects of the communications manager1810described herein. The communications manager1515, or its sub-components, may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager1515, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC), a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure. The communications manager1515, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the communications manager1515, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the communications manager1515, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure. The transmitter1520may transmit signals generated by other components of the device1505. In some examples, the transmitter1520may be collocated with a receiver1510in a transceiver module. For example, the transmitter1520may be an example of aspects of the transceiver1820described with reference toFIG.18. The transmitter1520may utilize a single antenna or a set of antennas. FIG.16shows a block diagram1600of a device1605that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The device1605may be an example of aspects of a device1505, or a base station105as described herein. The device1605may include a receiver1610, a communications manager1615, and a transmitter1665. The device1605may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver1610may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission batch scheduling and resource management, etc.). Information may be passed on to other components of the device1605. The receiver1610may be an example of aspects of the transceiver1820described with reference toFIG.18. The receiver1610may utilize a single antenna or a set of antennas. The communications manager1615may be an example of aspects of the communications manager1515as described herein. The communications manager1615may include a transmission direction identifier1620, a grant transmitting interface1625, a symbol identifier1630, a communication interface1635, a batch control component1640, a control component1645, a preemption interface1650, a preemption processing component1655, and a transmission power component1660. The communications manager1615may be an example of aspects of the communications manager1810described herein. The transmission direction identifier1620may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible. The grant transmitting interface1625may transmit, to a UE, a grant for communication of a packet that is one of a set of packets configured to be processed together as a file. The symbol identifier1630may identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet. The communication interface1635may participate in the communication of the packet on the identified one or more symbols of the slot. The batch control component1640may transmit a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The control component1645may transmit a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate. The communication interface1635may participate in the communication based on at least one of the first set of decoding candidates or the second set of decoding candidates. The batch control component1640may transmit at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication of a batch of transmissions that collectively carry a file having a set of packets. The communication interface1635may participate in the communication based on the configured grant. The batch control component1640may identify that a batch of transmissions has been transmitted to a UE or is scheduled to be received from the UE via a set of resources, the batch collectively including a file having a set of packets configured to be processed together. The preemption interface1650may identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted. The preemption processing component1655may apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The grant transmitting interface1625may transmit, to a UE a grant for communication of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The transmission power component1660may determine the transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches. The communication interface1635may transmit the uplink transmission in accordance with the increased power and the grant. The grant transmitting interface1625may transmit, to a UE a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The communication interface1635may transmit the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. The grant transmitting interface1625may transmit, to a UE, a grant for communication of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The communication interface1635may receive the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The transmitter1665may transmit signals generated by other components of the device1605. In some examples, the transmitter1665may be collocated with a receiver1610in a transceiver module. For example, the transmitter1665may be an example of aspects of the transceiver1820described with reference toFIG.18. The transmitter1665may utilize a single antenna or a set of antennas. FIG.17shows a block diagram1700of a communications manager1705that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The communications manager1705may be an example of aspects of a communications manager1515, a communications manager1615, or a communications manager1810described herein. The communications manager1705may include a transmission direction identifier1710, a grant transmitting interface1715, a symbol identifier1720, a communication interface1725, a batch control component1730, a control component1735, a preemption interface1740, a preemption processing component1745, and a transmission power component1750. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses). The transmission direction identifier1710may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible. The grant transmitting interface1715may transmit, to a UE, a grant for communication of a packet that is one of a set of packets configured to be processed together as a file. In some examples, the grant transmitting interface1715may transmit, to a UE a grant for communication of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the grant transmitting interface1715may transmit, to a UE a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the grant transmitting interface1715may transmit, to a UE, a grant for communication of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the grant transmitting interface1715may transmit, to the UE, a transmission direction schedule via a cell-specific or UE-specific radio resource control message, where a transmission direction of one or more symbols of a slot, as indicated by the grant, is in accordance with the transmission direction schedule for the one or more symbols. In some examples, the grant transmitting interface1715may transmit the grant via a UE-specific downlink control information message, where a transmission direction of a flexible symbol of a slot is based on the grant. In some examples, the grant transmitting interface1715may transmit the grant as a configured grant via a radio resource control message. In some examples, the grant transmitting interface1715may transmit a group common downlink control information message, where a transmission direction of a flexible symbol of a slot is based on the group common downlink control information message. In some examples, the grant transmitting interface1715may transmit the grant as a configured grant via a radio resource control message, where a transmission direction of the flexible symbol is based on the grant. In some examples, the grant transmitting interface1715may transmit a group common downlink control information message, where a transmission direction of the flexible symbol is based on the group common downlink control information message and where the group common downlink control information message is formatted as a batch-specific format. The symbol identifier1720may identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet. In some examples, the symbol identifier1720may identify that at least one of the one or more symbols is a flexible symbol, as indicated by the transmission direction schedule. The communication interface1725may participate in the communication of the packet on the identified one or more symbols of the slot. In some examples, the communication interface1725may participate in the communication based on at least one of the first set of decoding candidates or the second set of decoding candidates. In some examples, the communication interface1725may participate in the communication based on the configured grant. In some examples, the communication interface1725may transmit the uplink transmission in accordance with the increased power and the grant. In some examples, the communication interface1725may transmit the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. In some examples, the communication interface1725may receive the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. In some examples, the communication interface1725may determine a first DM-RS pattern for a first transmission of the at least two transmissions. In some examples, the communication interface1725may determine a second DM-RS pattern for a second transmission of the at least two transmissions based on at least in part of the first DM-RS pattern. In some cases, a precoding and energy per resource element are consistent across each transmission of the batch. In some cases, the phase continuity is maintained based on prohibiting power adjustments within the at least two transmissions. The batch control component1730may transmit a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. In some examples, the batch control component1730may transmit at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication of a batch of transmissions that collectively carry a file having a set of packets. In some examples, the batch control component1730may identify that a batch of transmissions has been transmitted to a UE or is scheduled to be received from the UE via a set of resources, the batch collectively including a file having a set of packets configured to be processed together. In some examples, the batch control component1730may transmit the first set of decoding candidates or the second set of decoding candidates in a cell-specific or a group-specific downlink control channel. In some examples, the batch control component1730may transmit one or more UE-specific grants. In some examples, the batch control component1730may transmit the configured grant including one or more assignments for the communication of the file using two or more transport blocks. In some examples, the batch control component1730may transmit, to the UE, an indication of an amount of the transmission power via a control channel. In some cases, the two or more transport blocks are scheduled by the grant to be transmitted or received in two or more adjacent slots. The control component1735may transmit a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate. In some cases, the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate based on a set of aggregation levels, a set of decoding candidates for a given aggregation level, or a downlink control information message size. In some cases, the first set of decoding candidates has a higher aggregation level than the second set of decoding candidates. In some cases, a downlink control information in the first set of decoding candidates includes an indication linking the downlink control information message to a previous downlink message in a previous grant corresponding to the batch of transmissions. In some cases, the configured grant is for communication of the file via uplink resources, downlink resources, or sidelink resources. The preemption interface1740may identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted. In some examples, the preemption interface1740may transmit at least one legacy preemption indication. In some examples, the preemption interface1740may transmit the preemption indication that is specific to the batch transmissions. The preemption processing component1745may apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. In some examples, the preemption processing component1745may process the batch without processing transmissions transmitted on the portion of the set of resources indicated as preempted, in accordance with the rule for preemption of batches. In some examples, the preemption processing component1745may receive a first portion of the file using resources of the set of resources that precede the portion of the set of resources indicated as preempted, where the second portion of the file on the portion of the set of resource indicated as preempted are not received in accordance with the rule for preemption of batches. In some examples, the preemption processing component1745may process the batch by ignoring the preemption indication, in accordance with the rule for preemption of batches. In some examples, the preemption processing component1745may receive the batch in accordance with the rule for preemption of batches. The transmission power component1750may determine the transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches. In some examples, the transmission power component1750may determine an amount of the transmission power based on a size of the file. FIG.18shows a diagram of a system1800including a device1805that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The device1805may be an example of or include the components of device1505, device1605, or a base station105as described herein. The device1805may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager1810, a network communications manager1815, a transceiver1820, an antenna1825, memory1830, a processor1840, and an inter-station communications manager1845. These components may be in electronic communication via one or more buses (e.g., bus1850). The communications manager1810may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible, transmit, to a UE, a grant for communication of a packet that is one of a set of packets configured to be processed together as a file, identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet, and participate in the communication of the packet on the identified one or more symbols of the slot. The communications manager1810may also transmit a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together, transmit a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate, and participate in the communication based on at least one of the first set of decoding candidates or the second set of decoding candidates. The communications manager1810may also transmit at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication of a batch of transmissions that collectively carry a file having a set of packets and participate in the communication based on the configured grant. The communications manager1810may also identify that a batch of transmissions has been transmitted to a UE or is scheduled to be received from the UE via a set of resources, the batch collectively including a file having a set of packets configured to be processed together, identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted, and apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The communications manager1810may also transmit, to a UE a grant for communication of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together, determine the transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches, and transmit the uplink transmission in accordance with the increased power and the grant. The communications manager1810may also transmit, to a UE a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and transmit the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. The communications manager1810may also transmit, to a UE, a grant for communication of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together and receive the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The network communications manager1815may manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communications manager1815may manage the transfer of data communications for client devices, such as one or more UEs115. The transceiver1820may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver1820may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1820may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas. In some cases, the wireless device may include a single antenna1825. However, in some cases the device may have more than one antenna1825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The memory1830may include RAM, ROM, or a combination thereof. The memory1830may store computer-readable code1835including instructions that, when executed by a processor (e.g., the processor1840) cause the device to perform various functions described herein. In some cases, the memory1830may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. The processor1840may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1840may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into processor1840. The processor1840may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1830) to cause the device1805to perform various functions (e.g., functions or tasks supporting transmission batch scheduling and resource management). The inter-station communications manager1845may manage communications with other base station105, and may include a controller or scheduler for controlling communications with UEs115in cooperation with other base stations105. For example, the inter-station communications manager1845may coordinate scheduling for transmissions to UEs115for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager1845may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between base stations105. The code1835may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications. The code1835may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code1835may not be directly executable by the processor1840but may cause a computer (e.g., when compiled and executed) to perform functions described herein. FIG.19shows a flowchart illustrating a method1900that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method1900may be implemented by a UE115or its components as described herein. For example, the operations of method1900may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At1905, the UE may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible. The operations of1905may be performed according to the methods described herein. In some examples, aspects of the operations of1905may be performed by a transmission direction identifier as described with reference toFIGS.11through14. At1910, the UE may receive a grant for communication, by the UE, of a packet that is one of a set of packets configured to be processed together as a file. The operations of1910may be performed according to the methods described herein. In some examples, aspects of the operations of1910may be performed by a grant receiving interface as described with reference toFIGS.11through14. At1915, the UE may identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet. The operations of1915may be performed according to the methods described herein. In some examples, aspects of the operations of1915may be performed by a symbol identifier as described with reference toFIGS.11through14. At1920, the UE may participate in the communication of the packet on the identified one or more symbols of the slot. The operations of1920may be performed according to the methods described herein. In some examples, aspects of the operations of1920may be performed by a communication interface as described with reference toFIGS.11through14. FIG.20shows a flowchart illustrating a method2000that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2000may be implemented by a UE115or its components as described herein. For example, the operations of method2000may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At2005, the UE may identify a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of2005may be performed according to the methods described herein. In some examples, aspects of the operations of2005may be performed by a batch decoding component as described with reference toFIGS.11through14. At2010, the UE may identify a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate. The operations of2010may be performed according to the methods described herein. In some examples, aspects of the operations of2010may be performed by a decoding component as described with reference toFIGS.11through14. At2015, the UE may participate in the communication by monitoring at least one of the first set of decoding candidates or the second set of decoding candidates. The operations of2015may be performed according to the methods described herein. In some examples, aspects of the operations of2015may be performed by a communication interface as described with reference toFIGS.11through14. FIG.21shows a flowchart illustrating a method2100that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2100may be implemented by a UE115or its components as described herein. For example, the operations of method2100may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At2105, the UE may receive at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication, by the UE, of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of2105may be performed according to the methods described herein. In some examples, aspects of the operations of2105may be performed by a grant receiving interface as described with reference toFIGS.11through14. At2110, the UE may participate in the communication based at least in part of on the configured grant. The operations of2110may be performed according to the methods described herein. In some examples, aspects of the operations of2110may be performed by a communication interface as described with reference toFIGS.11through14. FIG.22shows a flowchart illustrating a method2200that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2200may be implemented by a UE115or its components as described herein. For example, the operations of method2200may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At2205, the UE may identify that a batch of transmissions has been received from a base station or is scheduled to be transmitted to the base station via a set of resources, the batch collectively including a file having a set of packets configured to be processed together. The operations of2205may be performed according to the methods described herein. In some examples, aspects of the operations of2205may be performed by a batch transmission component as described with reference toFIGS.11through14. At2210, the UE may identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted. The operations of2210may be performed according to the methods described herein. In some examples, aspects of the operations of2210may be performed by a resource identification component as described with reference toFIGS.11through14. At2215, the UE may apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The operations of2215may be performed according to the methods described herein. In some examples, aspects of the operations of2215may be performed by a preemption processing component as described with reference toFIGS.11through14. FIG.23shows a flowchart illustrating a method2300that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2300may be implemented by a UE115or its components as described herein. For example, the operations of method2300may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At2305, the UE may receive a grant for communication, by the UE, of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of2305may be performed according to the methods described herein. In some examples, aspects of the operations of2305may be performed by a grant receiving interface as described with reference toFIGS.11through14. At2310, the UE may determine a transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches. The operations of2310may be performed according to the methods described herein. In some examples, aspects of the operations of2310may be performed by a transmission power component as described with reference toFIGS.11through14. At2315, the UE may transmit the uplink transmission in accordance with the transmission power and the grant. The operations of2315may be performed according to the methods described herein. In some examples, aspects of the operations of2315may be performed by a communication interface as described with reference toFIGS.11through14. FIG.24shows a flowchart illustrating a method2400that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2400may be implemented by a UE115or its components as described herein. For example, the operations of method2400may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At2405, the UE may receive a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of2405may be performed according to the methods described herein. In some examples, aspects of the operations of2405may be performed by a grant receiving interface as described with reference toFIGS.11through14. At2410, the UE may receive the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. The operations of2410may be performed according to the methods described herein. In some examples, aspects of the operations of2410may be performed by a communication interface as described with reference toFIGS.11through14. At2415, the UE may decode the downlink transmission in accordance with the combined reference signal. The operations of2415may be performed according to the methods described herein. In some examples, aspects of the operations of2415may be performed by a decoding component as described with reference toFIGS.11through14. FIG.25shows a flowchart illustrating a method2500that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2500may be implemented by a UE115or its components as described herein. For example, the operations of method2500may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At2505, the UE may receive a grant for communication, by the UE, of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of2505may be performed according to the methods described herein. In some examples, aspects of the operations of2505may be performed by a grant receiving interface as described with reference toFIGS.11through14. At2510, the UE may transmit the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The operations of2510may be performed according to the methods described herein. In some examples, aspects of the operations of2510may be performed by a communication interface as described with reference toFIGS.11through14. FIG.26shows a flowchart illustrating a method2600that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2600may be implemented by a base station105or its components as described herein. For example, the operations of method2600may be performed by a communications manager as described with reference toFIGS.15through18. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware. At2605, the base station may identify a transmission direction schedule for a slot, where the transmission direction schedule identifies one or more symbols of the slot as being uplink, downlink, or flexible. The operations of2605may be performed according to the methods described herein. In some examples, aspects of the operations of2605may be performed by a transmission direction identifier as described with reference toFIGS.15through18. At2610, the base station may transmit, to a UE, a grant for communication of a packet that is one of a set of packets configured to be processed together as a file. The operations of2610may be performed according to the methods described herein. In some examples, aspects of the operations of2610may be performed by a grant transmitting interface as described with reference toFIGS.15through18. At2615, the base station may identify, based on at least one of the grant and the transmission direction schedule, one or more symbols of the slot for communication of the packet. The operations of2615may be performed according to the methods described herein. In some examples, aspects of the operations of2615may be performed by a symbol identifier as described with reference toFIGS.15through18. At2620, the base station may participate in the communication of the packet on the identified one or more symbols of the slot. The operations of2620may be performed according to the methods described herein. In some examples, aspects of the operations of2620may be performed by a communication interface as described with reference toFIGS.15through18. FIG.27shows a flowchart illustrating a method2700that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2700may be implemented by a base station105or its components as described herein. For example, the operations of method2700may be performed by a communications manager as described with reference toFIGS.15through18. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware. At2705, the base station may transmit a first set of decoding candidates for communication of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of2705may be performed according to the methods described herein. In some examples, aspects of the operations of2705may be performed by a batch control component as described with reference toFIGS.15through18. At2710, the base station may transmit a second set of decoding candidates for communications not pertaining to files, where the first set of decoding candidates and the second set of decoding candidates differ by at least one decoding candidate. The operations of2710may be performed according to the methods described herein. In some examples, aspects of the operations of2710may be performed by a control component as described with reference toFIGS.15through18. At2715, the base station may participate in the communication based on at least one of the first set of decoding candidates or the second set of decoding candidates. The operations of2715may be performed according to the methods described herein. In some examples, aspects of the operations of2715may be performed by a communication interface as described with reference toFIGS.15through18. FIG.28shows a flowchart illustrating a method2800that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2800may be implemented by a base station105or its components as described herein. For example, the operations of method2800may be performed by a communications manager as described with reference toFIGS.15through18. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware. At2805, the base station may transmit at least one grant as a configured grant via a radio resource control message, the configured grant including a configured grant index indicative of a resource configuration for communication of a batch of transmissions that collectively carry a file having a set of packets. The operations of2805may be performed according to the methods described herein. In some examples, aspects of the operations of2805may be performed by a batch control component as described with reference toFIGS.15through18. At2810, the base station may participate in the communication based on the configured grant. The operations of2810may be performed according to the methods described herein. In some examples, aspects of the operations of2810may be performed by a communication interface as described with reference toFIGS.15through18. FIG.29shows a flowchart illustrating a method2900that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method2900may be implemented by a base station105or its components as described herein. For example, the operations of method2900may be performed by a communications manager as described with reference toFIGS.15through18. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware. At2905, the base station may identify that a batch of transmissions has been transmitted to a UE or is scheduled to be received from the UE via a set of resources, the batch collectively including a file having a set of packets configured to be processed together. The operations of2905may be performed according to the methods described herein. In some examples, aspects of the operations of2905may be performed by a batch control component as described with reference toFIGS.15through18. At2910, the base station may identify, via a preemption indication, that at least a portion of the set of resources allocated for communication of the batch is preempted. The operations of2910may be performed according to the methods described herein. In some examples, aspects of the operations of2910may be performed by a preemption interface as described with reference toFIGS.15through18. At2915, the base station may apply the preemption indication to processing or transmission of the batch in accordance with a rule for preemption of batches. The operations of2915may be performed according to the methods described herein. In some examples, aspects of the operations of2915may be performed by a preemption processing component as described with reference toFIGS.15through18. FIG.30shows a flowchart illustrating a method3000that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method3000may be implemented by a base station105or its components as described herein. For example, the operations of method3000may be performed by a communications manager as described with reference toFIGS.15through18. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware. At3005, the base station may transmit, to a UE a grant for communication of an uplink transmission that is part of batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of3005may be performed according to the methods described herein. In some examples, aspects of the operations of3005may be performed by a grant transmitting interface as described with reference toFIGS.15through18. At3010, the base station may determine the transmission power for transmitting the uplink transmission based on the grant pertaining to transmission of batches. The operations of3010may be performed according to the methods described herein. In some examples, aspects of the operations of3010may be performed by a transmission power component as described with reference toFIGS.15through18. At3015, the base station may transmit the uplink transmission in accordance with the increased power and the grant. The operations of3015may be performed according to the methods described herein. In some examples, aspects of the operations of3015may be performed by a communication interface as described with reference toFIGS.15through18. FIG.31shows a flowchart illustrating a method3100that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method3100may be implemented by a base station105or its components as described herein. For example, the operations of method3100may be performed by a communications manager as described with reference toFIGS.15through18. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware. At3105, the base station may transmit, to a UE a grant for communication of a downlink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of3105may be performed according to the methods described herein. In some examples, aspects of the operations of3105may be performed by a grant transmitting interface as described with reference toFIGS.15through18. At3110, the base station may transmit the downlink transmission in accordance with the grant, where a reference signal corresponding to a first transmission in the batch is combined with a reference signal corresponding to a second transmission in the batch. The operations of3110may be performed according to the methods described herein. In some examples, aspects of the operations of3110may be performed by a communication interface as described with reference toFIGS.15through18. FIG.32shows a flowchart illustrating a method3200that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method3200may be implemented by a base station105or its components as described herein. For example, the operations of method3200may be performed by a communications manager as described with reference toFIGS.15through18. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware. At3205, the base station may transmit, to a UE, a grant for communication of an uplink transmission that is part of a batch of transmissions that collectively carry a file having a set of packets configured to be processed together. The operations of3205may be performed according to the methods described herein. In some examples, aspects of the operations of3205may be performed by a grant transmitting interface as described with reference toFIGS.15through18. At3210, the base station may receive the uplink transmission while maintaining a phase continuity for at least two transmissions within the batch of transmissions based on receiving the grant for communication of the uplink transmission. The operations of3210may be performed according to the methods described herein. In some examples, aspects of the operations of3210may be performed by a communication interface as described with reference toFIGS.15through18. FIG.33shows a flowchart illustrating a method3300that supports transmission batch scheduling and resource management in accordance with aspects of the present disclosure. The operations of method3300may be implemented by a UE115or its components as described herein. For example, the operations of method3300may be performed by a communications manager as described with reference toFIGS.11through14. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware. At3305, the UE may identify a packet that is one of a set of packets configured to be processed together as a file. The operations of3305may be performed according to the methods described herein. In some examples, the operations of3305may be performed by a packet identification component1280as described with reference toFIGS.11through14. At3310, the UE may perform resource management for communicating the packet based on identifying that the packet is one of the set of packets configured to be processed together as the file. The operations of3310may be performed according to the methods described herein. In some examples, the operations of3310may be performed by a resource management component1285as described with reference toFIGS.11through14. At3315, the UE may participate in the communicating of the packet in accordance with the resource management and the packet being one of the set of packets configured to be processed together as the file. The operations of3315may be performed according to the methods described herein. In some examples, the operations of3315may be performed by a communication interface1235as described with reference toFIGS.11through14. It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined. Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” As used herein, the term “and/or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, and/or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label. The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples. The description herein is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein. | 185,074 |
11943763 | DETAILED DESCRIPTION The exemplary wireless communication systems and devices described below employ a wireless communication system, supporting a broadcast service. Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3rdGeneration Partnership Project (3GPP) LTE (Long Term Evolution) wireless access, 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra Mobile Broadband), WiMax, 3GPP NR (New Radio) wireless access for 5G, or some other modulation techniques. In particular, the exemplary wireless communication systems devices described below may be designed to support one or more standards such as the standard offered by a consortium named “3rd Generation Partnership Project” referred to herein as 3GPP, including: 3GPP TS 38.211 V15.7.0, “NR physical channels and modulation”; 3GPP TS 38.213 V16.2.0, “NR Physical layer procedures for control”; 3GPP TS 38.331 v16.0.0, “NR RRC specification”; 3GPP TS 38.214 V16.2.0, “NR Physical layer procedures for data”; RP-193259, “New SID: Study on supporting NR from 52.6 GHz to 71 GHz”. The standards and documents listed above are hereby expressly incorporated by reference in their entirety. FIG.1presents a multiple access wireless communication system in accordance with one or more embodiments of the disclosure. An access network100(AN) includes multiple antenna groups, one including104and106, another including108and110, and an additional including112and114. InFIG.1, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal116(AT) is in communication with antennas112and114, where antennas112and114transmit information to access terminal116over forward link120and receive information from access terminal116over reverse link118. AT122is in communication with antennas106and108, where antennas106and108transmit information to AT122over forward link126and receive information from AT122over reverse link124. In a frequency-division duplexing (FDD) system, communication links118,120,124and126may use different frequencies for communication. For example, forward link120may use a different frequency than that used by reverse link118. Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In the embodiment, antenna groups each may be designed to communicate to access terminals in a sector of the areas covered by access network100. In communication over forward links120and126, the transmitting antennas of access network100may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals116and122. Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage may normally cause less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to its access terminals. An access network (AN) may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an eNodeB (eNB), a Next Generation NodeB (gNB), or some other terminology. An access terminal (AT) may also be called user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology. FIG.2presents an embodiment of a transmitter system210(also known as the access network) and a receiver system250(also known as access terminal (AT) or user equipment (UE)) in a multiple-input and multiple-output (MIMO) system200. At the transmitter system210, traffic data for a number of data streams may be provided from a data source212to a transmit (TX) data processor214. In one embodiment, each data stream is transmitted over a respective transmit antenna. TX data processor214formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data. The coded data for each data stream may be multiplexed with pilot data using orthogonal frequency-division multiplexing (OFDM) techniques. The pilot data may typically be a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream may then be modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), or M-ary quadrature amplitude modulation (M-QAM)) selected for that data stream to provide modulation symbols. The data rate, coding, and/or modulation for each data stream may be determined by instructions performed by processor230. The modulation symbols for data streams are then provided to a TX MIMO processor220, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor220then provides NTmodulation symbol streams to NTtransmitters (TMTR)222athrough222t.In certain embodiments, TX MIMO processor220may apply beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted. Each transmitter222receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and/or upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. NTmodulated signals from transmitters222athrough222tmay then be transmitted from NTantennas224athrough224t,respectively. At receiver system250, the transmitted modulated signals are received by NRantennas252athrough252rand the received signal from each antenna252may be provided to a respective receiver (RCVR)254athrough254r.Each receiver254may condition (e.g., filters, amplifies, and downconverts) a respective received signal, digitize the conditioned signal to provide samples, and/or further process the samples to provide a corresponding “received” symbol stream. An RX data processor260then receives and/or processes the NRreceived symbol streams from NRreceivers254based on a particular receiver processing technique to provide NT“detected” symbol streams. The RX data processor260may then demodulate, deinterleave, and/or decode each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor260may be complementary to that performed by TX MIMO processor220and TX data processor214at transmitter system210. A processor270may periodically determine which pre-coding matrix to use (discussed below). Processor270formulates a reverse link message comprising a matrix index portion and a rank value portion. The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message may then be processed by a TX data processor238, which may also receive traffic data for a number of data streams from a data source236, modulated by a modulator280, conditioned by transmitters254athrough254r,and/or transmitted back to transmitter system210. At transmitter system210, the modulated signals from receiver system250are received by antennas224, conditioned by receivers222, demodulated by a demodulator240, and processed by a RX data processor242to extract the reserve link message transmitted by the receiver system250. Processor230may then determine which pre-coding matrix to use for determining the beamforming weights and may then process the extracted message. FIG.3presents an alternative simplified functional block diagram of a communication device according to one embodiment of the disclosed subject matter. As shown inFIG.3, the communication device300in a wireless communication system can be utilized for realizing the UEs (or ATs)116and122inFIG.1or the base station (or AN)100inFIG.1, and the wireless communications system may be the LTE system or the NR system. The communication device300may include an input device302, an output device304, a control circuit306, a central processing unit (CPU)308, a memory310, a program code312, and a transceiver314. The control circuit306executes the program code312in the memory310through the CPU308, thereby controlling an operation of the communications device300. The communications device300can receive signals input by a user through the input device302, such as a keyboard or keypad, and can output images and sounds through the output device304, such as a monitor or speakers. The transceiver314is used to receive and transmit wireless signals, delivering received signals to the control circuit306, and outputting signals generated by the control circuit306wirelessly. The communication device300in a wireless communication system can also be utilized for realizing the AN100inFIG.1. FIG.4is a simplified block diagram of the program code312shown inFIG.3in accordance with one embodiment of the disclosed subject matter. In this embodiment, the program code312includes an application layer400, a Layer 3 portion402, and a Layer 2 portion404, and is coupled to a Layer 1 portion406. The Layer 3 portion402may perform radio resource control. The Layer 2 portion404may perform link control. The Layer 1 portion406may perform and/or implement physical connections. One or more frame structures associated with Radio Access Technology (RAT) and/or New RAT (NR) (associated with 5G) may accommodate various requirements associated with time resources and/or frequency resources (e.g., ultra-low latency (e.g., ˜0.5 ms)) to delay-tolerant traffic for Machine Type Communication (MTC), from a high peak rate for enhanced Mobile Broadband (eMBB) to a very low data rate for MTC. Numerology may be adjusted such that reducing a symbol number of a Transmission Time Interval (TTI) is not the only way to change TTI length. In an example associated with LTE numerology, 14 Orthogonal Frequency Division Multiplexing (OFDM) symbols may be associated with 1 ms and/or a subcarrier spacing of 15 KHz. When the subcarrier spacing increases to 30 KHz, where a Fast Fourier Transform (FFT) size and/or a cyclic prefix (CP) structure may not change, there may be 28 OFDM symbols in 1 ms and/or the TTI may become 0.5 ms if the number of OFDM symbol in a TTI is kept the same. Accordingly, a design between different TTI lengths may be kept common, with scalability performed on the subcarrier spacing. One or more of FFT size, Physical Resource Block (PRB) definition/number, CP design, supportable system bandwidth, subcarrier spacing selection, etc. may be configured in association with subcarrier spacing selection. As NR is associated with a larger system bandwidth and/or a larger coherence bandwidth, inclusion of a larger subcarrier spacing may be beneficial. More details of NR frame structure, channel and/or numerology design are provided in 3GPP TS 38.211 V15.7.0. Notably, FIG. 4.3.1-1 of Section 4.3.1 of 3GPP TS 38.211 V15.7.0, entitled “Uplink-downlink timing relation”, is reproduced herein asFIG.5. One or more parts of 3GPP TS 38.211 V15.7.0 are quoted below: 4 Frame Structure and Physical Resources 4.1 General Throughout this specification, unless otherwise noted, the size of various fields in the time domain is expressed in time units Tc=1/(Δƒfmax·Nf) where Δƒmax=480·103Hz and Nf=4096. The constant κ=Ts/Tc=64 where Ts=1/(Δƒref·Nf,ref), Δƒref=15·103Hz and Nf,ref=2048. 4.2 Numerologies Multiple OFDM numerologies are supported as given by Table 4.2-1 where μ and the cyclic prefix for a bandwidth part are obtained from the higher-layer parameter subcarrierSpacing and cyclicPrefix, respectively. TABLE 4.2-1Supported transmission numerologies.μΔƒ = 2μ· 15[kHz]Cyclic prefix015Normal130Normal260Normal,Extended3120Normal4240Normal 4.3 Frame Structure 4.3.1 Frames and Subframes Downlink and uplink transmissions are organized into frames with Tf=(ΔƒmaxNf/100)·TC=10 ms duration, each consisting of ten subframes of Tsf=(ΔƒmaxNf/1000)·TC=1 ms duration. The number of consecutive OFDM symbols per subframe is Nsymbsubframe,μ=NsymbslotNslotsubframe,μ. Each frame is divided into two equally-sized half-frames of five subframes each with half-frame 0 consisting of subframes 0-4 and half-frame 1 consisting of subframes 5-9. There is one set of frames in the uplink and one set of frames in the downlink on a carrier. Uplink frame number i for transmission from the UE shall start TTA=(NTA+NTA,offset)TCbefore the start of the corresponding downlink frame at the UE where NTA,offsetis given by [5, TS 38.213]. FIG. 4.3.1-1: Uplink-Downlink Timing Relation. 4.3.2 Slots For subcarrier spacing configuration μ, slots are numbered nsμ∈{0, . . . , Nslotsubframe,μ−1} in increasing order within a subframe and ns,fμ∈{0, . . . , Nslotframe,μ−1} in increasing order within a frame. There are Nsymbslotconsecutive OFDM symbols in a slot where Nsymbslotdepends on the cyclic prefix as given by Tables 4.3.2-1 and 4.3.2-2. The start of slot nsμin a subframe is aligned in time with the start of OFDM symbol nsμNsymbslotin the same subframe. OFDM symbols in a slot can be classified as ‘downlink’, ‘flexible’, or ‘uplink’. Signaling of slot formats is described in subclause 11.1 of [5, TS 38.213]. In a slot in a downlink frame, the UE shall assume that downlink transmissions only occur in ‘downlink’ or ‘flexible’ symbols. In a slot in an uplink frame, the UE shall only transmit in ‘uplink’ or ‘flexible’ symbols. A UE not capable of full-duplex communication and not supporting simultaneous transmission and reception as defined by paremeter simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA or simultaneousRxTxSUL [10, TS 38.306] among all cells within a group of cells is not expected to transmit in the uplink in one cell within the group of cells earlier than NRx-TxTcafter the end of the last received downlink symbol in the same or different cell within the group of cells where NRx-Txis given by Table 4.3.2-3. A UE not capable of full-duplex communication and not supporting simultaneous transmission and reception as defined by parameter simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA or simultaneousRxTxSUL [10, TS 38.306] among all cells within a group of cells is not expected to receive in the downlink in one cell within the group of cells earlier than NTx-RxTcafter the end of the last transmitted uplink symbol in the same or different cell within the group of cells where NTx-Rxis given by Table 4.3.2-3. A UE not capable of full-duplex communication is not expected to transmit in the uplink earlier than NRx-TxTcafter the end of the last received downlink symbol in the same cell where NRx-Txis given by Table 4.3.2-3. A UE not capable of full-duplex communication is not expected to receive in the downlink earlier than NTx-RxTcafter the end of the last transmitted uplink symbol in the same cell where NTx-Rxis given by Table 4.3.2-3. TABLE 4.3.2-1Number of OFDM symbols per slot, slots per frame,and slots per subframe for normal cyclic prefix.μNsymbslotNslotframe, μNslotsubframe, μ01410111420221440431480841416016 TABLE 4.3.2-2Number of OFDM symbols per slot, slots per frame,and slots per subframe for extended cyclic prefix.μNsymbslotNslotframe, μNslotsubframe, μ212404 TABLE 4.3.2-3Transition time NRx-Txand NTx-RxTransition timeFR1FR2NTx-Rx2560013792NRx-Tx2560013792 4.4 Physical Resources 4.4.2 Resource Grid For each numerology and carrier, a resource grid of Ngrid,xsize,μNscRBsubcarriers and Nsymbsubframe,μOFDM symbols is defined, starting at common resource block Ngridstart,μindicated by higher-layer signalling. There is one set of resource grids per transmission direction (uplink or downlink) with the subscript x set to DL and UL for downlink and uplink, respectively. When there is no risk for confusion, the subscript x may be dropped. There is one resource grid for a given antenna port p, subcarrier spacing configuration μ, and transmission direction (downlink or uplink). The carrier bandwidth Ngridsize,μfor subcarrier spacing configuration μ is given by the higher-layer parameter carrierBandwidth in the SCS-SpecificCarrier IE. The starting position Ngridstart,μfor subcarrier spacing configuration μ is given by the higher-layer parameter offsetToCarrier in the SCS-SpecificCarrier IE. The frequency location of a subcarrier refers to the center frequency of that subcarrier. For the downlink, the higher-layer parameter txDirectCurrentLocation in the SCS-SpecificCarrier IE indicates the location of the transmitter DC subcarrier in the downlink for each of the numerologies configured in the downlink Values in the range 0-3299 represent the number of the DC subcarrier and the value 3300 indicates that the DC subcarrier is located outside the resource grid. For the uplink, the higher-layer parameter txDirectCurrentLocation in the UplinkTxDirectCurrentBWP IE indicates the location of the transmitter DC subcarrier in the uplink for each of the configured bandwidth parts, including whether the DC subcarrier location is offset by 7.5 kHz relative to the center of the indicated subcarrier or not. Values in the range 0-299 represent the number of the DC subcarrier, the value 3300 indicates that the DC subcarrier is located outside the resource grid, and the value 3301 indicates that the position of the DC subcarrier in the uplink is undetermined. 4.4.3 Resource Elements Each element in the resource grid for antenna port p and subcarrier spacing configuration μ is called a resource element and is uniquely identified by (k, l)p,μwhere k is the index in the frequency domain and l refers to the symbol position in the time domain relative to some reference point. Resource element (k,l)p,μcorresponds to a physical resource and the complex value αk,l(p,μ). When there is no risk for confusion, or no particular antenna port or subcarrier spacing is specified, the indices p and μ may be dropped, resulting in αk,l(p)or αk,l. 4.4.4 Resource Blocks 4.4.4.3 Common Resource Blocks Common resource blocks are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration μ. The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration μ coincides with ‘point A’. The relation between the common resource block number nCRBμin the frequency domain and resource elements (k,l) for subcarrier spacing configuration μ is given by nCRBμ=⌊kNscRB⌋ where k is defined relative to point A such that k=0 corresponds to the subcarrier centered around point A. 4.4.4.4 Physical Resource Blocks Physical resource blocks for subcarrier configuration μ are defined within a bandwidth part and numbered from 0 to NBWP,isize,μ−1 where i is the number of the bandwidth part. The relation between the physical resource block nPRBμin bandwidth part i and the common resource block nCRBμis given by nCRBμ=nPRBμ+NBWP,istart,μ where NBWP,istart,μis the common resource block where bandwidth part starts relative to common resource block 0. When there is no risk for confusion the index μ may be dropped. 4.4.4.5 Virtual Resource Blocks Virtual resource blocks are defined within a bandwidth part and numbered from 0 to NBWP,isize−1 where i is the number of the bandwidth part. 4.4.5 Bandwidth Part A bandwidth part is a subset of contiguous common resource blocks defined in subclause 4.4.4.3 for a given numerology μiin bandwidth part i on a given carrier. The starting position NBWP,istart,μand the number of resource blocks NBWP,isize,μin a bandwidth part shall fulfil Ngrid,xstart,μ≤NBWP,istart,μ<Ngrid,xstart,μ+Ngrid,xsize,μand Ngrid,xstart,μ<NBWP,istart,μ+NBWP,isize,μ≤Ngrid,xstart,μ+Ngrid,xsize,μ, respectively. Configuration of a bandwidth part is described in clause 12 of [5, TS 38.213]. A UE can be configured with up to four bandwidth parts in the downlink with a single downlink bandwidth part being active at a given time. The UE is not expected to receive PDSCH, PDCCH, or CSI-RS (except for RRM) outside an active bandwidth part. A UE can be configured with up to four bandwidth parts in the uplink with a single uplink bandwidth part being active at a given time. If a UE is configured with a supplementary uplink, the UE can in addition be configured with up to four bandwidth parts in the supplementary uplink with a single supplementary uplink bandwidth part being active at a given time. The UE shall not transmit PUSCH or PUCCH outside an active bandwidth part. For an active cell, the UE shall not transmit SRS outside an active bandwidth part. Unless otherwise noted, the description in this specification applies to each of the bandwidth parts. When there is no risk of confusion, the index μ may be dropped from NBWP,istart,μ, NBWP,isize,μ, Ngrid,xstart,μ, and Ngrid,xsize,μ. A bandwidth part has a frequency location (e.g., at least one of a starting position in frequency domain, a starting resource block, etc.) and a bandwidth. When a bandwidth part (of a serving cell, for example) is active, the UE performs transmission (if the bandwidth part is an uplink bandwidth part, for example) and/or reception (if the bandwidth part is a downlink bandwidth part, for example) within frequency resources of the bandwidth part (e.g., the frequency resources of the bandwidth part may be determined based on the frequency location and/or the bandwidth of the bandwidth part). In some examples, a bandwidth of a bandwidth part is up to 275 PRBs based on subcarrier spacing of the bandwidth part. A bandwidth part of a UE may be adapted and/or switched (e.g., an active bandwidth part of a UE may be switched from a first bandwidth part to a second bandwidth part). For example, a UE may be configured with multiple bandwidth parts. In some examples a bandwidth part (e.g., one bandwidth part) of the multiple bandwidth parts may be activated and/or be active at a time (e.g., more than one bandwidth part of the multiple bandwidth parts may not be activated and/or active at a time). When a first bandwidth part is active, the UE may activate a second bandwidth part. (e.g., and deactivate the second bandwidth part) to achieve bandwidth part adaptation, bandwidth part switch and/or bandwidth part change. There are various ways to change active bandwidth part (e.g., an active bandwidth part may be changed via at least one of Radio Resource Control (RRC), downlink control information (DCI), a timer, a random access procedure, etc.). More details of bandwidth part may be found in 3GPP TS 38.213 V16.2.0 and 3GPP TS 38.331 v16.0.0, parts of which are quoted below: One or more parts of 3GPP TS 38.213 V16.2.0 are quoted below: 12 Bandwidth Part Operation A UE configured for operation in bandwidth parts (BWPs) of a serving cell, is configured by higher layers for the serving cell a set of at most four bandwidth parts (BWPs) for receptions by the UE (DL BWP set) in a DL bandwidth by parameter BWP-Downlink or by parameter initialDownlinkBWP with a set of parameters configured by BWP-DownlinkCommon and BWP-DownlinkDedicated, and a set of at most four BWPs for transmissions by the UE (UL BWP set) in an UL bandwidth by parameter BWP-Uplink or by parameter initialUplinkBWP with a set of parameters configured by BWP-UplinkCommon and BWP-UplinkDedicated. If a UE is not provided initialDownlinkBWP, an initial DL BWP is defined by a location and number of contiguous PRBs, starting from a PRB with the lowest index and ending at a PRB with the highest index among PRBs of a CORESET for Type0-PDCCH CSS set, and a SCS and a cyclic prefix for PDCCH reception in the CORESET for Type0-PDCCH CSS set; otherwise, the initial DL BWP is provided by initialDownlinkBWP. For operation on the primary cell or on a secondary cell, a UE is provided an initial UL BWP by initialUplinkBWP. If the UE is configured with a supplementary UL carrier, the UE can be provided an initial UL BWP on the supplementary UL carrier by initialUplinkBWP. If a UE has dedicated BWP configuration, the UE can be provided by firstActiveDownlinkBWP-Id a first active DL BWP for receptions and by firstActiveUplinkBWP-Id a first active UL BWP for transmissions on a carrier of the primary cell. For each DL BWP or UL BWP in a set of DL BWPs or UL BWPs, respectively, the UE is provided the following parameters for the serving cell as defined in [4, TS 38.211] or [6, TS 38.214]:a SCS by subcarrierSpacinga cyclic prefix by cyclicPrefixa common RB NBWPstart=Ocarrier+RBstartand a number of contiguous RBs NBWPsize=LRBprovided by locationAndBandwidth that indicates an offset RBstartand a length LRBas RIV according to [6, TS 38.214], setting NBWPsize=275, and a value Ocarrierprovided by offsetTo Carrier for the subcarrierSpacingan index in the set of DL BWPs or UL BWPs by respective BWP-Ida set of BWP-common and a set of BWP-dedicated parameters by BWP-DownlinkCommon and BWP-DownlinkDedicated for the DL BWP, or BWP-UplinkCommon and BWP-UplinkDedicated for the UL BWP [12, TS 38.331] For unpaired spectrum operation, a DL BWP from the set of configured DL BWPs with index provided by BWP-Id is linked with an UL BWP from the set of configured UL BWPs with index provided by BWP-Id when the DL BWP index and the UL BWP index are same. For unpaired spectrum operation, a UE does not expect to receive a configuration where the center frequency for a DL BWP is different than the center frequency for an UL BWP when the BWP-Id of the DL BWP is same as the BWP-Id of the UL BWP. For each DL BWP in a set of DL BWPs of the PCell, or of the PUCCH-SCell, a UE can be configured CORESETs for every type of CSS sets and for USS as described in Clause 10.1. The UE does not expect to be configured without a CSS set on the PCell, or on the PUCCH-SCell, of the MCG in the active DL BWP. If a UE is provided controlResourceSetZero and searchSpaceZero in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon, the UE determines a CORESET for a search space set from controlResourcesetZero as described in Clause 13 and for Tables 13-1 through 13-10, and determines corresponding PDCCH monitoring occasions as described in Clause 13 and for Tables 13-11 through 13-15. If the active DL BWP is not the initial DL BWP, the UE determines PDCCH monitoring occasions for the search space set only if the CORESET bandwidth is within the active DL BWP and the active DL BWP has same SCS configuration and same cyclic prefix as the initial DL BWP. For each UL BWP in a set of UL BWPs of the PCell or of the PUCCH-SCell, the UE is configured resource sets for PUCCH transmissions as described in Clause 9.2.1. A UE receives PDCCH and PDSCH in a DL BWP according to a configured SCS and CP length for the DL BWP. A UE transmits PUCCH and PUSCH in an UL BWP according to a configured SCS and CP length for the UL BWP. One or more parts of 3GPP TS 38.331 v16.0.0 are quoted below: BWP The IE BWP is used to configure generic parameters of a bandwidth part as defined in TS 38.211 [16], clause 4.5, and TS 38.213 [13], clause 12. For each serving cell the network configures at least an initial downlink bandwidth part and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) initial uplink bandwidth parts. Furthermore, the network may configure additional uplink and downlink bandwidth parts for a serving cell. The uplink and downlink bandwidth part configurations are divided into common and dedicated parameters. BWP information element-- ASN1START-- TAG-BWP-STARTBWP ::=SEQUENCE {locationAndBandwidthINTEGER (0..37949),subcarrierSpacingSubcarrierSpacing,cyclicPrefixENUMERATED { extended }OPTIONAL -- Need R}-- TAG-BWP-STOP-- ASN1STOP BWP field descriptionscyclicPrefixIndicates whether to use the extended cyclic prefix for this bandwidth part.If not set, the UE uses the normal cyclic prefix. Normal CP is supportedfor all subcarrier spacings and slot formats. Extended CP is supported onlyfor 60 kHz subcarrier spacing. (see TS 38.211 [16], clause 4.2)locationAndBandwidthFrequency domain location and bandwidth of this bandwidth part. Thevalue of the field shall be interpreted as resource indicator value (RIV) asdefined TS 38.214 [19] with assumptions as described in TS 38.213 [13],clause 12, i.e. setting NBWIsize= 275. The first PRB is a PRB determinedby subcarrierSpacing of this BWP and offset ToCarrier (configured inSCS-SpecificCarrier contained within FrequencyInfoDL/FrequencyInfoUL/FrequencyInfoUL-SIB/FrequencyInfoDL-SIB withinServingCellConfigCommon/ServingCellConfigCommonSIB)corresponding to this subcarrier spacing. In case of TDD, a BWP-pair (ULBWP and DL BWP with the same bwp-Id) must have the same centerfrequency (see TS 38.213 [13], clause 12)subcarrierSpacingSubcarrier spacing to be used in this BWP for all channels and referencesignals unless explicitly configured elsewhere. Corresponds to subcarrierspacing according to TS 38.211 [16], table 4.2-1. The value kHz15corresponds to μ = 0, value kHz30 corresponds to μ = 1, and so on. Onlythe values 15 kHz, 30 kHz, or 60 kHz (FR1), and 60 kHz or 120 kHz(FR2) are applicable. For the initial DL BWP this field has the same valueas the field subCarrierSpacingCommon in MIB of the same serving cell. <. . . >SCS-SpecificCarrier The IE SCS-SpecificCarrier provides parameters determining the location and width of the actual carrier or the carrier bandwidth. It is defined specifically for a numerology (subcarrier spacing (SCS)) and in relation (frequency offset) to Point A. SCS-SpecificCarrier information element-- ASN1START-- TAG-SCS-SPECIFICCARRIER-STARTSCS-SpecificCarrier ::=SEQUENCE {offsetToCarrierINTEGER (0 . . 2199),subcarrierSpacingSubcarrierSpacing,carrierBandwidthINTEGER(1..maxNrofPhysicalResourceBlocks),...,[ [txDirectCurrentLocationINTEGER (0..4095)OPTIONAL -- Need S] ]}-- TAG-SCS-SPECIFICCARRIER-STOP-- ASN1STOP SCS-SpecificCarrier field descriptionscarrierBandwidthWidth of this carrier in number of PRBs (using the subcarrierSpacingdefined for this carrier) (see TS 38.211 [16], clause 4.4.2).offsetToCarrierOffset in frequency domain between Point A (lowest subcarrier ofcommon RB 0) and the lowest usable subcarrier on this carrier in numberof PRBs (using the subcarrierSpacing defined for this carrier). Themaximum value corresponds to 275*8-1. See TS 38.211 [16], clause 4.4.2.txDirectCurrentLocationIndicates the downlink Tx Direct Current location for the carrier. A valuein the range 0 . . . 3299 indicates the subcarrier index within the carrier.The values in the value range 3301 . . . 4095 are reserved and ignored bythe UE. If this field is absent for downlink withinServingCellConfigCommon and ServingCellConfigCommonSIB, the UEassumes the default value of 3300 (i.e. “Outside the carrier”). (see TS38.211 [16], clause 4.4.2). Network does not configure this field viaServingCellConfig or for uplink carriers.subcarrierSpacingSubcarrier spacing of this carrier. It is used to convert the offsetToCarrierinto an actual frequency. Only the values 15 kHz, 30 kHz or 60 kHz(FR1), and 60 kHz or 120 kHz (FR2) are applicable. Resource allocation in frequency domain for a data channel (e.g., Physical Downlink Shared Channel (PDSCH) and/or Physical Uplink Shared Channel (PUSCH)) may be performed via a field (e.g., an information field) carried on downlink control information (DCI). DCI may be carried on a PDCCH scheduling the data channel. A bit map and/or a resource indicator value (RIV) may be used to indicate one or more resources within a bandwidth of a bandwidth part (e.g., bandwidth portion). A bit map may comprise a plurality of bits and/or indicate one or more resources allocated for a UE. For example, each bit of the bit map may be associated with a resources unit (e.g., one resource unit), such as a physical resources block (PRB) (e.g., one PRB) and/or a resource block group (e.g., one RBG). In some examples, a bit of the bit map having a bit value of “1” may indicate that an associated resource unit (e.g., a PRB and/or RBG associated with the bit) is allocated for the UE. For example, the bit map comprising “1001 . . . ” may indicate that a first resource unit (e.g., initial resource unit) is allocated to the UE, a second resource unit following (e.g., directly following) the first resource unit is not allocated to the UE, a third resource unit following (e.g., directly following) the second resource unit is not allocated to the UE, a fourth resource unit following (e.g., directly following) the third resource unit is allocated to the UE, etc. A RIV may indicate a set of contiguous resources allocated for the UE. A UE may derive, from the RIV, a starting position and a length (in units of resource units, for example) of allocated resources (e.g., resources allocated to the UE). For example, if the starting position is 3 and the length is 5, the resources allocated to the UE are resource units 3˜7. More details of resource allocation are provided in 3GPP TS 38.214 V16.2.0, one or more parts of which are quoted below: 5.1.2.2 Resource Allocation in Frequency Domain Two downlink resource allocation schemes, type 0 and type 1, are supported. The UE shall assume that when the scheduling grant is received with DCI format 1_0, then downlink resource allocation type 1 is used. 5.1.2.2.1 Downlink Resource Allocation Type 0 In downlink resource allocation of type 0, the resource block assignment information includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual resource blocks defined by higher layer parameter rbg-Size configured by PDSCH-Config and the size of the bandwidth part as defined in Table 5.1.2.2.1-1. TABLE 5.1.2.2.1-1Nominal RBG size P• Bandwidth Part Size• Configuration 1• Configuration 21-362437-724873-144816145-2751616 The total number of RBGs (NRBG) for a downlink bandwidth part i of size NBWPsizeRPRBs is given by NRBG=┌(NBWP,isize+(NBWP,istartmodP))/P┐, wherethe size of the first RBG is RBG0size=P−NBWP,istartmodP,the size of last RBG is RBGlastsize=(NBWP,istart+NBWP,isize)modP if (NBWP,istart+NBWP,isize)modP>0 and P otherwise,the size of all other RBGs is P. The bitmap is of size NRBGbits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be indexed in the order of increasing frequency and starting at the lowest frequency of the bandwidth part. The order of RBG bitmap is such that RBG 0 to RBGNRBG−1are mapped from MSB to LSB. The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise. 5.1.2.2.2 Downlink Resource Allocation Type 1 In downlink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set of contiguously allocated non-interleaved or interleaved virtual resource blocks within the active bandwidth part of size NBWPsizePRBs except for the case when DCI format 1_0 is decoded in any common search space in which case the size of CORESET 0 shall be used if CORESET 0 is configured for the cell and the size of initial DL bandwidth part shall be used if CORESET 0 is not configured for the cell. A downlink type 1 resource allocation field consists of a resource indication value (RIV) corresponding to a starting virtual resource block (RBstart) and a length in terms of contiguously allocated resource blocks LRBs. The resource indication value is defined byif (LRBs−1)≤└NBWPsize/2┘ then RIV=NBWPsize(LRBs−1)+RBstart else RIV=NBWPsize(NBWPsize−LRBs+1)+(NBWPsize−1−RBstart) where LRBs≥1 and shall not exceed NBWPsize−RBstart. When the DCI size for DCI format 1_0 in USS is derived from the size of DCI format 1_0 in CSS but applied to an active BWP with size of NBWPactive, a downlink type 1 resource block assignment field consists of a resource indication value (RIV) corresponding to a starting resource block RBstart=0, K, 2·K . . . , (NBWPinitial−1)·K and a length in terms of virtually contiguously allocated resource blocks LRBs=K, 2, K , . . . , NBWPinitial·K , where NBWPinitialis given bythe size of CORESET 0 if CORESET 0 is configured for the cell;the size of initial DL bandwidth part if CORESET 0 is not configured for the cell. The resource indication value is defined by:if (L′RBs−1)≤└NBWPinitial/2┘ then RIV=NBWPinitial(L′RBs−1)+RB′start else RIV=NBWPinitial(NBWPinitial−L′RBs+1)+(NBWPinitial−1−RB′start) where L′RBs=LRBs/K, RB′start=RBstart/K and where L′RBsshall not exceed NBWPinitial−RB′start. If NBWPactive>NBWPinitial, K is the maximum value from set {1, 2, 4, 8} which satisfies K≤└NBWPactive/NBWPinitial┘; otherwise K=1. When the scheduling grant is received with DCI format 1_2, a downlink type 1 resource allocation field consists of a resource indication value (RIV) corresponding to a starting resource block group RBGstart=0, 1, . . . , NRBG−1 and a length in terms of virtually contiguously allocated resource block groups LRBGs=1, . . . , NRBG, where the resource block groups are defined as in 5.1.2.2.1 with P defined by ResourceAllocationType1-granularity-ForDCIFormat1_2 if the UE is configured with higher layer parameter ResourceAllocationType1-granularity-ForDCIFormat1_2, and P=1 otherwise. The resource indication value is defined byif (LRBG−1)≤└NRBG/2┘ then RIV=NRBG(LRBGs−1)+RBGstart else RIV=NRBG(NRBG−LRBGs+1)+(NRBG−1−RBGstart) where LRBGs≥1 and shall not exceed NRBG−RBGstart. One or more resource blocks assigned by a DCI via frequency domain resource allocation may be one or more virtual resource blocks (VRBs). One or more virtual resource blocks may be mapped to one or more physical resource blocks (PRBs). One or more transmissions for a data channel in the frequency domain may be performed based on the one or more PRBs. Two different types of mapping may be supported (such as to increase diversity of allocated frequency resources). One type of mapping is non-interleaved mapping (e.g., localized mapping). For non-interleaved mapping (e.g., localized mapping), a VRB is mapped to a PRB with a same index (e.g., the VRB and the PRB to which the VRB is mapped have the same index). One or more frequency resources occupied by a data channel are determined based on (e.g., only based on) a resource allocation field in DCI (e.g., a field, in the DCI, indicative of one or more allocated resources). Accordingly, under non-interleaved mapping (e.g., localized mapping), if allocated VRBs are contiguous in the frequency domain, the allocated VRBs would be mapped to contiguous PRBs (since the same index is used, for example). A second type of mapping is interleaved mapping (e.g., distributed mapping). For interleaved mapping (e.g., distributed mapping), a VRB with a first index may be mapped to a PRB with a second index different than the first index. There may be one or more mapping rules (e.g., one or more specified mapping rules) for interleaved mapping (e.g., distributed mapping). VRB indices may be interleaved and/or shuffled into (diverse, for example) PRB indices based on the interleaved mapping (e.g., distributed mapping). If allocated VRBs are contiguous in frequency domain, the allocated VRBs may be mapped to non-contiguous PRBs under interleaved mapping (e.g., distributed mapping), since, for example, the indices are interleaved and/or shuffled. Frequency hopping may be applied for PUSCH to achieve interleaved mapping (e.g., distributed mapping). More details for mapping may be found in 3GPP TS 38.211 V15.7.0, one or more parts of which are quoted below: 7.3.1.5 Mapping to Virtual Resource Blocks The UE shall, for each of the antenna ports used for transmission of the physical channel, assume the block of complex-valued symbols y(p)(0), . . . , y(p)(Msymbap−1) conform to the downlink power allocation specified in [6, TS 38.214] and are mapped in sequence starting with y(p)(0) to resource elements (k′,l)p,μin the virtual resource blocks assigned for transmission which meet all of the following criteria:they are in the virtual resource blocks assigned for transmission;the corresponding physical resource blocks are declared as available for PDSCH according to clause 5.1.4 of [6, TS 38.214];the corresponding resource elements in the corresponding physical resource blocks arenot used for transmission of the associated DM-RS or DM-RS intended for other co-scheduled UEs as described in clause 7.4.1.1.2;not used for non-zero-power CSI-RS according to clause 7.4.1.5 if the corresponding physical resource blocks are for PDSCH scheduled by PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or PDSCH with SPS, except if the non-zero-power CSI-RS is a CSI-RS configured by the higher-layer parameter CSI-RS-Resource-Mobility in the MeasObjectNR IE or except if the non-zero-power CSI-RS is an aperiodic non-zero-power CSI-RS resource;not used for PT-RS according to clause 7.4.1.2;not declared as ‘not available for PDSCH according to clause 5.1.4 of [6, TS 38.214]. The mapping to resource elements (k′,l)p,μallocated for PDSCH according to [6, TS 38.214] and not reserved for other purposes shall be in increasing order of first the index k′ over the assigned virtual resource blocks, where k′=0 is the first subcarrier in the lowest-numbered virtual resource block assigned for transmission, and then the index l. 7.3.1.6 Mapping from Virtual to Physical Resource Blocks The UE shall assume the virtual resource blocks are mapped to physical resource blocks according to the indicated mapping scheme, non-interleaved or interleaved mapping. If no mapping scheme is indicated, the UE shall assume non-interleaved mapping. For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, except for PDSCH transmissions scheduled with DCI format 1_0 in a common search space in which case virtual resource block n is mapped to physical resource block n+NstartCORESETwhere NstartCORESETis the lowest-numbered physical resource block in the control resource set where the corresponding DCI was received. For interleaved VRB-to-PRB mapping, the mapping process is defined by:Resource block bundles are defined asfor PDSCH transmissions scheduled with DCI format 1_0 with the CRC scrambled by SI-RNTI in Type0-PDCCH common search space in CORESET 0, the set of NBWP,initsizeresource blocks in CORESET 0 are divided into Nbundle=┌NBWP,initsize/L┘ resource-block bundles in increasing order of the resource-block number and bundle number where L=2 is the bundle size and NBWP,initsizeis the size of CORESET 0.resource block bundle Nbundle−1 consists of NBWP,initsizemod L resource blocks if NBWP,initsizemod L>0 and L resource blocks otherwise,all other resource block bundles consists of L resource blocks.for PDSCH transmissions scheduled with DCI format 1_0 in any common search space in bandwidth part i with starting position NBWP,istart, other than Type0-PDCCH common search space in CORESET 0, the set of NBWP,initsizevirtual resource blocks {0, 1, . . . , NBWP,initsize−1}, where NBWP,initsizeis the size of CORESET 0 if CORESET 0 is configured for the cell and the size of initial downlink bandwidth part if CORESET 0 is not configured for the cell, are divided into Nbundlevirtual resource-block bundles in increasing order of the virtual resource-block number and virtual bundle number and the set of NBWP,initsizephysical resource blocks {NstartCORESET, NstartCORESET+1, . . . , NstartCORESET+NBWP,unitsize−1} are divided into Nbundlephysical resource-block bundles in increasing order of the physical resource-block number and physical bundle number, where Nbundle=┌(NBWP,unitsize+(NBWP,istart+NstartCORESET)mod L)/L┐, L=2 is the bundle size, and NstartCORESETis the lowest-numbered physical resource block in the control resource set where the corresponding DCI was received.resource block bundle 0 consists of L−((NBWP,istart+NstartCORESET)mod L) resource blocks,resource block bundle Nbundle−1 consists of (NBWP,initsize+NBWP,istart+NstartCORESET) mod L resource blocks if (NBWP,initsize+NBWP,istart+NstartCORESET) mod L>0 and L resource blocks otherwise,all other resource block bundles consists of L resource blocks.for all other PDSCH transmissions, the set of NBWP,isizeresource blocks in bandwidth part i with starting position NBWP,istartare divided into Nbundle=┌(NBWP,isize+(NBWP,istartmod Li))/Li┐ resource-block bundles in increasing order of the resource-block number and bundle number where Liis the bundle size for bandwidth part i provided by the higher-layer parameter vrb-ToPRB-Interleaver andresource block bundle 0 consists of Li−(N(BWP,istartmod Li) resource blocks,resource block bundle Nbundle−1 consists of (NBWP,istart+NBWP,isize)mod Liresource blocks if (NBWP,istart+NBWP,isize)mod Li>0 and Liresource blocks otherwise,all other resource block bundles consists of Liresource blocks.Virtual resource blocks in the interval j ∈ {0,1, . . . , Nbundle−1} are mapped to physical resource blocks according tovirtual resource block bundle Nbundle−1 is mapped to physical resource block bundle Nbundle−1virtual resource block bundle j ∈ {0,1, . . . , Nbundle−2} is mapped to physical resource block bundle ƒ(j) where ƒ(j)=rC+c j=cR+r r=0,1, . . . ,R−1 c=0,1, . . . ,C−1 R=2 C=└Nbundle/R┘ One or more parts of 3GPP TS 38.214 V16.2.0 are quoted below: 6.3 UE PUSCH Frequency Hopping Procedure 6.3.1 Frequency Hopping for PUSCH Repetition Type A For PUSCH repetition Type A (as determined according to procedures defined in Clause 6.1.2.1 for scheduled PUSCH, or Clause 6.1.2.3 for configured PUSCH), a UE is configured for frequency hopping by the higher layer parameter frequencyHopping-ForDCIFormat0_2 in pusch-Config for PUSCH transmission scheduled by DCI format 0_2, and by frequencyHopping provided in pusch-Config for PUSCH transmission scheduled by a DCI format other than 0_2, and by frequencyHopping provided in configuredGrantConfig for configured PUSCH transmission. One of two frequency hopping modes can be configured:Intra-slot frequency hopping, applicable to single slot and multi-slot PUSCH transmission.Inter-slot frequency hopping, applicable to multi-slot PUSCH transmission. In case of resource allocation type 2, the UE transmits PUSCH without frequency hopping. In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the UE may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format or in a random access response UL grant is set to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher layer parameter frequencyHoppingOffset is provided, otherwise no PUSCH frequency hopping is performed. When frequency hopping is enabled for PUSCH, the RE mapping is defined in clause 6.3.1.6 of [4, TS 38.211]. For a PUSCH scheduled by RAR UL grant, fallbackRAR UL grant, or by DCI format 0_0 with CRC scrambled by TC-RNTI, frequency offsets are obtained as described in clause 8.3 of [6, TS 38.213]. For a PUSCH scheduled by DCI format 0_0/0_1 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0_0/0_1 and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-Config. For a PUSCH scheduled by DCI format 0_2 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0_2 and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists-ForDCIFormat0_2 in pusch-Config.When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in the UL grant.When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets is indicated in the UL grant. For PUSCH based on a Type1configured UL grant the frequency offset is provided by the higher layer parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant. For a MsgA PUSCH the frequency offset is provided by the higher layer parameter as described in [6, TS 38.213. In case of intra-slot frequency hopping, the starting RB in each hop is given by: RBstart={RBstarti=0(RBstart+RBoffset)modNBWPsizei=1, where i=0 and i=1 are the first hop and the second hop respectively, and RBstartis the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) or as calculated from the resource assignment for MsgA PUSCH (described in [6, TS 38.213]) and RBoffsetis the frequency offset in RBs between the two frequency hops. The number of symbols in the first hop is given by └NsymbPUSCHs/2┘, the number of symbols in the second hop is given by NsymbPUSCHs−└NsymbPUSCHs/2┘, where NsymbPUSCH,sis the length of the PUSCH transmission in OFDM symbols in one slot. In case of inter-slot frequency hopping, the starting RB during slot nsμis given by: RBstart(nsμ)={RBstartnsμmod2=0(RBstart+RBoffset)modNBWPsizensμmod2=1, where nsμis the current slot number within a radio frame, where a multi-slot PUSCH transmission can take place, RBstartis the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) and RBoffsetis the frequency offset in RBs between the two frequency hops. 6.3.2 Frequency Hopping for PUSCH Repetition Type B For PUSCH repetition Type B (as determined according to procedures defined in Clause 6.1.2.1 for scheduled PUSCH, or Clause 6.1.2.3 for configured PUSCH), a UE is configured for frequency hopping by the higher layer parameter frequencyHopping-ForDCIFormat0_2 in pusch-Config for PUSCH transmission scheduled by DCI format 0_2, by frequencyHopping-ForDCIFormat0_1 provided in pusch-Config for PUSCH transmission scheduled by DCI format 0_1, and by frequencyHopping-PUSCHRepTypeB provided in rrc-ConfiguredUplinkGrant for Type 1 configured PUSCH transmission. The frequency hopping mode for Type 2 configured PUSCH transmission follows the configuration of the activating DCI format. One of two frequency hopping modes can be configured:Inter-repetition frequency hoppingInter-slot frequency hopping In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the UE may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format is set to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher layer parameter frequencyHopping-PUSCHRepTypeB is provided, otherwise no PUSCH frequency hopping is performed. When frequency hopping is enabled for PUSCH, the RE mapping is defined in clause 6.3.1.6 of [4, TS 38.211]. In case of inter-repetition frequency hopping, the starting RB for an actual repetition within the n-th nominal repetition (as defined in Clause 6.1.2.1) is given by: RBstart(n)={RBstartnmod2=0(RBstart+RBoffset)modNBWPsizenmod2=1, where RBstartis the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) and RBoffsetis the frequency offset in RBs between the two frequency hops. In case of inter-slot frequency hopping, the starting RB during slot nsμfollows that of inter-slot frequency hopping for PUSCH Repetition Type A in Clause 6.3.1. One or more parts of 3GPP TS 38.211 V15.7.0 are quoted below: 9.2.1 PUCCH Resource Sets . . . If └rPUCCH/8┘=0 and a UE is provided a PUCCH resource by pucch-Resource Common and is not provided useInterlacePUCCHCornrnon-r16the UE determines the PRB index of the PUCCH transmission in the first hop as RBBWPoffset+└rPUCCH/NCS┘ and the PRB index of the PUCCH transmission in the second hop as NBWPsize−1−RBBWPoffset−└rPUCCH/NCS┘, where NCSis the total number of initial cyclic shift indexes in the set of initial cyclic shift indexesthe UE determines the initial cyclic shift index in the set of initial cyclic shift indexes as rPUCCHmodNCS If └rPUCCH/8┘=1 and a UE is provided a PUCCH resource by pucch-ResourceCommon and is not provided useInterlacePUCCH-PUCCH in BWP-UplinkConunonthe UE determines the PRB index of the PUCCH transmission in the first hop as NBWPsize−1−RBBWPoffset−└(rPUCCH−8)/NCS┘ and the PRB index of the PUCCH transmission in the second hop as RBBWPoffset+└(rPUCCH−8)/NCS┘the UE determines the initial cyclic shift index in the set of initial cyclic shift indexes as (rPUCCH−8)modNCS There is a study of operation in frequency band higher than 52.6 GHz. Some changes and/or amendments are under consideration as there are several characteristics different from lower conventional frequency bands (e.g., at least one of wider available bandwidth, larger noise such as larger phase noise, different, such as greater, intercell interference (ICI), etc.). Therefore, it may be expected that a larger subcarrier spacing (e.g., up to 960 kHz) and a bandwidth of a cell may be increased to GHz level, (e.g., 1 or 2 GHz). One or more parts of RP-193259, associated with the study, are quoted below: This study item will include the following objectives:,Study of required changes to NR using existing DL/UL NR waveform to support operation between 52.6 GHz and 71 GHzStudy of applicable numerology including subcarrier spacing, channel BW (including maximum BW), and their impact to FR2 physical layer design to support system functionality considering practical RF impairments [RAN1, RAN4].Identify potential critical problems to physical signal/channels, if any [RAN1]. As discussed above, resource allocation for a UE may be defined by (e.g., confined and/or limited to within) a bandwidth of a bandwidth part (BWP) (e.g., an active bandwidth part) of the UE. Resources that can be allocated to the UE may be based on (e.g., up to) the bandwidth of the bandwidth part (e.g., NBWPsizephysical resource blocks (PRBs)). To support a larger bandwidth of a cell, a larger subcarrier spacing may be preferred (e.g., a subcarrier spacing of 960 kHz). With existing Fast Fourier Transform (FFT) size and/or Inverse Fast Fourier Transform (IFFT) size (e.g., a FFT size and/or IFFT size of up to 4096), the number of PRBs that the UE is able to receive may be limited (e.g., confined). For example, the number of PRBs may be limited such that a product of the number of PRBs and 12 is smaller than the FFT and/or the IFFT size (i.e., in an example where the FFT and/or the IFFT size is 4096, PRB×12<4096). For example, the number of PRBs (for a bandwidth part and/or cell, for example) may be limited (e.g., confined) to 275. In an example, for 960 kHz subcarrier spacing (e.g., a subcarrier spacing of 960 kHz), 275 PRBs may correspond to about 3.2 GHz bandwidth. Accordingly, when a UE operates with a bandwidth part (e.g., an active bandwidth part) with 960 kHz subcarrier spacing, the UE may be scheduled with resources within a 3.2 GHz bandwidth (e.g., a bandwidth of 3.2 GHz). In this example, both radio frequency (RF) and base band of the UE may operate with 3.2 GHz bandwidth (or, considering guard band, the UE may operate with a bandwidth that is larger (e.g., slightly larger) than 3.2 GHz or smaller (e.g., slightly smaller) than 3.2 GHz). On the other hand, when the UE operates with a bandwidth part (e.g., an active bandwidth part) with 240 kHz subcarrier spacing, the schedulable bandwidth may be reduced to resources within 0.8 GHz bandwidth, even if 3.2 GHz bandwidth is supported by the UE. Accordingly, candidate resources of the UE is reduced if the subcarrier spacing is reduced. The reduction of candidate resources of the UE, as a result of a reduction of the subcarrier spacing, may be more significant if the subcarrier spacing of the bandwidth part is smaller. Scheduling efficiency may be reduced as well due to such constraints of the smaller bandwidth (e.g., the smaller schedulable bandwidth of the UE). A way to avoid this constraint may be to decouple a bandwidth of a bandwidth part and a maximum bandwidth and/or a maximum number of resources that may be scheduled to the UE within the bandwidth part. A first bandwidth may correspond to (and/or may be used as) a bandwidth of a bandwidth part and a second bandwidth may correspond to (and/or may be used as) a maximum bandwidth that may be scheduled to the UE within the bandwidth part. For example, when a bandwidth part with X PRBs is active (for the UE, for example), a maximum number of PRBs that can be allocated to the UE is Y. Alternatively and/or additionally, when a bandwidth part with X PRBs is active (for the UE, for example), a maximum bandwidth that can be allocated to the UE is associated with Y PRBs (e.g., the maximum bandwidth corresponds to a bandwidth of Y PRBs). A bandwidth that can be allocated to a UE may be determined based on (e.g., derived from) a difference between a PRB with a lowest index allocated to the UE (e.g., a PRB with a lowest index among PRBs allocated to the UE) and a PRB with a largest index allocated to the UE (e.g., a PRB with a largest index among PRBs allocated to the UE). A difference between the PRB with the lowest index allocated to the UE and the PRB with the largest index allocated to the UE may be smaller than Y. In some examples, Y is different from X. Y may be smaller than X. In some examples, X (and/or X PRBs of the active bandwidth part) and Y (and/or Y PRBs that can be allocated to the UE) are based on a subcarrier spacing of the bandwidth part. In some examples, X may be larger than 275. In some examples, Y is not larger than 275. However, with interleaved mapping, even if allocated virtual resource blocks (VRBs) (indicated by a resource allocation field, for example) are within a bandwidth of Y PRBs/VRBs (e.g., a set of Y PRBs and/or VRBs that can be allocated to the UE), one or more PRBs used (by the UE, for example) for transmission may be associated with a bandwidth larger than the bandwidth of the Y PRBs/VRBs (e.g., the one or more PRBs for used for transmission may spread across a bandwidth larger than the bandwidth of the Y PRBs/VRBs). Accordingly, the UE may not be able to process the data channel due to insufficient FFT and/or IFFT size. A first concept of the present disclosure is to disable and/or prohibit interleaved mapping. Interleaved mapping may be disabled and/or prohibited under situations in which one or more issues (e.g., one or more of the aforementioned issues) occur. For example, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or a base station, for example) when (and/or if) a bandwidth of a set of PRBs that can be processed by the UE is smaller than a bandwidth of a bandwidth part. In some examples, the bandwidth part is an active bandwidth part (of the UE, for example). For example, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) in response to determining that the bandwidth of the set of PRBs that can be processed by the UE is smaller than the bandwidth of the bandwidth part. Alternatively and/or additionally, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) when (and/or if) the UE receives an indication of a subset of frequency resources within the bandwidth part used for resource allocation (e.g., derived resource allocation). For example, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) in response to receiving the indication of the subset of frequency resources. Alternatively and/or additionally, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) when (and/or if) resource allocation for the UE is defined by (e.g., confined and/or limited to within) a bandwidth that is smaller than a bandwidth of a bandwidth part (e.g., an active bandwidth part of the UE). Alternatively and/or additionally, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) when (and/or if) VRBs allocated to the UE would spread across a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) when (and/or if) VRBs allocated to the UE would spread across a bandwidth larger than a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) when (and/or if) enablement and/or usage of the interleaved mapping would cause resources (e.g., VRBs and/or PRBs) to be allocated to the UE, where the resources would spread across a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, interleaved mapping may be disabled and/or prohibited (for use in allocating resources for a UE and/or for use in in one or more transmissions by the UE and/or the base station, for example) when (and/or if) enablement and/or usage of the interleaved mapping would cause resources (e.g., VRBs and/or PRBs) to be allocated to the UE, where the resources would spread across a bandwidth larger than a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). A second concept of the present disclosure is to develop and/or use an interleaved mapping (e.g., a new interleaved mapping) and/or a technique for performing interleaved mapping (e.g., a new technique for performing interleaved mapping), where by using the interleaved mapping and/or the technique for performing interleaved mapping, the PRBs for transmission are within a bandwidth that defines resource allocation (e.g., a bandwidth to which resource allocation is limited, such as a bandwidth to which resource allocation is confined). The technique may comprise performing a mapping (e.g., interleaved mapping) across a subset of resources within a bandwidth part. In some examples, the technique does not comprise performing a mapping across a whole bandwidth part (e.g., a whole active bandwidth part of the UE). The subset of resources may be a window. The window may have a size of a bandwidth that defines resource allocation (e.g., a bandwidth to which resource allocation is limited, such as a bandwidth to which resource allocation is confined). The subset of resources may be indicated by a base station (e.g., the base station may transmit an indication, of the subset of resources, to the UE). The subset of resources may be determined based on (e.g., derived from) a DCI (e.g., a DCI transmitted by the base station to the UE). The subset of resources may be determined (e.g., derived) based on one or more resources allocated to a UE. Examples for mapping (e.g., the new interleaved mapping) and/or techniques for performing mapping (e.g., interleaved mapping) are provided below. In a first example for mapping (e.g., interleaved VRB-to-PRB mapping), resource block bundles may be defined as: for one or more Physical Downlink Shared Channel (PDSCH) transmissions (e.g., the one or more PDSCH transmissions may correspond to PDSCH transmissions, such as all PDSCH transmissions, other than PDSCH transmissions scheduled with DCI format 1_0 with CRC scrambled by System Information Radio Network Temporary Identifier (SI-RNTI) in Type0-PDCCH common search space in Control Resource Set (CORESET)0and/or other than PDSCH transmissions scheduled with DCI format 1_0 in any common search space in bandwidth part i with starting position NBWP,istart), a set of Y resource blocks in bandwidth part i with starting position S are divided into Nbundle=┌(Y+(S mod Li))/Li┐ resource-block bundles in increasing order of the resource-block number and bundle number, where Liis the bundle size for bandwidth part i provided by the higher-layer parameter vrb-ToPRB-Interleaver and where: (i) resource block bundle 0 comprises (e.g., consists of) Li−(S mod Li) resource blocks; (ii) if (S+Y)modLi>0, resource block bundle Nbundle−1 comprises (e.g., consists of) (S+Y)mod Liresource blocks, (iii) if (S+Y)modLi≤0, resource block bundle Nbundle−1 comprises (e.g., consists of) Liresource blocks, and/or (iv) other resource block bundles (e.g., resource block bundles, such as all resource block bundles, other than resource block bundle 0 and resource block bundle Nbundle−1) each comprise (e.g., consist of) Liresource blocks. In the first example for mapping (e.g., interleaved VRB-to-PRB mapping), VRBs in the interval j ∈ {0, 1, . . . , Nbundle−1} are mapped to PRBs according to: (i) VRB bundle Nbundle−1 is mapped to PRB bundle Nbundle−1,(ii) VRB bundle j ∈{0, 1, . . . , Nbundle−2} is mapped to PRB bundle ƒ(j), where ƒ(j)=rC+c j=cR+r r=0, 1, . . . ,R−1 c=0, 1, . . . ,C−1 R=2 C=└Nbundle/R┘, and/or (iii) the UE does not expect (and/or is not expected) to be configured with Li=2 simultaneously and/or concurrently with a Physical Resource Block Group (PRG) size of 4 (such as defined in 3GPP TS 38.214 V16.2.0) (e.g., the UE may not be configured with Li=2 and the PRG size of 4 at the same time). In the first example for mapping (e.g., interleaved VRB-to-PRB mapping), S may be different from NBWP,istart. Y may be different from NBWP,isize. S and/or Y may be indicated by a base station (e.g., the base station may transmit an indication of S and/or Y to the UE). S may be a starting position of a set of frequency resources. Y may be a size and/or bandwidth of a set of resources (e.g., the set of frequency resources). The set of resources may be a subset of resources of a bandwidth part (e.g., an active bandwidth part of the UE). S and/or Y may not be provided via (and/or given by) a locationAndBandwidth field (e.g., S and/or Y may not be determined based on a locationAndBandwidth field). In some examples, S is not an index of a lowest PRB and/or a lowest Common Resource Block (CRB) of a bandwidth part (e.g., an active bandwidth part of the UE). In some examples, Y is not a size and/or bandwidth of a bandwidth part (e.g., an active bandwidth part of the UE). A lowest PRB of a bandwidth part may correspond to a PRB with a lowest index among PRBs of the bandwidth part. A lowest CRB of a bandwidth part may correspond to a CRB with a lowest index among CRB s of the bandwidth part. S may be larger than an index of a lowest PRB and/or lowest CRB of a bandwidth part. Y may be smaller than a bandwidth and/or size of a bandwidth part. S and/or NBWP,istartmay be used for VRB to PRB mapping under different situations (e.g., in some situations S may be used for VRB to PRB mapping and/or in other situations NBWP,istartmay be used for VRB to PRB mapping). Y and/or NBWP,isizemay be used for VRB to PRB mapping under different situations (e.g., in some situations Y may be used for VRB to PRB mapping and/or in other situations NBWP,isizemay be used for VRB to PRB mapping). In the first example for mapping (e.g., interleaved VRB-to-PRB mapping), S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when one or more issues (e.g., one or more of the aforementioned issues) occur. For example, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when (and/or if) a bandwidth of a set of PRBs that can be processed by the UE is smaller than a bandwidth of a bandwidth part. In some examples, the bandwidth part is an active bandwidth part (of the UE, for example). For example, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) in response to determining that the bandwidth of the set of PRBs that can be processed by the UE is smaller than the bandwidth of the bandwidth part. Alternatively and/or additionally, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when (and/or if) the UE receives an indication of a subset of frequency resources within the bandwidth part used for resource allocation (e.g., derived resource allocation). For example, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) in response to receiving the indication of the subset of frequency resources. Alternatively and/or additionally, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when (and/or if) resource allocation for the UE is defined by (e.g., confined and/or limited to within) a bandwidth that is smaller than a bandwidth of a bandwidth part (e.g., an active bandwidth part of the UE). Alternatively and/or additionally, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when (and/or if) VRBs allocated to the UE would spread across a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when (and/or if) VRBs allocated to the UE would spread across a bandwidth larger than a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when (and/or if) enablement and/or usage of the interleaved mapping would cause resources (e.g., VRBs and/or PRBs) to be allocated to the UE, where the resources would spread across a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, S and/or Y may be used for VRB to PRB mapping (and/or NBWP,istartand/or NBWP,isizemay not be used for VRB to PRB mapping) when (and/or if) enablement and/or usage of the interleaved mapping would cause resources (e.g., VRBs and/or PRBs) to be allocated to the UE, where the resources would spread across a bandwidth larger than a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). In the first example for mapping (e.g., interleaved VRB-to-PRB mapping), NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when one or more issues (e.g., one or more of the aforementioned issues) do not occur. For example, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when (and/or if) a bandwidth of a set of PRBs that can be processed by the UE is not smaller than a bandwidth of a bandwidth part. In some examples, the bandwidth part is an active bandwidth part (of the UE, for example). For example, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) in response to determining that the bandwidth of the set of PRBs that can be processed by the UE is not smaller than the bandwidth of the bandwidth part. Alternatively and/or additionally, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when (and/or if) the UE does not receive an indication of a subset of frequency resources within the bandwidth part used for resource allocation (e.g., derived resource allocation). Alternatively and/or additionally, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when (and/or if) resource allocation for the UE is not defined by (e.g., not confined and/or limited to within) a bandwidth that is smaller than a bandwidth of a bandwidth part (e.g., an active bandwidth part of the UE). Alternatively and/or additionally, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when (and/or if) VRBs allocated to the UE would not spread across a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when (and/or if) VRBs allocated to the UE would not spread across a bandwidth larger than a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when (and/or if) enablement and/or usage of the interleaved mapping would not cause resources (e.g., VRBs and/or PRBs) to be allocated to the UE, where the resources would spread across a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). Alternatively and/or additionally, NBWP,istartand/or NBWP,isizemay be used for VRB to PRB mapping (and/or S and/or Y may not be used for VRB to PRB mapping) when (and/or if) enablement and/or usage of the interleaved mapping would not cause resources (e.g., VRBs and/or PRBs) to be allocated to the UE, where the resources would spread across a bandwidth larger than a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined). In the first example for mapping (e.g., interleaved VRB-to-PRB mapping), a base station may indicate (to the UE, for example) whether S or NBWP,istartis to be used for VRB to PRB mapping (e.g., the base station may instruct the UE to use S for VRB to PRB mapping or the base station may instruct the UE to use NBWP,istartfor VRB to PRB mapping). A base station may indicate (to the UE, for example) whether Y or NBWP,isizeis to be used for VRB to PRB mapping (e.g., the base station may instruct the UE to use Y for VRB to PRB mapping or the base station may instruct the UE to use NBWP,isizefor VRB to PRB mapping). Alternatively and/or additionally, a base station and/or the UE may determine whether S or NBWP,istartis to be used for VRB to PRB mapping. Alternatively and/or additionally, a base station and/or the UE may determine whether Y or NBWP,isizeis to be used for VRB to PRB mapping. The determination (of whether to use S or NBWP,istartfor VRB to PRB mapping and/or whether to use Y or NBWP,isizefor VRB to PRB mapping) may be based on one or more conditions (e.g., one or more specified conditions), such as based on at least one of whether or not a bandwidth of a set of PRBs that can be processed by the UE is smaller than a bandwidth of a bandwidth part (e.g., an active bandwidth part of the UE), whether or not the UE receives an indication of a subset of frequency resources within the bandwidth part used for resource allocation (e.g., derived resource allocation), whether or not a bandwidth of the UE is defined by (e.g., confined and/or limited to within) a bandwidth that is smaller than a bandwidth of a bandwidth part (e.g., an active bandwidth part of the UE), whether or not VRBs allocated to the UE would spread across a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined), whether or not VRBs allocated to the UE would spread across a bandwidth larger than a bandwidth that defines resource allocation for the UE (e.g., the bandwidth that defines resource allocation for the UE may be a bandwidth to which resource allocation for the UE is limited, such as a bandwidth to which resource allocation for the UE is confined), etc. With respect to the first example for mapping (e.g., interleaved VRB-to-PRB mapping), the bandwidth part may be an active bandwidth part. Alternatively and/or additionally, the bandwidth part may be a bandwidth part that the UE is using. Alternatively and/or additionally, the bandwidth part may be a bandwidth part for resource allocation. Alternatively and/or additionally, the bandwidth part may be a bandwidth part for a data channel. Alternatively and/or additionally, the bandwidth part may be a bandwidth part where a transmission or reception is scheduled. In a second example for mapping (e.g., interleaved mapping for frequency hopping, such as intra-slot frequency hopping), in a scenario associated with intra-slot frequency hopping, a starting Resource Block (RB) in each hop may be given by RBstart={RBstarti=0S+[(RBstart+RBoffset)modL]i=1 where: (i) i=0 is the first hop (e.g., initial hop) and i=1 is the second hop (following, such as directly following, the first hop, for example), (ii) RBstartis the starting RB within the uplink (UL) bandwidth part, as calculated from the resource block assignment information of resource allocation type 1 (such as discussed in Clause 6.1.2.2.2 of 3GPP TS 38.214 V16.2.0) or as calculated from the resource assignment for MsgA Physical Uplink Shared Channel (PUSCH) (such as discussed in 3GPP TS 38.213 V16.2.0), and/or (iii) RBoffsetis the frequency offset (in units of RBs, for example) between the first hop and the second hop. S may be a starting PRB of a subset of resources. L may be a size and/or bandwidth of the subset of resources. In a third example for mapping (e.g., interleaved mapping for frequency hopping, such as intra-slot frequency hopping), the mapping may be performed based on rPUCCH. For example, in the third example for mapping (e.g., interleaved mapping for frequency hopping, such as intra-slot frequency hopping), if └PUCCH/8┘=0 and if a UE is provided with a Physical Uplink Control Channel (PUCCH) resource by pucch-ResourceCommon and is not provided with useInterlacePUCCHCommon-r16: (i) the UE determines a PRB index of a PUCCH transmission in the first hop (e.g., initial hop) to be RBBWPoffset+└rPUCCH/NCS┘, and/or the UE determines a PRB index of a PUCCH transmission in the second hop (e.g., a hop following, such as directly following, the initial hop) to be S+S+L−1−RBBWPoffset−└rPUCCH/NCS┘, where RBBWPoffsetmay be a frequency offset between the first hop and the second hop, NCSmay be a total number of initial cyclic shift indexes in a set of initial cyclic shift indexes, S may be a starting PRB of a subset of resources and/or L may be a size and/or bandwidth of the subset of resources, and/or (ii) the UE determines an initial cyclic shift index in the set of initial cyclic shift indexes to be rPUCCHmodNCS. Alternatively and/or additionally, in the third example for mapping (e.g., interleaved mapping for frequency hopping, such as intra-slot frequency hopping), if └rPUCCH/8┘=1 and if a UE is provided with a PUCCH resource by pucch-ResourceCommon and is not provided useInterlacePUCCH-PUSCH in BWP-UplinkCommon: (1) the UE determines a PRB index of a PUCCH transmission in the first hop (e.g., initial hop) to be S+S+L−1−RBBWPoffset−└(rPUCCH−8)/NCS┘ and/or the UE determines a PRB index of a PUCCH transmission in the second hop (e.g., a hop following, such as directly following, the initial hop) to be RBBWPoffset−└(rPUCCH−8)/NCS┘, where RBBWPoffsetmay be a frequency offset between the first hop and the second hop, NCSmay be a total number of initial cyclic shift indexes in a set of initial cyclic shift indexes, S may be a starting PRB of a subset of resources and/or L may be a size and/or bandwidth of the subset of resources, and/or (ii) the UE determines an initial cyclic shift index in the set of initial cyclic shift indexes to be (rPUCCH−8)modNCS. A baseband of a UE may operate at a smaller bandwidth than a bandwidth of RF (and/or a bandwidth of the baseband may be a portion of the bandwidth of the RF). RF (and/or a bandwidth of the RF) may cover a bandwidth of a bandwidth part. The baseband (e.g., IFFT and/or FFT), and/or a bandwidth of the baseband, may cover a subset of resources within the bandwidth part. For example, a RF of a UE (and/or a bandwidth of the RF) may cover a bandwidth of 3.2 GHz, and a baseband of the UE (and/or a bandwidth of the baseband) may cover a bandwidth of 0.8 GHz. Throughout the present disclosure, the term “window” can be replaced with “a set of frequency resources” and/or “a set of PRBs and/or CRBs”. A window may occupy a subset of frequency resources within a bandwidth part. Throughout the present disclosure, a subset of frequency resources may be a set of one or more frequency resources. In a first embodiment, a UE receives a configuration of a bandwidth part from a base station. The UE may receive an indication of a second subset of resources within the bandwidth part. The second subset of resources may be used for determining (e.g., deriving) a mapping between VRB and PRB. A starting location of the second subset of resources may be used for determining (e.g., deriving) a mapping between VRB and PRB. A size and/or bandwidth of the second subset of resources is used for determining (e.g., deriving) a mapping between VRB and PRB. The starting location and/or the bandwidth of the second subset of resources may be used for determining (e.g., deriving) a mapping between VRB and PRB. The bandwidth of the second subset of resources may be smaller than a bandwidth of the bandwidth part. The starting position of the second subset of resources is a PRB and/or CRB (e.g., one PRB and/or CRB) within the bandwidth part. The starting position of the second subset of resources may be different from a lowest PRB and/or CRB of the bandwidth part (and/or the starting position of the second subset of resources may be different from a starting PRB and/or CRB of the bandwidth part). The UE may receive an indication of a first subset of frequency resources within the bandwidth part. The UE may determine (e.g., derive) a resource allocation within a first subset of resources. The first subset of resources may be the same as the second subset of resources. The same indication may be used to indicate the first subset of resources and the second subset of resources if the first subset of resources is the same as the second subset of resources. The first subset of resources may be different from the second subset of resources. The resource allocation may be for a data channel received or transmitted by the UE. The UE may not be scheduled (and/or may not be allowed and/or configured to be scheduled) outside the first subset of frequency resources. The UE may not be scheduled with (and/or may not be allowed and/or configured to be scheduled with) a VRB and/or PRB (e.g., one VRB and/or PRB) that is outside the first subset of frequency resources within the bandwidth part. The first subset of frequency resources may be a set of contiguous frequency resources. The second subset of frequency resources may be a set of contiguous frequency resources. The first subset of resources may be a window. The second subset of resources may be a window. The first subset of frequency resources may comprise a set of contiguous PRBs. The second subset of frequency resources may comprise a set of contiguous PRBs. A frequency location of the first subset of frequency resources may be indicated to the UE (e.g., an indication of the frequency location of the first subset of frequency resources may be transmitted to the UE). A frequency location of the first subset of frequency resources and/or a frequency location of the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted to the UE may comprise an indication of the frequency location of the first subset of frequency resources and/or an indication of the frequency location of the second subset of frequency resources). A first PRB (e.g., an initial and/or starting PRB) of the first subset of frequency resources may be indicated to the UE (e.g., an indication of the first PRB of the first subset of frequency resources may be transmitted to the UE). A first PRB (e.g., an initial and/or starting PRB) of the second subset of frequency resources may be indicated to the UE (e.g., an indication of the first PRB of the second subset of frequency resources may be transmitted to the UE). A first PRB (e.g., an initial and/or starting PRB) of the first subset of frequency resources and/or a first PRB (e.g., an initial and/or starting PRB) of the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted to the UE may comprise an indication of the first PRB of the first subset of frequency resources and/or an indication of the first PRB of the second subset of frequency resources). A bandwidth of the first subset of frequency resources may be fixed and/or pre-defined. A bandwidth of the second subset of frequency resources may be fixed and/or pre-defined. A bandwidth of the first subset of frequency resources may be indicated to the UE (e.g., an indication of the bandwidth of the first subset of frequency resources may be transmitted to the UE). A bandwidth of the second subset of frequency resources may be indicated to the UE (e.g., an indication of the bandwidth of the second subset of frequency resources may be transmitted to the UE). A bandwidth of the first subset of frequency resources and/or a bandwidth of the second subset of frequency resources may be indicated by a Radio Resource Control (RRC) configuration (e.g., a RRC configuration with which the UE is configured may be indicative of the bandwidth of the first subset of frequency resources and/or the bandwidth of the second subset of frequency resources). A bandwidth of the first subset of frequency resources and/or a bandwidth of the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted to the UE may comprise an indication of the bandwidth of the first subset of frequency resources and/or an indication of the bandwidth of the second subset of frequency resources). The first subset of frequency resources and/or the second subset of frequency resources may have a smaller bandwidth than a bandwidth of the bandwidth part. The bandwidth part may be an active bandwidth part (of the UE, for example). The first subset of frequency resources and/or the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted to the UE may comprise an indication of the first subset of frequency resources and/or an indication of the second subset of frequency resources). In some examples, the DCI schedules one or more resources for the UE. Alternatively and/or additionally, the DCI may indicate resource allocation within the first subset of frequency resources and/or the second subset of frequency resources. A bitmap in the DCI may indicate resource allocation within the first subset of frequency resources. In some examples, a bit-width of the bitmap and/or a size of the bitmap is based on (e.g., determined based on) the bandwidth of the first subset of frequency resources. A resource indicator value (RIV) value in the DCI may indicate resource allocation within the first subset of frequency resources. In some examples, a bit-width of the RIV value and/or a size of the RIV value is based on (e.g., determined based on) the bandwidth of the first subset of frequency resources. In some examples, a frequency location of the first subset of frequency resources and a resource allocation within the first subset of frequency resources are indicated by two separate fields in the DCI (e.g., a first field may be indicative of the frequency location of the first subset of frequency resources and a second field may be indicative of the resource allocation within the first subset of frequency resources). In some examples, the frequency location of the first subset of frequency resources and the resource allocation within the first subset of frequency resources are indicated by two separate sets of bits in the DCI (e.g., a first set of one or more bits may be indicative of the frequency location of the first subset of frequency resources and a second set of one or more bits may be indicative of the resource allocation within the first subset of frequency resources, wherein the first set of one or more bits and the second set of one or more bits may be in the same field of the DCI or in separate fields of the DCI). The second set of resources may be determined (e.g., derived) based on a resource allocation field in a DCI. In a second embodiment, a base station transmits a configuration of a bandwidth part to a UE. A base station may transmit (to the UE, for example) an indication of a second subset of resources within the bandwidth part. The second subset of resources may be used for determining (e.g., deriving) a mapping between VRB and PRB. A starting location of the second subset of resources may be used for determining (e.g., deriving) a mapping between VRB and PRB. A size and/or bandwidth of the second subset of resources may be used for determining (e.g., deriving) a mapping between VRB and PRB. The starting location and/or the bandwidth of the second subset of resources may be used for determining (e.g., deriving) a mapping between VRB and PRB. The bandwidth of the second subset of resources may be smaller than a bandwidth of the bandwidth part. The starting position of the second subset of resources is a PRB and/or CRB (e.g., one PRB and/or CRB) within the bandwidth part. The starting position of the second subset of resources may be different from a lowest PRB and/or CRB of the bandwidth part (and/or the starting position of the second subset of resources may be different from a starting PRB and/or CRB of the bandwidth part). The base station may transmit (to the UE, for example) an indication of a first subset of frequency resources within the bandwidth part. The base station may determine and/or indicate (e.g., indicate to the UE) a resource allocation within a first subset of resources. The first subset of resources may be the same as the second subset of resources. The same indication may be used to indicate the first subset of resources and the second subset of resources if the first subset of resources is the same as the second subset of resources. The first subset of resources may be different from the second subset of resources. The resource allocation may be for a data channel received or transmitted by the UE. The base station may not schedule (and/or may not be allowed and/or configured to schedule) outside the first subset of frequency resources. Alternatively and/or additionally, the base station may not schedule (and/or may not be allowed and/or configured to schedule) the UE outside the first subset of frequency resources. The base station may not schedule (and/or may not be allowed and/or configured to schedule) a VRB outside the first subset of frequency resources. Alternatively and/or additionally, the base station may not schedule (and/or may not be allowed and/or configured to schedule) the UE with a VRB outside the first subset of frequency resources. The base station may not schedule (and/or may not be allowed and/or configured to schedule) outside the second subset of frequency resources. Alternatively and/or additionally, the base station may not schedule (and/or may not be allowed and/or configured to schedule) the UE outside the second subset of frequency resources. The base station is not allowed to schedule PRB outside the second subset of frequency resources. The base station may not schedule (and/or may not be allowed and/or configured to schedule) the UE in a way that a PRB is mapped outside the second subset of frequency resources. For example, the base station may not schedule (and/or may not be allowed and/or configured to schedule) the UE with a PRB mapped outside the second subset of frequency resources. The base station may not schedule (and/or may not be allowed and/or configured to schedule) a VRB and/or PRB (e.g., one VRB and/or PRB) that is outside the first subset of frequency resources within the bandwidth part. For example, the base station may not schedule (and/or may not be allowed and/or configured to schedule) the UE with a VRB and/or PRB (e.g., one VRB and/or PRB) that is outside the first subset of frequency resources within the bandwidth part. The first subset of frequency resources may be a set of contiguous frequency resources. The second subset of frequency resources may be a set of contiguous frequency resources. The first subset of resources may be a window. The second subset of resources may be a window. The first subset of frequency resources may comprise a set of contiguous PRBs. The second subset of frequency resources may comprise a set of contiguous PRBs. A frequency location of the first subset of frequency resources may be indicated to the UE (e.g., an indication of the frequency location of the first subset of frequency resources may be transmitted, by the base station, to the UE). A frequency location of the first subset of frequency resources and/or a frequency location of the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted, by the base station, to the UE may comprise an indication of the frequency location of the first subset of frequency resources and/or an indication of the frequency location of the second subset of frequency resources). A first PRB (e.g., an initial and/or starting PRB) of the first subset of frequency resources may be indicated to the UE (e.g., an indication of the first PRB of the first subset of frequency resources may be transmitted, by the base station, to the UE). A first PRB (e.g., an initial and/or starting PRB) of the second subset of frequency resources may be indicated to the UE (e.g., an indication of the first PRB of the second subset of frequency resources may be transmitted, by the base station, to the UE). A first PRB (e.g., an initial and/or starting PRB) of the first subset of frequency resources and/or a first PRB (e.g., an initial and/or starting PRB) of the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted, by the base station, to the UE may comprise an indication of the first PRB of the first subset of frequency resources and/or an indication of the first PRB of the second subset of frequency resources). A bandwidth of the first subset of frequency resources may be fixed and/or pre-defined. A bandwidth of the second subset of frequency resources may be fixed and/or pre-defined. A bandwidth of the first subset of frequency resources may be indicated to the UE (e.g., an indication of the bandwidth of the first subset of frequency resources may be transmitted, by the base station, to the UE). A bandwidth of the second subset of frequency resources may be indicated to the UE (e.g., an indication of the bandwidth of the second subset of frequency resources may be transmitted, by the base station, to the UE). A bandwidth of the first subset of frequency resources and/or a bandwidth of the second subset of frequency resources may be indicated by a RRC configuration (e.g., a RRC configuration with which the UE is configured may be indicative of the bandwidth of the first subset of frequency resources and/or the bandwidth of the second subset of frequency resources). A bandwidth of the first subset of frequency resources and/or a bandwidth of the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted, by the base station, to the UE may comprise an indication of the bandwidth of the first subset of frequency resources and/or an indication of the bandwidth of the second subset of frequency resources). The first subset of frequency resources and/or the second subset of frequency resources may have a smaller bandwidth than a bandwidth of the bandwidth part. The bandwidth part may be an active bandwidth part (of the UE, for example). The first subset of frequency resources and/or the second subset of frequency resources may be indicated by a DCI (e.g., a DCI transmitted, by the base station, to the UE may comprise an indication of the first subset of frequency resources and/or an indication of the second subset of frequency resources). In some examples, the DCI schedules one or more resources for the UE. Alternatively and/or additionally, the DCI may indicate resource allocation within the first subset of frequency resources and/or the second subset of frequency resources. A bitmap in the DCI may indicate resource allocation within the first subset of frequency resources. In some examples, a bit-width of the bitmap and/or a size of the bitmap is based on (e.g., determined based on) the bandwidth of the first subset of frequency resources. A RIV value in the DCI may indicate resource allocation within the first subset of frequency resources. In some examples, a bit-width of the RIV value and/or a size of the RIV value is based on (e.g., determined based on) the bandwidth of the first subset of frequency resources. In some examples, a frequency location of the first subset of frequency resources and a resource allocation within the first subset of frequency resources are indicated by two separate fields in the DCI (e.g., a first field may be indicative of the frequency location of the first subset of frequency resources and a second field may be indicative of the resource allocation within the first subset of frequency resources). In some examples, the frequency location of the first subset of frequency resources and the resource allocation within the first subset of frequency resources are indicated by two separate sets of bits in the DCI (e.g., a first set of one or more bits may be indicative of the frequency location of the first subset of frequency resources and a second set of one or more bits may be indicative of the resource allocation within the first subset of frequency resources, wherein the first set of one or more bits and the second set of one or more bits may be in the same field of the DCI or in separate fields of the DCI). The second set of resources may be determined (e.g., derived) based on a resource allocation field in a DCI. In a third embodiment, a base station may not indicate (and/or may be prohibited from indicating) interleaved mapping, e.g., VRB to PRB mapping, to a UE. For example, the base station may not indicate (and/or may be prohibited from indicating) interleaved mapping (e.g., VRB to PRB mapping) to the UE if and/or when using (e.g., enabling and/or applying) interleaved mapping (e.g., VRB to PRB mapping) would result in PRBs being allocated to the UE, wherein a bandwidth of the PRBs allocated to the UE is larger than a bandwidth that the UE can process (e.g., the bandwidth of the PRBs exceeds a maximum bandwidth of PRBs that the UE is able to process). Alternatively and/or additionally, the base station may not indicate (and/or may be prohibited from indicating) interleaved mapping (e.g., VRB to PRB mapping) to the UE if and/or when using (e.g., enabling and/or applying) interleaved mapping (e.g., VRB to PRB mapping) would result in PRBs being allocated to the UE, wherein a bandwidth of the PRBs allocated to the UE exceeds a capability of the UE. Alternatively and/or additionally, the base station may not indicate (and/or may be prohibited from indicating) interleaved mapping (e.g., VRB to PRB mapping) to the UE if and/or when using (e.g., enabling and/or applying) interleaved mapping (e.g., VRB to PRB mapping) would result in PRBs being allocated to the UE, wherein a number of PRBs of the PRBs allocated to the UE is more than the UE can process (e.g., the number of PRBs of the PRBs allocated to the UE exceeds a maximum number of PRB s allocated to the UE that the UE is able to process). Alternatively and/or additionally, the base station may not indicate (and/or may be prohibited from indicating) interleaved mapping (e.g., VRB to PRB mapping) to the UE if and/or when using (e.g., enabling and/or applying) interleaved mapping (e.g., VRB to PRB mapping) would result in a number of PRBs allocated to the UE exceeding a capability of the UE. Alternatively and/or additionally, the base station may not indicate (and/or may be prohibited from indicating) interleaved mapping (e.g., VRB to PRB mapping) to the UE if and/or when (and/or after) a base station indicates, to the UE, a subset of resources within a bandwidth part of the UE (e.g., an active bandwidth part of the UE). Resource allocation for the UE may be performed within the subset of resources. For example, one or more resources within the subset of resources may be allocated to the UE and/or resources outside the subset of resources may not be allocated to the UE. For example, the base station may not be configured and/or allowed to allocate a resource, outside the subset of the resources, to the UE. Alternatively and/or additionally, the base station may not indicate (and/or may be prohibited from indicating) interleaved mapping (e.g., VRB to PRB mapping) to the UE if and/or when (and/or after) a base station indicates, to the UE, that resource allocation is performed within a subset of resources of a bandwidth part of the UE (e.g., an active bandwidth part of the UE). Throughout the present disclosure, the present disclosure may describe behavior and/or operation of a single serving cell unless otherwise noted. Throughout the present disclosure, the present disclosure may describe behavior and/or operation of multiple serving cells unless otherwise noted. Throughout the present disclosure, the present disclosure may describe behavior and/or operation of a single bandwidth part unless otherwise noted. Throughout the present disclosure, a base station may configure a UE with multiple bandwidth parts unless otherwise noted. Throughout the present disclosure, interleaved mapping and/or distributed mapping (e.g., Distributed Virtual Resource Block (DVRB) mapping and/or frequency hopping) may be applied for downlink (DL) transmission and/or uplink transmission (e.g., at least one of PDSCH, PUSCH, Physical Downlink Control Channel (PDCCH), PUCCH). Throughout the present disclosure, a base station may configure a UE with a single bandwidth part unless otherwise noted. One, some and/or all of the foregoing techniques and/or embodiments can be formed to a new embodiment. In some examples, embodiments disclosed herein, such as embodiments described with respect to the first concept, the second concept, the first embodiment, the second embodiment and the third embodiment, may be implemented independently and/or separately. Alternatively and/or additionally, a combination of embodiments described herein, such as embodiments described with respect to the first concept, the second concept, the first embodiment, the second embodiment and/or the third embodiment, may be implemented. Alternatively and/or additionally, a combination of embodiments described herein, such as embodiments described with respect to the first concept, the second concept, the first embodiment, the second embodiment and/or the third embodiment, may be implemented concurrently and/or simultaneously. Various techniques, embodiments, methods and/or alternatives of the present disclosure may be performed independently and/or separately from one another. Alternatively and/or additionally, various techniques, embodiments, methods and/or alternatives of the present disclosure may be combined and/or implemented using a single system. Alternatively and/or additionally, various techniques, embodiments, methods and/or alternatives of the present disclosure may be implemented concurrently and/or simultaneously. FIG.6is a flow chart600according to one exemplary embodiment from the perspective of a UE. In step605, the UE receives a configuration of a bandwidth part from a base station. In step610, the UE receives an indication of a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part. In step615, the UE determines (e.g., derives) a mapping between VRB and PRB based on the subset of frequency resources. Referring back toFIGS.3and4, in one exemplary embodiment of a UE, the device300includes a program code312stored in the memory310. The CPU308may execute program code312to enable the UE (i) to receive a configuration of a bandwidth part from a base station, (ii) to receive an indication of a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part, and (iii) to determine (e.g., derive) a mapping between VRB and PRB based on the subset of frequency resources. Furthermore, the CPU308can execute the program code312to perform one, some and/or all of the above-described actions and steps and/or others described herein. FIG.7is a flow chart700according to one exemplary embodiment from the perspective of a base station. In step705, the base station transmits a configuration of a bandwidth part to a UE. In step710, the base station transmits (to the UE, for example) an indication of a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part. In step715, the base station determines (e.g., derives) a mapping between VRB and PRB based on the subset of frequency resources. Referring back toFIGS.3and4, in one exemplary embodiment of a base station, the device300includes a program code312stored in the memory310. The CPU308may execute program code312to enable the base station (i) to transmit a configuration of a bandwidth part to a UE, (ii) to transmit an indication of a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part, and (iii) to determine (e.g., derive) a mapping between VRB and PRB based on the subset of frequency resources. Furthermore, the CPU308can execute the program code312to perform one, some and/or all of the above-described actions and steps and/or others described herein. With respect toFIGS.6-7, in one embodiment, the mapping is based on a starting location of the subset of frequency resources. In one embodiment, the mapping is based on a size of the subset of frequency resources. In one embodiment, the subset of frequency resources is a set of contiguous resources (e.g., a set of contiguous PRBs, VRBs and/or CRBs). In one embodiment, a bandwidth and/or size of the subset of frequency resources is smaller than a bandwidth and/or size of the bandwidth part. In one embodiment, a starting location of the subset of frequency resources is different from a starting location of the bandwidth part. In one embodiment, a first PRB of the subset of frequency resources (e.g., an initial and/or starting PRB of the subset of frequency resources) is indicated to the UE. In one embodiment, a bandwidth of the subset of frequency resources is fixed and/or pre-defined. In one embodiment, a bandwidth of the subset of frequency resources is indicated to the UE (e.g., the bandwidth may be indicated to the UE via the indication or a different indication transmitted to the UE). In one embodiment, a bandwidth of the subset of frequency resources is indicated by a RRC configuration (e.g., the RRC configuration, indicative of the bandwidth, may be transmitted to the UE and/or the UE may be configured with the RRC configuration indicative of the bandwidth). In one embodiment, the bandwidth part is an active bandwidth part (e.g., an active bandwidth part of the UE). In one embodiment, the subset of frequency resources is indicated by a DCI (e.g., the DCI, transmitted to the UE, may comprise the indication of the subset of frequency resources). In one embodiment, the DCI schedules one or more resources for the UE. In one embodiment, the DCI is indicative of resource allocation within the subset of frequency resources. For example, the DCI may allocate (and/or indicate) one or more resources, within the subset of frequency resources, to the UE (e.g., the one or more resources may be allocated for one or more transmissions, such as one or more downlink transmissions and/or one or more uplink transmissions). In one embodiment, a bitmap in the DCI is indicative of resource allocation within the subset of frequency resources. For example, the bitmap in the DCI may allocate (and/or indicate) one or more resources, within the subset of frequency resources, to the UE (e.g., the one or more resources may be allocated for one or more transmissions, such as one or more downlink transmissions and/or one or more uplink transmissions). In one embodiment, a bit-width and/or size of the bitmap is based on the bandwidth and/or size of the subset of frequency resources (e.g., the bit-width and/or size of the bitmap is determined based on the bandwidth and/or size of the subset of frequency resources). In one embodiment, an RIV value in the DCI is indicative of resource allocation within the subset of frequency resources. For example, the RIV value in the DCI may allocate (and/or indicate) one or more resources, within the subset of frequency resources, to the UE (e.g., the one or more resources may be allocated for one or more transmissions, such as one or more downlink transmissions and/or one or more uplink transmissions). In one embodiment, the DCI is indicative of resource allocation within a second subset of frequency resources (e.g., a second subset of one or more frequency resources that may be different from the subset of frequency resources). For example, the DCI may allocate (and/or indicate) one or more resources, within the second subset of frequency resources, to the UE (e.g., the one or more resources may be allocated for one or more transmissions, such as one or more downlink transmissions and/or one or more uplink transmissions). In one embodiment, a bitmap in the DCI is indicative of resource allocation within a second subset of frequency resources (e.g., a second subset of one or more frequency resources that may be different from the subset of frequency resources). For example, the bitmap in the DCI may allocate (and/or indicate) one or more resources, within the second subset of frequency resources, to the UE (e.g., the one or more resources may be allocated for one or more transmissions, such as one or more downlink transmissions and/or one or more uplink transmissions). In one embodiment, a bit-width and/or size of the bitmap is based on a bandwidth and/or size of the second subset of frequency resources (e.g., the bit-width and/or size of the bitmap is determined based on the bandwidth and/or size of the second subset of frequency resources). In one embodiment, an RIV value in the DCI is indicative of resource allocation within a second subset of frequency resources (e.g., a second subset of one or more frequency resources that may be different from the subset of frequency resources). For example, the RIV value in the DCI may allocate (and/or indicate) one or more resources, within the second subset of frequency resources, to the UE (e.g., the one or more resources may be allocated for one or more transmissions, such as one or more downlink transmissions and/or one or more uplink transmissions). In one embodiment, after the mapping is determined and/or applied (and/or when the mapping is applied and/or used by the UE), the subset of frequency resources is used to define (e.g., limit and/or confine) an allocated bandwidth (e.g., a bandwidth of the allocated bandwidth), such as a bandwidth allocated to the UE. For example, the allocated bandwidth may be defined by (e.g., limited and/or confined to within) a bandwidth of the subset of frequency resources. In one embodiment, allocated PRBs after the mapping are within the subset of frequency resources. For example, one or more PRBs, within the subset of frequency resources, are allocated to the UE after determining and/or applying the mapping (and/or when the mapping is applied and/or used by the UE). For example, after the mapping is determined and/or applied (and/or when the mapping is applied and/or used by the UE), PRBs that are within the subset of frequency resources may be allocated to the UE and/or PRBs that are outside the subset of frequency resources may not be allocated to the UE. FIG.8is a flow chart800according to one exemplary embodiment from the perspective of a base station. In step805, the base station transmits a configuration of a bandwidth part to a UE. In step810, the base station determines (e.g., derives) a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part. For example, the subset of frequency resources may be a subset of the bandwidth part (and/or a bandwidth of the subset of frequency resources may correspond to a portion of a bandwidth of the bandwidth part). In step815, the base station transmits, to the UE, an indication of one or more allocated resources, within the subset of frequency resources, for a transmission. For example, the subset of frequency resources may comprise the one or more allocated resources (and/or the subset of frequency resources may comprise one or more frequency resources of the one or more allocated resources). Alternatively and/or additionally, the indication may allocate the one or more allocated resources for the transmission (e.g., the one or more allocated resources may be allocated to the UE for the transmission and/or the UE may perform the transmission using the one or more allocated resources). The base station does not enable interleaved mapping (associated with the UE, for example) for the transmission. For example, the base station is not configured (and/or is not allowed to) enable the interleaved mapping for the transmission. In one embodiment, the base station does not enable (and/or is not configured and/or allowed to enable) the interleaved mapping for the transmission based on determining (e.g., deriving) the subset of frequency resources within the bandwidth part. For example, the base station does not enable (and/or is not configured and/or allowed to enable) the interleaved mapping for the transmission based on the subset of frequency resources being within the bandwidth part. In one embodiment, the base station does not enable (and/or is not configured and/or allowed to enable) the interleaved mapping for the transmission if the base station determines (e.g., derives) the subset of frequency resources within the bandwidth part. For example, the base station does not enable (and/or is not configured and/or allowed to enable) the interleaved mapping for the transmission if the subset of frequency resources is within the bandwidth part. In one embodiment, the base station does not enable (and/or is not configured and/or allowed to enable) the interleaved mapping for the transmission based on a maximum bandwidth of the UE being smaller than a bandwidth of the bandwidth part. For example, the maximum bandwidth may correspond to a maximum bandwidth that the UE is able to process. In one embodiment, the base station does not enable (and/or is not configured and/or allowed to enable) the interleaved mapping for the transmission if a maximum bandwidth of the UE is smaller than a bandwidth of the bandwidth part. For example, the maximum bandwidth may correspond to a maximum bandwidth that the UE is able to process. In one embodiment, the transmission is a PUSCH transmission. In one embodiment, the transmission is a PUCCH transmission. In one embodiment, the interleaved mapping corresponds to an interleaved mapping for frequency hopping for uplink transmission (and/or the interleaved mapping is frequency hopping for uplink transmission). Referring back toFIGS.3and4, in one exemplary embodiment of a base station, the device300includes a program code312stored in the memory310. The CPU308may execute program code312to enable the base station (i) to transmit a configuration of a bandwidth part to a UE, (ii) to determine (e.g., derive) a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part, and (iii) to transmit, to the UE, an indication of one or more allocated resources, within the subset of frequency resources, for a transmission, wherein the base station does not enable interleaved mapping for the transmission. Furthermore, the CPU308can execute the program code312to perform one, some and/or all of the above-described actions and steps and/or others described herein. FIG.9is a flow chart900according to one exemplary embodiment from the perspective of a UE. In step905, the UE receives, from a base station, a configuration of a bandwidth part. In step910, the UE determines (e.g., derives) a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part. For example, the subset of frequency resources may be a subset of the bandwidth part (and/or a bandwidth of the subset of frequency resources may correspond to a portion of a bandwidth of the bandwidth part). In step915, the UE receives an indication of one or more allocated resources, within the subset of frequency resources, for a PUCCH transmission. For example, the subset of frequency resources may comprise the one or more allocated resources (and/or the subset of frequency resources may comprise one or more frequency resources of the one or more allocated resources). Alternatively and/or additionally, the indication may allocate the one or more allocated resources for the PUCCH transmission (e.g., the one or more allocated resources may be allocated to the UE for the PUCCH transmission and/or the UE may perform the PUCCH transmission using the one or more allocated resources). The UE does not enable interleaved mapping for the PUCCH transmission. For example, the UE may not determine and/or use the interleaved mapping to perform the PUCCH transmission (and/or the PUCCH transmission may not be performed using the interleaved mapping). In one embodiment, the UE does not enable the interleaved mapping for the PUCCH transmission based on determining (e.g., deriving) the subset of frequency resources within the bandwidth part. For example, the UE does not enable the interleaved mapping for the PUCCH transmission based on the subset of frequency resources being within the bandwidth part. In one embodiment, the UE does not enable the interleaved mapping for the PUCCH transmission if the UE determines (e.g., derives) the subset of frequency resources within the bandwidth part. For example, the UE does not enable the interleaved mapping for the PUCCH transmission if the subset of frequency resources is within the bandwidth part. In one embodiment, the UE does not enable the interleaved mapping for the PUCCH transmission based on a maximum bandwidth of the UE being smaller than a bandwidth of the bandwidth part. For example, the maximum bandwidth may correspond to a maximum bandwidth that the UE is able to process. In one embodiment, the UE does not enable the interleaved mapping for the PUCCH transmission if a maximum bandwidth of the UE is smaller than a bandwidth of the bandwidth part. For example, the maximum bandwidth may correspond to a maximum bandwidth that the UE is able to process. In one embodiment, the interleaved mapping corresponds to an interleaved mapping for frequency hopping for uplink transmission (and/or the interleaved mapping is frequency hopping for uplink transmission). Referring back toFIGS.3and4, in one exemplary embodiment of a UE, the device300includes a program code312stored in the memory310. The CPU308may execute program code312to enable the UE (i) to receive, from a base station, a configuration of a bandwidth part, (ii) to determine (e.g., derive) a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part, and (iii) to receive an indication of one or more allocated resources, within the subset of frequency resources, for a PUCCH transmission, wherein the UE does not enable interleaved mapping for the PUCCH transmission. Furthermore, the CPU308can execute the program code312to perform one, some and/or all of the above-described actions and steps and/or others described herein. FIG.10is a flow chart1000according to one exemplary embodiment from the perspective of a UE. In step1005, the UE receives, from a base station, a configuration of a bandwidth part. In step1010, the UE determines (e.g., derives) a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part. For example, the subset of frequency resources may be a subset of the bandwidth part (and/or a bandwidth of the subset of frequency resources may correspond to a portion of a bandwidth of the bandwidth part). In step1015, the UE receives an indication of one or more allocated resources, within the subset of frequency resources, for a transmission. For example, the subset of frequency resources may comprise the one or more allocated resources (and/or the subset of frequency resources may comprise one or more frequency resources of the one or more allocated resources). Alternatively and/or additionally, the indication may allocate the one or more allocated resources for the transmission. In step1020, the UE determines (e.g., derives) an interleaved mapping for the transmission based on the subset of frequency resources. In one embodiment, the UE uses the interleaved mapping to perform the transmission (and/or the UE performs the transmission based on the interleaved mapping and/or the one or more allocated resources). For example, one or more second resources for the transmission may be determined based upon the interleaved mapping and the one or more allocated resources (e.g., the one or more allocated resources may be mapped to the one or more second resources according to the interleaved mapping). The transmission may be performed using the one or more second resources. In one embodiment, the interleaved mapping is based on a size of the subset of frequency resources. In one embodiment, the interleaved mapping is based on a starting location of the subset of frequency resources. In one embodiment, one or more allocated PRB s after the interleaved mapping is determined (and/or applied) are within the subset of frequency resources. For example, one or more PRBs, within the subset of frequency resources, are allocated to the UE after determining (and/or applying) the interleaved mapping. For example, after the interleaved mapping is determined and/or applied (and/or when the interleaved mapping is applied and/or used by the UE), PRBs that are within the subset of frequency resources may be allocated to the UE (for use in performing one or more uplink transmissions and/or one or more downlink transmissions, for example) and/or PRBs that are outside the subset of frequency resources may not be allocated to the UE. In one embodiment, the subset of frequency resources defines (e.g., limits and/or confines) an allocated bandwidth of the UE after determining (and/or applying) the interleaved mapping. For example, after the interleaved mapping is determined and/or applied (and/or when the interleaved mapping is applied and/or used by the UE), the subset of frequency resources is used to define (e.g., limit and/or confine) an allocated bandwidth (e.g., a bandwidth of the allocated bandwidth), such as a bandwidth allocated to the UE. For example, the allocated bandwidth may be defined by (e.g., limited and/or confined to within) a bandwidth of the subset of frequency resources. In one embodiment, the transmission is a PUCCH transmission. In one embodiment, the transmission is a PUSCH transmission. In one embodiment, the interleaved mapping is for frequency hopping for uplink transmission (and/or the interleaved mapping is frequency hopping for uplink transmission). In one embodiment, the determining (e.g., deriving) the interleaved mapping (for the transmission) based on the subset of frequency resources is performed based on (e.g., in response to) the determining (e.g., deriving) the subset of frequency resources within the bandwidth part. For example, the determining (e.g., deriving) the interleaved mapping (for the transmission) based on the subset of frequency resources is performed based on the subset of frequency resources being within the bandwidth part. For example, the determining (e.g., deriving) the interleaved mapping (for the transmission) is performed based on the subset of frequency resources in response to the subset of frequency resources being within the bandwidth part. In one embodiment, the determining (e.g., deriving) the interleaved mapping (for the transmission) based on the subset of frequency resources is performed if the UE determines (e.g., derives) the subset of frequency resources within the bandwidth part. For example, the determining (e.g., deriving) the interleaved mapping (for the transmission) based on the subset of frequency resources is performed if the subset of frequency resources is within the bandwidth part. For example, the determining (e.g., deriving) the interleaved mapping (for the transmission) is performed based on the subset of frequency resources if the subset of frequency resources is within the bandwidth part. In one embodiment, the determining (e.g., deriving) the interleaved mapping (for the transmission) based on the subset of frequency resources is performed based on a maximum bandwidth of the UE being smaller than a bandwidth of the bandwidth part. For example, the determining (e.g., deriving) the interleaved mapping (for the transmission) is performed based on the subset of frequency resources in response to a determination that a maximum bandwidth of the UE is smaller than a bandwidth of the bandwidth part. For example, the maximum bandwidth may correspond to a maximum bandwidth that the UE is able to process. In one embodiment, the determining (e.g., deriving) the interleaved mapping (for the transmission) based on the subset of frequency resources is performed if a maximum bandwidth of the UE is smaller than a bandwidth of the bandwidth part. For example, the determining (e.g., deriving) the interleaved mapping (for the transmission) is performed based on the subset of frequency resources if a maximum bandwidth of the UE is smaller than a bandwidth of the bandwidth part. For example, the maximum bandwidth may correspond to a maximum bandwidth that the UE is able to process. Referring back toFIGS.3and4, in one exemplary embodiment of a UE, the device300includes a program code312stored in the memory310. The CPU308may execute program code312to enable the UE (i) to receive, from a base station, a configuration of a bandwidth part, (ii) to determine (e.g., derive) a subset of frequency resources (e.g., a subset of one or more frequency resources) within the bandwidth part, (iii) to receive an indication of one or more allocated resources, within the subset of frequency resources, for a transmission, and (iv) to determine (e.g., derive) an interleaved mapping for the transmission based on the subset of frequency resources. Furthermore, the CPU308can execute the program code312to perform one, some and/or all of the above-described actions and steps and/or others described herein. A communication device (e.g., a UE, a base station, a network node, etc.) may be provided, wherein the communication device may comprise a control circuit, a processor installed in the control circuit and/or a memory installed in the control circuit and coupled to the processor. The processor may be configured to execute a program code stored in the memory to perform method steps illustrated inFIGS.6-10. Furthermore, the processor may execute the program code to perform one, some and/or all of the above-described actions and steps and/or others described herein. A computer-readable medium may be provided. The computer-readable medium may be a non-transitory computer-readable medium. The computer-readable medium may comprise a flash memory device, a hard disk drive, a disc (e.g., a magnetic disc and/or an optical disc, such as at least one of a digital versatile disc (DVD), a compact disc (CD), etc.), and/or a memory semiconductor, such as at least one of static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc. The computer-readable medium may comprise processor-executable instructions, that when executed cause performance of one, some and/or all method steps illustrated inFIGS.6-10, and/or one, some and/or all of the above-described actions and steps and/or others described herein. It may be appreciated that applying one or more of the techniques presented herein may result in one or more benefits including, but not limited to, increased efficiency of communication between devices (e.g., a UE and/or a base station). The increased efficiency may be a result of enabling the UE to perform interleaved mapping over a cell with larger bandwidth (and/or more efficiently perform interleaved mapping over a cell with larger bandwidth). Alternatively and/or additionally, the increased efficiency may be a result of enabling the UE (and/or the base station) to disable interleaved mapping for communication between the UE and the base station (such as in a situation in which a bandwidth of a bandwidth part of the UE is larger than a maximum bandwidth of the UE). Various aspects of the disclosure have been described above. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. As an example of some of the above concepts, in some aspects concurrent channels may be established based on pulse repetition frequencies. In some aspects concurrent channels may be established based on pulse position or offsets. In some aspects concurrent channels may be established based on time hopping sequences. In some aspects concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences. Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Those of skill would further appreciate that the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as “software” or a “software module”), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit (“IC”), an access terminal, or an access point. The IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside of the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented. The steps of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module (e.g., including executable instructions and related data) and other data may reside in a data memory such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a “processor”) such the processor can read information (e.g., code) from and write information to the storage medium. A sample storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in user equipment. In the alternative, the processor and the storage medium may reside as discrete components in user equipment. Alternatively and/or additionally, in some aspects any suitable computer-program product may comprise a computer-readable medium comprising codes relating to one or more of the aspects of the disclosure. In some aspects a computer program product may comprise packaging materials. While the disclosed subject matter has been described in connection with various aspects, it will be understood that the disclosed subject matter is capable of further modifications. This application is intended to cover any variations, uses or adaptation of the disclosed subject matter following, in general, the principles of the disclosed subject matter, and including such departures from the present disclosure as come within the known and customary practice within the art to which the disclosed subject matter pertains. | 139,424 |
11943764 | DETAILED DESCRIPTION As presented in the background section, 3GPP is working at the next releases for the 5th generation cellular technology, simply called 5G, including the development of a new radio (NR) access technology operating in frequencies ranging up to 100 GHz. 3GPP has to identify and develop the technology components needed for successfully standardizing the NR system timely satisfying both the urgent market needs and the more long-term requirements. In order to achieve this, evolutions of the radio interface as well as radio network architecture are considered in the study item “New Radio Access Technology.” Results and agreements are collected in the Technical Report TR 38.804 v14.0.0, incorporated herein in its entirety by reference. Among other things, there has been a provisional agreement on the overall system architecture. The NG-RAN (Next Generation-Radio Access Network) consists of gNBs, providing the NG-radio access user plane, SDAP/PDCP/RLC/MAC/PHY (Service Data Adaptation Protocol/Packet Data Convergence Protocol/Radio Link Control/Medium Access Control/Physical) and control plane, RRC (Radio Resource Control) protocol terminations towards the UE. The NG-RAN architecture is illustrated inFIG.1, based on TS 38.300 v.15.0.0, section 4 incorporated herein by reference. The gNBs are interconnected with each other by means of the Xn interface. The gNBs are also connected by means of the Next Generation (NG) interface to the NGC (Next Generation Core), more specifically to the AMF (Access and Mobility Management Function) (e.g., a particular core entity performing the AMF) by means of the NG-C interface and to the UPF (User Plane Function) (e.g., a particular core entity performing the UPF) by means of the NG-U interface. Various different deployment scenarios are currently being discussed for being supported, as reflected, e.g., in 3GPP TR 38.801 v14.0.0, “Study on new radio access technology: Radio access architecture and interfaces.” For instance, a non-centralized deployment scenario (section 5.2 of TR 38.801; a centralized deployment is illustrated in section 5.4 incorporated herein by reference) is presented therein, where base stations supporting the 5G NR can be deployed.FIG.2illustrates an exemplary non-centralized deployment scenario and is based on FIG. 5.2.-1 of said TR 38.801, while additionally illustrating an LTE eNB as well as a user equipment (UE) that is connected to both a gNB and an LTE eNB. As mentioned before, the new eNB for NR 5G may be exemplarily called gNB. As also mentioned above, in 3rd generation partnership project new radio (3GPP NR), three use cases are being considered that have been envisaged to support wide variety of services and applications by IMT-2020 (see Recommendation ITU-R M.2083: IMT Vision—“Framework and overall objectives of the future development of IMT for 2020 and beyond,” September 2015). The specification for the phase1of enhanced mobile-broadband (eMBB) has been concluded by 3GPP in December 2017. In addition to further extending the eMBB support, the current and future work would involve the standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications.FIG.3(from the Recommendation ITU-R M.2083) illustrates some examples of envisioned usage scenarios for IMT for 2020 and beyond. The URLLC use case has stringent requirements for capabilities such as throughput, latency and availability and has been envisioned as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, remote medical surgery, distribution automation in a smart grid, transportation safety, etc. In the current WID (work item description) RP-172115, it is agreed to support the ultra-reliability for URLLC by identifying the techniques to meet the requirements set by TR 38.913. For NR URLCC in Release 15, key requirements include a target user plane latency of 0.5 ms for UL (uplink) and 0.5 ms for DL (downlink). The general URLLC requirement for one transmission of a packet is a BLER (block error rate) 1E-5 for a packet size of 32 bytes with a user plane of 1 ms. From RAN 1 perspective, reliability can be improved in a number of possible ways. The current scope for improving the reliability is captured in RP-172817 that includes defining of separate CQI tables for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, the scope may widen for achieving ultra-reliability as the NR becomes more stable and developed (for NR URLCC key requirements, see also 3GPP TR 38.913 V15.0.0, “Study on Scenarios and Requirements for Next Generation Access Technologies“incorporated herein by reference). Accordingly, NR URLLC in Rel. 15 should be capable of transmitting 32 bytes of data packet within a user-plane latency of 1 ms at the success probability corresponding to a BLER of 1E-5. Particular use cases of NR URLCC in Rel. 15 include Augmented Reality/Virtual Reality (AR/VR), e-health, e-safety, and mission-critical applications (see also ITU-R M.2083-0). Moreover, technology enhancements targeted by NR URLCC in Release 15 aim at latency improvement and reliability improvement. Technology enhancements for latency improvement include configurable numerology, non slot-based scheduling with flexible mapping, grant free (configured grant) uplink, slot-level repetition for data channels, and downlink pre-emption. Pre-emption means that a transmission for which resources have already been allocated is stopped, and the already allocated resources are used for another transmission that has been requested later, but has lower latency/higher priority requirements. Accordingly, the already granted transmission is pre-empted by a later transmission. Pre-emption is applicable independent of the particular service type. For example, a transmission for a service-type A (URLCC) may be pre-empted by a transmission for a service type B (such as eMBB). Technology enhancements with respect to reliability improvement include dedicated CQI/MCS tables for the target BLER of 1E-5 (for the technology enhancements, see also 3GPP TS 38.211“NR; Physical channels and modulation,” TS 38.212“NR; Multiplexing and channel coding,” TS 38.213“NR; Physical layer procedures for control,” and TS 38.214“NR; Physical layer procedures for data,” respective versions V15.4.0, all incorporated herein by reference). The use case of mMTC is characterized by a very large number of connected devices typically transmitting a relatively low volume of non-delay sensitive data. Devices are required to be low cost and to have a very long battery life. From NR perspective, utilizing very narrow bandwidth parts is one possible solution to have power saving from UE perspective and enable long battery life. As mentioned above, it is expected that the scope of reliability in NR becomes wider. One key requirement to all the cases and especially necessary for URLLC and mMTC is high reliability or ultra-reliability. Several mechanisms can be considered to improve the reliability from radio perspective and network perspective. In general, there are few key potential areas that can help improve the reliability. Among these areas are compact control channel information, data/control channel repetition, and diversity with respect to frequency, time and/or the spatial domain. These areas are applicable to reliability in general, regardless of particular communication scenarios. For NR URLLC Rel. 16, further use cases with tighter requirements have been identified such as factory automation, transport industry and electrical power distribution, including factory automation, transport industry, and electrical power distribution (see RP-181477, “New SID on Physical Layer Enhancements for NR URLLC,” Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, incorporated herein by reference). The tighter requirements are higher reliability (up to 10-6 level), higher availability, packet sizes of up to 256 bytes, time synchronization down to the order of a few ns where the value can be one or a few ns depending on frequency range and short latency in the order of 0.5 to 1 ms in particular a target user plane latency of 0.5 ms, depending on the use cases (see also 3GPP TS 22.261“Service requirements for next generation new services and markets” V16.4.0, incorporated herein by reference and RP-181477). Moreover, for NR URLCC in Rel. 16, several technology enhancements from RANI perspective have been identified. Among these are PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, increased PDCCH monitoring. Moreover, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. Also PUSCH enhancements related to mini-slot level hopping and retransmission/repetition enhancements have been identified. The term “mini-slot” refers to a Transmission Time Interval (TTI) including a smaller number of symbols than a slot (a slot comprising fourteen symbols). In general, TTI determines the timing granularity for scheduling assignment. One TTI is the time interval in which given signals is mapped to the physical layer. Conventionally, the TTI length can vary from 14-symbols (slot-based scheduling) to 2-symbols (non-slot based scheduling). Downlink and uplink transmissions are specified to be organized into frames (10 ms duration) consisting of 10 subframes (1 ms duration). In slot-based transmission, a subframe, in return, is divided into slots, the number of slots being defined by the numerology/subcarrier spacing and the specified values range between 10 slots for a subcarrier spacing of 15 kHz to 320 slots for a subcarrier spacing of 240 kHz. The number of OFDM symbols per slot is 14 for normal cyclic prefix and 12 for extended cyclic prefix (see section 4.1 (general frame structure), 4.2 (Numerologies), 4.3.1 (frames and subframes) and 4.3.2 (slots) of the 3GPP TS 38.211 V15.4.0, incorporated herein by reference). However, assignment of time resources for transmission may also be non-slot based. In particular, the TTIs in non slot-based assignment may correspond to mini-slots rather than slots. E.g., one or more mini-slots may be assign to a requested transmission of data/control signaling. In non slot-based assignment, the minimum length of a TTI may conventionally be 2 OFDM symbols. Other identified enhancements are related to scheduling/HARQ/CSI processing timeline and to UL inter-UE Tx prioritization/multiplexing. Further identified are UL configured grant (grant free) transmissions, with focus on improved configured grant operation, example methods such as explicit HARQ-ACK, ensuring K repetitions and mini-slot repetitions within a slot, and other MIMO (Multiple Input, Multiple Output) related enhancements (see also 3GPP TS 22.261 V16.4.0). The present disclosure is related to the potential layer1enhancements for further improved reliability/latency and for other requirements related to the use cases identified in (RP-181477, “New SID on Physical Layer Enhancements for NR URLLC,” Huawei, HiSilicon, Nokia, Nokia Shanghai Bell). Specifically, enhancements for PUSCH (Physical Uplink Shared CHannel) repetition are discussed. The impact of the proposed ideas in this disclosure is expected to be on PUSCH repetition enhancements which is within the main scope of new SI (study items)/WI (work items) on NR URLLC in Rel. 16. PUSCH Repetition One of the scopes for potential enhancements is related to mini-slot repetition of PUSCH within a slot. In the following, a motivation for supporting repetition of PUSCH within a slot is provided which may allow for potential enhancements to the repetition mechanism for further improving the reliability and/or latency to satisfy the new requirements of NR URLLC. To achieve the latency requirement for URLLC PUSCH transmission, one-shot transmission (e.g., single (TTI) assignment) is ideal, provided the reliability requirement is satisfied. However, it is not always the case that the target BLER of 1E-6 is achieved with one-shot transmission. Therefore, retransmission or repetition mechanisms are required. In NR Rel.15, both retransmissions and repetitions are supported to achieve the target BLER, when one-shot transmission is not enough. HARQ-based retransmission is well known to improve the overall reliability, by using the feedback information and improving the subsequent retransmissions according to the channel conditions. However, they suffer from additional delay due to feedback processing timeline. Therefore, repetitions are useful for highly delay-tolerant services, as they do subsequent transmission of the same transport blocks without waiting for any feedback. A PUSCH repetition can be defined as “transmitting a same transport block more than once, without waiting for any feedback of previous transmission(s) of the same transport block.” Advantages of PUSCH retransmissions are an improvement in the overall reliability and a reduction in latency in comparison with HARQ, as no feedback is required. However, in general, no link adaptation is possible, and resource usage may be inefficient. In NR Rel. 15, limited support for repetitions is introduced. Only semi-static configurations of repetitions are allowed. Moreover, repetitions are allowed only between slots (slot level PUSCH repetition). A repetition is only possible in the slot following the slot of the previous transmission. Depending up on the numerology and service type (e.g., URLCC, eMBB), latency between the repetitions can be too long for inter-slot repetition. Such limited support of repetition is mainly useful for PUSCH mapping type A. This PUSCH mapping type A only allow PUSCH transmissions starting from the beginning of the slot. With repetitions, this would result in an initial PUSCH transmission and each repetition stating at the beginning of plural consecutive slots. Less useful is the limited support of repetition for a PUSCH mapping type B. PUSCH mapping type B allows PUSCH transmissions to start at any symbol within a slot. With repetitions, this would result in an initial PUSCH transmission and each repetition starting within a slot, at a same symbol of plural consecutive slots. In any case, such limited support may not be able to achieve stricter latency requirements in NR Rel. 15, e.g., up to 0.5 ms latency. This would require mini-slot repetitions. Additionally, the limited support of repetitions does also not exploit the benefits resulting from mini-slots, namely, transmission time intervals (TTIs) including a smaller number of symbols than a slot (a slot comprising fourteen symbols). PUSCH Assignments Another of the scopes for potential enhancements is related to the mini-slot assignments of PUSCH within a slot. In the following, a motivation for supporting assignments of different PUSCH transmissions within a slot is provided which may allow for potential enhancements to the uplink usage for further improving the latency while meeting the reliability requirements to further satisfy new requirements of NR URLLC. To achieve the latency requirement for URLLC PUSCH transmission, again a one-shot transmission (e.g., single (TTI) assignment) is ideal, provided the reliability is satisfied. However, it is not always the case that the target user plane latency of 0.5 ms is achieved for concurrent PUSCH transmissions. Therefore, enhancements to the uplink assignments are required. In NR Rel. 15, uplink scheduling is constrained to a single uplink grant per TTI. In case of a single PUSCH transmission, this scheduling constraint is not a restriction and the target user plane latency may be achieved through a one-shot transmission. However, for concurrent PUSCH transmissions, the scheduling constraint results in that one-shot transmissions may not be enough to meet the target user plane latency. In particular, concurrent PUSCH transmissions demand for separate uplink grants which, however, due to the scheduling constraints must be signaled in consecutive TTIs. Thus, this scheduling constraint introduces unnecessary delay in case of concurrent PUSCH transmissions. Also, plural mini-slot assignments of PUSCH within a slot are also not possible. In any case, due to such scheduling constraint, it may not be able to achieve stricter latency requirements in NR Rel. 15, e.g., up to 0.5 ms latency. This would require mini-slot assignments of PUSCH. Additionally, the limited support of repetitions does also not exploit the benefits resulting from mini-slots, namely, transmission time intervals (TTIs) including a smaller number of symbols than a slot (a slot comprising fourteen symbols). Generic Scenario for Uplink Considering the above, the authors of the present disclosure have recognized that there is a need for more flexible support of PUSCH transmissions, namely for a mechanism which is not restricted to PUSCH transmissions which require separate uplink grants. At a same time, the more in flexibility shall not come at the expense of additional signaling overhead. In other words, the authors of the present disclosure have recognized that the flexible support of PUSCH transmissions shall not require modifications to the present uplink scheduling mechanism, namely the present format of the uplink grant. In other words, the signaling mechanism, e.g., in form of downlink control information (DCI) format 0-0 or 0-1 for conveying an uplink grant, shall stay the same, thereby avoiding any additional signaling overhead when scheduling the PUSCH transmissions. It is therefore a proposal of the present disclosure that transport block (TB) transmissions shall be supported with flexible timings which do not necessarily create additional signaling overhead. The following disclosure has been presented with a focus on uplink transmissions. Nevertheless, this shall not be construed as a limitation since the concepts disclosed herein can equally be applied to downlink transmissions. FIG.4shows an exemplary communication system including a user equipment (UE)410and a base station (BS)460in a wireless communication network. Such communication system may be a 3GPP system such as NR and/or LTE and/or UMTS. For example, as illustrated in the figure, the base station (BS) may be a gNB (gNodeB, e.g., an NR gNB) or an eNB (eNodeB, e.g., an LTE gNB). However, the present disclosure is not limited to these 3GPP systems or to any other systems. Even though the embodiments and exemplary implementations are described using some terminology of 3GPP systems, the present disclosure is also applicable to any other communication systems, and in particular in any cellular, wireless and/or mobile systems. Rather, it should be noted that many assumptions have been made herein so as to be able to explain the principles underlying the present disclosure in a clear and understandable manner. These assumptions are however to be understood as merely examples for illustration purposes and should not limit the scope of the disclosure. A skilled reader will be aware that the principles of the following disclosure and as laid out in the claims can be applied to different scenarios and in ways that are not explicitly described herein. A mobile terminal is referred to in the LTE and NR as a user equipment (UE). This may be a mobile device such as a wireless phone, smartphone, tablet computer, or an USB (universal serial bus) stick with the functionality of a user equipment. However, the term mobile device is not limited thereto, in general, a relay may also have functionality of such mobile device, and a mobile device may also work as a relay. A base station (BS) forms at least part of a system of interconnected units, for instance a (central) baseband unit and different radio frequency units, interfacing different antenna panels or radio heads in the network for providing services to terminals. In other words, a base station provides wireless access to terminals. Referring back to the figure, the user equipment410comprises processing circuitry (or processor)430and a transmitter/receiver (or transceiver)420which are indicated as separate building blocks in the diagram. Similarly, base station460, comprises processing circuitry (or processor)480and a transmitter/receiver (or transceiver)470, which are indicated as separate building blocks in the diagram. The transmitter/receiver420of the user equipment410is communicatively coupled via a radio link450with the transmitter/receiver470of the base station460. First Generic Uplink Scenario FIGS.5and6depict exemplary implementations according to a first generic scenario of the building blocks of the user equipment410and of the base station460, respectively. The user equipment410of the exemplary implementation comprises a PUSCH config IE receiver520-a, a table configuring processing circuitry530-a, a DCI receiver520-b, a configured grant config IE receiver520-c, an allocated resources determining processing circuitry530-b, a transport block selecting transmitter520-d, a PUSCH transmissions generating transmitter520-e, and a PUSCH transmitter520-f. Similarly, the base station460of the exemplary implementation comprises a PUSCH config IE transmitter570-a, a table configuring processing circuitry580-a, a DCI transmitter570-b, a configured grant config IE transmitter570-c, a resource allocating processing circuitry580-b, and PUSCH receiver570-d. In general, the present disclosure assumes that the user equipment410is in communication reach of the base station460and is configured with at least one bandwidth part in the downlink and at least one bandwidth part in the uplink. The bandwidth parts are located within the carrier bandwidth served by the base station460. Further, the present disclosure assumes that the user equipment410is operating in a radio resource control, RRC, connected state (termed: RRC_CONNECTED), thereby capable of receiving in the downlink data and/or control signals from the base station460and capable of transmitting in the uplink data and/or control signals to the base station460. Before performing plural PUSCH transmissions as suggested in the present disclosure, the user equipment410receives control messages as defined in the radio resource control, RRC, and the medium access control, MAC, protocol layer. In other words, the user equipment410employs signaling mechanism which is readily available in the different protocol layers of the various communication technologies. In general, a substantial difference is made between control messages defined in RRC and those defined in MAC. This difference becomes already aware from the fact that RRC control messages are usually used for configuration of radio resources (e.g., radio link) on a semi-static basis whereas MAC control messages are used for dynamically defining each medium access (e.g., transmission) separately. From this, it directly follows that RRC control occurs less frequently than MAC control. Accordingly, an excessive MAC control signaling overhead can substantially impair the communication system performance whereas the RRC control message has been treated more leniently in standardization. In other words, MAC control signaling overhead is a well-recognized constraint to the system performance. Considering the above, the authors of the present disclosure propose a mechanism which overcomes the disadvantages of conventional mechanisms and permits flexible transport block (TB) transmissions in uplink or downlink, while—at a same time—avoiding MAC signaling overhead. In the context of the disclosure, the term “transport block” is to be understood as data unit of an uplink and/or downlink transmission. For example, it is widely understood that the term “transport block” is equivalent to a MAC layer packed data unit, PDU. Thus, the transmission of transport block is equally understood as a physical uplink shared channel (PUSCH) and/or physical downlink shared channel (PDSCH) transmission. Particularly, since PUSCH and/or PDSCH transmissions generally carry payload, the present disclosure shall refer to PUSCH and/or PDSCH transmissions carrying a MAC PDU. In other words, the terms “PUSCH and/or PDSCH transmissions” shall be understood as describing MAC PDU transmission on PUSCH and/or PDSCH. Referring toFIG.7, a generic scenario is described with regard to performing plural PUSCH transmissions based on a dynamic grant, namely a DCI carrying a time-domain resource assignment filed, such as, for example, a DCI of DCI format 0-0 or of DCI format 0-1. This description shall, however, not be understood as a restriction to the present disclosure to only extend to PUSCH transmissions, for example to repetitions thereof. Rather, it will become apparent that the concepts disclosed herein can equally be applied to downlink transmissions The receiver420of the user equipment410receives (see, e.g., step710—FIG.7) a physical uplink shared channel, PUSCH, config information element, IE. This PUSCH config IE is received in form of radio resource control, RRC, signaling and applicable to a particular bandwidth part. The PUSCH config IE is received from the base station460serving the particular bandwidth part. For example, this reception operation may be performed by the PUSCH config IE receiver520-aofFIG.5. The PUSCH config IE carries among others a list of parameters in form of an information element (IE) termed “PUSCH-TimeDomainResourceAllocationList,” wherein each parameter of the list of parameters is termed “PUSCH-TimeDomainResourceAllocation.” Then, the processor430of the user equipment410configures (see, e.g., step720—FIG.7) a table which is defined by the PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The configured table includes at least one row comprising a first set of values related to allocated time-domain resources for plural PUSCH transmission. For example, the table includes rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator. For example, this configuration operation may be performed by the table configuring processing circuitry530-aofFIG.5. In an exemplary implementation, each row of the RRC configure table corresponds to one of plural parameters termed “PUSCH-TimeDomainResourceAllocation” of the list of parameters termed “PUSCH-TimeDomainResourceAllocationList.” This shall, however, not be understood as a limitation to the present disclosure, as apparent from the following alternative. Also scenarios different from the exemplary implementation are conceivable, namely where some rows of the configured table correspond to respective parameters comprised in the IE with the list of parameters, and other rows are configured complying with a set of pre-specified rules readily applying the principles laid out PUSCH time domain resource allocation list IE. This shall, however, not distract from the fact that the RRC configured table in its entirety is defined by the PUSCH time domain resource allocation list IE. Subsequently, the receiver420of the user equipment410receives (see, e.g., step730—FIG.7) downlink control information, DCI, signaling. The DCI is carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the configured table. For example, this reception operation may be performed by the DCI receiver520-bofFIG.5. In the context of the present disclosure, this DCI is carrying an uplink grant since it serves the purpose of triggering PUSCH transmissions. In this respect, the received DCI is in DCI format 0-0 or in DCI format 0-1. Also, the described scenario refers to situation where the PUSCH repetitions are scheduled by a dynamic grant. This shall, however, not be understood as limitation to the present disclosure, as the concepts disclosed herein are equally applicable to a configured grant or grant free scheduling technique. A detailed description of this grant free scheduling technique is given as an alternative to the mechanism depicted inFIG.7. Subsequently, the processor430of the user equipment410determines allocated resources for the plural PUSCH transmissions. For sake of clarity and brevity, the following description focusses on the allocation of resources in time domain. For example, this determination operation may be performed by the allocated resources determining processing circuitry530-bofFIG.5. The time-domain resources to be used by the user equipment410for the plural PUSCH transmissions have been previously allocated by the base station460. In this context, the processor430accordingly determines which of the previously allocated resource it shall use for the plural PUSCH transmissions. For easy reference, the plural PUSCH transmissions may be understood to include a first PUSCH transmission and at least one subsequent PUSCH transmission which are all being scheduled by a single DCI. As part of this determination operation, the processor430determines (see, e.g., step740—FIG.7) the allocated time-domain resources for a first of the plural PUSCH transmission based on: (i) index of a slot carrying the received DCI, and (ii) the first set of values that is related to allocated time-domain resources and comprised in the indexed row of the RRC configured table. For example, the processor430may determine the allocated time-domain resource for a first PUSCH transmission based on: (i) index of a slot carrying the received DCI, and (ii) the value K2indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. This implies that the processor430has previously determined that the value indicating the PUSCH mapping type indicates a type B mapping (only when the PUSCH transmission is permitted to start at any symbol within a slot, then it is necessary to base the determination on the value SLIV). Further to this example, let us assume the received DCI was carried in a slot which has the number k, and further the DCI has a time-domain resource assignment filed with value m. Then, the processor, for the first PUSCH transmission, reverts to the RRC configured table in row with row index m+1 and uses the respective values K2indicating the slot offsets, and SLIV indicating the start and length indicator. With these value, the processor determines that the allocated time-domain resources, for the first PUSCH transmission, are included in a slot with a number of k+K2, and have a start and length in terms of symbols of this slot corresponding to the value SLIV. When determining the allocated resources in this example, the processor430may also use the value indicating the PUSCH mapping type additionally comprised in the first set of values. Particularly, in case the value indicates a type A PUSCH mapping, the processor430only uses the length of the value SLIV indicating a start and length indicator. In case the value indicates a type B PUSCH mapping, the processor430uses both the start and the length of the value SLIV indicating the start and length indicator. Then, the processor430proceeds with its operation for the subsequent PUSCH transmissions. For this, the processor430checks (see, e.g., step750—FIG.7) a second parameter which indicates to the user equipment410whether the subsequent PUSCH transmissions are either different (or separate) PUSCH transmissions or whether they are repeated PUSCH transmissions. In other words, the second parameter instruct the processor430how the subsequent PUSCH transmissions are to be utilized, namely for carrying different or a same transport block(s). In the mechanism depicted inFIG.7, the first of the plural PUSCH transmissions is understood to always be a unique, e.g., different (or separate) PUSCH transmission. Thus, the second parameter is left to specify only in how far the subsequent PUSCH transmissions differ (or not) from this first (or any other preceding) PUSCH transmission. In this regard, the processor430may perform the checking of the second parameter after it has completed its operation for the first PUSCH transmission. It shall be emphasized in this context that the second parameter is comprised in a row of the RRC configured table which is defined by the PUSCH time domain resource allocation list IE. In other words, since the (entire) RRC configure table is defined by the PUSCH time domain resource allocation list IE, then also the second parameter comprised therein is defined by the PUSCH time domain resource allocation list IE. This shall, however, not be understood as a limitation to the present disclosure, as the concepts disclosed herein are equally applicable to a second parameter which uniformly specifies the difference (or not) among all of the plural PUSCH transmissions, namely whether all PUSCH transmissions are different or repeated PUSCH transmissions. Then, a different sequence of operation by the processor430is also possible. Although discussed in further detail below, according to one exemplary implementation the processor430may, for checking the second parameter, revert to the row with row index m+1 of the RRC configured table and check whether or not this row, comprises the second parameter. However, according to other exemplary implementations, the processor430may also employ to the received DCI or to a physical layer configuration for checking whether the second parameter indicates either different or repeated PUSCH transmissions. In case the check indicates different (or separate) PUSCH transmissions, then the sequence of operations of the mechanism depicted inFIG.7proceeds with the processor430determining (see, e.g., step770—FIG.7) allocated time-domain resources for the subsequent (not the first) transmissions in form of different (or separate) PUSCH transmissions. In the mechanism depicted inFIG.7, the processor430not necessarily determines the time-domain resources based on an explicit indication which is signaled from the base station460to the user equipment410. Instead, the processor430may also rely on pre-specified (e.g., in the relevant standard fixedly prescribed) timing relations between the first PUSCH transmission and subsequent PUSCH transmissions for determining the time-domain resources for the different (or separate) PUSCH transmissions. Also, the processor430may determine the time-domain resources by applying the same timing relations as specified in the first set of values to a consecutive number of slots for the subsequent PUSCH transmissions. This results in a first PUSCH transmission and each subsequent PUSCH transmission starting at a same symbol and having a same symbol length of plural consecutive slots This shall, however, not be understood as a limitation to the present disclosure, as apparent from the following alternative. In case the check indicates repeated PUSCH transmissions, then the sequence of operations of the mechanism depicted inFIG.7proceeds with the processor430checking (see, e.g., step755—FIG.7) if there exists (explicit) time-domain resource assignments for the subsequent PUSCH transmissions in form of repeated transmissions of the first (or any other preceding) PUSCH transmission. For this, the processor430checks (see, e.g., step755—FIG.7) if there exists a third set of values related to (explicit) time-domain resource assignments for the subsequent PUSCH transmissions. For this, the processor430reverts to the row with row index m+1 and checks whether or not this row comprises the third set of values (e.g., at least one value) which are specifying the allocated time-domain resource for the subsequent PUSCH transmissions in form of repeated PUSCH transmissions. In case the check is negative, the processor430uses (see, e.g., step760—FIG.7) a conventional slot-based repetition mechanism for the repetition of the first PUSCH transmission, if configured. In other words, the processor430relies on pre-specified (e.g., in the relevant standard fixedly prescribed) timing relations between the first PUSCH transmission and the repetitions thereof. For example, this results in a first PUSCH transmission and each repetition starting at a same symbol and having a same symbol length of plural consecutive slots. Referring back to the example, the processor430, for the at least one subsequent PUSCH transmission, reverts to the row with row index m+1 of the RRC configured table, and determines that the allocated resources, for the first repetition of the first PUSCH transmission, are included in a slot with number k+K2+1 (where 1 is a pre-defined constant fixed by standardization), and have a start and length in terms of symbols of this slot corresponding to the same value SLIV. Should there be a second repetition, the processor430that the allocated resources, for the second repetition of the initial PUSCH transmission, are included in a slot with number k+K2+2 (where 2 is again a pre-defined constant fixed by standardization), and have a start and length in terms of symbols of this slot corresponding to the same value SLIV as already the initial PUSCH transmission and the first repetition thereof. Further repetitions follow at contiguous slots. Further to this example, when assuming that the PUSCH mapping type indicted in the row with row index m+1 is type B, and when assuming that the value SLIV indicates a start at symbol 4 and a length of 4 symbols, then the processor430determines that each one of the initial, the first repetition and the second repetition of the PUSCH transmission have resources corresponding to symbol 4, symbol 5, symbol 6 and symbol 7 in the slots with number k+K2, number k+K2+1, number k+K2+2, respectively. Evidently, these allocated resources as determined by the processor430cannot be flexibly configured. This is overcome by the alternative determination by the processor430. In case the check is positive, the processor430uses (see, e.g., step770—FIG.7) the third set of values (e.g., at least one value) comprised in the indexed row of the RRC configure table for determining allocated resources for the repetition of the first PUSCH transmission in its subsequent PUSCH transmissions. In other words, the comprised third set of values is specifying the allocated time domain resource for the repetition of the initial PUSCH transmission. It shall be emphasized in this context that the third set of values (e.g., at least one value) is comprised in a row of the RRC configured table which is defined by the PUSCH time domain resource allocation list IE. In other words, since the (entire) RRC configure table is defined by the PUSCH time domain resource allocation list IE, then also the third set of values comprised therein is defined by the PUSCH time domain resource allocation list IE. To meet this constrains, the third set of values could be (directly) prescribed by a parameter comprised in the PUSCH time domain resource allocation list IE, or alternatively the third set of values could be (indirectly) inferred from related parameters comprised in the PUSCH time domain resource allocation list IE. In any case, the third set of values specifies in time domain the repetition of the initial PUSCH transmission. In one exemplary implementation, for the third set of values, a value SLIV′ indicating another start and length indicator may be (indirectly) inferred by the processor430from modified SLIV parameters comprised in the PUSCH time domain resource allocation list IE. A modified SLIV parameter is provided, for example, with twice, three times, . . . the number of bits (e.g., 14 bits instead of 7 bits, or also 21 bits instead of 7 bits, or so on). Thereby, this modified SLIV parameter may be used by the processor430to (indirectly) infer, when configuring the table, the value SLIV included in the first set of values, and the value SLIV′, included in the third set of values of the RRC configured table. It is important to realize that the processor430of the user equipment410uses the third set of values from the indexed row of the RRC configured table for determining the allocated time-domain resources for the repetitions of the first PUSCH transmission. This approach substantially differs from the conventional slot-based repetition mechanism. Although not depicted inFIG.7, in an alternative mechanism the processor430may also use the third set of values from the indexed row of the RRC configured table for determining the allocated time-domain resource for subsequent PUSCH transmissions in form of different (or separate) PUSCH transmissions. Thus, the third set of values is not restricted in its use for repeated PUSCH transmission. For this alternative mechanism, the processor430deviates from mechanism depicted inFIG.7, after the check of the second parameter (see, e.g., step750—FIG.7) indicates different (or separate) PUSCH transmissions, namely by thereafter checking (similar to, e.g., step755—FIG.7) if there exists a third set of values related to (explicit) time-domain resource assignments. With this check, the mechanism differs from what is depicted inFIG.7. The difference applies only to the case that different (or separate) PUSCH transmissions are being indicated. If this check is positive, then processor430then uses the third set of values for determining the allocated time-domain resource also for subsequent PUSCH transmissions in form of different (or separate) PUSCH transmissions. This is different for the following reasons:Firstly, the third set of values comes from a row of the RRC configured table which is (actively) indexed by the row index m+1 derived from value m in the time-domain resource assignment field of the received DCI. In this respect, varying index values m in the in the time-domain resource assignment field of the received DCI permit a varying third set of values to be used for determining the allocated time-domain resources for the subsequent PUSCH transmissions. Thereby, the flexibility of such allocated resources is increased.Secondly, the third set of values comes from a (same) row of the RRC configured table which is (already) indexed by the row index m+1 derived from value m in the time-domain resource assignment field of the received DCI. In this respect, no additional index value is required than then index value m in the in the time-domain resource assignment field of the received DCI when determining the allocated resources for the subsequent PUSCH transmission. Thereby, any additional signaling overhead is avoided. Consequently, this permits increasing flexibility while avoiding signaling overhead, namely by the processor430of the user equipment410using the third set of values from the indexed row of the RRC configured table for determining the allocated resources for the repetitions. Thereafter, the transmitter420of the user equipment410selects the transport blocks of data (see, e.g., step780—FIG.7) to be carried in the plural PUSCH transmissions including the first and subsequent PUSCH transmissions. This selection of transport blocks of data is based on the second parameter. In the case that the second parameter indicates different (or separate) PUSCH transmissions, the transmitter420selects a different transport block of data for each of the plural PUSCH transmissions. In case that the second parameter indicates repeated PUSCH transmissions, the transmitter420selects a same transport block of data for all of the plural PUSCH transmissions. For example, this selection operation may be performed by the transport blocks selecting transmitter520-dofFIG.5. Then, the transmitter420generates (see, e.g., step790—FIG.7) the plurality of PUSCH transmissions carrying the selected transport blocks of data. For example, this generation operation may be performed by the PUSCH transmissions generating transmitter520-eofFIG.5. In exemplary implementations, this generation operation may be based on at least one fourth value in the indexed row of the RRC configured table which are related to the generation of the plurality of plural PUSCH transmissions as will be discussed in further detail below. Also the generation operation may adhere to at least one fifth parameter in the indexed row of the RRC configured table which are also related to the generation of the plurality of PUSCH transmissions as will again be discussed in further detail below. Finally, the transmitter420of the user equipment410transmits (not depicted inFIG.7) a PUSCH transmission using the respectively determined allocated resources for the first and subsequent PUSCH transmission, namely either in the form of different (or separate) PUSCH transmissions or in the form of repeated PUSCH transmissions. For example, this transmission operation may be performed by the PUSCH transmitter520-fofFIG.5. In summary, a mechanism is disclosed which facilitates alleviating the uplink scheduling constraints resulting from one uplink grant per TTI. For this purpose, the RRC configure table permits the user equipment410, despite having received only a single DCI with an uplink grant, to transmit plural PUSCH transmission, be it in the form of different (or separate) PUSCH transmissions, or be it in the form of repeated PUSCH transmissions. Thereby, the present disclosure permits a more flexible support of PUSCH transmissions, namely enabling a mechanism which is not restricted to separate PUSCH transmissions which require separate uplink grants in consecutive TTIs. This mechanism may be combined, as discussed before, with the possibility to indicate (explicit) time-domain resource assignments for the subsequent PUSCH transmissions. Consequently, an increasing flexibility is facilitated while avoiding signaling overhead, namely by the processor430of the user equipment410using the third set of values from the indexed row of the RRC configured table for determining the allocated resources for the repetitions. The above description has been given from the perspective of the user equipment410. This shall, however, not be understood as a limitation to the present disclosure. The base station460equally performs the generic scenario disclosed herein. The transmitter470of the base station460transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling. The PUSCH config IE being applicable to a particular bandwidth part. For example, this transmission operation may be performed by the PUSCH config IE transmitter670-aofFIG.6. Then, the processor480of the base station460configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions. For example, this configuration operation may be performed by the table configuring processing circuitry680-aofFIG.6. Subsequently, the transmitter470of the base station460transmits downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table. For example, this transmission operation may be performed by the DCI transmitter670-bofFIG.6. The processor480of the base station460allocates time-domain resources for the plurality of PUSCH transmissions based on: (i) index of a slot carrying the transmitted DCI, and (ii) the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table. For example, this resource allocation operation may be performed by the resource allocating processing circuitry680-bofFIG.6. Then, the receiver470of the base station460receives the plurality of PUSCH transmissions using the respectively allocated time-domain resources. For example, this reception operation may be performed by the PUSCH receiver670-dofFIG.6. Further, the receiver470of the base station460processes transport blocks of data which are carried in the plurality of received PUSCH transmissions. For example, this processing operation may be performed by the Transport block processing receiver670-eofFIG.6. In particular, the transport blocks of data are processed based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. Now, a generic scenario is described with regard to performing PUSCH repetitions based on a configured grant (or grant free), namely a configured grant config IE received in form of RRC signaling, and also comprising a PUSCH time domain resource allocation list IE. The receiver420of the user equipment410receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling. The PUSCH config IE is applicable to a particular bandwidth part. The PUSCH config IE is received from the base station460serving the particular bandwidth part. For example, the reception operation may be performed by the PUSCH config IE receiver520-aofFIG.5. Then, the processor430of the user equipment410configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions. For example, this configuration operation may be performed by the table configuring processing circuitry530-aofFIG.5. Subsequently, the receiver420of the user equipment410receives a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the configured table. For example, this reception operation may be performed by the configured grant config IE receiver520-cofFIG.5. The processor430of the user equipment410determines allocated resources for the plurality of PUSCH transmissions based on: (i) a value of a time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and (ii) the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table. For example, this determination operation may be performed by the allocated resources determining processing circuitry530-bofFIG.5. Then, the transmitter420of the user equipment410selects transport blocks of data to be carried in the plurality of PUSCH transmissions. For example, this selection operation may be performed by the transport blocks selecting transmitter520-dofFIG.5. In particular, the transport blocks of data are selected based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. Finally, the transmitter420of the user equipment410transmits a PUSCH transmission using the respectively determined allocated resources. For example, this transmission operation may be performed by the PUSCH transmitter520-fofFIG.5. The above description has been given from the perspective of the user equipment410. This shall, however, not be understood as a limitation to the present disclosure. The base station460equally performs the generic scenario disclosed herein. The transmitter470of the base station460transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part. For example, this transmission operation may be performed by the PUSCH config IE transmitter670-aofFIG.6 Then, the processor480of the base station460configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions. For example, this configuration operation may be performed by the table configuring processing circuitry680-aofFIG.6. Subsequently, the transmitter470of the base station460transmits a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the RRC configured table. For example, this transmission operation may be performed by the configured grant config IE transmitter670-cofFIG.6. The processor480of the base station460allocates resources for a plurality of PUSCH transmissions based on: (i) a value of time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and (ii) the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table. For example, this resource allocation operation may be performed by the resource allocating processing circuitry680-bofFIG.6. Then, the receiver470of the base station460receives the plurality of PUSCH transmissions using the respectively allocated time-domain resources. For example, this reception operation may be performed by the PUSCH receiver670-dofFIG.6. Further, the receiver470of the base station460processes transport blocks of data which are carried in the plurality of received PUSCH transmissions. For example, this processing operation may be performed by the Transport block processing receiver670-eofFIG.6. In particular, the transport blocks of data are processed based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. Alternatives Complementing the Generic Scenarios The above description has been made with the focus on an implementation where the base station460and/or user equipment410assumes that the second parameter is comprised in the indexed row of the RRC configure table. As stated before, this description shall however not be understood as limiting the present disclosure. Rather, the description merely corresponds to one out of many alternative implementations of the present disclosure which all share the common concept of explicitly or implicitly signaling the second parameter between base station460and user equipment410. In more detail, for the subsequent PUSCH transmissions, the processor430of the above described implementation reverts to the row with row index m+1 of the RRC configured table in order to determine from the second parameter, comprised in this indexed row of the RRC configured table, whether these transmissions are either different (or separate) PUSCH transmissions or repeated PUSCH transmissions. The skilled reader readily understands that the second parameter is comprised in a row of the RRC configured table which is defined by the PUSCH time domain resource allocation list IE. In other words, since the (entire) RRC configure table is defined by the PUSCH time domain resource allocation list IE, then also the second parameter comprised therein is defined by the PUSCH time domain resource allocation list IE. In short, the second parameter in this one implementation is explicitly signaling between user equipment410and base station460in form of the PUSCH time domain resource allocation list IE. Alternative implementations of the present disclosure focus on the received DCI which is scheduling the PUSCH transmission (or the PDSCH transmission) for conveying the second parameter to the user equipment410and/or to the base station460. In such cases, the second parameter may be explicitly or implicitly signaled between base station460and user equipment410. In more detail, for the subsequent PUSCH transmission, the processor430of these alternative implementations reverts to the received DCI scheduling the plural PUSCH transmissions, in order to determine from a second parameter which is conveyed via the received DCI whether these transmissions are either different (or separate) PUSCH transmissions or repeated PUSCH transmissions. First Example of the Alternative Implementations In a first example of the alternative implementations, the second parameter may be conveyed via the received DCI in form of a separate (e.g., new) bit field comprised in the DCI transmitted between the base station460and the user equipment410. This equally applies to a DCI of DCI format 0-0 or of DCI format 0-1. Accordingly, this separate (e.g., new) bit filed comprised in the DCI permits explicitly signaling the second parameter between user equipment410and base station460. For instance, the separate (e.g., new) bit field comprised in the DCI may be termed “TBrepeat” and may have a format of 1 bit only for indicating whether the plurality of PUSCH transmissions are either different or repeated PUSCH transmissions. Considering a bit field with a 1 bit format, then a bit value of ‘0’ may indicate that the plural PUSCH transmissions are to be transmitted in the form of different (or separate) PUSCH transmissions, whereas a bit value of ‘1’ may indicate that the plural PUSCH transmissions are to be used in the form of repeated PUSCH transmissions. In this context, it should be noted that the DCI, which is being received by the receiver420of the user equipment410, is uniformly scheduling (at least to the extent of their timing relations) all of the plural PUSCH transmissions which are then transmitted by the transmitter420. Thus, it may appear artificial to distinguish for the second parameter in the separate (e.g., new) bit field of the DCI between the first and the subsequent PUSCH transmissions. In order to avoid such artificial distinctions, the DCI as well as the second parameter comprised therein are both stated to uniformly characterize all of the plural PUSCH transmissions. This statement, however, merely simplifies what has been said before:In case the second parameter indicates plural repeated PUSCH transmissions, then it is again the subsequent PUSCH transmissions which are repetitions of a first PUSCH transmission. In case the second parameter indicates plural different (or separate) PUSCH transmissions, then it is again the subsequent PUSCH transmissions which are different from a first PUSCH transmission. In summary, with this first example of the alternative implementations, it is possible to achieve a good trade-off between RRC signaling overhead and MAC signaling overhead when transmitting the DCI. Additionally this first example facilitates provide a mechanism which has no impact on the RRC configuration for time-domain resource assignments since the second parameter is explicitly provided in the DCI. Second Example of the Alternative Implementations In a second example of the alternative implementations, the second parameter may be conveyed via the received DCI in form of a particular (e.g., new) radio network temporary identifier, RNTI, which is used for scrambling the cyclic redundancy check, CRC, bit field of the DCI transmitted between the base station460and the user equipment410. This equally applies to a DCI of DCI format 0-0 or of DCI format 0-1. Accordingly, the particular (e.g., new) RNTI permits implicitly signaling the second parameter between user equipment410and base station460. For instance, the user equipment410may be configured with a particular (e.g., new) RNTI. After reception of the DCI, the receiver420of the user equipment410may attempt to decode the DCI at first without scrambling of the CRC filed of the DCI with the particular (e.g., new) RNTI. If the receiver420is successfully decoding the DCI, then the processor430infers a second parameter which indicates that the DCI is scheduling all of the plural PUSCH transmission in form of repeated PUSCH transmissions. If the receiver420with its first attempt to decode the DCI fails, then it may attempt to decode the DCI with scrambling of the CRC field of the DCI with the particular (e.g., new) RNTI. If the receiver is then successfully decoding the DCI, then the processor430infers a second parameter which indicates that the DCI is scheduling all of the plural PUSCH transmissions in form of different (e.g., separate) PUSCH transmissions. Again, it should be noted that the DCI, which is being received by the receiver420of the user equipment410, is uniformly scheduling (at least to the extent of their timing relations) all of the plural PUSCH transmissions which are then transmitted by the transmitter420. Thus, it may appear artificial to distinguish for the second parameter in the separate (e.g., new) bit field of the DCI between the first and the subsequent PUSCH transmissions. In order to avoid such artificial distinctions, the DCI as well as the second parameter comprised therein are both stated to uniformly characterize all of the plural PUSCH transmissions. This statement, however, merely simplifies what has been said before:In case the second parameter indicates plural repeated PUSCH transmissions, then it is again the subsequent PUSCH transmissions which are repetitions of a first PUSCH transmission. In case the second parameter indicates plural different (or separate) PUSCH transmissions, then it is again the subsequent PUSCH transmissions which are different from a first PUSCH transmission. In summary, with this second example of the alternative implementations, it is possible to avoid any RRC signaling overhead and avoid any additional MAC signaling overhead when transmitting the DCI. Additionally this second example facilitates providing a mechanism which has no impact on the RRC configuration for time-domain resource assignments since the second parameter is implicitly provided in the DCI. Further alternative implementations of the present disclosure focus on a physical layer configuration of the user equipment410which is being received from the base station460, for instance, upon initial access to the cell broadcasting the particular bandwidth part for which the PUSCH config IE is applicable. This physical layer configuration may alternatively also be referred to as “physical layer identification of the transmission/reception scenario or service type.” In more detail, the physical layer configuration being signaled between base station460and user equipment410is conveying the second parameter. Thus, for the subsequent PUSCH transmission, the processor430of these alternative implementations revert to the received physical layer configuration in order to determine from the second parameter, which is conveyed via the physical layer configuration whether these transmissions are either different (or separate) PUSCH transmissions or repeated PUSCH transmissions. Third Example of the Alternative Implementations In a third example of the alternative implementations, the second parameter may be conveyed via the physical layer configuration in form of a separate (e.g., new) parameter comprised in a physical, Phy-, parameter IE. This Phy-Parameter IE is received by the receiver420of the user equipment410in form of RRC signaling. After having received the Phy-Parameter IE, the processor430infers from same received second parameter, whether or not it is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. Accordingly, this separate (e.g., new) parameter comprised in the Phy-Parameter IE permits explicitly signaling the second parameter between user equipment410and base station460. For instance, the separate (e.g., new) parameter comprised in the Phy-Parameter IE may be termed “pusch-MultipleTrasmissions” and may be of format “ENUMERATED {repeatTB, differentTB].” This parameter may only be considered when a single DCI is configured to schedule plural PUSCH transmissions as in the focus of the present disclosure. If the single DCI is not configured to schedule multiple PUSCH transmissions, then this parameter is not considered by the user equipment410. Such distinction can be either applied to all DCIs or can be restricted to particular DCIs. Fourth Example of the Alternative Implementations In a third example of the alternative implementations, the second parameter may be conveyed via the physical layer configuration in form of particular radio spectrum configuration for a particular bandwidth part. The radio spectrum configuration is received by the receiver420of the user equipment410in form of RRC signaling. After having received the radio spectrum configuration of the particular bandwidth part to which the PUSCH config IE is applicable, then the processor430infers the second parameter by checking whether or not the radio spectrum configuration indicates specific radio bands which can only be used in an unlicensed mode of operation. For instance, industrial, scientific and medical (ISM) radio bands are radio bands (portions of the radio spectrum) reserved internationally for the use of radio frequency (RF) energy for industrial, scientific and medical purposes other than telecommunications. Due to this dedicated purpose, they may only be used in an unlicensed mode of operation. In case the check for specific radio bands is positive, the processor430infers a second parameter which indicates that all of the plural PUSCH transmissions are to be carried out in the form of repeated PUSCH transmissions. In case the check for specific radio bands is negative, the processor430infers a second parameter which indicates that all of the plural PUSCH transmissions are to be carried out in the form of different (or separate) PUSCH transmissions. Accordingly, the radio spectrum configuration permits implicitly signaling the second parameter between user equipment410and base station460. In more detail, due to the fact that the radio spectrum configuration pertains to the same particular bandwidth part to which also the PUSCH config IE is applicable, the user equipment410can implicitly establish a relationship between an unlicensed mode of operation and a necessity (or requirement) for an enhanced reliability of the PUSCH transmissions on the particular bandwidth part. In summary, with this fourth example of the alternative implementations, it is possible to avoid any RRC signaling overhead and avoid any additional MAC signaling overhead when transmitting the DCI. Further this fourth example facilitates providing a mechanism which may consistently ensure repeated PUSCH transmission in unlicensed spectrum. Fifth Example of the Alternative Implementations In a fifth example of the alternative implementations, the second parameter may be conveyed via the physical layer configuration in form of a service type configuration having specific reliability and/or latency requirements. This service type configuration is received by the receiver420of the user equipment410in form of RRC signaling. After having received the service configuration, then the processor430infers the second parameter by determining whether or not the specific reliability and/or latency requirements of the service type configuration exceeds particular target values. For instance, in case the processor430determines that the specific reliability and/or latency requirements of the service type configuration are below (are more lenient than) respective target values, then the processor430infers a second value which indicates that the plural PUSCH transmissions are to be carried out in form of different (or separate) PUSCH transmissions. In case the processor430determines that the specific reliability and/or latency requirements are above (are more strict than) respective target values, then the processor infers a second value which indicates that the plural PUSCH transmissions are to be carried out in form of repeated PUSCH transmissions. Accordingly, the service type configuration having specific reliability and/or latency requirements permits implicitly signaling the second parameter between user equipment410and base station460. Generic Scenario for Downlink As already mentioned above, the present disclosure is not limited to transport block (TB) transmissions in the uplink but can equally be applied to downlink transmissions, namely to achieve a flexible support of TB transmissions in the downlink. Also here, transport block (TB) transmissions are supported with flexible timings which do not create additional signaling overhead. In other words, the benefit of an improved flexibility when scheduling transport block transmissions are not only achievable for physical uplink shared channel (PUSCH) transmissions, but are equally achievable for physical downlink shared channel (PDSCH) transmissions. This directly follows from the high degree of similarity between the PUSCH-Time Domain Resource Allocation List information element (IE), and the PDSCH-Time Domain Resource Allocation List IE. Also, no additional signaling overhead is created since the scheduling described henceforth relies on the PDSCH-Time Domain resource allocation field in DCI Format 1-0 or 1-1, which is highly similar to the on the PUSCH-Time Domain Resource Allocation field in DCI format 0-0 or 0-1 discussed before. In general, the receiver420of the user equipment410receives a physical downlink shared channel, PDSCH, config information element, IE, in form of radio resource control, RRC, signaling. The PDSCH config IE is applicable to a particular bandwidth part which is served by the base station460. Then, the processor430of the user equipment410configures a table which is defined by a PDSCH time domain resource allocation list IE carried in the received PDSCH config IE. The RRC configured table comprising rows, each with a first set of values related to allocated time-domain resources for a plurality of PDSCH transmissions. Subsequently, the receiver420of the user equipment410receives downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table. The processor430of the user equipment410determines allocated resources for the plurality of PDSCH transmissions based on: (i) index of a slot carrying the received DCI, and (ii) the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table. Thereafter, the receiver420of the user equipment410receives the plurality of PDSCH transmissions using the respectively determined allocated time-domain resources, and processes transport blocks of data which are carried in the plurality of received PDSCH transmissions; and In particular, the transport blocks of data are processed based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PDSCH transmissions are either different PDSCH transmissions or repeated PDSCH transmissions. First Exemplary Implementation The following first exemplary implementation is conceived with the understanding that the indexed row of the RRC configured table comprises (exactly) one second parameter which has one of a value ‘Different’ indicating that the subsequent PUSCH transmissions are different (e.g., separate) PUSCH transmissions, or a value ‘Repeat’ indicating that the subsequent PUSCH transmissions are repeated PUSCH transmissions. Since the first PUSCH transmission from the plurality of PUSCH transmissions is always a different PUSCH transmission it may seem artificial to distinguish in case of (exactly) one second parameter between this first PUSCH transmission and the subsequent PUSCH transmissions. In this regard, it may be stated that the (exactly) one second parameter pertains to all of the PUSCH transmissions. In other words, the indexed row of the RRC configured table comprises a same one of the at least one second parameter which is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. The processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 1. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. Example 1 ASN.1 Notation of “Pusch-Timedomainresourceallocationlist IE” EXAMPLE 1:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127),TBtypeENUMERATED {Different, Repeat},multiplePUSCHTransmissionsSEQUENCE {. . . .. . . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP Second Exemplary Implementation The following second exemplary implementation is conceived with the understanding that the indexed row of the RRC configured table comprises separate second parameters for the subsequent PUSCH transmissions. Each of the second parameters has one of a value ‘Different’ indicating that the respective subsequent PUSCH transmission is a different (e.g., separate) PUSCH transmission compared to the preceding PUSCH transmission, or a value ‘Repeat’ indicating that the respective subsequent PUSCH transmission is a repeated PUSCH transmissions compared to the preceding PUSCH transmission. In other words, the indexed row of the RRC configured table comprises a different one of the at least one second parameter which is indicating different or repeated PUSCH transmissions for each of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions. The processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 2. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. Example 2 ASN.1 Notation of “Pusch-Timedomainresourceallocationlist IE” EXAMPLE 2:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE (1 . . .maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0 . . . 32) OPTIONAL,-- Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0 . . . 127),multiplePUSCHTransmissionsSEQUENCE {TBtypeENUMERATED {Different, Repeat},. . .. . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP Third Exemplary Implementation The following third exemplary implementation is conceived with the understanding that at least one of the third set of values, comprised in the indexed row of the RRC configured table, is at least one of a value K2‘ indicating another slot offset for at least one subsequent PUSCH transmission(s), a value SLIV’ indicating another start and length indicator value for the at least one subsequent PUSCH transmission(s), and/or a value indicating the number of the at least one subsequent PUSCH transmission(s). In particular, the other start and length indicator value SLIV′ comprises: a value S′ indicating a symbol number specifying the start of the allocated time-domain resources for the at least one subsequent PUSCH transmission(s), and a value L′ indicating a number of symbols specifying the length of the allocated time-domain resources for the at least one subsequent PUSCH transmission(s). With this understanding, the RRC configured table comprises not only values from the first set of values which are specifying allocated time-domain resources for the first PUSCH transmission. Rather the RRC configured table comprises a third set of values including values K2′ and/or SLIV′ which are specifying allocated time-domain resources for the at least one subsequent PUSCH transmission(s). In addition, the third set of values includes a value indicating the number of the at least one subsequent PUSCH transmission(s) further complements the RRC configured table in that it permits a more flexible determination as to which of the specified allocated time-domain resource are to be used for subsequent PUSCH transmissions. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 3. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 3:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},start SymbolAndLengthINTEGER (0..127) ,numberOfTransmissionsINTEGER (0..8),multiplePUSCHTransmissionsSEQUENCE {k2′INTEGER (0..32),startSymbolAndLength′INTEGER (0..127),. . . .. . . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP Fourth Exemplary Implementation The following fourth exemplary implementation is conceived with the understanding that the indexed row of the RRC configured table comprises at least one fourth value related to the generation of the plurality of PUSCH transmissions. The at least one fourth value assists the user equipment when generating the plurality of PUSCH transmissions carrying the selected transport blocks of data. In other words, the transmitter420of the user equipment410generates the plurality of PUSCH transmission carrying the selected transport blocks of data based on at least one fourth value related to the generation of the plurality of PUSCH transmissions. The at least one fourth value is also comprised in the indexed row of the RRC configured table. One example of a fourth value is a different modulation and coding scheme, MCS, index value for each of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions. In other words, the indexed row of the RRC configured table comprises a different modulation and coding scheme, MCS, index value for each of the subsequent PUSCH transmissions. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 4-1. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 4-1:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127),multiplePUSCHTransmissionsSEQUENCE {MCSindexINTEGER (0..32),. . . .. . . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP With such a different MCS index value for each of the subsequent PUSCH transmission, the present disclosure facilitates a more accurate match of the MCS index to the condition of the channel for each transmission. Another example of a fourth value is a same modulation and coding scheme, MCS, index value (e.g., with maximum robustness) for all of the plurality of PUSCH transmissions. In other words, the indexed row of the RRC configured table comprises a same modulation and coding scheme, MCS, index value for all of the plurality of PUSCH transmissions. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 4-2. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 4-2:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127),multiplePUSCHTransmissionsSEQUENCE {MCSindexINTEGER (0..32),. . . .. . . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP A further example of a fourth value is a different redundancy version, RV, offset value for each of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions. In other words, the indexed row of the RRC configured table comprises different redundancy version, RV, offset values for each of the subsequent PUSCH transmissions. For example, let us assume that the DCI was received by the receiver420of the user equipment410with an RV field comprising the value of ‘1’, then the transmitter420generates the first of the plurality of PUSCH transmissions with RV of value ‘1’ which is determined by the RV field with value ‘1’ of the DCI. Also the transmitter generates the subsequent of the plurality of PUSCH transmissions with a RV of value ‘1’ adding from the indexed row of the RRC configured table the respective value RV offset for each of the subsequent PUSCH transmissions. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 4-3. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 4-3:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127),multiplePUSCHTransmissionsSEQUENCE {RVoffsetENUMERATED (0..3),. . . .. . . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP With such a different RV offset value for each of the subsequent PUSCH transmission, the present disclosure facilitates enabling more flexibility when scheduling different PUSCH transmissions. In other words, independent RV offsets are allowed for each PUSCH transmissions. An even further example of a fourth value is a same redundancy version, RV, offset value for each of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions. In other words, the indexed row of the RRC configured table comprises a same redundancy version, RV, offset value for each of the subsequent PUSCH transmissions. For example, let us assume that the DCI is received by the receiver420of the user equipment410with an RV field comprising the value of ‘1’, then the transmitter420generates not only for the first but also the subsequent of the plurality of PUSCH transmissions with a RV value ‘1’ adding from the indexed row of the RRC configured table the same value RV offset for all of the plurality of PUSCH transmissions. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 4-4. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 4-4:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127),RVoffsetENUMERATED {0..3},multiplePUSCHTransmissionsSEQUENCE {. . . .. . . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP Fifth Exemplary Implementation The following fifth exemplary implementation is conceived with the understanding that the indexed row of the RRC configured table comprises at least one fifth parameter related to the generation of the plurality of PUSCH transmissions. The at least one fifth parameter assists the user equipment when generating the plurality of PUSCH transmissions carrying the selected transport blocks of data. The at least one fifth parameter related to the generation of the plurality of PUSCH transmissions is additionally comprised in the PUSCH time domain resource allocation list IE which defines the table that is created by the processor430,480of the user equipment410, or of the base station460. In other words, the transmitter420of the user equipment410generates the plurality of PUSCH transmission carrying the selected transport blocks of data adhering to principles prescribed by the at least one fifth parameter related to the generation of the plurality of PUSCH transmissions. The at least one fifth parameter is also comprised in the indexed row of the RRC configured table. One example of a fifth parameter prescribing principles related to the generation of the plurality of PUSCH transmissions is a parameter indicating whether the transport block size, TBS, is calculated for each of the plurality of PUSCH transmission separately, or whether a combined transport block size is calculated for all PUSCH transmissions. For example, let us assume that the DCI is received by the receiver420of the user equipment410with a transport block size, TBS, for the plural PUSCH transmissions. Then the transmitter420needs to know whether this TBS is calculated for each of the PUSCH transmissions separately, or is calculated as a combined TBS for all PUSCH transmissions. In the first case, the transmitter420generates PUSCH transmissions which each have the same TBS from the DCI. In the second case, the transmitter generates PUSCH transmissions which each have a TBS which corresponds to the combined TBS from the DCI divided by the total number of PUSCH transmissions. In both cases, the transmitter420adhering to principles prescribed by the at least one fifth parameter can generate the plural PUSCH transmissions. Another example of a fifth parameter prescribing principles related to the generation of the plurality of PUSCH transmissions is a parameter indicating whether a modulation and coding scheme, MCS, index is determined for each of the plurality of PUSCH transmission separately, or whether the same MCS index is determined for all PUSCH transmissions. In other words, with this parameter indicating the determination principle of the modulation and coding scheme, MCS, index the transmitter420generates the subsequent PUSCH transmissions either by following the same MCS as the first transmission or calculates the MCS for each subsequent transmission based on transport block size and the available resources for each of the subsequent transmission. When it is indicated to use same MCS for each transmission, then the length of each transmission could possibly be different if the TB size is different. In this case, the transmitter determines the MCS following the same principles as for the first PUSCH transmission. When the MCS needs to be determined for each subsequent PUSCH transmission after the first PUSCH transmission, then depending on the TB size and resource, the closest MCS value is calculated compared to that of first transmission. An example of such a PUSCH time domain resource allocation list IE with a parameter indicating the determination principle of the modulation and coding scheme, MCS, index is reproduced herein below, namely as example 5. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 5:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASNISTART-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127),MCSdeterminationENUMERATED {Same, Calculate},multiplePUSCHTransmissionsSEQUENCE {. . . .. . . .}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP A further example of a fifth parameter prescribing principles related to the generation of the plurality of PUSCH transmissions is a parameter indicating whether or not a same redundancy version, RV, is determined for all of the plurality of PUSCH transmissions based on a RV field in the received DCI. Alternatively, no additional parameter may be introduced to indicate the RV for the subsequent PUSCH transmissions of the plurality of PUSCH transmissions. Then the transmitter420of the user equipment410re-uses the same RV as for the first PUSCH transmission which is explicitly determined by the RV field of the DCI received by the receiver420. An even further example of a fifth parameter prescribing principles related to the generation of the plurality of PUSCH transmissions is a parameter indicating whether or not demodulation reference symbols, DMRS, are present in at least a first or in all of the plurality of PUSCH transmission. Comprehensive Example of First Generic Uplink Scenario Referring now toFIGS.8and9, a comprehensive example is given which combines the effects discussed for the first generic scenario with those of the numerous exemplary implementations. This example shall, however, not be understood as a restriction to the present disclosure since alternative combinations are also conceivable. In particular, this example is presented in form of a RRC configured table for plural PUSCH transmissions and corresponding time domain resource allocations for plural PUSCH transmissions. The RRC configured table is, also in this example, configured by the processor430of the user equipment410, namely in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE. This has been described before. Rather, focus is laid with this description on explaining how the processor430and the transmitter420jointly operate, with the help of the RRC configured table, to cause the plural PUSCH transmissions. In this table as shown inFIG.8, numerous values/parameters are combined which are referenced as first set of values, second parameters, third set of values, fourth values, and fifth parameters. The numbers do not follow any particular reason, e.g., they do not distinguish the level of importance, and also do not characterize the sequence of usage. Rather, they are given as a unique reference leading to a clear separation thereof. For example, the value K2cannot be confused with the value K2′ since the former value is included in (and belongs to) the first set of values whereas the latter value is included in (and belongs to) the third set of values. Nevertheless, the numerous values/parameters have been grouped functionally such that they are related to similar operations to be performed by processor430and transmitter430before the plural PUSCH transmissions are caused. In the example, it is assumed that the processor430has configured a table which is defined by a PUSCH time domain allocation resource list IE as shown inFIG.8and the receiver has received a DCI scheduling in total three PUSCH transmissions, and carrying a time-domain resource assignment filed with value m of 2, thereby providing a row index m+1 of 3 to the table. The scheduled three PUSCH transmissions can be individually referenced as PUSCH transmission #1, #2 and #3 or can be understood as a first PUSCH transmission (#1) and subsequent PUSCH transmissions (#2 and #3). For determining the allocated time-domain resources for the first PUSCH transmission (#1), the processor430reverts to the first set of parameters in the indexed row with row index 3 of the RRC configured table. From the value indicating the PUSCH mapping type, the processor430infers that the PUSCH mapping type is type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. This type b is not only applicable to the first but also to the subsequent PUSCH transmissions. Further, from the value K2, the processor430infers that allocated time-domain resources for the first PUSCH transmission are included in the slot with slot number k+2. Additionally, from the values S and L the processor430infers that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. For determining the allocated time-domain resource for the subsequent PUSCH transmissions (#2 and #3), the processor430reverts to the third set of parameters in the indexed row with row index 3 From the value K2′ the processor430infers that the allocated time-domain resources for the subsequent PUSCH transmission #2 and #3 are included in slots relative to the value k corresponding to the slot index carrying the received DCI. Thus, the allocated time-domain resources for the subsequent PUSCH transmission #2 and #3 are included in the slots with slot numbers k+2 and k+3, respectively. Additionally two values S′ and two values L′ are comprised indicating that the allocated resources for subsequent PUSCH transmission #2 and #3 start in the respective slot with slot number k+2 and k+3 at the symbol with symbol numbers 6 and 1, respectively. The respective resource allocations in time domain are also shown. For selecting the transport blocks of data to transmit in the scheduled PUSCH transmissions, the processor430reverts to the second parameters in the indexed row with row index 3 of the RRC configured table. From the values {R,D} included as second parameters in the table, the processor430infers whether the subsequent PUSCH transmissions #2 and #3 are either different PUSCH transmissions or repeated PUSCH transmissions. For the subsequent PUSCH transmission #2, the second parameter with value R, meaning a repetition of the preceding PUSCH transmission, indicates that the same transport block of data is to be selected which is repeating that of the preceding PUSCH transmission #1. For the subsequent PUSCH transmission #3, the second parameter with value D, meaning a difference over the preceding PUSCH transmission, indicates that a new transport block of data is to be selected which is different from that of the preceding PUSCH transmission #2. In other words, the second parameters define the repetition or difference for a subsequent PUSCH transmission with respect to the preceding PUSCH transmission. For more efficient selection of the transport blocks of data, the processor430reverts to the TBS determination parameter of the fifth parameters in the indexed row with row index 3 of the RRC configured table. From the TBS determination parameter with value C, meaning a calculated TBS determination, the processor430infers that the transport block size is to be calculated for each of the PUSCH transmissions separately. This calculation requires further information to be obtained by the processor430. In particular, the processor430additionally reverts to the MCS determination parameter of the fifth parameters also in the indexed row with row index 3 of the RRC configured table. From the MCS determination parameter with value S, meaning a same MCS determination, the processor430infers that the same modulation and coding scheme, MCS, index is determined for all PUSCH transmissions. In this regard, the processor430determines that the transmitter420can generate the first as well as the subsequent PUSCH transmissions #1, #2 and #3 with a same MCS corresponding to the MCS field in the scheduling DCI. For the actual (MCS) MCS index to be used, the transmitter420reverts to MCS field in the scheduling DCI and to the MCS index value of the fourth values also included in the indexed row of the RRC configured table. In more particular, the transmitter420reverts to the indexed row of the RRC configured table and checks if the MCS index value is among the fourth values included in same table. Here the transmitter420finds the MCS index value of 4. Having found a MCS index value and knowing that a same MCS value is to be used for all of the PUSCH transmissions #1, #2 and #3, the transmitter uses this MCS index value of 4 when generating the PUSCH transmissions instead of referring to the MCS field in the scheduling DCI. That said, the processor430is now also capable of calculating the TBS for each of the plural PUSCH transmission separately. In particular, the processor430determines from the fact that all PUSCH transmissions have a same length of symbols (L=4), and from the fact that all PUSCH transmissions are to be generated with a same MCS that the transport block size, TBS, for each of the PUSCH transmissions is also calculated same. In other words, despite the MCS determining parameter indicating a separate calculation of the MCS, the processor430infers from the same amount of time-domain resources (all PUSCH have a same length of L=4) and from the same MCS that the separate calculation will result in a same TBS for all PUSCH transmissions #1, #2 and #3. For the actual TBS values to be used, the transmitter420reverts to the TBS value included in the DCI scheduling the plural PUSCH transmissions and calculates each TBS value by divides the TBS value from the DCI by the total number of PUSCH. Further, from the RV parameter N of the fifth parameters, meaning not a same RV index, the processor430infers that the redundancy version, RV, index to be used when generating all of the PUSCH transmissions is not same for all the PUSCH transmissions. Since it is not same, the transmitter420reverts to the fourth parameters, namely to the RV offset value, and uses this RV offset value to determine the RV indices for the subsequent PUSCH transmissions. Due to the For the actual RV to be used, the transmitter420reverts to the RV field included in the DCI scheduling the plural PUSCH transmissions and reverts to the RV offset value of the fourth values included in the indexed row of the RRC configured table. In more particular, the transmitter420when generating the PUSCH transmissions, determines the RV of 0 for the first PUSCH transmission #1 based on the RV field of the DCI, and determines the RV of 1 for the subsequent PUSCH transmissions #2 and #3 based on the RV field of the DCI adding the RV offset of 1 corresponding to the fourth parameter in the indexed row with row index 3 of the RRC configured table. Finally, the processor430reverts to the DMRS parameter of the fifth parameters included in the indexed row of the table and from the DRMS parameter F, meaning only first DMRS, infers that demodulation reference symbols, DMRS, are present only in a first of the plurality of PUSCH transmission. Finally the PUSCH transmissions #1, #2 and #3 are being generated and then the PUSCH transmitter transmits same using the allocate time-domain resources. This is shown inFIG.9 Second Generic Uplink Scenario FIGS.10and11depict another exemplary implementations according to a second generic scenario of the building blocks of the user equipment410and of the base station460, respectively. The user equipment410of the exemplary implementation comprises a PUSCH config IE receiver1020-a, a table configuring processing circuitry1030-a, a DCI receiver1020-b, a configured grant config IE receiver1020-c, an allocated resources determining processing circuitry1030-b, and a PUSCH transmitter1020-d. Similarly, the base station460of the exemplary implementation comprises a PUSCH config IE transmitter1170-a, a table configuring processing circuitry1180-a, a DCI transmitter1170-b, a configured grant config IE transmitter1170-c, a resource allocating processing circuitry1180-b, and PUSCH receiver1170-d. In general, the present disclosure assumes that the user equipment410is in communication reach of the base station460and is configured with at least one bandwidth part in the downlink and at least one bandwidth part in the uplink. The bandwidth parts are located within the carrier bandwidth served by the base station460. Further, the present disclosure assumes that the user equipment410is operating in a radio resource control, RRC, connected state (termed: RRC_CONNECTED), thereby capable of receiving in the downlink data and/or control signals from the base station460and capable of transmitting in the uplink data and/or control signals to the base station460. Before performing PUSCH repetitions as suggested in the present disclosure, the user equipment410receives control messages as defined in the radio resource control, RRC, and the medium access control, MAC, protocol layer. In other words, the user equipment410employs signaling mechanism which is readily available in the different protocol layers of the various communication technologies. In general, a substantial difference is made between control messages defined in RRC and those defined in MAC. This difference becomes already aware from the fact that RRC control messages are usually used for configuration of radio resources (e.g., radio link) on a semi-static basis whereas MAC control messages are used for dynamically defining each medium access (e.g., transmission) separately. From this, it directly follows that RRC control occurs less frequently than MAC control. Accordingly, an excessive MAC control signaling overhead can substantially impair the communication system performance whereas the RRC control message have been treated more leniently in standardization. In other words, MAC control signaling overhead is a well-recognized constraint to the system performance. For this reason the conventional mechanisms of PUSCH repetitions relies on pre-specified (e.g., in the relevant standard fixedly prescribed) timing relations between the initial PUSCH transmission and the repetitions thereof. In other words, the risk of an impaired system performance was found to outbalance the benefits from a more flexible use of PUSCH repetitions. Considering the above, the authors of the present disclosure propose a mechanism which overcomes the disadvantages of conventional mechanisms and permits flexible transport block (TB) repetitions, while—at a same time—avoiding signaling overhead. In the context of the disclosure, the term “transport block” is to be understood as data unit of an uplink and/or downlink transmission. For example, it is widely understood that the term “transport block” is equivalent to a MAC layer packed data unit, PDU. Thus, the transmission of transport block is equally understood as a physical uplink shared channel (PUSCH) and/or physical downlink shared channel (PDSCH) transmission. Particularly, since PUSCH and/or PDSCH transmissions generally carry payload, the present disclosure shall refer to PUSCH and/or PDSCH transmissions carrying a MAC PDU. In other words, the terms “PUSCH and/or PDSCH transmissions” shall be understood as describing MAC PDU transmission on PUSCH and/or PDSCH. Referring toFIG.12, a generic scenario is described with regard to performing PUSCH repetitions based on a dynamic grant, namely a DCI carrying a time-domain resource assignment filed, such as, for example, a DCI of DCI format 0-0 or of DCI format 0-1. This description shall, however, not be understood as a restriction to the present disclosure to only extend to PUSCH transmissions, more specifically to repetitions thereof. Rather, it will become apparent that the concepts disclosed herein can equally be applied to downlink transmissions The receiver420of the user equipment410receives (see e.g., step1210—FIG.12) a physical uplink shared channel, PUSCH, config information element, IE. This PUSCH config IE is received in form of radio resource control, RRC, signaling and applicable to a particular bandwidth part. The PUSCH config IE is received from the base station410serving the particular bandwidth part. For example, this reception operation may be performed by the PUSCH config IE receiver1020-aofFIG.10. The PUSCH config IE carries among others a list of parameters in form of an information element (IE) termed “PUSCH-TimeDomainResourceAllocationList,” wherein each parameter of the list of parameters is termed “PUSCH-TimeDomainResourceAllocation.” Then, the processor430of the user equipment410configures (see, e.g., step1220—FIG.12) a table which is defined by the PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The table comprises rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator. For example, this configuration operation may be performed by the table configuring processing circuitry1030-aofFIG.10. In an exemplary implementation, each row of the RRC configure table corresponds to one of plural parameters termed “PUSCH-TimeDomainResourceAllocation” of the list of parameters termed “PUSCH-TimeDomainResourceAllocationList.” This shall, however, not be understood as a limitation to the present disclosure, as apparent from the following alternative. Also scenarios different from the exemplary implementation are conceivable, namely where some rows of the configured table correspond to respective parameters comprised in the IE with the list of parameters, and other rows are configured complying with a set of pre-specified rules readily applying the principles laid out PUSCH time domain resource allocation list IE. This shall, however, not distract from the fact that the RRC configured table in its entirety is defined by the PUSCH time domain resource allocation list IE. Subsequently, the receiver420of the user equipment410receives (see, e.g., step1230—FIG.12) downlink control information, DCI, signaling. The DCI is carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the configured table. For example, this reception operation may be performed by the DCI receiver1020-bofFIG.10. In the context of the present disclosure, this DCI is carrying an uplink grant since it serves the purpose of triggering PUSCH repetitions. In this respect, the received DCI is in DCI format 0-0 or in DCI format 0-1. In this respect, the described scenario refers to situation where the PUSCH repetitions are scheduled by a dynamic grant. This shall, however, not be understood as limitation to the present disclosure, as the concepts disclosed herein are equally applicable to a configure grant or grant free scheduling technique. A detailed description of this grant free scheduling technique is given as an alternative to the mechanism depicted inFIG.12. Subsequently, the processor430of the user equipment410determines allocated resources for an initial PUSCH transmission and also allocated resources for at least one repetition of the initial PUSCH transmission. For sake of clarity and brevity, the following description focusses on the allocation of resources in time domain. For example, this determination operation may be performed by the allocated resources determining processing circuitry1030-bofFIG.10. The resources to be used by the user equipment410for the initial PUSCH transmission and the repetition(s) thereof have been previously allocated by the base station460. In this context, the processor430accordingly determines which of the previously allocated resource it shall use for the PUSCH transmission and the repetition(s) thereof. As part of this determination operation, the processor430at first determines (see, e.g., step1240—FIG.12) the allocated resources for the initial PUSCH transmission based on: (i) index of a slot carrying the received DCI, and (ii) the value K2indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. This implies that the processor430has previously determined that the value indicating the PUSCH mapping type indicates a type B mapping. For example, let us assume the received DCI was carried in a slot which has the number k, and further the DCI has a time-domain resource assignment filed with value m. Then, the processor, for the initial PUSCH transmission, reverts to the RRC configured table in row with row index m+1 and uses the respective values K2indicating the slot offsets, and SLIV indicating the start and length indicator. With these value, the processor determines that the allocated resources, for the initial PUSCH transmission, are included in a slot with a number of k+K2, and have a start and length in terms of symbols of this slot corresponding to the value SLIV. When determining the allocated resources, the processor430also uses the value indicating the PUSCH mapping type additionally comprised in the row of the RRC configured table with row index m+1. Particularly, in case the value indicates a type A PUSCH mapping, the processor430only uses the length of the value SLIV indicating a start and length indicator. In case the value indicates a type B PUSCH mapping, the processor430uses both the start and the length of the value SLIV indicating the start and length indicator. As part of this determination operation, the processor430then determines allocated resources for the at least one repetition of the initial PUSCH transmission. For this, the processor430checks (see, e.g., step1250—FIG.12) if there is an (explicit) time domain resource assignment related to parameters (e.g., the timing) for the repetition. For this, the processor430reverts to the row with row index m+1 and checks whether or not this row comprises additional values (e.g., at least one value) which are specifying the allocated resource in time domain for the at least one repetition of the initial PUSCH transmission. In case the check is negative, the processor430uses (see, e.g., step1260—FIG.12) a conventional slot-based repetition mechanism for the repetition of the initial PUSCH transmission. In other words, the processor430relies on pre-specified (e.g., in the relevant standard fixedly prescribed) timing relations between the initial PUSCH transmission and the repetitions thereof. For example, this results in an initial PUSCH transmission and each repetition starting at a same symbol and having a same symbol length of plural consecutive slots. Referring back to the example, the processor430, for the at least one repetition, reverts to the row with row index m+1 of the RRC configured table, and determines that the allocated resources, for the first repetition of the initial PUSCH transmission, are included in a slot with number k+K2+1 (where 1 is a pre-defined constant fixed by standardization), and have a start and length in terms of symbols of this slot corresponding to the same value SLIV. Should there be a second repetition, the processor430that the allocated resources, for the second repetition of the initial PUSCH transmission, are included in a slot with number k+K2+2 (where 2 is again a pre-defined constant fixed by standardization), and have a start and length in terms of symbols of this slot corresponding to the same value SLIV as already the initial PUSCH transmission and the first repetition thereof. Further repetitions follow at contiguous slots. Further to this example, when assuming that the PUSCH mapping type indicted in the row with row index m+1 is type B, and when assuming that the value SLIV indicates a start at symbol 4 and a length of 4 symbols, then the processor430determines that each one of the initial, the first repetition and the second repetition of the PUSCH transmission have resources corresponding to symbol 4, symbol 5, symbol 6 and symbol 7 in the slots with number k+K2, number k+K2+1, number k+K2+2, respectively. Evidently, these allocated resources as determined by the processor430cannot be flexibly configured. This is overcome by the alternative determination by the processor430. In case the check is positive, the processor430uses (see, e.g., step1270—FIG.12) the additional values (e.g., at least one value) comprised in the indexed row of the RRC configure table for determining allocated resources for the repetition of the initial PUSCH transmission. In other words, the comprised at least one additional value is specifying the allocated resource in time domain for the repetition of the initial PUSCH transmission. It shall be emphasized in this context that the at least one additional value is comprised in a row of the RRC configured table which is defined by the PUSCH time domain resource allocation list IE. In other words, since the (entire) RRC configure table is defined by the PUSCH time domain resource allocation list IE, then also the at least one additional value comprised therein is defined by the PUSCH time domain resource allocation list IE. To meet this constrains, the at least one additional value could be (directly) prescribed by a parameter comprised in the PUSCH time domain resource allocation list IE, or alternatively the at least one additional value could be (indirectly) inferred from related parameters comprised in the PUSCH time domain resource allocation list IE. In any case, the at least one additional value specifies in time domain the repetition of the initial PUSCH transmission. It is important to realize that the processor430of the user equipment410uses additional values from the indexed row of the RRC configured table for determining the allocated resources for the repetitions. This approach substantially differs from the conventional slot-based repetition mechanism for the following reasons:Firstly, the at least one additional value comes from a row of the RRC configured table which is (actively) indexed by the row index m+1 derived from value m in the time-domain resource assignment field of the received DCI. In this respect, a varying index values m in the in the time-domain resource assignment field of the received DCI permit a varying at least one additional values to be used for determining the allocated resources for the at least one repetition of the initial PUSCH transmission. Thereby, the flexibility of such allocated resources is increased.Secondly, the at least one additional value comes from a (same) row of the RRC configured table which is (already) indexed by the row index m+1 derived from value m in the time-domain resource assignment field of the received DCI. In this respect, no additional index value is required than then index value m in the in the time-domain resource assignment field of the received DCI when determining the allocated resources for the repetition of the at least one repetition of the initial PUSCH transmission. Thereby, any additional signaling overhead is avoided. Consequently, this permits increasing flexibility while avoiding signaling overhead, namely by the processor430of the user equipment410using the at least one additional value from the indexed row of the RRC configured table for determining the allocated resources for the repetitions. Finally, the transmitter420of the user equipment410transmits (not depicted inFIG.12) a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof. For example, this transmission operation may be performed by the PUSCH transmitter520-eofFIG.5. The above description has been given from the perspective of the user equipment410. This shall, however, not be understood as a limitation to the present disclosure. The base station460equally performs the generic scenario disclosed herein. The transmitter470of the base station460transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling. The PUSCH config IE being applicable to a particular bandwidth part. For example, this transmission operation may be performed by the PUSCH config IE transmitter1170-aofFIG.11. Then, the processor480of the base station460configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator. For example, this configuration operation may be performed by the table configuring processing circuitry1180-aofFIG.11. Subsequently, the transmitter470of the base station460transmits downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table. For example, this transmission operation may be performed by the DCI transmitter1170-bofFIG.11. The processor480of the base station460allocates resources for an initial PUSCH transmission and allocates resources for at least one repetition thereof based on: (i) index of a slot carrying the transmitted DCI, and (ii) the value K2indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. In particular, the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. For example, this resource allocation operation may be performed by the resource allocating processing circuitry1180-bofFIG.11. Finally, a receiver470of the base station460receives a PUSCH transmission using the respectively allocated resources for the initial PUSCH transmission and for the at least one repetition thereof. For example, this reception operation may be performed by the PUSCH receiver1170-dofFIG.11. Now, a generic scenario is described with regard to performing PUSCH repetitions based on a configured grant (or grant free), namely a configured grant config IE received in form of RRC signaling, and also comprising a PUSCH time domain resource allocation list IE. The receiver420of the user equipment410receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling. The PUSCH config IE is applicable to a particular bandwidth part. The PUSCH config IE is received from the base station460serving the particular bandwidth part. For example, the reception operation may be performed by the PUSCH config IE receiver1020-aofFIG.10. Then, the processor430of the user equipment410configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offset, and a value SLIV indicating a start and length indicator. For example, this configuration operation may be performed by the table configuring processing circuitry1030-aofFIG.10. Subsequently, the receiver420of the user equipment410receives a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the configured table. For example, this reception operation may be performed by the configured grant config IE receiver1020-cofFIG.10. The processor430of the user equipment410determines allocated resources for an initial PUSCH transmission and allocated resources for at least one repetition thereof based on: (i) a value of time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and (ii) the value K2indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. In particular, the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. For example, this determination operation may be performed by the allocated resources determining processing circuitry1030-bofFIG.10. Finally, the transmitter420of the user equipment410transmits a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof. For example, this transmission operation may be performed by the PUSCH transmitter1030-dofFIG.10. The above description has been given from the perspective of the user equipment410. This shall, however, not be understood as a limitation to the present disclosure. The base station460equally performs the generic scenario disclosed herein. The transmitter470of the base station460transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part. For example, this transmission operation may be performed by the PUSCH config IE transmitter1170-aofFIG.11. Then, the processor480of the base station460configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE. The RRC configured table comprises rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator. For example, this configuration operation may be performed by the table configuring processing circuitry1180-aofFIG.11. Subsequently, the transmitter470of the base station460transmits a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the RRC configured table. For example, this transmission operation may be performed by the configured grant config IE transmitter1170-cofFIG.11. The processor480of the base station460allocates resources for an initial PUSCH transmission and allocates resources for at least one repetition thereof based on: (i) a value of time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and (ii) the value K2indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. In particular, the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. For example, this resource allocation operation may be performed by the resource allocating processing circuitry1180-bofFIG.11. Finally, the receiver470of the base station460receives a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof. For example, this reception operation may be performed by the PUSCH receiver1170-dofFIG.11. Generic Scenario for Downlink As already mentioned above, the present disclosure is not limited to transport block (TB) repetitions in the uplink but can equally be applied to downlink transmissions, namely to achieve a flexible support of repetitions in the downlink. Also here, transport block (TB) repetitions are supported with flexible timings which do not create additional signaling overhead. In other words, the benefit of an improved flexibility when scheduling transport block repetitions are not only achievable for physical uplink shared channel (PUSCH) transmissions, but are equally achievable for physical downlink shared channel (PDSCH) transmissions. This directly follows from the high degree of similarity between the PUSCH-Time Domain Resource Allocation List information element (IE), and the PDSCH-Time Domain Resource Allocation List IE. Also, no additional signaling overhead is created since the scheduling described henceforth relies on the PDSCH-Time Domain resource allocation field in DCI Format 1-0 or 1-1, which is highly similar to the on the PUSCH-Time Domain Resource Allocation field in DCI format 0-0 or 0-1 discussed before. In general, the receiver420of the user equipment410receives a physical downlink shared channel, PDSCH, config information element, IE, in form of radio resource control, RRC, signaling. The PDSCH config IE is applicable to a particular bandwidth part which is served by the base station460. Then, the processor430of the user equipment410configures a table which is defined by a PDSCH time domain resource allocation list IE carried in the received PDSCH config IE. The RRC configured table comprising rows, each with a value indicating a PDSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator. Subsequently, the receiver420of the user equipment410receives downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table. The processor430of the user equipment410determines allocated resources for an initial PDSCH transmission and allocated resources for at least one repetition thereof based on: (i) index of a slot carrying the received DCI, and (ii) the value K2indicating the slot offsets, and (iii) the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table. In particular, the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PDSCH transmission. Finally, the receiver420of the user equipment410receives a PDSCH transmission using the respectively determined allocated resources for the initial PDSCH transmission and for the at least one repetition thereof. Sixth Exemplary Implementation The following sixth exemplary implementation is conceived with the understanding that the at least one additional value, comprised in the indexed row of the RRC configured table, is at least one of a value K2′ indicating a second slot offset for the at least one repetition, a value SLIV′ indicating a second start and length indicator value for the at least one repetition, and optionally a value indicating the number of the at least one repetition. In particular, the second start and length indicator value SLIV′ comprises: a value S′ indicating a symbol number specifying the start of the allocated resources for the at least one repetition, and a value L′ indicating a number of symbols specifying the length of the allocated resources for the at least one repetition. With this understanding, the RRC configured table comprises not only values which are specifying allocated resources for the initial PUSCH transmission. Rather the RRC configured table comprises additional values K2′ and/or SLIV′ which are specifying allocated resources for the repetition of the initial PUSCH transmission. In addition, the optional additional value indicating the number of the least one repetition further complements the RRC configured table in that it permits a more flexible determination as to which of the specified allocated resource are to be used for repetitions. In particular, in the sixth exemplary implementation, the RRC configured table comprises rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets for the initial PUSCH transmission, a value SLIV indicating a start and length indicator for the initial PUSCH transmission, as additional values, a value K2′ indicating a second slot offset for the at least one repetition, a value SLIV′ indicating a second start and length indicator value for the at least one repetition. An example of such a RRC configured table is reproduced herein below, namely as Table 1: TABLE 1DCI RowPUSCHindexmapping typeK2SL{K2′}, {S′}, {L′}1Type AK2_1S_1L_1{K2′_1_1,K2′_1_2, . . . K2′_1_n},{S2′_1_1, S2′_1_2, . . . S2′_1_n},{L2′_1_1, L2′_1_2, . . . L2′_1_n}2Type BK2_2S_2L_2{K2′_2_1,K2′_2_2, . . . K2′_2_n},{S2′_2_1, S2′_2_2, . . . S2′_2_n},{L2′_2_1, L2′_2_2, . . . L2′_2_n}. . .. . .. . .. . .. . .. . .16. . .. . .. . .. . .. . . In this exemplary table 1, the values SLIV and SLIV′ are each shown to comprise: a value S and S′ indicating a symbol number specifying the start of the allocated resources, and a value L and L′ indicating a number of symbols specifying the length of the allocated resources. In particular, the RRC configured table not only comprises one set of additional values K2′ and SLIV′, or better K2′, S′ and L′, but instead comprises such a set of additional values for each of the PUSCH repetitions to be transmitted by the user equipment410. This achieves a high degree of flexibility for each of the PUSCH repetitions without creating additional signaling overhead. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE, namely with the list of parameters termed PUSCH time domain resource allocation. In other words, the table is defined by the PUSCH time domain resource allocation list IE as carried in the PUSCH config IE received in form of RRC signaling. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 6. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 6:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASNISTART-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127)numberOfRIVassignmentsINTEGER (0..n)RIVassignmentSEQUENCE {k2′INTEGER (0..32)startSymbolAndLength′INTEGER (0..127)}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP As can be seen from this example 6, the PUSCH time domain resource allocation parameter includes not only values indicating a PUSCH mapping type, a value K2indicating a slot offsets for the initial PUSCH transmission, a value SLIV indicating a start and length indicator for the initial PUSCH transmission, but also a value indicating the number of repetitions (termed number of resource indicator value, RIV, assignments), and for each of the repetitions (termed RIV assignments), a value K2′ indicating a second slot offset for the at least one repetition, a value SLIV′ indicating a second start and length indicator value for the at least one repetition. When comparing the PUSCH time domain resource allocation list IE of example 6 with the RRC configure table of table 1, it can be seen that the value indicating the number of repetitions (termed number of RIV assignments) of the IE is only indirectly reflected in the RRC configured table, namely in form of the total number of each of the values K2′, S′ and L′. This value may, however, also be directly included in the RRC configured table. The additional values shall be explained in further detail with respect to the different usages of the first exemplary implementation as depicted inFIGS.13-18. One Usage of the Sixth Exemplary Implementation One usage of the RRC configured table of the sixth exemplary implementation is depicted inFIGS.13-14where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to a usage of a sixth exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises two additional values K2′ indicating that the allocated resources for the first and second repetition of the initial PUSCH transmission are included in slots relative to the value k corresponding to the number of the slot carrying the received DCI, or corresponding to the value of time domain offset field additionally carried in the received configured grant config IE. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers k+2 and k+3, respectively. Additionally two values S′ and two values L′ are comprised indicating that the allocated resources for the first and second repetition of the initial PUSCH transmission start in the respective slot with slot number k+2 and k+3 at the symbol with symbol numbers 6 and 1, respectively. The respective resource allocations in time domain are also shown. Another Usage of the Sixth Exemplary Implementation Another usage of the RRC configured table of the sixth exemplary implementation is depicted inFIGS.15-16where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to a usage of a sixth exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises two additional values K2′ indicating that the allocated resources for both, the first and second repetition of the initial PUSCH transmission are included in slots relative to the number of the slot k+2 with the allocated resources for the initial PUSCH transmission. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers (k+2)+0 and (k+2)+1, respectively. Additionally two values S′ and two values L′ are comprised indicating that the allocated resources for the first and second repetition of the initial PUSCH transmission start in the respective slot with slot number (k+2)+0 and (k+2)+1 at the symbol with symbol numbers 6 and 1, respectively. The respective resource allocations in time domain are also shown. A Further Usage of the Sixth Exemplary Implementation Another usage of the RRC configured table of the first exemplary implementation is depicted inFIGS.17-18where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to a usage of a first exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises two additional values K2′ indicating that the allocated resources for the first repetition of the initial PUSCH transmission is included in the slots relative to the number of the slot k+2 with the allocated resources for the initial PUSCH transmission, and the second repetition is included in the slot relative to the number of the slot (k+2)+0 with the allocated resources for the first repetition. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers (k+2)+0 and ((k+2)+0)+1, respectively. Additionally two values S′ and two values L′ are comprised indicating that the allocated resources for the first and second repetition of the initial PUSCH transmission start in the respective slot with slot number (k+2)+0 and ((k+2)+0)+1 at the symbol with symbol numbers 6 and 1, respectively. The respective resource allocations in time domain are also shown. In other words, the second slot offset specifies the allocated resources for a subsequent one of the at least one repetition relative to index of a slot with the allocated resources for a preceding one of the at least one repetition. Seventh Exemplary Implementation The following seventh exemplary implementation is conceived with the understanding that the at least one additional value, comprised in the indexed row of the RRC configured table, is at least one of a value G′ indicating a number of symbols of a gap before the allocated resources for the at least one repetition, a value L′ indicating a number of symbols specifying the length of the allocated resources for the at least one repetition, and optionally a value indicating the number of the at least one repetition. With this understanding, the RRC configured table comprises not only values which are specifying allocated resources for the initial PUSCH transmission. Rather the RRC configured table comprises additional values G′ and/or L′ which are specifying allocated resources for the repetition of the initial PUSCH transmission. In addition, the optional additional value indicating the number of the least one repetition may further complement the RRC configured table in that it permits a more flexible determination which of the specified allocated resource are to be used for repetitions. An example of such a RRC configured table is reproduced herein below, namely as Table 2: TABLE 2DCI RowPUSCHindexmapping typeK2SLL′{G}1Type AK2_1S_1L_1L_1′{G_1_1,G_1_2 . . . G_1_n1}2Type BK2_2S_2L_2L_2′{G_2_1,G_2_2 . . . G_2_n2}. . .. . .. . .. . .. . .. . .. . .16. . .. . .. . .. . .. . .. . . In particular, the RRC configured table not only comprises one set of additional values G′ and L′ but instead comprises one additional value L′ which is applicable to all repetitions, and a set of additional values G′ for each of the PUSCH repetitions to be transmitted by the user equipment410. This achieves a high degree of flexibility for each of the PUSCH repetitions without creating additional signaling overhead. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE, namely with the list of parameters termed PUSCH time domain resource allocation. In other words, the table is defined by the PUSCH time domain resource allocation list IE as carried in the PUSCH config IE received in form of RRC signaling. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 7. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 7:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB} ,startSymbolAndLengthINTEGER (0..127)LengthOfEachRepetitionINTEGER (0..32)numberOfRepetitionsINTEGER (0..n)RepetitionGapSEQUENCE {GINTEGER (0..32)}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP As can be seen from this example 7, the PUSCH time domain resource allocation parameter includes not only values indicating a PUSCH mapping type, a value K2indicating a slot offsets for the initial PUSCH transmission, a value SLIV indicating a start and length indicator for the initial PUSCH transmission, but also a value L′ (termed length of each repetition) indicating the length in number of symbols of each repetition, a value indicating the number of repetitions (termed number of repetitions), and for each of the repetitions (termed repetition gap), a value G′ indicating a number of symbols of a gap before the allocated resources for the at least one repetition. When comparing the PUSCH time domain resource allocation list IE of example 7 with the RRC configure table in table 2, it can be seen that the value indicating the number of repetitions (termed number of repetitions) of the IE is only indirectly reflected in the RRC configured table, namely in form of the total number of the values G′. This value may, however, also be directly included in the RRC configured table. The additional values shall be explained in further detail with respect to the different usages of the second exemplary implementation as depicted inFIGS.19-22. One Usage of the Seventh Exemplary Implementation One usage of the RRC configured table of the second exemplary implementation is depicted inFIGS.19-20where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to a usage of a second exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises one additional value L′ indicating the length in number of symbols is 4 for the allocated resources of each of the first and second repetition, and two additional values G′ indicating that the allocated resources for the first and second repetition of the initial PUSCH transmission start at a symbol with a gap G′ of a number of symbols 1, 6 before the allocated resources. For the first and the second repetition, the number of symbols of the gap indicated by value G′ is relative to a number 4 of a last symbol within slot k+2 of the allocated resources for the initial PUSCH transmission. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers k+2. In particular, the number of the last symbol of the allocated resources of the initial PUSCH transmission is 4. Thereby, a gap of 1 symbol determines the allocated resources for the first repetition to start at symbol number 4+1 and to end at symbol number 4+1+4. A gap of 6 symbols determines the allocated resources for the second repetition to start at symbol 4+6 and to end at symbol number 4+6+4. The respective resource allocations in time domain are also shown. Another Usage of the Seventh Exemplary Implementation Another usage of the RRC configured table of the seventh exemplary implementation is depicted inFIGS.21-22where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to another usage of a second exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises one additional value L′ indicating the length in number of symbols is 4 for the allocated resources of each of the first and second repetition, and two additional values G′ indicating that the allocated resources for the first and second repetition of the initial PUSCH transmission start at a symbol with a gap of a number of symbols 1, 6 before the allocated resources. For the first repetition, the number of symbols of the gap indicated by value G′ is relative to a number 4 of a last symbol within slot k+2 of the allocated resources for the initial PUSCH transmission. For the second repetition, the number of the symbols of the gap indicated by value G′ is relative to the number 4+1+4 of a last symbol of the slot k+2 of the allocated resource for the first repetition. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers k+2. In particular, the number of the last symbol of the allocated resources of the initial PUSCH transmission is 4. Thereby, a gap of 1 symbol determines the allocated resources for the first repetition to start at symbol number 4+1 and to end at symbol number 4+1+4. A gap of 1 symbols determines the allocated resources for the second repetition to start at symbol 4+1+4+1 and to end at symbol number 4+1+4+1+4. In other words, the number of symbols of the gap specifies the allocated resources for a subsequent one of the at least one repetition relative to a number of a last symbol of the allocated resources for a preceding one of the at least one repetition. Eighth Exemplary Implementation The following eighth exemplary implementation is conceived with the understanding that the at least one additional value, comprised in the indexed row of the RRC configured table, is at least one of a value G′ indicating a number of symbols of a gap before the allocated resources for the at least one repetition, a value L′ indicating a number of symbols specifying the length of the allocated resources for the at least one repetition, and optionally a value indicating the number of the at least one repetition. With this understanding, the RRC configured table comprises not only values which are specifying allocated resources for the initial PUSCH transmission. Rather the RRC configured table comprises additional values G′ and/or L′ which are specifying allocated resources for the repetition of the initial PUSCH transmission. In addition, the optional additional value indicating the number of the least one repetition may further complement the RRC configured table in that it permits a more flexible determination as to which of the specified allocated resource are to be used for repetitions. An example of such a RRC configured table is reproduced herein below, namely as Table 3: TABLE 3DCI RowPUSCHindexmapping typeK2SL{L′}, {G}1Type AK2_1S_1L_1{L′_1_1, L′_1_2 . . . L′_1_n1},{G_1_1, G_1_2 . . . G_1_n1}2Type BK2_2S_2L_2{L′_2_1, L′_2_2 . . . L′_2_n2},{G_2_1, G_2_2 . . . G_2_n2}. . .. . .. . .. . .. . .. . .16. . .. . .. . .. . .. . . In particular, the RRC configured table not only comprises one set of additional values G′ and L′ but instead comprises a set of additional values G′ and L′ for each of the PUSCH repetitions to be transmitted by the user equipment410. This achieves a high degree of flexibility for each of the PUSCH repetitions without creating additional signaling overhead. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE, namely with the list of parameters termed PUSCH time domain resource allocation. In other words, the table is defined by the PUSCH time domain resource allocation list IE as carried in the PUSCH config IE received in form of RRC signaling. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 8. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 8:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127)numberOfRepetitionsINTEGER (0..n)EachRepetitionSEQUENCE {LengthOfEachRepetitionINTEGER (0..32)GINTEGER (0..32)}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASNISTOP As can be seen from this example 8, the PUSCH time domain resource allocation parameter includes not only values indicating a PUSCH mapping type, a value K2indicating a slot offsets for the initial PUSCH transmission, a value SLIV indicating a start and length indicator for the initial PUSCH transmission, but also a value indicating the number of repetitions (termed number of repetitions), and for each of the repetitions (termed repetition gap), a value L′ (termed length of each repetition) indicating the length in number of symbols of each repetition, and a value G′ indicating a number of symbols of a gap before the allocated resources for the at least one repetition. When comparing the PUSCH time domain resource allocation list IE of example 8 with the RRC configure table in table 3, it can be seen that the value indicating the number of repetitions (termed number of repetitions) of the IE is only indirectly reflected in the RRC configured table, namely in form of the total number of each of the values G′ and L′. This value may, however, also be directly included in the RRC configured table. The additional values shall be explained in further detail with respect to the different usages of the eighth exemplary implementation as depicted inFIGS.23-26. One Usage of the Eighth Exemplary Implementation One usage of the RRC configured table of the eighth exemplary implementation is depicted inFIGS.23-24where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to a usage of a second exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises two additional value L′ indicating the length in number of symbols 4, 3 for the allocated resources of the first and second repetition, and two additional values G′ indicating that the allocated resources, for the first and second repetition of the initial PUSCH transmission, start at a symbol with a gap G′ of a number of symbols 1, 6 before the allocated resources. For the first and the second repetition, the number of symbols of the gap indicated by value G′ is relative to a number 4 of a last symbol within slot k+2 of the allocated resources for the initial PUSCH transmission. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers k+2. In particular, the number of the last symbol of the allocated resources of the initial PUSCH transmission is 4. Thereby, a gap of 1 symbol determines the allocated resources for the first repetition to start at symbol number 4+1 and to end at symbol number 4+1+4. A gap of 6 symbols determines the allocated resources for the second repetition to start at symbol 4+6 and to end at symbol number 4+6+3. The respective resource allocations in time domain are also shown. Another Usage of the Eighth Exemplary Implementation Another usage of the RRC configured table of the eighth exemplary implementation is depicted inFIGS.25-26where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to another usage of a second exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises two additional value L′ indicating the length in number of symbols 4, 3 for the allocated resources of the first and second repetition, and two additional values G′ indicating that the allocated resources, for the first and second repetition of the initial PUSCH transmission, start at a symbol with a gap G′ of a number of symbols 1, 6 before the allocated resources. For the first repetition, the number of symbols of the gap indicated by value G′ is relative to a number 4 of a last symbol within slot k+2 of the allocated resources for the initial PUSCH transmission. For the second repetition, the number of the symbols of the gap indicated by value G′ is relative to the number 4+1+4 of a last symbol of the slot k+2 of the allocated resource for the first repetition. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers k+2. In particular, the number of the last symbol of the allocated resources of the initial PUSCH transmission is 4. Thereby, a gap of 1 symbol determines the allocated resources for the first repetition to start at symbol number 4+1 and to end at symbol number 4+1+4. A gap of 1 symbols determines the allocated resources for the second repetition to start at symbol 4+1+4+1 and to end at symbol number 4+1+4+1+3. In other words, the number of symbols of the gap specifies the allocated resources for a subsequent one of the at least one repetition relative to a number of a last symbol of the allocated resources for a preceding one of the at least one repetition. Ninth Exemplary Implementation The following ninth exemplary implementation is conceived with the understanding that the at least one additional value, comprised in the indexed row of the RRC configured table, is at least one of a value L′ indicating a number of symbols specifying the length of the allocated resources for the at least one repetition, and optionally a value indicating the number of the at least one repetition. With this understanding, the RRC configured table comprises not only values which are specifying allocated resources for the initial PUSCH transmission. Rather the RRC configured table comprises additional values which are specifying allocated resources for the repetition of the initial PUSCH transmission. In addition, the optional additional value indicating the number of the least one repetition may further complement the RRC configured table in that it permits a more flexible determination as to which of the specified allocated resource are to be used for repetitions. An example of such a RRC configured table is reproduced herein below, namely as table 4: TABLE 4DCI RowPUSCHindexmapping typeK2SL{L′}1Type AK2_1S_1L_1{L′_1_1, L′_1_2 . . . L′_1_n1}2Type BK2_2S_2L_2{L′_2_1, L′_2_2 . . . L′_2_n2}. . .. . .. . .. . .. . .. . .16. . .. . .. . .. . .. . . In particular, the RRC configured table not only comprises one additional value L′ but instead comprises a set of additional values L′ for each of the PUSCH repetitions to be transmitted by the user equipment410. This achieves a high degree of flexibility for each of the PUSCH repetitions without creating additional signaling overhead. In particular, the processor430,480of the user equipment410, or of the base station460, configures this table in accordance with the parameters comprised in a PUSCH time domain resource allocation list IE, namely with the list of parameters termed PUSCH time domain resource allocation. In other words, the table is defined by the PUSCH time domain resource allocation list IE as carried in the PUSCH config IE received in form of RRC signaling. An example of such a PUSCH time domain resource allocation list IE is reproduced herein below, namely as example 9. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 9:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASNISTART-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127)numberOfRepetitionsINTEGER (0..n)RepetitionlengthSEQUENCE {LengthOfEachRepetitionINTEGER (0..32)}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP As can be seen from this example 9, the PUSCH time domain resource allocation parameter includes not only values indicating a PUSCH mapping type, a value K2indicating a slot offsets for the initial PUSCH transmission, a value SLIV indicating a start and length indicator for the initial PUSCH transmission, but also a value indicating the number of repetitions (termed number of repetitions), and for each of the repetitions (termed repetition length), a value L′ (termed length of each repetition) indicating the length in number of symbols of each repetition for the at least one repetition. When comparing the PUSCH time domain resource allocation list IE of example 9 with the RRC configure table in table 4, it can be seen that the value indicating the number of repetitions (termed number of repetitions) of the IE is only indirectly reflected in the RRC configured table, namely in form of the total number of the values L′. This value may, however, also be directly included in the RRC configured table. The additional values shall be explained in further detail with respect to the different usage of the fourth exemplary implementation as depicted inFIGS.27-28. One Usage of the Ninth Exemplary Implementation One usage of the RRC configured table of the fourth exemplary implementation is depicted inFIGS.27-28where an exemplary RRC configured table for PUSCH repetitions is given and corresponding resource allocations in time domain are shown according to a usage of a second exemplary implementation. According to the exemplary RRC configured table, in a row with row index 3, values are given for which corresponding resource allocations in time domain are shown. The RRC configured table, comprises, in the row with the row index 3, a value indicating the PUSCH mapping type to be type b, meaning that resource allocations may start within the slot and are not necessarily starting at the beginning of the slot. Further, this row comprises a value K2indicating that allocated resources for the initial PUSCH transmission is included in the slot with slot number k+2. Additionally, values S and L are comprised indicating that the allocated resources for the initial PUSCH transmission start in the slot with slot number k+2 at the symbol with symbol number 1 and have a length of 4 symbols. Additionally, this row comprises two additional value L′ indicating the length in number of symbols 4, 4 for the allocated resources of the first and second repetition. For the first and the second repetition, the start of the allocated resources is contiguously following the last symbol of the allocated resources for the respective one of the initial PUSCH transmission and of the first repetition thereof. Thus, the allocated resources for the first and second repetition are included in the slots with slot numbers k+2. In particular, the number of the last symbol of the allocated resources of the initial PUSCH transmission is 4. Thereby, the allocated resources for the first repetition is determined to start at symbol number 4 and to end at symbol number 4+4. And the allocated resources for the second repetition is determined to start at symbol 4+4 and to end at symbol number 4+4+4. The respective resource allocations in time domain are also shown. Further Exemplary Implementation Referring now to a further exemplary implementation, according to which the behavior of the either first or the second exemplary implementation can be configured at the base station460. For this purpose, an exemplary PUSCH time domain resource allocation list IE can be specified is reproduced herein below, namely as in example 10. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 10:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127)choice of{numberOfRIVassignmentsINTEGER (0..n)RIVassignmentSEQUENCE {k2′INTEGER (0..32)startSymbolAndLength′INTEGER (0..127)}}or{numberOfRepetitionsINTEGER (0..n)EachRepetitionSEQUENCE {LengthOfEachRepetitionINTEGER (0..32)GINTEGER (0..32)}}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP In an even further exemplary implementation, the PUSCH time domain resource allocation list IE additionally comprises a parameter indicating whether the transport block size is calculated for each PUSCH transmission separately, or whether a combined transport block size is calculated for all PUSCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof. This further exemplary implementation may be combined with any one of the sixth to ninth exemplary implementations. If combined with the sixth exemplary implementation, an exemplary PUSCH time domain resource allocation list IE can be specified as reproduced herein below, namely as in example 11. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 11:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127)numberOfRIVassignmentsINTEGER (0..n)RIVassignmentSEQUENCE {k2′INTEGER (0..32)startSymbolAndLength′INTEGER (0..127)}TBSMethodENUMERATED {single, combined}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP Importantly, the example 11 refers to two different calculation mechanism for calculating the transport block size (TBS), namely a combined and a separate TBS calculation. This shall, however not be construed as limitation to the present disclosure. Rather, should an agreement be reached that three or even more different calculation mechanisms are to be used, then a skilled person will readily understand that also the applicable one of the tree or even more different calculation mechanisms can be indicated via the PUSCH time domain resource allocation list IE. In a further exemplary implementation, the PUSCH time domain resource allocation list IE additionally comprises a parameter indicating whether frequency hopping is applied for each PUSCH transmission separately, or whether continuous frequency hopping is applied for all PUSCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof. This further exemplary implementation may be combined with any one of the sixth to ninth exemplary implementations. If combined with the sixth exemplary implementation, an exemplary PUSCH time domain resource allocation list IE can be specified as reproduced herein below, namely as in example 12. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 12:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127)numberOfRIVassignmentsINTEGER (0..n)RIVassignmentSEQUENCE {k2′INTEGER (0..32)startSymbolAndLength′INTEGER (0..127)}FrequencyHoppingMethodENUMERATED {full, half}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP Importantly, the example 12 refers to two different frequency hopping mechanism, namely a mechanism where frequency hopping is applied either separately or to all of the PUSCH transmissions. This shall, however not be construed as limitation to the present disclosure. Rather, should an agreement be reached that three or even more different frequency hopping mechanisms are to be used, then a skilled person will readily understand that also the applicable one of the tree or even more different frequency hopping mechanism can be indicated via the PUSCH time domain resource allocation list IE. In an even further exemplary implementation, the PUSCH time domain resource allocation list IE additionally comprises a parameter indicating whether or not demodulation reference symbols, DMRS, are present in all or each individual one of the at least one repetition of the initial PUSCH transmission. This further exemplary implementation may be combined with any one of the sixth to ninth exemplary implementations. If combined with the sixth exemplary implementation, an exemplary PUSCH time domain resource allocation list IE can be specified as reproduced herein below, namely as in example 13. As the terminology may change in the future, this example shall be more broadly understood with regard to its functions and concepts of signaling the additional parameters comprised in a PUSCH time domain resource allocation list IE. EXAMPLE 13:ASN.1 NOTATION OF “PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST IE”-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList : := SEQUENCE (SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation : := SEQUENCE {k2INTEGER (0..32)OPTIONAL, --Need SmappingTypeENUMERATED {typeA, typeB},startSymbolAndLengthINTEGER (0..127)numberOfRIVassignmentsINTEGER (0..n)RIVassignmentSEQUENCE {k2′INTEGER (0..32)start SymbolAndLength′INTEGER (0..127)DMRSPresentENUMERATED {yes, no}}}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP According to a first aspect, a user equipment, UE, is provided comprising: a receiver, which in operation, receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; the receiver, in operation, receives downlink control information, DCI, in form of medium access control, MAC, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, determines allocated resources for an initial PUSCH transmission and allocated resources for at least one repetition thereof based on: a number of a slot carrying the received DCI, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; and a transmitter, which in operation, transmits a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to a second aspect, a user equipment, UE, is provided comprising: a receiver, which in operation, receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; the receiver, in operation, receives a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, determines allocated resources for an initial PUSCH transmission and allocated resources for at least one repetition thereof based on: a value of time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; and a transmitter, which in operation, transmits a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to a third aspect, which is provided in addition to a first or second aspect, the at least one additional value is one of: a value K2′ indicating a second slot offset for the at least one repetition, a value SLIV′ indicating a second start and length indicator value for the at least one repetition, and a value indicating the number of the at least one repetition, and/or wherein the second start and length indicator value SLIV′ comprises: a value S′ indicating a symbol number specifying the start of the allocated resources for the at least one repetition, and a value L′ indicating a number of symbols specifying the length of the allocated resources for the at least one repetition. According to a fourth aspect, which is provided in addition to a third or fourth aspect, in case the at least one additional value is the value K2′ indicating the second slot offset, the second slot offset specifies the allocated resources for all of the at least one repetition relative to: the number of the slot carrying the received DCI, or the value of time domain offset field additionally carried in the received configured grant config IE. According to a fifth aspect, which is provided in addition to a third or fourth aspect, in case the at least one additional value is the value K2′ indicating the second slot offset, the second slot offset specifies the allocated resources for all of the at least one repetition relative to a number of a slot with the allocated resources for the initial PUSCH transmission. According to a sixth aspect, which is provided in addition to a third or fourth aspect, in case the at least one additional value is the value K2′ indicating the second slot offset, the second slot offset specifies the allocated resources for a first of the at least one repetition relative to a number of a slot with the allocated resources for the initial PUSCH transmission, or the second slot offset specifies the allocated resources for a subsequent one of the at least one repetition relative to a number of a slot with the allocated resources for a preceding one of the at least one repetition. According to a seventh aspect, which is provided in addition to a first or second aspect, the at least one value is one of: a value G′ indicating a number of symbols of a gap before the allocated resources for the at least one repetition, a value L′ indicating a number of symbols specifying the length of the allocated resources for the at least one repetition, and a value indicating the number of the at least one repetition. According to an eighth aspect, which is provided in addition to a seventh aspect, in case the at least one additional value is the value G′ indicating the number of symbols of the gap, the number of symbols of the gap specifies the allocated resources for all of the at least one repetition relative to a number of a last symbol of the allocated resources for the initial PUSCH transmission. According to a ninth aspect, which is provided in addition to an eighth aspect, in case the at least one additional value is the value G′ indicating the number of symbols of the gap, the number of symbols of the gap specifies the allocated resources for a first of the at least one repetition relative to a number of a last symbol of the allocated resources for the initial PUSCH transmission, or the number of symbols of the gap specifies the allocated resources for a subsequent one of the at least one repetition relative to a number of a last symbol of the allocated resources for a preceding one of the at least one repetition. According to a tenth aspect, which is provided in addition to a third or eighth aspect, in case the at least one additional value is the value L′ indicating the number of symbols specifying the length of the allocated resources, the number of symbols specifies the length of the allocated resources for all of the at least one repetition, or the number of symbols specifies the length of the allocated resources for an individual one of the at least one repetition. According to an eleventh aspect, which is provided in addition to one of the first to tenth aspects, the PUSCH time domain resource allocation list IE additionally comprises at least one of: a parameter indicating whether the transport block size is calculated for each PUSCH transmission separately, or whether a combined transport block size is calculated for all PUSCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof, a parameter indicating whether frequency hopping is applied for each PUSCH transmission separately, or whether continuous frequency hopping is applied for all PUSCH transmissions, including the initial PUSCH transmission and the at least one repetition thereof, and a parameter indicating whether or not demodulation reference symbols, DMRS, are present in all or each individual one of the at least one repetition of the initial PUSCH transmission. According to a twelfth aspect, a method for a UE, is provided comprising: receiving a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; receiving downlink control information, DCI, in form of medium access control, MAC, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, determining allocated resources for an initial PUSCH transmission and allocated resources for at least one repetition thereof based on: a number of a slot carrying the received DCI, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; and transmitting a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to a thirteenth aspect, a method for a UE, is provided comprising: receiving a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; receiving configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, determining allocated resources for an initial PUSCH transmission and allocated resources for at least one repetition thereof based on: a value of time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; and transmitting a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to a fourteenth aspect, a base station, BS, is provided comprising: a transmitter, which in operation, transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; the transmitter, in operation, transmits downlink control information, DCI, in form of medium access control, MAC, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, allocates resources for an initial PUSCH transmission and allocates resources for at least one repetition thereof based on: a number of a slot carrying the transmitted DCI, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; and a receiver, which in operation, receives a PUSCH transmission using the respectively allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to a fifteenth aspect, a base station, BS, is provided comprising: a transmitter, which in operation, transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; the transmitter, in operation, transmits a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, allocates resources for an initial PUSCH transmission and allocates resources for at least one repetition thereof based on: a value of time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; and a receiver, in operation, receives a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to a sixteenth aspect, a method for a base station, BS, is provided comprising: transmitting a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; transmitting downlink control information, DCI, in form of medium access control, MAC, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, allocating resources for an initial PUSCH transmission and allocating resources for at least one repetition thereof based on: a number of a slot carrying the transmitted DCI, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; receiving a PUSCH transmission using the respectively allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to a seventeenth aspect, a method for a base station, BS, is provided comprising: transmitting a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, each with a value indicating a PUSCH mapping type, a value K2indicating a slot offsets, and a value SLIV indicating a start and length indicator; transmitting a configured grant config IE in form of RRC signaling carrying a time domain allocation filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, allocating resources for an initial PUSCH transmission and allocating resources for at least one repetition thereof based on: a value of time domain offset field additionally carried in the received configured grant config IE and associated with the time domain allocation filed, and the value K2indicating the slot offsets, and the value SLIV indicating the start and length indicator comprised in indexed row of the RRC configured table; receiving a PUSCH transmission using the respectively determined allocated resources for the initial PUSCH transmission and for the at least one repetition thereof; and wherein the determination of allocated resources is based on at least one additional value comprised in the indexed row of the RRC configured table which is specifying the allocated resources in time domain for the at least one repetition of the initial PUSCH transmission. According to an eighteenth aspect, a user equipment, UE, is provided comprising a receiver, which in operation, receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; the receiver, in operation, receives downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, determines allocated time-domain resources for the plurality of PUSCH transmissions based on the index of the slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; a transmitter, which in operation, selects transport blocks of data to be carried in the plurality of PUSCH transmissions, and transmits the plurality of PUSCH transmissions using the respectively determined allocated time-domain resources; and wherein the transport blocks of data are selected based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a nineteenth aspect, which is provided in addition to the eighteenth aspect, a same one of the at least one second parameter comprised in the indexed row of the RRC configured table is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. According to a twentieth aspect, which is provided in addition to the eighteenth aspect, a different one of the at least one second parameter comprised in the indexed row of the RRC configured table is indicating different or repeated PUSCH transmissions for each of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions According to a twenty-first aspect, which is provide in the eighteenth to twentieth aspect, the at least one second parameter is comprised in the PUSCH time domain resource allocation list IE. According to a twenty-second aspect, a user equipment, UE, is provided, comprising a receiver, which in operation, receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; the receiver, in operation, receives downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, determines allocated time-domain resources for the plurality of PUSCH transmissions based on the index of the slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; a transmitter, which in operation, selects transport blocks of data to be carried in the plurality of PUSCH transmissions, and transmits the plurality of PUSCH transmissions using the respectively determined allocated time-domain resources; and wherein the transport blocks of data are selected based on at least one second parameter conveyed via signaling the received DCI which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a twenty-third aspect, which is provided in addition to the twenty-second aspect, the at least one second parameter is comprised in a dedicated bit field of the received DCI, and a same one of the at least one second parameter is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. According to a twenty-fourth aspect, which is provided in addition to the twenty-second aspect, the receiver, in operation, infers the at least one second parameter from a particular radio network temporary identifier, RNTI, used for scrambling the cyclic redundancy check, CRC, bit field of the received DCI, and same inferred at least one second parameter is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. According to a twenty-fifth aspect, a user equipment, UE, provided comprising a receiver, which in operation, receives a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; the receiver, in operation, receives downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, determines allocated time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; and a transmitter, which in operation, selects transport blocks of data to be carried in the plurality of PUSCH transmissions, and transmits the plurality of PUSCH transmissions using the respectively determined allocated time-domain resources; and wherein the transport blocks of data are selected based on at least one second parameter conveyed via signaling of a physical layer configuration which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a twenty-sixth aspect, which is provided in addition to the twenty-fifth aspect, the receiver, in operation, receives the at least one second parameter comprised in a physical, Phy-, parameter IE in form of RRC signaling, and same received at least one second parameter is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. According to a twenty-seventh aspect, which is provided in addition to the twenty-fifth aspect, the receiver, in operation, infers the at least one second parameter from a radio spectrum configuration of the particular bandwidth part, and same inferred at least one second value is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. According to a twenty-eighth aspect, which is provided in addition to the twenty-fifth aspect, the receiver, in operation, infers the at least one second parameter from a service type configuration having specific reliability and/or latency requirements, and same inferred at least one second value is indicating different or repeated PUSCH transmissions for all of the plurality of PUSCH transmissions. According to a twenty-ninth aspect, which is provided in addition to the eighteenth to twenty-eighth aspect, the determination of allocated time-domain resources is based on the first set of values related to allocated time-domain resources and comprised in each row of the RRC configured table including: a value indicating a PUSCH mapping type for at least a first one of the plurality of PUSCH transmissions, a value K2indicating a slot offsets for at least a first one of the plurality of PUSCH transmissions, and a value SLIV indicating a start and length indicator for at least a first one of the plurality of PUSCH transmissions. According to a thirtieth aspect, which is provided in addition to the eighteenth to twenty-ninth aspect, the determination of allocated time-domain resources is further based on at least one third value related to allocated time-domain resources and comprised in the indexed row of the RRC configured table, including at least one of: a value K2′ indicating another slot offset for a subsequent one of the plurality of PUSCH transmissions, a value SLIV′ indicating another start and length indicator value for a subsequent one of the plurality of PUSCH transmissions, and a value indicating the total number of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions. According to a thirty-first aspect, which is provided in addition to the thirtieth aspect, the other start and length indicator value SLIV′ comprises: a value S′ indicating a symbol number specifying the start of the allocated resources for a subsequent one of the plurality of PUSCH transmissions, and a value L′ indicating a number of symbols specifying the length of the allocated resources for a subsequent one of the plurality of PUSCH transmissions. According to a thirty-second aspect, which is provided in addition to the eighteenth to thirty-first aspect, the transmitter, in operation, further generates the plurality of PUSCH transmission carrying the selected transport blocks of data based on at least one fourth value related to the generation of the plurality of PUSCH transmissions, and also comprised in the indexed row of the RRC configured table, including at least one of: a different modulation and coding scheme, MCS, index value for each of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions, or a same modulation and coding scheme, MCS, index value for all of the plurality of PUSCH transmissions, and a different redundancy version, RV, offset value for each of the plurality of PUSCH transmissions excluding a first of the plurality of PUSCH transmissions, or a same redundancy version, RV, offset value for all of the plurality of PUSCH transmission. According to thirty-third aspect, which is provided in addition to the eighteenth to thirty-second aspect, the PUSCH time domain resource allocation list IE additionally comprises at least one fifth parameter related to the generation of the plurality of PUSCH transmissions, including at least one of: a parameter indicating whether the transport block size is calculated for each of the plurality of PUSCH transmission separately, or whether a combined transport block size is calculated for all PUSCH transmissions, a parameter indicating whether a modulation and coding scheme, MCS, index is determined for each of the plurality of PUSCH transmission separately, or whether the same MCS index is determined for all PUSCH transmissions, a parameter indicating whether or not a same redundancy version, RV, is determined for all of the plurality of PUSCH transmissions based on a RV field in the received DCI, and a parameter indicating whether or not demodulation reference symbols, DMRS, are present in at least a first or in all of the plurality of PUSCH transmission. According to a thirty-fourth aspect, a method for a UE is provided comprising the steps of: receiving a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; receiving downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, determining allocated time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; selecting transport blocks of data to be carried in the plurality of PUSCH transmissions, and transmits the plurality of PUSCH transmissions using the respectively determined allocated time-domain resources; and wherein the transport blocks of data are selected based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a thirty-fifth aspect, a method for a UE is provided comprising the steps of: receiving a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; receiving downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, determining allocated time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; selecting transport blocks of data to be carried in the plurality of PUSCH transmissions, and transmits the plurality of PUSCH transmissions using the respectively determined allocated time-domain resources; and wherein the transport blocks of data are selected based on at least one second parameter conveyed via signaling the received DCI which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a thirty-sixth aspect, a method for a UE is provided comprising the steps of: receiving a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; receiving downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, determining allocated time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; and selecting transport blocks of data to be carried in the plurality of PUSCH transmissions, and transmits the plurality of PUSCH transmissions using the respectively determined allocated time-domain resources; and wherein the transport blocks of data are selected based on at least one second parameter conveyed via signaling of a physical layer configuration which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a thirty-seventh aspect, a base station, BS, is provided comprising: a transmitter, which in operation, transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; the transmitter, in operation, transmits downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, allocates time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; a receiver, which in operation, receives the plurality of PUSCH transmissions using the respectively allocated time-domain resources, and processes transport blocks of data which are carried in the plurality of received PUSCH transmissions; and wherein the transport blocks of data are processed based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a thirty-eighth aspect, a base station, BS, is provided comprising: a transmitter, which in operation, transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; the transmitter, in operation, transmits downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, allocates time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; a receiver, which in operation, receives the plurality of PUSCH transmissions using the respectively allocated time-domain resources, and processes transport blocks of data which are carried in the plurality of received PUSCH transmissions; and wherein the transport blocks of data are processed based on at least one second parameter conveyed via signaling the received DCI which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to thirty-ninth aspect, a base station, BS, is provided comprising: a transmitter, which in operation, transmits a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; a processor, which in operation, configures a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; the transmitter, in operation, transmits downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, the processor, in operation, allocates time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; and a receiver, which in operation, receives the plurality of PUSCH transmissions using the respectively allocated time-domain resources, and processes transport blocks of data which are carried in the plurality of received PUSCH transmissions; and wherein the transport blocks of data are processed based on at least one second parameter conveyed via signaling of a physical layer configuration which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a fortieth aspect, a method for a BS is provided comprising the steps of: transmitting a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; transmitting downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, allocating time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; receiving the plurality of PUSCH transmissions using the respectively allocated time-domain resources, and processes transport blocks of data which are carried in the plurality of received PUSCH transmissions; and wherein the transport blocks of data are processed based on at least one second parameter comprised in the indexed row of the RRC configured table which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a forty-first aspect, a method for a BS is provided comprising the steps of: transmitting a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; transmitting downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, allocating time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; receiving the plurality of PUSCH transmissions using the respectively allocated time-domain resources, and processes transport blocks of data which are carried in the plurality of received PUSCH transmissions; and wherein the transport blocks of data are processed based on at least one second parameter conveyed via signaling the received DCI which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. According to a forty-second aspect, a method for a BS, is provided comprising the steps of: transmitting a physical uplink shared channel, PUSCH, config information element, IE, in form of radio resource control, RRC, signaling, the PUSCH config IE being applicable to a particular bandwidth part; configuring a table which is defined by a PUSCH time domain resource allocation list IE carried in the received PUSCH config IE, the table comprising rows, at least one row comprising a first set of values related to allocated time-domain resources for a plurality of PUSCH transmissions; transmitting downlink control information, DCI, signaling carrying a time-domain resource assignment filed with value m, wherein the value m provides a row index m+1 to the RRC configured table, allocating time-domain resources for the plurality of PUSCH transmissions based on the index of slot carrying the received DCI, and the first set of values related to allocated time-domain resources comprised in the indexed row of the RRC configured table; and receiving the plurality of PUSCH transmissions using the respectively allocated time-domain resources, and processes transport blocks of data which are carried in the plurality of received PUSCH transmissions; and wherein the transport blocks of data are processed based on at least one second parameter conveyed via signaling of a physical layer configuration which is indicating whether the plurality of PUSCH transmissions are either different PUSCH transmissions or repeated PUSCH transmissions. The present disclosure can be realized by software, hardware, or software in cooperation with hardware. Each functional block used in the description of each embodiment described above can be partly or entirely realized by an LSI such as an integrated circuit, and each process described in the each embodiment may be controlled partly or entirely by the same LSI or a combination of LSIs. The LSI may be individually formed as chips, or one chip may be formed so as to include a part or all of the functional blocks. The LSI may include a data input and output coupled thereto. The LSI here may be referred to as an IC, a system LSI, a super LSI, or an ultra LSI depending on a difference in the degree of integration. However, the technique of implementing an integrated circuit is not limited to the LSI and may be realized by using a dedicated circuit, a general-purpose processor, or a special-purpose processor. In addition, a FPGA (Field Programmable Gate Array) that can be programmed after the manufacture of the LSI or a reconfigurable processor in which the connections and the settings of circuit cells disposed inside the LSI can be reconfigured may be used. The present disclosure can be realized as digital processing or analogue processing. If future integrated circuit technology replaces LSIs as a result of the advancement of semiconductor technology or other derivative technology, the functional blocks could be integrated using the future integrated circuit technology. Biotechnology can also be applied. The present disclosure can be realized by any kind of apparatus, device or system having a function of communication, which is referred to as a communication apparatus. Some non-limiting examples of such a communication apparatus include a phone (e.g., cellular (cell) phone, smart phone), a tablet, a personal computer (PC) (e.g., laptop, desktop, netbook), a camera (e.g., digital still/video camera), a digital player (digital audio/video player), a wearable device (e.g., wearable camera, smart watch, tracking device), a game console, a digital book reader, a telehealth/telemedicine (remote health and medicine) device, and a vehicle providing communication functionality (e.g., automotive, airplane, ship), and various combinations thereof. The communication apparatus is not limited to be portable or movable, and may also include any kind of apparatus, device or system being non-portable or stationary, such as a smart home device (e.g., an appliance, lighting, smart meter, control panel), a vending machine, and any other “things” in a network of an “Internet of Things (IoT).” The communication may include exchanging data through, for example, a cellular system, a wireless LAN system, a satellite system, etc., and various combinations thereof. The communication apparatus may comprise a device such as a controller or a sensor which is coupled to a communication device performing a function of communication described in the present disclosure. For example, the communication apparatus may comprise a controller or a sensor that generates control signals or data signals which are used by a communication device performing a communication function of the communication apparatus. The communication apparatus also may include an infrastructure facility, such as a base station, an access point, and any other apparatus, device or system that communicates with or controls apparatuses such as those in the above non-limiting examples. | 222,326 |
11943765 | DETAILED DESCRIPTION Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same reference numbers in different drawings represent the same or similar elements unless otherwise represented. The implementations set forth in the following description of exemplary embodiments do not represent all implementations consistent with the disclosure. Instead, they are merely examples of apparatuses and methods consistent with aspects related to the disclosure as recited in the appended claims. An embodiment of the present disclosure provides a method for data transmission, which is applied to a terminal, and the method includes: transmitting a target alert sequence to a network access device by using a first uplink grant-free transmission resource corresponding to the target alert sequence; where the target alert sequence is configured to notify the network access device that the terminal requests to use the first uplink grant-free transmission resource to transmit uplink data; and transmitting the uplink data by using a transmission resource different from the first uplink grant-free transmission resource, when receiving a collision indication fed back by the network access device in response to the target alert sequence. According to the method for data transmission provided by the embodiment of the present disclosure, the alert sequence is transmitted to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, and the terminal transmits the uplink data by using a transmission resource different from the first uplink grant-free transmission resource, when the network access device determines that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. In this way, the collision problem during transmission through resource multiplexing of multiples users can be avoided, transmission interference can be reduced, demodulation performance can be improved, and service quality can be ensured. It is to be noted that the method for data transmission provided in the embodiment of the present disclosure can be applied to a 3G/4G/5G-based communication network. The terminal according to the present disclosure may include, for example, an electronic device such as a smartphone, a notebook, an in-vehicle device, or an intelligent wearable device. The network access device may include, for example, a communication device, such as a base station or a relay station, which provides a wireless access service for the terminal. Based on the above analysis, the following specific embodiments are presented. FIG.1is a flow chart showing a method for data transmission, which may be executed by a terminal, according to an exemplary embodiment. Referring toFIG.1, the method for data transmission includes steps S101and S102. In step S101, the terminal transmits a target alert sequence to a network access device by using a first uplink grant-free transmission resource corresponding to the target alert sequence, where the target alert sequence is configured to notify the network access device that the terminal requests to use the first uplink grant-free transmission resource corresponding to the target alert sequence to transmit uplink data. For example, before the step S101, the method provided in this embodiment further includes selecting the target alert sequence from pre-acquired at least one candidate alert sequence. The uplink data may include uplink enhanced mobile broadband (eMBB) traffic data or uplink ultra reliable low latency communication (URLLC) traffic data, both of which allow uplink grant-free transmission. For example, the number of the target alert sequence may be 1. In order to obtain more transmission opportunities for the terminal, the terminal may transmit multiple different alert sequences. The number of the alert sequences that the terminal can transmit is determined by the network access device and notified to the terminal through a broadcast message. Alternatively, the terminal may transmit two alert sequences. For example, the network access device predetermines at least one candidate alert sequence, and allocates at least one uplink grant-free transmission resource for the at least one candidate alert sequence. The at least one candidate alert sequence may be a group of sequences predefined by the network access device, and the candidate alert sequences correspond to predefined uplink grant-free transmission resources one-to-one or many-to-many. Furthermore, different candidate alert sequences may be orthogonal to each other to avoid interference. The terminal may obtain the at least one candidate alert sequence in advance by transmitting a notification message to the terminal after the network access device determines the at least one candidate alert sequence. The notification message includes at least one candidate alert sequence and indication information of the uplink grant-free transmission resource, allocated for the at least one candidate alert sequence. The network access device may carry the notification message in the broadcast message, or the network access device may carry the notification message in an uplink grant-free transmission resource configuration message transmitted by the terminal. The terminal receives the notification message from the network access device, and learns the at least one candidate alert sequence and the indication information of the uplink grant-free transmission resource allocated for the at least one candidate alert sequence. Therefore, by carrying the at least one candidate alert sequence and the indication information of uplink grant-free transmission resource allocated for the at least one candidate alert sequence in the notification message issued by the network access device, implementation of the solution can be simplified. In step S102, the terminal transmits the uplink data by using a transmission resource different from the first uplink grant-free transmission resource, when receiving a collision indication fed back by the network access device in response to the target alert sequence. According to the technical solution provided by the embodiment of the disclosure, the alert sequence is predefined, and before transmitting the uplink data, the terminal transmits the target alert sequence to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, and the terminal transmits the uplink data by using the transmission resource different from the first uplink grant-free transmission resource, when the network access device determines that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. In this way, the collision problem during transmission through resource multiplexing of multiples users can be avoided, transmission interference can be reduced, demodulation performance can be improved, and service quality can be ensured. For example, before transmitting the uplink data, the terminal transmits the target alert sequence to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, so as to notify the network access device that the terminal requests to use the first uplink grant-free transmission resource corresponding to the target alert sequence to transmit the uplink data. When receiving the target alert sequence from the terminal, the network access device determines whether the first uplink grant-free transmission resource corresponding to the target alert sequence is currently occupied by other users or other services. When the first uplink grant-free transmission resource corresponding to the target alert sequence is not occupied currently, the network access device does not make any response to the terminal. And the terminal transmits the uplink data to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, when there is no collision indication fed back by the network access device. The network access device transmits a collision indication to the terminal, in response to that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. Herein, the collision indication is configured to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. After receiving the collision indication, the terminal selects a target uplink grant-free transmission resource, for which a collision indication is not received, from the uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence. The terminal transmits the uplink data to the network access device by using the target uplink grant-free transmission resource in an uplink grant-free transmission manner. For example, in response to that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied, the collision indication transmitted by the network access device to the terminal may also include indication information for instructing the terminal to transmit data in a grant-type transmission manner. After receiving the collision indication, the terminal requests the network access device to allocate an available transmission resource for the terminal in the grant-type transmission manner, and then transmits the uplink data by using the allocated available transmission resource. In response to that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied, the implementation manner in which the collision indication transmitted by the network access device to the terminal includes the indication information for instructing the terminal to transmit data in the grant-type transmission manner, may include any one of the following manners.Manner a): when the first uplink grant-free transmission resource is occupied by other users, and the uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence are occupied by other users, the network access device transmits a collision indication to the terminal, and the collision indication includes indication information for instructing the terminal to transmit data in the grant-type transmission manner. The collision indication is configured to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied; and the collision indication instructs the terminal to transmit data in the grant-type transmission manner. After receiving the collision indication, the terminal requests the network access device to allocate the available transmission resource for the terminal in the grant-type transmission manner, and then transmits the uplink data by using the allocated available transmission resource.Manner b): when the first uplink grant-free transmission resource is occupied by other users, and there are transmission resources that are not occupied by other users from the uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence, the network access device transmits the collision indication to the terminal, and the collision indication includes indication information for instructing the terminal to transmit data in the grant-type transmission manner. The collision indication is configured to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied; and the collision indication instructs the terminal to transmit data in the grant-type transmission manner. After receiving the collision indication, the terminal requests the network access device to allocate the available transmission resource for the terminal in the grant-type transmission manner, and then transmits the uplink data by using the allocated available transmission resource.Manner c): when the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied by other users, and there are transmission resources that are not occupied by other users from the uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence, the network access device transmits the collision indication to the terminal to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. After receiving the collision indication, the terminal selects the target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence; and the terminal transmits the uplink data to the network access device by using the target uplink grant-free transmission resource in the uplink grant-free transmission manner. For example, the network access device may carry the collision indication in a downlink control channel or a downlink traffic channel. Alternatively, when learning that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied, the network access device may select a closest resource position that can be used for data transmission. The closest resource position that can be used for transmission refers to a resource position of the channel that can carry the collision indication currently. For example, the terminal may determine the transmission resource and a transmission manner for the uplink data by setting an arrival time threshold of the collision indication, which can be exemplified as follows.a): If the terminal receives the collision indication fed back by the network access device in response to the target alert sequence at a time instant earlier than N−K before the terminal transmits the uplink data, the terminal transmits the uplink data by using the transmission resource different from the first uplink grant-free transmission resource. Where N is a time instant when the terminal transmits the uplink data and the value of K may be predetermined by the network access device and signaled to the terminal. Further, if the terminal receives the collision indication fed back by the network access device in response to the target alert sequence at a time instant earlier than N−K before the terminal transmits the uplink data, the terminal determines whether to receive the indication information for instructing the terminal to transmit data in the grant-type transmission manner. When there is no indication information for instructing the terminal to transmit data in the grant-type transmission manner, the terminal selects the target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence. The terminal transmits the uplink data to the network access device by using the target uplink grant-free transmission resource in the uplink grant-free transmission manner. When receiving the indication information for instructing the terminal to transmit data by using the grant-type transmission manner, the terminal requests the network access device to allocate the available transmission resource for the terminal in the grant-type transmission manner; and then the terminal transmits the uplink data by using the available transmission resource.b): if the terminal does not receive the collision indication fed back by the network access device in response to the target alert sequence at a time instant earlier than N−K before the terminal transmits the uplink data, the terminal determines that the first uplink grant-free transmission resource corresponding to the target alert sequence is not occupied by other users, so that the terminal can transmit the uplink data by directly using the first uplink grant-free transmission resource corresponding to the target alert sequence, and there is no collision problem during transmission through resource multiplexing. According to the technical solution provided by the embodiment of the disclosure, the alert sequence is predefined, and before transmitting the uplink data, the terminal firstly transmits the target alert sequence to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, and the terminal transmits the uplink data by using the transmission resource different from the first uplink grant-free transmission resource, when the network access device determines that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied by other users. Thereby, the collision problem during transmission through resource multiplexing of multiples users can be avoided, transmission interference can be reduced, demodulation performance can be improved, and service quality can be ensured. In one embodiment, step S102includes step C1and step C2: In step C1, the terminal selects a target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence. In step C2, the terminal transmits the uplink data to the network access device by using the target uplink grant-free transmission resource in an uplink grant-free transmission manner. According to the technical solution provided by the embodiment of the disclosure, when receiving the collision indication fed back by the network access device in response to the target alert sequence, the terminal learns that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied, and then the terminal transmits the uplink data by using the uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence, so as to reduce the network access delay of the terminal. In one embodiment, the collision indication includes indication information for instructing the terminal to transmit data in a grant-type transmission manner. Step102includes step D1and step D2. In step D1, the terminal requests the network access device to allocate an available transmission resource for the terminal in the grant-type transmission manner. In step D2, the terminal transmits the uplink data by using the available transmission resource. According to the technical solution provided in the embodiment of the present disclosure, when receiving indication information from the network access device for instructing the terminal to transmit data in the grant-type transmission manner, the terminal can directly transmit data in the grant-type transmission manner. In this way, the collision problem during transmission through resource multiplexing of multiples users can be avoided and the transmission interference can be reduced. In one embodiment, the number of the target alert sequence(s) is 1 or 2. Two target alert sequences can used to increase the transmission opportunities of the terminal. FIG.2is a flow chart showing a method for data transmission, which may be executed by a network access device, according to an exemplary embodiment. Parts of the embodiment not described in detail may be referred to the embodiment ofFIG.1. Referring toFIG.2, the method includes steps S201-S203. In step S201, the network access device receives a target alert sequence from a terminal. In step S202, the network access device determines whether a first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. In step S203, the network access device transmits a collision indication to the terminal in response to that the first uplink grant-free transmission resource is occupied. Herein, the collision indication is configured to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. For example, when receiving the target alert sequence from the terminal, the network access device determines whether the first uplink grant-free transmission resource corresponding to the target alert sequence is currently occupied by other users or other services. When the first uplink grant-free transmission resource corresponding to the target alert sequence is not occupied currently, the network access device does not make a response to the terminal. And when there is no collision indication fed back by the network access device, the terminal transmits the uplink data to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence. When the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied, the network access device transmits the collision indication to the terminal to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. After receiving the collision indication, the terminal selects the target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence. The terminal transmits the uplink data to the network access device by using the target uplink grant-free transmission resource in an uplink grant-free transmission manner. According to the technical solution provided by the embodiment of the disclosure, the alert sequence is predefined, and before transmitting the uplink data, the terminal transmits the alert sequence to the network access device. When determining that the first uplink grant-free transmission resource corresponding to the alert sequence is occupied, the network access device notifies the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied, so that the terminal can transmit the uplink data by using the transmission resource different from the first uplink grant-free transmission resource. In this way, the collision problem during transmission through resource multiplexing of multiples users can be avoided, transmission interference can be reduced, demodulation performance can be improved, and service quality can be ensured. In one embodiment, the method further includes determining at least one candidate alert sequence, allocating at least one uplink grant-free transmission resource for the at least one candidate alert sequence, and transmitting a notification message to the terminal. Herein, the notification message includes the at least one candidate alert sequence and indication information of the at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. In one embodiment, the collision indication includes indication information for instructing the terminal to transmit data in a grant-type transmission manner. In one embodiment, the step of transmitting the collision indication to the terminal includes carrying the collision indication in a downlink control channel or a downlink traffic channel. FIG.3is a flow chart showing a method for data transmission, which is implemented by a terminal in cooperation with a network access device, according to an exemplary embodiment. As shown inFIG.3, based on the embodiments shown inFIGS.1and2, the method for data transmission according to the present disclosure may include steps S301-S307. In step S301, the network access device determines at least one candidate alert sequence and allocates at least one uplink grant-free transmission resource for the at least one candidate alert sequence. In step S302, the network access device transmits a notification message to the terminal, where the notification message includes the at least one candidate alert sequence and the at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. The terminal receives the notification message from the network access device, and acquires the at least one candidate alert sequence and indication information of the at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. In step S303, before transmitting the uplink data, the terminal selects the target alert sequence from the pre-acquired at least one candidate alert sequence. In step S304, the terminal transmits the target alert sequence to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence. Herein, the target alert sequence is configured to notify the network access device that the terminal requests to use the first uplink grant-free transmission resource to transmit the uplink data. In step S305, when receiving the target alert sequence from the terminal, the network access device determines whether the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. When the first uplink grant-free transmission resource is occupied, the method proceeds to step306. When the first uplink grant-free transmission resource is not occupied, the network access device does not feedback the collision indication to the terminal, and the flow in network access device side ends. When there is no collision indication fed back by the network access device, the terminal transmits the uplink data to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence. In step S306, the network access device transmits the collision indication to the terminal, where the collision indication is configured to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. In step S307, the terminal transmits the uplink data by using a transmission resource different from the first uplink grant-free transmission resource, when receiving the collision indication fed back by the network access device in response to the target alert sequence. For example, the terminal selects a target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence. The terminal transmits the uplink data to the network access device by using the target uplink grant-free transmission resource in an uplink grant-free transmission manner. For example, the collision indication includes indication information for instructing the terminal to transmit data in a grant-type transmission manner. The terminal requests the network access device to allocate an available transmission resource for the terminal in the grant-type transmission manner. The terminal transmits the uplink data by using the available transmission resource. According to the technical solution provided by the embodiment of the disclosure, the alert sequence is predefined, and before transmitting the uplink data, the terminal transmits the alert sequence to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, and then the terminal transmits the uplink data by using the transmission resource different from the first uplink grant-free transmission resource, when the network access device determines that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. In this way, the collision problem during transmission through resource multiplexing of multiples users can be avoided, transmission interference can be reduced, demodulation performance can be improved, and service quality can be ensured. The following are embodiments for apparatuses of the present disclosure, which may be configured to implement the embodiments for the methods of the present disclosure. Parts of the embodiments for the apparatuses not described in detail may be referred to the embodiments for the methods. FIG.4is a block diagram of an apparatus for data transmission, which may be applied to a terminal, according to an exemplary embodiment. Referring toFIG.4, the apparatus for data transmission includes a first transmitting module401and a second transmitting module402. Herein, the first transmitting module401is configured to transmit a target alert sequence to a network access device by using a first uplink grant-free transmission resource corresponding to the target alert sequence, where the target alert sequence is configured to notify the network access device that the terminal requests to use the first uplink grant-free transmission resource to transmit uplink data. The second transmitting module402is configured to transmit the uplink data by using a transmission resource different from the first uplink grant-free transmission resource, when receiving a collision indication fed back by the network access device in response to the target alert sequence. According to the apparatus provided by the embodiment of the present disclosure, the alert sequence is predefined, and before transmitting the uplink data, the terminal transmits the alert sequence to the network access device by using the first uplink grant-free transmission resource corresponding to the alert sequence, and then the terminal transmits the uplink data by using the transmission resource different from the first uplink grant-free transmission resource, when the network access device determines that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. Thereby, the collision problem during transmission through resource multiplexing of multiples users can be avoided, transmission interference can be reduced, demodulation performance can be improved, and service quality can be ensured. In one embodiment, referring toFIG.5, the apparatus for data transmission shown inFIG.4may further include a first receiving module501, which is configured to receive a notification message from the network access device. Herein, the notification message includes at least one candidate alert sequence determined by the network access device, and indication information of at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. In one embodiment, referring toFIG.6, the apparatus for data transmission shown inFIG.4may further include a third transmitting module601, which is configured to transmit the uplink data to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, when there is no collision indication fed back by the network access device. In one embodiment, referring toFIG.7, the second transmitting module402from the apparatus for data transmission shown inFIG.4may be further configured to include a selection submodule701and a first transmitting submodule702. Herein, the selection submodule701is configured to select a target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence. The first transmitting submodule702is configured to transmit the uplink data to the network access device by using the target uplink grant-free transmission resource in an uplink grant-free transmission manner. In one embodiment, the collision indication includes indication information for instructing the terminal to transmit data in a grant-type transmission manner. Referring toFIG.8, the second transmitting module402from the apparatus for data transmission shown inFIG.4may be further configured to include a resource request submodule801and a second transmitting submodule802. Herein, the resource request submodule801is configured to request the network access device to allocate an available transmission resource for the terminal in the grant-type transmission manner. The second transmitting submodule802is configured to transmit the uplink data by using the available transmission resource. FIG.9is a block diagram of an apparatus for data transmission, which may be applied to a network access device, according to an exemplary embodiment. Referring toFIG.9, the apparatus for data transmission includes a second receiving module901, a judgement module902, and a fourth transmitting module903. Herein, the second receiving module901is configured to receive a target alert sequence from a terminal. The judgement module902is configured to determine whether a first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. The fourth transmitting module903is configured to transmit a collision indication to the terminal in response to that the first uplink grant-free transmission resource is occupied, where the collision indication is configured to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. In one embodiment, referring toFIG.10, the apparatus for data transmission shown inFIG.9may further include a determination module1001and a fifth transmitting module1002. Herein, the determination module1001is configured to determine at least one candidate alert sequence and allocate at least one uplink grant-free transmission resource for the at least one candidate alert sequence. The fifth transmitting module1002is configured to transmit a notification message to the terminal, where the notification message includes the at least one candidate alert sequence and indication information of the at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. In one embodiment, the fourth transmitting module902carries the collision indication in a downlink control channel or a downlink traffic channel. FIG.11is a block diagram of an apparatus1100for data transmission, which is applied to a terminal, according to an exemplary embodiment. The apparatus1100for data transmission includes:a processor1101;a memory1102for storing a computer program executable by the processor1101;herein, the processor1101is configured to:transmit a target alert sequence to a network access device by using a first uplink grant-free transmission resource corresponding to the target alert sequence; wherein the target alert sequence is configured to notify the network access device that the terminal requests to use the first uplink grant-free transmission resource to transmit uplink data; andtransmit the uplink data by using a transmission resource different from the first uplink grant-free transmission resource, when receiving a collision indication fed back by the network access device in response to the target alert sequence. In one embodiment, the processor1101may further be configured to:receive a notification message from the network access device, where the notification message comprises at least one candidate alert sequence determined by the network access device, and indication information of at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. In one embodiment, the processor1101may further be configured to:transmit the uplink data to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, when there is no collision indication fed back by the network access device. In one embodiment, the processor1101may further be configured to:select a target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence; andtransmit the uplink data to the network access device by using the target uplink grant-free transmission resource in an uplink grant-free transmission manner. In one embodiment, the collision indication includes indication information for instructing the terminal to transmit data in a grant-type transmission manner. The processor1101may further be configured to:request the network access device to allocate an available transmission resource for the terminal in the grant-type transmission manner; andtransmit the uplink data by using the available transmission resource. In one embodiment, the number of the target alert sequence is 1 or 2. In one embodiment, the uplink data comprises: uplink enhanced mobile broadband (eMBB) traffic data, or uplink ultra reliable low latency communication (URLLC) traffic data. FIG.12is a block diagram of an apparatus1200for data transmission, which is applied to a network access device, according to an exemplary embodiment. The apparatus1200for data transmission includes:a processor1201;a memory1202for storing a computer program executable by the processor1201;herein, the processor1201is configured to:receive a target alert sequence from a terminal;determine whether a first uplink grant-free transmission resource corresponding to the target alert sequence is occupied; andtransmit a collision indication to the terminal in response to that the first uplink grant-free transmission resource is occupied, where the collision indication is configured to notify the terminal that the first uplink grant-free transmission resource corresponding to the target alert sequence is occupied. In one embodiment, the processor1201may also be configured to:determine at least one candidate alert sequence and allocate at least one uplink grant-free transmission resource for the at least one candidate alert sequence; andtransmit a notification message to the terminal, where the notification message comprises the at least one candidate alert sequence and indication information of the at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. In one embodiment, the collision indication includes indication information for instructing the terminal to transmit data in a grant-type transmission manner. In one embodiment, the processor1201may further be configured to:carry the collision indication in a downlink control channel or a downlink traffic channel. With respect to the apparatuses in the aforementioned embodiments, the specific manner in which the various modules perform operations has been described in detail in the related embodiments for the methods, and will not be described in detail herein. FIG.13is a block diagram of an apparatus for data transmission according to an exemplary embodiment. The apparatus1300for data transmission is applicable to a terminal. The apparatus1300for data transmission may include one or more of the following components: a processing component1302, a memory1304, a power component1306, a multimedia component1308, an audio component1310, an input/output (I/O) interface1312, a sensor component1314, and a communication component1316. The processing component1302generally controls the overall operation of the apparatus1300for data transmission, such as operations associated with displays, telephone calls, data communications, camera operations, and recording operations. The processing component1302may include one or more processors1320to execute instructions to perform all or a portion of the steps of the methods described above. In addition, the processing component1302may include one or more modules to facilitate interaction between the processing component1302and other components. For example, the processing component1302may include a multimedia module to facilitate interaction between the multimedia component1308and the processing component1302. The memory1304is configured to store various types of data to support the operation at the apparatus1300for data transmission. Examples of such data include instructions for any applications or methods operated on the apparatus1300for data transmission, contact data, phonebook data, messages, pictures, video, etc. The memory1304may be implemented using any type of volatile or non-volatile memory devices, or a combination thereof, such as a static random access memory (SRAM), an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a programmable read-only memory (PROM), a read-only memory (ROM), a magnetic memory, a flash memory, a magnetic or optical disk. The power component1306provides power to various components of the apparatus1300for data transmission. The power component1306may include a power management system, one or more power sources, and any other components associated with the generation, management, and distribution of power in the apparatus1300for data transmission. The multimedia component1308includes a screen providing an output interface between the apparatus1300for data transmission and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes the touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may not only sense a boundary of a touch or swipe action, but also sense a period of time and a pressure associated with the touch or swipe action. In some embodiments, the multimedia component1308includes a front camera and/or a rear camera. The front camera and the rear camera may receive an external multimedia datum while the apparatus1300for data transmission is in an operation mode, such as a photographing mode or a video mode. Each of the front camera and the rear camera may be a fixed optical lens system or have focus and optical zoom capability. The audio component1310is configured to output and/or input audio signals. For example, the audio component1310includes a microphone (“MIC”) configured to receive an external audio signal when the apparatus1300for data transmission is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may be further stored in the memory1304or transmitted via the communication component1316. In some embodiments, the audio component1310further includes a speaker to output audio signals. The I/O interface1312provides an interface between the processing component1302and peripheral interface modules, such as a keyboard, a click wheel, buttons, and the like. The buttons may include, but are not limited to, a home button, a volume button, a starting button, and a locking button. The sensor component1314includes one or more sensors to provide status assessments of various aspects of the apparatus1300for data transmission. For instance, the sensor component1314may detect an open/closed status of the apparatus1300for data transmission, relative positioning of components, e.g., the display and the keypad, of the apparatus1300for data transmission, a change in position of the apparatus1300for data transmission or a component of the apparatus1300for data transmission, a presence or absence of user contact with the apparatus1300for data transmission, an orientation or an acceleration/deceleration of the apparatus1300for data transmission, and a change in temperature of the apparatus1300for data transmission. The sensor component1314may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component1314may also include a light sensor, such as a complementary metal oxide semiconductor (CMOS) or charge coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor component1314may also include an accelerometer sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor. The communication component1316is configured to facilitate communication, wired or wirelessly, between the apparatus1300for data transmission and other apparatuses. The apparatus1300for data transmission can access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof. In one exemplary embodiment, the communication component1316receives a broadcast signal or broadcast associated information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component1316further includes a near field communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on a radio frequency identification (RFID) technology, an infrared data association (IrDA) technology, an ultra-wideband (UWB) technology, a Bluetooth (BT) technology, and other technologies. In exemplary embodiments, the apparatus1300for data transmission may be implemented with one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, or other electronic components, for performing the above described methods. In exemplary embodiments, there is also provided a non-transitory computer-readable storage medium including instructions, such as included in the memory1304, executable by the processor1320in the apparatus1300for data transmission, for performing the above-described methods. For example, the non-transitory computer-readable storage medium may be a ROM, a compact disc read only memory (CD-ROM), a magnetic tape, a floppy disc, an optical data storage device, and the like. FIG.14is a block diagram illustrating an apparatus for data transmission according to an exemplary embodiment. For example, the apparatus1400for data transmission may be provided as a server. The apparatus1400for data transmission includes a processing component1402(that further includes one or more processors), and memory resources represented by a memory1403configured for storing instructions, such as applications, that may be executed by the processing component1402. The application stored in the memory1403may include one or more modules, each corresponding to a set of instructions. In addition, the processing component1402is configured to execute instructions to perform the methods described above. The apparatus1400for data transmission may also include a power component1406configured to perform power management of the apparatus1400for data transmission, a wired or wireless network interface1405configured to connect the apparatus1400for data transmission to a network, and an input/output (I/O) interface1408. The apparatus1400for data transmission may operate based on an operating system stored in the memory1403, such as Windows Server™, Mac OS X™, Unix™ Linux™, FreeBSD™, or the like. A non-temporary computer-readable storage medium, for example, may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, or the like. When the instructions in the storage medium are executed by the processor of the apparatus1300for data transmission or the apparatus1400for data transmission, which is enabled to perform a method including:transmitting a target alert sequence to a network access device by using a first uplink grant-free transmission resource corresponding to the target alert sequence, where the target alert sequence is configured to notify the network access device that the terminal requests to use the first uplink grant-free transmission resource to transmit uplink data; andtransmitting the uplink data by using a transmission resource different from the first uplink grant-free transmission resource, when receiving a collision indication fed back by the network access device in response to the target alert sequence. In one embodiment, the method further includes:receiving a notification message from the network access device, where the notification message comprises at least one candidate alert sequence determined by the network access device, and indication information of at least one uplink grant-free transmission resource allocated for the at least one candidate alert sequence. In one embodiment, the method further includes:transmitting the uplink data to the network access device by using the first uplink grant-free transmission resource corresponding to the target alert sequence, when there is no collision indication fed back by the network access device. In one embodiment, the transmitting the uplink data by using the transmission resource different from the first uplink grant-free transmission resource includes:selecting a target uplink grant-free transmission resource from uplink grant-free transmission resources pre-allocated for the terminal except the first uplink grant-free transmission resource corresponding to the target alert sequence; andtransmitting the uplink data to the network access device by using the target uplink grant-free transmission resource in an uplink grant-free transmission manner. In one embodiment, the collision indication includes indication information for instructing the terminal to transmit data in a grant-type transmission manner. The uplink data by using the transmission resource different from the first uplink grant-free transmission resource, includes:requesting the network access device to allocate an available transmission resource for the terminal in the grant-type transmission manner; andtransmitting the uplink data by using the available transmission resource. In one embodiment, the number of target alert sequences is 1 or 2. In one embodiment, the uplink data comprises: uplink enhanced mobile broadband (eMBB) traffic data, or uplink ultra reliable low latency communication (URLLC) traffic data. Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed here. This application is intended to cover any variations, uses, or adaptations of the disclosure following the general principles thereof and including such departures from the present disclosure as come within known or customary practice in the art. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims. It will be appreciated that the present disclosure is not limited to the exact construction that has been described above and illustrated in the accompanying drawings, and that various modifications and changes can be made without departing from the scope thereof. It is intended that the scope of the disclosure only be limited by the appended claims. | 51,950 |
11943766 | DESCRIPTION OF EMBODIMENTS According to legacy LTE systems (Rel. 10 to 14), a reference signal for measuring a channel state on downlink is specified. A reference signal for channel state measurement is also referred to as a Cell-specific Reference Signal (CRS) or a Channel State Information-Reference Signal (CSI-RS), and is a reference signal that is used to measure CSI such as a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI) or a Rank Indicator (RI) that is a channel state. A UE feeds back a result measured based on the reference signal for channel state measurement as Channel State Information (CSI) to a base station (that may be a network, an eNB, a gNB or a transmission/reception point) at a given timing. As a CSI feedback method, a Periodic CSI (P-CSI) reporting and an Aperiodic CSI (A-CSI) reporting are specified. When reporting P-CSI, the UE feeds back P-CSI per given periodicity (e.g., a 5 subframe periodicity or a 10 subframe periodicity). The UE transmits the P-CSI by using an uplink control channel of a given cell (e.g., a Primary Cell (PCell), a PUCCH cell or a Primary Secondary Cell (PSCell)). When uplink data (e.g., PUSCH) is not transmitted at a given timing (given subframe) at which the P-CSI is reported, the UE transmits the P-CSI by using an uplink control channel (e.g., PUCCH). On the other hand, when uplink data is transmitted at the given timing, the UE can transmit P-CSI by using an uplink shared channel. When reporting A-CSI, the UE transmits A-CSI in response to a CSI trigger (CSI request) from the base station. For example, the UE reports the A-CSI a given timing (e.g., 4 subframes) after receiving the CSI trigger. The CSI trigger notified from the base station is included in downlink control information (e.g., DCI format 0/4) for an uplink scheduling grant (UL grant) that is transmitted by using a downlink control channel. In addition, the UL grant may be DCI for scheduling transmission of UL data (e.g., PUSCH) and/or transmission of a UL sounding (measurement) signal. The UE reports the A-CSI by using an uplink shared channel indicated by the UL grant in response to the trigger included in the downlink control information for the UL grant. Furthermore, when CA is applied, the UE can receive a UL grant (including an A-CSI trigger) for a certain cell by a downlink control channel of another cell. It is studied for a future radio communication system (also referred to as NR) to report CSI by using a different configuration from those of legacy LTE systems. Although the legacy LTE systems support dynamically controlling triggering of a CSI reporting, NR assumes that a reference signal (e.g., CSI-RS) used to measure or report CSI is dynamically triggered. For example, the base station uses DCI to instruct the UE to trigger an aperiodic CSI-RS. In one example, the base station uses a DCI format (e.g., DCI format 1_1) used to schedule a PDSCH to notify the UE of a resource (CSI-RS resource) to which the CSI-RS is allocated. The CSI-RS may be a Zero Power CSI-RS (ZP CSI-RS) whose transmission power is configured to zero. The base station may use a code point of a bit field included in the DCI to notify the UE of a given CSI-RS resource set ID. CSI-RS resource set candidates may be configured in advance from the base station to the UE by a higher layer (e.g., RRC signaling). For example, the UE may decide that a CSI-RS resource set ID #1 is triggered when the code point of the DCI is “01”, a CSI-RS resource set ID #2 is triggered when the code point of the DCI is “10”, and a CSI-RS resource set ID #3 is triggered when the code point of the DCI is “11”. In addition, the number of bits of the bit field used to give notification of the CSI-RS resource set is not limited to 2. Thus, by dynamically allocating CSI-RS resources when necessary instead of semi-statically allocating the CSI-RS resources, it is possible to flexibly control allocation of a resource used for CSI measurement, and improve resource use efficiency. On the other hand, a case is also assumed where, when a CSI-RS resource (e.g., ZP CSI-RS resource set) is dynamically allocated, the CSI-RS resource and another signal or channel contend. For example, a case is assumed where the CSI-RS resource and DL data (e.g., PDSCH) resource to be transmitted to the UE overlap. In this case, it is conceived to perform puncture processing or rate-matching processing on one (PDSCH) of the PDSCH and the CSI-RS resource, and perform reception processing on at least one of the PDSCH and the CSI-RS. Performing the puncture processing on data refers to performing encoding assuming that resources allocated for the data can be used (or without taking an unavailable resource amount into account), yet not mapping encoded symbols on resources (e.g., CSI-RS resources) that cannot be actually used (i.e., keeping resources unused). By not using the encoded symbols of the punctured resources for decoding on a reception side, it is possible to suppress deterioration of characteristics due to the puncturing. Performing the rate-matching processing on data refers to controlling the number of bits after encoding (encoded bits) by taking actually available radio resources into account. When the number of encoded bits is smaller than the number of bits that can be mapped on the actually available radio resources, at least part of the encoded bits may be repeated. When the number of encoded bits is larger than the number of bits that can be mapped, part of the encoded bits may be deleted. By performing rate-matching processing, encoding is performed while taking into account a resource that becomes actually available, so that it is possible to efficiently perform encoding compared to puncture processing. Consequently, by, for example, applying rate-matching processing instead of puncture processing, it is possible to more efficiently perform encoding and generate a signal or a channel of higher quality, so that it is possible to improve communication quality. On the other hand, when rate-matching processing is applied, the reception side cannot perform demodulation unless the reception side knows that the rate-matching has been applied. However, when puncture processing is applied, the reception side can appropriately perform a reception operation even if the reception side does not know that the puncture processing has been applied. Furthermore, it is assumed that a processing load of rate-matching processing (e.g., transmission processing or reception processing to which the rate-matching processing is applied) is higher than that of puncture processing (e.g., transmission processing or reception processing to which the rate-matching processing is applied). Therefore, it is preferable to apply the puncture processing to transmission/reception without a spare processing time, and apply the rate-matching processing to transmission/reception with the spare processing time. Therefore, it is conceived to perform puncture processing on one (e.g., PDSCH) of a CSI-RS and the PDSCH from a viewpoint of communication quality when the CSI-RS and the PDSCH overlap. By the way, a case is also assumed where, when communication is performed by using a plurality of cells (or CCs) (e.g., CA), a cell that transmits DCI and a cell that triggers a CSI-RS (or a CSI-RS resource) by the DCI are different (seeFIG.1).FIG.1illustrates one example of a case where DCI #1 transmitted by a CC #1 triggers a CSI-RS of a CC #2 (or allocates a CSI-RS resource), and DCI #2 transmitted by the CC #2 schedules a PDSCH of the CC #2. Furthermore,FIG.1illustrates a case where a CSI-RS resource and a PDSCH resource indicated by pieces of DCI transmitted respectively by different cells are configured to overlap. Thus, according to NR, it is also conceived to permit (or support) overlapping of a PDSCH resource scheduled by DCI of a given cell, and a CSI-RS resource triggered by DCI transmitted by another cell. In this case, when receiving the PDSCH scheduled by the given cell, the UE needs to take into account pieces of DCI (e.g., whether or not a CSI-RS is triggered (or a CSI-RS resource is allocated) by DCI of each cell) transmitted by all cells. Hence, a case also occurs where, when a CSI-RS and a PDSCH overlap, the UE has difficulty in applying rate-matching processing to the PDSCH. The inventors of the present invention have conceived an appropriate UE operation and base station operation in a case where a CSI-RS is dynamically triggered by taking into account that there is a case where a cell that transmits DCI for triggering the CSI-RS and a cell that triggers the CSI-RS by the DCI are different, or a case where the DCI for triggering the CSI-RS and DCI for scheduling a PDSCH are different. An embodiment according to the present disclosure will be described in detail below with reference to the drawings. Each aspect may be each applied alone or may be applied in combination. In this description, “overlap” means that a plurality of signals or channels are transmitted (scheduled) in the same resource (e.g., at least one of a frequency resource or a time resource), yet the meaning of “overlap” is not limited to this. “Overlap” includes a case, too, where part of resources of a plurality of signals or channels overlap. In the following description, a CSI-RS may be read as an A-CSI-RS, a Zero Power CSI-RS (ZP CSI-RS) or a Non Zero Power CSI-RS (NZP CSI-RS). (First Aspect) According to the first aspect, when a PDSCH resource (e.g., Resource Element (RE)) and an A-CSI-RS resource overlap, application of rate-matching processing to a PDSCH is restricted based on a given condition. <UE Operation 1-1> A UE assumes a case (case 1) where a CC (or a cell) that transmits DCI for triggering a CSI-RS and a CC that triggers the CSI-RS are different, and the CSI-RS and the PDSCH are configured to the same resource. In this case, the UE may perform reception processing assuming that rate-matching processing is not applied to the PDSCH (seeFIG.2). FIG.2illustrates a case where DCI #1 transmitted by a CC #1 triggers a CSI-RS of a CC #2 (or allocates the CSI-RS resource), and the CSI-RS and a PDSCH transmitted by the CC #2 overlap. The PDSCH may be scheduled by DCI #2 transmitted by the CC #2. InFIG.2, the UE performs reception processing on the PDSCH assuming that rate-matching processing is not applied to the PDSCH that overlaps the CSI-RS (e.g., a part that overlaps the CSI-RS). In this case, the UE may perform reception processing assuming that puncture processing is applied to the PDSCH. Furthermore, the UE may measure and report CSI by using the CSI-RS transmitted by an A-CSI-RS resource (e.g., a resource in which the PDSCH has been punctured) notified by DCI. On the other hand, in a case other than the case 1, the UE may perform reception processing assuming that, even when the CSI-RS and the PDSCH are configured to the same resource, rate-matching processing is applied to the PDSCH (seeFIG.3).FIG.3illustrates a case where the DCI #2 transmitted by the CC #2 triggers the CSI-RS of the CC #2 (or allocates the CSI-RS resource), and schedules a PDSCH transmitted by the CC #2. In this case, the UE performs reception processing on the PDSCH and the CSI-RS assuming that rate-matching processing is applied to the PDSCH. In this regard, a configuration other than the case 1 is not limited to that inFIG.3. Consequently, compared to a case where puncture processing is always performed when the CSI-RS and the PDSCH are configured to the same resource, it is possible to apply rate-matching processing to cases other than the case 1, so that it is possible to improve communication quality. In addition, the case 1 may be a case where a CC that transmits DCI for triggering the CSI-RS and a CC that transmits DCI for scheduling the PDSCH are different, and the CSI-RS and the PDSCH are configured to the same resource. Alternatively, the case 1 may be a case where DCI for triggering the CSI-RS and DCI for scheduling the PDSCH are different, and the CSI-RS and the PDSCH are configured to the same resource. <UE Operation 1-2> The UE may control application of rate-matching processing to a PDSCH based on supported or reported UE capability. For example, a case is assumed where the UE reports given UE capability information. The given UE capability information may be at least one of whether or not cross-carrier scheduling is supported, and whether or not a DL search space is commonly supported for CA. For example, the UE that supports cross-carrier scheduling between CCs to which the same numerology is applied notifies a base station of that the UE supports cross-carrier scheduling. Furthermore, the UE that has capability for sharing a DL search space of a plurality of CCs to which CA is applied (or capability for making it possible to configure DCI of a plurality of CCs to a common DL search space). The UE that has this UE capability can perform reception processing with high performance even when a signal or a channel transmitted (or triggered) by a given cell is scheduled (or triggered) by DCI of another cell. In a case where the UE has the given UE capability, when a CSI-RS and a PDSCH are configured to the same resource, the UE may perform reception processing assuming that rate-matching processing is applied to the PDSCH. That is, when reporting the given UE capability information, the UE may perform rate-matching processing on the PDSCH irrespectively of a cell that transmits DCI for triggering the CSI-RS, a CC that triggers the CSI-RS and a cell that transmits DCI used to schedule the PDSCH. Consequently, even when the CSI-RS resource and the PDSCH resource overlap, the UE that has the given UE capability can apply rate-matching processing to the PDSCH, so that it is possible to improve communication quality. On the other hand, when the UE does not have the given UE capability, the UE may perform control to perform the above UE operation 1. <UE Operation 1-3> The UE may control application of rate-matching processing to a PDSCH based on whether or not a higher layer parameter associated with supported or reported UE capability is configured. For example, a case is assumed where the UE reports given UE capability information. In this regard, the given UE capability information may be the same as the capability information described in the UE operation 2. When a higher layer parameter associated with the given UE capability is configured from the base station, the UE may perform reception processing assuming that rate-matching processing is applied to a PDSCH that is scheduled to the same resource as that of a CSI-RS. When, for example, the UE gives notification of that the UE supports cross-carrier scheduling, and the higher layer parameter regarding control of the cross-carrier scheduling is configured from the base station, the UE assumes that rate-matching processing is applied to the PDSCH. Consequently, even when a CSI-RS resource and a PDSCH resource overlap, the UE to which the higher layer parameter associated with the given UE capability has been configured can apply rate-matching processing to the PDSCH, so that it is possible to improve communication quality. On the other hand, when the higher layer parameter associated with the given UE capability is not configured to the UE, the UE may perform control to perform the above UE operation 1. <Variation 1> When a cell that transmits DCI for triggering a CSI-RS and a cell that triggers the CSI-RS are different, the UE may operate as follows. Except in a case where the given condition holds, the UE performs reception processing assuming that a PDSCH is not rate-matched in a resource in which the CSI-RS (e.g., a Non Zero Power CSI-RS (NZP CSI-RS)) and the PDSCH overlap. Consequently, it is possible to suppress an increase in a UE processing load. The case where the given condition holds corresponds to a case where, in an overlapping resource, a CSI-RS is triggered by UL DCI (e.g., DCI used to schedule a PDSCH), and a last symbol in a time domain of a PDCCH in which the UL DCI is transmitted is received at least a given number of symbols (e.g., 14 symbols) before a first symbol of the PDSCH. In addition, an SCS that serves as a criterion to decide the number of symbols may be the smallest SCS among CCs in which the PDSCH and the PDCCH are transmitted. Consequently, when a reception processing time can be reserved, it is possible to apply rate-matching processing, and improve communication quality. Alternatively, the UE performs reception processing assuming that the PDSCH is not rate-matched in a resource in which a CSI-RS (e.g., ZP CSI-RS) resource triggered (or scheduled) by DL DCI other than DCI for scheduling the PDSCH, and the PDSCH overlap. <Variation 2> When a cell that transmits DCI for triggering a CSI-RS and a cell that triggers the CSI-RS are the same, and resources of the CSI-RS and the PDSCH overlap, the UE may operate as follows. The UE may perform reception processing assuming that the PDSCH is not rate-matched in the overlapping resource. In this case, the UE may assume that the PDSCH is punctured. Except in a case where the given condition holds, the UE may perform reception processing assuming that the PDSCH is not rate-matched in a resource in which the CSI-RS (e.g., NZP CSI-RS) and the PDSCH overlap. The case where the given condition holds corresponds to a case where, in the overlapping resource, a CSI-RS is triggered by UL DCI (e.g., DCI used to schedule a PUSCH), and a last symbol in the time domain of a PDCCH in which the UL DCI is transmitted is received at least a given number of symbols (e.g., 7 symbols) before a first symbol of the PDSCH. In addition, an SCS that serves as a criterion to decide the number of symbols may be the smallest SCS among CCs in which the PDSCH and the PDCCH are transmitted. (Second Aspect) According to the second aspect, in given cases, control is performed such that a CSI-RS and a PDSCH are not configured to the same resource. For example, in the given cases, a UE does not assume that the CSI-RS and the PDSCH are configured to the same resource, or controls reception of the PDSCH and the CSI-RS assuming that a CSI-RS resource and a PDSCH resource do not overlap. The given cases may be at least one of following (1) to (3).(1) A case where DCI for scheduling a PDSCH and DCI for triggering a CSI-RS are transmitted by different CCs (or cells)(2) A case where for scheduling a PDSCH and DCI for triggering a CSI-RS are different(3) A case where a CC (or a cell) that transmits DCI for triggering a CSI-RS, and a CC that triggers a CSI-RS are different In one of the above cases (1) to (3), the UE performs reception processing assuming that the CSI-RS and the PDSCH are not configured to the same resource. In this case, a base station controls allocation of resources of the CSI-RS and the PDSCH such that the CSI-RS and the PDSCH are not configured to the same resource in the above cases (1) to (3). Thus, by performing control such that the CSI-RS and the PDSCH are not configured to the same resource in the given cases, it is possible to suppress the CSI-RS from puncturing the PDSCH. Consequently, it is possible to simplify a UE operation, and reduce a UE processing load. In addition, a case also occurs where the CSI-RS and the PDSCH are configured to the same resource in cases other than the above cases (1) to (3). In this case, the UE may perform reception processing assuming that rate-matching processing (or puncture processing) is applied to the PDSCH. On the other hand, when a PDSCH resource scheduled by first DCI and a CSI-RS resource triggered by second DCI overlap in one of the above cases (1) to (3), the UE may perform control to perform at least one of following operations (2-1 to 2-4). <UE Operation 2-1> The UE performs control to measure (or receive) a CSI-RS and not to perform reception processing on a PDSCH. In this case, the UE may ignore DCI for scheduling the PDSCH. <UE Operation 2-2> The UE performs control to perform reception processing on a PDSCH and not to measure (or receive) a CSI-RS. In this case, the UE may ignore DCI for triggering the CSI-RS. <UE Operation 2-3> The UE performs control not to measure (or receive) a CSI-RS and not to perform reception processing on a PDSCH. In this case, the UE may ignore DCI for scheduling the PDSCH and DCI for triggering the CSI-RS. <UE Operation 2-4> The UE performs control to measure (or receive) a CSI-RS and to perform reception processing on a PDSCH, too. In this case, the UE may perform reception processing assuming that the PDSCH is punctured. When not measuring the CSI-RS (e.g., the UE operation 2-2 or 2-3), the UE may perform control not to transmit a CSI-RS measurement result (or a CSI-RS reporting) For example, the UE may transmit the CSI-RS measurement result to the base station without including the CSI-RS measurement result in a given reporting result. The given reporting result may be a result of at least one of a beam reporting, beam failure detection, Radio Link Monitoring (RLM), CSI measurement and Radio Resource Management (RRM). Alternatively, when not measuring the CSI-RS (e.g., the UE operation 2-2 or 2-3), the UE may include the CSI-RS measurement result in the given reporting result assuming that a value that is not based on the triggered CSI-RS has been measured. The value that is not based on the CSI-RS may be a value calculated uniquely by the UE, or may be, for example, a previously measured result (e.g., latest measurement result) or a value calculated based on the previously measured result. When measuring the CSI-RS (e.g., the UE operation 2-1 or 2-4), the UE may include the CSI-RS measurement result (or the CSI-RS reporting) in the given reporting result to transmit. Alternatively, the UE may transmit the CSI-RS measurement result without including the CSI-RS measurement result in the given reporting result. When not receiving the PDSCH (e.g., the UE operation 2-1 or 2-3), the UE may perform control to transmit NACK for the PDSCH. The base station that has received the NACK from the UE controls retransmission of the PDSCH. Alternatively, the UE may perform control not to transmit the NACK for the PDSCH. In this case, the base station controls retransmission of the PDSCH assuming that the UE does not receive the PDSCH when resources of the CSI-RS and the PDSCH overlap. Consequently, it is possible to simplify the UE operation. When receiving the PDSCH (e.g., the UE operation 2-2 or 2-4), the UE may perform control to transmit HARQ-ACK (ACK or NACK) for the PDSCH. The base station that has received the HARQ-ACK from the UE controls retransmission of the PDSCH. Alternatively, the UE may perform control not to transmit the HARQ-ACK for the PDSCH. Thus, by performing control such that the CSI-RS and the PDSCH are not configured to the same resource in the given cases, it is possible to simplify reception processing of the CSI-RS and the PDSCH in the UE. (Third Aspect) According to the third aspect, control is performed to apply a given process time in given cases. For example, a UE applies different process times in the given cases, and in cases other than the given cases (other cases). The given cases may be at least one of following (1) to (3).(1) A case where DCI for scheduling a PDSCH and DCI for triggering a CSI-RS are transmitted by different CCs (or cells)(2) A case where DCI for scheduling a PDSCH and DCI for triggering a CSI-RS are different(3) A case where a CC (or a cell) that transmits DCI for triggering a CSI-RS, and a CC that triggers a CSI-RS are different The process time may be a duration (e.g., symbols) taken until the UE reports CSI after measuring the CSI. Alternatively, the process time may be a duration taken until the UE reports CSI after receiving a CSI-RS resource. For example, in the given cases, the UE may control the CSI-RS measurement and the CSI reporting by applying a longer process time than those of the other cases. The process time applied in the given cases, and process times applied in the other cases (e.g., normal cases) may be defined in a table. For example, a process time may be defined per subcarrier spacing. In one example, a table in which two types of process times (e.g., Z(1) and Z′(1)) are defined per subcarrier spacing (e.g., 15 kHz, 30 kHz, 60 kHz and 120 kHz) may be used for the normal cases (seeFIG.4). Furthermore, a table in which one type of a process time (e.g., Z″(1)) is defined per subcarrier spacing may be used for the given cases (seeFIG.4). In addition, values inFIG.4are one example, and are not limited to these. In this case, the process time (e.g., Z″(1)) to be applied to the given cases may be configured longer than the process times (e.g., Z(1) and Z′(1)) to be applied to the normal cases to at least one subcarrier spacing. InFIG.4, for example, X1 may be made larger than 9 or 10, X2 may be made larger than 13, X3 may be made larger than 25, and X4 may be made larger than 43. Naturally, values of X1 to X4 are not limited to these. In addition, the process time applied by the UE may be configured by using at least one of a higher layer (e.g., RRC signaling) and downlink control information from a base station, or may be autonomously selected by the UE. Alternatively, the process time of the given cases may be determined based on the process times of the normal cases. For example, in addition to the two types of the process times (e.g., Z(1) and Z′(1)) of the normal cases, process times (e.g., X and X′) of the given cases matching the two types of the process times may be defined. In this case, the process times to be applied to the given cases may be configured longer than the process times to be applied to the normal cases to at least one subcarrier spacing. Thus, by configuring the process times of the given cases longer than the process times of the other cases, a great number of UEs can appropriately report CSI even when a cell that transmits DCI for triggering the CSI-RS and a cell that triggers the CSI-RS are different. <UE Operation 3-1> When there is a sufficient process time (e.g., the process time is a given value or more), the UE may assume that a PDSCH in the given cases is subjected to rate-matching processing. On the other hand, when the process time is less than the given value, the UE may not assume that the PDSCH in the given cases is scheduled. For example, the UE may perform control not to receive the PDSCH, or may perform control to ignore DCI that has scheduled the PDSCH (i.e., control not to receive the DCI). In addition, the process times described herein may be the above-described process times (at least one of Z(1), Z′(1), Z″(1), X and X′), or may be process times for another operation (e.g., an operation performed until a PDSCH is received after DCI is received). Furthermore, the UE may assume that a CSI-RS is measured (or received). Alternatively, the UE may assume that the CSI-RS is not measured (or received). <UE Operation 3-2> When there is a sufficient process time (when, for example, the process time is the given value or more), the UE may assume that a PDSCH in the given cases is subjected to rate-matching processing. On the other hand, when the process time is less than the given value, the UE may perform control to receive the PDSCH assuming that the PDSCH in the given cases is not subjected to rate-matching processing. In addition, the process times described herein may be the above-described process times (at least one of Z(1), Z′(1), Z″(1), X and X′), or may be process times for another operation (e.g., an operation performed until a PDSCH is received after DCI is received). Furthermore, the UE may perform reception processing (e.g., decoding or demodulation) on the PDSCH assuming that a CSI-RS is not transmitted. In this case, the UE may ignore DCI (or DCK field) for triggering the CSI-RS. Alternatively, the UE may perform reception processing on the PDSCH assuming that the PDSCH is punctured in a resource of the PDSCH that overlaps the CSI-RS. Thus, by controlling reception processing of at least one of the PDSCH and the CSI-RS based on a given process time, it is possible to appropriately perform reception processing by taking processing capability or a processing load of the UE into account. (Radio Communication System) The configuration of the radio communication system according to an embodiment of the present disclosure will be described below. This radio communication system uses at least one or a combination of the radio communication method described in the above embodiment to perform communication. FIG.5is a diagram illustrating one example of a schematic configuration of the radio communication system according to the one embodiment. A radio communication system1can apply Carrier Aggregation (CA) and/or Dual Connectivity (DC) that aggregate a plurality of base frequency blocks (component carriers) whose 1 unit is a system bandwidth (e.g., 20 MHz) of the LTE system. In this regard, the radio communication system1may be referred to as Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the 4th generation mobile communication system (4G), the 5th generation mobile communication system (5G), New Radio (NR), Future Radio Access (FRA) and the New Radio Access Technology (New-RAT), or a system that realizes these techniques. Furthermore, the radio communication system1may support dual connectivity between a plurality of Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). ML-DC may include, for example, Dual Connectivity of LTE and NR (EN-DC: E-UTRA-NR Dual Connectivity) where a base station (eNB) of LTE (E-UTRA) is a Master Node (MN), and a base station (gNB) of NR is a Secondary Node (SN), and dual connectivity of NR and LTE (NE-DC: NR-E-UTRA Dual Connectivity) where a base station (gNB) of NR is an MN, and a base station (eNB) of LTE (E-UTRA) is an SN. The radio communication system1includes a base station11that forms a macro cell C1of a relatively wide coverage, and base stations12(12ato12c) that are located in the macro cell C1and form small cells C2narrower than the macro cell C1. Furthermore, a user terminal20is located in the macro cell C1and each small cell C2. An arrangement and the numbers of respective cells and the user terminals20are not limited to the aspect illustrated inFIG.5. The user terminal20can connect with both of the base station11and the base stations12. The user terminal20is assumed to concurrently use the macro cell C1and the small cells C2by using CA or DC. Furthermore, the user terminal20can apply CA or DC by using a plurality of cells (CCs) (e.g., five CCs or less or six CCs or more). The user terminal20and the base station11can communicate by using a carrier (also referred to as a legacy carrier) of a narrow bandwidth in a relatively low frequency band (e.g., 2 GHz). On the other hand, the user terminal20and each base station12may use a carrier of a wide bandwidth in a relatively high frequency band (e.g., 3.5 GHz or 5 GHz) or may use the same carrier as that used between the user terminal20and the base station11. In this regard, a configuration of the frequency band used by each base station is not limited to this. Furthermore, the user terminal20can perform communication by using Time Division Duplex (TDD) and/or Frequency Division Duplex (FDD) in each cell. Furthermore, each cell (carrier) may be applied a single numerology or may be applied a plurality of different numerologies. The numerology may be a communication parameter to be applied to transmission and/or reception of a certain signal and/or channel, and may indicate at least one of, for example, a subcarrier spacing, a bandwidth, a symbol length, a cyclic prefix length, a subframe length, a TTI length, the number of symbols per TTI, a radio frame configuration, specific filtering processing performed by a transceiver in a frequency domain, and specific windowing processing performed by the transceiver in a time domain. For example, a case where subcarrier spacings of constituent OFDM symbols are different and/or a case where the numbers of OFDM symbols are different on a certain physical channel may be read as that numerologies are different. The base station11and each base station12(or the two base stations12) may be connected by way of wired connection (e.g., optical fibers compliant with a Common Public Radio Interface (CPRI) or an X2 interface) or radio connection. The base station11and each base station12are each connected with a higher station apparatus30and connected with a core network40via the higher station apparatus30. In this regard, the higher station apparatus30includes, for example, an access gateway apparatus, a Radio Network Controller (RNC) and a Mobility Management Entity (MME), yet is not limited to these. Furthermore, each base station12may be connected with the higher station apparatus30via the base station11. In this regard, the base station11is a base station that has a relatively wide coverage, and may be referred to as a macro base station, an aggregate node, an eNodeB (eNB) or a transmission/reception point. Furthermore, each base station12is a base station that has a local coverage, and may be referred to as a small base station, a micro base station, a pico base station, a femto base station, a Home eNodeB (HeNB), a Remote Radio Head (RRH) or a transmission/reception point. The base stations11and12will be collectively referred to as a base station10below when not distinguished. Each user terminal20is a terminal that supports various communication schemes such as LTE and LTE-A, and may include not only a mobile communication terminal (mobile station) but also a fixed communication terminal (fixed station). The radio communication system1applies Orthogonal Frequency-Division Multiple Access (OFDMA) to downlink and applies Single Carrier-Frequency Division Multiple Access (SC-FDMA) and/or OFDMA to uplink as radio access schemes. OFDMA is a multicarrier transmission scheme that divides a frequency band into a plurality of narrow frequency bands (subcarriers) and maps data on each subcarrier to perform communication. SC-FDMA is a single carrier transmission scheme that divides a system bandwidth into bands including one or contiguous resource blocks per terminal and causes a plurality of terminals to use respectively different bands to reduce an inter-terminal interference. In this regard, uplink and downlink radio access schemes are not limited to a combination of these schemes, and other radio access schemes may be used. The radio communication system1uses a downlink shared channel (PDSCH: Physical Downlink Shared Channel) shared by each user terminal20, a broadcast channel (PBCH: Physical Broadcast Channel) and a downlink L1/L2 control channel as downlink channels. User data, higher layer control information and a System Information Block (SIB) are conveyed on the PDSCH. Furthermore, a Master Information Block (MIB) is conveyed on the PBCH. The downlink L1/L2 control channel includes at least one of downlink control channels (a Physical Downlink Control Channel (PDCCH) and/or an Enhanced Physical Downlink Control Channel (EPDCCH)), a Physical Control Format Indicator Channel (PCFICH), and a Physical Hybrid-ARQ Indicator Channel (PHICH). Downlink Control Information (DCI) including scheduling information of the PDSCH and/or the PUSCH is conveyed on the PDCCH. In addition, the scheduling information may be notified by the DCI. For example, DCI for scheduling DL data reception may be referred to as a DL assignment, and DCI for scheduling UL data transmission may be referred to as a UL grant. The number of OFDM symbols used for the PDCCH is conveyed on the PCFICH. Transmission acknowledgement information (also referred to as, for example, retransmission control information, HARQ-ACK or ACK/NACK) of a Hybrid Automatic Repeat reQuest (HARQ) for the PUSCH is conveyed on the PHICH. The EPDCCH is subjected to frequency division multiplexing with the PDSCH (downlink shared data channel) and is used to convey DCI similar to the PDCCH. The radio communication system1uses an uplink shared channel (PUSCH: Physical Uplink Shared Channel) shared by each user terminal20, an uplink control channel (PDCCH: Physical Uplink Control Channel), and a random access channel (PRACH: Physical Random Access Channel) as uplink channels. User data and higher layer control information are conveyed on the PUSCH. Furthermore, downlink radio link quality information (CQI: Channel Quality Indicator), transmission acknowledgement information and a Scheduling Request (SR) are conveyed on the PUCCH. A random access preamble for establishing connection with a cell is conveyed on the PRACH. The radio communication system1conveys a Cell-specific Reference Signal (CRS), a Channel State Information-Reference Signal (CSI-RS), a DeModulation Reference Signal (DMRS) and a Positioning Reference Signal (PRS) as downlink reference signals. Furthermore, the radio communication system1conveys a Sounding Reference Signal (SRS) and a DeModulation Reference Signal (DMRS) as uplink reference signals. In this regard, the DMRS may be referred to as a user terminal-specific reference signal (UE-specific reference signal). Furthermore, a reference signal to be conveyed is not limited to these. <Base Station> FIG.6is a diagram illustrating one example of an overall configuration of the base station according to the one embodiment. The base station10includes pluralities of transmission/reception antennas101, amplifying sections102and transmitting/receiving sections103, a baseband signal processing section104, a call processing section105and a communication path interface106. In this regard, the base station10only needs to be configured to include one or more of each of the transmission/reception antennas101, the amplifying sections102and the transmitting/receiving sections103. User data transmitted from the base station10to the user terminal20on downlink is input from the higher station apparatus30to the baseband signal processing section104via the communication path interface106. The baseband signal processing section104performs processing of a Packet Data Convergence Protocol (PDCP) layer, segmentation and concatenation of the user data, transmission processing of a Radio Link Control (RLC) layer such as RLC retransmission control, Medium Access Control (MAC) retransmission control (e.g., HARQ transmission processing), and transmission processing such as scheduling, transmission format selection, channel coding, Inverse Fast Fourier Transform (IFFT) processing, and precoding processing on the user data, and transfers the user data to each transmitting/receiving section103. Furthermore, the baseband signal processing section104performs transmission processing such as channel coding and inverse fast Fourier transform on a downlink control signal, too, and transfers the downlink control signal to each transmitting/receiving section103. Each transmitting/receiving section103converts a baseband signal precoded and output per antenna from the baseband signal processing section104into a radio frequency range, and transmits a radio frequency signal. The radio frequency signal subjected to frequency conversion by each transmitting/receiving section103is amplified by each amplifying section102, and is transmitted from each transmission/reception antenna101. The transmitting/receiving sections103can be composed of transmitters/receivers, transmission/reception circuits or transmission/reception apparatuses described based on a common knowledge in a technical field according to the present disclosure. In this regard, the transmitting/receiving sections103may be composed as an integrated transmitting/receiving section or may be composed of transmitting sections and receiving sections. Meanwhile, each amplifying section102amplifies a radio frequency signal received by each transmission/reception antenna101as an uplink signal. Each transmitting/receiving section103receives the uplink signal amplified by each amplifying section102. Each transmitting/receiving section103performs frequency conversion on the received signal into a baseband signal, and outputs the baseband signal to the baseband signal processing section104. The baseband signal processing section104performs Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing, error correcting decoding, MAC retransmission control reception processing, and reception processing of an RLC layer and a PDCP layer on user data included in the input uplink signal, and transfers the user data to the higher station apparatus30via the communication path interface106. The call processing section105performs call processing (such as configuration and release) of a communication channel, state management of the base station10and radio resource management. The communication path interface106transmits and receives signals to and from the higher station apparatus30via a given interface. Furthermore, the communication path interface106may transmit and receive (backhaul signaling) signals to and from the another base station10via an inter-base station interface (e.g., optical fibers compliant with the Common Public Radio Interface (CPRI) or the X2 interface). In addition, each transmitting/receiving section103may further include an analog beam forming section that performs analog beam forming. The analog beam forming section can be composed of an analog beam forming circuit (e.g., a phase shifter or a phase shift circuit) or an analog beam forming apparatus (e.g., a phase shifter) described based on the common knowledge in the technical field according to the present disclosure. Furthermore, each transmission/reception antenna101can be composed of an array antenna, for example. Furthermore, each transmitting/receiving section103is configured to be able to apply single BF and multiple BF. Each transmitting/receiving section103may transmit a signal by using a transmission beam, and receive a signal by using a reception beam. Each transmitting/receiving section103may transmit and/or receive a signal by using a given beam determined by a control section301. Each transmitting/receiving section103may receive and/or transmit various pieces of information described in each of the above embodiment from and/or to the user terminal20. For example, each transmitting/receiving section103transmits a downlink shared channel and a Channel State Information (CSI) reference signal. Furthermore, each transmitting/receiving section103receives DCI for scheduling the downlink shared channel, and DCI for triggering the CSI reference signal. FIG.7is a diagram illustrating one example of a function configuration of the base station according to the one embodiment. In addition, this example mainly illustrates function blocks of characteristic portions according to the present embodiment, and assumes that the base station10includes other function blocks, too, that are necessary for radio communication. The baseband signal processing section104includes at least the control section (scheduler)301, a transmission signal generating section302, a mapping section303, a received signal processing section304and a measurement section305. In addition, these components only need to be included in the base station10, and part or all of the components may not be included in the baseband signal processing section104. The control section (scheduler)301controls the entire base station10. The control section301can be composed of a controller, a control circuit or a control apparatus described based on the common knowledge in the technical field according to the present disclosure. The control section301controls, for example, signal generation of the transmission signal generating section302and signal allocation of the mapping section303. Furthermore, the control section301controls signal reception processing of the received signal processing section304and signal measurement of the measurement section305. The control section301controls scheduling (e.g., resource allocation) of system information, a downlink data signal (e.g., a signal that is transmitted on the PDSCH), and a downlink control signal (e.g., a signal that is transmitted on the PDCCH and/or the EPDCCH and is, for example, transmission acknowledgement information). Furthermore, the control section301controls generation of a downlink control signal and a downlink data signal based on a result obtained by deciding whether or not it is necessary to perform retransmission control on an uplink data signal. The control section301controls scheduling of synchronization signals (e.g., PSS/SSS) and downlink reference signals (e.g., a CRS, a CSI-RS and a DMRS). The control section301may perform control for forming a transmission beam and/or a reception beam by using digital BF (e.g., precoding) in the baseband signal processing section104and/or analog BF (e.g., phase rotation) in each transmitting/receiving section103. In a given case (e.g., a case where first downlink control information for scheduling the downlink shared channel and second downlink control information for triggering the CSI-RS are transmitted by different cells), the control section301may perform control such that a resource for the downlink shared channel and a resource for the CSI-RS do not overlap. The transmission signal generating section302generates a downlink signal (such as a downlink control signal, a downlink data signal or a downlink reference signal) based on an instruction from the control section301, and outputs the downlink signal to the mapping section303. The transmission signal generating section302can be composed of a signal generator, a signal generating circuit or a signal generating apparatus described based on the common knowledge in the technical field according to the present disclosure. The transmission signal generating section302generates, for example, a DL assignment for giving notification of downlink data allocation information, and/or a UL grant for giving notification of uplink data allocation information based on the instruction from the control section301. The DL assignment and the UL grant are both DCI, and conform to a DCI format. Furthermore, the transmission signal generating section302performs encoding processing and modulation processing on the downlink data signal according to a code rate and a modulation scheme determined based on Channel State Information (CSI) from each user terminal20. Various CSI reportings are received via a PUCCH and a PUSCH. The mapping section303maps the downlink signal generated by the transmission signal generating section302, on given radio resources based on the instruction from the control section301, and outputs the downlink signal to each transmitting/receiving section103. The mapping section303can be composed of a mapper, a mapping circuit or a mapping apparatus described based on the common knowledge in the technical field according to the present disclosure. The received signal processing section304performs reception processing (e.g., demapping, demodulation and decoding) on a received signal input from each transmitting/receiving section103. In this regard, the received signal is, for example, an uplink signal (such as an uplink control signal, an uplink data signal or an uplink reference signal) transmitted from the user terminal20. The received signal processing section304can be composed of a signal processor, a signal processing circuit or a signal processing apparatus described based on the common knowledge in the technical field according to the present disclosure. The received signal processing section304outputs information decoded by the reception processing to the control section301. When, for example, receiving the PUCCH including HARQ-ACK, the received signal processing section304outputs the HARQ-ACK to the control section301. Furthermore, the received signal processing section304outputs the received signal and/or the signal after the reception processing to the measurement section305. The measurement section305performs measurement related to the received signal. The measurement section305can be composed of a measurement instrument, a measurement circuit or a measurement apparatus described based on the common knowledge in the technical field according to the present disclosure. For example, the measurement section305may perform Radio Resource Management (RRM) measurement or Channel State Information (CSI) measurement based on the received signal. The measurement section305may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), a Signal to Interference plus Noise Ratio (SINR) or a Signal to Noise Ratio (SNR)), a signal strength (e.g., a Received Signal Strength indicator (RSSI)) or channel information (e.g., CSI). The measurement section305may output a measurement result to the control section301. <User Terminal> FIG.8is a diagram illustrating one example of an overall configuration of the user terminal according to the one embodiment. The user terminal20includes pluralities of transmission/reception antennas201, amplifying sections202and transmitting/receiving sections203, a baseband signal processing section204and an application section205. In this regard, the user terminal20only needs to be configured to include one or more of each of the transmission/reception antennas201, the amplifying sections202and the transmitting/receiving sections203. Each amplifying section202amplifies a radio frequency signal received at each transmission/reception antenna201. Each transmitting/receiving section203receives a downlink signal amplified by each amplifying section202. Each transmitting/receiving section203performs frequency conversion on the received signal into a baseband signal, and outputs the baseband signal to the baseband signal processing section204. The transmitting/receiving sections203can be composed of transmitters/receivers, transmission/reception circuits or transmission/reception apparatuses described based on the common knowledge in the technical field according to the present disclosure. In this regard, the transmitting/receiving sections203may be composed as an integrated transmitting/receiving section or may be composed of transmitting sections and receiving sections. The baseband signal processing section204performs FFT processing, error correcting decoding and retransmission control reception processing on the input baseband signal. The baseband signal processing section204transfers downlink user data to the application section205. The application section205performs processing related to layers higher than a physical layer and an MAC layer. Furthermore, the baseband signal processing section204may transfer broadcast information of the downlink data, too, to the application section205. On the other hand, the application section205inputs uplink user data to the baseband signal processing section204. The baseband signal processing section204performs retransmission control transmission processing (e.g., HARQ transmission processing), channel coding, preceding, Discrete Fourier Transform (DFT) processing and IFFT processing on the uplink user data, and transfers the uplink user data to each transmitting/receiving section203. Each transmitting/receiving section203converts the baseband signal output from the baseband signal processing section204into a radio frequency range, and transmits a radio frequency signal. The radio frequency signal subjected to the frequency conversion by each transmitting/receiving section203is amplified by each amplifying section202, and is transmitted from each transmission/reception antenna201. Each transmitting/receiving section203receives the downlink shared channel and the Channel State Information (CSI) reference signal. Furthermore, each transmitting/receiving section203receives the DCI for scheduling the downlink shared channel, and the DCI for triggering the CSI reference signal. FIG.9is a diagram illustrating one example of a function configuration of the user terminal according to the one embodiment. In addition, this example mainly illustrates function blocks of characteristic portions according to the present embodiment, and assumes that the user terminal20includes other function blocks, too, that are necessary for radio communication. The baseband signal processing section204of the user terminal20includes at least a control section401, a transmission signal generating section402, a mapping section403, a received signal processing section404and a measurement section405. In addition, these components only need to be included in the user terminal20, and part or all of the components may not be included in the baseband signal processing section204. The control section401controls the entire user terminal20. The control section401can be composed of a controller, a control circuit or a control apparatus described based on the common knowledge in the technical field according to the present disclosure. The control section401controls, for example, signal generation of the transmission signal generating section402and signal allocation of the mapping section403. Furthermore, the control section401controls signal reception processing of the received signal processing section404and signal measurement of the measurement section405. The control section401obtains from the received signal processing section404a downlink control signal and a downlink data signal transmitted from the base station10. The control section401controls generation of an uplink control signal and/or an uplink data signal based on a result obtained by deciding whether or not it is necessary to perform retransmission control on the downlink control signal and/or the downlink data signal. The control section401may control reception processing of the downlink shared channel based on at least one of cells that respectively transmit first downlink control information used to schedule the downlink shared channel, and second downlink control information used to trigger the CSI reference signal, the cells that respectively transmit the second downlink control information and the CSI reference signal, and resources that are respectively indicated by the first downlink control information and the second downlink control information. When, for example, the cell that transmits the second downlink control information and the cell that triggers the CSI reference signal based on the second downlink control information are different, and when resources of the downlink shared channel and the CSI reference signal overlap, the control section401may control reception processing assuming that the downlink shared channel is not rate-matched. Furthermore, the control section401may decide whether or not the downlink shared channel is rate-matched based on whether or not given UE capability is supported or whether or not the given UE capability is configured from the base station. Furthermore, when the first downlink control information and the second downlink control information are transmitted by different cells, the control section401may assume that the resource for the downlink shared channel and the resource for the CSI reference signal do not overlap. Furthermore, when a resource in which the first downlink control information and the second downlink control information transmitted by the different cells overlap is indicated, or when a resource in which the first downlink control information and the second downlink control information to be separately transmitted overlap is indicated, the control section401may control reception processing based on a process time to be configured. Furthermore, according to a configuration where control is performed such that the CSI-RS and the PDSCH are not configured to the same resource, when the first downlink control information used to schedule the downlink shared channel and the second downlink control information used to trigger the CSI reference signal are transmitted by the different cells, and the resources respectively indicated by the first downlink control information and the second downlink control information overlap, the control section401may perform control not to perform at least one of reception of the downlink shared channel and measurement that uses the CSI reference signal. For example, the control section401may ignore at least one of the first downlink control information and the second downlink control information. Furthermore, when the measurement that uses the CSI reference signal is not performed, the control section401may perform control to report a value calculated without using the CSI reference signal. Alternatively, according to a configuration where control is performed such that the CSI-RS and the PDSCH are not configured to the same resource, when the first downlink control information used to schedule the downlink shared channel and the second downlink control information used to trigger the CSI reference signal are transmitted by the different cells, and the resources respectively indicated by the first downlink control information and the second downlink control information overlap, the control section401may perform control to perform both of reception of the downlink shared channel and measurement that uses the CSI reference signal. Furthermore, the control section401may decide whether or not the downlink shared channel is rate-matched based on the process time to be configured. The transmission signal generating section402generates an uplink signal (such as an uplink control signal, an uplink data signal or an uplink reference signal) based on an instruction from the control section401, and outputs the uplink signal to the mapping section403. The transmission signal generating section402can be composed of a signal generator, a signal generating circuit or a signal generating apparatus described based on the common knowledge in the technical field according to the present disclosure. The transmission signal generating section402generates, for example, an uplink control signal related to transmission acknowledgement information and Channel State Information (P-CSI, A-CSI or SP-CSI) based on the instruction from the control section401. Furthermore, the transmission signal generating section402generates an uplink data signal based on the instruction from the control section401. When, for example, the downlink control signal notified from the base station10includes a UL grant, the transmission signal generating section402is instructed by the control section401to generate an uplink data signal. The mapping section403maps the uplink signal generated by the transmission signal generating section402, on radio resources based on the instruction from the control section401, and outputs the uplink signal to each transmitting/receiving section203. The mapping section403can be composed of a mapper, a mapping circuit or a mapping apparatus described based on the common knowledge in the technical field according to the present disclosure. The received signal processing section404performs reception processing (e.g., demapping, demodulation and decoding) on the received signal input from each transmitting/receiving section203. In this regard, the received signal is, for example, a downlink signal (such as a downlink control signal, a downlink data signal or a downlink reference signal) transmitted from the base station10. The received signal processing section404can be composed of a signal processor, a signal processing circuit or a signal processing apparatus described based on the common knowledge in the technical field according to the present disclosure. Furthermore, the received signal processing section404can compose the receiving section according to the present disclosure. The received signal processing section404outputs information decoded by the reception processing to the control section401. The received signal processing section404outputs, for example, broadcast information, system information, an RRC signaling and DCI to the control section401. Furthermore, the received signal processing section404outputs the received signal and/or the signal after the reception processing to the measurement section405. The measurement section405performs measurement related to the received signal. The measurement section405can be composed of a measurement instrument, a measurement circuit or a measurement apparatus described based on the common knowledge in the technical field according to the present disclosure. For example, the measurement section405may perform RRM measurement or CSI measurement based on the received signal. The measurement section405may measure received power (e.g., RSRP), received quality (e.g., RSRQ, an SINR or an SNR), a signal strength (e.g., RSSI) or channel information (e.g., CSI). The measurement section405may output a measurement result to the control section401. (Hardware Configuration) In addition, the block diagrams used to describe the above embodiment illustrate blocks in function units. These function blocks (components) are realized by an arbitrary combination of at least one of hardware and software. Furthermore, a method for realizing each function block is not limited in particular. That is, each function block may be realized by using one physically or logically coupled apparatus or may be realized by using a plurality of these apparatuses formed by connecting two or more physically or logically separate apparatuses directly or indirectly (by using, for example, wired connection or radio connection). Each function block may be realized by combining software with the above one apparatus or a plurality of above apparatuses. In this regard, the functions include judging, determining, deciding, calculating, computing, processing, deriving, investigating, looking up, ascertaining, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, yet are not limited to these. For example, a function block (component) that causes transmission to function may be referred to as a transmitting unit/section or a transmitter. As described above, the method for realizing each function block is not limited in particular. For example, the base station and the user terminal according to the one embodiment of the present disclosure may function as computers that perform processing of the radio communication method according to the present disclosure.FIG.10is a diagram illustrating one example of the hardware configurations of the base station and the user terminal according to the one embodiment. The above-described base station10and user terminal20may be each physically configured as a computer apparatus that includes a processor1001, a memory1002, a storage1003, a communication apparatus1004, an input apparatus1005, an output apparatus1006and a bus1007. In this regard, a word “apparatus” in the following description can be read as a circuit, a device or a unit. The hardware configurations of the base station10and the user terminal20may be configured to include one or a plurality of apparatuses illustrated inFIG.10or may be configured without including part of the apparatuses. For example,FIG.10illustrates the only one processor1001. However, there may be a plurality of processors. Furthermore, processing may be executed by 1 processor or processing may be executed by 2 or more processors concurrently or successively or by using another method. In addition, the processor1001may be implemented by 1 or more chips. Each function of the base station10and the user terminal20is realized by, for example, causing hardware such as the processor1001and the memory1002to read given software (program), and thereby causing the processor1001to perform an operation, and control communication via the communication apparatus1004and control at least one of reading and writing of data in the memory1002and the storage1003. The processor1001causes, for example, an operating system to operate to control the entire computer. The processor1001may be composed of a Central Processing Unit (CPU) including an interface for a peripheral apparatus, a control apparatus, an operation apparatus and a register. For example, the above-described baseband signal processing section104(204) and call processing section105may be realized by the processor1001. Furthermore, the processor1001reads programs (program codes), a software module or data from at least one of the storage1003and the communication apparatus1004out to the memory1002, and executes various types of processing according to these programs, software module or data. As the programs, programs that cause the computer to execute at least part of the operations described in the above-described embodiment are used. For example, the control section401of the user terminal20may be realized by a control program that is stored in the memory1002and operates on the processor1001, and other function blocks may be also realized likewise. The memory1002is a computer-readable recording medium, and may be composed of at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM) and other appropriate storage media. The memory1002may be referred to as a register, a cache or a main memory (main storage apparatus). The memory1002can store programs (program codes) and a software module that can be executed to perform the radio communication method according to the one embodiment of the present disclosure. The storage1003is a computer-readable recording medium, and may be composed of at least one of, for example, a flexible disk, a floppy (registered trademark) disk, a magnetooptical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk and a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick or a key drive), a magnetic stripe, a database, a server and other appropriate storage media. The storage1003may be referred to as an auxiliary storage apparatus. The communication apparatus1004is hardware (transmission/reception device) that performs communication between computers via at least one of a wired network and a radio network, and is also referred to as, for example, a network device, a network controller, a network card and a communication module. The communication apparatus1004may be configured to include a high frequency switch, a duplexer, a filter and a frequency synthesizer to realize at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-described transmission/reception antennas101(201), amplifying sections102(202), transmitting/receiving sections103(203) and communication path interface106may be realized by the communication apparatus1004. Each transmitting/receiving section103may be physically or logically separately implemented as a transmitting section103aand a receiving section103b. The input apparatus1005is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button or a sensor) that accepts an input from an outside. The output apparatus1006is an output device (e.g., a display, a speaker or a Light Emitting Diode (LED) lamp) that sends an output to the outside. In addition, the input apparatus1005and the output apparatus1006may be an integrated component (e.g., touch panel). Furthermore, each apparatus such as the processor1001or the memory1002is connected by the bus1007that communicates information. The bus1007may be composed by using a single bus or may be composed by using different buses between apparatuses. Furthermore, the base station10and the user terminal20may be configured to include hardware such as a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD) and a Field Programmable Gate Array (FPGA). The hardware may be used to realize part or entirety of each function block. For example, the processor1001may be implemented by using at least one of these types of hardware. (Modified Example) In addition, each term that has been described in the present disclosure and each term that is necessary to understand the present disclosure may be replaced with terms having identical or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. A reference signal can be also abbreviated as an RS (Reference Signal), or may be referred to as a pilot or a pilot signal depending on standards to be applied. Furthermore, a Component Carrier (CC) may be referred to as a cell, a frequency carrier and a carrier frequency. A radio frame may include one or a plurality of durations (frames) in a time domain. Each of one or a plurality of durations (frames) that composes a radio frame may be referred to as a subframe. Furthermore, the subframe may include one or a plurality of slots in the time domain. The subframe may be a fixed time duration (e.g., 1 ms) that does not depend on the numerologies. In this regard, the numerology may be a communication parameter to be applied to at least one of transmission and reception of a certain signal or channel. The numerology may indicate at least one of, for example, a SubCarrier Spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a Transmission Time Interval (TTI), the number of symbols per TTI, a radio frame configuration, specific filtering processing performed by a transceiver in a frequency domain, and specific windowing processing performed by the transceiver in a time domain. The slot may include one or a plurality of symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier-frequency Division Multiple Access (SC-FDMA) symbols) in the time domain. Furthermore, the slot may be a time unit based on the numerologies. The slot may include a plurality of mini slots. Each mini slot may include one or a plurality of symbols in the time domain. Furthermore, the mini slot may be referred to as a subslot. The mini slot may include a smaller number of symbols than those of the slot. The PDSCH (or the PUSCH) to be transmitted in larger time units than that of the mini slot may be referred to as a PDSCH (PUSCH) mapping type A. The PDSCH (or the PUSCH) to be transmitted by using the mini slot may be referred to as a PDSCH (PUSCH) mapping type B. The radio frame, the subframe, the slot, the mini slot and the symbol each indicate a time unit for conveying signals. The other corresponding names may be used for the radio frame, the subframe, the slot, the mini slot and the symbol. In addition, time units such as a frame, a subframe, a slot, a mini slot and a symbol in the present disclosure may be interchangeably read. For example, 1 subframe may be referred to as a Transmission Time Interval (TTI), a plurality of contiguous subframes may be referred to as TTIs, or 1 slot or 1 mini slot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) according to legacy LTE, may be a duration (e.g., 1 to 13 symbols)) shorter than 1 ms or may be a duration longer than 1 ms. In addition, a unit that indicates the TTI may be referred to as a slot or a mini slot instead of a subframe. In this regard, the TTI refers to, for example, a minimum time unit of scheduling of radio communication. For example, in the LTE system, the base station performs scheduling for allocating radio resources (a frequency bandwidth or transmission power that can be used in each user terminal) in TTI units to each user terminal. In this regard, a definition of the TTI is not limited to this. The TTI may be a transmission time unit of a channel-coded data packet (transport block), code block or codeword, or may be a processing unit of scheduling or link adaptation. In addition, when the TTI is given, a time period (e.g., the number of symbols) in which a transport block, a code block or a codeword is actually mapped may be shorter than the TTI. In addition, when 1 slot or 1 mini slot is referred to as a TTI, 1 or more TTIs (i.e., 1 or more slots or 1 or more mini slots) may be a minimum time unit of scheduling. Furthermore, the number of slots (the number of mini slots) that compose a minimum time unit of the scheduling may be controlled. The TTI having the time duration of 1 ms may be referred to as a general TTI (TTIs according to LTE Rel. 8 to 12), a normal TTI, a long TTI, a general subframe, a normal subframe, a long subframe or a slot. A TTI shorter than the general TTI may be referred to as a reduced TTI, a short TTI, a partial or fractional TTI, a reduced subframe, a short subframe, a mini slot, a subslot or a slot. In addition, the long TTI (e.g., the general TTI or the subframe) may be read as a TTI having a time duration exceeding 1 ms, and the short TTI (e.g., the reduced TTI) may be read as a TTI having a TTI length less than the TTI length of the long TTI and equal to or more than 1 ms. A Resource Block (RB) is a resource allocation unit of the time domain and the frequency domain, and may include one or a plurality of contiguous subcarriers in the frequency domain. The numbers of subcarriers included in RBs may be the same irrespectively of a numerology, and may be, for example, 12. The numbers of subcarriers included in the RBs may be determined based on the numerology. Furthermore, the RB may include one or a plurality of symbols in the time domain or may have the length of 1 slot, 1 mini slot, 1 subframe or 1 TTI. 1 TTI or 1 subframe may each include one or a plurality of resource blocks. In this regard, one or a plurality of RBs may be referred to as a Physical Resource Block (PRB: Physical RB), a Sub-Carrier Group (SCG), a Resource Element Group (REG), a PRB pair or an RB pair. Furthermore, the resource block may include one or a plurality of Resource Elements (REs). For example, 1 RE may be a radio resource domain of 1 subcarrier and 1 symbol. A Bandwidth Part (BWP) (that may be referred to as a partial bandwidth) may mean a subset of contiguous common Resource Blocks (common RBs) for a certain numerology in a certain carrier. In this regard, the common RB may be specified by an RB index based on a common reference point of the certain carrier. A PRB may be defined based on a certain BWP, and may be numbered in the certain BWP. The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or a plurality of BWPs in 1 carrier may be configured to the UE. At least one of the configured BWPs may be active, and the UE may not assume that a given signal/channel is transmitted and received outside the active BWP. In addition, a “cell” and a “carrier” in the present disclosure may be read as a “BWP”. In this regard, structures of the above-described radio frame, subframe, slot, mini slot and symbol are only exemplary structures. For example, configurations such as the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of mini slots included in a slot, the numbers of symbols and RBs included in a slot or a mini slot, the number of subcarriers included in an RB, the number of symbols in a TTI, a symbol length and a Cyclic Prefix (CP) length can be variously changed. Furthermore, the information and the parameters described in the present disclosure may be expressed by using absolute values, may be expressed by using relative values with respect to given values or may be expressed by using other corresponding information. For example, a radio resource may be instructed by a given index. Names used for parameters in the present disclosure are in no respect restrictive names. Furthermore, numerical expressions that use these parameters may be different from those explicitly disclosed in the present disclosure. Various channels (the Physical Uplink Control Channel (PUCCH and the Physical Downlink Control Channel (PDCCH)) and information elements can be identified based on various suitable names. Therefore, various names assigned to these various channels and information elements are in no respect restrictive names. The information and the signals described in the present disclosure may be expressed by using one of various different techniques. For example, the data, the instructions, the commands, the information, the signals, the bits, the symbols and the chips mentioned in the above entire description may be expressed as voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or arbitrary combinations of these. Furthermore, the information and the signals can be output at least one of from a higher layer to a lower layer and from the lower layer to the higher layer. The information and the signals may be input and output via a plurality of network nodes. The input and output information and signals may be stored in a specific location (e.g., memory) or may be managed by using a management table. The information and signals to be input and output can be overridden, updated or additionally written. The output information and signals may be deleted. The input information and signals may be transmitted to other apparatuses. Notification of information is not limited to the aspects/embodiment described in the present disclosure and may be performed by using other methods. For example, the information may be notified by a physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), a higher layer signaling (e.g., a Radio Resource Control (RRC) signaling, broadcast information (a Master Information Block (MIB) and a System Information Block (SIB)), and a Medium Access Control (MAC) signaling), other signals or combinations of these. In addition, the physical layer signaling may be referred to as Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal) or L1 control information (L1 control signal). Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRCConnectionSetup message or an RRCConnectionReconfiguration message. Furthermore, the MAC signaling may be notified by using, for example, an MAC Control Element (MAC CE). Furthermore, notification of given information (e.g., notification of “being X”) is not limited to explicit notification, and may be given implicitly (by, for example, not giving notification of the given information or by giving notification of another information). Decision may be made based on a value (0 or 1) expressed as 1 bit, may be made based on a boolean expressed as true or false or may be made by comparing numerical values (by, for example, making comparison with a given value). Irrespectively of whether software is referred to as software, firmware, middleware, a microcode or a hardware description language or is referred to as other names, the software should be widely interpreted to mean a command, a command set, a code, a code segment, a program code, a program, a subprogram, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable file, an execution thread, a procedure or a function. Furthermore, software, commands and information may be transmitted and received via transmission media. When, for example, the software is transmitted from websites, servers or other remote sources by using at least ones of wired techniques (e.g., coaxial cables, optical fiber cables, twisted pairs and Digital Subscriber Lines (DSLs)) and radio techniques (e.g., infrared rays and microwaves), at least ones of these wired techniques and radio techniques are included in a definition of the transmission media. The terms “system” and “network” used in the present disclosure can be interchangeably used. In the present disclosure, terms such as “preceding”, a “precoder”, a “weight (preceding weight)”, “Quasi-Co-Location (QCL)”, “transmission power”, “phase rotation”, an “antenna port”, an “antenna port group”, a “layer”, “the number of layers”, a “rank”, a “beam”, a “beam width”, a “beam angle”, an “antenna”, an “antenna element” and a “panel” can be interchangeably used. In the present disclosure, terms such as a “base Station (BS)”, a “radio base station”, a “fixed station”, a “NodeB”, an “eNodeB (eNB)”, a “gNodeB (gNB)”, an “access point”, a “Transmission Point (TP)”, a “Reception Point (RP)”, a “Transmission/Reception Point (TRP)”, a a “cell”, a “sector”, a “cell group”, a “carrier” and a “component carrier” can be interchangeably used. The base station is also referred to as terms such as a macro cell, a small cell, a femtocell or a picocell. The base station can accommodate one or a plurality of (e.g., three) cells. When the base station accommodates a plurality of cells, an entire coverage area of the base station can be partitioned into a plurality of smaller areas. Each smaller area can also provide a communication service via a base station subsystem (e.g., indoor small base station (RRH: Remote Radio Head)). The term “cell” or “sector” indicates part or the entirety of the coverage area of at least one of the base station and the base station subsystem that provide a communication service in this coverage. In the present disclosure, the terms such as “Mobile Station (MS)”, “user terminal”, “user apparatus (UE: User Equipment)” and “terminal” can be interchangeably used. The mobile station is also referred to as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client or some other appropriate terms in some cases. At least one of the base station and the mobile station may be referred to as a transmission apparatus, a reception apparatus or a communication apparatus. In addition, at least one of the base station and the mobile station may be a device mounted on a movable body or the movable body itself. The movable body may be a vehicle (e.g., a car or an airplane), may be a movable body (e.g., a drone or a self-driving car) that moves unmanned or may be a robot (a manned type or an unmanned type). In addition, at least one of the base station and the mobile station includes an apparatus, too, that does not necessarily move during a communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor. Furthermore, the base station in the present disclosure may be read as the user terminal. For example, each aspect/embodiment of the present disclosure may be applied to a configuration where communication between the base station and the user terminal is replaced with communication between a plurality of user terminals (that may be referred to as, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal20may be configured to include the functions of the above-described base station10. Furthermore, words such as “uplink” and “downlink” may be read as a word (e.g., a “side”) that matches terminal-to-terminal communication. For example, the uplink channel and the downlink channel may be read as side channels. Similarly, the user terminal in the present disclosure may be read as the base station. In this case, the base station10may be configured to include the functions of the above-described user terminal20. In the present disclosure, operations performed by the base station are performed by an upper node of this base station depending on cases. Obviously, in a network including one or a plurality of network nodes including the base stations, various operations performed to communicate with a terminal can be performed by base stations, one or more network nodes (that are regarded as, for example, Mobility Management Entities (MMEs) or Serving-Gateways (S-GWs), yet are not limited to these) other than the base stations or a combination of these. Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination or may be switched and used when carried out. Furthermore, orders of the processing procedures, the sequences and the flowchart according to each aspect/embodiment described in the present disclosure may be rearranged unless contradictions arise. For example, the method described in the present disclosure presents various step elements by using an exemplary order and is not limited to the presented specific order. Each aspect/embodiment described in the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the 4th generation mobile communication system (4G), the 5th generation mobile communication system (5G), Future Radio Access (FRA), the New Radio Access Technology (New-RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM) (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems that use other appropriate radio communication methods, or next-generation systems that are expanded based on these systems. Furthermore, a plurality of systems may be combined (e.g., a combination of LTE or LTE-A and 5G) and applied. The phrase “based on” used in the present disclosure does not mean “based only on” unless specified otherwise. In other words, the phrase “based on” means both of “based only on” and “based at least on”. Every reference to elements that use names such as “first” and “second” used in the present disclosure does not generally limit the quantity or the order of these elements. These names can be used in the present disclosure as a convenient method for distinguishing between two or more elements. Hence, the reference to the first and second elements does not mean that only two elements can be employed or the first element should precede the second element in some way. The term “deciding (determining)” used in the present disclosure includes diverse operations in some cases. For example, “deciding (determining)” may be regarded to “decide (determine)” judging, calculating, computing, processing, deriving, investigating, looking up, search and inquiry (e.g., looking up in a table, a database or another data structure), and ascertaining. Furthermore, “deciding (determining)” may be regarded to “decide (determine)” receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output and accessing (e.g., accessing data in a memory). Furthermore, “deciding (determining)” may be regarded to “decide (determine)” resolving, selecting, choosing, establishing and comparing. That is, “deciding (determining)” may be regarded to “decide (determine)” some operation. Furthermore, “deciding (determining)” may be read as “assuming”, “expecting” and “considering”. The words “connected” and “coupled” used in the present disclosure or every modification of these words can mean every direct or indirect connection or coupling between 2 or more elements, and can include that 1 or more intermediate elements exist between the two elements “connected” or “coupled” with each other. The elements may be coupled or connected physically or logically or by a combination of these physical and logical connections. For example, “connection” may be read as “access”. It can be understood in the present disclosure that, when connected, the two elements are “connected” or “coupled” with each other by using 1 or more electric wires, cables or printed electrical connection, and by using electromagnetic energy having wavelengths in radio frequency domains, microwave domains or (both of visible and invisible) light domains in some non-restrictive and non-comprehensive examples. A sentence that “A and B are different” in the present disclosure may mean that “A and B are different from each other”. In this regard, the sentence may mean that “A and B are each different from C”. Words such as “separate” and “coupled” may be also interpreted in a similar way to “different”. When the words “include” and “including” and modifications of these words are used in the present disclosure, these words intend to be comprehensive similar to the word “comprising”. Furthermore, the word “or” used in the present disclosure intends not to be an exclusive OR. When, for example, translation adds articles such as a, an and the in English in the present disclosure, the present disclosure may include that nouns coming after these articles are plural. The invention according to the present disclosure has been described in detail above. However, it is obvious for a person skilled in the art that the invention according to the present disclosure is not limited to the embodiment described in the present disclosure. The invention according to the present disclosure can be carried out as modified and changed aspects without departing from the gist and the scope of the invention defined based on the recitation of the claims. Accordingly, the description of the present disclosure is intended for exemplary explanation, and does not bring any restrictive meaning to the invention according to the present disclosure. | 90,491 |
11943767 | DETAILED DESCRIPTION The detailed description set forth below, in connection with the appended drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts. This disclosure relates generally to wireless communications systems, also referred to as wireless communications networks. In various embodiments, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, 5thGeneration (5G) or new radio (NR) networks, as well as other communications networks. As described herein, the terms “networks” and “systems” may be used interchangeably. An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like. UTRA, E-UTRA, and GSM are part of universal mobile telecommunication system (UMTS). In particular, long term evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided from an organization named “3rd Generation Partnership Project” (3GPP), and cdma2000 is described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). These various radio technologies and standards are known or are being developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between groups of telecommunications associations that aims to define a globally applicable third generation (3G) mobile phone specification. 3GPP long term evolution (LTE) is a 3GPP project which was aimed at improving the UMTS mobile phone standard. The 3GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices. The present disclosure is concerned with the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond with shared access to wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces. In particular, 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. In order to achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for 5G NR networks. The 5G NR will be capable of scaling to provide coverage (1) to a massive Internet of things (IoTs) with a Ultra-high density (e.g., ˜1M nodes/km2), ultra-low complexity (e.g., ˜10 s of bits/sec), ultra-low energy (e.g., ˜10+ years of battery life), and deep coverage with the capability to reach challenging locations; (2) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., ˜99.9999% reliability), ultra-low latency (e.g., ˜1 ms), and users with wide ranges of mobility or lack thereof; and (3) with enhanced mobile broadband including extreme high capacity (e.g., ˜10 Tbps/km2), extreme data rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations. A 5G NR communication system may be implemented to use optimized OFDM-based waveforms with scalable numerology and transmission time interval (TTI). Additional features may also include having a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD)/frequency division duplex (FDD) design; and with advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility. Scalability of the numerology in 5G NR, with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of less than 3 GHz FDD/TDD implementations, subcarrier spacing may occur with 15 kHz, for example over 5, 10, 20 MHz, and the like bandwidth (BW). For other various outdoor and small cell coverage deployments of TDD greater than 3 GHz, subcarrier spacing may occur with 30 kHz over 80/100 MHz BW. For other various indoor wideband implementations, using a TDD over the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur with 60 kHz over a 160 MHz BW. Finally, for various deployments transmitting with mmWave components at a TDD of 28 GHz, subcarrier spacing may occur with 120 kHz over a 500 MHz BW. The scalable numerology of the 5G NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTI may be used for low latency and high reliability, while longer TTI may be used for higher spectral efficiency. The efficient multiplexing of long and short TTIs to allow transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with uplink (UL)/downlink (DL) scheduling information, data, and acknowledgement in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive UL/DL that may be flexibly configured on a per-cell basis to dynamically switch between UL and DL to meet the current traffic needs. Various other aspects and features of the disclosure are further described below. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative and not limiting. Based on the teachings herein one of an ordinary level of skill in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. For example, a method may be implemented as part of a system, device, apparatus, and/or as instructions stored on a computer readable medium for execution on a processor or computer. Furthermore, an aspect may comprise at least one element of a claim. In a certain wireless communication network, a BS may configure each connected UE with one or more sounding reference signal (SRS) resource sets for using to transmit SRS to the BS. Each SRS resource set may include one or more SRS resources. Each SRS resource may be associated with one or more SRS ports. An SRS port may be mapped to a transmit antenna port of the UE which may be used to sound an SRS transmission and may correspond to a certain transmission layer. The BS may configure a quantity of SRS ports for the SRS resources according to a quantity of transmit antenna ports and/or a quantity of receive antenna ports supported by the respective UE. For instance, if the UE has four transmit antenna ports and four receive antenna ports, the BS may configure the UE to transmit an SRS using four SRS ports. However, in some scenarios, it may be sufficient for the UE to sound a subset of the configured SRS ports instead of all the configured SRS ports. For example, in some instances, an SRS transmission may be used for estimations other than UL sounding. For instance, in channel reciprocity operations, an SRS can be used for DL channel state information (CSI) acquisition. In a certain wireless communication network, a BS may schedule, using an UL or a DL scheduling grant, a UE to transmit aperiodic SRS (A-SRS) to the BS. For example, the UL or DL scheduling grant may be transmitted to the UE via a downlink control information (DCI) transmission. In some aspects, the A-SRS may be transmitted to the BS via a SRS resource in a SRS resource set with an aperiodic resource type, i.e., a SRS resource set that may be utilized by the UE when the UE receives explicit trigger (e.g., the DCI transmission) from the BS. Upon receiving the A-SRS from the UE, in some aspects, the BS may use the A-SRS to acquire CSI about the UL or DL channel. In some aspects, the BS may use A-SRS to acquire CSI about a channel after receiving a negative acknowledgement (NACK) from the UE about a DL data transmission (e.g., physical downlink shared channel (PDSCH) transmission) from the BS to the UE. For example, a BS may transmit a PDSCH transmission to the UE and may receive a NACK back from the UE (e.g., due to erroneous decoding of the DL transmission by the UE). In some cases, the BS may then trigger an A-SRS transmission from the UE to use the A-SRS transmission to obtain CSI about the channel of the DL transmission. For instance, the BS may use the next DL scheduling grant (e.g., DCI transmission) to the UE to trigger the UE to transmit an A-SRS back to the BS. In some aspects, however, such a process may be too slow, because by the time the BS receives the A-SRS, there may not be enough time left for the BS to use the acquired CSI to re-transmit the PDSCH transmission that caused the UE to send the NACK. As such, it may be desirable to allow the UE to autonomously (i.e., without being triggered by the BS) transmit an A-SRS to the UE when the UE detects a NACK on the PDSCH transmission. In some aspects, UEs and BSs may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval. In some aspects, the physical hybrid automatic repeat request (HARQ) indicator channel (PHICH) carries HARQ feedback transmissions such as an acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission confirmed, an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc. Aspects of the present disclosure can provide several benefits, including improving latency and network efficiency and functionality. For example, by allowing the UE to transmit a A-SRS along with a NACK on a received PDSCH transmission, some aspects reduce or altogether eliminate the time it may take the BS to generate and send to the UE the next DL scheduling grant or DCI that triggers the A-SRS and receive in return the A-SRS from the UE. In some aspects, with the BS having received the A-SRS sooner than would be otherwise, the BS can have at least sufficient time to use the A-SRS for re-transmitting the PDSCH transmission, which improves latency and network efficiency. While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution. FIG.1illustrates a wireless communication network100according to some aspects of the present disclosure. The network100may be a 5G network. The network100includes a number of base stations (BSs)105(individually labeled as105a,105b,105c,105d,105e, and105f) and other network entities. ABS105may be a station that communicates with UEs115and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like. Each BS105may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to this particular geographic coverage area of a BS105and/or a BS subsystem serving the coverage area, depending on the context in which the term is used. A BS105may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, and/or other types of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell, such as a pico cell, would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell, such as a femto cell, would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS or a home BS. In the example shown inFIG.1, the BSs105dand105emay be regular macro BSs, while the BSs105a-105cmay be macro BSs enabled with one of three dimension (3D), full dimension (FD), or massive MIMO. The BSs105a-105cmay take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. The BS105fmay be a small cell BS which may be a home node or portable access point. A BS105may support one or multiple (e.g., two, three, four, and the like) cells. The network100may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time. The UEs115may be dispersed throughout the wireless network100, and each UE115may be stationary or mobile. UEs can take in a variety of forms and a range of form factors. A UE115may also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like. A UE115may be a cellular phone, a personal digital assistant (PDA), a smartphone, a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like. In one aspect, a UE115may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, the UEs115that do not include UICCs may also be referred to as IoT devices or internet of everything (IoE) devices. The UEs115a-115dare examples of mobile smart phone-type devices accessing network100. A UE115may also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. The UEs115e-115hare examples of various machines configured for communication that access the network100. The UEs115i-115kare examples of vehicles equipped with wireless communication devices configured for communication that access the network100. A UE115may be able to communicate with any type of the BSs, whether macro BS, small cell, or the like. InFIG.1, a lightning bolt (e.g., communication links) indicates wireless transmissions between a UE115and a serving BS105, which is a BS designated to serve the UE115on the downlink (DL) and/or uplink (UL), desired transmission between BSs105, backhaul transmissions between BSs, or sidelink transmissions between UEs115. In operation, the BSs105a-105cmay serve the UEs115aand115busing 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. The macro BS105dmay perform backhaul communications with the BSs105a-105c, as well as small cell, the BS105f. The macro BS105dmay also transmit multicast services which are subscribed to and received by the UEs115cand115d. Such multicast services may include mobile television or stream video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts. The BSs105may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs105(e.g., which may be an example of a gNB or an access node controller (ANC)) may interface with the core network through backhaul links (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communication with the UEs115. In various examples, the BSs105may communicate, either directly or indirectly (e.g., through core network), with each other over backhaul links (e.g., X1, X2, etc.), which may be wired or wireless communication links. The network100may also support mission critical communications with ultra-reliable and redundant links for mission critical devices, such as the UE115e, which may be a drone. Redundant communication links with the UE115emay include links from the macro BSs105dand105e, as well as links from the small cell BS105f. Other machine type devices, such as the UE115f(e.g., a thermometer), the UE115g(e.g., smart meter), and UE115h(e.g., wearable device) may communicate through the network100either directly with BSs, such as the small cell BS105f, and the macro BS105e, or in multi-step-size configurations by communicating with another user device which relays its information to the network, such as the UE115fcommunicating temperature measurement information to the smart meter, the UE115g, which is then reported to the network through the small cell BS105f. The network100may also provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as V2V, V2X, C-V2X communications between a UE115i,115j, or115kand other UEs115, and/or vehicle-to-infrastructure (V2I) communications between a UE115i,115j, or115kand a BS105. In some implementations, the network100utilizes OFDM-based waveforms for communications. An OFDM-based system may partition the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, or the like. Each subcarrier may be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system BW. The system BW may also be partitioned into subbands. In other instances, the subcarrier spacing and/or the duration of TTIs may be scalable. In some aspects, the BSs105can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RB)) for downlink (DL) and uplink (UL) transmissions in the network100. DL refers to the transmission direction from a BS105to a UE115, whereas UL refers to the transmission direction from a UE115to a BS105. The communication can be in the form of radio frames. A radio frame may be divided into a plurality of subframes or slots, for example, about 10. Each slot may be further divided into mini-slots. In a FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In a TDD mode, UL and DL transmissions occur at different time periods using the same frequency band. For example, a subset of the subframes (e.g., DL subframes) in a radio frame may be used for DL transmissions and another subset of the subframes (e.g., UL subframes) in the radio frame may be used for UL transmissions. The DL subframes and the UL subframes can be further divided into several regions. For example, each DL or UL subframe may have pre-defined regions for transmissions of reference signals, control information, and data. Reference signals are predetermined signals that facilitate the communications between the BSs105and the UEs115. For example, a reference signal can have a particular pilot pattern or structure, where pilot tones may span across an operational BW or frequency band, each positioned at a pre-defined time and a pre-defined frequency. For example, a BS105may transmit cell specific reference signals (CRSs) and/or channel state information-reference signals (CSI-RSs) to enable a UE115to estimate a DL channel. Similarly, a UE115may transmit sounding reference signals (SRSs) to enable a BS105to estimate a UL channel. Control information may include resource assignments and protocol controls. Data may include protocol data and/or operational data. In some aspects, the BSs105and the UEs115may communicate using self-contained subframes. A self-contained subframe may include a portion for DL communication and a portion for UL communication. A self-contained subframe can be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL communication than for UL communication. A UL-centric subframe may include a longer duration for UL communication than for UL communication. In some aspects, the network100may be an NR network deployed over a licensed spectrum. The BSs105can transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network100to facilitate synchronization. The BSs105can broadcast system information associated with the network100(e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, the BSs105may broadcast the PSS, the SSS, and/or the MIB in the form of synchronization signal block (SSBs) over a physical broadcast channel (PBCH) and may broadcast the RMSI and/or the OSI over a physical downlink shared channel (PDSCH). In some aspects, a UE115attempting to access the network100may perform an initial cell search by detecting a PSS from a BS105. The PSS may enable synchronization of period timing and may indicate a physical layer identity value. The UE115may then receive a SSS. The SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell. The PSS and the SSS may be located in a central portion of a carrier or any suitable frequencies within the carrier. After receiving the PSS and SSS, the UE115may receive a MIB. The MIB may include system information for initial network access and scheduling information for RMSI and/or OSI. After decoding the MIB, the UE115may receive RMSI and/or OSI. The RMSI and/or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource set (CORESET) for physical downlink control channel (PDCCH) monitoring, physical UL control channel (PUCCH), physical UL shared channel (PUSCH), power control, and SRS. After obtaining the MIB, the RMSI and/or the OSI, the UE115can perform a random access procedure to establish a connection with the BS105. The random access procedure (or RACH procedure) may be a single or multiple step process. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE115may transmit a random access preamble and the BS105may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, a UL grant, a temporary cell-radio network temporary identifier (C-RNTI), and/or a backoff indicator. Upon receiving the random access response, the UE115may transmit a connection request to the BS105and the BS105may respond with a connection response. The connection response may indicate a contention resolution. In some examples, the random access preamble, the RAR, the connection request, and the connection response can be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE115may transmit a random access preamble and a connection request in a single transmission and the BS105may respond by transmitting a random access response and a connection response in a single transmission. After establishing a connection, the UE115and the BS105can enter a normal operation stage, where operational data may be exchanged. For example, the BS105may schedule the UE115for UL and/or DL communications. The BS105may transmit UL and/or DL scheduling grants to the UE115via a PDCCH. Scheduling grants may be transmitted in the form of DL control information (DCI). The BS105may transmit a DL communication signal (e.g., carrying data) to the UE115via a PDSCH according to a DL scheduling grant. The UE115may transmit a UL communication signal to the BS105via a PUSCH and/or PUCCH according to a UL scheduling grant. In some aspects, the network100may operate over a system BW or a component carrier (CC) BW. The network100may partition the system BW into multiple bandwidth parts (BWPs) (e.g., portions). ABS105may dynamically assign a UE115to operate over a certain BWP (e.g., a certain portion of the system BW). The assigned BWP may be referred to as the active BWP. The UE115may monitor the active BWP for signaling information from the BS105. The BS105may schedule the UE115for UL or DL communications in the active BWP. In some aspects, a BS105may assign a pair of BWPs within the CC to a UE115for UL and DL communications. For example, the BWP pair may include one BWP for UL communications and one BWP for DL communications. In some aspects, the BS105may engage in beam management procedures with UE115to acquire and maintain a suitable set of beams for communication between BS105and UE115. For example, beam management procedures may include beam determination procedures where suitable beams are identified and selected at the BS105or the UE115based on evaluations of beam quality. To assist the BS105and/or the UE115in determining identifying and selecting suitable beams for communication, the BS105may configure each UE115to sound one or more transmit antenna ports of the respective UE115. Sounding may refer to the transmission of an SRS via one or more antenna ports of a SRS resource (of a SRS resource set). The SRS may include a waveform sequence (e.g., predetermined) that are known to the BS105and the UE115. For instance, the SRS may be Zadoff-Chu sequence or any suitable waveform sequence. In some instances, a transmit antenna port at a UE115may map to a physical transmit antenna element of the UE115. In some other instances, a transmit antenna port at a UE115may be a virtual antenna port or a logical port created by the UE115, for example, via precoding. Precoding may include applying different amplitude weights and/or different phased adjustments to signals output by the physical transmit antenna elements of the UE115to produce a signal directed towards a certain spatial direction. In some aspects, the network100may operate in a TDD mode. The BS105may also estimate DL channel characteristics from UL SRSs received from the UEs115based on TDD channel reciprocity. In some aspects, SRS resource sets including one or more SRS resources may also be configured for other new radio (NR) use cases or operations, such as but not limited to antenna switching use cases or operations. For example, SRS resource sets be configured to support antenna switching for SRS transmission. In some aspects, antenna switching can occur at the UE transmitter or the UE receiver for UL or DL communications, respectively. In some aspects, antenna switching at the UE transmitter may refer to the UE transmitter utilizing smaller number of transceiver units or radio frequency chains than the available number of antennas, while antenna switching at the UE receiver may refer to the UE processing signals received via some receiving antennas but not all receiving antennas. For example, when configured for antenna switching at the UE receiver, the UE can dynamically use an antenna subset that may have optimal or near optimal instantaneous link conditions to the transmitter of the BS, and process only signals received by those antennas. In some aspects, a SRS resource set configured for antenna switching use case or operation may facilitate antenna switching for an uplink SRS transmission, for example by specifying the order of the antenna ports that may be used for the SRS transmission in the UL direction. In some aspects, codebook-based or noncodebook-based transmissions can be example of NR use cases or operations supported by SRS resource sets, i.e., SRS resource sets can be configured to support codebook-based or non-codebook-based UL transmissions or PUSCH transmissions. In some aspects, for codebook-based transmission, the UE may be configured with a SRS resource set and only one SRS resource can be indicated based on a SRS resource indicator (SRI) field in the DCI from within the SRS resource set. The UE may then determine its PUSCH transmission precoder based on the SRI, transmitted precoding matrix indicator (TPMI) and the transmission rank from the DCI. In some cases, if A-SRS is configured for a UE, the SRS request field in the DCI can trigger the transmission of A-SRS. For non-codebook-based transmission, in some aspects, the UE can determine its PUSCH precoder and transmission rank based on the wideband SRI given by SRS resource indicator field from the DCI. FIG.2illustrates a radio frame structure200according to some aspects of the present disclosure. The radio frame structure200may be employed by BSs such as the BSs105and UEs such as the UEs115in a network such as the network100for communications, for example, for the transmission of SRS from the UEs to the BSs. In particular, the BS may communicate with the UE using time-frequency resources configured as shown in the radio frame structure200. InFIG.2, the x-axes represent time in some arbitrary units and the y-axes represent frequency in some arbitrary units. The transmission frame structure200includes a radio frame201. The duration of the radio frame201may vary depending on the aspects. In an example, the radio frame201may have a duration of about ten milliseconds. The radio frame201includes M number of slots202, where M may be any suitable positive integer. In an example, M may be about 10. Each slot202includes a number of subcarriers204in frequency and a number of symbols206in time. The number of subcarriers204and/or the number of symbols206in a slot202may vary depending on the aspects, for example, based on the channel bandwidth, the subcarrier spacing (SCS), and/or the cyclic prefix (CP) mode. One subcarrier204in frequency and one symbol206in time forms one resource element (RE)212for transmission. A resource block (RB)210is formed from a number of consecutive subcarriers204in frequency and a number of consecutive symbols206in time. Each slot202may be time-partitioned into K number of mini-slots208. Each mini-slot208may include one or more symbols206. The mini-slots208in a slot202may have variable lengths. For example, when a slot202includes N number of symbols206, a mini-slot208may have a length between one symbol206and (N−1) symbols206. In some aspects, a mini-slot208may have a length of about two symbols206, about four symbols206, or about seven symbols206. In some examples, the BS may schedule UE at a frequency-granularity of a resource block (RB)210(e.g., including about 12 subcarriers204). In an example, a BS (e.g., BS105inFIG.1) may schedule a UE (e.g., UE115inFIG.1) for UL and/or DL communications at a time-granularity of slots202or mini-slots208. In some aspects, a SRS may span one, two or four consecutive symbols and may be located within the last six symbols of a slot (i.e., in the time domain of the radio frame structure200that includes the time and frequency resources). In the frequency domain, an SRS may have a “comb” structure, i.e., the SRS may be transmitted on every second subcarrier (“comb-2”) or fourth (“comb-4”) subcarrier. In some aspects, SRS transmissions from different devices may be frequency multiplexed within the same frequency range by assigning different combs corresponding to different frequency offsets. For example, for “comb-2” and for “comb-4”, two SRSs and up to four SRSs, respectively, can be frequency multiplexed. FIG.3illustrates example configuration of a UE with one or more SRS resource sets according to some aspects of the present disclosure. The configuration300includes a plurality of SRS resource sets302(shown as SRS resource set 0 to SRS resource set N), each SRS resource set302including one or more SRS resources304, i.e., one or more configured SRSs. Each SRS resource304may include time-frequency resources. For instance, each SRS resource304may span one or more symbols (e.g., the symbols206) within a slot (e.g., the slot202) and may include one or more subcarriers (e.g., the subcarriers204) or REs (e.g., the REs212) within each SRS symbol. Additionally, each SRS resource304may be configured with one or more SRS ports306(e.g., up to four SRS ports). For instance, each SRS port306may be associated with one or more REs within an SRS symbol. A UE304may transmit an SRS via a transmit antenna port, and the SRS can assist the BS302in performing beam management procedures including beam refinement, facilitating communication with the UE304. In some aspects, each SRS resource set302may be associated with a certain resource type. For example, an SRS resource set302may have a resource type of periodic, semi-persistent, or aperiodic. An SRS resource set302with a periodic resource type may have a configured periodicity and each periodic SRS resource304may have a configured symbol offset within a slot. A UE304may utilize a periodic SRS resource304for periodic SRS transmission. An SRS resource set302with a semi-persistent resource type may have a configured periodicity similar to a periodic SRS resource set302and each semi-persistent resource304may have a configured symbol offset within a slot similar to a periodic SRS resource304. However, a UE304may not transmit an SRS in a semi-persistent SRS resource304until the BS302triggers an activation (e.g., via MAC-CE) of the SRS resource304. An SRS resource304in an SRS resource set302with an aperiodic resource type may be utilized by a UE304when the UE304receives an explicit trigger (e.g., via DCI) from the BS302. As discussed above, the configuration300includes multiple resources sets302each including one or more SRS resources304. In aspects where the SRS transmitted by the UE using the SRS resources is used for beam management by the BS to which the UE is attached, only one SRS resource in each of the one or more SRS resources may be transmitted at a given time instant, while SRS resources in different SRS resources sets with the same time domain behavior in the same bandwidth part can be transmitted simultaneously. In some aspects, the parameters of an SRS may be semi-statically configured, i.e., may be configured via an RRC message. For example, an RRC message may configure SRS parameters such as but not limited to SRS bandwidth (i.e., bandwidth to be used for transmission of a SRS), a timing or slot offset between the SRS transmission and the transmission (e.g., DCI transmission) triggering the SRS transmission, starting symbol of the SRS resource, transmission comb value (TxComb) and offset (e.g., for comb-2 or comb-4), cyclic shift (e.g., for TxComb value 2 and 4), an ID of the reference signal (RS) associated with the SRS transmission, etc. In some aspects, the RS can be an SS/PBCH block, CSI-RS configured on the BS to which the UE is attached. In some aspects, a transmission comb is a distributed comb-shaped transmission with equally-spaced outputs allocated over the entire bandwidth. In some aspects, the SRS can be quasi co-located (QCL'ed) with the SSB, CSI-RS or another RRC configured SRS. For example, the SRS resource can be transmitted with the same spatial domain transmission filter as used for the Rx/Tx of the RS. Quasi co-location (QCL) refers to the relationship between two signals where properties of a channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed, examples of the noted properties including but not limited to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters when applicable, and/or the like. In some aspects, power control for the SRS transmission by the UE may be controlled by the BS to which the UE is attached. For example, the UE may compute the transmit power, denoted as PSRS, as shown below: PSRS=min[Pcmax,PO_SRS+10×log(2μ·MSRS)+αSRS·PL+h](1) where Pcmaxrepresents the maximum transmit power configured for the UE, for example, according to a particular communication standard. PO_SRSrepresents an open loop power control parameter and can be a frequency parameter configured by the BS, such as a target power spectral density. MSRSrepresents the number of SRS frequency resources (e.g., REs) in the full set of SRS frequency resources assigned to the UE. PL represents estimated path loss (e.g., measured by DL reference signals). αSRSrepresents an open loop power control parameter and represents the factor, which may have a value between 0 and 1, to enable or disable fractional power control or cell specific factor, which may be configured by the BS. h represents a closed-loop component of the power control, for example, received from a transmission power control (TCP) command issued by the BS105(e.g., via a DCI transmission). In some aspects, the power control may be via a closed-loop transmission power control (TPC) command from the BS as part of the DCI transmission. In some aspects, the TPC command can be a group TPC command. For example, the UE may receive a DCI format 2_3 transmission (e.g., group-common DCI for power control for SRS) of TPC command(s) for SRS transmissions from the BS, and the SRS transmission power may follow the TPC command(s). In some aspects, the SRS power may be in accordance with closed-loop TPC command(s) from a BS to a PUSCH transmission. That is, the SRS transmission power may be related to a PUSCH transmission power as dictated by closed-loop TPC command(s) from the BS. For example, one or more of the parameters of equation 1 (e.g., Pcmax, PO_SRS, αSRS, PL, h, and/or the like) may be associated with corresponding parameters used to determine a transmission power for the PUSCH signal. For instance, the closed-loop component h of the PSRSmay be associated (e.g., be equal to) the closed-loop component of the transmit power of the PUSCH transmission. That is, if the transmission of the first SRS follows transmission of the PUSCH signal, the UE may determine a respective value of the one or more of the parameters in equation 1, based on the value of the corresponding parameters used to determine the transmission power for the PUSCH signal. In some aspects, a codepoint of the DCI may trigger one or more aperiodic resource sets configured for a UE. For example, a DCI transmission (e.g., DCI format 0_1 (uplink scheduling grant) and DCI format 1_1 (downlink scheduling assignment)) may include a 2-bit SRS-request that can trigger transmission of one of three different aperiodic resource sets configured for the UE (while the fourth bit combination corresponds to “no triggering” of the SRS resource sets). In some aspects, the minimal time interval between the last symbol of a transmission (e.g., PDCCH transmission) that triggers a aperiodic SRS transmission and the first symbol of the triggered SRS resource is N2+14, where N2is a number (in symbols) related to UE capability. Further, in some aspects, when a UE receives a DCI that triggers aperiodic SRS in slot n, the UE may transmit aperiodic SRS in each of the triggered SRS resource set(s) in slot n·2μ_SRS/2μ_PDCCH+k, where k is the semi-statically configured timing or slot offset (e.g., configured by an RRC message) for each triggered SRS resources set and is based on the subcarrier spacing of the triggered SRS transmission, and μSRSand μPDCCHare the subcarrier spacing configurations for the triggered SRS transmission and the transmission (e.g., PDCCH transmission) triggering the SRS transmission, respectively. In some aspects, the semi-statically configured timing or slot offset k can be a value between 1 slot and 32 slots. In some aspects, each SRS resource set302may be configured for a certain use case or operation, for example, for UL CSI acquisition, DL CSI acquisition (assuming TDD channel reciprocity), and/or beam management. For instance, the BS302may determine UL transmission schemes and/or UL precoding based on acquired UL CSI. The BS302may determine antenna switching or selection based on DL CSI. In an example, for DL CSI acquisition, the BS302may configure a UE304with up to two SRS resource sets302, each having a different resource type. In some instances, the BS302may configure a UE304with zero or one SRS resource set302configured with a resource type of periodic or semi-persistent. In some other instances, the BS302may configure a UE304with zero to two SRS resource sets302, each configured with a resource type of aperiodic. In some aspects, SRSs transmitted by a UE to a BS to which the UE is attached may be used by the BS for channel quality measurements and beam management. In general, beam management refers to the four operations of beam sweeping, beam measurement, beam determination and beam reporting. In some aspects, beam sweeping operation refers to covering a spatial area with a set of beams transmitted and received according to pre-specified intervals and directions. In some aspects, with respect to UL transmission, beam measurement operation refers to the evaluation of the quality of signals received at a BS (e.g., as measured by signal to noise ratios). In some aspects, beam determination operation refers to the selection of a suitable beam(s) at the BS based on the measurement results from the beam measurement operations. In some aspects, beam reporting operation refers to the procedure used by the UE to send beam quality and beam decision information to the Radio Access Network (RAN). FIGS.4A-Billustrate a NACK-triggered SRS transmission, according to some aspects of the present disclosure. In some aspects, a DL grant (e.g., PDCCH communication)402may schedule an ACK or NACK406for a downlink data transmission (e.g., PDSCH transmission)404transmitted to a UE from a BS via a BWP of a serving cell. In some cases, the UE may attempt to decode the PDSCH transmission404and generate an ACK or a NACK406for transmitting to the BS based on the results of the decoding. In some instances, the decoding results may indicate that the PDSCH transmission404was correct or erroneous, and the UE may generate an ACK or a NACK406, respectively, for transmitting back to the BS. In some aspects, a NACK406for a PDSCH transmission404may trigger the UE to transmit a SRS (e.g., A-SRS)408to the BS. In some aspects, the transmission of the NACK-triggered A-SRS408to the BS may occur via the same BWP on which the PDSCH transmission404was received at the UE. For example, the BS may configure a SRS resource set for the transmission, from the UE to the BS, of the NACK-triggered A-SRS408per BWP per serving cell, and use the configured SRS resource set in the same BWP as the BWP the BS used to transmit the PDSCH404to the UE to transmit the NACK-triggered A-SRS408to the BS. For example, the SRS resource set may be configured via a RRC message from the BS to the UE. In some aspects, the power control parameters for the NACK-triggered A-SRS408transmission may be configured to be different from or independent of the power control parameters of SRS from SRS resource sets configured for other NR use cases or operations, such as but not limited to SRS resource sets configured for “antenna switching” use case, “codebook-based or non-codebook-based UL transmission” use case, “beam management” use case, etc. For example, the SRS resource sets of the UE configured for the noted NR use cases may have associated therewith open-loop power control parameters αUse Caseand POUse Case, and the open-loop power control parameters αA-SRSand POA-SRSof the A-SRS408transmission may be different from or independent of the open-loop power control parameters of the SRS configured for the noted NR use cases or operations. In some aspects, the NACK-triggered A-SRS408may be transmitted to the BS using the same SRS resource sets that are configured for transmitting SRS for the afore-mentioned NR use cases or operations. In some aspects, the UE may transmit the A-SRS408to the BS using the SRS resource sets configured for the NR use cases and configured in the same BWP as the BWP the BS used to transmit the PDSCH404to the UE. For example, the UE may transmit to the BS the A-SRS408using a SRS resource set configured for “antenna switching” NR use case in the same BWP as the BWP that the BS used to transmit to the UE the erroneous PDSCH404. In some aspects, because the NACK-triggered A-SRS408is transmitted to the BS using SRS resource sets configured for the afore-mentioned NR use cases, the open-loop power control parameters of the A-SRS408may be same as the open-loop power control parameters of a SRS transmitted using the SRS resource sets configured for the afore-mentioned NR use cases or operations. For example, if the NACK-triggered A-SRS408is transmitted to the BS using a SRS resource set in a BWP configured for “antenna switching” NR use case or operation, the open-loop power control parameters of the NACK-triggered A-SRS408transmitted using a SRS resource set in the same BWP may be same as the open-loop power control parameters of a SRS transmission of “antenna switching” NR use case. In such cases, i.e., when SRS resource sets in a BWP configured for the afore-mentioned NR use cases are used to transmit the NACK-triggered A-SRS408in the same BWP, the UE may apply an additional power boost (e.g., in dB) to the A-SRS408transmission relative to the transmit power of a SRS transmission of the NR use case (e.g., a SRS of the NR use case transmitted using the SRS resource sets configured for the NR use cases). In some aspects, the UE may determine the closed-loop power control parameters of the NACK-triggered A-SRS408based on a DCI transmission (e.g., in DCI 2_3 format)410or414from the BS that includes TPC command(s) related to the closed-loop power control parameters. For example, the TPC command(s) may specify a closed-loop component h of a power control, and the UE may generate the NACK-triggered A-SRS408with a transmit power corresponding to the closed-loop component h specified by the TPC command(s). In some aspects, the DCI transmission410which include the TPC command(s) may be received at the UE prior to the last symbol X412of the corresponding DL grant (e.g., PDCCH transmission) that scheduled the NACK transmission406. That is, with reference toFIG.4A, the UE may use TPC command(s) received in a DCI communication (e.g., DCI 2_3 format)410received prior to the last symbol X412of the DL grant that scheduled the NACK transmission406to determine the closed-loop component of the power control for the NACK-triggered A-SRS408. In some aspects, the DCI transmission414which include the TCP command(s) may be received at the UE at least a threshold number of symbols prior to the NACK-triggered A-SRS408transmission. That is, with reference toFIG.4B, the UE may use TPC command(s) received in a DCI communication (e.g., DCI 2_3 format)414received at least a threshold number of symbols Y416prior to the NACK-triggered A-SRS408transmission to determine the closed-loop component of the power control for the NACK-triggered A-SRS408. In some aspects, if the UE receives the DCI but not (a) prior to the last symbol X412or (b) at least the threshold number of symbols Y416prior to the NACK-triggered A-SRS408transmission, the UE may discard the DCI communication (e.g., and as such may not determine the closed-loop component of the power control for the NACK-triggered A-SRS408based on the TCP command(s) in the DCI communication). In some aspects, the threshold number of symbols may be determined based on an RRC message from the BS. For example, an RRC message from the BS may include the parameter K2 that may specify a gap in slots between a DCI message scheduling a UL transmission via a PDCCH and a latter UL transmission via a PUSCH. In some aspects, the threshold number of symbols may equal the number of symbols of slot delays corresponding to a minimum value of the RRC parameter K2 configured by the RRC message. For instance, K2 can have values 1, 2, 3, etc. (e.g., natural numbers up to and including 12) specified in PUSCH-ConfigCommon. In such cases, if K2 is configured to have the values {1, 2, 3}, for instance, then the minimum value of K2 is 1 and the number of symbols corresponding to this minimum value is 1*14 OFDM symbols=14 OFDM symbols. In such examples, as the threshold number of symbols equals the number of symbols of slot delays or symbols corresponding to the minimum value of the RRC parameter K2, then the threshold number of symbols can be 14 OFDM symbols. In some aspects, a UE may be configured to transmit a periodic SRS to the BS, i.e., the UE may be configured to transmit to the BS a SRS with a configured periodicity using a periodic SRS resource set. In some aspects, the scheduled transmission of the periodic SRS may conflict with the transmission of the NACK-triggered A-SRS. In other words, the transmission of the NACK-triggered A-SRS may collide with a scheduled transmission of a periodic SRS. In such cases, i.e., when the transmission of the NACK-triggered A-SRS collide with a scheduled periodic SRS, the UE may be configured to abandon or abort the scheduled periodic SRS transmission and instead transmit the NACK-triggered A-SRS. In some aspects, a collision may be defined as two or more transmissions in the same subframe. In another example, a collision may also be defined as two or more transmissions in the same symbol. For the former, it implies that simultaneous transmissions over two or more component carriers are not allowed, even if the transmissions may happen over different symbols in the same subframe and within each symbol there is only one transmission in the same subframe. For the latter, it implies that it is possible to have two or more transmissions in the same subframe, as long as within each symbol there is only one transmission in the same subframe. In any case, a collision between two transmissions (e.g., between the NACK-triggered A-SRS and the scheduled periodic SRS) may interfere or interrupt either or both transmissions. In some aspects, as noted above, the BS may acquire a CSI report from the UE to determine, among other things, the quality of the channel for transmitting downlink data to the UE. In some aspects, the CSI report can be a periodic CSI (P-CSI) report, a semi-persistent CSI (SP-CSI) report or an aperiodic CSI (A-CSI) report. In some cases, the UE may transmit the P-CSI report periodically to the BS via the PUCCH. In some aspects, P-CSI reporting parameters such as but not limited to the periodicity and the slot offset may be configured semi-statically (e.g., via RRC messages from the BS). In some aspects, the SP-CSI may have associated therewith a periodicity and a slot offset that are configured semi-statically by the BS. In some aspects, the SP-CSI may be reported periodically (e.g., with the configured periodicity) when triggered by the BS dynamically, and the triggered periodic reporting may cease when a command from the BS requesting that the UE cease the periodic reporting is received at the UE. In some cases, the SP-CSI report may be transmitted via PUSCH. In some aspects, the A-CSI may be reported to the BS when the BS transmits a dynamic trigger (e.g., DCI) to trigger the UE to transmit the A-CSI report. In some cases, the A-CSI reporting parameters may be configured semi-statically, however, the triggering may occur dynamically. In some aspects, the A-CSI report may be transmitted by the UE to the BS via PUSCH. In some aspects, the scheduled transmission of a P-CSI or a SP-CSI by the UE to the BS may conflict with the transmission of the NACK-triggered A-SRS to the BS. In other words, the transmission of the NACK-triggered A-SRS to the BS may collide with a scheduled transmission of a P-CSI or SP-CSI report. In some aspects, when the transmission of the NACK-triggered A-SRS collide with a scheduled P-CSI or SP-CSI report transmission and the UE is not configured to or is incapable of transmitting both the NACK-triggered A-SRS and the P-CSI or SP-CSI report, the UE may be configured to abandon or abort the P-CSI or SP-CSI report transmission and instead transmit the NACK-triggered A-SRS. In some aspects, the DL grant (e.g., PDCCH communication)402that is configured to trigger the NACK406may also be configured to trigger an A-SRS. In such cases, the UE may be configured to abandon or abort the transmission of the NACK-triggered A-SRS408and instead transmit to the BS the A-SRS that is triggered by the DL grant402. In some cases, if the DL grant402that triggers the NACK406triggers an A-SRS, the NACK406may not trigger another A-SRS and the UE may transmit to the BS the A-SRS that is triggered by the DL grant402. In some aspects, an UL grant to from the BS to the UE may trigger an A-SRS, and if the UE is not configured to or is incapable of transmitting both the NACK-triggered A-SRS and the A-SRS triggered by the UL grant, the UE may be configured to (i) always transmit the NACK-triggered A-SRS, (ii) always transmit the A-SRS triggered by the UL grant or (iii) determine whether to transmit the NACK-triggered A-SRS or the A-SRS triggered by the UL grant. FIG.5is a block diagram of an exemplary UE500according to some aspects of the present disclosure. The UE500may be a UE115in the network100as discussed above inFIG.1. As shown, the UE500may include a processor502, a memory504, an SRS module508, a transceiver510including a modem subsystem512and a RF unit514, and one or more antennas516. These elements may be in direct or indirect communication with each other, for example via one or more buses. The processor502may have various features as a specific-type processor. For example, these may include a CPU, a DSP, an ASIC, a controller, a FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor502may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The memory504may include a cache memory (e.g., a cache memory of the processor502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid state memory device, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory504may include a non-transitory computer-readable medium. The memory504may store instructions506. The instructions506may include instructions that, when executed by the processor502, cause the processor502to perform operations described herein, for example, aspects ofFIGS.1-4and7. Instructions506may also be referred to as program code. The program code may be for causing a wireless communication device to perform these operations, for example by causing one or more processors (such as processor502) to control or command the wireless communication device to do so. The terms “instructions” and “code” should be interpreted broadly to include any type of computer-readable statement(s). For example, the terms “instructions” and “code” may refer to one or more programs, routines, sub-routines, functions, procedures, etc. “Instructions” and “code” may include a single computer-readable statement or many computer-readable statements. The SRS module508may be implemented via hardware, software, or combinations thereof. For example, the SRS module508may be implemented as a processor, circuit, and/or instructions506stored in the memory504and executed by the processor502. In some examples, the SRS module508can be integrated within the modem subsystem512. For example, the SRS module508can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem512. The SRS module508may be used for various aspects of the present disclosure, for example, aspects ofFIGS.1-4and7. For example, the SRS module508may be configured to detect an error when decoding a data transmission received from a BS (e.g., the BSs105and/or600) via a BWP. The SRS module508may also be configured to trigger, in response to detecting the error, a transmission to the BS of a first SRS using a first SRS resource set of the BWP. As shown, the transceiver510may include the modem subsystem512and the RF unit514. The transceiver510can be configured to communicate bi-directionally with other devices, such as the UEs115and/or another core network element. The modem subsystem512may be configured to modulate and/or encode data according to a MCS, e.g., a LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc. The RF unit514may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated/encoded data (e.g., PDSCH signal, PDCCH signal, SRS resource configuration, SRS resource activation, SRS resource deactivation) from the modem subsystem512(on outbound transmissions) or of transmissions originating from another source such as a UE115. The RF unit514may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver510, the modem subsystem512and/or the RF unit514may be separate devices that are coupled together at the UE500to enable the UE500to communicate with other devices. The RF unit514may provide modulated and/or processed data, e.g. data packets (or, more generally, data messages that may contain one or more data packets and other information), to the antennas516for transmission to one or more other devices. This may include, for example, transmission of information to complete attachment to a network and communication with a camped UE115according to some aspects of the present disclosure. The antennas516may further receive data messages transmitted from other devices and provide the received data messages for processing and/or demodulation at the transceiver510. The transceiver510may provide the demodulated and decoded data (e.g., PUSCH signal, UL data, SRSs, UE capability reports, RI reports) to the SRS module508for processing. The antennas516may include multiple antennas of similar or different designs to sustain multiple transmission links. In an aspect, the UE500can include multiple transceivers510implementing different RATs (e.g., NR and LTE). In an aspect, the UE500can include a single transceiver510implementing multiple RATs (e.g., NR and LTE). In an aspect, the transceiver510can include various components, where different combinations of components can implement different RATs. FIG.6is a block diagram of an exemplary BS600according to some aspects of the present disclosure. The BS600may be a BS105discussed above inFIG.1. As shown, the BS600may include a processor602, a memory604, a SRS module608, a transceiver610including a modem subsystem612and a radio frequency (RF) unit614, and one or more antennas616. These elements may be in direct or indirect communication with each other, for example via one or more buses. The processor602may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor602may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The memory604may include a cache memory (e.g., a cache memory of the processor602), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, solid state memory device, hard disk drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In an aspect, the memory604includes a non-transitory computer-readable medium. The memory604may store, or have recorded thereon, instructions606. The instructions606may include instructions that, when executed by the processor602, cause the processor602to perform the operations described herein with reference to the UEs115in connection with aspects of the present disclosure, for example, aspects ofFIGS.1-4, and7. Instructions606may also be referred to as program code, which may be interpreted broadly to include any type of computer-readable statement(s) as discussed above with respect toFIG.5. The SRS module608may be implemented via hardware, software, or combinations thereof. For example the SRS module608may be implemented as a processor, circuit, and/or instructions606stored in the memory604and executed by the processor602. In some examples, the SRS module608can be integrated within the modem subsystem612. For example, the SRS module608can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem612. The SRS module608may be used for various aspects of the present disclosure, for example, aspects ofFIGS.1-4, and7. As shown, the transceiver610may include a modem subsystem612and an RF unit614. The transceiver610can be configured to communicate bi-directionally with other devices, such as the BSs105. The modem subsystem612may be configured to modulate and/or encode the data from the memory604according to a modulation and coding scheme (MCS), e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc. The RF unit614may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.) modulated/encoded data (e.g., PUSCH signal, UL data, SRSs, UE capability reports, RI reports) from the modem subsystem612(on outbound transmissions) or of transmissions originating from another source such as a UE115or a BS105. The RF unit614may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver610, the modem subsystem612and the RF unit614may be separate devices that are coupled together at the BS600to enable the BS600to communicate with other devices. The RF unit614may provide modulated and/or processed data, e.g. data packets (or, more generally, data messages that may contain one or more data packets and other information), to the antennas616for transmission to one or more other devices. The antennas616may further receive data messages transmitted from other devices. The antennas616may provide the received data messages for processing and/or demodulation at the transceiver610. The transceiver610may provide the demodulated and decoded data (e.g., PDSCH signal, PDCCH, DL data, SRS resource configuration, SRS resource activation, SRS resource deactivation) to the SRS module608. The antennas616may include multiple antennas of similar or different designs in order to sustain multiple transmission links. The RF unit614may configure the antennas616. In an aspect, the BS600can include multiple transceivers610implementing different RATs (e.g., NR and LTE). In an aspect, the BS600can include a single transceiver610implementing multiple RATs (e.g., NR and LTE). In an aspect, the transceiver610can include various components, where different combinations of components can implement different RATs. FIG.7is a flow diagram of a wireless communication method700according to some aspects of the present disclosure. Aspects of the method700can be executed by a computing device (e.g., a processor, processing circuit, and/or other suitable component) of a wireless communication device or other suitable means for performing the steps. For example, a wireless communication device, such as the UEs115and/or500may utilize one or more components, such as the processor502, the memory504, the SRS module508, the transceiver510, the modem512, and the one or more antennas516, to execute the steps of method700. As illustrated, the method700includes a number of enumerated steps, but aspects of the method700may include additional steps before, after, and in between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order. At block710, a UE (e.g., the UEs115and/or500) can detect an error when decoding a data transmission received from a BS via a BWP. In some instances, the UE may utilize one or more components, such as the processor502, the memory504, the SRS module508, the transceiver510, the modem512, and the one or more antennas516, to detect an error when decoding a data transmission received from a BS via a BWP. At block720, a UE (e.g., the UEs115and/or500) can trigger, in response to detecting the error, a transmission to the BS of a first SRS using a first SRS resource set of the BWP. In some instances, the UE may utilize one or more components, such as the processor502, the memory504, the SRS module508, the transceiver510, the modem512, and the one or more antennas516, to trigger, in response to the detecting the error, a transmission to the BS of a first SRS using a first SRS resource set of the BWP. In some aspects of method700, the BWP is the BWP of a PDSCH. In some aspects, an open-loop power control parameter of the first SRS is configured to be independent from a corresponding open-loop power control parameter of a second SRS configured to be transmitted using a second SRS resource set of the BWP, the second SRS resource set configured for a NR use case or operation. In some aspects, the NR use case or operation is an antenna switching use case. In some aspects, the NR use case or operation is a codebook or a non-codebook use case. In some aspects, the NR use case or operation is a beam management use case. In some aspects, the first SRS resource set is configured for an antenna switching operation. In some instances, an open-loop power control parameter of the first SRS is configured to be same as a corresponding open-loop power control parameter of a second SRS of the antenna switching operation configured to be transmitted using the first SRS resource set. In some instances, a transmit power of the first SRS is configured to exceed a transmit power of a second SRS of the antenna switching operation configured to be transmitted using the first SRS resource set. Some aspects of method700further comprise receiving, from the BS, a DCI message including TPC command(s) to configure a closed-loop power control parameter of the first SRS. In some aspects, the method700further comprising receiving, from the BS, a PDCCH communication configured to schedule the data transmission received from the BS, the DCI message received prior to a last symbol of the PDCCH communication. In some aspects, method700further comprises configuring, in response to the DCI message being received prior to the last symbol of the PDCCH communication, the closed-loop power control parameter of the first SRS. In some aspects, the DCI message is received at least a threshold number of symbols prior to a start of the transmission of the first SRS. In some aspects, method700further comprises configuring, in response to the DCI message being received at least the threshold number of symbols prior to the start of the transmission of the first SRS, the closed-loop power control parameter of the first SRS. In some aspects, the threshold number of symbols is equal to a number of slot delays corresponding to a minimum value of a RRC parameter K2 configured by a RRC message from the BS. In some aspects, the first SRS resource set is an aperiodic SRS resource set. Some aspects of method700further comprise triggering a transmission to the BS of a second SRS using a periodic SRS resource set; and aborting, in response to the triggering the transmission to the BS of the second SRS, the transmission of the second SRS if the transmission of the second SRS collides with the transmission of the first SRS. Some aspects of method700further comprise triggering a transmission to the BS of a report including periodic channel state information (P-CSI) and/or semi-persistent channel state information (SP-CSI); and aborting, in response to the triggering the transmission to the BS of the report, the transmission of the report if (i) the transmission of the report collides with the transmission of the first SRS, and (ii) the UE is incapable of simultaneously transmitting (1) a SRS transmission, and (2) (a) a physical uplink control channel (PUCCH), or (b) a physical uplink shared channel (PUSCH) transmission. Some aspects of method700further comprise receiving, from the BS, a downlink (DL) grant configured to schedule the data transmission received from the BS and trigger a transmission to the BS of a second SRS using a second SRS resource set that is an aperiodic resource set; and aborting, in response to the receiving the DL grant, the transmission to the BS of the first SRS. Some aspects of method700further comprise receiving, from the BS, an uplink (UL) grant configured to trigger a transmission to the BS of a second SRS using a second SRS resource set that is an aperiodic resource set; and aborting, in response to the receiving the UL grant, the transmission to the BS of the first SRS or the second SRS, and transmitting to the BS the second SRS or the first SRS, respectively, if (i) the transmission of the first SRS collides with the transmission of the second SRS; and (ii) if the UE is incapable of simultaneously transmitting the first SRS and the second SRS to the BS. Some aspects of method700further comprise receiving, from the BS, an uplink (UL) grant configured to trigger a transmission to the BS of a second SRS using a second SRS resource set that is an aperiodic resource set; and selecting, in response to the receiving the UL grant, the first SRS or the second SRS to abort if (i) the transmission of the first SRS collides with the transmission of the second SRS; and (ii) if the UE is incapable of simultaneously transmitting the first SRS and the second SRS to the BS. Recitations of Some Aspects of the Present Disclosure Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: detecting an error when decoding a data transmission received from a base station (BS) via a bandwidth part (BWP); and triggering, in response to the detecting the error, a transmission to the BS of a first sounding resource signal (SRS) using a first SRS resource set of the BWP. Aspect 2: The method of aspect 1, wherein an open-loop power control parameter of the first SRS is configured to be independent from a corresponding open-loop power control parameter of a second SRS configured to be transmitted using a second SRS resource set of the BWP, and the second SRS resource set configured for a new radio (NR) use case. Aspect 3: The method of aspect 2, wherein the NR use case is an antenna switching operation. Aspect 4: The method of aspect 2, wherein the NR use case is a codebook or a non-codebook operation. Aspect 5: The method of as 2, wherein the NR use case is a beam management operation. Aspect 6: The method of aspect 1, wherein the first SRS resource set is configured for an antenna switching operation. Aspect 7: The method of aspect 6, wherein an open-loop power control parameter of the first SRS is configured to be match a corresponding open-loop power control parameter of a second SRS of the antenna switching operation configured to be transmitted using the first SRS resource set. Aspect 8: The method of aspect 6, wherein a transmit power of the first SRS is configured to exceed a transmit power of a second SRS of the antenna switching operation configured to be transmitted using the first SRS resource set. Aspect 9: The method of any of aspects 1-8, further comprising: receiving, from the BS, a downlink control information (DCI) message including a group transmission power control (TPC) command to configure a closed-loop power control parameter of the first SRS. Aspect 10: The method of any of aspects 1-9, further comprising: receiving, from the BS, a physical downlink control channel (PDCCH) communication scheduling the data transmission received from the BS, the DCI message received prior to a last symbol of the PDCCH communication; and configuring, in response to the DCI message being received prior to the last symbol of the PDCCH communication, the closed-loop power control parameter of the first SRS (e.g., based on the TPC command). Aspect 11: The method of any of aspects 1-9, wherein the DCI message is received at least a threshold number of symbols prior to a start of the transmission of the first SRS, the method further comprising: configuring, in response to the DCI message being received at least the threshold number of symbols prior to the start of the transmission of the first SRS, the closed-loop power control parameter of the first SRS. Aspect 12: The method of aspect 11, wherein the threshold number of symbols is equal to a number of symbols corresponding to a minimum gap in slots between a DCI message scheduling a UL transmission via a PDCCH and a latter UL transmission via a PUSCH. Aspect 13: The method of any of aspects 1-12, wherein the first SRS resource set is an aperiodic SRS resource set. Aspect 14: The method of any of aspects 1-13, further comprising: detecting a scheduled transmission of a second SRS to the BS using a periodic SRS resource set; and aborting the scheduled transmission of the second SRS, in response to the detecting a collision between the scheduled transmission of the second SRS and transmission of the first SRS. Aspect 15: The method of any of aspects 1-14, further comprising: detecting a scheduled transmission to the BS of a report including periodic channel state information (P-CSI) and/or semi-persistent channel state information (SP-CSI); and aborting, in response to the detecting the transmission to the BS of the report, the transmission of the report upon detecting a collision between the transmission of the report and the transmission of the first SRS, wherein the UE is incapable of simultaneously transmitting (1) a SRS transmission, and (2) (a) a physical uplink control channel (PUCCH), or (b) a physical uplink shared channel (PUSCH) transmission. Aspect 16: The method of any of aspects 1-15, further comprising: receiving, from the BS, a downlink (DL) grant configured to schedule the data transmission received from the BS, wherein the first RS is not transmitted when the DL grant includes a trigger for transmission of a second SRS using a second SRS resource set that is an aperiodic resource set. Aspect 17: The method of any of aspects 1-16, further comprising: receiving, from the BS, an uplink (UL) grant configured to trigger a transmission to the BS of a second SRS using a second SRS resource set that is an aperiodic resource set; and aborting, in response to the receiving the UL grant, the transmission to the BS of the first SRS or the second SRS, and transmitting to the BS the second SRS or the first SRS, respectively, if (i) the transmission of the first SRS collides with the transmission of the second SRS; and (ii) if the UE is incapable of simultaneously transmitting the first SRS and the second SRS to the BS. Aspect 18: The method of any of aspects 1-17, further comprising: receiving, from the BS, an uplink (UL) grant configured to trigger a transmission to the BS of a second SRS using a second SRS resource set that is an aperiodic resource set; and selecting, in response to the receiving the UL grant, the first SRS or the second SRS to abort if (i) the transmission of the first SRS collides with the transmission of the second SRS; and (ii) if the UE is incapable of simultaneously transmitting the first SRS and the second SRS to the BS. Aspect 19: A user equipment (UE), comprising: a memory; a processor coupled to the memory; and a transceiver coupled to the processor, the UE configured to perform the methods of aspects 1-18. Aspect 20: A user equipment (UE) comprising means for performing the methods of aspects 1-18. Aspect 21: A non-transitory computer-readable medium (CRM) having program code recorded thereon, the program code comprises code for causing a user equipment (UE) to perform the methods of aspects 1-18. Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). As those of some skill in this art will by now appreciate and depending on the particular application at hand, many modifications, substitutions and variations can be made in and to the materials, apparatus, configurations and methods of use of the devices of the present disclosure without departing from the spirit and scope thereof. In light of this, the scope of the present disclosure should not be limited to that of the particular embodiments illustrated and described herein, as they are merely by way of some examples thereof, but rather, should be fully commensurate with that of the claims appended hereafter and their functional equivalents. | 84,235 |
11943768 | DETAILED DESCRIPTION A wireless communication network may include devices that are capable of direct communications (e.g., communications that are not routed through a base station or other intermediary device). For example, in a factory setting there may be a controlling device (e.g., a programmable logic controller (PLC)) that not only communicates with a base station but also communicates with other devices (e.g., sensors, actuators) by using radio resources that are reserved for direct (or “sidelink”) communications. To ensure that a device can consistently communicate data with minimal signaling overhead, the controlling device may configure the device with semi-persistently scheduled (SPS) resources (e.g., frequency resources that are periodically allocated to the device). But in some cases the device may not have data to transmit to the controlling device when SPS resources occur, which means that the SPS resources may go unused. Unused SPS resources may reduce system efficiency and throughput, among other disadvantages that degrade system performance. According to the techniques described herein, a first device (e.g., a PLC) may improve system performance by re-allocating unused SPS resources configured for a second device to a third device or use the unused SPS resources for its own transmissions. To determine the use status of the SPS resources, the first device may configure a set of resources, referred to as “restart resources,” that the second device can use to request (or “claim”) the SPS resources. If the second device transmits a message over the restart resources, the first device may know that the second device wishes to use the SPS resources and, accordingly, restart (e.g., allocate) the SPS resources for the second device. If the second device does not transmit a message over the restart resources, the first device may know that the second device has no use for the SPS resources and, accordingly, re-allocate the SPS resources to the third device. Thus, SPS resources configured for the second device may be used even when the second device has no data to transmit. Aspects of the disclosure are initially described in the context of a wireless communications system. Aspects of the disclosure are further described in the context of an additional wireless communications system and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to various aspects of radio link management. FIG.1illustrates an example of a wireless communications system100that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The wireless communications system100may include one or more base stations105, one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communications system100may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof. The base stations105may be dispersed throughout a geographic area to form the wireless communications system100and may be devices in different forms or having different capabilities. The base stations105and the UEs115may wirelessly communicate via one or more communication links125. Each base station105may provide a coverage area110over which the UEs115and the base station105may establish one or more communication links125. The coverage area110may be an example of a geographic area over which a base station105and a UE115may support the communication of signals according to one or more radio access technologies. The UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. The UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115, the base stations105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown inFIG.1. The base stations105may communicate with the core network130, or with one another, or both. For example, the base stations105may interface with the core network130through one or more backhaul links120(e.g., via an S1, N2, N3, or other interface). The base stations105may communicate with one another over the backhaul links120(e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations105), or indirectly (e.g., via core network130), or both. In some examples, the backhaul links120may be or include one or more wireless links. One or more of the base stations105described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology. A UE115may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE115may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE115may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as the base stations105and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown inFIG.1. The UEs115and the base stations105may wirelessly communicate with one another via one or more communication links125over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links125. For example, a carrier used for a communication link125may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system100. For example, the carrier bandwidth may be one of a number of determined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system100(e.g., the base stations105, the UEs115, or both) may have hardware configurations that support communications over a particular carrier bandwidth or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system100may include base stations105or UEs115that support simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE115may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth. Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements that a UE115receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE115. A wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE115. The time intervals for the base stations105or the UEs115may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, where Δfmaxmay represent the maximum supported subcarrier spacing, and Nfmay represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023). Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation. A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system100and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)). Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs115. For example, one or more of the UEs115may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs115and UE-specific search space sets for sending control information to a specific UE115. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices. In some examples, a base station105may be movable and therefore provide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas110associated with different technologies may overlap, but the different geographic coverage areas110may be supported by the same base station105. In other examples, the overlapping geographic coverage areas110associated with different technologies may be supported by different base stations105. The wireless communications system100may include, for example, a heterogeneous network in which different types of the base stations105provide coverage for various geographic coverage areas110using the same or different radio access technologies. Some UEs115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station105without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program. Some UEs115may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging. The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications. The UEs115may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions). Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT), mission critical video (MCVideo), or mission critical data (MCData). Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein. In some examples, a UE115may also be able to communicate directly with other UEs115over a device-to-device (D2D) communication link135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs115utilizing D2D communications may be within the geographic coverage area110of a base station105. Other UEs115in such a group may be outside the geographic coverage area110of a base station105or be otherwise unable to receive transmissions from a base station105. In some examples, groups of the UEs115communicating via D2D communications may utilize a one-to-many (1:M) system in which each UE115transmits to every other UE115in the group. In some examples, a base station105facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs115without the involvement of a base station105. In some systems, the D2D communication link135may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., base stations105) using vehicle-to-network (V2N) communications, or with both. The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs115served by the base stations105associated with the core network130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services150for one or more network operators. The IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service. Some of the network devices, such as a base station105, may include subcomponents such as an access network entity140, which may be an example of an access node controller (ANC). Each access network entity140may communicate with the UEs115through one or more other access network transmission entities145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs). Each access network transmission entity145may include one or more antenna panels. In some configurations, various functions of each access network entity140or base station105may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station105). The wireless communications system100may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs115located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz. The wireless communications system100may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communications system100may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as the base stations105and the UEs115may employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples. A base station105or a UE115may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station105or a UE115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a base station105may be located in diverse geographic locations. A base station105may have an antenna array with a number of rows and columns of antenna ports that the base station105may use to support beamforming of communications with a UE115. Likewise, a UE115may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port. Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station105, a UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation). The wireless communications system100may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE115and a base station105or a core network130supporting radio bearers for user plane data. At the physical layer, transport channels may be mapped to physical channels. The UEs115and the base stations105may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval. In some examples, the UEs115may engage in direct (or “sidelink”) communications, which may be communications that are not routed through a base station105or other intermediary device. For instance, a first UE115may configure a second UE115with sidelink SPS resources that occur periodically. Such a scenario may occur, for example, in a factory setting where a first UE (e.g., a PLC) configures a second UE (e.g., a sensor, an actuator) with SPS resources so that the second UE can report data without the overhead associated with dynamic scheduling. However, some instances of the SPS resources may go unused if the second UE does not have any data to report when those instances occur. Unused SPS resources may reduce the efficiency and throughput of wireless communications system100, among other disadvantages. According to the techniques described herein, a first UE115may prevent SPS resources from going unused by allocating SPS resources configured for a second UE115to either the second UE115—if the second UE115has traffic (e.g., pending data, buffered data) for the first UE115—or another UE115. To do so, the first UE115may configure the second UE115with restart resources that the second UE115can use to request, claim, or otherwise secure the SPS resources. For example, if the second UE115has traffic for the first UE115, the second UE115may request a set of SPS resources associated with the restart resources by transmitting a message of a predetermined type over the restart resources. If the second UE115does not transmit a message over the restart resources, the first UE115may re-allocate the set of SPS resources to another UE115. In some examples, rather than re-allocating the set of SPS resources to another UE115, the first UE115may use the set of SPS resources to transmit data to one or more UEs115. Thus, the first UE115may ensure that SPS resources do not go unused, which may improve the performance of the wireless communications system100. FIG.2illustrates an example of a wireless communications system200that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. In some examples, the wireless communications system200may implement aspects of the wireless communications system100. For example, the wireless communications system200may include device205-a, device205-b, and device205-c, which may be examples of UEs115as described with reference toFIG.1. To ensure that SPS resources configured for device205-bare used, device205-amay allocate configured SPS resources for device205-bbased on the traffic—or lack thereof—at device205-b. Thus, device205-amay implement a traffic-driven restart technique for sidelink SPS. Although described with reference to sidelink communications, the techniques described herein may be implemented for other types of communications, and thus may performed by a base station or other type of device. Device205-amay communicate with other devices within its coverage area210. For example, device205-amay communicate with device205-band device205-c, among other devices (not shown). The communications may be routed through an intermediary device (e.g., a base station) or may be exchanged directly between device205-aand another device205, a technique which may be referred to as sidelink communication when the devices205are UEs. Communications between device205-aand a base station may occur through a first interface (e.g., the Uu interface) whereas sidelink communications between device205-aand another device205may occur through a second interface (e.g., the PC5 interface). In some examples, communications between a device205and a base station may be referred to as Uu communications. Device205-amay support multiple resource allocation modes for sidelink communications. For example, device205-amay implement sidelink communications with another device in Mode 1 or in Mode 2, which may be V2X modes. In Mode 1, a base station may not only configure sidelink resources for device205-abut also schedule communications between device205-aand another device205over the configured sidelink resources. For example, the base station may send device205-adownlink control information (DCI) (e.g., DCI3_0) that includes a dynamic grant indicating the resources (e.g., time and frequency) for one or more sidelink transmissions by device205-a. Additionally or alternatively, the base station may use RRC signaling to schedule the sidelink resources for device205-a. In Mode 2, a base station may configure device205-awith sidelink resources, but the scheduling of those resources may be performed by device205-a(as opposed to the base station). For example, device205-amay use sidelink control information (SCI) (e.g., SCI1, SCI2) to schedule a subset of the configured sidelink resources for communications by device205-5or another device. SCI1 may be transmitted in a physical sidelink control channel (PSCCH) and SCI2 may be transmitted in a physical sidelink shared channel (PSSCH), which may also be used to convey the scheduled data. The PSSCH may be used for unicast communications, groupcast communications, or broadcast communication. The SPS resources selected and scheduled by a device205may be based on one or more SCI1 messages and/or based on reference signal received power (RSRP) measurements of modulation signals (e.g., demodulation reference signals (DMRS)) in the PSSCH or the PSCCH. In some examples, the device205that schedules sidelink resources may be a more sophisticated, intelligent, or advanced device than the device for which the sidelink resources are scheduled. For instance, the scheduling device205may be a PLC or other device with more capabilities than the scheduled device. Transmissions from a scheduling device may be referred to as forward transmissions whereas transmissions to a scheduling device may be referred to as reverse transmissions. So, direct communications from device205-bto device205-amay be referred to as reverse sidelink communications. Upon receipt of sidelink data, device205-amay transmit HARQ feedback (e.g., in physical sidelink feedback channel (PSFCH)) to the transmitting device. For example, device205-amay transmit an acknowledgement (ACK) over the PSFCH if device205-asuccessfully decodes the received data. Alternatively, device205-amay transmit a negative-acknowledgement (NACK) over the PSFCH if device205-ais unable to decode the received data (e.g., so that the data can be re-transmitted). Sidelink HARQ feedback may be explicitly signaled for unicast or groupcast transmissions. Alternatively, implicit NACK (where a NACK is assumed if an ACK is not received) may be used for groupcast transmissions. In some examples, device205-a(which may be operating in Mode 2) may configure device205-bwith SPS resources so that device205-bcan transmit data to device205-awithout a dynamic grant. Such a technique may be particularly useful for high priority data, small data payloads, or periodic data, among others. To configure device205-bwith the SPS, device205-amay transmit SPS configuration information, such as SPS configuration information215, to device205-b. The SPS configuration information may indicate one or more parameters associated with the SPS configuration, such as the starting time, the frequency, the periodicity, and/or the length (number of slots) of the SPS resources. Device205-bmay use the configured SPS resources to periodically transmit data to device205-a. However, according to the techniques described herein, the SPS resources configured for device205-bmay not be automatically allocated to device205-b(e.g., for efficiency reasons). So, device205-bmay secure the allocation of SPS resources before device205-btransmits on those SPS resources. Such a process may be referred to as restarting the SPS resources, and may be based on device205-bhaving data for device205-a. Device205-bmay restart a set of SPS resources by transmitting a message (e.g., restart message225) to device205-aover restart resources associated with the set of SPS resources. Device205-amay configure device205-bwith the restart resources using restart resources configuration information220, which may indicate one or more parameters associated with the restart resources. Upon receiving the restart message225, device205-amay allocate to device205-bthe set of SPS resources associated with the restart resources. That is, the restart message225may indicate to device205-athat the device205-bhas data to transmit or otherwise intends to use the set of SPS resources, and as such, the device205-amay anticipate receiving data from device205-bon the set of SPS resources, and may refrain from re-allocating the set of SPS resources to another device205. Alternatively, device205-bmay decide not to utilize or restart the set of SPS resources (e.g., because device205-bdoes not have data for device205-a). In such a scenario, device205-bmay refrain from transmitting a message over the restart resources. Upon determining that a restart message is absent from the restart resources, device205-amay allocate to device205-cthe set of SPS resources associated with the restart resources. This way, the re-allocated set of SPS resources configured for device205-bmay be used for communications between device205-aand device205-c(e.g., using communication link230). Thus, device205-amay allocate the SPS resources based on the traffic—or lack thereof—at device205-b, which may ensure that SPS resources configured for device205-bdo not go unused. Such techniques may be referred to as traffic-driven restart techniques for SPS sidelink resources. FIG.3illustrates an example of SPS resources300that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The SPS resources300may be an example of SPS resources configured for a device as described herein. To ensure that the SPS resources300are used, the configuring device may allocate the SPS resources300based on the presence or absence of traffic at the device for which the SPS resources300are configured. For ease of reference, the configuring device may be referred to inFIG.3as the first device and the configured device may be referred to as the second device. The SPS resources300may include multiple instances of SPS resources (e.g., SPS instance 0 through SPS instance N), which may be sets of time and frequency resources that occur periodically in the time domain. Thus, the SPS resources300may have a period305. The SPS instances may be configured to occur indefinitely (e.g., until the SPS resources are explicitly deactivated) or for a configured amount of time. Each SPS instance may include n+1 time slots, which may be continuous in the time domain, and each SPS instance may also include a set of frequencies that make up frequency band310. The second device configured with SPS resources300may secure a set of the SPS resources before transmitting data over those resources. Otherwise, the set of SPS resources may be re-allocated to another device. To secure a set of SPS resources, the second device may transmit a restart message (e.g., a data message or other type of message) in the restart resources315associated with the set of SPS resources. The presence of the message may indicate to the first device that the second device wishes for the set of SPS resources associated with the restart resources315to be restarted. The set of SPS resources associated with the restart resources315may include the next x SPS instances or the SPS instances that occur within ay ms (relative to the restart resources315), as configured by the first device. Put another way, the restart resources315may be associated with a configured quantity of SPS instances or a threshold duration of time. Alternatively, the restart resources315may be associated with an indefinite quantity of SPS instances (e.g., SPS resources may be allocated to the second device until a termination message is communicated by one of the devices). The restart resources315may be transmitted over the full bandwidth of frequency band310or over a portion of the frequency band310. Thus, the restart resources315may cover the same frequency resources occupied by a transmission on the SPS resources300. As an illustration, the restart resources315may occupy m subchannels where each subchannel includes M resources blocks (RBs). After transmitting the restart message in restart resources315, the second device may determine whether the set of SPS resources is allocated to the second device based on the presence or absence of feedback for the restart message. If the second device does not receive feedback for the restart message within a threshold duration of time (e.g., within x time slots) of transmitting the restart message, the second device may determine that the set of SPS resources has not been restarted and may refrain from transmitting in the remaining resources of the set. If the second device does receive feedback for the restart message within the threshold duration of time, the second device may determine that the set of SPS resources has been restarted and may transmit data to the first device using the set of SPS resources. In some examples, the threshold duration of time may be configured so that expiry of the duration falls within the restart resources315(or coincides with the end of the restart resources315). For example, assuming that the second device transmits a restart message in time slot 0, the threshold duration of time may be set to two time slots so that the second device knows by the end of the restart resources315whether the set of SPS resources has been restarted. So, the restart resources315may in some examples be divided into two subsets of resources: a first subset of resources (e.g., time slot 0) in which a restart message is permitted or expected, and a second subset of resources (e.g., time slots 1 and 2) in which feedback is permitted or expected. In some examples, the threshold duration of time may be tracked via an early suspension timer. Upon securing a set of SPS resources, the second device may transmit data in the set of SPS resources until the second device runs out of data for the first device or some other suspension event occurs. At this point, the second device may implicitly release any remaining SPS resources in the set of SPS resources by failing to transmit data for a threshold duration of time (which may be tracked via an early suspension timer). Alternatively, the second device may explicitly release the remaining SPS resources by transmitting a message to the first device indicating as much. Such a process may be referred to as early suspension, early termination, early release, or any other suitable terminology. Some or all of the released SPS resources may be re-allocated by the first device to another device, which may improve the efficiency of the system. For example, if the first device detects early suspension at time slot 5, the first device may re-allocate the remaining slots in that SPS instance (e.g., time slots 6 through n) to a third device, as well any remaining SPS instances in the set of SPS resources. Although shown occurring once, in some examples, the first device may configure restart resources315to occur periodically (e.g., every nth SPS instance). Although shown included in an SPS instance, in some examples, restart resources315may be included in resources other than SPS resources300. FIG.4illustrates an example of a process flow400that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. In some examples, process flow400may implement aspects of wireless communications system100or200. For example, process flow400may be implemented by device405, device410, and device415, which may be examples of a device as described herein. Process flow400may be an example of a traffic-driven restart technique for SPS sidelink resources as described herein. Specifically, process flow400illustrates an example in which device410restarts a set of SPS resources then releases the set of SPS resources early. At420, device405may transmit to device410an indication of an SPS configuration for device410. The indication of the SPS configuration may include values for various SPS parameters, such as the starting time, the frequency, the periodicity, and/or the length (number of slots) of the SPS resources. The indication of the SPS configuration may be conveyed via higher layer signaling (e.g., RRC signaling) or lower layer signaling (e.g., in a DCI or a MAC control element (MAC-CE)). At425, device405may transmit to device410an indication of a restart configuration for device410. The indication of the restart configuration may be conveyed via higher layer signaling (e.g., RRC signaling) or lower layer signaling (e.g., in a DCI or a MAC-CE). The indication of the restart configuration may include values for various restart parameters, such as the time and frequency of restart resources and/or a periodicity of the restart resources. In some examples, the restart configuration may define the set of SPS resources associated with the restart resources. In some examples, the restart configuration may define the type of message device410should use as a restart message. For example, the restart message may be a data message, a dummy message (e.g., an all-1 message), or some other type of message. In some examples, the restart configuration may define the type of message device410should use to release SPS resources. In some examples, the restart configuration may set the duration of time used for implicit early suspension. After425, device405may monitor the restart resources for a possible restart message from device410. At430, device410may determine that device410has traffic intended for device405. For example, device410may detect that device410has data pending (e.g., buffered) for device405. At435, device410may transmit a restart message over the restart resources indicated at425. The restart message may request allocation of the set of SPS resources associated with the restart resources. Device410may transmit the restart message based on determining that device410has traffic intended for device405. The restart message may be a data message, a dummy message, or another type of message preconfigured by device405. At440, device405may transmit feedback for the restart message based on the decoding status of the message. In some examples, the transmission of the feedback message coincides (e.g., temporally, in the time domain) with at least a portion of the restart resources, as described with reference toFIG.3. In some examples, the feedback for the restart message may serve as a confirmation of restarting the set of SPS resources. After440, device405may monitor the set of SPS resources for data from device410. At445, device410may transmit to device405data based on receiving the feedback at440. Device410may transmit the data over at least a subset of the set of SPS resources associated with the restart resources used at435. Device410may continue to transmit data over the subsets of the set of SPS resources until device410has no more data for device405(or until another early suspension event occurs). At450, device410may determine that an early suspension event has occurred (e.g., device410may detect an absence of data for device410). At455, device410may transmit to device405an early suspension message that indicates device410has released any remaining SPS resources in the set of SPS resources. Device410may transmit the early suspension message based on detecting the early suspension event at450. In some examples device410may transmit the early suspension message over a subset of the set of SPS resources. At460, device405may determine that early suspension of the set of SPS resources has occurred based on the early suspension message received at455. Additionally or alternatively, device405may determine that early suspension has occurred based on an early suspension timer expiring. At465, device405may re-allocate the remaining SPS resources in the set of SPS resources to one or more devices, such as device415. Device405may re-allocate the remaining SPS resources for transmissions by device405(e.g., to device415and/or another device), for transmissions by device415(e.g., to device405, and/or another device), or a combination thereof. At470, device405may transmit to device415an indication of the re-allocated SPS resources. In some examples, device505may schedule device515for communications over the set of SPS resources. If device405re-allocated the remaining SPS resources for transmissions by device415, device405may, after470, monitor the remaining SPS resources in set of SPS resources for data from device415. At475, device405and device415may communicate over the re-allocated SPS resources. For example, device415may transmit, and device405may receive, information for device405over at least a portion of the remaining SPS resources in the set of SPS resources. Device415may transmit the data based on the indication of SPS resources received at470. Additionally or alternatively, device405may transmit, and device415may receive, information for device415over at least a portion of the remaining SPS resources in the set of SPS resources. Thus, device405may prevent the set of SPS resources from being wasted, even when device410does not have use for the entire set of SPS resources. Alternative examples of the foregoing may be implemented, where some operations are performed in a different order than described, are performed in parallel, or are not performed at all. In some cases, operations may include additional features not mentioned below, or further operations may be added. Additionally, certain operations may be performed multiple times or certain combinations of operations may repeat or cycle. The various indications and messages described herein and with reference to process flow400may be conveyed via higher layer signaling (e.g., RRC signaling) or lower layer signaling (e.g., in a DCI or a MAC-CE). FIG.5illustrates an example of a process flow500that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. In some examples, process flow500may implement aspects of wireless communications system100or200. For example, process flow500may be implemented by device505, device510, and device515, which may be examples of a device as described herein. Process flow500may be an example of a traffic-driven restart technique for SPS sidelink resources as described herein. Specifically, process flow500illustrates an example in which device505re-allocates to device515a set of SPS resources configured for device510, thereby ensuring that the set of SPS resource are used. At520, device505may transmit to device510an indication of an SPS configuration for device450. The indication of the SPS configuration may include values for various SPS parameters, such as the starting time, the frequency, the periodicity, and/or the length (number of slots) of the SPS resources. The indication of the SPS configuration may be conveyed via higher layer signaling (e.g., RRC signaling) or lower layer signaling (e.g., in a DCI or a MAC-CE). At525, device505may transmit to device510an indication of a restart configuration for device510. The indication of the restart configuration may be conveyed via higher layer signaling (e.g., RRC signaling) or lower layer signaling (e.g., in a DCI or a MAC-CE). The indication of the restart configuration may include values for various restart parameters, such as the time and frequency of restart resources and/or a periodicity of the restart resources. In some examples, the restart configuration may define the set of SPS resources associated with the restart resources. In some examples, the restart configuration may define the type of message device510should use as a restart message. For example, the restart message may be a data message, a dummy message (e.g., an all-1 message), or some other type of message. In some examples, the restart configuration may define the type of message device510should use to release SPS resources. In some examples, the restart configuration may set the duration of time used for implicit early suspension. After525, device505may monitor the restart resources for a possible restart message from device510. At530, device510may determine that it does not have traffic intended for device505. For example, device510may determine that data for device505is absent from device510. Accordingly, device510may refrain from transmitting a restart message over a set of the restart resources configured at525. At535, device505may determine that a restart message from device510is absent from the restart resources configured at525. Accordingly, at540, device505may re-allocate the set of SPS resources to one or more devices, such as device515. Device505may re-allocate the set of SPS resources for transmissions by device505(e.g., to device415and/or another device), for transmissions by device515(e.g., to device405, and/or another device), or a combination thereof. At545, device505may transmit to device515an indication of the re-allocated set of SPS resources. In some examples, device505may schedule device515for communications over the set of SPS resources. If device505re-allocated the set of SPS resources for transmissions by device515, device505may, after570, monitor the set of SPS resources for transmissions from device515. At550, device505and device515may communicate over the re-allocated set of SPS resources. For example, device515may transmit, and device505may receive, information for device505over at least a subset of the set of SPS resources. Device515may transmit the information based on the indication of SPS resources received at545. Additionally or alternatively, device505may transmit, and device515may receive, information for device455over at least a subset of the set SPS resources. In some examples, device515may continue to use the set of SPS resources to communicate data to device505until device515runs out of data for device505or until the set of SPS resources ends. At555, device510may determine that device510has traffic intended for device505. For example, device510may detect that device510has data pending (e.g., buffered) for device505. At560, device510may transmit a restart message over a periodic instance of the restart resources indicated at525. The restart message may request allocation of the set of SPS resources associated with the restart resources. Device510may transmit the restart message based on determining that device510has traffic intended for device505. The restart message may be a data message, a dummy message, or another type of message preconfigured by device505. At565, device505may transmit feedback for the restart message based on the decoding status of the message. In some examples, the transmission of the feedback message coincides (e.g., temporally, in the time domain) with at least a portion of the restart resources, as described with reference toFIG.3. In some examples, the feedback for the restart message may serve as a confirmation of restarting the set of SPS resources. After565, device505may monitor the set of SPS resources for data from device510. At570, device510may transmit to device505data based on receiving the feedback at565. Device510may transmit the data over at least a subset of the set of SPS resources associated with the restart resources used at560. Device510may continue to transmit data over subsets of the set of SPS resources until an early suspension event occurs of the set of SPS resources ends. Thus, device505may prevent SPS resources from going unused, even when device510does not initially have data for the device505. Alternative examples of the foregoing may be implemented, where some operations are performed in a different order than described, are performed in parallel, or are not performed at all. In some cases, operations may include additional features not mentioned below, or further operations may be added. Additionally, certain operations may be performed multiple times or certain combinations of operations may repeat or cycle. The various indications and messages described herein and with reference to process flow500may be conveyed via higher layer signaling (e.g., RRC signaling) or lower layer signaling (e.g., in a DCI or a MAC-CE). FIG.6shows a block diagram600of a device605that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The device605may be an example of aspects of a UE115as described herein. The device605may include a receiver610, a transmitter615, and a communications manager620. The device605may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver610may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). Information may be passed on to other components of the device605. The receiver610may utilize a single antenna or a set of multiple antennas. The transmitter615may provide a means for transmitting signals generated by other components of the device605. For example, the transmitter615may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). In some examples, the transmitter615may be co-located with a receiver610in a transceiver module. The transmitter615may utilize a single antenna or a set of multiple antennas. The communications manager620, the receiver610, the transmitter615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein. For example, the communications manager620, the receiver610, the transmitter615, or various combinations or components thereof may support a method for performing one or more of the functions described herein. In some examples, the communications manager620, the receiver610, the transmitter615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory). Additionally or alternatively, in some examples, the communications manager620, the receiver610, the transmitter615, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager620, the receiver610, the transmitter615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure). In some examples, the communications manager620may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver610, the transmitter615, or both. For example, the communications manager620may receive information from the receiver610, send information to the transmitter615, or be integrated in combination with the receiver610, the transmitter615, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager620may support wireless communication at a first device in accordance with examples as disclosed herein. For example, the communications manager620may be configured as or otherwise support a means for receiving an indication of a configuration that schedules semi-persistently scheduled resources for data transmissions from the first device. The communications manager620may be configured as or otherwise support a means for receiving, from a second device, an indication of a set of resources available to the first device for requesting a set of the semi-persistently scheduled resources configured for the first device. The communications manager620may be configured as or otherwise support a means for transmitting a message over the set of resources to request the set of semi-persistently scheduled resources. By including or configuring the communications manager620in accordance with examples as described herein, the device605(e.g., a processor controlling or otherwise coupled to the receiver610, the transmitter615, the communications manager620, or a combination thereof) may support techniques for efficient utilization of communication resources. FIG.7shows a block diagram700of a device705that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The device705may be an example of aspects of a device605or a UE115as described herein. The device705may include a receiver710, a transmitter715, and a communications manager720. The device705may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver710may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). Information may be passed on to other components of the device705. The receiver710may utilize a single antenna or a set of multiple antennas. The transmitter715may provide a means for transmitting signals generated by other components of the device705. For example, the transmitter715may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). In some examples, the transmitter715may be co-located with a receiver710in a transceiver module. The transmitter715may utilize a single antenna or a set of multiple antennas. The device705, or various components thereof, may be an example of means for performing various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein. For example, the communications manager720may include an SPS component725, a restart component730, a request component735, or any combination thereof. The communications manager720may be an example of aspects of a communications manager620as described herein. In some examples, the communications manager720, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver710, the transmitter715, or both. For example, the communications manager720may receive information from the receiver710, send information to the transmitter715, or be integrated in combination with the receiver710, the transmitter715, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager720may support wireless communication at a first device in accordance with examples as disclosed herein. The SPS component725may be configured as or otherwise support a means for receiving an indication of a configuration that schedules semi-persistently scheduled resources for data transmissions from the first device. The restart component730may be configured as or otherwise support a means for receiving, from a second device, an indication of a set of resources available to the first device for requesting a set of the semi-persistently scheduled resources configured for the first device. The request component735may be configured as or otherwise support a means for transmitting a message over the set of resources to request the set of semi-persistently scheduled resources. FIG.8shows a block diagram800of a communications manager820that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The communications manager820may be an example of aspects of a communications manager620, a communications manager720, or both, as described herein. The communications manager820, or various components thereof, may be an example of means for performing various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein. For example, the communications manager820may include an SPS component825, a restart component830, a request component835, a feedback component840, a data component845, a suspension component850, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications manager820may support wireless communication at a first device in accordance with examples as disclosed herein. The SPS component825may be configured as or otherwise support a means for receiving an indication of a configuration that schedules semi-persistently scheduled resources for data transmissions from the first device. The restart component830may be configured as or otherwise support a means for receiving, from a second device, an indication of a set of resources available to the first device for requesting a set of the semi-persistently scheduled resources configured for the first device. The request component835may be configured as or otherwise support a means for transmitting a message over the set of resources to request the set of semi-persistently scheduled resources. In some examples, the feedback component840may be configured as or otherwise support a means for receiving, from the second device, a message indicating feedback responsive to the message that requests the set of semi-persistently scheduled resources. In some examples, the data component845may be configured as or otherwise support a means for transmitting data over at least a subset of the set of semi-persistently scheduled resources based on receiving the message indicating the feedback. In some examples, the feedback component840may be configured as or otherwise support a means for determining that a message indicating feedback responsive to the message that requests the set of semi-persistently scheduled resources has not been received within a threshold duration of time. In some examples, the data component845may be configured as or otherwise support a means for refraining from transmitting data over the set of semi-persistently scheduled resources based on the determination. In some examples, the data component845may be configured as or otherwise support a means for transmitting data in a first subset of the set of semi-persistently scheduled resources based on transmitting the message that requests the set of semi-persistently scheduled resources. In some examples, the suspension component850may be configured as or otherwise support a means for transmitting a second message indicating that a second subset of the set of semi-persistently scheduled resources will not be used by the first device. In some examples, the second message is transmitted over a third subset of the set of semi-persistently scheduled resources. In some examples, the set of semi-persistently scheduled resources includes the set of resources for requesting the set of the semi-persistently scheduled resources. In some examples, the restart component830may be configured as or otherwise support a means for receiving a message indicating a type of message for transmission over the set of resources to request the set of the semi-persistently scheduled resources. In some examples, the set of semi-persistently scheduled resources is associated with the set of resources. In some examples, the set of semi-persistently scheduled resources includes a quantity of consecutive instances of semi-persistently scheduled resources, and the SPS component825may be configured as or otherwise support a means for receiving a message indicating the quantity of consecutive instances or a duration of time that includes the quantity of consecutive instances. In some examples, the restart component830may be configured as or otherwise support a means for receiving a message indicating a periodicity associated with the set of resources, where the message that requests the set of semi-persistently scheduled resources is transmitted based on the periodicity. In some examples, the data component845may be configured as or otherwise support a means for determining that the first device has data for the second device, where the message that requests the set of semi-persistently scheduled resources is transmitted based on the determination. FIG.9shows a diagram of a system900including a device905that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The device905may be an example of or include the components of a device605, a device705, or a UE115as described herein. The device905may communicate wirelessly with one or more base stations105, UEs115, or any combination thereof. The device905may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager920, an input/output (I/O) controller910, a transceiver915, an antenna925, a memory930, code935, and a processor940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus945). The I/O controller910may manage input and output signals for the device905. The I/O controller910may also manage peripherals not integrated into the device905. In some cases, the I/O controller910may represent a physical connection or port to an external peripheral. In some cases, the I/O controller910may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I/O controller910may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller910may be implemented as part of a processor, such as the processor940. In some cases, a user may interact with the device905via the I/O controller910or via hardware components controlled by the I/O controller910. In some cases, the device905may include a single antenna925. However, in some other cases, the device905may have more than one antenna925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver915may communicate bi-directionally, via the one or more antennas925, wired, or wireless links as described herein. For example, the transceiver915may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver915may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas925for transmission, and to demodulate packets received from the one or more antennas925. The transceiver915, or the transceiver915and one or more antennas925, may be an example of a transmitter615, a transmitter715, a receiver610, a receiver710, or any combination thereof or component thereof, as described herein. The memory930may include random access memory (RAM) and read-only memory (ROM). The memory930may store computer-readable, computer-executable code935including instructions that, when executed by the processor940, cause the device905to perform various functions described herein. The code935may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code935may not be directly executable by the processor940but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory930may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices. The processor940may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor940may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor940. The processor940may be configured to execute computer-readable instructions stored in a memory (e.g., the memory930) to cause the device905to perform various functions (e.g., functions or tasks supporting resource configuration for requesting semi-persistently scheduled resources). For example, the device905or a component of the device905may include a processor940and memory930coupled to the processor940, the processor940and memory930configured to perform various functions described herein. The communications manager920may support wireless communication at a first device in accordance with examples as disclosed herein. For example, the communications manager920may be configured as or otherwise support a means for receiving an indication of a configuration that schedules semi-persistently scheduled resources for data transmissions from the first device. The communications manager920may be configured as or otherwise support a means for receiving, from a second device, an indication of a set of resources available to the first device for requesting a set of the semi-persistently scheduled resources configured for the first device. The communications manager920may be configured as or otherwise support a means for transmitting a message over the set of resources to request the set of semi-persistently scheduled resources. By including or configuring the communications manager920in accordance with examples as described herein, the device905may support techniques for more efficient utilization of communication resources. In some examples, the communications manager920may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver915, the one or more antennas925, or any combination thereof. Although the communications manager920is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager920may be supported by or performed by the processor940, the memory930, the code935, or any combination thereof. For example, the code935may include instructions executable by the processor940to cause the device905to perform various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein, or the processor940and the memory930may be otherwise configured to perform or support such operations. FIG.10shows a block diagram1000of a device1005that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The device1005may be an example of aspects of a base station, UE, or device as described herein. The device1005may include a receiver1010, a transmitter1015, and a communications manager1020. The device1005may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver1010may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). Information may be passed on to other components of the device1005. The receiver1010may utilize a single antenna or a set of multiple antennas. The transmitter1015may provide a means for transmitting signals generated by other components of the device1005. For example, the transmitter1015may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). In some examples, the transmitter1015may be co-located with a receiver1010in a transceiver module. The transmitter1015may utilize a single antenna or a set of multiple antennas. The communications manager1020, the receiver1010, the transmitter1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein. For example, the communications manager1020, the receiver1010, the transmitter1015, or various combinations or components thereof may support a method for performing one or more of the functions described herein. In some examples, the communications manager1020, the receiver1010, the transmitter1015, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory). Additionally or alternatively, in some examples, the communications manager1020, the receiver1010, the transmitter1015, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager1020, the receiver1010, the transmitter1015, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure). In some examples, the communications manager1020may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver1010, the transmitter1015, or both. For example, the communications manager1020may receive information from the receiver1010, send information to the transmitter1015, or be integrated in combination with the receiver1010, the transmitter1015, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager1020may support wireless communication at a first device in accordance with examples as disclosed herein. For example, the communications manager1020may be configured as or otherwise support a means for configuring semi-persistently scheduled resources for a second device. The communications manager1020may be configured as or otherwise support a means for transmitting an indication of a set of resources available to the second device for requesting a set of the semi-persistently scheduled resources configured for the second device. The communications manager1020may be configured as or otherwise support a means for communicating data over at least a subset of the set of semi-persistently scheduled resources configured for the second device based on transmitting the indication of the set of resources. By including or configuring the communications manager1020in accordance with examples as described herein, the device1005(e.g., a processor controlling or otherwise coupled to the receiver1010, the transmitter1015, the communications manager1020, or a combination thereof) may support techniques for more efficient utilization of communication resources. FIG.11shows a block diagram1100of a device1105that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The device1105may be an example of aspects of a device1005, a UE, or a base station as described herein. The device1105may include a receiver1110, a transmitter1115, and a communications manager1120. The device1105may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses). The receiver1110may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). Information may be passed on to other components of the device1105. The receiver1110may utilize a single antenna or a set of multiple antennas. The transmitter1115may provide a means for transmitting signals generated by other components of the device1105. For example, the transmitter1115may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource configuration for requesting semi-persistently scheduled resources). In some examples, the transmitter1115may be co-located with a receiver1110in a transceiver module. The transmitter1115may utilize a single antenna or a set of multiple antennas. The device1105, or various components thereof, may be an example of means for performing various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein. For example, the communications manager1120may include an SPS component1125, a restart component1130, a data component1135, or any combination thereof. The communications manager1120may be an example of aspects of a communications manager1020as described herein. In some examples, the communications manager1120, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver1110, the transmitter1115, or both. For example, the communications manager1120may receive information from the receiver1110, send information to the transmitter1115, or be integrated in combination with the receiver1110, the transmitter1115, or both to receive information, transmit information, or perform various other operations as described herein. The communications manager1120may support wireless communication at a first device in accordance with examples as disclosed herein. The SPS component1125may be configured as or otherwise support a means for configuring semi-persistently scheduled resources for a second device. The restart component1130may be configured as or otherwise support a means for transmitting an indication of a set of resources available to the second device for requesting a set of the semi-persistently scheduled resources configured for the second device. The data component1135may be configured as or otherwise support a means for communicating data over at least a subset of the set of semi-persistently scheduled resources configured for the second device based on transmitting the indication of the set of resources. FIG.12shows a block diagram1200of a communications manager1220that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The communications manager1220may be an example of aspects of a communications manager1020, a communications manager1120, or both, as described herein. The communications manager1220, or various components thereof, may be an example of means for performing various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein. For example, the communications manager1220may include an SPS component1225, a restart component1230, a data component1235, a request component1240, an allocation component1245, a suspension component1250, a feedback component1255, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications manager1220may support wireless communication at a first device in accordance with examples as disclosed herein. The SPS component1225may be configured as or otherwise support a means for configuring semi-persistently scheduled resources for a second device. The restart component1230may be configured as or otherwise support a means for transmitting an indication of a set of resources available to the second device for requesting a set of the semi-persistently scheduled resources configured for the second device. The data component1235may be configured as or otherwise support a means for communicating data over at least a subset of the set of semi-persistently scheduled resources configured for the second device based on transmitting the indication of the set of resources. In some examples, the request component1240may be configured as or otherwise support a means for receiving a message over the set of resources for requesting the set of semi-persistently scheduled resources, where the data is received from the second device after the message is received. In some examples, the feedback component1255may be configured as or otherwise support a means for transmitting, to the second device, a message indicating feedback responsive to the message for requesting the set of semi-persistently scheduled resources, where the data is received based on transmitting the message indicating the feedback. In some examples, the request component1240may be configured as or otherwise support a means for determining that the second device has not transmitted a message over the set of resources for requesting the set of semi-persistently scheduled resources. In some examples, the allocation component1245may be configured as or otherwise support a means for re-allocating the semi-persistently scheduled resources to a third device. In some examples, the data is received from the second device, and the suspension component1250may be configured as or otherwise support a means for receiving from the second device a second message indicating that a second subset of the set of semi-persistently scheduled resources will not be used by the second device. In some examples, the data is received from the second device, and the allocation component1245may be configured as or otherwise support a means for re-allocating the second subset of the set of semi-persistently scheduled resources to a third device based on receiving the second message. In some examples, the data is received from the second device, and the suspension component1250may be configured as or otherwise support a means for determining that a threshold duration of time has elapsed since receipt of the data. In some examples, the data is received from the second device, and the allocation component1245may be configured as or otherwise support a means for re-allocating a second subset of the set of semi-persistently scheduled resources to a third device based on the determination. In some examples, the restart component1230may be configured as or otherwise support a means for transmitting a message indicating a type of message the second device is to transmit over the set of resources to request the set of the semi-persistently scheduled resources. In some examples, the set of semi-persistently scheduled resources is associated with the set of resources. In some examples, the set of semi-persistently scheduled resources includes a quantity of consecutive instances of semi-persistently scheduled resources, and the SPS component1225may be configured as or otherwise support a means for transmitting a message indicating the quantity of consecutive instances or a duration of time that includes the quantity of consecutive instances. In some examples, the set of semi-persistently scheduled resources includes the set of resources for requesting the set of the semi-persistently scheduled resources. In some examples, the restart component1230may be configured as or otherwise support a means for transmitting a message indicating a periodicity associated with the set of resources, where the message for requesting the set of semi-persistently scheduled resources is received based on the periodicity. FIG.13shows a diagram of a system1300including a device1305that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The device1305may be an example of or include the components of a device1005, a device1105, a UE, a base station as described herein. The device1305may communicate wirelessly with one or more base stations105, UEs115, or any combination thereof. The device1305may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager1320, an I/O controller1310, a transceiver1315, an antenna1325, a memory1330, code1335, and a processor1340. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1345). The I/O controller1310may manage input and output signals for the device1305. The I/O controller1310may also manage peripherals not integrated into the device905. In some cases, the I/O controller1310may represent a physical connection or port to an external peripheral. In some cases, the I/O controller1310may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I/O controller1310may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller1310may be implemented as part of a processor, such as the processor1340. In some cases, a user may interact with the device1305via the I/O controller1310or via hardware components controlled by the I/O controller1310. In some cases, the device1305may include a single antenna1325. However, in some other cases, the device1305may have more than one antenna1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver1315may communicate bi-directionally, via the one or more antennas1325, wired, or wireless links as described herein. For example, the transceiver1315may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1315may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas1325for transmission, and to demodulate packets received from the one or more antennas1325. The transceiver1315, or the transceiver1315and one or more antennas1325, may be an example of a transmitter101515, a transmitter1115, a receiver1010, a receiver1110, or any combination thereof or component thereof, as described herein. The memory1330may include RAM and ROM. The memory1330may store computer-readable, computer-executable code1335including instructions that, when executed by the processor1340, cause the device1305to perform various functions described herein. The code1335may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1335may not be directly executable by the processor1340but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1330may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. The processor1340may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1340may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1340. The processor1340may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1330) to cause the device1305to perform various functions (e.g., functions or tasks supporting resource configuration for requesting semi-persistently scheduled resources). For example, the device1305or a component of the device1305may include a processor1340and memory1330coupled to the processor1340, the processor1340and memory1330configured to perform various functions described herein. The communications manager1320may support wireless communication at a first device in accordance with examples as disclosed herein. For example, the communications manager1320may be configured as or otherwise support a means for configuring semi-persistently scheduled resources for a second device. The communications manager1320may be configured as or otherwise support a means for transmitting an indication of a set of resources available to the second device for requesting a set of the semi-persistently scheduled resources configured for the second device. The communications manager1320may be configured as or otherwise support a means for communicating data over at least a subset of the set of semi-persistently scheduled resources configured for the second device based on transmitting the indication of the set of resources. By including or configuring the communications manager1320in accordance with examples as described herein, the device1305may support techniques for more efficient utilization of communication resources. In some examples, the communications manager1320may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver1315, the one or more antennas1325, or any combination thereof. Although the communications manager1320is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1320may be supported by or performed by the processor1340, the memory1330, the code1335, or any combination thereof. For example, the code1335may include instructions executable by the processor1340to cause the device1305to perform various aspects of resource configuration for requesting semi-persistently scheduled resources as described herein, or the processor1340and the memory1330may be otherwise configured to perform or support such operations. FIG.14shows a flowchart illustrating a method1400that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The operations of the method1400may be implemented by a UE or its components as described herein. For example, the operations of the method1400may be performed by a UE115as described with reference toFIGS.1through9. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware. At1405, the method may include receiving an indication of a configuration that schedules semi-persistently scheduled resources for data transmissions from the first device. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by an SPS component825as described with reference toFIG.8. At1410, the method may include receiving, from a second device, an indication of a set of resources available to the first device for requesting a set of the semi-persistently scheduled resources configured for the first device. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by a restart component830as described with reference toFIG.8. At1415, the method may include transmitting a message over the set of resources to request the set of semi-persistently scheduled resources. The operations of1415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1415may be performed by a request component835as described with reference toFIG.8. FIG.15shows a flowchart illustrating a method1500that supports resource configuration for requesting semi-persistently scheduled resources in accordance with aspects of the present disclosure. The operations of the method1500may be implemented by a UE or a base station or its components as described herein. For example, the operations of the method1500may be performed by a UE115or a base station105as described with reference toFIGS.1through5and10through13. In some examples, the operations of the method1500may be performed by a PLC. In some examples, a base station or a UE may execute a set of instructions to control the functional elements of the base station or the UE to perform the described functions. Additionally or alternatively, the base station or the UE may perform aspects of the described functions using special-purpose hardware. At1505, the method may include configuring semi-persistently scheduled resources for a second device. The operations of1505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1505may be performed by an SPS component1225as described with reference toFIG.12. At1510, the method may include transmitting an indication of a set of resources available to the second device for requesting a set of the semi-persistently scheduled resources configured for the second device. The operations of1510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1510may be performed by a restart component1230as described with reference toFIG.12. At1515, the method may include communicating data over at least a subset of the set of semi-persistently scheduled resources configured for the second device based on transmitting the indication of the set of resources. The operations of1515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1515may be performed by a data component1235as described with reference toFIG.12. The following provides an overview of aspects of the present disclosure: Aspect 1: A method for wireless communication at a first device, comprising: receiving an indication of a configuration that schedules semi-persistently-scheduled resources for data transmissions from the first device; receiving, from a second device, an indication of a set of resources available to the first device for requesting a set of the semi-persistently-scheduled resources configured for the first device; and transmitting a message over the set of resources to request the set of semi-persistently-scheduled resources. Aspect 2: The method of aspect 1, further comprising: receiving, from the second device, a message indicating feedback responsive to the message that requests the set of semi-persistently-scheduled resources; and transmitting data over at least a subset of the set of semi-persistently-scheduled resources based at least in part on receiving the message indicating the feedback. Aspect 3: The method of aspect 1, further comprising: determining that a message indicating feedback responsive to the message that requests the set of semi-persistently-scheduled resources has not been received within a threshold duration of time; and refraining from transmitting data over the set of semi-persistently-scheduled resources based at least in part on the determination. Aspect 4: The method of any of aspects 1 through 2, further comprising: transmitting data in a first subset of the set of semi-persistently-scheduled resources based at least in part on transmitting the message that requests the set of semi-persistently-scheduled resources; and transmitting a second message indicating that a second subset of the set of semi-persistently-scheduled resources will not be used by the first device. Aspect 5: The method of aspect 4, wherein the second message is transmitted over a third subset of the set of semi-persistently-scheduled resources. Aspect 6: The method of any of aspects 1 through 5, wherein the set of semi-persistently-scheduled resources comprises the set of resources for requesting the set of the semi-persistently-scheduled resources. Aspect 7: The method of any of aspects 1 through 6, further comprising: receiving a message indicating a type of message for transmission over the set of resources to request the set of the semi-persistently-scheduled resources. Aspect 8: The method of any of aspects 1 through 7, wherein the set of semi-persistently-scheduled resources is associated with the set of resources. Aspect 9: The method of any of aspects 1 through 8, wherein the set of semi-persistently-scheduled resources comprises a quantity of consecutive instances of semi-persistently-scheduled resources, the method further comprising: receiving a message indicating the quantity of consecutive instances or a duration of time that includes the quantity of consecutive instances. Aspect 10: The method of any of aspects 1 through 9, further comprising: receiving a message indicating a periodicity associated with the set of resources, wherein the message that requests the set of semi-persistently-scheduled resources is transmitted based at least in part on the periodicity. Aspect 11: The method of any of aspects 1 through 10, further comprising: determining that the first device has data for the second device, wherein the message that requests the set of semi-persistently-scheduled resources is transmitted based at least in part on the determination. Aspect 12: A method for wireless communication at a first device, comprising: configuring semi-persistently-scheduled resources for a second device; transmitting an indication of a set of resources available to the second device for requesting a set of the semi-persistently-scheduled resources configured for the second device; and communicating data over at least a subset of the set of semi-persistently-scheduled resources configured for the second device based at least in part on transmitting the indication of the set of resources. Aspect 13: The method of aspect 12, further comprising: receiving a message over the set of resources for requesting the set of semi-persistently-scheduled resources, wherein the data is received from the second device after the message is received. Aspect 14: The method of aspect 13, further comprising: transmitting, to the second device, a message indicating feedback responsive to the message for requesting the set of semi-persistently-scheduled resources, wherein the data is received based at least in part on transmitting the message indicating the feedback. Aspect 15: The method of aspect 12, further comprising: determining that the second device has not transmitted a message over the set of resources for requesting the set of semi-persistently-scheduled resources; and re-allocating the semi-persistently-scheduled resources to a third device. Aspect 16: The method of any of aspects 12 through 14, wherein the data is received from the second device, the method further comprising: receiving from the second device a second message indicating that a second subset of the set of semi-persistently-scheduled resources will not be used by the second device; and re-allocating the second subset of the set of semi-persistently-scheduled resources to a third device based at least in part on receiving the second message. Aspect 17: The method of any of aspects 12 through 14, wherein the data is received from the second device, the method further comprising: determining that a threshold duration of time has elapsed since receipt of the data; and re-allocating a second subset of the set of semi-persistently-scheduled resources to a third device based at least in part on the determination. Aspect 18: The method of any of aspects 12 through 17, further comprising: transmitting a message indicating a type of message the second device is to transmit over the set of resources to request the set of the semi-persistently-scheduled resources. Aspect 19: The method of any of aspects 12 through 18, wherein the set of semi-persistently-scheduled resources is associated with the set of resources. Aspect 20: The method of any of aspects 12 through 19, wherein the set of semi-persistently-scheduled resources comprises a quantity of consecutive instances of semi-persistently-scheduled resources, the method further comprising: transmitting a message indicating the quantity of consecutive instances or a duration of time that includes the quantity of consecutive instances. Aspect 21: The method of any of aspects 12 through 20, wherein the set of semi-persistently-scheduled resources comprises the set of resources for requesting the set of the semi-persistently-scheduled resources. Aspect 22: The method of any of aspects 12 through 21, further comprising: transmitting a message indicating a periodicity associated with the set of resources, wherein the message for requesting the set of semi-persistently-scheduled resources is received based at least in part on the periodicity. Aspect 23: An apparatus for wireless communication at a first device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 11. Aspect 24: An apparatus for wireless communication at a first device, comprising at least one means for performing a method of any of aspects 1 through 11. Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a first device, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 11. Aspect 26: An apparatus for wireless communication at a first device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 12 through 22. Aspect 27: An apparatus for wireless communication at a first device, comprising at least one means for performing a method of any of aspects 12 through 22. Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a first device, the code comprising instructions executable by a processor to perform a method of any of aspects 12 through 22. It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined. Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label. The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples. The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein. | 114,389 |
11943769 | DETAILED DESCRIPTION The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts. The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band. With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and/or uses may come about via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution. Various aspects of the disclosure relate to a scheduling entity (e.g., a UE for sidelink communication, a base station for access communication) generating a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. For example, the message may be a sidelink, medium access control (MAC) control element (MAC-CE), a radio access network (RAN) (e.g., access) MAC-CE, sidelink control information (SCI), downlink control information (DCI), a RAN (e.g., access) radio resource control (RRC) message, or the like. The scheduling entity may transmit the message to a scheduled entity (e.g., another UE) to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. In response to receiving the message, the scheduled entity may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, when the scheduled entity receives the updated TCI-states or the SRs for the group of two or more component carriers, the scheduled entity may be able to identify whether the updates are for the access link, the sidelink, or both. Thus, the system allows for updating TCI-states or SRs on the access link, sidelink, or both. Similarly, various aspects of the disclosure relate to a scheduling entity (e.g., a UE for sidelink communication, a base station for access communication) generating a message indicating one or more pathloss reference signals (PL-RSs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. For example, the message may be a sidelink MAC-CE, a RAN MAC-CE, SCI, DCI, a RAN RRC message, or the like. The scheduling entity may transmit the message to a scheduled entity (e.g., another UE) to update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. In response to receiving the message, the scheduled entity may update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, when the scheduled entity receives the updated PL-RSs for the group of two or more component carriers, the scheduled entity may be able to identify whether the updates are for the access link, the sidelink, or both. Thus, the system allows for updating PL-RSs on the access link, sidelink, or both. The various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards. Referring now toFIG.1, as an illustrative example without limitation, a schematic illustration of a radio access network100is provided. The RAN100may implement any suitable wireless communication technology or technologies to provide radio access. As one example, the RAN100may operate according to 3rdGeneration Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G. As another example, the RAN100may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. The 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure. The geographic region covered by the radio access network100may be divided into a number of cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted over a geographical area from one access point or base station.FIG.1illustrates cells102,104,106, and cell108, each of which may include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector. In a cell that is divided into sectors, the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell. In general, a respective base station (BS) serves each cell. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE. A BS may also be referred to by those skilled in the art as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP), or some other suitable terminology. In some examples, a base station may include two or more TRPs that may be collocated or non-collocated. Each TRP may communicate on the same or different carrier frequency within the same or different frequency band. In examples where the RAN100operates according to both the LTE and 5G NR standards, one of the base stations may be an LTE base station, while another base station may be a 5G NR base station. Various base station arrangements can be utilized. For example, inFIG.1, two base stations110and112are shown in cells102and104; and a third base station114is shown controlling a remote radio head (RRH)116in cell106. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables. In the illustrated example, the cells102,104, and106may be referred to as macrocells, as the base stations110,112, and114support cells having a large size. Further, a base station118is shown in the cell108which may overlap with one or more macrocells. In this example, the cell108may be referred to as a small cell (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc.), as the base station118supports a cell having a relatively small size. Cell sizing can be done according to system design as well as component constraints. It is to be understood that the radio access network100may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell. The base stations110,112,114,118provide wireless access points to a core network for any number of mobile apparatuses. FIG.1further includes an unmanned aerial vehicle (UAV)120, which may be a drone or quadcopter. The UAV120may be configured to function as a base station, or more specifically as a mobile base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station such as the UAV120. In general, base stations may include a backhaul interface for communication with a backhaul portion (not shown) of the network. The backhaul may provide a link between a base station and a core network (not shown), and in some examples, the backhaul may provide interconnection between the respective base stations. The core network may be a part of a wireless communication system and may be independent of the radio access technology used in the radio access network. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network. The RAN100is illustrated supporting wireless communication for multiple mobile apparatuses. A mobile apparatus is commonly referred to as user equipment (UE) in standards and specifications promulgated by the 3rd Generation Partnership Project (3GPP), but may also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be an apparatus that provides a user with access to network services. Within the present document, a “mobile” apparatus need not necessarily have a capability to move, and may be stationary. The term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies. For example, some non-limiting examples of a mobile apparatus include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC), a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA), and a broad array of embedded systems, e.g., corresponding to an “Internet of things” (IoT). A mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, etc. A mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc. A mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid), lighting, water, etc., an industrial automation and enterprise device, a logistics controller, agricultural equipment, etc. Still further, a mobile apparatus may provide for connected medicine or telemedicine support, i.e., health care at a distance. Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data. Within the RAN100, the cells may include UEs that may be in communication with one or more sectors of each cell. For example, UEs122and124may be in communication with base station110; UEs126and128may be in communication with base station112; UEs130and132may be in communication with base station114by way of RRH116; UE134may be in communication with base station118; and UE136may be in communication with mobile base station120. Here, each base station110,112,114,118, and120may be configured to provide an access point to a core network (not shown) for all the UEs in the respective cells. In some examples, the UAV120(e.g., the quadcopter) can be a mobile network node and may be configured to function as a UE. For example, the UAV120may operate within cell102by communicating with base station110. Wireless communication between a RAN100and a UE (e.g., UE122or124) may be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station110) to one or more UEs (e.g., UE122and124) may be referred to as downlink (DL) transmission. In accordance with certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station110). Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE122) to a base station (e.g., base station110) may be referred to as uplink (UL) transmissions. In accordance with further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE122). For example, DL transmissions may include unicast or broadcast transmissions of control information and/or traffic information (e.g., user data traffic) from a base station (e.g., base station110) to one or more UEs (e.g., UEs122and124), while UL transmissions may include transmissions of control information and/or traffic information originating at a UE (e.g., UE122). In addition, the uplink and/or downlink control information and/or traffic information may be time-divided into frames, subframes, slots, and/or symbols. As used herein, a symbol may refer to a unit of time that, in an orthogonal frequency division multiplexed (OFDM) waveform, carries one resource element (RE) per sub-carrier. A slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame. Within the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmissions, with each frame consisting of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and various time divisions of the waveform may have any suitable duration. In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs or scheduled entities utilize resources allocated by the scheduling entity. Base stations are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, two or more UEs (e.g., UEs138,140, and142) may communicate with each other using sidelink signals137without relaying that communication through a base station. In some examples, the UEs138,140, and142may each function as a scheduling entity or transmitting sidelink device and/or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals137therebetween without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs126and128) within the coverage area of a base station (e.g., base station112) may also communicate sidelink signals127over a direct link (sidelink) without conveying that communication through the base station112. In this example, the base station112may allocate resources to the UEs126and128for the sidelink communication. In either case, such sidelink signaling127and137may be implemented in a peer-to-peer (P2P) network, a device-to-device (D2D) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, a mesh network, or other suitable direct link network. In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communication to/from the base station112via D2D links (e.g., sidelinks127or137). For example, one or more UEs (e.g., UE128) within the coverage area of the base station112may operate as relaying UEs to extend the coverage of the base station112, improve the transmission reliability to one or more UEs (e.g., UE126), and/or to allow the base station to recover from a failed UE link due to, for example, blockage or fading. Two primary technologies that may be used by V2X networks include dedicated short range communication (DSRC) based on IEEE 802.11p standards and cellular V2X based on LTE and/or 5G (New Radio) standards. Various aspects of the present disclosure may relate to New Radio (NR) cellular V2X networks, referred to herein as V2X networks, for simplicity. However, it should be understood that the concepts disclosed herein may not be limited to a particular V2X standard or may be directed to sidelink networks other than V2X networks. In order for transmissions over the air interface to obtain a low block error rate (BLER) while still achieving very high data rates, channel coding may be used. That is, wireless communication may generally utilize a suitable error correcting block code. In a typical block code, an information message or sequence is split up into code blocks (CBs), and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. Exploitation of this redundancy in the encoded information message can improve the reliability of the message, enabling correction for any bit errors that may occur due to the noise. Data coding may be implemented in multiple manners. In early 5G NR specifications, user data is coded using quasi-cyclic low-density parity check (LDPC) with two different base graphs: one base graph is used for large code blocks and/or high code rates, while the other base graph is used otherwise. Control information and the physical broadcast channel (PBCH) are coded using Polar coding, based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching. Aspects of the present disclosure may be implemented utilizing any suitable channel code. Various implementations of base stations and UEs may include suitable hardware and capabilities (e.g., an encoder, a decoder, and/or a CODEC) to utilize one or more of these channel codes for wireless communication. In the RAN100, the ability for a UE to communicate while moving, independent of their location, is referred to as mobility. The various physical channels between the UE and the RAN are generally set up, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF can manage, in whole or in part, the security context for both the control plane and the user plane functionality. In some examples, a RAN100may enable mobility and handovers (i.e., the transfer of a UE's connection from one radio channel to another). For example, during a call with a scheduling entity, or at any other time, a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if signal quality from a neighboring cell exceeds that from the serving cell for a given amount of time, the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell. For example, UE124may move from the geographic area corresponding to its serving cell102to the geographic area corresponding to a neighbor cell106. When the signal strength or quality from the neighbor cell106exceeds that of its serving cell102for a given amount of time, the UE124may transmit a reporting message to its serving base station110indicating this condition. In response, the UE124may receive a handover command, and the UE may undergo a handover to the cell106. In various implementations, the air interface in the RAN100may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides for exclusive use of a portion of the spectrum, generally by virtue of a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides for shared use of a portion of the spectrum without need for a government-granted license. While compliance with some technical rules is generally still required to access unlicensed spectrum, generally, any operator or device may gain access. Shared spectrum may fall between licensed and unlicensed spectrum, wherein technical rules or limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs. For example, the holder of a license for a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with suitable licensee-determined conditions to gain access. The air interface in the RAN100may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices. For example, 5G NR specifications provide multiple access for UL or reverse link transmissions from UEs122and124to base station110, and for multiplexing DL or forward link transmissions from the base station110to UEs122and124utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other suitable multiple access schemes. Further, multiplexing DL transmissions from the base station110to UEs122and124may be provided utilizing time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes. Further, the air interface in the RAN100may utilize one or more duplexing algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions. Full-duplex means both endpoints can simultaneously communicate with one another. Half-duplex means only one endpoint can send information to the other at a time. Half-duplex emulation is frequently implemented for wireless links utilizing time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g., several times per slot. In a wireless link, a full-duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies. Full-duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or spatial division duplex (SDD). In FDD, transmissions in different directions may operate at different carrier frequencies (e.g., within paired spectrum). In SDD, transmissions in different directions on a given channel are separated from one another using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full duplex (SBFD), also known as flexible duplex. FIG.2illustrates an example of a wireless communication network200configured to support D2D or sidelink communication. In some examples, sidelink communication may include V2X communication. V2X communication involves the wireless exchange of information directly between not only vehicles (e.g., vehicles202and204) themselves, but also directly between vehicles202/204and infrastructure (e.g., roadside units (RSUs)206), such as streetlights, buildings, traffic cameras, tollbooths or other stationary objects, vehicles202/204and pedestrians208, and vehicles202/204and wireless communication networks (e.g., base station210). In some examples, V2X communication may be implemented in accordance with the New Radio (NR) cellular V2X standard defined by 3GPP, Release 16, or other suitable standard. V2X communication enables vehicles202and204to obtain information related to the weather, nearby accidents, road conditions, activities of nearby vehicles and pedestrians, objects nearby the vehicle, and other pertinent information that may be utilized to improve the vehicle driving experience and increase vehicle safety. For example, such V2X data may enable autonomous driving and improve road safety and traffic efficiency. For example, the exchanged V2X data may be utilized by a V2X connected vehicle202and204to provide in-vehicle collision warnings, road hazard warnings, approaching emergency vehicle warnings, pre-/post-crash warnings and information, emergency brake warnings, traffic jam ahead warnings, lane change warnings, intelligent navigation services, and other similar information. In addition, V2X data received by a V2X connected mobile device of a pedestrian/cyclist208may be utilized to trigger a warning sound, vibration, flashing light, etc., in case of imminent danger. The sidelink communication between vehicle-UEs (V-UEs)202and204or between a V-UE202or204and either an RSU206or a pedestrian-UE (P-UE)208may occur over a sidelink212utilizing a proximity service (ProSe) PC5 interface. In various aspects of the disclosure, the PC5 interface may further be utilized to support D2D sidelink212communication in other proximity use cases (e.g., other than V2X). Examples of other proximity use cases may include smart wearables, public safety, or commercial (e.g., entertainment, education, office, medical, and/or interactive) based proximity services. In the example shown inFIG.2, ProSe communication may further occur between UEs214and216. ProSe communication may support different operational scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to a scenario in which UEs (e.g., UEs214and216) are outside of the coverage area of a base station (e.g., base station210), but each are still configured for ProSe communication. Partial coverage refers to a scenario in which some of the UEs (e.g., V-UE204) are outside of the coverage area of the base station210, while other UEs (e.g., V-UE202and P-UE208) are in communication with the base station210. In-coverage refers to a scenario in which UEs (e.g., V-UE202and P-UE208) are in communication with the base station210(e.g., gNB) via a Uu (e.g., cellular interface) connection to receive ProSe service authorization and provisioning information to support ProSe operations. To facilitate D2D sidelink communication between, for example, UEs214and216over the sidelink212, the UEs214and216may transmit discovery signals therebetween. In some examples, each discovery signal may include a synchronization signal, such as a primary synchronization signal (PSS) and/or a secondary synchronization signal (SSS) that facilitates device discovery and enables synchronization of communication on the sidelink212. For example, the discovery signal may be utilized by the UE216to measure the signal strength and channel status of a potential sidelink (e.g., sidelink212) with another UE (e.g., UE214). The UE216may utilize the measurement results to select a UE (e.g., UE214) for sidelink communication or relay communication. In 5G NR sidelink, sidelink communication may utilize transmission or reception resource pools. For example, the minimum resource allocation unit in frequency may be a sub-channel (e.g., which may include, for example, 10, 15, 20, 25, 50, 75, or 100 consecutive resource blocks) and the minimum resource allocation unit in time may be one slot. The number of sub-channels in a resource pool may include between one and twenty-seven sub-channels. A radio resource control (RRC) configuration of the resource pools may be either pre-configured (e.g., a factory setting on the UE determined, for example, by sidelink standards or specifications) or configured by a base station (e.g., base station210). In addition, there may be two main resource allocation modes of operation for sidelink (e.g., PC5) communications. In a first mode, Mode 1, a base station (e.g., gNB)210may allocate resources to sidelink devices (e.g., V2X devices or other sidelink devices) for sidelink communication between the sidelink devices in various manners. For example, the base station210may allocate sidelink resources dynamically (e.g., a dynamic grant) to sidelink devices, in response to requests for sidelink resources from the sidelink devices. For example, the base station210may schedule the sidelink communication via DCI 3_0. In some examples, the base station210may schedule the PSCCH/PSSCH within uplink resources indicated in DCI 3_0. The base station210may further activate preconfigured sidelink grants (e.g., configured grants) for sidelink communication among the sidelink devices. In some examples, the base station210may activate a configured grant (CG) via RRC signaling. In Mode 1, sidelink feedback may be reported back to the base station210by a transmitting sidelink device. In a second mode, Mode 2, the sidelink devices may autonomously select sidelink resources for sidelink communication therebetween. In some examples, a transmitting sidelink device may perform resource/channel sensing to select resources (e.g., sub-channels) on the sidelink channel that are unoccupied. Signaling on the sidelink is the same between the two modes. Therefore, from a receiver's point of view, there is no difference between the modes. In some examples, sidelink (e.g., PC5) communication may be scheduled by use of sidelink control information (SCI). SCI may include two SCI stages. Stage 1 sidelink control information (first stage SCI) may be referred to herein as SCI-1. Stage 2 sidelink control information (second stage SCI) may be referred to herein as SCI-2. SCI-1 may be transmitted on a physical sidelink control channel (PSCCH). SCI-1 may include information for resource allocation of a sidelink resource and for decoding of the second stage of sidelink control information (i.e., SCI-2). SCI-1 may further identify a priority level (e.g., Quality of Service (QoS)) of a PSSCH. For example, ultra-reliable-low-latency communication (URLLC) traffic may have a higher priority than text message traffic (e.g., short message service (SMS) traffic). SCI-1 may also include a physical sidelink shared channel (PSSCH) resource assignment and a resource reservation period (if enabled). Additionally, SCI-1 may include a PSSCH demodulation reference signal (DMRS) pattern (if more than one pattern is configured). The DMRS may be used by a receiver for radio channel estimation for demodulation of the associated physical channel. As indicated, SCI-1 may also include information about the SCI-2, for example, SCI-1 may disclose the format of the SCI-2. Here, the format indicates the resource size of SCI-2 (e.g., a number of REs that are allotted for SCI-2), a number of a PSSCH DMRS port(s), and a modulation and coding scheme (MCS) index. In some examples, SCI-1 may use two bits to indicate the SCI-2 format. Thus, in this example, four different SCI-2 formats may be supported. SCI-1 may include other information that is useful for establishing and decoding a PSSCH resource. SCI-2 may also be transmitted on the PSCCH or within the PSSCH and may contain information for decoding the PSSCH. According to some aspects, SCI-2 includes a 16-bit layer 1 (L1) destination identifier (ID), an 8-bit L1 source ID, a hybrid automatic repeat request (HARQ) process ID, a new data indicator (NDI), and a redundancy version (RV). For unicast communications, SCI-2 may further include a CSI report trigger. For groupcast communications, SCI-2 may further include a zone identifier and a maximum communication range for NACK. SCI-2 may include other information that is useful for establishing and decoding a PSSCH resource. FIG.3is a diagram illustrating an example of a wireless communication system300for facilitating both cellular and sidelink communication. The wireless communication system300includes a plurality of wireless communication devices302a,302b, and302cand a base station (e.g., eNB or gNB)306. In some examples, the wireless communication devices302a,302b, and302cmay be UEs capable of implementing D2D or V2X devices within a V2X network. The wireless communication devices302aand302bmay communicate over a first PC5 interface304a, while wireless communication devices302aand302cmay communicate over a second PC5 interface304b. Wireless communication devices302a,302b, and302cmay further communicate with the base station306over respective Uu interfaces308a,308b, and308b. The sidelink communication over the PC5 interfaces304aand304bmay be carried, for example, in a licensed frequency domain using radio resources operating according to a 5G NR or NR sidelink (SL) specification and/or in an unlicensed frequency domain, using radio resources operating according to 5G new radio-unlicensed (NR-U) specifications. In some examples, a common carrier may be shared between the PC5 interfaces304aand304band Uu interfaces308a-308c, such that resources on the common carrier may be allocated for both sidelink communication between wireless communication devices302a-302cand cellular communication (e.g., uplink and downlink communication) between the wireless communication devices302a-302cand the base station306. For example, the wireless communication system300may be configured to support a V2X network in which resources for both sidelink and cellular communication are scheduled by the base station306. In other examples, the wireless communication devices302a-302cmay autonomously select sidelink resources (e.g., from one or more frequency bands or sub-bands designated for sidelink communication) for communication therebetween. In this example, the wireless communication devices302a-302cmay function as both scheduling entities and scheduled entities scheduling sidelink resources for communication with each other. In some aspects of the disclosure, the scheduling entity and/or scheduled entity may be configured for beamforming and/or multiple-input multiple-output (MIMO) technology.FIG.4illustrates an example of a wireless communication system400supporting beamforming and/or MIMO. In a MIMO system, a transmitter402includes multiple transmit antennas404(e.g., N transmit antennas) and a receiver406includes multiple receive antennas408(e.g., M receive antennas). Thus, there are N×M signal paths410from the transmit antennas404to the receive antennas408. Each of the transmitter402and the receiver406may be implemented, for example, within a scheduling entity, a scheduled entity, or any other suitable device. In some examples, the transmitter and receiver are each wireless communication devices (e.g., UEs or V2X devices) communicating over a sidelink channel. The use of such multiple antenna technology enables the wireless communication system to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data, also referred to as layers, simultaneously on the same time-frequency resource. The data streams may be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data streams with different weighting and phase shifting) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE(s) with different spatial signatures, which enables each of the UE(s) to recover the one or more data streams destined for that UE. On the uplink, each UE transmits a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream. The number of data streams or layers corresponds to the rank of the transmission. In general, the rank of the MIMO system400is limited by the number of transmit or receive antennas404or408, whichever is lower. In addition, the channel conditions at the UE, as well as other considerations, such as the available resources at the base station, may also affect the transmission rank. For example, the rank (and therefore, the number of data streams) assigned to a particular UE on the downlink may be determined based on the rank indicator (RI) transmitted from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and a measured signal-to-interference-and-noise ratio (SINR) on each of the receive antennas. The RI may indicate, for example, the number of layers that may be supported under the current channel conditions. The base station may use the RI, along with resource information (e.g., the available resources and amount of data to be scheduled for the UE), to assign a transmission rank to the UE. In one example, as shown inFIG.4, a rank-2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will transmit one data stream from each transmit antenna404. Each data stream reaches each receive antenna408along a different signal path410. The receiver406may then reconstruct the data streams using the received signals from each receive antenna408. Beamforming is a signal processing technique that may be used at the transmitter402or receiver406to shape or steer an antenna beam (e.g., a transmit beam or receive beam) along a spatial path between the transmitter402and the receiver406. Beamforming may be achieved by combining the signals communicated via antennas404or408(e.g., antenna elements of an antenna array module) such that some of the signals experience constructive interference while others experience destructive interference. To create the desired constructive/destructive interference, the transmitter402or receiver406may apply amplitude and/or phase offsets to signals transmitted or received from each of the antennas404or408associated with the transmitter402or receiver406. In 5G New Radio (NR) systems, particularly for FR2 or higher (millimeter wave) systems, beamformed signals may be utilized for most downlink channels, including the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH). In addition, broadcast control information, such as the synchronization signal block (SSB), slot format indicator (SFI), and paging information, may be transmitted in a beam-sweeping manner to enable all scheduled entities (UEs) in the coverage area of a transmission and reception point (TRP) (e.g., a gNB) to receive the broadcast control information. In addition, for UEs configured with beamforming antenna arrays, beamformed signals may also be utilized for uplink channels, including the physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH). In addition, beamformed signals may further be utilized in D2D systems, such as NR SL or V2X, utilizing FR2. FIG.5is a diagram illustrating communication between a radio access network (RAN) node502, a first wireless communication device504, and a second wireless communication device506using beamformed sidelink signals according to some aspects. Each of the RAN node502(e.g., a base station, such as a gNB) and the first wireless communication device504may be any of the receiving devices or transmitting devices illustrated in any ofFIGS.1-4. Each of the first wireless communication device504and the second wireless communication device506may be any of the UEs, V2X devices, transmitting devices or receiving devices illustrated in any ofFIGS.1-4. In the example shown inFIG.5, the radio access network (RAN) node502and the first wireless communication device504may be configured to communicate access (e.g., Uu) signals on one or more of a plurality of beams508a,508b,508c,508d,508e,508f,508g, and508h. Although the beams508a,508b,508c,508d,508e,508f,508g, and508hare illustrated inFIG.5as being generated on the RAN node502, it should be understood that the same concepts described herein apply to beams generated on the first wireless communication device504. For example, each of the RAN node502and the first wireless communication device504may select one or more beams to transmit access signals to the other communication device. In some examples, due to channel reciprocity, the selected beam(s) on each of the RAN node502and the first wireless communication device504may be used for both transmission and reception of access signals. It should be noted that while some beams are illustrated as adjacent to one another, such an arrangement may be different in different aspects. In some examples, the RAN node502and the first wireless communication device504may generate more or less beams distributed in different directions. The number of beams on which a particular RAN node502or the first wireless communication device504may simultaneously communicate may be defined based on NR standards and specifications and capabilities of the RAN node502and the first wireless communication device504. For example, the number of beams may be determined based on a number of antenna panels configured on the RAN node502or the first wireless communication device504. Each beam may be utilized, for example, to transmit a respective layer for MIMO communication. In some examples, to select one or more beams for communication on a access link between the RAN node502and the first wireless communication device504, the RAN node502may transmit an access reference signal, such as an access synchronization signal block (SSB) or an access channel state information (CSI) reference signal (RS), on each of the plurality of beams508a,508b,508c,508d,508e,508f,508g, and508hin a beam-sweeping manner towards the first wireless communication device504. The first wireless communication device504searches for and identifies the beams based on the beam reference signals. The first wireless communication device504then performs beam measurements (e.g., reference signal received power (RSRP), signal-to-interference-plus-noise ratio (SINR), reference signal received quality (RSRQ), etc.) on the beam reference signals to determine the respective beam quality of each of the beams. The first wireless communication device504may then transmit a beam measurement report to the RAN node502indicating the beam quality of one or more of the measured beams. The RAN node502may then select the particular beam(s) for communication between the RAN node502and the first wireless communication device504on the access link based on the beam measurement report. The RAN node502may then signal the selected beam(s) via, for example, a radio resource control (RRC) message or via a medium access control (MAC) control element (CE). Each selected beam on one of the communication devices (e.g., the RAN node502or the first wireless communication device504) may form a beam pair link (BPL) with a corresponding selected beam on the other communication device. Thus, each BPL includes corresponding transmit and receive beams on the RAN node502and the first wireless communication device504. For example, a BPL may include a first transmit/receive beam on the RAN node502and a second transmit/receive beam on the first wireless communication device504. To increase the data rate, multiple BPLs can be used to facilitate spatial multiplexing of multiple data streams. In some examples, the different BPLs can include beams from different antenna panels. Also, in the example shown inFIG.5, the first wireless communication device504and the second wireless communication device506may be configured to communicate sidelink signals on one or more of a plurality of beams510a,510b,510c,510d,510e,510f,510g, and510h. Although the beams510a,510b,510c,510d,510e,510f,510g, and510hare illustrated inFIG.5as being generated on the first wireless communication device504, it should be understood that the same concepts described herein apply to beams generated on the second wireless communication device506. For example, each of the first wireless communication device504and the second wireless communication device506may select one or more beams to transmit sidelink signals to the other wireless communication device. In some examples, due to channel reciprocity, the selected beam(s) on each of the first wireless communication device504and the second wireless communication device506may be used for both transmission and reception of sidelink signals. It should be noted that while some beams are illustrated as adjacent to one another, such an arrangement may be different in different aspects. In some examples, the first wireless communication device504and the second wireless communication device506may generate more or less beams distributed in different directions. The number of beams on which a particular first wireless communication device504or the second wireless communication device506may simultaneously communicate may be defined based on NR SL standards and specifications and capabilities of the first wireless communication device504and the second wireless communication device506. For example, the number of beams may be determined based on a number of antenna panels configured on the first wireless communication device504or the second wireless communication device506. Each beam may be utilized, for example, to transmit a respective layer for MIMO communication. In some examples, to select one or more beams for communication on a sidelink between the first wireless communication device504and the second wireless communication device506, the first wireless communication device504may transmit a sidelink reference signal, such as a sidelink synchronization signal block (SSB) or sidelink channel state information (CSI) reference signal (RS), on each of the plurality of beams510a,510b,510c,510d,510e,510f,510g, and510hin a beam-sweeping manner towards the second wireless communication device506. The second wireless communication device506searches for and identifies the beams based on the beam reference signals. The second wireless communication device506then performs beam measurements (e.g., reference signal received power (RSRP), signal-to-interference-plus-noise ratio (SINR), reference signal received quality (RSRQ), etc.) on the beam reference signals to determine the respective beam quality of each of the beams. The second wireless communication device506may then transmit a beam measurement report to the first wireless communication device504indicating the beam quality of one or more of the measured beams. The first wireless communication device504may then select the particular beam(s) for communication between the first wireless communication device504and the second wireless communication device506on the sidelink based on the beam measurement report. For example, the first wireless communication device504may forward the beam measurement report to a base station for selection of the beam(s). The base station may then signal the selected beam(s) via, for example, a radio resource control (RRC) message or via a medium access control (MAC) control element (CE). Each selected beam on one of the wireless communication devices (e.g., the first wireless communication device504or the second wireless communication device506) may form a beam pair link (BPL) with a corresponding selected beam on the other wireless communication device. Thus, each BPL includes corresponding transmit and receive beams on the first wireless communication device504and the second wireless communication device506. For example, a BPL may include a first transmit/receive beam on the first wireless communication device504and a second transmit/receive beam on the second wireless communication device506. To increase the data rate, multiple BPLs can be used to facilitate spatial multiplexing of multiple data streams. In some examples, the different BPLs can include beams from different antenna panels. Various aspects of the present disclosure will be described with reference to an OFDM waveform, schematically illustrated inFIG.6. It should be understood by those of ordinary skill in the art that the various aspects of the present disclosure may be applied to an SC-FDMA waveform in substantially the same way as described herein below. That is, while some examples of the present disclosure may focus on an OFDM link for clarity, it should be understood that the same principles may be applied as well to SC-FDMA waveforms. Referring now toFIG.6, an expanded view of an exemplary subframe602is illustrated, showing an OFDM resource grid. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application may vary from the example described here, depending on any number of factors. Here, time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers of the carrier. The resource grid604may be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input-multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple number of resource grids604may be available for communication. The resource grid604is divided into multiple resource elements (REs)606. An RE, which is 1 subcarrier×1 symbol, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB)608, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as the RB608entirely corresponds to a single direction of communication (either transmission or reception for a given device). Scheduling of UEs or sidelink devices (hereinafter collectively referred to as UEs) for downlink, uplink, or sidelink transmissions typically involves scheduling one or more resource elements606within one or more sub-bands. Thus, a UE generally utilizes only a subset of the resource grid604. In some examples, an RB may be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme chosen for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a base station (e.g., gNB, eNB, etc.) or may be self-scheduled by a UE/sidelink device implementing D2D sidelink communication. In this illustration, the RB608is shown as occupying less than the entire bandwidth of the subframe602, with some subcarriers illustrated above and below the RB608. In a given implementation, the subframe602may have a bandwidth corresponding to any number of one or more RBs608. Further, in this illustration, the RB608is shown as occupying less than the entire duration of the subframe602, although this is merely one possible example. Each 1 ms subframe602may consist of one or multiple adjacent slots. In the example shown inFIG.6, one subframe602includes four slots610, as an illustrative example. In some examples, a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini slots, sometimes referred to as shortened transmission time intervals (TTIs), having a shorter duration (e.g., one to three OFDM symbols). These mini-slots or shortened transmission time intervals (TTIs) may in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs. Any number of resource blocks may be utilized within a subframe or slot. An expanded view of one of the slots610illustrates the slot610including a control region612and a data region614. In general, the control region612may carry control channels, and the data region614may carry data channels. Of course, a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. The simple structure illustrated inFIG.4is merely exemplary in nature, and different slot structures may be utilized, and may include one or more of each of the control region(s) and data region(s). Although not illustrated inFIG.6, the various REs606within a RB608may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs606within the RB608may also carry pilots or reference signals. These pilots or reference signals may provide for a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channels within the RB608. In some examples, the slot610may be utilized for broadcast or unicast communication. For example, a broadcast, multicast, or groupcast communication may refer to a point-to-multipoint transmission by one device (e.g., a base station, UE, or other similar device) to other devices. Here, a broadcast communication is delivered to all devices, whereas a multicast communication is delivered to multiple intended recipient devices. A unicast communication may refer to a point-to-point transmission by a one device to a single other device. In an example of cellular communication over a cellular carrier via a Uu interface, for a DL transmission, the scheduling entity (e.g., a base station) may allocate one or more REs606(e.g., within the control region612) to carry DL control information including one or more DL control channels, such as a physical downlink control channel (PDCCH), to one or more scheduled entities (e.g., UEs). The PDCCH carries downlink control information (DCI) including but not limited to power control commands (e.g., one or more open loop power control parameters and/or one or more closed loop power control parameters), scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions. The PDCCH may further carry HARQ feedback transmissions such as an acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission confirmed, an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc. The base station may further allocate one or more REs606(e.g., in the control region612or the data region614) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase-tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); a primary synchronization signal (PSS); and a secondary synchronization signal (SSS). A UE may utilize the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell. The synchronization signals PSS and SSS, and in some examples, the PBCH and a PBCH DMRS, may be transmitted in a synchronization signal block (SSB). The PBCH may further include a master information block (MIB) that includes various system information, along with parameters for decoding a system information block (SIB). The SIB may be, for example, a SystemInformationType 1 (SIB1) that may include various additional system information. Examples of system information transmitted in the MIB may include, but are not limited to, a subcarrier spacing, system frame number, a configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESETO), and a search space for SIB1. Examples of additional system information transmitted in the SIB1 may include, but are not limited to, a random access search space, downlink configuration information, and uplink configuration information. The MIB and SIB1 together provide the minimum system information (SI) for initial access. In an UL transmission, the scheduled entity (e.g., UE) may utilize one or more REs606to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH), to the scheduling entity. UCI may include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. In some examples, the UCI may include a scheduling request, i.e., request for the scheduling entity to schedule uplink transmissions. Here, in response to the scheduling request transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI) that may schedule resources for uplink packet transmissions. UCI may also include HARQ feedback, channel state feedback (CSF), such as a CSI report, or any other suitable UCI. In addition to control information, one or more REs606(e.g., within the data region614) may be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH); or for an UL transmission, a physical uplink shared channel (PUSCH). In some examples, one or more REs606within the data region614may be configured to carry other signals, such as one or more SIBs and DMRSs. In an example of sidelink communication over a sidelink carrier via a PC5 interface, the control region612of the slot610may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., V2X or other sidelink device) towards a set of one or more other receiving sidelink devices. The data region614of the slot610may include a physical sidelink shared channel (PSSCH) including sidelink data traffic transmitted by the initiating (transmitting) sidelink device within resources reserved over the sidelink carrier by the transmitting sidelink device via the SCI. Other information may further be transmitted over various REs606within slot610. For example, HARQ feedback information may be transmitted in a physical sidelink feedback channel (PSFCH) within the slot610from the receiving sidelink device to the transmitting sidelink device. In addition, one or more reference signals, such as a sidelink SSB and/or a sidelink CSI-RS, may be transmitted within the slot610. These physical channels described above are generally multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TB). The transport block size (TBS), which may correspond to a number of bits of information, may be a controlled parameter, based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission. The channels or carriers illustrated inFIG.6are not necessarily all of the channels or carriers that may be utilized between devices, and those of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels. FIG.7is a conceptual diagram illustrating an example of a multi-component carrier transmission environment700according to some aspects. The multi-component carrier transmission environment700may include a base station702(e.g., a RAN node) and a UE704. The base station702or scheduling entity may be similar to those illustrated in any ofFIGS.1-5. The UE704or scheduled entity may be similar to those illustrated in any ofFIGS.1-5. The multi-component carrier transmission environment700may also include a first component carrier706, a second component carrier708, a third component carrier710, a fourth component carrier712, and a fifth component carrier714. Each of the first component carrier706, the second component carrier708, the third component carrier710, the fourth component carrier712, and the fifth component carrier714may be co-located with each other. The coverage of each of the first component carrier706, the second component carrier708, the third component carrier710, the fourth component carrier712, and the fifth component carrier714may differ since component carriers in different frequency bands may experience different path loss. In some aspects, the first component carrier706may be a primary component carrier (e.g. an anchor component carrier) and each of the second component carrier708, the third component carrier710, the fourth component carrier712, and the fifth component carrier714may be secondary component carriers. When carrier aggregation is configured, one or more of the secondary component carriers may be activated or added to the primary component carrier to form the serving component carriers serving the UE704. In some examples, the base station702may add or remove one or more of the secondary component carriers to improve reliability of the connection to the UE704and/or increase the data rate. The primary component carrier may be changed upon a handover to another base station or another primary component carrier. In some examples, the primary component carrier may be a low band component carrier, and the secondary component carriers may be high band component carriers. A low band (LB) component carrier has a frequency band lower than that of the high band component carrier. For example, the high band component carrier may use a mmWave component carrier, and the low band component carrier may use a component carrier in a band (e.g., sub-6 GHz band) lower than mmWave. In general, a mmWave component carrier can provide greater bandwidth than a low band component carrier. In some examples, the primary component carrier or the primary component carrier and one or more secondary component carriers may form a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with one or more TCI-states, one or more SRs, or one or more PL-RSs. In some examples, the UE704may transmit an uplink signal (e.g., a PUCCH or PUSCH) on a component carrier using an uplink transmit power that may be controlled based on a path loss between the UE704and the base station702. For example, the UE704may calculate the uplink transmit power for an uplink transmission based on the estimated or measured path loss, a transmit power control (TPC) command received from the base station702, and other suitable parameters (e.g., the transport block size (TBS)). The path loss can be measured or estimated, for example, by measuring the received power of a path loss reference signal (PL-RS). Examples of PL-RS include, but are not limited to, SSBs and CSI-RSs. In 5G NR networks, the UE704may maintain up to four PL-RSs per serving cell. The maintained PL-RSs may include PL-RSs configured by the serving cell via radio resource control (RRC) signaling or MAC-CE activation, and default PL-RSs on the UE704. In some aspects, carrier aggregation may be configured for the sidelink. As similarly described with respect to the access link, with carrier aggregation for the sidelink, one or more of the secondary component carriers may be activated or added to the primary component carrier to form the serving component carriers serving a scheduled entity (e.g., UE). In some examples, the scheduling entity (e.g., UE) may add or remove one or more of the secondary component carriers to improve reliability of the connection to another UE and/or increase the data rate. In some examples, the UE704may utilize one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) for multi-component carrier communication. The UE704may receive a message, from the base station702, indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) and including an index identifying a group of two or more component carriers of a plurality of access component carriers associated with the one or more TCI-states or the one or more SRs. The index may also identify a group of two or more component carriers of a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. The UE704may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers associated with the access link, the sidelink, or both for the multi-component carrier communication based on the message. In some examples, the UE704may utilize one or more pathloss reference signal (PL-RSs) for multi-component carrier communication. The UE704may receive a message, from the base station702, indicating one or more PL-RSs and including an index identifying a group of two or more component carriers of a plurality of access component carriers associated with the one or more PL-RSs. The index may also identify a group of two or more component carriers of a plurality of sidelink component carriers associated with the one or more PL-RSs. The UE704may update the one or more PL-RSs for the group of two or more component carriers associated with the access link, the sidelink, or both for the multi-component carrier communication based on the message. FIG.8is a signaling diagram illustrating an example of beam indication according to some aspects. In the example shown inFIG.8, a RAN node802is in wireless communication with a first wireless communication device (UE1)804over an access link. The first wireless communication device (UE1)804may be in wireless communication with a second wireless communication device (UE2)806over a sidelink. The RAN node802may correspond to any of the entities, gNodeBs, UEs, V2X devices, or D2D devices shown inFIGS.1-5and7. The UE1804and/or the UE2806may correspond to any of the entities, gNodeBs, UEs, V2X devices, or D2D devices shown inFIGS.1-5and7. At708, the RAN node802, which may be a transmitting wireless communication device, generates a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication on the access link or the sidelink. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). The TCI-states or SRs may indicate the spatial property (e.g., beam direction and/or beam width) of a transmit beams to be utilized by a wireless communication device. For example, for access communication, the TCI-state may include quasi co-location (QCL) information (e.g., QCL-Type D) referencing an access SSB beam or access CSI-RS transmit beam on the transmitting wireless communication device. Similarly, the SRI may indicate a spatial relation between an access SSB or access CSI-RS beam and an uplink transmit beam utilized by the UE (e.g., UE1804) for uplink transmissions. In this example, a wireless communication device may identify the selected uplink transmit beam having a spatial direction in the same direction as the indicated access SSB or CSI-RS beam. Similarly, for sidelink communication, the TCI states or SRs may indicate the sidelink transmit beams to be utilized for communication on the sidelink between UEs (e.g., between UE1804and UE2806). Subsequently, the receive beams may be determined by the BPL. The message may include one of a TCI-state activation and deactivation message or an SRI activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of TCI-states including the one or more TCI states or each of a plurality of SRs including the one or more SRs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first TCI-states or first SRs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first TCI-states or the first SRs. Additionally, or alternatively, the message may include a second entry indicating second TCI-states or second SRs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second TCI-states or the second SRs. At810, the RAN node802transmits the message to a user equipment (UE) to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, the RAN node802may transmit the message to the UE1804to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. It should be understood that the transmitting device can be either a RAN node, as shown inFIG.8, or a UE. Thus, for the sidelink, a UE may receive the message from a RAN node, and subsequently transmit the information provided in the message to another UE on the sidelink using SCI. In other examples, a UE may autonomously transmit a message via SCI to update one or more TCI-states or one or more SRs for a group of two or more sidelink component carriers to another UE on the sidelink. At812, the UE1804updates the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, in response to receiving the message from the RAN node802, the UE1804may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. In some aspects, when a reference signal source of a TCI-state of the one or more TCI-states or an SRI of the one or more SRs in the message is associated with access communication, the UE1804may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers of the plurality of access carriers. In some aspects, when a reference signal source of a TCI-state of the one or more TCI-states or an SRI of the one or more SRs in the message is associated with sidelink communication, the UE1804may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the plurality of sidelink carriers. At814, the UE1804communicates using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE1804may communicate with the RAN node802using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. In some examples, the UE1804may communicate with the RAN node802on one or more beams on each of the aggregated access component carriers, as indicated in the message. For example, the message may indicate a downlink receive beam or a transmit uplink beam to use on one or more of the aggregated access component carriers. At816, the UE1804communicates using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the sidelink multi-component carrier communication. For example, the UE1804may communicate with the UE2806using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the sidelink multi-component carrier communication. In some examples, the UE1804may communicate with the UE2806on one or more beams on each of the aggregated sidelink component carriers, as indicated in the message. For example, the message may indicate a transmit sidelink beam to use by the UE1804or the UE2806on one or more of the aggregated sidelink component carriers. FIG.9is a signaling diagram illustrating an example of path loss reference signal indication for multi-component carrier communication according to some aspects. In the example shown inFIG.9, a RAN node902is in wireless communication with a first wireless communication device (UE1)904over an access link. The first wireless communication device (UE1)904may be in wireless communication with a second wireless communication device (UE2)906over a sidelink. Each of the RAN node902, the UE1904, and the UE2906may correspond to any of the entities, gNodeBs, UEs, V2X device, or D2D devices shown inFIGS.1-5,7, and8. At908, the RAN node902, which may be a transmitting wireless communication device, generates a message indicating one or more pathloss reference signals (PL-RSs) to utilize for multi-component carrier communication. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). It should be understood that the transmitting device can be either a RAN node or a UE. Thus, for the sidelink, a UE may receive the message from a RAN node, and subsequently transmit the information provided in the message to another UE in the sidelink using SCI. The message may include one of a PL-RS activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of PL-RSs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first PL-RSs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first PL-RSs. Additionally, or alternatively, the message may include a second entry indicating second PL-RSs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second PL-RSs. At910, the RAN node902transmits the message for updating the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, the RAN node902may transmit the message to the UE1904to update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. It should be understood that the transmitting device can be either a RAN node, as shown inFIG.8, or a UE. Thus, for the sidelink, a UE may receive the message from a RAN node, and subsequently transmit the information provided in the message to another UE on the sidelink using SCI. In other examples, a UE may autonomously transmit a message via SCI to update one or more PL-RS for a group of two or more sidelink component carriers to another UE on the sidelink. At912, the UE1904update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, in response to receiving the message from the RAN node902, the UE1904may update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. In some aspects, when a reference signal source of a PL-RS of the one or more PL-RSs in the message is associated with access communication, the UE1904updates the one or more PL-RSs for the group of two or more component carriers of the plurality of access carriers. In some aspects, when a reference signal source of a PL-RS of the one or more PL-RSs in the message is associated with sidelink communication, the UE1904updates the one or more PL-RSs for the group of two or more component carriers for the plurality of sidelink carriers. At914, the UE1904communicates using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE1904may communicate with the RAN node902using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. At916, the UE1904communicates using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the sidelink multi-component carrier communication. For example, the UE1904may communicate with the UE2906using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the sidelink multi-component carrier communication. FIG.10is a block diagram illustrating an example of a hardware implementation for a radio access network (RAN) node employing a processing system1014. For example, the RAN node1000may be any of the base stations (e.g., gNB or eNB) illustrated in any one or more ofFIGS.1-5,7,8, and9. The RAN node1000may be implemented with a processing system1014that includes one or more processors1004. Examples of processors1004include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. In various examples, the RAN node1000may be configured to perform any one or more of the functions described herein. That is, the processor1004, as utilized in a RAN node1000, may be used to implement any one or more of the processes described herein. The processor1004may in some instances be implemented via a baseband or modem chip and in other implementations, the processor1004may itself comprise a number of devices distinct and different from a baseband or modem chip (e.g., in such scenarios is may work in concert to achieve aspects discussed herein). And as mentioned above, various hardware arrangements and components outside of a baseband modem processor can be used in implementations, including RF-chains, power amplifiers, modulators, buffers, interleavers, adders/summers, etc. In this example, the processing system1014may be implemented with a bus architecture, represented generally by the bus1002. The bus1002may include any number of interconnecting buses and bridges depending on the specific application of the processing system1014and the overall design constraints. The bus1002communicatively couples together various circuits including one or more processors (represented generally by the processor1004), and computer-readable media (represented generally by the computer-readable storage medium1006). The bus1002may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. A bus interface1008provides an interface between the bus1002and a transceiver1010. The transceiver1010provides a means for communicating with various other apparatus over a transmission medium (e.g., air interface). A user interface1012(e.g., keypad, display, speaker, microphone, joystick) may also be provided. The processor1004is responsible for managing the bus1002and general processing, including the execution of software stored on the computer-readable storage medium1006. The software, when executed by the processor1004, causes the processing system1014to perform the various functions described herein for any particular apparatus. The computer-readable storage medium1006may also be used for storing data that is manipulated by the processor1004when executing software. One or more processors1004in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable storage medium1006. The computer-readable storage medium1006may be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a smart card, a flash memory device (e.g., a card, a stick, or a key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. The computer-readable storage medium1006may reside in the processing system1014, external to the processing system1014, or distributed across multiple entities including the processing system1014. The computer-readable storage medium1006may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system. In some aspects of the disclosure, the processor1004may include circuitry configured for various functions. For example, the processor1004may include generating circuitry1040configured to generate a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. Additionally, or alternatively, the generating circuitry1040may be configured to generate a message indicating one or more pathloss reference signals (PL-RSs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. The generating circuitry1040may further be configured to execute generating instructions1050stored in the computer-readable storage medium1006to implement any of the one or more of the functions described herein. The processor1004may also include transmitting circuitry1042configured to transmit, via the transceiver1010, the message to a user equipment (UE) to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. Additionally, or alternatively, the transmitting circuitry1042may be configured to transmit, via the transceiver1010, the message for updating the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. The transmitting circuitry1042may further be configured to execute transmitting instructions1052stored in the computer-readable storage medium1006to implement any of the one or more of the functions described herein. The processor1004may further include communication circuitry1044configured to utilize a communication link and communicate with a user equipment using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. The communication circuitry1044may further be configured to execute communication instructions1054stored in the computer-readable storage medium1006to implement any of the one or more of the functions described herein. FIG.11is a flow chart1100of a method for generating and transmitting transmission configuration indicator states (TCI-states) or spatial relations (SRs) to utilize for multi-component communication according to some aspects. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all aspects. In some examples, the method may be performed by the RAN node1000, as described above and illustrated inFIG.10, by a processor or processing system, or by any suitable means for carrying out the described functions. At block1102, the RAN node1000generates a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). The TCI-states or SRs may indicate the spatial property (e.g., beam direction and/or beam width) of a transmit beams to be utilized by a wireless communication device. For example, for access communication, the TCI-state may include quasi co-location (QCL) information (e.g., QCL-Type D) referencing an access SSB beam or access CSI-RS transmit beam on the transmitting wireless communication device. Similarly, the SRI may indicate a spatial relation between an access SSB or access CSI-RS beam and an uplink transmit beam utilized by the UE for uplink transmissions. In this example, a wireless communication device may identify the selected uplink transmit beam having a spatial direction in the same direction as the indicated access SSB or CSI-RS beam. Similarly, for sidelink communication, the TCI states or SRs may indicate the sidelink transmit beams to be utilized for communication on the sidelink between UEs. Subsequently, the receive beams may be determined by the BPL. The message may include one of a TCI-state activation and deactivation message or an SRI activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of TCI-states including the one or more TCI states or each of a plurality of SRs including the one or more SRs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first TCI-states or first SRs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first TCI-states or the first SRs. Additionally, or alternatively, the message may include a second entry indicating second TCI-states or second SRs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second TCI-states or the second SRs. The generation of the message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication may be further described with respect to the description ofFIGS.1-5,7,8, and9provided herein. The generating circuitry1040shown and described above in connection withFIG.10, may provide a means to generate the message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication. At block1104, the RAN node1000transmits the message to a user equipment (UE) to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, the RAN node802may transmit the message to the UE1804to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. It should be understood that the transmitting device can be either a RAN node or a UE. Thus, for the sidelink, a UE may receive the message from a RAN node, and subsequently transmit the information provided in the message to another UE in the sidelink using SCI. The transmitting circuitry1042, together with the transceiver1010, shown and described above in connection withFIG.10may provide a means to transmit the message to a user equipment (UE) to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. At block1106, the RAN node1000communicates using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE1804may communicate with the RAN node802using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. In some examples, the UE1804may communicate with the RAN node802on one or more beams on each of the aggregated access component carriers, as indicated in the message. For example, the message may indicate a downlink receive beam or a transmit uplink beam to use on one or more of the aggregated access component carriers. The communication circuitry1044, together with the transceiver1010, shown and described above in connection withFIG.10may provide a means to communicate using access communication by aggregating at least two of the plurality of access component carriers. FIG.12is a flow chart1200of a method for generating and transmitting pathloss reference signals (PL-RSs) to utilize for multi-component communication according to some aspects. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all aspects. In some examples, the method may be performed by the RAN node1000, as described above and illustrated inFIG.10, by a processor or processing system, or by any suitable means for carrying out the described functions. At block1202, the RAN node1000generates a message indicating one or more pathloss reference signals (PL-RSs) to utilize for multi-component carrier communication. The message comprising an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). It should be understood that the transmitting device can be either a RAN node or a UE. Thus, for the sidelink, a UE may receive the message from a RAN node, and subsequently transmit the information provided in the message to another UE in the sidelink using SCI. The message may include one of a PL-RS activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of PL-RSs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first PL-RSs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first PL-RSs. Additionally, or alternatively, the message may include a second entry indicating second PL-RSs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second PL-RSs. The generation of the message indicating one or more PL-RSs to utilize for multi-component carrier communication may be further described with respect to the description ofFIGS.1-5,7,8, and9provided herein. The generating circuitry1040shown and described above in connection withFIG.10, may provide a means to generate the message indicating one or more PL-RSs to utilize for multi-component carrier communication. At block1204, the RAN node1000transmits the message for updating the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, the RAN node1000may transmit the message to a UE to update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. The transmitting circuitry1042, together with the transceiver1010, shown and described above in connection withFIG.10, may provide a means to transmit the message for updating the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. At block1206, the RAN node1000communicates using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE1804may communicate with the RAN node802using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. In some examples, the UE1804may communicate with the RAN node802on one or more beams on each of the aggregated access component carriers, as indicated in the message. The communication circuitry1044, together with the transceiver1010, shown and described above in connection withFIG.10may provide a means to communicate using access communication by aggregating at least two of the plurality of component carriers. FIG.13is a flow chart of another method for generating and transmitting pathloss reference signals (PL-RSs) to utilize for multi-component communication according to some aspects. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all aspects. In some examples, the method may be performed by the RAN node1000, as described above and illustrated inFIG.10, by a processor or processing system, or by any suitable means for carrying out the described functions. At block1302, the RAN node1000generates a message indicating one or more pathloss reference signals (PL-RSs) to utilize for multi-component carrier communication. The message comprising an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). It should be understood that the transmitting device can be either a RAN node or a UE. Thus, for the sidelink, a UE may receive the message from a RAN node, and subsequently transmit the information provided in the message to another UE in the sidelink using SCI. The message may include one of a PL-RS activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of PL-RSs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first PL-RSs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first PL-RSs. Additionally, or alternatively, the message may include a second entry indicating second PL-RSs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second PL-RSs. The generation of the message indicating one or more PL-RSs to utilize for multi-component carrier communication may be further described with respect to the description ofFIGS.1-5,7-9,11and12provided herein. The generating circuitry1040shown and described above in connection withFIG.10, may provide a means to generate the message indicating one or more PL-RSs to utilize for multi-component carrier communication. At block1304, the RAN node1000transmits the message for updating the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, the RAN node1000may transmit the message to a UE to update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. The transmitting circuitry1042, together with the transceiver1010, shown and described above in connection withFIG.10, may provide a means to transmit the message for updating the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. At block1306, the RAN node1000communicates using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE1804may communicate with the RAN node802using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. In some examples, the UE1804may communicate with the RAN node802on one or more beams on each of the aggregated access component carriers, as indicated in the message. The communication circuitry1044, together with the transceiver1010, shown and described above in connection withFIG.10may provide a means to communicate using access communication by aggregating at least two of the plurality of component carriers. FIG.14is a block diagram illustrating an example of a hardware implementation for a UE1400(e.g., a wireless communication device) employing a processing system1414according to some aspects. For example, the UE1400may correspond to any of the UEs shown and described above in any one or more ofFIGS.1-5,7,8, and/or9. In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system1414that includes one or more processors1404. The processing system1414may be substantially the same as the processing system1014illustrated inFIG.10, including a bus interface1408, a bus1402, a processor1404, and a computer-readable storage medium1406. Furthermore, the UE1400may include a user interface1412and a transceiver1410substantially similar to those described above inFIG.10. That is, the processor1404, as utilized in a UE1400, may be used to implement any one or more of the processes described herein. In some aspects of the disclosure, the processor1404may include circuitry configured for various functions. For example, the processor1404may include receiving circuitry1440configured to receive, from a RAN node (e.g., base station, such as a gNB or eNB) and via the transceiver1410, a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. Additionally, or alternatively, the receiving circuitry1440may be configured to receive a message indicating one or more pathloss reference signals (PL-RSs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. The receiving circuitry1440may further be configured to execute receiving instructions1450stored in the computer-readable storage medium1406to implement any of the one or more of the functions described herein. The processor1404may also include updating circuitry1442configured to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. Additionally, or alternatively, the updating circuitry1442may be configured to updating the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. The updating circuitry1442may further be configured to execute updating instructions1452stored in the computer-readable storage medium1406to implement any of the one or more of the functions described herein. The processor1404may further include communication circuitry1444configured to utilize a communication link and communicate with a base station using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. Additionally, or alternatively, the communication circuitry1444may be configured to utilize a communication link and communicate with another UE using sidelink communication by aggregating at least two of the plurality of sidelink component carriers for the multi-component carrier communication. The communication circuitry1444may further be configured to execute communication instructions1454stored in the computer-readable storage medium1406to implement any of the one or more of the functions described herein. FIG.15is a flow chart1500of a method for receiving and updating transmission configuration indicator states (TCI-states) or spatial relations (SRs) to utilize for multi-component communication according to some aspects. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all aspects. In some examples, the method may be performed by the UE1400, as described above, and illustrated inFIG.14, by a processor or processing system, or by any suitable means for carrying out the described functions. At block1502, the UE1400receives a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). The TCI-states or SRs may indicate the spatial property (e.g., beam direction and/or beam width) of a transmit beams to be utilized by a wireless communication device. For example, for access communication, the TCI-state may include quasi co-location (QCL) information (e.g., QCL-Type D) referencing an access SSB beam or access CSI-RS transmit beam on the transmitting wireless communication device. Similarly, the SRI may indicate a spatial relation between an access SSB or access CSI-RS beam and an uplink transmit beam utilized by the UE for uplink transmissions. In this example, a wireless communication device may identify the selected uplink transmit beam having a spatial direction in the same direction as the indicated access SSB or CSI-RS beam. Similarly, for sidelink communication, the TCI states or SRs may indicate the sidelink transmit beams to be utilized for communication on the sidelink between UEs Subsequently, the receive beams may be determined by the BPL. The message may include one of a TCI-state activation and deactivation message or an SRI activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of TCI-states including the one or more TCI states or each of a plurality of SRs including the one or more SRs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first TCI-states or first SRs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first TCI-states or the first SRs. Additionally, or alternatively, the message may include a second entry indicating second TCI-states or second SRs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second TCI-states or the second SRs. The reception of the message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication may be further described with respect to the description ofFIGS.1-5,7,8, and9provided herein. The receiving circuitry1440, together with the transceiver1410, shown and described above in connection withFIG.14, may provide a means to receive the message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication. At block1504, the UE1400updates the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, in response to receiving the message from the RAN node, the UE may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. In some aspects, when a reference signal source of a TCI-state of the one or more TCI-states or an SRI of the one or more SRs in the message is associated with access communication, the UE may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers of the plurality of access carriers. In some aspects, when a reference signal source of a TCI-state of the one or more TCI-states or an SRI of the one or more SRs in the message is associated with sidelink communication, the UE may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the plurality of sidelink carriers. The updating circuitry1442shown and described above in connection withFIG.14may provide a means to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. At block1506, the UE1400communicates using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE may communicate with the RAN node using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. In some examples, the UE may communicate with the RAN node on one or more beams on each of the aggregated access component carriers, as indicated in the message. For example, the message may provide a means to indicate a transmit downlink beam or a transmit uplink beam to use on one or more of the aggregated access component carriers. The communication circuitry1444, together with the transceiver1410, shown and described above in connection withFIG.14may provide a means to communicate using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. At block1508, the UE1400communicates using sidelink communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE may communicate with another UE using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the sidelink multi-component carrier communication. In some examples, the UE may communicate with the other UE on one or more beams on each of the aggregated sidelink component carriers, as indicated in the message. For example, the message may indicate a transmit sidelink beam to use by the UE or the other UE on one or more of the aggregated sidelink component carriers. The communication circuitry1444, together with the transceiver1410, shown and described above in connection withFIG.14may provide a means to communicate using sidelink communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. FIG.16is a flow chart of a method for receiving and updating pathloss reference signals (PL-RSs) to utilize for multi-component communication according to some aspects. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all aspects. In some examples, the method may be performed by the UE1400, as described above, and illustrated inFIG.14, by a processor or processing system, or by any suitable means for carrying out the described functions. At block1602, the UE1400receives a message indicating one or more pathloss reference signals (PL-RSs) to utilize for multi-component carrier communication. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). The message may include one of a PL-RS activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of PL-RSs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more PL-RSs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first PL-RSs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first PL-RSs. Additionally, or alternatively, the message may include a second entry indicating second PL-RSs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second PL-RSs. The reception of the message indicating one or more PL-RSs to utilize for multi-component carrier communication may be further described with respect to the description ofFIGS.1-5,7,8, and9provided herein. The receiving circuitry1440, together with the transceiver1410, shown and described above in connection withFIG.14, may provide a means to receive the message indicating one or more PL-RSs to utilize for multi-component carrier communication. At block1604, the UE1400updates the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, in response to receiving the message from the RAN node, the UE may update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. In some aspects, when a reference signal source of a PL-RS of the one or more PL-RSs in the message is associated with access communication, the UE updates the one or more PL-RSs for the group of two or more component carriers of the plurality of access carriers. In some aspects, when a reference signal source of a PL-RS of the one or more PL-RSs in the message is associated with sidelink communication, the UE updates the one or more PL-RSs for the group of two or more component carriers for the plurality of sidelink carriers. The updating circuitry1442shown and described above in connection withFIG.14, may provide a means to update the one or more PL-RSs for the group of two or more component carriers for the multi-component carrier communication based on the message. At block1606, the UE1400communicates using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE may communicate with the RAN node using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. In some examples, the UE may communicate with the RAN node on one or more beams on each of the aggregated access component carriers, as indicated in the message. The communication circuitry1444, together with the transceiver1410, shown and described above in connection withFIG.14may provide a means to communicate using access communication by aggregating at least two of the plurality of component carriers. At block1608, the UE1400communicates using sidelink communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. For example, the UE may communicate with another UE using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the sidelink multi-component carrier communication. In some examples, the UE may communicate with the other UE on one or more beams on each of the aggregated sidelink component carriers. For example, the message may indicate a PL-RS to use by the UE or the other UE on one or more of the aggregated sidelink component carriers. The communication circuitry1444, together with the transceiver1410, shown and described above in connection withFIG.14may provide a means to communicate using sidelink communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication. FIG.17is a flow chart1700of a method for receiving and updating transmission configuration indicator states (TCI-states) or spatial relations (SRs) to utilize for multi-component communication according to some aspects. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all aspects. In some examples, the method may be performed by the UE1400, as described above, and illustrated inFIG.14, by a processor or processing system, or by any suitable means for carrying out the described functions. At block1702, the UE1400receives a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication, the message comprising an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. The message may include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. The message may include at least one of a medium access control (MAC) control element (MAC-CE), or downlink control information (DCI). The TCI-states or SRs may indicate the spatial property (e.g., beam direction and/or beam width) of a transmit beams to be utilized by a wireless communication device. For example, for access communication, the TCI-state may include quasi co-location (QCL) information (e.g., QCL-Type D) referencing an access SSB beam or access CSI-RS transmit beam on the transmitting wireless communication device. Similarly, the SRI may indicate a spatial relation between an access SSB or access CSI-RS beam and an uplink transmit beam utilized by the UE for uplink transmissions. In this example, a wireless communication device may identify the selected uplink transmit beam having a spatial direction in the same direction as the indicated access SSB or CSI-RS beam. Similarly, for sidelink communication, the TCI states or SRs may indicate the sidelink transmit beams to be utilized for communication on the sidelink between UEs Subsequently, the receive beams may be determined by the BPL. The message may include one of a TCI-state activation and deactivation message or an SRI activation and deactivation message. For example, the message may include a binary string of one or more “zeros” and one or more “ones” for activating or deactivating each of a plurality of TCI-states including the one or more TCI states or each of a plurality of SRs including the one or more SRs. The message may also include an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. In some aspects, the index may identify the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may identify the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. In some aspects, the index may include a group index identifying a designated component carrier representing the group of two or more component carriers. The message may include a first entry indicating first TCI-states or first SRs to utilize for access multi-component carrier communication. The first entry may include a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first TCI-states or the first SRs. Additionally, or alternatively, the message may include a second entry indicating second TCI-states or second SRs to utilize for sidelink multi-component carrier communication. The second entry may include a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second TCI-states or the second SRs. The reception of the message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication may be further described with respect to the description ofFIGS.1-5,7,8, and9provided herein. The receiving circuitry1440, together with the transceiver1410, shown and described above in connection withFIG.14, may provide a means to receive a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication, the message comprising an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs. At block1704, the UE1400communicates an update of one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. For example, in response to receiving the message from the RAN node, the UE may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. In some aspects, when a reference signal source of a TCI-state of the one or more TCI-states or an SRI of the one or more SRs in the message is associated with access communication, the UE may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers of the plurality of access carriers. In some aspects, when a reference signal source of a TCI-state of the one or more TCI-states or an SRI of the one or more SRs in the message is associated with sidelink communication, the UE may update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the plurality of sidelink carriers. The communication circuitry1444, together with the transceiver1410, shown and described above in connection withFIG.14may provide a means to communicate an update of one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. The following provides an overview of aspects of the present disclosure: Aspect 1: A method for wireless communication at a user equipment (UE), comprising: receiving a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication, the message comprising an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs; and updating the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. Aspect 2: The method of aspect 1, wherein the index identifies the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. Aspect 3: The method of aspect 1, wherein the index identifies the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. Aspect 4: The method of aspect 1, wherein the index comprises a group index identifying a designated component carrier representing the group of two or more component carriers. Aspect 5: The method of aspect 1, wherein the message comprises at least one of a medium access control (MAC) control element (MAC-CE), sidelink control information (SCI), or downlink control information (DCI). Aspect 6: The method of aspect 1, wherein the message comprises one of a TCI-state activation and deactivation message or an SRI activation and deactivation message. Aspect 7: The method of aspect 6, wherein the message comprises a binary string for activating or deactivating each of a plurality of TCI-states including the one or more TCI states or each of a plurality of SRs including the one or more SRs. Aspect 8: The method of aspect 1, further comprising: updating the one or more TCI-states or the one or more SRs for the group of two or more component carriers of the plurality of access carriers in response to a reference signal source of a TCI-state of the one or more TCI-states or an SR of the one or more SRs in the message being associated with access communication. Aspect 9: The method of aspect 1, further comprising: updating the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the plurality of sidelink carriers in response to a reference signal source of a TCI-state of the one or more TCI-states or an SR of the one or more SRs in the message being associated with the access communication. Aspect 10: The method of aspect 1, further comprising at least one of: communicating with a base station using access communication by aggregating at least two of the plurality of access component carriers for the multi-component carrier communication, or communicating with another UE using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the sidelink multi-component carrier communication. Aspect 11: The method of aspect 1, wherein the message comprises at least one of: a first entry indicating first TCI-states or first SRs to utilize for access multi-component carrier communication, the first entry comprising a first index identifying a first group of two or more component carriers of the plurality of access component carriers associated with the first TCI-states or the first SRs, or a second entry indicating second TCI-states or second SRs to utilize for sidelink multi-component carrier communication, the second entry comprising a second index identifying a second group of two or more component carriers of the plurality of sidelink component carriers associated with the second TCI-states or the second SRs. Aspect 12: A user equipment (UE) in a radio access network (RAN) of a wireless communication system, the UE comprising: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, wherein the processor and memory are configured to perform a method of any one of aspects 1 through 11. Aspect 13: A user equipment (UE) comprising means for performing a method of any one of aspects 1 through 11. Aspect 14: A non-transitory processor-readable storage medium storing processor-executable instructions for causing a processing circuit to perform a method of any one of aspects 1 through 11. Aspect 15: A method for wireless communication at a Radio Access Network (RAN) node, comprising: generating a message indicating one or more transmission configuration indicator states (TCI-states) or one or more spatial relations (SRs) to utilize for multi-component carrier communication, the message comprising an index identifying a group of two or more component carriers of a plurality of access component carriers or a plurality of sidelink component carriers associated with the one or more TCI-states or the one or more SRs, and transmitting the message to a user equipment (UE) to update the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the multi-component carrier communication based on the message. Aspect 16: The method of aspect 15, wherein the index identifies the group of two or more component carriers from a set of all configured component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. Aspect 17: The method of aspect 15, wherein the index identifies the group of two or more component carriers from a set of all active component carriers of the plurality of access component carriers or the plurality of sidelink component carriers. Aspect 18: The method of aspect 15, wherein the index comprises a group index identifying a designated component carrier representing the group of two or more component carriers. Aspect 19: The method of aspect 15, wherein the message comprises at least one of a medium access control (MAC) control element (MAC-CE), sidelink control information (SCI), or downlink control information (DCI). Aspect 20: The method of aspect 15, wherein the message comprises one of a TCI-state activation and deactivation message or an SR activation and deactivation message. Aspect 21: The method of aspect 20, wherein the message comprises a binary string for activating or deactivating each of a plurality of TCI-states including the one or more TCI states or each of a plurality of SRs including the one or more SRs. Aspect 22: The method of aspect 15, further comprising: updating the one or more TCI-states or the one or more SRs for the group of two or more component carriers of the plurality of access carriers in response to a reference signal source of a TCI-state of the one or more TCI-states or an SR of the one or more SRs in the message being associated with access communication. Aspect 23: The method of aspect 15, further comprising: updating the one or more TCI-states or the one or more SRs for the group of two or more component carriers for the plurality of sidelink carriers in response to a reference signal source of a TCI-state of the one or more TCI-states or an SR of the one or more SRs in the message being associated with the access communication. Aspect 24: The method of aspect 15, further comprising at least one of: communicating using access communication by aggregating at least two of the plurality of the access component carriers for the multi-component carrier communication, or communicating using sidelink communication by aggregating at least two of the plurality of the sidelink component carriers for the multi-component carrier communication. Aspect 25: A radio access network (RAN) node of a wireless communication system, the RAN node comprising: a wireless transceiver; a memory; and a processor communicatively coupled to the wireless transceiver and the memory, wherein the processor and memory are configured to perform a method of any one of aspects 15 through 24. Aspect 26: A radio access network (RAN) node comprising means for performing a method of any one of aspects 15 through 24. Aspect 27: A non-transitory processor-readable storage medium storing processor-executable instructions for causing a processing circuit to perform a method of any one of aspects 15 through 24. By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE), the Evolved Packet System (EPS), the Universal Mobile Telecommunication System (UMTS), and/or the Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and/or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and/or other suitable systems. The actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system. Within the present disclosure, the word “exemplary” is used to mean “serving as an example, instance, or illustration.” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another-even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object. The terms “circuit” and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure. One or more of the components, steps, features and/or functions illustrated inFIGS.1-17may be rearranged and/or combined into a single component, step, feature, or function or embodied in several components, steps, or functions. Additional stages, components, steps, and/or functions may also be added without departing from novel features disclosed herein. The apparatus, devices, and/or components illustrated inFIGS.1-17may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware. It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present stages of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein reference to an stage in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents to the stages of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. | 148,281 |
11943770 | DESCRIPTION OF EXEMPLARY EMBODIMENTS In the present disclosure, “A or B” may mean “only A”, “only B” or “both A and B.” In other words, in the present disclosure, “A or B” may be interpreted as “A and/or B”. For example, in the present disclosure, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”. A slash (/) or comma used in the present disclosure may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”. In the present disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present disclosure, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”. In addition, in the present disclosure, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”. In addition, a parenthesis used in the present disclosure may mean “for example”. Specifically, when indicated as “control information (PDCCH)”, it may mean that “PDCCH” is proposed as an example of the “control information”. In other words, the “control information” of the present disclosure is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., PDCCH)”, it may also mean that “PDCCH” is proposed as an example of the “control information”. In the following description, ‘when, if, or in case of’ may be replaced with ‘based on’. A technical feature described individually in one figure in the present disclosure may be individually implemented, or may be simultaneously implemented. In the present disclosure, a higher layer parameter may be a parameter which is configured, pre-configured or pre-defined for a UE. For example, a base station or a network may transmit the higher layer parameter to the UE. For example, the higher layer parameter may be transmitted through radio resource control (RRC) signaling or medium access control (MAC) signaling. The technology described below may be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and so on. The CDMA may be implemented with a radio technology, such as universal terrestrial radio access (UTRA) or CDMA-2000. The TDMA may be implemented with a radio technology, such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE). The OFDMA may be implemented with a radio technology, such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), and so on. IEEE 802.16m is an evolved version of IEEE 802.16e and provides backward compatibility with a system based on the IEEE 802.16e. The UTRA is part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is part of an evolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA in a downlink and uses the SC-FDMA in an uplink. LTE-advanced (LTE-A) is an evolution of the LTE. 5G NR is a successive technology of LTE-A corresponding to a new Clean-slate type mobile communication system having the characteristics of high performance, low latency, high availability, and so on. 5G NR may use resources of all spectrum available for usage including low frequency bands of less than 1 GHz, middle frequency bands ranging from 1 GHz to 10 GHz, high frequency (millimeter waves) of 24 GHz or more, and so on. For clarity in the description, the following description will mostly focus on LTE-A or 5G NR. However, technical features according to an embodiment of the present disclosure will not be limited only to this. FIG.1shows a structure of an NR system, based on an embodiment of the present disclosure. The embodiment ofFIG.1may be combined with various embodiments of the present disclosure. Referring toFIG.1, a next generation—radio access network (NG-RAN) may include a BS20providing a UE10with a user plane and control plane protocol termination. For example, the BS20may include a next generation-Node B (gNB) and/or an evolved-NodeB (eNB). For example, the UE10may be fixed or mobile and may be referred to as other terms, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), wireless device, and so on. For example, the BS may be referred to as a fixed station which communicates with the UE10and may be referred to as other terms, such as a base transceiver system (BTS), an access point (AP), and so on. The embodiment ofFIG.1exemplifies a case where only the gNB is included. The BSs20may be connected to one another via Xn interface. The BS20may be connected to one another via 5th generation (5G) core network (5GC) and NG interface. More specifically, the BSs20may be connected to an access and mobility management function (AMF)30via NG-C interface, and may be connected to a user plane function (UPF)30via NG-U interface. Layers of a radio interface protocol between the UE and the network can be classified into a first layer (layer 1, L1), a second layer (layer 2, L2), and a third layer (layer 3, L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system. Among them, a physical (PHY) layer belonging to the first layer provides an information transfer service by using a physical channel, and a radio resource control (RRC) layer belonging to the third layer serves to control a radio resource between the UE and the network. For this, the RRC layer exchanges an RRC message between the UE and the BS. FIG.2shows a radio protocol architecture, based on an embodiment of the present disclosure. The embodiment ofFIG.2may be combined with various embodiments of the present disclosure. Specifically, (a) ofFIG.2shows a radio protocol stack of a user plane for Uu communication, and (b) ofFIG.2shows a radio protocol stack of a control plane for Uu communication. (c) ofFIG.2shows a radio protocol stack of a user plane for SL communication, and (d) ofFIG.2shows a radio protocol stack of a control plane for SL communication. Referring toFIG.2, a physical layer provides an upper layer with an information transfer service through a physical channel. The physical layer is connected to a medium access control (MAC) layer which is an upper layer of the physical layer through a transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. The transport channel is classified according to how and with what characteristics data is transmitted through a radio interface. Between different physical layers, i.e., a physical layer of a transmitter and a physical layer of a receiver, data are transferred through the physical channel. The physical channel is modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and utilizes time and frequency as a radio resource. The MAC layer provides services to a radio link control (RLC) layer, which is a higher layer of the MAC layer, via a logical channel. The MAC layer provides a function of mapping multiple logical channels to multiple transport channels. The MAC layer also provides a function of logical channel multiplexing by mapping multiple logical channels to a single transport channel. The MAC layer provides data transfer services over logical channels. The RLC layer performs concatenation, segmentation, and reassembly of Radio Link Control Service Data Unit (RLC SDU). In order to ensure diverse quality of service (QoS) required by a radio bearer (RB), the RLC layer provides three types of operation modes, i.e., a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). An AM RLC provides error correction through an automatic repeat request (ARQ). A radio resource control (RRC) layer is defined only in the control plane. The RRC layer serves to control the logical channel, the transport channel, and the physical channel in association with configuration, reconfiguration and release of RBs. The RB is a logical path provided by the first layer (i.e., the physical layer or the PHY layer) and the second layer (i.e., a MAC layer, an RLC layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer) for data delivery between the UE and the network. Functions of a packet data convergence protocol (PDCP) layer in the user plane include user data delivery, header compression, and ciphering. Functions of a PDCP layer in the control plane include control-plane data delivery and ciphering/integrity protection. A service data adaptation protocol (SDAP) layer is defined only in a user plane. The SDAP layer performs mapping between a Quality of Service (QoS) flow and a data radio bearer (DRB) and QoS flow ID (QFI) marking in both DL and UL packets. The configuration of the RB implies a process for specifying a radio protocol layer and channel properties to provide a particular service and for determining respective detailed parameters and operations. The RB can be classified into two types, i.e., a signaling RB (SRB) and a data RB (DRB). The SRB is used as a path for transmitting an RRC message in the control plane. The DRB is used as a path for transmitting user data in the user plane. When an RRC connection is established between an RRC layer of the UE and an RRC layer of the E-UTRAN, the UE is in an RRC_CONNECTED state, and, otherwise, the UE may be in an RRC_IDLE state. In case of the NR, an RRC INACTIVE state is additionally defined, and a UE being in the RRC INACTIVE state may maintain its connection with a core network whereas its connection with the BS is released. Data is transmitted from the network to the UE through a downlink transport channel. Examples of the downlink transport channel include a broadcast channel (BCH) for transmitting system information and a downlink-shared channel (SCH) for transmitting user traffic or control messages. Traffic of downlink multicast or broadcast services or the control messages can be transmitted on the downlink-SCH or an additional downlink multicast channel (MCH). Data is transmitted from the UE to the network through an uplink transport channel. Examples of the uplink transport channel include a random access channel (RACH) for transmitting an initial control message and an uplink SCH for transmitting user traffic or control messages. Examples of logical channels belonging to a higher channel of the transport channel and mapped onto the transport channels include a broadcast channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), a multicast traffic channel (MTCH), etc. FIG.3shows a structure of a radio frame of an NR, based on an embodiment of the present disclosure. The embodiment ofFIG.3may be combined with various embodiments of the present disclosure. Referring toFIG.3, in the NR, a radio frame may be used for performing uplink and downlink transmission. A radio frame has a length of 10 ms and may be defined to be configured of two half-frames (HFs). A half-frame may include five 1 ms subframes (SFs). A subframe (SF) may be divided into one or more slots, and the number of slots within a subframe may be determined based on subcarrier spacing (SCS). Each slot may include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP). In case of using a normal CP, each slot may include 14 symbols. In case of using an extended CP, each slot may include 12 symbols. Herein, a symbol may include an OFDM symbol (or CP-OFDM symbol) and a Single Carrier-FDMA (SC-FDMA) symbol (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol). Table 1 shown below represents an example of a number of symbols per slot (Nslotsymb), a number slots per frame (Nframe.uslot), and a number of slots per subframe (Nsubframe.uslot) based on an SCS configuration (u), in a case where a normal CP is used. TABLE 1SCS (15*2u)NsymbslotNslotframe,uNslotsubframe,u15 KHz (u = 0)1410130 KHz (u = 1)1420260 KHz (u = 2)14404120 KHz (u = 3)14808240 KHz (u = 4)1416016 Table 2 shows an example of a number of symbols per slot, a number of slots per frame, and a number of slots per subframe based on the SCS, in a case where an extended CP is used. TABLE 2SCS (15*2u)NsymbslotNslotframe,uNslotsubframe,u60 KHz (u = 2)12404 In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, and so on) between multiple cells being integrate to one UE may be differently configured. Accordingly, a (absolute time) duration (or section) of a time resource (e.g., subframe, slot or TTI) (collectively referred to as a time unit (TU) for simplicity) being configured of the same number of symbols may be differently configured in the integrated cells. In the NR, multiple numerologies or SCSs for supporting diverse 5G services may be supported. For example, in case an SCS is 15 kHz, a wide area of the conventional cellular bands may be supported, and, in case an SCS is 30 kHz/60 kHz a dense-urban, lower latency, wider carrier bandwidth may be supported. In case the SCS is 60 kHz or higher, a bandwidth that is greater than 24.25 GHz may be used in order to overcome phase noise. An NR frequency band may be defined as two different types of frequency ranges. The two different types of frequency ranges may be FR1 and FR2. The values of the frequency ranges may be changed (or varied), and, for example, the two different types of frequency ranges may be as shown below in Table 3. Among the frequency ranges that are used in an NR system, FR1 may mean a “sub 6 GHz range”, and FR2 may mean an “above 6 GHz range” and may also be referred to as a millimeter wave (mmW). TABLE 3FrequencyRangeCorrespondingSubcarrierdesignationfrequency rangeSpacing (SCS)FR1450 MHz-6000 MHz15, 30, 60 kHzFR224250 MHz-52600 MHz60, 120, 240 kHz As described above, the values of the frequency ranges in the NR system may be changed (or varied). For example, as shown below in Table 4, FR1 may include a band within a range of 410 MHz to 7125 MHz. More specifically, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher being included in FR1 mat include an unlicensed band. The unlicensed band may be used for diverse purposes, e.g., the unlicensed band for vehicle-specific communication (e.g., automated driving). TABLE 4FrequencyRangeCorrespondingSubcarrierdesignationfrequency rangeSpacing (SCS)FR1410 MHz-7125 MHz15, 30, 60 kHzFR224250 MHz-52600 MHz60, 120, 240 kHz FIG.4shows a structure of a slot of an NR frame, based on an embodiment of the present disclosure. The embodiment ofFIG.4may be combined with various embodiments of the present disclosure. Referring toFIG.4, a slot includes a plurality of symbols in a time domain. For example, in case of a normal CP, one slot may include 14 symbols. However, in case of an extended CP, one slot may include 12 symbols. Alternatively, in case of a normal CP, one slot may include 7 symbols. However, in case of an extended CP, one slot may include 6 symbols. A carrier includes a plurality of subcarriers in a frequency domain. A Resource Block (RB) may be defined as a plurality of consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A Bandwidth Part (BWP) may be defined as a plurality of consecutive (Physical) Resource Blocks ((P)RBs) in the frequency domain, and the BWP may correspond to one numerology (e.g., SCS, CP length, and so on). A carrier may include a maximum of N number BWPs (e.g., 5 BWPs). Data communication may be performed via an activated BWP. Each element may be referred to as a Resource Element (RE) within a resource grid and one complex symbol may be mapped to each element. Hereinafter, a bandwidth part (BWP) and a carrier will be described. The BWP may be a set of consecutive physical resource blocks (PRBs) in a given numerology. The PRB may be selected from consecutive sub-sets of common resource blocks (CRBs) for the given numerology on a given carrier. For example, the BWP may be at least any one of an active BWP, an initial BWP, and/or a default BWP. For example, the UE may not monitor downlink radio link quality in a DL BWP other than an active DL BWP on a primary cell (PCell). For example, the UE may not receive PDCCH, physical downlink shared channel (PDSCH), or channel state information reference signal (CSI-RS) (excluding RRM) outside the active DL BWP. For example, the UE may not trigger a channel state information (CSI) report for the inactive DL BWP. For example, the UE may not transmit physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH) outside an active UL BWP. For example, in a downlink case, the initial BWP may be given as a consecutive RB set for a remaining minimum system information (RMSI) control resource set (CORESET) (configured by physical broadcast channel (PBCH)). For example, in an uplink case, the initial BWP may be given by system information block (SIB) for a random access procedure. For example, the default BWP may be configured by a higher layer. For example, an initial value of the default BWP may be an initial DL BWP. For energy saving, if the UE fails to detect downlink control information (DCI) during a specific period, the UE may switch the active BWP of the UE to the default BWP. Meanwhile, the BWP may be defined for SL. The same SL BWP may be used in transmission and reception. For example, a transmitting UE may transmit a SL channel or a SL signal on a specific BWP, and a receiving UE may receive the SL channel or the SL signal on the specific BWP. In a licensed carrier, the SL BWP may be defined separately from a Uu BWP, and the SL BWP may have configuration signaling separate from the Uu BWP. For example, the UE may receive a configuration for the SL BWP from the BS/network. For example, the UE may receive a configuration for the Uu BWP from the BS/network. The SL BWP may be (pre-)configured in a carrier with respect to an out-of-coverage NR V2X UE and an RRC_IDLE UE. For the UE in the RRC_CONNECTED mode, at least one SL BWP may be activated in the carrier. FIG.5shows an example of a BWP, based on an embodiment of the present disclosure. The embodiment ofFIG.5may be combined with various embodiments of the present disclosure. It is assumed in the embodiment ofFIG.5that the number of BWPs is 3. Referring toFIG.5, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other end thereof. In addition, the PRB may be a resource block numbered within each BWP. A point A may indicate a common reference point for a resource block grid. The BWP may be configured by a point A, an offset NstartBWP from the point A, and a bandwidth NsizeBwp. For example, the point A may be an external reference point of a PRB of a carrier in which a subcarrier 0 of all numerologies (e.g., all numerologies supported by a network on that carrier) is aligned. For example, the offset may be a PRB interval between a lowest subcarrier and the point A in a given numerology. For example, the bandwidth may be the number of PRBs in the given numerology. Hereinafter, V2X or SL communication will be described. A sidelink synchronization signal (SLSS) may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS), as a SL-specific sequence. The PSSS may be referred to as a sidelink primary synchronization signal (S-PSS), and the SSSS may be referred to as a sidelink secondary synchronization signal (S-SSS). For example, length-127-M-sequences may be used for the S-PS S, and length-127 gold sequences may be used for the S-SSS. For example, a UE may use the S-PSS for initial signal detection and for synchronization acquisition. For example, the UE may use the S-PSS and the S-SSS for acquisition of detailed synchronization and for detection of a synchronization signal ID. A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for transmitting default (system) information which must be first known by the UE before SL signal transmission/reception. For example, the default information may be information related to SLSS, a duplex mode (DM), a time division duplex (TDD) uplink/downlink (UL/DL) configuration, information related to a resource pool, a type of an application related to the SLSS, a subframe offset, broadcast information, or the like. For example, for evaluation of PSBCH performance, in NR V2X, a payload size of the PSBCH may be 56 bits including 24-bit cyclic redundancy check (CRC). The S-PSS, the S-SSS, and the PSBCH may be included in a block format (e.g., SL synchronization signal (SS)/PSBCH block, hereinafter, sidelink-synchronization signal block (S-SSB)) supporting periodical transmission. The S-SSB may have the same numerology (i.e., SCS and CP length) as a physical sidelink control channel (PSCCH)/physical sidelink shared channel (PSSCH) in a carrier, and a transmission bandwidth may exist within a (pre-)configured sidelink (SL) BWP. For example, the S-SSB may have a bandwidth of 11 resource blocks (RBs). For example, the PSBCH may exist across 11 RBs. In addition, a frequency position of the S-SSB may be (pre-)configured. Accordingly, the UE does not have to perform hypothesis detection at frequency to discover the S-SSB in the carrier. FIG.6shows a procedure of performing V2X or SL communication by a UE based on a transmission mode, based on an embodiment of the present disclosure. The embodiment ofFIG.6may be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be called a mode or a resource allocation mode. Hereinafter, for convenience of explanation, in LTE, the transmission mode may be called an LTE transmission mode. In NR, the transmission mode may be called an NR resource allocation mode. For example, (a) ofFIG.6shows a UE operation related to an LTE transmission mode 1 or an LTE transmission mode 3. Alternatively, for example, (a) ofFIG.6shows a UE operation related to an NR resource allocation mode 1. For example, the LTE transmission mode 1 may be applied to general SL communication, and the LTE transmission mode 3 may be applied to V2X communication. For example, (b) ofFIG.6shows a UE operation related to an LTE transmission mode 2 or an LTE transmission mode 4. Alternatively, for example, (b) ofFIG.6shows a UE operation related to an NR resource allocation mode 2. Referring to (a) ofFIG.6, in the LTE transmission mode 1, the LTE transmission mode 3, or the NR resource allocation mode 1, a base station may schedule SL resource(s) to be used by a UE for SL transmission. For example, in step S600, a base station may transmit information related to SL resource(s) and/or information related to UL resource(s) to a first UE. For example, the UL resource(s) may include PUCCH resource(s) and/or PUS CH resource(s). For example, the UL resource(s) may be resource(s) for reporting SL HARQ feedback to the base station. For example, the first UE may receive information related to dynamic grant (DG) resource(s) and/or information related to configured grant (CG) resource(s) from the base station. For example, the CG resource(s) may include CG type 1 resource(s) or CG type 2 resource(s). In the present disclosure, the DG resource(s) may be resource(s) configured/allocated by the base station to the first UE through a downlink control information (DCI). In the present disclosure, the CG resource(s) may be (periodic) resource(s) configured/allocated by the base station to the first UE through a DCI and/or an RRC message. For example, in the case of the CG type 1 resource(s), the base station may transmit an RRC message including information related to CG resource(s) to the first UE. For example, in the case of the CG type 2 resource(s), the base station may transmit an RRC message including information related to CG resource(s) to the first UE, and the base station may transmit a DCI related to activation or release of the CG resource(s) to the first UE. In step S610, the first UE may transmit a PSCCH (e.g., sidelink control information (SCI) or 1st-stage SCI) to a second UE based on the resource scheduling. In step S620, the first UE may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S630, the first UE may receive a PSFCH related to the PSCCH/PSSCH from the second UE. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second UE through the PSFCH. In step S640, the first UE may transmit/report HARQ feedback information to the base station through the PUCCH or the PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first UE based on the HARQ feedback information received from the second UE. For example, the HARQ feedback information reported to the base station may be information generated by the first UE based on a pre-configured rule. For example, the DCI may be a DCI for SL scheduling. For example, a format of the DCI may be a DCI format 3_0 or a DCI format 3_1. Hereinafter, an example of DCI format 3_0 will be described. DCI format 3_0 is used for scheduling of NR PSCCH and NR PSSCH in one cell. The following information is transmitted by means of the DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI:Resource pool index—ceiling (log2I) bits, where I is the number of resource pools for transmission configured by the higher layer parameter sl-TxPoolScheduling.Time gap—3 bits determined by higher layer parameter sl-DCI-ToSL-TransHARQ process number—4 bitsNew data indicator—1 bitLowest index of the subchannel allocation to the initial transmission—ceiling (log2(NSLsubChannel)) bitsSCI format 1-A fields: frequency resource assignment, time resource assignment PSFCH-to-HARQ feedback timing indicator—ceiling (log2Nfb_timing) bits, where Nfb_timingis the number of entries in the higher layer parameter sl-PSFCH-ToPUCCH.PUCCH resource indicator—3 bitsConfiguration index—0 bit if the UE is not configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI; otherwise 3 bits. If the UE is configured to monitor DCI format 3_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3_0 with CRC scrambled by SL-RNTI.Counter sidelink assignment index—2 bits, 2 bits if the UE is configured with pdsch-HARQ-ACK-Codebook=dynamic, 2 bits if the UE is configured with pdsch-HARQ-ACK-Codebook=semi-staticPadding bits, if required Referring to (b) ofFIG.6, in the LTE transmission mode 2, the LTE transmission mode 4, or the NR resource allocation mode 2, a UE may determine SL transmission resource(s) within SL resource(s) configured by a base station/network or pre-configured SL resource(s). For example, the configured SL resource(s) or the pre-configured SL resource(s) may be a resource pool. For example, the UE may autonomously select or schedule resource(s) for SL transmission. For example, the UE may perform SL communication by autonomously selecting resource(s) within the configured resource pool. For example, the UE may autonomously select resource(s) within a selection window by performing a sensing procedure and a resource (re)selection procedure. For example, the sensing may be performed in a unit of subchannel(s). For example, in step S610, a first UE which has selected resource(s) from a resource pool by itself may transmit a PSCCH (e.g., sidelink control information (SCI) or 1st-stage SCI) to a second UE by using the resource(s). In step S620, the first UE may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S630, the first UE may receive a PSFCH related to the PSCCH/PSSCH from the second UE. Referring to (a) or (b) ofFIG.6, for example, the first UE may transmit a SCI to the second UE through the PSCCH. Alternatively, for example, the first UE may transmit two consecutive SCIs (e.g., 2-stage SCI) to the second UE through the PSCCH and/or the PSSCH. In this case, the second UE may decode two consecutive SCIs (e.g., 2-stage SCI) to receive the PSSCH from the first UE. In the present disclosure, a SCI transmitted through a PSCCH may be referred to as a 1stSCI, a first SCI, a 1st-stage SCI or a 1st-stage SCI format, and a SCI transmitted through a PSSCH may be referred to as a 2ndSCI, a second SCI, a 2nd-stage SCI or a 2nd-stage SCI format. For example, the 1st-stage SCI format may include a SCI format 1-A, and the 2nd-stage SCI format may include a SCI format 2-A and/or a SCI format 2-B. Hereinafter, an example of SCI format 1-A will be described. SCI format 1-A is used for the scheduling of PSSCH and 2nd-stage-SCI on PSSCH. The following information is transmitted by means of the SCI format 1-A:Priority—3 bitsFrequency resource assignment—ceiling (log2(NsLsubchannel(NsLsubchannel1+1)/2)) bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 2; otherwise ceiling log2(NSLsubChannel(NSLsubChannel+1)(2NSLsubChannel+1)/6) bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 3Time resource assignment—5 bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 2; otherwise 9 bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 3Resource reservation period—ceiling (log2Nrsv_period) bits, where Nrsv_periodis the number of entries in the higher layer parameter sl-ResourceReservePeriodList, if higher layer parameter sl-MultiReserveResource is configured; 0 bit otherwiseDMRS pattern—ceiling (log2Npattern) bits, where Npatternis the number of DMRS patterns configured by higher layer parameter sl-PSSCH-DMRS-TimePatternList2nd-stage SCI format—2 bits as defined in Table 5Beta_offset indicator—2 bits as provided by higher layer parameter sl-BetaOffsets2ndSCINumber of DMRS port—1 bit as defined in Table 6Modulation and coding scheme—5 bitsAdditional MCS table indicator—1 bit if one MCS table is configured by higher layer parameter sl-Additional-MCS-Table; 2 bits if two MCS tables are configured by higher layer parameter sl-Additional-MCS-Table; 0 bit otherwisePSFCH overhead indication—1 bit if higher layer parameter sl-PSFCH-Period=2 or 4; 0 bit otherwiseReserved—a number of bits as determined by higher layer parameter sl-NumReservedBits, with value set to zero. TABLE 5Value of 2nd-stage SCI2nd-stageformat fieldSCI format00SCI format 2-A01SCI format 2-B10Reserved11Reserved TABLE 6Value ofthe Numberof DMRSport fieldAntenna ports0100011000 1001 Hereinafter, an example of SCI format 2-A will be described. SCI format 2-A is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes ACK or NACK, when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. The following information is transmitted by means of the SCI format 2-A:HARQ process number—4 bitsNew data indicator—1 bitRedundancy version—2 bitsSource ID—8 bitsDestination ID—16 bitsHARQ feedback enabled/disabled indicator—1 bitCast type indicator—2 bits as defined in Table 7CSI request—1 bit TABLE 7Value of Casttype indicatorCast type00Broadcast01Groupcast when HARQ-ACKinformation includes ACK or NACK10Unicast11Groupcast when HARQ-ACKinformation includes only NACK Hereinafter, an example of SCI format 2-B will be described. SCI format 2-B is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. The following information is transmitted by means of the SCI format 2-B:HARQ process number—4 bitsNew data indicator—1 bitRedundancy version—2 bitsSource ID—8 bitsDestination ID—16 bitsHARQ feedback enabled/disabled indicator—1 bitZone ID—12 bitsCommunication range requirement—4 bits determined by higher layer parameter sl-ZoneConfigMCR-Index Referring to (a) or (b) ofFIG.6, in step S630, the first UE may receive the PSFCH. For example, the first UE and the second UE may determine a PSFCH resource, and the second UE may transmit HARQ feedback to the first UE using the PSFCH resource. Referring to (a) ofFIG.6, in step S640, the first UE may transmit SL HARQ feedback to the base station through the PUCCH and/or the PUSCH. FIG.7shows three cast types, based on an embodiment of the present disclosure. The embodiment ofFIG.7may be combined with various embodiments of the present disclosure. Specifically, (a) ofFIG.7shows broadcast-type SL communication, (b) ofFIG.7shows unicast type-SL communication, and (c) ofFIG.7shows groupcast-type SL communication. In case of the unicast-type SL communication, a UE may perform one-to-one communication with respect to another UE. In case of the groupcast-type SL transmission, the UE may perform SL communication with respect to one or more UEs in a group to which the UE belongs. In various embodiments of the present disclosure, SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, or the like. Hereinafter, a hybrid automatic repeat request (HARQ) procedure will be described. For example, the SL HARQ feedback may be enabled for unicast. In this case, in a non-code block group (non-CBG) operation, if the receiving UE decodes a PSCCH of which a target is the receiving UE and if the receiving UE successfully decodes a transport block related to the PSCCH, the receiving UE may generate HARQ-ACK. In addition, the receiving UE may transmit the HARQ-ACK to the transmitting UE. Otherwise, if the receiving UE cannot successfully decode the transport block after decoding the PSCCH of which the target is the receiving UE, the receiving UE may generate the HARQ-NACK. In addition, the receiving UE may transmit HARQ-NACK to the transmitting UE. For example, the SL HARQ feedback may be enabled for groupcast. For example, in the non-CBG operation, two HARQ feedback options may be supported for groupcast. (1) Groupcast option1: After the receiving UE decodes the PSCCH of which the target is the receiving UE, if the receiving UE fails in decoding of a transport block related to the PSCCH, the receiving UE may transmit HARQ-NACK to the transmitting UE through a PSFCH. Otherwise, if the receiving UE decodes the PSCCH of which the target is the receiving UE and if the receiving UE successfully decodes the transport block related to the PSCCH, the receiving UE may not transmit the HARQ-ACK to the transmitting UE. (2) Groupcast option2: After the receiving UE decodes the PSCCH of which the target is the receiving UE, if the receiving UE fails in decoding of the transport block related to the PSCCH, the receiving UE may transmit HARQ-NACK to the transmitting UE through the PSFCH. In addition, if the receiving UE decodes the PSCCH of which the target is the receiving UE and if the receiving UE successfully decodes the transport block related to the PSCCH, the receiving UE may transmit the HARQ-ACK to the transmitting UE through the PSFCH. For example, if the groupcast option1is used in the SL HARQ feedback, all UEs performing groupcast communication may share a PSFCH resource. For example, UEs belonging to the same group may transmit HARQ feedback by using the same PSFCH resource. For example, if the groupcast option2is used in the SL HARQ feedback, each UE performing groupcast communication may use a different PSFCH resource for HARQ feedback transmission. For example, UEs belonging to the same group may transmit HARQ feedback by using different PSFCH resources. In the present disclosure, HARQ-ACK may be referred to as ACK, ACK information, or positive-ACK information, and HARQ-NACK may be referred to as NACK, NACK information, or negative-ACK information. Hereinafter, UE procedure for determining the subset of resources to be reported to higher layers in PSSCH resource selection in sidelink resource allocation mode 2 will be described. In resource allocation mode 2, the higher layer can request the UE to determine a subset of resources from which the higher layer will select resources for PSSCH/PSCCH transmission. To trigger this procedure, in slot n, the higher layer provides the following parameters for this PSSCH/PSCCH transmission:the resource pool from which the resources are to be reported;L1 priority, prioTX;the remaining packet delay budget;the number of sub-channels to be used for the PSSCH/PSCCH transmission in a slot, LsubCH;optionally, the resource reservation interval, Prsvp_TX, in units of msec.if the higher layer requests the UE to determine a subset of resources from which the higher layer will select resources for PSSCH/PSCCH transmission as part of re-evaluation or pre-emption procedure, the higher layer provides a set of resources (r0, r1, r2, . . . ) which may be subject to re-evaluation and a set of resources (r′0, r′1, r′2, . . . ) which may be subject to pre-emption.it is up to UE implementation to determine the subset of resources as requested by higher layers before or after the slot r1″—T3, where r1″ is the slot with the smallest slot index among (r0, r1, r2, . . . ) and (r′0, r′1, r′2, . . . ), and T3is equal to TSLproc,1, where TSLproc,1is the number of slots determined based on the SCS configuration of the SL BWP. The following higher layer parameters affect this procedure:sl-SelectionWindowList: internal parameter T2minis set to the corresponding value from higher layer parameter sl-SelectionWindowList for the given value of prioTX.sl-Thres-RSRP-List: this higher layer parameter provides an RSRP threshold for each combination (pi, pj), where piis the value of the priority field in a received SCI format 1-A and pjis the priority of the transmission of the UE selecting resources; for a given invocation of this procedure, pj=prioTX.sl-RS-ForSensing selects if the UE uses the PSSCH-RSRP or PSCCH-RSRP measurement.sl-ResourceReservePeriodListsl-SensingWindow: internal parameter T0is defined as the number of slots corresponding to sl-SensingWindow msec.sl-TxPercentageList: internal parameter X for a given prioTXis defined as sl-TxPercentageList (prioTX) converted from percentage to ratio.sl-PreemptionEnable: if sl-PreemptionEnable is provided, and if it is not equal to ‘enabled’, internal parameter priopreis set to the higher layer provided parameter sl-PreemptionEnable. The resource reservation interval, Prsvp_TX, if provided, is converted from units of msec to units of logical slots, resulting in P′rsvp_TX. Notation: (t′SL0, t′SL1, t′SL2, . . . ) denotes the set of slots which belongs to the sidelink resource pool. For example, the UE may select a set of candidate resources (SA) based on Table 8. For example, if resource (re)selection is triggered, the UE may select a set of candidate resources (SA) based on Table 11. For example, if re-evaluation or pre-emption is triggered, the UE may select a set of candidate resources (SA) based on Table 8. TABLE 8The following steps are used:1) A candidate single-slot resource for transmission Rx,yis defined as a set of LsubCHcontiguous sub-channels with sub-channel x + j in slot ty′SLwhere j = 0, . . . , LsubCH− 1. The UE shall assume thatany set of LsubCHcontiguous sub-channels included in the corresponding resource pool within thetime interval [n + T1, n + T2] correspond to one candidate single-slot resource, whereselection of T1is up to UE implementation under 0 ≤ T1≤ Tproc,1SL, where Tproc,1SLis definedin slots in Table 8.1.4-2 where μSLis the SCS configuration of the SL BWP;if T2minis shorter than the remaining packet delay budget (in slots) then T2is up to UEimplementation subject to T2min≤ T2≤ remaining packet delay budget (in slots); otherwiseT2is set to the remaining packet delay budget (in slots).The total number of candidate single-slot resources is denoted by Mtotal.2) The sensing window is defined by the range of slots [n − T0, n − Tproc,0SL) where T0is defined aboveand Tproc,0SLis defined in slots in Table 8.1.4-1 where μSLis the SCS configuration of the SL BWP.The UE shall monitor slots which belongs to a sidelink resource pool within the sensing windowexcept for those in which its own transmissions occur. The UE shall perform the behaviour in thefollowing steps based on PSCCH decoded and RSRP measured in these slots.3) The internal parameter Th(pi, pj) is set to the corresponding value of RSRP threshold indicated bythe i-th field in sl-Thres-RSRP-List, where i = pi+ (pj− 1) * 8.4) The set SAis initialized to the set of all the candidate single-slot resources.5) The UE shall exclude any candidate single-slot resource Rx,yfrom the set SAif it meets all thefollowing conditions:the UE has not monitored slot tm′SLin Step 2.for any periodicity value allowed by the higher layer parameter sl-ResourceReservePeriodList anda hypothetical SCI format 1-A received in slot tm′SLwith ′Resource reservation period′ field set tothat periodicity value and indicating all subchannels of the resource pool in this slot, condition c instep 6 would be met.5a) If the number of candidate single-slot resources Rx,yremaining in the set SAis smaller than X ·Mtotal, the set SAis initialized to the set of all the candidate single-slot resources as in step 4.6) The UE shall exclude any candidate single-slot resource Rx,yfrom the set SAif it meets all thefollowing conditions:a) the UE receives an SCI format 1-A in slot tm′SL, and ′Resource reservation period′ field, if present,and ′Priority′ field in the received SCI format 1-A indicate the values Prsvp_RX and prioRX,respectively;b) the RSRP measurement performed, for the received SCI format 1-A, is higher thanTh(prioRX, prioTX);c) the SCI format received in slot tm′SLor the same SCI format which, if and only if the ′Resourcereservation period′ field is present in the received SCI format 1-A, is assumed to be received inslot(s) tm+q×Prsvp_RX′′SLdetermines the set of resource blocks and slots which overlaps withRx,y+j×Prsvp_TX′for q = 1, 2, . . . , Q and j = 0, 1, . . . , Creset− 1. Here, Prsvp_RX′ is Prsvp_RX convertedtounitsoflogicalslots,Q=⌈TscalPrsvp_RX⌉ifPrsvp_RX<Tscalandn′-m≤Prsvp_RX′,wheretn′′SL= n if slot n belongs to the set (t0′SL, t1′SL, . . . , tT′max−1′SL), otherwise slot tn′′SLis the first slotafter slot n belonging to the set (t0′SL, t1′SL, . . . , tT′max−1′SL) otherwise Q = 1. Tscalis set toselection window size T2converted to units of msec.7) If the number of candidate single-slot resources remaining in the set SAis smaller than X · Mtotal,then Th(pi, pj) is increased by 3 dB for each priority value Th(pi, pj) and the procedure continueswith step 4.The UE shall report set SAto higher layers.If a resource rifrom the set (r0, r1, r2, . . .) is not a member of SA, then the UE shall report re-evaluation ofthe resource rito higher layers.If a resource ri′ from the set (r0′, r1′, r2′, . . .) meets the conditions below then the UE shall report pre-emptionof the resource ri′ to higher layersri′ is not a member of SA, andri′ meets the conditions for exclusion in step 6, with Th(prioRX, prioTX) set to the final thresholdafter executing steps 1)-7), i.e. including all necessary increments for reaching X · Mtotal, andthe associated priority prioRX, satisfies one of the following conditions:sl-PreemptionEnable is provided and is equal to ′enabled′ and prioTX> prioRXsl-PreemptionEnable is provided and is not equal to ′enabled′, and prioRX< priopreandprioTX> prioRX Meanwhile, partial sensing may be supported for power saving of the UE. For example, in LTE SL or LTE V2X, the UE may perform partial sensing based on Tables 9 and 10. TABLE 9In sidelink transmission mode 4, when requested by higher layers in subframe n for a carrier, the UE shalldetermine the set of resources to be reported to higher layers for PSSCH transmission according to the stepsdescribed in this Subclause. Parameters LsubCHthe number of sub-channels to be used for the PSSCHtransmission in a subframe, Prsvp_TX the resource reservation interval, and prioTXthe priority to betransmitted in the associated SCI format 1 by the UE are all provided by higher layers.In sidelink transmission mode 3, when requested by higher layers in subframe n for a carrier, the UE shalldetermine the set of resources to be reported to higher layers in sensing measurement according to the stepsdescribed in this Subclause. Parameters LsubCH, Prsvp_TX and prioTXare all provided by higher layers.Creselis determined by Cresel= 10 * SL_RESOURCE_RESELECTION_COUNTER, whereSL_RESOURCE_RESELECTION_COUNTER is provided by higher layers.If partial sensing is configured by higher layers then the following steps are used:1) A candidate single-subframe resource for PSSCH transmission Rx,yis defined as a set of LsubCHcontiguous sub-channels with sub-channel x + j in subframe tySLwhere j = 0, . . . , LsubCH− 1. TheUE shall determine by its implementation a set of subframes which consists of at least Y subframeswithin the time interval [n + T1, n + T2] where selections of T1and T2are up to UEimplementations under T1≤ 4 and T2min(prioTX) ≤ T2≤ 100, if T2min(prioTX) is provided byhigher layers for prioTX, otherwise 20 ≤ T2≤ 100. UE selection of T2shall fulfil the latencyrequirement and Y shall be greater than or equal to the high layer parameter minNumCandidateSF.The UE shall assume that any set of LsubCHcontiguous sub-channels included in the correspondingPSSCH resource pool within the determined set of subframes correspond to one candidate single-subframe resource. The total number of the candidate single-subframe resources is denoted by Mtotal.2) If a subframe tySLis included in the set of subframes in Step 1, the UE shall monitor any subframety−k×PstepSLif k-th bit of the high layer parameter gapCandidateSensing is set to 1. The UE shall performthe behaviour in the following steps based on PSCCH decoded and S-RSST measured in thesesubframes.3) The parameter Tha,bis set to the value indicated by the i-th SL-ThresPSSCH-RSRP field in SL-ThresPSSCH-RSRP-List where i = (a − 1) * 8 + b.4) The set SAis initialized to the union of all the candidate single-subframe resources. The set SBisinitialized to an empty set.5) The UE shall exclude any candidate single-subframe resource Rx,yfrom the set SAif it meets allthe following conditions:the UE receives an SCI format 1 in subframe tmSL, and ″Resource reservation″ field and ″Priority″field in the received SCI format 1 indicate the values Prsvp_RX and prioRX, respectively.PSSCH-RSRP measurement according to the received SCI format 1 is higher than ThprioTX,prioRX.the SCI format received in subframe tmSLor the same SCI format 1 which is assumed to be receivedin subframe(s) tm+q×Pstep×Prsvp_RXSLdetermines according to 14.1.1.4C the set of resource blocks andsubframes which overlaps with Rx,y+j×Prsvp_TX′for q = 1, 2, . . . , Q and j = 0, 1, . . . , Cresel− 1. Here,Q=1Prsvp_RXifPrsvp_RX<1andy′-m≤Pstep×Prsvp_RX+Pstep,wherety′SListhelast subframe of the Y subframes, and Q = 1 otherwise.6) If the number of candidate single-subframe resources remaining in the set SAis smaller than0.2 · Mtotal, then Step 4 is repeated with Tha,bincreased by 3 dB. TABLE 107) For a candidate single-subframe resource Rx,yremaining in the set SA, the metric Ex,yis definedas the linear average of S-RSSI measured in sub-channels x+k for k = 0, . . . , LsubCH- 1 in themonitored subframes in Step 2 that can be expressed by ty-Pstep*jSLfor a non-negative integer j.8) The UE moves the candidate single-subframe resource Rx,ywith the smallest metric Ex,yfrom theset SAto SB. This step is repeated until the number of candidate single-subframe resources in theset SBbecomes greater than or equal to 0.2 · Mtotal.9) When the UE is configured by upper layers to transmit using resource pools on multiple carriers, itshall exclude a candidate single-subframe resource Rx,yfrom SBif the UE does not supporttransmission in the candidate single-subframe resource in the carrier under the assumption thattransmissions take place in other carrier(s) using the already selected resources due to its limitation inthe number of simultaneous transmission carriers, its limitation in the supported carrier combinations,or interruption for RF retuning time.The UE shall report set SBto higher layers.If transmission based on random selection is configured by upper layers and when the UE is configured byupper layers to transmit using resource pools on multiple carriers, the following steps are used:1) A candidate single-subframe resource for PSSCH transmission Rx,yis defined as a set of LsubCHcontiguous sub-channels with sub-channel x+j in subframe tySLwhere j = 0, . . . , LsubCH- 1. TheUE shall assume that any set of LsubCHcontiguous sub-channels included in the correspondingPSSCH resource pool within the time interval [n + T1, n + T2] corresponds to one candidate single-subframe resource, where selections of T1and T2are up to UE implementations under T1≤ 4and T2min(prioTX) ≤ T2≤ 100, if T2min(prioTX) is provided by higher layers for prioTX,otherwise 20 ≤ T2≤ 100. UE selection of T2shall fulfil the latency requirement. The total numberof the candidate single-subframe resources is denoted by Mtotal.2) The set SAis initialized to the union of all the candidate single-subframe resources. The set SBisinitialized to an empty set.3) The UE moves the candidate single-subframe resource Rx,yfrom the set SAto SB.4) The UE shall exclude a candidate single-subframe resource Rx,yfrom SBif the UE does notsupport transmission in the candidate single-subframe resource in the carrier under the assumption thattransmissions take place in other carrier(s) using the already selected resources due to its limitation inthe number of simultaneous transmission carriers, its limitation in the supported carrier combinations,or interruption for RF retuning time.The UE shall report set SBto higher layers. Meanwhile, the conventional candidate resource selection method has a problem of performance (or capability) degradation, which is caused by applying only random selection for a first packet of periodic transmission. Meanwhile, when a UE performs partial sensing, the UE needs to determine a range of partial sensing (e.g., range/number of slots being the target (or object) of partial sensing). For example, when the partial sensing range is not defined, the UE may perform monitoring during a relatively long time period (or time duration), and this may cause unnecessary power consumption of the UE. For example, when the partial sensing range is not defined, the UE may perform monitoring during a relatively short time period (or time duration). In this case, the UE may not determine resource conflict (or resource collision) with another UE, and, due to such resource conflict, reliability in SL transmission may not be ensured. In the present disclosure, partial sensing may include periodic-based partial sensing (PPS) or continuous partial sensing (CPS). In the present disclosure, PPS may also be referred to as PBPS. According to various embodiments of the present disclosure, proposed herein are a method for selectively applying random selection and CPS based resource selection for the first packet of a periodic transmission and an apparatus supporting the same. According to various embodiments of the present disclosure, proposed herein are an SL transmission resource selection method and an apparatus supporting the same that can minimize power consumption of the UE, when the UE is operating based on partial sensing. For example, in various embodiments of the present disclosure, when performing sensing for resource selection, based on a number of cycle periods corresponding to a specific configuration value, periodic-based partial sensing (PPS) may mean an operation performing sensing at time points corresponding to an integer multiple (k) of each cycle period. For example, the cycle periods may be cycle periods of transmission resource configured in a resource pool. For example, PPS may sense resource of a time point temporally preceding a time point of a candidate resource, which is to be a target that determines resource conflict, as much as the integer multiple k value of each cycle period. For example, the k value may be configured to have a bitmap format. FIG.8andFIG.9respectively show a method for performing PPS, by a UE, in accordance with an embodiment of the present disclosure.FIG.8andFIG.9may be combined with various embodiments of the present disclosure. In the embodiments ofFIG.8andFIG.9, it is assumed that a resource reservation cycle period that is allowed for a resource pool or a resource reservation cycle period that is configured for PPS are P1 and P2, respectively. Furthermore, it is assumed that a UE performs partial sensing (i.e., PPS) for selecting SL resource within slot #Y1. ReferringFIG.8, a UE may perform sensing for a slot that precedes slot #Y1 (or that is located before slot #Y1) by P1 and a slot that precedes slot #Y1 by P2. ReferringFIG.9, a UE may perform sensing for a slot that precedes slot #Y1 (or that is located before slot #Y1) by P1 and a slot that precedes slot #Y1 by P2. Furthermore, optionally, the UE may perform sensing for a slot that precedes slot #Y1 by A*P1 and a slot that precedes slot #Y1 by B*P2. For example, A and B may be positive integers that are equal to or greater than 2. More specifically, for example, a UE that has selected slot #Y1 as a candidate slot may perform sensing for slot #(Y1-resource reservation cycle period*k), and k may be a bitmap. For example, when k is equal to 10001, a UE that has selected slot #Y1 as a candidate slot may perform sensing for slot #(Y1-P1*1), slot #(Y1-P1*5), slot #(Y1-P2*1), and slot #(Y1-P2*5). For example, in various embodiments of the present disclosure, continuous partial sensing (CPS) may mean an operation performing sensing for all or part of a time domain that is given as a specific configuration value. For example, CPS may include a short-term sensing operation that performs sensing during a relatively short time period (or time duration). FIG.10shows a method for performing CPS, by a UE, in accordance with an embodiment of the present disclosure.FIG.10may be combined with various embodiments of the present disclosure. In the embodiment ofFIG.10, it is assumed that Y number of candidate slots that are selected by a UE are slot #M, slot #(M+T1), and slot #(M+T1+T2). In this case, the slot(s) for which the UE should perform sensing may be determined based on a first slot (i.e., slot #M) among the Y number of candidate slots. For example, after determining the first slot among the Y number of candidate slots as a reference slot, the UE may perform sensing for N number of slots (preceding) from the reference slot. Referring toFIG.10, based on the first slot (i.e., slot #M) among the Y number of candidate slots, the UE may perform sensing on N number of slots. For example, the UE may perform sensing for N number of slots preceding slot #M, and the UE may select at least one SL resource from within the Y number of candidate slots (i.e., slot #M, slot #(M+T1), and slot #(M+T1+T2)), based on the sensing result. For example, N may be configured for the UE or may be pre-configured. For example, among the N number of slots, a time gap for processing may exist between the last slot and slot #M. In an embodiment of the present disclosure, REV may mean resource re-evaluation, and PEC may mean resource pre-emption checking. In an embodiment of the present disclosure, when a transmission resource selection is initially triggered for transmitting a random packet, a resource selection window for performing sensing (e.g., full, partial sensing) may be selected, and a “candidate resource/slot” may mean resource that is selected for detecting the occurrence or non-occurrence of resource conflict within the resource selection window, a “valid resource/slot” is a resource that has been determined to be valid (or effective) for transmission, since resource conflict has not been detected among the candidate resources based on the sensing, and, then, reported from a PHY layer to a MAC layer, and a “transmission resource/slot” may mean a resource that has been finally selected, by the MAC layer, among the reported resources, in order to be used for an SL transmission. FIG.11is a diagram for describing problems of a method for performing wireless communication based on SL resource, in accordance with an embodiment of the present disclosure.FIG.11may be combined with various embodiments of the present disclosure. Referring toFIG.11, according to an embodiment of the present disclosure, for example, an RX UE may perform an SL DRX operation based on SL DRX configuration. For example, an RX UE may perform reception/monitoring of a TB (e.g., or MAC PDU) (e.g., reception/monitoring of a PSCCH/PSSCH) within an SL DRX active time. For example, an RX UE may not perform reception/monitoring of a TB (e.g., or MAC PDU) (e.g., reception/monitoring of a PSCCH/PSSCH) within an SL DRX inactive time. For example, a TX UE may select a candidate resource from a set of candidate resources (e.g., candidate single-slot resources) that are initialized within a selection window. For example, a TX UE may monitor a slot belonging to an SL resource pool within a sensing window and in a region excluding slots in which transmission of a TX UE occurs. For example, a TX UE may measure a reference signal received power (RSRP) from the slot and may select an SL resource based on the measured RSRP and decoding of the PSCCH. For example, a TX UE may perform RSRP measurement based on a first SCI, and, when the RSRP is higher (or greater) than an RSRP threshold (e.g., an RSRP threshold that is determined based on a transmission (L1) priority (prioTX) and a reception priority (prioRX) included in the received first SCI), the TX UE may exclude candidate resources being related to the first SCI based on partial sensing or full sensing. For example, for the TX UE, when a remaining number of candidate resources is less than a threshold (e.g., a value multiplying a total number of candidate resources (e.g., M) by a parameter (e.g., X, a value between 0 and 1) that is related to a transmission priority (e.g., prioTX)), the RSRP threshold may be incremented (or increased) N number of times as much as a predetermined step value (e.g., 3 dB). For example, N may be equal to 0 or may be a positive integer. For example, a TX UE may perform exclusion of candidate resources based on the (e.g., incremented (or increased)) RSRP threshold. For example, the TX UE may report, to a MAC layer, valid resource(s)/slot(s) being selected (e.g., remaining after the exclusion) based on partial sensing or full sensing among the candidate resources/slots within a selection window. For example, the TX UE may perform SL communication with an RX UE based on an SL resource/slot that is finally selected, by the MAC layer, in order to be used for SL transmission among the reported resources. For example, the candidate resource/slot may be selected within the selection window and within a region excluding the SL DRX active time (e.g., an SL DRX inactive time within an SL DRX cycle) based on the sensing. For example, the TX UE may perform SL communication with an RX UE based on the SL resource/slot that is finally selected from among candidate resources/slots that are selected from the region excluding the SL DRX active time. In this case, for example, when the TX UE selects an SL resource based on full sensing or continuous partial sensing (CPS), the TX UE may perform unnecessary (re-)transmission due to an SL DRX operation of the RX UE. For example, when the TX UE selects an SL resource based on periodic-based partial sensing (PBPS), the TX UE may continuously perform unnecessary (re-)transmission due to the SL DRX operation of the RX UE. For example, power of the TX UE and the RX UE may be wasted. For example, the SL resource of the TX UE that is selected based on resource allocation mode 2 (e.g., or mode 4) may be wasted. According to an embodiment of the present disclosure, for example, partial sensing may be operated in combination with SL discontinuous reception (DRX). For example, when a UE performing partial sensing during SL DRX operation performs periodic transmission, and when the UE selects a candidate resource, and, by applying an RSRP threshold value, the UE may not be capable of efficiently selecting a resource. According to an embodiment of the present disclosure, a UE performing partial sensing during SL DRX operation may adaptively select an RSRP threshold value, and the UE may efficiently select a resource. According to an embodiment of the present disclosure, when a power-saving UE performs partial sensing based resource allocation while performing an SL-DRX operation at the same time, the TX UE performing the SL DRX operation may select a transmission resource based on (or while considering) the SL-DRX configuration on an RX UE. According to an embodiment of the present disclosure, for example, the TX UE may perform initial transmission or partial re-transmission on a packet that is to be transmitted during or (within) an ON period (or duration) or SL DRX Active time period of the RX UE, and the TX UE may anticipate (or expect) the RX UE to extend its SL DRX Active time period based on the initial transmission and the partial re-transmission, and the TX UE may perform the remaining re-transmission excluding the initial transmission and the partial re-transmission during the expected extended SL DRX Active time period. As an embodiment of the present disclosure, for example, when the TX UE performs periodic transmission, and/or when a length (or duration) of the ON or SL DRX Active time period of the RX UE is less than or equal to a specific threshold value, as compared to a length of a Packet Delay Budget (PDB) or resource selection window of a packet that is to be transmitted, a maximum (or highest) reference signal received power (RSRP) threshold value (e.g., maximum (or highest) RSRP threshold value that is used for determining whether or not a resource conflict occurs when the TX UE selects a resource based on partial sensing) and/or an RSRP step value (e.g., the RSRP unit being a unit that increases the RSRP threshold when the number of valid resources is insufficient) may be configured as a specific threshold value. As an embodiment of the present disclosure, for example, when the TX UE selects a valid resource within the ON or SL DRX Active time period of the RX UE, even if the RSRP threshold value increases up to the aforementioned maximum (or highest) value in order to meet with (or satisfy) a target resource ratio that is configured as a specific threshold value, in case the number of valid resources that can be selected by the TX UE fails to satisfy the target resource ratio, the TX UE may select a valid resource for a period that is expected to have the ON or SL DRX Active time period of the RX UE extended based on the transmission during the ON or SL DRX Active time period. For example, even if the RSRP threshold value increases up to the highest (or maximum) value for the period for which the extension of the ON or SL DRX Active time period of the RX UE is expected, if the number/ratio of valid resources does not satisfy the target resource number/target resource ratio, the TX UE may select a valid resource while increasing the RSRP threshold value to its maximum (or highest) value within a PDB or resource selection window period of the remaining packet(s) that is/are to be transmitted. For example, in case the number/ratio of valid resources fail(s) to satisfy the target resource number/target resource ratio even if the RSRP threshold value within the PDB or resource selection window period of the remaining packet(s) that is/are to be transmitted is increased up to the highest (or maximum) value, the TX UE may cancel the maximum RSRP threshold value, and the TX UE may select a valid resource while assuming an infinite maximum value and incrementing (or increasing) the RSRP threshold value by an order of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining PDB or resource selection window period. As an embodiment of the present disclosure, for example, the maximum RSRP threshold value and/or RSRP step value that is/are used for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining PDB or resource selection window period may be separately configured so as to be different from one another. As an embodiment of the present disclosure, for example, a common or separate highest RSRP threshold value may be configured for all or part of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining PDB or resource selection window period. As an embodiment of the present disclosure, for example, the RSRP step value that is applied to the ON or SL DRX Active time period may be configured to have a greater value than the RSRP step value that is applied to the expected extended SL DRX time Active time period or the remaining resource selection window period. As an embodiment of the present disclosure, for example, the maximum RSRP threshold value that is used for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining PDB or resource selection window period may each be separately configured to have the maximum value cancelled or increased up to an infinite value. As an embodiment of the present disclosure, for example, the RSRP step value that is applied to the ON or SL DRX Active time period may be configured to have a greater value than the RSRP step value that is applied to the expected extended SL DRX time Active time period or the remaining resource selection window period. As an embodiment of the present disclosure, for example, the maximum RSRP threshold value that is used for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining PDB or resource selection window period may each be separately configured to have the maximum value cancelled or increased up to an infinite value. As an embodiment of the present disclosure, for example, when the TX UE selects a valid resource from among candidate resources based on partial sensing within a resource selection window, initially, the RSRP threshold value may be commonly applied to the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining resource selection window period. For example, according to the resource selection process, as the RSRP threshold value is sequentially increased as much as a specific configuration value, after the number/ratio of candidate resources for a whole resource selection window satisfies target resource number #1/target resource ratio #1 being configured as a specific threshold value, when the number/ratio of valid resources within the ON or SL DRX Active time period is less than target resource number #2/target resource ratio #2 being configured as a specific threshold value, as the TX UE sequentially increases the RSRP threshold value as much as the specific configuration value only for the ON or SL DRX Active time period, the TX UE may select additional valid resources only for the ON or SL DRX Active time period until the target resource number #2/target resource ratio #2 is/are satisfied. For example, (e.g., as the RSRP threshold value is sequentially increased as much as a specific configuration value,) after the number/ratio of candidate resources for a whole resource selection window satisfies target resource number #1/target resource ratio #1 being configured as a specific threshold value, when the number/ratio of valid resources within the ON or SL DRX Active time period is less than target resource number #2/target resource ratio #2 being configured as a specific threshold value, (e.g., as the TX UE sequentially increases the RSRP threshold value as much as the specific configuration value only for the ON or SL DRX Active time period) the TX UE may select additional valid resources only for the ON or SL DRX Active time period until the target resource number #2/target resource ratio #2 is/are satisfied. As an embodiment of the present disclosure, for example, when an SL DRX active time of the RX UE is provided by a higher layer (e.g., a radio resource control (RRC) layer) and when candidate single-slot resources remained within the SL DRX active time is not present in the set, based on its implementation, the UE may perform additional selection, and the set SA may include at least one candidate single-slot resource within the SL DRX active time. FIG.12is a diagram for describing a method for performing wireless communication based on SL resource, in accordance with an embodiment of the present disclosure.FIG.12may be combined with various embodiments of the present disclosure. Referring toFIG.12, according to an embodiment of the present disclosure, for example, an RX UE may perform an SL DRX operation based on SL DRX configuration. For example, an RX UE may perform reception/monitoring of a TB (e.g., or MAC PDU) (e.g., reception/monitoring of a PSCCH/PSSCH) within an SL DRX active time. For example, an RX UE may not perform reception/monitoring of a TB (e.g., or MAC PDU) (e.g., reception/monitoring of a PSCCH/PSSCH) within an SL DRX inactive time. For example, a TX UE may select a candidate resource from a set of candidate resources (e.g., candidate single-slot resources) that are initialized within a selection window. For example, a TX UE may monitor a slot belonging to an SL resource pool within a sensing window and in a region excluding slots in which transmission of a TX UE occurs. For example, a TX UE may measure a reference signal received power (RSRP) from the slot and may select an SL resource based on the measured RSRP and decoding of the PSCCH. For example, a TX UE may perform RSRP measurement based on a first SCI, and, when the RSRP is higher (or greater) than an RSRP threshold (e.g., an RSRP threshold that is determined based on a transmission (L1) priority (prioTX) and a reception priority (prioRX) included in the received first SCI), the TX UE may exclude candidate resources being related to the first SCI based on partial sensing or full sensing. For example, for the TX UE, when a remaining number of candidate resources is less than a threshold (e.g., a value multiplying a total number of candidate resources (e.g., M) by a parameter (e.g., X, a value between 0 and 1) that is related to a transmission priority (e.g., prioTX)), the RSRP threshold may be incremented (or increased) N number of times as much as a predetermined step value (e.g., 3 dB). For example, N may be equal to 0 or may be a positive integer. For example, a TX UE may perform sensing and exclusion of candidate resources based on the (e.g., incremented (or increased)) RSRP threshold. For example, based on sensing, the TX UE may determine whether a number of remained candidate resources/slots within an SL DRX active time of an RX UE, among a set of selected candidate resources/slots (e.g., candidate resources/slots remaining after exclusion), is less than a threshold value. For example, the threshold value may be integer that is equal to or greater than 1. For example, when the number of remained candidate resources/slots within the SL DRX active time of the RX UE is less than the threshold value, the TX UE may additionally select at least one or more candidate resources/slots within the SL DRX active time (e.g., within the SL DRX active time within an SL DRX cycle) of the RX UE. For example, when there are no remained candidate resources/slots within the SL DRX active time of the RX UE, the TX UE may additionally select at least one or more candidate resources/slots within the SL DRX active time (e.g., within the SL DRX active time within an SL DRX cycle) of the RX UE. For example, the TX UE may report, to the MAC layer, the additionally selected candidate resources/slots. For example, the TX UE may perform SL communication with the RX UE based on the finally selected SL resources/slots, among the reported resources, in order to be used, by the MAC layer, for SL transmission. Therefore, according to an embodiment of the present disclosure, for example, when the TX UE selects an SL resource based on full sensing or continuous partial sensing (CPS), the TX UE may not perform unnecessary (re-)transmission due to an SL DRX operation of the RX UE. For example, when the TX UE selects an SL resource based on periodic-based partial sensing (PBPS), the TX UE may not continuously perform unnecessary (re-)transmission due to the SL DRX operation of the RX UE. For example, power of the TX UE and the RX UE may not be wasted. For example, the SL resource of the TX UE that is selected based on resource allocation mode 2 (e.g., or mode 4) may not be wasted. FIG.13is a diagram for describing a procedure of performing wireless communication based on SL resource, in accordance with an embodiment of the present disclosure.FIG.13may be combined with various embodiments of the present disclosure. Referring toFIG.13, in step S1310, a TX UE and/or an RX UE may obtain SL DRX configuration including information related to an SL DRX active time. For example, the TX UE may transmit an SL DRX configuration to the RX UE based on a PC5-RRC connection, and the like. In step S1320, for example, the TX UE may trigger resource selected from slot n. In step S1330, for example, the TX UE may determine a selection window based on the slot n. In step S1340, for example, the TX UE may select at least one first candidate resource within the selection window. In step S1350, for example, whether or not remained candidate resources (e.g., candidate single-slot resources) are present during or (within) the SL DRX active time may be determined. For example, the TX UE may determine whether or not remained candidate resources (e.g., candidate single-slot resources) are present within the SL DRX active time. In step S1352, for example, when there are no remained candidate resources (e.g., candidate single-slot resources) within the SL DRX active time, the TX UE may additionally select at least one second candidate resource within the SL DRX active time. In step S1360, for example, when at least one or more remained candidate resources (e.g., candidate single-slot resources) are present within the SL DRX active time, the TX UE may report the at least one first candidate resource to a higher layer (e.g., MAC layer) from a physical layer (PHY layer). For example, when there are no remained candidate resources (e.g., candidate single-slot resources) present within the SL DRX active time, the TX UE may report the at least one second candidate resource to a higher layer (e.g., MAC layer) from a physical layer (PHY layer). In step S1370, for example, the TX UE (e.g., a higher layer of the TX UE) may select an SL resource from among the candidate resources (e.g., at least one first candidate resource and/or at least one second candidate resource). In step S1380, for example, the TX UE may transmit a first SCI to the RX UE through a PSCCH, based on the SL resource (e.g., over the SL resource). In step S1390, for example, the TX UE may transmit a second SCI and a MAC PDU to the RX UE through a PSSCH, based on the SL resource (e.g., over the SL resource). An embodiment of the present disclosure may have various effects. For example, according to an embodiment of the present disclosure, when a UE performing an SL DRX operation selects a transmission resource based on partial sensing, an RSRP threshold value may be applied based on an SL DRX configuration of the RX UE. According to an embodiment of the present disclosure, for example, the TX UE may efficiently select a candidate resource based on the SL DRX operation of the RX UE. According to an embodiment of the present disclosure, for example, the TX UE may efficiently select a candidate resource so as to minimize resource conflict based on the SL DRX operation of the RX UE. According to an embodiment of the present disclosure, for example, by having the TX UE efficiently select a candidate resource so as to minimize resource conflict based on the SL DRX operation of the RX UE, power consumption caused by unnecessary (re-)transmission during a time period that is not the SL DRX active time of the RX UE may be minimized. According to an embodiment of the present disclosure, for example, by having the TX UE efficiently select a candidate resource so as to minimize resource conflict based on the SL DRX operation of the RX UE, waste of resource caused by unnecessary (re-)transmission during a time period that is not the SL DRX active time of the RX UE may be minimized. As an embodiment of the present disclosure, for example, when the TX UE selects a valid resource from among the candidate resources based on partial sensing within the resource selection window, for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining resource selection window period, the target resource number/target resource ratio may be separately configured so as to be different from one another. For example, as the TX UE sequentially increases the RSRP threshold value until each target resource number/target resource ratio is satisfied for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining resource selection window period, the TX UE may select a valid resource in each period. As an embodiment of the present disclosure, for example, the target resource number/target resource ratio, RSRP threshold, RSRP step (increment) values, which are separately configured so as to be different from one another for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining PDB or resource selection window period, may be determined based on channel congestion or interference level, Channel Busy Ratio (CBR)/Channel Occupancy Ratio (CR), PDB, transmission packet priority, minimum communication range requirement for a transmission packet, total number of (re-)transmissions/remaining number of retransmissions for a transmission packet, number of candidate/valid/transmission resources, resource selection window length, configuration or non-configuration of re-evaluation (REV)/pre-emption checking (PEC), cast type, size of packet that is to be transmitted, configuration or non-configuration of HARQ feedback enabled, and so on. As an embodiment of the present disclosure, for example, when the TX UE selects a valid resource from among candidate resources based on partial sensing within the resource selection window, and when the target resource number/target resource ratio is/are not satisfied for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining resource selection window period, the TX UE may align (or match) the transmission time points of the TX UE for each period or within the whole resource selection window so as to re-include the excluded valid resources or transmission resources and may then select the re-included resources as the valid resource or transmission resource. As an embodiment of the present disclosure, for example, when the TX UE selects a valid resource from among candidate resources based on partial sensing within the resource selection window, when the target resource number/target resource ratio is/are not satisfied for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining resource selection window period, or, for example, even if the transmission time points of the TX UE for each period or within the whole resource selection window are aligned (or matched) so as to re-include the excluded valid resources or transmission resources and then select the re-included resources as the valid resource or transmission resource, when the target resource number/target resource ratio is/are not satisfied for each of the ON or SL DRX Active time period, the expected extended SL DRX time Active time period, and the remaining resource selection window period, the UE (e.g., based on its implementation) may configure a partial sensing window or resource selection window so that the target resource number/target resource ratio for each of the aforementioned periods can be satisfied. For example, the TX UE may reduce a partial sensing window period that is required for resource selection before the resource selection window (e.g., contiguous partial sensing (CPS) period), and, thus, the TX UE may extend the resource selection window. As an embodiment of the present disclosure, for example, in order to allow the RX UE to extend the ON or SL DRX Active time period and receive the remaining re-transmission(s) based on the transmission during the ON or SL DRX Active time period, since the likelihood of success in the transmission during the ON or SL DRX Active time period should be high, among the valid resources within the resource selection window that is reported from the PHY layer, the MAC layer of the TX UE may preferentially select a transmission resource within the ON or SL DRX Active time period from among resources having RSRP measurement values that are less than or equal to a specific threshold value among the resources within the ON or SL DRX Active time period. As an embodiment of the present disclosure, for example, although the number/ratio of valid resources within the ON or SL DRX Active time period have been selected to be greater than or equal to the number/ratio of target valid resources of the corresponding period, when a number of valid resources within an OFF period has been selected to be less than a number of target valid resources of the corresponding period, or, for example, when a total number of valid resources within the resource selection window is selected to be less than a total number of target valid resources, the TX UE may additionally increase only the RSRP threshold for the OFF period, or the TX UE may cancel the maximum RSRP threshold value for the OFF period, or the TX UE may increase the RSRP step value for the OFF period. As an embodiment of the present disclosure, for example, the TX UE may re-include the excluded resources, which were excluded due to overlapping transmission time points of the UE for the OFF period, as candidate/valid resources, or the TX UE may secure additional candidate/valid resources for the OFF period by additionally extending the resource selection window. As an embodiment of the present disclosure, for example, in order to allow the MAC layer of the TX UE to determine and to allow the PHY layer of the TX UE to perform, the TX UE may configure related parameters (e.g., cancelling maximum RSRP threshold value, increasing RSRP step, extending resource selection window, and so on), so as to be capable of performing operations according to the embodiment of the present disclosure, or, for example, the TX UE may perform the operations according to the embodiment of the present disclosure by having the PHY layer determine on its own. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a service type. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) (LCH or service) priority. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) QoS requirements (e.g., latency, reliability, minimum communication range). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) PQI parameters. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) HARQ feedback ENABLED LCH/MAC PDU (transmission). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) HARQ feedback DISABLED LCH/MAC PDU (transmission). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a CBR measurement value of a resource pool. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) an SL cast type (e.g., unicast, groupcast, broadcast). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) an SL groupcast HARQ feedback option (e.g., NACK only feedback, ACK/NACK feedback, TX-RX range-based NACK only feedback). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) SL mode 1 CG type (e.g., SL CG type 1 or SL CG type 2). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) SL mode type (e.g., mode 1 or mode 2). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a resource pool. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) whether or not the resource pool is configured of PSFCH resource. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a source (L2) ID. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a destination (L2) ID. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a PC5 RRC connection link. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) an SL link. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a connection status (with a base station) (e.g., RRC_CONNECTED state, IDLE state, INACTIVE state). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) an SL HARQ process (ID). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a performance or non-performance of an SL DRX operation (of the TX UE or RX UE). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) whether or not the (TX or RX) UE is a power saving UE. For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a case where PSFCH TX and PSFCH RX (and/or a plurality of PSFCH TXs (exceeding the UE capability)) overlap (in the viewpoint of a specific UE). For example, a parameter value that is related to the application or non-application of the aforementioned rule and/or that is related to the proposed method/rule of the present disclosure may be configured/allowed specifically to (or differently or independently from) a case where an RX UE has actually received PSCCH (and/or PSSCH) (re-)transmission (successfully) from a TX UE. For example, in the present disclosure, the wording for configuration (or designation) may be extendedly interpreted as a form of informing (or notifying), by a base station, to a UE through a pre-defined (physical layer or higher layer) channel/signal (e.g., SIB, RRC, MAC CE) (and/or a form being provided through a pre-configuration and/or a form of informing (or notifying), by the UE, to another UE through a pre-defined (physical layer or higher layer) channel/signal (e.g., SL MAC CE, PC5 RRC)). For example, in the present disclosure, the wording for PSFCH may be extendedly interpreted as (NR or LTE) PSSCH (and/or (NR or LTE) PSCCH) (and/or (NR or LTE) SL SSB (and/or UL channel/signal)). Additionally, the proposed method of the present disclosure may be extendedly used by being inter-combined (to a new type of method). For example, in the present disclosure, a specific threshold value may be pre-defined or may mean a threshold value that is (pre-)configured by a network or base station or a higher layer (including an application layer) of a UE. For example, in the present disclosure, a specific configuration value may be pre-defined or may mean a value that is (pre-)configured by a network or base station or a higher layer (including an application layer) of a UE. For example, an operation that is configured by the network/base station may mean an operation that is (pre-)configured by the base station to the UE via higher layer signaling, or that is configured/signaled by the base station to the UE through a MAC CE, or that is signaled by the base station to the UE through DCI. FIG.14is a diagram for describing a method for performing wireless communication, by a first apparatus, in accordance with an embodiment of the present disclosure.FIG.14may be combined with various embodiments of the present disclosure. Referring toFIG.14, in step S1410, the first apparatus may obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of a second apparatus. In step S1420, for example, the first apparatus may determine a selection window. In step S1430, for example, the first apparatus may select at least one first candidate resource within the selection window based on sensing. In step S1440, for example, the first apparatus may select at least one second candidate resource within the SL DRX active time of the second apparatus, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. In step S1450, for example, the first apparatus may select an SL resource from among the at least one first candidate resource and the at least one second candidate resource. In step S1460, for example, the first apparatus may transmit first SCI, to the second apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. In step S1470, for example, the first apparatus may transmit the second SCI and a medium access control (MAC) packet data unit (PDU) to the second apparatus, through the PSSCH, based on the SL resource. Additionally or alternatively, the at least one first candidate resource may be a number of resources being selected to be equal to or greater than a first threshold value within the selection window. Additionally or alternatively, the first threshold value may be a positive integer being equal to or greater than 1. Additionally or alternatively, the at least one second candidate resource may be a number of resources being additionally selected to be equal to or greater than a second threshold value within the SL DRX active time of the second apparatus. Additionally or alternatively, the second threshold value may be a positive integer being equal to or greater than 1. Additionally or alternatively, the second threshold value may be a threshold value related to the SL DRX active time of the second apparatus. Additionally or alternatively, the at least one second candidate resource may be a number of resources being additionally selected to be equal to or less than a third threshold value within the SL DRX active time of the second apparatus. Additionally or alternatively, the third threshold value may be a positive integer being equal to or greater than 1. Additionally or alternatively, the sensing may include partial sensing. Additionally or alternatively, the partial sensing may include at least one of periodic-based partial sensing (PBPS) or continuous partial sensing (CPS). Additionally or alternatively, the CPS may include short-term sensing (STS). Additionally or alternatively, the at least one second candidate resource may not be selected outside of the SL DRX active time of the second apparatus. Additionally or alternatively, the at least one second candidate resource may be selected based on a first reference signal received power (RSRP) threshold value related to the SL DRX active time of the second apparatus. Additionally or alternatively, the at least one second candidate resource may be selected based on the first RSRP threshold value and a discrete first step value. Additionally or alternatively, the at least one second candidate resource may be selected based on an increase in the first reference signal received power (RSRP) threshold value related to the SL DRX active time. Additionally or alternatively, the at least one second candidate resource may be selected based on the first RSRP threshold value being incremented (or increased) by N number of times, which is equivalent to a pre-configured first step value. Additionally or alternatively, the value N may be a positive integer. Additionally or alternatively, the first apparatus may select at least one third candidate resource within a time region during which the SL DRX active time of the second apparatus is extendable, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. Additionally or alternatively, the first apparatus may select at least one fourth candidate resource being excluded from the selection window within the SL DRX active time of the second apparatus, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. Additionally or alternatively, among the at least one second candidate resource, a second candidate resource related to an RSRP being less than or equal to a second reference signal received power (RSRP) threshold value may be selected by a higher priority, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. Additionally or alternatively, among the at least one second candidate resource, a second candidate resource related to an RSRP being less than or equal to a second reference signal received power (RSRP) threshold value may be selected as the SL resource by a higher priority within the SL DRX active time of the second apparatus. Additionally or alternatively, the first apparatus may extend the selection window, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. The proposed method may be applied to the apparatus according to various embodiments of the present disclosure. Firstly, a processor (102) of the first apparatus (100) may execute the instructions to obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of a second apparatus. For example, the processor (102) of the first apparatus (100) may execute the instructions to determine a selection window. For example, the processor (102) of the first apparatus (100) may execute the instructions to select at least one first candidate resource within the selection window based on sensing. For example, the processor (102) of the first apparatus (100) may execute the instructions to select at least one second candidate resource within the SL DRX active time of the second apparatus, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. For example, the processor (102) of the first apparatus (100) may execute the instructions to select an SL resource from among the at least one first candidate resource and the at least one second candidate resource. For example, the processor (102) of the first apparatus (100) may execute the instructions to transmit first SCI, to the second apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, the processor (102) of the first apparatus (100) may execute the instructions to transmit the second SCI and a medium access control (MAC) packet data unit (PDU) to the second apparatus, through the PSSCH, based on the SL resource. According to an embodiment of the present disclosure, a first apparatus for performing wireless communication may be provided. The first apparatus may include one or more memories storing instructions, one or more transceivers, and one or more processors connected to the one or more memories and the one or more transceivers, wherein the one or more processors may execute the instructions to obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of a second apparatus. For example, the one or more processors may execute the instructions to determine a selection window. For example, the one or more processors may execute the instructions to select at least one first candidate resource within the selection window based on sensing. For example, the one or more processors may execute the instructions to select at least one second candidate resource within the SL DRX active time of the second apparatus, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. For example, the one or more processors may execute the instructions to select an SL resource from among the at least one first candidate resource and the at least one second candidate resource. For example, the one or more processors may execute the instructions to transmit first SCI, to the second apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, the one or more processors may execute the instructions to transmit the second SCI and a medium access control (MAC) packet data unit (PDU) to the second apparatus, through the PSSCH, based on the SL resource. According to an embodiment of the present disclosure, an apparatus configured to control a first user equipment (UE) may be provided. The apparatus may include one or more processors, and one or more memories operably connectable to the one or more processors and storing instructions, wherein the one or more processors may execute the instructions to obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of a second UE. For example, the one or more processors may execute the instructions to determine a selection window. For example, the one or more processors may execute the instructions to select at least one first candidate resource within the selection window based on sensing. For example, the one or more processors may execute the instructions to select at least one second candidate resource within the SL DRX active time of the second UE, based on the at least one first candidate resource not being within the SL DRX active time of the second UE. For example, the one or more processors may execute the instructions to select an SL resource from among the at least one first candidate resource and the at least one second candidate resource. For example, the one or more processors may execute the instructions to transmit first SCI, to the second UE, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, the one or more processors may execute the instructions to transmit the second SCI and a medium access control (MAC) packet data unit (PDU) to the second UE, through the PSSCH, based on the SL resource. According to an embodiment of the present disclosure, a non-transitory computer-readable medium having instructions recorded thereon may be provided. When enacted by one or more processors, the instructions may cause the one or more processors to obtain, by a first apparatus, sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of a second apparatus. For example, when enacted by one or more processors, the instructions may cause the one or more processors to determine, by the first apparatus, a selection window. For example, when enacted by one or more processors, the instructions may cause the one or more processors to select, by the first apparatus, at least one first candidate resource within the selection window based on sensing. For example, when enacted by one or more processors, the instructions may cause the one or more processors to select, by the first apparatus, at least one second candidate resource within the SL DRX active time of the second apparatus, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. For example, when enacted by one or more processors, the instructions may cause the one or more processors to select, by the first apparatus, an SL resource from among the at least one first candidate resource and the at least one second candidate resource. For example, when enacted by one or more processors, the instructions may cause the one or more processors to transmit, by the first apparatus, first SCI, to the second apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, when enacted by one or more processors, the instructions may cause the one or more processors to transmit, by the first apparatus, the second SCI and a medium access control (MAC) packet data unit (PDU) to the second apparatus, through the PSSCH, based on the SL resource. FIG.15is a diagram for describing a method for performing wireless communication, by a second apparatus, in accordance with an embodiment of the present disclosure.FIG.15may be combined with various embodiments of the present disclosure. Referring toFIG.15, in step S1510, the second apparatus may obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of the second apparatus. In step S1520, the second apparatus may receive first SCI, from a first apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. In step S1530, the second apparatus may receive the second SCI and a medium access control (MAC) packet data unit (PDU) from the first apparatus, through the PSSCH, based on the SL resource. For example, the SL resource may be a resource that is selected from among at least one second candidate resource being selected within the SL DRX active time of the second apparatus, based on at least one first candidate resource being selected from a selection window and not being within the SL DRX active time of the second apparatus. Additionally or alternatively, the at least one first candidate resource may be a number of resources being selected to be equal to or greater than a first threshold value within the selection window. Additionally or alternatively, the first threshold value may be a positive integer being equal to or greater than 1. Additionally or alternatively, the at least one second candidate resource may be a number of resources being additionally selected to be equal to or greater than a second threshold value within the SL DRX active time of the second apparatus. Additionally or alternatively, the second threshold value may be a positive integer being equal to or greater than 1. Additionally or alternatively, the second threshold value may be a threshold value related to the SL DRX active time of the second apparatus. Additionally or alternatively, the at least one second candidate resource may be a number of resources being additionally selected to be equal to or less than a third threshold value within the SL DRX active time of the second apparatus. Additionally or alternatively, the third threshold value may be a positive integer being equal to or greater than 1. Additionally or alternatively, the sensing may include partial sensing. Additionally or alternatively, the partial sensing may include at least one of periodic-based partial sensing (PBPS) or continuous partial sensing (CPS). Additionally or alternatively, the CPS may include short-term sensing (STS). Additionally or alternatively, the at least one second candidate resource may not be selected outside of the SL DRX active time of the second apparatus. Additionally or alternatively, the at least one second candidate resource may be selected based on a first reference signal received power (RSRP) threshold value related to the SL DRX active time of the second apparatus. Additionally or alternatively, the at least one second candidate resource may be selected based on the first RSRP threshold value and a discrete first step value. Additionally or alternatively, the at least one second candidate resource may be selected based on an increase in the first reference signal received power (RSRP) threshold value related to the SL DRX active time. Additionally or alternatively, the at least one second candidate resource may be selected based on the first RSRP threshold value being incremented (or increased) by N number of times, which is equivalent to a pre-configured first step value. Additionally or alternatively, the value N may be a positive integer. Additionally or alternatively, at least one third candidate resource may be selected within a time region during which the SL DRX active time of the second apparatus is extendable, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. Additionally or alternatively, at least one fourth candidate resource being excluded from the selection window may be selected within the SL DRX active time of the second apparatus, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. Additionally or alternatively, among the at least one second candidate resource, a second candidate resource related to an RSRP being less than or equal to a second reference signal received power (RSRP) threshold value may be selected by a higher priority, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. Additionally or alternatively, among the at least one second candidate resource, a second candidate resource related to an RSRP being less than or equal to a second reference signal received power (RSRP) threshold value may be selected as the SL resource by a higher priority within the SL DRX active time of the second apparatus. Additionally or alternatively, the first apparatus may extend the selection window, based on the at least one first candidate resource not being within the SL DRX active time of the second apparatus. The proposed method may be applied to the apparatus according to various embodiments of the present disclosure. Firstly, a processor (202) of the second apparatus (200) may execute the instructions to obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of the second apparatus. For example, the processor (202) of the second apparatus (200) may execute the instructions to receive first SCI, from a first apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, the processor (202) of the second apparatus (200) may execute the instructions to receive the second SCI and a medium access control (MAC) packet data unit (PDU) from the first apparatus, through the PSSCH, based on the SL resource. For example, the SL resource may be a resource that is selected from among at least one second candidate resource being selected within the SL DRX active time of the second apparatus, based on at least one first candidate resource being selected from a selection window and not being within the SL DRX active time of the second apparatus. According to an embodiment of the present disclosure, a second apparatus for performing wireless communication may be provided. The second apparatus may include one or more memories storing instructions, one or more transceivers, and one or more processors connected to the one or more memories and the one or more transceivers, wherein the one or more processors may execute the instructions to obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of the second apparatus. For example, the one or more processors may execute the instructions to receive first SCI, from a first apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, the one or more processors may execute the instructions to receive the second SCI and a medium access control (MAC) packet data unit (PDU) from the first apparatus, through the PSSCH, based on the SL resource. For example, the SL resource may be a resource that is selected from among at least one second candidate resource being selected within the SL DRX active time of the second apparatus, based on at least one first candidate resource being selected from a selection window and not being within the SL DRX active time of the second apparatus. According to an embodiment of the present disclosure, an apparatus configured to control a second user equipment (UE) may be provided. The apparatus may include one or more processors, and one or more memories operably connectable to the one or more processors and storing instructions, wherein the one or more processors may execute the instructions to obtain sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of the second UE. For example, the one or more processors may execute the instructions to receive first SCI, from a first UE, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, the one or more processors may execute the instructions to receive the second SCI and a medium access control (MAC) packet data unit (PDU) from the first UE, through the PSSCH, based on the SL resource. For example, the SL resource may be a resource that is selected from among at least one second candidate resource being selected within the SL DRX active time of the second UE, based on at least one first candidate resource being selected from a selection window and not being within the SL DRX active time of the second UE. According to an embodiment of the present disclosure, a non-transitory computer-readable medium having instructions recorded thereon may be provided. When enacted by one or more processors, the instructions may cause the one or more processors to obtain, by a second apparatus, sidelink (SL) discontinuous reception (DRX) configuration including information related to SL DRX active time of the second apparatus. For example, when enacted by one or more processors, the instructions may cause the one or more processors to receive, by the second apparatus, first SCI, from a first apparatus, for scheduling a physical sidelink shared channel (PSSCH) and second sidelink control information (SCI), through a physical sidelink control channel (PSCCH), based on the SL resource. For example, when enacted by one or more processors, the instructions may cause the one or more processors to receive, by the second apparatus, the second SCI and a medium access control (MAC) packet data unit (PDU) from the first apparatus, through the PSSCH, based on the SL resource. For example, the SL resource may be a resource that is selected from among at least one second candidate resource being selected within the SL DRX active time of the second apparatus, based on at least one first candidate resource being selected from a selection window and not being within the SL DRX active time of the second apparatus. Various embodiments of the present disclosure may be combined with each other. Hereinafter, device(s) to which various embodiments of the present disclosure can be applied will be described. The various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure described in this document may be applied to, without being limited to, a variety of fields requiring wireless communication/connection (e.g., 5G) between devices. Hereinafter, a description will be given in more detail with reference to the drawings. In the following drawings/description, the same reference symbols may denote the same or corresponding hardware blocks, software blocks, or functional blocks unless described otherwise. FIG.16shows a communication system1, based on an embodiment of the present disclosure. The embodiment ofFIG.16may be combined with various embodiments of the present disclosure. Referring toFIG.16, a communication system1to which various embodiments of the present disclosure are applied includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot100a, vehicles100b-1and100b-2, an eXtended Reality (XR) device100c, a hand-held device100d, a home appliance100e, an Internet of Things (IoT) device100f, and an Artificial Intelligence (AI) device/server400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. For example, the BSs and the network may be implemented as wireless devices and a specific wireless device200amay operate as a BS/network node with respect to other wireless devices. Here, wireless communication technology implemented in wireless devices100ato100fof the present disclosure may include Narrowband Internet of Things for low-power communication in addition to LTE, NR, and 6G. In this case, for example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented as standards such as LTE Cat NB1, and/or LTE Cat NB2, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices100ato100fof the present disclosure may perform communication based on LTE-M technology. In this case, as an example, the LTE-M technology may be an example of the LPWAN and may be called by various names including enhanced Machine Type Communication (eMTC), and the like. For example, the LTE-M technology may be implemented as at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-Bandwidth Limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or7) LTE M, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices100ato100fof the present disclosure may include at least one of Bluetooth, Low Power Wide Area Network (LPWAN), and ZigBee considering the low-power communication, and is not limited to the name described above. As an example, the ZigBee technology may generate personal area networks (PAN) related to small/low-power digital communication based on various standards including IEEE 802.15.4, and the like, and may be called by various names. The wireless devices100ato100fmay be connected to the network300via the BSs200. An AI technology may be applied to the wireless devices100ato100fand the wireless devices100ato100fmay be connected to the AI server400via the network300. The network300may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices100ato100fmay communicate with each other through the BSs200/network300, the wireless devices100ato100fmay perform direct communication (e.g., sidelink communication) with each other without passing through the BS s/network. For example, the vehicles100b-1and100b-2may perform direct communication (e.g., Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices100ato100f. Wireless communication/connections150a,150b, or150cmay be established between the wireless devices100ato100f/BS200, or BS200/BS200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication150a, sidelink communication150b(or, D2D communication), or inter BS communication (e.g., relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections150aand150b. For example, the wireless communication/connections150aand150bmay transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure. FIG.17shows wireless devices, based on an embodiment of the present disclosure. The embodiment ofFIG.17may be combined with various embodiments of the present disclosure. Referring toFIG.17, a first wireless device100and a second wireless device200may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, {the first wireless device100and the second wireless device200} may correspond to {the wireless device100xand the BS200} and/or {the wireless device100xand the wireless device100x} ofFIG.16. The first wireless device100may include one or more processors102and one or more memories104and additionally further include one or more transceivers106and/or one or more antennas108. The processor(s)102may control the memory(s)104and/or the transceiver(s)106and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s)102may process information within the memory(s)104to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s)106. The processor(s)102may receive radio signals including second information/signals through the transceiver106and then store information obtained by processing the second information/signals in the memory(s)104. The memory(s)104may be connected to the processor(s)102and may store a variety of information related to operations of the processor(s)102. For example, the memory(s)104may store software code including commands for performing a part or the entirety of processes controlled by the processor(s)102or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s)102and the memory(s)104may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)106may be connected to the processor(s)102and transmit and/or receive radio signals through one or more antennas108. Each of the transceiver(s)106may include a transmitter and/or a receiver. The transceiver(s)106may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip. The second wireless device200may include one or more processors202and one or more memories204and additionally further include one or more transceivers206and/or one or more antennas208. The processor(s)202may control the memory(s)204and/or the transceiver(s)206and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s)202may process information within the memory(s)204to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s)206. The processor(s)202may receive radio signals including fourth information/signals through the transceiver(s)106and then store information obtained by processing the fourth information/signals in the memory(s)204. The memory(s)204may be connected to the processor(s)202and may store a variety of information related to operations of the processor(s)202. For example, the memory(s)204may store software code including commands for performing a part or the entirety of processes controlled by the processor(s)202or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s)202and the memory(s)204may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)206may be connected to the processor(s)202and transmit and/or receive radio signals through one or more antennas208. Each of the transceiver(s)206may include a transmitter and/or a receiver. The transceiver(s)206may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip. Hereinafter, hardware elements of the wireless devices100and200will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors102and202. For example, the one or more processors102and202may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors102and202may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers106and206. The one or more processors102and202may receive the signals (e.g., baseband signals) from the one or more transceivers106and206and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors102and202may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors102and202may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors102and202or stored in the one or more memories104and204so as to be driven by the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands. The one or more memories104and204may be connected to the one or more processors102and202and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories104and204may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories104and204may be located at the interior and/or exterior of the one or more processors102and202. The one or more memories104and204may be connected to the one or more processors102and202through various technologies such as wired or wireless connection. The one or more transceivers106and206may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers106and206may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers106and206may be connected to the one or more processors102and202and transmit and receive radio signals. For example, the one or more processors102and202may perform control so that the one or more transceivers106and206may transmit user data, control information, or radio signals to one or more other devices. The one or more processors102and202may perform control so that the one or more transceivers106and206may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers106and206may be connected to the one or more antennas108and208and the one or more transceivers106and206may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas108and208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers106and206may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors102and202. The one or more transceivers106and206may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors102and202from the base band signals into the RF band signals. To this end, the one or more transceivers106and206may include (analog) oscillators and/or filters. FIG.18shows a signal process circuit for a transmission signal, based on an embodiment of the present disclosure. The embodiment ofFIG.18may be combined with various embodiments of the present disclosure. Referring toFIG.18, a signal processing circuit1000may include scramblers1010, modulators1020, a layer mapper1030, a precoder1040, resource mappers1050, and signal generators1060. An operation/function ofFIG.18may be performed, without being limited to, the processors102and202and/or the transceivers106and206ofFIG.17. Hardware elements ofFIG.18may be implemented by the processors102and202and/or the transceivers106and206ofFIG.17. For example, blocks1010to1060may be implemented by the processors102and202ofFIG.17. Alternatively, the blocks1010to1050may be implemented by the processors102and202ofFIG.17and the block1060may be implemented by the transceivers106and206ofFIG.17. Codewords may be converted into radio signals via the signal processing circuit1000ofFIG.18. Herein, the codewords are encoded bit sequences of information blocks. The information blocks may include transport blocks (e.g., a UL-SCH transport block, a DL-SCH transport block). The radio signals may be transmitted through various physical channels (e.g., a PUSCH and a PDSCH). Specifically, the codewords may be converted into scrambled bit sequences by the scramblers1010. Scramble sequences used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of a wireless device. The scrambled bit sequences may be modulated to modulation symbol sequences by the modulators1020. A modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complex modulation symbol sequences may be mapped to one or more transport layers by the layer mapper1030. Modulation symbols of each transport layer may be mapped (precoded) to corresponding antenna port(s) by the precoder1040. Outputs z of the precoder1040may be obtained by multiplying outputs y of the layer mapper1030by an N*M precoding matrix W. Herein, N is the number of antenna ports and M is the number of transport layers. The precoder1040may perform precoding after performing transform precoding (e.g., DFT) for complex modulation symbols. Alternatively, the precoder1040may perform precoding without performing transform precoding. The resource mappers1050may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generators1060may generate radio signals from the mapped modulation symbols and the generated radio signals may be transmitted to other devices through each antenna. For this purpose, the signal generators1060may include Inverse Fast Fourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters, Digital-to-Analog Converters (DACs), and frequency up-converters. Signal processing procedures for a signal received in the wireless device may be configured in a reverse manner of the signal processing procedures1010to1060ofFIG.18. For example, the wireless devices (e.g.,100and200ofFIG.17) may receive radio signals from the exterior through the antenna ports/transceivers. The received radio signals may be converted into baseband signals through signal restorers. To this end, the signal restorers may include frequency downlink converters, Analog-to-Digital Converters (ADCs), CP remover, and Fast Fourier Transform (FFT) modules. Next, the baseband signals may be restored to codewords through a resource demapping procedure, a postcoding procedure, a demodulation processor, and a descrambling procedure. The codewords may be restored to original information blocks through decoding. Therefore, a signal processing circuit (not illustrated) for a reception signal may include signal restorers, resource demappers, a postcoder, demodulators, descramblers, and decoders. FIG.19shows another example of a wireless device, based on an embodiment of the present disclosure. The wireless device may be implemented in various forms according to a use-case/service (refer toFIG.16). The embodiment ofFIG.19may be combined with various embodiments of the present disclosure. Referring toFIG.19, wireless devices100and200may correspond to the wireless devices100and200ofFIG.17and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices100and200may include a communication unit110, a control unit120, a memory unit130, and additional components140. The communication unit may include a communication circuit112and transceiver(s)114. For example, the communication circuit112may include the one or more processors102and202and/or the one or more memories104and204ofFIG.17. For example, the transceiver(s)114may include the one or more transceivers106and206and/or the one or more antennas108and208ofFIG.17. The control unit120is electrically connected to the communication unit110, the memory130, and the additional components140and controls overall operation of the wireless devices. For example, the control unit120may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit130. The control unit120may transmit the information stored in the memory unit130to the exterior (e.g., other communication devices) via the communication unit110through a wireless/wired interface or store, in the memory unit130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit110. The additional components140may be variously configured according to types of wireless devices. For example, the additional components140may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100aofFIG.16), the vehicles (100b-1and100b-2ofFIG.16), the XR device (100cofFIG.16), the hand-held device (100dofFIG.16), the home appliance (100eofFIG.16), the IoT device (100fofFIG.16), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a fintech device (or a finance device), a security device, a climate/environment device, the AI server/device (400ofFIG.16), the BSs (200 ofFIG.16), a network node, etc. The wireless device may be used in a mobile or fixed place according to a use-example/service. InFIG.19, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices100and200may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit110. For example, in each of the wireless devices100and200, the control unit120and the communication unit110may be connected by wire and the control unit120and first units (e.g.,130and140) may be wirelessly connected through the communication unit110. Each element, component, unit/portion, and/or module within the wireless devices100and200may further include one or more elements. For example, the control unit120may be configured by a set of one or more processors. As an example, the control unit120may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory130may be configured by a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof. Hereinafter, an example of implementingFIG.19will be described in detail with reference to the drawings. FIG.20shows a hand-held device, based on an embodiment of the present disclosure. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), or a portable computer (e.g., a notebook). The hand-held device may be referred to as a mobile station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). The embodiment ofFIG.20may be combined with various embodiments of the present disclosure. Referring toFIG.20, a hand-held device100may include an antenna unit108, a communication unit110, a control unit120, a memory unit130, a power supply unit140a, an interface unit140b, and an I/O unit140c. The antenna unit108may be configured as a part of the communication unit110. Blocks110to130/140ato140ccorrespond to the blocks110to130/140ofFIG.19, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit120may perform various operations by controlling constituent elements of the hand-held device100. The control unit120may include an Application Processor (AP). The memory unit130may store data/parameters/programs/code/commands needed to drive the hand-held device100. The memory unit130may store input/output data/information. The power supply unit140amay supply power to the hand-held device100and include a wired/wireless charging circuit, a battery, etc. The interface unit140bmay support connection of the hand-held device100to other external devices. The interface unit140bmay include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit140cmay input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit140cmay include a camera, a microphone, a user input unit, a display unit140d, a speaker, and/or a haptic module. As an example, in the case of data communication, the I/O unit140cmay acquire information/signals (e.g., touch, text, voice, images, or video) input by a user and the acquired information/signals may be stored in the memory unit130. The communication unit110may convert the information/signals stored in the memory into radio signals and transmit the converted radio signals to other wireless devices directly or to a BS. The communication unit110may receive radio signals from other wireless devices or the BS and then restore the received radio signals into original information/signals. The restored information/signals may be stored in the memory unit130and may be output as various types (e.g., text, voice, images, video, or haptic) through the I/O unit140c. FIG.21shows a vehicle or an autonomous vehicle, based on an embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aerial Vehicle (AV), a ship, etc. The embodiment ofFIG.21may be combined with various embodiments of the present disclosure. Referring toFIG.21, a vehicle or autonomous vehicle100may include an antenna unit108, a communication unit110, a control unit120, a driving unit140a, a power supply unit140b, a sensor unit140c, and an autonomous driving unit140d. The antenna unit108may be configured as a part of the communication unit110. The blocks110/130/140ato140dcorrespond to the blocks110/130/140ofFIG.19, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit120may perform various operations by controlling elements of the vehicle or the autonomous vehicle100. The control unit120may include an Electronic Control Unit (ECU). The driving unit140amay cause the vehicle or the autonomous vehicle100to drive on a road. The driving unit140amay include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit140bmay supply power to the vehicle or the autonomous vehicle100and include a wired/wireless charging circuit, a battery, etc. The sensor unit140cmay acquire a vehicle state, ambient environment information, user information, etc. The sensor unit140cmay include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit140dmay implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like. For example, the communication unit110may receive map data, traffic information data, etc. from an external server. The autonomous driving unit140dmay generate an autonomous driving path and a driving plan from the obtained data. The control unit120may control the driving unit140asuch that the vehicle or the autonomous vehicle100may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit110may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit140cmay obtain a vehicle state and/or surrounding environment information. The autonomous driving unit140dmay update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit110may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous vehicles and provide the predicted traffic information data to the vehicles or the autonomous vehicles. Claims in the present description can be combined in a various way. For instance, technical features in method claims of the present description can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. | 148,518 |
11943771 | To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation. DETAILED DESCRIPTION Aspects of the present disclosure provide apparatus, methods, processing systems, and computer program products for new radio (NR) (new radio access technology or 5G technology). NR may support various wireless communication services, such as Enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra reliable low latency communications (URLLC). Aspects of the present disclosure provide techniques and apparatus for performing resource allocation for NR. For example, techniques are provided for resource allocation patterns for scheduling services, such that other services (e.g., URLLC) are protected. Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Although particular aspects are described herein, many variations and permutations of these aspects fall within the scope of the disclosure. Although some benefits and advantages of the preferred aspects are mentioned, the scope of the disclosure is not intended to be limited to particular benefits, uses, or objectives. Rather, aspects of the disclosure are intended to be broadly applicable to different wireless technologies, system configurations, networks, and transmission protocols, some of which are illustrated by way of example in the figures and in the following description of the preferred aspects. The detailed description and drawings are merely illustrative of the disclosure rather than limiting and the scope of the disclosure is being defined by the appended claims and equivalents thereof. The techniques described herein may be used for various wireless communication networks such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as NR (e.g. 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies. Example Wireless Communications System FIG.1illustrates an example wireless communication system100in which aspects of the present disclosure may be performed. For example, wireless communication system100may be a new radio (NR) or 5G network. Wireless communication system100may include user equipment (UEs)120configured to determine a resource allocation pattern that defines first resources, from a plurality of configured resource allocation patterns, for use in communicating. Wireless communication system100may include base station (BS)110configured to perform complementary operations to the operations performed by the UE120. For example, BS110may determine a resource allocation pattern that defines resources, from the plurality of resource allocation patterns configured for the UE120, wherein at least one of the plurality of configured resource allocation patterns comprises a plurality of resource elements with at least a first resource element associated with a first resource allocation restriction and at least a second resource element associated with a second resource allocation restriction, and provide an indication of the resource allocation pattern to the UE120and/or configure the UE120with the resource allocation pattern(s). UE120and BS110may communicate according to the determined resource allocation pattern. In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed. As illustrated inFIG.1, wireless communication system100may include a number of BSs110and other network entities. ABS may be a station that communicates with UEs. Each BS110may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a Node B and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term “cell” and gNB, Node B, eNB, 5G NB, AP, NR BS, transmission reception point (TRP), etc. may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in wireless communication system100through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network. A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown inFIG.1, the BSs110a,110band110cmay be macro BSs for the macro cells102a,102band102c, respectively. The BS110xmay be a pico BS for a pico cell102x. The BSs110yand110zmay be femto BS for the femto cells102yand102z, respectively. ABS may support one or multiple (e.g., three) cells. Wireless communication system100may also include relay stations. A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS110or a UE120) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. In the example shown inFIG.1, a relay station110rmay communicate with the BS110aand a UE120rin order to facilitate communication between the BS110aand the UE120r. A relay station may also be referred to as a relay BS, a relay, etc. Wireless communication system100may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless communication system100. For example, macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt). Wireless communication system100may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation. A network controller130may couple to a set of BSs and provide coordination and control for these BSs. The network controller130may communicate with the BSs110via a backhaul. The BSs110may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul. The UEs120(e.g.,120x,120y, etc.) may be dispersed throughout the wireless communication system100, and each UE may be stationary or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered evolved or machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a BS, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices. InFIG.1, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. A dashed line with double arrows indicates interfering transmissions between a UE and a BS. Certain wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a ‘resource block’ (RB)) may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 RBs), and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively. In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. BSs are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication. A UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity. Thus, in a wireless communication network with a scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources. FIG.2illustrates example components of BS110and UE120illustrated inFIG.1, which may be used to implement aspects of the present disclosure. For a restricted association scenario, BS110may be the macro BS110cinFIG.1, and UE120may be the UE120y. BS110may also be a BS of some other type. BS110may be equipped with antennas234athrough234t, and the UE120may be equipped with antennas252a-252r. One or more components of BS110and/or UE120may be used to practice aspects of the present disclosure. For example, antennas252, DEMOD/MOD254a-254r, processors266,258,264, and/or controller/processor280of the UE120and/or antennas234a-234t, MOD/DEMOD232a-234t, processors260,220,238, and/or controller/processor240of BS110may be used to perform the operations described herein and illustrated with reference toFIG.7andFIG.8. At BS110, a transmit processor220may receive data from a data source212and control information from a controller/processor240. The control information may be for the PBCH, PCFICH, PHICH, PDCCH, etc. The data may be for the PDSCH, etc. The processor220may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor220may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal. A transmit (TX) multiple-input multiple-output (MIMO) processor230may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs)232a-432t. Each modulator232may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator232may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators232a-232tmay be transmitted via the antennas234a-234t, respectively. At UE120, the antennas252a-252rmay receive the downlink signals from BS110and may provide received signals to the demodulators (DEMODs)254a-254r, respectively. Each demodulator254may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator254may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector256may obtain received symbols from all the demodulators254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor258may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE120to a data sink260, and provide decoded control information to a controller/processor280. On the uplink, at UE120, a transmit processor264may receive and process data (e.g., for the PUSCH) from a data source262and control information (e.g., for the PUCCH) from the controller/processor280. The transmit processor464may also generate reference symbols for a reference signal. The symbols from the transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by the demodulators254a-254r(e.g., for SC-FDM, etc.), and transmitted to BS110. At BS110, the uplink signals from UE120may be received by the antennas234, processed by the modulators232, detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by UE120. The receive processor238may provide the decoded data to a data sink239and the decoded control information to the controller/processor240. The controllers/processors240and280may direct the operation at BS110and UE120, respectively. The processor240and/or other processors and modules at BS110may perform or direct, e.g., the execution of the functional blocks illustrated inFIG.8, and/or other processes for the techniques described herein. The processor280and/or other processors and modules at the UE120may also perform or direct, e.g., the execution of the functional blocks illustrated inFIG.7, and/or other processes for the techniques described herein. The memories242and282may store data and program codes for the BS110and the UE120, respectively. A scheduler244may schedule UEs for data transmission on the downlink and/or uplink. Example NR/5G RAN Architecture While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as new radio (NR) or 5G technologies. NR may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)). NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and include support for half-duplex operation using time division duplexing (TDD). NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz or beyond), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical (MiCr) targeting ultra-reliable low-latency communications (URLLC) service. A single component carrier bandwidth of 100 MHZ may be supported. NR resource blocks (RBs) may span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a 0.1 ms duration. Each radio frame may consist of 50 subframes (or slots) with a length of 10 ms. Consequently, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., downlink, uplink or sidelink) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be as described in more detail below with respect toFIG.5andFIG.6. Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. Alternatively, NR may support a different air interface, other than an OFDM-based interface. NR networks may include entities such central units (CUs) or distributed units (DUs). The NR radio access network (RAN) may include a CU and one or more DUs. A NR BS (e.g., referred to as a gNB, 5G Node B, NB, eNB, transmission reception point (TRP), access point (AP), etc.) may correspond to one or multiple BSs. NR cells can be configured (e.g., by the RAN) as access cells (ACells) or data only cells (DCells). DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals—in some case cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type. FIG.3illustrates an example logical architecture of a distributed RAN300, according to aspects of the present disclosure. A 5G access node306may include an access node controller (ANC)302. ANC302may be a CU of the distributed RAN300. The backhaul interface to the next generation core network (NG-CN)304may terminate at ANC302. The backhaul interface to neighboring next generation access nodes (NG-ANs)310may terminate at ANC302. ANC302may include one or more TRPs308 TRPs308may be a DU. TRPs308may be connected to one ANC (e.g., ANC302) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. TRPs308may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE. The logical architecture of the distributed RAN300may support fronthauling solutions across different deployment types. For example, the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). The logical architecture of the distributed RAN300may share features and/or components with LTE. For example, the NG-AN310may support dual connectivity with NR. NG-AN310may share a common fronthaul for LTE and NR. The logical architecture of distributed RAN300may enable cooperation between and among TRPs308. For example, cooperation may be within a TRP and/or across TRPs via ANC302. An inter-TRP interface may not be present. The logical architecture of a distributed RAN300may include a dynamic configuration of split logical functions. For example, packet data convergence protocol (PDCP), radio link control (RLC) protocol, and/or medium access control (MAC) protocol may be adaptably placed at ANC302or TRP308. FIG.4illustrates an example physical architecture of a distributed RAN400, according to aspects of the present disclosure. A centralized core network unit (C-CU)402may host core network functions. C-CU402may be centrally deployed. C-CU402functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity. A centralized RAN unit (C-RU)404may host one or more ANC functions. Optionally, C-RU404may host core network functions locally. C-RU404may have distributed deployment. C-RU404may be located near the network edge. DU406may host one or more TRPs. DU406may be located at edges of the network with radio frequency (RF) functionality. FIG.5is a diagram showing an example of a DL-centric slot500. DL-centric slot500may include a control portion502. The control portion502may exist in the initial or beginning portion of DL-centric slot500. The control portion502may include various scheduling information and/or control information corresponding to various portions of DL-centric slot500. In some configurations, the control portion502may be a physical DL control channel (PDCCH), as shown inFIG.5. DL-centric slot500may also include a DL data portion504. The DL data portion504may be referred to as the payload of DL-centric slot500. The DL data portion504may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE). In some configurations, the DL data portion504may be a physical DL shared channel (PDSCH). DL-centric slot500may also include a common UL portion506. The common UL portion506may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion506may include feedback information corresponding to various other portions of DL-centric slot500. For example, the common UL portion506may include feedback information corresponding to the control portion502. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion506may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information. As illustrated inFIG.5, the end of the DL data portion504may be separated in time from the beginning of the common UL portion506. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)). The foregoing is merely one example of a DL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein. FIG.6is a diagram showing an example of an UL-centric slot600. UL-centric slot600may include a control portion602. The control portion602may exist in the initial or beginning portion of UL-centric slot600. The control portion602inFIG.6may be similar to the control portion602described above with reference toFIG.6. UL-centric slot600may also include an UL data portion604. The UL data portion604may sometimes be referred to as the payload of UL-centric slot600. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). In some configurations, the control portion602may be a physical UL shared channel (PUSCH). As illustrated inFIG.6, the end of the control portion602may be separated in time from the beginning of the UL data portion604. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). UL-centric slot600may also include a common UL portion606. The common UL portion606inFIG.6may be similar to the common UL portion606described above with reference toFIG.6. The common UL portion606may additionally or alternatively include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. The foregoing is merely one example of an UL-centric slot and alternative structures having similar features may exist without necessarily deviating from the aspects described herein. In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum). Example Resource Allocation Patterns for Scheduling Services in a Wireless Network As described above, certain systems (e.g. such as wireless communication system100) may be new radio (NR) systems (e.g., configured to operate according a wireless standard, such as 5G)) that support various wireless communication services such as, for example, enhanced mobile broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) service targeting high carrier frequency (e.g. 60 GHz), massive machine type communications (mMTC) service targeting non-backward compatible MTC techniques, and/or mission critical (MiCr) service targeting ultra-reliable low-latency communications (URLLC). These services may be associated with latency and reliability requirements, may be associated different transmission time intervals (TTI) to meet the quality of service (QoS) requirements. In addition, these services may co-exist in the same subframe Latency in a network may refer to the amount of time for a packet of data to get from one point in the network to another point in the network. In some example, URLLC (MiCr service) may target a latency of 0.5 ms; eMBB may target 4 ms latency; and mMTC may target 10 seconds (e.g., for a 20 byte uplink application packet or 105 bytes at the PHY layer with uncompressed IP headers) at 164 dB minimum coupling loss (MCL). Reliability in a network may refer to a probability of successfully transmitting X number of bytes within 1 ms at a certain channel quality. For example, reliability for URLLC may target a block error rate (BLER) of 10−3. Avoiding or minimizing the impact of interference between uplink transmissions of reliable low latency services, are desirable to help meet the reliability and latency requirements when such services are operating together on a wireless network. For example, it may be desirable to protect resources used for URLLC transmissions, particularly in cases where uplink transmission between multiple wireless devices may not be easily punctured. Low-latency services typically need to be transmitted and received quickly as delays increase the latency of the services. As uplink slots are typically assigned multiple milliseconds in advance, it may be difficult to schedule or reschedule uplink assignments fast enough to adequately meet latency requirements (e.g., 0.5 ms). For example, where a different service (e.g., such as eMBB and/or mMTC) is multiplexed with URLLC, it is desirable to reschedule the regular service whenever there is a URLLC transmission. In the downlink direction, this can be achieved by puncturing downlink eMBB data with URLLC, but on the uplink, the eMBB data is typically scheduled ahead of time, so such dynamic puncturing may be challenging. For eMBB service scheduling, link efficiency may be important. If too many resources are reserved for URLLC, less resources are available for eMBB service, which can result in inefficient resource usage. On the other hand, even if URLLC communications puncture eMBB services, the punctured resources may be still subject to inter-cell interference from other cells, which may make it difficult to meet the stringent QoS targets for URLLC service. For mMTC scheduling or other services that use coverage enhancement (e.g., such as voice over Internet protocol (VoIP)), a single transport block (e.g., packet) may have a time span (TTI) of multiple subframes (e.g., up to one second or longer). Such long-TTI transmissions, if contiguous, may cause inter-cell interference to other services including URLLC. Accordingly, techniques for scheduling resource for different wireless communication services in a wireless network, such as NR, are desirable. Aspects of the present disclosure provide resource allocation patterns for scheduling services, such as reliable low-latency services (e.g., URLLC) and other services, in a wireless network, such as (NR (e.g., a 5G network). FIG.7is flowchart illustrating example operations700for wireless communications, in accordance with certain aspects of the present disclosure. Operations700may be performed, for example, by a UE (e.g., UE120). Operations700may begin at702by determining a resource allocation pattern that defines resources, from a plurality of configured resource allocation patterns, wherein at least one of the plurality of configured resource allocation patterns comprises a plurality of resource elements with at least a first resource element associated with a first resource allocation restriction and at least a second resource element associated with a second resource allocation restriction. At704, the UE communicates based on the determined resource allocation pattern. FIG.8is flowchart illustrating example operations800for wireless communications, in accordance with certain aspects of the present disclosure. Operations800may be performed, for example, by a BS (e.g., BS110). Operations 8—may be complementary operations by the BS to the operations700by the UE. Operations800may begin at802by determining a resource allocation pattern, from a plurality of configured resource allocation patterns configured for a UE, that defines resource for communicating, wherein at least one of the plurality of configured resource allocation patterns comprises a plurality of resource elements with at least a first resource element associated with a first resource allocation restriction and at least a second resource element associated with a second resource allocation restriction. At804, the BS provides an indication to the UE of the resource allocation pattern to use for communicating. At806, the BS communicates based on the determined resource allocation pattern. Example Resource Allocation Patterns According to certain aspects, a plurality of different resource allocations patterns may be defined and configured for the UE (e.g., a UE120). One of the configured resource allocation patterns may be indicated for a UE (e.g., by a BS110) to use for particular communications. The resource allocation patterns may define resource allocation restrictions for different resource elements. As will be described in more detail below, the resource allocation pattern may indicate resources at a granularity of symbols, tones, resource blocks, etc. The resource allocation pattern may indicate resources that can be used or not used (e.g., ON/OFF) by the UE or can indicate various power levels that can be used for particular resources. The resource allocation patterns may be semi-statically signaled, configured, or dynamically determined/signaled. Separate (e.g., different) resource allocation patterns may be indicated for different services, different subframes, different UEs, different carriers, different channels, etc. For example, the resource allocation patterns may be selected/determined/signaled in order to minimize interference, for example, to URLLC service, and/or interference, for example, from mMTC service. Example ON/OFF Resource Allocation Pattern FIG.9,FIG.9AandFIG.9Billustrate example ON/OFF resource allocation patterns at a symbol level granularity, in accordance with certain aspects of the present disclosure. InFIG.9,FIG.9AandFIG.9B, an 8-symbol resource allocation pattern is used. In aspects, resource allocation patterns may be defined for different durations (e.g., different numbers of symbols). InFIG.9andFIG.9B, the resource allocation patterns are defined at the symbol-level granularity. The resource allocation patterns indicate symbols that may be used by a UE for a particular communication and symbols that are not allocated (e.g., excluded) for the UE to use for that communication. This may be referred to as an ON/OFF resource allocation pattern. As will be discussed in greater detail below, different resource allocation granularities may be used (e.g., tone, resource block, etc.) and different patterns may be used, for example, rather than an ON/OFF pattern, levels of usage may be defined for particular resources in the resource allocation patterns. InFIG.9, an example of a contiguous resource allocation pattern900is shown where only contiguous symbols are allocated for use. InFIG.9AandFIG.9B, examples of non-contiguous resource allocation patterns are shown (or hybrid contiguous and non-contiguous). InFIG.9A, a 2-ON, 1-OFF, resource allocation pattern900A is illustrated. With this pattern, URLLC communications having a 1-symbol TTI may have protected resources every three symbols (e.g., the OFF symbols).FIG.9Bshows another example non-contiguous resource allocation pattern900B having a 2-ON, 2-OFF, resource allocation pattern. With this pattern, URLLC communications having a 2-symbol TTI can have two symbols of protected resources every 4 symbols. Although not shown inFIG.9,FIG.9AandFIG.9B, other ON/OFF resource allocation patterns may be defined/configured using different combinations of ON/OFF symbols, different numbers of symbols, transmit time intervals (TTIs), slots, subframes, etc., and/or different resource granularities (e.g., tone, RBs, etc.). Example Usage-Level Resource Allocation Patterns According to certain aspects, rather than (or in combination with) an ON/OFF resource allocation pattern, a level of usage may be defined (e.g., determined, signaled, indicated, configured, etc.) for a resource allocation pattern. The level of usage may be defined for various granularities (e.g., symbols, TTIs slots, subframes, tones, and/or RBs, etc.). The usage may be a power level that may be used by the UE for a particular communications on the particular resource. FIG.10and FIG. FIG. illustrate example resource allocation patterns indicating power levels that may be used for the symbols in the resource allocation pattern, in accordance with certain aspects of the present disclosure. As shown inFIG.10, in one example resource allocation pattern1000, two different power levels may be indicated for different resources—a normal power level (e.g., unrestricted) or a restricted (e.g., reduced) power level. In the example resource allocation pattern1000, the UE may use the normal power level in two symbols, followed by a restricted power level in the next symbol. As shown inFIG.10A, in another example resource allocation pattern1000A, three different power levels may be indicated for different resources—the normal power level (e.g., unrestricted), the restricted (e.g., reduced) power level, and a zero-power level (e.g., OFF). In the example resource allocation pattern1000A, the UE may use the normal power level in two symbols, followed by a zero-power level in the next symbol, followed by a restricted power level in the next two symbols. According to certain aspects, a resource allocation pattern may be defined/configured that indicates power level usages for resources in two dimensions (e.g., time and frequency). For example, resource allocation patterns may be defined/configured that indicate power level usage for different symbols and for different frequency resources (e.g., tones) within the symbols.FIG.10Billustrates an example resource allocation pattern1000B, in which two different power levels may be indicated for different resources—a normal power level (e.g., unrestricted) or a restricted (e.g., reduced) power level. As shown inFIG.10B, within in some symbols, certain frequency resources are indicated one usage level and other frequency resources are indicated a different usage level. According to certain aspects, although not shown inFIG.10,FIG.10AandFIG.10B, different combinations/patterns of usage levels, time resources, and frequency resources may be defined/configured for resource allocation. For example, more than three power levels could be indicated for different resources. Also, different combinations of single-dimensional and/or two-dimensional resources may be used for a resource allocation pattern with any combinations of resource usage levels associated with the particular resources. According to certain aspects, the resource usage levels (e.g., power levels) may be signaled to the UE, predetermined, and/or blindly detected. Example Resource Block Level Granularity Resource Allocation Patterns As mentioned above, resource allocation patterns may be defined/configured/indicated at various resource granularity levels. According to certain aspects, resource allocation patterns may be defined at the resource block (RB) level. The resource allocation pattern may be defined per-subband, per-RB, or per-set of RBs to indicate RBs that may be used or not used (or levels of resource usage) for a particular communication. As illustrated inFIG.11, this may also be combined with symbol (or other time dimension resource) resource allocation. According to certain aspects, some RBs in some symbols may be reserved. Some RBs may be reserved for forward compatibility (e.g., blank resources). Some RBs may be semi-statically configured or reserved for a particular service, such as mMTC communications. For example, an anchor RB may be defined for mMTC synchronization signals, information transmissions, etc. Example Indication of Resource Allocation Pattern According to certain aspects, an indication of the resource allocation pattern (e.g., a particular resource allocation of a plurality of resource allocations configured for the UE) for the UE to use for a particular communication may be provided. The indication may be provided via a semi-static configuration (e.g., higher layer infrequent radio resource control (RRC) signaling), an activation/deactivation message, dynamic signaling, or a combination thereof. In one example, the UE may be semi-statically configured, via higher layers, with a set of defined resource allocation patterns (e.g., a set of four patterns). The configured resource allocation patterns may be defined according to any of the resource allocation patterns described above (e.g., contiguous, non-contiguous, ON/OFF, usage levels, granularities, etc.) or other resource allocation patterns. The UE may then be sent (e.g., by the BS) an indication (e.g., a 2-bit indicator in the case of four configured resource allocation patterns) of which resource allocation pattern in the configured set of defined resource allocation patterns is to be used for a particular communication. The indication of the resource allocation pattern to use for the communication may be provided in a control channel (e.g., broadcast, groupcast, or unicast) to indicate the resource allocation pattern for a data transmission that is scheduled by the control channel. As another example, the UE may receive an activation message that activates the resource allocation pattern. In this case, the UE may use the resource allocation pattern (e.g., indefinitely) for communications until a new resource allocation pattern is activated (e.g., by receiving another activation message) or the current resource allocation pattern is released (e.g., by a deactivation message). Example Selection/Determination of the Resource Allocation Patterns As described above, different (e.g., a plurality or set of) resource allocation patterns may be defined/configured for the UE. The UE may be configured with or signaled the defined resource allocation patterns and may be indicated (e.g., configured or dynamically signaled) a particular one of the resource allocations patterns to use for a particular communication. According to certain aspects, the BS may determine/select the particular resource allocation pattern to indicate/configure the UE to use based on various parameters. For example, the determination/selection may be UE-dependent, uplink or downlink dependent, component carrier dependent, service type dependent, TTI length dependent, channel dependent, and/or subframe (slot configuration) dependent. According to certain aspects, separate indications of resource allocation patterns may be indicated/configured for different ones of the above parameters. Example UE-Dependent Resource Allocation Patterns According to certain aspects, the resource allocation pattern may be UE-dependent (e.g., selected based on and/or determined separately for). Transmissions to/from different UEs contributes various amount of inter-cell interference. For example, a UE close to cell-center may cause little or minimal inter-cell interference in the uplink (even if the UE transmits continuous in the uplink). Thus, the resource allocation pattern may be contiguous. Such a UE may be semi-statically with the particular resource allocation pattern. On the downlink, the inter-cell interference may be reasonable small if its downlink transmission is subject to restricted power. Thus, a resource allocation pattern restricting the resource usage level may be used. Alternatively, a UE at cell-edge may contribute inter-cell interference to other cells for its uplink and downlink transmissions. Similarly, its downlink traffic would also contribute inter-cell interference to other cells. In this case, a non-contiguous resource pattern may be semi-statically and/or dynamically indicated for such as UE. Example Link-Dependent and/or CC-Dependent Resource Allocation Patterns According to certain aspects, the resource allocation pattern may be link dependent. For example, the resource allocation patterns may be separately managed (e.g., determined/selected/indicated/configured) for downlink, uplink, or sideline. Downlink and uplink may have different channel and interference characteristics, different antenna patterns, different transmission power, etc. For the UE, downlink operations may be different than uplink operations. For example, the UE may be served by a different cell (or set of cells) on the downlink than on the uplink (e.g., in coordinated multipoint (CoMP) operation). Different cells may have different uplink-downlink subframe configurations. Thus, interference characteristics for communication with a UE may be quite different for the downlink and uplink. Accordingly, different resource allocation patterns may be determined (selected/indicated/configured/signaled) for the uplink, downlink, and sidelink directions. Similarly, the resource pattern may be separately configured for different component carriers (CCs), which may also have different UL/DL subframe configurations. Example Service Type-Dependent and/or TTI Length-Dependent Resource Allocation Patterns According to certain aspects, the resource allocation pattern may be dependent on the service type and/or TTI length. The resource allocation patterns may be managed separately for different types of services. In one example, a first set of resource allocation patterns may be defined and/or selected for eMBB service, a second set of patterns may be defined and/or selected for URLLC service, and a third set of patterns may be defined and/or selected (and configured and/or signaled) for mMTC service. In one example, the set of patterns for each service may be a function of the TTI length of that service being scheduled. For example, for a very short TTI transmission (e.g., a few symbols), the resource allocation pattern for that communication (e.g., service) may be continuous (e.g., semi-statically configured); for a less short TTI transmission (e.g., 5-14 symbols), the resource allocation pattern may be dynamically indicated from one of four patterns; and for a long TTI transmission (e.g., >14 symbols), the resource allocation pattern may be dynamically indicated from one of two patterns Example Channel-Dependent Resource Allocation Patterns According to certain aspects, resource allocation patterns may be channel-dependent. The resource allocation patterns may be managed separately for different types of channels. For example, a first resource allocation pattern may be defined and/or selected (and configured and/or signaled) for a control channel, a second resource allocation pattern may be defined and/or selected for eMBB PDSCH, and a third resource allocation pattern may be defined and/or selected for URLLC PDSCH, etc. Some channels (e.g., important channels, broadcast channels, groupcast channels, etc.) may have different treatments. For example, PSS/SSS/PBCH/SIB/MIB (including bundled PSS/SSS/PBCH or other SS) may have a resource allocation pattern that never skips any symbol. Example Subframe-Dependent Resource Allocation Patterns According to certain aspects, the resource allocation patterns may be subframe-dependent. The resource allocation patterns may be a function of subframe indices. For example, certain services may be valid services may be valid in a subset of subframes, thus, some resource allocation patterns may be applicable only in the subset of subframes. URLLC may be present in a subset of subframes on a particular CC, thus some resource pattern may be applicable only in the subset of subframes on the CC. According to certain aspects, any combination of the above may be applied for determining the resource allocation patterns for UEs. The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c). As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering. The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. If implemented in hardware, an example hardware configuration may comprise a processing system in a wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including a processor, machine-readable media, and a bus interface. The bus interface may be used to connect a network adapter, among other things, to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal120(seeFIG.1), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. The processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system. If implemented in software, the functions may be stored or transmitted over as one or more instructions or code on a computer-readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media. A computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface. Alternatively, or in addition, the machine-readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files. Examples of machine-readable storage media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable media may be embodied in a computer-program product. A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer-readable media may comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from that software module. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Thus, in some aspects computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects computer-readable media may comprise transitory computer-readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media. Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. For example, instructions for determining a maximum available transmit power of the UE, instructions for semi-statically configuring a first minimum guaranteed power available for uplink transmission to a first base station and a second minimum guaranteed power available for uplink transmission to a second base station, and instructions for dynamically determining a first maximum transmit power available for uplink transmission to the first base station and a second maximum transmit power available for uplink transmission to the second base station based, at least in part, on the maximum available transmit power of the UE, the first minimum guaranteed power, and the second minimum guaranteed power. Further, it should be appreciated that modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized. It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims. | 63,572 |
11943772 | DETAILED DESCRIPTION The following description of the embodiments refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. The following detailed description does not limit the invention. The embodiments to be discussed next are not limited to the configurations described below, but may be extended to other arrangements as discussed later. Reference throughout the specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with an embodiment is included in at least one embodiment of the present invention. Thus, the appearance of the phrases “in one embodiment” or “in an embodiment” in various places throughout the specification is not necessarily all referring to the same embodiment. Further, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. Embodiments described herein allow more flexible long term evolution (LTE) uplink (UL) transmissions in unlicensed spectrum that considers a mixture of contention-based and scheduled-based channel access principles. Embodiments generate higher LTE user equipment (UE) probabilities of getting access to the medium. The UE can avoid performing two listen before talk (LBT) operations corresponding to the scheduling request and scheduling grant. Thus, LTE UL performance in unlicensed spectrum is improved. UL transmission efficiency (in terms of data throughput) is improved in unlicensed carriers since the latency between UL grant and PUSCH transmission is reduced. At low load, there is a UL latency reduction and higher channel utilization for UL access. In the embodiments described below LBT and Clear Channel Assessment (CCA) may be interchangeably used. The following embodiments describe how to allow more flexible LTE UL transmissions in unlicensed spectrum that considers a mixture of contention-based and scheduled-based channel access principles. It is to be understood that the proposed methods also apply to different variations of LTE operating in unlicensed spectrum, such as LTE-U and standalone LTE-U. A non-prefixed term in this disclosure is to be understood in the LTE sense unless otherwise stated. However, any term designating an object or operation known from LTE is expected to be reinterpreted functionally in view of NR specifications. Examples: An LTE radio frame may be functionally equivalent to an NR frame, considering that both have a duration of 10 ms. An LTE eNB may be functionally equivalent to an NR gNB, since their functionalities as downlink transmitter are at least partially overlapping. The least schedulable resource unit in LTE may be reinterpreted as the least schedulable resource unit in NR. The shortest data set for which LTE acknowledgement feedback is possible may be reinterpreted as the shortest data set for which NR acknowledgement feedback is possible. Therefore, even though some embodiments of this disclosure have been described using LTE-originated terminology, they remain fully applicable to NR technology. According to an embodiment, a UE can perform LBT to gain uplink channel access whenever the UL data arrives without having an UL grant from the eNB (or base station). UE will transmit using unscheduled mode for first N transmission bursts. Note that the value of N could be set according to different criteria (e.g. load conditions, number of collisions, traffic type, etc.). After the first N uplink transmission bursts are finalized, scheduled-based channel access mechanism is activated and the eNB is again controlling the uplink access. As a non-limiting example, self-carrier scheduling can be used. The eNB sends the grant on the same carrier as the data transmissions is scheduled. As another non-limiting example, the eNB can send the grant using cross carrier scheduling that allows scheduling data on another carrier. The carrier used for the grant transmission could be either licensed or unlicensed. By having unscheduled transmission of the first N transmission bursts, UL transmissions can avoid scheduling request (SR) delay and improve probability of getting access to the medium since UL transmission does not depend on UL grant reception. In another aspect of this embodiment, unscheduled UL transmissions are confined in time to pre-specified opportunistic windows. As non-limiting examples, these windows may exclude the UE DMTC configured for the serving cell or neighbor cells, may exclude paging occasion windows of the eNB, and may exclude measurement gaps configured for RRM. As another non-limiting example, the eNB may explicitly signal specific subframes in which unscheduled transmissions are allowed. In another aspect of this embodiment, the UE may send a UL transmission burst of new data based on an explicit grant from the eNB, and send an unscheduled retransmission for the data in the first burst if a new UL grant or HARQ ACK/NACK is not received from the eNB within a pre-specified time window. The redundancy version (RV) used for the retransmission may for example be the subsequent RV of the initial transmission, or be the same RV as the initial transmission. According to an embodiment, during the unscheduled access, if the intended unlicensed channel for uplink transmission is busy, the UE can keep trying attempting to transmit data in the unlicensed channel using the unscheduled mode until the earliest opportunity to transmit the SR on any of the available carriers including other unlicensed carriers or licensed carriers. If UE is not able to transmit with the unscheduled mode, then the UE will transmit the SR to inform the eNB about its buffer. The eNB needs some time to decode the SR message and transmit the UL grant. The UE can deactivate the unscheduled mode after the SR is sent, or stay in the unscheduled mode and try to transmit the uplink data until the grant is received. In this case, the scheduling request delay is avoided by not idly waiting for the SR and the grant to be received and still inform the eNB about the buffer status at the earliest possible, either by the SR or by successful unscheduled uplink transmission. According to an embodiment, during the unscheduled access, the UE needs to imbed UE ID in the first UL burst for the eNB so that the eNB can distinguish the source of the received data. In one non-limiting example, the UE ID (e.g., C-RNTI) is transmitted in the first SC-FDMA symbol of the unscheduled transmission since the first symbol may be partly utilized for UL LBT. In another non-limiting example, the UE ID is transmitted in the first SC-FDMA symbol of every unscheduled UL subframe. In a further non-limiting example, the UE transmits the corresponding DCI of the UL transmission. The DCI has the same format and error correction coded as if it was prepared by an eNB for a PDCCH or an EPDCCH (see Section 2.1.1.3). The encoded bits can be transmitted in the first SC-FDMA symbol of the unscheduled transmission. The transmission can be present in the first subframe or in every subframe of every unscheduled UL transmission. The DCI allows the eNB to check the identity of the transmitting UE because the CRC bits are scrambled by the UE C-RNTI; and to correctly receive the UL transmission based on the transmission formats and parameters provided in the DCI. According to an alternative embodiment, it is possible to scramble the PUSCH CRC with the UE C-RNTI as an additional check. According to an embodiment, during the unscheduled mode, after a successful LBT, the UE can transmit using the full available bandwidth. However, if more than one UE, served by the same eNB, finish their back off at the same time and start simultaneous transmission, they will collide with each other and the sub frame might be wasted. To minimize this problem, each UE can transmit using a portion of the full bandwidth (referred to as interlace). Different interlaces do not overlap in frequency, and therefore UEs will not interfere with each other. The UE can select a certain interlace for transmission randomly or based on certain criteria. As a non-limiting example, interlace selection can be randomized based on UE ID. Another non-limiting example includes that different interlace assignment can be coordinated by eNB by informing to UEs in the unscheduled mode via downlink transmission such as PDSCH or PDCCH. According to an embodiment, switching between unscheduled and scheduled mode can be decided by the UE itself or by the serving eNB. The eNB can mandate a specific UE or a group of UEs to deactivate the unscheduled or scheduled mode based on different criteria such as the number of UEs with active transmissions, rate of collisions, BSR. For instance, at high load conditions, when large number of nodes would have to contend in order to access the medium, it is not efficient to use unscheduled mode due to the high number of potential collisions. In a non-limiting example, this information may be carried on the C-PDCCH or another PDCCH sent in the common search space. Another important criterion can be the buffer size ratio between eNB and serving UEs. If the buffer size of eNB is larger than aggregate reported buffer size of UEs, the scheduled mode can be enforced in order to reduce collisions due to downlink transmission and uplink transmissions in the same cell. According to an embodiment, prioritization between a scheduled transmission and an unscheduled transmission can be done in both time and frequency domain(s). In a non-limiting example, prioritization in the time domain by setting the starting time of the scheduled uplink transmission burst later than that for the scheduled uplink transmissions if both have the same back-off. In another non-limiting example, prioritization in the frequency domain can be achieved by allowing the eNB to reserve M interlaces for unscheduled transmission via SIB or C-PDCCH, these M interlaces are not used for scheduled transmissions, and the number of interlaces for unscheduled transmission is lower than that for scheduled transmissions. According to an embodiment, the scheduling mode switch can also consider the impact to the neighboring eNBs. A non-limiting example is now described with respect toFIG.9. An eNB902in a first cell916which includes a plurality of active UEs910,912and914, informs neighboring eNBs904,906and908(each of which has their own cell918,920, and922, respectively) whenever the unscheduled mode is activated. Then, if any neighboring eNBs experience interference level increase above a certain threshold, they indicate the eNB in the unscheduled mode to change to the scheduled mode in order to reduce the excessive interference due to the unscheduled mode. The information exchange between eNBs can be done via X2 interface. According to an embodiment, in the unscheduled mode, the multiple UEs can be hidden each other so that LBT may not properly work which leads to unwanted uplink collisions. The user grouping for the unscheduled mode can further consider this aspect. In a non-limiting example, the eNB activates only UEs which are in the sensing range to let them rely on LBT for reducing collisions. The eNB can estimate which UEs are out of the sensing range based on UEs' measurement reports on the average interference level. In the unscheduled mode, although UEs can hear each other, they might still collide due to unlucky choice of random backoff. According to an embodiment, this can be mitigated if eNB also control different UEs in the unscheduled mode by assigning the different backoff offset. Different backoff offset makes UEs wait a slightly more but in a different amount of time. This allows minimizing the simultaneous uplink transmissions. In a non-limiting example, the backoff offset can be function of the contention window size so that each UE may apply different offset according to the contention window size. This assignment from eNB can be done via PDCCH or PDSCH. By doing so, the collisions can be also minimized even at the unscheduled mode. According to an embodiment there is a method for performing an unscheduled uplink transmission by a user equipment (UE) in an unlicensed portion of a radio spectrum as shown inFIG.10. The method includes: in step1002, performing, by the UE, a listen before talk (LBT) operation in the unlicensed portion of the radio spectrum, wherein the LBT operation includes sensing the portion of the radio spectrum for a pre-determined minimum amount of time for traffic; and in step1004, performing, if no traffic was sensed, the unscheduled uplink transmission, by the UE, of data in an unscheduled mode of operation for at least one transmission burst. The method may further include step1006, activating, after transmitting the at least one transmission burst, a schedule based channel access mechanism, wherein an eNodeB (eNB) controls the UE's uplink access and step (1008) receiving, by the UE after transmitting the at least one transmission burst, an uplink transmission grant via cross carrier scheduling. Alternatively, the method may include step1006, activating, after transmitting the at least one transmission burst, a schedule based channel access mechanism, wherein an eNodeB (eNB) controls the UE's uplink access; and step (1008) receiving, by the UE after transmitting the at least one transmission burst, an uplink transmission grant on the same carrier as the data transmissions is scheduled. The method may also include step1010, receiving, at the UE, an uplink transmission grant, and in response to received uplink transmission grant, transmitting, by the UE, an uplink transmission burst of new data. In step1012the UE sends an unscheduled retransmission for the new data if a new uplink grant or HARQ ACK/NACK is not received from the eNB within a pre-specified time window. Step1014includes embedding an identification of the UE in a first of the least one uplink transmission burst when in the unscheduled mode of operation, wherein the identification of the UE is embedded in a first single carrier frequency division multiple access (SC-FDMA) symbol of the first of the least one uplink transmission burst. Alternatively, step1014may include embedding the identification of the UE in a first SC-FDMA symbol of every uplink transmission burst when in an unscheduled mode of operation. Step1016includes prioritizing between a scheduled uplink transmission burst and an unscheduled uplink transmission burst by having different transmission start times when if both transmission bursts have a same back-off timing. According to embodiments, products, services and associated updates can be provisioned to a customer's contract for use on a user equipment (UE) and/or other devices. An example of such a UE is shown inFIG.11. The UE10includes a processor12for executing instructions, a display14which can display information associated with various products and services, a memory11which stores information and a transceiver13for communicating with nodes of communication networks, e.g., the eNB, as well as other UEs and devices. The UE may be configured to perform the method step described above. According to an embodiment there is a method for an eNB as shown inFIG.12. The method is directed to an unscheduled uplink transmission in an unlicensed portion of a radio spectrum. The method includes, step2002, controlling a user equipment's UE's uplink access, after receiving a at least one transmission burst in an unscheduled mode of operation from the UE, using a schedule based channel access mechanism; where controlling the UE's uplink access includes transmitting, step2004, to the UE, an uplink transmission grant for scheduled-based channel access. The method may also include, step2006, signaling, to the UE, specific subframes in which unscheduled transmissions are allowed. In step2008, the eNB informs neighboring eNBs whether an unscheduled mode of operation is active for at least one UE and receives information from the neighboring eNBs associated with a level of interference when the level of interference is greater than a pre-determined threshold, step2010, and finally in step2012the eNB instructs the at least one UE to switch from the unscheduled mode of operation to a scheduled mode of operation. The method may also include step2014activating UEs to operate in an unscheduled mode of operation that are in a sensing range of each other, wherein the eNB estimates which UEs are out of the sensing range based on the UEs measurement reports which include an average interference level. Further the method may include step2016, assigning a different backoff offset to each UE which is operating in an unscheduled mode of operation, wherein the backoff offset is a function of a contention window size. According to an embodiment, an eNB (or base station) can be used to implement the various embodiments described herein, e.g., determining when the UE is to operate in an unscheduled mode or a scheduled mode. An example of such a eNB20is shown inFIG.13. The eNB includes a processor23for executing instructions, a memory21for storing information and an interface22for communicating with other nodes and devices in support of operations associated UE uplink transmissions. The eNB may be configured to perform the method step described above. Functional modules or circuit architecture may be implemented in the UE (10). The embodiments at least functionally include a first performing module for performing a listen before talk, LBT, operation in the unlicensed portion of the radio spectrum. The LBT operation includes sensing the portion of the radio spectrum for a pre-determined minimum amount of time for traffic. The embodiments further include a second performing module, which, if no traffic was sensed, is for performing the unscheduled uplink transmission, by the UE, of data in an unscheduled mode of operation for at least one transmission burst. Functional modules or circuit architecture may be implemented in the eNB (20). The embodiments at least functionally include a controlling module for controlling a UE's (10) uplink access, after receiving a at least one transmission burst in an unscheduled mode of operation from the UE, using a schedule based channel access mechanism. The embodiments further include a transmitting module for transmitting, to the UE, an uplink transmission grant for scheduled-based channel access. The disclosed embodiments provide methods and devices for avoiding batch updates to the customer base by instead using global entities. It should be understood that this description is not intended to limit the invention. On the contrary, the embodiments are intended to cover alternatives, modifications and equivalents, which are included in the spirit and scope of the invention. Further, in the detailed description of the embodiments, numerous specific details are set forth in order to provide a comprehensive understanding of the invention. However, one skilled in the art would understand that various embodiments may be practiced without such specific details. As also will be appreciated by one skilled in the art, the embodiments may take the form of an entirely hardware embodiment or an embodiment combining hardware and software aspects. Further, the embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions embodied in the medium. Any suitable computer-readable medium may be utilized, including hard disks, CD-ROMs, digital versatile disc (DVD), optical storage devices, or magnetic storage devices such as floppy disk or magnetic tape. Other non-limiting examples of computer-readable media include flash-type memories or other known memories. Although the features and elements of the present embodiments are described in the embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the embodiments or in various combinations with or without other features and elements disclosed herein. The methods or flowcharts provided in the present application may be implemented in a computer program, software or firmware tangibly embodied in a computer-readable storage medium for execution by a specifically programmed computer or processor. ABBREVIATIONS AbbreviationExplanationBSRBuffer Status RequestCCComponent CarrierCCAClear Channel AssessmentCQIChannel Quality InformationCRCCyclic Redundancy CheckDCIDownlink Control InformationDLDownlinkDMTCDRS Measurement Timing ConfigurationDRSDiscovery Reference SignaleNBevolved NodeB, base stationUEUser EquipmentULUplinkLAALicensed-Assisted AccessSCellSecondary CellSTAStationLBTListen-before-talkLTE-ULTE in Unlicensed SpectrumPDCCHPhysical Downlink Control ChannelPMIPrecoding Matrix IndicatorPUSCHPhysical Uplink Shared ChannelRATRadio Access TechnologyRNTIRadio Network Temporary IdentifierTXOPTransmission OpportunityULUplink | 21,091 |
11943773 | DETAILED DESCRIPTION For simplicity and illustrative purposes, the present invention is described by referring mainly to an exemplary embodiment thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be readily apparent to one of ordinary skill in the art that the present invention may be practiced without limitation to these specific details. In this description, well known methods and structures have not been described in detail so as not to unnecessarily obscure the present invention. UCI Transmission Including SR with PUCCH Format 2 or 3 or 4 In one embodiment, for a UCI transmission on PUCCH format 2 or 3 or 4 that overlaps with one of multiple SR PUCCH resources, X bits are added to the UCI carried on PUCCH to indicate which scheduling request ID is triggered. In this embodiment, assume M is the number of configured schedulingRequestIDs at the UE. One method in this embodiment is to use X=M bits in form of bitmap, where each bit in the bitmap is associated with one of the configured scheduling request IDs which maps to a logical channel ID on the MAC layer. The bits corresponding to the schedulingRequestIDs with triggered SR are set to “1” in the bitmap, otherwise zero (or vice versa). Another method in this embodiment is to use X=ceil(log2(M+1)) to indicate one of the M configured scheduling request IDs that is triggered if SR is present. The additional codepoint “+1” is needed to indicate if no scheduling request has been triggered on any of the M logical channels. In case multiple SR requests corresponding to multiple logical channels are triggered and report the need to transmit data, the indicated schedulingRequestID corresponding to the logical channel with the highest priority is conveyed by X. Although multiple triggered SRs may overlap with SR PUCCH resources, not all of these PUCCH resources have transmission occasions in the same slot where the UCI transmission occurs. Accordingly, a more conservative mapping omits the triggered SRs which cannot, in any event, be added to the UCI. In this embodiment, for a UCI transmission on PUCCH format 2 or 3 or 4 that overlaps with one or multiple SR PUCCH resources, X bits are added to the UCI carried on PUCCH to indicate which scheduling request ID is triggered. Assume L is the number of configured schedulingRequestIDs at the UE for which their corresponding configured SR PUCCH resources have transmission occasions in the slot where the UCI transmission on PUCCH format 2 or 3 or 4 occurs (i.e., in total the UE can be configured with more than L schedulingRequestIDs, but only L overlap with the PUCCH transmission). Which L configured scheduling requests (out of all configured schedulingRequestIDs) overlap are known to the gNB. The ordering can be in an increasing ID number or decreasing ID number. One method in this embodiment is to use X=L bits in form of bitmap, where each bit in the bitmap is associated with one of the L configured scheduling request IDs which maps to a logical channel ID on the MAC layer. The bits corresponding to the schedulingRequestIDs with triggered SR are set to “1” in bitmap, otherwise zero (or vice versa). Another method in this embodiment is to use X=ceil(log2(L+1)) to indicate one of the L configured scheduling request IDs that is triggered if SR is present. The additional codepoint “+1” is needed to indicate if no scheduling request has been triggered on any of the L logical channels. In case multiple SR requests corresponding to multiple logical channels are triggered and report the incoming of new data, the schedulingRequestID corresponding to the logical channel with the highest priority is conveyed by X. FIG.5depicts the operation of the encoding method of these two embodiments (as opposed to the bitmap method), for PUCCH formats 2, 3, or 4. Eleven slots are depicted, ranging from slot n to slot n+10. There are three SR PUCCH resources, each having different periodicities. SR ID 3 has a periodicity of every slot; SR ID 2 has a periodicity of 5 slots (with transmissions in slots n+1, n+6, and n+11); and SR ID 1 has a periodicity of 10 slots (with transmissions in slots n and n+10). UCI transmissions on PUCCH occur in slots n, n+3, n+6, and n+10. However, SRs are triggered only in slots n, n+6, and n+10, as indicated by the “X” in the relevant SR PUCCH resource (corresponding to the relevant SR ID). Table 1 below depicts the implementation of the encoding method of the two embodiments described above, wherein the number of bits X added to UCI to directly report a SR ID are M and L. Table 1 explicitly indicates the encodings of X in each slot for which a UCI transmission occurs on PUCCH. In each cell, the underlined encoding is the one that would be transmitted for the corresponding situation inFIG.5. TABLE 1Encoding of X added bits for Various EmbodimentsFirst EmbodimentSecond EmbodimentSlotX = ceil(log2(M + 1))X = ceil(log2(L + 1))nM = 3, X −> 2 bitsL = 2, X −> 2 bitsX = 00 −> No SRX = 00 −> No SRX = 01 −> SR ID = 1X = 01 −> SR ID = 1X = 10 −> SR ID = 2X = 10 −> SR ID = 3X = 11 −> SR ID = 3X = 11 −> unusedn + 3M = 3, X −> 2 bitsL = 1, X −> 1 bitX = 00 −> No SRX = 0 −> No SRX = 01 −> SR ID = 1X = 1 −> SR ID = 3X = 10 −> SR ID = 2X = 11 −> SR ID = 3n + 6M = 3, X −> 2 bitsL = 2, X −> 2 bitsX = 00 −> No SRX = 00 −> No SRX = 01 −> SR ID = 1X = 01 −> SR ID = 3X = 10 −> SR ID = 2X = 10 −> SR ID = 2X = 11 −> SR ID = 3X = 11 −> unusedn + 10M = 3, X −> 2 bitsL = 2, X −> 2 bitsX = 00 −> No SRX = 00 −> No SRX = 01 −> SR ID = 1X = 01 −> SR ID = 1X = 10 −> SR ID = 2X = 10 −> SR ID = 3X = 11 −> SR ID = 3X = 11 −> unused Considering the first embodiment, M=3 for every slot, as there are three SR IDs at the UE. In slot n, the two X bits identify SR ID 3. In slot n+3, the two X bits indicate that no SR is triggered at the UE. In slot n+6, the two X bits identify SR ID 2, and in slot n+10 they identify SR ID 1. If two or more SRs were triggered in the same slot, the X bits would indicate the highest priority among them. Considering the second embodiment, for slot n, L=2, as there are two SRs triggered in the same slot as a UCI transmission on PUCCH. The two X bits identify SR ID 3 as the only one triggered in that slot. In slot n+3, only one SR PUCCH resource is present in the same slot that UCI is transmitted on PUCCH, therefore L=1 and X is one bit. In this case, the single X bit indicates that no SR is triggered. For both slots n+6 and n+10, two SR PUCCH resources overlap a UCI transmission on PUCCH, and hence L=2 and thus X is two bits in both cases. The encoding of the two X bits—known to both the UE and the gNB—indicates the triggered SR ID, as indicated inFIG.5. If two or more SRs were triggered in the same slot, the X bits would indicate the highest priority among them. Note that in slot n+3, X=1 in this embodiment, as opposed to X=2 in the first embodiment. Of course, the particular encodings of X bits in Table 1 are exemplary only. In other implementations, SR IDs could always be assigned the same encoding, for example matching their SR ID. UCI Transmission Including SR with PUCCH Format 0 In one embodiment, for a UCI transmission on PUCCH format 0 that overlaps with at least one of M SR PUCCH resources, only the two schedulingRequestIDs associated with two logical channels having the highest priority are considered for transmission. If data to be transmitted arrive in the one of these two logical channels with the highest priority, the HARQ-ACK bits are transmitted on PUCCH format 0 resource of the HARQ-ACK-only bits, with the initial cyclic shift being increased by a first amount. For a 2-bit transmission, the cyclic shift is increased by X1 (e.g., X1=1). For a single-bit transmission, the cyclic shift is increased by X2 (e.g., X2=3). If new data arrives in one of these two logical channels having the second priority, the HARQ-ACK bits are transmitted on PUCCH format 0 resource of the HARQ-ACK-only bits with the initial cyclic shift being increased by a second amount. For a 2-bit transmission, the cyclic shift is increased by Y1 (e.g., Y1=2). For a single-bit transmission, the cyclic shift is increased by Y2 (e.g., Y2=4). If both of these logical channels receive new data, only the highest-priority one is assumed for triggering SR, and the cyclic shift increase is X1 or X2. In another embodiment, for a UCI transmission on PUCCH format 0 that overlaps with at least one of M SR PUCCH resources, the corresponding schedulingRequestIDs and their associated logical channels are partitioned into two groups. One group has a higher priority than the other group. If new data arrives for any of the logical channels in the group with the highest priority, the HARQ-ACK bits are transmitted on PUCCH format 0 resource of the HARQ-ACK-only bits, with the initial cyclic shift being increased by a first amount. For a 2-bit transmission, the cyclic shift is increased by X1 (e.g., X1=1). For a single-bit transmission, the cyclic shift is increased by X2 (e.g., X2=3). If new data arrives in any of the logical channels in the group with the second priority, the HARQ-ACK bits are transmitted on PUCCH format 0 resource of the HARQ-ACK-only bits with the initial cyclic shift being increased by a second amount. For a 2-bit transmission, the cyclic shift is increased by Y1 (e.g., Y1=2). For a single-bit transmission, the cyclic shift is increased by Y2 (e.g., Y2=4). If both of these group have at least one logical channel which receives new data, only the group with highest priority is assumed for triggering SR, and the cyclic shift increase is X1 or X2. The two groups can be constructed in different ways. In one embodiment, the groups are constructed by ordering the SR ID in increasing order. Each group then includes every other SR ordered ID. In another embodiment, the highest priority SR IDs are collected to form one group, and the lowest priority SR IDs are collected to form the other group. Note, the groups can be the same or different sizes. If a PUCCH format 0 is configured to only carry one bit, then five cyclic shifts are possible. In this case, the above two embodiments are directly generalized to five schedulingRequestIDs or five groups of schedulingRequestIDs. Another embodiment is shown in Table 2. Here, three different schedulingRequestIDs (or groups thereof) exist, and different combinations of triggered schedulingRequestIDs combinations are mapped to the five code points (five cyclic shifts). In this example, SR ID 2 has highest priority, and SR ID 0 had the lowest priority. A ‘1’ in the table indicates SR has been triggered, ‘0’ indicates not triggered, and X is ‘don't care’ (i.e., it may be either 0 or 1). TABLE 2Mapping of SR IDs to cyclic shifts for PUCCH format 0Cyclic shift mcsSR ID 0SR ID 1SR ID 21X012X10310040115111 Those of skill in the art may readily device different mappings, given the teachings herein. In all of the PUCCH format 0 embodiments described herein, the SR IDs are directly indicated, by predetermined cyclic shifts, rather than indirectly indicating the SR IDs by using cyclic shifts to indicate SR PUCCH resources to which SR IDs are mapped. Methods and Apparatuses FIG.6depicts a method100, performed by a wireless device, of uplink control signaling to a network node in a wireless communication network. A Scheduling Request (SR) corresponding to a logical channel having data to transmit is triggered (block102). A Scheduling Request ID associated with the logical channel is mapped to one or more Physical Uplink Control Channel (PUCCH) resources (block104). If a mapped SR PUCCH resource overlaps with a PUCCH carrying uplink control information (UCI), an indication of the Scheduling Request ID is encoded directly in the UCI (block106), and the UCI, including the Scheduling Request ID indication, is transmitted to the network node on the PUCCH (block108). FIG.7depicts a method200, performed by a node operative in a wireless communication network, of receiving and processing uplink control signaling from a wireless device. A PUCCH transmission of UCI, including a direct indication of at least one Scheduling Request ID identifying a logical channel having data to transmit, is received from the wireless device (block202). The indication of the Scheduling Request ID is extracted to identify the logical channel. The apparatuses described herein may perform the methods100,200herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein. FIG.8for example illustrates a wireless device10as implemented in accordance with one or more embodiments. A wireless device10is any type device capable of communicating with a network node and/or access point using radio signals. A wireless device10may therefore refer to a machine-to-machine (M2M) device, a machine-type communications (MTC) device, a Narrowband Internet of Things (NB IoT) device, etc. The wireless device10may also be referred to as a User Equipment (UE), such as a cellular telephone or “smartphone,” however, the term UE should be understood to encompass any wireless device10. A wireless device10may also be referred to as a radio device, a radio communication device, a wireless device, a wireless terminal, or simply a terminal—unless the context indicates otherwise, the use of any of these terms is intended to include device-to-device UEs or devices, machine-type devices, or devices capable of machine-to-machine communication, sensors equipped with a wireless device, wireless-enabled table computers, mobile terminals, smart phones, laptop-embedded equipped (LEE), laptop-mounted equipment (LME), USB dongles, wireless customer-premises equipment (CPE), etc. In the discussion herein, the terms machine-to-machine (M2M) device, machine-type communication (MTC) device, wireless sensor, and sensor may also be used. It should be understood that these devices, although referred to as UEs, but may be configured to transmit and/or receive data without direct human interaction. In some embodiments, the wireless device10includes a user interface, including e.g. a display, touchscreen, keyboard or keypad, microphone, speaker, and the like) (not shown); in other embodiments, such as in many M2M, MTC, or NB IoT scenarios, the wireless device10may include only a minimal, or no, user interface. The wireless device10also includes processing circuitry14; memory16; and communication circuitry18connected to one or more antennas20, to effect wireless communication across an air interface to one or more radio network nodes, such as a base station, and/or access points. As indicated by the dashed lines, the antenna(s)20may protrude externally from the wireless device10, or the antenna(s)20may be internal. In some embodiments, a wireless device10may additionally include features such as a camera, accelerometer, satellite navigation signal receiver circuitry, vibrating motor, and the like (not depicted inFIG.8). According to embodiments of the present invention, the memory16is operative to store, and the processing circuitry14is operative to execute, software which when executed is operative to cause the wireless device10to directly encode at least one Scheduling Request ID into UCI transmitted in the uplink on PUCCH. In particular, the software, when executed on the processing circuitry14, is operative to perform the method100described and claimed herein. The processing circuitry14in this regard may implement certain functional means, units, or modules. FIG.9illustrates a schematic block diagram of a wireless device30in a wireless network according to still other embodiments. As shown, the wireless device30implements various functional means, units, or modules, e.g., via the processing circuitry14inFIG.8and/or via software code. These functional means, units, or modules, e.g., for implementing the method(s) herein, include for instance: a SR triggering unit32, a SR ID mapping unit34, a SR ID encoding unit36, and a PUCCH transmitting unit38. The SR triggering unit32is configured to trigger a SR corresponding to a logical channel having data to transmit. The SR ID mapping unit34is configured to map a SR ID associated with the logical channel to one or more PUCCH resources. If a mapped SR PUCCH resource overlaps with a PUCCH carrying UCI, the SR ID encoding unit36is configured to encode an indication of the SR ID directly in the UCI, and the PUCCH transmitting unit38is configured to transmit to the network node, on the PUCCH, the UCI including the SR ID indication. FIG.10depicts a network node50operative in a wireless communication network. The network node50may be a serving node of one or more wireless devices10, known in the art as a base station, NodeB, NB, eNB, gNB, Radio Base Station, Base Transceiver Station, Access Point, or the like. The network node50includes processing circuitry52; memory54; and communication circuitry56connected to one or more antennas58, to effect wireless communication across an air interface to one or more wireless devices10. As indicated by the broken connection to the antenna(s)58, the antenna(s)58may be physically located separately from the base station50, such as mounted on a tower, building, or the like. Although the memory54is depicted as being internal to the processing circuitry52, those of skill in the art understand that the memory54may also be external. Those of skill in the art additionally understand that virtualization techniques allow some functions nominally executed by the processing circuitry52to actually be executed by other hardware, perhaps remotely located (e.g., in the so-called “cloud”). According to one embodiment of the present invention, the processing circuitry52is operative to cause the network node50to receive and process uplink control signaling from a wireless device10. In particular, the processing circuitry52is operative to perform the method200described and claimed herein. The processing circuitry52in this regard may implement certain functional means, units, or modules. FIG.11illustrates a schematic block diagram of a base station70in a wireless network according to still other embodiments. As shown, the base station70implements various functional means, units, or modules, e.g., via the processing circuitry52inFIG.10and/or via software code. These functional means, units, or modules, e.g., for implementing the method200herein, include for instance: PUCCH receiving unit72and SR ID extracting unit74. The PUCCH receiving unit72is configured to receive from the wireless device10a PUCCH transmission of UCI, including a direct indication of at least one Scheduling Request ID identifying a logical channel having data to transmit. The SR ID extracting unit64is configured to extract the indication of the Scheduling Request ID to identify the logical channel. Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs. A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above. Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium. In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above. Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium. Embodiments of the present invention provide numerous advantages over the prior art. The PHR can be selectively reported with different sizes of PH fields, and different PHR tables, based on the need and/or UE capability and/or configuration. A better flexibility is thus achieved. The PHR report is achieved with better accuracy, fitting in particular with the NR demands. Although embodiments of the present invention are discussed herein with reference to LTE, NR, LTE-M, and NB-IoT, e.g., referring to UEs, eNB, gNB, and the like, the invention is not limited to these standardized wireless communication network protocols. Rather, embodiments of the present invention may be advantageously deployed in any wireless communication network in which power headroom or max power reporting may require large dynamic range, necessitating the use of more than one format (e.g., 6-bit and 7-bit formats). As such, those of skill in the art will understand that the claims are to be construed broadly—for example, the term “base station” encompasses any wireless network node that serves as an access point, or RAN terminal, for wireless communication with wireless devices. As used herein, the phrase “one of A and B” means the logical OR of A and B (as opposed to XOR), and is satisfied by one or more A without B, one or more B without A, or any number of A together with any number of B. The present invention may, of course, be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the invention. The present embodiments are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein. Over the Top Embodiments Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated inFIG. QQ1. For simplicity, the wireless network ofFIG. QQ1only depicts network QQ106, network nodes QQ160and QQ160b, and WDs QQ110, QQ110b, and QQ110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160and wireless device (WD) QQ110are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network. The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-IoT), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards. Network QQ106may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices. Network node QQ160and WD QQ110comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network. InFIG. QQ1, network node QQ160includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160illustrated in the example wireless network ofFIG. QQ1may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180may comprise multiple separate hard drives as well as multiple RAM modules). Similarly, network node QQ160may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180for the different RATs) and some components may be reused (e.g., the same antenna QQ162may be shared by the RATs). Network node QQ160may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160. Processing circuitry QQ170is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170may include processing information obtained by processing circuitry QQ170by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Processing circuitry QQ170may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160components, such as device readable medium QQ180, network node QQ160functionality. For example, processing circuitry QQ170may execute instructions stored in device readable medium QQ180or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170may include a system on a chip (SOC). In some embodiments, processing circuitry QQ170may include one or more of radio frequency (RF) transceiver circuitry QQ172and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172and baseband processing circuitry QQ174may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172and baseband processing circuitry QQ174may be on the same chip or set of chips, boards, or units In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170alone or to other components of network node QQ160, but are enjoyed by network node QQ160as a whole, and/or by end users and the wireless network generally. Device readable medium QQ180may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170and, utilized by network node QQ160. Device readable medium QQ180may be used to store any calculations made by processing circuitry QQ170and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170and device readable medium QQ180may be considered to be integrated. Interface QQ190is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190comprises port(s)/terminal(s) QQ194to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190also includes radio front end circuitry QQ192that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192comprises filters QQ198and amplifiers QQ196. Radio front end circuitry QQ192may be connected to antenna QQ162and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162and processing circuitry QQ170. Radio front end circuitry QQ192may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components. In certain alternative embodiments, network node QQ160may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170may comprise radio front end circuitry and may be connected to antenna QQ162without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172may be considered a part of interface QQ190. In still other embodiments, interface QQ190may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown). Antenna QQ162may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162may be coupled to radio front end circuitry QQ190and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna QQ162may be separate from network node QQ160and may be connectable to network node QQ160through an interface or port. Antenna QQ162, interface QQ190, and/or processing circuitry QQ170may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment. Power circuitry QQ187may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160with power for performing the functionality described herein. Power circuitry QQ187may receive power from power source QQ186. Power source QQ186and/or power circuitry QQ187may be configured to provide power to the various components of network node QQ160in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186may either be included in, or external to, power circuitry QQ187and/or network node QQ160. For example, network node QQ160may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used. Alternative embodiments of network node QQ160may include additional components beyond those shown inFIG. QQ1that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160may include user interface equipment to allow input of information into network node QQ160and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160. As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal. As illustrated, wireless device QQ110includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-IoT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110. Antenna QQ111may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111may be separate from WD QQ110and be connectable to WD QQ110through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ111may be considered an interface. As illustrated, interface QQ114comprises radio front end circuitry QQ112and antenna QQ111. Radio front end circuitry QQ112comprise one or more filters QQ118and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111and processing circuitry QQ120. Radio front end circuitry QQ112may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122may be considered a part of interface QQ114. Radio front end circuitry QQ112may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components. Processing circuitry QQ120may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110components, such as device readable medium QQ130, WD QQ110functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120may execute instructions stored in device readable medium QQ130or in memory within processing circuitry QQ120to provide the functionality disclosed herein. As illustrated, processing circuitry QQ120includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120of WD QQ110may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124and application processing circuitry QQ126may be combined into one chip or set of chips, and RF transceiver circuitry QQ122may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122and baseband processing circuitry QQ124may be on the same chip or set of chips, and application processing circuitry QQ126may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122may be a part of interface QQ114. RF transceiver circuitry QQ122may condition RF signals for processing circuitry QQ120. In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120alone or to other components of WD QQ110, but are enjoyed by WD QQ110as a whole, and/or by end users and the wireless network generally. Processing circuitry QQ120may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Device readable medium QQ130may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120and device readable medium QQ130may be considered to be integrated. User interface equipment QQ132may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132installed in WD QQ110. For example, if WD QQ110is a smart phone, the interaction may be via a touch screen; if WD QQ110is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120to allow processing circuitry QQ120to process the input information. User interface equipment QQ132may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120to output information from WD QQ110. User interface equipment QQ132may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein. Auxiliary equipment QQ134is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134may vary depending on the embodiment and/or scenario. Power source QQ136may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110may further comprise power circuitry QQ137for delivering power from power source QQ136to the various parts of WD QQ110which need power from power source QQ136to carry out any functionality described or indicated herein. Power circuitry QQ137may in certain embodiments comprise power management circuitry. Power circuitry QQ137may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137may perform any formatting, converting, or other modification to the power from power source QQ136to make the power suitable for the respective components of WD QQ110to which power is supplied. FIG. QQ2illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ2200may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated inFIG. QQ2, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, althoughFIG. QQ2is a UE, the components discussed herein are equally applicable to a WD, and vice-versa. InFIG. QQ2, UE QQ200includes processing circuitry QQ201that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221may include other similar types of information. Certain UEs may utilize all of the components shown inFIG. QQ2, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. InFIG. QQ2, processing circuitry QQ201may be configured to process computer instructions and data. Processing circuitry QQ201may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer. In the depicted embodiment, input/output interface QQ205may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200may be configured to use an input device via input/output interface QQ205to allow a user to capture information into UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor. InFIG. QQ2, RF interface QQ209may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211may be configured to provide a communication interface to network QQ243a. Network QQ243amay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243amay comprise a Wi-Fi network. Network connection interface QQ211may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately. RAM QQ217may be configured to interface via bus QQ202to processing circuitry QQ201to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221may be configured to include operating system QQ223, application program QQ225such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems. Storage medium QQ221may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221may allow UE QQ200to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221, which may comprise a device readable medium. InFIG. QQ2, processing circuitry QQ201may be configured to communicate with network QQ243busing communication subsystem QQ231. Network QQ243aand network QQ243bmay be the same network or networks or different network or networks. Communication subsystem QQ231may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233and/or receiver QQ235to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233and receiver QQ235of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately. In the illustrated embodiment, the communication functions of communication subsystem QQ231may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243bmay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243bmay be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200. The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231may be configured to include any of the components described herein. Further, processing circuitry QQ201may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware. FIG. QQ3is a schematic block diagram illustrating a virtualization environment QQ300in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks). In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized. The functions may be implemented by one or more applications QQ320(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320are run in virtualization environment QQ300which provides hardware QQ330comprising processing circuitry QQ360and memory QQ390. Memory QQ390contains instructions QQ395executable by processing circuitry QQ360whereby application QQ320is operative to provide one or more of the features, benefits, and/or functions disclosed herein. Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1which may be non-persistent memory for temporarily storing instructions QQ395or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2having stored therein software QQ395and/or instructions executable by processing circuitry QQ360. Software QQ395may include any type of software including software for instantiating one or more virtualization layers QQ350(also referred to as hypervisors), software to execute virtual machines QQ340as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein. Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350or hypervisor. Different embodiments of the instance of virtual appliance QQ320may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways. During operation, processing circuitry QQ360executes software QQ395to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350may present a virtual operating platform that appears like networking hardware to virtual machine QQ340. As shown inFIG. QQ3, hardware QQ330may be a standalone network node with generic or specific components. Hardware QQ330may comprise antenna QQ3225and may implement some functions via virtualization. Alternatively, hardware QQ330may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, virtual machine QQ340may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE). Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340on top of hardware networking infrastructure QQ330and corresponds to application QQ320inFIG. QQ3. In some embodiments, one or more radio units QQ3200that each include one or more transmitters QQ3220and one or more receivers QQ3210may be coupled to one or more antennas QQ3225. Radio units QQ3200may communicate directly with hardware nodes QQ330via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be effected with the use of control system QQ3230which may alternatively be used for communication between the hardware nodes QQ330and radio units QQ3200. FIG. QQ4illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference toFIGURE QQ4, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412cis connectable to core network QQ414over a wired or wireless connection QQ415. A first UE QQ491located in coverage area QQ413cis configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492in coverage area QQ413ais wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412. Telecommunication network QQ410is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421and QQ422between telecommunication network QQ410and host computer QQ430may extend directly from core network QQ414to host computer QQ430or may go via an optional intermediate network QQ420. Intermediate network QQ420may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420may comprise two or more sub-networks (not shown). The communication system ofFIG. QQ4as a whole enables connectivity between the connected UEs QQ491, QQ492and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430and the connected UEs QQ491, QQ492are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450may be transparent in the sense that the participating communication devices through which OTT connection QQ450passes are unaware of routing of uplink and downlink communications. For example, base station QQ412may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491towards the host computer QQ430. Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG. QQ5.FIG. QQ5illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system QQ500, host computer QQ510comprises hardware QQ515including communication interface QQ516configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510further comprises software QQ511, which is stored in or accessible by host computer QQ510and executable by processing circuitry QQ518. Software QQ511includes host application QQ512. Host application QQ512may be operable to provide a service to a remote user, such as UE QQ530connecting via OTT connection QQ550terminating at UE QQ530and host computer QQ510. In providing the service to the remote user, host application QQ512may provide user data which is transmitted using OTT connection QQ550. Communication system QQ500further includes base station QQ520provided in a telecommunication system and comprising hardware QQ525enabling it to communicate with host computer QQ510and with UE QQ530. Hardware QQ525may include communication interface QQ526for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527for setting up and maintaining at least wireless connection QQ570with UE QQ530located in a coverage area (not shown inFIG. QQ5) served by base station QQ520. Communication interface QQ526may be configured to facilitate connection QQ560to host computer QQ510. Connection QQ560may be direct or it may pass through a core network (not shown inFIG. QQ5) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525of base station QQ520further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520further has software QQ521stored internally or accessible via an external connection. Communication system QQ500further includes UE QQ530already referred to. Its hardware QQ535may include radio interface QQ537configured to set up and maintain wireless connection QQ570with a base station serving a coverage area in which UE QQ530is currently located. Hardware QQ535of UE QQ530further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530further comprises software QQ531, which is stored in or accessible by UE QQ530and executable by processing circuitry QQ538. Software QQ531includes client application QQ532. Client application QQ532may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512may communicate with the executing client application QQ532via OTT connection QQ550terminating at UE QQ530and host computer QQ510. In providing the service to the user, client application QQ532may receive request data from host application QQ512and provide user data in response to the request data. OTT connection QQ550may transfer both the request data and the user data. Client application QQ532may interact with the user to generate the user data that it provides. It is noted that host computer QQ510, base station QQ520and UE QQ530illustrated inFIG. QQ5may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412cand one of UEs QQ491, QQ492ofFIG. QQ4, respectively. This is to say, the inner workings of these entities may be as shown inFIG. QQ5and independently, the surrounding network topology may be that ofFIG. QQ4. InFIG. QQ5, OTT connection QQ550has been drawn abstractly to illustrate the communication between host computer QQ510and UE QQ530via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530or from the service provider operating host computer QQ510, or both. While OTT connection QQ550is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). Wireless connection QQ570between UE QQ530and base station QQ520is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE QQ530using OTT connection QQ550, in which wireless connection QQ570forms the last segment. More precisely, the teachings of these embodiments may improve the network access performance and thereby provide benefits such as more orderly network access when large numbers of wireless devices attempt simultaneous access, thus reducing the instantaneous processing load at the base station, and preserving battery power in the wireless devices due to decreased repeated access attempts. A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550between host computer QQ510and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550may be implemented in software QQ511and hardware QQ515of host computer QQ510or in software QQ531and hardware QQ535of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511, QQ531may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511and QQ531causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550while it monitors propagation times, errors etc. FIG. QQ6is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS. QQ4and QQ5. For simplicity of the present disclosure, only drawing references toFIG. QQ6will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611(which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630(which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640(which may also be optional), the UE executes a client application associated with the host application executed by the host computer. FIG. QQ7is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS. QQ4and QQ5. For simplicity of the present disclosure, only drawing references toFIG. QQ7will be included in this section. In step QQ710of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ730(which may be optional), the UE receives the user data carried in the transmission. FIG. QQ8is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS. QQ4and QQ5. For simplicity of the present disclosure, only drawing references toFIG. QQ8will be included in this section. In step QQ810(which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821(which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811(which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830(which may be optional), transmission of the user data to the host computer. In step QQ840of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. FIG. QQ9is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS. QQ4and QQ5. For simplicity of the present disclosure, only drawing references toFIG. QQ9will be included in this section. In step QQ910(which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920(which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930(which may be optional), the host computer receives the user data carried in the transmission initiated by the base station. Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description. The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. The following specific embodiments illustrate implementation of embodiments of the present invention in Over the Top embodiments, with reference to the claims: Group A Embodiments include claims1-14and embodiment AA: AA. The method of any of claims1-14, further comprising: providing user data; andforwarding the user data to a host computer via the transmission to the base station. Group B Embodiments include claims29-42and embodiment BB: BB. The method of any of claims29-42, further comprising:obtaining user data; andforwarding the user data to a host computer or a wireless device. Group C Embodiments: C1. A wireless device configured to perform any of the steps of any of the Group A embodiments. C2. A wireless device comprising:processing circuitry configured to perform any of the steps of any of the Group A embodiments; andpower supply circuitry configured to supply power to the wireless device. C3. A wireless device comprising:processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the Group A embodiments. C4. A user equipment (UE) comprising:an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda battery connected to the processing circuitry and configured to supply power to the UE. C5. A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A embodiments. C6. A carrier containing the computer program of embodiment C5, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. C7. A base station configured to perform any of the steps of any of the Group B embodiments. C8. A base station comprising:processing circuitry configured to perform any of the steps of any of the Group B embodiments;power supply circuitry configured to supply power to the wireless device. C9. A base station comprising:processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the base station is configured to perform any of the steps of any of the Group B embodiments. C10. A computer program comprising instructions which, when executed by at least one processor of a base station, causes the base station to carry out the steps of any of the Group B embodiments. C11. A carrier containing the computer program of embodiment C10, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. Group D Embodiments: D1. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments. D2. The communication system of the pervious embodiment further including the base station. D3. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. D4. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE comprises processing circuitry configured to execute a client application associated with the host application. D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. D6. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. D7. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments. D9. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments. D10. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. D11. The communication system of the previous 2 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE's processing circuitry is configured to execute a client application associated with the host application. D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. D13. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. D14. A communication system including a host computer comprising:communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments. D15. The communication system of the previous embodiment, further including the UE. D16. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. D17. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. D18. The communication system of the previous 4 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. D20. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. D21. The method of the previous 2 embodiments, further comprising:at the UE, executing a client application, thereby providing the user data to be transmitted; andat the host computer, executing a host application associated with the client application. D22. The method of the previous 3 embodiments, further comprising:at the UE, executing a client application; andat the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,wherein the user data to be transmitted is provided by the client application in response to the input data. D23. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments. D24. The communication system of the previous embodiment further including the base station. D25. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. D26. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application;the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. D28. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. D29. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer. | 100,867 |
11943774 | DETAILED DESCRIPTION OF EMBODIMENTS Before a detailed description of the embodiments under reference ofFIG.3is given, general explanations are made. As mentioned in the outset, in general, several generations of mobile telecommunications systems are known, e.g. the third generation (“3G”), which is based on the International Mobile Telecommunications-2000 (IMT-2000) specifications, the fourth generation (“4G”), which provides capabilities as defined in the International Mobile Telecommunications-Advanced Standard (IMT-Advanced Standard), and the current fifth generation (“5G”), which is under development and which might be put into practice in the year 2020. One of the candidates for meeting the 5G requirements are termed New Radio (NR) Access Technology Systems. Some aspects of NR can be based on LTE technology, in some embodiments, just as some aspects of LTE were based on previous generations of mobile communications technology. As mentioned in the outset, two new functionalities for the New Radio (NR) Access Technology, which are discussed, are Enhanced Mobile Broadband (eMBB) and Ultra Reliable & Low Latency Communications (URLLC) services. A typical embodiment of an NR radio access network RAN1is illustrated inFIG.1. The RAN1has a macro cell2, which is established by an LTE eNodeB3, and an NR cell4, which is established by an NR eNodeB5(also referred to as gNB (next generation eNodeB)). A UE6can communicate with the LTE eNodeB3and, as long as it is within the NR cell4, it can also communicate with the NR eNodeB5. As mentioned, eMBB services are characterized in some embodiments by high capacity with a requirement to support up to 20 Gb/s. For efficient transmission of large amounts of data at high throughput, eMBB requires a long scheduling time so as to minimize the overhead used (wherein, in some embodiments, the “scheduling time” is the time to allocate and transmit a data packet). In some embodiments, as mentioned, a requirement for URLLC is low latency measured from the ingress of a layer2packet to its egress from the network, with a proposed target of 1 ms, without limiting the present disclosure in that regard, and another requirement for URLLC is a reliability of 1-105(99.999%) for one transmission of a 32 byte packet. The URLLC data may be expected to be short and hence a short scheduling time where the control and data have short duration are required in some embodiments within a frame duration that is significantly less than that of the eMBB frame. In some embodiments, the reliability aspect of URLLC is addressed through the use of LDPC codes (Low Density Parity Check codes), low coding rates (with low spectral efficiency), high aggregation levels for control channels and the support of multiple antennas at both the transmitter and receiver. Introduction of a new CQI table (Channel Quality Indicator), having entries with low spectral efficiency, allows URLLC to operate in a spectrally efficient manner, in some embodiments, where the scheduled modulation and coding scheme (MCS) can be chosen to meet the reliability criteria in the current channel conditions. Another aspect, in some embodiments, of URLLC operation for a UE is that the URLLC transmission may pre-empt an existing transmission, in particular if the ongoing transmission is of lower priority, e.g. an enhanced Mobile Broadband (eMBB) transmission that is typically more delay tolerant than a URLLC transmission. Such a pre-emption may occur within or for the same UE. An example is illustrated inFIG.2, where at time to (abscissa, ordinate shows frequency) in a Slot n, the gNB (5, see exemplaryFIG.1) transmits a DCI (Downlink Control Information) carrying a DL Grant #1 to schedule a PDSCH (Physical Downlink Shared Channel) for an eMBB transmission at time t1. At time t2, a URLLC packet arrives for another UE and since it has a low latency, the gNB transmits a DL Grant #2 to schedule another PDSCH for this URLLC transmission at time t3in the same slot, i.e. Slot n. In this case, there are not sufficient resources available and, thus, the gNB schedules the URLLC transmission to occupy some of the resources originally scheduled for the eMBB transmission, which started at time t1, thereby pre-empting this eMBB transmission. In some embodiments, the physical channels involved in the transmission of URLLC may be enhanced to ensure that the URLLC requirements are met. It has been recognized that apart from improving the reliability and latency for the data channels, such as PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), that carry the URLLC packet, the control channels such as PDCCH (Physical Downlink Control Channel) and PUCCH (Physical Uplink Control Channel) that carry the scheduling and feedback for URLLC transmission are improved in some embodiments. In Rel-15, at the physical layer, the PDSCH or PUSCH packets are not differentiated by their service. That is at the physical layer the UE is unaware whether the DL grant for a PDSCH or UL grant for a PUSCH is for a URLLC or an eMBB transmission. However, in Rel-15, separate MCS (Modulation and Coding Scheme) tables for PDSCH and PUSCH are introduced for URLLC, wherein the entries in these MCS tables include low spectral efficiency MCS, which are targeted at high reliability transmission. Thus, in some embodiments, the network can configure the UE to use one of these high reliability MCS tables and additionally, the UE can also be configured with a separate RNTI (Radio Network Temporary Identifier), where a DCI (Downlink Control Information) with CRC (Cyclic Redundancy Check) masked with this RNTI would indicate to the UE to use the high reliability MCS table rather than the normal MCS table for its transmissions. The use of a different RNTI therefore implicitly allows some level of service (URLLC or eMBB) awareness at the physical layer in some embodiments. Thus, some embodiments pertain to enhancements in transmitting the uplink channels PUSCH and PUCCH if the UE is aware that the grant is for a URLLC packet. In some embodiments, it is assumed that the URLLC service is known either implicitly (e.g. through the use of a different MCS table) or explicitly. Consequently, some embodiments pertain to a base station for a mobile telecommunications system comprising circuitry configured to communicate with at least one user equipment, wherein the circuitry is further configured to indicate use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for use by the at least one user equipment for a data transmission, wherein, for example, the first and second sets of uplink channel transmission parameters differ from each other and/or are independent of each other. Some embodiments pertain to a user equipment for a mobile telecommunications system comprising circuitry configured to communicate with at least one base station, wherein the circuitry is further configured to receive an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for a data transmission, wherein, for example, the first and second sets of uplink channel transmission parameters differ from each other and/or are independent of each other. In this specification, an eMBB transmission is an example for a “long data transmission” (or “long term transmission”) and a URLLC transmission is an example for a “short data transmission” (or “short term transmission”). The data transmission may be an uplink or a downlink transmission and it may be short data or a long data transmission, it may be a control (data) transmission, and, thus, it is not limited to user data, but covers also control data or other data. The data transmission may be or may not be carried by a PUSCH, PUCCH or a PDSCH, PDCCH, without limiting the present disclosure in that regard. The base station may be based on the principles of LTE (LTE-A) and/or it may be based on NR RAT, as also discussed above. The base station may be based on the known eNodeB of LTE, as one example, or it may be based on the discussed NR gNodeB. The user equipment may be, for example, a mobile phone, smartphone, a computer, tablet, tablet personal computer, or the like, including a mobile communication interface, or any other device which is able to perform a mobile telecommunication via, for example, LTE or NR, such as a hot spot device with a mobile communication interface, etc. In some embodiments, the data transmission is an uplink data transmission from the user equipment to a base station and, additionally, it may be a short data transmission or a long data transmission, as mentioned above. In some embodiments, the first set of uplink channel transmission parameters refers to a short data transmission and the second set of uplink channel transmission parameters refers to a long data transmission. Hence, by indicating (by the base station) whether the first set or the second set of uplink channel transmission parameters is to be used by the user equipment, the user equipment can use a corresponding set of uplink channel transmission parameters which is adapted to the short data or to the long data transmission. The first and/or the second set of uplink channel transmission parameters may be predefined or it may be (dynamically) configured by the network. The indication indicates which or both of the first set and the second set of uplink channel transmission should be use by the user equipment for the data transmission. In some embodiments, the use of the first set and the second set of uplink channel transmission parameters is explicitly or implicitly indicated (by the base station) based on, for example at least one of the following: radio network temporary identifier, downlink control information format, physical downlink control channel control resource set, search space, usage of grant free resource for a physical uplink shared channel, occupation of number of slots, radio resource control. Hence, the user equipment can receive such an indication and based on the indication it determines which of the sets of uplink channel transmission parameters is to be used for its data transmission. In some embodiments, the use of the first set and the second set of uplink channel transmission parameters is implicitly indicated (by the base station) based on a signaled physical uplink control channel resource and based on at least one of the following: physical uplink control channel resource set identification, physical uplink control channel resource identification, group of resource identifications. Hence, the user equipment can receive such an implicit indication and based on the indication it determines which of the sets of uplink channel transmission parameters is to be used for its data transmission. As will also become apparent from the following discussion, in some embodiments, by indicating which of the first and second set of uplink channel transmission parameters is to be used, it is also (indirectly or implicitly) indicated that the (or at least one) parameters of the first or second set of uplink channel transmission parameters are to be used. For instance, if the first set of uplink channel transmission parameters is indicated to be used, the parameters (or at least one parameter) included in the first set of uplink channel transmission parameters are to be used and if the second set of uplink channel transmission parameters is indicated to be used, the parameters (or at least one parameter) included in the second set of uplink parameters are to be used. The set of uplink channel transmission parameters and/or the parameters itself may be configured in an RRC connection setup in some embodiments. In some embodiments, the indication of the use of the first and second set of uplink channel transmission parameters indicates a power control parameter, which is included in the first and/or second set of uplink channel transmission parameters, wherein the first and second sets of uplink channel transmission parameters are associated with a power control parameter, e.g. different power control parameters (a first for the first set and a second power control parameter for the second set of uplink channel transmission parameters, wherein the first and the second power control parameter may be different). Hence, the user equipment can, for example, adapt a transmission power based on the indication received from the base station, such that, e.g., for the short data transmission and the long data transmission different power control parameters are used. In some embodiments, the power control parameter is associated with the indicated use of the first and second set of uplink channel transmission parameters. For instance, if the use of the first set of uplink channel transmission parameters is indicated, a first power control parameter is used, wherein a second power control parameter is used, if the use of the second set of uplink channel transmission parameters is indicated. In some embodiments, the first and the second sets of uplink channel transmission parameters are associated with different physical uplink control channel resources, such that, for example, the user equipment may use respective different physical uplink control channel resources based on the indication and, thus, e.g., different physical uplink control channel resources for the short data and the long data transmission. In some embodiments, the indication of the use of the first and second set of uplink channel transmission parameters indicates a repetition to be used in an uplink or a downlink transmission (e.g. the first and second sets of uplink channel transmission parameters are associated with a repetition to be used in an uplink or a downlink transmission, e.g. a first repetition for the first set and a second repetition for the second set of uplink channel transmission parameters), which might be included in or associated with the first and/or second set of uplink channel transmission parameters, such that the user equipment can apply an according repetition, for example, of PUCCH/PUSCH or PDCCH/PDSCH candidates. In some embodiments, the indication of the use of the first and second set of uplink channel transmission parameters indicates a delay for at least one of a physical downlink shared channel and an physical uplink control channel (e.g. the first and second sets of uplink channel transmission parameters are associated with a delay for at least one of: physical downlink shared channel and physical uplink control channel, e.g. a first delay for the first set and a second delay for the second set of uplink channel transmission parameters), which might be included in or associated with the first and/or second set of uplink channel transmission parameters, such that user equipment may apply an according delay for the data transmission in response to the detected or determined indication, e.g., different delays for the short data and the long data transmission. The delay may be such applied that a delay (time interval) is caused (introduced) between the physical downlink shared channel and the physical uplink control channel. In some embodiments, the indication of the use of the first and second set of uplink channel transmission parameters indicates frequency hopping parameters (e.g. the first and second sets of uplink channel transmission parameters are associated with a frequency hopping pattern, e.g. a first frequency hopping pattern for the first set and a second frequency hopping pattern for the second set of uplink channel transmission parameters), which might be included in or associated with the first and/or second set of uplink channel transmission parameters, such that the user equipment may apply an according frequency hopping pattern for the data transmission in response to the determined indication, e.g., different frequency hopping switching frequency for the short data and the long data transmission. In some embodiments, the indication of the use of the first and second set of uplink channel transmission parameters indicates a transmit diversity scheme (e.g. the first and second sets of uplink channel transmission parameters are associated with a transmit diversity scheme, e.g. a first transmit diversity scheme for the first set and a second transmit diversity scheme for the second set of uplink channel transmission parameters), which might be included in or associated with the first and/or second set of uplink channel transmission parameters, such that the user equipment may apply transmit diversity for the data transmission in a manner according to the determined indication. For example, the user equipment may apply a different number of transmit antennas for the short data and the long data transmission or may apply a different mapping between transmit antennas and reference signals for the short data and long data transmissions. In some embodiments, the indication of the use of the first and second set of uplink channel transmission parameters indicates whether piggybacking is used, which might be included in or associated with the first and/or second set of uplink channel transmission parameters, such that the user equipment may decide on the basis of the indication, whether piggybacking is used in the data transmission, such as the short data or long data transmission. In some embodiments, the usage of piggybacking of uplink control information is indicated, which might be included in or associated with the first and/or second set of uplink channel transmission parameters, such that the user equipment may decide on the basis of the indication, whether uplink control information is piggybacked in the data transmission or not. In some embodiments, piggybacking of uplink control information onto the data transmission is not used (by the user equipment) if the use of the first set of uplink channel transmission parameters is indicated for the data transmission. In some embodiments, piggybacking of uplink control information is used (by the user equipment) if the use of the first set of uplink channel transmission parameters is indicated for the data transmission and the amount of uplink control information is below a threshold. The threshold may be indicative of a number of bits and, for example, if the number of bits of the uplink control information is below the threshold, the user equipment decides to piggyback the uplink control information. In some embodiments, piggybacking of uplink control information is not used or rejected (by the user equipment) when use of the first set of uplink channel transmission parameters is indicated and when the uplink control information is carried by a physical uplink control channel using the second set of uplink channel transmission parameters. For instance, in LTE, when a UCI carried by a PUCCH collides with a PUSCH transmission in the same UE, the UCI information is added to the PUSCH transmission, i.e. piggybacked. However, as a short data transmission such as URLLC, requires high reliability, piggybacking additional information may reduce its performance, and, thus, if the use of the first set of uplink channel transmission parameters is indicated, piggybacking is rejected. In some embodiments, piggybacking of uplink control information is used (by the user equipment) when the use of the first set of uplink channel transmission parameters is indicated for the data transmission and when the uplink control information is carried by a physical uplink control channel using the first set of uplink channel transmission parameters. For example, when a PUCCH collides with a PUSCH in the same UE and the PUSCH uses the 1stset of uplink channel transmission parameters, piggybacking of the UCI onto the PUSCH is accepted if the UCI is carried by a PUCCH using the 1stset of uplink channel transmission parameters. In some embodiments, when two physical uplink shared channels collide (in the user equipment), the physical uplink shared channel using the first set of uplink channel transmission parameters has priority over the physical uplink shared channel using the second set of uplink channel transmission parameters, such that the user equipment may prioritize the PUSCH using the first set of uplink channel transmission parameters. In one prioritization scheme, the PUSCH using the first set of uplink channel transmission parameters is transmitted and the PUSCH using the second set of uplink transmission parameters is not transmitted. In another prioritization scheme, the power applied to the PUSCH using the first set of uplink channel transmission parameters is increased relative to the power applied to the PUSCH using the second set of uplink channel transmission parameters. In some embodiments, wherein, when two physical uplink shared channels collide and the two physical uplink shared channels use the first set of uplink channel transmission parameters, the later physical uplink shared channel has priority over the earlier physical uplink shared channel, such that the user equipment may prioritize the later physical uplink shared channel. In one prioritization scheme, the later PUSCH is transmitted and the earlier PUSCH is not transmitted. In another prioritization scheme, the power applied to the later PUSCH is increased relative to the power applied to the earlier PUSCH. In some embodiments, when two physical uplink control channels collide (in the user equipment), the physical uplink control channel using the first set of uplink channel transmission parameters has priority over the physical uplink control channel using the second set of uplink channel transmission parameters, such that the user equipment may prioritize the PUCCH using the first set of uplink channel transmission parameters. In one prioritization scheme, the PUCCH using the first set of uplink channel transmission parameters is transmitted and the PUCCH using the second set of uplink transmission parameters is not transmitted. In another prioritization scheme, the power applied to the PUCCH using the first set of uplink channel transmission parameters is increased relative to the power applied to the PUCCH using the second set of uplink channel transmission parameters. In some embodiments, when two physical uplink control channels using the first set of uplink channel transmission parameters collide (in the user equipment), uplink control information of both physical uplink control channels are jointly coded (by the user equipment) into a single physical uplink control channels transmission. Some embodiments pertain to a circuitry for a base station, as described herein, for a mobile telecommunications system configured to communicate with at least one user equipment, wherein the circuitry is further configured to indicate use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameter for use by the at least one user equipment for a data transmission, as discussed herein. Some embodiments pertain to a circuitry for a user equipment, as described herein, for a mobile telecommunications system configured to communicate with at least one base station, wherein the circuitry is further configured to receive an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for a data transmission, as discussed herein. Some embodiments pertain to a mobile telecommunications system, as described herein, configured to provide communication between at least one base station and at least one user equipment, wherein the at least one base station, as discussed herein, comprises circuitry configured to indicate use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameter for use by the at least one user equipment for a data transmission, and wherein the at least one user equipment, as discussed herein, comprises circuitry configured to receive an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for the data transmission. Some embodiments pertain to a mobile telecommunications system method for providing communication between at least one base station and at least one user equipment, including: indicating use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameter for use by the at least one user equipment for a data transmission, as discussed herein; and or receiving an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for the data transmission, as discussed herein. Returning back toFIG.3, there is illustrated the basic principle used in some embodiments, namely to provide at least two sets of uplink channel transmission parameters10,11, one (first) set10for PUSCH & PUCCH and another 11 for PUSCH & PUCCH (in other embodiments further sets of parameters may be provided). The first set of uplink transmission parameters is targeted at and used for a URLLC transmission, i.e. with low latency and high reliability, whereas the second set11of uplink transmission parameters is targeted at and used for non-URLLC transmission, e.g. eMBB. The transmission parameters and/or its values in the 1st10 and 2nd11 sets are different. Other transmission parameters not defined in the 1stand 2ndsets are common for both URLLC and eMBB transmissions. As illustrated inFIG.4, which shows the same RAN1as illustrated inFIG.1and explained above, the LTE eNodeB3and/or the gNB5may transmit the first and second sets of uplink transmission parameters to the UE6and/or may indicate to the UE6whether to use the first10or second11set of uplink transmission parameters. The sets of uplink channel transmission parameters to be used are indicated using one or more of the following possibilities in some embodiments: Different RNTI: that is the first set of uplink channel parameters are implicitly indicated using an RNTI that is different to that used by the second set of uplink channel parameters. DCI Format: A different DCI format is used when the first set is to be used from when the second set is to be used. PDCCH control resource set (CORESET)/search space: the sets of uplink channel parameters are implicitly indicated by the CORESET and/or search space in which a PDCCH is detected. The sets of uplink channel transmission parameters corresponding to CORESETs and/or search spaces can be indicated using RRC signalling. For example, if a PDCCH is received in a first CORESET, the first set of uplink channel parameters is used whereas if a PDCCH is received in a second CORESET, the second set of uplink channel parameters is used. Grant free resource space: some grant free resources are associated with the first set of uplink channel parameters and other grant free resources are associated with the second set of uplink channel parameters. The set of uplink channel parameters to use then depends on the grant free resources used for the PUSCH transmission. In an example different grant free resources are used for URLLC and eMBB and the different grant free resources are associated with different uplink channel parameters. The scheduled PDSCH/PUSCH occupies a predetermined number of mini-slots, e.g. if the scheduled PDSCH/PUSCH occupies, e.g. two mini-slots then it uses the 1stset of parameters otherwise it uses the 2ndset of parameters The sets can be implicitly indicated via the PUCCH resource that the UE is signalled to use. The linkage between PUCCH resources and set of uplink transmission parameters can be based on one or more of the following in some embodiments: PUCCH resource set ID. There are up to four PUCCH resource sets. The PUCCH resource set that the UE is to use is signalled via RRC (Radio Resource Control). A group of resource IDs (within a PUCCH resource set) that is indicated using DCI or PDCCH, wherein either the Resource IDs associated with some PDCCH CCEs (control channel elements) are associated with one set of uplink transmission parameters (certain PUCCH resource IDs within the PUCCH resource set are associated with PDCCH that start at a certain CCE), or Resource IDs associated with certain ‘PUCCH resource indication’ DCI bits are associated with one set of uplink transmission parameters (the ‘PUCCH resource indication’ is provided in a 3 bit field within the DCI). As an example of the use of the PUCCH resource indication, if these 3 bits indicate a value between ‘000’ and ‘011’, the first set of uplink transmission parameters is used, otherwise the second set of uplink transmission parameters is used. The linkage between PUCCH resources and set of uplink transmission parameters can also be based on PUCCH resource ID. There are up to 128 PUCCH resource IDs. Some resource IDs (e.g. resource IDs 0→63) can be associated with the first set of uplink transmission parameters, some resource IDs (e.g. resource IDs 64→127) with the second set of uplink transmission parameters. The set of parameters may also be indicated based on RRC configuration: The network RRC-configures which set of uplink channel transmission parameters to use. In an embodiment, as illustrated inFIG.5, the said different sets10,11of uplink channel transmission parameters indicate a power control offset parameter. When the UE is indicated at20to use the first set of uplink channel transmission parameters, the transmission power of the PUSCH or PUCCH is increased by the power control offset parameter amount. For example, if the RNTI indicates that the transmission is to use the first set of uplink channel transmission parameters, a power control offset of 3 dB is applied to the uplink transmission at21by the UE. The one or more power control offsets can be RRC configured by the network. In another embodiment, as illustrated inFIG.6, the different sets of uplink channel transmission parameters or the indication of them are used to apply repetitions to the uplink channel. That is, if the UE is indicated at25to use the first set of parameters, the PUSCH or PUCCH is repeated by a predetermined number. This predetermined repetition number or set of predetermined repetition numbers can be RRC configured by the network or it can be tied to MCS level. In the case where a plurality of predetermined repetition numbers are configured, an additional field in the DCI can indicate which repetition number is used, wherein a new DCI format or field is used. In other embodiments, instead of using a new DCI format, the repetition number can be a function of the MCS, that is as MCS level increases the repetition number decreases. For example, if the RNTI indicates that the transmission is to use the first set of parameters, the PUSCH transmission is repeated 4× and the PUCCH transmission is repeated 8×, however if the RNTI indicates that the transmission is to use the second set of parameters, the PUSCH transmission is repeated 2× and the PUCCH transmission is repeated 4×. At26, the UE makes an uplink transmission with the applied repetitions. In an embodiment, as illustrated inFIG.7, this scheme is also used in the downlink for PDSCH. Hence, in this case the respective sets of uplink channel transmission parameters as discussed herein are used to apply repetitions to the downlink channel. Hence, if the UE is indicated at30to use the first set of parameters, the PDSCH or PDCCH is repeated by a predetermined number for a downlink transmission at31. This predetermined repetition number or set of predetermined repetition numbers can be RRC configured by the network or it can be tied to MCS level. In the case where a plurality of predetermined repetition numbers are configured, an additional field in the DCI can indicate which repetition number is used, wherein a new DCI format or field is used. In other embodiments, instead of using a new DCI format, the repetition number can be a function of the MCS, that is as MCS level increases the repetition number decreases. For example, if the RNTI indicates that the transmission is to use the first set of parameters, the PDSCH transmission is repeated 4× and the PDCCH transmission is repeated 8×, however if the RNTI indicates that the transmission is to use the second set of parameters, the PDSCH transmission is repeated 2× and the PDCCH transmission is repeated 4×. In another embodiment, the different sets of uplink channel transmission parameters for PUCCH (carrying the HARQ-ACK feedback for PDSCH) relate to a delay between the PDSCH and PUCCH. In Rel-15 NR, the DCI Format 1_0 and Format 1_1 carrying the DL grant that schedules PDSCH contains a three bit field “PDSCH-to-HARQ_feedback timing indicator” which tells the UE in which slot, relative to the PDSCH, the PUCCH is to be transmitted (see, for example, TS38.212, “NR: Multiplexing and channel coding (Release 15)”). Hence, if the PDSCH ends in slot n, the PUCCH is transmitted in slot n+k where k is indicated in this “PDSCH-to-HARQ_feedback timing indicator” field. The network will configure eight different k values and the DCI using three bits would point to one of these eight different k values. Since URLLC requires low latency and as in some embodiments, the PDSCH for URLLC has a duration of less than a slot (e.g. one mini-slot), the value k needs to be in a smaller unit, e.g. in mini-slots (two OFDM symbols) or in number of OFDM symbols. Thus, if the UE is indicated to use the first set of parameters, the “PDSCH-to-HARQ feedback timing indicator” uses a different set of k values. In other words, if the PDSCH carrying URLLC ends in a mini-slot (or OFDM symbol) m, the “PDSCH-to-HARQ_feedback timing indicator” indicates the value k where the PUCCH would be transmitted in mini-slot or OFDM symbol m+k. For illustrating this embodiment,FIG.8shows in an upper uplink section and a lower downlink section being divided into slots, which in turn are divided into mini-slots, and it illustrates exemplary that at time to, the network transmits a DL grant to schedule a PDSCH for a URLLC UE at time t1. At time t3, the network transmits another DL grant to schedule another PDSCH for an eMBB UE in the same slot (slot n). Both DL grants indicate a “PDSCH-to-HARQ_feedback timing indicator” of 2 (i.e. for URLLC UE k1=2 and for eMBB UE k2=2). The eMBB UE would interpret k2using the 2ndset of parameters, i.e. since the PDSCH ends in Slot n, the PUCCH is transmitted in Slot n+k2, i.e. Slot n+2. However, for the URLLC UE, recognizing that the DL grant is for a URLLC transmission (e.g. via the RNTI, the length of PDSCH<2 mini-slots, etc.), it interprets k1using the 1stset of parameters, i.e. the PUCCH is transmitted two mini-slots later, i.e. at time t2. In another embodiment, the (use of the) different sets of uplink channel transmission parameters indicate a frequency hopping pattern, as illustrated inFIG.9. When a UE is indicated at35(by the eNodeB or gNB) to use the 1stset of uplink channel transmission parameters, frequency hopping is always applied to the transmission at36and the frequency hops between mini-slots, whilst for the 2ndset of transmission parameters, the frequency hopping is enabled by DCI or RRC signalling and the frequency hops between the adjacent slots. The frequency hopping pattern is configured by the network or predefined in specifications for the RAN for the different sets of transmission parameters. In a further embodiment, frequency hopping is used when repetition is configured. Although this is discussed for uplink transmission, in some embodiments the discussed frequency hopping is also applicable for the downlink PDSCH URLLC, such that the sets of uplink channel transmission parameters are accordingly used for indication of a corresponding frequency hopping pattern for the PDSCH URLLC In another embodiment, as illustrated inFIG.10, the (use of the) different sets of uplink channel transmission parameters indicate a transmit diversity scheme. For example, when a UE is indicated at40to use the 1stset of transmission parameters, transmit diversity is used for an uplink transmission at41, in the other case not. In another embodiment, as illustrated inFIG.11, the (the use of the) different sets of uplink channel transmission parameters indicate to reject UCI (Uplink Control Information) piggybacking. In LTE, when a UCI carried by a PUCCH collides with a PUSCH transmission in the same UE, the UCI information is added to the PUSCH transmission, i.e. piggybacked. This avoids the UE from having to transmit two different physical channels at the same time, which has PAPR (Peak to Average Power Ratio) consequences. Since, URLLC requires high reliability, piggybacking additional information may reduce its performance, and, thus, if, for example, the use of the first set of uplink channel transmission parameters is indicated at45, piggybacking is rejected for an uplink transmission at46. Moreover, for example, when a PUCCH collides with a PUSCH in the same UE and the PUSCH uses the 1stset of uplink channel transmission parameters, piggybacking of the UCI onto the PUSCH is accepted if the number of UCI information bits is below a predetermined threshold, otherwise piggybacking is rejected. This predetermined threshold can be configured by the network or predefined in the specifications. In another embodiment, when a PUCCH collides with a PUSCH in the same UE and the PUSCH uses the 1stset of uplink channel transmission parameters, piggybacking of the UCI onto the PUSCH is rejected if the UCI is carried by a PUCCH using the 2ndset of uplink channel transmission parameters. That is, the UCI carries the HARQ-ACK response for an eMBB PDSCH. An example for illustrating this embodiment is shown inFIG.12, where in an upper section the uplink and in a lower section the downlink transmission is illustrated. At time t1, the UE receives a DL grant for a PDSCH carrying an eMBB transmission where the corresponding PUCCH carrying the HARQ-ACK feedback is to be transmitted in the next slot at time t4. This PUCCH uses the 2ndset of uplink channel transmission parameters. At time t3the same UE receives an UL grant for a PUSCH for a URLLC transmission at time t4and this PUSCH transmission uses the 1stset of uplink channel transmission parameters. This causes a collision between PUSCH and PUCCH in this embodiment, and since the PUCCH uses the 2ndset of transmission parameters, the PUSCH transmission rejects piggybacking the UCI from the PUCCH. In another embodiment, when a PUCCH collides with a PUSCH in the same UE and the PUSCH uses the 1stset of uplink channel transmission parameters, piggybacking of the UCI onto the PUSCH is accepted if the UCI is carried by a PUCCH using the 1stset of uplink channel transmission parameters. That is if the UCI carries the HARQ-ACK response for a URLLC PDSCH. An example for illustrating this embodiment is shown inFIG.13, where in an upper section the uplink and in a lower section the downlink transmission is illustrated. At time t1, the UE receives a DL grant for a PDSCH carrying a URLLC transmission and the corresponding PUCCH carrying the HARQ-ACK feedback is to be transmitted at time t4. This PUCCH uses the 1stset of uplink channel transmission parameters. At time t3the same UE receives an UL grant for a PUSCH for a URLLC transmission at time t4and this PUSCH transmission uses the 1stset of transmission parameters. This causes a collision between PUSCH and PUCCH and in this embodiment, since the PUCCH uses the 1stset of uplink channel transmission parameters, the PUSCH transmission accepts piggybacking the UCI on the PUCCH. In another embodiment, as illustrated inFIG.14, when two PUSCHs collide at50in the same UE, the PUSCH using the 1stset of uplink channel transmission parameters has higher priority than the PUSCH using the 2ndset of uplink channel transmission parameters. The PUSCH using the 2ndset of uplink channel transmission parameter is dropped or paused at51so that the PUSCH using the 1stset of uplink channel transmission parameters can be transmitted at52. In another embodiment, as illustrated inFIG.15, when two PUSCHs53and54collide in the same UE and these two PUSCH53,54use the 1stset of uplink channel transmission parameters, the later PUSCH54has higher priority than the earlier PUSCH53. The earlier PUSCH53is dropped or paused so that the later PUSCH can be transmitted. In another embodiment, when two PUCCHs collide in the same UE, the PUCCH using the 1stset of uplink channel transmission parameters has higher priority than the PUCCH using the 2ndset of uplink channel transmission parameters. The PUCCH using the 2ndset of uplink channel transmission parameter is dropped or delayed so that the PUCCH using the 1stset of uplink channel transmission parameters can be transmitted. In another embodiment, as illustrated inFIG.16, when two PUCCHs using the 1stset of uplink channel transmission parameters collide at55, a joint coded UCI is transmitted using a PUCCH. Hence, the UCI information of both PUCCHs are joint coded at56so that information in both UCIs are transmitted without delay. This joint coded UCI PUCCH is transmitted at57using the 1stset of uplink channel transmission parameters. As mentioned, a different MCS table may be used for URLLC transmission compared to other types of transmission, and in some embodiments other (additional) transmission parameters that are used differently for URLLC transmission are introduced. An embodiment of a UE100and an eNB105(or NR eNB/gNB) and a communications path104between the UE100and the eNB105, which are used for implementing embodiments of the present disclosure, is discussed under reference ofFIG.17. The UE100has a transmitter101, a receiver102and a controller103, wherein, generally, the technical functionality of the transmitter101, the receiver102and the controller103are known to the skilled person, and, thus, a more detailed description of them is omitted. The eNB105has a transmitter106, a receiver107and a controller108, wherein also here, generally, the functionality of the transmitter106, the receiver107and the controller108are known to the skilled person, and, thus, a more detailed description of them is omitted. The communication path104has an uplink path104a, which is from the UE100to the eNB105, and a downlink path104b, which is from the eNB105to the UE100. During operation, the controller103of the UE100controls the reception of downlink signals over the downlink path104bat the receiver102and the controller103controls the transmission of uplink signals over the uplink path104avia the transmitter101. Similarly, during operation, the controller108of the eNB105controls the transmission of downlink signals over the downlink path104bover the transmitter106and the controller108controls the reception of uplink signals over the uplink path104aat the receiver107. In the following, an embodiment of a general purpose computer130is described under reference ofFIG.18. The computer130can be implemented such that it can basically function as any type of base station or new radio base station, transmission and reception point, or user equipment as described herein. The computer has components131to141, which can form a circuitry, such as any one of the circuitries of the base stations, and user equipment, as described herein. Embodiments which use software, firmware, programs or the like for performing the methods as described herein, can be installed on computer130, which is then configured to be suitable for the concrete embodiment. The computer130has a CPU131(Central Processing Unit), which can execute various types of procedures and methods as described herein, for example, in accordance with programs stored in a read-only memory (ROM)132, stored in a storage137and loaded into a random access memory (RAM)133, stored on a medium140which can be inserted in a respective drive139, etc. The CPU131, the ROM132and the RAM133are connected with a bus141, which in turn is connected to an input/output interface134. The number of CPUs, memories and storages is only exemplary, and the skilled person will appreciate that the computer130can be adapted and configured accordingly for meeting specific requirements which arise, when it functions as a base station or as user equipment. At the input/output interface134, several components are connected: an input135, an output136, the storage137, a communication interface138and the drive139, into which a medium140(compact disc, digital video disc, compact flash memory, or the like) can be inserted. The input135can be a pointer device (mouse, graphic table, or the like), a keyboard, a microphone, a camera, a touchscreen, etc. The output136can have a display (liquid crystal display, cathode ray tube display, light emittance diode display, etc.), loudspeakers, etc. The storage137can have a hard disk, a solid state drive and the like. The communication interface138can be adapted to communicate, for example, via a local area network (LAN), wireless local area network (WLAN), mobile telecommunications system (GSM, UMTS, LTE, NR etc.), Bluetooth, infrared, etc. It should be noted that the description above only pertains to an example configuration of computer130. Alternative configurations may be implemented with additional or other sensors, storage devices, interfaces or the like. For example, the communication interface138may support other radio access technologies than the mentioned UMTS, LTE and NR. When the computer130functions as a base station, the communication interface138can further have a respective air interface (providing e.g. E-UTRA protocols OFDMA (downlink) and SC-FDMA (uplink)) and network interfaces (implementing for example protocols such as S1-AP, GTP-U, S1-MME, X2-AP, or the like). Moreover, the computer130may have one or more antennas and/or an antenna array. The present disclosure is not limited to any particularities of such protocols. The methods as described herein are also implemented in some embodiments as a computer program causing a computer and/or a processor and/or circuitry to perform the method, when being carried out on the computer and/or processor and/or circuitry. In some embodiments, also a non-transitory computer-readable recording medium is provided that stores therein a computer program product, which, when executed by a processor and/or circuitry, such as the processor and/or circuitry described above, causes the methods described herein to be performed. It should be recognized that the embodiments describe methods with an exemplary order of method steps. The specific order of method steps is, however, given for illustrative purposes only and should not be construed as binding. All units and entities described in this specification and claimed in the appended claims can, if not stated otherwise, be implemented as integrated circuit logic, for example on a chip, and functionality provided by such units and entities can, if not stated otherwise, be implemented by software. In so far as the embodiments of the disclosure described above are implemented, at least in part, using a software-controlled data processing apparatus, it will be appreciated that a computer program providing such software control and a transmission, storage or other medium by which such a computer program is provided are envisaged as aspects of the present disclosure. Note that the present technology can also be configured as described below.(1) A base station for a mobile telecommunications system comprising circuitry configured to communicate with at least one user equipment, wherein the circuitry is further configured to:indicate use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameter for use by the at least one user equipment for a data transmission.(2) The base station of (1), wherein the first set of uplink channel transmission parameters refers to a short data transmission and the second set of uplink channel transmission parameters refers to a long data transmission.(3) The base station of (1) or (2), wherein the use of the first set and the second set of uplink channel transmission parameters is indicated based on at least one of the following: radio network temporary identifier, downlink control information format, physical downlink control channel control resource set, search space, usage of grant free resource for a physical uplink shared channel, occupation of number of slots, radio resource control.(4) The base station of (1) or (2), wherein the use of the first set and the second set of uplink channel transmission parameters is implicitly indicated based on a signaled physical uplink control channel resource and based on at least one of the following: physical uplink control channel resource set identification, physical uplink control channel resource identification, group of resource identifications.(5) The base station of anyone of (1) to (4), wherein the first and second sets of uplink channel transmission parameters are associated with a power control parameter.(6) The base station of anyone of (1) to (5), wherein the first and the second sets of uplink channel transmission parameters are associated with different physical uplink control channel resources.(7) The base station of anyone of (1) to (6), wherein the first and second sets of uplink channel transmission parameters are associated with a repetition to be used in an uplink or a downlink transmission.(8) The base station of anyone of (1) to (7), wherein the first and second sets of uplink channel transmission parameters are associated with a delay for at least one of: physical downlink shared channel and physical uplink control channel.(9) The base station of anyone of (1) to (8), wherein the first and second sets of uplink channel transmission parameters are associated with a frequency hopping pattern.(10) The base station of anyone of (1) to (9), wherein the first and second sets of uplink channel transmission parameters are associated with a transmit diversity scheme.(11) The base station of anyone of (1) to (10), wherein the first and second sets of uplink channel transmission parameters are associated with whether piggybacking is used.(12) The base station of (11), wherein usage of piggybacking of uplink control information is indicated.(13) The base station of (12), wherein piggybacking of uplink control information is not used if the use of the first set of uplink channel transmission parameters is indicated for the data transmission.(14) The base station of (12), wherein piggybacking of uplink control information is used if the use of the first set of uplink channel transmission parameters is indicated for the data transmission and the amount of uplink control information is below a threshold.(15) The base station of (12), wherein piggybacking of uplink control information is not used when the use of the first set of uplink channel transmission parameters is indicated for the data transmission and when the uplink control information is carried by a physical uplink control channel using the second set of uplink channel transmission parameters.(16) The base station of (12), wherein piggybacking of uplink control information is used when the use of the first set of uplink channel transmission parameters is indicated for the data transmission and when the uplink control information is carried by a physical uplink control channel using the first set of uplink channel transmission parameters.(17) The base station of anyone of (1) to (16), wherein, when two physical uplink shared channels collide, the physical uplink shared channel using the first set of uplink channel transmission parameters has priority over the physical uplink shared channel using the second set of uplink channel transmission parameters.(18) The base station of anyone of (1) to (18), wherein, when two physical uplink shared channels collide and the two physical uplink shared channels use the first set of uplink channel transmission parameters, the later physical uplink shared channel has priority over the earlier physical uplink shared channel.(19) The base station of anyone of (1) to (18), wherein, when two physical uplink control channels collide, the physical uplink control channel using the first set of uplink channel transmission parameters has priority over the physical uplink control channel using the second set of uplink channel transmission parameters.(20) The base station of anyone of (1) to (19), wherein, when two physical uplink control channels using the first set of uplink channel transmission parameters collide, uplink control information of both physical uplink control channels are jointly coded into a single physical uplink control channels transmission.(21) A user equipment for a mobile telecommunications system comprising circuitry configured to communicate with at least one base station, wherein the circuitry is further configured to:receive an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for a data transmission.(22) The user equipment of (21), wherein the first set of uplink channel transmission parameters refers to a short data transmission and the second set of uplink channel transmission parameters refers to a long data transmission.(23) The user equipment of (21) or (22), wherein the use of the first set and the second set of uplink channel transmission parameters is indicated based on at least one of the following: radio network temporary identifier, downlink control information format, physical downlink control channel control resource set, search space, usage of grant free resource for a physical uplink shared channel, occupation of number of slots, radio resource control.(24) The user equipment of (21) or (22), wherein the use of the first set and the second set of uplink channel transmission parameters is implicitly indicated based on a signaled physical uplink control channel resource and based on at least one of the following: physical uplink control channel resource set identification, physical uplink control channel resource identification, group of resource identifications.(25) The user equipment of anyone of (21) to (24), wherein the first and second sets of uplink channel transmission parameters are associated with a power control parameter.(26) The user equipment of anyone of (21) to (25), wherein the first and the second sets of uplink channel transmission parameters are associated with different physical uplink control channel resources.(27) The user equipment of anyone of (21) to (26), wherein the first and second sets of uplink channel transmission parameters are associated with a repetition to be used in an uplink or a downlink transmission.(28) The user equipment of anyone of (21) to (27), wherein the first and second sets of uplink channel transmission parameters are associated with a delay for at least one of: physical downlink shared channel and physical uplink control channel.(29) The user equipment of anyone of (21) to (28), wherein the first and second sets of uplink channel transmission parameters are associated with a frequency hopping pattern.(30) The user equipment of anyone of (21) to (29), wherein the first and second sets of uplink channel transmission parameters are associated with a transmit diversity scheme.(31) The user equipment of anyone of (21) to (30), wherein the first and second sets of uplink channel transmission parameters are associated with whether piggybacking is used.(32) The user equipment of anyone of (21) to (30), wherein usage of piggybacking of uplink control information is indicated.(33) The user equipment of (32), wherein piggybacking of uplink control information is not used if the use of the first set of uplink channel transmission parameters is indicated for the data transmission.(34) The user equipment of (32), wherein piggybacking of uplink control information is used if the use of the first set of uplink channel transmission parameters is indicated for the data transmission and the amount of uplink control information is below a threshold.(35) The user equipment of (32), wherein piggybacking of uplink control information is not used when the use of the first set of uplink channel transmission parameters is indicated for the data transmission and when the uplink control information is carried by a physical uplink control channel using the second set of uplink channel transmission parameters.(36) The user equipment of (32), wherein piggybacking of uplink control information is used when the use of the first set of uplink channel transmission parameters is indicated for the data transmission and when the uplink control information is carried by a physical uplink control channel using the first set of uplink channel transmission parameters.(37) The user equipment of anyone of (21) to (36), wherein, when two physical uplink shared channels collide, the physical uplink shared channel using the first set of uplink channel transmission parameters has priority over the physical uplink shared channel using the second set of uplink channel transmission parameters.(38) The user equipment of anyone of (21) to (37), wherein, when two physical uplink shared channels collide and the two physical uplink shared channels use the first set of uplink channel transmission parameters, the later physical uplink shared channel has priority over the earlier physical uplink shared channel.(39) The user equipment of anyone of (21) to (37), wherein, when two physical uplink control channels collide, the physical uplink control channel using the first set of uplink channel transmission parameters has priority over the physical uplink control channel using the second set of uplink channel transmission parameters.(40) The user equipment of anyone of (21) to (38), wherein, when two physical uplink control channels using the first set of uplink channel transmission parameters collide, uplink control information of both physical uplink control channels are jointly coded into a single physical uplink control channels transmission.(41) A circuitry for a base station, in particular for a base station according to anyone of (1) to (20), for a mobile telecommunications system configured to communicate with at least one user equipment, wherein the circuitry is further configured to:indicate use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameter for use by the at least one user equipment for a data transmission.(42) A circuitry for a user equipment, in particular for a user equipment according to anyone of (21) to (40), for a mobile telecommunications system configured to communicate with at least one base station, wherein the circuitry is further configured to:receive an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for a data transmission.(43) A mobile telecommunications system configured to provide communication between at least one base station and at least one user equipment, whereinthe at least one base station, in particular according to anyone of (1) to (20), comprises circuitry configured to indicate use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameter for use by the at least one user equipment for a data transmission, and whereinthe at least one user equipment, in particular according to anyone of (21) to (40), comprises circuitry configured to receive an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for the data transmission.(44) A mobile telecommunications system method for providing communication between at least one base station and at least one user equipment, comprising:indicating use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameter for use by the at least one user equipment for a data transmission; orreceiving an indication of use of a first set of uplink channel transmission parameters and a second set of uplink channel transmission parameters for the data transmission. | 60,754 |
11943775 | DETAILED DESCRIPTION The following technology may be used in various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and so on. CDMA may be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented as a radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (wireless fidelity (Wi-Fi)), IEEE 802.16 (worldwide interoperability for microwave access (WiMAX)), IEEE 802.20, evolved UTRA (E-UTRA), and so on. UTRA is a part of universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA, and LTE-advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP new radio or new radio access technology (NR) is an evolved version of 3GPP LTE/LTE-A. As more and more communication devices require larger communication capacities, the need for enhanced mobile broadband communication relative to the legacy radio access technologies (RATs) has emerged. Massive machine type communication (MTC) providing various services to inter-connected multiple devices and things at any time in any place is one of significant issues to be addressed for next-generation communication. A communication system design in which services sensitive to reliability and latency are considered is under discussion as well. As such, the introduction of the next-generation radio access technology (RAT) for enhanced mobile broadband communication (eMBB), massive MTC (mMTC), and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, this technology is called NR or New RAT in the present disclosure. While the following description is given in the context of a 3GPP communication system (e.g., NR) for clarity, the technical spirit of the present disclosure is not limited to the 3GPP communication system. In a wireless access system, a user equipment (UE) receives information from a base station (BS) on DL and transmits information to the BS on UL. The information transmitted and received between the UE and the BS includes general data and various types of control information. There are many physical channels according to the types/usages of information transmitted and received between the BS and the UE. FIG.1illustrates physical channels and a general signal transmission method using the physical channels in a 3GPP system. When a UE is powered on or enters a new cell, the UE performs initial cell search (S101). The initial cell search involves acquisition of synchronization to a BS. For this purpose, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE synchronizes its timing to the BS and acquires information such as a cell identifier (ID) based on the PSS/SSS. Further, the UE may acquire information broadcast in the cell by receiving the PBCH from the BS. During the initial cell search, the UE may also monitor a DL channel state by receiving a downlink reference signal (DL RS). Subsequently, to complete connection to the BS, the UE may perform a random access procedure with the BS (S103to S106). Specifically, the UE may transmit a preamble on a physical random access channel (PRACH) (S103) and may receive a PDCCH and a random access response (RAR) for the preamble on a PDSCH corresponding to the PDCCH (S104). The UE may then transmit a physical uplink shared channel (PUSCH) by using scheduling information in the RAR (S105), and perform a contention resolution procedure including reception of a PDCCH and a PDSCH signal corresponding to the PDCCH (S106). After the above procedure, the UE may receive a PDCCH and/or a PDSCH from the BS (S107) and transmit a physical uplink shared channel (PUSCH) and/or a physical uplink control channel (PUCCH) to the BS (S108), in a general UL/DL signal transmission procedure. Control information that the UE transmits to the BS is generically called uplink control information (UCI). The UCI includes a hybrid automatic repeat and request acknowledgement/negative acknowledgement (HARQ-ACK/NACK), a scheduling request (SR), channel state information (CSI), and so on. The CSI includes a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indication (RI), and so on. In general, UCI is transmitted on a PUCCH. However, if control information and data should be transmitted simultaneously, the control information and the data may be transmitted on a PUSCH. In addition, the UE may transmit the UCI aperiodically on the PUSCH, upon receipt of a request/command from a network. FIG.2illustrates a radio frame structure. In NR, UL and DL transmissions are configured in frames. Each radio frame has a length of 10 ms and is divided into two 5-ms half-frames. Each half-frame is divided into five 1-ms subframes. A subframe is divided into one or more slots, and the number of slots in a subframe depends on a subcarrier spacing (SCS). Each slot includes 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP). When a normal CP is used, each slot includes 14 OFDM symbols. When an extended CP is used, each slot includes 12 OFDM symbols. A symbol may include an OFDM symbol (or a CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol). Table 1 exemplarily illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCSs in a normal CP case. TABLE 1SCS (15*2{circumflex over ( )}u)NslotsymbNframe, uslotNsubframe, uslot15 KHz14101(u = 0)30 KHz14202(u = l)60 KHz14404(u = 2)120 KHz14808(u = 3)240 KHz1416016(u = 4)* Nslotsymb: number of symbols in a slot* Nframe, uslot: number of slots in a frame* Nsubframe, uslot: number of slots in a subframe Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCSs in an extended CP case. TABLE 2SCS(15*2{circumflex over ( )}u)NslotsymbNframe, uslotNsubframe, uslot60 KHz12404(u = 2) The frame structure is merely an example, and the number of subframes, the number of slots, and the number of symbols in a frame may be changed in various manners. In the NR system, different OFDM(A) numerologies (e.g., SCSs, CP lengths, and so on) may be configured for a plurality of cells aggregated for one UE. Accordingly, the (absolute time) duration of a time resource (e.g., a subframe, a slot, or a transmission time interval (TTI)) (for convenience, referred to as a time unit (TU)) composed of the same number of symbols may be configured differently between the aggregated cells. A symbol may include an OFDM symbol (or a CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol). NR may support various numerologies (or subcarrier spacings (SCSs)) to provide various 5G services. For example, NR may support a wide area in conventional cellular bands in an SCS of 15 kHz and support a dense urban area and a wide carrier bandwidth with lower latency in an SCS of 30/60 kHz. In an SCS of 60 kHz or above, NR may support a bandwidth higher than 24.25 GHz to overcome phase noise. NR frequency bands may be divided into two frequency ranges: frequency range 1 (FR1) and frequency range 2 (FR2). FR1 and FR2 may be configured as shown in Table 3 below. FR 2 may mean a millimeter wave (mmW). TABLE 3Frequency RangeCorrespondingdesignationfrequency rangeSubcarrier SpacingFR1450 MHz-7125 MHz15, 30, 60kHzFR224250MHz-52600 MHz60, 120, 240kHz FIG.3illustrates a resource grid during the duration of one slot. A slot includes a plurality of symbols in the time domain. For example, one slot includes 14 symbols in a normal CP case and 12 symbols in an extended CP case. A carrier includes a plurality of subcarriers in the frequency domain. A resource block (RB) may be defined by a plurality of (e.g.,12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) may be defined by a plurality of consecutive (physical) RBs ((P)RBs) in the frequency domain and correspond to one numerology (e.g., SCS, CP length, and so on). A carrier may include up to N (e.g.,5) BWPs. Data communication may be conducted in an active BWP, and only one BWP may be activated for one UE. Each element in a resource grid may be referred to as a resource element (RE), to which one complex symbol may be mapped. FIG.4illustrates a structure of a slot. In the NR system, a frame has a self-contained structure in which a DL control channel, DL or UL data, a UL control channel, and the like may all be contained in one slot. For example, the first N symbols (hereinafter, DL control region) in the slot may be used to transmit a DL control channel (e.g., PDCCH), and the last M symbols (hereinafter, UL control region) in the slot may be used to transmit a UL control channel (e.g., PUCCH). N and M are integers greater than or equal to 0. A resource region (hereinafter, a data region) that is between the DL control region and the UL control region may be used for DL data (e.g., PDSCH) transmission or UL data (e.g., PUSCH) transmission. The GP provides a time gap for the BS and UE to transition from the transmission mode to the reception mode or from the reception mode to the transmission mode. Some symbols at the time of DL-to-UL switching in a subframe may be configured as the GP. The PDCCH delivers DCI. For example, the PDCCH (i.e., DCI) may carry information about a transport format and resource allocation of a DL shared channel (DL-SCH), resource allocation information of an uplink shared channel (UL-SCH), paging information on a paging channel (PCH), system information on the DL-SCH, information on resource allocation of a higher-layer control message such as an RAR transmitted on a PDSCH, a transmit power control command, information about activation/release of configured scheduling, and so on. The DCI includes a cyclic redundancy check (CRC). The CRC is masked with various identifiers (IDs) (e.g. a radio network temporary identifier (RNTI)) according to an owner or usage of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked by a UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is for a paging message, the CRC is masked by a paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., a system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for an RAR, the CRC is masked by a random access-RNTI (RA-RNTI). The PUCCH delivers uplink control information (UCI). The UCI includes the following information.SR: information used to request UL-SCH resources.HARQ-ACK: a response to a DL data packet (e.g., codeword) on the PDSCH. An HARQ-ACK indicates whether the DL data packet has been successfully received. In response to a single codeword, a 1-bit of HARQ-ACK may be transmitted. In response to two codewords, a 2-bit HARQ-ACK may be transmitted. The HARQ-ACK response includes positive ACK (simply, ACK), negative ACK (NACK), discontinuous transmission (DTX) or NACK/DTX. The term “HARQ-ACK is interchangeably used with HARQ ACK/NACK and ACK/NACK.CSI: feedback information for a DL channel. Multiple input multiple output (MIMO)-related feedback information includes an RI and a PMI. Table 4 illustrates exemplary PUCCH formats. PUCCH formats may be divided into short PUCCHs (Formats 0 and 2) and long PUCCHs (Formats 1, 3, and 4) based on PUCCH transmission durations. TABLE 4Length in OFDMPUCCHsymbolsNumberformatNsymbPUCCHof bitsUsageEtc01-2≤2HARQ, SRSequenceselection14-14≤2HARQ, [SR]Sequencemodulation21-2>2HARQ, CSI,CP-OFDM[SR]34-14>2HARQ, CSI,DFT-s-OFDM[SR](no UEmultiplexing)44-14>2HARQ, CSI,DFT-s-OFDM[SR](Pre DFT OCC) FIG.5illustrates an ACK/NACK transmission process. Referring toFIG.5, the UE may detect a PDCCH in slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates a DL assignment-to-PDSCH offset, K0 and a PDSCH-to-HARQ-ACK reporting offset, K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.Frequency domain resource assignment: Indicates an RB set assigned to a PDSCH.Time domain resource assignment: Indicates K0 and the starting position (e.g. OFDM symbol index) and length (e.g. the number of OFDM symbols) of the PDSCH in a slotPDSCH-to-HARQ_feedback timing indicator: Indicates K1.HARQ process number (4 bits): Indicates the HARQ process ID of data (e.g., a PDSCH or TB).PUCCH resource indicator (PRI): Indicates PUCCH resource used for UCI transmission among a plurality of PUCCH resources in a PUCCH resource set. After receiving a PDSCH in slot #(n+K0) according to the scheduling information of slot #n, the UE may transmit UCI on a PUCCH in slot #(n+K1). The UCI includes an HARQ-ACK response to the PDSCH. In the case where the PDSCH is configured to carry one TB at maximum, the HARQ-ACK response may be configured in one bit. In the case where the PDSCH is configured to carry up to two TBs, the HARQ-ACK response may be configured in two bits if spatial bundling is not configured and in one bit if spatial bundling is configured. When slot #(n+K1) is designated as an HARQ-ACK transmission timing for a plurality of PDSCHs, UCI transmitted in slot #(n+K1) includes HARQ-ACK responses to the plurality of PDSCHs. FIG.6illustrates an exemplary PUSCH transmission process. Referring toFIG.6, the UE may detect a PDCCH in slot #n. The PDCCH may include UL scheduling information (e.g., DCI format 0_0 or DCI format 0_1). DCI format 0_0 and DCI format 0_1 may include the following information.Frequency domain resource assignment: Indicates an RB set allocated to a PUSCH.Time domain resource assignment: Specifies a slot offset K2 indicating the starting position (e.g., symbol index) and length (e.g., the number of OFDM symbols) of the PUSCH in a slot. The starting symbol and length of the PUSCH may be indicated by a start and length indicator value (SLIV), or separately. The UE may then transmit a PUSCH in slot #(n+K2) according to the scheduling information in slot #n. The PUSCH includes a UL-SCH TB. When PUCCH transmission time and PUSCH transmission time overlaps, UCI can be transmitted via PUSCH (PUSCH piggyback). FIG.7illustrates an exemplary wireless communication system supporting an unlicensed band applicable to the present disclosure. In the following description, a cell operating in a licensed band (L-band) is defined as an L-cell, and a carrier of the L-cell is defined as a (DL/UL) LCC. A cell operating in an unlicensed band (U-band) is defined as a U-cell, and a carrier of the U-cell is defined as a (DL/UL) UCC. The carrier/carrier-frequency of a cell may refer to the operating frequency (e.g., center frequency) of the cell. A cell/carrier (e.g., CC) is commonly called a cell. When carrier aggregation is supported, one UE may use a plurality of aggregated cells/carriers to exchange a signal with the BS. When one UE is configured with a plurality of CCs, one CC may be set to a primary CC (PCC), and the remaining CCs may be set to secondary CCs (SCCs). Specific control information/channels (e.g., CSS PDCCH, PUCCH) may be transmitted and received only on the PCC. Data may be transmitted and received on the PCC/SCC.FIG.7(a)shows a case in which the UE and BS exchange signals on both the LCC and UCC (non-standalone (NSA) mode). In this case, the LCC and UCC may be set to the PCC and SCC, respectively. When the UE is configured with a plurality of LCCs, one specific LCC may be set to the PCC, and the remaining LCCs may be set to the SCC.FIG.7(a)corresponds to the LAA of the 3GPP LTE system.FIG.7(b)shows a case in which the UE and BS exchange signals on one or more UCCs with no LCC (standalone (SA) mode). In this case, one of the UCCs may be set to the PCC, and the remaining UCCs may be set to the SCC. Both the NSA mode and SA mode may be supported in the U-band of the 3GPP NR system. FIG.8illustrates an exemplary method of occupying resources in an unlicensed band. According to regional regulations for the U-band, a communication node in the U-band needs to determine whether a corresponding channel is used by other communication node(s) before transmitting a signal. Specifically, the communication node may perform carrier sensing (CS) before transmitting the signal so as to check whether the other communication node(s) perform signal transmission. When the other communication node(s) perform no signal transmission, it is said that clear channel assessment (CCA) is confirmed. When a CCA threshold is predefined or configured by higher layer signaling (e.g., RRC signaling), if the detected channel energy is higher than the CCA threshold, the communication node may determine that the channel is busy. Otherwise, the communication node may determine that the channel is idle. When it is determined that the channel is idle, the communication node may start the signal transmission in the UCell. The Wi-Fi standard (802.11ac) specifies a CCA threshold of 62 dBm for non-Wi-Fi signals and a CCA threshold of −82 dBm for Wi-Fi signals. The sires of processes described above may be referred to as Listen-Before-Talk (LBT) or a channel access procedure (CAP). The LBT may be interchangeably used with the CAP. In Europe, two LBT operations are defined: frame based equipment (FBE) and load based equipment (LBE). In FBE, one fixed frame is made up of a channel occupancy time (e.g., 1 to 10 ms), which is a time period during which once a communication node succeeds in channel access, the communication node may continue transmission, and an idle period corresponding to at least 5% of the channel occupancy time, and CCA is defined as an operation of observing a channel during a CCA slot (at least 20 us) at the end of the idle period. The communication node performs CCA periodically on a fixed frame basis. When the channel is unoccupied, the communication node transmits during the channel occupancy time, whereas when the channel is occupied, the communication node defers the transmission and waits until a CCA slot in the next period. In LBE, the communication node may set q∈{4, 5, . . . , 32} and then perform CCA for one CCA slot. When the channel is unoccupied in the first CCA slot, the communication node may secure a time period of up to (13/32)q ms and transmit data in the time period. When the channel is occupied in the first CCA slot, the communication node randomly selects NE {1, 2, . . . , q}, stores the selected value as an initial value, and then senses a channel state on a CCA slot basis. Each time the channel is unoccupied in a CCA slot, the communication node decrements the stored counter value by 1. When the counter value reaches 0, the communication node may secure a time period of up to (13/32)q ms and transmit data. Example: Signal Transmission in NR-U The 3GPP standardization group has been working on standardization of a 5G wireless communication system called new RAT (NR). The 3GPP NR system has been designed to support a plurality of logical networks in a single physical system and provide services with various requirements (e.g., eMBB, mMTC, URLLC, and so on) by changing a transmission time interval (TTI) and an OFDM numerology (e.g., an OFDM symbol duration, an SCS, and so on). With the recent emergence of smart devices, data traffic has significantly increased. In this context, use of an unlicensed band for cellular communication is under consideration in the 3GPP NR system, as is the case with licensed-assisted access (LAA) of the legacy 3GPP LTE system. Compared to the LAA, however, an NR cell in the unlicensed-band (NR U-cell) aims to support a standalone (SA) operation. For example, PUCCH, PUSCH, and sound reference signal (SRS) transmissions may be supported in the NR UCell. To support an SA operation in a U-band, an HARQ-ACK feedback operation (for convenience, HARQ-ACK will be referred to as A/N) of a UE based on a PUCCH/PUSCH transmission in the U-band in response to reception of DL data (e.g., a PDSCH) may be essential. For example, a BS may schedule a PDSCH transmission for a specific UE in a channel occupancy time (COT) period secured by performing LBT (e.g., CCA) and indicate to the UE to transmit an A/N feedback for the PDSCH reception in the same COT period (or any gNB-initiated COT period started/occupied by a DL transmission of the BS). This process is referred to as an intra-COT A/N transmission, for convenience. In another example, the BS may indicate to the UE to transmit an A/N feedback for a PDSCH reception which has been scheduled/transmitted in a specific COT period in another COT period subsequent to the COT period (or a period that does not belong to the above gNB-initiated COT period) in view of a UE processing time involved in decoding of the PDSCH signal and encoding of a corresponding HARQ-ACK signal. This process is referred to as an inter-COT A/N transmission, for convenience (hereinbelow, LBT or CCA is referred to as LBT, for convenience). In a U-band situation, one component carrier (CC) or BWP may be configured for a UE as a wideband (WB) CC or BWP having a larger bandwidth (BW) than in legacy LTE. However, a BW requiring CCA based on an independent LBT operation may be limited even in the WB CC/BWP (according to a specific regulation). In this context, when a subband for which LBT is individually performed is defined as an LBT-subband (LBT-SB), one WB CC/BWP may include a plurality of LBT-SBs. FIG.9illustrates a BWP of a cell, which includes a plurality of LBT-SBs. An LBT-SB may be, for example, a band of 20 MHz. The LBT-SB may include a plurality of consecutive (P)RBs, and thus may be referred to as a (P)RB set. While not shown, a guard band (GB) may be interposed between LBT-SBs. Accordingly, the BWP may be configured in the form of {LBT-SB #0 (RB set #0)+GB #0+LBT-SB #1 (RB set #1+GB #1)+ . . . +LBT-SB #(K−1) (RB set (#K−1))}. For convenience, LBT-SB/RB indexes may be configured/defined in an increasing order from the lowest frequency to the highest frequency. In the U-band situation, considering that the UE may fail in LBT for a UL transmission (e.g., an A/N PUCCH) (and thus drop the A/N PUCCH transmission), a method may be considered, in which a plurality of candidate PUCCH resources in time and/or frequency are indicated/configured (by higher-layer signaling (e.g., RRC signaling) and/or DCI) and a UE transmits an A/N PUCCH in a specific (one) PUCCH resource for which the UE has succeeded in LBT among the plurality of candidate PUCCH resources. For example, for a single A/N PUCCH transmission, a plurality of candidate PUCCH resources (e.g., slots or symbol groups) multiplexed in TDM in the time domain may be indicated/configured (candidate T-domain resources). The UE may attempt LBT in the plurality of candidate PUCCH resources sequentially in time and transmit an A/N PUCCH in a specific (one) PUCCH resource in which the UE has succeeded in CCA (for the first time). In another example, for a single A/N PUCCH transmission, a plurality of candidate PUCCH resources (e.g., LBT-SBs/BWPs/CCs) multiplexed in FDM in the frequency domain may be indicated/configured (candidate F-domain resources). The UE may attempt LBT in the plurality of candidate PUCCH resources (at the same time) and transmit an A/N PUCCH in a specific (one) PUCCH resource in which the UE has succeeded in CCA. The present disclosure proposes resource allocation for a UL (physical) channel transmission based on a plurality of (candidate) F-domain resources (e.g., LBT-SBs, BWPs, or CCs) in a U-band situation, and a related UE operation. For example, the present disclosure proposes allocation of PUCCH resources for an (A/N) PUCCH transmission and a method of operating a UE. The proposed methods of the present disclosure may be applied in a similar manner to an operation/process of transmitting other USI (e.g., CSI and an SR) on a PUCCH/PUSCH, data on a PUSCH, or an SRS, not limited to the operation/process of transmitting an A/N feedback on a PUCCH/PUSCH. Further, the proposed methods of the present disclosure may be applied in a similar manner to an L-band (or U-band) operation without LBT, not limited to an LBT-based U-band operation. (0) Unit Resource for UL (Physical) Channel/Signal Transmission In the U-band environment, a (single) set of (equidistant) non-consecutive RBs in frequency may be defined as a unit resource used/allocated for transmission of a UL (physical) channel/signal in consideration of a regulation related to an occupied channel bandwidth (OCB) and a power spectral density (PSD). This non-consecutive RB set is defined as an “RB interlace”, for convenience. FIG.10illustrates an RB interlace. Referring toFIG.10, an RB interlace may be defined as non-consecutive RBs in a frequency band. For example, four RB interlaces may be available out of 20 RBs, and each RB interlace may include {RB #N, RB #(N+4), . . . }(N=0-3). A transmitter (e.g., a UE) may use one or more interlaces to transmit a signal/channel. The frequency band may include a (wideband) CC/BWP/LBT-SB, and an RB may include a PRB. An RB interlace may be defined by frequency resources or frequency/time resources. When an RB interlace refers to frequency/time resources, the time resources may be defined as a time instance/period for a UL (physical) channel/signal (or a UL (physical) channel/signal transmission occasion). The time resources may include a slot or a symbol set. The symbol set includes one or more consecutive symbols for the UL (physical) channel/signal. A symbol includes an OFDM-based symbol (e.g., a CP-OFDM symbol, an SC-FDMA symbol, and a DFT-s-OFDM symbol). The UL (physical) channel/signal may include a PUCCH, a PUSCH, or an SRS. FIG.11illustrates methods of defining an RB interlace (RB interlace indexing). Referring toFIG.11, when one (wideband) CC/BWP (hereinafter, referred to as BWP) includes a plurality of LBT-SBs, the following two options may be considered to define an RB interlace (RB interlace indexing) in the BWP (for transmitting a UL channel). While LBT-SBs are shown as consecutive inFIG.11, a GB may be configured between LBT-SBs. 1) Opt 1: An RB interlace (RB interlace indexing) is defined based on a BWP (FIG.11(a)). One interlace (index) may be defined as a set of all RBs spaced from each other by a specific equal distance, starting from a specific RB index in the BWP, among all RBs of the BWP (or a plurality of LBT-SBs included in the BWP). 2) Opt 2: An RB interlace (RB interlace indexing) is defined on an LBT-SB basis (FIG.11(b)). One interlace (index) in each LBT-SB (index) may be defined as a set of RBs spaced from each other by a specific equal distance, starting from a specific RB index (in the LBT-SB), among all RBs of the LBT-SB. (1) UL (Physical) Channel (e.g., PUCCH) Resource Allocation Based on a Plurality of Candidate LBT-SBs Depending on an option of defining an RB interlace (RB interlace indexing), the following methods may be considered for UL channel resource allocation based on a plurality of candidate LBT-SBs. Specifically, the following (single) PUCCH resource allocation methods may be considered based on each option. PUCCH resource allocation (RA) information may be preconfigured by higher-layer signaling (e.g., RRC signaling). Further, the PUCCH RA information may be indicated by a PDCCH that schedules a PDSCH (i.e., DL grant DCI), and HARQ-ACK information for the PDSCH may be transmitted in allocated PUCCH resources. 1) Opt 1: Case in which an RB interlace (RB interlace indexing) is defined based on a BWPAlt 1-1: A PUCCH resource may be allocated by “single interlace index+LBT-SB index bitmap”. For example, once one RB interlace index is indicated, an LBT-SB to be allocated as a candidate PUCCH resource among a plurality of LBT-SBs spanned by the (indicated) interlace is indicated (e.g., by an LBT-SB index bitmap). In this manner, one PUCCH resource may be configured.FIG.12(a)illustrates RA based on Alt 1-1. RA information may include information about {interlace index, LBT-SB bitmap}. Each bit of the bitmap indicates whether resources of a corresponding LBT-SB are allocated. In the illustrated case, the first bit of the bitmap indicates allocation of resources of LBT-SB #N, and the second bit of the bitmap indicates allocation of resources of LBT-SB #M. When the interlace index is #1 and the bitmap is ‘01’, interlace #1 of LBT-SB #M may be allocated as a PUCCH resource.Alt 1-2: A PUCCH resource may be allocated based on “an interlace index in each of a plurality of LBT-SBs”. For example, one PUCCH resource may be configured by, for each of the plurality of LBT-SBs, indicating an RB interlace index to be allocated as a candidate PUCCH resource in the corresponding LBT-SB. The interlace index may include “no interlace allocation” (i.e., no interlace).FIG.12(b)illustrates an exemplary RA based on Alt 1-2. RA information may include {interlace index of LBT-SB #N, interlace index of LBT-SB #M}. In the illustrated case ofFIG.12(b), no interlace of LBT-SB #N is allocated, and interlace #1 of LBT-SB #M is allocated, by way of example. 2) Opt 2: Case in which an RB interlace (RB interlace indexing) is defined on an LBT-SB basis.Alt 2-1: A PUCCH resource may be allocated by “single common interlace index+LBT-SB index bitmap”. For example, once a (common) RB interlace index is indicated for all of a plurality of LBT-SBs, an LBT-SB to which an interlace to be allocated as a candidate PUCCH resource belongs is indicated among the plurality of LBT-SBs (e.g., by an LBT-SB index bitmap). In this manner, one PUCCH resource may be configured.FIG.13(a)illustrates an exemplary RA based on Alt 2-1. Herein, RA information may include information about {common interlace index, LBT-SB bitmap}. Each bit of the bitmap indicates whether resources of a corresponding LBT-SB are allocated. InFIG.13(a), the first bit of the bitmap indicates allocation of resources of LBT-SB #N, and the second bit of the bitmap indicates allocation of resources of LBT-SB #M. When the common interlace index is #1 and the bitmap is ‘01’, interlace #1 of LBT-SB #M may be allocated as a PUCCH resource.Alt 2-2: A PUCCH resource may be allocated based on “an interlace index in each of a plurality of LBT-SBs”. For example, one PUCCH resource may be configured by, for each of the plurality of LBT-SBs, indicating an RB interlace index to be allocated as a candidate PUCCH resource in the corresponding LBT-SB. The interlace index may include “no interlace allocation” (i.e., no interlace).FIG.13(b)illustrates an exemplary RA based on Alt 1-2. RA information may include {interlace index of LBT-SB #N, interlace index of LBT-SB #M}. In the illustrated case, no interlace of LBT-SB #N is allocated, and interlace #1 of LBT-SB #M is allocated, by way of example. (2) UE Operation when LBT-SBs have Different Numbers of Allocated RBs When a PUCCH resource is allocated in the above proposed methods (or any other method), a plurality of (candidate) LBT-SBs (i.e., interlaces configured in each LBT-SB) configured/allocated as the same one PUCCH resource may have different numbers of RBs. In this case, to avoid the burden of a (post)process (including an IFFT operation) which should be performed shortly after an LBT operation at the UE, the following PUCCH signal process and UE transmission operation may be considered. The number of RBs allocated to an LBT-SB may be the total number of RBs included in the LBT-SB or the number of RBs actually used in a UL channel transmission (e.g., the number of RBs in an RB interlace) within the LBT-SB. 1) The PUCCH is processed based on an LBT-SB with a minimum number of RBs among LBT-SBs. A. The PUCCH may be subjected to a (pre)process (including an IFFT operation) based on an LBT-SB with a minimum number of RBs among a plurality of (candidate) LBT-SBs. Specifically, based on the minimum number M of RBs, the UE may determine a maximum UCI payload size (according to a configured maximum UCI coding rate), (the number of) coded UCI bits (for UCI encoding/rate-matching), and a DMRS sequence (length), and perform an IFFT operation (with a frequency input size of M RBs) and a UL power control operation (applied to the M-RB allocation). When the PUCCH format of the PUCCH requires a DFT operation and the minimum of the numbers of RBs of the LBT-SBs is not a multiple of {2, 3, 5} (e.g., 11 RBs), the maximum UCI payload size, the (number of) coded UCI bits, and the DMRS sequence (length) may be determined, and the IFFT operation and the UL power control operation may be performed, based on the largest integer M (e.g., M=10) which is smaller than the minimum number of RBs and is a multiple of {2, 3, 5}. B. Based on the above description, when there is any LBT-SB configured with M (the minimum number of RBs) RBs among LBT-SBs for which LBT is successful, the UE may select the LBT-SB configured with M RBs (as a PUCCH transmission band) with priority. When an LBT-SB with more RBs than M is selected as the PUCCH transmission band (from among the LBT-SBs for which LBT is successful), the PUCCH signal may be mapped to/transmitted in M RBs with the lowest or highest indexes among the RBs configured in the LBT-SB. 2) Case in which a plurality of LBT-SBs are allocated/scheduled as a single PUSCH transmission resource. A. A plurality of (e.g., two) LBT-SBs may be allocated as a single PUSCH transmission resource, and a PUSCH transmission in DFT-s-OFDM modulation may be indicated/configured. In this case, for each of the LBT-SBs, when the number of RBs configured in the LBT-SB is not a multiple of {2, 3, 5} (e.g., 11 RBs), a PUSCH signal may be mapped/transmitted (e.g., (the number of) coded bits for rate-matching and a DMRS sequence (length) may be determined, and an IFFT operation and a UL power control operation may be performed) based on M RBs (e.g., M=10) where M is the largest integer smaller than the number of RBs and a multiple of {2, 3, 5}. For example, when 10 RBs and 11 RBs are allocated to LBT-SB index 0 and LBT-SB index 1, respectively, only 10 RBs of LBT-SB index 1 may be used for PUSCH signal mapping/transmission. In another example, when 11 RBs are allocated to each of LBT-SB index 0 and LBT-SB index 1, only 10 RBs of each of LBT-SB index 0 and LBT-SB index 1 may be used for PUSCH signal mapping/transmission. B. When the number M′ of RBs initially configured for a PUSCH transmission in an LBT-SB is larger than the number M of RBs used in an actual PUSCH mapping/transmission, the PUSCH signal may not be mapped to/transmitted in the remaining L RBs (L=(M′-M)). The PUSCH signal may be mapped to/transmitted in M RBs with the highest indexes in an LBT-SB with a low LBT-SB index (in a low frequency band) or in M RBs with the lowest indexes in an LBT-SB with a high LBT-SB index (in a high frequency band). It is assumed herein that RBs are indexed in an increasing order from a low frequency to a high frequency. From the perspective of PUSCH mapping, a low LBT-SB index or a high LBT-SB index may depend on the relative position of an LBT-SB with respect to the center frequency of the BWP. For example, the M RBs which the PUSCH signal is mapped to/transmitted in may be determined to be M RBs with the highest indexes in an LBT-SB in a frequency band lower than the center (frequency) of the BWP and M RBs with the lowest indexes in an LBT-SB in a frequency band higher than the center (frequency) of the BWP. Additionally, for a single SRS transmission, a plurality of candidate F-domain resources (e.g., LBT-SBs/BWPs/CCs) separated in the frequency domain may be configured. The UE may attempt LBT in the plurality of (frequency) resources (e.g., LBT-SBs) (at the same time) and transmit an SRS in a specific (one) resource (e.g., LBT-SB) in which the UE has succeeded in CCA. Accordingly, a principle similar to that in the above proposal may be applied to the SRS transmission, and thus, the following SRS signal process and UE transmission operation may be considered. 1) The SRS is processed based on the minimum of the numbers of RBs in LBT-SBs. A. The SRS may be subjected to a (pre)process (including an IFFT operation) based on the minimum of the numbers of RBs in a plurality of (candidate) LBT-SBs. For example, the UE may determine an SRS sequence (length) and perform an IFFT operation (with a frequency input size of M RBs) and a UL power control operation (applied to the M-RB allocation), based on the minimum number M of RBs. B. Based on the above description, when there is any LBT-SB configured with M (the minimum number of RBs) RBs among LBT-SBs for which LBT is successful, the UE may select the LBT-SB configured with M RBs (as an SRS transmission band) with priority. When an LBT-SB with more RBs than M is selected as the SRS transmission band (from among the LBT-SBs for which LBT is successful), the SRS signal may be mapped to/transmitted in M RBs with the lowest or highest indexes among the RBs configured in the LBT-SB. In the above proposed method, “minimum number of RBs” may be replaced with “maximum number of RBs”. FIG.14illustrates an exemplary UL transmission process according to an example of the present disclosure. Referring toFIG.14, a BS may transmit RA information to a UE (S1402). The RA information may include information about one or more (candidate) UL resources for a U-band (e.g., CC/BWP). The UL resources include physical resources for transmission of a UL physical channel/signal (e.g., PUCCH, PUSCH, or SRS). For example, the UL resources may include a (P)RB set for transmission of the UL physical channel/signal (e.g., PUCCH, PUSCH, or SRS). The plurality of UL resources may be multiplexed in TDM in the time domain or in FDM in the frequency domain. The RA information may be indicated by higher-layer signaling (e.g., RRC signaling) and/or DCI according to a proposed method. Then, the UE may perform a UL transmission in one specific UL resource for which CCA is successful among the one or more (candidate) UL resources. When CCA is successful for a plurality of UL resources (e.g., a plurality of LBT-SBs), the UL transmission may be performed in one specific UL resource (e.g., an RB interlace in a specific LBT-SB) selected according to the afore-described method. (3) Method of Configuring Wideband BWP Including a Plurality of LBT-SBs and transmission method It may be necessary to define a wideband BWP configuration (including a plurality of LBT-SBs) and a transmission and reception operation based on the wideband BWP configuration in consideration of a regulation on an LBT operation (in frequency) and GB management in a U-band situation. For this purpose, the following methods may be considered. In the present disclosure, a CC/cell BW (an RB set/index in the BW) may refer to a (virtual) BW (the RB set/index in the BW) based on (e.g., starting from) a separately configured specific frequency position, reference point A. In the present disclosure, an LBT-SB (an RB set in a corresponding BW) may refer to a unit BW (e.g., 20 MHz) (or an RB set corresponding to the unit BW) requiring individual/independent LBT or a BW except for a GB in the unit BW (or an RB set corresponding to the BW except for the GB). 1) Method 1 A. An SB-RB range corresponding to each single LBT-SB may be configured based on an RB set in a CC/cell BW (RB indexes in the RB set) (hereinafter, referred to as a CRB set/index). An SB-RB range may be configured/defined by a starting RB index and an ending RB index or a total number of RBs with consecutive indexes from a starting RB, based on a CRB set/index. B. A BWP-RB range corresponding to each single BWP may be configured based on a CRB set/index. The BWP-RB range may be configured/defined by a starting RB index and an ending RB index or a total number of RBs with consecutive indexes from a starting RB, based on the CRB set/index. C. One BWP-RB range may be configured to include one or more SB-RB ranges (always a corresponding whole range for each SB-RB). 2) Method 2 A. An SB-RB range corresponding to each single LBT-SB may be configured based on a CRB set/index, and the index of each SB-RB range may be set/configured according to the frequency position of each LBT-SB or SB-RB range. For example, the indexes of SB-RB range may be continuously set/configured from a low frequency to a high frequency. B. For each BWP, a combination of the indexes of the SB-RB ranges included in the BWP may be configured. C. One BWP may be configured to include one or more consecutive SB-RB range indexes. For example, (for each BWP) a starting index and an ending index (or a total number of SB-RB ranges starting from the starting index) may be configured for a set of consecutive SB-RB ranges. 3) Method 3 A. A BWP-RB range corresponding to each BWP may be configured based on a CRB set/index. B. Based on an RB set (the RB indexes of the RB set) (hereinafter, referred to as an LRB set/index) in each BWP, an SB-RB range corresponding to each single LBT-SB belonging to/included in the BWP may be configured/defined. C. When a plurality of RB ranges are configured in a specific BWP based on Method 1/2/3 or any other method, each RB range may correspond to a single different LBT-SB. Accordingly, an RB range including a plurality of LBT-SBs may not be configured. For UL (e.g., PUSCH) scheduling/transmission, a wideband UL BWP including a plurality of LBT-SBs or a plurality of SB-RB ranges corresponding to the plurality of LBT-SBs may be configured. FIG.15illustrates exemplary UL resources according to an example of the present disclosure. Referring toFIG.15, a BWP includes a plurality of LBT-SBs (or SB-RB ranges) (hereinafter, referred to as SBs) and a GB between LBT-SBs. For example, the BWP may include {SB #0+GB #0+SB #1+GB #1+SB #2}. (P)RBs included in the SBs/GBs of the BWP may be defined/configured based on a CRB set/index. The BWP may include a plurality of (RB) interlaces. For example, when (RB) interlaces are defined/configured on a BWP basis (FIG.11(a)), each (RB) interlace may include the following RBs inFIG.15.Interlace #0: CRB indexes {15, 18, 21, 24, 27, 30, 33}Interlace #1: CRB indexes {16, 19, 22, 25, 28, 31, 34}Interlace #2: CRB indexes {17, 20, 23, 26, 29, 32} A final UL (PUSCH) resource to be actually transmitted/used may be determined (by the UE) in the following manner according to an SB-RB range combination/interlaces indicated as UL (PUSCH) transmission resources. When it is said that a plurality of LBT-SBs or SB-RB ranges are consecutive (in frequency), this may imply that a gap between the LBT-SBs or SB-RB ranges is equal to or less than a specific level (e.g., a maximum BW defined as a GB) or the indexes of the plurality of LBT-SBs or SB-RB ranges are consecutive. 1) Case 1: When one SB-RB range index is indicated as a UL (PUSCH) transmission resource, the indicated SB-RB range (or a separately indicated RB resource (e.g., interlace) set for the SB-RB range) may be determined as the final UL (PUSCH) resource. For example, referring toFIG.16(a), based on RA information for a PUSCH indicating {interlace #1, SB #1}, RBs belonging to interlace #1 in SB #1 may be determined as a PUSCH resource. That is, the RBs corresponding to the intersection of {interlace #1, SB #1} may be determined as the PUSCH resource. GBs (e.g., GB #0 and GB #1) adjacent to SB #1 are not used as the PUSCH transmission resource. 2) Case 2: When a plurality of consecutive SB-RB range indexes are indicated as a UL (PUSCH) transmission resource, a gap between the indicated SB-RB ranges may also be used as an available RB resource. That is, the indicated SB-RB ranges and the gap between the indicated SB-RB ranges (or a separately indicated RB resource (e.g., interlace) set for the indicated SB-RB ranges and the gap between the indicated SB-RB ranges) may be determined as a final UL (PUSCH) resource. A. For example, when the number of consecutive SB-RB range indexes is 2, an RB range corresponding to {SB-RB range+gap+SB-RB range} (a separately indicated RB resource (e.g., interlace) set for the corresponding SB-RB range) may be determined as the final UL (PUSCH) resource. B. For example, when SB-RB range index #0 and SB-RB range index #1 are indicated, an RB range corresponding to {SB-RB range index #0, gap, SB-RB range index #1} (a separately indicated RB resource (e.g., interlace) set for the range) may be determined as the final UL (PUSCH) resource. C. In another example, when SB-RB range index #0, SB-RB range index #1, and SB-RB range index #2 are indicated, an RB range corresponding to {SB-RB range index #0, gap, SB-RB range index #1, gap SB-RB range index #2} (a separately indicated RB resource (e.g., interlace) set for the range) may be determined as the final UL (PUSCH) resource. D. For example, referring toFIG.16(b), based on RA information for a PUSCH indicating {interlace #2, SB #1/#2}, RBs belonging to interlace #2 in SB #1/#2 may be determined as a PUSCH resource. The GB between SB #1 and SB #2, that is, GB #1 may also be used as the PUSCH transmission resource. That is, the RBs corresponding to the intersection of {interlace #1, SB #1/#2+GB #1} may be determined as the PUSCH resource. A GB (i.e., GB #0) adjacent to SB #1/#2 but not interposed between SB #1 and SB #2 is not used as the PUSCH transmission resource. 3) Case 3: When a plurality of non-consecutive SB-RB range indexes are indicated as a UL (PUSCH) transmission resource, each of the indicated SB-RB ranges (a separately indicated RB (e.g., interlace) set for the corresponding range) may be determined as a final UL (PUSCH) resource. A. For example, when SB-RB range index #0 and SB-RB range index #2 are indicated, an RB range corresponding to {SB-RB range index #0, SB-RB range index #2} (e.g., a non-consecutive RB range in which a gap between the two SB-RB ranges is not used) may be determined as a final UL (PUSCH) resource. B. In another example, when SB-RB range index #0, SB-RB range index #1, and SB-RB range index #3 are indicated, an RB range corresponding to {range #0, gap between range #0 and range #1, range #1, range #3} (e.g., a separately indicated RB set (e.g., interlace) for the corresponding range) may be determined as a final UL (PUSCH) resource. FIG.17is a diagram illustrating an exemplary UL transmission (e.g., a PUSCH transmission) according to an example of the present disclosure. Referring toFIG.17, a UE may receive RA information for a PUSCH transmission from a BS (S1702). The RA information may include information about consecutive SB index(es). The RA information may be received by higher-layer signaling (e.g., RRC signaling) or on a PDCCH (i.e., by DCI). An SB corresponds to an LBT-SB/an SB-RB range. The SB may be configured in a BWP, which may have, for example, the structure illustrated inFIGS.15and16. Subsequently, the UE may perform the PUSCH transmission in interlace(s) of SB(s) (within the BWP) indicated by the RA information (S1704). The PUSCH transmission may be performed in an unlicensed band (e.g., a UCell or an unlicensed/shared spectrum). Based on the RA information indicating only one SB index, the PUSCCH transmission may be performed only in the interlace(s) of the indicated SB (FIG.16(a)). Based on the RA information indicating a plurality of SB indexes, the PUSCH transmission may be performed using (i) the indicated plurality of SBs and (ii) the interlace(s) within the GB(s) between the indicated plurality of SBs. With a GB (an RB set corresponding to the GB) configured (between adjacent LBT-SBs) in a BWP/CC BW, RB range(s) including only consecutive RB indexes (except for the GB) may be (automatically) configured. In this case, the proposed methods may be applied by replacing/considering an RB range and a GB with/as an SB-RB range and a gap, respectively. The various descriptions, functions, procedures, proposals, methods, and/or operation flowcharts of the present disclosure described herein may be applied to, but not limited to, various fields requiring wireless communication/connectivity (e.g., 5G) between devices. More specific examples will be described below with reference to the drawings. In the following drawings/description, like reference numerals denote the same or corresponding hardware blocks, software blocks, or function blocks, unless otherwise specified. FIG.18illustrates a communication system1applied to the present disclosure. Referring toFIG.18, the communication system1applied to the present disclosure includes wireless devices, BSs, and a network. A wireless device is a device performing communication using radio access technology (RAT) (e.g., 5G NR (or New RAT) or LTE), also referred to as a communication/radio/5G device. The wireless devices may include, not limited to, a robot100a, vehicles100b-1and100b-2, an extended reality (XR) device100c, a hand-held device100d, a home appliance100e, an IoT device100f, and an artificial intelligence (AI) device/server400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of vehicle-to-vehicle (V2V) communication. Herein, the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR)/virtual reality (VR)/mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television (TV), a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and so on. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smart glasses), and a computer (e.g., a laptop). The home appliance may include a TV, a refrigerator, a washing machine, and so on. The IoT device may include a sensor, a smartmeter, and so on. For example, the BSs and the network may be implemented as wireless devices, and a specific wireless device200amay operate as a BS/network node for other wireless devices. The wireless devices100ato100fmay be connected to the network300via the BSs200. An AI technology may be applied to the wireless devices100ato100f, and the wireless devices100ato100fmay be connected to the AI server400via the network300. The network300may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices100ato100fmay communicate with each other through the BSs200/network300, the wireless devices100ato100fmay perform direct communication (e.g., sidelink communication) with each other without intervention of the BSs/network. For example, the vehicles100b-1and100b-2may perform direct communication (e.g. V2V/vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices100ato100f. Wireless communication/connections150a,150b, and150cmay be established between the wireless devices100ato100f/BS200and between the BSs200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as UL/DL communication150a, sidelink communication150b(or, D2D communication), or inter-BS communication (e.g. relay or integrated access backhaul (TAB)). Wireless signals may be transmitted and received between the wireless devices, between the wireless devices and the BSs, and between the BSs through the wireless communication/connections150a,150b, and150c. For example, signals may be transmitted and receive don various physical channels through the wireless communication/connections150a,150band150c. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocation processes, for transmitting/receiving wireless signals, may be performed based on the various proposals of the present disclosure. FIG.19illustrates wireless devices applicable to the present disclosure. Referring toFIG.19, a first wireless device100and a second wireless device200may transmit wireless signals through a variety of RATs (e.g., LTE and NR). {The first wireless device100and the second wireless device200} may correspond to {the wireless device100xand the BS200} and/or {the wireless device100xand the wireless device100x} ofFIG.18. The first wireless device100may include one or more processors102and one or more memories104, and further include one or more transceivers106and/or one or more antennas108. The processor(s)102may control the memory(s)104and/or the transceiver(s)106and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. For example, the processor(s)102may process information in the memory(s)104to generate first information/signals and then transmit wireless signals including the first information/signals through the transceiver(s)106. The processor(s)102may receive wireless signals including second information/signals through the transceiver(s)106and then store information obtained by processing the second information/signals in the memory(s)104. The memory(s)104may be connected to the processor(s)102and may store various pieces of information related to operations of the processor(s)102. For example, the memory(s)104may store software code including instructions for performing all or a part of processes controlled by the processor(s)102or for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. The processor(s)102and the memory(s)104may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)106may be connected to the processor(s)102and transmit and/or receive wireless signals through the one or more antennas108. Each of the transceiver(s)106may include a transmitter and/or a receiver. The transceiver(s)106may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the wireless device may be a communication modem/circuit/chip. The second wireless device200may include one or more processors202and one or more memories204, and further include one or more transceivers206and/or one or more antennas208. The processor(s)202may control the memory(s)204and/or the transceiver(s)206and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. For example, the processor(s)202may process information in the memory(s)204to generate third information/signals and then transmit wireless signals including the third information/signals through the transceiver(s)206. The processor(s)202may receive wireless signals including fourth information/signals through the transceiver(s)106and then store information obtained by processing the fourth information/signals in the memory(s)204. The memory(s)204may be connected to the processor(s)202and store various pieces of information related to operations of the processor(s)202. For example, the memory(s)204may store software code including instructions for performing all or a part of processes controlled by the processor(s)202or for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. The processor(s)202and the memory(s)204may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s)206may be connected to the processor(s)202and transmit and/or receive wireless signals through the one or more antennas208. Each of the transceiver(s)206may include a transmitter and/or a receiver. The transceiver(s)206may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may be a communication modem/circuit/chip. Now, hardware elements of the wireless devices100and200will be described in greater detail. One or more protocol layers may be implemented by, not limited to, one or more processors102and202. For example, the one or more processors102and202may implement one or more layers (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), RRC, and service data adaptation protocol (SDAP)). The one or more processors102and202may generate one or more protocol data units (PDUs) and/or one or more service data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. The one or more processors102and202may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document and provide the messages, control information, data, or information to one or more transceivers106and206. The one or more processors102and202may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document and provide the generated signals to the one or more transceivers106and206. The one or more processors102and202may receive the signals (e.g., baseband signals) from the one or more transceivers106and206and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. The one or more processors102and202may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors102and202may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be included in the one or more processors102and202or may be stored in the one or more memories104and204and executed by the one or more processors102and202. The descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of code, an instruction, and/or a set of instructions. The one or more memories104and204may be connected to the one or more processors102and202and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories104and204may be configured to include read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories104and204may be located at the interior and/or exterior of the one or more processors102and202. The one or more memories104and204may be connected to the one or more processors102and202through various technologies such as wired or wireless connection. The one or more transceivers106and206may transmit user data, control information, and/or wireless signals/channels, mentioned in the methods and/or operation flowcharts of this document, to one or more other devices. The one or more transceivers106and206may receive user data, control information, and/or wireless signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers106and206may be connected to the one or more processors102and202and transmit and receive wireless signals. For example, the one or more processors102and202may perform control so that the one or more transceivers106and206may transmit user data, control information, or wireless signals to one or more other devices. The one or more processors102and202may perform control so that the one or more transceivers106and206may receive user data, control information, or wireless signals from one or more other devices. The one or more transceivers106and206may be connected to the one or more antennas108and208and the one or more transceivers106and206may be configured to transmit and receive user data, control information, and/or wireless signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document, through the one or more antennas108and208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers106and206may convert received wireless signals/channels from RF band signals into baseband signals in order to process received user data, control information, and wireless signals/channels using the one or more processors102and202. The one or more transceivers106and206may convert the user data, control information, and wireless signals/channels processed using the one or more processors102and202from the baseband signals into the RF band signals. To this end, the one or more transceivers106and206may include (analog) oscillators and/or filters. FIG.20illustrates another example of a wireless device applied to the present disclosure. The wireless device may be implemented in various forms according to a use case/service (refer toFIG.18). Referring toFIG.20, wireless devices100and200may correspond to the wireless devices100and200ofFIG.19and may be configured to include various elements, components, units/portions, and/or modules. For example, each of the wireless devices100and200may include a communication unit110, a control unit120, a memory unit130, and additional components140. The communication unit110may include a communication circuit112and transceiver(s)114. For example, the communication circuit112may include the one or more processors102and202and/or the one or more memories104and204ofFIG.19. For example, the transceiver(s)114may include the one or more transceivers106and206and/or the one or more antennas108and208ofFIG.19. The control unit120is electrically connected to the communication unit110, the memory130, and the additional components140and provides overall control to the wireless device. For example, the control unit120may control an electric/mechanical operation of the wireless device based on programs/code/instructions/information stored in the memory unit130. The control unit120may transmit the information stored in the memory unit130to the outside (e.g., other communication devices) via the communication unit110through a wireless/wired interface or store, in the memory unit130, information received through the wireless/wired interface from the outside (e.g., other communication devices) via the communication unit110. The additional components140may be configured in various manners according to type of the wireless device. For example, the additional components140may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, not limited to, the robot (100aofFIG.18), the vehicles (100b-1and100b-2ofFIG.18), the XR device (100cofFIG.18), the hand-held device (100dofFIG.18), the home appliance (100eofFIG.18), the IoT device (100fofFIG.18), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400ofFIG.18), the BSs (200ofFIG.18), a network node, or the like. The wireless device may be mobile or fixed according to a use case/service. InFIG.20, all of the various elements, components, units/portions, and/or modules in the wireless devices100and200may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit110. For example, in each of the wireless devices100and200, the control unit120and the communication unit110may be connected by wire and the control unit120and first units (e.g.,130and140) may be wirelessly connected through the communication unit110. Each element, component, unit/portion, and/or module in the wireless devices100and200may further include one or more elements. For example, the control unit120may be configured with a set of one or more processors. For example, the control unit120may be configured with a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphical processing unit, and a memory control processor. In another example, the memory130may be configured with a RAM, a dynamic RAM (DRAM), a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof. FIG.21illustrates a vehicle or an autonomous driving vehicle applied to the present disclosure. The vehicle or autonomous driving vehicle may be implemented as a mobile robot, a car, a train, a manned/unmanned aerial vehicle (AV), a ship, or the like. Referring toFIG.21, a vehicle or autonomous driving vehicle100may include an antenna unit108, a communication unit110, a control unit120, a driving unit140a, a power supply unit140b, a sensor unit140c, and an autonomous driving unit140d. The antenna unit108may be configured as a part of the communication unit110. The blocks110/130/140ato140dcorrespond to the blocks110/130/140ofFIG.20, respectively. The communication unit110may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit120may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle100. The control unit120may include an ECU. The driving unit140amay enable the vehicle or the autonomous driving vehicle100to drive on a road. The driving unit140amay include an engine, a motor, a powertrain, a wheel, a brake, a steering device, and so on. The power supply unit140bmay supply power to the vehicle or the autonomous driving vehicle100and include a wired/wireless charging circuit, a battery, and so on. The sensor unit140cmay acquire information about a vehicle state, ambient environment information, user information, and so on. The sensor unit140cmay include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, and so on. The autonomous driving unit140dmay implement technology for maintaining a lane on which the vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a route if a destination is set, and the like. For example, the communication unit110may receive map data, traffic information data, and so on from an external server. The autonomous driving unit140dmay generate an autonomous driving route and a driving plan from the obtained data. The control unit120may control the driving unit140asuch that the vehicle or autonomous driving vehicle100may move along the autonomous driving route according to the driving plan (e.g., speed/direction control). During autonomous driving, the communication unit110may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. During autonomous driving, the sensor unit140cmay obtain information about a vehicle state and/or surrounding environment information. The autonomous driving unit140dmay update the autonomous driving route and the driving plan based on the newly obtained data/information. The communication unit110may transfer information about a vehicle position, the autonomous driving route, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology based on the information collected from vehicles or autonomous driving vehicles and provide the predicted traffic information data to the vehicles or the autonomous driving vehicles. The embodiments of the present disclosure described above are combinations of elements and features of the present disclosure. The elements or features may be considered selective unless otherwise mentioned. Each element or feature may be practiced without being combined with other elements or features. Further, an embodiment of the present disclosure may be constructed by combining parts of the elements and/or features. Operation orders described in embodiments of the present disclosure may be rearranged. Some constructions of any one embodiment may be included in another embodiment and may be replaced with corresponding constructions of another embodiment. It is obvious to those skilled in the art that claims that are not explicitly cited in each other in the appended claims may be presented in combination as an embodiment of the present disclosure or included as a new claim by a subsequent amendment after the application is filed. The embodiments of the present disclosure have been described above, focusing on the signal transmission and reception relationship between a UE and a BS. The signal transmission and reception relationship is extended to signal transmission and reception between a UE and a relay or between a BS and a relay in the same manner or a similar manner. A specific operation described as performed by a BS may be performed by an upper node of the BS. Namely, it is apparent that, in a network comprised of a plurality of network nodes including a BS, various operations performed for communication with a UE may be performed by the BS, or network nodes other than the BS. The term BS may be replaced with the term fixed station, Node B, enhanced Node B (eNode B or eNB), access point, and so on. Further, the term UE may be replaced with the term terminal, mobile station (MS), mobile subscriber station (MSS), and so on. The embodiments of the present disclosure may be achieved by various means, for example, hardware, firmware, software, or a combination thereof. In a hardware configuration, the methods according to the embodiments of the present disclosure may be achieved by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc. In a firmware or software configuration, the embodiments of the present disclosure may be implemented in the form of a module, a procedure, a function, etc. For example, software code may be stored in a memory unit and executed by a processor. The memory unit is located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means. Those skilled in the art will appreciate that the present disclosure may be carried out in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present disclosure. The above embodiments are therefore to be construed in all aspects as illustrative and not restrictive. The scope of the disclosure should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein. The present disclosure may be used for a UE, a BS, or other equipment in a wireless mobile communication system. | 73,680 |
11943776 | DETAILED DESCRIPTION Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth. In addition, the scope of the disclosure is intended to cover such an apparatus or method, which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth. It should be understood that any aspect of the disclosure disclosed may be embodied by one or more elements of a claim. Several aspects of telecommunications systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. It should be noted that while aspects may be described using terminology commonly associated with 5G and later wireless technologies, aspects of the present disclosure can be applied in other generation-based communications systems, such as and including 3G and/or 4G technologies. In some examples, a user equipment (UE) may request an offset for a start time for a data transmission on a pre-configured uplink resource (PUR). In some such examples, a PUR configuration request transmitted by the UE may include a time offset request. Additionally, a PUR configuration transmitted by a base station may include a time offset. In the present disclosure, the PUR configuration may refer to an initial PUR configuration or a PUR reconfiguration. In some example, the PUR configuration may be transmitted by the base station regardless of whether the UE transmitted the PUR configuration request. The maximum PUR time offset range may be the same as the maximum PUR periodicity. Future recurring PUR occasions are based on the first PUR occasion and PUR periodicity. In one configuration, the PUR configuration request may be transmitted in a PURConfigurationRequest message. A requestedTimeOffset field may request the offset. The base station may transmit the PUR start time in a pur-StartTime field of a PUR-Config information element. Additionally, the base station may configure and/or reconfigure the PUR with or without the UE request. The PUR configuration and/or reconfiguration may be provided in a radio resource control (RRC) connection release message. That is, a PUR-Config information element may be included in the RRCConnectionRelease message. The network may be unaware of when the UE successfully receives the RRC connection release message. The release message may be successfully received via potential repetitions of an initial transmission, as well as one or more potential retransmissions, where the one or more retransmissions may also consist of repetitions. After the release message is successfully received by the UE, the UE enters an idle mode without sending a confirmation RRC message to the network. In some examples, the UE may send the confirmation via a one or both of physical layer acknowledgment (PHY ACK) or RLC poll bit, if configured. Based on current medium access control (MAC) specifications, it is possible to have a misalignment. For example, the UE may receive a downlink message in a first physical downlink shared channel (PDSCH). In this example, the base station may miss the ACK and retransmit the downlink message. The UE may skip decoding the second downlink message, still the UE may send an ACK corresponding to the first downlink message. The base station may wrongly assume the UE only received the second downlink message. Depending on when the downlink message is received by the UE, the understanding of PUR start time (e.g., first PUR occasion) may be misaligned. An unambiguous reference time is desirable to determine the first PUR occasion. FIG.1is a diagram illustrating a network100in which aspects of the present disclosure may be practiced. The network100may be a 5G or NR network or some other wireless network, such as an LTE network. The wireless network100may include a number of BSs110(shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A BS is an entity that communicates with user equipment (UEs) and may also be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), and/or the like. Each BS may provide communications coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used. A BS may provide communications coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. ABS for a pico cell may be referred to as a pico BS. ABS for a femto cell may be referred to as a femto BS or a home BS. In the example shown inFIG.1, a BS110amay be a macro BS for a macro cell102a, a BS110bmay be a pico BS for a pico cell102b, and a BS110cmay be a femto BS for a femto cell102c. ABS may support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “node B,” “5G NB,” and “cell” may be used interchangeably herein. In some aspects, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some aspects, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network100through various types of backhaul interfaces such as a direct physical connection, a virtual network, and/or the like using any suitable transport network. The wireless network100may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown inFIG.1, a relay station110dmay communicate with macro BS110aand a UE120din order to facilitate communications between the BS110aand UE120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, and/or the like. The wireless network100may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 Watts). A network controller130may couple to a set of BSs and may provide coordination and control for these BSs. The network controller130may communicate with the BSs via a backhaul. The BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul. UEs120(e.g.,120a,120b,120c) may be dispersed throughout the wireless network100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communications device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered machine-type communications (MTC) or evolved or enhanced machine-type communications (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and/or the like, that may communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communications link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a customer premises equipment (CPE). UE120may be included inside a housing that houses components of UE120, such as processor components, memory components, and/or the like. In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, and/or the like. A frequency may also be referred to as a carrier, a frequency channel, and/or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed. In some aspects, two or more UEs120(e.g., shown as UE120aand UE120e) may communicate directly using one or more sidelink channels (e.g., without using a base station110as an intermediary to communicate with one another). For example, the UEs120may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like), a mesh network, and/or the like. In this case, the UE120may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station110. As indicated above,FIG.1is provided merely as an example. Other examples may differ from what is described with regard toFIG.1. FIG.2shows a block diagram of a design200of the base station110and UE120, which may be one of the base stations and one of the UEs inFIG.1. The base station110may be equipped with T antennas234athrough234t, and UE120may be equipped with R antennas252athrough252r, where in general T≥1 and R≥1. At the base station110, a transmit processor220may receive data from a data source212for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MC S(s) selected for the UE, and provide data symbols for all UEs. The transmit processor220may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols. The transmit processor220may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor230may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs)232athrough232t. Each modulator232may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream. Each modulator232may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators232athrough232tmay be transmitted via T antennas234athrough234t, respectively. According to various aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information. At the UE120, antennas252athrough252rmay receive the downlink signals from the base station110and/or other base stations and may provide received signals to demodulators (DEMODs)254athrough254r, respectively. Each demodulator254may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator254may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols. A MIMO detector256may obtain received symbols from all R demodulators254athrough254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor258may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE120to a data sink260, and provide decoded control information and system information to a controller/processor280. A channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), and/or the like. In some aspects, one or more components of the UE120may be included in a housing. On the uplink, at the UE120, a transmit processor264may receive and process data from a data source262and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from the controller/processor280. Transmit processor264may also generate reference symbols for one or more reference signals. The symbols from the transmit processor264may be precoded by a TX MIMO processor266if applicable, further processed by modulators254athrough254r(e.g., for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to the base station110. At the base station110, the uplink signals from the UE120and other UEs may be received by the antennas234, processed by the demodulators254, detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by the UE120. The receive processor238may provide the decoded data to a data sink239and the decoded control information to a controller/processor240. The base station110may include communications unit244and communicate to the network controller130via the communications unit244. The network controller130may include a communications unit294, a controller/processor290, and a memory292. The controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with machine learning for non-linearities, as described in more detail elsewhere. For example, the controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, the processes ofFIGS.6-8and/or other processes as described. Memories242and282may store data and program codes for the base station110and UE120, respectively. A scheduler246may schedule UEs for data transmission on the downlink and/or uplink. In some aspects, the UE120may include means for receiving PUR configuration information comprising one or more LSBs of an H-SFN, means for determining a PUR start time based on the H-SFN identified by the one or more LSBs; and means for transmitting, to a base station, a data message on a PUR indicated in the PUR configuration information at the PUR start time. In some aspects, the UE120may include means for receiving a downlink message comprising pre-configured uplink (UL) resource (PUR) configuration information; means for determining at least one least significant bit (LSB) of a hyper system frame number (H-SFN) corresponding to the received downlink message; and means for transmitting a signal including the one or more LSBs to a base station. The signal may include an RLC (radio link control) message, or a RRC message, or a similar type of message. In some aspects, the UE120may include means for decoding a downlink (DL) transmission, means for determining whether the DL transmission is a retransmission, means for using an H-SFN of the DL transmission as a reference H-SFN for determining a PUR start time when the DL transmission is the retransmission; and means for transmitting, to a base station, a data message on a PUR indicated in the PUR configuration information at the PUR start time. As indicated above,FIG.2is provided merely as an example. Other examples may differ from what is described with regard toFIG.2. Legacy uplink (UL) data transmissions (up to release 14 (Rel-14)) employ a four-step UL random access procedure, allowing a data transmission in a message five (Msg 5) uplink transmission. In at least release 15 (Rel-15), early data transmission (EDT) is specified to support a two-step uplink access procedure, such that data may be transmitted in a message three (Msg 3) uplink transmission. Data transmissions in a message one (Msg 1) uplink transmission, referred to as a pre-configured uplink resource (PUR), are specified in at least release 16 (Rel-16). In such examples, a UE in a radio resource control idle (RRC_IDLE) mode may have a valid timing advance (TA) and may use the PUR for an uplink data transmission. In some such examples, the timing advance may be specified for a stationary UE. The PUR may be an example of a grant-free approach to uplink data transmissions and may improve uplink transmission efficiency and also reduce power consumption. For example, the PUR may improve transmission efficiency and reduce power consumption for enhanced machine-type communication/narrow band-Internet-of-Things (eMTC/NB-IoT) devices. FIG.3illustrates an example of a PUR call flow300, according to aspects of the present disclosure. As shown inFIG.3, at time T1, a UE is in a radio resource control (RRC) connected mode. While in the connected mode, at time T2, the UE may request pre-configured uplink resource (PUR) for an uplink transmission. In some examples, the resource request may include a PUR offset request indicating a requested offset for a PUR start time. As described, the PUR request at time T2may be optional. In the example ofFIG.3, a base station (e.g., an eNB or a gNB) transmits an RRC connection release message to the UE at time T3. The RRC connection release message may include a PUR configuration or reconfiguration. The PUR configuration or reconfiguration may identify a PUR start time for performing an uplink transmission using the PUR. In some implementations, the base station may configure and/or reconfigure the PUR with or without UE request, such as the UE request transmitted at time T2. In some implementations, the PUR configuration and/or PUR re-configuration include(s) one or more bits to indicate least significant bits (LSBs) of a current hyper system frame number (H-SFN) to resolve misalignment. In some such implementations, one bit is allocated for indicating the LSB. In other implementations, more than one least significant bits of an H-SFN may be indicated. In some such implementations, remaining bits identifying the H-SFN may be present in a system information block or determined by UE based on the information in a system information block. In response to receiving the RRC connection release, the UE enters an RRC idle mode at time T4. While in the idle mode, the UE transmits uplink data to the base station on the pre-configured uplink resource (PUR) at the PUR start time, indicated as time T5. The PUR start time may be a specific subframe from a set of subframes in a frame. In some examples, the UE uses the PUR to perform an uplink data transmission to the base station. In the example ofFIG.3, at time T6, the PUR is released after the UE performed the idle mode transmissions (e.g., RRC_IDLE mode transmission). In one configuration, the PUR may be released in response to the UE receiving a PUR release message from the base station (not shown inFIG.3). Alternatively, the UE may autonomously release the PUR without receiving the PUR release message. In some examples, the UE may enter a connected mode (e.g., RRC connected mode) after the PUR is released. As discussed, the UE may request an offset for the PUR start time. The PUR configuration request transmitted by the UE may include a time offset request. The PUR configuration transmitted by the base station may include a time offset. The maximum PUR time offset range may be the same as the maximum PUR periodicity. Future recurring PUR occasions are based on the first PUR occasion and PUR periodicity. In one configuration, the PUR configuration request may be transmitted in a PURConfigurationRequest message. A requestedTimeOffset field may request the offset. The base station may transmit the PUR start time in a pur-StartTime field of a PUR-Config information element. Additionally, the base station may configure and/or reconfigure the PUR with or without the UE request. The PUR configuration and/or reconfiguration may be provided in an RRC connection release message. That is, a PUR-Config information element may be included in the RRCConnectionRelease message. The network may be unaware of when the UE successfully receives the RRC connection release message. The release message may be successfully received via potential repetitions of an initial transmission, as well as one or more potential retransmissions. In some examples, the one or more retransmissions may also be repetitions. After the release message is successfully received by the UE, the UE enters an idle mode without sending a confirmation RRC message to the network. The confirmation may be a physical layer ACK (PHY ACK) or RLC poll bit, if configured. In conventional systems, based on current medium access control (MAC) specifications, it is possible to have a misalignment. For example, the UE may receive a downlink message in a first physical downlink shared channel (PDSCH). In this example, the base station may miss the acknowledgment (ACK) and retransmit the downlink message. The UE may skip decoding the second downlink message, still the UE may send an ACK corresponding to the first downlink message. The base station may wrongly assume the UE only received the second downlink message. Depending on when the downlink message is received by the UE, the understanding of PUR start time (e.g., first PUR occasion) may be misaligned. An unambiguous reference time is desirable to determine the first PUR occasion. The offset time may be provided in terms of a relative delay and/or gap with respect to a current time. To reduce ambiguity, one or more solutions may be used. In one configuration, one or more least significant bits (LSBs) of a current hyper system frame number (H-SFN) may be included in the PUR configuration message to indicate the reference time of an initial downlink (DL) message transmitted by a base station. In some implementations, based on receiving the PUR configuration (e.g., pur-Config) or reconfiguration, the UE determines the PUR start time (e.g., first PUR occasion) occurs at an H-SFN determined by H-SFN=(H-SFNRef+offset) mod 1024 occurring after FLOOR (offset/1024) H-SFN cycles, where an offset may be determined by an identifier in the PUR configuration, such a periodicityAndOffset identifier. Additionally, H-SFNRefcorresponds to the H-SFN corresponding to a last subframe of a first transmission of the RRC connection release message (e.g., RRCConnectionRelease) containing the PUR configuration, while taking into account the H-SFN LSB information. In some examples, the H-SFN cycle corresponds to the duration of 1024 H-SFNs. Additionally, a system frame number (SFN) and a subframe for a PUR start time may be indicated by a start SFN indicator (e.g., startSFN) and a start subframe indicator (e.g., startSubframe). A number of bits for the LSB may be based on a length of time for determining the initial DL message. For example, a one-bit LSB may be used to determine the initial DL message after one or more DL retransmission(s). The same LSB(s) of an H-SFN corresponding to the initial DL message may be included in subsequent retransmissions of the same DL message. Both the network and the UE determine the first PUR occasion based on the reference H-SFN corresponding to the initial DL message. That is, a retransmitted message has the same H-SFN value as in the initial transmission of a message. Additionally, or alternatively, a value of the LSB may be the LSB of an H-SFN that is subsequent to a current H-SFN (e.g., subsequent to an initial PUR configuration message transmission). In some examples, the value of the LSB may be the LSB of an H-SFN that was previous to a current H-SFN. In some implementations, if one bit LSB is used, the bit may be set to (H-SFN and 0000000001b) if the reference point is the start of the current H-SFN. Alternatively, the bit may be set to ((H-SFN+1) AND 0000000001b) if the reference point is the start of a subsequent H-SFN. In such examples, the H-SFN is 10 bits. The H-SFN is not limited to 10 bits, more bits or fewer bits may be used for the H-SFN. In one configuration, if the UE transmits a radio link control (RLC) status report, the report may include the LSB(s) of the H-SFN on which the UE received the connection release (e.g., RRC connection release). The base station and UE may use the indicated H-SFN as the reference time. In one configuration, if the UE decodes a DL transmission, the UE may determine if the DL transmission was a DL retransmission. For example, an indication from a medium access control (MAC) layer to a radio resource control (RRC) layer in the UE may indicate that the base station tried to retransmit the H-SFN. Thus, the UE should use the new H-SFN as the reference H-SFN instead of the previously decoded H-SFN. For each transmission and retransmission, the MAC protocol data unit (PDU) containing the downlink message may be repeated in multiple subframes (e.g., 1, 2, 4, 8, etc.) for extended coverage. The H-SFN may change for each repetition subframe. In one configuration, a mapping of the reference H-SFN to a specific shared downlink channel (e.g., physical downlink shared channel (PDSCH)) repetition subframe is fixed. For example, the reference H-SFN may be specified as the H-SFN corresponding to a last subframe of a PDSCH repetition. Alternatively, the SFN may be specified as the H-SFN corresponding to a first subframe of a PDSCH repetition. Additionally, or alternatively, in the PUR configuration, the actual subframe within the H-SFN is indicated for the first PUR occasion. In one configuration, a start time of the first PUR is provided in terms of an absolute H-SFN number instead of relative to the current time. For example, the H-SFN number may be H-SFN number two hundred. If the current H-SFN number is one thousand, the UE will wait until H-SFN two hundred (which occurs after H-SFN wrap around). The start time in terms of an absolute H-SFN number may be included in a PUR configuration transmitted by a base station or a PUR configuration request transmitted by a UE. In LTE, for example, a length of an H-SFN is 10.24 seconds and an H-SFN is 10 bits. As such, the H-SFNs wrap around every 2.9 hours (e.g., 10.24 seconds*1024=2.9127 hours). The H-SFN may wrap around one or more times before the first PUR occasion with regards to a current time. Therefore, the UE may be notified for a number of H-SFN wraparounds to skip from a current time until a first occurrence of the PUR. In the PUR configuration, a specific subframe, such as a specific subframe number, within the H-SFN is indicated for the first PUR occasion. That is, the specific subframe (e.g., actual subframe) within the H-SFN may be indicated as the PUR start time. In one configuration, a start time of the first PUR is provided in terms of an absolute timestamp (e.g., UTC time). The start time in terms of an absolute timestamp may be included in a PUR configuration transmitted by a base station or a PUR configuration request transmitted by a UE. In some implementations, the specific subframe within the H-SFN may be excluded for the PUR configuration request message. A granularity in terms of H-SFN duration may be sufficient for the request. For a PUR configuration request transmitted by a UE, an indication for a subframe within the H-SFN for the first PUR occasion may be excluded. A granularity in terms of an H-SFN duration may be sufficient for the request. As discussed, the offset requests a PUR start time in terms of a relative H-SFN gap or relative time gap from a current H-SFN or a current absolute time. The offset may also be relative to fractions of H-SFNs (e.g., subframes). FIG.4is a diagram illustrating an example process400performed, for example, by a UE, in accordance with various aspects of the present disclosure. As shown inFIG.4, at block402, a UE (e.g., using the antenna252, demodulator (DEMOD)254, RX processor258, controller/processor280, memory282, and/or the like) receives PUR configuration information comprising one or more LSBs of a reference H-SFN. In some implementations, a value of the one or more LSBs corresponds to the LSB(s) of a H-SFN corresponding to a last subframe of the initial DL message transmission. In other implementations, a value of the one or more LSBs corresponds to the LSB(s) of a H-SFN corresponding to a first subframe of the initial DL message transmission. Alternatively, a value of the LSB corresponds to an H-SFN subsequent to an initial DL message transmission. In other implementations, the one or more LSBs indicates a reference time of an initial downlink message. In such implementations, the initial DL message included the PUR configuration information. In some such implementations, the initial downlink message is an RRC connection release message, such as the RRC connection release message received at time T3inFIG.3. In such implementations, a retransmission of the initial DL message includes the one or more LSBs. At block404, the UE (e.g., using the controller/processor280, memory282, and/or the like) determines a PUR start time based on the H-SFN identified by the one or more LSBs. In some implementations, the H-SFN may further be determined based on a specific subframe of a set of subframes for repetitions of a physical downlink shared channel (PDSCH). At block406, the UE (e.g., using the antenna252, modulator (MOD)254, TX processor264, controller/processor280, memory282, and/or the like) transmits, to a base station, data on a PUR indicated in the PUR configuration information at the PUR start time. FIG.5is a diagram illustrating an example process500performed, for example, by a UE, in accordance with various aspects of the present disclosure. As shown inFIG.5, at block502, a UE (e.g., using the antenna252, DEMOD254, RX processor258, controller/processor280, memory282, and/or the like) receives a downlink message comprising pre-configured uplink (UL) resource (PUR) configuration information. In some examples, the downlink message is a radio resource control (RRC) connection release message. In the example ofFIG.5, at block504, the UE (e.g., using the controller/processor280, memory282, and/or the like) determines one or more LSBs of an H-SFN where a UE received a connection release message comprising PUR configuration information. In some implementations, the UE determines a PUR start time based on the H-SFN corresponding to the at least one LSB. In some implementations, the UE may determine the H-SFN based on a specific subframe within a set of subframes used for repetitions of a physical downlink shared channel (PDSCH). The specific subframe may be a first subframe of the set of subframes used for repetitions of the PDSCH. In some implementations, the specific subframe may be a last subframe of the set of subframes used for repetitions of the PDSCH. In other implementations, the UE receives a message identifying a subframe of the H-SFN, the identified subframe corresponding to the PUR start time. At block506, the UE (e.g., using the antenna252, MOD254, TX processor264, controller/processor280, memory282, and/or the like) transmits a signal including the one or more LSBs to a base station. The signal may be included in an RLC message, an RRC message, or another type of signal. The base station may align the PUR start time with the UE based on the one or more LSBs included in the message. FIG.6is a diagram illustrating an example process600performed, for example, by a UE, in accordance with various aspects of the present disclosure. As shown inFIG.6, at block602, a UE (e.g., using the controller/processor280, memory282, and/or the like) decodes a downlink (DL) transmission. At block604, the UE (e.g., using the controller/processor280, memory282, and/or the like) determines whether the DL transmission is a retransmission. In some examples, the UE determines whether the DL transmission is a retransmission based on an RRC message. At block606, the UE (e.g., using the controller/processor280, memory282, and/or the like) uses an H-SFN of the DL transmission as a reference H-SFN for determining a PUR start time when the DL transmission is the retransmission. In some implementations, the UE determines the H-SFN based on a specific subframe within the subframes used for repetitions of a physical downlink shared channel (PDSCH). In some such implementations, the specific subframe is a first subframe of the subframes used for repetitions of the PDSCH. In other such implementations, the specific subframe is a last subframe of the subframes used for repetitions of the PDSCH. In other implementations, the UE receives, from the base station, PUR configuration information and determines a subframe corresponding to the PUR start time based on the PUR configuration information. In still other implementations, the UE receives a message identifying a subframe of the H-SFN. In such implementations, the identified subframe corresponds to the PUR start time. At block608, the UE (e.g., using the antenna252, MOD254, TX processor264, controller/processor280, memory282, and/or the like) transmits, to a base station, data on a PUR at the PUR start time. Implementation examples are described in the following numbered clauses:1. A method for wireless communication, comprising:receiving a pre-configured uplink resource (PUR) configuration information comprising at least one least significant bit (LSB) of a hyper system frame number (H-SFN);determining a PUR start time based on the H-SFN identified at least by the LSB; andtransmitting, to a base station, a data message on a PUR indicated in the PUR configuration information at the PUR start time.2. The method of clause 1, in which a value of the LSB corresponds to an LSB of a current H-SFN or a last H-SFN.3. The method of any of clauses 1-2, in which:the LSB indicates a reference time of an initial downlink message; andthe initial downlink message comprises the PUR configuration information.4. The method of clause 3, in which the initial downlink message comprises a radio resource control (RRC) connection release message.5. The method of clause 3, in which retransmissions of the initial downlink message comprise the LSB.6. The method of any of clauses 1-5, in which a value of the LSB corresponds to an H-SFN subsequent to an initial downlink message.7. The method of any of clauses 1-6, further comprising determining the H-SFN based on a specific subframe of a set of subframes for repetitions of a physical downlink shared channel (PDSCH).8. The method of clause 7, in which the specific subframe is a first subframe of the set of subframes.9. The method of clause 7, in which the specific subframe is a last subframe of the set of subframes used.10. The method of any of clauses 1-9, in which the PUR configuration information comprises an initial configuration information or reconfiguration information.11. A method for wireless communication, comprising:receiving a downlink message comprising pre-configured uplink resource (PUR) configuration information;determining at least one least significant bit (LSB) of a hyper system frame number (H-SFN) corresponding to the received downlink message; andtransmitting a signal including the at least one LSB to a base station.12. The method of clause 11, in which the downlink message comprises a radio resource control (RRC) connection release message.13. The method of any of clauses 11-12, further comprising determining a PUR start time based on the H-SFN corresponding to the at least one LSB.14. The method of any of clauses 11-13, further comprising determining the H-SFN based on a specific subframe within a set of subframes used for repetitions of a physical downlink shared channel (PDSCH).15. The method of clause 14, in which the specific subframe is a first subframe of the set of subframes used for repetitions of the PDSCH.16. The method of clause 14, in which the specific subframe is a last subframe of the set of subframes used for repetitions of the PDSCH.17. The method of any of clauses 11-16, further comprising receiving a message identifying a subframe of the H-SFN, the identified subframe corresponding to a PUR start time.18. A method for wireless communication, comprising:decoding a downlink transmission;determining whether the downlink transmission is a retransmission;determining a pre-configured uplink resource (PUR) start time based on a hyper system frame number (H-SFN) of the downlink transmission as a reference H-SFN when the downlink transmission is the retransmission; andtransmitting, to a base station, data on a PUR at the PUR start time.19. The method of clause 18, further comprising determining whether the downlink transmission is the retransmission based on a radio resource control (RRC) message.20. The method of any of clauses 18-19, further comprising determining the H-SFN based on a specific subframe of a set of subframes used for repetitions of a physical downlink shared channel (PDSCH).21. The method of clause 20, in which the specific subframe is a first subframe of the set of subframes used for repetitions of the PDSCH.22. The method of clause 20, in which the specific subframe is a last subframe of the set of subframes used for repetitions of the PDSCH.23. The method of any of clauses 18-22, further comprising:receiving, from the base station, PUR configuration information; anddetermining a subframe corresponding to the PUR start time based on the PUR configuration information.24. The method of any of clauses 18-23, further comprising receiving a message identifying a subframe of the H-SFN, the identified subframe corresponding to the PUR start time. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. As used herein, the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and/or a combination of hardware and software. Some aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein. Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c). No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. | 44,053 |
11943777 | To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation. DETAILED DESCRIPTION Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for configuring default beams when an uplink TCI state is not indicated to a user equipment. The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. The techniques described herein may be used for various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as NR (e.g. 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). New Radio (NR) is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (SGTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies. New radio (NR) access (e.g., 5G technology) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services may co-exist in the same subframe. Example Wireless Communications System FIG.1illustrates an example wireless communication network100in which aspects of the present disclosure may be performed. For example, a UE120in the wireless communication network100may include an UL subband precoding module configured to perform (or assist the UE120in performing) operations1600described below with reference toFIG.16. Similarly, a base station120(e.g., a gNB) may include an UL subband precoding module configured to perform (or assist the base station120in performing) operations1700described below with reference toFIG.17. As illustrated inFIG.1, the wireless communication network100may include a number of base stations (BSs)110and other network entities. A BS may be a station that communicates with user equipment (UE). Each BS110may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a Node B (NB) and/or a NB subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term “cell” and next generation NodeB (gNB or gNodeB), NR BS, 5G NB, access point (AP), or transmission reception point (TRP) may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in wireless communication network100through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network. In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed. A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown inFIG.1, the BSs110a,110band110cmay be macro BSs for the macro cells102a,102band102c, respectively. The BS110xmay be a pico BS for a pico cell102x. The BSs110yand110zmay be femto BSs for the femto cells102yand102z, respectively. ABS may support one or multiple (e.g., three) cells. Wireless communication network100may also include relay stations. A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. In the example shown inFIG.1, a relay station110rmay communicate with the BS110aand a UE120rin order to facilitate communication between the BS110aand the UE120r. A relay station may also be referred to as a relay BS, a relay, etc. Wireless communication network100may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless communication network100. For example, macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt). Wireless communication network100may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation. A network controller130may couple to a set of BSs and provide coordination and control for these BSs. The network controller130may communicate with the BSs110via a backhaul. The BSs110may also communicate with one another (e.g., directly or indirectly) via wireless or wireline backhaul. The UEs120(e.g.,120x,120y, etc.) may be dispersed throughout the wireless communication network100, and each UE may be stationary or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a BS, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices. Certain wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a “resource block” (RB)) may be 12 subcarriers (or 180 kHz). Consequently, the nominal Fast Fourier Transfer (FFT) size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into sub-bands. For example, a sub-band may cover 1.08 MHz (i.e.,6resource blocks), and there may be 1, 2, 4, 8, or 16 sub-bands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively. Communication systems such as NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD). Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 4 streams per UE. Multi-layer transmissions with up to 4 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. Base stations are not the only entities that may function as a scheduling entity. In some examples, a UE may function as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may communicate directly with one another in addition to communicating with a scheduling entity. InFIG.1, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. A finely dashed line with double arrows indicates interfering transmissions between a UE and a BS. FIG.2illustrates a diagram showing examples for implementing a communications protocol stack in a RAN (e.g., such as the RAN100), according to aspects of the present disclosure. The illustrated communications protocol stack200may be implemented by devices operating in a wireless communication system, such as a 5G NR system (e.g., the wireless communication network100). In various examples, the layers of the protocol stack200may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device or a UE. As shown inFIG.2, the system may support various services over one or more protocols. One or more protocol layers of the protocol stack200may be implemented by the AN and/or the UE. As shown inFIG.2, the protocol stack200is split in the AN (e.g., BS110inFIG.1). The RRC layer205, PDCP layer210, RLC layer215, MAC layer220, PHY layer225, and RF layer230may be implemented by the AN. For example, the CU-CP may implement the RRC layer205and the PDCP layer210. A DU may implement the RLC layer215and MAC layer220. The AU/RRU may implement the PHY layer(s)225and the RF layer(s)230. The PHY layers225may include a high PHY layer and a low PHY layer. The UE may implement the entire protocol stack200(e.g., the RRC layer205, the PDCP layer210, the RLC layer215, the MAC layer220, the PHY layer(s)225, and the RF layer(s)230). FIG.3illustrates example components of BS110and UE120(as depicted inFIG.1), which may be used to implement aspects of the present disclosure. For example, antennas352, processors366,358,364, and/or controller/processor380of the UE120may be configured (or used) to perform operations1600ofFIG.16and/or antennas334, processors320,330,338, and/or controller/processor340of the BS110may be configured (or used) to perform operations1700described below with reference toFIG.17. At the BS110, a transmit processor320may receive data from a data source312and control information from a controller/processor340. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. The processor320may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor320may also generate reference symbols, e.g., for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor330may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs)332athrough332t. Each modulator332may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators332athrough332tmay be transmitted via the antennas334athrough334t, respectively. At the UE120, the antennas352athrough352rmay receive the downlink signals from the base station110and may provide received signals to the demodulators (DEMODs) in transceivers354athrough354r, respectively. Each demodulator354may condition (e.g., filter, amplify, down-convert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector356may obtain received symbols from all the demodulators354athrough354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor358may process (e.g., demodulate, de-interleave, and decode) the detected symbols, provide decoded data for the UE120to a data sink360, and provide decoded control information to a controller/processor380. In a MIMO system, a transmitter (e.g., BS120) includes multiple transmit antennas354athrough354r, and a receiver (e.g., UE110) includes multiple receive antennas352athrough352r. Thus, there are a plurality of signal paths394from the transmit antennas354athrough354rto the receive antennas352athrough352r. Each of the transmitter and the receiver may be implemented, for example, within a UE110, a BS120, or any other suitable wireless communication device. The use of such multiple antenna technology enables the wireless communication system to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data, also referred to as layers, simultaneously on the same time-frequency resource. The data streams may be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data streams with different weighting and phase shifting) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE(s) with different spatial signatures, which enables each of the UE(s) to recover the one or more data streams destined for that UE. On the uplink, each UE transmits a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream. The number of data streams or layers corresponds to the rank of the transmission. In general, the rank of the MIMO system is limited by the number of transmit or receive antennas, whichever is lower. In addition, the channel conditions at the UE, as well as other considerations, such as the available resources at the base station, may also affect the transmission rank. For example, the rank (and therefore, the number of transmission layers) assigned to a particular UE on the downlink may be determined based on the rank indicator (RI) transmitted from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and a measured signal-to-interference-and-noise ratio (SINR) on each of the receive antennas. The RI may indicate, for example, the number of layers that may be supported under the current channel conditions. The base station may use the RI, along with resource information (e.g., the available resources and amount of data to be scheduled for the UE), to assign a transmission rank to the UE. On the uplink, at UE120, a transmit processor364may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source362and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor380. The transmit processor364may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor364may be precoded by a TX MIMO processor366if applicable, further processed by the demodulators in transceivers354athrough354r(e.g., for SC-FDM, etc.), and transmitted to the base station110. At the BS110, the uplink signals from the UE120may be received by the antennas334, processed by the modulators332, detected by a MIMO detector336if applicable, and further processed by a receive processor338to obtain decoded data and control information sent by the UE120. The receive processor338may provide the decoded data to a data sink339and the decoded control information to the controller/processor340. The controllers/processors340and380may direct the operation at the BS110and the UE120, respectively. The processor340and/or other processors and modules at the BS110may perform or direct the execution of processes for the techniques described herein. The memories342and382may store data and program codes for BS110and UE120, respectively. A scheduler344may schedule UEs for data transmission on the downlink and/or uplink. FIG.4is a diagram showing an example of a frame format400for NR. The transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9. Each subframe may include a variable number of slots depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols) depending on the subcarrier spacing. The symbol periods in each slot may be assigned indices. A mini-slot, which may be referred to as a sub-slot structure, refers to a transmit time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols). Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission and the link direction for each subframe may be dynamically switched. The link directions may be based on the slot format. Each slot may include DL/UL data as well as DL/UL control information. In NR, a synchronization signal (SS) block is transmitted. The SS block includes a PSS, a SSS, and a two symbol PBCH. The SS block can be transmitted in a fixed slot location, such as the symbols0-3as shown inFIG.4. The PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half-frame timing, the SS may provide the CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SS blocks may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI) can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes. The SS block can be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions for mmW. The up to sixty-four transmissions of the SS block are referred to as the SS burst set. SS blocks in an SS burst set are transmitted in the same frequency region, while SS blocks in different SS bursts sets can be transmitted at different frequency locations. A UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated set of resources for transmitting a pilot signal to a network. When operating in the RRC common state, the UE may select a common set of resources for transmitting a pilot signal to the network. In either case, a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals, may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs. Example Default Configuration of Uplink (UL) Transmission Configuration Indicator (TCI) State Aspects of the present disclosure provide mechanisms that may provide for default configuration of uplink transmission configuration states (e.g., when no TCI state is configured when uplink transmissions are to be performed). By providing techniques for identifying a default configuration for uplink transmissions when no TCI state is configured, aspects of the present disclosure may allow for assumptions to be made to facilitate uplink beam selection. A UE need not wait for a gNodeB to indicate a configuration of an UL TCI state before performing uplink transmissions in a multi-beam environment. Because a UE may not need to wait for the gNodeB to indicate a configuration of an UL TCI state before performing uplink transmissions, latencies may be reduced from signaling reductions in communications between the UE and the gNodeB, and a UE may be able to more quickly commence uplink transmissions to the gNodeB. In Rel-16, signaling overhead reductions may allow a gNB to not configure spatial relations for the physical uplink control channel (PUCCH) or SRS. Rule based determinations may be used to identify a default spatial relation that is to be used if a spatial relation has not been configured. The use of rule-based determinations to identify default spatial relations may allow for lower latency in communications between a UE and a gNB, which may improve overall throughput. Enhancements for multi-beam operation may target different operating frequencies, such as the FR1 and FR2 bands. Some of these enhancements may facilitate more efficient beam management to support intra-cell and inter-cell mobility and/or a larger number of configured TCI states. For example, a common beam may be used for data and control transmission and/or reception for both downlink and uplink (e.g., for intra-band carrier aggregation). A unified TCI framework for downlink/uplink beam indication may be used. Further, signaling mechanisms, such as more dynamic usage of control signaling, may be used to improve latency and efficiency. For UEs equipped with multiple panels, various mechanisms may be used to facilitate uplink beam selection. For example, UL beam indication may be based on a unified TCI framework in which TCI states are associated with both UL and DL beam indication. Simultaneous transmission may be enabled across multiple panels, and fast panel selection may be enabled. Enhancements to support multi-transmit/receive pair (TRP) deployment may target both the FR1 and FR2 bands. These enhancements may improve reliability and robustness for various channels, such as the physical downlink control channel (PDCCH), physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), etc. using multi-TRP and/or multi-panel transmission and reception. Various features may enable inter-cell multi-TRP operations, and some enhancements may allow for simultaneous multi-TRP transmission with multi-panel reception. The TCI state framework used for downlink transmissions may be extended to uplink transmissions. Beam management generally includes TCI state-based quasi co-location (QCL) definitions for the downlink and spatial relation based configurations for the uplink. Default beams for use may be identified in the context of an uplink spatial relation for PUCCH and/or SRS and when a scheduling DCI is received within a scheduling threshold of a scheduled transmission on the physical downlink shared channel. Generally, the default parameters to use for SRS resources are defined; however, the default uplink parameters (e.g., default beam and/or default PL RS) may not be defined when an UL TCI state is not indicated or configured for uplink transmission. When the uplink TCI state is not indicated or configured for uplink transmission of the physical uplink control channel, the physical uplink shared channel, sounding reference signals, and/or the physical random access channel (PRACH), embodiments of the present disclosure may allow for the default uplink beam and/or path loss (PL) reference signal (RS) to be determined according to a set of rules. FIG.5illustrates example operations500that may be performed by a user equipment (UE) to determine an uplink beam for use in uplink transmissions. As illustrated, operations500begin, at502, where the UE determines, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) to use for an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission. In some aspects, the one or more rules based on whether a control resource set (CORESET) is configured in an active DL BWP. If a CORESET is not configured in an active DL BWP, the rules may be based on whether certain TCI states are activated in an active DL BWP. At504, the UE sends the uplink transmission in accordance with the determination. FIG.6illustrates example operations600that may be performed by a network entity to process received uplink transmissions based on the timing of an uplink transmission. Operations600begin, at602, where a network entity determines, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) for a user equipment (UE) to use an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission. At604, the network entity processes the uplink transmission in accordance with the determination. In some embodiments, when a CORESET is configured in an active downlink (DL) bandwidth part (BWP), the default beam and/or corresponding PL RS may follow a spatial QCL reference signal, such as the QCL-TypeD reference signal identified in the downlink TCI state or QCL assumptions of one CORESET in the active DL BWP. The QCL assumptions may be, for example, the QCL assumptions used for receiving the CORESET in the active DL BWP. For example, the QCL assumptions may be based on the CORESET with the lowest identifier or highest identifier in the active DL BWP. In some aspects, the default uplink beam may correspond to a downlink beam indicated by a DL TCI state. In some embodiments, when a CORESET is not configured in an active DL BWP for uplink transmission, but at least one PDSCH TCI state is activated in the active DL BWP, the default UL beam and/or corresponding default PL RS may follow the QCL-TypeD reference signal in the active PDSCH TCI state or other downlink TCI state in the active DL BWP. The determined UL beam and/or PL RS may be corresponding, for example, to the beam and/or PL RS associated with a lowest or highest TCI state identifier in the active DL BWP. That is, the PDSCH TCI state may be used as a quasi-colocation (QCL) source in addition to or in lieu of using CSI-RSs or SSBs as a QCL source from which QCL assumptions may be made. In some embodiments, if an uplink transmission is scheduled within a scheduling threshold using a DCI that carries the corresponding UL TCI state, the default TCI state may be used for uplink transmissions for an amount of time corresponding to a scheduling threshold period. The scheduling threshold period may be a configured value or a value determined based on a capability of the UE. After the scheduling threshold amount of time has elapsed, uplink transmissions may be performed according to the parameters (e.g., beam indication, PL RS, etc.) included in the UL TCI state. Before the scheduling threshold amount of time has expired, however, the default TCI state may be used for uplink transmissions. The default TCI state may be different from the UL TCI state carried in the received DCI. FIG.7illustrates a communications device700that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated inFIG.5. The communications device700includes a processing system702coupled to a transceiver708(e.g., a transmitter and/or a receiver). The transceiver708is configured to transmit and receive signals for the communications device700via an antenna710, such as the various signals as described herein. The processing system702may be configured to perform processing functions for the communications device700, including processing signals received and/or to be transmitted by the communications device700. The processing system702includes a processor704coupled to a computer-readable medium/memory712via a bus706. In certain aspects, the computer-readable medium/memory712is configured to store instructions (e.g., computer-executable code) that when executed by the processor704, cause the processor704to perform the operations illustrated inFIG.5, or other operations for performing the various techniques discussed herein for a beam switching gap. In certain aspects, computer-readable medium/memory712stores code714for determining, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) to use for an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission; and code716for sending the uplink transmission in accordance with the determination, in accordance with aspects of the present disclosure. In certain aspects, the processor704has circuitry configured to implement the code stored in the computer-readable medium/memory712. The processor704includes circuitry718for determining, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) to use for an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission; and circuitry720for sending the uplink transmission in accordance with the determination, in accordance with aspects of the present disclosure. FIG.8illustrates a communications device800that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated inFIG.6. The communications device800includes a processing system802coupled to a transceiver808(e.g., a transmitter and/or a receiver). The transceiver808is configured to transmit and receive signals for the communications device800via an antenna810, such as the various signals as described herein. The processing system802may be configured to perform processing functions for the communications device800, including processing signals received and/or to be transmitted by the communications device800. The processing system802includes a processor804coupled to a computer-readable medium/memory812via a bus806. In certain aspects, the computer-readable medium/memory812is configured to store instructions (e.g., computer-executable code) that when executed by the processor804, cause the processor804to perform the operations illustrated inFIG.6, or other operations for performing the various techniques discussed herein for a beam switching gap. In certain aspects, computer-readable medium/memory812stores code814for determining, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) for a user equipment (UE) to use for receiving an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission; and code816for processing the uplink transmission in accordance with the determination, in accordance with aspects of the present disclosure. In certain aspects, the processor804has circuitry configured to implement the code stored in the computer-readable medium/memory812. The processor804includes circuitry818for determining, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) for a user equipment (UE) to use for receiving an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission; and circuitry820for processing the uplink transmission in accordance with the determination, in accordance with aspects of the present disclosure. Example Embodiments Embodiment 1: A method of wireless communications by a User Equipment (UE), comprising: determining, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) to use for an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission; and sending the uplink transmission in accordance with the determination. Embodiment 2: The method of Embodiment 1, wherein the uplink transmission comprises at least one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), or a physical random access channel (PRACH). Embodiment 3: The method of Embodiments 1 or 2, wherein, according to one of the rules, the UE uses a downlink transmission configuration indicator (TCI) state as a quasi co-location source to determine at least one of the default uplink beam or PL RS. Embodiment 4: The method of Embodiment 3, wherein the UE determines, as the default uplink beam, an uplink beam corresponding to a downlink beam indicated by the downlink TCI state. Embodiment 5: The method of Embodiments 1 or 2, wherein, according to one of the rules: the UE determines at least one of the default uplink beam or default PL RS based on spatial quasi co-location (QCL) reference signal (RS) or QCL assumption of at least one control resource set (CORESET) in an active downlink bandwidth part (BWP). Embodiment 6: The method of Embodiment 5, wherein, according to one of the rules: the spatial QCL RS comprises a QCL Type-D RS. Embodiment 7: The method of Embodiments 5 or 6, wherein the at least one CORESET is selected based on a value of its CORESET ID relative to one or more other CORESET IDs in the active downlink BWP. Embodiment 8: The method of Embodiments 1 or 2, wherein, according to one of the rules: the UE determines, when a control resource set (CORESET) is not configured in an active downlink bandwidth part (BWP), at least one of the default uplink beam or default PL RS based on a spatial quasi co-location (QCL) reference signal (RS) in an active physical downlink shared channel (PDSCH) transmission configuration indicator (TCI) state in an active downlink bandwidth part (BWP). Embodiment 9: The method of Embodiment 8, wherein the at active PDSCH TCI state is selected based on a value of its TCI state ID relative to one or more other TCI state IDs in the active downlink BWP. Embodiment 10: The method of Embodiments 1 through 9, wherein the UE is configured to use the default uplink beam or default PL RS if the uplink transmission is scheduled within a threshold scheduling period by a downlink control information (DCI) that carries a corresponding uplink transmission configuration indicator (TCI) state for the uplink transmission. Embodiment 11: The method of Embodiment 10, wherein the threshold scheduling period is at least one of a configured value or determined based on capability of the UE. Embodiment 12: A method of wireless communications by a network entity, comprising: determining, based on one or more rules, at least one of a default uplink beam or default path loss reference signal (PL RS) for a user equipment (UE) to use for receiving an uplink transmission in the absence of a signaled uplink transmission configuration indicator (TCI) state for the uplink transmission; and processing the uplink transmission in accordance with the determination. Embodiment 13: The method of Embodiment 12, wherein the uplink transmission comprises at least one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), or a physical random access channel (PRACH). Embodiment 14: The method of Embodiments 12 or 13, wherein, according to one of the rules, the network entity determines the UE uses a downlink transmission configuration indicator (TCI) state as a quasi co-location source to determine at least one of the default uplink beam or PL RS. Embodiment 15: The method of Embodiment 14, wherein the network entity determines that the UE uses, as the default uplink beam, an uplink beam corresponding to a downlink beam indicated by the downlink TCI state. Embodiment 16: The method of Embodiments 12 or 13, wherein, according to one of the rules: the network entity determines the UE uses at least one of the default uplink beam or default PL RS based on spatial quasi co-location (QCL) reference signal (RS) or QCL assumption of at least one control resource set (CORESET) in an active downlink bandwidth part (BWP). Embodiment 17: The method of Embodiment 16, wherein, according to one of the rules: the spatial QCL RS comprises a QCL Type-D RS. Embodiment 18: The method of Embodiments 16 or 17, wherein the at least one CORESET is selected based on a value of its CORESET ID relative to one or more other CORESET IDs in the active downlink BWP. Embodiment 19: The method of Embodiments 12 or 13, wherein, according to one of the rules: the network entity determines, when a control resource set (CORESET) is not configured in an active downlink bandwidth part (BWP), the UE uses at least one of the default uplink beam or default PL RS based on a spatial quasi co-location (QCL) reference signal (RS) in an active physical downlink shared channel (PDSCH) transmission configuration indicator (TCI) state in an active downlink bandwidth part (BWP). Embodiment 20: The method of Embodiment 19, wherein the at active PDSCH TCI state is selected based on a value of its TCI state ID relative to one or more other TCI state IDs in the active downlink BWP. Embodiment 21: The method of Embodiments 12 through 20, wherein the network entity determines the UE is configured to use the default uplink beam or default PL RS if the uplink transmission is scheduled within a threshold scheduling period by a downlink control information (DCI) that carries a corresponding uplink transmission configuration indicator (TCI) state for the uplink transmission. Embodiment 22: The method of Embodiment 21, wherein the threshold scheduling period is at least one of a configured value or determined based on capability of the UE. Embodiment 23: An apparatus for wireless communications by a user equipment (UE), comprising: a processor; and a memory having instructions which, when executed by the processor, performs the operations of any of Embodiments 1 through 11. Embodiment 24: An apparatus for wireless communications by a network entity, comprising: a processor; and a memory having instructions which, when executed by the processor, performs the operations of any of Embodiments 12 through 22. Embodiment 25: An apparatus for wireless communications by a user equipment (UE), comprising: means capable of performing the operations of any of Embodiments 1 through 11. Embodiment 26: An apparatus for wireless communications by a network entity, comprising: means capable of performing the operations of any of Embodiments 12 through 22 Embodiment 27: A computer-readable medium having instructions stored thereon which, when executed by a processor, performs the operations of any of Embodiments 1 through 11. Embodiment 28: A computer-readable medium having instructions stored thereon which, when executed by a processor, performs the operations of any of Embodiments 12 through 22. Additional Considerations The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c). As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like. The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. For example, the various processor shown inFIG.3may be configured to perform operations1000and1100ofFIGS.10and11. The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. If implemented in hardware, an example hardware configuration may comprise a processing system in a wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including a processor, machine-readable media, and a bus interface. The bus interface may be used to connect a network adapter, among other things, to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal120(seeFIG.1), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. The processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system. If implemented in software, the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media. A computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface. Alternatively, or in addition, the machine-readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files. Examples of machine-readable storage media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable media may be embodied in a computer-program product. A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer-readable media may comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from that software module. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Thus, in some aspects computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects computer-readable media may comprise transitory computer-readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media. Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein (e.g., instructions for performing the operations described herein and illustrated inFIGS.15and16). Further, it should be appreciated that modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized. It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims. | 57,802 |
11943778 | DETAILED DESCRIPTION Technical solutions in implementations of the present application will be described below with reference to the drawings in implementations of the present application. It is apparent that the implementations described are a part of implementations of the present application, but not all implementations. According to the implementations of the present application, all other implementations achieved by a person of ordinary skill in the art without paying an inventive effort are within the protection scope of the present application. The technical solutions of the implementations of the present application may be applied to various communication systems, such as a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a Universal Mobile Telecommunication System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, or a 5G system, etc. Illustratively, a communication system100applied in an implementation of the present application is shown inFIG.1. The communication system100may include a network device110, and the network device110may be a device that communicates with a terminal device120(or referred to as a communication terminal, or a terminal). The network device110may provide communication coverage for a specific geographical area, and may communicate with terminal devices located within the coverage area. Optionally, the network device110may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a NodeB (NB) in a WCDMA system, an Evolutional Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switch center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network side device in a 5G network, or a network device in a future evolved Public Land Mobile Network (PLMN), etc. The communication system100also includes at least one terminal device120located within the coverage area of the network device110. As used herein, the term “terminal device” includes, but not limited to, a device configured to receive/send a communication signal via a wired circuit, for example, via Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable; and/or another data connection/network; and/or via a wireless interface, for instance, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, and an AM-FM broadcast sender; and/or another terminal device; and/or an Internet of Things (IoT) device. A terminal device configured to communicate via a wireless interface may be referred to as a “wireless communication terminal”, a “wireless terminal” or a “mobile terminal”. Examples of the mobile terminal include, but not limited to, a satellite or a cellular telephone, a Personal Communication System (PCS) terminal that may combine with a cellular radio telephone and data processing, faxing, and data communication abilities, a PDA that may include a radio telephone, a pager, an Internet/intranet access, a Web browser, a memo pad, a calendar, and/or a Global Positioning System (GPS) receiver, and a conventional laptop and/or palmtop receiver or another electronic apparatus including a radio telephone transceiver. The terminal device may be referred to as an access terminal, a User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile platform, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with a wireless communication function, a computing device, or another processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, or the like. Optionally, terminal direct connection (Device to Device, D2D) communication may be performed between the terminal devices120. Optionally, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network. FIG.1shows one network device and two terminal devices as an example. Optionally, the communication system100may include multiple network devices, and other quantity of terminal devices may be included within the coverage area of each network device, and this is not limited in the implementations of the present application. Optionally, the communication system100may also include another network entity such as a network controller, a mobile management entity, etc., which is not restricted in implementations of the present application. It should be understood that, a device with a communication function in a network/system in the implementation of the present application may be referred to as a terminal device. Taking the communication system100shown inFIG.1as an example, the terminal device may include a network device110and a terminal device120which have communication functions, and the network device110and the terminal device120may be the specific devices described above, which will not be repeated here again. The terminal device may also include another device in the communication system100, such as a network controller, a mobile management entity, or another network entity, which is not restricted in the implementations of the present application. It should be understood that the terms “system” and “network” are often used interchangeably in this document. The term “and/or” in this document is merely an association relationship describing associated objects, indicating that there may be three relationships, for example, A and/or B may indicate three cases: A alone, A and B, and B alone. In addition, the symbol “/” in this document generally indicates that objects before and after the symbol “/” have an “or” relationship. In the 5G system, in order to improve flexibility of resource allocation and reduce delay, a time domain position of a channel may be allocated in units of a symbol. Specifically, a time domain resource for a channel may be indicated by an indication mode of “a starting symbol+a quantity of symbols”. For a reference point of a starting position of the time domain resource, following solutions may be adopted: Solution 1: taking a starting position of a time slot as the reference point of the starting position of the time domain resource, that is, the starting position of the time domain resource is calculated relative to a starting position of a time slot. Solution 2: taking a position of a downlink control channel as the reference point of the starting position of the time domain resource, that is, the starting position of the time domain resource is calculated relative to a position of a downlink control channel. For the above solution 1, there may be a problem that scheduling of low-latency services cannot be effectively realized. Specifically, a scheduled channel is usually located behind the downlink control channel that schedules this channel. Since where the downlink control channel is located in the time slot is unknown, possible positions of a starting symbol can only be distributed within one time slot as uniformly as possible, that is, reference points of the starting position are uniformly distributed within one time slot. As shown inFIG.2, four possible positions of the starting symbol may be uniformly set within one time slot. In this case, when the downlink control channel is located at certain positions in the time slot, such as positions of a downlink control channel inFIG.2, since the scheduled channel cannot be transmitted close to the downlink control channel, scheduling of a low-latency service cannot be realized. For the solution 2, when the downlink control channel is located at any position in the time slot, the starting symbol of the scheduled channel may be configured at a position close to the downlink control channel, as shown inFIG.3. However, the solution 2 cannot realize effectively scheduling a channel farther from the downlink control channel. For example, a time interval between the starting symbol of the scheduled channel and the downlink control channel exceeds one time slot. In this case, if this solution 2 is adopted, overhead of control signaling will be caused to increase. In view of this, an implementation of the present application provides a method for wireless communication, in which a terminal device can determine a reference point of a starting position of a time domain resource of a scheduled channel according to a Radio Network Temporary Identity (RNTI) used for scrambling Downlink Control Information (DCI), so that flexibly configuring reference points of different time domain resources without increasing DCI overhead can be realized, which is beneficial to meet requirements of different types of services. Hereinafter, the method for wireless communication according to implementations of the present application will be explained with reference toFIGS.4to9. It should be understood thatFIGS.4to9show main acts or operations of the wireless communication method according to implementations of the present application, but these acts or operations are only examples, and implementations of the present application may also perform other operations or variations of various operations ofFIGS.4to9. In addition, various acts in the method implementation of present application may also be performed in different orders as described in the method implementation, and it is possible that not all operations in the method implementation need to be performed. FIG.4is a schematic flowchart of a method for wireless communication according to an implementation of the present application. As shown inFIG.4, the method200includes following contents. In S210, a terminal device receives Downlink Control Information (DCI) sent by a network device. In S220, the terminal device determines a resource for a first channel in at least one resource table according to a Radio Network Temporary Identity (RNTI) for scrambling the DCI, wherein the at least one resource table contains at least two types of resources, and reference points of starting positions of the at least two types of resources are different. Optionally, in an implementation of the present application, the first channel may be a Physical Uplink Shared Channel (PUSCH), a Physical Downlink Shared Channel (PDSCH), or another data channel, which is not limited in implementations of the present application. As an example and not limitation, the resource in the at least one resource table may be represented by at least one of following parameters: a starting symbol, a length, an ending symbol and a mapping type. It should be understood that in an implementation of the present application, at least two types of resources may be included in the at least one resource table, and the at least two types of resources may be located in a same resource table or different resource tables, which is not limited by implementations of the present application. The at least two types of resources respectively correspond to reference points of different time domain resources. Optionally, the reference point of the time domain resource may be the reference point of the starting position or a reference point of an ending position, that is to say, the reference points of the starting positions or the ending positions of the at least two types of resources may be different. To simplify the description, the following description will take the reference point of the time domain resource as the reference point of the starting position as an example, but implementations of the present application are not limited to this. Optionally, in an implementation of the present application, the at least two types of resources include a first type of resource and a second type of resource, wherein the reference point of the starting position of the first type resource may be a starting position of a time slot, in a specific implementation, the first type of resource may be a resource determined using the aforementioned solution 1, and the reference point of the starting position of the second type of resource may be the DCI or the time domain position of a first resource range including the DCI. In a specific implementation, the second type of resource may be a resource determined using the aforementioned solution 2, that is, a position of a downlink control channel is taken as the reference point of the starting position. It should be understood that the above two types of resources are only examples, and the at least two types of resources may also include a third type of resource. A reference point of a starting position of the third type of resource may be a starting position of a subframe, or a starting position of a radio frame, or a starting position of a radio frame period, etc. This is not limited by implementations of the present application. For convenience of description, hereinafter, the at least two types of resources including the first type of resource and the second type of resource are taken as an example, but implementations of the present application are not limited to this. Optionally, in some implementations, the time domain position of the first resource range including the DCI may specifically be a starting symbol or an ending symbol of a Control Resource Set (CORESET) or a search space including the DCI. As shown inFIG.5andFIG.6, it is shown respectively that the time domain position of the first resource range including the DCI is the starting symbol and the ending symbol of the CORESET or the search space including the DCI. That is to say, the starting symbol of the first channel may take the starting symbol or the ending symbol of the CORESET or the search space including DCI scheduling the first channel as the reference point of the starting position of the time domain resource, then in a specific implementation, according to the position of the starting symbol of the CORESET where the DCI is located or the search space, and an offset of the first channel relative to the CORESET where the DCI is located or the starting symbol of the search space, a position of a starting symbol of the first channel may be determined, for example, if the starting symbol of the CORESET where the DCI is located is symbol 2 and the offset is 3, the starting position of the first channel may be determined as symbol 5. In an implementation of the present application, the terminal device may determine the resource for the first channel by the RNTI used for scrambling the DCI, for example, the starting position and length of the time domain resource of the first channel and the reference point of the starting position of the time domain resource. In a specific implementation, different RNTIs may correspond to different types of resources, that is, different RNTIs may be used for indicating reference points of different starting positions, and the network device may determine the reference point of the starting position of the time domain resource for a service to be transmitted according to a service type of the service to be transmitted, for example, if the service to be transmitted is an Ultra-Reliable and Low Latency Communication (URLLC) service, the network device may determine to use the second type of resource, for example, taking the position of the DCI as the reference point of the starting position; or if the service to be transmitted is Enhance Mobile Broadband (eMBB), the network device may determine to use the first type of resource, for example, taking the starting position of the time slot as the reference point of the starting position. Furthermore, the network device may scramble DCI using the determined RNTI corresponding to the reference point of the starting position, and the terminal device may determine the type of resource for the first channel according to the RNTI used for scrambling the DCI, so that it can be realized that reference points of different time domain resources are dynamically configured for different types of services without increasing DCI overhead, which is conducive to meeting service requirements of different services and improving resource utilization rate of a communication system. In another optional implementation, the network device may configure the terminal device with a reference point for the starting position of the resource of the first channel through a sending mode of the DCI, where the sending mode of the DCI may refer to a scrambling code sequence used for sending the DCI, that is, RNTI. Of course, it may also be at least one of a beam, an antenna port, a precoding matrix, an Modulation and Coding Scheme (MCS), a Physical Downlink Control Channel (PDCCH) resource, a search space and an aggregation level, used for sending the DCI, or it may also be sequence information such as a mask sequence, a Demodulation Reference Signal (DMRS) sequence, etc. used for processing the DCI, or the like, which is not limited by implementation of the present application. That is to say, the network device may indirectly indicate the type of resource used for a first channel through at least one piece of the above information, so that flexible configuration of the reference point of time domain resource can be realized without increasing additional overhead, which is beneficial to configure appropriate reference points of time domain resources for different services to meet service requirements. It should be understood that the implementation of implicitly indicating the reference point of the starting position by the sending mode of the DCI is similar to the implementation of indicating the reference point of the starting position by the RNTI. For example, the beams used for sending the DCI may correspond to the reference points of different starting positions respectively, or different mask sequences correspond to the reference points of different starting positions, which is not repeated here. Optionally, in some implementations, the RNTI used for scrambling the DCI may be a first RNTI or a second RNTI, wherein the first RNTI may be a Cell Radio Network Temporary Identity (C-RNTI), and the second RNTI may be another RNTI except the C-RNTI, for example, a Paging Radio Network Temporary Identity (P-RNTI), etc., which are not limited in implementations of present application. Optionally, in some implementations, the method200may further include: the terminal device receives first configuration information sent by the network device, wherein the first configuration information includes the at least one resource table for determining the resource of the first channel. That is, the at least one resource table may be configured by the network device, and in another alternative implementation, the at least one resource table may be preset on the terminal device, or it may be agreed by a protocol or determined through negotiation between the network device and the terminal device. Implementations of the present application do not limit an acquisition mode of the at least one resource table. Optionally, in some implementations, S220may specifically include: the terminal device determines a target resource table in the at least one resource table and a type of a resource in the target resource table according to the RNTI for scrambling the DCI; the terminal device determines the resource for the first channel in the target resource table according to indication information in the DCI. Specifically, different RNTIs correspond to different types of resources, or different RNTIs are used for indicating reference points of different starting positions. In some implementations, the at least one resource table may include multiple resource tables (denoted as Case 1), each resource table corresponds to a reference point of a corresponding starting position, and the RNTI may have a corresponding relationship with the multiple resource tables. In this case, the terminal device may determine which resource table to use as well as the type of resource in the resource table according to the RNTI used for scrambling the DCI. In some other implementations, the at least one resource table may only include one resource table (denoted as Case 2). In this case, the resource table may correspond to different types of resources under different RNTIs, that is, the reference points of the starting positions corresponding to the resource in the resource table are different under different RNTIs, so that the terminal device may determine the type of resource in the resource table according to the RNTI used for scrambling the DCI, that is, the reference point of the starting point corresponding to the resource in the resource table. Further, the terminal device may determine which resource in the target resource table is used as the resource of the first channel according to the indication information included in the DCI, so that the first channel may be sent using the resource of the first channel. Hereinafter, the mode of determining the resource of the first channel in the above Cases 1 and 2 will be specifically explained. Case 1: the at least one resource table includes a first resource table and a second resource table, wherein the first resource table corresponds to the first RNTI, a resource in the first resource table is the first type of resource, the second resource table corresponds to the second RNTI, and at least one resource in the second resource table is the second type of resource. That is to say, in Case 1, different resource tables may be configured for different RNTIs, and the resource in the first resource table corresponding to the first RNTI is the first type of resource, that is, the resource in the first resource table takes the starting position of the time slot as the reference point of the time domain resource, and the second resource table corresponding to the second RNTI includes at least one second type of resource. In an alternative implementation, the resources in the second resource table are all the second type of resources, or in another alternative implementation, part of resources in the second resource table are the first type of resources and other resources are the second type of resources. Which resources in the second resource table are the second type of resources may be determined according to configuration of the network device or a preset condition. For example, the network device may configure the resource with a starting symbol within a certain range as the second type of resource, or the preset condition may also be that the resource with a starting symbol smaller than a specific value is the second type of resource, which is not limited by implementations of the present application. In a first implementation of Case 1, the terminal device determines the target resource table in the at least one resource table and the type of the resource in the target resource table according to the RNTI for scrambling the DCI, including: if the RNTI for scrambling the DCI is the first RNTI, the terminal device determines that the first resource table is the target resource table and the resource in the first resource table is the first type of resource; or if the RNTI for scrambling the DCI is the second RNTI, the terminal device determines that the second resource table is the target resource table, and at least one resource in the second resource table is a candidate second type of resource. It should be noted that in some implementations, the candidate second type of resource may be the second type of resource, that is, the candidate second type of resource may be directly determined as the second type of resource; or, in some other implementations, the candidate second type of resource may be understood as a to-be-determined type of resource. If a certain condition is met, the candidate second type of resource may be determined as the second type of resource; otherwise, the candidate second type of resource is determined as the first type of resource. For example, when a time-slot-level offset K of the DCI is zero, that is, when the DCI and the first channel are in a same time slot, it may be determined that the candidate second type of resource is the second type of resource; otherwise, it is determined that the candidate second type of resource is the first type of resource. That is to say, whether the resource is the second type of resource still needs to meet a specific additional condition. To simplify the description, the second type of resource is directly used for description below, and this judgment process is omitted. Specifically, in a case that different RNTIs correspond to different resource tables, the terminal device may determine the target resource table and the type of resource in the target resource table according to the RNTI used for scrambling DCI. For example, if the RNTI is the first RNTI, the terminal device may determine that the first resource table corresponding to the first RNTI is the target resource table and the resource in the first resource table is the first type of resource; or if the RNTI is the second RNTI, the terminal device may determine the second resource table corresponding to the second RNTI as the target resource table, and may further determine which resources in the second resource table are the second type of resources. Then, the target resource in the target resource table may be determined according to the indication information in the DCI, so that the first channel may be transmitted on the target resource. In some implementations, the first implementation of Case 1 may be based on such a premise that before the terminal device receives the DCI, the terminal device receives second configuration information sent by the network device, wherein the second configuration information is used for indicating that the second RNTI may be used, that is, the first implementation of Case 1 may be the mode of determining the target resource table and the type of resource in the target resource table in a case that the second RNTI may be used. In a second implementation of Case 1, the terminal device determines the target resource table in the at least one resource table and the type of the resource in the target resource table according to the RNTI for scrambling the DCI, including: the terminal device determines that the first resource table is the target resource table. That is to say, in a case that different RNTIs correspond to different resource tables, the terminal device may directly determine that the first resource table corresponding to the first RNTI is the target resource table, and the resource in the target resource table is the first type of resource, regardless of which RNTI the RNTI used for scrambling the DCI is. In some implementations, the second implementation of Case 1 may be based on such a premise that before the terminal device receives the DCI, the terminal device receives the second configuration information sent by the network device, wherein the second configuration information is used for indicating that the second RNTI is not used, or the terminal device does not receive the second configuration information sent by the network device, that is, the second implementation of Case 1 may be the mode of determining the target resource table and the type of resource in the target resource table in a case that the second RNTI is not used. To sum up, in the Case 1, a specific implementation process of determining the target resource for the first channel may be as shown inFIG.7, and specifically includes: S11, the terminal device receives the first configuration information sent by the network device, and determines the first resource table for the first RNTI and the second resource table for the second RNTI according to the first configuration information. Further, in S12, the terminal device receives the second configuration information of the network device, and determines whether the second RNTI may be used according to the second configuration information. If the second configuration information indicates that the second RNTI may be used, the flow proceeds to S13, otherwise, the flow proceeds to S14, in which the terminal device determines that the first resource table is the target resource table. In S13, the terminal device determines the target resource table according to the RNTI used by the network device to scramble the DCI. If the DCI is scrambled using the first RNTI, the flow proceeds to S15, in which the terminal device determines that the first resource table corresponding to the first RNTI is the target resource table; or if the DCI is scrambled using the second RNTI, the flow proceeds to S16, in which the terminal device determines that the second resource table corresponding to the second RNTI is the target resource table. Further, in S17, the terminal device determines the target resource for the first channel from the target resource table according to the indication information in the DCI. Case 2: the at least one resource table includes a third resource table, wherein at least one resource in the third resource table is a to-be-determined type of resource. That is, a unified third resource table is configured for different RNTIs, and the third resource table includes at least one to-be-determined type of resource, so that the terminal device may determine which type of resource the to-be-determined type of resource is, according to the RNTI for scrambling the DCI. In a first implementation of Case 2, the terminal device determines the target resource table in the at least one resource table and the type of the resource in the target resource table according to the RNTI for scrambling the DCI, including: the terminal device determines that the third resource table is the target resource table; if the RNTI for scrambling the DCI is the first RNTI, the terminal device determines that the to-be-determined type of resource in the target resource table is the first type of resource; or if the RNTI for scrambling the DCI is the second RNTI, the terminal device determines that the to-be-determined type of resource in the target resource table is the second type of resource. Specifically, in a case that different RNTIs correspond to a same resource table, the terminal device may directly determine the third resource table as the target resource table. Further, which type of resource the to-be-determined type of resource in the target resource table is may be determined according to the RNTI for scrambling the DCI. For example, if the RNTI is the first RNTI, the terminal device may determine that the to-be-determined type of resource is the first type resource; or, if the RNTI is the second RNTI, the terminal device may determine that the to-be-determined type of resource is the second type of resource, or the terminal device may firstly determine that the to-be-determined type of resource is a candidate second type of resource, and in a case that a certain condition is met, the candidate second type of resource is determined as the second type of resource, otherwise the candidate second type of resource is determined as the first type of resource, wherein the specific condition may refer to the relevant descriptions in the aforementioned implementations, and is not repeated here. It should be understood that which resources in the third resource table are the to-be-determined type of resources may be configured by the network device or determined according to a preset condition. For example, it may be determined that the resource of which the starting symbol is less than a specific value is the to-be-determined type of resource. The specific implementation may refer to the relevant descriptions of the aforementioned implementations, and is not repeated here. In some implementations, the first implementation of Case 2 may be based on such a premise that before the terminal device receives the DCI, the terminal device receives the second configuration information sent by the network device, wherein the aforementioned is used for indicating that the second RNTI may be used, that is, the first implementation of Case 2 may be the mode of determining the target resource table and the type of resource in the target resource table in a case that the second RNTI may be used. In a second implementation of Case 2, the terminal device determines the target resource table in the at least one resource table and the type of the resource in the target resource table according to the RNTI for scrambling the DCI, including: the terminal device determines that the third resource table is the target resource table; and the terminal device determines that the to-be-determined type of resource in the target resource table is the first type of resource. That is to say, in a case that different RNTIs correspond to a same resource table, the terminal device may directly determine that the third resource table is the target resource table and the resource in the target resource table is the first type of resource, regardless of which RNTI the RNTI used for scrambling the DCI is. In some implementations, the second implementation of Case 2 may be based on such a premise that before the terminal device receives the DCI, the terminal device receives the second configuration information sent by the network device, wherein the second configuration information is used for indicating that the second RNTI is not used, or the terminal device does not receive the second configuration information sent by the network device, that is, the second implementation of Case 2 may be the mode of determining the target resource table and the type of resource in the target resource table when the second RNTI is not used. To sum up, in the Case 2, a specific implementation process of determining the target resource for the first channel may be as shown inFIG.8, and specifically includes: S21, the terminal device receives the first configuration information sent by the network device, and determines a third resource table for the first RNTI and the second RNTI according to the first configuration information, and further may determine that the third resource table is a target resource table and at least one resource in the target resource table is a to-be-determined type of resource. Further, in S22, the terminal device receives the second configuration information of the network device, and determines whether the second RNTI may be used according to the second configuration information. If the second configuration information indicates that the second RNTI may be used, the flow proceeds to S23, otherwise, the flow proceeds to S24, in which the terminal device determines that the to-be-determined type of resource in the target resource table is the first type of resource. In S23, the terminal device determines which type of resource the to-be-determined type of resource in the target resource table is, according to the RNTI used by the network device to scramble the DCI. If the DCI is scrambled using the first RNTI, the flow proceeds to S25, in which the terminal device determines that the to-be-determined type of resource in the target resource table is the first type of resource, or if the DCI is scrambled using the second RNTI, the flow proceeds to S26, in which the terminal device determines that the to-be-determined type of resource in the target resource table is the second type of resource. Further, in S27, the terminal device determines the target resource for the first channel from the target resource table according to the indication information in the DCI. Hereinafter, the mode of determining the resource of the first channel will be described in detail with reference to specific implementations. It should be noted that following implementations are described by taking two kinds of RNTIs including the first RNTI and the second RNTI, two types of resources including the first type of resource and the second type of resource, and the first channel is PUSCH/PDSCH as an example, but implementations of the present application are not limited to this, and implementations of the present application may also include more RNTIs for indicating more types of resources. Implementation One: corresponding resource tables are configured for the first RNTI and the second RNTI respectively. Specifically, the first RNTI may correspond to a first resource table, and the second RNTI may correspond to a second resource table, wherein the first resource table and the second resource table are different in reference points of starting positions of the resources. For example, the reference point of the starting position of the resource in the first resource table is a starting position of a time slot, and the reference point of the starting position of the resource in the second resource table may be the starting symbol of CORESET including the DCI, or another position in the aforementioned implementations, which are not repeated here. As an example but not limitation, the first resource table corresponding to the first RNTI may be as shown in Table 1, and the second resource table corresponding to the second RNTI may be as shown in Table 2. Herein, the resources in the first resource table are all the first type of resources, that is, the starting symbols of the resources are calculated relative to the starting positions of the time slots, so the resources in the first resource table are more suitable for scheduling transmission of PDSCH/PUSCH with various delays, such as an eMBB service. The resources in the second resource table are all the second type of resources, that is, the starting symbols of resources are calculated relative to the starting symbols of CORESET where the DCI scheduling this resource is located, so the resources in the second resource table are more suitable for scheduling transmission of PDSCH/PUSCH with a low delay, such as a URLLC service. TABLE 1ResourceStartingLength (quantity ofnumberType of resourcesymbolsymbols)0.A first type (a startingSymbol 01symbol1symbol of resource is2symbols2relative to a starting4symbols3symbol of a time slot)Symbol 21symbol42symbols54symbols6Symbol 41symbol72symbols84symbols9Symbol 61symbol102symbols114symbols12Symbol 81symbol132symbols14Symbol 101symbol152symbols TABLE 2ResourceStartingLength (quantity ofnumberType of resourcesymbolsymbols)0A second type (a startingSymbol 01symbol1symbol of resource is2symbols2relative to a starting symbol3symbols3of CORESET where DCI4symbols4scheduling the resource isSymbol 11symbol5located)2symbols63symbols74symbols8Symbol 21symbol92symbols103symbols114symbols12Symbol 31symbol132symbols143symbols154symbols In some implementations, the terminal device may determine whether the second RNTI may be used according to the second configuration information, and may further determine which of the first resource table and the second resource table the target resource table is. For example, if the second configuration information indicates that the second RNTI may be used, in this case, the terminal device determines which RNTI is used for scrambling the DCI, and if the DCI is scrambled using the first RNTI, the terminal device determines the first resource table as the target resource table; or if the DCI is scrambled using the second RNTI, the terminal device may determine the second resource table as the target resource table. Or, if the second configuration information indicates that the second RNTI cannot be used, the terminal device may determine that the first resource table is the target resource table, regardless of whether the DCI is scrambled using the first RNTI or the second RNTI. Further, the terminal device determines the resource for PDSCH/PUSCH transmission from the target resource table according to the indication information in the DCI. For example, if the target resource table is the first resource table, and the indication information indicates a number 10, then according to Table 1, the terminal device may determine that the starting symbol of PDSCH/PUSCH is symbol 6 in the time slot, with a length of 2 symbols. Furthermore, if the target resource table is the second resource table, and the indication information indicates a number 5, then according to Table 2, the terminal device may determine that the starting symbol of PDSCH/PUSCH is the first symbol from the starting symbol of CORESET where the DCI is located, with a length of 2 symbols. Therefore, by configuring the terminal device with two resource tables, the network device may flexibly configure the resource for PUSCH/PDSCH according to the types of services to be transmitted through the RNTI, so that the transmission requirements of different types of services can be met. For example, the resource in the first resource table may be configured for the eMBB service, so that diversity of delay requirements of the eMBB service can be met, and configuring the resources in the second resource table for the URLLC service can reduce transmission delay of the URLLC service. At the same time, by allocating different resources to different types of services, the resource allocation of different types of services may be optimized, which is conducive to improving resource utilization rate of the communication system. Implementation Two: corresponding resource tables for the first RNTI and the second RNTI are configured respectively. Specifically, the first RNTI may correspond to the first resource table, and the second RNTI may correspond to the second resource table, which is different from the first implementation in that a part of resources in the second resource table are the first type of resources and a part of resources are the second type of resources. Therefore, the resources in the first resource table configured for the first RNTI are more suitable for scheduling PDSCH/PUSCH transmission with more various delays, such as the eMBB service. A part of the resources in the second resource table configured for the second RNTI are more suitable for scheduling PDSCH/PUSCH transmission with more various delays, such as the eMBB service, and another part of the resources are more suitable for PDSCH/PUSCH transmission with low delay, such as the URLLC service. As an example, but not limitation, the first resource table may be as shown in Table 3, and the second resource table may be as shown in Table 4. Which resources in the second resource table are the second type of resources may be determined according to the configuration information of the network device, such as the first configuration information, or may be determined according to a preset condition. For example, in Table 4, the resources with resource numbers from 8 to 15 may be configured as the second type of resources according to the first configuration information, or the resources with the starting symbol numbers less than 2 may be configured as the second type of resources according to the preset condition. TABLE 3ResourceStartingLength (quantity ofnumberType of resourcesymbolsymbols)0A first type (a startingSymbol 01symbol1symbol of resource is2symbols2relative to a starting4symbols3symbol of a time slot)Symbol 21symbol42symbols54symbols6Symbol 41symbol72symbols84symbols9Symbol 61symbol102symbols114symbols12Symbol 81symbol132symbols14Symbol 101symbol152symbols TABLE 4ResourceStartingLength (quantity ofnumberType of resourcesymbolsymbols)0A first type (a startingSymbol 22symbols1symbol of resource is4symbols2relative to a startingSymbol 42symbols3symbol of a time slot)4symbols4Symbol 72symbols54symbols6Symbol 102symbols74symbols8A second type (a startingSymbol 01symbol9symbol of resource is2symbols10relative to a starting symbol3symbols11of CORESET where DCI4symbols12scheduling the resource isSymbol 11symbol13located)2symbols143symbols154symbols The mode of determining the resources for PDSCH/PUSCH transmission according to Table 3 and Table 4 is similar to the implementation One, and is not repeated here. Implementation Three: a same resource table for the first RNTI and the second RNTI is configured. For example, as shown in Table 5, the resource table includes at least one resource of to-be-determined type, which resources in the resource table being resources of to-be-determined type is determined according to the configuration information of the network device, such as the first configuration information, or according to a preset condition. For example, the first configuration information may configure the resources with resource numbers from 0 to 7 as resources of to-be-determined type, or the resources with the resource numbers less than a specific value, such as 4, may be determined as the resources of to-be-determined type according to the preset condition. TABLE 5ResourceStartingLength (quantity ofnumberType of resourcesymbolsymbols)0To-be-determined typeSymbol 01symbol12symbols2Symbol 11symbol32symbols4Symbol 21symbol52symbols6Symbol 31symbol72symbols8A first type (a startingSymbol 42symbols9symbol of resource is4symbols10relative to a startingSymbol 62symbols11symbol of a time slot)4symbols12Symbol 82symbols134symbols14Symbol 102symbols154symbols Further, the terminal device may determine the resource type of the to-be-determined type of resource in combination with the second configuration information. For example, if the second configuration information indicates that the second RNTI cannot be used, the terminal device may determine that the to-be-determined type of resource is the first type of resource, or if the second configuration information indicates that the second RNTI may be used, in this case, the terminal device may also further combine the RNTI for scrambling the DCI to determine which type of resource the to-be-determined type of resource is. For example, if the DCI is scrambled by using the first RNTI, the terminal device may determine that the to-be-determined type of resource is the first type of resource, or if the DCI is scrambled by using the second RNTI, the terminal device may determine that the to-be-determined type of resource is the second type of resource. Further, the terminal device may determine the target resource for PDSCH/PUSCH transmission in the resource table in combination with the indication information in the DCI. For example, if the to-be-determined type of resource is the second type of resource, the indication information in the DCI indicates the resource number 6, then the terminal device may determine that the starting symbol of the resource, with a length of 1 symbol, for PDSCH/PUSCH transmission is a third symbol relative to the starting symbol of CORESET where the DCI is located, or if the to-be-determined type of resource is the first type of resource and at least information in the DCI indicates the resource number 3, the terminal device may determine that the starting symbol of the resource, with a length of 2 symbols, for PDSCH/PUSCH transmission is the first symbol relative to the starting position of the time slot. The method for wireless communication according to an implementation of the present application is described in detail from a perspective of the terminal device above with reference toFIGS.4to8, and a method for wireless communication according to another implementation of the present application is described in detail from a perspective of the network device below with reference toFIG.9. It should be understood that the description of the network device side corresponds to the description of the terminal device side with each other, and the above description may be referred to for similar descriptions, which is not repeated here again to avoid repetition. FIG.9is a schematic flowchart of a method300for wireless communication according to another implementation of the present application, and the method300may be performed by the terminal device in the communication system shown inFIG.1. As shown inFIG.9, the method300includes following contents. In S310, a network device sends Downlink Control Information (DCI) scrambled by using a target Radio Network Temporary Identity (RNTI) to a terminal device, wherein the target RNTI is used for the terminal device to determine a resource for a first channel in at least one resource table, the at least one resource table contains at least two types of resources, and reference points of starting positions of the at least two types of resources are different. Optionally, in some implementations, the method300further includes: the network device sends first configuration information to the terminal device, wherein the first configuration information includes the at least one resource table for determining the resource of the first channel. Optionally, in some implementations, the at least two types of resources include a first type of resource and a second type of resource, wherein the reference point of the starting position of the first type of resource is a starting position of a time slot, and the reference point of the starting position of the second type of resource is the DCI or a time domain position of a first resource range including the DCI. Optionally, in some implementations, the time domain position of the first resource range including the DCI is a starting symbol or an ending symbol of a Control Resource Set (CORESET) or a search space including the DCI. Optionally, in some implementations, the at least one resource table includes a first resource table and a second resource table, wherein the first resource table corresponds to a first RNTI, the resource in the first resource table is a first type of resource, the second resource table corresponds to a second RNTI, and at least one resource in the second resource table is a second type of resource. Optionally, in some implementations, the first RNTI is a Cell Radio Network Temporary Identity (C-RNTI), and the second RNTI is another RNTI except the C-RNTI. Optionally, in some implementations, the at least one resource table includes a third resource table, wherein at least one resource in the third resource table is a to-be-determined type of resource. Optionally, in some implementations, before the network device sends the Downlink Control Information (DCI) scrambled by using the target Radio Network Temporary Identity (RNTI) to the terminal device, the method further includes: the network device sends second configuration information to the terminal device, wherein the second configuration information is used for indicating whether the second RNTI may be used. Optionally, in some implementations, the first channel is a Physical Downlink Shared Signal (PDSCH) or a Physical Uplink Shared Channel (PUSCH). Optionally, in some implementations, the resource table at least includes following parameters: a starting symbol, a length and a mapping type of the first channel. Method implementations of the present application are described in detail above with reference toFIGS.4to9, apparatus implementations of the present application are described in detail below with reference toFIGS.10to14. It should be understood that the apparatus implementations correspond to the method implementations with each other, and description of the method implementations may be referred to for similar description of the apparatus implementations. FIG.10shows a schematic block diagram of a terminal device400according to an implementation of the present application. As shown inFIG.10, the terminal device400includes: a communicating module410, configured to receive Downlink Control Information (DCI) sent by a network device; and a determining module420, configured to determine a resource for a first channel in at least one resource table according to a Radio Network Temporary Identifier (RNTI) for scrambling the DCI, wherein the at least one resource table contains at least two types of resources, and reference points of starting positions of the at least two types of resources are different. Optionally, in some implementations, the communicating module410is further configured to: receive first configuration information sent by the network device, wherein the first configuration information includes the at least one resource table for determining the resource of the first channel. Optionally, in some implementations, the at least two types of resources include a first type of resource and a second type of resource, wherein a reference point of a starting position of the first type of resource is a starting position of a time slot, and a reference point of a starting position of the second type of resource is the DCI or a time domain position of a first resource range including the DCI. Optionally, in some implementations, the time domain position of the first resource range including the DCI is a starting symbol or an ending symbol of a Control Resource Set (CORESET) or a search space including the DCI. Optionally, in some implementations, the determining module420is specifically configured to: according to the RNTI for scrambling the DCI, determine a target resource table in the at least one resource table and a type of a resource in the target resource table; and according to the indication information in the DCI, determine the resource for the first channel in the target resource table. Optionally, in some implementations, the at least one resource table includes a first resource table and a second resource table, wherein the first resource table corresponds to a first RNTI, the resource in the first resource table is a first type of resource, the second resource table corresponds to a second RNTI, and at least one resource in the second resource table is a second type of resource. Optionally, in some implementations, the first RNTI is a Cell Radio Network Temporary identity (C-RNTI), and the second RNTI is another RNTI except the C-RNTI. Optionally, in some implementations, the determining module420is further configured to: if the RNTI for scrambling the DCI is the first RNTI, determine that the first resource table is the target resource table and the resource in the first resource table is the first type of resource; or, if the RNTI for scrambling the DCI is the second RNTI, determine that the second resource table is the target resource table and at least one resource in the second resource table is a candidate second type of resource. Optionally, in some implementations, the determining module420is further configured to: determine that the first resource table is the target resource table. Optionally, in some implementations, the at least one resource table includes a third resource table, wherein at least one resource in the third resource table is a to-be-determined type of resource. Optionally, in some implementations, the determining module420is further configured to determine that the third resource table is the target resource table; if the RNTI for scrambling the DCI is the first RNTI, determine that the to-be-determined type of resource in the target resource table is the first type of resource; or if the RNTI for scrambling the DCI is the second RNTI, determine that the to-be-determined type of resource in the target resource table is the second type of resource. Optionally, in some implementations, the determining module420is further configured to: determine that the third resource table is the target resource table; and determine that the to-be-determined type of resource in the target resource table is the first type of resource. Optionally, in some implementations, the communicating module is further configured to: receive second configuration information sent by the network device before receiving the Downlink Control Information (DCI) sent by the network device, wherein the second configuration information is used for indicating that the second RNTI may be used. Optionally, in some implementations, the communicating module is further configured to: receive the second configuration information sent by the network device before receiving the Downlink Control Information (DCI) sent by the network device, wherein the second configuration information is used for indicating that the second RNTI is not used; or before receiving the Downlink Control Information (DCI) sent by the network device, the second configuration information sent by the network device is not received. Optionally, in some implementations, the determining module420is further configured to: determine the candidate second type of resource as the second type of resource; or when a time-slot-level offset of the DCI is zero, determine the candidate second type of resource as the second type of resource. Optionally, in some implementations, the determining module420is further configured to: determine the candidate second type of resource in the target resource table according to configuration of the network device or a preset condition. Optionally, in some implementations, the preset condition is preset on the terminal device, and the preset condition is to determine a resource of which a starting symbol is less than a specific value as the candidate second type of resource. Optionally, in some implementations, it is characterized that the first channel is a Physical Downlink Shared Signal (PDSCH) or a Physical Uplink Shared Channel (PUSCH). Optionally, in some implementations, the resource table at least includes following parameters: a starting symbol of the first channel and a length. Optionally, in some implementations, the resource table further includes a mapping type of the first channel. Specifically, the terminal device400may correspond to (e.g., may be configured in or be itself) the terminal device described in the above method200, and various modules or units in the terminal device400are respectively configured to perform various actions or processing processes performed by the terminal device in the above method200. Herein, in order to avoid redundancy, detailed description thereof is omitted. FIG.11is a schematic block diagram of a network device according to an implementation of the present application. A network device500inFIG.11includes: a communicating module510, configured to send Downlink Control Information (DCI) scrambled by using a target Radio Network Temporary Identity (RNTI) to a terminal device, wherein the target RNTI is used for the terminal device to determine a resource for the first channel in at least one resource table, the at least one resource table contains at least two types of resources, and reference points of starting positions of the at least two types of resources are different. Optionally, in some implementations, the communicating module510is further configured to: send first configuration information to the terminal device, wherein the first configuration information includes the at least one resource table for determining the resource of the first channel. Optionally, in some implementations, the type of resource is a first type of resource or a second type of resource, wherein a reference point of a starting position of the first type of resource is a starting position of a time slot, and a reference point of a starting position of the second type of resource is the DCI or a time domain position of a first resource range including the DCI. Optionally, in some implementations, the time domain position of the first resource range including the DCI is a starting symbol or an ending symbol of a Control Resource Set (CORESET) or a search space including the DCI. Optionally, in some implementations, the at least one resource table includes a first resource table and a second resource table, wherein the first resource table corresponds to a first RNTI, the resource in the first resource table is a first type of resource, the second resource table corresponds to a second RNTI, and at least one resource in the second resource table is a second type of resource. Optionally, in some implementations, the first RNTI is a Cell Radio Network Temporary Identity (C-RNTI), and the second RNTI is another RNTI except the C-RNTI. Optionally, in some implementations, the at least one resource table includes a third resource table, wherein at least one resource in the third resource table is a to-be-determined type of resource. Optionally, in some implementations, the communicating module510is further configured to: send second configuration information to the terminal device, wherein the second configuration information is used for indicating whether the second RNTI may be used. Optionally, in some implementations, the first channel is a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH). Optionally, in some implementations, the resource table at least includes following parameters: a starting symbol, a length and a mapping type of the first channel. Specifically, the network device500may correspond to (e.g., may be configured in or be itself) the network device described in the above method300, and various modules or units in the network device500are respectively configured to perform various actions or processing processes performed by the network device in the above method300. Herein, in order to avoid redundancy, detailed description thereof is omitted. FIG.12is a schematic diagram of structure of a communication device600according to an implementation of the present application. The communication device600shown inFIG.12includes a processor610. The processor610may call and run a computer program from a memory to implement the method in the implementation of the present application. Optionally, as shown inFIG.12, the communication device600may further include a memory620. Herein, the processor610may call and run a computer program from the memory620to implement the method in the implementation of the present application. Herein, the memory620may be a separate device independent of the processor610or may be integrated in the processor610. Optionally, as shown inFIG.12, the communication device600may further include a transceiver630, and the processor610may control the transceiver630to communicate with another device. Specifically, information or data may be sent to another device or information or data sent by another device is received. Herein, the transceiver630may include a transmitter and a receiver. The transceiver630may also further include antennas, and a quantity of antennas may be one or more. Optionally, the communication device600may be specifically a network device of an implementation of the present application, and the communication device600may implement the corresponding processes implemented by the network device in various methods of the implementations of the present application, which is not repeated here again for brevity. Optionally, the communication device600may be specifically a mobile terminal/terminal device of an implementation of the present application, and the communication device600may implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the implementations of the present application, which is not repeated here again for brevity. FIG.13is a schematic diagram of structure of a chip of an implementation of the present application. A chip700shown inFIG.13includes a processor710. The processor710may call and run a computer program from a memory to implement the method in the implementation of the present application. Optionally, as shown inFIG.13, the chip700may further include a memory720. Herein, the processor710may call and run a computer program from the memory720to implement the method in the implementation of the present application. Herein, the memory720may be a separate device independent of the processor710or may be integrated in the processor710. Optionally, the chip700may further include an input interface730. Herein, the processor710may control the input interface730to communicate with another device or chip. Specifically, information or data sent by another device or chip may be acquired. Optionally, the chip700may further include an output interface740. Herein, the processor710may control the output interface740to communicate with another device or chip. Specifically, information or data may be output to another device or chip. Optionally, the chip may be applied in a network device of the implementation of the present application, and the chip may implement the corresponding processes implemented by the network device in various methods of the implementations of the present application, which is not repeated here again for brevity. Optionally, the chip may be applied in a mobile terminal/terminal device of the implementation of the present application, and the chip may implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the implementations of the present application, which is not repeated here again for brevity. It should be understood that the chip mentioned in the implementation of the present application may also be referred to as a system-level chip, a system chip, a chip system or a system chip-on-chip, etc. FIG.14is a schematic block diagram of a communication system900according to an implementation of the present application. As shown inFIG.14, the communication system900includes a terminal device910and a network device920. Herein, the terminal device910may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device920may be configured to implement the corresponding functions implemented by the network device in the above method, which is not repeated here again for brevity. It should be understood that, the processor in the implementation of the present application may be an integrated circuit chip having a signal processing capability. In an implementation process, the acts of the above method implementations may be completed by an integrated logic circuit of hardware in the processor or instructions in a form of software. The above processor may be a general purpose processor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or another programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component. Methods, acts and logical block diagrams disclosed in the implementations of the present application may be implemented or performed. The general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The acts of the method disclosed with reference to the implementation of the present application may be directly embodied as executed and completed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in a decoding processor. The software modules may be located in a storage medium commonly used in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads information in the memory and completes the acts of the above method in combination with its hardware. It may be understood that, the memory in the implementation of the present application may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. Herein, the non-volatile memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory may be a Random Access Memory (RAM), which is used as an external cache. Through exemplary but not limitative description, many forms of RAMs may be used, for example, a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM), and a direct internal memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory in the systems and the methods described in this specification are aimed at including but being not limited to these and any memory of another proper type. It should be understood that, the above memory is an example for illustration and should not be construed as limiting. For example, the memory in the implementations of the present application may also be a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM), a Direct Rambus RAM (DR RAM), or the like. That is, memories in the implementations of the present application are aimed at including, but not limited to, these and any memory of another proper type. An implementation of the present application further provides a computer readable storage medium, configured to store a computer program. Optionally, the computer readable storage medium may be applied in a network device of an implementation of the present application, and the computer program causes a computer to perform the corresponding processes implemented by the network device in various methods of implementations of the present application, which is not repeated here again for brevity. Optionally, the computer readable storage medium may be applied in a mobile terminal/terminal device of an implementation of the present application, and the computer program causes the computer to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods of implementations of the present application, which is not repeated here again for brevity. An implementation of the present application also provides a computer program product, including computer program instructions. Optionally, the computer program product may be applied in a network device of an implementation of the present application, and the computer program instructions cause a computer to perform the corresponding processes implemented by the network device in various methods of implementations of the present application, which is not repeated here again for brevity. Optionally, the computer program product may be applied in a mobile terminal/terminal device of an implementation of the present application, and the computer program instructions cause the computer to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods of implementations of the present application, which is not repeated here again for brevity. An implementation of the present application also provides a computer program. Optionally, the computer program may be applied in a network device of an implementation of the present application. When the computer program is run on the computer, the computer is caused to perform the corresponding processes implemented by the network device in various methods of implementations of the present application, which is not repeated here again for brevity. Optionally, the computer program may be applied in a mobile terminal/terminal device of an implementation of the present application. When the computer program is run on the computer, the computer is caused to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods of implementations of the present application, which is not repeated here again for brevity. Those of ordinary skill in the art may recognize that the exemplary elements and algorithm acts described in combination with the implementations disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on a particular application and a design constraint condition of a technical solution. Skilled artisans may use different methods to implement the described functions in respect to each particular application, but such implementation should not be considered to be beyond the scope of the present application. Those skilled in the art may clearly learn that for convenience and conciseness of description, the specific working processes of the systems, apparatuses and units described above may refer to the corresponding processes in the aforementioned method implementations and is not repeated here again. In several implementations provided by the present application, it should be understood that the disclosed systems, apparatuses and methods may be implemented in another mode. For example, the apparatus implementations described above are only illustrative, for example, the division of the units is only a logical function division, and there may be another division mode in an actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. On the other hand, mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, apparatuses or units, or may be in electrical, mechanical or another form. The unit described as a separate component may or may not be physically separated, and the component shown as a unit may or may not be a physical unit, i.e., it may be located in one place or may be distributed over multiple network units. Part or all of the units therein may be selected according to an actual requirement to achieve a purpose of a solution of the implementation. In addition, functional units in various implementations of the present application may be integrated in one processing unit, or various units may be physically present separately, or two or more units may be integrated in one unit. The functions may be stored in a computer readable storage medium if realized in a form of software functional units and sold or used as a separate product. Based on this understanding, the technical solution of the present application, in essence, or the part contributing to the prior art, or the part of the technical solution, may be embodied in a form of a software product. The computer software product is stored in a storage medium, including a number of instructions for causing a computer device (which may be a personal computer, a server, or a network device, or the like) to perform all or part of the acts of the methods described in various implementations of the present application. And the aforementioned storage medium includes: various kinds of media that may store program codes, such as a USB flash drive, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disc, etc. What are described above are merely specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any variation or substitution that may be easily conceived by a person skilled in the art within the technical scope disclosed by the present application shall be included within the protection scope of the present application. Therefore, the protection scope of the present application shall be determined by the protection scope of the claims. | 76,390 |
Subsets and Splits