Internet of vehicles service scheduling method, system and device based on slice private network, and medium

Abstract

The invention discloses an Internet of Vehicles service scheduling method, system and device based on a slice private network and a medium, and the method comprises the steps: dividing an Internet of Vehicles service into a plurality of service types according to service demands, and determining the priority of each service type; an eSIM + SoftSIM scheme is adopted to generate a plurality of network slices of different slice types, and slice resource allocation is carried out on the network slices; requesting a network slice through the Internet of Vehicles intelligent terminal, and mapping the Internet of Vehicles services of each service type to the network slices of different slice types according to the priority; and performing data transmission on the corresponding Internet of Vehicles service by using the network slices. According to the invention, refined resource scheduling and multi-service parallel guarantee of the Internet of Vehicles service are realized, the reliability of the Internet of Vehicles service and the network resource utilization rate are improved, the hardware cost and the use power consumption of the Internet of Vehicles intelligent terminal are reduced, and the method can be widely applied to the technical field of Internet of Vehicles.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking, and in particular to a vehicle networking service scheduling method, system, device and medium based on a sliced private network. Background Art

[0002] Currently, in 4G / 5G vehicle networking, voice calls are transmitted in the form of data packets through IMS (IP Multimedia Subsystem) (i.e., VoLTE / VoNR), sharing the same physical channel with ordinary data traffic (such as navigation and OTA upgrades). At this time, the T-BOX (vehicle networking intelligent terminal) can assign different priorities to voice services and ordinary data services through the QoS (Quality of Service) mechanism, so that the two can be transmitted in parallel without conflict.

[0003] However, the above solutions have the following disadvantages:

[0004] 1) Risks caused by resource competition: In a weak signal environment, the T-BOX may suspend ordinary data services and give priority to ensuring voice calls, or it may switch the encoding method of the voice to free up bandwidth for critical data services, resulting in resource preemption between services and the communication reliability cannot be guaranteed.

[0005] 2) Hardware cost and power consumption: Dual-channel concurrency requires a higher-specification radio frequency front end, resulting in an approximately 15% increase in the cost of the T-BOX. At the same time, the power consumption in the concurrent state can reach 3W, affecting the battery life of electric vehicles. Summary of the Invention

[0006] An object of the present invention is to solve at least to some extent one of the technical problems existing in the prior art.

[0007] To this end, an object of an embodiment of the present invention is to provide a vehicle networking service scheduling method based on a sliced private network. This method realizes the refined resource scheduling and multi-service parallel guarantee of vehicle networking services, improves the reliability of vehicle networking services and the utilization rate of network resources, and reduces the hardware cost and power consumption of vehicle networking intelligent terminals.

[0008] Another object of an embodiment of the present invention is to provide a vehicle networking service scheduling system based on a sliced private network.

[0009] To achieve the above technical objectives, the technical solutions adopted in the embodiments of the present invention include:

[0010] In a first aspect, an embodiment of the present invention provides a vehicle networking service scheduling method based on a sliced private network, including the following steps:

[0011] Dividing vehicle networking services into multiple service types according to service requirements, and determining the priorities of each service type;

[0012] Adopt the eSIM + SoftSIM solution to generate multiple network slices of different slice types, and allocate slice resources to the network slices;

[0013] The vehicle networking intelligent terminal requests the network slices, and maps the vehicle networking services of each service type to the network slices of different slice types according to the priority;

[0014] Use the network slices to perform data transmission on the corresponding vehicle networking services.

[0015] Furthermore, in an embodiment of the present invention, the service types include real-time control services, safety emergency services, data transmission services, and management service services. The real-time control services include autonomous driving instruction transmission and V2X cooperation. The safety emergency services include eCall emergency calls and collision warnings. The data transmission services include high-definition map updates and driving behavior log uploads. The management service services include FOTA upgrades and remote diagnoses. The priorities of the real-time control services, the safety emergency services, the data transmission services, and the management service services decrease in sequence.

[0016] Furthermore, in an embodiment of the present invention, the vehicle networking intelligent terminal is embedded with a hardware chip supporting eSIM and is equipped with a software protocol stack supporting SoftSIM. The eSIM + SoftSIM solution is adopted to generate multiple network slices of different slice types, and slice resources are allocated to the network slices. Specifically, it includes:

[0017] Pre-define multiple slice type templates according to service requirements, and determine the QoS indicators and security levels of each slice type template;

[0018] Create multiple virtual SIM instances, and associate the virtual SIM instances with the slice type templates one by one;

[0019] Send a network slice creation instruction to the base station according to the associated virtual SIM instances to generate corresponding multiple network slices;

[0020] Allocate resources to each network slice according to the QoS indicators and the security levels;

[0021] Among them, the network slices include URLLC slices, dedicated URLLC slices, eMBB slices, and mMTC slices.

[0022] Furthermore, in an embodiment of the present invention, the vehicle networking intelligent terminal requests the network slices, and specifically includes:

