Solar Floodlights and the Smart Factory: Integrating VP TITAN I with IoT for Predictive Maintenance and Energy Management

Created on：2026-05-09 14:28

1. Introduction: When a Floodlight Becomes a Data Node

Industrial lighting has historically been a binary system: on or off. A 500-watt metal-halide floodlight above a loading dock either blazed at full throttle or sat cold and dark. It consumed energy, generated heat, and required periodic bulb changes, but it contributed nothing to the factory’s understanding of itself. It was a cost centre, not an asset.

The emergence of LED technology introduced dimmability. The addition of solar power removed the physical tether to the grid. But the true transformation—the moment a floodlight evolves from a passive illuminator into an active participant in the smart factory—occurs when it becomes an Internet of Things (IoT) endpoint. The VAST PROSPERITY (VP) SOLAR FLOOD LIGHT TITAN I stands at precisely this inflection point. Beneath its die-cast aluminum shell, behind its SMD5054 LEDs and its game-changing 150°×90° Teijin PC lens, hums a microprocessor that measures, records, and communicates. It knows how much sunlight its panel captured yesterday. It knows the internal temperature of its battery at 3:00 a.m. It knows that a forklift passed at 11:42 p.m. and that the light dutifully ramped to full brightness for 47 seconds.

This article is about connecting that intelligence to the factory’s digital brain. It explores how a VP TITAN I solar floodlight, when integrated into an IoT fabric, can deliver predictive maintenance that prevents unexpected darkness, orchestrate energy management that shrinks carbon footprints, and feed data into the Manufacturing Execution System (MES) and Enterprise Resource Planning (ERP) layers that govern Industry 4.0. We will move beyond the billboard origin story and into the realm of SCADA dashboards, edge analytics, and digital twins. The goal is to provide facility managers, automation engineers, and sustainability officers with a comprehensive blueprint for deploying VP solar floodlights not just as lights, but as sentinels of the intelligent industrial enterprise.

2. The VP TITAN I Hardware Platform: A Quick Review of the IoT-Ready Foundation

Before we dive into network topologies and predictive algorithms, it is essential to revisit the TITAN I's internal architecture—not as a black-box luminaire, but as a connected device. The following features, already introduced in our earlier article on industrial area lighting, are the physical enablers of IoT integration.

2.1 High-Efficacy LED Engine with Fine-Grained Dimming
The VP TITAN I employs an upgrade version SMD5054 chip that delivers 160 lumens per watt. Crucially, its LED driver supports smooth, flicker-free dimming from 0% to 100% via a pulse-width modulation (PWM) signal generated by the onboard microcontroller. This dimming is not merely a two-step toggle between “dim” and “bright”; it can follow an arbitrary curve, responding in real time to commands from the radar sensor, a schedule stored in non-volatile memory, or an external command arriving over a wireless link. This granularity is essential for energy management strategies that must balance illumination quality against kilowatt-hour budgets.

2.2 Radar Sensor with Motion Signatures
The integrated 5.8 GHz microwave radar module is the TITAN I's primary environmental sensor. It detects Doppler shifts caused by moving objects, but its digital signal processor also extracts rudimentary signatures: the speed of the target, its approximate size (based on reflected signal amplitude), and its dwell time within the detection zone. While not a full imaging radar, this data stream—exported as a simple serial message—enables the smart factory to distinguish between a fast-moving truck and a slowly walking human, count vehicle movements on a haul road, or log how many times a security patrol passed a checkpoint during the night. This transforms the floodlight into a non-intrusive presence sensor, a capability that traditional passive infrared (PIR) sensors cannot match due to their limited range and susceptibility to thermal noise.

2.3 Onboard Telemetry Sensors
Beyond the radar, every VP TITAN I includes a suite of internal sensors that monitor its own health:

  • Battery voltage (V_bat) and charging current (I_chg) sampled every minute, allowing calculation of state-of-charge (SoC) and energy harvested.

  • Panel voltage (V_pv) and current (I_pv), enabling real-time solar irradiance estimation.

  • Internal temperature of the battery compartment and the LED heatsink, critical for predicting thermal degradation.

  • Accumulated runtime counters for the LED array and the radar module, tracked in hours.

All these parameters are accessible through a UART or I²C interface on the controller board. In a stand-alone TITAN I, they are only used locally to implement the 365-day radar mode logic. But when a communication module is added, they become the raw material for a predictive maintenance engine.

