Communication method and apparatus

Abstract

A communication method and an apparatus. The method may be applied to non-terrestrial network (NTN) communication. The method comprises: an RNTI allocated by a network to a terminal may comprise two portions: one portion is used for identifying a user group (denoted as a first identifier), and the other portion is used for identifying a terminal in the user group (denoted as a second identifier), wherein terminals belonging to a same user group are located in a same geographic area; and the network associates first configuration information with the first identifier, and associates second configuration information with the second identifier, the first configuration information and the second configuration information being used for control channel detection. An RNTI allocated by a network comprises an identifier of a user group, so that compared with additionally allocating a group identifier beyond an RNTI, the present application can reduce signaling overhead. In addition, a network performs differentiated control channel detection configurations for user groups and terminals in the user groups, so that control channel detection timing and the like can be flexibly configured, thereby avoiding frequent control channel detection by terminals, reducing detection overhead of terminals, and reducing power consumption.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411709886.7, filed with the State Intellectual Property Office of China on November 25, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0003] Non-terrestrial networks (NTNs) possess significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and no geographical limitations. They have been widely applied in various fields including maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. NTN networks can be integrated with terrestrial networks, leveraging their respective strengths to form a seamless global communication network encompassing sea, land, air, space, and ground, meeting users' ubiquitous and diverse service needs.

[0004] A radio network temporary identifier (RNTI) is a type of identifier. Currently, in terrestrial networks, RNTIs are mainly used by base stations to identify terminals and as a cyclic redundancy code (CRC) for scrambling downlink control information (DCI).

[0005] However, due to the differences between terrestrial networks and NTN networks (such as the wide coverage and high mobility of NTN networks), the RNTI and related configurations of terrestrial networks are not suitable for NTN networks. Using the RNTI and related configurations of terrestrial networks for NTN networks may result in lower communication efficiency. Summary of the Invention

[0006] This application provides a communication method and apparatus that can improve communication efficiency, such as saving signaling overhead.

[0007] Firstly, a communication method is provided. This method can be executed by a first terminal, or by a component of the first terminal, such as a processor, chip, or chip system of the first terminal, or by a logic module or software capable of implementing all or part of the functions of the first terminal. The method includes: receiving a first Radio Network Temporary Identifier (RNTI) of the first terminal, the first RNTI including a first identifier and a second identifier; receiving first configuration information and second configuration information, the first identifier being associated with the first configuration information and the second identifier being associated with the second configuration information; and performing control channel detection based on the first configuration information and the second configuration information. The first identifier is used to identify a first user group, and the second identifier is used to identify first terminals within the first user group, wherein terminals belonging to the first user group are located in the same geographical area.

[0008] Based on this scheme, since the terminal's RNTI includes the user group identifier, signaling overhead can be significantly reduced compared to additionally allocating a group identifier outside the RNTI. Furthermore, because the RNTI includes the user group identifier, user group-based signaling configuration is enabled. For example, the network configures common mobility configuration information for a user group, and terminals within the user group can use a first identifier to obtain this common mobility configuration information, further reducing signaling overhead compared to terminal-level configuration. Moreover, the network sends configuration information separately to the user group and the terminals within the user group, performing differentiated control channel detection configuration. This allows for flexible configuration of the timing of control channel detection based on the frequency of common configuration and terminal-specific configuration, avoiding frequent control channel detection by the terminal, reducing terminal detection overhead, and saving power.

[0009] In one possible design, the first configuration information is used to configure the first search space, and the second configuration information is used to configure the second search space; the first search space and the second search space differ from at least one of the following: detection period, time offset, or detection duration.

[0010] Based on this possible design, by differentiating the search space, the blind detection overhead of the terminal can be reduced, energy efficiency improved, and power consumption saved. For example, the common configuration information of user groups appears every tens or even hundreds of seconds, while the granularity of user data scheduling of the terminal is at the TTI level, typically 1ms or even lower. If the first and second identifiers are associated with the same search space, and if a small detection period is configured to ensure that the terminal's data reception is consistently received, the terminal will frequently perform detection of the common PDCCH. However, the common PDCCH appears infrequently, and the terminal will not be able to detect it in every detection, thus wasting the terminal's power consumption. The differential configuration based on the search space in this application can avoid this problem.

[0011] In one possible design, the control channel includes a Physical Downlink Control Channel (PDCCH). Control channel detection based on first configuration information includes: determining a first search space based on the first configuration information; performing blind PDCCH detection using a first identifier or a third identifier within the first search space; the length of the third identifier is the same as the length of the first RNTI, and the third identifier includes the first identifier and a preset value. Alternatively, control channel detection based on second configuration information includes: determining a second search space based on the second configuration information; performing blind PDCCH detection using a second identifier or the first RNTI within the second search space.

[0012] Based on this possible design, when using a first identifier in the first search space and a second identifier or a first RNTI in the second search space for PDCCH blind detection, identifiers of different lengths can be used to perform blind detection of the public PDCCH and the terminal-specific PDCCH respectively, simplifying implementation and reducing terminal implementation complexity. Alternatively, when using a third identifier in the first search space and a first RNTI in the second search space for PDCCH blind detection, identifiers of the same length can be used to perform blind detection of the public PDCCH and the terminal-specific PDCCH respectively, allowing PDCCH blind detection to be performed based on the same criteria.

[0013] In one possible design, first configuration information is used to configure a first discontinuous reception DRX pattern, and second configuration information is used to configure a second DRX pattern; the first DRX pattern and the second DRX pattern differ from at least one of the following: DRX period, activation duration, or DRX timer. For example, the DRX timer may include a DRX retransmission timer, a DRX inactive state timer, etc.

[0014] Based on this possible design, different DRX patterns can be associated with user group identifiers and the identifiers of terminals within the user group, enabling differentiated configuration of DRX patterns. Compared to associating the same DRX pattern with user group identifiers and the identifiers of terminals within the user group, this reduces the blind detection overhead of the terminal and saves the terminal's power consumption.

[0015] In one possible design, the control channel includes a PDCCH; control channel detection based on first configuration information includes: determining a first DRX pattern based on the first configuration information; performing blind PDCCH detection using a first identifier or a third identifier during the activation duration of the first DRX pattern; the length of the third identifier is the same as the length of the first RNTI, and the third identifier includes the first identifier and a preset value. Alternatively, control channel detection based on second configuration information includes: determining a second DRX pattern based on the second configuration information; performing blind PDCCH detection using a second identifier or the first RNTI during the activation duration of the second DRX pattern.

[0016] Based on this possible design, when using the first identifier during the activation duration of the first DRX pattern and the second identifier or the first RNTI during the activation duration of the second DRX pattern for PDCCH blind detection, identifiers of different lengths can be used to perform blind detection of the public PDCCH and the terminal-specific PDCCH respectively, simplifying implementation and reducing terminal implementation complexity. Alternatively, when using a third identifier during the activation duration of the first DRX pattern and the first RNTI during the activation duration of the second DRX pattern for PDCCH blind detection, identifiers of the same length can be used to perform blind detection of the public PDCCH and the terminal-specific PDCCH respectively, allowing PDCCH blind detection to be performed based on the same criteria.

[0017] In one possible design, the first configuration information is also used to configure the wake-up signal (WUS) associated with the first identifier. Control channel detection based on the first configuration information includes: determining the time-frequency location of the WUS associated with the first identifier based on the first configuration information; and, if the WUS associated with the first identifier is detected at the time-frequency location, performing PDCCH blind detection using either the first identifier or the third identifier during the activation duration of the first DRX pattern.

[0018] Based on this possible design, PDCCH blind detection is only performed during the activation duration of the first DRX pattern if the WUS associated with the first identifier is detected; if the WUS associated with the first identifier is not detected, the terminal can remain in a sleep state during the activation duration of the first DRX pattern without performing PDCCH blind detection, which can further save the terminal's power consumption.

[0019] In one possible design, the first configuration information is used to configure the MBS control channel MCCH; control channel detection is performed based on the first configuration information, including: detecting the MCCH based on the first configuration information.

[0020] Based on this possible design, control channel detection configurations can be applied separately for MBS associated with the first identifier and unicast services associated with the second identifier, enabling differentiated configurations for control channel detection across different service types. Compared to applying the same control channel detection configuration to MBS and unicast services, this avoids the terminal frequently detecting the control channel associated with MBS, thereby reducing the terminal's detection overhead and saving power consumption.

[0021] In one possible design, the method further includes: receiving control signaling, the control signaling being associated with the MBS.

[0022] In one possible design, the method further includes receiving third configuration information and / or fourth configuration information. The third configuration information is used to configure the position of public information associated with the first identifier in the first Media Access Control Protocol Data Unit (MAC PDU); the fourth configuration information is used to configure the position of private information associated with the second identifier in the first MAC PDU, the position of which is related to the second identifier.

[0023] Based on this possible design, the common information of the user group and the dedicated information of each terminal within the user group can be multiplexed and carried in the same MAC PDU. Furthermore, the position of a terminal's dedicated information within the MAC PDU is related to that terminal's identifier. Therefore, the terminal can decode its own MAC subPDU to obtain its dedicated information without needing to decode the MAC subPDUs associated with other terminals, thus reducing decoding complexity and saving terminal power consumption. In addition, the network configures common information for the user group, and all terminals within the user group can use a first identifier to obtain this common information. Compared to configuration at the terminal level, this further reduces signaling overhead.

[0024] Secondly, a communication method is provided. This method can be executed by a first network device, or by a component of the first network device, such as its processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the functions of the first network device. The method includes: sending a first radio network temporary identifier (RNTI) of a first terminal, the first RNTI including a first identifier and a second identifier; sending first configuration information and second configuration information, the first identifier associated with the first configuration information, and the second identifier associated with the second configuration information, the first configuration information and the second configuration information being used for control channel detection. The first identifier is used to identify a first user group, and the second identifier is used to identify a first terminal within the first user group, wherein terminals belonging to the first user group are located in the same geographical area. The technical effects of this second aspect are similar to those of the first aspect described above, and will not be repeated here.

[0025] In one possible design, the method further includes: sending control signaling associated with the MBS.

[0026] In one possible design, the method further includes sending third configuration information and / or fourth configuration information. The third configuration information is used to configure the position of public information associated with the first identifier in the first Media Access Control Protocol Data Unit (MAC PDU); the fourth configuration information is used to configure the position of private information associated with the second identifier in the first MAC PDU, the position of the private information in the first MAC PDU being related to the second identifier.

[0027] The technical effects of any possible design in the second aspect can be referred to the technical effects of the corresponding design in the first aspect mentioned above, and will not be repeated here.

[0028] In one possible design, in conjunction with the first or second aspect, the first configuration information is used to configure the first search space, and the second configuration information is used to configure the second search space; the first search space and the second search space differ from at least one of the following: detection period, time offset, or detection duration.

[0029] In conjunction with the first or second aspect, in one possible design, the first configuration information includes at least one of the following in the first search space: detection period, time offset, or detection duration; the second configuration information includes at least one of the following in the second search space: detection period, time offset, or detection duration.

[0030] In one possible design, in conjunction with the first or second aspect, the second configuration information includes at least one of the following in the second search space: detection period, time offset, or detection duration; the first configuration information includes a scaling factor, which is used to scale the second search space to obtain the first search space.

[0031] In one possible design, combining the first or second aspect, the first search space is a group search space and the second search space is a terminal-specific search space.

[0032] In conjunction with the first or second aspect, in one possible design, the first configuration information is used to configure a first discontinuous reception DRX pattern, and the second configuration information is used to configure a second DRX pattern; the first DRX pattern and the second DRX pattern differ from at least one of the following: DRX period, active duration, or DRX timer (such as a DRX retransmission timer, a DRX inactive state timer, etc.).

[0033] In conjunction with the first or second aspect, in one possible design, the first configuration information is also used to configure the wake-up signal WUS associated with the first identifier.

