WO2020073678A1 - 车辆通信方法、装置、计算机可读介质及电子设备 - Google Patents

车辆通信方法、装置、计算机可读介质及电子设备 Download PDF

Info

Publication number
WO2020073678A1
WO2020073678A1 PCT/CN2019/091809 CN2019091809W WO2020073678A1 WO 2020073678 A1 WO2020073678 A1 WO 2020073678A1 CN 2019091809 W CN2019091809 W CN 2019091809W WO 2020073678 A1 WO2020073678 A1 WO 2020073678A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
vehicle communication
network slices
identification information
user equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/091809
Other languages
English (en)
French (fr)
Inventor
王涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to JP2020560135A priority Critical patent/JP7058833B2/ja
Priority to EP19871415.6A priority patent/EP3761608B1/en
Publication of WO2020073678A1 publication Critical patent/WO2020073678A1/zh
Priority to US17/075,612 priority patent/US11445522B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/52—Allocation or scheduling criteria for wireless resources based on load
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria

Definitions

  • the present application relates to the field of computers and communication technologies, and in particular, to a vehicle communication method, device, computer-readable medium, and electronic equipment.
  • 5G Internet of Vehicles includes more than 20 different vehicles to the outside world (vehicle to X, V2X) use cases (use case), different use cases have different quality of service (Quality of Service, QoS) requirements.
  • V2X use cases may use different network slices because of different QoS, and the number of V2X use cases is far greater than 8.
  • 3GPP Rel-15 stipulates that a user equipment (User Equipment, UE) supports up to 8 network slices, and different network slices must use different protocol data unit (Protocol Data Unit, PDU) sessions. This assumption has a large The limitations are not conducive to the deployment of network slicing in IoV communications.
  • the embodiments of the present application provide a vehicle communication method, device, computer readable medium, and electronic equipment, which can at least to a certain extent increase the number of vehicle communication use cases that can be supported by user equipment, which is beneficial to the promotion of Internet of Vehicle solutions and deploy.
  • a vehicle communication method which is applied to a network-side device and includes: receiving a connection establishment request sent by user equipment, where the connection establishment request carries identification information of multiple network slices; Determine whether the multiple network slices correspond to the same vehicle communication service according to the identification information of the multiple network slices; if it is determined that the multiple network slices correspond to the same vehicle communication service, establish a connection with the user equipment Between a PDU session.
  • a vehicle communication method which is applied to a network-side device and includes: receiving a connection establishment request sent by user equipment, where the connection establishment request carries identification information of a virtual bundled network slice;
  • the identification information of the plurality of network slices corresponding to the virtual bundled network slice is determined according to the identification information of the virtual bundled network slice, so as to establish a PDU session with the user equipment based on the plurality of network slices.
  • a vehicle communication device including: a receiving unit configured to receive a connection establishment request sent by user equipment, where the connection establishment request carries identification information of multiple network slices; A unit for determining whether the plurality of network slices correspond to the same vehicle communication service according to the identification information of the plurality of network slices; a processing unit for determining that the plurality of network slices correspond to the same vehicle communication service Time, a PDU session with the user equipment is established.
  • the value interval of the identification information of the multiple network slices is within a predetermined interval to identify that the multiple network slices correspond to the same PDU session; or the multiple The slice / service type (SST) field in the identification information of each network slice contains an indicator bit to indicate that the multiple network slices correspond to the same PDU session; or The slice differentiation (Slice Differentiator, SD) field in the identification information includes an indication bit to indicate that the multiple network slices correspond to the same PDU session.
  • SST slice / service type
  • SD slice differentiation
  • the processing unit is further configured to: in the PDU session, control different network slices or different vehicle communication use cases corresponding to different QoS flows.
  • the processing unit is further used to: through the GPRS channel protocol-user plane (GPRS Tunnel Protocol User Glan), virtual private network (Virtual Private Network, VPN) Or a bandwidth management mechanism to isolate the different QoS flows.
  • GPRS channel protocol-user plane GPRS Tunnel Protocol User Glan
  • VPN Virtual Private Network
  • the vehicle communication device further includes: a scheduling unit configured to schedule the user equipment to use different wireless transmission resources for different network slices.
  • the vehicle communication device further includes: a configuration unit configured to configure a wireless transmission resource pool for different network slices, so that the user equipment can be used for different network slices For different wireless transmission resources, the priority of the wireless transmission resource pool has a positive correlation with the priority of the corresponding network slice, and the resource size of the wireless transmission resource pool has a positive correlation with the priority of the corresponding network slice.
  • the configuration unit is configured to: send configuration signaling to the user equipment to configure the user equipment with wireless transmission resource pools corresponding to the different network slices; Or pre-configure the wireless transmission resource pool corresponding to the different network slices to the user equipment.
  • the configuration unit is configured to: the configuration signaling sent to the user equipment is used to indicate the different networks in an explicit manner or an implicit manner The wireless transmission resource pool corresponding to the slice.
  • the vehicle communication device further includes: a sending unit configured to send information of available network slices to the user equipment, the information of available network slices including the Identification information for multiple network slices.
  • the access and mobility functional entities Access and Mobility Function (AMF) and the user plane functional entities (User Plane Function, UPF) corresponding to the multiple network slices are the same.
  • AMF Access and Mobility Function
  • UPF User Plane Function
  • the vehicle communication device further includes: an expansion unit, configured to expand the number of data wireless bearers to expand the number of network slices supported by the user equipment.
  • a vehicle communication device including: a receiving unit configured to receive a connection establishment request sent by user equipment, where the connection establishment request carries identification information of a virtual bundled network slice; processing A unit, configured to determine identification information of a plurality of network slices corresponding to the virtual bundled network slice according to the identification information of the virtual bundled network slice, to establish a PDU session with the user equipment based on the plurality of network slices .
  • the processing unit is configured to: according to a pre-configured correspondence, determine identification information of multiple network slices corresponding to the virtual bundled network slice.
  • the vehicle communication device further includes: a sending unit configured to send information of available network slices to the user equipment, the information of available network slices including the The identification information of the virtual bundled network slice.
  • the value interval of the identification information of the virtual bundled network slice is within a predetermined interval to indicate that the virtual bundled network slice corresponds to multiple network slices; or the virtual An indication bit is included in the SST field in the identification information of the bundled network slice to indicate that the virtual bundled network slice corresponds to multiple network slices; or an indication bit is included in the SD field in the identification information of the virtual bundled network slice To indicate that the virtual bundled network slice corresponds to multiple network slices.
  • a computer readable medium on which a computer program is stored, and when the computer program is executed by a processor, the vehicle communication method as described in the above embodiment is implemented.
  • an electronic device including: one or more processors; a storage device, configured to store one or more programs, when the one or more programs are When multiple processors execute, the one or more processors implement the vehicle communication method as described in the above embodiments.
  • the network-side device receives the connection establishment request sent by the user equipment, and determines that the identification information of multiple network slices included in the connection establishment request corresponds to the same vehicle communication During business, establish a PDU session with the user equipment, so that multiple network slices can share a PDU session, and thus enable the user equipment to support more network slices by establishing multiple PDU sessions, and the number of network slices corresponds Due to the number of vehicle communication use cases, the number of vehicle communication use cases that can be supported by user equipment is also increased, which is beneficial to the promotion and deployment of the Internet of Vehicles solution.
  • the network-side device receives the connection establishment request sent by the user equipment, and determines the number of virtual bundled network slices corresponding to the virtual bundled network slice identification information carried in the connection establishment request.
  • the identification information of each network slice enables the user equipment to support more network slices through virtual bundled network slices corresponding to multiple network slices, and the number of network slices corresponds to the number of vehicle communication use cases, thus also increasing the user equipment
  • the number of vehicle communication use cases that can be supported is conducive to the promotion and deployment of Internet of Vehicles solutions.
  • FIG. 1 shows a schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied;
  • FIG. 2 schematically shows a flowchart of a vehicle communication method according to an embodiment of the present application
  • FIG. 3 schematically shows a flowchart of a vehicle communication method according to an embodiment of the present application
  • FIG. 4 shows a schematic diagram of an application scenario of a vehicle communication method according to an embodiment of the present application
  • FIG. 5 shows a partial signaling flow diagram of establishing a PDU session between a user equipment and a network-side device according to an embodiment of the present application
  • FIG. 6 schematically shows a block diagram of a vehicle communication device according to an embodiment of the present application.
  • FIG. 7 schematically shows a block diagram of a vehicle communication device according to an embodiment of the present application.
  • FIG. 8 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application.
  • Example embodiments will now be described more fully with reference to the drawings.
  • the example embodiments can be implemented in various forms and should not be construed as being limited to the examples set forth herein; on the contrary, providing these embodiments makes the application more comprehensive and complete, and fully conveys the concept of the example embodiments For those skilled in the art.
  • FIG. 1 shows a schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied.
  • the system architecture may include a vehicle terminal 101, a base station 102, a core network device 103, and an application server 104.
  • the core network device 103 may be an AMF in a 5G core network or the like.
  • vehicle terminals 101, base stations 102, core network devices 103, and application servers 104 shown in FIG. 1 are only schematic. According to implementation requirements, there may be any number of vehicle terminals 101, base stations 102, core network devices 103, and application servers 104.
  • the network-side device (such as the base station 102, the core network device 103, or the application server 104 shown in FIG. 1), if the connection establishment request is Carrying identification information of multiple network slices, and determining that the multiple network slices correspond to the same vehicle communication service, a PDU session with the vehicle terminal 101 may be established, thereby enabling the vehicle terminal 101 to establish multiple PDU sessions to support more network slices, and the number of network slices corresponds to the number of V2X use cases, so it also increases the number of V2X use cases that user equipment can support, which is beneficial to the promotion and deployment of car networking solutions.
  • the network-side device (such as the base station 102, the core network device 103, or the application server 104 shown in FIG. 1), if the connection establishment request Carrying the identification information of the virtual bundled network slice, the identification information of the plurality of network slices corresponding to the virtual bundled network slice can be determined according to the identification information of the virtual bundled network slice to establish a vehicle terminal 101 based on the plurality of network slices
  • the number of network slices corresponds to the number of V2X use cases, thus also increasing users
  • the number of V2X use cases that the device can support is conducive to the promotion and deployment of IoV solutions.
  • FIG. 2 schematically shows a flowchart of a vehicle communication method according to an embodiment of the present application.
  • the vehicle communication method may be executed by a network-side device, such as a base station, a core network device, or an application server at the edge of the network .
  • the vehicle communication method includes at least S210 to S230, which are described in detail as follows:
  • connection establishment request sent by a user equipment is received, where the connection establishment request carries identification information of multiple network slices.
  • the user equipment may be a vehicle terminal, and the connection establishment request sent by the user equipment may be a request to establish a PDU session.
  • the identification information of the network slice may be selection assistance information (Single Network Selection Selection Assistance (S-NSSAI) for a single network slice).
  • S-NSSAI Single Network Selection Selection Assistance
  • the network side device may send information of available network slices (such as Allowed NSSAI) to the user equipment.
  • the information of the available network slices includes the The identification information of the multiple network slices, so that the user equipment can select from the available network slice information.
  • the connection establishment request in the embodiment of the present application can have the following configurations:
  • the value interval of the identification information of the multiple network slices is within a predetermined interval to identify that the multiple network slices correspond to the same PDU session.
  • the predetermined interval needs to be different from the value interval of the identification information of the ordinary network slice (the ordinary network slice is a network slice carried in the message sent by the user equipment in the current solution).
  • an indication bit is included in the SST field in the identification information of the multiple network slices to indicate that the multiple network slices correspond to the same PDU session.
  • an indication bit is included in the SD field in the identification information of the multiple network slices to indicate that the multiple network slices correspond to the same PDU session.
  • the AMF and UPF corresponding to the multiple network slices may be the same.
  • S220 it is determined whether the multiple network slices correspond to the same vehicle communication service according to the identification information of the multiple network slices.
  • the network side device may determine the multiple networks according to the indication of the service request message included in the connection establishment request Whether the slice corresponds to the same vehicle communication service.
  • the technical solution of the embodiment shown in FIG. 2 enables multiple network slices to share a PDU session, thereby enabling the user equipment to support more network slices by establishing multiple PDU sessions, and the number of network slices corresponds to the V2X use case The number, therefore, also increases the number of V2X use cases that user equipment can support, which is beneficial to the promotion and deployment of Internet of Vehicles solutions.
  • different QoS flows can be isolated by GTP-U protocol, VPN, or bandwidth management mechanism.
  • the network side device scheduling may be used to ensure that the user equipment uses different wireless transmission resources for different network slices, the wireless transmission resources including the time domain Resources and frequency domain resources.
  • a wireless transmission resource pool may also be configured for different network slices, so that user equipment uses different wireless transmission resources for different network slices, where
  • the priority and resource size of the wireless transmission resource pool have a positive correlation with the priority of the corresponding network slice, and the resource size of the wireless transmission resource pool has a positive correlation with the priority of the corresponding network slice. For example, if the priority and / or resources of the wireless transmission resource pool are larger, the priority of the corresponding network slice is also larger.
  • configuration signaling may be sent to user equipment to configure the user equipment with wireless transmission resource pools corresponding to the different network slices.
  • the wireless transmission resource pool corresponding to the different network slices can be pre-configured to the user equipment.
  • the configuration signaling may indicate different ones in an explicit manner or an implicit manner
  • the explicit way is to directly indicate the wireless transmission resource pools corresponding to different network slices; the implicit way may be to sequentially indicate multiple wireless transmission resource pools in sequence, and the multiple wireless transmission resource pools respectively correspond to Different network slices.
  • the above configuration signaling may be Radio Resource Control (RRC) signaling or Non-Access Stratum (NAS) signaling.
  • RRC Radio Resource Control
  • NAS Non-Access Stratum
  • the number of network slices supported by the user equipment can also be expanded by expanding the number of data radio bearers (Data Radio Bearer, DRB).
  • Data Radio Bearer Data Radio Bearer
  • FIG. 3 schematically shows a flowchart of a vehicle communication method according to an embodiment of the present application.
  • the vehicle communication method may be executed by a network-side device, such as a base station, a core network device, or an application server at the edge of the network .
  • the vehicle communication method includes at least S310 to S320, which are described in detail as follows:
  • step S310 a connection establishment request sent by the user equipment is received, where the connection establishment request carries identification information of the virtual bundled network slice.
  • the user equipment may be a vehicle terminal, and the connection establishment request sent by the user equipment may be a request to establish a PDU session.
  • the identification information of the network slice may be S-NSSAI.
  • the virtual bundled network slice corresponds to multiple real-world network slices, specifically, the multiple real-world network slices are bundled to obtain a network corresponding to the multiple real-world networks.
  • the sliced virtual network slice is called a virtual bundled network slice.
  • the identification information of the virtual bundled network slice may also be S-NSSAI.
  • the network side device may send information of available network slices (such as Allowed NSSAI) to the user equipment, the available network slice information includes The identification information of the virtual bundled network slice is convenient for the user equipment to select from the available network slice information.
  • available network slices such as Allowed NSSAI
  • the connection establishment request in the embodiment of the present application can have the following configurations:
  • the value interval of the identification information of the virtual bundled network slice is within a predetermined interval to indicate that the virtual bundled network slice corresponds to multiple network slices.
  • the predetermined interval needs to be different from the value interval of the identification information of the ordinary network slice (the ordinary network slice is a network slice carried in the message sent by the user equipment in the current solution).
  • an indication bit is included in the SST field in the identification information of the virtual bundled network slice to indicate that the virtual bundled network slice corresponds to multiple network slices.
  • an indication bit is included in the SD field in the identification information of the virtual bundled network slice to indicate that the virtual bundled network slice corresponds to multiple network slices.
  • step S320 the identification information of a plurality of network slices corresponding to the virtual bundled network slice is determined according to the identification information of the virtual bundled network slice to establish a connection with the user based on the plurality of network slices PDU session between devices.
  • the identification information of multiple network slices corresponding to the virtual bundled network slice may be determined according to the pre-configured correspondence.
  • one network slice may correspond to one PDU session, or multiple The network slice corresponds to a PDU session.
  • the technical solution of the embodiment shown in FIG. 3 enables the user equipment to support more network slices through virtual bundled network slices corresponding to multiple network slices, and the number of network slices corresponds to the number of vehicle communication use cases, thus also increasing The number of vehicle communication use cases that user equipment can support is conducive to the promotion and deployment of Internet of Vehicles solutions.
  • Embodiment 1 Expand the number of network slices that the UE can support in parallel.
  • the limitation of 3GPP Rel-15 on the number of network slices supported by the UE mainly considers the number of DRBs and the network slices introduced to reduce the impact on the specifications of the radio access network (Radio Access Network, RAN) side. Restrictions on PDU sessions.
  • the purpose of expanding the number of network slices that the UE can support can be achieved by expanding the number of DRBs.
  • the number of DRBs can be expanded to 32, and the number of slices supported by the UE can also be supported to 32.
  • Embodiment 2 Introduce a mechanism where multiple network slices share the same PDU session.
  • a network slice supporting shared PDU sessions may be introduced, that is, establishment of multiple network slices is carried through the same PDU session.
  • One of the prerequisites for adopting this solution is that the AMFs corresponding to different V2X use cases / network slices are the same, and the UPFs corresponding to different V2X use cases / network slices are also the same.
  • multiple network slices sharing a PDU session need to be reflected in Allowed NSSAI.
  • multiple network slices sharing a PDU session need to be identified and distinguished from other network slices (ie, network slices that do not share a PDU session) at the protocol level.
  • the network slice sharing the PDU session still uses 24 bits S-NSSAI, it can be distinguished in different ways.
  • the value interval of the S-NSSAI of the network slice sharing the PDU session may be separated from the value interval of the S-NSSAI of the ordinary network slice; or an indication bit area may be introduced, such as defining a new SST to identify Add corresponding identification bits in the SST; or you can add corresponding identification bits in the SD part to distinguish.
  • the connection establishment process of multiple network slices sharing a PDU session is different from the connection establishment process of a common network slice. Specifically, it is different from the MSG5RRC Setup message completed by 3GPP Rel-15 with only one S-NSSAI for AMF selection.
  • the UE when the UE initiates a connection establishment request to the network side device, it may carry multiple S-NSSAIs, and the network side device (such as a base station or AMF) receives the MSG5 containing multiple S-NSSAIs.
  • V2X use cases / network slices can establish different QoS flows.
  • 5G core network equipment can realize the isolation between different QoS flows through GTP-U tunnel, VPN or bandwidth management mechanism.
  • the wireless side (such as the base station gNB) can implement isolation between different network slices in a scheduling manner.
  • the wireless side may configure corresponding shared resource pools for different network slices to achieve isolation between different network slices.
  • the priority and resource size of the shared resource pool configured on the wireless side can reflect the priority between different slices.
  • the wireless side configuration can configure the shared resource pool corresponding to different network slices through signaling (such as RRC signaling, NAS signaling, etc.) or pre-configuration, and the correspondence between the network slice and the shared resource pool can be explicit Is given in configuration signaling or implicitly.
  • part of the signaling process for establishing a PDU session between the user equipment and the network-side device may be as shown in FIG. 5, where the interaction between the user equipment and the base station
  • the signaling (such as RRC message) contains information about the network slice, which may include the following steps:
  • the base station sends an NG setup request (that is, NG Setup Request) to AMF1, where the NG setup request carries the supported S-NSSAI list.
  • NG setup request that is, NG Setup Request
  • AMF1 returns an NG setup response message (ie, NG Setup Response) to the base station.
  • the NG setup response message carries the supported S-NSSAI list.
  • the base station sends an NG setup request (that is, NG Setup Request) to AMF2, and the NG setup request carries the supported S-NSSAI list.
  • NG setup request that is, NG Setup Request
  • AMF2 returns an NG setup response message (that is, NG Setup Response) to the base station, and the NG setup response message carries the supported S-NSSAI list.
  • NG setup response message that is, NG Setup Response
  • the base station identifies a network slicing strategy and identifies CN (Core Network) nodes supporting related network slicing; or selects the default CN node.
  • the network slicing strategy identified by the base station is to identify whether multiple network slices need to be carried through the same PDU session.
  • the base station sends an initial UE message (that is, Initial UE Message) to AMF1.
  • an initial UE message that is, Initial UE Message
  • AMF1 verifies the UE authority and the availability of network slices.
  • Embodiment 3 Introduce virtual bundled network slices.
  • the virtual bundled network slice corresponds to a plurality of V2X use case network slices corresponding to one virtual bundled network slice.
  • the correspondence between the virtual bundled network slice and multiple V2X use case network slices can be maintained only on the network side.
  • the virtual bundled network slice needs to be identified and distinguished from other network slices (that is, network slices that are not virtually bundled) at the protocol level.
  • the virtual bundled network slice still uses 24 bits S-NSSAI, it can be distinguished in different ways.
  • the value interval of the S-NSSAI of the virtual bundled network slice can be separated from the value interval of the S-NSSAI of the ordinary network slice; or an indicator bit area can be introduced, such as defining a new SST to be included in the new SST Add the corresponding identification bit; or you can add the corresponding identification bit in the SD part to distinguish.
  • the information of the virtual bundled network slice can be maintained only on the network side, and the same as the network slice of the shared PDU session (that is, the above embodiment 2) is that the network slice corresponding to different V2X use cases It will still be maintained in the core network, but the UE on the wireless side does not need to maintain all the network slices corresponding to V2X use cases in Allowed NSSAI, but can only include virtual bundled network slices, and the network slices corresponding to multiple V2X use cases are The wireless side is bundled into one.
  • the connection establishment process of the virtual bundled network slice is different from the connection establishment process of the ordinary network slice. Specifically, it is different from the MSG5 RRC Setup Setup Complete message proposed by 3GPP Rel-15 with only one S-NSSAI for AMF selection.
  • the network-side device such as a base station or AMF
  • receives the virtual bundled network slice in the MSG5 message when the UE initiates connection establishment to the network, it only carries one virtual bundled network slice, and the network-side device (such as a base station or AMF) receives the virtual bundled network slice in the MSG5 message. Introduce new functions to identify multiple corresponding V2X use case network slices, for example, according to the correspondence between virtual bundled network slices and V2X use case network slices.
  • the network-side device (such as a base station or AMF) can determine the correspondence between the virtual bundled network slice and multiple V2X use case network slices, the isolation between the network slices can still be guaranteed .
  • part of the signaling process for establishing a PDU session between the user equipment and the network-side device may also be as shown in FIG. 5, where, in S506, the base station recognizes
  • the network slicing strategy is to identify multiple V2X use case network slices corresponding to the virtual bundled network slices.
  • the technical solutions of the above-mentioned embodiments of the present application are suitable for future deployment scenarios based on network slicing in 5G Internet of Vehicles and autonomous driving, which can effectively overcome the restrictive problem of network slicing proposed in 3GPP Rel-15 and improve the support of user equipment
  • the number of V2X use cases, and make V2X use cases can use network slicing mechanism to achieve isolation, which is beneficial to the promotion and deployment of Internet of Vehicles solutions.
  • FIG. 6 schematically shows a block diagram of a vehicle communication device according to an embodiment of the present application.
  • a vehicle communication device 600 includes a receiving unit 602, a determining unit 604, and a processing unit 606.
  • the receiving unit 602 is used to receive a connection establishment request sent by the user equipment, where the connection establishment request carries identification information of multiple network slices; the determining unit 604 is used to determine the connection information according to the identification information of the multiple network slices Whether multiple network slices correspond to the same vehicle communication service; the processing unit 606 is configured to establish a PDU session with the user equipment when determining that the multiple network slices correspond to the same vehicle communication service.
  • the value interval of the identification information of the multiple network slices is within a predetermined interval to identify that the multiple network slices correspond to the same PDU session; or the identification of the multiple network slices
  • the SST field in the information includes an indicator bit to indicate that the multiple network slices correspond to the same PDU session; or the SD field in the identification information of the multiple network slices includes an indicator bit to indicate the multiple One network slice corresponds to the same PDU session.
  • the processing unit 606 is further configured to: in the PDU session, control different network slices or different use cases corresponding to different QoS flows.
  • the processing unit 606 is further used to isolate different QoS flows through the GTP-U protocol, VPN, or bandwidth management mechanism.
  • the vehicle communication device 600 further includes: a scheduling unit, configured to schedule the user equipment to use different wireless transmission resources for different network slices.
  • the vehicle communication device 600 further includes: a configuration unit configured to configure a wireless transmission resource pool for different network slices, so that the user equipment uses different wireless for different network slices Transmission resources, wherein the priority of the wireless transmission resource pool has a positive correlation with the priority of the corresponding network slice, and the resource size of the wireless transmission resource pool has a positive correlation with the priority of the corresponding network slice.
  • a configuration unit configured to configure a wireless transmission resource pool for different network slices, so that the user equipment uses different wireless for different network slices Transmission resources, wherein the priority of the wireless transmission resource pool has a positive correlation with the priority of the corresponding network slice, and the resource size of the wireless transmission resource pool has a positive correlation with the priority of the corresponding network slice.
  • the configuration unit is configured to: send configuration signaling to the user equipment to configure the user equipment with wireless transmission resource pools corresponding to the different network slices; or to the user equipment The user equipment pre-configures the wireless transmission resource pool corresponding to the different network slices.
  • the configuration unit is configured to: the configuration signaling sent to the user equipment is used to indicate the wireless corresponding to the different network slices in an explicit manner or an implicit manner Transmission resource pool.
  • the vehicle communication device 600 further includes: a sending unit, configured to send information of available network slices to the user equipment, the information of the available network slices including the plurality of networks The identification information of the slice.
  • the AMF and UPF corresponding to the multiple network slices are the same.
  • the vehicle communication device 600 further includes: an expansion unit, configured to expand the number of data wireless bearers to expand the number of network slices supported by the user equipment.
  • FIG. 7 schematically shows a block diagram of a vehicle communication device according to an embodiment of the present application.
  • a vehicle communication device 700 includes a receiving unit 702 and a processing unit 704.
  • the receiving unit 702 is used to receive a connection establishment request sent by the user equipment, where the connection establishment request carries identification information of the virtual bundled network slice; the processing unit 704 is used to determine the The identification information of the plurality of network slices corresponding to the virtual bundled network slice to establish a PDU session with the user equipment based on the plurality of network slices.
  • the processing unit 704 is configured to: according to the pre-configured correspondence, determine the identification information of the plurality of network slices corresponding to the virtual bundled network slice.
  • the vehicle communication device 700 further includes: a sending unit, configured to send information of available network slices to the user equipment, the information of the available network slices including the virtual bundled network The identification information of the slice.
  • the value interval of the identification information of the virtual bundled network slice is within a predetermined interval to indicate that the virtual bundled network slice corresponds to multiple network slices; or An indication bit is included in the SST field in the identification information to indicate that the virtual bundled network slice corresponds to multiple network slices; or an indication bit is included in the SD field in the identification information of the virtual bundled network slice to indicate the The virtual bundled network slice corresponds to multiple network slices.
  • FIG. 8 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application.
  • the computer system 800 includes a central processing unit (Central Processing Unit, CPU) 801, which can be loaded into the random portion according to the program stored in the read-only memory (Read-Only Memory, ROM) 802 or from the storage section 808 Random Access (RAM) 803 programs are accessed to perform various appropriate actions and processes. In RAM 803, various programs and data required for system operation are also stored.
  • the CPU 801, ROM 802, and RAM 803 are connected to each other through a bus 804.
  • An input / output (Input / Output, I / O) interface 805 is also connected to the bus 804.
  • the following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc .; an output section 807 including a cathode ray tube (Cathode Ray Tube, CRT), liquid crystal display (Liquid Crystal Display, LCD), etc.
  • a storage section 808 including a hard disk, etc .; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card, modem, etc.
  • the communication section 809 performs communication processing via a network such as the Internet.
  • the driver 810 is also connected to the I / O interface 805 as needed.
  • a removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is installed on the drive 810 as necessary, so that a computer program read out therefrom is installed into the storage portion 808 as necessary.
  • the process described below with reference to the flowchart may be implemented as a computer software program.
  • the embodiments of the present application include a computer program product including a computer program carried on a computer-readable medium, the computer program containing program code for performing the method shown in the flowchart.
  • the computer program may be downloaded and installed from the network through the communication section 809, and / or installed from the removable medium 811.
  • CPU central processing unit
  • the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two.
  • the computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above.
  • Computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer diskettes, hard drives, random access memory (RAM), read-only memory (ROM), erasable Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage device, magnetic storage device, or any suitable The combination.
  • the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • the computer-readable signal medium may include a data signal propagated in the baseband or as part of the carrier wave, in which the computer-readable program code is carried.
  • This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above.
  • the computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, and the computer-readable medium may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. .
  • the program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
  • each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the above-mentioned module, program segment, or part of code contains one or more for implementing a specified logical function Executable instructions.
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession can actually be executed in parallel, and sometimes they can also be executed in reverse order, depending on the functions involved.
  • each block in the block diagram or flowchart, and a combination of blocks in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be used It is realized by a combination of dedicated hardware and computer instructions.
  • the units described in the embodiments of the present application may be implemented in software or hardware, and the described units may also be provided in a processor. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances.
  • the present application also provides a computer-readable medium, which may be contained in the electronic device described in the foregoing embodiments; or may exist alone without being assembled into the electronic device in.
  • the computer-readable medium carries one or more programs. When the one or more programs are executed by one electronic device, the electronic device causes the electronic device to implement the method described in the foregoing embodiments.
  • the example embodiments described herein can be implemented by software, or can be implemented by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to enable a computing device (which may be a personal computer, server, touch terminal, or network device, etc.) to perform the method according to the embodiments of the present application.
  • a computing device which may be a personal computer, server, touch terminal, or network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请的实施例提供了一种车辆通信方法、装置、计算机可读介质及电子设备。该车辆通信方法可以应用于网络侧设备，所述方法包括：接收用户设备发送的连接建立请求，所述连接建立请求中携带有多个网络切片的标识信息；根据所述多个网络切片的标识信息确定所述多个网络切片是否对应于同一个车辆通信业务；若确定所述多个网络切片对应于同一个车辆通信业务，则建立与所述用户设备之间的一个PDU会话。本申请实施例的技术方案提高了用户设备能够支持的车辆通信用例的数量，有利于车联网方案的推广及部署。