2.4 Communication Module Options
The VAST PROSPERITY product ecosystem already includes the SOLAR SMART STREET LIGHT HD-AI900, which integrates a 4G/Wi-Fi modem and an HD camera, all managed via the EseeCloud platform. The same communication architecture can be integrated into a TITAN I floodlight—either as an embedded daughterboard inside the luminaire housing, or via a small external gateway box connected through a weatherproof M12 connector. The communication stack supports:

  • 4G LTE Cat-1/Cat-M1 for direct cloud connectivity without relying on the factory’s Wi-Fi network.

  • Wi-Fi 802.11 b/g/n for integration into the local industrial LAN.

  • 433 MHz / LoRaWAN for low-power, long-range mesh networking where cellular coverage is patchy or where data payloads are minimal.

This multi-protocol flexibility is key: a TITAN I monitoring a remote perimeter fence may use LoRaWAN to reach a gateway at the control room, while a unit on the main loading dock connects directly to the factory’s Wi-Fi and streams high-resolution telemetry to the MES.

3. IoT Architecture for Industrial Solar Lighting: From Edge to Cloud

Integrating hundreds of VP TITAN I floodlights into a smart factory requires a thoughtful network architecture that balances bandwidth, latency, security, and cost. The following layered model has been validated in real-world deployments.

3.1 Layer 1: The Luminaire as an Edge Device
At the bottom of the stack sits the TITAN I itself, equipped with a microcontroller unit (MCU) running a lightweight real-time operating system (RTOS). The MCU aggregates local sensor data, executes the radar dimming logic, and implements a constrained application protocol (CoAP) or Message Queuing Telemetry Transport (MQTT) client over TCP/IP. A typical telemetry payload—battery voltage, SoC, internal temperature, radar event count for the last 5 minutes, and a heartbeat flag—is under 200 bytes. This payload is transmitted every 5 to 15 minutes during normal operation, with the ability to burst up to once per second in diagnostic mode.

Edge processing is performed locally to reduce data transmission. For example, the MCU calculates a rolling average of battery state-of-charge over the past three days and compares it against a baseline. If the deviation exceeds a threshold, it attaches a “warning” flag to the next telemetry uplink. This edge-based anomaly detection prevents network congestion and allows the light to operate autonomously even if connectivity is interrupted.

3.2 Layer 2: The Gateway or Direct-to-Cloud Link
For TITAN I units equipped with Wi-Fi or 4G, the MCU communicates directly with the cloud platform (e.g., EseeCloud or a custom MQTT broker). For LoRaWAN deployments, a gateway device located at a central point within the industrial site—often co-located on an existing lighting pole or the rooftop of a switchgear building—receives transmissions from up to 1,000 luminaires and forwards them to the cloud over Ethernet or cellular backhaul. The gateway also handles downlink commands: pushing a new dimming schedule, locking out a light for maintenance, or requesting an immediate full-brightness override during an emergency.

3.3 Layer 3: The Cloud Platform and Data Lake
All telemetry converges on a cloud-based IoT platform. While VAST PROSPERITY provides the EseeCloud operating platform for its smart street lights, industrial customers often prefer to integrate with their existing platforms—Microsoft Azure IoT Hub, AWS IoT Core, Siemens MindSphere, or a private OPC-UA server. The VP telemetry format is designed to be easily mapped to these platforms using standard JSON schemas. The cloud platform ingests the data, timestampes it, applies validation rules, and routes it to:

  • A time-series database (e.g., InfluxDB, TimescaleDB) for historical trending and analytics.

  • An alarm engine that triggers notifications (SMS, email, Teams/Slack) when critical thresholds are breached.

  • A dashboard application (Grafana, Power BI, or a custom web UI) that provides facility managers with real-time visibility into every light’s status, energy generation, and motion activity.

3.4 Layer 4: Integration with Factory Systems
This is where the VP TITAN I truly becomes part of the smart factory. Via REST APIs or OPC-UA connectors, the cloud platform exposes lighting data to:

  • The Building Management System (BMS) or Energy Management System (EMS), allowing solar lighting energy production and consumption to be folded into the plant-wide energy balance.

  • The Manufacturing Execution System (MES) and Warehouse Management System (WMS), using radar-detected movement in loading docks to automatically log truck arrival and departure events, or to verify that a designated area is clear before a robotic shuttle operates.

  • The Computerised Maintenance Management System (CMMS), which automatically creates work orders when a TITAN I reports a battery nearing its end-of-life or a panel whose daily energy harvest has fallen below 70% of the seasonal norm—indicating soiling or damage.

