WO2023246619A1 - Procédé de partage de canal, dispositif et support de stockage lisible - Google Patents

Procédé de partage de canal, dispositif et support de stockage lisible Download PDF

Info

Publication number
WO2023246619A1
WO2023246619A1 PCT/CN2023/100429 CN2023100429W WO2023246619A1 WO 2023246619 A1 WO2023246619 A1 WO 2023246619A1 CN 2023100429 W CN2023100429 W CN 2023100429W WO 2023246619 A1 WO2023246619 A1 WO 2023246619A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
cot
data
shared
information
Prior art date
Application number
PCT/CN2023/100429
Other languages
English (en)
Chinese (zh)
Inventor
黎建辉
郑倩
肖潇
纪子超
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2023246619A1 publication Critical patent/WO2023246619A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • 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/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • 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/563—Allocation or scheduling criteria for wireless resources based on priority criteria of the wireless resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]

Definitions

  • This application belongs to the field of communication technology, and specifically relates to a method, device and readable storage medium for sharing a channel.
  • COT sharing Channel Occupancy Time sharing
  • UE User Equipment
  • COT sharing can be classified into uplink COT sharing (UE shares Channel Occupancy Time (COT) with the base station) and downlink COT sharing (the base station shares COT with the UE).
  • COT Channel Occupancy Time
  • the embodiments of this application provide a method, device and readable storage medium for sharing a channel, which can solve the problem of how to implement COT sharing behavior in SL-U.
  • the first aspect provides a method of sharing channels, including:
  • the first terminal receives COT sharing information from one or more second terminals, the COT sharing information is used to indicate sharing COT;
  • the first terminal determines whether to use the shared COT indicated by the COT sharing information based on the received one or more COT sharing information.
  • the second aspect provides a method of sharing channels, including:
  • the first terminal receives COT shared information from one or more second terminals, and the COT shared information Information is used to indicate shared COT;
  • the first terminal determines whether to use the shared COT indicated by the COT sharing information based on the received one or more COT sharing information.
  • a terminal in a third aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor, the following implementations are implemented: The steps of the method described in one aspect.
  • a terminal including a processor and a communication interface, wherein the communication interface is used for a first terminal to receive COT sharing information from one or more second terminals, and the COT sharing information is used to indicate sharing. COT; the processor is configured for the first terminal to determine whether to use the shared COT indicated by the COT sharing information according to the received one or more COT sharing information.
  • a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented as described in the first aspect. The steps of the method described in the second aspect.
  • a chip in a sixth aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. steps, or steps to implement the method described in the second aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the method described in the first aspect.
  • An eighth aspect provides a system for sharing a channel, including: a first terminal and a second terminal.
  • the first terminal may be configured to perform the steps of the method for sharing a channel as described in the first aspect.
  • the first terminal receives COT sharing information used to indicate sharing COT from one or more second terminals, and the first terminal determines whether to use the COT sharing information based on the received one or more COT sharing information.
  • the indicated shared COT enables channel sharing between terminals in SL-U.
  • Figure 1 is a block diagram of a wireless communication system provided by an embodiment of the present application.
  • Figure 2 is a flow chart of a method for sharing a channel provided by an embodiment of the present application
  • FIG 3a is one of the application examples provided by the embodiment of this application.
  • Figure 3b is the second application example provided by the embodiment of this application.
  • Figure 3c is the third application example provided by the embodiment of this application.
  • Figure 3d is the fourth application example provided by the embodiment of this application.
  • Figure 3e is the fifth application example provided by the embodiment of this application.
  • Figure 3f is the sixth application example provided by the embodiment of this application.
  • Figure 3g is the seventh application example provided by the embodiment of this application.
  • Figure 4 is a structural diagram of a device for sharing a channel provided by an embodiment of the present application.
  • Figure 5 is a structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 6 is a structural diagram of a terminal provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA single-carrier frequency division multiple access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • MID mobile Internet Device
  • AR augmented reality
  • VR virtual reality
  • robots wearable devices
  • WUE Vehicle User Equipment
  • PUE Pedestrian User Equipment
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computer, PC), teller machine or self-service machine and other terminal-side devices.
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets) bracelets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the network side device 12 may include an access network device or a core network device, where the access network device may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a wireless access network unit.
  • Access network equipment may include a base station, a Wireless Local Area Network (WLAN) access point or a Wireless Fidelity (WiFi) node, etc.
  • the base station may be called a Node B or an Evolved Node B.
  • the base station is not limited to specific technical terms. It needs to be explained that , in the embodiment of this application The description only takes the base station in the NR system as an example, and does not limit the specific type of base station.
  • Radio Resource Control configures a consistent LBT failure recovery procedure (consistent LBT failure recovery procedure) for the Medium Access Control (MAC) entity. If LBT is performed before transmission and the channel is detected to be busy, the lower layer transmits an LBT failure indication to the MAC entity.
  • Consistent LBT failure is based on per Uplink Bandwidth Part (per UL BWP) and is generated by counting the LBT failure indications of all UL transmissions from the lower layer to the MAC entity.
  • the parameter used by the UE for LBT failure counting is LBT_COUNTER (per Serving Cell).
  • RRC configures two parameters lbt-FailureInstanceMaxCount and lbt-FailureDetectionTimer for Consistent LBT failure detection in lbt-FailureRecoveryConfig.
  • the LBT_COUNTER count is incremented by one.
  • LBT_COUNTER ⁇ lbt-FailureInstanceMaxCount the activation (active) UL BWP of the serving cell triggers consistent LBT failure.
  • PRACH Physical Random Access Channel
  • eNB/gNB can initiate Channel Occupancy based on base station (nodeB) own downlink (DL) channel access or UE UL channel access.
  • eNB/gNB/UE can determine a maximum COT through channel access priority class (CAPC).
  • CAC channel access priority class
  • COT sharing in the downlink direction When the eNB/gNB accesses the channel through the Type1 channel access method and obtains the CO, it can instruct the UE to share this CO with itself through DCI, which is called COT sharing.
  • COT sharing in the uplink direction When the UE accesses the channel through the Type1 channel access method and obtains the CO, it can transmit the uplink control information (autonomous uplink-uplink control information, AUL-UCI)/configured grant through automatic uplink transmission.
  • AUL-UCI autonomous uplink-uplink control information
  • CG-UCI -uplink control information instructs eNB/gNB to share this CO with itself, also called COT sharing.
  • CAPC CAPC value
  • RAT radio access technology
  • the network side can configure the CAPC value for the UE to send data carried by SRB2 and DRB.
  • SRB refers to Signaling Radio Bearer.
  • DRB refers to Data Radio Bearer.
  • SL UE When SL UE needs to perform SL transmission, it can access the network and report SidelinkUEInformationNR information to the base station.
  • the message carries up to 32 SL targets.
  • the Tx resource request for each SL target contains the sl-QoS-FlowIdentity and sl-QoS-Profile of up to 64 SL QoS flows.
  • the base station may then indicate to the UE which sl-QoS- FlowIdentity is mapped to this radio bearer.
  • SIB System Information Block
  • SCI Sidelink Control Information
  • 1.5>sl-HARQ-FeedbackEnabled is set to disabled, if the physical sidelink feedback channel (Physical Sidelink Feedback Channel, PSFCH) is not configured for the SL grant associated with the SCI.
  • PSFCH Physical Sidelink Feedback Channel
  • the resources obtained in the resource pool are not enough to adapt to the Radio Link Control (Radio Link Control, RLC) Service Data Unit (Service Data Unit, SDU) and the UE chooses not to split the RLC SDU;
  • Radio Link Control Radio Link Control, RLC
  • Service Data Unit Service Data Unit
  • Initiator UE A UE that accesses the channel in type 1 LBT in unlicensed spectrum.
  • COT-sharing UE In a SL-U COT sharing relationship, a UE that indicates that the opposite UE or other UEs can use its shared COT. (Here, COT-sharing UE may not be equivalent to initiator UE. There are two reasons: 1. initiator UE does not necessarily need to do COT sharing after seizing the channel; 2. It does not rule out that COT-sharing UE is not the initiator UE. Possibly, for example, UE1 is the initiator UE and shares COT with UE2. After UE2 uses this COT, it may also share COT with UE3. In other words, a COT-sharing UE can be an initiator UE or not an initiator UE)
  • COT-shared UE In a SL-U COT sharing relationship, COT-sharing UE is received COT sharing information (COT sharing information) of the UE indicates that the COT-shared UE can use a shared COT according to the COT sharing information in the information.
  • COT sharing information COT sharing information
  • COT-shared UE only refers to the UE that receives COT sharing information, and is not equivalent to "the UE that uses shared COT”; in other scenarios, COT-shared UE It refers to "UE using shared COT”. That is to say, after receiving the COT sharing information, the COT-shared UE may use the shared COT indicated by the information or not use the shared COT indicated by the information.
  • an embodiment of the present application provides a method for sharing a channel, including:
  • Step 201 The first terminal receives COT sharing information from one or more second terminals, and the COT sharing information is used to indicate sharing COT;
  • Step 202 The first terminal determines whether to use the shared COT indicated by the COT sharing information to send data based on the received one or more COT sharing information.
  • the above COT sharing information is used to indicate shared COT.
  • the first terminal receives COT sharing information used to indicate sharing COT from one or more second terminals, and the first terminal determines whether to use the COT sharing information based on the received one or more COT sharing information.
  • the indicated shared COT enables channel sharing between terminals in SL-U.
  • the above-mentioned first terminal is specifically a COT-shared UE
  • the corresponding second terminal is a COT-sharing UE
  • the COT sharing information sent by the second terminal to the first terminal is COT sharing information.
  • COT can be shared by one or more COT-sharing UEs to COT-shared UEs.
  • first terminal and the second terminal there may be a communication relationship between the first terminal and the second terminal.
  • a sidelink (SL) communication is used between the first terminal and the second terminal; or the first terminal and the second terminal
  • UE1 shares a COT with UE2.
  • UE2 is only in the same group as UE1, and then UE2 uses the shared COT to send data to UE3. In this scenario, UE2 and UE1 have no communication relationship.
  • the COT shared information includes one or more of the following:
  • the first information is used to indicate the propagation type for which the shared COT is used
  • the name of the first information may be castType, indicating the cast type that shared COT can be used for, such as unicast (unicast), multicast (group-cast), broadcast (broadcast), and any-cast (any-cast);
  • Second information used to indicate the identity of the second terminal
  • the name of the second information may be the first identifier, indicating the ID of the COT-sharing UE;
  • the name of the third information may be the second identifier, indicating the ID of the COT-shared UE (or the ID of the UE group containing the COT-shared UE);
  • the fourth information is used to indicate the identity of the third terminal, or the identity of the terminal group containing the third terminal.
  • the identity of the third terminal or the identity of the terminal group containing the third terminal is used to allow the third terminal.
  • One terminal will use the shared COT to send data to the third terminal;
  • the name of the fourth information may be a third identifier, indicating the ID of a specified UE (or the ID of a UE group containing the specified UE); the third identifier can be used to indicate that the COT-shared UE can use the COT sharing information.
  • the indicated shared COT is used to send data to the UE corresponding to the third identity;
  • COT shared information meets one or more of the following:
  • the COT sharing information does not include the fourth information, indicate that the first terminal is allowed to use the shared COT to send data to the second terminal, or indicate that the first terminal is allowed to use the shared COT to send data to the target terminal.
  • the target terminal includes a second terminal;
  • the COT shared information includes fourth information and the value of the fourth information is a default value
  • the fourth information is used to indicate that the first terminal is allowed to use the shared COT to send data to any terminal.
  • the COT-shared UE can use the shared COT indicated by the COT sharing information to send data to the UE corresponding to the third identifier;
  • the COT-shared UE can only use the shared COT indicated by the COT sharing information to send data to the COT-sharing UE that sends the COT sharing information, or to send control signaling or broadcast
  • the object of the data at least includes the COT-sharing UE;
  • the name of the fifth information may be flagSharingToOtherUE, indicating whether the COT-shared UE can further share the shared COT to other UEs. For example, 1 indicates that it is possible, and 0 indicates that it is not possible.
  • the name of the sixth information may be flagTransmissionToOtherUE, indicating whether the COT-shared UE can use the shared COT indicated by the COT sharing information to send data and control information to UEs other than the COT-sharing UE that sends the COT sharing information. command or multicast/broadcast message.
  • the seventh information is used to indicate whether the shared COT is used to send the physical direct link feedback channel PSFCH message
  • the name of the seventh information may be flagHarqFeedback, indicating whether the shared COT indicated by the COT sharing information can be used to send PSFCH;
  • the eighth information is used to indicate the time domain resource information of the shared COT and/or the frequency domain resource information of the shared COT;
  • the name of the ninth information may be sharedResource, indicating the resource shared by the COT-sharing UE to the COT-shared UE;
  • the name of the tenth information may be sharedResourcePool, indicating the resource pool shared by the COT-sharing UE to the COT-shared UE;
  • the name of the eleventh information may be sharedBWPConfig: indicating the BWP configuration shared by the COT-sharing UE to the COT-shared UE; including but not limited to one of the following:
  • the twelfth information is used to indicate the identification of the terminal that can use the shared COT;
  • the name of the twelfth information may be memberID/memberIDlist/memberIDrange.
  • the COT-sharing UE instructs a group of UEs to use shared COT, if the ID of the COT-shared UE that receives the COT sharing information is the same as the memberID, or in memberIDlist, or in the memberIDrange range, the COT-shared UE can use the shared COT indicated by the COT-sharing UE.
  • the thirteenth information is used to indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located in units of time slots;
  • the name of the thirteenth information may be offsetInSlot, indicating the time domain offset between the starting position of the shared COT and the position where the COT sharing information is located, in units of slots.
  • the fourteenth information is used to indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located in symbol units, or is used in conjunction with the twelfth information Indicates the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located;
  • the name of the fourteenth information can be offsetInSymbol.
  • This information field can be used alone to indicate the time domain offset between the starting position of the shared COT and the position of the COT sharing information, in symbol units; it can also be used together with offsetInSlot. Use the time domain offset described in the instructions. For example, the time domain offset between the starting position of the shared COT and the position where the COT sharing information is located is offsetInSymbol+14*offsetInSlot).
  • the fifteenth information is used to indicate the duration of the shared COT in units of slots;
  • the sixteenth information is used to indicate the duration of the shared COT in symbol units, or is used together with the fifteenth information to indicate the duration of the shared COT;
  • the name of the sixteenth information can be durationInSymbol: this information field can be used alone to indicate the duration of shared COT, in symbol units; it can also be used together with durationInSlot to indicate the duration of shared COT (for example, the symbol of shared COT The duration is durationInSymbol+14*durationInSlot).
  • the seventeenth information is used to indicate the channel access priority CAPC value.
  • the CAPC value is the same as
  • the corresponding priority may be negatively correlated, that is, the smaller the CAPC value, the greater the corresponding priority; or the CAPC value and the corresponding priority may be positively correlated, that is, the larger the CAPC value, the greater the corresponding priority.
  • the first terminal determines the shared COT indicated by the COT sharing information based on the received multiple COT sharing information, that is, when the COT-shared UE receives multiple COT sharing information;
  • the COT-shared UE When the COT-shared UE receives multiple COT sharing information, if the shared COTs indicated by the multiple COT sharing information do not overlap in time and frequency domain resources, the COT-shared UE can use the corresponding shared information based on the content of each COT sharing information. COT location try to use shared COT.
  • COT-shared UE needs to handle it accordingly according to different situations.
  • the following methods only take a scenario in which two UEs share a COT with the same UE as an example.
  • the above methods can also be similarly applied to a scenario in which more UEs share a COT with the same UE.
  • Method 1 The first terminal determines to use the shared COT of the target COT shared information to send data based on the target COT shared information that indicates the earliest starting time domain position of the shared COT among the multiple COT shared information;
  • COT-shared UE uses the shared COT whose starting position is earlier, as shown in Figure 3a:
  • UE1 When UE1 receives the shared COT indicated by UE2 and UE3, since the shared COT indicated by UE2 starts earlier, UE1 preferentially uses the shared COT indicated by UE2 and performs LBT before the shared COT indicated by UE2 to try to access the channel.
  • the gap between the starting positions of the shared COT indicated by UE2 and UE3 is greater than or equal to m us (for example, 25 us).
  • UE1 performs LBT before the shared COT indicated by UE2 and an LBT failure occurs, and the gap between the starting positions of the shared COT indicated by UE2 and UE3 is greater than or equal to m us (such as 25 us), then UE1 can Perform LBT before the shared COT indicated by UE2. After LBT failure occurs, perform LBT before the shared COT indicated by UE3 to try to access the channel.
  • m us such as 25 us
  • the beneficial effect of the first method is that it attempts to access a shared COT that is earlier in time. If successful, the UE can use the channel to send data earlier. In addition, even if the UE receives the earlier shared COT If the access fails, the UE may still have the opportunity to try to access the channel before the shared COT indicated by other UEs (for example, the gap between the starting positions of the two shared COTs mentioned above is greater than or equal to m us).
  • Method 2 The first terminal determines to use the shared COT indicated by the target COT sharing information to send data based on the target COT sharing information indicating the longest shared COT among the multiple COT sharing information;
  • COT-shared UE uses shared COT with longer duration shared COT, as shown in Figure 3b:
  • UE1 When UE1 receives the shared COT indicated by UE2 and UE3, although the shared COT indicated by UE2 starts earlier, the duration of the shared COT indicated by UE3 is longer, so UE1 performs LBT before the shared COT indicated by UE3 to try to connect. Enter the channel.
  • the beneficial effect of the second method is that by using the shared COT with longer duration, the UE can send more data if the access is successful.
  • UE1 performs LBT before the shared COT indicated by UE2, as shown in Figure 3c.
  • Method 3 The first terminal determines to use the shared COT indicated by the target COT sharing information to send the data based on the target COT sharing information with the highest priority corresponding to the CAPC value indicated in the multiple COT sharing information; or, the first terminal determines to send data based on the multiple COT sharing information.
  • the information indicates the target COT sharing information with the lowest priority corresponding to the CAPC value, and determines to use the shared COT sharing information of the target COT to send data;
  • COT-shared UE uses the shared COT with a larger or smaller CAPC value indicated by the COT sharing information.
  • COT-shared UE uses a shared COT with a larger CAPC value (that is, a lower priority corresponding to the CAPC value).
  • the beneficial effect of the third method is that the UE can send more mapped data associated with the priority by using a CAPC value indicating a lower priority (that is, a CAPC with a larger CAPC value).
  • Method 4 The first terminal determines to use the shared COT indicated by the target COT sharing information to send data according to the target COT sharing information indicating that the shared COT is used to send the PSFCH message in the multiple COT sharing information;
  • COT-shared UE uses the shared COT indicated by the COT-sharing UE that needs to send PSFCH to the COT-sharing UE.
  • UE1 when UE1 receives the shared COT indicated by UE2 and UE3, if UE1 needs to feed back PSFCH to UE2 but does not need to feedback PSFCH to UE3, UE1 will perform LBT before the shared COT indicated by UE2 to try to access the channel. UE1 does not use the shared COT indicated by UE3.
  • the location where the PSFCH is sent is within the shared COT interval indicated by the COT-sharing UE.
  • UE1 when UE1 receives the shared COT indicated by UE2 and UE3, if UE1 needs to feed back PSFCH to both UE2 and UE3, but the position of the PSFCH fed back by UE1 to UE2 is within the shared COT interval indicated by UE2, and UE1 If the position of the PSFCH fed back to UE2 is outside the shared COT interval indicated by UE3, UE1 will perform LBT to try to access the channel before the shared COT indicated by UE2. UE1 does not use the shared COT indicated by UE3.
  • the beneficial effect of the fourth method is that the UE can ensure the transmission of the PSFCH first.
  • Method 5 The first terminal determines to use the shared COT indicated by the target COT sharing information to send the data based on the priority of the CAPC value indicated in the multiple COT sharing information that can satisfy the target COT sharing information of the data in the cache of the first terminal;
  • COT-shared UE uses the shared COT that has data in the cache that satisfies the CAPC value indicated by the COT-sharing UE through COT sharing information.
  • the beneficial effect of method five is that the UE can exclude unavailable shared COTs based on the cached data and the content of COT sharing information.
  • Method 6 The first terminal determines to use the shared COT indicated by the target COT sharing information to send the data according to the target COT sharing information indicating that the propagation type of the shared COT used in multiple COT sharing information can satisfy the data in the cache of the first terminal;
  • COT-shared UE uses the shared COT that has data in the cache that satisfies the cast type indicated by the COT-sharing UE through COT sharing information.
  • UE1 when UE1 receives the shared COT indicated by UE2 and UE3, if UE2 indicates the cast type of the shared COT is unicast in the COT sharing information, and UE3 indicates the shared COT in the COT sharing information
  • the cast type of COT is groupcast. If UE1 has no multicast data to be sent in the cache, but only unicast data to be sent to UE2 or any UE, then UE1 should exclude the shared COT indicated by UE3 when resource selection/selection/reselection.
  • the beneficial effect of method six is that the UE can exclude unavailable shared COTs based on the cached data and the content of COT sharing information.
  • Method 7 The first terminal determines to use the shared COT indicated by the target COT sharing information to send data according to the target COT sharing information indicating the shared COT carrying the most data among the multiple COT sharing information;
  • the COT-shared UE (preferably) uses the shared COT that can utilize the COT-sharing UE to send more data through the shared COT indicated by the COT sharing information.
  • UE1 determines that the shared COTs indicated by UE2 and UE3 can be used, UE1 uses the shared COT of the two shared COTs that can carry more valid data.
  • Method 8 The first terminal determines to use only the shared COT to send data based on the target COT shared information of the target second terminal, where the target second terminal is included in the target object of the cached data of the first terminal, or, The target second terminal contains the control sent by the first terminal. in the target object of the signaling, or the target second terminal is included in the target object of the multicast message sent by the first terminal;
  • the COT-shared UE uses the shared COT indicated by COT sharing information.
  • Method 9 The first terminal determines to use the shared COT indicated by the target COT sharing information to send data based on the target COT sharing information of the target second terminal, where the data to be sent by the first terminal to the target second terminal is the cached data of the first terminal.
  • COT-shared UE uses the COT-shared UE to COT-sharing UE's CAPC priority of the data to be transmitted to the COT-sharing UE or the COT-sharing UE with a higher SL logical channel priority through the shared COT indicated by the COT sharing information.
  • UE1 when UE1 receives the shared COT indicated by UE2 and UE3, if UE1 has data to be transmitted to UE2 and UE3 in the cache, if the CAPC priority or SL logical channel priority of the data to be transmitted to UE2 is If the CAPC priority or SL logical channel priority of the data to be transmitted to UE3 is higher than the CAPC priority or SL logical channel priority of the data to be transmitted to UE3, UE1 (preferentially) uses the shared COT indicated by UE2.
  • UE1 gives up/discards the shared COT indicated by UE3.
  • Method 10 The first terminal determines to send data using the shared COT indicated by the target COT sharing information according to the target COT sharing information of one or more target second terminals, wherein the COT sharing information indicated by the one or more target second terminals
  • the shared COT is used to send target multicast services
  • COT-shared UE uses a shared COT with the same Destination ID of the multicast target that the shared COT indicated by the COT sharing information can be used by the UE, and uses this shared COT to send the multicast data of the multicast target.
  • UE1 when UE1 receives the shared COT indicated by multiple UEs (UE2 and UE3 as shown in Figure 3g), if the COT sharing information sent by multiple UEs can be used to send services of a certain multicast target , then UE1 uses at least one shared COT to send the service of the multicast target.
  • UE1 uses all shared COTs (that is, the shared COT formed by the union of all shared COT resources) to send the multicast target service.
  • UE1 uses the resources of the overlapping resources in all shared COTs (that is, the shared COT formed by the intersection of all shared COT resources) to send the multicast target service.
  • Method 11 The first terminal determines to send the data using the shared COT indicated by the target COT sharing information according to the target COT sharing information of the target second terminal, wherein the COT sharing information of the target second terminal indicates the identity of the second terminal or contains the identity of the second terminal.
  • the identifier of the terminal's terminal group is
  • COT-shared UE receives COT sharing information sent by multiple UEs
  • the COT sharing information sent by some UEs carries the second identifier described in Embodiment 1 and the second identifier is equal to the identifier of the COT-shared UE, and some UEs
  • the COT sharing information sent does not carry the second identification described in Embodiment 1, or carries the second identification described in Embodiment 1 but the second identification is not equal to the identification of COT-shared UE, then COT-shared UE ( Priority) Use the shared COT indicated by the COT sharing information that carries the second identifier described in Embodiment 1 and the second identifier is equal to the identifier of the COT-shared UE.
  • UE1 receives COT sharing information from UE2, UE3, and UE4, if UE2's COT sharing information carries the second identifier, and the second identifier is equal to the identifier of UE1; if UE3's COT sharing information carries the third identifier, Two identities, but the second identity is not equal to the identity of UE1; if the COT sharing information of UE4 does not carry the second identity, then:
  • UE1 (priority) uses the shared COT indicated by UE2.
  • the target recipient using shared COT to send data in the cache includes the COT-sharing UE.
  • COT sharing information terminal that is, when UE1 has data to be sent by multiple targets (such as UE2 and UE3), if UE2 shares COT with UE1 and UE3 does not share COT with UE1, then UE1 Do at least one of the following ways.
  • the following method can also be similarly applied to scenarios where multiple UEs share a COT, and multiple UEs do not share a COT:
  • the first terminal determines that the shared COT indicated by the COT sharing information includes one or more of the following:
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal to send data to the second terminal;
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal to send data to the second terminal and/or the third terminal. send data;
  • the data to be sent by the second terminal and the data to be sent by the third terminal both contain MAC CE, or both contain the data with the highest logical channel priority, or the data to be sent by the second terminal and the data by the third terminal
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal to send data to the second terminal;
  • the data to be sent by the second terminal and the data to be sent by the third terminal do not contain MAC CE, or the data with the highest logical channel priority is not included, or the data to be sent by the second terminal and the data by the third terminal are not included.
  • the first The terminal uses the first type LBT access channel and sends data to the third terminal; if the priority of the highest priority data in the data to be sent by the second terminal is higher than the priority of the highest priority data in the data to be sent by the third terminal High, the first terminal uses the shared COT indicated by the COT sharing information of the second terminal, and uses the second type LBT to access the channel, and sends data to the third terminal.
  • UE1 excludes targets that do not share COT with UE1, such as UE3, that is, UE1 chooses to use the COT shared by UE2 with UE1 to send data to UE2;
  • UE1 selects the target corresponding to the higher priority data among the data to be sent by UE2 and UE3 to send data.
  • UE1 uses the first type LBT (type 1 LBT) access channel to UE3.
  • Send data if the priority of the highest priority data in the data to be sent by UE2 is higher than the priority of the highest priority data in the data to be sent by UE3, then UE1 chooses to use shared COT and the second type of LBT (type 2 LBT ) access the channel to send data to UE2;
  • type1 and type2 LBT are defined in NR-U.
  • the types of LBT commonly used in NRU can be divided into Type1, Type2A, Type2B and Type2C.
  • Type1LBT is a channel listening mechanism based on back-off. When the transmission node detects that the channel is busy, it backs off and continues listening until it detects that the channel is empty.
  • Type2C means that the sending node does not perform LBT, that is, no LBT or immediate transmission.
  • Type2A and Type2B LBT are one-shot LBT, that is, the node performs an LBT before transmission. If the channel is empty, it will transmit, and if the channel is busy, it will not transmit. You can continue to use two types of LBT in SL-U, or you can define type3 LBT in SL-U and then change the definition of Type1 type2
  • the data to be sent by the second terminal and the data to be sent by the third terminal both contain MAC CE, or both contain the data with the highest logical channel priority, or the data to be sent by the second terminal and the data by the third terminal
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal to send data to the second terminal and/or the third terminal;
  • UE1 uses shared COT to send the target data corresponding to the higher priority data among the data to be sent by UE2 and UE3. For example, if the priority of the highest priority data in the data to be sent by UE2 is lower than the priority of the highest priority data in the data to be sent by UE3, then UE1 uses shared COT to send data to UE3.
  • the first terminal uses the COT shared information indication of the second terminal based on the Packet Delay Budget (PDB) requirements or remaining PDB requirements of the data to be sent by the second terminal and the data to be sent by the third terminal. Share COT and send data to the second terminal or third terminal;
  • PDB Packet Delay Budget
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal to send the data to the third terminal.
  • the second terminal sends data
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal to The terminal corresponding to the data with the highest PDB requirement level or the highest remaining PDB requirement level among the data to be sent by the second terminal and the data to be sent by the third terminal sends the data.
  • UE1 excludes targets that do not share COT with UE1, such as UE3, that is, UE1 chooses to use the COT shared by UE2 with UE1 to send data to UE2;
  • UE1 uses shared COT to send the pending data of the target corresponding to the PDB or the data with higher remaining PDB requirement level in the pending data of UE2 and UE3. For example, if the PDB or remaining PDB requirement level of the data to be sent by UE2 is lower than the PDB or remaining PDB requirement level of the data to be sent by UE3, then UE1 uses shared COT to send data to UE3.
  • the acquisition of the PDB requirement value or the remaining PDB requirement value of the data to be sent by UE2 and UE3 includes one or more of the following:
  • UE2 sends a PDB or remaining PDB demand value to UE1 as the PDB or remaining PDB demand value of UE2; or UE2 sends multiple PDB or remaining PDB demand values to UE1, and UE1 uses the largest or smallest among the multiple PDB demand values.
  • the PDB or remaining PDB value is used as the PDB or remaining PDB requirement value of UE2;
  • UE1 sends a PDB or remaining PDB requirement value request to UE2.
  • the request can be sent through SCI or MAC CE.
  • UE2 then sends PDB or remaining PDB requirement value information to UE1, and the request can be sent through SCI or MAC CE.
  • the PDB or remaining PDB requirement value can be directly included in the MAC CE, or can be derived by indirect association, derivation, mapping, etc. from the information domain of the MAC CE.
  • UE1 needs to send control plane information or PSFCH feedback to UE3, it uses the COT shared by UE2 to send control plane information or PSFCH feedback to UE3.
  • the first terminal determines whether the shared COT indicated by the COT sharing information includes one or more of the following:
  • the first terminal stops using the shared COT indicated by the COT sharing information of the second terminal;
  • UE1 does not use the shared COT indicated by UE2.
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal to send data to the third terminal;
  • UE1 uses the shared COT indicated by UE2 to send data to UE3.
  • COT sharing information carries flagTransmissionToOtherUE
  • UE1 uses the shared COT indicated by UE2 to send data to UE3.
  • the first terminal uses the shared COT indicated by the COT sharing information of the second terminal, Send data to a third terminal.
  • UE1 uses the shared COT indicated by UE2 to send data to UE3.
  • UE1 indicates that the resource associated with UE3's Sidelink grant sends data or feedback messages to UE3 at the time domain location [T0, T1]. If [T0, T1] is within the range of the shared COT indicated by UE2, UE1 can Send data to UE3 using the shared COT indicated by UE2.
  • the execution subject may be a device that shares the channel.
  • the method of performing the shared channel method by a shared channel device is used as an example to illustrate the shared channel device provided by the embodiment of the present application.
  • an embodiment of the present application provides a device 400 for sharing a channel.
  • the device can be applied to the first terminal as described in the above method, including:
  • the receiving module 401 is configured to receive COT sharing information from one or more second terminals, where the COT sharing information is used to indicate shared COT;
  • Determining module 402 is configured to determine whether to use the shared COT indicated by the COT sharing information according to the received one or more COT sharing information.
  • the COT shared information includes one or more of the following:
  • the third information is used to indicate the identity of the device that shares the channel, or is used to indicate the identity of the terminal group that includes the device that shares the channel;
  • the fourth information is used to indicate the identification of the third terminal, or the identification of the terminal group including the third terminal.
  • the identification of the third terminal or the identification of the terminal group including the third terminal is used. Allowing the device of the shared channel to use the shared COT to send data to the third terminal;
  • Sixth information used to indicate whether the device of the shared channel is allowed to use the shared COT to send data, control signaling, multicast messages and/or broadcast messages to other terminals except the second terminal;
  • the seventh information is used to indicate whether the shared COT is used to send the physical direct link feedback channel PSFCH message
  • the eighth information is used to indicate the time domain resource information of the shared COT and/or the frequency domain resource information of the shared COT;
  • Ninth information used to indicate resources shared by the second terminal to the device sharing the channel
  • Tenth information used to indicate the resource pool shared by the second terminal to the device of the shared channel
  • Twelfth information used to indicate the identity of the terminal that can use the shared COT
  • the thirteenth information is used to indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located in units of time slots;
  • the fourteenth information is used to indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located in symbol units, or used to communicate with the tenth information.
  • the two pieces of information jointly indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located;
  • the fifteenth information is used to indicate the duration of the shared COT in slot units
  • the sixteenth information is used to indicate the duration of the shared COT in symbol units, or is used together with the fifteenth information to indicate the duration of the shared COT;
  • the seventeenth information is used to indicate the channel access priority CAPC value.
  • the COT shared information satisfies one or more of the following:
  • the COT sharing information does not include the fourth information, instruct the device that allows the shared channel to use the shared COT to send data to the second terminal, or instruct the device that allows the shared channel to use the shared COT to send data to the second terminal, or indicate that the shared channel is allowed.
  • the device uses the shared COT to send control signaling or broadcast data to a target terminal, where the target terminal includes the second terminal;
  • the fourth information is used to instruct the device that allows the shared channel to use the shared COT. Used to send data to any terminal.
  • the determining module is used for one or more of the following:
  • the target COT shared information indicating the earliest starting time domain position of the shared COT among the plurality of COT shared information, determine to use the shared COT indicated by the target COT shared information to send data;
  • the target COT shared information with the highest priority corresponding to the indicated CAPC value in the multiple COT shared information determine to use the shared COT indicated by the target COT shared information to send data; or, according to the indicated in the multiple COT shared information
  • the target COT shared information with the lowest priority corresponding to the CAPC value determines to use the shared COT indicated by the target COT shared information to send data;
  • Target COT shared information and determine to use the shared COT indicated by the target COT shared information to send data;
  • the target COT sharing information indicating that the priority of the CAPC value in the plurality of COT sharing information can satisfy the data in the device cache of the shared channel, determine to use the shared COT indicated by the target COT sharing information to send the data;
  • the target COT sharing information in the plurality of COT sharing information indicating that the propagation type used by the shared COT can satisfy the data in the device cache of the shared channel determine to use the shared COT indicated by the target COT sharing information to send the data;
  • the target COT sharing information indicating the shared COT carrying the most data among the multiple COT sharing information, determine to use the shared COT indicated by the target COT sharing information to send the data;
  • the target second terminal is included in the target object of the cached data of the device sharing the channel, or , the target second terminal is included in the target object for which the device sharing the channel sends control signaling, or the target second terminal is included in the target object for which the device sharing the channel sends a multicast message;
  • the target COT sharing information of the target second terminal it is determined to use the shared COT indicated by the target COT sharing information to send data, wherein the data to be sent by the device of the shared channel to the target second terminal is of the shared channel
  • the buffered data of the device sharing the channel includes the data to be sent by the third terminal and the data to be sent by the second terminal, wherein the third terminal It is a terminal that has not sent the COT shared information to the device sharing the channel, and the determination module is used for one or more of the following:
  • the shared COT indicated by the COT sharing information of the second terminal is used to send the data to the second terminal and/or the third terminal.
  • the third terminal sends data
  • the shared COT indicated by the COT sharing information of the second terminal is used to send the data to the second terminal or The third terminal sends data;
  • the buffered data of the device sharing the channel includes the data to be sent by the third terminal and does not include the data to be sent by the second terminal
  • the third terminal is a terminal that has not sent the COT shared information to the device sharing the channel
  • the determining module is used for one or more of the following:
  • the module is determined to be used for one or more of the following:
  • the data to be sent by the second terminal and the data to be sent by the third terminal both contain MAC CE, or both contain data with the highest logical channel priority, or the data to be sent by the second terminal and the data to be sent are both When the highest priority of the data to be sent by the third terminal is the same, use the shared COT indicated by the COT sharing information of the second terminal to send data to the second terminal;
  • the data to be sent by the second terminal and the data to be sent by the third terminal do not contain MAC CE, or the data with the highest logical channel priority is not included, or the data to be sent by the second terminal and the data to be sent are not included in the data.
  • the highest priority of the data to be sent by the third terminal is not the same, if the second terminal The priority of the highest priority data in the data to be sent is lower than the priority of the highest priority data in the data to be sent by the third terminal, using the first type LBT access channel, and sending data to the third terminal ; If the priority of the highest priority data in the data to be sent by the second terminal is higher than the priority of the highest priority data in the data to be sent by the third terminal, use the COT sharing information indication of the second terminal shared COT, and uses the second type LBT access channel, and sends data to the third terminal.
  • the module is determined to be used for one or more of the following:
  • the data to be sent by the second terminal and the data to be sent by the third terminal both contain MAC CE, or both contain data with the highest logical channel priority, or the data to be sent by the second terminal and the data to be sent are both
  • the highest priority of the data to be sent by the third terminal is the same, use the shared COT indicated by the COT sharing information of the second terminal to send data to the second terminal and/or the third terminal;
  • the data to be sent by the second terminal and the data to be sent by the third terminal do not contain MAC CE, or the data with the highest logical channel priority is not included, or the data to be sent by the second terminal and the data to be sent are not included in the data.
  • the shared COT indicated by the COT sharing information of the second terminal is used to send data to the second terminal and the data to be sent by the third terminal.
  • the terminal corresponding to the highest priority data in the sent data sends data.
  • the module is determined to be used for one or more of the following:
  • the shared COT indicated by the COT sharing information of the second terminal is used to provide the data to the second terminal.
  • the second terminal sends data
  • the shared COT indicated by the COT sharing information of the second terminal is used to The terminal corresponding to the data with the highest PDB requirement level or the highest remaining PDB requirement level among the data to be sent by the second terminal and the data to be sent by the third terminal sends data.
  • the device for sharing the channel in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network-affiliated storage devices, etc.
  • Storage Network Attached Storage, NAS), etc. are not specifically limited in the embodiments of this application.
  • the device for sharing a channel provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 2 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • this embodiment of the present application also provides a communication device 500, which includes a processor 501 and a memory 502.
  • the memory 502 stores programs or instructions that can be run on the processor 501, for example.
  • the communication device 500 is a terminal, when the program or instruction is executed by the processor 501, each step of the above shared channel method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 500 is a network-side device, when the program or instruction is executed by the processor 501, each step of the above shared channel method embodiment is implemented, and the same technical effect can be achieved. To avoid duplication, the details are not repeated here.
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface.
  • the communication interface is used for a first terminal to receive COT sharing information from one or more second terminals, and the COT sharing information is used to indicate sharing COT;
  • the processor is configured for the first terminal to determine the target shared COT to be used based on the received one or more COT sharing information.
  • FIG. 6 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 600 includes but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, a processor 610, etc. At least some parts.
  • the terminal 600 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 610 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 6 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042.
  • the graphics processor 6041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 606 may include a display panel 6061, which may The display panel 6061 is configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 607 includes a touch panel 6071 and at least one of other input devices 6072 . Touch panel 6071, also called touch screen.
  • the touch panel 6071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 6072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 601 after receiving downlink data from the network side device, can transmit it to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network side device.
  • the radio frequency unit 601 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
  • Memory 609 may be used to store software programs or instructions as well as various data.
  • the memory 609 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 609 may include volatile memory or non-volatile memory, or memory 609 may include both volatile and non-volatile memory.
  • 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), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), 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, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • 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 Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus
  • the processor 610 may include one or more processing units; optionally, the processor 610 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 610.
  • the radio frequency unit 601 is used to receive COT sharing information from one or more second terminals, where the COT sharing information is used to indicate sharing COT;
  • the processor 610 is configured to determine the target shared COT to be used based on the received one or more COT sharing information.
  • the COT shared information includes one or more of the following:
  • the fourth information is used to indicate the identification of the third terminal, or the identification of the terminal group including the third terminal.
  • the identification of the third terminal or the identification of the terminal group including the third terminal is used. Allowing the device of the shared channel to use the shared COT to send data to the third terminal;
  • Sixth information used to indicate whether the device of the shared channel is allowed to use the shared COT to send data, control signaling, multicast messages and/or broadcast messages to other terminals except the second terminal;
  • Ninth information used to indicate resources shared by the second terminal to the device sharing the channel
  • Tenth information used to indicate the resource pool shared by the second terminal to the device of the shared channel
  • Twelfth information used to indicate the identity of the terminal that can use the shared COT
  • the thirteenth information is used to indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located in units of time slots;
  • the fourteenth information is used to indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located in symbol units, or used to communicate with the tenth information.
  • the two pieces of information jointly indicate the time domain compensation between the starting time domain position of the shared COT and the time domain position where the COT shared information is located;
  • the sixteenth information is used to indicate the duration of the shared COT in symbol units, or is used together with the fifteenth information to indicate the duration of the shared COT;
  • the COT shared information satisfies one or more of the following:
  • the fourth information is used to instruct the device that allows the shared channel to use the shared COT. Used to send data to any terminal.
  • the processor 610 is used for one or more of the following:
  • the target COT sharing information in the plurality of COT sharing information indicating that the propagation type used by the shared COT can satisfy the data in the device cache of the shared channel determine to use the shared COT indicated by the target COT sharing information to send the data;
  • the target COT sharing information indicating the shared COT carrying the most data among the multiple COT sharing information, determine to use the shared COT indicated by the target COT sharing information to send the data;
  • the target COT sharing information of the target second terminal it is determined to use the shared COT indicated by the target COT sharing information to send data, wherein the data to be sent by the device of the shared channel to the target second terminal is of the shared channel
  • the buffered data of the device sharing the channel includes the data to be sent by the third terminal and does not include the data to be sent by the second terminal, wherein the third terminal
  • the terminal is a terminal that has not sent the COT shared information to the device that shares the channel.
  • the processor 610 is used for one or more of the following:
  • the processor 610 is used for one or more of the following:
  • the data to be sent by the second terminal and the data to be sent by the third terminal both contain MAC CE, or both contain data with the highest logical channel priority, or the data to be sent by the second terminal and the data to be sent are both When the highest priority of the data to be sent by the third terminal is the same, use the shared COT indicated by the COT sharing information of the second terminal to send data to the second terminal;
  • the processor 610 is used for one or more of the following:
  • the shared COT indicated by the COT sharing information of the second terminal is used to The terminal corresponding to the data with the highest PDB requirement level or the highest remaining PDB requirement level among the data to be sent by the second terminal and the data to be sent by the third terminal sends data.
  • Embodiments of the present application also provide a readable storage medium.
  • Programs or instructions are stored on the readable storage medium.
  • the program or instructions are executed by a processor, each process of the above shared method embodiments is implemented and the same can be achieved. The technical effects will not be repeated here to avoid repetition.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the above shared method embodiments. Each process can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above shared method embodiments.
  • Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.