Description

车辆通信方法、装置、计算机可读介质及电子设备
本申请要求于2018年10月08日提交中国专利局、申请号为201811169725.8、申请名称为“车辆通信方法、装置、计算机可读介质及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机及通信技术领域，具体而言，涉及一种车辆通信方法、装置、计算机可读介质及电子设备。
背景技术
5G车联网包括了20多种不同的车辆对外界(vehicle to X，V2X)用例(use case)，不同的use case有不同的服务质量(Quality of Service，QoS)需求。而不同V2X use case因为不同的QoS可能使用不同的网络切片，并且V2X use case的数量远远大于8个。但是，3GPP Rel-15规定了一个用户设备(User Equipment，UE)最多支持8个网络切片，而不同网络切片必须使用不同的协议数据单元(Protocol Data Unit，PDU)会话，这种假设具有较大的局限性，不利于车联网通信中网络切片的部署。
发明内容
本申请的实施例提供了一种车辆通信方法、装置、计算机可读介质及电子设备，进而至少在一定程度上可以提高用户设备能够支持的车辆通信用例的数量，有利于车联网方案的推广及部署。
本申请的其他特性和优点将通过下面的详细描述变得显然，或部分地通过本申请的实践而习得。
根据本申请实施例的一个方面，提供了一种车辆通信方法，应用于网络侧设备，包括：接收用户设备发送的连接建立请求，所述连接建立请求中携带有多个网络切片的标识信息；根据所述多个网络切片的标识信息确定所述多个网络切片是否对应于同一个车辆通信业务；若确定所述多个网络切片对应于同一个车辆通信业务，则建立与所述用户设备之间的一个PDU会话。
根据本申请实施例的一个方面，提供了一种车辆通信方法，应用于网络侧设备，包括：接收用户设备发送的连接建立请求，所述连接建立请求中携带有 虚拟捆绑网络切片的标识信息；根据所述虚拟捆绑网络切片的标识信息确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息，以基于所述多个网络切片建立与所述用户设备之间的PDU会话。
根据本申请实施例的一个方面，提供了一种车辆通信装置，包括：接收单元，用于接收用户设备发送的连接建立请求，所述连接建立请求中携带有多个网络切片的标识信息；确定单元，用于根据所述多个网络切片的标识信息确定所述多个网络切片是否对应于同一个车辆通信业务；处理单元，用于在确定所述多个网络切片对应于同一个车辆通信业务时，建立与所述用户设备之间的一个PDU会话。
在本申请的一些实施例中，基于前述方案，所述多个网络切片的标识信息的取值区间处于预定区间内，以标识所述多个网络切片对应于同一个PDU会话；或所述多个网络切片的标识信息中的切片/服务类型(Slice/Service Type，SST)字段中包含有指示位，以指示所述多个网络切片对应于同一个PDU会话；或所述多个网络切片的标识信息中的切片区分(Slice Differentiator，SD)字段中包含有指示位，以指示所述多个网络切片对应于同一个PDU会话。
在本申请的一些实施例中，基于前述方案，所述处理单元还用于：在所述PDU会话中，控制不同的网络切片或不同的车辆通信use case对应于不同的QoS flow。
在本申请的一些实施例中，基于前述方案，所述处理单元还用于：通过GPRS通道协议-用户面(GPRS Tunnel Protocol User Plane，GTP-U)、虚拟专用网络(Virtual Private Network，VPN)或带宽管理机制对不同的所述QoS flow进行隔离。
在本申请的一些实施例中，基于前述方案，所述的车辆通信装置还包括：调度单元，用于调度所述用户设备针对不同的网络切片使用不同的无线传输资源。
在本申请的一些实施例中，基于前述方案，所述的车辆通信装置还包括：配置单元，用于针对不同的网络切片配置无线传输资源池，以使所述用户设备针对不同的网络切片使用不同的无线传输资源，其中，所述无线传输资源池的优先级与对应的网络切片的优先级成正相关关系，所述无线传输资源池的资源 大小与对应的网络切片的优先级成正相关关系。
在本申请的一些实施例中，基于前述方案，所述配置单元配置为：向所述用户设备发送配置信令，以向所述用户设备配置所述不同的网络切片对应的无线传输资源池；或向所述用户设备预配置所述不同的网络切片对应的无线传输资源池。
在本申请的一些实施例中，基于前述方案，所述配置单元配置为：向所述用户设备发送的所述配置信令用于通过显式的方式或隐式的方式指示所述不同的网络切片对应的无线传输资源池。
在本申请的一些实施例中，基于前述方案，所述车辆通信装置还包括：发送单元，用于向所述用户设备发送可用的网络切片的信息，所述可用的网络切片的信息包含所述多个网络切片的标识信息。
在本申请的一些实施例中，基于前述方案，所述多个网络切片对应的接入和移动性功能实体(Access and Mobility Function，AMF)和用户面功能实体(User Plane Function，UPF)相同。
在本申请的一些实施例中，基于前述方案，所述的车辆通信装置还包括：扩展单元，用于扩展数据无线承载的数量，以扩展所述用户设备支持的网络切片的数量。
根据本申请实施例的一个方面，提供了一种车辆通信装置，包括：接收单元，用于接收用户设备发送的连接建立请求，所述连接建立请求中携带有虚拟捆绑网络切片的标识信息；处理单元，用于根据所述虚拟捆绑网络切片的标识信息确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息，以基于所述多个网络切片建立与所述用户设备之间的PDU会话。
在本申请的一些实施例中，基于前述方案，所述处理单元配置为：根据预配置的对应关系，确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息。
在本申请的一些实施例中，基于前述方案，所述车辆通信装置还包括：发送单元，用于向所述用户设备发送可用的网络切片的信息，所述可用的网络切片的信息包含所述虚拟捆绑网络切片的标识信息。
在本申请的一些实施例中，基于前述方案，所述虚拟捆绑网络切片的标识 信息的取值区间处于预定区间内，以指示所述虚拟捆绑网络切片对应于多个网络切片；或所述虚拟捆绑网络切片的标识信息中的SST字段中包含有指示位，以指示所述虚拟捆绑网络切片对应于多个网络切片；或所述虚拟捆绑网络切片的标识信息中的SD字段中包含有指示位，以指示所述虚拟捆绑网络切片对应于多个网络切片。
根据本申请实施例的一个方面，提供了一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如上述实施例中所述的车辆通信方法。
根据本申请实施例的一个方面，提供了一种电子设备，包括：一个或多个处理器；存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如上述实施例中所述的车辆通信方法。
在本申请的一些实施例所提供的技术方案中，网络侧设备通过接收用户设备发送的连接建立请求，并在确定该连接建立请求中包含的多个网络切片的标识信息对应于同一个车辆通信业务时，建立与用户设备之间的一个PDU会话，使得多个网络切片能够共享一个PDU会话，进而使得用户设备能够通过建立多个PDU会话来支持更多的网络切片，而网络切片的数量对应于车辆通信用例的数量，因此也提高了用户设备能够支持的车辆通信用例的数量，有利于车联网方案的推广及部署。
在本申请的一些实施例所提供的技术方案中，网络侧设备通过接收用户设备发送的连接建立请求，并根据连接建立请求中携带的虚拟捆绑网络切片的标识信息确定虚拟捆绑网络切片对应的多个网络切片的标识信息，使得用户设备能够通过对应于多个网络切片的虚拟捆绑网络切片来支持更多的网络切片，而网络切片的数量对应于车辆通信用例的数量，因此也提高了用户设备能够支持的车辆通信用例的数量，有利于车联网方案的推广及部署。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请 的实施例，并与说明书一起用于解释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。在附图中：
图1示出了可以应用本申请实施例的技术方案的示例性系统架构的示意图；
图2示意性示出了根据本申请的一个实施例的车辆通信方法的流程图；
图3示意性示出了根据本申请的一个实施例的车辆通信方法的流程图；
图4示出了根据本申请的一个实施例的车辆通信方法的应用场景示意图；
图5示出了根据本申请的实施例的用户设备与网络侧设备之间建立PDU会话的部分信令流程示意图；
图6示意性示出了根据本申请的一个实施例的车辆通信装置的框图；
图7示意性示出了根据本申请的一个实施例的车辆通信装置的框图；
图8示出了适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
具体实施方式
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施方式使得本申请将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。
此外，所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施例中。在下面的描述中，提供许多具体细节从而给出对本申请的实施例的充分理解。然而，本领域技术人员将意识到，可以实践本申请的技术方案而没有特定细节中的一个或更多，或者可以采用其它的方法、组元、装置、步骤等。在其它情况下，不详细示出或描述公知方法、装置、实现或者操作以避免模糊本申请的各方面。
附图中所示的方框图仅仅是功能实体，不一定必须与物理上独立的实体相对应。即，可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
附图中所示的流程图仅是示例性说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解，而有的操作/步骤可以合并或部分合并，因此实际执行的顺序有可能根据实际情况改变。
图1示出了可以应用本申请实施例的技术方案的示例性系统架构的示意图。
如图1所示，系统架构可以包括车辆终端101、基站102、核心网设备103和应用服务器104。核心网设备103可以是5G核心网中的AMF等。
应该理解，图1中所示的车辆终端101、基站102、核心网设备103和应用服务器104的数目仅仅是示意性的。根据实现需要，可以具有任意数目的车辆终端101、基站102、核心网设备103和应用服务器104。
在本申请的一个实施例中，网络侧设备(如图1中所示的基站102、核心网设备103或应用服务器104)在接收到车辆终端101发送的连接建立请求后，若连接建立请求中携带有多个网络切片的标识信息，且确定这多个网络切片对应于同一个车辆通信业务，则可以建立与该车辆终端101之间的一个PDU会话，进而使得车辆终端101能够通过建立多个PDU会话来支持更多的网络切片，而网络切片的数量对应于V2X use case的数量，因此也提高了用户设备能够支持的V2X use case的数量，有利于车联网方案的推广及部署。
在本申请的另一个实施例中，网络侧设备(如图1中所示的基站102、核心网设备103或应用服务器104)在接收到车辆终端101发送的连接建立请求后，若连接建立请求中携带有虚拟捆绑网络切片的标识信息，则可以根据该虚拟捆绑网络切片的标识信息确定该虚拟捆绑网络切片对应的多个网络切片的标识信息，以基于该多个网络切片建立与车辆终端101之间的PDU会话，进而使得车辆终端101能够通过对应于多个网络切片的虚拟捆绑网络切片来支持更多的网络切片，而网络切片的数量对应于V2X use case的数量，因此也提高了用户设备能够支持的V2X use case的数量，有利于车联网方案的推广及部署。
以下对本申请实施例的技术方案的实现细节进行详细阐述：
图2示意性示出了根据本申请的一个实施例的车辆通信方法的流程图，该车辆通信方法可以由网络侧设备来执行，比如可以由基站、核心网设备或网络 边缘的应用服务器来执行。参照图2所示，该车辆通信方法至少包括S210至S230，详细介绍如下：
在S210中，接收用户设备发送的连接建立请求，所述连接建立请求中携带有多个网络切片的标识信息。
在本申请的一个实施例中，用户设备可以是车辆终端，用户设备发送的连接建立请求可以是建立PDU会话的请求。网络切片的标识信息可以是单个网络切片的选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)。
在本申请的一个实施例中，在接收用户设备发送的连接建立请求之前，网络侧设备可以向用户设备发送可用的网络切片的信息(如Allowed NSSAI)，该可用的网络切片的信息包含所述的多个网络切片的标识信息，以便于用户设备从可用的网络切片的信息中进行选择。
在本申请的一个实施例中，为了与目前方案中用户设备发送的消息中(如Rel-15 MSG5 RRC Setup Complete)仅携带一个网络切片的标识信息进行区分，本申请实施例中的连接建立请求中携带的多个网络切片的标识信息可以有如下几种配置：
配置1：
在本申请的一个实施例中，所述多个网络切片的标识信息的取值区间处于预定区间内，以标识所述多个网络切片对应于同一个PDU会话。该预定区间需要与普通的网络切片(普通的网络切片即目前方案中用户设备发送的消息所携带的一个网络切片)的标识信息的取值区间不相同。
配置2：
在本申请的一个实施例中，所述多个网络切片的标识信息中的SST字段中包含有指示位，以指示所述多个网络切片对应于同一个PDU会话。
配置3：
在本申请的一个实施例中，所述多个网络切片的标识信息中的SD字段中包含有指示位，以指示所述多个网络切片对应于同一个PDU会话。
在本申请的一个实施例中，所述多个网络切片对应的AMF和UPF可以是相同的。
继续参照图2所示，在S220中，根据所述多个网络切片的标识信息确定所述多个网络切片是否对应于同一个车辆通信业务。
在本申请的一个实施例中，若网络侧设备在接收到包含多个网络切片的标识信息的连接建立请求时，可以根据该连接建立请求中包含的业务请求消息的指示来确定该多个网络切片是否对应于同一个车辆通信业务。
继续参照图2所示，在S230中，若确定所述多个网络切片对应于同一个车辆通信业务，则建立与所述用户设备之间的一个PDU会话。
图2所示实施例的技术方案使得多个网络切片能够共享一个PDU会话，进而使得用户设备能够通过建立多个PDU会话来支持更多的网络切片，而网络切片的数量对应于V2X use case的数量，因此也提高了用户设备能够支持的V2X use case的数量，有利于车联网方案的推广及部署。
基于图2所示实施例的技术方案，在本申请的一个实施例中，当网络侧设备建立与用户设备之间的一个PDU会话之后，则在该PDU会话中，不同的网络切片或不同的V2X use case对应于不同的QoS flow。
在本申请的一个实施例中，若不同的网络切片或不同的V2X use case对应于不同的QoS flow，则可以通过GTP-U协议、VPN或带宽管理机制对不同的QoS flow进行隔离。
在本申请的一个实施例中，为了实现不同网络切片之间的隔离，可以通过网络侧设备调度的方式来确保用户设备针对不同的网络切片使用不同的无线传输资源，该无线传输资源包括时域资源和频域资源。
在本申请的另一个实施例中，为了实现不同网络切片之间的隔离，也可以针对不同的网络切片配置无线传输资源池，以使用户设备针对不同的网络切片使用不同的无线传输资源，其中，所述无线传输资源池的优先级和资源大小与对应的网络切片的优先级成正相关关系，所述无线传输资源池的资源大小与对应的网络切片的优先级成正相关关系。比如，若无线传输资源池的优先级和/或资源越大，则对应的网络切片的优先级也越大。
在本申请的一个实施例中，在针对不同的网络切片配置无线传输资源池时，可以向用户设备发送配置信令，以向所述用户设备配置所述不同的网络切片对应的无线传输资源池；或者可以向用户设备预配置所述不同的网络切片对 应的无线传输资源池。
在本申请的一个实施例中，在通过配置信令向用户设备配置不同的网络切片对应的无线传输资源池的情况下，该配置信令可以通过显式的方式或隐式的方式指示不同的网络切片对应的无线传输资源池。可选地，显式的方式即是直接指示不同的网络切片对应的无线传输资源池；隐式的方式可以是按照顺序依次指示多个无线传输资源池，这多个无线传输资源池分别对应于不同的网络切片。
在本申请的一个实施例中，上述的配置信令可以是无线资源控制(Radio Resource Control，RRC)信令或非接入层(Non-Access Stratum，NAS)信令。
在本申请的一个实施例中，还可以通过扩展数据无线承载(Data Radio Bearer，DRB)的数量来扩展用户设备支持的网络切片的数量。
图3示意性示出了根据本申请的一个实施例的车辆通信方法的流程图，该车辆通信方法可以由网络侧设备来执行，比如可以由基站、核心网设备或网络边缘的应用服务器来执行。参照图3所示，该车辆通信方法至少包括S310至S320，详细介绍如下：
在步骤S310中，接收用户设备发送的连接建立请求，该连接建立请求中携带有虚拟捆绑网络切片的标识信息。
在本申请的一个实施例中，用户设备可以是车辆终端，用户设备发送的连接建立请求可以是建立PDU会话的请求。网络切片的标识信息可以是S-NSSAI。
在本申请的一个实施例中，虚拟捆绑网络切片是与多个真实存在的网络切片相对应的，具体是将多个真实存在的网络切片进行捆绑，得到一个对应于这多个真实存在的网络切片的虚拟网络切片，将该虚拟网络切片称之为虚拟捆绑网络切片。虚拟捆绑网络切片的标识信息也可以是S-NSSAI。
在本申请的一个实施例中，在接收用户设备发送的连接建立请求之前，网络侧设备可以向所述用户设备发送可用的网络切片的信息(如Allowed NSSAI)，该可用的网络切片的信息包含所述虚拟捆绑网络切片的标识信息，以便于用户设备从可用的网络切片的信息中进行选择。
在本申请的一个实施例中，为了与目前方案中用户设备发送的消息中(如 Rel-15 MSG5 RRC Setup Complete)仅携带一个网络切片的标识信息进行区分，本申请实施例中的连接建立请求中携带的虚拟捆绑网络切片的标识信息可以有如下几种配置：
配置1：
在本申请的一个实施例中，虚拟捆绑网络切片的标识信息的取值区间处于预定区间内，以指示虚拟捆绑网络切片对应于多个网络切片。该预定区间需要与普通的网络切片(普通的网络切片即目前方案中用户设备发送的消息所携带的一个网络切片)的标识信息的取值区间不相同。
配置2：
在本申请的一个实施例中，虚拟捆绑网络切片的标识信息中的SST字段中包含有指示位，以指示所述虚拟捆绑网络切片对应于多个网络切片。
配置3：
在本申请的一个实施例中，虚拟捆绑网络切片的标识信息中的SD字段中包含有指示位，以指示虚拟捆绑网络切片对应于多个网络切片。
继续参照图3所示，在步骤S320中，根据虚拟捆绑网络切片的标识信息确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息，以基于所述多个网络切片建立与所述用户设备之间的PDU会话。
在本申请的一个实施例中，可以根据预配置的对应关系，确定虚拟捆绑网络切片对应的多个网络切片的标识信息。
在本申请的一个实施例中，在基于与虚拟捆绑网络切片对应的多个网络切片建立网络侧设备与用户设备之间的PDU会话时，可以一个网络切片对应于一个PDU会话，也可以多个网络切片对应于一个PDU会话。
图3所示实施例的技术方案使得用户设备能够通过对应于多个网络切片的虚拟捆绑网络切片来支持更多的网络切片，而网络切片的数量对应于车辆通信用例的数量，因此也提高了用户设备能够支持的车辆通信用例的数量，有利于车联网方案的推广及部署。
以下以在5G车联网的应用场景下，对本申请实施例的技术方案的实现细节进行阐述：
在本申请的实施例中，在5G车联网的应用场景中，对于包含了不同QoS 需求的V2X use case且V2X use case之间因涉及V2X安全需要通过切片化隔离以确保可靠传输，而V2X use case的数量大于UE允许上限的情况，可以采用以下实施例的技术方案来进行处理：
实施例1：扩展UE能够并行支持的网络切片数量。
3GPP Rel-15对UE支持的网络切片数量的限制主要是考虑了DRB数量以及为了减少对无线接入网(Radio Access Network，RAN)侧规范的影响而引入的网络切片在RAN侧必须使用不同的PDU会话的限制条件。而在本申请的实施例中，可以通过扩充DRB数量来实现扩展UE能够支持的网络切片数量的目的。比如，DRB数量可以扩展到32个，进而UE所支持的切片数量也可以支持到32个。
实施例2：引入多个网络切片共享同一PDU会话的机制。
在本申请的一个实施例中，可以引入支持共享PDU会话的网络切片，即多个网络切片的建立通过同一个PDU会话来承载。采取这种方案的前提之一是不同的V2X use case/网络切片对应的AMF是相同的，并且不同V2X use case/网络切片对应的UPF也是相同的。
在本申请的一个实施例中，共享PDU会话的多个网络切片都需要在Allowed NSSAI中体现。
在本申请的一个实施例中，共享PDU会话的多个网络切片需要在协议层面与其他网络切片(即不共享PDU会话的网络切片)进行标识和区分。
在本申请的一个实施例中，如果共享PDU会话的网络切片仍然使用24bits的S-NSSAI，则可以采取不同的方式来区分。可选地，共享PDU会话的网络切片的S-NSSAI的取值区间可以与普通网络切片的S-NSSAI的取值区间分开；或者可以引入指示比特区，如定义新的SST，以在新的SST中添加相应的标识位；或者可以在SD部分添加相应的标识位来进行区分。
在本申请的一个实施例中，共享PDU会话的多个网络切片的连接建立过程与普通的网络切片的连接建立过程不相同。具体地，与3GPP Rel-15提出的MSG5RRC Setup Complete消息中只带有一个S-NSSAI用于AMF进行选择的方案不同。在本申请实施例的技术方案中，UE向网络侧设备发起连接建立请求时，可以携带多个S-NSSAI，而网络侧设备(如基站或AMF等)收到包含多个 S-NSSAI的MSG5消息时，需要引入新的功能来辨识多个S-NSSAI归属于同一个V2X业务(比如可以通过该MSG5消息中包含的业务请求消息的指示来确定该多个S-NSSAI是否归属于同一个V2X业务)，进而只触发建立一个PDU会话。
在本申请的一个实施例中，如图4所示，在针对多个S-NSSAI建立一个PDU会话之后，不同的V2X use case/网络切片可以建立不同的QoS flow。并且5G核心网设备可以通过GTP-U隧道、VPN或者带宽管理机制来实现不同QoS flow之间的隔离。
此外，在本申请的一个实施例中，无线侧(如基站gNB)可以通过调度的方式实现不同网络切片之间的隔离。或者无线侧可以为不同网络切片配置对应的共享资源池，以实现不同网络切片之间的隔离。其中，无线侧配置的共享资源池的优先级和资源大小可以体现不同切片之间的优先级。并且，无线侧配置可以通过信令(如RRC信令、NAS信令等)或预配置的方式来配置不同网络切片对应的共享资源池，并且网络切片与共享资源池的对应关系可以是显式的在配置信令中给出或者隐式间隔给出。
基于实施例2的技术方案，在本申请的一个实施例中，用户设备与网络侧设备之间建立PDU会话的部分信令流程可以如图5所示，其中，用户设备与基站之间的交互信令(如RRC消息)中包含有网络切片的信息，具体可以包括如下步骤：
S501，基站向AMF1发送NG建立请求(即NG Setup Request)，该NG建立请求中携带有支持的S-NSSAI列表。
S502，AMF1向基站返回NG建立响应消息(即NG Setup Response)，该NG建立响应消息中携带有支持的S-NSSAI列表。
S503，基站向AMF2发送NG建立请求(即NG Setup Request)，该NG建立请求中携带有支持的S-NSSAI列表。
S504，AMF2向基站返回NG建立响应消息(即NG Setup Response)，该NG建立响应消息中携带有支持的S-NSSAI列表。
S505，基站和用户设备之间建立RRC连接。
S506，基站识别网络切片策略，并识别支持相关网络切片的CN(Core Network，核心网)节点；或者选择默认的CN节点。具体地，基站识别的网络 切片策略即为识别出是否需要多个网络切片通过同一个PDU会话来承载。
S507，基站向AMF1发送初始UE消息(即Initial UE Message)。
S508，AMF1验证UE权限和网络切片的可用性。
实施例3：引入虚拟捆绑网络切片。
在本申请的一个实施例中，虚拟捆绑网络切片是将多个V2X use case的网络切片对应于一个虚拟捆绑网络切片。而该虚拟捆绑网络切片与多个V2X use case网络切片的对应可以只在网络侧维护。
在本申请的一个实施例中，虚拟捆绑网络切片需要在协议层面与其他网络切片(即未进行虚拟捆绑的网络切片)进行标识和区分。
在本申请的一个实施例中，如果虚拟捆绑网络切片仍然使用24bits的S-NSSAI，则可以采取不同的方式来区分。可选地，虚拟捆绑网络切片的S-NSSAI的取值区间可以与普通网络切片的S-NSSAI的取值区间分开；或者可以引入指示比特区，如定义新的SST，以在新的SST中添加相应的标识位；或者可以在SD部分添加相应的标识位来进行区分。
在本申请的一个实施例中，虚拟捆绑网络切片的信息可以只在网络侧维护，与共享PDU会话的网络切片(即上述实施例2)的相同点在于，不同的V2X use case对应的网络切片在核心网仍然会维护，但是无线侧的UE并不需要在Allowed NSSAI中维护所有的V2X use case对应的网络切片，而可以只包含虚拟捆绑网络切片，进而多个V2X use case对应的网络切片在无线侧被捆绑成一个。
在本申请的一个实施例中，虚拟捆绑网络切片的连接建立过程与普通的网络切片的连接建立过程不相同。具体地，与3GPP Rel-15提出的MSG5 RRC Setup Complete消息中只带有一个S-NSSAI用于AMF进行选择的方案不同。在本申请实施例的技术方案中，UE向网络发起连接建立时，只携带一个虚拟捆绑网络切片，而网络侧设备(如基站或AMF等)收到MSG5消息中的虚拟捆绑网络切片时，需要引入新的功能来辨识所对应的多个V2X use case的网络切片，比如根据虚拟捆绑网络切片与V2X use case网络切片的对应关系来进行识别。
在本申请的一个实施例中，由于网络侧设备(如基站或AMF等)能够判别虚拟捆绑网络切片与多个V2X use case网络切片之间的对应关系，因此网络切片之间的隔离仍然可以保证。
基于实施例3的技术方案，在本申请的一个实施例中，用户设备与网络侧设备之间建立PDU会话的部分信令流程也可以如图5所示，其中，在S506中，基站识别的网络切片策略即为识别出虚拟捆绑网络切片对应的多个V2X use case网络切片。
本申请上述实施例的技术方案适用于未来5G车联网和自动驾驶中基于网络切片的部署实施场景中，可以有效克服3GPP Rel-15中提出的网络切片的限制性问题，提高了用户设备能够支持的V2X use case的数量，并且使得V2X use case可以使用网络切片机制来实现隔离，有利于车联网方案的推广及部署。
以下介绍本申请的装置实施例，可以用于执行本申请上述实施例中的车辆通信方法。对于本申请装置实施例中未披露的细节，请参照本申请上述的车辆通信方法的实施例。
图6示意性示出了根据本申请的一个实施例的车辆通信装置的框图。
参照图6所示，根据本申请的一个实施例的车辆通信装置600，包括：接收单元602、确定单元604和处理单元606。
其中，接收单元602用于接收用户设备发送的连接建立请求，所述连接建立请求中携带有多个网络切片的标识信息；确定单元604用于根据所述多个网络切片的标识信息确定所述多个网络切片是否对应于同一个车辆通信业务；处理单元606用于在确定所述多个网络切片对应于同一个车辆通信业务时，建立与所述用户设备之间的一个PDU会话。
在本申请的一个实施例中，所述多个网络切片的标识信息的取值区间处于预定区间内，以标识所述多个网络切片对应于同一PDU会话；或所述多个网络切片的标识信息中的SST字段中包含有指示位，以指示所述多个网络切片对应于同一PDU会话；或所述多个网络切片的标识信息中的SD字段中包含有指示位，以指示所述多个网络切片对应于同一PDU会话。
在本申请的一个实施例中，处理单元606还用于：在所述PDU会话中，控制不同的网络切片或不同的use case对应于不同的QoS flow。
在本申请的一个实施例中，处理单元606还用于：通过GTP-U协议、VPN或带宽管理机制对不同的所述QoS flow进行隔离。
在本申请的一个实施例中，所述的车辆通信装置600还包括：调度单元， 用于调度所述用户设备针对不同的网络切片使用不同的无线传输资源。
在本申请的一个实施例中，所述的车辆通信装置600还包括：配置单元，用于针对不同的网络切片配置无线传输资源池，以使所述用户设备针对不同的网络切片使用不同的无线传输资源，其中，所述无线传输资源池的优先级与对应的网络切片的优先级成正相关关系，所述无线传输资源池的资源大小与对应的网络切片的优先级成正相关关系。
在本申请的一个实施例中，所述配置单元配置为：向所述用户设备发送配置信令，以向所述用户设备配置所述不同的网络切片对应的无线传输资源池；或向所述用户设备预配置所述不同的网络切片对应的无线传输资源池。
在本申请的一个实施例中，所述配置单元配置为：向所述用户设备发送的所述配置信令用于通过显式的方式或隐式的方式指示所述不同的网络切片对应的无线传输资源池。
在本申请的一个实施例中，所述车辆通信装置600还包括：发送单元，用于向所述用户设备发送可用的网络切片的信息，所述可用的网络切片的信息包含所述多个网络切片的标识信息。
在本申请的一个实施例中，所述多个网络切片对应的AMF和UPF相同。
在本申请的一个实施例中，所述的车辆通信装置600还包括：扩展单元，用于扩展数据无线承载的数量，以扩展所述用户设备支持的网络切片的数量。
图7示意性示出了根据本申请的一个实施例的车辆通信装置的框图。
参照图7所示，根据本申请的一个实施例的车辆通信装置700，包括：接收单元702和处理单元704。
其中，接收单元702用于接收用户设备发送的连接建立请求，所述连接建立请求中携带有虚拟捆绑网络切片的标识信息；处理单元704用于根据所述虚拟捆绑网络切片的标识信息确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息，以基于所述多个网络切片建立与所述用户设备之间的PDU会话。
在本申请的一个实施例中，处理单元704配置为：根据预配置的对应关系，确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息。
在本申请的一个实施例中，所述车辆通信装置700还包括：发送单元，用于向所述用户设备发送可用的网络切片的信息，所述可用的网络切片的信息包 含所述虚拟捆绑网络切片的标识信息。
在本申请的一个实施例中，所述虚拟捆绑网络切片的标识信息的取值区间处于预定区间内，以指示所述虚拟捆绑网络切片对应于多个网络切片；或所述虚拟捆绑网络切片的标识信息中的SST字段中包含有指示位，以指示所述虚拟捆绑网络切片对应于多个网络切片；或所述虚拟捆绑网络切片的标识信息中的SD字段中包含有指示位，以指示所述虚拟捆绑网络切片对应于多个网络切片。
图8示出了适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
需要说明的是，图8示出的电子设备的计算机系统800仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图8所示，计算机系统800包括中央处理单元(Central Processing Unit，CPU)801，其可以根据存储在只读存储器(Read-Only Memory，ROM)802中的程序或者从存储部分808加载到随机访问存储器(Random Access Memory，RAM)803中的程序而执行各种适当的动作和处理。在RAM 803中，还存储有系统操作所需的各种程序和数据。CPU 801、ROM 802以及RAM 803通过总线804彼此相连。输入/输出(Input/Output，I/O)接口805也连接至总线804。
以下部件连接至I/O接口805：包括键盘、鼠标等的输入部分806；包括诸如阴极射线管(Cathode Ray Tube，CRT)、液晶显示器(Liquid Crystal Display，LCD)等以及扬声器等的输出部分807；包括硬盘等的存储部分808；以及包括诸如LAN(Local Area Network，局域网)卡、调制解调器等的网络接口卡的通信部分809。通信部分809经由诸如因特网的网络执行通信处理。驱动器810也根据需要连接至I/O接口805。可拆卸介质811，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器810上，以便于从其上读出的计算机程序根据需要被安装入存储部分808。
特别地，根据本申请的实施例，下文参考流程图描述的过程可以被实现为计算机软件程序。例如，本申请的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信部分809从网络上被下载和安装，和/或从可拆卸介质811被安装。在该计算机程序被中 央处理单元(CPU)801执行时，执行本申请的系统中限定的各种功能。
需要说明的是，本申请实施例所示的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、有线等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现，所描述的单元也可以设置在处理器中。其中，这些单元的名称在某种情况下并不构成对该单元本身的限定。
作为另一方面，本申请还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被一个该电子设备执行时，使得该电子设备实现上述实施例中所述的方法。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本申请的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、触控终端、或者网络设备等)执行根据本申请实施方式的方法。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (15)

  1. 一种车辆通信方法，其特征在于，所述车辆通信方法包括：
    网络侧设备接收用户设备发送的连接建立请求，所述连接建立请求中携带有多个网络切片的标识信息；
    所述网络侧设备根据所述多个网络切片的标识信息确定所述多个网络切片是否对应于同一个车辆通信业务；
    若确定所述多个网络切片对应于同一个车辆通信业务，则所述网络侧设备建立与所述用户设备之间的一个协议数据单元PDU会话。
  2. 根据权利要求1所述的车辆通信方法，其特征在于，所述多个网络切片的标识信息的取值区间处于预定区间内，以标识所述多个网络切片对应于同一个PDU会话；或
    所述多个网络切片的标识信息中的切片/服务类型SST字段中包含有指示位，以指示所述多个网络切片对应于同一个PDU会话；或
    所述多个网络切片的标识信息中的切片区分SD字段中包含有指示位，以指示所述多个网络切片对应于同一个PDU会话。
  3. 根据权利要求1所述的车辆通信方法，其特征在于，在所述PDU会话中，不同的网络切片或不同的车辆通信用例对应于不同的服务质量流QoSflow。
  4. 根据权利要求3所述的车辆通信方法，其特征在于，所述车辆通信方法还包括：
    所述网络侧设备通过GPRS隧道协议GTP-U、虚拟专用网络VPN或带宽管理机制对不同的所述QoS flow进行隔离。
  5. 根据权利要求1所述的车辆通信方法，其特征在于，所述车辆通信方法还包括：
    所述网络侧设备调度所述用户设备针对不同的网络切片使用不同的无线传输资源。
  6. 根据权利要求1所述的车辆通信方法，其特征在于，所述车辆通信方法还包括：
    所述网络侧设备针对不同的网络切片配置无线传输资源池，以使所述用户 设备针对不同的网络切片使用不同的无线传输资源，其中，所述无线传输资源池的优先级与对应的网络切片的优先级成正相关关系，所述无线传输资源池的资源大小与对应的网络切片的优先级成正相关关系。
  7. 根据权利要求6所述的车辆通信方法，其特征在于，所述网络侧设备针对不同的网络切片配置无线传输资源池，包括：
    所述网络侧设备向所述用户设备发送配置信令，以向所述用户设备配置所述不同的网络切片对应的无线传输资源池；或
    所述网络侧设备向所述用户设备预配置所述不同的网络切片对应的无线传输资源池。
  8. 一种车辆通信方法，其特征在于，所述车辆通信方法包括：
    网络侧设备接收用户设备发送的连接建立请求，所述连接建立请求中携带有虚拟捆绑网络切片的标识信息；
    所述网络侧设备根据所述虚拟捆绑网络切片的标识信息，确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息；
    所述网络侧设备基于所述多个网络切片建立与所述用户设备之间的协议数据单元PDU会话。
  9. 根据权利要求8所述的车辆通信方法，其特征在于，所述网络侧设备根据所述虚拟捆绑网络切片的标识信息，确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息，包括：
    所述网络侧设备根据预配置的对应关系，确定所述虚拟捆绑网络切片的标识信息对应的多个网络切片的标识信息。
  10. 根据权利要求8所述的车辆通信方法，其特征在于，
    所述虚拟捆绑网络切片的标识信息的取值区间处于预定区间内，以指示所述虚拟捆绑网络切片对应于多个网络切片；或
    所述虚拟捆绑网络切片的标识信息中的切片/服务类型SST字段中包含有指示位，以指示所述虚拟捆绑网络切片对应于多个网络切片；或
    所述虚拟捆绑网络切片的标识信息中的切片区分SD字段中包含有指示位，以指示所述虚拟捆绑网络切片对应于多个网络切片。
  11. 一种车辆通信装置，其特征在于，包括：
    接收单元，用于接收用户设备发送的连接建立请求，所述连接建立请求中携带有多个网络切片的标识信息；
    确定单元，用于根据所述多个网络切片的标识信息确定所述多个网络切片是否对应于同一个车辆通信业务；
    处理单元，用于在确定所述多个网络切片对应于同一个车辆通信业务时，建立与所述用户设备之间的一个协议数据单元PDU会话。
  12. 一种车辆通信装置，其特征在于，包括：
    接收单元，用于接收用户设备发送的连接建立请求，所述连接建立请求中携带有虚拟捆绑网络切片的标识信息；
    处理单元，用于根据所述虚拟捆绑网络切片的标识信息确定所述虚拟捆绑网络切片对应的多个网络切片的标识信息，以基于所述多个网络切片建立与所述用户设备之间的协议数据单元PDU会话。
  13. 一种计算机可读介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现如权利要求1至7中任一项所述的车辆通信方法；或实现如权利要求8至10中任一项所述的车辆通信方法。
  14. 一种电子设备，其特征在于，包括：
    一个或多个处理器；
    存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求1至7中任一项所述的车辆通信方法；或实现如权利要求8至10中任一项所述的车辆通信方法。
  15. 一种包括指令的计算机程序产品，当其在计算机上运行时，使得所述计算机执行权利要求1至7中任意一项所述的车辆通信方法，或者，使得所述计算机执行权利要求8至10中任意一项所述的车辆通信方法。
