WO2020199218A1 - 无线通信的方法和终端设备 - Google Patents
无线通信的方法和终端设备 Download PDFInfo
- Publication number
- WO2020199218A1 WO2020199218A1 PCT/CN2019/081585 CN2019081585W WO2020199218A1 WO 2020199218 A1 WO2020199218 A1 WO 2020199218A1 CN 2019081585 W CN2019081585 W CN 2019081585W WO 2020199218 A1 WO2020199218 A1 WO 2020199218A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- terminal device
- terminal
- requirement
- uplink
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 98
- 238000004891 communication Methods 0.000 title claims abstract description 43
- 230000005540 biological transmission Effects 0.000 claims abstract description 141
- 230000015654 memory Effects 0.000 claims description 44
- 238000004590 computer program Methods 0.000 claims description 33
- 238000013507 mapping Methods 0.000 claims description 15
- 230000011664 signaling Effects 0.000 claims description 13
- 230000001960 triggered effect Effects 0.000 claims description 9
- 230000009286 beneficial effect Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 10
- 230000001360 synchronised effect Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 4
- 230000003068 static effect Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 230000010267 cellular communication Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
-
- 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/54—Allocation or scheduling criteria for wireless resources based on quality criteria
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- 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/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
-
- 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
- H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
-
- 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
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
-
- 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
- H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
- H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
Definitions
- the embodiments of the present application relate to the field of communications, and in particular to a method and terminal device for wireless communication.
- a terminal device can trigger a Buffer State Report (BSR) to request uplink resources from a network device.
- BSR Buffer State Report
- UL grant uplink resource grant
- SR scheduling request
- Device-to-device communication is a side-link transmission technology based on Device to Device (D2D) technology.
- D2D Device to Device
- the Internet of Vehicles system is a system based on D2D technology, and traditional cellular communication systems need to be carried out through network equipment.
- the difference between data transmission and reception is that in the Internet of Vehicles system, terminal-to-terminal direct communication can be used, so it has higher spectrum efficiency and lower transmission delay.
- terminal devices need side-link resources for side-link communication. Therefore, for terminal devices, how to request side-link resources is an urgent problem to be solved.
- the embodiments of the present application provide a wireless communication method and terminal device.
- the terminal device can trigger a side-link BSR when side-line data transmission is required, and further determine whether to trigger an SR based on the first information to request the side Uplink resources.
- a wireless communication method including: a first terminal triggers a side-link buffer status report BSR, the side-link BSR is used to request the side-link for the first side-line data to be sent Path resource; the first terminal determines whether to trigger a scheduling request SR for requesting the side link resource according to the first information.
- a terminal device configured to execute the foregoing first aspect or any possible implementation of the first aspect.
- the device includes a unit for executing the foregoing first aspect or the method in any possible implementation manner of the first aspect.
- a terminal device in a third aspect, includes a processor and a memory.
- the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.
- a chip which is used to implement the method in the first aspect or its implementation manners.
- the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the method in the above-mentioned first aspect or each of its implementation modes.
- a computer-readable storage medium for storing a computer program that enables a computer to execute the method in the first aspect or its implementation manners.
- a computer program product including computer program instructions that cause a computer to execute the method in the first aspect or its implementation manners.
- a computer program which when running on a computer, causes the computer to execute the method in the first aspect or its implementation manners.
- the terminal device can trigger the side-link BSR when it needs to transmit side-line data, and further determine whether to trigger the SR according to the first information, which helps to ensure that the requested side-link resources meet actual transmission requirements.
- Fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
- FIG. 2 is a schematic diagram of a wireless communication method provided by an embodiment of the present application.
- Fig. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.
- Fig. 4 is a schematic block diagram of a communication device according to another embodiment of the present application.
- Fig. 5 is a schematic block diagram of a chip provided by an embodiment of the present application.
- D2D Device to Device
- a car networking system based on Long Term Evolution (LTE) for D2D communication, or based on new wireless To other equipment (New Radio Vehicle to Everything, NR-V2X) system.
- LTE Long Term Evolution
- NR-V2X new wireless To other equipment
- the Internet of Vehicles system uses terminal-to-terminal direct communication, so it has higher spectrum efficiency and lower Transmission delay.
- the communication system based on the Internet of Vehicles system may be the Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (Wideband Code Division) system.
- GSM Global System of Mobile Communication
- CDMA Code Division Multiple Access
- Wideband Code Division Wideband Code Division Multiple Access
- Multiple Access (WCDMA) system General Packet Radio Service (GPRS), LTE system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), General Mobile communication system (Universal Mobile Telecommunication System, UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5G New Radio (NR) system, etc.
- GPRS General Packet Radio Service
- LTE LTE Frequency Division Duplex
- TDD Time Division Duplex
- UMTS General Mobile communication system
- WiMAX Worldwide Interoperability for Microwave Access
- 5G New Radio (NR) system etc.
- the terminal device in the embodiment of the present application may be a terminal device capable of implementing D2D communication.
- it may be a vehicle-mounted terminal device, a terminal device in a 5G network, or a terminal device in a public land mobile communication network (Public Land Mobile Network, PLMN) that will evolve in the future, which is not limited in the embodiment of the present application.
- PLMN Public Land Mobile Network
- Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
- Figure 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
- the terminal device is not limited in this embodiment of the application.
- the wireless communication system may also include mobile management entities (Mobile Management Entity, MME), Serving Gateway (Serving Gateway, S-GW), Packet Data Network Gateway (Packet Data Network Gateway, P-GW) and other networks Entity, or the wireless communication system may also include session management function (Session Management Function, SMF), unified data management (Unified Data Management, UDM), authentication server function (Authentication Server Function, AUSF) and other network entities.
- MME Mobile Management Entity
- S-GW Serving Gateway
- Packet Data Network Gateway Packet Data Network Gateway
- P-GW Packet Data Network Gateway
- SMF Session Management Function
- UDM Unified Data Management
- AUSF Authentication Server Function
- terminal devices can communicate in mode A and mode B.
- the terminal device 121 and the terminal device 122 may communicate in a D2D communication mode.
- the terminal device 121 and the terminal device 122 directly communicate through a D2D link, that is, a side link (SideLink, SL).
- a D2D link that is, a side link (SideLink, SL).
- the transmission resources of the terminal equipment are allocated by the base station, and the terminal equipment can send data on the SL according to the resources allocated by the base station.
- the base station can allocate resources for a single transmission to the terminal device, or allocate resources for semi-static transmission to the terminal.
- the terminal device adopts a sensing plus reservation (reservation) transmission mode, and the terminal device independently selects transmission resources from the SL resources.
- the terminal device obtains a set of available transmission resources in the resource pool by means of interception, and the terminal device randomly selects a resource from the set of available transmission resources for data transmission.
- mode A and mode B are only exemplary descriptions of two transmission modes, and other transmission modes may be defined.
- mode C and mode D are introduced in NR-V2X.
- Mode C means that the side link transmission resources of the terminal device are allocated by the base station
- mode D means that the side link transmission resources of the terminal device are selected by the terminal. of.
- D2D communication may refer to vehicle to vehicle (Vehicle to Vehicle, "V2V”) communication or vehicle to other device (Vehicle to Everything, V2X) communication.
- V2X communication X can generally refer to any device with wireless receiving and sending capabilities, such as but not limited to slow-moving wireless devices, fast-moving vehicle-mounted devices, or network control nodes with wireless transmitting and receiving capabilities. It should be understood that the embodiment of the present invention 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 the embodiment of the present application.
- FIG. 2 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.
- the method may be executed by a terminal device in a car networking system, such as a terminal device 121 or a terminal device 122, as shown in FIG.
- Method 200 includes:
- the first terminal triggers a side link buffer status report BSR, where the side link BSR is used to request side link resources for the first side link data to be sent;
- S220 The first terminal determines whether to trigger a scheduling request SR for requesting the side link resource according to the first information.
- the first terminal needs to send side-line data to other terminals, such as the second terminal, it needs side-line link resources. If there is no side-line link resource, it needs to request the network device for the side-line link. Resources.
- the terminal device can trigger a side-link BSR, and the side-link BSR can be used to request side-link resources for side-line data transmission.
- the first side row data to be sent may be a logical channel that triggers the side link BSR, or a logical channel group (Logic Channel Group, which triggers the side link BSR) LCG).
- the first terminal can trigger the side link BSR.
- the first terminal triggers the side-link BSR, and the side-link BSR is in the Pending state at this time, that is, the first terminal is ready to send but not to The network device sends the side link BSR.
- the first side row data includes data in a data radio bearer (Data Radio Bearer, DRB) and/or data in a signaling radio bearer (Signalling Radio Bearer, SRB).
- DRB Data Radio Bearer
- SRB Signaling Radio Bearer
- the SRB may be used to carry side link radio resource control (Radio Resource Control, RRC) signaling and/or side link PC5 interface signaling (PC5Signalling, PC5- S).
- RRC Radio Resource Control
- PC5Signalling PC5- S
- the QoS attribute of the SRB is configured by a network device or is pre-configured.
- the QoS attribute of the SRB may include priority, and optionally, may also include other attributes such as delay.
- the first terminal may determine whether to trigger an SR according to the first information when the side link BSR is triggered, so as to request the side link resource through the SR.
- the side link BSR may not be sent.
- the network device may allocate the side link resource to the first terminal.
- the side row resource cannot meet the transmission requirement of the side row data. For example, if the size of the side row link resource is not enough to transmit the first side row data to be sent, the first terminal can further trigger the side row link BSR by The side link BSR requests side link resources from the network device.
- the first terminal may also initiate a random access procedure to the network device Request uplink authorization resources.
- the first information may include:
- the first terminal has available side link resources for initial transmission, and/or whether the available side link resources for initial transmission meets the transmission requirement of the first side line data.
- the first terminal may determine to trigger an SR, and further send the SR to the network device.
- the first terminal may determine not to trigger SR if the first terminal is configured with available side link resources for initial transmission.
- the first terminal can determine whether to trigger the SR according to whether there are available side link resources for initial transmission (ie, new transmission).
- the first terminal may further determine whether the available side link resources meet the requirements of the first side link resources. Data transmission requirements, determine whether to trigger SR, in this way, it is helpful to ensure that the requested side-line link resources can meet the side-line data transmission requirements.
- the first terminal may determine to trigger the SR, and further send the SR to the network device.
- the first terminal may determine not to trigger the SR, and use the available side link resource to send the first side link data.
- the available side link resources that cannot meet the transmission requirement of the first side row data include at least one of the following:
- the available side link resource and the first side row data do not satisfy the first mapping relationship
- the available side link resource does not meet the delay requirement of the first side row data
- the size of the available side link resources is not enough to transmit the first side link data.
- the first terminal may further determine whether the actual transmission requirement is met according to the attribute of the available link resource, and determine whether to trigger the SR Therefore, when the available link resource does not meet the actual transmission demand, the SR can be triggered, and the side link resource is further requested through the SR, which is beneficial to ensure that the side link resource that meets the actual transmission demand is requested.
- the situation where the available side link resources cannot meet the transmission demand of the first side data is only an example, and the transmission demand of the side data may also include other parameters that affect transmission performance, such as , Quality-of-Service (QoS) requirements, priority, reliability requirements, etc., which are not specifically limited in the embodiment of the present application.
- QoS Quality-of-Service
- the first mapping relationship may be a mapping relationship between the sideline data that triggers the sideline BSR and the attribute of the sideline link resource.
- the first mapping relationship may be the relationship between the logical channel or logical channel group that triggers the side link BSR and the attribute of the side link resource.
- the sideline data that triggers the sideline BSR requires sidelink resources corresponding to specific attributes. If the attributes of the available sidelink resources correspond to the sidelinks mapped by the first sideline data If the attributes of the resources are different, the available side link resources and the first side link data do not satisfy the first mapping relationship. In this case, the first terminal can trigger an SR, and further request to satisfy the side link through the SR The resource is beneficial to requesting side link resources that satisfy the specific attribute of the first mapping relationship.
- the first terminal may further determine whether to trigger SR based on the current data packetization situation, for example, If the data has been packaged, that is, the BSR can no longer be assembled into the data packet.
- the first terminal can trigger the SR, specifically, it can send (Physical Uplink Control Channel, PUCCH), the SR is sent to the network device through the PUCCH.
- PUCCH Physical Uplink Control Channel
- the first information may also include at least one of the following:
- the first terminal has available physical uplink control channel PUCCH resources, and/or information about the conflicting data of the SR.
- the PUCCH resource is a PUCCH resource mapped to a logical channel or logical channel group corresponding to the first side row data.
- Embodiment 3 The first terminal determines whether to trigger the SR according to whether the first terminal is configured with available PUCCH resources.
- the SR may be sent through PUCCH resources.
- the first terminal determines whether to trigger the SR according to whether the first terminal is configured with available PUCCH resources.
- the first terminal may be configured with available PUCCH resources. In the case of resources, determine to trigger SR, or determine not to trigger SR when no available PUCCH resources are configured.
- the first terminal may also determine whether to trigger the SR according to the information of the conflicting data of the SR.
- the conflicting data information of the SR includes at least one of the following:
- the first terminal may only send uplink data or sideline data at the same time. Therefore, in this embodiment of the application, the first terminal may according to whether there is currently uplink data and side line data that conflict with the SR. / Or side line data, determine whether to trigger SR, or, in the case of uplink data and/or side line data to be sent, the first terminal may further combine the uplink data and/or side line data to be sent Attribute to determine whether to trigger SR.
- Embodiment 5 With reference to Embodiment 5 to Embodiment 9, the specific implementation of this Embodiment 4 will be described.
- Embodiment 5 The first terminal determines whether to trigger the SR according to whether there is uplink data to be sent that conflicts with the SR.
- the first terminal may determine not to trigger the SR when there is uplink data to be transmitted that conflicts with the SR, or determine to trigger the SR when there is no uplink data to be transmitted that conflicts with the SR. .
- Embodiment 6 The first terminal determines whether to trigger the SR according to the importance level of the uplink data to be sent that conflicts with the SR.
- the first terminal may determine to trigger the SR when the importance level of the uplink data is lower than the importance level of the first side line data, that is, send SR first to request the side line chain of the first side line data Road resources.
- the importance of the SR is higher than the importance of the uplink data, or in other words, the priority of the SR is higher than the priority of the uplink data.
- the first terminal may determine to trigger an SR when the importance level of the uplink data is lower than a specific importance level threshold, that is, send the SR preferentially to request the side link resource of the first side line data.
- the importance level of the uplink message in the random access process can be considered to be high.
- the first terminal may determine to trigger the SR when the uplink data is not an uplink message in the random access process.
- the uplink message in the random access process is a message 3 (MSG3) for requesting uplink resources in the random access process.
- MSG3 message 3
- Embodiment 7 The first terminal determines whether to trigger the SR according to the transmission demand of the uplink data to be sent that conflicts with the SR.
- the first terminal may determine not to trigger SR, and send uplink data first.
- the first terminal may determine to trigger the SR, and send the SR first to request the side link resource for sending the first side row data.
- the first terminal can determine to trigger the SR, and send the SR first to Request a side link resource for sending the first side row data.
- the transmission demand of the uplink data is higher than the specific transmission demand threshold, in this case, it can be considered that the priority of the SR is lower than the priority of the uplink data, and the first terminal can determine not to trigger the SR and send the uplink data first .
- the transmission requirement may be a delay requirement, a QoS requirement, a reliability requirement, etc.
- the transmission requirement threshold may be a delay requirement threshold, a QoS requirement threshold, a reliability requirement threshold, etc.
- the transmission requirement of the uplink data being lower than the transmission requirement of the first side line data includes at least one of the following:
- the priority of the uplink data is lower than the priority of the first side row data
- the quality of service QoS requirement of the uplink data is lower than the QoS requirement of the first side line data
- the QoS requirement of the uplink data is the QoS requirement in the first QoS requirement set
- the delay requirement of the uplink data is lower than the delay requirement of the first side line data.
- the first set of QoS requirements may be pre-configured or configured by a network device.
- the network device may configure one or more QoS requirements to form the first QoS requirement set.
- the QoS requirements in the first QoS set are lower than a specific QoS requirement threshold.
- the QoS requirements in the first QoS requirement set may be considered to be QoS requirements with lower priority.
- the first terminal may determine to trigger the SR.
- the delay requirement of the uplink data being lower than the delay requirement of the first side line data includes: the uplink data does not include call data.
- the first terminal may further combine the transmission demand of the uplink data to determine whether to trigger the SR.
- the transmission demand of the uplink data may be lower than that of the first side line data.
- SR is sent first to request side link resources for the first side line data, or, when the transmission demand of uplink data is higher than the transmission demand of the first side line data, priority is given Send uplink data to meet the transmission demand of uplink data first.
- Embodiment 8 The first terminal determines whether to trigger the SR according to whether there is sideline data to be sent that conflicts with the SR.
- the first terminal may determine not to trigger the SR when there is sideline data to be sent that conflicts with the SR, or determine that there is no sideline data to be sent that conflicts with the SR Trigger SR.
- Embodiment 9 The first terminal determines whether to trigger the SR according to the transmission demand of the second side line data to be sent that conflicts with the SR.
- the first terminal may determine not to trigger the SR and send the second side line data first.
- the first terminal may determine to trigger the SR, and send the SR first, so as to request the side line link resource for the first side line data.
- the first terminal may determine to trigger the SR , Send SR first, so as to request side link resources for the first side row data.
- the first terminal may determine not to trigger SR, send the second side line data first, so as to meet the transmission demand of the second side line data.
- the transmission requirement may be a delay requirement, a QoS requirement, a reliability requirement, etc.
- the transmission requirement threshold may be a delay requirement threshold, a QoS requirement threshold, a reliability requirement threshold, etc.
- the transmission requirement of the second side row data is lower than the transmission requirement of the first side row data includes at least one of the following:
- the priority of the second side row data is lower than the priority of the first side row data
- the QoS requirement of the second side row data is lower than the QoS requirement of the first side row data
- the delay requirement of the second side row data is lower than the delay requirement of the first side row data.
- the QoS requirement of the second side row data is the QoS requirement in the second QoS requirement set.
- the second set of QoS requirements is pre-configured or configured by a network device.
- the network device may configure one or more QoS requirements to form the second QoS requirement set.
- the QoS requirements in the second QoS set are lower than a specific QoS requirement threshold.
- the QoS requirements in the second QoS requirement set can be considered as lower priority QoS requirements.
- the first terminal may determine to trigger the SR.
- the first terminal can further determine whether to trigger the SR in the case of the second side line data that conflicts with the SR, according to the transmission demand of the second side line data. For example, it can transmit the second side line data.
- the SR is sent first to request side link resources for the first side line data, or the transmission demand of the second side line data is higher than the first side line data transmission demand.
- the second side line data is sent first to satisfy the transmission demand of the second side line data first.
- the first terminal can further implement the fourth to the fourth embodiments when the PUCCH resource is available.
- the first terminal may further determine whether to trigger the SR according to the information of the conflicting data of the SR.
- the first terminal may combine the important information of the uplink data that conflicts with the SR. Level and transmission requirements to determine whether to trigger SR.
- the first terminal may determine to trigger SR when the uplink data is an uplink message in a random access process, or when the uplink data is not an uplink message in a random access process
- the transmission requirements of the uplink data are further gathered to determine whether to trigger SR, etc., which is not limited in the embodiment of the present application.
- the first information may only include the content included in the first information in Embodiment 1, or may only include the content included in the first information in Embodiment 2, or it may also Both are included, which is not limited in the embodiments of the present application.
- the first terminal can determine whether to trigger the SR based on the available side link resources, the available PUCCH resources, and the data conflicting with the SR. It is beneficial to ensure that when the currently available side link resources do not meet the demand, new side link resources are requested through the SR.
- FIG. 3 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 3, the device 400 includes:
- the trigger module 410 is configured to trigger a side-link buffer status report BSR, where the side-link BSR is used to request side-link resources for the first side-line data to be sent;
- the determining module 420 is configured to determine whether to trigger the scheduling request SR for requesting the side link resource according to the first information.
- the first information includes:
- the terminal device has available side link resources for initial transmission, and/or whether the available side link resources for initial transmission meets the transmission requirement of the first side line data.
- the determining module 420 is specifically configured to:
- the terminal device has no available side link resources for initial transmission
- the terminal device has available side link resources for initial transmission, and the available side link resources cannot meet the transmission demand of the first side line data;
- the terminal device has available side link resources for initial transmission, and the data has been packaged.
- the available side link resources that cannot meet the transmission requirement of the first side row data include at least one of the following:
- the available side link resource and the first side row data do not satisfy the first mapping relationship
- the available side link resource does not meet the delay requirement of the first side link data.
- the first mapping relationship is a mapping relationship between sideline data that triggers the sideline BSR and an attribute of the sideline link resource.
- the first information includes:
- the terminal device has available physical uplink control channel PUCCH resources, and/or information about the conflicting data of the SR.
- the conflict data information of the SR includes at least one of the following:
- the determining module 420 is specifically configured to:
- the terminal equipment has available physical uplink control channel PUCCH resources;
- the terminal device has no uplink data to be sent that conflicts with the SR;
- the terminal device has uplink data to be sent that conflicts with the SR, and the importance level of the uplink data is lower than the importance level of the SR;
- the terminal device has uplink data to be sent that conflicts with the SR, and the transmission demand of the uplink data is lower than the transmission demand of the first side row data;
- the terminal device has no second side line data to be sent that conflicts with the SR;
- the terminal device has second side line data to be sent that conflicts with the SR, and the transmission demand of the second side line data is lower than the transmission demand of the first side line data.
- the importance level of the uplink data being lower than the importance level of the SR includes:
- the uplink data does not include uplink messages in the random access process.
- the uplink message is a message 3 for requesting uplink resources in a random access process.
- the transmission requirement of the uplink data being lower than the transmission requirement of the first side line data includes at least one of the following:
- the priority of the uplink data is lower than the priority of the first side row data
- the quality of service QoS requirement of the uplink data is lower than the QoS requirement of the first side line data
- the QoS requirement of the uplink data is the QoS requirement in the first QoS requirement set
- the delay requirement of the uplink data is lower than the delay requirement of the first side row data.
- the first set of QoS requirements is pre-configured or configured by a network device.
- the QoS requirement in the first QoS set is lower than a specific QoS requirement threshold.
- the delay requirement of the uplink data being lower than the delay requirement of the first side line data includes: the uplink data does not include call data.
- the transmission requirement of the second side row data being lower than the transmission requirement of the first side row data includes at least one of the following:
- the priority of the second side row data is lower than the priority of the first side row data
- the QoS requirement of the second side row data is lower than the QoS requirement of the first side row data
- the delay requirement of the second side row data is lower than the delay requirement of the first side row data.
- the QoS requirement of the second side row data is the QoS requirement in the second QoS requirement set.
- the second QoS set is pre-configured or configured by a network device.
- the QoS requirement in the second QoS set is lower than a specific QoS requirement threshold.
- the PUCCH resource is a PUCCH resource mapped to a logical channel or logical channel group corresponding to the first side row data.
- the first sideline data that triggers the sidelink BSR includes at least one of the following:
- the logical channel of the side link BSR is triggered, and the logical channel group of the side link BSR is triggered.
- the first side row data includes data in a data radio bearer DRB, and/or data in a signaling radio bearer SRB.
- the SRB is used to carry side link radio resource control (Radio Resource Control, RRC) signaling and/or side link PC5 interface signaling (PC5Signalling, PC5-S). ).
- RRC Radio Resource Control
- PC5Signalling PC5-S
- the QoS attribute of the SRB is configured by a network device or is pre-configured.
- the QoS attribute of the SRB may include priority, and optionally, may also include other attributes such as delay.
- terminal device 400 may correspond to the first terminal in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of the various units in the terminal device 400 are respectively intended to realize the The corresponding process of the first terminal in the method 200 is not repeated here for brevity.
- FIG. 4 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
- the communication device 600 shown in FIG. 4 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
- the communication device 600 may further include a memory 620.
- the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
- the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
- the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
- the transceiver 630 may include a transmitter and a receiver.
- the transceiver 630 may further include an antenna, and the number of antennas may be one or more.
- the communication device 600 may specifically be the first terminal of the embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the first terminal in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.
- Fig. 5 is a schematic structural diagram of a chip of an embodiment of the present application.
- the chip 700 shown in FIG. 5 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
- the chip 700 may further include a memory 720.
- the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
- the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
- the chip 700 may further include an input interface 730.
- the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
- the chip 700 may further include an output interface 740.
- the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
- the chip can be applied to the first terminal in the embodiment of the present application, and the chip can implement the corresponding process implemented by the first terminal in each method of the embodiment of the present application.
- the chip can implement the corresponding process implemented by the first terminal in each method of the embodiment of the present application.
- the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
- the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
- the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
- the aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
- DSP Digital Signal Processor
- ASIC application specific integrated circuit
- FPGA ready-made programmable gate array
- the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
- the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
- the software module can be located in a mature storage medium in the field, such as random memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
- the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
- the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
- the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
- RAM random access memory
- SRAM static random access memory
- DRAM dynamic random access memory
- DRAM synchronous dynamic random access memory
- SDRAM double data rate synchronous dynamic random access memory
- Double Data Rate SDRAM DDR SDRAM
- ESDRAM enhanced synchronous dynamic random access memory
- Synchlink DRAM SLDRAM
- DR RAM Direct Rambus RAM
- the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
- the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
- the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
- the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
- I will not repeat it here.
- the embodiments of the present application also provide a computer program product, including computer program instructions.
- the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I won't repeat them here.
- the embodiment of the present application also provides a computer program.
- the computer program can be applied to the network device in the embodiment of the present application.
- the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- I won’t repeat it here.
- the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
- the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
- the disclosed system, device, and method may be implemented in other ways.
- the device embodiments described above are only illustrative.
- the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
- 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, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
- the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (49)
- 一种无线通信的方法,其特征在于,包括:第一终端触发侧行链路缓存状态报告BSR,所述侧行链路BSR用于为待发送的第一侧行数据请求侧行链路资源;所述第一终端根据第一信息,确定是否触发用于请求所述侧行链路资源的调度请求SR。
- 根据权利要求1所述的方法,其特征在于,所述第一信息包括:所述第一终端是否有用于初传的可用侧行链路资源,和/或所述用于初传的可用侧行链路资源是否满足所述第一侧行数据的传输需求。
- 根据权利要求2所述的方法,其特征在于,所述第一终端根据第一信息,确定是否触发用于请求所述侧行链路资源的调度请求SR,包括:若满足以下条件中的至少一个,所述第一终端确定触发所述SR:所述第一终端没有用于初传的可用侧行链路资源;所述第一终端有用于初传的可用侧行链路资源,且所述可用侧行链路资源不能满足所述第一侧行数据的传输需求;所述第一终端有用于初传的可用侧行链路资源,且数据已组包完成。
- 根据权利要求3所述的方法,其特征在于,所述可用侧行链路资源不能满足所述第一侧行数据的传输需求包括以下中的至少一项:所述可用侧行链路资源和所述第一侧行数据不满足第一映射关系;所述可用侧行链路资源不满足所述第一侧行数据的时延要求。
- 根据权利要求4所述的方法,其特征在于,所述第一映射关系为触发所述侧行链路BSR的侧行数据和侧行链路资源的属性的映射关系。
- 根据权利要求1至5中任一项所述的方法,其特征在于,所述第一信息包括:所述第一终端是否有可用的物理上行控制信道PUCCH资源,和/或所述SR的冲突数据的信息。
- 根据权利要求6所述的方法,其特征在于,所述SR的冲突数据的信息包括以下中的至少一项:是否有与所述SR冲突的待发送的上行数据;与所述SR冲突的所述上行数据的重要等级;与所述SR冲突的所述上行数据的传输需求;是否有与所述SR冲突的待发送的侧行数据;与所述SR冲突的所述侧行数据的传输需求。
- 根据权利要求7所述的方法,其特征在于,所述第一终端根据第一信息,确定是否触发用于请求所述侧行链路资源的调度请求SR,包括:若满足以下条件中的至少一个,所述第一终端确定触发所述SR:所述第一终端有可用的物理上行控制信道PUCCH资源;所述第一终端没有与所述SR相冲突的待发送的上行数据;所述第一终端有与所述SR相冲突的待发送的上行数据,且所述上行数据的重要等级低于所述SR的重要等级;所述第一终端有与所述SR相冲突的待发送的上行数据,且所述上行数据的传输需求低于所述第一侧行数据的传输需求;所述第一终端没有与所述SR相冲突的待发送的第二侧行数据;所述第一终端有与所述SR相冲突的待发送的第二侧行数据,且所述第二侧行数据的传输需求低于所述第一侧行数据的传输需求。
- 根据权利要求8所述的方法,其特征在于,所述上行数据的重要等级低于所述SR的重要等级包括:所述上行数据中不包括随机接入过程中的上行消息。
- 根据权利要求9所述的方法,其特征在于,所述上行消息为随机接入过程中的用于请求上行资源的消息3。
- 根据权利要求8至10中任一项所述的方法,其特征在于,所述上行数据的传输需求低于所述第一侧行数据的传输需求包括以下中的至少一项:所述上行数据的优先级低于所述第一侧行数据的优先级;所述上行数据的服务质量QoS要求低于所述第一侧行数据的QoS要求;所述上行数据的QoS要求为第一QoS要求集合中的QoS要求;所述上行数据的时延需求低于所述第一侧行数据的时延需求。
- 根据权利要求11所述的方法,其特征在于,所述第一QoS要求集合为预配置的,或者网络设备配置的。
- 根据权利要求11或12所述的方法,其特征在于,所述第一QoS集合中的QoS要求低于特定QoS要求阈值。
- 根据权利要求11至13中任一项所述的方法,其特征在于,所述上行数据的时延需求低于所述第一侧行数据的时延需求包括:所述上行数据不包括通话数据。
- 根据权利要求8至14中任一项所述的方法,其特征在于,所述第二侧行数据的 传输需求低于所述第一侧行数据的传输需求包括以下中的至少一项:所述第二侧行数据的优先级低于所述第一侧行数据的优先级;所述第二侧行数据的QoS要求低于所述第一侧行数据的QoS要求;所述第二侧行数据的时延需求低于所述第一侧行数据的时延需求;所述第二侧行数据的QoS要求为第二QoS要求集合中的QoS要求。
- 根据权利要求15所述的方法,其特征在于,所述第二QoS集合为预配置的,或者网络设备配置的。
- 根据权利要求15或16所述的方法,其特征在于,所述第二QoS集合中的QoS要求低于特定QoS要求阈值。
- 根据权利要求8至17中任一项所述的方法,其特征在于,所述PUCCH资源为所述第一侧行数据对应的逻辑信道或逻辑信道组所映射的PUCCH资源。
- 根据权利要求1至18中任一项所述的方法,其特征在于,所述触发所述侧行链路BSR的所述第一侧行数据包括以下中的至少一种:触发所述侧行链路BSR的逻辑信道,触发所述侧行链路BSR的逻辑信道组。
- 根据权利要求1至19中任一项所述的方法,其特征在于,所述第一侧行数据包括数据无线承载DRB中的数据,和/或信令无线承载SRB中的数据。
- 根据权利要求20所述的方法,其特征在于,所述SRB用于承载侧行链路的无线资源控制RRC信令和/或侧行链路PC5接口信令PC5-S。
- 根据权利要求20或21所述的方法,其特征在于,所述SRB的QoS属性是由网络设备配置的或者是预配置的。
- 一种终端设备,其特征在于,包括:触发模块,用于触发侧行链路缓存状态报告BSR,所述侧行链路BSR用于为待发送的第一侧行数据请求侧行链路资源;确定模块,用于根据第一信息,确定是否触发用于请求所述侧行链路资源的调度请求SR。
- 根据权利要求23所述的终端设备,其特征在于,所述第一信息包括:所述终端设备是否有用于初传的可用侧行链路资源,和/或所述用于初传的可用侧行链路资源是否满足所述第一侧行数据的传输需求。
- 根据权利要求24所述的终端设备,其特征在于,所述确定模块具体用于:若满足以下条件中的至少一个,确定触发所述SR:所述终端设备没有用于初传的可用侧行链路资源;所述终端设备有用于初传的可用侧行链路资源,且所述可用侧行链路资源不能满足所述第一侧行数据的传输需求;所述终端设备有用于初传的可用侧行链路资源,且数据已组包完成。
- 根据权利要求25所述的终端设备,其特征在于,所述可用侧行链路资源不能满足所述第一侧行数据的传输需求包括以下中的至少一项:所述可用侧行链路资源和所述第一侧行数据不满足第一映射关系;所述可用侧行链路资源不满足所述第一侧行数据的时延要求。
- 根据权利要求26所述的终端设备,其特征在于,所述第一映射关系为触发所述侧行链路BSR的侧行数据和侧行链路资源的属性的映射关系。
- 根据权利要求23至27中任一项所述的终端设备,其特征在于,所述第一信息包括:所述终端设备是否有可用的物理上行控制信道PUCCH资源,和/或所述SR的冲突数据的信息。
- 根据权利要求28所述的终端设备,其特征在于,所述SR的冲突数据的信息包括以下中的至少一项:是否有与所述SR冲突的待发送的上行数据;与所述SR冲突的所述上行数据的重要等级;与所述SR冲突的所述上行数据的传输需求;是否有与所述SR冲突的待发送的侧行数据;与所述SR冲突的所述侧行数据的传输需求。
- 根据权利要求29所述的终端设备,其特征在于,所述确定模块具体用于:若满足以下条件中的至少一个,确定触发所述SR:所述终端设备有可用的物理上行控制信道PUCCH资源;所述终端设备没有与所述SR相冲突的待发送的上行数据;所述终端设备有与所述SR相冲突的待发送的上行数据,且所述上行数据的重要等级低于所述SR的重要等级;所述终端设备有与所述SR相冲突的待发送的上行数据,且所述上行数据的传输需求低于所述第一侧行数据的传输需求;所述终端设备没有与所述SR相冲突的待发送的第二侧行数据;所述终端设备有与所述SR相冲突的待发送的第二侧行数据,且所述第二侧行数据的传输需求低于所述第一侧行数据的传输需求。
- 根据权利要求30所述的终端设备,其特征在于,所述上行数据的重要等级低于所述SR的重要等级包括:所述上行数据中不包括随机接入过程中的上行消息。
- 根据权利要求31所述的终端设备,其特征在于,所述上行消息为随机接入过程中的用于请求上行资源的消息3。
- 根据权利要求30至32中任一项所述的终端设备,其特征在于,所述上行数据的传输需求低于所述第一侧行数据的传输需求包括以下中的至少一项:所述上行数据的优先级低于所述第一侧行数据的优先级;所述上行数据的服务质量QoS要求低于所述第一侧行数据的QoS要求;所述上行数据的QoS要求为第一QoS要求集合中的QoS要求;所述上行数据的时延需求低于所述第一侧行数据的时延需求。
- 根据权利要求33所述的终端设备,其特征在于,所述第一QoS要求集合为预配置的,或者网络设备配置的。
- 根据权利要求33或34所述的终端设备,其特征在于,所述第一QoS集合中的QoS要求低于特定QoS要求阈值。
- 根据权利要求33至35中任一项所述的终端设备,其特征在于,所述上行数据的时延需求低于所述第一侧行数据的时延需求包括:所述上行数据不包括通话数据。
- 根据权利要求30至36中任一项所述的终端设备,其特征在于,所述第二侧行数据的传输需求低于所述第一侧行数据的传输需求包括以下中的至少一项:所述第二侧行数据的优先级低于所述第一侧行数据的优先级;所述第二侧行数据的QoS要求低于所述第一侧行数据的QoS要求;所述第二侧行数据的时延需求低于所述第一侧行数据的时延需求;所述第二侧行数据的QoS要求为第二QoS要求集合中的QoS要求。
- 根据权利要求37所述的终端设备,其特征在于,所述第二QoS集合为预配置的,或者网络设备配置的。
- 根据权利要求37或38所述的终端设备,其特征在于,所述第二QoS集合中的QoS要求低于特定QoS要求阈值。
- 根据权利要求30至39中任一项所述的终端设备,其特征在于,所述PUCCH资源为所述第一侧行数据对应的逻辑信道或逻辑信道组所映射的PUCCH资源。
- 根据权利要求23至40中任一项所述的终端设备,其特征在于,所述触发所述侧行链路BSR的所述第一侧行数据包括以下中的至少一种:触发所述侧行链路BSR的逻辑信道,触发所述侧行链路BSR的逻辑信道组。
- 根据权利要求23至41中任一项所述的终端设备,其特征在于,所述第一侧行数据包括数据无线承载DRB中的数据,和/或信令无线承载SRB中的数据。
- 根据权利要求42所述的终端设备,其特征在于,所述SRB用于承载侧行链路的无线资源控制RRC信令和/或侧行链路PC5接口信令PC5-S。
- 根据权利要求42或43所述的终端设备,其特征在于,所述SRB的QoS属性是由网络设备配置的或者是预配置的。
- 一种终端设备,其特征在于,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求1至22中任一项所述的方法。
- 一种芯片,其特征在于,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至22中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至22中任一项所述的方法。
- 一种计算机程序产品,其特征在于,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至22中任一项所述的方法。
- 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求1至22中任一项所述的方法。
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19922312.4A EP3930395B1 (en) | 2019-04-04 | 2019-04-04 | Method for wireless communication and terminal device |
KR1020217032655A KR20210148175A (ko) | 2019-04-04 | 2019-04-04 | 무선 통신 방법 및 단말 디바이스 |
CN201980089689.0A CN113348710A (zh) | 2019-04-04 | 2019-04-04 | 无线通信的方法和终端设备 |
PCT/CN2019/081585 WO2020199218A1 (zh) | 2019-04-04 | 2019-04-04 | 无线通信的方法和终端设备 |
JP2021558859A JP7476227B2 (ja) | 2019-04-04 | 2019-04-04 | 無線通信方法及び端末デバイス |
BR112021019008A BR112021019008A2 (pt) | 2019-04-04 | 2019-04-04 | Método para comunicação sem fio e dispositivo terminal |
CN202111108931.XA CN113873572A (zh) | 2019-04-04 | 2019-04-04 | 无线通信的方法和终端设备 |
US17/488,072 US20220022230A1 (en) | 2019-04-04 | 2021-09-28 | Method for wireless communication and terminal device |
JP2023168427A JP2023169410A (ja) | 2019-04-04 | 2023-09-28 | 無線通信方法及び端末デバイス |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2019/081585 WO2020199218A1 (zh) | 2019-04-04 | 2019-04-04 | 无线通信的方法和终端设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/488,072 Continuation US20220022230A1 (en) | 2019-04-04 | 2021-09-28 | Method for wireless communication and terminal device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020199218A1 true WO2020199218A1 (zh) | 2020-10-08 |
Family
ID=72664725
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/081585 WO2020199218A1 (zh) | 2019-04-04 | 2019-04-04 | 无线通信的方法和终端设备 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20220022230A1 (zh) |
EP (1) | EP3930395B1 (zh) |
JP (2) | JP7476227B2 (zh) |
KR (1) | KR20210148175A (zh) |
CN (2) | CN113873572A (zh) |
BR (1) | BR112021019008A2 (zh) |
WO (1) | WO2020199218A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11792841B2 (en) * | 2022-01-13 | 2023-10-17 | Qualcomm Incorporated | Sidelink intra-UE prioritization |
KR20240127200A (ko) * | 2023-02-15 | 2024-08-22 | 삼성전자주식회사 | 무선 통신 시스템에서 중요도가 다른 xr 트래픽을 서비스 하기 위한 방법 및 장치 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016181094A1 (en) * | 2015-05-14 | 2016-11-17 | Blackberry Limited | Transmitting a scheduling request for a device-to-device transmission |
CN107333334A (zh) * | 2016-04-29 | 2017-11-07 | 普天信息技术有限公司 | 副链路半持续调度的配置方法和装置 |
CN108633074A (zh) * | 2017-03-23 | 2018-10-09 | 华硕电脑股份有限公司 | 无线通信系统中报告侧链路服务的辅助信息的方法和设备 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
PT2922360T (pt) * | 2014-03-21 | 2019-04-24 | Sun Patent Trust | Procedimento de solicitação de programação para comunicação d2d |
US9907056B2 (en) * | 2014-08-06 | 2018-02-27 | Futurewei Technologies, Inc. | System and method for allocating resources for device-to-device communications |
CN108347784B (zh) * | 2017-01-23 | 2023-10-13 | 华为技术有限公司 | 一种资源调度方法以及无线接入网设备和终端设备 |
WO2018148893A1 (zh) * | 2017-02-15 | 2018-08-23 | 华为技术有限公司 | 数据传输方法和设备 |
CN116437465A (zh) * | 2017-03-24 | 2023-07-14 | 北京三星通信技术研究有限公司 | 窄带物联网系统中调度请求上报的方法和装置 |
US11706721B2 (en) * | 2019-06-17 | 2023-07-18 | Ofinno, Llc | Power control of sidelink operation |
-
2019
- 2019-04-04 KR KR1020217032655A patent/KR20210148175A/ko not_active Application Discontinuation
- 2019-04-04 CN CN202111108931.XA patent/CN113873572A/zh active Pending
- 2019-04-04 BR BR112021019008A patent/BR112021019008A2/pt not_active IP Right Cessation
- 2019-04-04 EP EP19922312.4A patent/EP3930395B1/en active Active
- 2019-04-04 WO PCT/CN2019/081585 patent/WO2020199218A1/zh unknown
- 2019-04-04 CN CN201980089689.0A patent/CN113348710A/zh active Pending
- 2019-04-04 JP JP2021558859A patent/JP7476227B2/ja active Active
-
2021
- 2021-09-28 US US17/488,072 patent/US20220022230A1/en active Pending
-
2023
- 2023-09-28 JP JP2023168427A patent/JP2023169410A/ja active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016181094A1 (en) * | 2015-05-14 | 2016-11-17 | Blackberry Limited | Transmitting a scheduling request for a device-to-device transmission |
CN107333334A (zh) * | 2016-04-29 | 2017-11-07 | 普天信息技术有限公司 | 副链路半持续调度的配置方法和装置 |
CN108633074A (zh) * | 2017-03-23 | 2018-10-09 | 华硕电脑股份有限公司 | 无线通信系统中报告侧链路服务的辅助信息的方法和设备 |
Non-Patent Citations (3)
Title |
---|
CATT: "Consideration on Uu MAC Due to V2X Transmission", 3GPP TSG-RAN WG2 MEETING #103BIS R2-1813730, 12 October 2018 (2018-10-12), XP051523225, DOI: 20191216163953A * |
HUAWEI ET AL.: "Potential RAN2 Impacts on gNB Scheduled Resource Allocation for NR V2X", 3GPP TSG-RAN WG2 # 104 R2-1816518, 16 November 2018 (2018-11-16), XP051480472, DOI: 20191216163644X * |
SAMSUNG: "Discussion on Uu-Based Sidelink Resource Allocation and Configuration", 3GPP TSG RAN WG1 #95 R1-1812989, 16 November 2018 (2018-11-16), XP051554968, DOI: 20191216163844A * |
Also Published As
Publication number | Publication date |
---|---|
EP3930395B1 (en) | 2023-09-13 |
CN113348710A (zh) | 2021-09-03 |
JP2022532471A (ja) | 2022-07-15 |
EP3930395A1 (en) | 2021-12-29 |
BR112021019008A2 (pt) | 2021-11-30 |
JP2023169410A (ja) | 2023-11-29 |
CN113873572A (zh) | 2021-12-31 |
KR20210148175A (ko) | 2021-12-07 |
US20220022230A1 (en) | 2022-01-20 |
EP3930395A4 (en) | 2022-03-23 |
JP7476227B2 (ja) | 2024-04-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
TWI805641B (zh) | D2d通訊中資源配置的方法、終端設備和網路設備 | |
US11317389B2 (en) | Data transmission method, apparatus, and system | |
US20210051675A1 (en) | Communication method and device | |
WO2020015727A1 (zh) | 路径选择的方法、终端设备和网络设备 | |
WO2020164152A1 (zh) | 无线通信的方法和设备 | |
WO2020056696A1 (zh) | 一种资源分配方法及装置、终端 | |
US11297602B2 (en) | Service data transmission method and apparatus | |
US11432370B2 (en) | D2D communication method and terminal device | |
WO2019061982A1 (zh) | 用于资源分配的方法、网络设备和通信设备 | |
JP2023169410A (ja) | 無線通信方法及び端末デバイス | |
WO2021026841A1 (zh) | 调度请求传输的方法和设备 | |
KR20220011649A (ko) | 정보 전송 방법 및 단말 기기 | |
WO2020258521A1 (zh) | 无线通信方法和终端设备 | |
WO2022227993A1 (zh) | 用于检测pscch的方法和通信装置 | |
WO2020051767A1 (zh) | 传输信息、接收信息的方法和通信设备 | |
WO2019174017A1 (zh) | 车联网中载波选择的方法和终端设备 | |
WO2019213806A1 (zh) | 通信方法和终端 | |
WO2020073259A1 (zh) | 一种传输反馈信息的方法和终端设备 | |
WO2020107412A1 (zh) | 无线通信方法和终端设备 | |
WO2019213893A1 (zh) | 通信方法和终端设备 | |
WO2021026928A1 (zh) | 无线通信的方法和设备 | |
WO2023133902A1 (zh) | 一种无线通信方法及装置、终端设备、网络设备 | |
WO2022267022A1 (zh) | 无线通信方法、终端设备和网络设备 | |
WO2020191757A1 (zh) | 一种终端的连接方法和终端 | |
WO2020191742A1 (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: 19922312 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2021558859 Country of ref document: JP Kind code of ref document: A Ref document number: 2019922312 Country of ref document: EP Effective date: 20210921 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112021019008 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 20217032655 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 112021019008 Country of ref document: BR Kind code of ref document: A2 Effective date: 20210923 |