Semi-persistent scheduling method in PTM mode in NR cell
By configuring core resources and time-frequency mapping for services under PTM mode in the NR cell, the gap in the lower semi-static scheduling transmission scheme of the PTM mode is solved, and the stable transmission of service data is achieved.
Patent Information
- Application Number
- CN202310532956.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-12
AI Technical Summary
In the new wireless access (NR) cell, a semi-static scheduling transmission scheme is lacking in the point-to-multipoint (PTM) mode, and services cannot be effectively transmitted.
In the NR cell, the base station (gNB) configures the mapping window list and SPS resource list of CORESET, CSS, PDCCH timing to SSB for services under PTM mode, selects the SPS resource and generates the activated SPS resource, and sends services periodically through this resource Data, the UE receives configuration information to receive service data.
It realizes the transmission of services in semi-static scheduling under PTM mode to ensure stable and efficient transmission of service data.
Smart Images

Figure CN118945838A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology and, in particular, to a semi-static scheduling method under a PTM mode in an NR cell. Background Art
[0002] In a new radio access (NR) cell, when a gNB transmits a unicast session to a user equipment (UE) in a point-to-point (PTP) manner, a semi-static scheduling method may be used.
[0003] Specifically, in the semi-persistent scheduling mode, the gNB allocates a configured scheduling-radio network temporary identifier (CS-RNTI) and at least one semi-persistent scheduling (SPS) resource to the UE, and sends the CS-RNTI and the configuration information of each SPS resource to the UE through dedicated signaling. When starting to transmit a unicast session, the gNB selects an SPS resource from all configured SPS resources, determines the time-frequency resources used when the selected SPS resource is used to send the unicast session, generates activated SPS resources, and selects a time slot for sending a physical downlink control channel (PDCCH) and a time slot for sending a physical downlink shared channel (PDSCH). The gNB sends a PDCCH scrambled with a CS-RNTI for a cyclic redundancy check (CRC) in the time slot for sending the PDCCH, and the DCI format on the PDCCH provides the configuration information of the activated SPS resources. Starting from the timeslot in which PDSCH is sent, the gNB periodically sends PDSCH through the activated SPS resources. PDSCH carries the data of the unicast session.
[0004] After receiving the CS-RNTI and configuration information of each SPS resource through dedicated signaling, the UE monitors the PDCCH whose CRC is scrambled with the CS-RNTI. When the corresponding PDCCH is monitored, the UE determines the activated SPS resource and the first time slot for sending PDSCH according to the DCI format on the PDCCH. Then, starting from the first time slot for sending PDSCH, the UE periodically receives the PDSCH sent by the gNB through the activated SPS resource to obtain the data of the unicast session.
[0005] In the NR cell, the gNB will also send a service to a group of UEs in Point to Multipoint (PTM) mode. There is no solution for how to transmit the service in a semi-static scheduling manner in PTM mode. Summary of the invention
[0006] An embodiment of the present application provides a semi-static scheduling method in a PTM mode in an NR cell, which is used to solve the problem of how to transmit services in a semi-static scheduling manner in a PTM mode.
[0007] In a first aspect, an embodiment of the present application provides a semi-static scheduling method in a PTM mode in an NR cell, including:
[0008] The gNB configures CORESET, CSS, PDCCH opportunity to SSB mapping window list and SPS resource list for services transmitted in PTM mode;
[0009] For a service transmitted in PTM mode, when the gNB schedules the service in semi-static scheduling, the gNB configures a G-CS-RNTI for the service, configures at least one SPS resource for the service from the SPS resource list, and specifies a PDCCH opportunity to SSB mapping window for the service from the PDCCH opportunity to SSB mapping window list;
[0010] The gNB configures activated SPS resources for the service;
[0011] The gNB sends target configuration information in the NR cell;
[0012] The gNB sends data of the service according to the configuration information of the service;
[0013] For the service, the UE receiving the service receives the target configuration information, obtains the configuration information of the service from the target configuration information, and receives the data of the service according to the configuration information of the service.
[0014] In a specific implementation manner, the gNB configures an activated SPS resource for the service, including:
[0015] When the gNB starts to transmit data of the service, the gNB selects an SPS resource from the SPS resources configured for the service, and determines the frequency domain resources, time domain resources, VRB to PRB mapping method and coding modulation method used when the SPS resource is used to send the service, to form an activated SPS resource, and determines the configuration information of the activated SPS resource;
[0016] Among them, the activated SPS resources are periodically appearing resources, and in each period the activated SPS resources are composed of S resource blocks, each resource block is composed of F consecutive downlink time slots, F is the aggregation factor contained in the configuration information of the activated SPS resources, S is the number of beams for sending SSB in the cell, and different resource blocks correspond to different beams; according to the configuration information of the activated SPS resources, the positions of the S resource blocks contained in the activated SPS resources in each period can be determined.
[0017] In a specific implementation manner, the gNB configures an activated SPS resource for the service, including:
[0018] In each cycle, the S resource blocks contained in the activated SPS resources correspond to the first beam to the Sth beam in chronological order; in each cycle, the S resource blocks contained in the activated SPS resources are composed of F*S consecutive downlink time slots.
[0019] In a specific implementation, if the gNB belongs to a 3GPP NR system, the gNB sends target configuration information in the NR cell, including:
[0020] The gNB sends, through SIB1 in the NR cell, configuration information of CORESET and CSS for multicast MCCH and configuration information of CORESET and CSS for multicast session configured in RRC inactive state;
[0021] The gNB sends the configuration information of the multicast MCCH through the multicast SIB in the NR cell;
[0022] The gNB sends configuration information of each RRC inactive multicast session through the multicast MCCH in the NR cell;
[0023] The gNB sends the configuration information of the multicast session to the UE receiving the multicast session through dedicated signaling in the NR cell;
[0024] For each RRC inactive multicast session using semi-static scheduling, the gNB activates the SPS resources of the multicast session through the PDCCH in the NR cell.
[0025] In a specific implementation manner, the configuration information of the multicast MCCH on the multicast SIB includes:
[0026] CFR configuration information; CORESET and CSS configuration information; at least one set of modification period and repetition period configuration information;
[0027] The CFR configuration information is used to configure the CFR for sending multicast MCCH and multicast session in RRC inactive state;
[0028] The CORESET and CSS configuration information is used to configure the CORESET and the CSS, and the CORESET and the CSS are used to send scheduling information of a multicast MCCH and a multicast session in an RRC inactive state;
[0029] The configuration information of each group of modification period and repetition period includes: repetition period and offset, starting time slot position, transmission window length and modification period.
[0030] In a specific implementation manner, the multicast MCCH includes:
[0031] A mapping window list of PDCCH timing to SSB, an SPS resource list, a PDSCH parameter list, a DRX parameter list, a neighbor cell list, and configuration information of each multicast session; the neighbor cell list is used to indicate each neighbor cell of the NR cell, the number of neighbor cells is L, and the neighbor cell list contains L groups of parameters, each group of parameters corresponds to a neighbor cell.
[0032] In a specific implementation, for a multicast session using semi-static scheduling, the configuration information of the multicast session includes:
[0033] TMGI, G-CS-RNTI, PDCCH opportunity to SSB mapping window configuration information, DRX parameter configuration information, PDSCH parameter configuration information, each SPS resource configuration information, activated semi-static PTM resource configuration information, multicast session high-level configuration information, length L bitmap, length L1 bitmap;
[0034] The configuration information of the PDCCH opportunity to SSB mapping window consists of the subscript of the PDCCH opportunity to SSB mapping window specified for the multicast session;
[0035] The configuration information of the DRX parameters consists of a set of subscripts of DRX parameters specified for the multicast session from a DRX parameter list;
[0036] The configuration information of the PDSCH parameters consists of subscripts of a set of PDSCH parameters specified for the multicast session from a PDSCH parameter list;
[0037] The configuration information of each SPS resource consists of the subscripts of each SPS resource allocated to the multicast session;
[0038] The configuration information of the activated semi-static PTM resources includes the positions of S resource blocks in each period and the beam used by each resource block;
[0039] The high-level configuration information of the multicast session consists of an MRB list of the multicast session, wherein the MRB list includes PDCP configuration information and RLC configuration information of each MRB of the multicast session;
[0040] The bit map of length L is used to indicate whether each neighboring cell provides the multicast session, each bit corresponds to a neighboring cell, and when one bit is 0 / 1, it indicates that the neighboring cell corresponding to the bit does not provide / provides the multicast session;
[0041] The bit map of length L1 is used to indicate whether the configuration information of the multicast session in each neighboring cell providing the multicast session is the same as that of the current NR cell. Each bit corresponds to a neighboring cell providing the multicast session. When one bit is 0 / 1, it indicates that the configuration information of the multicast session in the neighboring cell corresponding to the bit is different from / the same as that of the current NR cell.
[0042] In a specific implementation, if the gNB belongs to a B-TRUNC 5G system, the gNB sends target configuration information in the NR cell, including:
[0043] The gNB sends the CORESET and CSS configuration information of the cluster service configuration of the group through SIB1 in the NR cell;
[0044] The gNB sends a cluster-specific SIB in the NR cell;
[0045] The gNB sends TCCH configuration information of each group through cluster paging in the NR cell;
[0046] When the cluster service of a group adopts the semi-static scheduling mode, the gNB activates the SPS resources of the cluster service of the group through the PDCCH in the NR cell. To support the UE entering later, the gNB periodically sends the PDCCH to activate the SPS resources of the cluster service of the group;
[0047] The gNB sends configuration information of each cluster service of the group on the TCCH of each group.
[0048] In a specific implementation, the cluster-specific SIB includes:
[0049] Configuration information of CORESET and CSS, mapping window list of PDCCH opportunity to SSB, SPS resource list, PDSCH parameter list; the configuration information of CORESET and CSS is used to configure CORESET and CSS, and the CORESET and CSS are used to send scheduling information of cluster services of the group.
[0050] In a specific implementation, when the gNB adopts semi-static scheduling for a cluster service of a group, the TCCH configuration information of the group includes:
[0051] The group ID, G-CS-RNTI, configuration information of the PDCCH opportunity to SSB mapping window, configuration information of each SPS resource, configuration information of PDSCH parameters, and high-level configuration information of the TCCH of the group;
[0052] The configuration information of each SPS resource consists of the subscripts of each SPS resource allocated to the group;
[0053] The configuration information of the PDSCH parameters consists of a set of subscripts of PDSCH parameters assigned to the group from the PDSCH parameter list;
[0054] The high-level configuration information of the TCCH of the group includes: PDCP configuration information of the TCCH and RLC configuration information of the TCCH.
[0055] In a specific implementation, when the gNB adopts semi-static scheduling for a cluster service of a group, the configuration information on the TCCH of the group includes:
[0056] Configuration information of activated SPS resources configured for the cluster service of the group, high-level configuration information of each cluster service of the group, a bit map of length L, and a bit map of length L1; the high-level configuration information of each cluster service includes: PDCP layer configuration information and RLC layer configuration information.
[0057] In a specific implementation manner, the gNB activates the SPS resources of the service through the PDCCH, including:
[0058] When the gNB configures a mapping window of the PDCCH opportunity to the SSB for the service, the gNB determines the beam corresponding to each PDCCH opportunity in the CSS of the service according to the mapping window of the PDCCH opportunity to the SSB of the service;
[0059] The gNB selects S PDCCH opportunities in the CSS of the service, the S PDCCH opportunities respectively corresponding to S different beams, sends a PDCCH scrambled by CRC using G-CS-RNTI in the S PDCCH opportunities, the PDCCH sent in each PDCCH opportunity uses a corresponding beam, and the DCI format on the PDCCH sent in each PDCCH opportunity is used to activate the SPS resources configured for the service in the corresponding beam direction;
[0060] When the gNB does not configure a mapping window from a PDCCH opportunity to an SSB for the service; the gNB selects S PDCCH opportunities in the CSS of the service, and determines the beam used when sending the PDCCH in each PDCCH opportunity, and the beams used by the PDCCH in different PDCCH opportunities are different, and the gNB sends the PDCCH scrambled by the CRC using the G-CS-RNTI through the corresponding beam in each selected PDCCH opportunity;
[0061] For the PDCCH sent in each PDCCH opportunity, the gNB determines the position of the first time slot for sending the PDSCH according to the timing difference between the PDCCH and the PDSCH provided in the DCI format on the PDCCH, and the consecutive F downlink time slots starting from the first time slot are the resource blocks allocated to the PDCCH. The gNB periodically sends the PDSCH through the resource blocks. In each period, the gNB sends the PDSCH in each downlink time slot in the resource block. The PDSCH uses G-CS-RNTI for bit scrambling. The same TB of the service is carried on the PDSCH, and the beam used by the PDCCH is used when sending the PDSCH.
[0062] In a specific implementation manner, the gNB activates the SPS resources of the service through the PDCCH, including:
[0063] The S PDCCH opportunities correspond to the first beam to the Sth beam respectively in chronological order, and the S resource blocks allocated by the S PDCCH opportunities in each cycle correspond to the first beam to the Sth beam respectively in chronological order; the S resource blocks allocated by the S PDCCH opportunities are connected end to end, and in each cycle, the S resource blocks allocated by the S PDCCH opportunities are composed of consecutive F*S downlink time slots, and in each cycle, the gNB sends the same TB of the service through the S resource blocks, and sends the same TB of the service consecutively F times in each beam direction.
[0064] In a specific implementation manner, the gNB sends data of the service according to the configuration information of the service, including:
[0065] When the service adopts a semi-static scheduling method, the gNB periodically sends data of the service through the activated SPS resources configured for the service.
[0066] In a specific implementation manner, the gNB sends data of the service according to the configuration information of the service, including:
[0067] When the TB length of the service is greater than the TB length that can be transmitted by the activated SPS resources of the service, the gNB transmits data of the service in a dynamic scheduling manner;
[0068] The gNB transmits data of the service in a dynamic scheduling manner, including:
[0069] When the gNB configures a mapping window from a PDCCH opportunity to an SSB for the service, the gNB selects S PDCCH opportunities in the CSS of the service, and the S PDCCH opportunities correspond to S different beams respectively; when the gNB does not configure a mapping window from a PDCCH opportunity to an SSB for the service, the gNB selects S PDCCH opportunities in the CSS of the service, and determines the beam used when sending the PDCCH in each PDCCH opportunity, and different PDCCH opportunities use different beams;
[0070] The gNB allocates PDSCH resources for each PDCCH opportunity for transmitting data of the service, sends a PDCCH scrambled by G-CS-RNTI for CRC in each PDCCH opportunity, the DCI format on the PDCCH is the dynamic scheduling information of the PDSCH resources allocated to the PDCCH opportunity, and uses the corresponding beam when sending the PDCCH in each PDCCH opportunity;
[0071] For the PDCCH sent in each PDCCH opportunity, when the configuration information of the PDSCH parameters in the configuration information of the multicast session includes the aggregation factor F1, the gNB determines the first time slot for sending the PDSCH according to the timing difference between the PDCCH and the PDSCH provided by the DCI format on the PDCCH, and starting from the time slot, the gNB occupies F1 consecutive downlink time slots to send the PDSCH. The PDSCH sent in each time slot carries the TB of the service. The beam used when sending the PDSCH is the beam used by the PDCCH, and the PDSCH uses G-CS-RNTI for bit scrambling.
[0072] In a specific implementation manner, the gNB sends data of the service according to the configuration information of the service, including:
[0073] The gNB retransmits the service through PTM. When the gNB decides to retransmit a TB of the service, the gNB retransmits the TB in a dynamic scheduling manner in each beam direction, or retransmits the TB in a dynamic scheduling manner only in several beam directions.
[0074] In a specific implementation, for the service, the UE receiving the service receives the target configuration information, obtains the configuration information of the service from the target configuration information, and receives data of the service according to the configuration information of the service, including:
[0075] In a 3GPP NR system, the service is a multicast session in an RRC inactive state, and a UE receiving the multicast session receives the target configuration information sent by the gNB, obtains the configuration information of the multicast session from the target configuration information, and receives data of the multicast session according to the configuration information of the multicast session;
[0076] The obtaining the configuration information of the multicast session from the target configuration information, and receiving the data of the multicast session according to the configuration information of the multicast session, comprises:
[0077] When the multicast session adopts the semi-persistent scheduling mode, the UE may obtain the configuration information of the activated SPS resources configured by the gNB for the multicast session from the DCI format on the PDCCH scrambled by the multicast MCCH or CRC with the G-CS-RNTI, and the UE periodically receives the data of the multicast session according to the configuration information of the activated SPS resources;
[0078] Alternatively, the UE obtains the dynamic scheduling information of the multicast session from the DCI format on the PDCCH in which the CRC is scrambled with the G-CS-RNTI, and receives the data of the multicast session according to the dynamic scheduling information of the multicast session.
[0079] In a specific implementation, for the service, the UE receiving the service receives target configuration information, obtains configuration information of the service from the target configuration information, and receives data of the service according to the configuration information of the service, including:
[0080] In the B-TRUNCH 5G system, the service is a trunk service of a group. A UE receiving the trunk service of the group receives the target configuration information sent by the gNB, obtains the configuration information of the TCCH of the group from the target configuration information, and when the trunk service of the group adopts a semi-static scheduling mode, the UE monitors the PDCCH scrambled by the CRC using the G-CS-RNTI in the CSS configured for the trunk service of the group according to the G-CS-RNTI in the configuration information of the TCCH of the group.
[0081] The UE obtains configuration information of activated SPS resources of the cluster service of the group from the TCCH or from the DCI format on the PDCCH scrambled by the G-CS-RNTI; the UE periodically receives data of the cluster service of the group according to the configuration information of the activated SPS resources of the cluster service of the group;
[0082] Alternatively, the UE obtains the dynamic scheduling information of the cluster service of the group from the DCI format on the PDCCH in which the CRC is scrambled with the G-CS-RNTI, and receives the data of the cluster service of the group according to the dynamic scheduling information of the cluster service of the group.
[0083] In a specific implementation, the gNB sending the target configuration information in the NR cell includes: the gNB sending the multicast MCCH in the NR cell;
[0084] For the service, a UE receiving the service receives the target configuration information, including: the UE receives the multicast MCCH;
[0085] The gNB sending the multicast MCCH in the NR cell includes:
[0086] In a transmission window of each repetition period in each modification period of the multicast MCCH, the gNB sends a PDCCH of the multicast MCCH, and sends a corresponding PDSCH according to the PDCCH of the multicast MCCH;
[0087] The UE receiving the multicast MCCH includes:
[0088] The UE monitors the PDCCH scrambled by the CRC using the MMCCH-RNTI in the CSS of the multicast MCCH;
[0089] When the UE monitors the PDCCH whose CRC is scrambled with MMCCH-RNTI, the UE determines whether it needs to receive the PDSCH of the multicast MCCH scheduled by the PDCCH according to the MCCH change notification field provided by the DCI format on the PDCCH;
[0090] When it is necessary to receive the PDSCH of the multicast MCCH, the UE receives the PDSCH of the multicast MCCH according to the scheduling information provided in the DCI format on the PDCCH.
[0091] The embodiment of the present application provides a semi-static scheduling method under the PTM mode in the NR cell. For a service adopting the semi-static scheduling mode, the gNB configures a PDCCH opportunity to SSB mapping window and several SPS resources for the service; the gNB selects an SPS resource and generates an activated SPS resource from the selected SPS resource; the gNB sends the configuration information of the activated SPS resource of the service, and periodically sends the data of the service through the activated SPS resource of the service; the UE receives the configuration information of the service and periodically receives the data of the service sent by the gNB according to the configuration information of the service, thereby realizing the transmission of the service in a semi-static scheduling manner under the PTM mode. BRIEF DESCRIPTION OF THE DRAWINGS
[0092] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0093] Figure 1 Schematic diagram of the process of the semi-static scheduling method under the PTM mode in the NR cell provided by this application Figure 1 ;
[0094] Figure 2 Schematic diagram of the process of the semi-static scheduling method under the PTM mode in the NR cell provided by this application Figure 2 . DETAILED DESCRIPTION
[0095] In a new radio access (NR) cell, when a gNB transmits a unicast session to a user equipment (UE) in a point-to-point (PTP) manner, a semi-static scheduling method may be used.
[0096] Specifically, in the semi-persistent scheduling mode, the gNB allocates a configured scheduling-radio network temporary identifier (CS-RNTI) and at least one semi-persistent scheduling (Semi-Persistent Scheduling) resource to the UE, and sends the CS-RNTI and the configuration information of each SPS resource to the UE through dedicated signaling. When starting to transmit a unicast session, the gNB selects an SPS resource from all configured SPS resources, determines the time-frequency resources used when using the selected SPS resource to send the unicast session, generates activated SPS resources, and selects a time slot for sending a physical downlink control channel (PDCCH) and a time slot for sending a PDSCH. The gNB sends a PDCCH scrambled with a CS-RNTI for cyclic redundancy check (CRC) in the time slot for sending PDCCH, and the DCI format on the PDCCH provides the configuration information of the activated SPS resources. Starting from the timeslot in which PDSCH is sent, the gNB periodically sends PDSCH through the activated SPS resources. PDSCH carries the data of the unicast session.
[0097] After receiving the CS-RNTI and the configuration information of each SPS resource through dedicated signaling, the UE monitors the PDCCH with CS-RNTI scrambled by CRC. When monitoring the corresponding PDCCH, the UE determines the activated SPS resource and the first time slot to send PDSCH according to the DCI format on the PDCCH. Then, the UE periodically receives the PDSCH sent by the gNB through the activated SPS resource starting from the first time slot to send PDSCH to obtain the data of the unicast session. During the transmission interval of the unicast session, the gNB can deactivate the activated SPS resource through the PDCCH scrambled by CS-RNTI scrambled by CRC. When the unicast session resumes transmission, the gNB reselects an SPS resource, regenerates an activated SPS resource, and then activates the new SPS resource through the PDCCH scrambled by CS-RNTI scrambled by CRC, and continues to transmit the data of the unicast session through the newly activated SPS resource.
[0098] In the NR cell, the gNB will also send a service to a group of UEs in a point-to-multipoint (PTM) mode. There is no solution for how to transmit the service in a semi-static scheduling manner in the PTM mode. Therefore, a method is urgently needed to realize the transmission of the service in a semi-static scheduling manner in the PTM mode.
[0099] In view of the problems existing in the prior art, the inventor proposes a semi-static scheduling method under the PTM mode in the NR cell. The method of the present application is described in detail below through specific embodiments.
[0100] Figure 1 Schematic diagram of the process of the semi-static scheduling method under the PTM mode in the NR cell provided by this application Figure 1 ,like Figure 1 As shown, the semi-static scheduling method under the PTM mode in the NR cell specifically includes the following steps:
[0101] S101: gNB configures CORESET, CSS, PDCCH opportunity to SSB mapping window list and SPS resource list for the service transmitted in PTM mode.
[0102] In this step, the gNB configures a control resource set (CORESET) and a common search space (CSS) for the service transmitted in PTM mode. The CORESET and CSS are used to send the PDCCH of the service transmitted in PTM mode. The DCI format on the PDCCH is the scheduling information of the service.
[0103] In this step, the gNB configures a PDCCH opportunity to SSB mapping window list for the service transmitted in PTM transmission mode.
[0104] The PDCCH opportunity to SSB mapping window list is composed of configuration information of several PDCCH opportunity to SSB mapping windows. One PDCCH opportunity to SSB mapping window can be uniquely determined by one PDCCH opportunity to SSB mapping window configuration information.
[0105] The configuration information of a mapping window from a PDCCH opportunity to an SSB includes the period of the mapping window and the radio frame offset. The period and offset of the mapping window are used to determine the starting position of the mapping window in each period. The transmitted SSBs are numbered from 1 to S according to the order of the SSB subscript from small to large. The SSBs are numbered from 1 to S. S is the number of SSBs transmitted in the cell. The sth SSB uses the sth beam when it is transmitted. The S beams that transmit S SSBs cover the entire cell. In each period, the PDCCH opportunities in the mapping window are numbered from 1 in time order starting from the starting position of the mapping window. The x*S+Kth PDCCH opportunity corresponds to the Kth transmitted SSB. The PDCCH transmitted in this opportunity uses the Kth beam. K=1,…,S, x=1,…,CEIL[X / S], X is the number of PDCCH opportunities in the mapping window, and CEIL[X / S] means rounding up X / S.
[0106] In this step, the gNB configures an SPS resource list for the service transmitted in PTM mode.
[0107] The SPS resource list is composed of configuration information of several SPS resources, and one SPS resource can be uniquely identified by the configuration information of one SPS resource.
[0108] It should be noted that for the configuration information of a PDCCH opportunity to SSB mapping window, refer to the configuration information of the PDCCH opportunity to SSB mapping window of the broadcast session in the 3GPP TS38.331 protocol. For the configuration information of a semi-static PDSCH resource, refer to the configuration information of the semi-static PDSCH resource in the 3GPP TS38.331 protocol.
[0109] It should be noted that in the 3GPP NR system, the service transmitted in PTM mode is a multicast session in RRC inactive state. A multicast session in RRC inactive state refers to a multicast session that the UE can receive in RRC inactive state. Accordingly, the gNB configures CORESET, CSS, PDCCH timing to SSB mapping window list and SPS resource list for the multicast session in RRC inactive state; in the B-TRUNC 5G system, the service transmitted in PTM mode is the cluster service of the group. Accordingly, the gNB configures CORESET, CSS, PDCCH timing to SSB mapping window list and SPS resource list for the cluster service of the group.
[0110] S102: For a service transmitted in PTM mode, when the gNB schedules the service in semi-static scheduling, the gNB configures a G-CS-RNTI for the service, configures at least one SPS resource for the service from the SPS resource list, and specifies a PDCCH opportunity to SSB mapping window for the service from the PDCCH opportunity to SSB mapping window list.
[0111] S103: gNB configures activated SPS resources for the service.
[0112] When the gNB starts to transmit service data, the gNB selects an SPS resource from the SPS resources configured for the service, and determines the frequency domain resources, time domain resources, VRB to PRB mapping method and coding modulation method used when the selected SPS resource is used to send the service, forms an activated SPS resource, and determines the configuration information of the activated SPS resource.
[0113] The activated SPS resources are periodically appearing resources. The SPS resources activated in each period consist of S resource blocks, each resource block consists of F consecutive downlink time slots, F is the aggregation factor contained in the configuration information of the activated SPS resources, S is the number of beams for sending SSBs in the cell, and different resource blocks correspond to different beams. The positions of the S resource blocks contained in the SPS resources activated in each period can be determined according to the configuration information of the activated SPS resources.
[0114] Preferably, the S resource blocks included in the SPS resources activated in each cycle correspond to the first beam to the Sth beam in time sequence. Preferably, in each cycle, the S resource blocks included in the SPS resources activated are composed of F*S consecutive downlink time slots.
[0115] S104: The gNB sends target configuration information in the NR cell.
[0116] In a specific implementation, in a 3GPP NR system, when the gNB supports a multicast session in which the radio resource control (RRC) is not activated, the gNB configures a multicast SIB and a multicast MCCH in the cell. The multicast SIB carries the configuration information of the multicast MCCH, and the multicast MCCH carries the configuration information of each multicast session in which the RRC is not activated in the cell. The CORESET / CSS used by the multicast MCCH may be the same as or different from the CORESET / CSS configured for the service in step S101.
[0117] In the 3GPP NR system, the target configuration information includes: the configuration information of the CORESET and CSS of the multicast MCCH, the configuration information of the CORESET and CSS configured for the RRC inactive multicast session, the configuration information of the multicast MCCH, and the configuration information of each RRC inactive multicast session.
[0118] The target configuration information sent by the gNB in the NR cell includes:
[0119] The gNB sends through SIB1 in the NR cell: the configuration information of CORESET and CSS for multicast MCCH, and the configuration information of CORESET and CSS for multicast sessions in RRC inactive state.
[0120] The gNB sends the configuration information of multicast MCCH through the multicast SIB in the NR cell.
[0121] The gNB sends the configuration information of each RRC inactive multicast session via the multicast MCCH in the NR cell.
[0122] The gNB sends the configuration information of the RRC inactive multicast session to the UE receiving the multicast session through dedicated signaling in the NR cell.
[0123] For each RRC inactive multicast session using semi-persistent scheduling, the gNB activates the SPS resources of the multicast session through PDCCH in the NR cell. Preferably, when the activated SPS resources are configured for the multicast session for the first time or when the activated SPS resources are configured for the multicast session for the first time after the transmission interval of the multicast session, the gNB notifies the UE receiving the multicast session of the activated SPS resources configured for the multicast session through PDCCH.
[0124] Specifically, for a multicast session using semi-persistent scheduling, the process by which the gNB activates the SPS resources of the multicast session through the PDCCH in the NR cell is as follows:
[0125] When the gNB configures a PDCCH opportunity to SSB mapping window for a service, the gNB determines the beam corresponding to each PDCCH opportunity in the CSS of the service according to the mapping window of the PDCCH opportunity to SSB of the service. The gNB selects S PDCCH opportunities in the CSS of the service, and the S PDCCH opportunities correspond to S different beams respectively. The PDCCH scrambled with CRC using G-CS-RNTI is sent in these PDCCH opportunities. The PDCCH sent in each PDCCH opportunity uses the corresponding beam. The DCI format on the PDCCH sent in each PDCCH opportunity is used to activate the SPS resources configured for the service in the corresponding beam direction.
[0126] When the gNB does not configure a PDCCH opportunity to SSB mapping window for the service, there is no fixed correspondence between each PDCCH opportunity and beam in the CSS of the service. The gNB selects S PDCCH opportunities in the CSS of the service and determines the beam to be used when sending PDCCH in each PDCCH opportunity. The beams used by PDCCH in different PDCCH opportunities are different. The gNB sends PDCCH scrambled with CRC using G-CS-RNTI through the corresponding beam in each selected PDCCH opportunity.
[0127] For the PDCCH sent in each PDCCH opportunity, the gNB determines the position of the first time slot for sending PDSCH according to the timing difference between PDCCH and PDSCH provided in the DCI format on the PDCCH. The consecutive F downlink time slots starting from the first time slot are the resource blocks allocated by PDCCH. The gNB periodically sends PDSCH through the resource block. In each period, the gNB sends PDSCH in each downlink time slot in the resource block. PDSCH uses G-CS-RNTI for bit scrambling. The same TB that carries the service on PDSCH uses the beam used by PDCCH when sending PDSCH.
[0128] Preferably, the S PDCCH opportunities correspond to the first beam to the Sth beam in time sequence, and accordingly, the S resource blocks allocated by the S PDCCH opportunities in each cycle correspond to the first beam to the Sth beam in time sequence. Preferably, the S resource blocks allocated by the S PDCCH opportunities can be connected end to end. In each cycle, the S resource blocks allocated by the S PDCCH opportunities are composed of consecutive F*S downlink time slots. In each cycle, the gNB sends the same TB of the service through the S resource blocks, and sends the same TB of the service F times in succession in each beam direction.
[0129] The configuration information of multicast MCCH on the multicast SIB includes:
[0130] (1) Multicast Common Frequency Resource (CFR) configuration information: used to configure the CFR for sending multicast MCCH and multicast sessions in RRC inactive state.
[0131] CFR can be CORESET0, or the initial downlink (DL) bandwidth part (Bandwidth Part, BWP), or include the initial DL BWP. When CFR includes the initial DL BWP, CFR configuration information is provided in the multicast SIB, and the starting position of CFR and the number of occupied physical resource blocks (PRBs) are provided in the CFR configuration information; when CFR is the initial DL BWP, CFR configuration information is provided in the multicast SIB, and a flag is used in the CFR configuration information to indicate that CFR is the initial DL BWP; when CFR is CORESET 0, CFR configuration information is not provided in the multicast SIB.
[0132] The CFR configuration information provides PDSCH parameters, which are used to send the PDSCH of the multicast MCCH. If the PDSCH parameters are not provided, the PDSCH of the multicast MCCH uses the PDSCH parameters configured on SIB1 when sending. The PDSCH parameters consist of parameters used in various processes performed by the PDSCH of the multicast MCCH in the physical layer.
[0133] (2) CORESET and CSS configuration information: used to configure CORESET and CSS. CORESET and CSS are used to send multicast MCCH and scheduling information of multicast sessions in RRC inactive state.
[0134] (3) At least one set of configuration information for a modification period and a repetition period.
[0135] A set of configuration information of modification period and repetition period includes: repetition period and offset, starting time slot position, transmission window length and modification period.
[0136] Optionally, a group of modification period and repetition period is configured for the multicast MCCH; Optionally, two groups of modification period and repetition period are configured for the multicast MCCH. When two groups of modification period and repetition period are configured, one group is a short modification period and a short repetition period, and the other group is a long modification period and a long repetition period.
[0137] Tm and Tr are used to represent the short modification period and the short repetition period respectively, then the long modification period TmL and the long repetition period TrL are respectively: TmL = Tm*2 m1 , TrL=Tr*2 m2 , m1>0 and m2>0.
[0138] Whenever sending a multicast MCCH, the gNB needs to select one modification period and repetition period from the two groups of modification periods and repetition periods for sending the multicast MCCH. During the process of sending the multicast MCCH, the gNB can flexibly switch between the two groups of modification periods and repetition periods as needed.
[0139] In the transmission window of each repetition period in each modification period of the multicast MCCH, the mapping relationship between the PDCCH opportunity and the SSB beam is the same as the mapping relationship between the PDCCH opportunity and the SSB beam in the transmission window of the MCCH of the broadcast session.
[0140] The following information is provided on the multicast MCCH:
[0141] (1) PDCCH opportunity to SSB mapping window list: A PDCCH opportunity to SSB mapping window is assigned to a multicast session from this list.
[0142] (2) SPS resource list: At least one SPS resource is allocated from this list to a multicast session using semi-persistent scheduling. For the configuration information of each SPS resource, refer to "SPS-Config" in the 3GPP TS38.331 protocol.
[0143] (3) PDSCH parameter list: A set of PDSCH parameters is allocated to the multicast session from multiple sets of PDSCH parameters contained in the list, and is used to send the PDSCH of the multicast session.
[0144] (4) Discontinuous Reception (DRX) parameter list: A set of DRX parameters is allocated to the multicast session from multiple sets of DRX parameters contained in the list. The gNB dynamically schedules the multicast session according to the set of DRX parameters, and the UE monitors the multicast session according to the set of DRX parameters.
[0145] (5) Neighbor cell list: indicates each neighbor cell of the NR cell. The number of neighbor cells is L. The list contains L groups of parameters, each group of parameters corresponds to a neighbor cell.
[0146] (6) Configuration information of each multicast session.
[0147] For a multicast session using semi-persistent scheduling, the configuration information of the multicast session includes:
[0148] 1) Temporary Mobile Group Identity (TMGI) of the multicast session.
[0149] 2)G-CS-RNTI.
[0150] 3) Configuration information of the PDCCH opportunity to SSB mapping window: It consists of the subscript of the PDCCH opportunity to SSB mapping window specified for the multicast session.
[0151] 4) DRX parameter configuration information: consists of a set of DRX parameter subscripts specified for the multicast session from the DRX parameter list.
[0152] 5) PDSCH parameter configuration information: consists of a set of PDSCH parameter subscripts specified for the multicast session from the PDSCH parameter list.
[0153] 6) Configuration information of each SPS resource: It consists of the index of each SPS resource allocated to the multicast session.
[0154] 7) Configuration information of activated semi-static PTM resources: the positions of S resource blocks in each cycle, and the beam used by each resource block. Preferably, the S resource blocks correspond to the first beam to the Sth beam in chronological order, and the S resource blocks are connected end to end.
[0155] 8) High-level configuration information of multicast session: It consists of the multicast radio bearer (MRB) list of the multicast session. The MRB list provides the packet data convergence protocol (PDCP) configuration information and radio link control (RLC) configuration information of each MRB of the multicast session. The information provided by the MRB list of the multicast session is the same as the information provided by the MRB list of the broadcast session in the 3GPP TS38.331 protocol.
[0156] The Service Data Adaptation Protocol (SDAP) entity at the sending end maps each QOS flow of the multicast session to an MRB, and the SDAP protocol data unit (PDU) on each MRB does not contain the SDAP header. The SDAP entity at the receiving end does not need to know the ID of the MRB corresponding to each QOS flow, and directly uploads the SDAP PDU from each MRB.
[0157] 9) Bit mapping of length L: used to indicate whether each neighboring cell provides multicast sessions. Each bit corresponds to a neighboring cell. When a bit is 0 / 1, it indicates that the neighboring cell corresponding to the bit does not provide / provides multicast sessions. The number of neighboring cells that provide multicast sessions is L1.
[0158] 10) Bit mapping of length L1: used to indicate whether the configuration information of the multicast session in each neighboring cell providing the multicast session is the same as that of the current NR cell. Each bit corresponds to a neighboring cell providing the multicast session. When a bit is 0 / 1, it indicates that the configuration information of the multicast session in the neighboring cell corresponding to the bit is different from / the same as that of the current NR cell.
[0159] For a multicast session using dynamic scheduling, the configuration information of the multicast session includes:
[0160] 1) TMGI of the multicast session.
[0161] 2)G-RNTI.
[0162] 3) Configuration information of the PDCCH opportunity to SSB mapping window: It consists of the subscript of the PDCCH opportunity to SSB mapping window specified for the multicast session.
[0163] 4) DRX parameter configuration information: consists of a set of DRX parameter subscripts specified for the multicast session from the DRX parameter list.
[0164] 5) PDSCH parameter configuration information: consists of a set of PDSCH parameter subscripts specified for the multicast session from the PDSCH parameter list.
[0165] 6) High-level configuration information of the multicast session: It consists of the MRB list of the multicast session. The MRB list gives the PDCP configuration information and RLC configuration information of each MRB of the multicast session.
[0166] 7) A bitmap of length L.
[0167] 8) A bitmap of length L1.
[0168] In another specific implementation, in the B-TRUNC 5G system, the gNB configures a trunking-specific SIB in the cell, sends the trunking control channel (TCCH) configuration information of each group through trunking paging, and sends the configuration information of each trunking service of the group on the TCCH of each group. Each group has one or more trunking services.
[0169] The target configuration information includes: the configuration information of CORESET and CSS for cluster services of the group, the information provided on the cluster-specific SIB, the TCCH configuration information of each group, and the configuration information of cluster services of each group.
[0170] The target configuration information sent by the gNB in the NR cell includes:
[0171] The gNB sends the configuration information of CORESET and CSS of the cluster service configuration of the group through SIB1 in the NR cell.
[0172] The gNB sends cluster-specific SIBs within the NR cell.
[0173] The gNB sends the TCCH configuration information of each group through cluster paging in the NR cell.
[0174] When a group's cluster service adopts semi-static scheduling, the gNB activates the SPS resources of the group's cluster service through PDCCH in the NR cell. To support late-entering UEs, the gNB periodically sends PDCCH to activate the SPS resources of the group's cluster service.
[0175] The gNB sends the configuration information of each cluster service of each group on the TCCH of the group.
[0176] The cluster-specific SIB provides the following information:
[0177] (1) Configuration information of CORESET and CSS: used to configure CORESET and CSS, which are used to send scheduling information of cluster services of the group.
[0178] (2) Mapping window list from PDCCH opportunity to SSB.
[0179] (3) List of SPS resources.
[0180] (4)PDSCH parameter list.
[0181] When the gNB adopts semi-static scheduling for the trunking service of a group, the TCCH configuration information of the group includes the following information:
[0182] (1) Group ID.
[0183] (2)G-CS-RNTI.
[0184] (3) Configuration information of the mapping window from PDCCH opportunity to SSB.
[0185] (4) Configuration information of each SPS resource: It consists of the subscripts of each SPS resource allocated to the group.
[0186] (5) PDSCH parameter configuration information: consists of a set of PDSCH parameter subscripts assigned to the group from the PDSCH parameter list.
[0187] (6) High-level configuration information of the TCCH of the group: PDCP configuration information of the TCCH and RLC configuration information of the TCCH.
[0188] When the gNB uses dynamic scheduling for the trunking services of a group, the TCCH configuration information of the group includes the following information:
[0189] (1) Group ID.
[0190] (2)G-RNTI.
[0191] (3) Configuration information of the mapping window from PDCCH opportunity to SSB.
[0192] (4) Configuration information of PDSCH parameters.
[0193] (5) High-level configuration information of the group's TCCH.
[0194] When the gNB adopts semi-persistent scheduling for the trunking service of a group, the gNB sends the following information on the TCCH of the group:
[0195] (1) Configuration information of activated SPS resources configured for the cluster service of the group.
[0196] (2) High-level configuration information of each cluster service of the group: PDCP layer configuration information and RLC layer configuration information.
[0197] (3) A bit map of length L.
[0198] (4) Bitmap of length L1
[0199] When the gNB uses dynamic scheduling for the trunking services of a group, the gNB sends the following information on the TCCH of the group:
[0200] (1) High-level configuration information of each cluster service of the group: PDCP layer configuration information and RLC layer configuration information.
[0201] (2) A bitmap of length L.
[0202] (3) A bit map of length L1.
[0203] S105: gNB sends service data according to the service configuration information.
[0204] When the service adopts semi-static scheduling, the gNB periodically sends the service data through the activated SPS resources configured for the service.
[0205] Optionally, when the TB length of the service is greater than the TB length that can be transmitted by the activated SPS resources of the service, the gNB transmits the TB of the service in a dynamic scheduling manner.
[0206] Specifically, when the mapping window from PDCCH opportunity to SSB is configured for the service, the gNB selects S PDCCH opportunities in the CSS of the service, and the S PDCCH opportunities correspond to S different beams respectively; when the mapping window from PDCCH opportunity to SSB is not configured for the service, the gNB selects S PDCCH opportunities in the CSS of the service, and determines the beam used when sending PDCCH in each PDCCH opportunity, and different PDCCH opportunities use different beams. The gNB allocates PDSCH resources for each PDCCH opportunity to transmit the TB of the service, sends the PDCCH scrambled with CRC using G-CS-RNTI in each PDCCH opportunity, and the DCI format on the PDCCH is the dynamic scheduling information of the PDSCH resources allocated to the PDCCH opportunity, and uses the corresponding beam when sending PDCCH in each PDCCH opportunity.
[0207] For the PDCCH sent in each PDCCH opportunity, when the configuration information of the PDSCH parameters in the configuration information of the multicast session contains the aggregation factor F1, the gNB determines the first time slot for sending PDSCH based on the timing difference between PDCCH and PDSCH provided by the DCI format on the PDCCH. Starting from this time slot, the gNB occupies F1 consecutive downlink time slots to send PDSCH. The PDSCH sent in each time slot carries the TB of the service. The beam used when sending PDSCH is the beam used by PDCCH, and PDSCH uses G-CS-RNTI for bit scrambling.
[0208] Optionally, the gNB can retransmit the service in PTM mode. When the gNB decides to retransmit a TB of the service, the gNB can retransmit the TB in each beam direction in a dynamic scheduling manner, or it can retransmit the TB in only several beam directions in a dynamic scheduling manner.
[0209] S106: For the service, the UE receiving the service receives the target configuration information, obtains the configuration information of the service from the target configuration information, and receives the data of the service according to the configuration information of the service.
[0210] In the 3GPP NR system, the service is a multicast session in RRC inactive state. The UE receiving the multicast session receives the target configuration information sent by the gNB, obtains the configuration information of the multicast session from the target configuration information, and the specific process of the UE receiving the data of the multicast session according to the configuration information of the multicast session is as follows:
[0211] When the multicast session adopts semi-static scheduling, the UE can obtain the configuration information of the activated SPS resources configured by the gNB for the multicast session from the DCI format on the PDCCH scrambled by the multicast MCCH or CRC with G-CS-RNTI, and the UE periodically receives the data of the multicast session according to the configuration information of the activated SPS resources. The UE can also obtain the dynamic scheduling information of the multicast session from the DCI format on the PDCCH scrambled by the CRC with G-CS-RNTI, and receive the data of the multicast session according to the dynamic scheduling information of the multicast session.
[0212] In the B-TRUNCH 5G system, the service is a group trunk service. The UE receiving the group trunk service receives the target configuration information sent by the gNB, and obtains the group TCCH configuration information from the target configuration information. When the group trunk service adopts the semi-static scheduling mode, the UE monitors the PDCCH scrambled by CRC with G-CS-RNTI in the CSS configured for the group trunk service according to the G-CS-RNTI in the TCCH configuration information of the group. The UE can obtain the configuration information of the activated SPS resources of the group trunk service from the TCCH or from the DCI format on the PDCCH scrambled by G-CS-RNTI. The UE can periodically receive the data of the group trunk service according to the configuration information of the activated SPS resources of the group trunk service. The UE can also obtain the dynamic scheduling information of the group trunk service from the DCI format on the PDCCH scrambled by G-CS-RNTI on the CRC, and receive the data of the group trunk service according to the dynamic scheduling information of the group trunk service.
[0213] In the semi-static scheduling method under the PTM mode in the NR cell provided in this embodiment, for the service using the semi-static scheduling mode, the gNB configures a PDCCH opportunity to SSB mapping window and several SPS resources for the service; when transmitting the service, the gNB selects an SPS resource and generates an activated SPS resource from the selected SPS resource; the gNB sends the configuration information of the activated SPS resources of the service, and periodically sends the data of the service through the activated SPS resources of the service; the UE receives the configuration information of the activated SPS resources of the service sent by the gNB and periodically receives the data of the service sent by the gNB through the activated SPS resources of the service. Therefore, the semi-static scheduling method under the PTM mode in the NR cell provided in the embodiment of the present application realizes the function of scheduling the service transmitted in the PTM mode in a semi-static scheduling manner.
[0214] Figure 2 Schematic diagram of the process of the semi-static scheduling method under the PTM mode in the NR cell provided by this application Figure 2 The second embodiment of the present application describes in detail the related processing in S104 and S106 in the first embodiment of the present application. Specifically, the second embodiment of the present application describes in detail the following contents:
[0215] (1) Specific process of gNB sending multicast MCCH in S104;
[0216] (2) The specific process of UE receiving multicast MCCH in S106.
[0217] like Figure 2 As shown, the semi-static scheduling method under the PTM mode in the NR cell specifically includes the following steps:
[0218] S201: In the transmission window of each repetition period in each modification period of the multicast MCCH, the gNB sends the PDCCH of the multicast MCCH, and sends the corresponding PDSCH according to the PDCCH of the multicast MCCH.
[0219] Specifically, when a set of modification periods and repetition periods is configured for the multicast MCCH, the gNB determines the transmission windows for sending the PDCCH according to the configuration information of the modification period and repetition period. When two sets of modification periods and repetition periods are configured for the multicast MCCH, the gNB selects one set of modification periods and repetition periods from the two sets of modification periods and repetition periods before sending the MCCH, determines the position of the modification period for sending the most recent PDCCH according to the configuration information of the selected modification period and repetition period, and determines the position of the transmission windows in each repetition period in the modification period. Whether to send the PDCCH and PDSCH of the multicast MCCH in one modification period depends on the implementation of the gNB.
[0220] The gNB sends the PDCCH of the multicast MCCH in the CSS of the multicast MCCH in each transmission window. The CRC of the PDCCH of the multicast MCCH is scrambled with the MMCCH-RNTI, which is used to identify the multicast MCCH on the air interface. The DCI format on the PDCCH of the multicast MCCH provides the scheduling information of the corresponding PDSCH and the MCCH change notification. The MCCH change notification consists of the MCCH change notification field in the DCI format on the PDCCH. The MCCH change notification field contains 3 bits: when there is a new multicast session on the MCCH, the gNB sets the first bit in the MCCH change notification field to 1; when the configuration information of the existing multicast session on the MCCH is updated, the gNB sets the second bit in the MCCH change notification field to 1; when the gNB adopts a short modification period and repetition period, the gNB sets the third bit in the MCCH change notification field to 0, and when the gNB adopts a long modification period and repetition period, the gNB sets the third bit in the MCCH change notification field to 1.
[0221] The gNB sends the corresponding PDSCH according to the scheduling information provided in the DCI format on the PDCCH of the multicast MCCH, and uses the beam of the PDCCH that sends the multicast MCCH to send the corresponding PDSCH. The corresponding PDSCH uses MMCCH-RNTI when bit scrambling.
[0222] S202: The UE monitors the PDCCH whose CRC is scrambled with the MMCCH-RNTI in the CSS of the multicast MCCH.
[0223] When a set of modification periods and repetition periods is configured for the multicast MCCH, the UE monitors the PDCCH according to the set of modification periods and repetition periods; when two sets of modification periods and repetition periods are configured for the multicast MCCH, the UE monitors the PDCCH according to the shorter modification period and the shorter repetition period of the two sets of modification periods and repetition periods.
[0224] The UE may monitor every PDCCH opportunity, or monitor some discrete PDCCH opportunities according to its own needs.
[0225] Specifically, the UE can determine the beam corresponding to each PDCCH opportunity in the transmission window according to the mapping relationship between the PDCCH opportunity and the SSB beam in the transmission window of the multicast MCCH; when the UE determines that it is located within the coverage area of the kth beam, the UE only needs to monitor the PDCCH in each PDCCH opportunity corresponding to the kth beam in the transmission window.
[0226] S203: When the UE monitors the PDCCH whose CRC is scrambled with MMCCH-RNTI, the UE determines whether it needs to receive the PDSCH scheduled by the PDCCH according to the MCCH change notification field provided by the DCI format on the PDCCH. When it needs to receive the corresponding PDSCH, the UE receives the corresponding PDSCH according to the scheduling information provided by the DCI format on the PDCCH.
[0227] Specifically, when at least one of the first bit and the second bit in the MCCH change notification field in the DCI format on the PDCCH is set to 1, the UE determines that the corresponding PDSCH needs to be received. The UE receives the corresponding PDSCH according to the scheduling information provided by the DCI format on the PDCCH.
[0228] When the UE decodes the corresponding PDSCH incorrectly in the current transmission window, the UE determines the modification period and repetition period adopted by the multicast MCCH according to the value of the third bit in the MCCH change notification field in the DCI format on the PDCCH: when the third bit is 0 / 1, the UE determines that the multicast MCCH adopts a short / long modification period and a short / long repetition period. The UE determines the position of each transmission window in the current modification period according to the modification period and repetition period adopted by the multicast MCCH, and continues to receive the PDCCH and corresponding PDSCH of the multicast MCCH in subsequent transmission windows.
[0229] In the semi-static scheduling method in the PTM mode in the NR cell provided in this embodiment, the gNB sends the PDCCH and the corresponding PDSCH of the multicast MCCH within the transmission window of each repetition period in each modification period of the multicast MCCH. When the UE monitors the PDCCH whose CRC is scrambled with MMCCH-RNTI in the CSS of the multicast MCCH, the UE determines whether it needs to receive the corresponding PDSCH based on the MCCH change notification field provided in the DCI format on the PDCCH. When it is necessary to receive the corresponding PDSCH, the UE receives the corresponding PDSCH based on the scheduling information provided in the DCI format on the PDCCH. Therefore, the semi-static scheduling method in the PTM mode in the NR cell provided in this embodiment enables the gNB to send multicast MCCH in the NR cell and the UE to receive multicast MCCH in the NR cell.
[0230] An embodiment of the present application also provides a gNB for implementing the above-mentioned semi-static scheduling method under the PTM mode in the NR cell.
[0231] An embodiment of the present application also provides a UE for implementing the semi-static scheduling method under the PTM mode in the above-mentioned NR cell.
Claims
1. A semi-static scheduling method in a PTM mode in an NR cell, characterized in that: include: The gNB configures CORESET, CSS, PDCCH opportunity to SSB mapping window list and SPS resource list for services transmitted in PTM mode; For a service transmitted in PTM mode, when the gNB schedules the service in semi-static scheduling, the gNB configures a G-CS-RNTI for the service, configures at least one SPS resource for the service from the SPS resource list, and specifies a PDCCH opportunity to SSB mapping window for the service from the PDCCH opportunity to SSB mapping window list; The gNB configures activated SPS resources for the service; The gNB sends target configuration information in the NR cell; The gNB sends data of the service according to the configuration information of the service; For the service, the UE receiving the service receives the target configuration information, obtains the configuration information of the service from the target configuration information, and receives the data of the service according to the configuration information of the service.
2. The method according to claim 1, characterized in that The gNB configures an activated SPS resource for the service, including: When the gNB starts to transmit data of the service, the gNB selects an SPS resource from the SPS resources configured for the service, and determines the frequency domain resources, time domain resources, VRB to PRB mapping method and coding modulation method used when the SPS resource is used to send the service, to form an activated SPS resource, and determines the configuration information of the activated SPS resource; Among them, the activated SPS resources are periodically appearing resources, and in each period the activated SPS resources are composed of S resource blocks, each resource block is composed of F consecutive downlink time slots, F is the aggregation factor contained in the configuration information of the activated SPS resources, S is the number of beams for sending SSB in the cell, and different resource blocks correspond to different beams; according to the configuration information of the activated SPS resources, the positions of the S resource blocks contained in the activated SPS resources in each period can be determined.
3. The method according to claim 2, characterized in that The gNB configures an activated SPS resource for the service, including: In each cycle, the S resource blocks contained in the activated SPS resources correspond to the first beam to the Sth beam in chronological order; in each cycle, the S resource blocks contained in the activated SPS resources are composed of F*S consecutive downlink time slots.
4. The method according to claim 1, characterized in that: If the gNB belongs to a 3GPP NR system, the gNB sends target configuration information in the NR cell, including: The gNB sends, through SIB1 in the NR cell, configuration information of CORESET and CSS for multicast MCCH and configuration information of CORESET and CSS for multicast session configuration in RRC inactive state; The gNB sends the configuration information of the multicast MCCH through the multicast SIB in the NR cell; The gNB sends configuration information of each RRC inactive multicast session through the multicast MCCH in the NR cell; The gNB sends the configuration information of the multicast session to the UE receiving the multicast session through dedicated signaling in the NR cell; For each RRC inactive multicast session using semi-static scheduling, the gNB activates the SPS resources of the multicast session through the PDCCH in the NR cell.
5. The method according to claim 4, characterized in that The configuration information of the multicast MCCH on the multicast SIB includes: CFR configuration information; CORESET and CSS configuration information; at least one set of modification period and repetition period configuration information; The CFR configuration information is used to configure the CFR for sending multicast MCCH and multicast session in RRC inactive state; The CORESET and CSS configuration information is used to configure the CORESET and the CSS, and the CORESET and the CSS are used to send scheduling information of a multicast MCCH and a multicast session in an RRC inactive state; The configuration information of each group of modification period and repetition period includes: repetition period and offset, starting time slot position, transmission window length and modification period.
6. The method according to claim 4, characterized in that The multicast MCCH includes: A mapping window list of PDCCH timing to SSB, an SPS resource list, a PDSCH parameter list, a DRX parameter list, a neighbor cell list, and configuration information of each multicast session; the neighbor cell list is used to indicate each neighbor cell of the NR cell, the number of neighbor cells is L, and the neighbor cell list contains L groups of parameters, each group of parameters corresponds to a neighbor cell.
7. The method according to claim 6, characterized in that For a multicast session using semi-static scheduling, the configuration information of the multicast session includes: TMGI, G-CS-RNTI, PDCCH opportunity to SSB mapping window configuration information, DRX parameter configuration information, PDSCH parameter configuration information, each SPS resource configuration information, activated semi-static PTM resource configuration information, multicast session high-level configuration information, length L bitmap, length L1 bitmap; The configuration information of the PDCCH opportunity to SSB mapping window consists of the subscript of the PDCCH opportunity to SSB mapping window specified for the multicast session; The configuration information of the DRX parameters consists of a set of subscripts of DRX parameters specified for the multicast session from a DRX parameter list; The configuration information of the PDSCH parameters consists of a set of subscripts of PDSCH parameters specified for the multicast session from a PDSCH parameter list; The configuration information of each SPS resource consists of the subscripts of each SPS resource allocated to the multicast session; The configuration information of the activated semi-static PTM resources includes the positions of S resource blocks in each period and the beam used by each resource block; The high-level configuration information of the multicast session consists of an MRB list of the multicast session, wherein the MRB list includes PDCP configuration information and RLC configuration information of each MRB of the multicast session; The bit map of length L is used to indicate whether each neighboring cell provides the multicast session, each bit corresponds to a neighboring cell, and when one bit is 0 / 1, it indicates that the neighboring cell corresponding to the bit does not provide / provides the multicast session; The bit map of length L1 is used to indicate whether the configuration information of the multicast session in each neighboring cell providing the multicast session is the same as that of the current NR cell. Each bit corresponds to a neighboring cell providing the multicast session. When one bit is 0 / 1, it indicates that the configuration information of the multicast session in the neighboring cell corresponding to the bit is different from / the same as that of the current NR cell.
8. The method according to claim 1, characterized in that: If the gNB belongs to a B-TRUNC 5G system, the gNB sends target configuration information in the NR cell, including: The gNB sends the CORESET and CSS configuration information of the cluster service configuration of the group through SIB1 in the NR cell; The gNB sends a cluster-specific SIB in the NR cell; The gNB sends TCCH configuration information of each group through cluster paging in the NR cell; When a cluster service of a group adopts semi-static scheduling, the gNB activates the SPS resources of the cluster service of the group through PDCCH in the NR cell. To support UEs entering later, the gNB periodically sends PDCCH to activate the SPS resources of the cluster service of the group. The gNB sends configuration information of each cluster service of the group on the TCCH of each group.
9. The method according to claim 8, characterized in that The cluster-specific SIB includes: Configuration information of CORESET and CSS, mapping window list of PDCCH opportunity to SSB, SPS resource list, PDSCH parameter list; the configuration information of CORESET and CSS is used to configure CORESET and CSS, and the CORESET and CSS are used to send scheduling information of cluster services of the group.
10. The method according to claim 8, characterized in that When the gNB adopts semi-static scheduling for a cluster service of a group, the TCCH configuration information of the group includes: The group ID, G-CS-RNTI, configuration information of the PDCCH opportunity to SSB mapping window, configuration information of each SPS resource, configuration information of PDSCH parameters, and high-level configuration information of the TCCH of the group; The configuration information of each SPS resource consists of the subscripts of each SPS resource allocated to the group; The configuration information of the PDSCH parameters consists of a set of subscripts of PDSCH parameters assigned to the group from the PDSCH parameter list; The high-level configuration information of the TCCH of the group includes: PDCP configuration information of the TCCH and RLC configuration information of the TCCH.
11. The method according to claim 8, characterized in that When the gNB adopts semi-static scheduling for a trunking service of a group, the configuration information on the TCCH of the group includes: Configuration information of activated SPS resources configured for the cluster service of the group, high-level configuration information of each cluster service of the group, a bit map of length L, and a bit map of length L1; the high-level configuration information of each cluster service includes: PDCP layer configuration information and RLC layer configuration information.
12. The method according to claim 4 or 8, characterized in that: The gNB activates the SPS resources of the service through the PDCCH, including: When the gNB configures a mapping window of the PDCCH opportunity to the SSB for the service, the gNB determines the beam corresponding to each PDCCH opportunity in the CSS of the service according to the mapping window of the PDCCH opportunity to the SSB of the service; The gNB selects S PDCCH opportunities in the CSS of the service, the S PDCCH opportunities respectively corresponding to S different beams, sends a PDCCH scrambled by CRC using G-CS-RNTI in the S PDCCH opportunities, the PDCCH sent in each PDCCH opportunity uses a corresponding beam, and the DCI format on the PDCCH sent in each PDCCH opportunity is used to activate the SPS resources configured for the service in the corresponding beam direction; When the gNB does not configure a mapping window from a PDCCH opportunity to an SSB for the service; the gNB selects S PDCCH opportunities in the CSS of the service, and determines the beam used when sending the PDCCH in each PDCCH opportunity, and the beams used by the PDCCH in different PDCCH opportunities are different, and the gNB sends the PDCCH scrambled by the CRC using the G-CS-RNTI through the corresponding beam in each selected PDCCH opportunity; For the PDCCH sent in each PDCCH opportunity, the gNB determines the position of the first time slot for sending the PDSCH according to the timing difference between the PDCCH and the PDSCH provided in the DCI format on the PDCCH, and the consecutive F downlink time slots starting from the first time slot are the resource blocks allocated to the PDCCH. The gNB periodically sends the PDSCH through the resource blocks. In each period, the gNB sends the PDSCH in each downlink time slot in the resource block. The PDSCH uses G-CS-RNTI for bit scrambling. The same TB of the service is carried on the PDSCH, and the beam used by the PDCCH is used when sending the PDSCH.
13. The method according to claim 12, characterized in that The gNB activates the SPS resources of the service through the PDCCH, including: The S PDCCH opportunities correspond to the first beam to the Sth beam respectively in chronological order, and the S resource blocks allocated by the S PDCCH opportunities in each cycle correspond to the first beam to the Sth beam respectively in chronological order; the S resource blocks allocated by the S PDCCH opportunities are connected end to end, and in each cycle, the S resource blocks allocated by the S PDCCH opportunities are composed of consecutive F*S downlink time slots, and in each cycle, the gNB sends the same TB of the service through the S resource blocks, and sends the same TB of the service consecutively F times in each beam direction.
14. The method according to claim 1, characterized in that The gNB sends data of the service according to the configuration information of the service, including: When the service adopts a semi-static scheduling method, the gNB periodically sends data of the service through the activated SPS resources configured for the service.
15. The method according to claim 1, characterized in that The gNB sends data of the service according to the configuration information of the service, including: When the TB length of the service is greater than the TB length that can be transmitted by the activated SPS resources of the service, the gNB transmits data of the service in a dynamic scheduling manner; The gNB transmits data of the service in a dynamic scheduling manner, including: When the gNB configures a mapping window from a PDCCH opportunity to an SSB for the service, the gNB selects S PDCCH opportunities in the CSS of the service, and the S PDCCH opportunities correspond to S different beams respectively; when the gNB does not configure a mapping window from a PDCCH opportunity to an SSB for the service, the gNB selects S PDCCH opportunities in the CSS of the service, and determines the beam used when sending the PDCCH in each PDCCH opportunity, and different PDCCH opportunities use different beams; The gNB allocates PDSCH resources for each PDCCH opportunity for transmitting data of the service, sends a PDCCH scrambled by G-CS-RNTI for CRC in each PDCCH opportunity, the DCI format on the PDCCH is the dynamic scheduling information of the PDSCH resources allocated to the PDCCH opportunity, and uses the corresponding beam when sending the PDCCH in each PDCCH opportunity; For the PDCCH sent in each PDCCH opportunity, when the configuration information of the PDSCH parameters in the configuration information of the multicast session includes the aggregation factor F1, the gNB determines the first time slot for sending the PDSCH according to the timing difference between the PDCCH and the PDSCH provided by the DCI format on the PDCCH, and starting from the time slot, the gNB occupies F1 consecutive downlink time slots to send the PDSCH. The PDSCH sent in each time slot carries the TB of the service. The beam used when sending the PDSCH is the beam used by the PDCCH, and the PDSCH uses G-CS-RNTI for bit scrambling.
16. The method according to claim 1, characterized in that The gNB sends data of the service according to the configuration information of the service, including: The gNB retransmits the service through PTM. When the gNB decides to retransmit a TB of the service, the gNB retransmits the TB in a dynamic scheduling manner in each beam direction, or retransmits the TB in a dynamic scheduling manner only in several beam directions.
17. The method according to claim 1, characterized in that For the service, a UE receiving the service receives the target configuration information, obtains the configuration information of the service from the target configuration information, and receives data of the service according to the configuration information of the service, including: In a 3GPP NR system, the service is a multicast session in an RRC inactive state, and a UE receiving the multicast session receives the target configuration information sent by the gNB, obtains the configuration information of the multicast session from the target configuration information, and receives data of the multicast session according to the configuration information of the multicast session; The obtaining the configuration information of the multicast session from the target configuration information, and receiving the data of the multicast session according to the configuration information of the multicast session, comprises: When the multicast session adopts the semi-persistent scheduling mode, the UE may obtain the configuration information of the activated SPS resources configured by the gNB for the multicast session from the DCI format on the PDCCH scrambled by the multicast MCCH or CRC with the G-CS-RNTI, and the UE periodically receives the data of the multicast session according to the configuration information of the activated SPS resources; Alternatively, the UE obtains the dynamic scheduling information of the multicast session from the DCI format on the PDCCH in which the CRC is scrambled with the G-CS-RNTI, and receives the data of the multicast session according to the dynamic scheduling information of the multicast session.
18. The method according to claim 1, characterized in that For the service, the UE receiving the service receives target configuration information, obtains configuration information of the service from the target configuration information, and receives data of the service according to the configuration information of the service, including: In the B-TRUNCH 5G system, the service is a trunk service of a group. A UE receiving the trunk service of the group receives the target configuration information sent by the gNB, obtains the configuration information of the TCCH of the group from the target configuration information, and when the trunk service of the group adopts a semi-static scheduling mode, the UE monitors the PDCCH scrambled by the CRC using the G-CS-RNTI in the CSS configured for the trunk service of the group according to the G-CS-RNTI in the configuration information of the TCCH of the group. The UE obtains configuration information of activated SPS resources of the cluster service of the group from the TCCH or from the DCI format on the PDCCH scrambled by the G-CS-RNTI; the UE periodically receives data of the cluster service of the group according to the configuration information of the activated SPS resources of the cluster service of the group; Alternatively, the UE obtains the dynamic scheduling information of the cluster service of the group from the DCI format on the PDCCH scrambled by the CRC using the G-CS-RNTI, and receives the data of the cluster service of the group according to the dynamic scheduling information of the cluster service of the group.
19. The method according to claim 4 or 17, characterized in that: The gNB sending the target configuration information in the NR cell includes: the gNB sending the multicast MCCH in the NR cell; For the service, a UE receiving the service receives the target configuration information, including: the UE receives the multicast MCCH; The gNB sending the multicast MCCH in the NR cell includes: In a transmission window of each repetition period in each modification period of the multicast MCCH, the gNB sends a PDCCH of the multicast MCCH, and sends a corresponding PDSCH according to the PDCCH of the multicast MCCH; The UE receiving the multicast MCCH includes: The UE monitors the PDCCH scrambled by the CRC using the MMCCH-RNTI in the CSS of the multicast MCCH; When the UE monitors the PDCCH whose CRC is scrambled with MMCCH-RNTI, the UE determines whether it needs to receive the PDSCH of the multicast MCCH scheduled by the PDCCH according to the MCCH change notification field provided by the DCI format on the PDCCH; When it is necessary to receive the PDSCH of the multicast MCCH, the UE receives the PDSCH of the multicast MCCH according to the scheduling information provided in the DCI format on the PDCCH.