[0034] In one possible design, combining the first or second aspect, the first configuration information is used to configure the multicast / broadcast service MBS, and the second configuration information is used to configure the unicast service.

[0035] In conjunction with the first or second aspect, in one possible design, the first configuration information for configuring MBS includes: the first configuration information for configuring the MBS control channel MCCH.

[0036] In one possible design, in conjunction with the first or second aspect, the third configuration information indicates that the public information associated with the first identifier is carried in the first MAC subPDU of the first MAC PDU.

[0037] In conjunction with the first or second aspect, in one possible design, the third configuration information is carried in the subheader of the first MAC subPDU of the first MAC PDU, and the third configuration information indicates the number of MAC subPDUs occupied by the public information associated with the first identifier; or, the third configuration information is carried in the subheader of the first X MAC subPDUs of the first MAC PDU, and the third configuration information indicates whether the information carried by the MAC subPDU where the third configuration information is located is the public information associated with the first identifier.

[0038] In one possible design, in conjunction with the first or second aspect, the fourth configuration information indicates a preset rule for determining the location of the special information associated with the second identifier in the first MAC PDU.

[0039] In one possible design, combining the first or second aspect, the preset rules include: the MAC subPDU carrying the special information associated with the second identifier has an index in the first MAC PDU that is the sum of K and the second identifier, where K is a positive integer.

[0040] In conjunction with either the first or second aspect, in one possible design, the private information associated with the second identifier is encrypted and / or scrambled using the second identifier. Based on this possible design, it is possible to prevent the private information of a certain terminal from being obtained by other terminals, thereby avoiding user information leakage, etc.

[0041] Thirdly, a communication device is provided for implementing various methods. This communication device can be a first terminal as described in the first aspect, or a device included in the first terminal, such as a chip or chip system; or, the communication device can be a first network device as described in the second aspect, or a device included in the first network device, such as a chip or chip system. The communication device includes modules, units, or means corresponding to the implementation of the methods, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0042] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

[0043] In some possible designs, the transceiver module can consist of transceiver circuits, transceivers, transceivers, or communication interfaces.

[0044] Fourthly, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform the method described in any of the aspects. The communication device may be a first terminal as described in the first aspect, or a device included in the first terminal, such as a chip or a chip system; or, the communication device may be a first network device as described in the second aspect, or a device included in the first network device, such as a chip or a chip system.

[0045] Fifthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute computer programs or instructions to cause the communication device to perform the methods described in any of the aspects. The communication device may be a first terminal as described in the first aspect, or a device included in the first terminal, such as a chip or chip system; or, the communication device may be a first network device as described in the second aspect, or a device included in the first network device, such as a chip or chip system.

[0046] A sixth aspect provides a communication device, comprising: at least one processor; the processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the methods described in any aspect. The memory may be coupled to the processor, or may be independent of the processor. The communication device may be a first terminal as described in the first aspect, or a device included in the first terminal, such as a chip or chip system; or, the communication device may be a first network device as described in the second aspect, or a device included in the first network device, such as a chip or chip system.

[0047] In a seventh aspect, a communication device (e.g., a chip or a chip system) is provided, the communication device including at least one processor for implementing the functions involved in any aspect and any possible design thereof. The communication device may be a first terminal in the first aspect, or a device included in the first terminal, such as a chip or a chip system; or, the communication device may be a first network device in the second aspect, or a device included in the first network device, such as a chip or a chip system.

[0048] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0049] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0050] Eighthly, a communication device is provided. This communication device may be a first terminal, or a module or unit (e.g., a chip, chip system, or circuit) within the first terminal that performs the methods / operations / steps / actions described in the first aspect, or a module or unit that can be used in conjunction with the first terminal; or, the communication device may be a first network device, or a module or unit (e.g., a chip, chip system, or circuit) within the first network device that performs the methods / operations / steps / actions described in the second aspect, or a module or unit that can be used in conjunction with the first network device.

[0051] It is understandable that when the communication device provided by any of the third to eighth aspects is a chip, the sending action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0052] A ninth aspect provides a computer-readable storage medium storing a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in the first aspect and any possible design thereof.

[0053] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to perform the method described in any aspect and any possible design thereof.

[0054] Eleventhly, a communication system is provided, comprising a first terminal and a first network device. The first terminal is used to implement the method described in the first aspect and any possible design thereof, and the first network device is used to implement the method described in the second aspect and any possible design thereof.

[0055] The technical effects of any of the design methods in aspects three through eleven can be found in the technical effects of different design methods in aspects one or two, and will not be repeated here. Attached Figure Description

[0056] Figure 1 is a schematic diagram of the beam coverage range in non-staring mode and staring mode of an NTN provided in this application;

[0057] Figure 2 is a schematic diagram of a group handover scenario provided in this application;

[0058] Figure 3 is a schematic diagram of a cell handover process provided in this application;

[0059] Figure 4 is a schematic diagram of the architecture of an O-RAN system provided in this application;

[0060] Figure 5 is a schematic diagram of the architecture of a mobile satellite communication system provided in this application;

[0061] Figure 6 is a flowchart illustrating a communication method provided in this application;

[0062] Figure 7 is a schematic diagram of an enhanced RNTI provided in this application;

[0063] Figure 8 is a schematic diagram of an enhanced RNTI for a terminal in different geographical regions provided in this application;

[0064] Figure 9 is a schematic diagram illustrating the differences between a first search space and a second search space provided in this application;

[0065] Figure 10 is a schematic diagram of a PDDCH processing procedure provided in this application;

[0066] Figure 11 is a schematic diagram of an RNTI usage rule provided in this application;

[0067] Figure 12 is a schematic diagram showing the differences between a first DRX pattern and a second DRX pattern provided in this application;

[0068] Figure 13 is a schematic diagram of a WUS-based detection method provided in this application;

[0069] Figure 14 is a schematic diagram of the structure of a MAC PDU provided in this application;

[0070] Figure 15 is a schematic diagram of the structure of a communication device provided in this application;

[0071] Figure 16 is a schematic diagram of another communication device provided in this application;

[0072] Figure 17 is a schematic diagram of another communication device provided in this application. Detailed Implementation

[0073] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0074] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0075] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0076] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0077] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0078] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0079] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0080] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments described below do not constitute a limitation on the scope of protection of this application.

[0081] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0082] 1. Non-terrestrial networks (NTN):

[0083] Currently, the 5th generation (5G) new radio (NR) has moved from the standardization stage to the commercial deployment stage. The NR standard is mainly designed and researched for the characteristics of terrestrial communication, which can provide user terminals with high-speed, high-reliability, and low-latency communication.

[0084] Compared to terrestrial communications, NTN communications offer significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and freedom from geographical limitations. It has been widely applied in various fields including maritime communications, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. NTN networks can be integrated with terrestrial networks, leveraging their respective strengths to create a seamless, globally integrated sea, land, air, space, and ground communications network, meeting the diverse and ubiquitous service needs of users.

[0085] Depending on the altitude of the flight platform above the ground, the NTN can include a low altitude platform (LAP) subnetwork, a high altitude platform (HAP) subnetwork, and a satellite communication subnetwork.

[0086] For example, in the LAP subnetwork, base stations or base station functions are deployed on low-altitude flight platforms (e.g., drones) at an altitude of 0.1km to 1km above the ground to provide coverage for terminals; in the HAP subnetwork, base stations or base station functions are deployed on high-altitude flight platforms (e.g., airplanes) at an altitude of 8km to 50km above the ground to provide coverage for terminals; and in the SATCOM subnetwork, base stations or base station functions are deployed on satellites at an altitude of more than 50km above the ground to provide coverage for terminals.

[0087] Furthermore, based on the satellite's orbital altitude, satellite communication systems can be divided into geostationary earth orbit (GEO) satellite communication systems, medium earth orbit (MEO) satellite communication systems, and low-earth orbit (LEO) satellite communication systems.

[0088] The GEO satellite communication system, also known as the geostationary orbit satellite system, operates at an altitude of 35,786 km. Its orbital speed is the same as the Earth's rotation speed, meaning GEO satellites can remain stationary relative to the ground. The GEO satellite communication system can provide large cell coverage, typically with a cell diameter of 500 km. However, GEO satellite communication also has significant drawbacks: 1) The high distance between GEO satellites and Earth's orbits results in significant free-space propagation loss, leading to tight communication link budgets and requiring larger antennas to increase transmit / receive gain; 2) Large communication transmission delays, such as a round-trip delay of approximately 500 milliseconds, cannot meet the demands of real-time services; 3) GEO orbital resources are relatively scarce, launch costs are high, and coverage of the polar regions is not available.

[0089] MEO satellites orbit at altitudes between 2000 and 35786 km, enabling global coverage with a relatively small number of satellites. However, MEO satellites orbit at higher altitudes than LEO satellites, resulting in longer transmission delays. Therefore, considering both the advantages and disadvantages of MEO satellite communication, it is primarily used for positioning and navigation.

[0090] LEO satellites orbit at altitudes between 300 and 2000 km, lower than MEO satellites. They offer advantages such as lower transmission delay, less transmission loss, and relatively lower launch costs.

[0091] The next generation of satellite communication systems generally exhibits a trend towards ultra-dense and heterogeneous architectures. First, the number of satellites has grown from 66 in the Iridium constellation to 720 in a single-network constellation, and eventually extended to the Starlink ultra-dense LEO satellite constellation with over 12,000 satellites. Second, satellite networks are exhibiting heterogeneous characteristics, evolving from traditional single-layer communication networks to multi-layer communication networks. The functions of communication satellite networks are also becoming more complex and diversified, gradually becoming compatible with and supporting functions such as navigation enhancement, Earth observation, and on-orbit processing of multi-dimensional information.

[0092] 2. Non-gazing mode (earth-moving) and gazing mode (earth-fixed or quasi-earth fixed):

[0093] In satellite communication systems, beam operation modes are typically categorized into non-staring mode and staring mode. As shown in Figure 1(a), in non-staring mode, the coverage area of ​​the satellite beam moves along with the satellite over a period of time (e.g., between time t0 and time t2). As shown in Figure 1(b), in staring mode, the satellite dynamically adjusts the beam pointing to approximately cover the same area of ​​the ground over a period of time (e.g., between time t0 and time t2). However, in practical applications, due to beam pointing accuracy issues and distortion caused by beam projection onto the ground at different incident angles, the coverage area of ​​the beam still exhibits some degree of jitter over time in staring mode.

[0094] For example, the beam in the protocol can be represented as a spatial domain filter, or a spatial filter, or a spatial domain parameter, spatial parameter, spatial domain setting, spatial setting, or quasi-colocation (QCL) information, QCL assumption, QCL indication, etc. The beam can be indicated by a transmission configuration indication (TCI) state parameter or a spatial relation parameter. Therefore, in this application, the beam can be replaced by spatial domain filter, spatial filter, spatial parameter, spatial parameter, spatial setting, spatial setting, QCL information, QCL assumption, QCL indication, TCI-state, spatial relation, etc. These terms are also equivalent to each other. The beam in this application can also be replaced by other beam-related terms, and this application does not limit this.

[0095] 3. Group switching and group reselection:

[0096] The movement of satellites can cause a group handover of connected terminals in a certain area, or cause a group reselection of idle terminals in that area.

[0097] Taking group handover as an example, as shown in Figure 2, assume that a user equipment (UE) cluster (denoted as UE-G1, which includes multiple UEs) exists within sub-region 1 of region 2. At time T1, sub-region 1 is served by one or more beams of satellite 2. At time T2, the movement of satellite 2 causes it to be unable to continue serving sub-region 1, and one or more beams of satellite 1 take over the service of sub-region 1. During this process, because the satellites covering sub-region 1 change, multiple UEs in UE-G1 undergo group handover, switching from satellite 2 to satellite 1.