[0023] Request the network slice from the slice manager through the vehicle networking intelligent terminal, so that the slice manager allocates an IMSI as the virtual identifier of the vehicle networking intelligent terminal, and sends an attachment request according to the IMSI through a software protocol stack supporting SoftSIM;

[0024] Transmit the attachment request to the AMF network element through the RAN, so that the AMF network element requests the HSS network element to authenticate the identity and slice permission of the vehicle networking intelligent terminal;

[0025] When the authentication is passed, authorize the vehicle networking intelligent terminal to access the network slice through the AMF network element.

[0026] Further, in an embodiment of the present invention, mapping the vehicle networking services of each service type to the network slices of different slice types according to the priority specifically includes:

[0027] Map the real-time control type services to the URLLC slice;

[0028] Map the safety emergency type services to the dedicated URLLC slice;

[0029] Map the data transmission type services to the eMBB slice;

[0030] Map the management service type services to the mMTC slice.

[0031] Further, in an embodiment of the present invention, the vehicle networking service scheduling method further includes the following steps:

[0032] Real-time monitor the network status data of each network slice through the vehicle networking terminal;

[0033] Judge in real time whether the network slice meets the resource requirements of the corresponding vehicle networking service according to the network status data;

[0034] When the network slice does not meet the service requirements of the corresponding vehicle networking service, request to switch slice resources from the slice manager through the vehicle networking terminal.

[0035] Further, in an embodiment of the present invention, the vehicle networking service scheduling method further includes the following steps:

[0036] Real-time monitor the service status of each vehicle networking service through the vehicle networking terminal, predict the change of resource requirements of each vehicle networking service according to the service status, and perform slice resource recycling and reallocation according to the change of resource requirements.

[0037] In a second aspect, an embodiment of the present invention provides a vehicle-to-everything (V2X) service scheduling system based on a sliced private network, including:

[0038] A service division module, configured to divide V2X services into multiple service types according to service requirements, and determine the priority of each of the service types;

[0039] A slice generation module, configured to generate multiple network slices of different slice types by adopting an eSIM+SoftSIM solution, and allocate slice resources to the network slices;

[0040] A service mapping module, configured to request the network slices through a V2X intelligent terminal, and map the V2X services of each of the service types to the network slices of different slice types according to the priority;

[0041] A data transmission module, configured to perform data transmission on the corresponding V2X services by using the network slices.

[0042] In a third aspect, an embodiment of the present invention provides a V2X service scheduling device based on a sliced private network, including:

[0043] At least one processor;

[0044] At least one memory, configured to store at least one program;

[0045] When the at least one program is executed by the at least one processor, the at least one processor is caused to implement the above-mentioned V2X service scheduling method based on a sliced private network.

[0046] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, in which a program executable by a processor is stored, and the program executable by the processor is used to execute the above-mentioned V2X service scheduling method based on a sliced private network when being executed by the processor.

[0047] The advantages and beneficial effects of the present invention will be partially given in the following description, partially will become obvious from the following description, or will be understood through the practice of the present invention:

[0048] In the embodiments of the present invention, vehicle networking services are divided into multiple service types according to service requirements, and the priorities of each service type are determined. An eSIM + SoftSIM solution is adopted to generate network slices of multiple different slice types, and slice resource allocation is performed on the network slices. The vehicle networking intelligent terminal requests the network slices, and vehicle networking services of each service type are mapped to network slices of different slice types according to the priorities, and the corresponding vehicle networking services are data - transmitted using the network slices. The embodiments of the present invention adopt the eSIM + SoftSIM solution to map vehicle networking services with different priorities to network slices of different slice types, ensure that there is no interference between vehicle networking services through hard isolation and soft isolation, realize refined resource scheduling and multi - service parallel guarantee of vehicle networking services, improve the reliability of vehicle networking services and the utilization rate of network resources, and reduce the hardware cost and power consumption of vehicle networking intelligent terminals. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] To more clearly illustrate the technical solutions in the embodiments of the present invention, the following introduces the drawings required to be used in the embodiments of the present invention. It should be understood that the drawings introduced below only facilitate the clear expression of some embodiments of the technical solutions in the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0050] Figure 1 It is a flowchart of the steps of a vehicle networking service scheduling method based on a slice dedicated network provided by the embodiments of the present invention;

[0051] Figure 2 It is a schematic flowchart of slice resource allocation provided by the embodiments of the present invention;

[0052] Figure 3 It is a schematic flowchart of slice communication authentication provided by the embodiments of the present invention;

[0053] Figure 4 It is a schematic flowchart of slice mapping allocation provided by the embodiments of the present invention;

[0054] Figure 5 It is a block diagram of the structure of a vehicle networking service scheduling system based on a slice dedicated network provided by the embodiments of the present invention;