PCT/CN2019/091809 2018-10-08 2019-06-19 车辆通信方法、装置、计算机可读介质及电子设备 Ceased WO2020073678A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2020560135A JP7058833B2 (ja) 2018-10-08 2019-06-19 車両通信方法、装置、コンピュータ可読媒体、電子デバイス、及びコンピュータプログラム
EP19871415.6A EP3761608B1 (en) 2018-10-08 2019-06-19 Vehicle communication method, device, computer readable medium and electronic device
US17/075,612 US11445522B2 (en) 2018-10-08 2020-10-20 Vehicle communication method and apparatus, computer-readable medium, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811169725.8A CN109040322B (zh) 2018-10-08 2018-10-08 车辆通信方法、装置、计算机可读介质及电子设备
CN201811169725.8 2018-10-08

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/075,612 Continuation US11445522B2 (en) 2018-10-08 2020-10-20 Vehicle communication method and apparatus, computer-readable medium, and electronic device

Publications (1)

Publication Number Publication Date
WO2020073678A1 true WO2020073678A1 (zh) 2020-04-16

Family

ID=64615768

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/091809 Ceased WO2020073678A1 (zh) 2018-10-08 2019-06-19 车辆通信方法、装置、计算机可读介质及电子设备

Country Status (5)

Country Link
US (1) US11445522B2 (zh)
EP (1) EP3761608B1 (zh)
JP (1) JP7058833B2 (zh)
CN (1) CN109040322B (zh)
WO (1) WO2020073678A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118842828A (zh) * 2024-06-27 2024-10-25 岚图汽车科技有限公司 汽车型号识别方法、装置、设备及存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109040322B (zh) 2018-10-08 2021-05-11 腾讯科技（深圳）有限公司 车辆通信方法、装置、计算机可读介质及电子设备
CN113475039B (zh) * 2019-01-30 2023-02-03 华为技术有限公司 基于开放信息的网络和/或管理功能适配的装置和方法
CN113261361B (zh) * 2019-03-28 2023-04-11 华为技术有限公司 用于辅助侧行链路通信的控制单元和方法
EP4061024B1 (en) * 2019-12-31 2023-11-22 Huawei Technologies Co., Ltd. D2d communication method and apparatus
CN111294762B (zh) * 2020-01-23 2021-04-13 北京邮电大学 基于无线接入网络ran切片协作的车辆业务处理方法
CN113285876B (zh) * 2020-02-19 2024-04-23 中兴通讯股份有限公司 路由方法、路由装置及计算机可读存储介质
CN111698290B (zh) * 2020-05-19 2021-06-15 展讯通信(天津)有限公司 Pdu会话复用方法、装置、用户设备及存储介质
US11671876B2 (en) * 2020-05-29 2023-06-06 Dell Products, L.P. Classifying network traffic to use cellular network slices based on application parameters
TWI740713B (zh) * 2020-11-11 2021-09-21 財團法人工業技術研究院 網路切片的資源管理方法、資源管理系統及工作負載調度裝置
WO2022257133A1 (zh) * 2021-06-11 2022-12-15 北京小米移动软件有限公司 多终端共享pdu会话的方法、装置、通信设备及存储介质
CN113365245B (zh) * 2021-07-01 2024-03-22 腾讯科技（深圳）有限公司 应用于远程驾驶的通信方法、装置、介质及电子设备
CN114257618A (zh) * 2021-12-13 2022-03-29 航天科技控股集团股份有限公司 一种基于车联网平台的车辆运行数据实时分析系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
CN108307516A (zh) * 2016-09-30 2018-07-20 华为技术有限公司 数据传输方法及相关设备
CN108323245A (zh) * 2017-06-19 2018-07-24 华为技术有限公司 一种注册及会话建立的方法、终端和amf实体
WO2018141269A1 (en) * 2017-02-06 2018-08-09 Huawei Technologies Co., Ltd. Network registration and network slice selection system and method
CN109040322A (zh) * 2018-10-08 2018-12-18 腾讯科技（深圳）有限公司 车辆通信方法、装置、计算机可读介质及电子设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10512109B2 (en) * 2016-01-15 2019-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Transmitting communication device, receiving communication device and methods performed thereby
JP6725703B2 (ja) 2016-02-16 2020-07-22 アイディーエーシー ホールディングス インコーポレイテッド ネットワークスライシング操作
KR102650322B1 (ko) * 2016-11-11 2024-03-25 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 무선 통신 방법, 단말 기기 및 네트워크 기기
JP6889263B2 (ja) * 2017-01-27 2021-06-18 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ユーザ機器の二次認証
CN108696905B (zh) * 2017-02-20 2023-06-13 中兴通讯股份有限公司 一种无线资源的管理方法及装置
CN113784333B (zh) * 2017-10-16 2022-05-24 华为技术有限公司 一种移动性管理的方法、装置及系统
US10797894B2 (en) * 2017-12-28 2020-10-06 Ofinno, Llc Service type and device type-based policy and charging control
CN110121168B (zh) * 2018-02-06 2021-09-21 华为技术有限公司 安全协商方法及装置
KR102436652B1 (ko) * 2018-04-05 2022-08-29 삼성전자 주식회사 5g 시스템에서 차량 통신 서비스 제공 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
CN108307516A (zh) * 2016-09-30 2018-07-20 华为技术有限公司 数据传输方法及相关设备
WO2018141269A1 (en) * 2017-02-06 2018-08-09 Huawei Technologies Co., Ltd. Network registration and network slice selection system and method
CN108323245A (zh) * 2017-06-19 2018-07-24 华为技术有限公司 一种注册及会话建立的方法、终端和amf实体
CN109040322A (zh) * 2018-10-08 2018-12-18 腾讯科技（深圳）有限公司 车辆通信方法、装置、计算机可读介质及电子设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3GPP. ''Technical Specification Group Services and System Aspects; Study on Enhancement of Network Slicing(Release 16", 3GPP TR 23. 740, 5 September 2018 (2018-09-05), XP051475217 *
See also references of EP3761608A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118842828A (zh) * 2024-06-27 2024-10-25 岚图汽车科技有限公司 汽车型号识别方法、装置、设备及存储介质

Also Published As

Publication number Publication date
EP3761608A4 (en) 2021-07-14
CN109040322B (zh) 2021-05-11
US11445522B2 (en) 2022-09-13
JP2021519040A (ja) 2021-08-05
CN109040322A (zh) 2018-12-18
EP3761608A1 (en) 2021-01-06
JP7058833B2 (ja) 2022-04-25
EP3761608B1 (en) 2025-01-15
US20210037542A1 (en) 2021-02-04

Similar Documents

Publication Publication Date Title
WO2020073678A1 (zh) 车辆通信方法、装置、计算机可读介质及电子设备
EP3968700B1 (en) Network access control method, computer-readable medium and electronic device
CN108696950B (zh) 一种会话重建的方法、装置、amf、smf及终端
JP7669274B2 (ja) サイドリンク通信のサービス品質制御方法、装置、コンピュータプログラム及び電子機器
WO2018028342A1 (zh) 业务处理方法、装置、系统、基站、终端及核心网网元
CN109640289B (zh) 一种通信方法及设备、通信系统
CN110366254B (zh) 一种资源确定方法、相关设备及系统
WO2020029825A1 (zh) 资源调度方法、终端及网络设备
CN110859012A (zh) 一种速率控制的方法、装置和系统
WO2019179260A1 (zh) 一种载波中的资源选择方法及设备
CN116210276B (zh) 用于iab通信的设备、方法、装置和计算机可读介质
CN110234094B (zh) 一种资源配置方法、第一通信设备、第二通信设备及系统
JP7767608B2 (ja) 指示方法、データ伝送方法、通信ノードおよび記憶媒体
CN110933758A (zh) 一种干扰协调方法及装置、基站
WO2023011107A1 (zh) 会话策略控制方法、网元、存储介质和电子设备
CN114514764B (zh) 设备、方法和计算机程序
CN110708727B (zh) 搬迁管理方法及装置
WO2016201860A1 (zh) 数据传输方法及装置
CN115707143B (zh) 接入网切片的随机接入资源隔离方法、设备及介质
KR20230128989A (ko) 네트워크 슬라이스 지원 장치 및 그 지원 방법
CN115843073A (zh) 一种网络切片的选择方法、移动管理功能实体及终端
CN115297020B (zh) 通信控制方法及装置、电子设备、存储介质
CN116325551B (zh) 用于建立通信链路的设备、方法、装置和计算机可读介质
CN111491336B (zh) 一种配置QoS和数据传输的方法和设备
CN117255131A (zh) 基于切片进行业务请求的方法、装置、设备和可读介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19871415

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019871415

Country of ref document: EP

Effective date: 20201001

ENP Entry into the national phase

Ref document number: 2020560135

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE