WO2019033416A1 - 无线通信的方法、终端设备和网络设备 - Google Patents

无线通信的方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2019033416A1
WO2019033416A1 PCT/CN2017/098126 CN2017098126W WO2019033416A1 WO 2019033416 A1 WO2019033416 A1 WO 2019033416A1 CN 2017098126 W CN2017098126 W CN 2017098126W WO 2019033416 A1 WO2019033416 A1 WO 2019033416A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
carrier
transmitted
terminal device
identifier
Prior art date
Application number
PCT/CN2017/098126
Other languages
English (en)
French (fr)
Inventor
杨宁
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201780091771.8A priority Critical patent/CN110720229A/zh
Priority to US16/628,629 priority patent/US11178526B2/en
Priority to EP17921797.1A priority patent/EP3637807B1/en
Priority to PCT/CN2017/098126 priority patent/WO2019033416A1/zh
Publication of WO2019033416A1 publication Critical patent/WO2019033416A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50Service provisioning or reconfiguring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/02Selection of wireless resources by user or terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/51Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/56Allocation or scheduling criteria for wireless resources based on priority criteria
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA

Definitions

  • the present application relates to the field of communications, and more particularly to a method, terminal device and network device for wireless communication.
  • V2X vehicle to Everything
  • a specific V2X service can be mapped to a specific frequency for transmission.
  • PPPP ProSe Per Packet Priority
  • the access layer Access Statum, AS
  • PPPP logical channel priority
  • Each PPPP value corresponds to a logical channel group (LCG), and a packet with a high priority PPPP value can be used.
  • the transmission resource of a low priority packet for example, a resource on a carrier), and vice versa.
  • PPPP-based solutions may encounter many problems.
  • the PPPP value of the V2X service is the same. In this case, it is difficult to use the PPPP value to allocate resources on different carriers for different services.
  • the embodiment of the present application provides a method, a terminal device, and a network device for wireless communication, which can divide a V2X service into a service code point or a service primitive at a service layer, and map the V2X service according to a service code point or a service primitive. Transmission to different carriers, thereby overcoming the problem of being unable to allocate resources on different carriers for V2X services having more PPPP values due to the limited number of PPPP values.
  • an embodiment of the present application provides a method for wireless communication, including:
  • the terminal device determines, according to the service identifier of the service to be transmitted, a carrier or a carrier set that sends or receives the service to be transmitted;
  • the terminal device sends on the carrier or carrier set corresponding to the service identifier of the to-be-transmitted service or Receiving the to-be-transmitted service, where the service identifier of the to-be-transmitted service is a service code point or service primitive of the to-be-transmitted service generated at the service layer, where the service code point is a service generated by the to-be-transmitted service on the service layer Encoding, the business primitive is a textual description of the service generated by the to-be-transmitted service on the business layer.
  • the terminal device determines, according to the service code point or the service primitive of the to-be-transmitted service that is generated in the service layer, the carrier or the carrier set that sends or receives the service to be transmitted, and thus,
  • the services to be transmitted on the service layer correspond to different carriers or carrier sets, and the services to be transmitted can be transmitted on the carrier or carrier set in more granularity.
  • the number of PPPP values is limited and cannot be compared to PPPP.
  • the problem of multi-valued services allocating resources on different carriers.
  • the terminal device determines, according to the service identifier of the service to be transmitted, a carrier or a carrier set that sends or receives the service to be transmitted, including:
  • the terminal device classifies the to-be-transmitted service on the service layer, and assigns different service identifiers to different types of services;
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, a carrier or a carrier set for transmitting or receiving the to-be-transmitted service.
  • the terminal device determines, according to the service identifier of the service to be transmitted, a carrier or a carrier set that sends or receives the service to be transmitted, including:
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, whether to transmit or receive the carrier or carrier set of the to-be-transmitted service.
  • the terminal device may determine, according to the service identifier of the service to be transmitted, and the correspondence between the service identifier of the service to be transmitted and the carrier or the carrier set, determine whether to transmit or receive the carrier to be transmitted. Or carrier set.
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, determining to send or receive the Before the carrier or carrier set of the service to be transmitted, the method further includes:
  • the terminal device receives the first information sent by the network device, where the first information includes a correspondence between the service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the terminal device may receive, from the network device, a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, determining to send or receive the Before the carrier or carrier set of the service to be transmitted, the method further includes:
  • the terminal device classifies the to-be-transmitted service on the service layer, and assigns different service identifiers to different types of services, where the service identifier is a service code point or a service primitive;
  • the terminal device establishes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the terminal device itself may establish a correspondence between the service identifier of the service to be transmitted and the carrier or the carrier set.
  • the terminal device classifies the to-be-transmitted service on the service layer, including:
  • the terminal device divides the to-be-transmitted service into multiple service types on the service layer, and the number of the multiple service types is greater than the value of the single-packet preference-level PPPP.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is pre-configured.
  • the terminal device determines to send or receive the service identifier according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set.
  • the carrier or carrier set of the transport service including:
  • the terminal device receives the second information sent by the network device, where the second information indicates that the first carrier set is a carrier set used by the terminal device to transmit a service;
  • the terminal device determines, according to the first carrier set, the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, whether to transmit or receive the carrier or the carrier set of the to-be-transmitted service.
  • the second information is system information or radio resource control RRC information.
  • the terminal device determines to send or receive the service identifier according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set.
  • the carrier or carrier set of the transport service including:
  • the second carrier set is a pre-configured terminal device for the transmission industry. Carrier set.
  • the terminal device sends or receives the to-be-transmitted service on a carrier or a carrier set corresponding to the service identifier of the to-be-transmitted service, including:
  • the terminal device When the media access control MAC layer performs the logical channel priority LCP processing on the to-be-transmitted service, the terminal device performs the service to be transmitted according to the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set.
  • the service to be transmitted is transmitted on a transport block that identifies a corresponding carrier or carrier set.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is integrated in the mapping table.
  • mapping table further includes:
  • the information of the service to which the service identifier of the service to be transmitted belongs is copied or diverted.
  • the to-be-transmitted service is a vehicle to another terminal device V2X service.
  • the embodiment of the present application provides a method for wireless communication, including:
  • the network device establishes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set;
  • the network device sends the first information to the terminal device, where the first information includes a correspondence between the service identifier of the to-be-transmitted service and a carrier or a carrier set;
  • the service identifier of the to-be-transmitted service is a service code point or a service primitive of the to-be-transmitted service generated at the service layer, where the service code point is a code of a service generated by the to-be-transmitted service on the service layer, where the service original
  • the text is a textual description of the service generated by the to-be-transmitted service on the service layer.
  • the network device establishes a correspondence between a service identifier of a to-be-transmitted service and a carrier or a carrier set, and sets a service identifier of the service to be transmitted Corresponding relationship between the carrier or the carrier set is sent to the terminal device, so that the terminal device performs service transmission on the carrier or carrier set corresponding to the service to be transmitted, thereby overcoming the fact that the PPPP value cannot be more than the PPPP value due to the limited number of PPPP values.
  • the problem of allocating resources on different carriers is described by the terminal device performs service transmission on the carrier or carrier set corresponding to the service to be transmitted.
  • the method further includes:
  • the network device sends second information to the terminal device, where the second information indicates that the first carrier set is a carrier set used by the terminal device to transmit a service.
  • the second information is system information or radio resource control RRC information.
  • the network device establishes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set, including:
  • the network device classifies the to-be-transmitted service on the service layer, and assigns different service identifiers to different types of services, where the service identifier is a service code point or a service primitive;
  • the network device establishes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the network device classifies the to-be-transmitted service on the service layer, including:
  • the network device divides the to-be-transmitted service into multiple service types on the service layer, and the number of the multiple service types is greater than the value of the single-packet preference-level PPPP.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is integrated in the mapping table.
  • mapping table further includes:
  • the information of the service to which the service identifier of the service to be transmitted belongs is copied or diverted.
  • the to-be-transmitted service is a vehicle to another terminal device V2X service.
  • the embodiment of the present application provides a terminal device, which can execute the module or unit of the method in the first aspect or any optional implementation manner of the first aspect.
  • the embodiment of the present application provides a network device, which can execute the module or unit of the method in any of the optional implementations of the second aspect or the second aspect.
  • a terminal device comprising a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface.
  • the memory is for storing instructions for the processor to execute, and the communication interface is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a network device comprising a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface.
  • the memory is for storing instructions for the processor to execute, and the communication interface is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.
  • a computer storage medium storing program code for instructing a computer to perform the method of any of the first aspect or the first aspect of the first aspect. instruction.
  • a computer storage medium storing program code for instructing a computer to perform the method in any one of the possible implementation manners of the second aspect or the second aspect instruction.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the methods described in the various aspects above.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 2 is a schematic diagram of another application scenario of an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a correspondence between a service identifier of a to-be-transmitted service and a carrier or a carrier set according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another correspondence between a service identifier of a to-be-transmitted service and a carrier or a carrier set according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another correspondence between a service identifier of a to-be-transmitted service and a carrier or a carrier set according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a terminal device acquiring a carrier or a carrier set for transmitting a service according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another method of wireless communication according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of an apparatus for wireless communication provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a system chip according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the technical solution of the embodiment of the present application may be applied to a vehicle networking system, and the vehicle networking system may be based on the foregoing various communication systems, thereby implementing communication between a terminal and a terminal (Device to Device, D2D), for example, based on LTE. -D2D's car networking system.
  • D2D Device to Device
  • -D2D's car networking system Different from the manner in which communication data between terminals in a conventional LTE system is received or transmitted through a network device (for example, a base station), the car network system can adopt a terminal-to-terminal direct communication method, thereby having higher spectrum efficiency and lower. Transmission delay.
  • the D2D communication may refer to a vehicle to vehicle (V2V) communication or a vehicle to Everything (V2X) communication.
  • V2X communication X can refer to any device with wireless receiving and transmitting capabilities, such as but not limited to slow moving wireless devices, fast moving in-vehicle devices, or network control nodes with wireless transmit and receive capabilities. It should be understood that the embodiment of the present application is mainly applied to the scenario of V2X communication, but can also be applied to any other D2D communication scenario, which is not limited in this embodiment of the present application.
  • the terminal device in the embodiment of the present application may refer to an in-vehicle terminal device, and may also refer to other devices that communicate with the in-vehicle terminal device, for example, a terminal device in a future 5G network or a public land mobile communication network in the future (Public Land Mobile)
  • a terminal device in a future 5G network or a public land mobile communication network in the future Public Land Mobile
  • the terminal device in the network, the PLMN, and the like are not limited in the embodiment of the present application.
  • the present application describes various embodiments in connection with a network device.
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, where the network device may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB, NB) in a WCDMA system. And may be an evolved base station (eNB or eNodeB) in the LTE system, or may be a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be
  • the embodiments of the present application are not limited to the relay station, the access point, the in-vehicle device, the wearable device, and the network device in the future 5G network or the network device in the future evolved PLMN network.
  • FIG. 1 and FIG. 2 are schematic diagrams of an application scenario of an embodiment of the present application.
  • Fig. 1 exemplarily shows one network device and two terminal devices.
  • the wireless communication system in the embodiment of the present application may include multiple network devices, and the coverage of each network device may include other numbers of terminal devices, which is not limited in this embodiment of the present application.
  • the wireless communication system may further include other network entities such as a Mobile Management Entity (MME), a Serving Gateway (S-GW), and a Packet Data Network Gateway (P-GW).
  • MME Mobile Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • the terminal device 20 and the terminal device (other terminal) 30 can communicate through the D2D communication mode, and when the D2D communication is performed, the terminal device 20 and the terminal device 30 pass the D2D link, that is, the side link. (Sidelink, SL) communicates directly.
  • the terminal device 20 and the terminal device 30 directly communicate via a side line.
  • the terminal device 20 and the terminal device 30 communicate by side line communication, and their transmission resources (for example, carrier waves) are allocated by the network device; in FIG. 2, the terminal device 20 and the terminal device 30 communicates through the side line, and the transmission resource is selected by the terminal device autonomously (for example, the terminal device selects a carrier that can be used in the resource pool), and does not need the network device to allocate the transmission resource.
  • a terminal device having a listening capability such as a Vehicle User Equipment (VUE) or a Pedestrian User Equipment (PUE), and no listening.
  • VUE Vehicle User Equipment
  • PUE Pedestrian User Equipment
  • Capable terminal equipment such as PUE.
  • VUE has higher processing power and is usually powered by the battery in the car, while PUE has lower processing power, and reducing power consumption is also a major factor that PUE needs to consider. Therefore, in the existing car network system, VUE is considered to have Full reception and listening capabilities; while PUE is considered to have partial or no reception and listening capabilities.
  • the resource may be selected by using a similar listening method as the VUE, and the available resources may be selected on the part of the resources that can be intercepted; if the PUE does not have the listening capability, the PUE is in the resource pool. Randomly select transmission resources.
  • the V2X service can support the following three scenarios:
  • MAC PDUs Media Access Control Packet Data Units
  • a MAC PDU of a V2X service can be copied and transmitted on different carriers to improve reliability.
  • the support (1) needs to determine a set of carriers that can be offloaded for a specific service, and supports (2) determining a set of carriers that can be copied and transmitted for a specific service, and supporting (3) determining that the transmitting terminal device can be used.
  • To transmit the carrier or carrier set of data it is also necessary to explicitly receive the carrier set of the specific V2X service.
  • the corresponding carriers are allocated for different V2X services, and the V2X services need to be mapped to corresponding carriers to implement V2X services on specific carrier resources.
  • the term "article of manufacture” as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or media.
  • the computer readable medium may include, but is not limited to, a magnetic storage device (eg, a hard disk, a floppy disk, or a magnetic tape, etc.), such as a compact disc (CD), a digital versatile disc (Digital Versatile Disc, DVD). Wait), Smart cards and flash memory devices (eg, Erasable Programmable Read-Only Memory (EPROM), cards, sticks or key drivers, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, a variety of media capable of storing, containing, and/or carrying instructions and/or data.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • FIG. 3 is a schematic flowchart of a method 200 for wireless communication according to an embodiment of the present application.
  • the method 200 may be performed by a terminal device, which may be a terminal device as shown in FIG. 1 or FIG. 2, and the network device in the method 200 may be a network device as shown in FIG. .
  • the method 200 includes the following.
  • the terminal device determines, according to the service identifier of the service to be transmitted, a carrier or a carrier set that sends or receives the service to be transmitted.
  • the to-be-transmitted service is a V2X service.
  • the V2X service includes a service type such as a Cooperative Awareness Message (CAM) or a Decentralized Environmental Notification Message (DENM).
  • CAM Cooperative Awareness Message
  • DENM Decentralized Environmental Notification Message
  • the V2X service type may include formation driving, remote driving, sensor data sharing, and the like.
  • the service identifier of the to-be-transmitted service is a service code point or a service primitive of the to-be-transmitted service generated at the service layer, where the service code point is a code of a service generated by the to-be-transmitted service on the service layer, where The service primitive is a textual description of the service generated by the to-be-transmitted service on the service layer.
  • the service code point of the to-be-transmitted service may select a number of bits according to a potential service type, and may support more service type division.
  • the service code point of the to-be-transmitted service may be V2X.1, V2X.2, V2X.3...V2X.i...V2X.n.
  • the service primitive of the to-be-transmitted service may be text and may carry more service type information.
  • the service primitives of the to-be-transmitted service may be V2X.CAM1, V2X.CAM2...V2X.CAM m, V2X.DENM1, V2X.DENM2...V2X.DENM m, V2X.X 1...V2X .X m....
  • the carrier or carrier set for transmitting or receiving the to-be-transmitted service may be determined by:
  • the terminal device classifies the to-be-transmitted service on the service layer, and assigns different service identifiers to different types of services;
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, a carrier or a carrier set for transmitting or receiving the to-be-transmitted service.
  • the QoS requirement characteristics of the to-be-transmitted service in terms of delay, reliability, and the like may be considered.
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, whether to send or receive the carrier or carrier set of the to-be-transmitted service.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • V2X.CAM 1/V2X.1 corresponds to DRB 1
  • V2X.DENM 2/V2X.2 corresponds to DRB 2
  • V2X.CAM 2/V2X.3 corresponds to DRB 3
  • DRB 1 corresponds to logical channel identifier.
  • DRB 2 corresponds to LCID 2
  • DRB 3 corresponds to LCID 3
  • LCID 1 corresponds to carrier a
  • LCID 2 corresponds to carrier b
  • LCID 3 corresponds to carrier c, thereby implementing service identification from the to-be-transmitted service to carrier Or the correspondence of the carrier set.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • V2X.CAM 1/V2X.1 corresponds to LCID 1
  • V2X.CAM 2/V2X.2 corresponds to LCID 2
  • V2X.CAM 3/V2X.3 corresponds to LCID 3
  • LCID 1 corresponds to carrier a
  • the LCID 2 corresponds to the carrier b
  • the LCID 3 corresponds to the carrier c, thereby implementing the service identifier from the to-be-transmitted service to the Correspondence of a wave or carrier set.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the service identifier of the to-be-transmitted service directly corresponds to a carrier or a carrier set.
  • V2X.DENM 1/V2X.1 corresponds to carrier a
  • V2X.DENM 2/V2X.2 corresponds to carrier b
  • V2X.DENM 3/V2X.3 corresponds to carrier c.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is integrated in the mapping table.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or carrier set is determined according to the mapping table as shown in Table 1.
  • service primitive is only used as an example in the table 1 and may also be a service code point, which is not limited in this application.
  • mapping table further includes:
  • the information of the service to which the service identifier of the service to be transmitted belongs is copied or diverted.
  • mapping table shown in Table 2 includes information about duplication or offloading of the service to which the service identifier of the service to be transmitted belongs.
  • service primitive is only used as an example in the table 2, and may also be a service code point, which is not limited in this application.
  • the data radio bearer identifier, the mapping carrier, and the corresponding offloading or copying information corresponding to the service layer primitives in the table 2 are merely examples, and the application does not limit this.
  • the terminal device may obtain, from the network device, a correspondence between the service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the terminal device receives the first information sent by the network device, where the first information includes a correspondence between the service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the terminal device may be a terminal device as shown in FIG. 1 and receive grant information of the network device for resource transmission.
  • the terminal device may establish a correspondence between the service identifier of the to-be-transmitted service and a carrier or a carrier set by itself.
  • the terminal device classifies the to-be-transmitted service on the service layer, and assigns different service identifiers to different types of services, where the service identifier is a service code point or a service primitive;
  • the terminal device establishes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the terminal device divides the to-be-transmitted service into multiple service types on the service layer, where the number of the multiple service types is greater than the value of the PPPP.
  • PPPP can take up to 8 values.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set may also be pre-configured, for example, by using a protocol.
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, and the corresponding relationship between the service identifier of the to-be-transmitted service and the carrier or the carrier set, to determine whether to send or receive the carrier or the carrier set of the to-be-transmitted service, including:
  • the terminal device determines, according to the first carrier set, the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, whether to transmit or receive the carrier or the carrier set of the to-be-transmitted service.
  • the second information may be grant information.
  • the first carrier set is a carrier set configured by the network device for the terminal device to transmit a service.
  • the second information is system information that is sent by the network device by using a broadcast, or Radio Resource Control (RRC) information transmitted by the network device.
  • RRC Radio Resource Control
  • the first carrier set includes carrier a, carrier b, carrier c, and carrier d;
  • the carrier or carrier set corresponding to the service identifier of the to-be-transmitted service includes carrier b, carrier c, carrier f, and carrier h, and the terminal at this time
  • the device determines that the carrier that sends or receives the service to be transmitted is carrier b and carrier c, or is the carrier set b+c.
  • the terminal device determines, according to the service identifier of the to-be-transmitted service, and the corresponding relationship between the service identifier of the to-be-transmitted service and the carrier or the carrier set, to determine whether to send or receive the carrier or the carrier set of the to-be-transmitted service, including:
  • the second carrier set is a pre-configured carrier set used by the terminal device to transmit services.
  • the second set of carriers is a set of carriers for transmitting traffic determined by a protocol.
  • the second carrier set includes a carrier e, a carrier f, a carrier g, and a carrier h.
  • the carrier or carrier set corresponding to the service identifier of the to-be-transmitted service includes a carrier b, a carrier c, a carrier f, and a carrier h.
  • the terminal device determines that the carrier transmitting or receiving the to-be-transmitted service is the carrier f and the carrier h, or is the carrier set f+h.
  • the terminal device determines the second carrier set according to the pre-configured carrier for transmitting resources, for example, the carrier that the terminal device can use for transmitting resources is carrier a, carrier b, carrier c, carrier d, carrier e, carrier f, carrier g, and carrier h, the terminal device determines that the second carrier set is carrier a, carrier b, and carrier c.
  • the carrier set used by the terminal device to transmit the service may be configured by the network device, or may be pre-configured by the protocol.
  • the network device may configure a carrier or a carrier set for transmitting a service to the terminal device through the authorization information.
  • the server determines the carrier or carrier set of the terminal device transmission service by using the protocol. At this time, both the terminal device and the network device can learn a protocol information from the server.
  • the terminal device sends or receives the to-be-transmitted service on a carrier or a carrier set corresponding to the service identifier of the to-be-transmitted service.
  • the terminal device performs the logical channel prioritization (LCP) processing on the to-be-transmitted service when the media access control (MAC) layer performs the service identifier and the carrier of the to-be-transmitted service.
  • LCP logical channel prioritization
  • MAC media access control
  • the terminal device performs the logical channel prioritization (LCP) processing on the to-be-transmitted service when the media access control (MAC) layer performs the service identifier and the carrier of the to-be-transmitted service.
  • LCP logical channel prioritization
  • MAC media access control
  • the terminal device determines, according to the service code point or the service primitive of the to-be-transmitted service that is generated in the service layer, the carrier or the carrier set that sends or receives the service to be transmitted, and thus,
  • the services generated on the service layer correspond to different carriers or carrier sets.
  • the services to be transmitted can be transmitted on the carrier or the carrier set at a smaller granularity, which overcomes the limitation of the PPPP value and cannot exceed the PPPP.
  • the number of V2X services corresponds to different carriers or carrier sets for service transmission, thereby improving the service transmission rate.
  • FIG. 8 is a schematic flowchart of a method 300 for wireless communication according to an embodiment of the present application. As shown in FIG. 8, the method 300 may be performed by a network device, which may be a network device as shown in FIG. 1, and the terminal device in the method 300 may be a terminal device as shown in FIG. 1. The method 300 includes the following.
  • the network device establishes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the network device sends the first information to the terminal device, where the first information includes a correspondence between the service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the service identifier of the to-be-transmitted service is a service code point or a service primitive of the to-be-transmitted service generated at the service layer, where the service code point is a code of a service generated by the to-be-transmitted service on the service layer, where The service primitive is a textual description of the service generated by the to-be-transmitted service on the service layer.
  • the to-be-transmitted service is a V2X service.
  • the method 300 further includes:
  • the network device sends second information to the terminal device, where the second information indicates that the first carrier set is a carrier set used by the terminal device to transmit a service.
  • the second information is system information or RRC information.
  • the network device establishes a correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, including:
  • the network device classifies the to-be-transmitted service on the service layer, and assigns different service identifiers to different types of services, where the service identifier is a service code point or a service primitive;
  • the network device establishes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the network device classifies the to-be-transmitted service on the service layer, including:
  • the network device divides the to-be-transmitted service into multiple service types on the service layer, and the number of the multiple service types is greater than the value of the single-packet preference-level PPPP.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is integrated in the mapping table.
  • mapping table further includes:
  • the information of the service to which the service identifier of the service to be transmitted belongs is copied or diverted.
  • the network device establishes a correspondence between a service identifier of a to-be-transmitted service and a carrier or a carrier set, and sets a service identifier between the service to be transmitted and a carrier or a carrier set.
  • the corresponding relationship is sent to the terminal device, so that the terminal device performs service transmission on the carrier or carrier set corresponding to the service to be transmitted, and overcomes the limitation that the number of PPPP values cannot make the V2X service exceeding the PPPP value correspond to different carriers. Or the service transmission on the carrier set, thereby improving the service transmission rate.
  • FIG. 9 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 9, the terminal device 400 includes:
  • the processing unit 410 is configured to determine, according to the service identifier of the service to be transmitted, a carrier or a carrier set that sends or receives the service to be transmitted;
  • the transceiver unit 420 is configured to send or receive the to-be-transmitted service on the carrier or the carrier set corresponding to the service identifier of the to-be-transmitted service, where the service identifier of the to-be-transmitted service is the service of the to-be-transmitted service generated at the service layer.
  • a code point or a service primitive where the service code point is a code of a service generated by the to-be-transmitted service on a service layer, where the service primitive is a service generated by the to-be-transmitted service on a service layer Description of the text.
  • processing unit 410 is specifically configured to:
  • processing unit 410 is specifically configured to:
  • the processing unit 410 determines, according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, before determining whether to send or receive the carrier or carrier set of the to-be-transmitted service,
  • the transceiver unit 420 is further configured to receive the first information sent by the network device, where the first information includes a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the processing unit 410 determines, according to the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, before determining whether to send or receive the carrier or carrier set of the to-be-transmitted service,
  • the processing unit 410 is further configured to classify the to-be-transmitted service on the service layer, and assign different service identifiers to the different types of services, where the service identifier is a service code point or a service primitive;
  • the processing unit 410 is further configured to establish a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the processing unit 410 is further configured to divide the to-be-transmitted service into multiple service types on the service layer, where the number of the multiple service types is greater than the value of the single-packet preference-level PPPP.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is pre-configured.
  • the transceiver unit 420 is further configured to receive second information sent by the network device, where the second information indicates that the first carrier set is a carrier set used by the terminal device to transmit a service;
  • the processing unit 410 is further configured to determine, according to the first carrier set, the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, to determine whether to send or receive the to-be-transmitted service.
  • Carrier or carrier set is further configured to determine, according to the first carrier set, the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set, to determine whether to send or receive the to-be-transmitted service.
  • the second information is system information or radio resource control RRC information.
  • the processing unit 410 is further configured to determine to send or receive the second carrier set, the service identifier of the to-be-transmitted service, and the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set.
  • the transceiver unit 420 is further configured to: when the media access control MAC layer performs logical channel priority LCP processing on the to-be-transmitted service, according to the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set.
  • the relationship is that the to-be-transmitted service is transmitted on a transport block of a carrier or a carrier set corresponding to the service identifier of the to-be-transmitted service.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is integrated in the mapping table.
  • mapping table further includes:
  • the information of the service to which the service identifier of the service to be transmitted belongs is copied or diverted.
  • the to-be-transmitted service is a vehicle to another terminal device V2X service.
  • terminal device 400 may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 400 respectively implement the method shown in FIG.
  • the corresponding process of the terminal device in 200 is not described here for brevity.
  • FIG. 10 is a schematic block diagram of a network device 500 in accordance with an embodiment of the present application. As shown in FIG. 10, the network device 500 includes:
  • the processing unit 510 is configured to establish a correspondence between a service identifier of the service to be transmitted and a carrier or a carrier set.
  • the transceiver unit 520 is configured to send, to the terminal device, first information, where the first information includes the to-be-supplied Corresponding relationship between the service identifier of the transport service and the carrier or carrier set;
  • the service identifier of the to-be-transmitted service is a service code point or a service primitive of the to-be-transmitted service generated at the service layer, where the service code point is a code of a service generated by the to-be-transmitted service on the service layer, where the service original
  • the text is a textual description of the service generated by the to-be-transmitted service on the service layer.
  • the transceiver unit 520 is further configured to send, to the terminal device, second information, where the second information indicates that the first carrier set is a carrier set used by the terminal device to transmit a service.
  • the second information is system information or radio resource control RRC information.
  • the processing unit 510 is further configured to classify the to-be-transmitted service on the service layer, and assign different service identifiers to the different types of services, where the service identifier is a service code point or a service primitive;
  • the processing unit 510 is further configured to establish a correspondence between a service identifier of the to-be-transmitted service and a carrier or a carrier set.
  • the processing unit 510 is further configured to divide the to-be-transmitted service into multiple service types on the service layer, where the number of the multiple service types is greater than the value of the single-packet preference-level PPPP.
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set includes:
  • the correspondence between the service identifier of the to-be-transmitted service and the carrier or the carrier set is integrated in the mapping table.
  • mapping table further includes:
  • the information of the service to which the service identifier of the service to be transmitted belongs is copied or diverted.
  • the to-be-transmitted service is a vehicle to another terminal device V2X service.
  • the network device 500 may correspond to the network device in the method embodiment of the present application, and the foregoing operations and/or functions of the respective units in the network device 500 respectively implement the method shown in FIG.
  • the corresponding process of the network device in 300, for the sake of brevity, here is not Let me repeat.
  • FIG. 11 is a schematic block diagram of a device 600 for wireless communication provided by an embodiment of the present application.
  • the device 600 includes:
  • a memory 610 configured to store a program, where the program includes code
  • the transceiver 620 is configured to communicate with other devices;
  • the processor 630 is configured to execute program code in the memory 610.
  • the processor 630 can implement various operations performed by the terminal device in the method 200 in FIG. 3, and details are not described herein for brevity.
  • the device 600 may be a terminal device (for example, a mobile phone).
  • the transceiver 620 is configured to perform specific signal transceiving under the driving of the processor 630.
  • the processor 630 can also implement various operations performed by the network device in the method 300 in FIG. 8.
  • the device 600 may be a network device (for example, an access network device or a core network device).
  • the processor 630 may be a central processing unit (CPU), and the processor 630 may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 610 can include read only memory and random access memory and provides instructions and data to the processor 630. A portion of the memory 610 may also include a non-volatile random access memory. For example, the memory 610 can also store information of the device type.
  • the transceiver 620 can be used to implement signal transmission and reception functions, such as frequency modulation and demodulation functions or upconversion and down conversion functions.
  • the device 600 for wireless communication can be a chip or chipset.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor 630 reads the information in the memory and completes the steps of the above method in combination with the hardware thereof. To avoid repetition, here is no longer Detailed Description.
  • FIG. 12 is a schematic structural diagram of a system chip 700 according to an embodiment of the present application.
  • the system chip 700 of FIG. 12 includes an input interface 701, an output interface 702, a processor 703, and a memory 704 that can be connected by an internal communication connection line.
  • the processor 703 is configured to execute code in the memory 704.
  • the processor 703 implements a method performed by the terminal device in the method embodiment. For the sake of brevity, it will not be repeated here.
  • the processor 703 when the code is executed, the processor 703 implements a method performed by a network device in a method embodiment. For the sake of brevity, it will not be repeated here.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种无线通信的方法、终端设备和网络设备,可以在业务层上将V2X业务划分为业务码点或业务原语,并根据业务码点或业务原语将V2X业务映射到不同的载波上进行传输。该方法包括:终端设备根据待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集;该终端设备在该待传输业务的业务标识对应的载波或载波集上发送或接收该待传输业务,其中,该待传输业务的业务标识为在业务层生成的该待传输业务的业务码点或业务原语,该业务码点为该待传输业务在业务层上生成的业务的编码,该业务原语为该待传输业务在业务层上生成的业务的文本描述。

Description

无线通信的方法、终端设备和网络设备 技术领域
本申请涉及通信领域,并且更具体地,涉及一种无线通信的方法、终端设备和网络设备。
背景技术
在第三代合作伙伴项目(the 3rd Generation Partnership Project,3GPP)协议的版本Release-14中,车辆到其它设备(Vehicle to Everything,V2X)业务可以根据安全特性分为安全相关业务和非安全相关业务,同时,在3GPP版本Release-14中提出可以将特定的V2X业务映射到特定的频率上进行传输,具体地,在上层为每个V2X包确定相应的单包优先级(ProSe Per Packet Priority,PPPP)值,接入层(Access Statum,AS)可以根据PPPP来进行逻辑信道优先级,每个PPPP值会和逻辑信道组(Logical Channel Group,LCG)对应,PPPP值优先级高的分组,可以使用低优先级的分组的传输资源(例如,载波上的资源),反之则不可以。
然而,上层分配的PPPP值的数量有限,难以准确反映不同V2X业务在时延、可靠性等方面的服务质量(Quality of Service,QoS)需求特性,其次,基于PPPP的方案有可能会碰到多个V2X业务的PPPP值一样,这种情况下,难以使用PPPP值来为不同的业务分配不同的载波上的资源。
发明内容
本申请实施例提供了一种无线通信的方法、终端设备和网络设备,可以在业务层上将V2X业务划分为业务码点或业务原语,并根据业务码点或业务原语将V2X业务映射到不同的载波上进行传输,从而,克服了因PPPP值的数量有限而无法为比PPPP值多的V2X业务分配不同的载波上的资源的问题。
第一方面,本申请实施例提供了一种无线通信的方法,包括:
终端设备根据待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集;
该终端设备在该待传输业务的业务标识对应的载波或载波集上发送或 接收该待传输业务,其中,该待传输业务的业务标识为在业务层生成的该待传输业务的业务码点或业务原语,该业务码点为该待传输业务在业务层上生成的业务的编码,该业务原语为该待传输业务在业务层上生成的业务的文本描述。
因此,在本申请实施例的无线通信的方法中,终端设备根据在业务层生成的待传输业务的业务码点或业务原语确定发送或接收该待传输业务的载波或载波集,从而,可以为在业务层上生成的业务对应不同的载波或载波集,待传输业务可以在更多粒度上对应到载波或载波集上进行传输,进而,克服了因PPPP值的数量有限而无法为比PPPP值多的业务分配不同的载波上的资源的问题。
可选地,在第一方面的一种实现方式中,该终端设备根据待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集,包括:
该终端设备在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识;
该终端设备根据该待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集。
可选地,在第一方面的一种实现方式中,该终端设备根据待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集,包括:
该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集。
因此,在本申请实施例的无线通信的方法中,终端设备可以根据待传输业务的业务标识,以及待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收待传输业务的载波或载波集。
可选地,在第一方面的一种实现方式中,在该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集之前,该方法还包括:
该终端设备接收网络设备发送的第一信息,该第一信息中包括该待传输业务的业务标识与载波或载波集之间的对应关系。
因此,在本申请实施例的无线通信的方法中,终端设备可以从网络设备接收待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,在第一方面的一种实现方式中,在该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集之前,该方法还包括:
该终端设备在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识,该业务标识为业务码点或业务原语;
该终端设备建立该待传输业务的业务标识与载波或载波集之间的对应关系。
因此,在本申请实施例的无线通信的方法中,终端设备自身可以建立接收待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,在第一方面的一种实现方式中,该终端设备在业务层上对该待传输业务进行分类,包括:
该终端设备在业务层上将该待传输业务划分为多种业务类型,该多种业务类型的数量大于单包优选级PPPP的取值数量。
可选地,在第一方面的一种实现方式中,该待传输业务的业务标识与载波或载波集之间的对应关系是预先配置的。
可选地,在第一方面的一种实现方式中,该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集,包括:
该终端设备接收网络设备发送的第二信息,该第二信息指示第一载波集为该终端设备用于传输业务的载波集;
该终端设备根据该第一载波集、该待传输业务的业务标识和该待传输业务的业务标识与载波或载波集之间的对应关系,确定发送或接收该待传输业务的载波或载波集。
可选地,在第一方面的一种实现方式中,该第二信息为系统信息或无线资源控制RRC信息。
可选地,在第一方面的一种实现方式中,该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集,包括:
该终端设备根据该第二载波集、该待传输业务的业务标识和该待传输业务的业务标识与载波或载波集之间的对应关系,确定发送或接收该待传输业务的载波或载波集,其中,该第二载波集为预配置的该终端设备用于传输业 务的载波集。
可选地,在第一方面的一种实现方式中,该终端设备在该待传输业务的业务标识对应的载波或载波集上发送或接收该待传输业务,包括:
该终端设备在媒体接入控制MAC层对该待传输业务进行逻辑信道优先级LCP处理时,根据该待传输业务的业务标识与载波或载波集之间的对应关系,在该待传输业务的业务标识对应的载波或载波集的传输块上传输该待传输业务。
可选地,在第一方面的一种实现方式中,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与数据无线承载DRB之间的对应关系,该DRB与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,在第一方面的一种实现方式中,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,在第一方面的一种实现方式中,该待传输业务的业务标识与载波或载波集之间的对应关系集成于映射表中。
可选地,在第一方面的一种实现方式中,该映射表还包括:
该待传输业务的业务标识所属的业务进行复制或分流的信息。
可选地,在第一方面的一种实现方式中,该待传输业务为车辆到其它终端设备V2X业务。
第二方面,本申请实施例提供了一种无线通信的方法,包括:
网络设备建立待传输业务的业务标识与载波或载波集之间的对应关系;
该网络设备向终端设备发送第一信息,该第一信息中包括该待传输业务的业务标识与载波或载波集之间的对应关系;
其中,该待传输业务的业务标识为在业务层生成的该待传输业务的业务码点或业务原语,该业务码点为该待传输业务在业务层上生成的业务的编码,该业务原语为该待传输业务在业务层上生成的业务的文本描述。
因此,在本申请实施例的无线通信的方法中,网络设备建立待传输业务的业务标识与载波或载波集之间的对应关系,并将待传输业务的业务标识与 载波或载波集之间的对应关系发送给终端设备,以使终端设备在待传输业务对应的载波或载波集上进行业务传输,进而,克服了因PPPP值的数量有限而无法为比PPPP值多的业务分配不同的载波上的资源的问题。
可选地,在第二方面的一种实现方式中,该方法还包括:
该网络设备向该终端设备发送第二信息,该第二信息指示第一载波集为该终端设备用于传输业务的载波集。
可选地,在第二方面的一种实现方式中,该第二信息为系统信息或无线资源控制RRC信息。
可选地,在第二方面的一种实现方式中,该网络设备建立待传输业务的业务标识与载波或载波集之间的对应关系,包括:
该网络设备在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识,该业务标识为业务码点或业务原语;
该网络设备建立该待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,在第二方面的一种实现方式中,该网络设备在业务层上对该待传输业务进行分类,包括:
该网络设备在业务层上将该待传输业务划分为多种业务类型,该多种业务类型的数量大于单包优选级PPPP的取值数量。
可选地,在第二方面的一种实现方式中,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与数据无线承载DRB之间的对应关系,该DRB与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,在第二方面的一种实现方式中,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,在第二方面的一种实现方式中,该待传输业务的业务标识与载波或载波集之间的对应关系集成于映射表中。
可选地,在第二方面的一种实现方式中,该映射表还包括:
该待传输业务的业务标识所属的业务进行复制或分流的信息。
可选地,在第二方面的一种实现方式中,该待传输业务为车辆到其它终端设备V2X业务。
第三方面,本申请实施例提供了一种终端设备,可以执行第一方面或第一方面的任一可选的实现方式中的方法的模块或者单元。
第四方面,本申请实施例提供了一种网络设备,可以执行第二方面或第二方面的任一可选的实现方式中的方法的模块或者单元。
第五方面,提供了一种终端设备,该终端设备包括处理器、存储器和通信接口。处理器与存储器和通信接口连接。存储器用于存储指令,处理器用于执行该指令,通信接口用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时,该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面,提供了一种网络设备,该网络设备包括处理器、存储器和通信接口。处理器与存储器和通信接口连接。存储器用于存储指令,处理器用于执行该指令,通信接口用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时,该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第七方面,提供了一种计算机存储介质,该计算机存储介质中存储有程序代码,该程序代码用于指示计算机执行上述第一方面或第一方面的任一种可能的实现方式中的方法的指令。
第八方面,提供了一种计算机存储介质,该计算机存储介质中存储有程序代码,该程序代码用于指示计算机执行上述第二方面或第二方面的任一种可能的实现方式中的方法的指令。
第九方面,提供了一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述各方面所述的方法。
附图说明
图1是本申请实施例的一个应用场景的示意图。
图2是本申请实施例的另一个应用场景的示意图。
图3是根据本申请实施例的一种无线通信的方法的示意性流程图。
图4是根据本申请实施例的待传输业务的业务标识与载波或载波集之间的一种对应关系的示意图。
图5是根据本申请实施例的待传输业务的业务标识与载波或载波集之间的另一种对应关系的示意图。
图6是根据本申请实施例的待传输业务的业务标识与载波或载波集之间的再一种对应关系的示意图。
图7是根据本申请实施例的终端设备获取用于传输业务的载波或载波集的示意图。
图8是根据本申请实施例的另一种无线通信的方法的示意性流程图。
图9是根据本申请实施例的终端设备的示意性框图。
图10是根据本申请实施例的网络设备的示意性框图。
图11示出了本申请实施例提供的无线通信的设备的示意性框图。
图12是根据本申请实施例的系统芯片的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(Global System of Mobile communication,GSM)系统、码分多址(Code Division Multiple Access,CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)系统、通用分组无线业务(General Packet Radio Service,GPRS)、长期演进(Long Term Evolution,LTE)系统、LTE频分双工(Frequency Division Duplex,FDD)系统、LTE时分双工(Time Division Duplex,TDD)、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access,WiMAX)通信系统或未来的5G系统等。
应理解,本申请实施例的技术方案可以应用于车联网系统,车联网系统可以基于上述各种通信系统,进而实现终端与终端之间的通信(Device to Device,D2D)通信,例如,基于LTE-D2D的车联网系统。与传统的LTE系统中终端之间的通信数据通过网络设备(例如,基站)接收或者发送的方式不同,车联网系统可以采用终端到终端直接通信的方式,因此具有更高的频谱效率以及更低的传输时延。
D2D通信可以指车对车(Vehicle to Vehicle,简称“V2V”)通信或车辆到其他设备(Vehicle to Everything,V2X)通信。在V2X通信中,X可以泛指任何具有无线接收和发送能力的设备,例如但不限于慢速移动的无线装置,快速移动的车载设备,或是具有无线发射接收能力的网络控制节点等。应理解,本申请实施例主要应用于V2X通信的场景,但也可以应用于任意其它D2D通信场景,本申请实施例对此不做任何限定。
本申请实施例中的终端设备可以指车载终端设备,也可以是指与车载终端设备进行通信的其它设备,例如,未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network,PLMN)中的终端设备等,本申请实施例并不限定。
本申请结合网络设备描述了各个实施例。本申请实施例中的网络设备可以是用于与终端设备通信的设备,该网络设备可以是GSM或CDMA中的基站(Base Transceiver Station,BTS),也可以是WCDMA系统中的基站(NodeB,NB),还可以是LTE系统中的演进型基站(Evolutional NodeB,eNB或eNodeB),还可以是云无线接入网络(Cloud Radio Access Network,CRAN)场景下的无线控制器,或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等,本申请实施例并不限定。
图1和图2是本申请实施例的一个应用场景的示意图。图1示例性地示出了一个网络设备和两个终端设备。可选地,本申请实施例中的无线通信系统可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备,本申请实施例对此不做限定。此外,该无线通信系统还可以包括移动管理实体(Mobile Management Entity,MME)、服务网关(Serving Gateway,S-GW)、分组数据网络网关(Packet Data Network Gateway,P-GW)等其他网络实体,但本申请实施例不限于此。
具体地,终端设备(例如,车载终端)20和终端设备(其它终端)30可以通过D2D通信模式进行通信,在进行D2D通信时,终端设备20和终端设备30通过D2D链路即侧行链路(Sidelink,SL)直接进行通信。例如图1或者图2所示,终端设备20和终端设备30通过侧行链路直接进行通信。在图1中,终端设备20和终端设备30之间通过侧行链路通信,其传输资源(例如,载波)是由网络设备分配的;在图2中,终端设备20和终端设备 30之间通过侧行链路通信,其传输资源是由终端设备自主选取的(例如,终端设备在资源池中选择可以使用的载波),不需要网络设备分配传输资源。
在车联网系统中,可以存在两种类型的终端设备,即具有侦听能力的终端设备例如车载终端(Vehicle User Equipment,VUE)或行人手持终端(Pedestrian User Equipment,PUE),以及不具有侦听能力的终端设备例如PUE。VUE具有更高的处理能力,并且通常通过车内的蓄电池供电,而PUE处理能力较低,降低功耗也是PUE需要考虑的一个主要因素,因此在现有的车联网系统中,VUE被认为具有完全的接收能力和侦听能力;而PUE被认为具有部分或者不具有接收和侦听能力。如果PUE具有部分侦听能力,其资源的选取可以采用和VUE类似的侦听方法,在可侦听的那部分资源上进行可用资源的选取;如果PUE不具有侦听能力,则PUE在资源池中随机选取传输资源。
可选地,V2X业务可以支持以下三种场景:
(1)一个V2X业务的不同媒体接入控制分组数据单元(Media Access Control Packet Data Unit,MAC PDU)可以在不同的载波上传输,以提高吞吐量。
(2)一个V2X业务的MAC PDU可以在不同的载波上复制和发送,以提高可靠性。
(3)从接收终端设备的角度,需要接收多个载波,发送终端设备可以在一部分载波发送,从而也可以实现容量的提升。
具体地,支持(1)需要确定针对某一个特定业务可以分流传输的载波集合,支持(2)需要确定针对某一个特定业务可以复制传输的载波集合,支持(3)需要确定发送终端设备可以用来传输数据的载波或者载波集,同时还需要明确接收特定V2X业务的载波集合。
在上述3种场景下,为不同的V2X业务分配相应的载波,需要将V2X业务映射相应的载波,以实现在特定的载波的资源上传输V2X业务。
此外,本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如,计算机可读介质可以包括,但不限于:磁存储器件(例如,硬盘、软盘或磁带等),光盘(例如,压缩盘(Compact Disc,CD)、数字通用盘(Digital Versatile Disc,DVD)等), 智能卡和闪存器件(例如,可擦写可编程只读存储器(Erasable Programmable Read-Onlv Memory,EPROM)、卡、棒或钥匙驱动器等)。另外,本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于,能够存储、包含和/或承载指令和/或数据的各种介质。
应理解,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
图3是根据本申请实施例的一种无线通信的方法200的示意性流程图。如图3所示,该方法200可以由终端设备执行,该终端设备可以是如图1或图2中所示的终端设备,该方法200中的网络设备可以是如图1所示的网络设备。该方法200包括以下内容。
210,终端设备根据待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集。
可选地,该待传输业务为V2X业务。
可选地,该V2X业务包括协同感知信息(Cooperative Awareness Message,CAM)、分散环境通知信息(Decentralized Environmental Notification Message,DENM)等业务类型。
可选地,在3GPP版本Release-15中,V2X业务类型可以包括编队驾驶、远程驾驶、传感器数据分享等。
可选地,该待传输业务的业务标识为在业务层生成的该待传输业务的业务码点或业务原语,该业务码点为该待传输业务在业务层上生成的业务的编码,该业务原语为该待传输业务在业务层上生成的业务的文本描述。
可选地,该待传输业务的业务码点可以根据潜在的业务类型选择比特数,可以支持更多的业务类型划分。
例如,该待传输业务的业务码点可以是V2X.1、V2X.2、V2X.3...V2X.i...V2X.n。
可选地,该待传输业务的业务原语可以是文本,可以携带更多的业务类型信息。
例如,该待传输业务的业务原语可以是V2X.CAM1、V2X.CAM2...V2X.CAM m、V2X.DENM1、V2X.DENM2...V2X.DENM m、V2X.X 1...V2X.X m...。
可选地,可以通过如下方式确定发送或接收该待传输业务的载波或载波集:
方式一,该终端设备在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识;
该终端设备根据该待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集。
可选地,该终端设备在业务层上对该待传输业务进行分类时,可以考虑该待传输业务在时延、可靠性等方面的QoS需求特性。
方式二,该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与数据无线承载(Data Radio Bearer,DRB)之间的对应关系,该DRB与逻辑信道(Logical Channel,LC)之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
例如,如图4所示,V2X.CAM 1/V2X.1对应DRB 1、V2X.DENM 2/V2X.2对应DRB 2、V2X.CAM 2/V2X.3对应DRB 3,DRB 1对应逻辑信道标识(Logical Channel Identity LCID)1、DRB 2对应LCID 2、DRB 3对应LCID 3,LCID 1对应载波a、LCID 2对应载波b、LCID 3对应载波c,进而实现从该待传输业务的业务标识到载波或载波集的对应。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
例如,如图5所示,V2X.CAM 1/V2X.1对应LCID 1、V2X.CAM 2/V2X.2对应LCID 2、V2X.CAM 3/V2X.3对应LCID 3,LCID 1对应载波a、LCID 2对应载波b、LCID 3对应载波c,进而实现从该待传输业务的业务标识到载 波或载波集的对应。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识直接对应载波或载波集。
例如,如图6所示,V2X.DENM 1/V2X.1对应载波a、V2X.DENM 2/V2X.2对应载波b、V2X.DENM 3/V2X.3对应载波c。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系集成于映射表中。
例如,如表1所示,根据如表1所示的映射表确定该待传输业务的业务标识与载波或载波集之间的对应关系。
表1
业务层原语 数据无线承载标识 映射载波(或者频点) 其他标识(预留)
V2X.CAM1 1 a+b  
V2X.DENM2 2 c  
V2X.CAM2 3 b+c  
     
应理解,该表1中仅以业务原语为例进行说明,还可以是业务码点,本申请对此并不限制。
还应理解,该表1中业务层原语对应的数据无线承载标识和映射载波,仅仅只是示例,本申请对此并不限制。
可选地,该映射表还包括:
该待传输业务的业务标识所属的业务进行复制或分流的信息。
例如,如表2所示的映射表包括该待传输业务的业务标识所属的业务进行复制(duplication)或分流的信息。
表2
业务层原语 数据无线承载标识 映射载波(或者频点) 分流或复制 其他标识
V2X.CAM1 1 a+b 分流  
V2X.DENM2 2 c 复制  
V2X.CAM2 3 b+c 分流  
       
应理解,该表2中仅以业务原语为例进行说明,还可以是业务码点,本申请对此并不限制。
还应理解,该表2中业务层原语对应的数据无线承载标识、映射载波和对应的分流或复制信息,仅仅只是示例,本申请对此并不限制。
可选地,该终端设备可以从网络设备获取该待传输业务的业务标识与载波或载波集的对应关系。
例如,该终端设备接收网络设备发送的第一信息,该第一信息中包括该待传输业务的业务标识与载波或载波集之间的对应关系。
应理解,此时,该终端设备可以是如图1中所示的终端设备,接收网络设备的授权(grant)信息来进行资源传输。
可选地,该终端设备可以自己建立该待传输业务的业务标识与载波或载波集的对应关系。
例如,该终端设备在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识,该业务标识为业务码点或业务原语;
该终端设备建立该待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,该终端设备在业务层上将该待传输业务划分为多种业务类型,该多种业务类型的数量大于PPPP的取值数量。
应理解,PPPP最多可以取值8个值。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系也可以是预先配置的,例如,通过协议确定。
可选地,该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集,包括:
该终端设备接收网络设备发送的第二信息,所述第二信息指示第一载波集为所述终端设备用于传输业务的载波集;
该终端设备根据该第一载波集、该待传输业务的业务标识和该待传输业务的业务标识与载波或载波集之间的对应关系,确定发送或接收该待传输业务的载波或载波集。
可选地,该第二信息可以是授权(grant)信息。
可选地,该第一载波集为网络设备为终端设备配置的用于传输业务的载波集。
可选地,该第二信息为网络设备通过广播方式发送的系统信息,或者, 网络设备发送的无线资源控制(Radio Resource Control,RRC)信息。
例如,该第一载波集包括载波a、载波b、载波c和载波d;该待传输业务的业务标识对应的载波或载波集包括载波b、载波c、载波f和载波h,此时该终端设备确定发送或接收该待传输业务的载波为载波b和载波c,或者为载波集b+c。
可选地,该终端设备根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集,包括:
该终端设备根据该第二载波集、该待传输业务的业务标识和该待传输业务的业务标识与载波或载波集之间的对应关系,确定发送或接收该待传输业务的载波或载波集,其中,该第二载波集为预配置的该终端设备用于传输业务的载波集。
例如,该第二载波集为通过协议确定的用于传输业务的载波集。
又例如,该第二载波集包括载波e、载波f、载波g和载波h;该待传输业务的业务标识对应的载波或载波集包括载波b、载波c、载波f和载波h,此时该终端设备确定发送或接收该待传输业务的载波为载波f和载波h,或者为载波集f+h。
可选地,该终端设备根据预配置的用于传输资源的载波确定该第二载波集,例如,该终端设备可以用于传输资源的载波为载波a、载波b、载波c、载波d、载波e、载波f、载波g和载波h,该终端设备确定该第二载波集为载波a、载波b和载波c。
可选地,该终端设备用于传输业务的载波集可以是网络设备配置的,也可以是通过协议预配置的。例如,如图7所示,网络设备可以通过授权信息向终端设备配置用于传输业务的载波或载波集。又例如,如图7所示,服务器通过协议确定终端设备传输业务的载波或载波集,此时,终端设备和网络设备都可以从服务器获知一种协议信息。
220,该终端设备在该待传输业务的业务标识对应的载波或载波集上发送或接收该待传输业务。
可选地,该终端设备在媒体接入控制(Media Access Control,MAC)层对该待传输业务进行逻辑信道优先级(Logical Channel Prioritization,LCP)处理时,根据该待传输业务的业务标识与载波或载波集之间的对应关系,在 该待传输业务的业务标识对应的载波或载波集的传输块上传输该待传输业务。
因此,在本申请实施例的无线通信的方法中,终端设备根据在业务层生成的待传输业务的业务码点或业务原语确定发送或接收该待传输业务的载波或载波集,从而,可以为在业务层上生成的业务对应不同的载波或载波集,进而,待传输业务可以在更小粒度上对应到载波或载波集上进行传输,克服了因PPPP值的数量有限而无法使超过PPPP值的数量的V2X业务对应到不同的载波或载波集上进行业务传输,进而,提高了业务传输速率。
图8是根据本申请实施例的一种无线通信的方法300的示意性流程图。如图8所示,该方法300可以由网络设备执行,该网络设备可以是如图1中所示的网络设备,该方法300中的终端设备可以是如图1所示的终端设备。该方法300包括以下内容。
310,网络设备建立待传输业务的业务标识与载波或载波集之间的对应关系。
320,该网络设备向终端设备发送第一信息,该第一信息中包括该待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,该待传输业务的业务标识为在业务层生成的该待传输业务的业务码点或业务原语,该业务码点为该待传输业务在业务层上生成的业务的编码,该业务原语为该待传输业务在业务层上生成的业务的文本描述。
可选地,该待传输业务为V2X业务。
可选地,该方法300还包括:
该网络设备向该终端设备发送第二信息,该第二信息指示第一载波集为该终端设备用于传输业务的载波集。
可选地,该第二信息为系统信息或RRC信息。
可选地,该网络设备建立待传输业务的业务标识与载波或载波集之间的对应关系,包括:
该网络设备在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识,该业务标识为业务码点或业务原语;
该网络设备建立该待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,该网络设备在业务层上对该待传输业务进行分类,包括:
该网络设备在业务层上将该待传输业务划分为多种业务类型,该多种业务类型的数量大于单包优选级PPPP的取值数量。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与数据无线承载DRB之间的对应关系,该DRB与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系集成于映射表中。
可选地,该映射表还包括:
该待传输业务的业务标识所属的业务进行复制或分流的信息。
应理解,无线通信的方法300中的步骤可以无线通信的方法200中的相应步骤的描述,为了简洁,在此不再赘述。
因此,在本申请实施例的无线通信的方法中,网络设备建立待传输业务的业务标识与载波或载波集之间的对应关系,并将待传输业务的业务标识与载波或载波集之间的对应关系发送给终端设备,以使终端设备在待传输业务对应的载波或载波集上进行业务传输,克服了因PPPP值的数量有限而无法使超过PPPP值的数量的V2X业务对应到不同的载波或载波集上进行业务传输,进而,提高了业务传输速率。
图9是根据本申请实施例的终端设备400的示意性框图。如图9所示,该终端设备400包括:
处理单元410,用于根据待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集;
收发单元420,用于在该待传输业务的业务标识对应的载波或载波集上发送或接收该待传输业务,其中,该待传输业务的业务标识为在业务层生成的该待传输业务的业务码点或业务原语,该业务码点为该待传输业务在业务层上生成的业务的编码,该业务原语为该待传输业务在业务层上生成的业务 的文本描述。
可选地,该处理单元410具体用于:
在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识;
根据该待传输业务的业务标识确定发送或接收该待传输业务的载波或载波集。
可选地,该处理单元410具体用于:
根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集。
可选地,在该处理单元410根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集之前,
该收发单元420还用于接收网络设备发送的第一信息,该第一信息中包括该待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,在该处理单元410根据该待传输业务的业务标识,以及该待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收该待传输业务的载波或载波集之前,
该处理单元410还用于在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识,该业务标识为业务码点或业务原语;
该处理单元410还用于建立该待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,该处理单元410还用于在业务层上将该待传输业务划分为多种业务类型,该多种业务类型的数量大于单包优选级PPPP的取值数量。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系是预先配置的。
可选地,该收发单元420,还用于接收网络设备发送的第二信息,该第二信息指示第一载波集为该终端设备用于传输业务的载波集;
该处理单元410,还用于根据该第一载波集、该待传输业务的业务标识和该待传输业务的业务标识与载波或载波集之间的对应关系,确定发送或接收该待传输业务的载波或载波集。
可选地,该第二信息为系统信息或无线资源控制RRC信息。
可选地,该处理单元410,还用于根据该第二载波集、该待传输业务的业务标识和该待传输业务的业务标识与载波或载波集之间的对应关系,确定发送或接收该待传输业务的载波或载波集,其中,该第二载波集为预配置的该终端设备用于传输业务的载波集。
可选地,该收发单元420,还用于在媒体接入控制MAC层对该待传输业务进行逻辑信道优先级LCP处理时,根据该待传输业务的业务标识与载波或载波集之间的对应关系,在该待传输业务的业务标识对应的载波或载波集的传输块上传输该待传输业务。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与数据无线承载DRB之间的对应关系,该DRB与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系集成于映射表中。
可选地,该映射表还包括:
该待传输业务的业务标识所属的业务进行复制或分流的信息。
可选地,该待传输业务为车辆到其它终端设备V2X业务。
应理解,根据本申请实施例的终端设备400可对应于本申请方法实施例中的终端设备,并且终端设备400中的各个单元的上述和其它操作和/或功能分别为了实现图3所示方法200中终端设备的相应流程,为了简洁,在此不再赘述。
图10是根据本申请实施例的网络设备500的示意性框图。如图10所示,该网络设备500包括:
处理单元510,用于建立待传输业务的业务标识与载波或载波集之间的对应关系;
收发单元520,用于向终端设备发送第一信息,该第一信息中包括该待 传输业务的业务标识与载波或载波集之间的对应关系;
其中,该待传输业务的业务标识为在业务层生成的该待传输业务的业务码点或业务原语,该业务码点为该待传输业务在业务层上生成的业务的编码,该业务原语为该待传输业务在业务层上生成的业务的文本描述。
可选地,该收发单元520,还用于向该终端设备发送第二信息,该第二信息指示第一载波集为该终端设备用于传输业务的载波集。
可选地,该第二信息为系统信息或无线资源控制RRC信息。
可选地,该处理单元510,还用于在业务层上对该待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识,该业务标识为业务码点或业务原语;
该处理单元510,还用于建立该待传输业务的业务标识与载波或载波集之间的对应关系。
可选地,该处理单元510,还用于在业务层上将该待传输业务划分为多种业务类型,该多种业务类型的数量大于单包优选级PPPP的取值数量。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与数据无线承载DRB之间的对应关系,该DRB与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系包括:
该待传输业务的业务标识与逻辑信道之间的对应关系,该逻辑信道与载波或载波集之间的对应关系。
可选地,该待传输业务的业务标识与载波或载波集之间的对应关系集成于映射表中。
可选地,该映射表还包括:
该待传输业务的业务标识所属的业务进行复制或分流的信息。
可选地,该待传输业务为车辆到其它终端设备V2X业务。
应理解,根据本申请实施例的网络设备500可对应于本申请方法实施例中的网络设备,并且网络设备500中的各个单元的上述和其它操作和/或功能分别为了实现图8所示方法300中网络设备的相应流程,为了简洁,在此不 再赘述。
图11示出了本申请实施例提供的无线通信的设备600的示意性框图,该设备600包括:
存储器610,用于存储程序,该程序包括代码;
收发器620,用于和其他设备进行通信;
处理器630,用于执行存储器610中的程序代码。
可选地,当该代码被执行时,该处理器630可以实现图3中的方法200中终端设备执行的各个操作,为了简洁,在此不再赘述。此时,该设备600可以为终端设备(例如,手机)。收发器620用于在处理器630的驱动下执行具体的信号收发。
可选地,当该代码被执行时,该处理器630还可以实现图8中的方法300中网络设备执行的各个操作,为了简洁,在此不再赘述。此时,该设备600可以为网络设备(例如,接入网设备或核心网设备)。
应理解,在本申请实施例中,该处理器630可以是中央处理单元(Central Processing Unit,CPU),该处理器630还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器610可以包括只读存储器和随机存取存储器,并向处理器630提供指令和数据。存储器610的一部分还可以包括非易失性随机存取存储器。例如,存储器610还可以存储设备类型的信息。
收发器620可以是用于实现信号发送和接收功能,例如频率调制和解调功能或叫上变频和下变频功能。
在实现过程中,上述方法的至少一个步骤可以通过处理器630中的硬件的集成逻辑电路完成,或该集成逻辑电路可在软件形式的指令驱动下完成该至少一个步骤。因此,无线通信的设备600可以是个芯片或者芯片组。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器630读取存储器中的信息,结合其硬件完成上述方法的步骤。为避免重复,这里不再 详细描述。
图12是根据本申请实施例的系统芯片700的示意性结构图。图12的系统芯片700包括输入接口701、输出接口702、处理器703以及存储器704之间可以通过内部通信连接线路相连,该处理器703用于执行该存储器704中的代码。
可选地,当该代码被执行时,该处理器703实现方法实施例中由终端设备执行的方法。为了简洁,在此不再赘述。
可选地,当该代码被执行时,该处理器703实现方法实施例中由网络设备执行的方法。为了简洁,在此不再赘述。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应所述以权利要求的保护范围为准。

Claims (5)

  1. 一种无线通信的方法,其特征在于,包括:
    终端设备根据待传输业务的业务标识确定发送或接收所述待传输业务的载波或载波集;
    所述终端设备在所述待传输业务的业务标识对应的载波或载波集上发送或接收所述待传输业务,其中,所述待传输业务的业务标识为在业务层生成的所述待传输业务的业务码点或业务原语,所述业务码点为所述待传输业务在业务层上生成的业务的编码,所述业务原语为所述待传输业务在业务层上生成的业务的文本描述。
  2. 根据权利要求1所述的方法,其特征在于,所述终端设备根据待传输业务的业务标识确定发送或接收所述待传输业务的载波或载波集,包括:
    所述终端设备在业务层上对所述待传输业务进行分类,以及为不同类型的业务赋予不同的业务标识;
    所述终端设备根据所述待传输业务的业务标识确定发送或接收所述待传输业务的载波或载波集。
  3. 根据权利要求1所述的方法,其特征在于,所述终端设备根据待传输业务的业务标识确定发送或接收所述待传输业务的载波或载波集,包括:
    所述终端设备根据所述待传输业务的业务标识,以及所述待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收所述待传输业务的载波或载波集。
  4. 根据权利要求3所述的方法,其特征在于,在所述终端设备根据所述待传输业务的业务标识,以及所述待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收所述待传输业务的载波或载波集之前,所述方法还包括:
    所述终端设备接收网络设备发送的第一信息,所述第一信息中包括所述待传输业务的业务标识与载波或载波集之间的对应关系。
  5. 根据权利要求3所述的方法,其特征在于,在所述终端设备根据所述待传输业务的业务标识,以及所述待传输业务的业务标识与载波或载波集的对应关系,确定发送或接收所述待传输业务的载波或载波集之前,所述方法还包括:
    所述终端设备在业务层上对所述待传输业务进行分类,以及为不同类型
PCT/CN2017/098126 2017-08-18 2017-08-18 无线通信的方法、终端设备和网络设备 WO2019033416A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201780091771.8A CN110720229A (zh) 2017-08-18 2017-08-18 无线通信的方法、终端设备和网络设备
US16/628,629 US11178526B2 (en) 2017-08-18 2017-08-18 Service transmission method, terminal device, and network device
EP17921797.1A EP3637807B1 (en) 2017-08-18 2017-08-18 Wireless communication method, terminal device, and network device
PCT/CN2017/098126 WO2019033416A1 (zh) 2017-08-18 2017-08-18 无线通信的方法、终端设备和网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/098126 WO2019033416A1 (zh) 2017-08-18 2017-08-18 无线通信的方法、终端设备和网络设备

Publications (1)

Publication Number Publication Date
WO2019033416A1 true WO2019033416A1 (zh) 2019-02-21

Family

ID=65362883

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/098126 WO2019033416A1 (zh) 2017-08-18 2017-08-18 无线通信的方法、终端设备和网络设备

Country Status (4)

Country Link
US (1) US11178526B2 (zh)
EP (1) EP3637807B1 (zh)
CN (1) CN110720229A (zh)
WO (1) WO2019033416A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3965501A4 (en) * 2019-05-07 2022-06-29 Huawei Technologies Co., Ltd. Communication method and device

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110139376B (zh) * 2018-02-08 2021-11-02 中兴通讯股份有限公司 载波集合的确定方法、装置、存储介质及电子装置
KR20220070494A (ko) * 2019-09-30 2022-05-31 후아웨이 테크놀러지 컴퍼니 리미티드 통신 방법, 장치 및 시스템

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102547610A (zh) * 2010-12-31 2012-07-04 华为技术有限公司 消息处理方法、设备及系统
CN103678688A (zh) * 2013-12-27 2014-03-26 国家电网公司 电力自动化通讯全过程报文快速存储及检索方法
CN106488384A (zh) * 2015-08-31 2017-03-08 电信科学技术研究院 一种发送数据包的方法及装置
WO2017051330A1 (en) * 2015-09-25 2017-03-30 Telefonaktiebolaget Lm Ericsson (Publ) Per-packet resource pool selection in lte v2x system
CN106658352A (zh) * 2015-11-02 2017-05-10 中兴通讯股份有限公司 车联网v2x业务的转发方法及装置

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5469431A (en) * 1993-07-12 1995-11-21 Philips Electronics North America Corp. Method of and apparatus for channel mapping with relative service identification
US6215530B1 (en) * 1995-05-22 2001-04-10 Scientific-Atlanta, Inc. Logical and composite channel mapping in an MPEG network
KR20050101006A (ko) * 2004-04-16 2005-10-20 삼성전자주식회사 멀티캐스트 멀티미디어 방송 서비스를 지원하는 이동통신시스템에서 제어 정보를 효율적으로 전송하는 방법
US8966543B2 (en) * 2008-09-29 2015-02-24 Nokia Corporation Method and system to enable adaptation between physical bearers and OMA-BCAST
CN101860475B (zh) 2010-04-02 2013-04-03 北京邮电大学 基于上下文感知的自治队列管理的方法
WO2012138070A2 (en) * 2011-04-03 2012-10-11 Lg Electronics Inc. Method of providing service to user equipment in wireless communication system and apparatus thereof
KR101935785B1 (ko) 2011-08-16 2019-04-03 삼성전자 주식회사 무선통신시스템에서 멀티미디어 방송 서비스를 수신하는 방법 및 장치
EP3703395B1 (en) 2015-06-23 2024-07-10 InterDigital Patent Holdings, Inc. Priority handling for prose communcations
EP3148285B1 (en) 2015-09-25 2019-04-17 Panasonic Intellectual Property Corporation of America Improved radio bearer mapping for proximity services ue to network relay with associated priority signalling
WO2017060756A1 (en) * 2015-10-07 2017-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Service aware carrier aggregation
CN106658424B (zh) 2015-11-02 2019-01-25 中兴通讯股份有限公司 车联网v2x业务的发送方法及装置
US10827501B2 (en) * 2016-02-25 2020-11-03 Nokia Solutions And Networks Oy Techniques for providing proximity services (ProSe) priority-related information to a base station in a wireless network
CN109076397B (zh) * 2016-05-13 2021-07-09 华为技术有限公司 一种资源分配方法及相关设备
US9781744B1 (en) * 2016-08-11 2017-10-03 Futurewei Technologies, Inc. System and method for uplink data scheduling for grant free transmission
CN107733955B (zh) * 2016-08-12 2021-07-30 中兴通讯股份有限公司 车联网业务配置方法及装置,业务获取方法、装置及系统
KR102275288B1 (ko) * 2017-01-03 2021-07-09 삼성전자 주식회사 V2X 통신을 위한 inter-carrier 방법
JP6985415B2 (ja) * 2017-01-25 2021-12-22 華為技術有限公司Huawei Technologies Co., Ltd. サービスデータ伝送方法、第1通信ノード、及び基地局
EP3577985B1 (en) * 2017-02-03 2020-07-22 Telefonaktiebolaget LM Ericsson (publ) Logical channel priority reconfiguration for mac-ces in nr

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102547610A (zh) * 2010-12-31 2012-07-04 华为技术有限公司 消息处理方法、设备及系统
CN103678688A (zh) * 2013-12-27 2014-03-26 国家电网公司 电力自动化通讯全过程报文快速存储及检索方法
CN106488384A (zh) * 2015-08-31 2017-03-08 电信科学技术研究院 一种发送数据包的方法及装置
WO2017051330A1 (en) * 2015-09-25 2017-03-30 Telefonaktiebolaget Lm Ericsson (Publ) Per-packet resource pool selection in lte v2x system
CN106658352A (zh) * 2015-11-02 2017-05-10 中兴通讯股份有限公司 车联网v2x业务的转发方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3637807A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3965501A4 (en) * 2019-05-07 2022-06-29 Huawei Technologies Co., Ltd. Communication method and device
US12082039B2 (en) 2019-05-07 2024-09-03 Huawei Technologies Co., Ltd. Communication method and communications apparatus