[0055] Figure 6 It is a block diagram of the structure of a vehicle networking service scheduling device based on a slice dedicated network provided by the embodiments of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0056] Embodiments of the present invention will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the accompanying drawings are exemplary and are only used to explain the present invention and should not be construed as a limitation of the present invention. For the step numbers in the following embodiments, they are only set for the convenience of explanation and illustration, and no limitation is imposed on the order between the steps. The execution order of each step in the embodiments can be adaptively adjusted according to the understanding of those skilled in the art.

[0057] In the description of the present invention, the meaning of "a plurality" is two or more. If the first and second are described, it is only for the purpose of distinguishing technical features and should not be construed as indicating or implying relative importance or implicitly indicating the quantity of the indicated technical features or implicitly indicating the sequence of the indicated technical features. In addition, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art of this technical field.

[0058] Referring to Figure 1 , an embodiment of the present invention provides a method for scheduling vehicle networking services based on a sliced private network, which specifically includes the following steps:

[0059] S101. Divide the vehicle networking services into multiple service types according to service requirements and determine the priorities of each service type;

[0060] S102. Adopt the eSIM+SoftSIM solution to generate multiple network slices of different slice types and allocate slice resources to the network slices;

[0061] S103. Request network slices through the vehicle networking intelligent terminal and map the vehicle networking services of each service type to the network slices of different slice types according to the priorities;

[0062] S104. Use the network slices to perform data transmission on the corresponding vehicle networking services.

[0063] The embodiment of the present invention adopts the eSIM+SoftSIM solution to map vehicle networking services with different priorities to network slices of different slice types, and ensures that there is no interference between vehicle networking services through hard isolation and soft isolation, realizing refined resource scheduling and multi-service parallel guarantee of vehicle networking services, improving the reliability of vehicle networking services and the utilization rate of network resources, and reducing the hardware cost and power consumption of vehicle networking intelligent terminals.

[0064] As a further optional implementation, the service types include real-time control services, safety emergency services, data transmission services, and management service services. The real-time control services include autonomous driving instruction transmission and V2X collaboration. The safety emergency services include eCall emergency calls and collision warnings. The data transmission services include high-definition map updates and driving behavior log uploads. The management service services include FOTA upgrades and remote diagnostics. The priorities of the real-time control services, safety emergency services, data transmission services, and management service services decrease in sequence.

[0065] Specifically, in the embodiments of the present invention, for the multi-scenario communication requirements of intelligent connected vehicles, the in-vehicle T-BOX function is divided into four types of key services, which are specifically as follows:

[0066] Real-time control type: Autonomous driving instruction transmission, V2X collaboration (low latency, high reliability);

[0067] Safety emergency type: eCall emergency call, collision warning (independent channel, high priority);

[0068] Data transmission type: High-definition map update, driving behavior log upload (high bandwidth);

[0069] Management service type: FOTA upgrade, remote diagnosis (dynamic bandwidth allocation).

[0070] As a further optional implementation, the intelligent vehicle terminal is embedded with a hardware chip supporting eSIM and is equipped with a software protocol stack supporting SoftSIM. The eSIM+SoftSIM solution is adopted to generate multiple network slices of different slice types and perform slice resource allocation for the network slices, which specifically includes:

[0071] S1021. Pre-define multiple slice type templates according to service requirements and determine the QoS metrics and security levels of each slice type template;

[0072] S1022. Create multiple virtual SIM instances and associate the virtual SIM instances with the slice type templates one by one;

[0073] S1023. Send a network slice creation instruction to the base station according to the associated virtual SIM instance to generate corresponding multiple network slices;

[0074] S1024. Perform resource allocation for each network slice according to the QoS metrics and security levels;

[0075] Among them, the network slices include URLLC slices, dedicated URLLC slices, eMBB slices, and mMTC slices.

[0076] Specifically, as Figure 2The following is a schematic diagram of the process for slice resource allocation provided by an embodiment of the present invention. The embodiment of the present invention adopts the eSIM+SoftSIM solution, assigns independent identity identifiers to different slices, and realizes virtual SIM card isolation. The specific process is as follows:

[0077] 1) Business requirement analysis and slice template predefined

[0078] (1) Scenario-based slice type division

[0079] Four basic slice templates are defined according to the 3GPP standard:

[0080] URLLC slice: latency < 1ms, reliability > 99.999%, applicable to industrial control, autonomous driving (can be derived into a dedicated URLLC slice when dedicated spectrum is required);

[0081] eMBB slice: peak rate > 10Gbps, high bandwidth priority, used for 4K / 8K video, AR / VR;

[0082] mMTC slice: connection density > 1M devices / km 2 , low power consumption, applicable to Internet of Things sensors;

[0083] (2) QoS metric and security level definition

[0084] QoS parameters: Based on the 3GPP TS23.501 specification, set indicators such as GBR (guaranteed bit rate), MFBR (maximum flow bit rate), PDB (packet delay budget), etc.

[0085] Security level: Adopt isolation level division, such as:

[0086] Level 1 (basic isolation): logical isolation + dynamic key management (eMBB);