The net result is a closed loop between illumination, operations, and maintenance. The factory no longer just consumes light; it is informed by it.

4. Predictive Maintenance: Keeping the Lights On Before They Fail

Unplanned lighting failure in an industrial setting is not an inconvenience; it is a safety, security, and operational risk. A single dark floodlight above a chemical storage area can invalidate a risk assessment, halt night-shift operations, and expose the company to regulatory penalties. Traditional maintenance models—reactive (fix it when it breaks) or preventive (replace bulbs on a calendar schedule)—are either too risky or too wasteful. Predictive maintenance (PdM), enabled by continuous telemetry from VP TITAN I units, offers a superior third way.

4.1 The Data Foundation for PdM
The TITAN I generates several time-series streams that are highly prognostic of imminent failure:

  1. Battery State-of-Health (SoH): Lithium iron phosphate (LiFePO₄) batteries degrade gracefully. Their capacity fades linearly over thousands of cycles. By tracking the daily depth-of-discharge (DoD) and the corresponding minimum voltage reached each night, the cloud platform can calculate the battery’s effective capacity using a Kalman filter or an equivalent circuit model. When estimated capacity drops below 70% of the original rating (e.g., from 90 Ah to 63 Ah), a maintenance flag is raised. This provides a lead time of several months before the light fails to last a full winter night.

  2. Solar Panel Soiling and Degradation: The daily energy harvest (in watt-hours) for a given date should correlate strongly with the theoretical clear-sky insolation. By comparing the TITAN I’s actual daily harvest against a site-specific model (derived from the first 30 days of “clean” operation), the platform can detect progressive soiling. If a panel’s harvest ratio (actual / modelled) drops below 0.8, a cleaning alert is issued. If the ratio remains low after a cleaning event, it indicates a permanent defect—micro-cracks, delamination, or partial shading by new construction—and triggers a replacement order.

  3. LED Lumen Depreciation: The TITAN I’s MCU monitors the LED driver’s forward voltage and current. While it cannot directly measure lumen output without an optical sensor, a rise in driver temperature for a given power level, or an increase in the required PWM duty cycle to maintain target current, can indicate LED chip degradation. By tracking the internal heatsink temperature and correlating it with ambient conditions, the platform can compute an estimated L70 or L80 remaining life, allowing the facility to plan a relamping campaign well before the illumination falls below the required lux level on the ground.

  4. Radar Sensor Drift: The radar module’s detection range can be affected by component aging, moisture ingress, or physical obstruction (e.g., a bird’s nest). The platform monitors the daily count of radar triggers. If a light that historically logged 200 triggers per night suddenly drops to near-zero for three consecutive nights, while its neighbours continue to register normal activity, it is likely a sensor fault rather than a genuine traffic reduction. An automated diagnostic command can then be sent to perform a self-test.

4.2 From Data to Work Order: The CMMS Integration
All these predictive indicators flow into a rules engine that publishes maintenance recommendations to the factory’s CMMS (SAP PM, IBM Maximo, or a simpler open-source solution). Each TITAN I is inventoried as an asset with a unique ID, installation date, and location. The recommendation includes:

  • Priority (critical for lights on egress paths; routine for storage yard corners).

  • Recommended action (clean panel, replace battery, check radar alignment, etc.).

  • Time window (e.g., “within 4 weeks” for a degrading battery, “at next scheduled shutdown” for a dusty panel).

  • Required parts and technician skill level.

A maintenance planner can then batch these actions geographically, dispatching a single technician to service multiple lights in the same zone during a single shift. This reduces windshield time and labour costs by an estimated 40% compared to reactive maintenance, while simultaneously improving lighting reliability from “three-nines” (99.9%) to “four-nines” (99.99%) availability.

5. Energy Management: From Passive Consumer to Active Participant