[0098] Because satellites move at relatively high speeds, for example, LEO satellites move at approximately 7.5 km / s, group handovers occur frequently, approximately once every few seconds to tens of seconds. In other words, in NTN, group handovers primarily triggered by network mobility are considered the norm.

[0099] 4. Mobility Management:

[0100] Mobility management mainly includes cell handover, cell reselection, registration update, and tracking area update. Taking cell handover as an example, as shown in Figure 3, the cell handover process in the NR system mainly includes the following steps:

[0101] 1) Cell handover measurement: The source base station (such as a next-generation node B (gNodeB or gNB)) can send measurement configurations for multiple cells (including the serving cell and neighboring cells) to the terminal. The terminal measures the cell signal quality according to the measurement configuration.

[0102] For example, cell signal quality can be represented by reference signal receiving power (RSRP) and / or reference signal receiving quality (RSRQ). The measured signal is typically a synchronization signal block (SSB), with typical periods of 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms.

[0103] 2) Measurement Result Reporting: The terminal reports the measurement results to the source base station. For example, the terminal can report periodically or based on event triggers. For example, the reporting trigger event could be the serving cell's signal quality being less than threshold 1, and / or the neighboring cell's signal quality being greater than threshold 2.

[0104] 3) Handover decision: The source base station selects a suitable neighboring cell as the target cell based on the measurement results and sends a handover request to the target base station, which carries the user handover-related context information.

[0105] 4) Admission Control: After receiving the handover request, the target base station performs admission control. If the terminal is allowed to access, it sends a handover request confirmation message to the source base station, which carries relevant information for the terminal to access the target cell. After receiving the handover request confirmation message, the source base station sends a radio resource control (RRC) reconfiguration message to the terminal, which carries relevant information for accessing the target cell.

[0106] 5) Handover Execution: After receiving the handover-related information, the terminal completes the access process in the target cell.

[0107] For example, the terminal sends a random access preamble to the target cell to initiate random access in the target cell. The random access preamble used by the terminal during handover is a dedicated preamble, which is different from the contention-based random access preamble used during initial access. Furthermore, the period of the random access channel (RACH) during cell handover can be 10 / 20 / 40 / 80 / 160ms.

[0108] During the cell reselection process, the base station broadcasts parameters such as measurement configuration related to neighboring cells. The terminal compares the signal quality measurement value with the parameters (such as reselection threshold) sent by the network. If the reselection conditions are met, the terminal will automatically reselect to the target neighboring cell.

[0109] In other words, in NR systems, terminals perform cell handover or cell reselection based on signal quality. However, in NTN, the near-far effect is not significant, and cell handover or cell reselection based solely on signal quality is inefficient. Therefore, NTN proposes to implement mobility management based on information such as time and location (e.g., the distance between the terminal and the reference point of the source cell and the reference point of the target cell).

[0110] 5. Radio Network Temporary Identifier (RNTI):

[0111] An RNTI can be understood as an identifier. Identifiers are typically used to distinguish one thing from another in an environment, such as a student's student ID number at school.

[0112] In wireless networks, RNTI can be understood as a terminal identifier (or UE ID) used in communication between a terminal and the base station to distinguish one terminal from others. In this context, RNTI can also be used to scramble the cyclic redundancy code (CRC) of downlink control information (DCI). In other words, RNTI has two main uses:

[0113] Used to identify the terminal or for base station to identify the terminal: The RRC message sent by the terminal will carry the terminal's unique RNTI;

[0114] CRC used for scrambling DCI: Each DCI (more precisely, the CRC of each DCI) is scrambled by a specific RNTI. The terminal can only decode the information sent to it by the base station using its own RNTI.

[0115] For example, RNTIs in current terrestrial networks include, but are not limited to, one or more of the following RNTIs:

[0116] System Information RNTI (SI-RNTI): An RNTI used for scrambling system information. SI-RNTI is a common RNTI; system information is information that all terminals within the cell need to monitor, therefore SI-RNTI is applicable to all terminals within the cell. After DCI is scrambled using SI-RNTI, it indicates that the DCI is scheduling information for system information. When the terminal successfully decodes the DCI, it can detect the system information from the corresponding physical downlink shared channel (PDSCH).

[0117] Paging RNTI (P-RNTI): An RNTI used for scrambling paging messages, used by the terminal to receive paging messages. P-RNTI is a public RNTI, meaning it is not explicitly assigned to any terminal. After the DCI is scrambled with the P-RNTI, it represents the scheduling information for the paging message. Once the terminal successfully decodes the DCI, it can receive the paging message from the corresponding PDSCH.

[0118] Random access RNTI (RA-RNTI): The RNTI used for scrambling Msg2 (i.e., random access response (RAR)) during random access (RA) process. It can be calculated based on the resource location of the physical random access channel (PRACH). After RA-RNTI scrambles the DCI, it indicates that the PDSCH scheduled by that DCI is used for the random access response.

[0119] Temporary cell RNTI (TC-RNTI): Used for scrambling Msg3 (contention resolution message) and Msg4 (contention resolution message). It is allocated by the base station and sent to the terminal via Msg2 for contention-based access. In contention-based random access, the terminal monitors the physical downlink control channel (PDCCH) scrambled using TC-RNTI.

[0120] Cell RNTI (C-RNTI): Obtained from the TC-RNTI during access contention, and sent to the terminal in handover signaling during handover scenarios. It is used by the base station to distinguish connected terminals; it can also be understood as a temporary identifier for a connected terminal within the cell. Within the same cell, different terminals will have different C-RNTIs. The base station uses different C-RNTIs to perform uplink and downlink scheduling for different terminals.

[0121] Transmission power control RNTI (TPC RNTI): Used for uplink power control. Typically, TPC RNTIs are assigned to a group of terminals and include the following three types: TPC-Physical uplink shared channel (PUSCH)-RNTI, TPC-Physical uplink control channel (PUCCH)-RNTI, and TPC-Sounding reference signal (SRS)-RNTI. They are carried to the terminals through the higher-layer signaling PhysicalCellGroupConfig.

[0122] Modulation and coding scheme C-RNTI (MSC-C-RNTI): This indicates the MCS table used by PUSCH / PDSCH and is carried to the terminal via higher-layer signaling PhysicalCellGroupConfig. MCS-C-RNTI is used to descramble PDCCH, and the MCS table to be used is determined based on the CRC check result.

[0123] Configured scheduling RNTI (CS-RNTI): Used for semi-persistent scheduling (SPS), it is carried to the terminal via higher-level signaling PhysicalCellGroupConfig. The start and release of SPS are determined by the result of descrambling DCI.

[0124] Interruption RNTI (INT-RNTI): RNTI used for scrambling DCI Format 2_1. Configured to the terminal via the higher-level signaling DownlinkPreemption.

[0125] Slot format indication RNTI (SFI-RNTI): An RNTI used for scrambling DCI Format 2_0 (carrying frame structure information). It is carried to the terminal via the higher-layer signaling slotFormatCombToAddModList.

[0126] Semi-persistent channel state information (RNTI, SP-CSI-RNTI): This indicates the reporting of semi-persistent CSI at the PUSCH and is transmitted to the terminal via higher-layer signaling PhysicalCellGroupConfig. The result of descrambling DCI determines whether CSI should be reported.

[0127] Inactive RNTI (I-RNTI): Carried in the UE-Identity information cell in the RAN-Paging message, used to wake up the UE in the INACTIVE state.

[0128] Currently, mobility management signaling is typically transmitted at the UE-specific level. To distinguish mobility management signaling associated with different UEs, the signaling may carry the UE's C-RNTI. For example, in cell handover, the terminal needs to exchange UE-specific C-RNTIs and handover signaling with the source base station, the source base station and the target base station, and the target base station and the core network, resulting in extremely high signaling overhead (e.g., tens of thousands of messages per second). Furthermore, due to the movement of satellites in the NTN, mobility scenarios such as cell handover occur more frequently. If the existing RNTI design and related configuration of the terrestrial network are used, it may lead to even greater signaling overhead and UE power consumption.

[0129] Based on this, this application provides a communication method in which the RNTI allocated by the network to a terminal may include two parts: one part is used to identify a user group (denoted as a first identifier), and the other part is used to identify terminals within that user group (denoted as a second identifier). Terminals belonging to the same user group are located in the same geographical area. Furthermore, the network associates the first identifier with first configuration information and manages second configuration information for the second identifier. The first and second configuration information are used for control channel detection. The specific implementation of this scheme will be described in detail in subsequent embodiments and will not be elaborated upon here.

[0130] Based on this scheme, since the RNTI allocated by the network includes the user group identifier, signaling overhead can be reduced compared to additionally allocating a group identifier outside the RNTI. Furthermore, because the RNTI includes the user group identifier, user group-based signaling configuration is enabled. For example, the network configures common mobility configuration information for a user group, and terminals within the user group can use a first identifier to obtain this common mobility configuration information, further reducing signaling overhead compared to terminal-level configuration. Moreover, the network sends configuration information separately to the user group and the terminals within the user group, performing differentiated control channel detection configuration. This allows for flexible configuration of the timing of control channel detection based on the frequency of common configuration and terminal-specific configuration, avoiding frequent control channel detection by terminals, reducing terminal detection overhead, and saving power.

[0131] The technical solutions of this application embodiment can be used in NTN systems such as satellite communication systems, high altitude platform station (HAPS) communication, and unmanned aerial vehicles (UAVs). Examples include integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS), and ultra-dense low-Earth orbit (LEO) satellite communication systems. NTN systems can be integrated with traditional mobile communication systems. For example, the mobile communication system can be a 4th generation (4G) communication system (e.g., Long Term Evolution (LTE) system), a worldwide interoperability for microwave access (WiMAX) communication system, a 5G communication system (e.g., NR system), a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) communication system, a vehicle-to-everything (V2X) communication system, and future mobile communication systems.

[0132] The communication systems described above are merely illustrative examples, and the communication systems and scenarios applicable to this application are not limited thereto. The communication systems and scenarios provided in this application do not impose any limitations on the solutions of this application. This is hereby stated uniformly and will not be repeated below.

[0133] As one possible implementation, the communication system applicable to the present application may include at least one terminal and at least one network device. For example, terminals may communicate with each other via wired or wireless means, as may a terminal communicate with a network device, and as may a network device communicate with each other.

[0134] Optionally, the terminal can be a user-side device with wireless transceiver capabilities, or a chip or chip system embedded in that device. The terminal can also be referred to as user equipment (UE), terminal, access terminal, user unit, user station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), user terminal, wireless communication equipment, user agent, or user device, etc. For example, the terminal can be a terminal in IoT, V2X, D2D, M2M, 5G networks, or future evolved public land mobile networks (PLMNs). The terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (such as on airplanes, balloons, and satellites).

[0135] For example, a terminal can be a drone, an IoT device (e.g., a sensor, an electricity meter, a water meter, etc.), a V2X device, a station (ST) in a wireless local area network (WLAN), a satellite phone, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smartphone, a wireless data card, a wireless modem, a machine-type communication device, a wireless local loop (WLL) station, a 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 (also known as a wearable smart device), a tablet or a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home. Wireless terminals (such as those in the home), vehicle-mounted terminals, vehicles with vehicle-to-vehicle (V2V) communication capabilities, intelligent connected vehicles, and drones with unmanned aerial vehicle (UAV) to UAV (U2U) communication capabilities, etc. Terminals can be mobile or fixed; this application does not specifically limit their location.

[0136] Optionally, the network device can be a network-side device with wireless transceiver capabilities, or it can be a chip, chip system, or module installed in the device. The network device is located in the radio access network (RAN) of the mobile communication system and is used to provide access services to terminals.

[0137] As one possible implementation, the network device can be a wireless relay node or a wireless backhaul node. For example, the network device can act as a Layer 1 relay device to regenerate physical layer signals (i.e., wireless frequency filtering, frequency conversion, and amplification processing) without having other higher protocol layers.