[0087] Level 3 (dedicated isolation): physical resource exclusive + hardware encryption module (dedicated URLLC).

[0088] 2) Association between virtual SIM instance and slice template

[0089] Virtual SIM instantiation: Generate a vSIM configuration file through the UDM (Unified Data Management), which includes IMSI, slice subscription information (Subscribed S-NSSAI), and security credentials; use DNN (Data Network Name) to identify the slice type, such as "DNN_URLLC" corresponding to the URLLC slice template.

[0090] Dynamic binding mechanism: Configure policy rules in the PCF (Policy Control Function) to bind the SUPI (Subscriber Permanent Identifier) of the vSIM to a specific S-NSSAI (Slice Identifier). Example: vSIM_001 → SST = 1 (eMBB), SD = Video (Video Optimization Subclass).

[0091] 3) Network slice creation and instruction issuance

[0092] Core network orchestration process: The NSMF (Network Slice Management Function) calls the NSSMF (Sub-slice Management Function) to generate CN (Core Network) slices (such as SMF / UPF instances) according to a template; the RAN dynamically configures radio resources through the Near-RT RIC (Real-Time Intelligence Controller) of the O-RAN architecture.

[0093] Base station side slice instantiation: The base station receives N2 interface instructions, allocates dedicated PRBs (Physical Resource Blocks) to the URLLC slice, and enables a pre-scheduling mechanism to reduce latency. Example: The gNB reserves 20% of the spectrum for the dedicated URLLC slice and enables HARQ retransmission count optimization.

[0094] Furthermore, as an optional implementation, the vehicle networking intelligent terminal requests a network slice, which specifically includes:

[0095] S1031. The vehicle networking intelligent terminal requests a network slice from the slice manager, enabling the slice manager to allocate an IMSI as the virtual identifier of the vehicle networking intelligent terminal, and sending an attachment request according to the IMSI through a software protocol stack supporting SoftSIM;

[0096] S1032. The attachment request is transmitted to the AMF network element through the RAN, enabling the AMF network element to request the HSS network element to authenticate the identity and slice permissions of the vehicle networking intelligent terminal;

[0097] S1033. When the authentication is passed, the AMF network element authorizes the vehicle networking intelligent terminal to access the network slice.

[0098] Specifically, as Figure 3 shown in the flowchart of slice communication authentication provided by the embodiment of the present invention, where the RAN (Radio Access Network) is responsible for transmitting the wireless signal of the vehicle to the core network, the AMF (Access and Mobility Management Function) is used to receive the attachment request of the T-BOX and initiate authentication to the HSS, and the HSS (Home Subscriber Server) is used to verify the identity and slice permissions of the T-BOX and then authorize access through the AMF. The specific process is as follows:

[0099] 1) Slice request and virtual identity assignment

[0100] (1) The vehicle networking terminal initiates a slice request: The TBox (in-vehicle intelligent terminal) sends a slice request message to the slice manager (NSMF) by integrating the SoftSIM protocol stack. The request content includes:

[0101] Service feature identifier: such as V2X high reliability and low latency (SST = URLLC), autonomous driving subclass (SD = AutoDriving);

[0102] QoS requirements: latency < 10ms, reliability > 99.99% (refer to 3GPP TS22.186).

[0103] (2) IMSI virtual identifier allocation: The slice manager calls the UDM (Unified Data Management) to generate a dedicated IMSI. The rules include:

[0104] Dynamic mapping mechanism: The 4th - 8th bits of the IMSI encode the slice type (e.g., 46001 represents the URLLC vehicle networking slice);

[0105] Security isolation: An independent key set (Kausf, Kamf) is assigned to each IMSI and stored through the SE security chip.

[0106] 2) Transmission of the RAN side attachment request

[0107] (1) Radio access layer process

[0108] The TBox establishes an RRC connection through the following steps:

[0109] Msg1 (PRACH preamble): Select the URLLC dedicated RACH resource (the time - frequency position is indicated by SIB1 broadcast);

[0110] Msg3 (RRCSetupRequest): Carry the establishment reason as "mo - Signalling", and the encrypted IMSI is encapsulated in the NAS Attach Request.

[0111] (2) NAS signalling transparent transmission

[0112] The gNB forwards the NAS message to the AMF through the N2 interface. Key processing:

[0113] Slice identifier association: Add S - NSSAI = URLLC.AutoDriving in the N2 message header;

[0114] QoS pre - configuration: Set QFI = 1 (guaranteed bit rate GBR) according to the NGAP protocol.

[0115] 3) AMF - HSS two - way authentication and slice authorization

[0116] (1) Authentication Vector Acquisition

[0117] The AMF sends an Authentication Information Request to the HSS, including:

[0118] SUCI Conversion: Convert the IMSI to a SUCI temporary identifier based on Elliptic Curve Integrated Encryption Scheme (ECIES);