Industrial facilities are under unprecedented pressure to decarbonise. The EU’s Energy Efficiency Directive, the UK’s Streamlined Energy and Carbon Reporting (SECR), and various carbon border adjustment mechanisms (CBAM) all require granular, auditable energy data. Solar lighting, if managed correctly, can be a significant contributor to both energy savings and renewable generation reporting.

5.1 Dynamic Dimming Strategies Guided by Production Schedules
The TITAN I’s radar mode already slashes energy consumption by dimming to 20% when no motion is detected. But in a smart factory, the dimming logic can be made even more intelligent by linking it to the production schedule. At 8:00 p.m., when the MES indicates that the second shift is active, all loading dock floodlights can be remotely commanded to hold a minimum of 50% brightness, overriding the radar’s 20% idle setting, to provide a well-lit backdrop for worker safety. At 11:00 p.m., when the MES shows the shift has ended and only automatic guided vehicles (AGVs) remain active, the lights revert to radar-only mode. At 5:00 a.m., when the morning cleaning crew arrives, a scheduled mid-level brightness is restored.

This schedule can be stored in the TITAN I’s firmware as a weekly timetable, updated over the air, ensuring that even if the network goes down, the light still follows the last known plan. The energy savings compound: a 200 W fixture that burns at 50% for 3 hours, then 20% for 5 hours with periodic full-brightness bursts, can consume as little as 0.9 kWh per night—a 62% reduction compared to constant full brightness. For a site with 500 lights, that is a daily saving of over 1,500 kWh, enough to power 50 average European homes.

5.2 Solar Generation Integration into Plant-Wide Energy Budgets
Each VP TITAN I is not only a consumer of energy but also a generator. Its monocrystalline panel produces green electricity that is consumed behind-the-meter. While this energy never touches the factory’s AC bus, it directly offsets what would otherwise be drawn from the grid for lighting. The cloud platform tallies the total watt-hours harvested by all TITAN I units each day and exports a daily “Solar Lighting Generation Report” to the factory’s EMS. This report can be used to:

  • Claim Scope 2 emission reductions in the corporate sustainability report.

  • Verify the performance ratio of the solar assets, triggering panel cleaning or vegetation trimming if the ratio falls below a contractual guarantee.

  • Provide data for green bond or sustainability-linked loan reporting.

In some jurisdictions, the virtual energy generated can even be certified as renewable energy credits (RECs), provided the monitoring system meets the local regulatory standard for accuracy. VP’s telemetry, with its current and voltage sampling every minute, typically meets the requirements for such certification.

5.3 Peak Shaving and Battery as Emergency Reserve
The LiFePO₄ battery inside a TITAN I is primarily sized for overnight lighting. However, its stored energy—typically 300 to 1,500 watt-hours—can be viewed as a distributed energy resource (DER). In a future scenario where VP lights are equipped with bidirectional DC-DC converters and a DC microgrid connection, a cluster of 100 lights could collectively provide a 50 kWh battery bank. During a grid peak-demand event, the factory’s energy management system could command the lights to temporarily switch to battery-only (even during the day), shedding the equivalent grid load of their panel production to reduce demand charges. The lights would then recharge from solar once the peak window passes. While this requires additional hardware, the VP TITAN I’s power electronics architecture—centred on a 5 V fast-charge MPPT converter—could be adapted for such vehicle-to-grid (V2G)-like functionality at the lighting scale.

6. Security, Data Integrity, and Edge Autonomy

Bringing hundreds of lighting nodes onto a factory network raises legitimate cybersecurity concerns. A compromised floodlight could be a beachhead for an attack on the Operational Technology (OT) environment. VAST PROSPERITY addresses these concerns through a multi-layered approach.

6.1 Secure Boot and Firmware Signing
The TITAN I’s MCU employs a secure boot process that cryptographically verifies the firmware signature before execution. Over-the-air (OTA) updates are signed with a private key held by VP’s engineering team, and the luminaire will reject any unsigned firmware image. This prevents malicious actors from injecting code that could, for example, disable all perimeter lights before an intrusion.

6.2 Encrypted Communications
All data in transit—whether over MQTT, CoAP, or HTTPS—is encrypted using TLS 1.3. The EseeCloud platform, or a private MQTT broker, requires X.509 certificate-based mutual authentication, ensuring that only legitimate VP devices can publish data and only authorised clients can subscribe to control topics. For LoRaWAN, the standard’s built-in AES-128 encryption at the network and application layers is used.