[0138] As another possible implementation, network equipment can perform some or all of the functions of a base station. For example, network equipment can be an evolved Node B (eNB or eNodeB) in LTE or evolved LTE-Advanced (LTE-A) systems, such as traditional macro base stations (eNBs) and micro base stations (eNBs) in heterogeneous network scenarios; or it can be a next-generation node B (gNodeB or gNB) in a 5G system; or it can be a transmission point (TP) or transmission reception point (TRP); or it can be a base station in a future evolved PLMN; or it can be one or a group of antenna panels of a base station; or it can be an access point (AP) in a wireless fidelity (WIFI) system; or it can be a device that performs network-side functions in IoT communication systems, V2X communication systems, D2D communication systems, M2M communication systems, or other communication systems; or it can be a radio controller in a cloud radio access network (CRAN) scenario. Optionally, network equipment can also be a server, wearable device, vehicle, or in-vehicle equipment, etc.

[0139] For example, the base station in the embodiments of this application may include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, access points, etc., and the embodiments of this application do not specifically limit them.

[0140] As another possible implementation, the network device may include at least one of the following: a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), a radio unit (RU), etc.

[0141] For example, the CU and DU can be configured separately or included in the same network element, such as in the baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0142] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an O-RAN central unit (O-CU), DU can also be called an O-RAN distributed unit (O-DU), CU-CP can also be called an O-RAN central unit control plane (O-CU-CP), CU-UP can also be called an O-RAN central unit user plane (O-CU-UP), and RU can also be called an O-RAN radio unit (O-RU). Any of the units CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0143] In one possible design, devices such as CU, DU, and RU can communicate with each other through open interfaces. For example, as shown in Figure 4, CU-CP and DU communicate via the F1-C interface, CU-UP and DU communicate via the F1-U interface, DU and RU communicate via the fronthaul interface, DU and terminals communicate via the air interface, and CU and core network devices communicate via the NG interface. Furthermore, core network devices and network devices can connect to the Operation Administration and Maintenance (OAM) system.

[0144] Furthermore, O-RAN utilizes artificial intelligence (AI) technology to integrate the RAN intelligent controller into the RAN, enabling real-time monitoring, optimization, and management of the RAN. As shown in Figure 4, the RIC can be further divided into non-real-time RIC (Non-RT RIC or NRT RIC) and near-real-time RIC (Near-RT RIC or nRT RIC).

[0145] Non-real-time RICs are used to implement non-real-time intelligent management of the RAN, processing non-real-time information, such as latency-insensitive data with latency in the order of seconds. They can also implement AI / machine learning (ML) including model training and updates, and guide applications / functions in near-real-time RICs based on policies. Near-real-time RICs are used to implement near-real-time intelligent management of the RAN, processing near-real-time information, such as latency-sensitive data with latency in the order of tens of milliseconds. They can also achieve near-real-time control and optimization of O-RAN modules and resources through data collection and related operations on the E2 interface.

[0146] In this embodiment, the apparatus for implementing the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing those functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, the example of a network device being used to implement the functions of a network device is provided only and does not constitute a limitation on the solutions described in this embodiment.

[0147] Optionally, the network devices in this application embodiment can be deployed on non-terrestrial platforms, such as low-altitude platforms (e.g., drones), high-altitude platforms (e.g., aircraft), or satellites. Therefore, the network devices in this application embodiment can also be referred to as non-terrestrial network devices.

[0148] For example, the satellite can be a LEO satellite, MEO satellite, GEO satellite, or non-geostationary earth orbit (NGEO) satellite, etc., without limitation. The satellite can provide communication services, navigation services, positioning services, etc., to the terminal through multiple beams. The satellite can use multiple beams to cover the service area, and different beams can communicate through one or more of the following methods: time division, frequency division, and space division.

[0149] Optionally, the satellite can operate in transparent or regenerative mode. Transparent mode, also known as bend-tube relay transmission, means that the signal only undergoes frequency conversion and amplification on the satellite; the satellite is transparent to the signal, as if it doesn't exist. Regenerative mode, also known as non-transparent (on-board access / processing) transmission, means that the satellite has some or all of the base station functions. A particular satellite may support only transparent mode, only regenerative mode, or both, and can switch between the two modes. Furthermore, the satellite can operate in staring mode or non-staring mode.

[0150] Optionally, the satellite can wirelessly communicate with ground equipment. For example, the ground equipment can be devices within the core network (CN) of an existing or future mobile communication architecture (such as the 3GPP access architecture). The core network, as the bearer network, provides the interface to the data network, offering terminals communication connectivity, authentication, management, policy control, and the ability to bear data services. The CN can further include: access and mobility management function (AMF) network elements, session management function (SMF) network elements, authentication server function (AUSF) network elements, policy control function (PCF) network elements, user plane function (UPF) network elements, and so on.

[0151] For example, a satellite can wirelessly communicate with ground equipment via an NTN gateway (or gateway station). The link between the satellite and the NTN gateway can be called a feeder link.

[0152] As a possible example, Figure 5 illustrates the architecture of a possible mobile satellite communication system to which this application applies. The system includes at least one satellite, with satellites 101, 102, and 103 used as examples in Figure 5. The satellites can provide communication and other services to terminals via multiple beams. The ellipses identifying the beams in Figure 5 can be understood as representing the coverage area of ​​the beams.

[0153] For example, satellites 101 and 102 can operate in regeneration mode, and satellite 103 can operate in transparent transmission mode. There is an inter-satellite link 01 between satellites 101 and 102, and an inter-satellite link 02 between satellites 102 and 103. Satellite 103 is connected to the ground core network equipment.

[0154] It should be noted that the satellite mentioned in the embodiments of this application may be a satellite base station, or may include an orbital receiver or repeater for relaying information, or a network-side device mounted on a satellite.

[0155] It is understood that the satellites in the embodiments of this application can be replaced with network-side equipment mounted on other flight platforms such as drones and airplanes.

[0156] It should be noted that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0157] The following description, using the communication system described above as an example, illustrates the communication method provided in the embodiments of this application through the interaction between network devices and terminals.

[0158] It should be noted that in the following embodiments of this application, the message names between various devices, the names of various parameters, or the names of various information are just examples. Other names may also be used in other embodiments, and the method provided in this application does not specifically limit them.

[0159] It is understood that in the embodiments of this application, the network device or terminal may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the various steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0160] As an example, the following embodiments use the aforementioned flight platform as a satellite, specifically satellite communication in NTN, for illustration. Of course, this method can also be applied to other scenarios in NTN, such as LAP subnetworks or HAP subnetworks, and is not specifically limited thereto.

[0161] The communication method provided in the embodiments of this application will be described below based on the above-described communication system. Referring to Figure 6, which is a flowchart of a communication method provided in an embodiment of this application, the communication method may include the following steps:

[0162] S601, the first network device sends a first RNTI to the first terminal. Correspondingly, the first terminal receives the first RNTI from the first network device.

[0163] The first RNTI includes a first identifier and a second identifier. The first identifier identifies the first user group, and the second identifier identifies the first terminal within the first user group. That is, the first identifier is the identifier of the first user group, and the second identifier is the identifier of the first terminal within the first user group. Terminals belonging to the first user group are located in the same geographical area.

[0164] In one possible implementation, the first RNTI is an enhanced RNTI. The enhanced RNTI includes two parts: an identifier for the user group and an identifier for each terminal within the user group. Terminals belonging to the same user group are located in the same geographical area. For example, the identifier for the user group can be understood as a shared identifier for terminals within the user group. The identifier for each terminal within the user group can be understood as a terminal-specific identifier.

[0165] Optionally, in addition to the user group identifier and the identifiers of the terminals within the user group, the enhanced RNTI may also include other bits, such as reserved bits, which can be used for future expansion. In the following embodiments of this application, unless otherwise specified, the enhanced RNTI is described as including only the user group identifier and the identifiers of the terminals within the user group.

[0166] In one possible implementation, as shown in Figure 7, the length of the enhanced RNTI is X+Y bits, the length of the user group identifier is X bits, and the length of the identifier of the terminal within the user group is Y bits, where X and Y are positive integers. The length of RNTI / user group identifier / identifier of the terminal within the user group can be understood as: the number of bits occupied by RNTI / user group identifier / identifier of the terminal within the user group.

[0167] As one possible implementation, the length of the enhanced RNTI, or X+Y, can be any of the following: 16 bits, 24 bits, 29 bits, 32 bits, 40 bits, 48 ​​bits, 56 bits, or 64 bits. Of course, the length of the enhanced RNTI can also be other values, and this application does not specifically limit this.

[0168] As one possible implementation, the values ​​of X and Y can be predefined by the protocol; or, the values ​​of X and Y can be dynamically indicated by the network, for example, the network can indicate the values ​​of X and / or Y.

[0169] It should be noted that this application does not limit the order or position of the user group identifier and the identifiers of the terminals within the user group in the enhanced RNTI. For example, the user group identifier may precede the identifiers of the terminals within the user group, or vice versa; there is no restriction.

[0170] In one possible implementation, when terminals belonging to the same user group are located in the same geographical area, the identifier of the user group in the enhanced RNTI can be the identifier of the geographical area, or the identifier of the user group can also be understood as the area identifier.

[0171] As one possible implementation, the geographic region can also be called a "wave position," "broadcast wave position," "geographic grid," etc. Of course, other names are also possible, and this application does not specifically limit the name of the geographic region.

[0172] In one possible implementation, the network can flexibly set the values ​​of X and / or Y to adapt to the needs of different geographical radii or different network deployments.

[0173] In one possible implementation, the first network device can assign enhanced RNTIs to multiple terminals within its coverage area. Specifically, different terminals located in the same geographical area share the same user group identifier, while at least one terminal in the same geographical area has different identifiers within its user group. Conversely, different terminals located in different geographical areas have different user group identifiers, and the identifiers within a user group can be the same or different. Therefore, different terminals have different enhanced RNTIs; thus, a terminal's RNTI can also be understood as a terminal's unique identifier within the network.

[0174] For example, as shown in Figure 8, if UE1 and UE2 are located in geographical region SC#i, then UE1 and UE2 have the same user group identifier (i.e., the same X bit value), but different identifiers within the user group (i.e., different Y bit values). For instance, the X bit value of UE1 and UE2 is X = 00 00001 00, the Y bit value of UE1 is Y = 00 00001, and the Y bit value of UE2 is Y = 00 00011.

[0175] Furthermore, since UE3 is located in geographical region SC#j, the user group identifier of UE3 is different from that of UE1 / UE2 (i.e., the value of the X bit is different). The identifier of UE3 within the user group may be the same as or different from that of UE1 / UE2 within the user group. For example, the value of the X bit of UE3 is X = 10 00100 11, and the value of the Y bit of UE3 is Y = 01 01000.

[0176] It is worth noting that although the enhanced RNTI can include the identifier of the user group and the identifier of the terminal within the user group, the complete RNTI value is still the identifier corresponding to the value of the X+Y bits.

[0177] In one possible implementation, the enhanced RNTI in the embodiments of this application can be a C-RNTI, TC-RNTI, CS-RNTI, or RA-RNTI. Of course, the enhanced RNTI can also be other RNTIs, such as TPC-RNTI, etc., and is not limited to the above-mentioned types of RNTIs. This application does not make specific limitations in this regard.

[0178] S602, the first network device sends first configuration information and second configuration information. Correspondingly, the first terminal receives the first configuration information and second configuration information from the first network device.

[0179] Here, the first identifier is associated with the first configuration information, and the second identifier is associated with the second configuration information. That is, the first configuration information can be understood as the public configuration information of the first user group, and the second configuration information can be understood as the private configuration information of the first terminal.

[0180] As one possible implementation, the first configuration information and the second configuration information can be used for control channel detection. For example, the control channel can be a physical downlink control channel (PDCCH) or a multicast / broadcast services (MBS) control channel (MCCH).