[0119] Slice Permission Verification: The HSS verifies whether the IMSI has subscribed to the URLLC.AutoDriving slice service.

[0120] (2) 5G-AKA Mutual Authentication

[0121] Execute the following key derivation process:

[0122] The HSS generates an AV: including RAND, AUTN, XRES*, KAUSF;

[0123] The terminal verifies the AUTN: The SoftSIM of the TBox calculates the SQN and MAC and matches the AUTN sent by the AMF;

[0124] Key Hierarchy Derivation: After successful authentication, generate Kamf→Knas→Kupenc for NAS encryption and user plane encryption.

[0125] (3) Slice Access Authorization

[0126] The AMF completes the authorization through the following mechanisms:

[0127] NSSAI Activation: Return the Allowed NSSAI list in the Registration Accept message;

[0128] Resource Reservation Instruction: Send a PDU Session Establishment request to the SMF, requesting to reserve edge UPF resources;

[0129] Security Policy Distribution: Enable user plane integrity protection (UPIP) and hardware encryption acceleration.

[0130] Further as an optional implementation, map the vehicle networking services of each service type to network slices of different slice types according to the priority, which specifically includes:

[0131] S1034. Map real-time control services to the URLLC slice;

[0132] S1035. Map security emergency services to a dedicated URLLC slice;

[0133] S1036. Map data transmission services to the eMBB slice;

[0134] S1037. Map management service - type services to the mMTC slice.

[0135] Specifically, as Figure 4 shown in the process schematic diagram of slice mapping and allocation provided by the embodiments of the present invention, the embodiments of the present invention map four types of key services to slice types according to service characteristics to achieve precise resource matching.

[0136] Further as an optional implementation manner, the vehicle - to - everything (V2X) service scheduling method further includes the following steps:

[0137] S201. Real - time monitor the network status data of each network slice through the V2X terminal;

[0138] S202. Real - time determine whether the network slice meets the resource requirements of the corresponding V2X service according to the network status data;

[0139] S203. When the network slice does not meet the service requirements of the corresponding V2X service, request to switch slice resources from the V2X terminal to the slice manager.

[0140] Specifically, the embodiments of the present invention real - time monitor the network status data of the network slice and perform slice resource switching to ensure the normal operation of the V2X service. The specific process is as follows:

[0141] 1) Real - time monitoring of network slice status

[0142] (1) Multi - dimensional data collection

[0143] The vehicle - mounted terminal (TBox / OBU) obtains the slice status in the following ways:

[0144] Radio layer metrics: Collect RSRP (-110 dBm), SINR (15 dB), and PRB utilization (>80% triggers an alarm) through the RRC layer interface;

[0145] Core network metrics: Subscribe to the NEF open interface to obtain the end - to - end delay (<10 ms) and UPF throughput (1 Gbps threshold);

[0146] Service layer perception: Integrate the application SDK to monitor the V2X message delivery success rate (99.95%) and the delay jitter of the autonomous driving control instruction (±0.5 ms).

[0147] (2) Edge computing pre - processing

[0148] Execute the following steps at the vehicle - mounted MEC node:

[0149] Data cleaning: Use Kalman filter to eliminate signal fluctuation noise (such as signal mutation in tunnel scenarios);

[0150] Feature extraction: Predict the bandwidth demand trend in the next 5 seconds through the LSTM model (accuracy > 92%);

[0151] Compressed transmission: Use Protobuf binary encoding to reduce the data volume by 70% and upload it through the C-V2X PC5 interface.

[0152] 2) Resource demand compliance judgment

[0153] (1) Dynamic SLA matching engine (example shown in Table 1 below)

[0154]

[0155] Table 1

[0156] (2) Multi-factor decision-making mechanism

[0157] Environmental perception compensation: Integrate weather data provided by roadside units (such as increasing 20% redundant bandwidth on rainy and snowy days);

[0158] Service priority arbitration: Adopt the weighted fair queue algorithm, and emergency services can preempt low-priority slice resources;

[0159] Historical data analysis: Call the historical KPI library of NWDAF (such as the resource demand on the same road section increasing by 35% during the Friday evening rush hour every week).

[0160] 3) Slice resource switching execution (S203)

[0161] (1) Handover request generation

[0162] The terminal generates a handover signaling containing the following elements:

[0163] Target slice identifier: S-NSSAI = URLLC.V2X (3GPP standard slice type);

[0164] QoS renegotiation parameters: MFBR (maximum bit rate) increased by 30%, PDB (packet delay budget) compressed to 15ms;

[0165] Security credentials: Generate a handover token (Token) based on a vehicle-grade HSM chip, containing a timestamp and a digital signature.

[0166] (2) Slice manager response process

[0167] TBox → NSMF: Slice_Handover_Request (S-NSSAI, QoS parameters);

[0168] NSMF→PCF: Query the target slice policy rules (such as spectrum allocation ratio);

[0169] PCF→UDM: Verify the terminal subscription permission (check the eSIM subscription information);

[0170] UDM→AMF: Send the N2 / N11 interface reconfiguration instruction;

[0171] AMF→gNB: Perform the RAN slice handover (reserve dedicated BWP resource blocks).

[0172] (3) Verification mechanism after handover

[0173] Three-layer health check:

[0174] Physical layer: Verify that the new slice PRB allocation rate ≥ 90% of the application value;

[0175] Protocol layer: Complete the 5G-AKA secondary authentication (two-way certificate verification);

[0176] Service layer: Inject test data packets to verify that the end-to-end SLA is met.

[0177] Progressive migration: For latency-sensitive services, adopt the "dual-connection first then handover" mode to ensure zero interruption.

[0178] Further as an optional implementation manner, the vehicle networking service scheduling method further includes the following steps:

[0179] S204. Real-time monitor the service status of each vehicle networking service through the vehicle networking terminal, predict the resource requirement changes of each vehicle networking service according to the service status, and perform slice resource recycling and reallocation according to the resource requirement changes.

[0180] Specifically, the embodiments of the present invention real-time monitor the service status of vehicle networking services and perform slice resource recycling and reallocation to improve the network resource utilization rate. The specific process is as follows

[0181] 1) Multi-dimensional real-time monitoring of service status

[0182] (1) Vehicle-mounted terminal data acquisition layer

[0183] Wireless layer metrics: Collect RSRP (> -110dBm), SINR (> 15dB), and PRB utilization rate (threshold 80%) through the RRC interface;

[0184] Core network metrics: Subscribe to the NEF interface to obtain the end-to-end latency (< 10ms), UPF throughput (threshold 1Gbps), and packet loss rate (< 0.1%);

[0185] Business layer perception: Integrate the SDK to monitor the V2X message delivery success rate (>99.95%), the jitter of autonomous driving commands (±0.5 ms), and the high-precision map update delay (<50 ms).

[0186] (2) Edge node preprocessing

[0187] Data cleaning: Use Kalman filtering to eliminate signal mutation noise caused by tunnels / harsh weather;

[0188] Feature extraction: Use the LSTM model to extract key features such as delay fluctuation and bandwidth occupancy rate, and compress 70% of the transmission data volume.

[0189] Anomaly detection: Identify abnormal traffic flows (such as DDoS attack traffic) based on the Isolation Forest algorithm, with an accuracy rate >95%2

[0190] 2) Resource demand prediction and modeling

[0191] (1) Prediction model construction

[0192] Time series prediction: Use the Prophet model to analyze historical KPI data and predict the resource demand for the next 5 minutes (error rate <8%);

[0193] Scenario-based modeling, examples are as follows:

[0194] a. Emergency braking: Delay-sensitive, the resource demand is positively correlated with the square of the vehicle speed (R = kv 2 +c);

[0195] b. Fleet formation: Driven by connection density, for every additional 10 vehicles, 5% of the wireless resources need to be expanded;

[0196] Dynamic weight adjustment: Calculate the weights of environmental factors through the AHP (Analytic Hierarchy Process) method (such as rain and snow weather increasing the redundancy demand by 20%).

[0197] (2) Visualization of prediction results

[0198] Generate a heat map on the vehicle networking management platform to identify high-load areas in the next 15 minutes (such as around transportation hubs);

[0199] Trigger a three-level warning mechanism: yellow (load >60%), orange (>80%), red (>95%).

[0200] 3) Slice resource recycling and dynamic allocation

[0201] (1) Resource recycling strategy

[0202] Idle resource identification: Initiate a recycling command for slices with a utilization rate <10% for 3 consecutive cycles;

[0203] Priority recycling: Recycle in descending order of QCI level (QCI = 6 → 9), and retain the minimum guaranteed resources for emergency services;

[0204] Secure release mechanism: Adopt two-stage confirmation (AMF → SMF → UPF) to prevent mis-recycling, with a latency < 50ms;

[0205] (2) Reallocation execution process

[0206] Prediction engine → NSMF: Resource requirement change request (S-NSSAI, Δ bandwidth, Δ latency);

[0207] NSMF → PCF: Verify SLA compliance (refer to 3GPP TS28.532);

[0208] PCF → SMF: Issue UPF reconfiguration instructions (expansion / contraction);

[0209] SMF → gNB: RAN side carrier aggregation adjustment (CA Band1 + Band3);

[0210] gNB → TBox: RRC reconfiguration message (new resource block allocation information).

[0211] (3) Allocation strategy optimization, examples are as follows:

[0212] Emergency control, adopt an exclusive allocation strategy (reserve 20% spectrum + edge UPF instance), implemented based on TSN time-sensitive scheduling;

[0213] HD video, adopt elastic shared pool measurement (QCI = 1 has priority preemption, GTP-U header compression reduces bandwidth occupancy by 15%), implemented based on dynamic spectrum sharing;