Also Published As

Publication number Publication date
US20210144529A1 (en) 2021-05-13
CN110720229A (zh) 2020-01-21
EP3637807B1 (en) 2021-03-31
US11178526B2 (en) 2021-11-16
EP3637807A4 (en) 2020-05-20
EP3637807A1 (en) 2020-04-15

Similar Documents

Publication Publication Date Title
WO2019051803A1 (zh) 资源配置的方法、终端设备和网络设备
WO2020221281A1 (zh) 用于获取无线承载配置的方法和装置
WO2020015727A1 (zh) 路径选择的方法、终端设备和网络设备
CN110651514B (zh) 数据传输的方法、终端设备和网络设备
EP3678437B1 (en) Method for conflict resolution and terminal device
WO2019100356A1 (zh) 载波选取的方法和设备、终端设备
WO2020087226A1 (zh) 无线通信的方法、终端设备和网络设备
WO2020029403A1 (zh) 侧行信道配置方法、终端设备和网络设备
WO2019033416A1 (zh) 无线通信的方法、终端设备和网络设备
WO2018137209A1 (zh) 一种业务数据传输方法、第一通信节点及基站
WO2020062079A1 (zh) 数据传输方法、发射端设备和接收端设备
TWI785085B (zh) 支援資料重複的方法、發射端設備和接收端設備
WO2019127266A1 (zh) 无线通信的方法、终端设备和网络设备
US11973848B2 (en) Apparatus, method and computer program
US11510199B2 (en) Wireless communication method, terminal device and network device
WO2023185956A1 (zh) 基于侧行链路的通信方法、装置、存储介质和芯片系统
CN116326027A (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: 17921797

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017921797

Country of ref document: EP

Effective date: 20200107

NENP Non-entry into the national phase

Ref country code: DE