[0181] As one possible implementation, the association between the first identifier and the first configuration information can be achieved by: the first configuration information including the first identifier, or the first configuration information being scrambled with the first identifier. The association method between the second identifier and the second configuration information can be referenced from the association method between the first identifier and the first configuration information, and will not be elaborated here.

[0182] S603, The first terminal performs control channel detection based on the first configuration information and the second configuration information.

[0183] For example, the first terminal performs public PDCCH detection based on the first configuration information. The public PDCCH may carry the public configuration of the first user group or schedule the public physical downlink shared channel (PDSCH) of the first user group. Alternatively, the first terminal performs dedicated PDCCH detection based on the second configuration information. The dedicated PDCCH may carry the dedicated configuration of the first terminal or schedule the dedicated PDSCH of the first terminal.

[0184] Based on this scheme, since the RNTI allocated by the network includes the user group identifier, signaling overhead can be significantly reduced compared to additionally allocating a group identifier outside the RNTI. Furthermore, because the RNTI includes the user group identifier, user group-based signaling configuration is enabled. For example, the network configures common mobility configuration information for a user group, and terminals within the user group can use a first identifier to obtain this common mobility configuration information, further reducing signaling overhead compared to terminal-level configuration. Moreover, the network sends configuration information separately to the user group and the terminals within the user group, performing differentiated control channel detection configuration. This allows for flexible configuration of the timing of control channel detection based on the frequency of common configuration and terminal-specific configuration, avoiding frequent control channel detection by terminals, reducing terminal detection overhead, and saving power.

[0185] The overall flow of the communication method provided in this application has been described above. The first and second configuration information will now be described in detail. For example, the first and second configuration information can be implemented in three ways: Method 1, Method 2, and Method 3.

[0186] Method 1: The first configuration information is used to configure the first search space (SS), and the second configuration information is used to configure the second search space.

[0187] In other words, the first search space is associated with the first identifier, or the first search space is the common search space (CSS) or group search space (GSS) of the first user group. The second search space is the UE-specific search space (USS) of the first terminal. That is, the search spaces associated with the first identifier and the second identifier are different.

[0188] As one possible implementation, the search space encapsulates information such as the starting orthogonal frequency division multiplexing (OFDM) symbol for detecting the PDCCH, the detection period, and the associated control resource set (CORESET). The CORESET encapsulates information such as the frequency domain resources of the PDCCH and the number of OFDM symbols occupied in the time domain. Based on the search space and the CORESET, the terminal can determine the time-frequency resources of the PDCCH. For example, some important parameters of the search space include:

[0189] Search Space Identifier (searchSpaceId): Used to identify the search space. Each bandwidth part (BWP) can contain a maximum of 10 search spaces (including the initial search space), and each search space identifier is unique within a BWP.

[0190] CORESET identifier (controlResourceSetId): The CORESET associated with the search space, allowing the terminal to blindly detect the PDCCH within the time-frequency domain range indicated by the CORESET.

[0191] Monitoring Slot Periodicity and Offset: This indicates the detection period and time offset. The detection period is the period during which the PDCCH is detected, and the time offset is the offset between the start of the detection slot and the beginning of the detection period. The units for the detection period and time offset can be slots, seconds, milliseconds, etc., without restriction.

[0192] Duration: Indicates the duration of detection. For example, detection duration can be understood as the number of time slots for continuous detection of the PDCCH within a detection period. Detection duration is less than the detection period.

[0193] Monitoring Symbols Within Slot: Within each slot, the starting OFDM symbol of the PDCCH is detected. A 14-bit bitmap is used, with the highest bit representing the first OFDM symbol within the slot.

[0194] Search Space Type: Includes public search space / group search space and UE-specific search space.

[0195] For example, assuming a detection period of 10 time slots, a time offset of 5 time slots, a detection duration of 1 time slot, a search space associated CORESET indicating a time domain symbol count of 2, and the starting OFDM symbols for PDCCH detection being OFDM symbols 0 and 7. Therefore, under this configuration, the terminal will detect PDCCH in symbols 0, 1, 7, and 8 of time slot 5 in each detection period.

[0196] The first search space and the second search space have different temporal locations. For example, the first search space and the second search space differ in at least one of the following: detection period, time offset, or detection duration. For instance, the detection period of the first search space is greater than the detection period of the second search space, and / or the detection duration of the first search space is greater than the detection duration of the second search space.

[0197] For example, as shown in Figure 9, the detection period for the first search space associated with the first identifier is 10s / 20s / 40s / 80s, etc., and the detection duration is 1s / 2s, etc. The monitoring period for the second search space associated with the second identifier is up to 2560 time slots, for example, it can be 1 time slot, 2 time slots, etc., and the detection duration is in the millisecond range.

[0198] Optionally, other parameters such as CORESET associated with the first search space and the second search space can be the same or different, and this application does not make specific limitations on this.

[0199] As one possible implementation, the network can be configured independently using first configuration information and second configuration information. For example, the first configuration information includes at least one of the following: a detection period (denoted as detection period 1), a time offset (denoted as time offset 1), or a detection duration (denoted as detection duration 1) for the first search space; the second configuration information includes at least one of the following: a detection period (denoted as detection period 2), a time offset (denoted as time offset 2), or a detection duration (denoted as detection duration 2) for the second search space.

[0200] Optionally, the first configuration information can also configure other parameters of the first search space, such as the associated CORESET, search space type, etc., and the second configuration information can also configure other parameters of the second search space.

[0201] As another possible implementation, the network can configure one of a first search space and a second search space, and then configure a scaling factor. The other search space can be obtained by scaling the configured search space using the scaling factor. For example, the second configuration information may include at least one of the following: detection period, time offset, or detection duration of the second search space. The first configuration information may include a scaling factor used to scale the second search space to obtain the first search space. For example, the detection period of the first search space may be the product of the detection period of the second search space and the scaling factor. For example, the scaling factor can take values ​​such as {1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024}.

[0202] As another possible implementation, the network can configure different search space types for the first and second search spaces to achieve different temporal locations for the first and second search spaces. For example, the first search space can be configured as a group search space, and the second search space can be configured as a terminal-specific search space.

[0203] In this mode, the control channel can be PDCCH.

[0204] As one possible implementation, the first terminal performing control channel detection based on the first configuration information may include: the first terminal determining a first search space based on the first configuration information, and performing PDCCH blind detection using a first identifier or a third identifier in the first search space. The third identifier has the same length as the first RNTI, and includes the first identifier and a preset value. For example, the preset value can be all zeros; that is, the third identifier can be obtained by setting the bits occupied by the second identifier in the first RNTI to the preset value (e.g., all zeros).

[0205] As one possible implementation, the first terminal performs control channel detection based on the second configuration information, which may include: the first terminal determining a second search space based on the second configuration information, and performing PDCCH blind detection using a second identifier or a first RNTI in the second search space.

[0206] For example, the first terminal can perform blind PDCCH detection using a first identifier in a first search space, and a second identifier or a first RNTI in a second search space. The PDCCH blindly detected in the first search space can be understood as a public PDCCH, and the PDCCH blindly detected in the second search space can be understood as a terminal-specific PDCCH. Based on this, identifiers of different lengths can be used to perform blind detection of the public PDCCH and the terminal-specific PDCCH respectively, simplifying implementation and reducing terminal implementation complexity.

[0207] Alternatively, for example, the first terminal can perform blind PDCCH detection using a third identifier in a first search space and a first RNTI in a second search space. Based on this, identifiers of the same length can be used to perform blind detection of public PDCCH and terminal-specific PDCCH respectively, and blind PDCCH detection can be performed based on the same criteria.

[0208] As one possible implementation, performing blind PDCCH detection in the search space can be understood as performing blind PDCCH detection at the corresponding time-frequency domain location in the search space. For example, the frequency domain location can be determined based on the CORESET associated with the search space, and the time domain location can be determined based on the CORESER associated with the search space, as well as the detection period, time offset, and detection duration indicated by the search space.

[0209] As one possible implementation, Figure 10 illustrates the PDCCH processing procedure on the network device side. This process includes the following steps: 1. Information element multiplexing; 2. Cyclic redundancy check (CRC) attachment; 3. Channel coding; 4. Rate matching; 5. Scrambling; 6. Modulation; 7. Resource element mapping. The PDCCH detection process on the terminal side is the reverse of the process shown in Figure 10.

[0210] In the processing flow shown in Figure 10, the RNTI can be used as the CRC mask in step 2, or it can be used to determine the scrambling code in step 5. Therefore, the first terminal performing blind PDCCH detection in the first search space using the first identifier or the third identifier can include: the first terminal using the first identifier / third identifier as a mask and scrambling code to detect the PDCCH in the first search space; the first terminal performing blind PDCCH detection in the second search space using the second identifier or the first RNTI can include: the first terminal using the second identifier / first RNTI as a mask and scrambling code to detect the PDCCH in the second search space.

[0211] In one possible implementation, if the first terminal detects a PDCCH in the first search space, it parses the public configuration associated with the first identifier carried in the PDCCH, or receives the public information associated with the first identifier according to the scheduling of the PDCCH. If the first terminal detects a PDCCH in the second search space, it parses the private configuration associated with the second identifier carried in the PDCCH, or receives the private information associated with the second identifier according to the scheduling of the PDCCH.

[0212] Based on the first method described above, differentiated configuration of the search space can reduce the blind detection overhead of the terminal, improve energy efficiency, and save power consumption. For example, the common configuration information of user groups appears every tens or even hundreds of seconds, while the granularity of user data scheduling of the terminal is at the transmission time interval (TTI) level, typically 1ms or even lower. If the first and second identifiers are associated with the same search space, and if a small detection period is configured to ensure that the terminal's data reception is consistently received, the terminal will frequently perform detection of the common PDCCH. However, the common PDCCH appears infrequently, and the terminal will not be able to detect it in every detection, thus wasting the terminal's power consumption. The differentiated configuration based on the search space in this application can avoid this problem.

[0213] In one possible implementation, this application also provides an RNTI usage rule.

[0214] As one possible implementation, as shown in Figure 11, the usage rules include: for the group search space / public search space, using the first identifier as the group RNTI (G-RNTI); for the terminal-specific search space, using the second identifier or the first RNTI as the C-RNTI. That is, using the first identifier to perform blind PDCCH detection in the group search space / public search space, and using the second identifier / first RNTI to perform blind PDCCH detection in the terminal-specific search space.

[0215] As another possible implementation, as shown in Figure 11, the usage rules include: for the group search space / public search space, a third identifier is used as the G-RNTI; for the terminal-specific search space, a first RNTI is used as the C-RNTI. That is, the third identifier is used for blind PDCCH detection in the group search space / public search space, and the first RNTI is used for blind PDCCH detection in the terminal-specific search space. The third identifier can be found in the relevant descriptions above and will not be repeated here.

[0216] It should be noted that the above RNTI usage rules can be used alone or in combination with the above method. For example, the first terminal uses the first identifier or the third identifier in the first search space to perform blind PDCCH detection, and uses the second identifier or the first RNTI in the second search space to perform blind PDCCH detection.

[0217] Based on the constraints of the above RNTI usage rules, the terminal can use the corresponding identifier as the RNTI for PDCCH detection for a specific type of search space, avoiding the terminal using an identifier different from the network for PDCCH detection, thereby improving the success rate of PDCCH detection and communication success rate.

[0218] Method 2: The first configuration information is used to configure the first discontinuous reception (DRX) pattern, and the second configuration information is used to configure the second DRX pattern.

[0219] In other words, the first DRX pattern is associated with the first identifier, and the second DRX pattern is associated with the second identifier. That is, the DRX patterns associated with the first identifier and the second identifier are different.

[0220] As one possible implementation, as shown in Figure 12, the DRX pattern includes an on-duration period and a sleep period. The sum of the on-duration and sleep periods constitutes the DRX pattern. During the on-duration period, the terminal wakes up and checks the PDCCH; during the sleep period, the terminal remains asleep and does not check the PDCCH.

