22.185 V2X业务要求 Service requirements for v2x services

该文详细阐述了V2X服务在Release17阶段的一系列技术要求,包括V2X应用如V2Vehicle、V2Pedestrian等,对E-UTRA(N)的通用和特殊服务需求,如最大20ms的pre-crashsensing时延和100ms的其他场景时延,以及消息大小、发送频率和速度限制。此外,还提到了安全措施,如MNO对UE的授权和匿名使用的规定,以符合地域监管和运营商政策。

Service requirements for v2x services; stage 1; Release 17

1,V2X的典型应用场景——V2 Vehicle,V2 Pedestrian,V2 Infrastructure,V2 Network。
2,列举了对E-UTRA(N)的通用要求、特殊服务要求、安全要求。
3,特殊服务要求里,对时延做出了要求——需要支持,除pre-crash sensing场景最大时延为20ms外,其余场景最大时延均为100。
4,特殊服务要求里,对消息大小做出了规定——能够支持广播消息50~300 Bytes;event-trigger消息最大到1200 Bytes。
5,特殊服务要求里,对发送消息的频率做出规定——能够支持最多1秒发10个消息。
6,特殊服务要求里,对能够支持的速度做出了规定——V2V场景为相对速度500km/h,其余场景绝对速度250km/h。
7,安全要求里,MNO=Mobile Network Operator 移动网络运营商,network需要提供一些方法给MNO去授权UE支持V2X。
8,为了服从地域监管/运营商政策,3gpp系统应该支持UE在应用V2X时,使用匿名。

### V2X Communication IPv6 Packet Format Specification In Vehicle-to-Everything (V2X) communications, the structure of an IPv6 packet adheres closely to standard Internet Protocol version 6 specifications while incorporating specific requirements for vehicular networks. The general layout includes several critical components: #### Header Structure The basic header consists of a fixed part that is always present followed by optional extension headers as needed. - **Version**: Specifies the IP version number; this value must be `6` for IPv6 packets. - **Traffic Class**: An 8-bit field used for Quality of Service (QoS). - **Flow Label**: A 20-bit identifier intended to facilitate handling of related packets. - **Payload Length**: Indicates the length of the payload data following the header fields. - **Next Header**: Identifies either the type of next-level protocol or indicates which kind of extension header follows immediately after the main one. - **Hop Limit**: Defines how many routers can forward the datagram before being discarded. - **Source Address**: Contains the full 128 bits representing the sender's address. - **Destination Address**: Holds another complete set of 128 bits specifying where the message should go. For V2X applications, particular attention may need to be paid to ensuring proper configuration regarding multicast addresses since these are often utilized within cooperative awareness messages exchanged between vehicles and infrastructure points[^3]. #### Extension Headers Depending on application needs, various types of additional information might get appended via extension headers such as routing options, fragmentation details, authentication mechanisms etc., but typically not required in simple scenarios involving direct vehicle-infrastructure interaction unless security features like encryption come into play. Regarding specifics about L2 MTU settings mentioned earlier[Cisco Systems 和 MikroTik 使用 L2 MTU 作为最大帧大小][^1], although relevant when configuring network devices supporting V2X services, does not directly influence the actual composition of individual IPv6 frames beyond affecting overall permissible sizes allowed across links involved. When considering parameters influencing behavior towards certain kinds of traffic patterns including those seen under V2X contexts, configurations similar to `echo_ignore_anycast`, controlling responses to special queries directed at groups rather than single entities could prove important though primarily concerning host operating system tuning instead of shaping fundamental aspects of packet construction itself [If set non-zero, then the kernel will ignore all ICMP ECHO requests sent to it over the IPv6 protocol destined to anycast address. Default: 0 ][^2]. ```python # Example Python code snippet demonstrating creation of minimalistic raw IPv6 packet using Scapy library from scapy.all import * packet = IPv6(dst="ff02::1")/ICMPv6EchoRequest() send(packet) ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值