6.3 Network Segmentation
Industrial best practice dictates that IoT lighting devices reside on a dedicated Virtual Local Area Network (VLAN) or a separate physical network segment, firewalled from the process control network. The gateway that bridges the lighting network to the cloud is placed in a demilitarised zone (DMZ). Inbound connections to the lights are prohibited; all communication is initiated by the luminaire outbound to the broker, effectively making it invisible to external scans.

6.4 Edge Autonomy as a Safety Mechanism
A critical design principle of the VP TITAN I is that it must function as a safe and effective light even if all network connectivity is severed. The 365-day radar mode logic, the battery protection circuits, and the dusk-to-dawn sensor all operate autonomously on the local MCU. Connectivity adds intelligence, analytics, and optimisation, but it does not create a dependency. A cyberattack that isolates the lighting network will not plunge the factory into darkness; it will simply cause the lights to continue operating on their last programmed schedule until connectivity is restored. This failsafe design is non-negotiable for industrial acceptance.

7. Case Studies: VP TITAN I IoT Integration in Practice

To make the architecture tangible, we present two composite case studies based on real-world patterns.

Case Study 1: Automotive Assembly Plant, Germany
A major automotive OEM operates a 120,000 m² final assembly building with 48 external loading docks, employee parking for 2,000 vehicles, and 3 km of perimeter fence. The facility aimed to achieve carbon-neutral operations by 2028, with outdoor lighting identified as a key contributor to both energy consumption and Scope 1 emissions from diesel lighting towers used in the overflow yard.

The solution deployed 280 VP TITAN I solar floodlights across the exterior, all factory-integrated with Wi-Fi modules and linked to a private instance of EseeCloud hosted on the OEM’s Azure Stack. Telemetry flows every 5 minutes. The integration team built a custom connector to SAP EAM (Enterprise Asset Management).

Within the first year of operation:

  • Predictive maintenance detected 12 batteries whose capacity had degraded faster than expected due to a firmware issue that caused shallower-than-optimal charging in winter. VP provided an OTA update that corrected the charge profile, and the batteries were replaced under warranty before any light failed to last a full night.

  • Radar motion data from the overflow yard was integrated into the WMS. The system now automatically logs when a truck enters a specific dock lane, reducing the need for manual RFID scanning by the driver. This repurposing of lighting infrastructure saved an estimated €70,000 in dedicated sensor installation.

  • Energy reporting showed that the TITAN I fleet generated 82 MWh of solar electricity in its first year, directly reducing the plant’s grid consumption by that amount—sufficient to achieve a 5% reduction in outdoor lighting energy intensity and contribute to a verified Scope 2 emission reduction of 34 tonnes CO₂e.

Case Study 2: Cold Storage Logistics Hub, Canada
A frozen food distributor in Alberta operates a 15-hectare outdoor storage yard where temperatures drop to -35 °C. Conventional wired lighting had repeatedly failed due to ground frost heaving conduits apart. The company replaced 60 metal-halide pole lights with VP TITAN I floodlights equipped with LoRaWAN modules and remote monocrystalline panel arrays mounted on a south-facing warehouse wall.

The extreme cold posed a challenge: LiFePO₄ battery capacity temporarily drops below -20 °C, and charging must be inhibited to prevent lithium plating. The VP TITAN I’s onboard battery management system includes a low-temperature charge cutoff and a self-heating function that draws a small current to warm the battery before charging commences. The IoT platform monitors this process. In January, the data revealed that one particular light was spending 4 hours per day in “warming mode,” significantly reducing its energy harvest. Inspection revealed that its panel had been partially shaded by a new snowdrift accumulated on an adjacent roof. Facility staff cleared the drift, restoring full harvest. Without the IoT telemetry, the light would have simply gone offline after a few sunless days, with no diagnostic trail to explain why.

The integration also tied the radar sensors into the security system. Because the yard is remote, any after-hours motion triggers an alert to a central monitoring station. The VP lights’ radar data, with its speed and size estimation, reduced false alarms from animals by 70% compared to the previous standalone PIR system.

8. Implementation Roadmap: From Pilot to Enterprise Scale

Deploying an IoT-integrated solar lighting system across a large industrial site is a multidisciplinary project that touches IT, OT, facilities, and sustainability teams. Based on dozens of deployments, the following roadmap has proven effective.