[0221] The first DRX pattern and the second DRX pattern differ in at least one of the following: DRX period, activation duration, or DRX timer. The DRX timer may include, but is not limited to, the DRX retransmission timer, the DRX inactive state timer, etc.

[0222] For example, the DRX retransmission timer may include a DRX downlink retransmission timer and / or a DRX uplink retransmission timer. During the operation of the DRX downlink retransmission timer, the terminal detects the control channel, and if the terminal receives the corresponding downlink scheduling information or downlink configuration authorization, it stops the DRX downlink retransmission timer. During the operation of the DRX uplink retransmission timer, the terminal detects the control channel, and if the terminal receives the corresponding uplink scheduling information or uplink configuration authorization, it stops the DRX uplink retransmission timer.

[0223] For example, the DRX inactive state timer starts after the terminal detects the control channel or receives the PDCCH for new data scheduling. The duration of the DRX inactive state timer can be understood as the number of subframes that the terminal needs to continue detecting after successfully decoding the DCI carried by the PDCCH.

[0224] For example, the period of the first DRX pattern is greater than the period of the second DRX pattern, and / or the activation duration of the first DRX pattern is greater than the activation duration of the second DRX pattern. For instance, as shown in Figure 12, the period of the first DRX pattern can be 10s / 20s / 40s / 80s, etc., and the activation duration can be 1s / 2s, etc. The period of the second DRX pattern can be 1s / 2s / 4s / 8s, etc., and the activation duration can be 10ms / 20ms, etc.

[0225] As one possible implementation, the network can be configured independently using first configuration information and second configuration information. For example, the first configuration information includes the period and / or activation duration of a first DRX pattern, and the second configuration information includes the period and / or activation duration of a second DRX pattern.

[0226] As another possible implementation, the network can be configured with one of the first and second DRX patterns, and then a scaling factor can be configured. The other DRX pattern can be obtained by scaling the configured DRX pattern using the scaling factor. Please refer to the relevant descriptions of the configuration of the first and second search spaces mentioned above, which will not be repeated here.

[0227] In this second method, the control channel can be PDCCH.

[0228] As one possible implementation, the first terminal performs control channel detection based on the first configuration information, which may include: the first terminal determining a first DRX pattern based on the first configuration information, and performing PDCCH blind detection using a first identifier or a third identifier during the activation duration of the first DRX pattern. The third identifier can be referred to the description in Method 1 above, and will not be repeated here.

[0229] As one possible implementation, the first terminal performs control channel detection based on the second configuration information, which may include: the first terminal determining a second DRX pattern based on the second configuration information, and performing PDCCH blind detection using a second identifier or a first RNTI during the activation duration of the second DRX pattern.

[0230] For example, the first terminal may perform blind PDCCH detection using a first identifier during the activation duration of the first DRX pattern, and perform blind PDCCH detection using a second identifier or a first RNTI during the activation duration of the second DRX pattern. Alternatively, the first terminal may perform blind PDCCH detection using a third identifier during the activation duration of the first DRX pattern, and perform blind PDCCH detection using a first RNTI during the activation duration of the second DRX pattern.

[0231] As one possible implementation, the first terminal can use the identifier to perform blind PDCCH detection within the activation duration of the DRX pattern. For the implementation of blind PDCCH detection using the identifier within the search space in Method 1 above, please refer to the relevant description. It will not be repeated here.

[0232] In one possible implementation, the first configuration information is further used to configure a wake-up signal (WUS) associated with the first identifier, for example, configuring the time-frequency position of the wake-up signal. The wake-up signal associated with the first identifier can also be understood as a wake-up signal associated with the first DRX pattern.

[0233] As one possible implementation, WUS is sent before the DRX pattern. As shown in Figure 13, if a wake-up signal associated with the first identifier exists (or the first terminal detects) it indicates that there is a subsequent public PDCCH or user group data scheduling, and the first terminal performs a blind PDCCH check within the activation duration of the first DRX pattern; if a wake-up signal associated with the first identifier does not exist (or the first terminal does not detect) it indicates that there is no subsequent public PDCCH or user group data scheduling, and the first terminal does not perform a blind PDCCH check within the activation duration of the first DRX pattern and remains in sleep mode.

[0234] In other words, in this scenario, the first terminal performs control channel detection based on the first configuration information, which may include: the first terminal determining the time-frequency location of the WUS associated with the first identifier and the first DRX pattern based on the first configuration information. If the WUS associated with the first identifier is detected at the time-frequency location of the WUS, blind PDCCH detection is performed using either the first identifier or the third identifier during the active duration of the first DRX pattern; if the WUS associated with the first identifier is not detected at the time-frequency location of the WUS, blind PDCCH detection is not performed during the active duration of the first DRX pattern, for example, the terminal remains in a dormant state during the active duration.

[0235] In one possible implementation, if the first terminal detects a PDCCH during the activation duration of the first DRX pattern, it parses the common configuration associated with the first identifier carried in the PDCCH, or receives the common information associated with the first identifier according to the scheduling of the PDCCH. If the first terminal detects a PDCCH during the activation duration of the second DRX pattern, it parses the special configuration associated with the second identifier carried in the PDCCH, or receives the special information associated with the second identifier according to the scheduling of the PDCCH.

[0236] Based on the second method described above, different DRX patterns can be associated with user group identifiers and the identifiers of terminals within the user group, enabling differentiated configuration of DRX patterns. Compared to associating the same DRX pattern with user group identifiers and the identifiers of terminals within the user group, this reduces the blind detection overhead of the terminal and saves the terminal's power consumption.

[0237] In one possible implementation, Method 1 and Method 2 described above can be combined. For example, the first configuration information is used to configure the first search space and the first DRX pattern, and the second configuration information is used to configure the second search space and the second DRX pattern. Accordingly, the first terminal performs PDCCH blind detection within the first search space during the activation duration of the first DRX pattern, and performs PDCCH blind detection within the second search space during the activation duration of the second DRX pattern. Of course, Method 1 and Method 2 described above can also be executed independently, without dependence on each other.

[0238] Method 3: The first configuration information is used to configure multicast / broadcast service (MBS), and the second configuration information is used to configure unicast service.

[0239] In other words, the first identifier is associated with MBS, or rather, the first identifier can serve as the identifier for MBS, i.e., the first identifier can serve as G-RNTI. The second identifier is associated with unicast services. That is, the first and second identifiers are associated with different service types.

[0240] As one possible implementation, the first configuration information is used to configure the MBS, which can be understood as: the first configuration information is used to configure the MBS control channel, that is, to configure the MCCH. For example, the first configuration information can be the configuration information of the MCCH.

[0241] The MCCH is used to transmit control information, which may include configuration information for the MBS traffic channel (MTCH). The MTCH is used to transmit MBS data. At the physical layer, the MCCH and MBS can be carried in the PDSCH.

[0242] For example, the configuration information of MCCH may include the MCCH repetition period (RP), offset (mcch-Offset), transmission time (mcch-duration), modification period (MP), etc.

[0243] For example, the configuration information of MTCH in MCCH can be at the MBS granularity, that is, the configuration of MTCH is per service level. Each MBS can be associated with a first identifier (as G-RNTI). The configuration information of MTCH may include the first identifier (as G-RNTI), DRX parameters, temporary multicast group identifier (TMGI), and the PDSCH configuration corresponding to MTCH, etc.

[0244] In this third method, the common control channel can be the MCCH. That is, the first terminal performs control channel detection according to the first configuration information, which may include: the first terminal detecting the MCCH according to the first configuration information. For example, the first terminal determines the time-frequency position of the MCCH according to the first configuration information, and uses the first identifier to detect the MCCH at that time-frequency position, such as detecting whether there is an MCCH associated with the first identifier at that time-frequency position.

[0245] Optionally, if the first terminal detects the MCCH based on the first configuration information, it can obtain the configuration information of the MTCH carried in the MCCH, and receive the MBS data associated with the first identifier carried in the MTCH based on the configuration information of the MTCH.

[0246] As one possible implementation, in this embodiment, the MBS can support multicast / multicast signaling functions. For example, network devices can send (e.g., broadcast or multicast) control signaling associated with the MBS, and correspondingly, the first terminal can receive the control signaling associated with the MBS. Exemplarily, this signaling can be signaling during cell handover, such as RRC reconfiguration signaling, satellite ephemeris information, timing information, scheduling information, etc. Of course, it can also be other control signaling associated with the MBS, and this application does not specifically limit this.

[0247] As one possible implementation, the second configuration information is used to configure unicast services. This can be understood as: the second configuration information configures the terminal-specific search space, control resource set (CORESET), etc., for detecting terminal-specific data services, i.e., unicast services. The first terminal performs control channel detection based on the second configuration information, which may include: the first terminal performing blind PDCCH detection based on the search space, control resource set, and DCI format configured in the second configuration information to determine whether there is subsequent scheduling information for terminal-specific data services. If scheduling information exists (e.g., PDCCH is detected), then unicast service data is further received on the PDSCH / PUSCH indicated by the scheduling information.

[0248] Based on the above method three, control channel detection configurations can be performed separately for MBS associated with the first identifier and unicast services associated with the second identifier, achieving differentiated configurations for control channel detection for different service types. Compared to performing the same control channel detection configuration for MBS and unicast services, this avoids the terminal frequently detecting the control channel associated with MBS, thereby reducing the terminal's detection overhead and saving terminal power consumption.

[0249] In one possible implementation, after the first terminal performs detection based on the first configuration information or the second configuration information, it may detect a control channel, which may carry information for scheduling medium access control (MAC) protocol data units (PDUs).

[0250] For example, a MAC PDU consists of one or more MAC subPDUs. For instance, a MAC subPDU might consist of a MAC header and a MAC SDU, or it might consist of a MAC header and a MAC CE. The size of the MAC SDU is variable. Some MAC CEs have a fixed size, while others have a variable size.

[0251] For example, Figure 14(a) shows a schematic diagram of a downlink (DL) MAC PDU structure. The MAC subPDU containing the MAC CE is placed before the MAC subPDU containing the MAC SDU and the MAC subPDU containing padding. Each MAC subPDU contains a MAC subheader and either a MAC CE or a MAC SDU or padding. For example, the MAC subheader consists of the header field R / F / LCID / (eLCID) / L, or the header field R / LCID / (eLCID).

[0252] LCID: Logical Channel Identification (LCID) field, used to indicate the logical channel of the MAC SDU corresponding to the MAC subheader, or to indicate the type of the MAC CE corresponding to the MAC subheader, or to indicate the padding corresponding to the MAC subheader.

[0253] eLCID: Extended Logical Channel Identifier field, used to indicate the logical channel of the MAC SDU corresponding to the MAC subheader, or to indicate the type of the MAC CE corresponding to the MAC subheader, with a size of 8 bits or 16 bits. The eLCID field is optional.

[0254] L: Length field, used to indicate the number of bytes in the MAC SDU corresponding to the MAC subheader, or the number of bytes in the variable-size MAC CE corresponding to the MAC subheader. The size of the L field is indicated by the F field.

[0255] F: Format field, used to indicate the size of the length field L. The size of the F field is 1 bit, a value of 0 indicates that the size of the L field is 8 bits, and a value of 1 indicates that the size of the L field is 16 bits.

[0256] R: Reserved bit, set to 0.

[0257] As one possible implementation, the MAC PDU for control channel scheduling detected by the first terminal may be a multi-user multiplexed MAC PDU. For example, as shown in Figure 14(b), the multi-user multiplexed MAC PDU carries common information associated with the user group and private information associated with at least one terminal in the user group.

[0258] In this scenario, the position of the MAC subPDU carrying public information associated with a user group in the multi-user multiplexed MAC PDU can be predefined by the protocol or indicated by the network; the position of the MAC subPDU carrying the private information of a terminal in the multi-user multiplexed MAC PDU can be determined according to a preset rule, which is related to the identifier of the terminal, and the preset rule can be predefined by the protocol or indicated by the network.

[0259] The MAC subPDU can be either a MAC CE or a MAC SDU. This means that public information for the user group can be carried in a MAC CE and / or a MAC SDU, and the terminal's private information can also be carried in a MAC CE and / or a MAC SDU. The following embodiments use a MAC SDU as an example for illustration.

[0260] Taking the first terminal's detected control channel scheduling multi-user multiplexed MAC PDU as an example:

[0261] As one possible implementation, the public information associated with the first identifier can be carried in the first MAC subPDU of the first MAC PDU; or, the public information associated with the first identifier can be carried in the first X MAC subPDUs of the first MAC PDU, where X is a positive integer greater than 1. Here, X can be predefined by the protocol, or it can be indicated by the network.

[0262] As one possible implementation, the index of the MAC subPDU containing the private information of the first terminal associated with the second identifier in the first MAC PDU is determined based on a preset rule, which is related to the second identifier. For example, the preset rule may include: the index of the MAC subPDU containing the private information of the first terminal associated with the second identifier in the first MAC PDU is the sum of K and the second identifier; or, the starting position of the MAC subPDU in the first MAC PDU is the sum of K and the second identifier; or, the index of the MAC subPDU in other MAC subPDUs besides those carrying public information is the sum of K and the second identifier; or, the starting position of the MAC subPDU in other MAC subPDUs besides those carrying public information is the sum of K and the second identifier. Here, K is a positive integer, and the preset rule may be predefined by the protocol or indicated by the network.

[0263] Taking the location of a MAC subPDU carrying public information associated with a user group within the first MAC PDU, and / or the location of a MAC subPDU carrying private information of the first terminal within the first MAC PDU as an example, the first network device may send third configuration information and / or fourth configuration information. The third configuration information is used to configure the location of public information associated with the first identifier within the first MAC PDU, and the fourth configuration information is used to configure the location of private information associated with the second identifier within the first MAC PDU, the location of which is related to the second identifier.

[0264] As one possible implementation, the third configuration information can indicate that the public information associated with the first identifier is carried in the first MAC subPDU of the first MAC PDU. In this case, the third configuration information can be carried in the control channel detected by the first terminal based on the first configuration information.

[0265] As another possible implementation, the third configuration information may indicate the number X of MAC subPDUs occupied by the public information associated with the first identifier. For example, the third configuration information may be carried in the subheader of the first MAC subPDU of the first MAC PDU, indicating that the public information associated with the first identifier occupies the first X MAC subPDUs of the first MAC PDU.

[0266] As another possible implementation, the third configuration information can be carried in the sub-header of the first X MAC subPDUs of the first MAC PDU, indicating whether the information carried by the MAC subPDU is public information associated with the first identifier. For example, the third configuration information can be a 1-bit indicator. If this 1-bit is set to a first value, it indicates that the information carried by the current MAC subPDU (i.e., the MAC subPDU containing the third configuration information) is public information associated with the first identifier; if this 1-bit is set to a second value, it indicates that the information carried by the current MAC subPDU is not public information associated with the first identifier. For example, the first value can be 1, and correspondingly, the second value can be 0; or, the first value can be 0, and correspondingly, the second value can be 1.

[0267] As one possible implementation, the fourth configuration information can indicate a preset rule, such as the aforementioned K. The fourth configuration information can be carried in the control channel detected by the first terminal based on the second configuration information.

[0268] As one possible implementation, the private information of the first terminal can be encrypted or scrambled using a second identifier or a first RNTI to prevent the private information of the first terminal from being obtained by other terminals.

[0269] As one possible implementation, the public information associated with the first identifier can be public mobility management auxiliary information, such as including but not limited to: reference location, distance threshold, measurement configuration (such as SSB measurement timing configuration (SMTC) and offset), synchronization or access information after handover, transmission configuration indication (TCI) status information associated with beam switching, channel state information (CSI) resource set information, or L1 / L2 triggered mobility (LTM) configuration information.

[0270] The dedicated information associated with the second identifier can be mobility management auxiliary information specific to the first terminal, such as including but not limited to: the first terminal's security information, capability information, handover time information, and dedicated random access timing (RACH Occasio, RO) information. Here, RACH refers to the random access channel.

[0271] Of course, the public information associated with the first identifier and the private information associated with the second identifier may also be other information, and this application does not limit the specific content of such information.

[0272] Based on the above scheme, the common information of the user group and the dedicated information of each terminal within the user group can be multiplexed and carried in the same MAC PDU. Furthermore, the position of a terminal's dedicated information in the MAC PDU is related to the terminal's identifier. Therefore, the terminal can decode its own MAC subPDU to obtain its dedicated information without needing to decode the MAC subPDUs associated with other terminals, thus reducing decoding complexity and saving terminal power consumption. In addition, the network configures common information for the user group, and all terminals within the user group can use a first identifier to obtain this common information. Compared to configuration at the terminal level, this further reduces signaling overhead.

[0273] It is understood that, in the above embodiments, the methods and / or steps implemented by the terminal can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the terminal; similarly, the methods and / or steps implemented by the network device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the network device. The chip system can be composed of chips, or it can include chips and other discrete devices.

[0274] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0275] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0276] Figure 15 shows a schematic diagram of a communication device 150. The communication device 150 includes a processing module 1501 and a transceiver module 1502. This communication device 150 can be used to implement the functions of the aforementioned terminal or network equipment.

[0277] In some embodiments, the communication device 150 may further include a storage module (not shown in FIG15) for storing program instructions and data.

[0278] In some embodiments, the transceiver module 1502, also referred to as a transceiver unit, is used to implement sending and / or receiving functions. The transceiver module 1502 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0279] In some embodiments, the transceiver module 1502 may include a receiving module and a sending module, respectively configured to perform receiving and sending steps performed by the terminal or network device in the above method embodiments, and / or other processes to support the technology described herein; the processing module 1501 may be configured to perform processing steps (e.g., determining) performed by the terminal or network device in the above method embodiments, and / or other processes to support the technology described herein.

[0280] For example, when the communication device 150 is used to implement the functions of the terminal described above:

[0281] The transceiver module 1502 is used to receive the first radio network temporary identifier (RNTI) of the first terminal. The first RNTI includes a first identifier and a second identifier. The first identifier is used to identify a first user group, and the second identifier is used to identify the first terminal within the first user group. Terminals belonging to the first user group are located in the same geographical area. The transceiver module 1502 is also used to receive first configuration information and second configuration information. The first identifier is associated with the first configuration information, and the second identifier is associated with the second configuration information. The processing module 1501 is used to perform control channel detection based on the first configuration information and the second configuration information.

[0282] Optionally, the first configuration information is used to configure the first search space, and the second configuration information is used to configure the second search space; the first search space and the second search space differ from each other in at least one of the following: detection period, time offset, or detection duration.

[0283] Optionally, the control channel includes the Physical Downlink Control Channel (PDCCH). Processing module 1501 is used to perform control channel detection based on first configuration information, including: processing module 1501 determining a first search space based on the first configuration information, and performing PDCCH blind detection using a first identifier or a third identifier within the first search space; the length of the third identifier is the same as the length of the first RNTI, and the third identifier includes the first identifier and a preset value. Alternatively, processing module 1501 is used to perform control channel detection based on second configuration information, including: processing module 1501 determining a second search space based on the second configuration information, and performing PDCCH blind detection using a second identifier or the first RNTI within the second search space.

[0284] Optionally, the first configuration information is used to configure a first discontinuous reception DRX pattern, and the second configuration information is used to configure a second DRX pattern; the first DRX pattern and the second DRX pattern differ from at least one of the following: DRX period, activation duration, or DRX timer.

[0285] Optionally, the control channel includes a PDCCH; the processing module 1501 is used to perform control channel detection according to the first configuration information, including: the processing module 1501 is used to determine a first DRX pattern according to the first configuration information, and to perform PDCCH blind detection using a first identifier or a third identifier during the activation duration of the first DRX pattern; the length of the third identifier is the same as the length of the first RNTI, and the third identifier includes the first identifier and a preset value. Alternatively, the processing module 1501 is used to perform control channel detection according to the second configuration information, including: the processing module 1501 is used to determine a second DRX pattern according to the second configuration information, and to perform PDCCH blind detection using a second identifier or a first RNTI during the activation duration of the second DRX pattern.

[0286] Optionally, the first configuration information is also used to configure the wake-up signal WUS associated with the first identifier.

[0287] Optionally, the processing module 1501 is used to perform control channel detection according to the first configuration information, including: the processing module 1501 is used to determine the time-frequency location of the WUS associated with the first identifier according to the first configuration information; the processing module 1501 is also used to perform PDCCH blind detection using the first identifier or the third identifier within the activation duration of the first DRX pattern when the WUS associated with the first identifier is detected at the time-frequency location.

[0288] Optionally, the first configuration information is used to configure the MBS control channel MCCH; the processing module 1501 is used to perform control channel detection according to the first configuration information, including: the processing module 1501 is used to detect the MCCH according to the first configuration information.

[0289] Optionally, the transceiver module 1502 is also used to receive control signaling, which is associated with the MBS.

[0290] Optionally, the transceiver module 1502 is further configured to receive third configuration information and / or fourth configuration information. The third configuration information is used to configure the position of public information associated with the first identifier in the first Media Access Control Protocol Data Unit (MAC PDU); the fourth configuration information is used to configure the position of private information associated with the second identifier in the first MAC PDU, the position of which is related to the second identifier.

[0291] When the communication device 150 is used to implement the functions of the aforementioned network device:

[0292] The transceiver module 1502 is used to send the first radio network temporary identifier (RNTI) of the first terminal. The first RNTI includes a first identifier and a second identifier. The first identifier is used to identify the first user group, and the second identifier is used to identify the first terminal within the first user group. Terminals belonging to the first user group are located in the same geographical area. The transceiver module 1502 is also used to send first configuration information and second configuration information. The first identifier is associated with the first configuration information, and the second identifier is associated with the second configuration information. The first configuration information and the second configuration information are used for control channel detection.

[0293] Optionally, the transceiver module 1502 is also used to send control signaling, which is associated with the MBS.

[0294] Optionally, the transceiver module 1502 is further configured to send third configuration information and / or fourth configuration information. The third configuration information is used to configure the position of public information associated with the first identifier in the first Media Access Control Protocol Data Unit (MAC PDU). The fourth configuration information is used to configure the position of private information associated with the second identifier in the first MAC PDU, the position of which is related to the second identifier.

[0295] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0296] In this application, the communication device 150 can be presented in an integrated manner by dividing it into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0297] Alternatively, the modules in communication device 150 can be implemented in software, hardware, or a combination of both. When any of the above modules are implemented in software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a system-on-chip (SoC) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes the software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0298] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a general-purpose central processing unit (CPU), microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0299] In some embodiments, when the communication device 150 in FIG15 is a chip or chip system, the function / implementation process of the transceiver module 1502 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1501 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0300] Since the communication device 150 provided in this embodiment can execute the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

[0301] As a possible product form, the terminal or network device described in the embodiments of this application can also be implemented using one or more FPGAs, PLDs, controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0302] As another possible product form, the terminal or network device described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, refer to FIG16, which is a schematic diagram of the structure of a communication device 1600 provided in an embodiment of this application. The communication device 1600 includes a processor 1601 and a transceiver 1602. The communication device 1600 can be a terminal, or a chip or chip system therein; or, the communication device 1600 can be a network device, or a chip or chip system therein. FIG16 only shows the main components of the communication device 1600. In addition to the processor 1601 and transceiver 1602, the communication device may further include a memory 1603 and input / output devices (not shown in the figure).