Landscapes

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

Abstract

La présente demande relève du domaine technique des communications et divulgue un procédé de partage de canal, un dispositif et un support de stockage lisible. Le procédé comprend les étapes suivantes : un premier terminal reçoit des informations de partage de temps d'occupation de canal (COT) d'un ou de plusieurs seconds terminaux, les informations de partage de COT servant à indiquer un COT partagé ; et le premier terminal détermine, selon l'information ou les informations de partage de COT reçues, s'il faut utiliser le COT partagé indiqué par les informations de partage de COT.
PCT/CN2023/100429 2022-06-22 2023-06-15 Procédé de partage de canal, dispositif et support de stockage lisible WO2023246619A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210712798.7 2022-06-22
CN202210712798.7A CN117336872A (zh) 2022-06-22 2022-06-22 共享信道的方法、设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2023246619A1 true WO2023246619A1 (fr) 2023-12-28

Family

ID=89277887

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/100429 WO2023246619A1 (fr) 2022-06-22 2023-06-15 Procédé de partage de canal, dispositif et support de stockage lisible

Country Status (2)

Country Link
CN (1) CN117336872A (fr)
WO (1) WO2023246619A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018127237A1 (fr) * 2017-01-06 2018-07-12 电信科学技术研究院有限公司 Procédé et appareil de transmission d'informations
CN111565475A (zh) * 2019-02-14 2020-08-21 索尼公司 用户设备、网络侧设备、无线通信方法和存储介质
US20210014892A1 (en) * 2019-07-11 2021-01-14 Qualcomm Incorporated Methods, apparatuses and systems for user equipment (ue)-to-ue sharing of channel occupancy time
CN114642057A (zh) * 2020-01-09 2022-06-17 Oppo广东移动通信有限公司 信息确定方法、信息指示方法、终端设备和网络设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018127237A1 (fr) * 2017-01-06 2018-07-12 电信科学技术研究院有限公司 Procédé et appareil de transmission d'informations
CN111565475A (zh) * 2019-02-14 2020-08-21 索尼公司 用户设备、网络侧设备、无线通信方法和存储介质
US20210014892A1 (en) * 2019-07-11 2021-01-14 Qualcomm Incorporated Methods, apparatuses and systems for user equipment (ue)-to-ue sharing of channel occupancy time
CN114642057A (zh) * 2020-01-09 2022-06-17 Oppo广东移动通信有限公司 信息确定方法、信息指示方法、终端设备和网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
APPLE: "Considerations on NR V2X mode 2 resource allocation mechanism", 3GPP DRAFT; R1-1909051 CONSIDERATIONS ON NR V2X MODE 2 RESOURCE ALLOCATION MECHANISM, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Prague, CZ; 20190826 - 20190830, 17 August 2019 (2019-08-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051765655 *

Also Published As

Publication number Publication date
CN117336872A (zh) 2024-01-02

Similar Documents

Publication Publication Date Title
US20220141824A1 (en) Carrier aggregation parameter configuration method, device, and system
US20230262517A1 (en) Pdcp duplication configuring, activating, or deactivating method and terminal
US20230144480A1 (en) Method for configuring sidelink relay architecture and terminal
WO2023046196A1 (fr) Procédé de rapport d'informations auxiliaires, procédé de configuration de service, terminal et dispositif de réseau
US20240040595A1 (en) Method and Apparatus for Determining Sidelink Feedback Resource, Terminal, and Storage Medium
CN113923712A (zh) 数据处理的方法及装置
JP2024516949A (ja) サイドリンクフィードバックリソースの決定方法、端末及びネットワーク側機器
WO2022033560A1 (fr) Procédé de notification de capacité, dispositif terminal et dispositif de réseau
WO2023246619A1 (fr) Procédé de partage de canal, dispositif et support de stockage lisible
WO2022012592A1 (fr) Procédé et appareil de transmission d'informations en retour, terminal et dispositif côté réseau
WO2022017409A1 (fr) Procédé et appareil de transmission de liaison montante, et dispositif associé
WO2023246615A1 (fr) Procédé et dispositif de partage de canal, et support de stockage lisible
JP2024510589A (ja) 上りリンク伝送方法、装置及び端末
WO2023066129A1 (fr) Procédé de rapport d'informations, dispositif, et support de stockage lisible
WO2023236856A1 (fr) Procédé d'envoi de données et terminal
WO2023241477A1 (fr) Procédé de partage de ressources, terminal et dispositif
WO2023093636A1 (fr) Procédé et appareil de rapport d'informations, procédé et appareil de configuration d'informations, terminal, et dispositif côté réseau
WO2024093921A1 (fr) Procédé et appareil de traitement pour défaillance d'écoute avant de parler (lbt) cohérente, et équipement utilisateur et support de stockage
WO2022017342A1 (fr) Procédé et appareil de transmission de liaison montante, et dispositf
WO2022242675A1 (fr) Procédé et appareil de transmission d'informations, procédé et appareil d'acquistion d'informations, et dispositif de communication
WO2023011480A1 (fr) Procédé et appareil de transmission d'informations de commande de liaison montante et dispositif associé
WO2023011286A1 (fr) Procédé de rétroaction, dispositif associé et support d'enregistrement lisible
WO2023001172A1 (fr) Procédé et appareil pour déterminer un débit binaire recommandé et dispositif associé
WO2022148368A1 (fr) Procédé et appareil de transmission d'informations, terminal et dispositif de réseau
WO2024120351A1 (fr) Procédé et appareil de transmission de message, ue et support de stockage

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: 23826268

Country of ref document: EP

Kind code of ref document: A1