[0214] Bulk upload, adopt off-peak aggregation measurement (utilize the low-load period in the early morning for mMTC slice bulk transmission), optimized and implemented based on discontinuous reception (DRX).

[0215] The above has described the method steps of the embodiments of the present invention. It can be understood that the embodiments of the present invention adopt the eSIM + SoftSIM solution to map vehicle networking services with different priorities to network slices of different slice types, and ensure that vehicle networking services do not interfere with each other through hard isolation and soft isolation, realizing refined resource scheduling and multi-service parallel guarantee for vehicle networking services, improving the reliability of vehicle networking services and the utilization rate of network resources, and reducing the hardware cost and power consumption of vehicle networking intelligent terminals.

[0216] Refer to Figure 5 , the embodiments of the present invention provide a vehicle networking service scheduling system based on a slice private network, including:

[0217] A service division module, configured to divide the vehicle networking services into multiple service types according to service requirements and determine the priorities of each service type;

[0218] A slice generation module, configured to generate multiple network slices of different slice types by adopting the eSIM+SoftSIM solution and allocate slice resources to the network slices;

[0219] A service mapping module, configured to request network slices through a vehicle networking intelligent terminal and map the vehicle networking services of each service type to the network slices of different slice types according to the priorities;

[0220] A data transmission module, configured to use the network slices to perform data transmission on the corresponding vehicle networking services.

[0221] The content in the above method embodiments is applicable to the system embodiments of the present invention. The functions specifically implemented by the system embodiments of the present invention are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those of the above method embodiments.

[0222] Referring to Figure 6 , an embodiment of the present invention provides a vehicle networking service scheduling device based on a sliced private network, including:

[0223] At least one processor;

[0224] At least one memory, configured to store at least one program;

[0225] When the at least one program is executed by the at least one processor, the at least one processor implements the above vehicle networking service scheduling method based on a sliced private network.

[0226] The content in the above method embodiments is applicable to the device embodiments of the present invention. The functions specifically implemented by the device embodiments of the present invention are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those of the above method embodiments.

[0227] An embodiment of the present invention also provides a computer-readable storage medium, in which a program executable by a processor is stored. The program executable by the processor is used to execute the above vehicle networking service scheduling method based on a sliced private network when executed by the processor.

[0228] A computer-readable storage medium according to an embodiment of the present invention can execute a vehicle networking service scheduling method provided by an embodiment of the method of the present invention, can execute any combination of implementation steps of the method embodiment, and has the corresponding functions and beneficial effects of the method.

[0229] An embodiment of the present invention also discloses a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device can read the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes Figure 1 the method shown.

[0230] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order mentioned in the operation diagrams. For example, depending on the functions / operations involved, two consecutive blocks shown may actually be executed substantially simultaneously or the above-mentioned blocks can sometimes be executed in the reverse order. In addition, the embodiments presented and described in the flowcharts of the present invention are provided by way of example for the purpose of providing a more comprehensive understanding of the technology. The disclosed method is not limited to the operations and logical flows presented herein. Alternative embodiments are contemplated, where the order of various operations is changed and where sub-operations described as part of a larger operation are executed independently.

[0231] In addition, although the present invention has been described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the above functions and / or features may be integrated in a single physical device and / or software module, or one or more functions and / or features may be implemented in separate physical devices or software modules. It can also be understood that a detailed discussion of the actual implementation of each module is not necessary for understanding the present invention. More precisely, considering the attributes, functions and internal relationships of the various functional modules in the devices disclosed herein, the actual implementation of the modules will be understood within the ordinary skills of an engineer. Therefore, those skilled in the art can implement the present invention as set forth in the claims without undue experimentation. It can also be understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0232] If the above functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the above methods in various embodiments of the present invention. The foregoing storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs, etc., which can store program codes of various types.

[0233] The logic and / or steps represented in the flowchart or described in other ways herein, for example, can be considered as a definite sequence list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or in combination with these instruction execution systems, apparatuses, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0234] More specific examples (non-exhaustive list) of computer-readable media include the following: electrical connection parts (electronic devices) having one or more wirings, portable computer disk cartridges (magnetic devices), random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (EPROMs or flash memories), optical fiber devices, and portable compact disc read-only memories (CDROMs). Additionally, a computer-readable medium can even be paper or other suitable media on which the above program can be printed, because the above program can be obtained electronically, for example, by optically scanning the paper or other media, then editing, interpreting, or otherwise processing it as appropriate, and then storing it in a computer memory.

[0235] It should be understood that various parts of the present invention can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0236] In the foregoing description of this specification, descriptions with reference to the terms "one embodiment / example", "another embodiment / example", or "certain embodiments / examples", etc., mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0237] Although the embodiments of the present invention have been shown and described, those of ordinary skill in the art can understand that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of the present invention. The scope of the present invention is defined by the claims and their equivalents.

[0238] The above is a specific description of the preferred embodiments of the present invention, but the present invention is not limited to the above embodiments. Those skilled in the art can also make various equivalent deformations or substitutions without departing from the spirit of the present invention, and these equivalent deformations or substitutions are all included within the scope defined by the claims of this application.

Claims

1. A vehicle networking service scheduling method based on a sliced private network, characterized in that Including the following steps: Dividing the vehicle networking services into multiple service types according to business requirements, and determining the priority of each of the service types; Adopting the eSIM+SoftSIM solution to generate multiple network slices of different slice types, and performing slice resource allocation for the network slices; Requesting the network slices through a vehicle networking intelligent terminal, and mapping the vehicle networking services of each of the service types to the network slices of different slice types according to the priority; Using the network slices to perform data transmission for the corresponding vehicle networking services.

2. The vehicle networking service scheduling method based on a sliced private network according to claim 1, wherein: The service types include real-time control services, safety emergency services, data transmission services, and management service services. The real-time control services include autonomous driving instruction transmission and V2X collaboration. The safety emergency services include eCall emergency calls and collision warnings. The data transmission services include high-definition map updates and driving behavior log uploads. The management service services include FOTA upgrades and remote diagnosis. The priorities of the real-time control services, the safety emergency services, the data transmission services, and the management service services decrease in sequence.

3. The vehicle - to - everything (V2X) service scheduling method based on a sliced private network according to claim 2, wherein, The vehicle networking intelligent terminal is embedded with a hardware chip supporting eSIM and is equipped with a software protocol stack supporting SoftSIM. The step of adopting the eSIM+SoftSIM solution to generate multiple network slices of different slice types and performing slice resource allocation for the network slices specifically includes: Pre-defining multiple slice type templates according to business requirements, and determining the QoS metrics and security levels of each of the slice type templates; Creating multiple virtual SIM instances, and associating the virtual SIM instances with the slice type templates one by one; Sending a network slice creation instruction to a base station according to the associated virtual SIM instances to generate corresponding multiple network slices; Performing resource allocation for each of the network slices according to the QoS metrics and the security levels; Among them, the network slices include URLLC slices, dedicated URLLC slices, eMBB slices, and mMTC slices.

4. The vehicle networking service scheduling method based on a sliced private network according to claim 3, wherein, The step of requesting the network slices through the vehicle networking intelligent terminal specifically includes: Requesting the network slices from a slice manager through the vehicle networking intelligent terminal, so that the slice manager allocates an IMSI as the virtual identifier of the vehicle networking intelligent terminal, and sending an attachment request according to the IMSI through the software protocol stack supporting SoftSIM; Transmitting the attachment request to an AMF network element through the RAN, so that the AMF network element requests the HSS network element to authenticate the identity and slice permissions of the vehicle networking intelligent terminal; When the authentication is passed, authorizing the vehicle networking intelligent terminal to access the network slices through the AMF network element.

5. The method for scheduling vehicle networking services based on a sliced private network according to claim 3, wherein The step of mapping the vehicle networking services of each of the service types to the network slices of different slice types according to the priority specifically includes: Mapping the real-time control services to the URLLC slices; Mapping the safety emergency services to the dedicated URLLC slices; Mapping the data transmission services to the eMBB slices; Map the management service - type services to the mMTC slice.

6. A method for scheduling vehicle networking services based on a sliced private network according to any one of claims 1 to 5, characterized in that, The vehicle - to - everything (V2X) service scheduling method further includes the following steps: Real - time monitor the network status data of each of the network slices through the V2X terminal. Based on the network status data, determine in real - time whether the network slice meets the resource requirements of the corresponding V2X service. When the network slice does not meet the service requirements of the corresponding V2X service, request to switch slice resources from the slice manager through the V2X terminal.

7. A method for scheduling vehicle networking services based on a sliced private network according to any one of claims 1 to 5, characterized in that, The vehicle - to - everything (V2X) service scheduling method further includes the following steps: Real - time monitor the service status of each of the V2X services through the V2X terminal, predict the change in resource requirements of each of the V2X services based on the service status, and perform slice resource recycling and re - allocation according to the change in resource requirements.

8. A vehicle networking service scheduling system based on a sliced private network, characterized in that, Comprises: A service division module, configured to divide V2X services into multiple service types according to service requirements and determine the priority of each service type. A slice generation module, configured to generate network slices of multiple different slice types using the eSIM + SoftSIM solution and allocate slice resources to the network slices. A service mapping module, configured to request the network slices through the V2X intelligent terminal and map the V2X services of each service type to the network slices of different slice types according to the priority. A data transmission module, configured to perform data transmission on the corresponding V2X services using the network slices.

9. An in-vehicle network service scheduling device based on a sliced private network, characterized in that, Comprises: At least one processor; At least one memory, configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements a V2X service scheduling method based on a sliced private network as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a program executable by a processor, characterized in that, The program executable by the processor, when executed by the processor, is used to execute a V2X service scheduling method based on a sliced private network as described in any one of claims 1 to 7.

Images