[0303] Optionally, the processor 1601 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1603 is mainly used to store software programs and data. The transceiver 1602 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0304] Optionally, the processor 1601, transceiver 1602, and memory 1603 can be connected via a communication bus.

[0305] When the communication device is powered on, the processor 1601 can read the software program in the memory 1603, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1601 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1601. The processor 1601 converts the baseband signal into data and processes the data.

[0306] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0307] In some embodiments, those skilled in the art will recognize that the above-described communication device 150 can take the form of the communication device 1600 shown in FIG16 in terms of hardware implementation.

[0308] As an example, the functions / implementation of the processing module 1501 and transceiver module 1502 in Figure 15 can be implemented by the processor 1601 in the communication device 1600 shown in Figure 16 calling computer execution instructions stored in the memory 1603. Alternatively, the functions / implementation of the processing module 1501 in Figure 15 can be implemented by the processor 1601 in the communication device 1600 shown in Figure 16 calling computer execution instructions stored in the memory 1603, and the functions / implementation of the transceiver module 1502 in Figure 15 can be implemented by the transceiver 1602 in the communication device 1600 shown in Figure 16.

[0309] As another possible product form, the terminal or network device in this application may adopt the composition structure shown in FIG17, or include the components shown in FIG17. FIG17 is a schematic diagram of the composition of a communication device 1700 provided in this application. The communication device 1700 may be a network device or a module, chip or system-on-a-chip in a network device; or the communication device 1700 may be a terminal or a module, chip or system-on-a-chip in a terminal.

[0310] As shown in Figure 17, the communication device 1700 includes at least one processor 1701 and at least one communication interface (Figure 17 is merely an example illustrating the inclusion of a communication interface 1704 and a processor 1701). Optionally, the communication device 1700 may also include a communication bus 1702 and a memory 1703.

[0311] Processor 1701 may be a CPU, a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 1701 may also be other devices with processing functions, such as circuits, devices, one or more integrated circuits or software modules for controlling the execution of the program of this application, without limitation.

[0312] Communication bus 1702 is used to connect different components in communication device 1700, enabling communication between them. Communication bus 1702 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 17, but this does not indicate that there is only one bus or one type of bus.

[0313] Communication interface 1704 is used for communicating with other devices or communication networks. For example, communication interface 1704 can be a module, circuit, transceiver, or any device capable of communication, such as an Ethernet interface, RAN interface, WLAN interface, transceiver, pin, bus, interface circuit, or transceiver circuit. Optionally, communication interface 1704 can also be an input / output interface located within processor 1701, used to implement signal input and signal output for the processor.

[0314] The memory 1703 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.

[0315] For example, memory 1703 may be read-only memory (ROM) or other types of static storage devices capable of storing static information and / or instructions; it may also be random access memory (RAM) or other types of dynamic storage devices capable of storing information and / or instructions; it may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0316] It should be noted that the memory 1703 can exist independently of the processor 1701, or it can be integrated with the processor 1701. The memory 1703 can be located inside or outside the communication device 1700, without limitation.

[0317] The memory stores the computer execution instructions involved in the implementation of the solution provided in this solution, and the processor controls the execution of these instructions. The processor executes the computer execution instructions stored in the memory to implement the method provided in this solution. Alternatively, in this solution, the processor may execute the processing-related functions of the method provided below, and the communication interface is responsible for communicating with other devices or communication networks; this solution does not specifically limit this aspect.

[0318] Optionally, the computer execution instructions in this solution can also be referred to as application code, and this solution does not specifically limit this.

[0319] As an optional implementation, the communication device 1700 may also include an output device 1705 and an input device 1706. The output device 1705 communicates with the processor 1701 and can display information in various ways. For example, the output device 1705 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1706 communicates with the processor 1701 and can receive user input in various ways. For example, the input device 1706 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0320] In some embodiments, those skilled in the art will recognize that the communication device 150 shown in FIG15 can take the form of the communication device 1700 shown in FIG17 in terms of hardware implementation.

[0321] As an example, the functions / implementation of the processing module 1501 and transceiver module 1502 in Figure 15 can be implemented by the processor 1701 in the communication device 1700 shown in Figure 17 calling computer execution instructions stored in the memory 1703. Alternatively, the functions / implementation of the processing module 1501 in Figure 15 can be implemented by the processor 1701 in the communication device 1700 shown in Figure 17 calling computer execution instructions stored in the memory 1703, and the functions / implementation of the transceiver module 1502 in Figure 15 can be implemented by the communication interface 1704 in the communication device 1700 shown in Figure 17.

[0322] It should be noted that the structure shown in Figure 17 does not constitute a specific limitation on the network device. For example, in other embodiments of this application, the network device may include more or fewer components than shown in the figure, or combine some components, or split some components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0323] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0324] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0325] As one possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0326] As one possible implementation, the communication device further includes a communication interface for communicating with modules outside the communication device. For example, the processor can be coupled to memory via the communication interface, causing the methods in any of the above method embodiments to be executed when the processor executes a computer program or instructions in the memory.

[0327] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0328] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0329] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0330] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0331] It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0332] The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. The components shown as units may or may not be physical units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0333] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0334] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0335] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0336] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method is applied to a first terminal or a chip in the first terminal, and the method includes: The first terminal receives a first wireless network temporary identifier (RNTI). The first RNTI includes a first identifier and a second identifier. The first identifier is used to identify a first user group, and the second identifier is used to identify the first terminal within the first user group. Terminals belonging to the first user group are located in the same geographical area. Receive first configuration information and second configuration information, wherein the first identifier is associated with the first configuration information and the second identifier is associated with the second configuration information; Control channel detection is performed based on the first configuration information and the second configuration information.

2. The method according to claim 1, characterized in that, The first configuration information is used to configure the first search space, and the second configuration information is used to configure the second search space; the first search space and the second search space differ from each other in at least one of the following: detection period, time offset, or detection duration.

3. The method according to claim 2, characterized in that, The first configuration information includes at least one of the following in the first search space: detection period, time offset, or detection duration; The second configuration information includes at least one of the following in the second search space: detection period, time offset, or detection duration.

4. The method according to claim 2, characterized in that, The second configuration information includes at least one of the following in the second search space: detection period, time offset, or detection duration; The first configuration information includes a scaling factor, which is used to scale the second search space to obtain the first search space.

5. The method according to any one of claims 2-4, characterized in that, The first search space is a group search space, and the second search space is a terminal-specific search space.

6. The method according to any one of claims 2-5, characterized in that, The control channel includes the Physical Downlink Control Channel (PDCCH); Control channel detection based on the first configuration information includes: determining the first search space based on the first configuration information; performing PDCCH blind detection in the first search space using the first identifier or the third identifier; wherein the length of the third identifier is the same as the length of the first RNTI, and the third identifier includes the first identifier and a preset value; or... The control channel detection based on the second configuration information includes: determining the second search space based on the second configuration information; and performing PDCCH blind detection in the second search space using the second identifier or the first RNTI.

7. The method according to claim 1, characterized in that, The first configuration information is used to configure a first discontinuous reception DRX pattern, and the second configuration information is used to configure a second DRX pattern; the first DRX pattern and the second DRX pattern differ from each other in at least one of the following: DRX period, activation duration, or DRX timer.

8. The method according to claim 7, characterized in that, The control channel includes PDCCH; Control channel detection based on the first configuration information includes: determining the first DRX pattern based on the first configuration information; performing PDCCH blind detection using the first identifier or the third identifier during the activation duration of the first DRX pattern; the length of the third identifier is the same as the length of the first RNTI, and the third identifier includes the first identifier and a preset value; or... The control channel detection based on the second configuration information includes: determining the second DRX pattern based on the second configuration information; and performing PDCCH blind detection using the second identifier or the first RNTI during the activation duration of the second DRX pattern.

9. The method according to claim 7 or 8, characterized in that, The first configuration information is also used to configure the wake-up signal WUS associated with the first identifier.

10. The method according to claim 9, characterized in that, Control channel detection is performed based on the first configuration information, including: The time-frequency location of the WUS associated with the first identifier is determined based on the first configuration information; If a WUS associated with the first identifier is detected at the time-frequency location, a PDCCH blind detection is performed using the first identifier or the third identifier during the activation duration of the first DRX pattern.

11. The method according to claim 1, characterized in that, The first configuration information is used to configure the multicast / broadcast service MBS, and the second configuration information is used to configure the unicast service.

12. The method according to claim 11, characterized in that, The first configuration information for configuring MBS includes: the first configuration information for configuring the MBS control channel MCCH; Control channel detection based on the first configuration information includes: detecting the MCCH based on the first configuration information.

13. The method according to claim 11 or 12, characterized in that, The method further includes: receiving control signaling associated with the MBS.

14. The method according to any one of claims 1-13, characterized in that, The method further includes: receiving third configuration information and / or fourth configuration information; The third configuration information is used to configure the position of the public information associated with the first identifier in the first Media Access Control Protocol Data Unit (MAC PDU). The fourth configuration information is used to configure the position of the private information associated with the second identifier in the first MAC PDU, and the position of the private information in the first MAC PDU is related to the second identifier.

15. A communication method, characterized in that, The method is applied to a first network device or a chip in the first network device, and the method includes: Send the first wireless network temporary identifier (RNTI) of the first terminal. The first RNTI includes a first identifier and a second identifier. The first identifier is used to identify a first user group, and the second identifier is used to identify the first terminal within the first user group. Terminals belonging to the first user group are located in the same geographical area. Send first configuration information and second configuration information, wherein the first identifier is associated with the first configuration information and the second identifier is associated with the second configuration information, and the first configuration information and the second configuration information are used for control channel detection.

16. The method according to claim 15, characterized in that, The first configuration information is used to configure the first search space, and the second configuration information is used to configure the second search space; the first search space and the second search space differ from each other in at least one of the following: detection period, time offset, or detection duration.

17. The method according to claim 16, characterized in that, The first configuration information includes at least one of the following in the first search space: detection period, time offset, or detection duration; The second configuration information includes at least one of the following in the second search space: detection period, time offset, or detection duration.

18. The method according to claim 16, characterized in that, The second configuration information includes at least one of the following in the second search space: detection period, time offset, or detection duration; The first configuration information includes a scaling factor, which is used to scale the second search space to obtain the first search space.

19. The method according to any one of claims 16-18, characterized in that, The first search space is a group search space, and the second search space is a terminal-specific search space.

20. The method according to claim 15, characterized in that, The first configuration information is used to configure a first discontinuous reception DRX pattern, and the second configuration information is used to configure a second DRX pattern; the first DRX pattern and the second DRX pattern differ from each other in at least one of the following: DRX period, activation duration, or DRX timer.

21. The method according to claim 20, characterized in that, The first configuration information is also used to configure the wake-up signal WUS associated with the first identifier.

22. The method according to claim 15, characterized in that, The first configuration information is used to configure the multicast / broadcast service MBS, and the second configuration information is used to configure the unicast service.

23. The method according to claim 22, characterized in that, The first configuration information is used to configure MBS, including: the first configuration information is used to configure the MBS control channel MCCH.

24. The method according to claim 22 or 23, characterized in that, The method further includes: sending control signaling associated with the MBS.

25. The method according to any one of claims 15-24, characterized in that, The method further includes: sending third configuration information and / or fourth configuration information; The third configuration information is used to configure the position of the public information associated with the first identifier in the first Media Access Control Protocol Data Unit (MAC PDU). The fourth configuration information is used to configure the position of the private information associated with the second identifier in the first MAC PDU, and the position of the private information in the first MAC PDU is related to the second identifier.

26. A communication device, characterized in that, The communication device includes at least one processor; the at least one processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-14, or to cause the communication device to perform the method as described in any one of claims 15-25.

27. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-14 to be performed, or cause the method described in any one of claims 15-25 to be performed.

28. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, they cause the method of any one of claims 1-14 to be performed, or cause the method of any one of claims 15-25 to be performed.

Images