CN118251958A - Wireless communication method, terminal equipment and network equipment - Google Patents

Wireless communication method, terminal equipment and network equipment Download PDF

Info

Publication number
CN118251958A
CN118251958A CN202280075165.8A CN202280075165A CN118251958A CN 118251958 A CN118251958 A CN 118251958A CN 202280075165 A CN202280075165 A CN 202280075165A CN 118251958 A CN118251958 A CN 118251958A
Authority
CN
China
Prior art keywords
sps configuration
information field
sps
dci
index
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202280075165.8A
Other languages
Chinese (zh)
Inventor
马腾
张世昌
赵振山
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN118251958A publication Critical patent/CN118251958A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling

Landscapes

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

Abstract

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, wherein a communication system can simultaneously support SPS configuration associated with unicast service and SPS configuration associated with MBS service to work simultaneously, and the SPS configuration associated with unicast service and the SPS configuration associated with MBS service have no limit or influence on each other, and furthermore, the SPS configuration associated with unicast service and the SPS configuration associated with MBS service can cooperatively work, so that the compatibility of the communication system is improved. The method of wireless communication includes: the terminal equipment receives first DCI; the first DCI is used for activating or deactivating M SPS configurations, wherein M is a positive integer; wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with MBS service.

Description

Wireless communication method, terminal equipment and network equipment Technical Field
The embodiment of the application relates to the field of communication, and more particularly relates to a wireless communication method, terminal equipment and network equipment.
Background
In a New Radio (NR) system, it is a problem to be solved how to activate or deactivate Semi-persistent scheduling (Semi-PERSISTENT SCHEDULING, SPS) configuration associated with different services, which can support unicast services and multicast broadcast services (Multicast Broadcast Service, MBS) services.
Disclosure of Invention
The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, wherein a communication system can simultaneously support SPS configuration associated with unicast service and SPS configuration associated with MBS service to work simultaneously, and the SPS configuration associated with unicast service and the SPS configuration associated with MBS service have no limit or influence on each other, and furthermore, the SPS configuration associated with unicast service and the SPS configuration associated with MBS service can cooperatively work, so that the compatibility of the communication system is improved.
In a first aspect, a method of wireless communication is provided, the method comprising:
the terminal equipment receives first DCI;
the first DCI is used for activating or deactivating M SPS configurations, wherein M is a positive integer;
Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with MBS service.
In a second aspect, there is provided a method of wireless communication, the method comprising:
The network equipment sends first DCI;
the first DCI is used for activating or deactivating M SPS configurations, wherein M is a positive integer;
Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with MBS service.
In a third aspect, a terminal device is provided for performing the method in the first aspect.
Specifically, the terminal device comprises functional modules for performing the method in the first aspect described above.
In a fourth aspect, a network device is provided for performing the method in the second aspect.
In particular, the network device comprises functional modules for performing the method in the second aspect described above.
In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the first aspect.
In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect described above.
In a seventh aspect, there is provided an apparatus for implementing the method of any one of the first to second aspects.
Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any of the first to second aspects as described above.
In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to execute the method of any one of the first to second aspects.
In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects above.
In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any of the first to second aspects described above.
Through the above technical solution, the network device may activate or deactivate M SPS configurations through the first DCI, where the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with MBS service. Therefore, the communication system can simultaneously support the SPS configuration associated with the unicast service and the SPS configuration associated with the MBS service to work simultaneously without limitation and influence among the SPS configuration associated with the unicast service and the SPS configuration associated with the MBS service, and furthermore, the SPS configuration associated with the unicast service and the SPS configuration associated with the MBS service can work cooperatively, so that the compatibility of the communication system is improved.
Drawings
Fig. 1 is a schematic diagram of a communication system architecture to which embodiments of the present application apply.
Fig. 2 is a schematic diagram of a BWP according to the present application.
Fig. 3 is a schematic diagram of an SC-PTM channel and its mapping provided by the present application.
Fig. 4 is a schematic diagram of an MBS downlink scheduling method provided by the present application.
Fig. 5 is a schematic interaction flow chart of a method of wireless communication provided in accordance with an embodiment of the present application.
Fig. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application.
Fig. 7 is a schematic block diagram of a network device according to an embodiment of the present application.
Fig. 8 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
Fig. 9 is a schematic block diagram of an apparatus provided in accordance with an embodiment of the present application.
Fig. 10 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
Detailed Description
The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art to which the application pertains without inventive faculty, are intended to fall within the scope of the application.
The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general Packet Radio Service (GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-TERRESTRIAL NETWORKS, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), internet of things (internet of things, ioT), wireless fidelity (WIRELESS FIDELITY, WIFI), fifth Generation communication (5 th-Generation, 5G) system or other communication system, etc.
Generally, the number of connections supported by the conventional Communication system is limited and easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, device-to-Device (D2D) Communication, machine-to-machine (Machine to Machine, M2M) Communication, machine type Communication (MACHINE TYPE Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) Communication, or internet of vehicles (Vehicle to everything, V2X) Communication, etc., and the embodiments of the present application can also be applied to these Communication systems.
In some embodiments, the communication system in the embodiments of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, an independent (Standalone, SA) networking scenario, or a Non-independent (Non-Standalone, NSA) networking scenario.
In some embodiments, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; or the communication system in the embodiment of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.
In some embodiments, the communication system in the embodiments of the present application may be applied to the FR1 frequency band (corresponding to the frequency band range 410MHz to 7.125 GHz), the FR2 frequency band (corresponding to the frequency band range 24.25GHz to 52.6 GHz), and the new frequency band, such as the high frequency band corresponding to the frequency band range 52.6GHz to 71GHz or the frequency band range 71GHz to 114.25 GHz.
Embodiments of the present application are described in connection with a network device and a terminal device, where the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User Equipment, or the like.
The terminal device may be a STATION (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) STATION, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).
In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned (SELF DRIVING), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (SMART GRID), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (SMART CITY) or smart home (smart home), an on-vehicle communication device, a wireless communication Chip/application specific integrated circuit (application SPECIFIC INTEGRATED circuit)/a System on Chip (ASIC), or the like.
By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.
In the embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in a WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device or a base station (gNB) in an NR network, a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
By way of example, and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. In some embodiments, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth Orbit (medium earth Orbit, MEO) satellite, a geosynchronous Orbit (geostationary earth Orbit, GEO) satellite, a high elliptical Orbit (HIGH ELLIPTICAL Orbit, HEO) satellite, or the like. In some embodiments, the network device may also be a base station located on land, in water, etc.
In the embodiment of the present application, a network device may provide services for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (SMALL CELL), where the small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.
An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.
Fig. 1 illustrates one network device and two terminal devices, and in some embodiments, the communication system 100 may include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited by the embodiments of the present application.
In some embodiments, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.
It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.
It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
It is to be understood that the present disclosure relates to a first communication device, which may be a terminal device, such as a cell phone, a machine facility, a customer premises equipment (Customer Premise Equipment, CPE), an industrial device, a vehicle, etc., and a second communication device; the second communication device may be a peer communication device of the first communication device, such as a network device, a cell phone, an industrial device, a vehicle, etc. The description is made herein taking a specific example in which the first communication device is a terminal device and the second communication device is a network device.
The terminology used in the description of the embodiments of the application herein is for the purpose of describing particular embodiments of the application only and is not intended to be limiting of the application. The terms "first," "second," "third," and "fourth" and the like in the description and in the claims and drawings are used for distinguishing between different objects and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion.
It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.
In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, etc.
In the embodiment of the present application, the "pre-defining" or "pre-configuring" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the present application is not limited to the specific implementation manner thereof. Such as predefined may refer to what is defined in the protocol.
In the embodiment of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited in the present application.
In order to facilitate understanding of the technical solution of the embodiments of the present application, the technical solution of the present application is described in detail below through specific embodiments. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.
Currently, with the pursuit of speed, delay, high-speed mobility, energy efficiency and the diversity and complexity of future life services, 5G communication networks are introduced. The main application scenario of 5G is: enhanced mobile Ultra-wideband (Enhance Mobile Broadband, eMBB), low latency high reliability communications (Ultra-Reliable and Low Latency Communication, URLLC), large scale machine type communications (MASSIVE MACHINE TYPE of communications, mMTC).
EMBB still aims at obtaining multimedia content, services and data by users, and the demand of which is growing very rapidly. On the other hand, eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., where the capability and demand are also quite different, so detailed analysis must be performed in conjunction with a specific deployment scenario. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical features of mMTC include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.
The NR may also be deployed independently, and a new radio resource control (Radio Resource Control, RRC) state, i.e., rrc_inactive state, is introduced in the 5G network environment for the purposes of reducing air interface signaling and fast recovery of radio connections, and fast recovery of data traffic. The rrc_inactive state is different from the RRC IDLE (rrc_idle) state and the RRC ACTIVE (rrc_active) state.
Rrc_idle: mobility is terminal-based cell selection reselection, paging is initiated by a Core Network (CN), and paging areas are configured by the CN. The base station side does not have Access Stratum (AS) context of the terminal. There is no RRC connection.
Rrc_connected: there is an RRC connection and the base station and the terminal have an AS context for the terminal. The network side knows that the location of the terminal is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the terminal and the base station.
Rrc_inactive: mobility is terminal-based cell selection reselection, there is a connection between the core network and the NR (CN-NR), the AS context of the terminal is present on a certain base station, paging is triggered by the radio access network (Radio Access Network, RAN), the RAN-based paging area is managed by the RAN, and the network side knows that the location of the terminal is based on the RAN paging area level.
In 5G, the maximum channel bandwidth may be 400MHz (e.g., wideband carrier), which is large compared to the maximum 20M bandwidth of LTE. If the terminal device remains operating on the broadband carrier, the power consumption of the terminal device is significant. Thus, the Radio Frequency (RF) bandwidth of the terminal device may be adjusted according to the actual throughput of the terminal device. And introduces a bandwidth part (Band WIDTH PART, BWP) to optimize the power consumption of the terminal device. For example, the rate of the terminal device is low, a smaller bandwidth may be configured for the terminal device (as shown in (a) of fig. 2), and if the rate requirement of the terminal device is high, a larger bandwidth may be configured for the terminal device (as shown in (b) of fig. 2). If the terminal device supports a high rate or operates in a carrier aggregation (Carrier Aggregation, CA) mode, the terminal device may be configured with a plurality of BWPs (as shown in (c) of fig. 2). Another purpose of BWP is to trigger coexistence of multiple basic parameter sets (numerology) in one cell.
In some embodiments, terminals in the RRC idle state or RRC deactivated state reside on an initial (initial) BWP, which is visible to terminals in the RRC idle state or RRC deactivated state, within which a master Information block (Master Information Block, MIB), remaining system Information (REMAINING SYSTEM Information, RMSI), other system Information (Other System Information, OSI), padding, and the like may be acquired.
For better understanding of the embodiments of the present application, MBMS and SC-PTM systems in LTE related to the present application are described.
Multimedia broadcast multicast service (Multimedia Broadcast Multicast Service, MBMS) is a technology for transmitting data from one data source to a plurality of user equipments through a shared network resource, and can effectively utilize the network resource while providing multimedia services, realizing broadcasting and multicasting of multimedia services at a higher rate (256 kbps).
Due to the low MBMS spectrum efficiency, it is not sufficient to effectively carry and support the operation of the mobile tv type service. Enhanced MBMS (E-MBMS) introduces the concept of a single frequency network (Single Frequency Network, SFN), i.e. transmitting data simultaneously in all cells using a unified frequency, but ensuring synchronization between cells. The method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. And implements broadcast and multicast of services based on an internet protocol (Internet Protocol, IP) multicast protocol.
In LTE/LTE-a, MBMS has only a broadcast bearer mode and no multicast bearer mode.
The reception of the MBMS service is applicable to UEs in an RRC connected state or an RRC idle state.
The single cell point-to-multipoint transmission (SINGLE CELL Point To Multipoint, SC-PTM) is based on the MBMS network architecture, and the Multi-cell/multicast coordination unit (Multi-cell/multicast Coordination Entity, MCE) decides whether to employ the SC-PTM transmission scheme or the multimedia broadcast multicast service single frequency network (Multimedia Broadcast multicast SERVICE SINGLE Frequency Network, MBSFN) transmission scheme.
Specifically, as shown in fig. 3, SC-PTM introduces a single cell multicast control channel (SINGLE CELL Multicast Control Channel, SC-MCCH) and a single cell multicast transport channel (SINGLE CELL Multicast Transport Channel, SC-MTCH), logical channel identification (Logical CHANNEL IDENTITY, LCID) of SC-mcch=11001, lcid=11001 of SC-MTCH. The SC-MCCH and SC-MCCH may be mapped to a Downlink shared channel (Downlink SHARED CHANNEL, DL-SCH) transport channel, a physical Downlink shared channel (Physical Downlink SHARED CHANNEL, PDSCH) physical channel. The SC-MCCH and SC-MTCH do not support hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) operations.
The SC-PTM introduces a new system information block (System Information Block, SIB) type, SIB20 to transmit configuration information of the SC-MCCH, and one cell has only one SC-MCCH. The configuration information includes: modification period, repetition period, and radio frame and subframe configuration information of the SC-MCCH.
Radio frame scheduled by SC-MCCH: system Frame Number (SFN) mod MCCH repetition period (MCCH-RepetitionPeriod) =mcch Offset (MCCH-Offset).
The subframes of the SC-MCCH schedule are indicated by an SC-MCCH Subframe (SC-MCCH-Subframe) field.
The SC-MCCH transmits only one message SC-PTM configuration (SC-PTMConfiguration) for configuring configuration information of the SC-PTM. A new radio network temporary identity (Radio Network Temporary Identity, RNTI), single cell RNTI (SINGLE CELL RNTI, SC-RNTI) (fixed value FFFC) is introduced to identify scheduling information of the SC-MCCH on the physical downlink control channel (Physical Downlink Control Channel, PDCCH).
The SC-PTM introduces a new RNTI, a single cell Notification RNTI (SINGLE CELL Notification RNTI, SC-N-RNTI) (fixed value FFFB), and identifies the PDCCH of the SC-MCCH change Notification. The change notification is indicated by one bit of 8 bits (bits) in a downlink control information Format (Downlink Control Information Format, DCI Format) 1C. The modification period boundary is defined as SFN mod m=0, where m is the modification period (sc-mcch-ModificationPeriod) configured in SIB 20.
In NR, the radio link control (Radio Link Control, RLC) acknowledged mode (Acknowledged Mode, AM) mode is with automatic repeat request (Automatic Repeat reQuest, ARQ) feedback mechanism. The receiving end transmits an RLC status report to feedback whether the reception status of the RLC packet is an Acknowledgement (ACK) or a negative Acknowledgement (Negative Acknowledgement, NACK). The transmitting end may repeatedly transmit the RLC packet of the Sequence Number (SN) number of the feedback NACK.
For better understanding of the embodiments of the present application, the downlink BWP configuration related to the present application is described.
The Downlink BWP is configured by a BWP-Downlink parameter, as shown in the following first-segment asn.1 code, and the parameter includes an identifier (Id) for BWP-Id field identifying the current BWP, BWP-Common is used to configure a Common parameter of the Downlink BWP, as shown in the following second-segment asn.1 code, where GENERICPARAMETERS in BWP-DownlinkCommon is used to configure a frequency domain starting point of the Downlink BWP and the number of physical resource blocks (physical resource block, PRBs) included. For a terminal-specific unicast BWP, the BWP-decoded parameter in BWP-Downlink will configure the Downlink reception parameter on the Downlink BWP, which as shown in the following third-segment asn.1 code, at least includes PDCCH-Config, PDSCH-Config, and SPS-Config, and the second-segment asn.1 code, where PDCCH-Config is used to indicate the PDCCH transmission mode on the Downlink BWP, PDSCH-Config is used to indicate the PDSCH transmission mode on the Downlink BWP, and SPS-Config is used to indicate the Semi-persistent scheduling (Semi-PERSISTENT SCHEDULING, SPS) configuration on the Downlink BWP.
First segment asn.1 encoding:
third segment asn.1 coding:
In order to better understand the embodiments of the present application, the propagation mode of the NR MBS related to the present application will be described.
For MBS services, the manner in which the base station schedules transmissions is as follows:
Broadcast (Broadcast): the MBS service is sent in a broadcast mode, and is suitable for the terminal to be in an RRC_IDLE/RRC_INACTIVE state and the terminal equipment to be in an RRC_CONNECTED state. That is, through the MBS service transmitted by broadcasting, the terminal is in any link state as long as it can receive the same within the coverage area.
Multicast/Multicast (Multicast): and the base station sends the same MBS service to a group of terminals by a one-to-many PTM sending mode.
Unicast (Unicast): and the base station sends the same MBS service to each terminal by a one-to-one PTP sending mode.
For better understanding of the embodiments of the present application, descriptions are given to the NR MBS group scheduling method related to the present application.
In NR MBS, one-to-many multicast transmission needs to be supported, in this transmission mode, the base station needs to schedule a common PDSCH by sending a common downlink control channel, where the common PDCCH and the common PDSCH are sent in a section of common frequency domain resource (Common Frequency Resource, CFR). In some embodiments, there are two alternative CFR configurations:
First kind: the CFR is configured as an MBS-specific BWP, which is associated with a terminal-specific unicast BWP, and the subcarrier spacing and cyclic prefix configured on the CFR are the same as those on the terminal-specific unicast BWP.
Second kind: the CFR is configured as a plurality of PRBs that are contiguous in the terminal-specific unicast BWP range.
The first approach has the advantage that the CFR can follow the BWP signaling configuration, which is advantageous for reducing the standard workload, but has the problem that, since the CFR is defined as BWP, if the terminal is required to receive unicast in dedicated unicast BWP and multicast in CFR at the same time, meaning that the terminal needs to receive downlink transmission on two BWP simultaneously, the terminal is however only capable of receiving downlink on one BWP at a given moment, and in addition, even if the terminal receives unicast and multicast at different times, BWP handover delay is introduced because both are located in different BWP. The second method can avoid the problem of BWP handover, but in this method, since the CFR is a plurality of consecutive PRBs, the existing BWP-based signaling configuration cannot be used, and the resource range of the CFR, the configuration mode of uplink and downlink transmission parameters, and the like need to be redesigned, which has a large impact on the standard.
In addition, since the common PDCCH scheduling the common PDSCH needs to be simultaneously transmitted to a plurality of receiving terminals, in order to ensure that the number of bits of common downlink control information (Downlink Control Information, DCI) carried in the common PDCCH determined by the plurality of terminals is the same, the terminal cannot determine the number of bits of the common DCI according to the configuration of the respective dedicated unicast BWP, and in addition, since the number of PRBs of the CFR may be different from the initial BWP or control resource set #0 (Control Resource Set 0, coreset # 0) currently configured by the terminal, the terminal cannot determine the number of bits of the common DCI through the initial BWP or CORESET #0. Therefore, it is inevitable that the number of bits of the Common DCI may be different from the number of DCI bits received by the terminal in the terminal device specific search space (UE SEARCH SPACE, USS) or the Common search space (Common SEARCH SPACE, CSS). Then, in order to reduce the implementation complexity of the terminal, the terminal can only receive DCI with 4 different bit numbers at most in one cell, wherein the bit number of DCI scrambled by a cell radio network temporary identifier (Cell Radio Network Temporary Identity, C-RNTI) is not more than 3.
In some embodiments, as shown in fig. 4, there may be three ways of scheduling transmission of MBS services, in which PTM1 and Point-to-Point (PTP) are already supported. A group shared PDCCH (GC-PDCCH) or a group shared PDSCH (GC-PDSCH) refers to a PDCCH/PDSCH transmitted by a base station on a set of time-frequency resources that can be received by multiple UEs of the same group. The Point-to-multipoint-Point (PTM) scheduling modes mentioned in this scheme are all referred to as PTM1.
PTM 1: for multiple UEs of the same group in a connected state, a group shared PDCCH (GC-PDCCH) is used to schedule a group shared PDSCH (GC-PDSCH), wherein a cyclic redundancy check (Cyclical Redundancy Check, CRC) of the group shared PDCCH (GC-PDCCH) is scrambled using a group shared RNTI (G-RNTI), and the group shared PDSCH (GC-PDSCH) is scrambled using the same group shared RNTI (G-RNTI).
PTM 2: for multiple UEs of the same group in a connected state, a group shared PDSCH (GC-PDSCH) is scheduled for each UE using a UE-specific PDCCH, wherein the CRC of the UE-specific PDCCH is scrambled using a UE-specific RNTI (i.e., C-RNTI), and the group shared PDSCH (GC-PDSCH) is scrambled using a group shared RNTI (G-RNTI).
PTP: for connected UEs, a UE-specific PDCCH is used to schedule a UE-specific PDSCH for each UE, wherein the CRC of the UE-specific PDCCH is scrambled using a UE-specific RNTI (i.e., C-RNTI) and the UE-specific PDSCH is scrambled using a UE-specific RNTI (i.e., C-RNTI).
In some embodiments, the retransmission mechanism of MBS service based on hybrid automatic repeat request-acknowledgement (Hybrid Automatic Repeat request Acknowledgement, HARQ-ACK) feedback in connection state supports several ways as follows:
mode one: primary transmission PTM1+retransmission PTM1;
mode two: the PTM1+ retransmission PTP is initially transmitted.
For better understanding of the embodiments of the present application, the manner in which HARQ Process IDs (HPIDs) are used for NR MBS multicast and unicast related to the present application will be described.
HPID (HARQ process ID: 0-15) sharing the system between multicast/multicast and unicast, how HPID is specifically allocated is determined by the base station implementation.
HPID and the new data indication (New Data Indicator, NDI) together determine whether a currently transmitted transport block (Transmission block, TB) is an initial transmission or a retransmission. For example, currently received HPID #1 corresponds to ndi=0 carried in DCI.
Comparing ndi=1 corresponding to HPID #1 received immediately before, and determining the currently received TB as an initial transmission of a new TB; the UE empties the data information of the last TB stored in the buffer, and then stores the initial transmission of the newly received TB and the potentially received retransmission in the buffer for soft combining.
The currently received TB may be determined to be retransmitted at this time by comparing ndi=0 corresponding to HPID #1 received previously.
In order to facilitate better understanding of the embodiments of the present application, the technical problems to be solved by the present application will be described.
For SPS PDSCH of unicast service, the technical schemes of SPS activation (activation) and deactivation (deactivation) are as follows:
the CRC of DCI is scrambled by CS-RNTI to indicate activation and deactivation of SPS configuration (SPS configuration).
Activating: a single DCI activates a single SPS configuration at a time, and the HPN information field in the DCI indicates the SPS configuration index to be activated.
Deactivation: a) A single DCI may deactivate a single SPS configuration at a time, a hybrid automatic repeat request process number (Hybrid Automatic Repeat request process number, HPN) information field in the DCI indicating an SPS configuration index to be deactivated; b) Multiple SPS configurations can be deactivated at a time by a single DCI, and the higher layer configures the list of deactivation status lists (SPS-ConfigDeactivationStateList) by configuration parameters SPS, each row of the list corresponds to a list index value, each index value corresponds to one or more SPS configuration indexes, and the HPN information field in the DCI indicates a list index value and corresponds to deactivating one or more SPS configuration indexes corresponding to the list index value.
The SPS configuration supported by the unicast service is 8 at most, and the SPS configuration index is represented by 0-7;
The HPN information field in DCI is 4 bits long, and the first 8bits (i.e., 0000-0111) are used to indicate the SPS configuration index or list index to which activation/deactivation corresponds.
The CRC of the group shared DCI is scrambled by a group pre-configured scheduling radio network temporary identity (Group Configured Scheduling Radio Network Temporary Identity, G-CS-RNTI) for indicating activation or deactivation of SPS configuration common to a group of terminals.
Activating: a single group shared DCI activating a single SPS configuration for a group of UEs at a time, an HPN information field in the DCI indicating an SPS configuration index to activate;
Deactivation: a) A single group shared DCI may deactivate a single SPS configuration of a group of UEs at a time, an HPN information field in the DCI indicating an SPS configuration index to be deactivated; b) A single UE-specific DCI (CRC scrambled with a pre-configured scheduling radio network temporary identity (Configured Scheduling Radio Network Temporary Identity, CS-RNTI)) may deactivate a single SPS configuration of one UE at a time, the HPN information field in the DCI indicating the SPS configuration index to be deactivated; c) A single set of shared DCI may deactivate multiple SPS configurations for a set of UEs at a time; or a single UE-specific DCI may deactivate multiple SPS configurations for one UE at a time.
The SPS configuration supported by MBS service is 8 at most, and the SPS configuration index is undetermined; the HPN information field in the DCI is 4 bits long, which status bits are used to indicate that the SPS configuration index or list index corresponding to activation/deactivation is not specified.
Considering the SPS configuration design when the system has only unicast service, when the system supports SPS configuration of MBS service, the unicast service and SPS of MBS service coexist, which can generate a series of problems, and the following problems are not solved yet.
When the terminal-specific DCI is used for deactivating SPS configuration, the terminal cannot distinguish the SPS of the unicast service or the SPS configuration of the MBS service when the DCI is deactivated because the CRC of the DCI adopts CS-RNTI scrambling, and because only the HPN information field is used for indicating the corresponding SPS configuration index in the DCI, no other information is used for indicating the distinction between the unicast service and the MBS service.
The SPS configuration index for MBS services has not been determined, and 0-7 is used to represent the SPS configuration index, or other numerical representation.
How to map the correspondence between bit status bits in the HPN information domain and MBS SPS configuration indexes.
How to design an SPS configuration list configuring MBS services, multiple SPS configurations can be deactivated using a single DCI, and it is possible to distinguish which SPS configurations belong to the unicast service and which SPS configurations belong to the MBS services from these deactivated SPS configuration indexes.
Based on the technical problems, the application provides a scheme for activating or deactivating SPS configuration, a communication system can simultaneously support SPS configuration associated with unicast service and SPS configuration associated with MBS service to work simultaneously, and the SPS configuration associated with unicast service and the SPS configuration associated with MBS service have no limit or influence on each other, and furthermore, the SPS configuration associated with unicast service and the SPS configuration associated with MBS service can work cooperatively, so that the compatibility performance of the communication system is improved.
The technical scheme of the application is described in detail below through specific embodiments.
Fig. 5 is a schematic flow chart of a method 200 of wireless communication according to an embodiment of the application, as shown in fig. 5, the method 200 of wireless communication may include at least some of the following:
S210, the network equipment sends first DCI to the terminal equipment; the first DCI is used for activating or deactivating M SPS configurations, wherein M is a positive integer; wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with MBS service;
s220, the terminal device receives the first DCI.
In the embodiment of the present application, the DCI for activating the SPS configuration is different from the DCI for deactivating the SPS configuration.
In some embodiments, the MBS service according to the embodiments of the present application may also be an MBMS service, which is not limited in this aspect of the present application.
In some embodiments, m=1, i.e., the first DCI may activate or deactivate a single SPS configuration, in which case the unicast service associated SPS configuration or the MBS service associated SPS configuration.
In some embodiments, M > 1, i.e., the first DCI may activate or deactivate a plurality of SPS configurations, where the plurality of SPS configurations are each unicast service-associated SPS configurations, or the plurality of SPS configurations are each MBS service-associated SPS configurations, or a portion of the plurality of SPS configurations are unicast service-associated SPS configurations, and another portion of the plurality of SPS configurations are MBS service-associated SPS configurations.
In some embodiments, the M SPS configurations may be SPS configurations of the terminal device, or the M SPS configurations may be SPS configurations of a terminal group to which the terminal device belongs.
In some embodiments, the CRC of the first DCI is scrambled with a CS-RNTI. That is, the first DCI is DCI specific to the terminal device.
In some embodiments, there are R SPS configurations configured for unicast traffic and/or Q SPS configurations configured for MBS traffic; wherein R is more than or equal to 1 and less than or equal to R max,1≤Q≤Q max,R、Q、R max and Q max are positive integers. That is, the network device may configure R SPS configurations for the terminal device for unicast traffic and Q SPS configurations for the terminal device for MBS traffic.
Specifically, the values of R and Q may be the same or different. R max and Q max may be the same or different.
In some implementations, the value of R may also be 0 (r=0), i.e. no SPS configuration is configured for unicast traffic. Similarly, the value of Q may also be 0 (q=0), i.e. no SPS configuration is configured for MBS service.
In some embodiments, R max is one of the following values: 8. 16, 32. Of course, R max may have other values, which are not limited in this regard.
For example, r=8, that is, the value range of the SPS configuration index (SPS-ConfigIndex) associated with the unicast service is 0 to 7.
In some embodiments, Q max is one of the following values: 8. 16, 32. Of course, Q max may have other values, which the present application is not limited to.
For example, q=8, i.e. the SPS configuration index (SPS-ConfigIndex) associated with MBS service has a value ranging from 0 to 7.
Embodiment 1, the first DCI includes a first information field; wherein the number of SPS configurations associated with MBS service in the M SPS configurations is 1, and the first information field is used to indicate SPS configuration indexes associated with MBS service in the M SPS configurations.
In some implementations, m=1, i.e., the M SPS configurations include only one MBS service associated SPS configuration.
In some implementations, the M SPS configurations may also include one or more SPS configurations associated with unicast traffic, and in particular, the SPS configuration index associated with unicast traffic may be indicated by other information fields in the first DCI.
In some implementations, different status bits of the first information field correspond to SPS configuration indexes associated with different MBS services, respectively.
In some implementations of embodiment 1, the correspondence between the status bits of the first information domain and SPS configuration indexes associated with MBS services is agreed by a protocol, or the correspondence between the status bits of the first information domain and SPS configuration indexes associated with MBS services is configured by a network device.
In some implementations, the length of the first information field is greater than or equal to 3 bits, and the SPS configuration index of the MBS service association indicated by the first information field is K; wherein K is an integer, and K is more than or equal to 0 and less than or equal to Q-1.
In some implementations of embodiment 1, the first information field is an information field other than the HPN information field in the first DCI, or the first information field is an information field in the first DCI dedicated to indicating an SPS configuration index associated with an MBS service.
Specifically, for example, the first information domain is a time domain resource allocation (Time domain resource assignment, TDRA) information domain, or the first information domain is a modulation and coding scheme (Modulation and Coding Scheme, MCS) information domain, or the first information domain is a physical uplink control channel (Physical Uplink Control Channel, PUCCH) resource indication information domain, or the first information domain is a PDSCH-to-HARQ feedback timing indication information domain.
In some implementations of embodiment 1, assuming that the length of the first information field is 3 bits, q=8, that is, the SPS configuration index (SPS-ConfigIndex) of the MBS service association ranges from 0 to 7, the SPS configuration index of the MBS service association indicated by the 8 status bits of the first information field in the first DCI may be specifically shown in table 1.
TABLE 1
The above table 1 is merely an example, and does not limit the present application.
Embodiment 2, the first DCI includes a second information field and a third information field;
Wherein the M SPS configurations include only a first SPS configuration (i.e., m=1), the second information field is used to indicate an index of the first SPS configuration, the third information field is used to indicate that the first SPS configuration is a unicast service associated SPS configuration, or the third information field is used to indicate that the first SPS configuration is an MBS service associated SPS configuration.
Specifically, for example, the second information field is used to indicate an index of the first SPS configuration (e.g., SPS-configindex=1). The third information field occupies 1 bit; wherein, bit state 0 corresponds to indicate that the first SPS configuration is SPS configuration associated with unicast service, and bit state 1 corresponds to indicate that the first SPS configuration is SPS configuration associated with MBS service; or bit state 1 corresponds to indicate that the first SPS configuration is an SPS configuration associated with a unicast service and bit state 0 corresponds to indicate that the first SPS configuration is an SPS configuration associated with an MBS service.
In some implementations, different status bits of the second information field correspond to different SPS configuration indexes, respectively.
In some implementations of embodiment 2, the correspondence between the status bits of the second information field and the SPS configuration index is agreed by a protocol, or the correspondence between the status bits of the second information field and the SPS configuration index is configured by a network device.
In some implementations of embodiment 2, the SPS configuration index associated with unicast traffic is L, 0.ltoreq.L.ltoreq.R-1; and/or SPS configuration index related to MBS service is K, K is more than or equal to 0 and less than or equal to Q-1; wherein L and K are integers.
In some implementations, the second information field is an HPN information field in the first DCI, e.g., the second information field is 4 bits of the HPN information field in the first DCI.
In some implementations, the third information field is a virtual resource block (virtual resource block, VRB) to PRB mapping (VRB-to-PRB mapping) information field in the first DCI, or the third information field is a redundancy version (Redundancy version) information field in the first DCI, which may be specifically shown in table 2. Alternatively, the third information field may be a new data indication (New Data Indicator, NDI) information field, or other information field, which is not limited by the present application.
TABLE 2
In some implementations of embodiment 2, the second information field in the first DCI is assumed to be 4 bits in length and the third information field in the first DCI is assumed to be 1 bit in length. R=8, i.e. the value range of the SPS configuration index (SPS-ConfigIndex) associated with the unicast service is 0-7; q=8, i.e. the SPS configuration index (SPS-ConfigIndex) associated with MBS service has a value ranging from 0 to 7. Specifically, as shown in tables 3 and 4, 8 status bits of the second information field in the first DCI indicate 8 SPS configuration indexes, respectively, and status 0 of the third information field in the first DCI indicates an SPS configuration index associated with an MBS, and status 1 indicates an SPS configuration index associated with a unicast service.
TABLE 3 Table 3
TABLE 4 Table 4
Note that, the status bits corresponding to the numbers 9 to 16 in the above tables 3 and 4 are reserved. Further, the above tables 3 and 4 are only examples and do not limit the constitution of the present application.
Embodiment 3, the first DCI includes a fourth information field; wherein the M SPS configurations include only a second SPS configuration (i.e., m=1), the fourth information field is used to indicate an index of the second SPS configuration, and the fourth information field is used to indicate that the second SPS configuration is a unicast service associated SPS configuration, or the fourth information field is used to indicate that the second SPS configuration is an MBS service associated SPS configuration.
Specifically, the SPS configuration associated with the unicast service and the SPS configuration associated with the MBS service may be distinguished by the status bit of the fourth information field.
In some implementations, the fourth information field is an HPN information field in the first DCI.
In some implementations of embodiment 3, the SPS configuration index associated with unicast traffic is L, 0.ltoreq.L.ltoreq.R-1, the SPS configuration index associated with MBS traffic is K, 0.ltoreq.K.ltoreq.Q-1, where L and K are integers; the 1 st to the R-th status bits in the fourth information domain are used for indicating an SPS configuration index associated with a unicast service, and the r+1st to the q+r-th status bits in the fourth information domain are used for indicating an SPS configuration index associated with an MBS service.
Specifically, for example, assume that the length of the fourth information field in the first DCI is 4 bits. R=8, i.e. the value range of the SPS configuration index (SPS-ConfigIndex) associated with the unicast service is 0-7; q=8, i.e. the SPS configuration index (SPS-ConfigIndex) associated with MBS service has a value ranging from 0 to 7. Specifically, as shown in table 5, the first 8 status bits of the fourth information field in the first DCI indicate SPS configuration indexes associated with 8 unicast services, and the last 8 status bits of the fourth information field in the first DCI indicate SPS configuration indexes associated with 8 MBS services.
TABLE 5
In some implementations of embodiment 3, the SPS configuration index associated with unicast traffic is L, 0.ltoreq.L.ltoreq.R-1, and the SPS configuration index associated with MBS traffic is K, R.ltoreq.K.ltoreq.R+Q-1; wherein L and K are integers; the 1 st to the R-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with unicast service, respectively, and the r+1st to the q+r-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with MBS service, respectively.
Specifically, for example, assume that the length of the fourth information field in the first DCI is 4 bits. R=8, i.e. the value range of the SPS configuration index (SPS-ConfigIndex) associated with the unicast service is 0-7; q=8, i.e. the SPS configuration index (SPS-ConfigIndex) associated with MBS service has a value range of 8-15. Specifically, as shown in table 6, the first 8 status bits of the fourth information field in the first DCI indicate SPS configuration indexes associated with 8 unicast services, and the last 8 status bits of the fourth information field in the first DCI indicate SPS configuration indexes associated with 8 MBS services.
TABLE 6
It should be noted that the above tables 5 and 6 are only examples, and do not limit the present application.
In some implementations of embodiment 3, in tables 5 and 6 above, the first 8 status bits indicate SPS configuration indexes associated with 8 unicast services, respectively, and the last 8 status bits indicate SPS configuration indexes associated with 8 MBS services, respectively. In some implementations, the 8 status bits of the odd bits may respectively indicate SPS configuration indexes associated with 8 unicast services, and the 8 status bits of the even bits respectively indicate SPS configuration indexes associated with 8 MBS services. Or other combinations of status bits to distinguish between unicast service associated SPS configurations and MBS service associated SPS configurations.
Embodiment 4, the first DCI includes a fifth information field and a sixth information field; the fifth information field is used for indicating a first state index, and the first state index corresponds to the indexes of the M SPS configurations; the sixth information field is used to indicate that the first state index is a state index in a first SPS configuration state list, or the sixth information field is used to indicate that the first state index is a state index in a second SPS configuration state list.
In example 4, M.gtoreq.1.
In some implementations, the fifth information field in the first DCI is assumed to be 4 bits in length. R=8, i.e. the value range of the SPS configuration index (SPS-ConfigIndex) associated with the unicast service is 0-7; q=8, i.e. the SPS configuration index (SPS-ConfigIndex) associated with MBS service has a value ranging from 0 to 7. Specifically, the first SPS configuration state list may be as shown in table 7, and the second SPS configuration state list may be as shown in table 8.
Specifically, for example, the sixth information field may occupy 1 bit. For example, a bit state of 0 corresponds to the first SPS configuration state list, i.e., as shown in table 7; the bit state of 1 corresponds to the second SPS configuration state list, i.e., as shown in table 8.
TABLE 7
TABLE 8
It should be noted that, the above tables 7 and 8 are only examples, and the SPS configuration indexes corresponding to each state index in tables 7 and 8 may be randomly combined, and the present application is not limited thereto.
In embodiment 4, one state index in the first SPS configuration state list (SPS-ConfigStateList-1) corresponds to one or more unicast service associated SPS configuration indexes, and one state index in the second SPS configuration state list (SPS-ConfigStateList-2) corresponds to one or more MBS service associated SPS configuration indexes.
In some implementations, the first SPS configuration state list is agreed upon by a protocol, or the first SPS configuration state list is configured by a network device.
In some implementations, the second SPS configuration state list is agreed upon by a protocol, or the second SPS configuration state list is configured by a network device.
Alternatively, the first SPS configuration state list and the second SPS configuration state list may be configured by a network device via one signaling, or the first SPS configuration state list and the second SPS configuration state list may be configured by a network device via a different signaling.
In some implementations of embodiment 4, the fifth information field is an HPN information field in the first DCI. For example, the fifth information field is HPN 4 bits.
In some implementations of embodiment 4, the sixth information field is a VRB-to-PRB mapping information field in the first DCI or the sixth information field is a redundancy version information field in the first DCI. See, in particular, table 2 above. Alternatively, the sixth information field may be an NDI information field, or other information fields, which is not limited by the present application.
Embodiment 5, the first DCI includes a seventh information field; the seventh information field is used for indicating one state index in the third SPS configuration state list, and the state index indicated by the seventh information field corresponds to the indexes of the M SPS configurations.
In embodiment 5, one state index in the third SPS configuration state list corresponds to at least one SPS configuration index associated with unicast traffic and/or at least one SPS configuration index associated with MBS traffic.
In example 5, M.gtoreq.1.
In some implementations of embodiment 5, the SPS configuration index associated with unicast traffic is L, 0.ltoreq.L.ltoreq.R-1, and the SPS configuration index associated with MBS traffic is K, R.ltoreq.K.ltoreq.R+Q-1; wherein L and K are integers.
For example, let r=8, that is, the value range of the SPS configuration index (SPS-ConfigIndex) associated with the unicast service is 0 to 7; q=8, i.e. the SPS configuration index (SPS-ConfigIndex) associated with MBS service has a value range of 8 to 15, as shown in table 9.
TABLE 9
The above table 9 is merely an example, and does not limit the present application.
In some implementations, the seventh information field in the first DCI is assumed to be 4 bits in length. R=8, i.e. the value range of the SPS configuration index (SPS-ConfigIndex) associated with the unicast service is 0-7; q=8, i.e. the SPS configuration index (SPS-ConfigIndex) associated with MBS service has a value ranging from 0 to 7. Specifically, the third SPS configuration state list may be as shown in table 10 below.
Table 10
It should be noted that, the above table 10 is merely an example, and the SPS configuration indexes corresponding to each state index in the table 10 may be randomly combined, and the present application is not limited thereto.
In some implementations, the third SPS configuration state list is agreed upon by a protocol, or the third SPS configuration state list is configured by a network device.
In some implementations of embodiment 5, the seventh information field is an HPN information field in the first DCI.
Embodiment 6, the first DCI includes an eighth information field;
wherein the M SPS configurations include only a third SPS configuration (i.e., m=1), the eighth information field is used to indicate an index of the third SPS configuration among indexes of N SPS configurations, the N SPS configurations include N 1 SPS configurations associated with unicast service and N 2 SPS configurations associated with MBS service, the third SPS configuration is an SPS configuration associated with unicast service, or the third SPS configuration is an SPS configuration associated with MBS service;
Wherein N, N 1,n 2 are both positive integers, and N 1+n 2 =n.
In some of the embodiments of the present invention, N is more than or equal to 1 and less than or equal to N max,N max, and the value is one of the following: 8. 16, 32.
Specifically, for example, n=8, 0.ltoreq.n 1≤8,0≤n 2.ltoreq.8, and N 1+n 2 =8.
In some implementations, the eighth information field is ≡3 bits in length.
In some implementations of embodiment 6, the indexes of the N SPS configurations are uniformly numbered.
In some implementations of embodiment 6, the index of the N SPS configurations and the corresponding SPS configuration type are agreed by a protocol, or the index of the N SPS configurations and the corresponding SPS configuration type are configured by the network device.
In some implementations of embodiment 6, the eighth information field is an HPN information field (4 bits) in the first DCI.
In some implementations, assume that the eighth information field in the first DCI is 4 bits in length, n=8. n 1 = 5, SPS configuration index (SPS-ConfigIndex) 0,2,3,5,7 is SPS configuration associated with unicast traffic; n 2 = 3, SPS configuration index (SPS-ConfigIndex) of 1,4,6 is SPS configuration associated with MBS service. Specifically, the index of 8 SPS configurations and the corresponding SPS configuration type may be as shown in table 11 below.
TABLE 11
In the embodiment of the application, the terminal-dedicated DCI is used for activating/deactivating the SPS configuration, so that the problem of confusion of the terminal-dedicated DCI for activating/deactivating the SPS configuration is effectively avoided, the DCI is clearly and definitely distinguished between the unicast service and the MBS service, the design mechanism of the unicast service is not influenced, and additional signaling overhead or redundant design is not added; in addition, the design of activating/deactivating a plurality of SPS configurations by single DCI in MBS service is supported, the cost of downlink control signaling is greatly saved, and the flexibility of the system in SPS dynamic control is improved.
Thus, in an embodiment of the present application, the network device may activate or deactivate M SPS configurations through the first DCI, where the types of M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with MBS service. Therefore, the communication system can simultaneously support the SPS configuration associated with the unicast service and the SPS configuration associated with the MBS service to work simultaneously without limitation and influence among the SPS configuration associated with the unicast service and the SPS configuration associated with the MBS service, and furthermore, the SPS configuration associated with the unicast service and the SPS configuration associated with the MBS service can work cooperatively, so that the compatibility of the communication system is improved.
The method embodiment of the present application is described in detail above with reference to fig. 5, and the apparatus embodiment of the present application is described in detail below with reference to fig. 6 to 7, it being understood that the apparatus embodiment corresponds to the method embodiment, and similar descriptions can refer to the method embodiment.
Fig. 6 shows a schematic block diagram of a terminal device 300 according to an embodiment of the application. As shown in fig. 6, the terminal device 300 includes:
a communication unit 310, configured to receive first downlink control information DCI;
The first DCI is used for activating or deactivating M semi-persistent scheduling (SPS) configurations, wherein M is a positive integer;
Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with multicast broadcast service MBS service.
In some embodiments, the cyclic redundancy check, CRC, of the first DCI is scrambled with a pre-configured scheduling radio network temporary identity, CS-RNTI.
In some embodiments, there are R SPS configurations configured for unicast traffic and/or Q SPS configurations configured for MBS traffic;
Wherein R is more than or equal to 1 and less than or equal to R max,1≤Q≤Q max,R、Q、R max and Q max are positive integers.
In some embodiments, R max is one of the following values: 8. 16, 32; and/or, the value of Q max is one of the following: 8. 16, 32.
In some embodiments, the first DCI includes a first information field;
Wherein the number of SPS configurations associated with MBS service in the M SPS configurations is 1, and the first information field is used to indicate SPS configuration indexes associated with MBS service in the M SPS configurations.
In some embodiments, different status bits of the first information field correspond to SPS configuration indexes associated with different MBS services, respectively.
In some embodiments, the correspondence between the status bits of the first information domain and SPS configuration indexes associated with MBS services is agreed by a protocol, or the correspondence between the status bits of the first information domain and SPS configuration indexes associated with MBS services is configured by a network device.
In some embodiments, the length of the first information field is greater than or equal to 3 bits, and the SPS configuration index of the MBS service association indicated by the first information field is K; wherein K is an integer, and K is more than or equal to 0 and less than or equal to Q-1.
In some embodiments, the first information field is an information field other than the hybrid automatic repeat request process number HPN information field in the first DCI, or the first information field is an information field in the first DCI dedicated to indicating an SPS configuration index associated with an MBS service.
In some embodiments, the first DCI includes a second information field and a third information field;
Wherein the M SPS configurations include only a first SPS configuration, the second information field is used to indicate an index of the first SPS configuration, the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with a unicast service, or the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with an MBS service.
In some embodiments, different status bits of the second information field correspond to different SPS configuration indexes, respectively.
In some embodiments, the correspondence between the status bits of the second information field and the SPS configuration index is agreed by a protocol, or the correspondence between the status bits of the second information field and the SPS configuration index is configured by a network device.
In some embodiments, SPS configuration index associated with unicast traffic is L, 0.ltoreq.L.ltoreq.R-1; and/or SPS configuration index related to MBS service is K, K is more than or equal to 0 and less than or equal to Q-1; wherein L and K are integers.
In some embodiments, the second information field is an HPN information field in the first DCI.
In some embodiments, the third information field is a virtual resource block VRB to physical resource block PRB mapping information field in the first DCI or the third information field is a redundancy version information field in the first DCI.
In some embodiments, the first DCI includes a fourth information field;
Wherein the M SPS configurations include only a second SPS configuration, the fourth information field is used to indicate an index of the second SPS configuration, and the fourth information field is used to indicate that the second SPS configuration is an SPS configuration associated with a unicast service, or the fourth information field is used to indicate that the second SPS configuration is an SPS configuration associated with an MBS service.
In some embodiments, SPS configuration index associated with unicast service is L, 0.ltoreq.L.ltoreq.R-1, SPS configuration index associated with MBS service is K, 0.ltoreq.K.ltoreq.Q-1; or SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, R is more than or equal to K and less than or equal to R+Q-1; wherein L and K are integers;
The 1 st to the R-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with unicast service, respectively, and the r+1st to the q+r-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with MBS service, respectively.
In some embodiments, the fourth information field is an HPN information field in the first DCI.
In some embodiments, the first DCI includes a fifth information field and a sixth information field;
The fifth information field is used for indicating a first state index, the sixth information field is used for indicating that the first state index is a state index in a first SPS configuration state list, or the sixth information field is used for indicating that the first state index is a state index in a second SPS configuration state list;
Wherein, one state index in the first SPS configuration state list corresponds to one or more SPS configuration indexes associated with unicast service, one state index in the second SPS configuration state list corresponds to one or more SPS configuration indexes associated with MBS service, and the first state index corresponds to the M SPS configuration indexes.
In some embodiments, the first SPS configuration state list is agreed upon by a protocol, or the first SPS configuration state list is configured by a network device.
In some embodiments, the second SPS configuration state list is agreed upon by a protocol, or the second SPS configuration state list is configured by a network device.
In some embodiments, the fifth information field is an HPN information field in the first DCI.
In some embodiments, the sixth information field is a VRB-to-PRB mapping information field in the first DCI or the sixth information field is a redundancy version information field in the first DCI.
In some embodiments, the first DCI includes a seventh information field;
wherein the seventh information field is for indicating a state index in the third SPS configuration state list;
Wherein, one state index in the third SPS configuration state list corresponds to at least one SPS configuration index associated with a unicast service and/or at least one SPS configuration index associated with an MBS service, and the state index indicated by the seventh information field corresponds to the indexes of the M SPS configurations.
In some embodiments, SPS configuration index associated with unicast service is L, 0.ltoreq.L.ltoreq.R-1, SPS configuration index associated with MBS service is K, R.ltoreq.K.ltoreq.R+Q-1; wherein L and K are integers.
In some embodiments, the third SPS configuration state list is agreed upon by a protocol, or the third SPS configuration state list is configured by a network device.
In some embodiments, the seventh information field is an HPN information field in the first DCI.
In some embodiments, the first DCI includes an eighth information field;
Wherein the M SPS configurations include only a third SPS configuration, the eighth information field is used to indicate an index of the third SPS configuration among indexes of N SPS configurations, the N SPS configurations include N 1 SPS configurations associated with unicast service and N 2 SPS configurations associated with MBS service, the third SPS configuration is an SPS configuration associated with unicast service, or the third SPS configuration is an SPS configuration associated with MBS service;
Wherein N, N 1,n 2 are both positive integers, and N 1+n 2 =n.
In some embodiments, the indexes of the N SPS configurations are uniformly numbered.
In some embodiments, the index of the N SPS configurations and the corresponding SPS configuration type are agreed by a protocol, or the index of the N SPS configurations and the corresponding SPS configuration type are configured by a network device.
In some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip.
It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 5, which is not described herein for brevity.
Fig. 7 shows a schematic block diagram of a network device 400 according to an embodiment of the application. As shown in fig. 7, the network device 400 includes:
A communication unit 410, configured to send first downlink control information DCI;
The first DCI is used for activating or deactivating M semi-persistent scheduling (SPS) configurations, wherein M is a positive integer;
Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with multicast broadcast service MBS service.
In some embodiments, the cyclic redundancy check, CRC, of the first DCI is scrambled with a pre-configured scheduling radio network temporary identity, CS-RNTI.
In some embodiments, there are R SPS configurations configured for unicast traffic and/or Q SPS configurations configured for MBS traffic;
Wherein R is more than or equal to 1 and less than or equal to R max,1≤Q≤Q max,R、Q、R max and Q max are positive integers.
In some embodiments, R max is one of the following values: 8. 16, 32; and/or, the value of Q max is one of the following: 8. 16, 32.
In some embodiments, the first DCI includes a first information field;
Wherein the number of SPS configurations associated with MBS service in the M SPS configurations is 1, and the first information field is used to indicate SPS configuration indexes associated with MBS service in the M SPS configurations.
In some embodiments, different status bits of the first information field correspond to SPS configuration indexes associated with different MBS services, respectively.
In some embodiments, the correspondence between the status bits of the first information domain and SPS configuration indexes associated with MBS services is agreed by a protocol, or the correspondence between the status bits of the first information domain and SPS configuration indexes associated with MBS services is configured by a network device.
In some embodiments, the length of the first information field is greater than or equal to 3 bits, and the SPS configuration index of the MBS service association indicated by the first information field is K; wherein K is an integer, and K is more than or equal to 0 and less than or equal to Q-1.
In some embodiments, the first information field is an information field other than the hybrid automatic repeat request process number HPN information field in the first DCI, or the first information field is an information field in the first DCI dedicated to indicating an SPS configuration index associated with an MBS service.
In some embodiments, the first DCI includes a second information field and a third information field;
Wherein the M SPS configurations include only a first SPS configuration, the second information field is used to indicate an index of the first SPS configuration, the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with a unicast service, or the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with an MBS service.
In some embodiments, different status bits of the second information field correspond to different SPS configuration indexes, respectively.
In some embodiments, the correspondence between the status bits of the second information field and the SPS configuration index is agreed by a protocol, or the correspondence between the status bits of the second information field and the SPS configuration index is configured by a network device.
In some embodiments, SPS configuration index associated with unicast traffic is L, 0.ltoreq.L.ltoreq.R-1; and/or SPS configuration index related to MBS service is K, K is more than or equal to 0 and less than or equal to Q-1; wherein L and K are integers.
In some embodiments, the second information field is an HPN information field in the first DCI.
In some embodiments, the third information field is a virtual resource block VRB to physical resource block PRB mapping information field in the first DCI or the third information field is a redundancy version information field in the first DCI.
In some embodiments, the first DCI includes a fourth information field;
Wherein the M SPS configurations include only a second SPS configuration, the fourth information field is used to indicate an index of the second SPS configuration, and the fourth information field is used to indicate that the second SPS configuration is an SPS configuration associated with a unicast service, or the fourth information field is used to indicate that the second SPS configuration is an SPS configuration associated with an MBS service.
In some embodiments, SPS configuration index associated with unicast service is L, 0.ltoreq.L.ltoreq.R-1, SPS configuration index associated with MBS service is K, 0.ltoreq.K.ltoreq.Q-1; or SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, R is more than or equal to K and less than or equal to R+Q-1; wherein L and K are integers;
The 1 st to the R-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with unicast service, respectively, and the r+1st to the q+r-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with MBS service, respectively.
In some embodiments, the fourth information field is an HPN information field in the first DCI.
In some embodiments, the first DCI includes a fifth information field and a sixth information field;
The fifth information field is used for indicating a first state index, the sixth information field is used for indicating that the first state index is a state index in a first SPS configuration state list, or the sixth information field is used for indicating that the first state index is a state index in a second SPS configuration state list;
Wherein, one state index in the first SPS configuration state list corresponds to one or more SPS configuration indexes associated with unicast service, one state index in the second SPS configuration state list corresponds to one or more SPS configuration indexes associated with MBS service, and the first state index corresponds to the M SPS configuration indexes.
In some embodiments, the first SPS configuration state list is agreed upon by a protocol, or the first SPS configuration state list is configured by a network device.
In some embodiments, the second SPS configuration state list is agreed upon by a protocol, or the second SPS configuration state list is configured by a network device.
In some embodiments, the fifth information field is an HPN information field in the first DCI.
In some embodiments, the sixth information field is a VRB-to-PRB mapping information field in the first DCI or the sixth information field is a redundancy version information field in the first DCI.
In some embodiments, the first DCI includes a seventh information field;
wherein the seventh information field is for indicating a state index in the third SPS configuration state list;
Wherein, one state index in the third SPS configuration state list corresponds to at least one SPS configuration index associated with a unicast service and/or at least one SPS configuration index associated with an MBS service, and the state index indicated by the seventh information field corresponds to the indexes of the M SPS configurations.
In some embodiments, SPS configuration index associated with unicast service is L, 0.ltoreq.L.ltoreq.R-1, SPS configuration index associated with MBS service is K, R.ltoreq.K.ltoreq.R+Q-1; wherein L and K are integers.
In some embodiments, the third SPS configuration state list is agreed upon by a protocol, or the third SPS configuration state list is configured by a network device.
In some embodiments, the seventh information field is an HPN information field in the first DCI.
In some embodiments, the first DCI includes an eighth information field;
Wherein the M SPS configurations include only a third SPS configuration, the eighth information field is used to indicate an index of the third SPS configuration among indexes of N SPS configurations, the N SPS configurations include N 1 SPS configurations associated with unicast service and N 2 SPS configurations associated with MBS service, the third SPS configuration is an SPS configuration associated with unicast service, or the third SPS configuration is an SPS configuration associated with MBS service;
Wherein N, N 1,n 2 are both positive integers, and N 1+n 2 =n.
In some embodiments, the indexes of the N SPS configurations are uniformly numbered.
In some embodiments, the index of the N SPS configurations and the corresponding SPS configuration type are agreed by a protocol, or the index of the N SPS configurations and the corresponding SPS configuration type are configured by the network device.
In some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip.
It should be understood that the network device 400 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the network device 400 are respectively for implementing the corresponding flow of the network device in the method 200 shown in fig. 5, which is not described herein for brevity.
Fig. 8 is a schematic block diagram of a communication device 500 according to an embodiment of the present application. The communication device 500 shown in fig. 8 comprises a processor 510, from which the processor 510 may call and run a computer program to implement the method in an embodiment of the application.
In some embodiments, as shown in fig. 8, the communication device 500 may also include a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the method in an embodiment of the application.
Wherein the memory 520 may be a separate device from the processor 510 or may be integrated into the processor 510.
In some embodiments, as shown in fig. 8, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and in particular, may transmit information or data to other devices, or receive information or data transmitted by other devices.
Wherein the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, the number of which may be one or more.
In some embodiments, the communication device 500 may be a network device in the embodiments of the present application, and the communication device 500 may implement corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.
In some embodiments, the communication device 500 may be specifically a terminal device according to an embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the terminal device in each method according to an embodiment of the present application, which is not described herein for brevity.
Fig. 9 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 600 shown in fig. 9 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the method in the embodiment of the present application.
In some embodiments, as shown in fig. 9, the apparatus 600 may further include a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.
The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.
In some embodiments, the apparatus 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.
In some embodiments, the apparatus 600 may further comprise an output interface 640. Wherein the processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.
In some embodiments, the apparatus may be applied to a network device in the embodiments of the present application, and the apparatus may implement corresponding flows implemented by the network device in each method in the embodiments of the present application, which are not described herein for brevity.
In some embodiments, the apparatus may be applied to a terminal device in the embodiments of the present application, and the apparatus may implement corresponding flows implemented by the terminal device in each method in the embodiments of the present application, which are not described herein for brevity.
In some embodiments, the device according to the embodiments of the present application may also be a chip. For example, a system-on-chip or a system-on-chip, etc.
Fig. 10 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in fig. 10, the communication system 700 includes a terminal device 710 and a network device 720.
The terminal device 710 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.
It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (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 link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (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), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing a computer program.
In some embodiments, the computer readable storage medium may be applied to the network device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.
In some embodiments, the computer readable storage medium may be applied to the terminal device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.
The embodiment of the application also provides a computer program product comprising computer program instructions.
In some embodiments, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.
In some embodiments, the computer program product may be applied to a terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.
The embodiment of the application also provides a computer program.
In some embodiments, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.
In some embodiments, the computer program may be applied to a terminal device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the terminal device in each method in the embodiments of the present application, which are not described herein for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (72)

  1. A method of wireless communication, comprising:
    the terminal equipment receives first downlink control information DCI;
    The first DCI is used to activate or deactivate M semi-persistent scheduling SPS configurations, where M is a positive integer;
    Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with multicast broadcast service MBS service.
  2. The method of claim 1, wherein a cyclic redundancy check, CRC, of the first DCI employs a pre-configured scheduling radio network temporary identity, CS-RNTI, scrambling.
  3. The method of claim 1 or 2, wherein,
    R SPS configurations are configured for unicast service and/or Q SPS configurations are configured for MBS service;
    Wherein R is more than or equal to 1 and less than or equal to R max,1≤Q≤Q max,R、Q、R max and Q max are positive integers.
  4. The method of claim 3, wherein,
    R max has one of the following values: 8. 16, 32; and/or, the value of Q max is one of the following: 8. 16, 32.
  5. The method of claim 3 or 4, wherein,
    The first DCI includes a first information field;
    Wherein the number of SPS configurations associated with MBS service in the M SPS configurations is 1, and the first information field is used to indicate SPS configuration indexes associated with MBS service in the M SPS configurations.
  6. The method of claim 5, wherein,
    Different status bits of the first information domain respectively correspond to SPS configuration indexes associated with different MBS services.
  7. The method of claim 6, wherein,
    The corresponding relation between the status bit of the first information domain and the SPS configuration index associated with the MBS service is agreed by a protocol, or the corresponding relation between the status bit of the first information domain and the SPS configuration index associated with the MBS service is configured by network equipment.
  8. The method according to any one of claim 5 to 7,
    The length of the first information domain is more than or equal to 3 bits, and the SPS configuration index of the MBS service association indicated by the first information domain is K; wherein K is an integer, and K is more than or equal to 0 and less than or equal to Q-1.
  9. The method according to any one of claim 5 to 8,
    The first information field is an information field except for a hybrid automatic repeat request (HPN) information field in the first DCI, or the first information field is an information field in the first DCI dedicated to indicating an SPS configuration index associated with an MBS service.
  10. The method of claim 3 or 4, wherein,
    The first DCI comprises a second information domain and a third information domain;
    Wherein the M SPS configurations include only a first SPS configuration, the second information field is used to indicate an index of the first SPS configuration, the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with a unicast service, or the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with an MBS service.
  11. The method of claim 10, wherein,
    Different status bits of the second information field correspond to different SPS configuration indexes, respectively.
  12. The method of claim 11, wherein,
    The corresponding relation between the status bit of the second information domain and the SPS configuration index is agreed by a protocol, or the corresponding relation between the status bit of the second information domain and the SPS configuration index is configured by network equipment.
  13. The method according to any one of claim 10 to 12, wherein,
    SPS configuration index associated with unicast service is L, L is more than or equal to 0 and less than or equal to R-1; and/or SPS configuration index related to MBS service is K, K is more than or equal to 0 and less than or equal to Q-1; wherein L and K are integers.
  14. The method according to any one of claim 11 to13, wherein,
    The second information field is an HPN information field in the first DCI.
  15. The method according to any one of claim 11 to 14, wherein,
    The third information field is a virtual resource block VRB to physical resource block PRB mapping information field in the first DCI, or the third information field is a redundancy version information field in the first DCI.
  16. The method of claim 3 or 4, wherein,
    The first DCI includes a fourth information field;
    Wherein the M SPS configurations include only a second SPS configuration, the fourth information field is used to indicate an index of the second SPS configuration, and the fourth information field is used to indicate that the second SPS configuration is a unicast service associated SPS configuration, or the fourth information field is used to indicate that the second SPS configuration is an MBS service associated SPS configuration.
  17. The method of claim 16, wherein,
    SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, K is more than or equal to 0 and less than or equal to Q-1; or SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, R is more than or equal to K and less than or equal to R+Q-1; wherein L and K are integers;
    The 1 st to the R-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with unicast service, respectively, and the r+1st to the q+r-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with MBS service, respectively.
  18. The method of claim 16 or 17, wherein,
    The fourth information field is an HPN information field in the first DCI.
  19. The method of claim 3 or 4, wherein,
    The first DCI includes a fifth information field and a sixth information field;
    the fifth information field is used for indicating a first state index, the sixth information field is used for indicating that the first state index is a state index in a first SPS configuration state list, or the sixth information field is used for indicating that the first state index is a state index in a second SPS configuration state list;
    wherein, one state index in the first SPS configuration state list corresponds to one or more SPS configuration indexes associated with unicast service, one state index in the second SPS configuration state list corresponds to one or more SPS configuration indexes associated with MBS service, and the first state index corresponds to the M SPS configuration indexes.
  20. The method of claim 19, wherein,
    The first SPS configuration state list is agreed by a protocol, or the first SPS configuration state list is configured by a network device.
  21. The method of claim 19 or 20, wherein,
    The second SPS configuration state list is agreed by a protocol, or the second SPS configuration state list is configured by a network device.
  22. The method according to any one of claim 19 to 21,
    The fifth information field is an HPN information field in the first DCI.
  23. The method according to any one of claim 19 to 22,
    The sixth information field is a VRB-to-PRB mapping information field in the first DCI or the sixth information field is a redundancy version information field in the first DCI.
  24. The method of claim 3 or 4, wherein,
    The first DCI includes a seventh information field;
    wherein the seventh information field is configured to indicate a state index in a third SPS configuration state list;
    Wherein, one state index in the third SPS configuration state list corresponds to at least one SPS configuration index associated with a unicast service and/or at least one SPS configuration index associated with an MBS service, and the state index indicated by the seventh information field corresponds to the indexes of the M SPS configurations.
  25. The method of claim 24, wherein,
    SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, R is more than or equal to K and less than or equal to R+Q-1; wherein L and K are integers.
  26. The method of claim 24 or 25, wherein,
    The third SPS configuration state list is agreed by a protocol, or the third SPS configuration state list is configured by a network device.
  27. The method of any one of claim 24 to 26,
    The seventh information field is an HPN information field in the first DCI.
  28. The method of claim 1 or 2, wherein,
    The first DCI includes an eighth information field;
    Wherein the M SPS configurations include only a third SPS configuration, the eighth information field is used to indicate an index of the third SPS configuration among indexes of N SPS configurations, the N SPS configurations include N 1 SPS configurations associated with unicast service and N 2 SPS configurations associated with MBS service, the third SPS configuration is a SPS configuration associated with unicast service, or the third SPS configuration is a SPS configuration associated with MBS service;
    Wherein N, N 1,n 2 are both positive integers, and N 1+n 2 =n.
  29. The method of claim 28, wherein the indexes of the N SPS configurations are uniformly numbered.
  30. The method of claim 28 or 29, wherein,
    The indexes of the N SPS configurations and the corresponding SPS configuration types are agreed by a protocol, or the indexes of the N SPS configurations and the corresponding SPS configuration types are configured by network equipment.
  31. A method of wireless communication, comprising:
    The network equipment sends first downlink control information DCI;
    The first DCI is used to activate or deactivate M semi-persistent scheduling SPS configurations, where M is a positive integer;
    Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with multicast broadcast service MBS service.
  32. The method of claim 31, wherein a cyclic redundancy check, CRC, of the first DCI employs a pre-configured scheduling radio network temporary identity, CS-RNTI, scrambling.
  33. The method of claim 31 or 32, wherein,
    R SPS configurations are configured for unicast service and/or Q SPS configurations are configured for MBS service;
    Wherein R is more than or equal to 1 and less than or equal to R max,1≤Q≤Q max,R、Q、R max and Q max are positive integers.
  34. The method of claim 33, wherein,
    R max has one of the following values: 8. 16, 32; and/or, the value of Q max is one of the following: 8. 16, 32.
  35. The method of claim 33 or 34, wherein,
    The first DCI includes a first information field;
    Wherein the number of SPS configurations associated with MBS service in the M SPS configurations is 1, and the first information field is used to indicate SPS configuration indexes associated with MBS service in the M SPS configurations.
  36. The method of claim 35, wherein,
    Different status bits of the first information domain respectively correspond to SPS configuration indexes associated with different MBS services.
  37. The method of claim 36, wherein,
    The corresponding relation between the status bit of the first information domain and the SPS configuration index associated with the MBS service is agreed by a protocol, or the corresponding relation between the status bit of the first information domain and the SPS configuration index associated with the MBS service is configured by the network equipment.
  38. The method of any one of claim 35 to 37,
    The length of the first information domain is more than or equal to 3 bits, and the SPS configuration index of the MBS service association indicated by the first information domain is K; wherein K is an integer, and K is more than or equal to 0 and less than or equal to Q-1.
  39. The method of any one of claim 35 to 38, wherein,
    The first information field is an information field except for a hybrid automatic repeat request (HPN) information field in the first DCI, or the first information field is an information field in the first DCI dedicated to indicating an SPS configuration index associated with an MBS service.
  40. The method of claim 33 or 34, wherein,
    The first DCI comprises a second information domain and a third information domain;
    Wherein the M SPS configurations include only a first SPS configuration, the second information field is used to indicate an index of the first SPS configuration, the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with a unicast service, or the third information field is used to indicate that the first SPS configuration is an SPS configuration associated with an MBS service.
  41. The method of claim 40, wherein,
    Different status bits of the second information field correspond to different SPS configuration indexes, respectively.
  42. The method of claim 41, wherein,
    The corresponding relation between the status bit of the second information domain and the SPS configuration index is agreed by a protocol, or the corresponding relation between the status bit of the second information domain and the SPS configuration index is configured by the network equipment.
  43. The method of any one of claims 40 to 42,
    SPS configuration index associated with unicast service is L, L is more than or equal to 0 and less than or equal to R-1; and/or SPS configuration index related to MBS service is K, K is more than or equal to 0 and less than or equal to Q-1; wherein L and K are integers.
  44. The method of any one of claim 41 to 43,
    The second information field is an HPN information field in the first DCI.
  45. The method of any one of claim 41 to 44,
    The third information field is a virtual resource block VRB to physical resource block PRB mapping information field in the first DCI, or the third information field is a redundancy version information field in the first DCI.
  46. The method of claim 33 or 34, wherein,
    The first DCI includes a fourth information field;
    Wherein the M SPS configurations include only a second SPS configuration, the fourth information field is used to indicate an index of the second SPS configuration, and the fourth information field is used to indicate that the second SPS configuration is a unicast service associated SPS configuration, or the fourth information field is used to indicate that the second SPS configuration is an MBS service associated SPS configuration.
  47. The method of claim 46, wherein,
    SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, K is more than or equal to 0 and less than or equal to Q-1; or SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, R is more than or equal to K and less than or equal to R+Q-1; wherein L and K are integers;
    The 1 st to the R-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with unicast services, respectively, and the r+1st to the q+r-th status bits in the fourth information domain are used for indicating SPS configuration indexes associated with MBS services, respectively.
  48. The method of claim 46 or 47, wherein,
    The fourth information field is an HPN information field in the first DCI.
  49. The method of claim 33 or 34, wherein,
    The first DCI includes a fifth information field and a sixth information field;
    the fifth information field is used for indicating a first state index, the sixth information field is used for indicating that the first state index is a state index in a first SPS configuration state list, or the sixth information field is used for indicating that the first state index is a state index in a second SPS configuration state list;
    wherein, one state index in the first SPS configuration state list corresponds to one or more SPS configuration indexes associated with unicast service, one state index in the second SPS configuration state list corresponds to one or more SPS configuration indexes associated with MBS service, and the first state index corresponds to the M SPS configuration indexes.
  50. A method as in claim 49 wherein said first SPS configuration state list is agreed upon by a protocol or said first SPS configuration state list is configured by said network device.
  51. A method as in claim 49 or 50 wherein said second SPS configuration state list is agreed upon by a protocol or said second SPS configuration state list is configured by said network device.
  52. The method of any one of claims 49 to 51,
    The fifth information field is an HPN information field in the first DCI.
  53. The method of any one of claim 49 to 52,
    The sixth information field is a VRB-to-PRB mapping information field in the first DCI or the sixth information field is a redundancy version information field in the first DCI.
  54. The method of claim 33 or 34, wherein,
    The first DCI includes a seventh information field;
    wherein the seventh information field is configured to indicate a state index in a third SPS configuration state list;
    Wherein, one state index in the third SPS configuration state list corresponds to at least one SPS configuration index associated with a unicast service and/or at least one SPS configuration index associated with an MBS service, and the state index indicated by the seventh information field corresponds to the indexes of the M SPS configurations.
  55. The method of claim 54, wherein,
    SPS configuration index related to unicast service is L, L is more than or equal to 0 and less than or equal to R-1, SPS configuration index related to MBS service is K, R is more than or equal to K and less than or equal to R+Q-1; wherein L and K are integers.
  56. A method as in claim 54 or 55 wherein said third SPS configuration state list is agreed upon by a protocol or said third SPS configuration state list is configured by said network device.
  57. The method of any one of claims 54 to 56,
    The seventh information field is an HPN information field in the first DCI.
  58. The method of claim 31 or 32, wherein,
    The first DCI includes an eighth information field;
    Wherein the M SPS configurations include only a third SPS configuration, the eighth information field is used to indicate an index of the third SPS configuration among indexes of N SPS configurations, the N SPS configurations include N 1 SPS configurations associated with unicast service and N 2 SPS configurations associated with MBS service, the third SPS configuration is a SPS configuration associated with unicast service, or the third SPS configuration is a SPS configuration associated with MBS service;
    Wherein N, N 1,n 2 are both positive integers, and N 1+n 2 =n.
  59. A method as in claim 58 wherein the indexes of the N SPS configurations are uniformly numbered.
  60. The method of claim 58 or 59,
    The indexes of the N SPS configurations and the corresponding SPS configuration types are agreed by a protocol, or the indexes of the N SPS configurations and the corresponding SPS configuration types are configured by the network equipment.
  61. A terminal device, comprising:
    a communication unit, configured to receive first downlink control information DCI;
    The first DCI is used to activate or deactivate M semi-persistent scheduling SPS configurations, where M is a positive integer;
    Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with multicast broadcast service MBS service.
  62. A network device, comprising:
    a communication unit, configured to send first downlink control information DCI;
    The first DCI is used to activate or deactivate M semi-persistent scheduling SPS configurations, where M is a positive integer;
    Wherein the types of the M SPS configurations include at least one of: SPS configuration associated with unicast service, SPS configuration associated with multicast broadcast service MBS service.
  63. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to cause the terminal device to perform the method of any of claims 1 to 30.
  64. A network device, comprising: a processor and a memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to cause the network device to perform the method of any of claims 31 to 60.
  65. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 30.
  66. A chip, comprising: a processor for calling and running a computer program from memory, causing a device on which the chip is mounted to perform the method of any one of claims 31 to 60.
  67. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 30.
  68. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 31 to 60.
  69. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 30.
  70. A computer program product comprising computer program instructions which cause a computer to perform the method of any one of claims 31 to 60.
  71. A computer program, characterized in that the computer program causes a computer to perform the method of any one of claims 1 to 30.
  72. A computer program, characterized in that the computer program causes a computer to perform the method of any one of claims 31 to 60.
CN202280075165.8A 2022-02-18 2022-02-18 Wireless communication method, terminal equipment and network equipment Pending CN118251958A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/076880 WO2023155151A1 (en) 2022-02-18 2022-02-18 Wireless communication method, terminal device, and network device

Publications (1)

Publication Number Publication Date
CN118251958A true CN118251958A (en) 2024-06-25

Family

ID=87577405

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202280075165.8A Pending CN118251958A (en) 2022-02-18 2022-02-18 Wireless communication method, terminal equipment and network equipment

Country Status (2)

Country Link
CN (1) CN118251958A (en)
WO (1) WO2023155151A1 (en)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210243782A1 (en) * 2020-04-21 2021-08-05 Honglei Miao Methods of enhanced sps transmission and harq feedback
US20230299890A1 (en) * 2020-07-13 2023-09-21 Samsung Electronics Co., Ltd. Sps operation method and device for mbs reception
CN117295171A (en) * 2020-12-11 2023-12-26 Oppo广东移动通信有限公司 Semi-static scheduling method and device for MBS service, terminal and network equipment
US11974291B2 (en) * 2021-04-01 2024-04-30 Qualcomm Incorporated Activation and release for group-common downlink channels with repetitions

Also Published As

Publication number Publication date
WO2023155151A1 (en) 2023-08-24

Similar Documents

Publication Publication Date Title
CN114424626A (en) Resource indication method and device, and communication equipment
CN114600473A (en) Service synchronous scheduling method and device, and communication equipment
US20240049264A1 (en) Physical sidelink feedback channel (psfch) transmission method and terminal device
WO2022134076A1 (en) Wireless communication method and terminal device
CN113678500B (en) Feedback resource allocation method, communication method, device and communication equipment
WO2020063596A1 (en) Communication method and device
EP4243528A1 (en) Semi-persistent scheduling method and apparatus for mbs service, and terminal device and network device
WO2022021008A1 (en) Method for determining sidelink configured grant resource, and terminal device
CN113728683B (en) BWP configuration method and device, terminal equipment and network equipment
CN115243384B (en) Method, device, equipment and storage medium for solving business conflict
CN117121590A (en) Wireless communication method, terminal device and network device
CN111543113B (en) Method and device for data transmission
CN109831824B (en) Method, device and system for uplink piggyback transmission
CN114902758A (en) Resource configuration method and device, terminal equipment and network equipment
CN114070474A (en) Data transmission method and device
CN118251958A (en) Wireless communication method, terminal equipment and network equipment
EP4369645A1 (en) Wireless communication method, terminal device, and network device
WO2023279399A1 (en) Sidelink transmission resource determination method and sending method and apparatus, device, and medium
US20230361927A1 (en) Wireless communication method, terminal device and network device
WO2023050319A1 (en) Wireless communication method, terminal device and network device
WO2024031307A1 (en) Hybrid automatic repeat request (harq) feedback method and apparatus, and device and medium
WO2022126636A1 (en) Wireless communication method and terminal device
CN117941299A (en) Information determination method and device and terminal equipment
CN118056451A (en) Communication method, terminal device and network device
CN117063495A (en) Method and device for determining transmission mode, terminal equipment and network equipment

Legal Events

Date Code Title Description
PB01 Publication
SE01 Entry into force of request for substantive examination