Phase 1: Pilot (2–3 Months)

  • Select a representative zone with 5–10 VP TITAN I lights—ideally a mix of high-traffic and low-traffic areas.

  • Choose the communication technology (Wi-Fi, 4G, or LoRaWAN) based on a site survey.

  • Connect the lights to a cloud test environment and configure a basic Grafana dashboard showing key telemetry.

  • Run the pilot through a full seasonal cycle (e.g., winter solstice) to validate the battery autonomy and the energy model.

Phase 2: Integration (3–4 Months)

  • Work with the IT/OT teams to establish the network architecture, VLANs, and firewall rules. Procure and install any required LoRa gateways.

  • Develop the API connectors between the VP cloud platform (or the company’s own MQTT broker) and the CMMS, EMS, and optionally the MES/WMS.

  • Define the predictive maintenance rules and alarm thresholds, calibrating them against the pilot data.

  • Train the maintenance and facility teams on the new dashboards and mobile alerting.

Phase 3: Enterprise Rollout (6–12 Months)

  • Deploy the remaining lights in phases aligned with the factory’s production calendar to minimise disruption.

  • Commission each light using the VP mobile app, which scans a QR code on the luminaire and automatically registers it in the asset database with its GPS coordinates.

  • Initiate a 30-day “learning period” during which the system builds baseline models for battery capacity, daily harvest, and motion patterns.

  • Go live with automated work order generation.

Phase 4: Continuous Improvement (Ongoing)

  • Review predictive maintenance alert accuracy monthly and adjust thresholds to balance sensitivity versus false alarms.

  • Use the radar motion heatmaps to identify underutilised areas where lighting can be further dimmed, or high-traffic zones that may need additional fixtures.

  • Incorporate new OT applications as they emerge: digital twin of the lighting network, AI-based video analytics from companion VP HD-AI900 smart lights, and integration with AGV fleet management.

9. The Long View: AI, Digital Twins, and the Autonomous Factory

The VP TITAN I’s current IoT capabilities are the foundation for a far more ambitious vision. Imagine a digital twin of the entire industrial site, rendered in real time with lighting data as one of its layers. When a safety engineer runs an evacuation simulation, the twin dynamically models the illuminance on escape routes as batteries degrade and seasons change, automatically flagging when the lighting falls below code. When the factory’s AI scheduler plans production for the next week, it factors in the predicted solar harvest—ramping down non-essential outdoor tasks on cloudy days to conserve battery for security lighting. When an autonomous drone patrols the perimeter, it communicates directly with the nearest VP lights, requesting a brief full-brightness illumination of the zone it is about to inspect, then releasing the lights back to their dim state.

All of this is achievable because VAST PROSPERITY built the TITAN I with an open, extensible architecture. The same SMD5054 LEDs that illuminate a billboard with 160 lm/W efficiency, the same Teijin PC lens that increases irradiated area by 30%, and the same 5 V fast-charge system that harvests 25% more energy—these are not just components of a light. They are components of a cyber-physical system. The light bulb has become a computer, a sensor, a generator, and a communicator. In the smart factory, it is no longer a fixture; it is a value stream.

 

10. Conclusion: Turning Light into Intelligence

The journey that began with a solar billboard light on a dusty highway has reached an extraordinary destination: the cognitive industrial floodlight that not only illuminates the work, but understands it. The VAST PROSPERITY SOLAR FLOOD LIGHT TITAN I is the hardware embodiment of a simple yet profound idea—that every asset in the industrial environment, no matter how humble, can generate data that reduces cost, increases safety, and accelerates the transition to a sustainable, net-zero economy.

For the automation engineer, the VP TITAN I offers a ready-made IoT endpoint that drops into an existing OPC-UA or MQTT infrastructure without months of custom integration. For the reliability manager, it delivers the predictive maintenance data that eliminates unplanned darkness. For the sustainability director, it provides auditable, granular proof that every lumen of light is powered by clean sunshine, every night of the year. And for the CFO, it transforms a lighting line item from a fixed operating expense into a capital investment with a measurable return—lower energy bills, fewer maintenance call-outs, and new operational insights harvested from the radar motion data.

The smart factory is lit by the sun. And with VP TITAN I, that light is not just bright; it is brilliant—in every sense of the word.

ꄴPrevious： null
ꄲNext： null