Communication method, communication device, communication system, storage medium, and program product
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- BEIJING XIAOMI MOBILE SOFTWARE CO LTD
- Filing Date
- 2025-01-22
- Publication Date
- 2026-07-30
Smart Images

Figure CN2025074009_30072026_PF_FP_ABST
Abstract
Description
Communication methods, communication equipment, communication systems, storage media and software products Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology
[0002] With the continuous development of communication technology, non-terrestrial networks (NTNs) have gradually become a research hotspot. NTNs can utilize airborne platforms or in-orbit satellites and other non-terrestrial infrastructure to build wireless communication systems. This effectively enhances network coverage and can also be used for emergency communications. Furthermore, NTNs can play a role in the development of the Internet of Things (IoT) and possess scalability. Summary of the Invention
[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0004] A first aspect of this disclosure provides a communication method, which is executed by a terminal, and the method includes:
[0005] Receive first information sent by the network device, the first information being used to determine the location of the time-domain resource where the system information SI message is located;
[0006] The first information is used to indicate at least one of the following:
[0007] The length of the SI window corresponding to the SI message;
[0008] First offset;
[0009] The period of the SI message;
[0010] The repeating pattern of the SI message;
[0011] The SI message is located in a Time Division Duplex (TDD) frame and is sent within the SI window.
[0012] A second aspect of this disclosure provides a communication method, which is executed by a network device, and the method includes:
[0013] Send first information to the terminal, the first information being used to determine the location of the time domain resource where the system information SI message is located;
[0014] The first information is used to indicate at least one of the following:
[0015] The length of the SI window corresponding to the SI message;
[0016] First offset;
[0017] The period of the SI message;
[0018] The repeating pattern of the SI message;
[0019] The SI message is located in a Time Division Duplex (TDD) frame and is sent within the SI window.
[0020] A third aspect of this disclosure provides a terminal, the terminal comprising:
[0021] The transceiver module is used to receive first information sent by the network device, the first information being used to determine the location of the time domain resource where the system information SI message is located;
[0022] The first information is used to indicate at least one of the following:
[0023] The length of the SI window corresponding to the SI message;
[0024] First offset;
[0025] The period of the SI message;
[0026] The repeating pattern of the SI message;
[0027] The SI message is located in a Time Division Duplex (TDD) frame and is sent within the SI window.
[0028] A fourth aspect of this disclosure provides a network device, the network device comprising:
[0029] The transceiver module is used to send first information to the terminal, the first information being used to determine the location of the time domain resource where the system information SI message is located;
[0030] The first information is used to indicate at least one of the following:
[0031] The length of the SI window corresponding to the SI message;
[0032] First offset;
[0033] The period of the SI message;
[0034] The repeating pattern of the SI message;
[0035] The SI message is located in a Time Division Duplex (TDD) frame and is sent within the SI window.
[0036] The solution proposed in this embodiment receives first information sent by a network device. This first information is used to determine the location of the time-domain resource where the System Information (SI) message resides. The first information indicates at least one of the following: the length of the SI window corresponding to the SI message; a first offset; the period of the SI message; and the repetition pattern of the SI message. The SI message is located within a Time Division Duplex (TDD) frame and is sent within the SI window. This ensures that the scheduling of SI messages in the new TDD mode is aligned as closely as possible with the DL time unit, avoiding situations where the time-domain resource corresponding to the SI message exceeds its range, resulting in incomplete SI message transmission. This effectively improves system communication efficiency and guarantees channel performance. Attached Figure Description
[0037] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.
[0038] Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;
[0039] Figure 1B is a schematic diagram of the TDD frame structure of a satellite system provided in an embodiment of this disclosure;
[0040] Figure 2A is an interactive schematic diagram of a communication method provided in an embodiment of this disclosure;
[0041] Figures 2B-2C are schematic diagrams of a TDD frame structure provided in an embodiment of this disclosure;
[0042] Figure 2D is a schematic diagram of the frame structure corresponding to the downlink channel in a TDD frame provided in the embodiments of this disclosure;
[0043] Figure 3A is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure;
[0044] Figure 3B is a schematic diagram of the structure of a network device provided in an embodiment of this disclosure;
[0045] Figure 4A is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;
[0046] Figure 4B is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation
[0047] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0048] In a first aspect, embodiments of this disclosure provide a communication method, the method comprising:
[0049] Receive first information sent by the network device, the first information being used to determine the location of the time-domain resource where the system information SI message is located;
[0050] The aforementioned first information is used to indicate at least one of the following: the length of the SI window corresponding to the aforementioned SI message; and the first offset;
[0051] The period of the aforementioned SI messages; the repetition pattern of the aforementioned SI messages;
[0052] The aforementioned SI message is located within a Time Division Duplex (TDD) frame and is sent within the aforementioned SI window.
[0053] In the above embodiments, it can be ensured that the scheduling of SI messages in the new TDD mode is aligned with the DL time unit as much as possible, avoiding the situation where the time domain resources corresponding to the SI message are out of range, resulting in incomplete SI message transmission, effectively improving system communication efficiency and ensuring channel performance.
[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the length of the SI window is an integer multiple of the period corresponding to the TDD frame.
[0055] In the above embodiments, it is possible to ensure that the downlink time domain resources where the SI window is located match the downlink time units in the TDD frame structure as much as possible. This helps to ensure the complete transmission of scheduling information, effectively improves the transmission efficiency of system information, and thus improves the system communication efficiency.
[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the period of the aforementioned SI message is an integer multiple of the period corresponding to the aforementioned TDD frame.
[0057] In the above embodiments, it is possible to match the downlink time domain resources corresponding to the SI message with the selected DL time unit in the designed TDD frame structure, which can help ensure the complete transmission of scheduling information, effectively improve the transmission efficiency of system information, and thus improve the system communication efficiency.
[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the SI message occupies at least one valid subframe within each SI window; and the starting temporal position corresponding to the SI message is the first valid subframe within the SI window.
[0059] Among them, the aforementioned valid subframes are those subframes in the time domain resources occupied by the downlink channel corresponding to the aforementioned terminal that are not used to transmit the second information.
[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the aforementioned second information includes at least one of the following: narrowband primary synchronization signal NPSS; narrowband secondary synchronization signal NSSS; narrowband physical broadcast channel NPBCH; narrowband system information block 1SIB1-NB.
[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the period of the SI message is an integer multiple of the repetition pattern of the SI message.
[0062] In the above embodiments, when performing SI scheduling, the SI period is made to be an integer multiple of the repetition mode, which can ensure the integrity of repeated transmission of SI messages, effectively improve the transmission efficiency of system information, and thus improve the system communication efficiency.
[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the first offset is used to determine the starting position of the SI window within the period of the SI message.
[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the starting temporal position of the temporal resource pattern of the TDD frame corresponding to the above-mentioned terminal, relative to the offset of the first subframe #0 in the first system frame SFN#0, is equal to the first offset mentioned above.
[0065] In the above embodiments, the starting position of the time-domain resource pattern of each TDD frame can be aligned with the starting time-domain position of the entire SI window, thereby enabling the SI message to be sent in the downlink time unit selected in the time-domain resource pattern of the TDD frame. This helps to ensure the complete transmission of the SI message, effectively improves the transmission efficiency of system information, and thus improves the system communication efficiency.
[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal does not expect the transport block size (TBS) corresponding to the SI message to exceed 120; or, the transport block size (TBS) corresponding to the SI message to not exceed 120.
[0067] In the above embodiments, it is possible to effectively avoid the situation where SI messages cannot be completely sent in one SI window, resulting in overlap with adjacent SI windows, thereby effectively improving the success rate of system information transmission and improving system communication efficiency.
[0068] Secondly, embodiments of this disclosure provide a communication method, the method comprising:
[0069] Send first information to the terminal, the first information being used to determine the location of the time domain resource where the system information SI message is located;
[0070] The aforementioned first information is used to indicate at least one of the following: the length of the SI window corresponding to the aforementioned SI message; the first offset; the period of the aforementioned SI message; and the repetition pattern of the aforementioned SI message.
[0071] The aforementioned SI message is located within a Time Division Duplex (TDD) frame and is sent within the aforementioned SI window.
[0072] In the above embodiments, it can be ensured that the scheduling of SI messages in the new TDD mode is aligned with the DL time unit as much as possible, avoiding the situation where the time domain resources corresponding to the SI message are out of range, resulting in incomplete SI message transmission, effectively improving system communication efficiency and ensuring channel performance.
[0073] In conjunction with some embodiments of the second aspect, in some embodiments, the length of the SI window is an integer multiple of the period corresponding to the TDD frame.
[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the period of the aforementioned SI message is an integer multiple of the period corresponding to the aforementioned TDD frame.
[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned SI message occupies at least one valid subframe within each of the aforementioned SI windows; and,
[0076] The starting time domain position corresponding to the above SI message is the first valid subframe within the above SI window;
[0077] Among them, the aforementioned valid subframes are those subframes in the time domain resources occupied by the downlink channel corresponding to the aforementioned terminal that are not used to transmit the second information.
[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned second information includes at least one of the following: narrowband primary synchronization signal NPSS; narrowband secondary synchronization signal NSSS; narrowband physical broadcast channel NPBCH; narrowband system information block 1SIB1-NB.
[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the period of the SI message is an integer multiple of the repetition pattern of the SI message.
[0080] In conjunction with some embodiments of the second aspect, in some embodiments, the first offset is used to determine the starting position of the SI window within the period of the SI message.
[0081] In conjunction with some embodiments of the second aspect, in some embodiments, the starting temporal position of the temporal resource pattern of the TDD frame corresponding to the above-mentioned terminal, relative to the offset of the first subframe #0 in the first system frame SFN#0, is equal to the first offset mentioned above.
[0082] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal does not expect the transport block size (TBS) corresponding to the SI message to exceed 120; or,
[0083] The transport block size (TBS) corresponding to the above SI message does not exceed 120.
[0084] Thirdly, embodiments of this disclosure provide a communication method, the method comprising:
[0085] The network device sends first information to the terminal, the first information being used to determine the location of the time-domain resource where the system information SI message is located;
[0086] The aforementioned first information is used to indicate at least one of the following: the length of the SI window corresponding to the aforementioned SI message; the first offset; the period of the aforementioned SI message; and the repetition pattern of the aforementioned SI message.
[0087] The aforementioned SI message is located within a Time Division Duplex (TDD) frame and is sent within the aforementioned SI window.
[0088] In the above embodiments, it can be ensured that the scheduling of SI messages in the new TDD mode is aligned with the DL time unit as much as possible, avoiding the situation where the time domain resources corresponding to the SI message are out of range, resulting in incomplete SI message transmission, effectively improving system communication efficiency and ensuring channel performance.
[0089] Fourthly, embodiments of this disclosure provide a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.
[0090] Fifthly, embodiments of this disclosure provide a network device, which includes a transceiver module and a processing module; wherein the network device is used to execute the second aspect and optional implementations of the second aspect.
[0091] In a sixth aspect, embodiments of this disclosure provide a communication device comprising: at least one processor and an interface circuit; wherein the communication device is used to execute the first aspect and optional implementations thereof.
[0092] In a seventh aspect, embodiments of this disclosure provide a communication device comprising: at least one processor and an interface circuit; wherein the communication device is used to execute the second aspect and optional implementations of the second aspect.
[0093] Eighthly, embodiments of this disclosure provide a communication system comprising: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and optional implementations thereof, and the network device is configured to perform the method described in the second aspect and optional implementations thereof.
[0094] Ninthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.
[0095] In a tenth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the first aspect and its optional implementation, the second aspect and its optional implementation.
[0096] In one aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its alternative implementations, the second aspect and its alternative implementations.
[0097] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the first aspect and its optional implementations, the second aspect, and its optional implementations.
[0098] It is understood that the aforementioned terminals, access network equipment, core network equipment, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0099] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method and information processing method may be used interchangeably.
[0100] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0101] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0102] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0103] In the embodiments disclosed herein, "multiple" refers to two or more.
[0104] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “aplurality of”, “multiple”, etc., may be used interchangeably.
[0105] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0106] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.
[0107] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0108] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0109] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0110] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0111] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0112] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.
[0113] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0114] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0115] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0116] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.
[0117] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.
[0118] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0119] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0120] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0121] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
[0122] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102.
[0123] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things (IoT) device, narrowband-Internet of Things (NB-IoT) device, satellite communication device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, and red-capped terminal, but is not limited thereto.
[0124] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, nodes such as satellites or drones in non-terrestrial communication networks, evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), next-generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in Wi-Fi system.
[0125] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0126] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0127] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0128] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0129] The embodiments disclosed herein can be applied to Non-terrestrial Networks (NTN), Internet of Things (IoT) systems, Narrow Band-IoT (NB-IoT) systems, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), Super 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), and IEEE 802.16 (WiMAX, a registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0130] In some embodiments, non-terrestrial networks (NTNs) are increasingly becoming a research hotspot. NTNs can utilize airborne platforms or non-terrestrial infrastructure such as satellites to build wireless communication systems. They can effectively enhance network coverage and can also be used for emergency communications. Furthermore, NTNs can play a role in the development of the Internet of Things (IoT) and possess scalability.
[0131] In some embodiments, only Frequency Division Duplexing (FDD) operation is supported for IoT-NTN systems.
[0132] In some embodiments, it is considered to support Time Division Duplex (TDD) operation on the dedicated spectrum (1616-1626.5 MHz) allocated to the satellite system.
[0133] The satellite systems include the Iridium communication system, Globalstar, the European Data Relay System (EDRS), Tianlian-1, Starlink, OneWeb, and navigation-related systems such as the Global Positioning System (GPS), GLONASS, Galileo, and BeiDou. In some embodiments, introducing a period in the TDD band can be considered to save power consumption. For example, a 90ms period could be defined.
[0134] Taking the Iridium communication system as an example: one DL time unit (8.28ms) and one UL time unit (8.28ms) from its 90ms period are allocated to the 3GPP TDD mode, while the remaining resources are used to maintain the operation of its original proprietary system. That is, compatibility between the 3GPP IoT-NTN TDD mode and the Iridium proprietary system is achieved.
[0135] In some embodiments, the Time Division Multiple Access (TDMA) frame structure of a satellite system can be as shown in Figure 1B.
[0136] Since the current IoT-NTN system only supports FDD operation, the frame structure needs to be considered and redesigned for TDD mode.
[0137] In some embodiments, resource mapping in a TDD system is based on the mapping method in an FDD system.
[0138] Furthermore, in some embodiments, the following effects may also need to be considered when designing a TDD system:
[0139] 1. Considering coexistence with the TDD resources of the satellite system, x DL time units (8.28ms) within a 90ms period are selected for DL transmission in TDD mode, and x UL time units (8.28ms) within a 90ms period are selected for UL transmission in TDD mode. Therefore, the design needs to consider the reasonable allocation of DL and UL time units to ensure that the requirements of IoT-NTN TDD are met while reserving the operating space of the satellite system.
[0140] 2. Resource mapping in IoT-NTN TDD mode needs to refer to the mapping methods of Narrow Band Primary Synchronization Signal (NPSS), Narrow Band Secondary Synchronization Signal (NSSS), Narrow Band Physical Broadcast Channel (NPBCH), and Narrow Band Physical Random Access Channel (NPRACH) in FDD mode. To achieve resource consistency with FDD in TDD mode, it is necessary to ensure that the resource locations of NPSS, NSSS, and NPBCH are not covered or omitted.
[0141] 3. For Low Earth Orbit (LEO) satellite systems, the Round Trip Time (RTT) varies depending on the satellite's altitude:
[0142] For example, LEO 600km: RTT is approximately 25.77ms; LEO 1200km: RTT is approximately 41.77ms.
[0143] Furthermore, in some embodiments, the scheduling method and scheduling information settings of System Information (SI) messages in IoT-NTN TDD mode need to refer to the scheduling method and scheduling information settings of SI messages in FDD mode. In order to realize the frame structure design based on FDD in TDD mode, it is necessary to ensure that the transmission resource positions of SI messages are not covered or omitted.
[0144] Therefore, when designing a TDD frame structure, the location of the DL transmission time resource where the SI message is transmitted should be matched with the selected DL time unit in the designed TDD frame structure as much as possible. This will help ensure the complete transmission of scheduling information.
[0145] In some embodiments, under NB-IoT FDD mode, the SI message scheduling method adopts a semi-static scheduling method, that is, scheduling without the Narrow Band Physical Downlink Control Channel (NPDCCH). The scheduling method can be described as follows:
[0146] The scheduling of Narrow Band System Information Blocks (SIB-NBs) other than Narrow Band System Information Block 1 (SIB1-NB) is similar to LTE: an SI message can include one or more SIB-NBs (excluding SIB1-NB) with the same scheduling requirements (these SIB-NBs have the same transmission period), and they are sent within independent SI windows. The SI windows of different SI messages do not overlap. The length of the SI window is indicated in the SIB1-NB, and the length of the SI window for all SI messages is the same.
[0147] SI messages are transmitted only within the SI window, which can have the following characteristics:
[0148] (1) An SI message is associated with an SI window, and only this SI message can be sent within the SI window.
[0149] (2) An SI message can be sent multiple times within an SI window, but no other SI messages can be sent.
[0150] (3) SI windows are close together (if adjacent), without overlapping or gaps.
[0151] (4) All SI messages have the same SI window length.
[0152] (5) The periods of different SI messages are independent of each other.
[0153] Because the SI message transmission period is not an integer multiple of the 90ms TDD bandperiod in the 3GPP IoT-NTN TDD mode, and the start time of the SI window and the repetition pattern of the SI message may cause the SI message transmission time resource location to be misaligned with the DL time unit in the TDD mode. This may lead to situations where the time period occupied by the SI message transmission resources is difficult to align to the complete downlink time unit (DL time unit) when designing the TDD frame structure (especially when compatible with satellite systems). As a result, some SI message transmission resources may exceed the range of the DL time unit, affecting transmission efficiency.
[0154] Therefore, it is necessary to consider and determine a new SI message scheduling scheme.
[0155] The communication method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.
[0156] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiments of the present disclosure relate to a communication method, which includes:
[0157] In step S2101, network device 102 sends the first information.
[0158] In some embodiments, terminal 101 receives the first information sent by network device 102.
[0159] In some embodiments, the first information is used by terminal 101 to determine the location of the time-domain resource where the SI message is located.
[0160] In some embodiments, the SI message is located in a time-division duplex (TDD) frame.
[0161] In some embodiments, the aforementioned SI message is sent within the SI window.
[0162] In some embodiments, the SI message mentioned above includes one or more SIB-NBs with the same scheduling requirements (e.g., an SI message includes SIB2-NB, or an SI message includes SIB3-NB and SIB4-NB, etc.).
[0163] In some embodiments, the first information described above is used to indicate at least one of the following:
[0164] The length of the SI window corresponding to the above SI message;
[0165] First offset;
[0166] The periodicity of the aforementioned SI messages;
[0167] The above SI message repetition pattern.
[0168] Optionally, the first offset is used to determine the starting time-domain position of the SI window within the period of the SI message.
[0169] Optionally, in some embodiments, the first offset can be 0.
[0170] In some embodiments, the first offset may not be set, and the default first offset may be set to a default value, such as 0 or 1.
[0171] In some embodiments, the length of the SI window is an integer multiple of the period corresponding to the TDD frame.
[0172] In some embodiments, the length of the SI window can be measured in seconds (s), milliseconds (ms), slots, system frames (SF), radio frames (RF), subframes, etc.
[0173] In some embodiments, the period of the SI message is an integer multiple of the period corresponding to the TDD frame.
[0174] In some embodiments, the period of the SI message can be in seconds (s), milliseconds (ms), slots, system frames (SF), radio frames (RF), subframes, etc.
[0175] In some embodiments, the repetition pattern of the SI message described above can be set to a new value to match the period of the TDD frame.
[0176] In some embodiments, the repetition pattern of the above SI message can be, for example, every9thRF, every18thRF, every27thRF, every36thRF, etc. The repetition pattern of the above SI message is every9thRF, meaning that it is transmitted once starting from the first valid radio subframe of every 9 RFs.
[0177] In some embodiments, the SI message occupies at least one valid subframe within each window, and the corresponding starting temporal position of the SI message within each SI window is the first valid subframe within that SI window.
[0178] Among them, a valid subframe refers to a subframe in the time domain resources occupied by the downlink channel corresponding to terminal 101 that is not used to transmit the second information.
[0179] Optionally, the second information may include at least one of the following:
[0180] Narrow Band Primary Synchronization Signal (NPSS);
[0181] Narrow Band Secondary Synchronization Signal (NSSS);
[0182] Narrowband Physical Broadcast Channel (NPBCH);
[0183] Narrowband System Information Block 1 (SIB1-NB).
[0184] In some embodiments, the period of the aforementioned SI message is an integer multiple of the repetition pattern.
[0185] In some embodiments, the unit of the first offset can be milliseconds (ms), system frame (SF), radio frame (RF), subframe, etc.
[0186] In some embodiments, the starting temporal position of the temporal resource pattern of the TDD frame corresponding to the terminal 101 is equal to the first offset mentioned above relative to the first subframe #0 in the first system frame (i.e., the system frame with system frame number (SFN) #0) SFN#0.
[0187] In some embodiments, the name of the first information is not limited, and may be, for example, "system information", "broadcast message", "Radio Resource Control (RRC) signaling", "dedicated signaling", "ephemeris information", "scheduling information", "configuration information", "communication configuration", "SI message scheduling", "resource configuration", "downlink configuration", "synchronization configuration", etc.
[0188] In step S2102, terminal 101 determines the location of the time domain resource where the SI message is located.
[0189] In some embodiments, the terminal 101 may determine the location of the SI message in the time domain resource in the time domain resource pattern (TDD pattern) corresponding to the terminal based on the agreement of the protocol.
[0190] Optionally, the protocol may specify the patterns of one or more time-domain resources.
[0191] Optionally, the protocol can pre-define a fixed TDD pattern, which is used in different systems, cases, and scenarios.
[0192] Optionally, the aforementioned preset fixed pattern can refer to the pattern examples in any embodiment of this application.
[0193] In some embodiments, the protocol may preset multiple patterns, and the terminal 101 may further determine one of the patterns in an implicit manner (for example, implicitly determining one of the patterns based on ephemeris information broadcast by System Information Block (SIB) messages, or information such as satellite type).
[0194] Furthermore, based on the pattern of the determined time-domain resources, the terminal 101 can repeatedly transmit in the time domain to form a complete TDD frame structure, thereby determining the uplink and downlink resources that the terminal 101 can use.
[0195] In some embodiments, terminal 101 may determine the time-domain resource location corresponding to the SI message based on the first information described above.
[0196] In some embodiments, the first information described above can be used to determine the corresponding time-domain resource location of multiple SI messages.
[0197] In some embodiments, the terminal 101 may determine the position of the SI window and the transmission method of the SI message within the SI window based on the first information described above.
[0198] In some embodiments, terminal 101 may determine the length of the SI window based on the first information described above.
[0199] In some embodiments, terminal 101 may determine the length of the SI window based on the “si-WindowLength” field in the first information described above.
[0200] In some embodiments, the length of the SI window is an integer multiple of the period corresponding to the TDD frame.
[0201] In some embodiments, the length of the SI window is an integer multiple of the 90ms TDD period, that is, si-WindowLength mod90 = 0.
[0202] As an example, one could consider setting the length of the SI window to an enumeration value type ENUMERATED{ms90,ms180,ms270,ms360,ms450,ms540,ms630,spare1}.
[0203] In some embodiments, terminal 101 may determine the period of each SI message based on the first information described above.
[0204] In some embodiments, terminal 101 may determine the period of each SI message based on the “si-Periodicity” field in the first information described above.
[0205] In some embodiments, the periods of different SI messages are independent of each other.
[0206] In some embodiments, the period of the SI message is an integer multiple of the period corresponding to the TDD frame.
[0207] In some embodiments, the period of the SI message is an integer multiple of the 90ms TDD period, that is, si-Periodicity mod 90 = 0.
[0208] As an example, one could consider setting the period of the SI message to an enumeration value type ENUMERATED{rf81,rf162,rf324,rf648,rf1296,rf2592,rf5184,spare}.
[0209] In some embodiments, the terminal 101 may determine the starting time-domain position of the SI window within the SI cycle based on the first information described above.
[0210] In some embodiments, the terminal 101 may determine the starting time-domain position of the SI window within the SI period based on the first offset in the first information described above.
[0211] In some embodiments, the starting temporal position of the SI window is subframe #0 in the system frame that satisfies (H-SFN*1024+SFN)mod T=FLOOR(x / 10)+Offset. Here, x=(n-1) / W, Offset is the first offset mentioned above, W is the length of the SI window, T is the period of the SI message, n is the number of the SI window corresponding to each SI message (starting from 1, for example, n=1 for the SI window corresponding to the first SI message, n=2 for the SI window corresponding to the second SI message, etc.), and FLOOR() represents rounding down.
[0212] As an example, the first piece of information mentioned above indicates that the SI window length corresponding to SI message 1 is 90ms, the SI message period is 81RF, the first offset is 1RF, and the window number n = 1. That is, the SI window has a period of 81RF and a window length of 90ms. Based on the above formula (H - SFN * 1024 + SFN) mod T = FLOOR(x / 10) + Offset, setting H - SFN = 0, it can be determined that the SI window starts at subframe #0 of the system frame that satisfies SFN mod 81 = 1. That is, the starting temporal position of the SI window is at SFN#1, SFN#82, SFN#163, ...
[0213] The aforementioned first information also indicates that the SI window length corresponding to SI message 2 is 90ms, the SI message period is 162RF, the first offset is 1RF, and the window number n = 2. That is, the SI window has a period of 162RF and a window length of 90ms. Based on the formula (H - SFN * 1024 + SFN) mod T = FLOOR(x / 10) + Offset, setting H - SFN = 0, we can determine that the SI window starts at subframe #0 of the system frame that satisfies SFN mod 162 = 10. In other words, the initial temporal position of the SI window is at SFN#10, SFN#172, ...
[0214] In some embodiments, each SI message is sent on the first valid subframe within the aforementioned SI window.
[0215] In some embodiments, the terminal 101 may determine the repetition pattern of the SI message based on the first information mentioned above, that is, determine how many frames to retransmit once, until the SI message is completely sent once.
[0216] Optionally, the length of the SI message is determined by the Transport Block Size (TBS).
[0217] Optionally, when the TBS corresponding to the SI message is 56 / 120, it takes 2 subframes to complete one repeated transmission of the SI message; when the TBS corresponding to the SI message is any value exceeding 120, it takes 8 subframes to complete one repeated transmission of the SI message.
[0218] As an example, the DL subframe corresponding to the DL time unit of length 8 subframes in SI in TDD mode can be any of the following options (where the positions of NPSS, NSSS, and NPBCH can be as shown in Figure 2D):
[0219] Option 1: (Across two consecutive wireless frames);
[0220] Option 2: (Across two consecutive wireless frames);
[0221] Option 3: (Across two consecutive wireless frames);
[0222] Option 4: (Across two consecutive wireless frames).
[0223] For an SI message with a TBS of 56 / 120 bits, Option 1 transmits the first complete SI message on subframes #3 and #4, with subframe #5 used to send NPSS, subframe #9 used to send NSSS, and subframe #0 used to send NPBCH; Option 2 transmits the first complete SI message on subframes #4 and #6, with subframe #5 used to send NPSS, subframe #9 used to send NSSS, and subframe #0 used to send NPBCH; Option 3 transmits the first complete SI message on subframes #8 and #1, with subframe #5 used to send NPSS, subframe #9 used to send NSSS, and subframe #0 used to send NPBCH; Option 4 transmits the first complete SI message on subframes #1 and #2, with subframe #5 used to send NPSS, subframe #9 used to send NSSS, and subframe #0 used to send NPBCH.
[0224] In some embodiments, an SI message may include multiple SIBs. For example, if an SI message includes SIB2 and SIB3, and the TBS corresponding to each SIB is 56 / 120 bits, then transmitting a complete SI message requires 4 subframes. Correspondingly, Option 1 transmits the first complete SIB2 and SIB3 on subframes #3, 4, 6, and 7; Option 2 transmits the first complete SIB2 and SIB3 on subframes #4, 6, 7, and 8; Option 3 transmits the first complete SIB2 and SIB3 on subframes #8, 1, 2, and 3; and Option 4 transmits the first complete SIB2 and SIB3 on subframes #1, 2, 3, and 4.
[0225] Understandably, when SI scheduling exceeds 120 TBS, a single SI retransmission requires 8 subframes to complete. If there are insufficient subframes within the corresponding SI window to transmit an SI message (insufficient remaining subframes after the DL time unit containing NPSS, NSSS, and NPBCH), the UE will continue to receive SI messages in the system frame immediately following the system frame indicated by the si-RepetitionPattern. If the subsequent system frame contains an SI window corresponding to another SI message, a temporal resource overlap problem will occur between the transmissions of two different SI messages.
[0226] In some embodiments, terminal 101 does not expect the transport block size (TBS) corresponding to the aforementioned SI message to exceed 120.
[0227] In some embodiments, the transport block size (TBS) corresponding to the SI message may be specified to not exceed 120 through protocol agreements or other means.
[0228] In some embodiments, the period of the SI message is an integer multiple of the repetition pattern. This ensures the integrity of the repeated transmission of SI messages as much as possible.
[0229] In some embodiments, the starting temporal position of the temporal resource pattern of the TDD frame corresponding to the terminal 101 is equal to the first offset relative to the offset of the first subframe #0 in the first system frame (i.e., the system frame with SFN #0) (which can be denoted as the second offset).
[0230] In other words, the starting position of each TDD transmission cycle (i.e., the overall TDD pattern) corresponding to terminal 101 is located on a radio frame with SFN mod N = Offset (first offset), where N is the TDD transmission cycle. This ensures that the overall temporal resource starting position of the TDD transmission is aligned with the overall temporal resource starting position of the SI window.
[0231] As an example, the network schedules two SI messages, SI-1 and SI-2, where SI-1 includes SIB1 and SIB2, and SI-2 includes SIB4. The scheduling information for the two SI messages can be shown in the table below:
[0232] Table 1 Example 1 of SI message scheduling information
[0233] As an example, the TDD pattern corresponding to the SI message mentioned above can be shown in Figure 2B. The TDD frame structure (TDD pattern) period is 90ms, the DL transmission time is 8ms, and the second offset (TDD time offset) equals the first offset (Offset) of 1RF. Within each 90ms period, the first DL slot of the satellite system is used for DL transmission in TDD mode. In the figure, #n represents the system frame number n, and the shaded area represents the DL time unit that can be used to transmit SI-1 and SI-2.
[0234] As an example, the network schedules two SI messages, SI-1 and SI-2, where SI-1 includes SIB1 and SIB2, and SI-2 includes SIB4. The scheduling information for the two SI messages can be shown in the table below:
[0235] Table 2. Example 2 of SI message scheduling information
[0236] As an example, the TDD pattern corresponding to the SI message mentioned above can be shown in Figure 2C. The TDD frame structure (TDD pattern) period is 90ms, the DL transmission time is 8ms, and the second offset (TDD time offset) equals the first offset (Offset) of 1RF. Within each 90ms period, the first DL slot of the satellite system is used for DL transmission in TDD mode. In the figure, #n represents the system frame number n, and the shaded area represents the DL time unit that can be used to transmit SI-1 and SI-2.
[0237] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.
[0238] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.
[0239] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0240] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".
[0241] In some embodiments, the terms "repeating pattern", "repeating pattern", "pattern", "repeating pattern" and other similar terms may be used interchangeably.
[0242] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DLDCI,” “uplink (UL) grant,” and “ULDCI” can be used interchangeably.
[0243] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".
[0244] In some embodiments, the terms "time domain unit", "time unit", "transmission unit", "satellite unit", "satellite system unit", "satellite system transmission unit", and "time slot" can be used interchangeably.
[0245] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", and "RAN-based" can be used interchangeably. In some embodiments, the terms "moment", "point in time", "time", and "time location" can be used interchangeably, as can the terms "duration", "segment", "time window", "window", and "time".
[0246] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.
[0247] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.
[0248] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.
[0249] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.
[0250] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0251] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0252] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.
[0253] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2102. For example, step 2101 may be implemented as a standalone embodiment, step 2102 may be implemented as a standalone embodiment, step 2101+2102 may be implemented as a standalone embodiment, etc., but is not limited thereto.
[0254] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0255] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2A.
[0256] The following is an exemplary description of the methods described in the above embodiments.
[0257] In some embodiments, the scheduling method of SIMessage in NB-IoT FDD mode adopts a semi-static scheduling method, that is, scheduling without NPDCCH.
[0258] In some embodiments, the scheduling information of SI messages and information such as TBS are specified in the schedulingInfoList-r13 field of the SIB1-NB. As an example, the fields related to SI message scheduling in the SIB1-NB may be as follows:
[0259] In some embodiments, terminal 101 can first confirm the starting position and length of the SI window corresponding to the SI message, and the processing procedure is as follows:
[0260] (1) In SIB1-NB, schedulingInfoList specifies the list of SI messages. Each SI message is represented by n (starting from 1) in the message list. If 4 SI messages are specified, there will be 4 consecutive SI windows for sending these 4 SI messages, and n indicates which SI window the SI message is in.
[0261] (2) Each SI message has a parameter x = (n-1)*w, where w is the window length of the SI and is set via si-WindowLength. It can be seen that this parameter x is in milliseconds.
[0262] (3) The starting frame of the SI window for different SI messages satisfies (H-SFN*1024+SFN)mod T=floor(x / 10)+Offset of the subframe 0 of the system frame, where T corresponds to the period of the SI message, specified by si-periodicity (in system frames, i.e., in 10ms units), and FLOOR(x / 10)+Offset is used to determine the starting position of the SI window within the period, where Offset is specified by si-RadioFrameOffset.
[0263] Furthermore, terminal 101 needs to confirm the transmission mode of SI messages within each SI window, and the processing procedure is as follows:
[0264] (1) The UE will receive and accumulate SI messages transmitted on DL-SCH from the beginning of the SI window until the end of the SI window. Within each SI window, the UE will start from the system frame indicated by si-RepetitionPattern and the downlink bitmap indicated by the valid downlink transmission subframe, until the accumulated SI message transmission is successfully decoded. That is, the SI message will start from the first valid downlink subframe in the system frame defined by the repetition pattern, occupying consecutive valid downlink subframes until a complete repetition is completed. The valid downlink transmission subframe does not include any downlink subframes used to transmit NPSS / NSSS / NPBCH / SIB1-NB.
[0265] (2) si-TB specifies the TBS of the SI message and the number of consecutive NB-IoT downlink subframes used to transmit the SI message. If the TBS is 56 or 120 bits, one TB requires 2 downlink subframes for transmission; while for other TBSs, one TB requires 8 downlink subframes for transmission.
[0266] (3) If there are not enough subframes in the system frame indicated by si-RepetitionPattern to transmit an SI message, the UE will continue to receive SI messages in the system frame immediately following the system frame indicated by si-RepetitionPattern.
[0267] (4) The protocol does not require the UE to accumulate multiple SI messages in parallel, but depending on the coverage conditions, the UE may be required to accumulate the same SI message transmitted in multiple SI windows. If the SI message cannot be decoded from the accumulated SI message transmission at the end of the SI window, the UE will continue to receive and accumulate SI message transmission on the Downlink Shared Channel (DL-SCH) in the next SI window of the relevant SI message.
[0268] In some embodiments, to ensure that the time-domain resource location corresponding to the SI message is aligned with the DL time unit in TDD mode and does not exceed the DL time unit, the following design considerations can be taken into account:
[0269] Key Point 1: Consider determining a new SI window length (si-WindowLength) for the scheduling information of SI messages in IoT-NTN TDD mode.
[0270] In some embodiments, each SI message is transmitted in only one SI window and all SI messages have the same SI window length. The SI sets the SI window length (in slot, subframe, or ms) to an integer multiple of 90ms TDD Time Period, i.e., si-WindowLength mod 90 = 0.
[0271] As an example, one could consider setting si-WindowLength to ENUMERATED{ms90,ms180,ms270,ms360,ms450,ms540,ms630,spare1}.
[0272] In the above embodiments, this processing can achieve the matching of the DL transmission time resource location where the SI window is located with the selected DL time unit in the designed TDD frame structure, which will help ensure the complete transmission of scheduling information.
[0273] Key Point 2: Consider determining a new period (si-Periodicity) for each SI message in the scheduling information of IoT-NTN TDD mode SI messages.
[0274] In some embodiments, the scheduling system configures a sending window for each SI message based on the SI message period, and the periods of different SI messages are independent of each other. Therefore, the SI message period should also be set to an integer multiple of 90ms TDD Time Period, i.e., si-Periodicity mod 90 = 0.
[0275] As an example, one could consider setting si-Periodicity ENUMERATED{rf81,rf162,rf324,rf648,rf1296,rf2592,rf5184,spare}.
[0276] In the above embodiments, by setting the period of the SI message to an integer multiple of 90ms, it is helpful to match the location of the DL transmission time resource where the SI message is transmitted with the selected DL time unit in the designed TDD frame structure, which will help ensure the complete transmission of scheduling information.
[0277] Key Point 3: Determine a new repetition pattern (si-RepetitionPattern) for each SI message in the scheduling information of SI messages under IoT-NTN TDD mode.
[0278] In some embodiments, SI messages are repeated a number of times within their configured SI period. The number of repetitions is determined by the repetition pattern configured for each SI in SIB1-NB and the length of the SI window. The repetition pattern of the SI message is defined as transmitting one repetition starting from the first valid radio subframe every n radio frames. The SI message is transmitted starting from the first subframe of the SI window. The downlinkBitmap indicates the valid downlink transmission subframes until the accumulated SI message transmission is successfully decoded. That is, the SI message will start from the first valid downlink subframe within the system frame defined by the repetition pattern, occupying consecutive valid downlink subframes until a complete repetition is completed. The valid downlink transmission subframes are all downlink subframes that do not contain those used to transmit NPSS / NSSS / NPBCH / SIB1-NB.
[0279] In some embodiments, the SI message may be transmitted at the following locations within the IoT-NTN TDD mode DL time unit:
[0280] SI messages will be transmitted on subframes that are not NPSS, NSSS, or NPBCH (excluding subframes 5, 9, and 0). The valid subframes for SI message transmission are the remaining unmarked subframes in Figure 2D.
[0281] In some embodiments, if TBS = 56 / 120 bits, meaning that SI requires 2 subframes to complete one repeated transmission, then Option 1 transmits the first complete SI message on the 3rd and 4th subframes; Option 2 transmits the first complete SI message on the 4th and 6th subframes; Option 1 transmits the first complete SI message on the 8th and 1st subframes; Option 2 transmits the first complete SI message on the 1st and 2nd subframes.
[0282] Specifically, as an example, the SI message repetition pattern (si-RepetitionPattern) can be defined as follows: si-RepetitionPattern ENUMERATED{every9thRF,every18thRF,every27thRF,every36thRF}
[0283] Optionally, when performing SI scheduling, the SI period can be made as an integer multiple of the repetition pattern as possible to ensure the integrity of repeated SI message transmission.
[0284] In some embodiments, when the TBS of the SI scheduling exceeds 120 bits, a single SI retransmission requires 8 subframes to complete. If there are not enough subframes within the corresponding SI window to transmit an SI message (insufficient remaining subframes after the DL time unit containing the subframes of NPSS, NSSS, and NPBCH), the UE will continue to receive SI messages in the system frame immediately following the system frame indicated by the si-RepetitionPattern. If the subsequent system frame contains an SI window corresponding to another SI message, a temporal resource overlap problem will occur between the transmission of two different SI messages.
[0285] Therefore, in some embodiments, terminal 101 may not expect SI scheduling to exceed 120 TBS, that is, terminal 101 does not expect SI to require 8 subframes to complete a single repeated transmission; or, the protocol presets a limit on TBS scheduling not exceeding 120 TBS.
[0286] Point 4: Consider defining a new overall transmission time offset (TDD time offset) for IoT-NTN TDD mode.
[0287] In NB-IoT, the SI window configuration introduces a starting offset to allow base stations to stagger the time-domain resources used by adjacent cells to send SI messages, thereby reducing mutual interference. The SI window starts at subframe 0 of the system frame that satisfies (H-SFN*1024+SFN)mod T=FLOOR(x / 10)+Offset. FLOOR(x / 10)+Offset is used to determine the starting position of the SI window within the period, where Offset is specified by si-RadioFrameOffset.
[0288] The aforementioned first offset will cause the overall starting position of the SI window to be offset relative to the subframe #0 of the system frame #0 within a certain superframe. This offset is specified by the integer value si-RadioFrameOffset-INTEGER(1..15).
[0289] In some embodiments, the starting position of the overall TDD mode transmission is usually subframe #0 of system frame #0. Due to the introduction of offset in NB-IoT, the starting position of the overall time domain resources of TDD transmission may not be aligned with the starting position of the overall time domain resources of the SI window. Therefore, it is necessary to define a TDD time offset for IoT-NTN TDD mode that is subframe #0 of system frame #0 to offset this effect.
[0290] In some embodiments, specifically, the TDD time offset (in radio frames) setting must satisfy: TDD time offset = Offset, with a value range of INTEGER (1..15).
[0291] In the above embodiments, the starting position of each TDD transmission cycle can be located on the radio frame where SFN mod N = Offset (N is the TDD transmission cycle); ensuring that the overall time domain resource starting position of TDD transmission is aligned with the overall time domain resource starting position of the SI window, thereby enabling SI messages to be transmitted on the DL time unit corresponding to the selected TDD pattern, ensuring the integrity of SI message transmission.
[0292] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.
[0293] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0294] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0295] Figure 3A is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. Terminal 3100 is used to execute any of the above methods. In some embodiments, as shown in Figure 3A, terminal 3100 may include at least one of a transceiver module 3101, a processing module 3102, etc. In some embodiments, the transceiver module 3101 is used to receive first information sent by a network device, the first information being used to determine the location of the time-domain resource where the system information SI message is located; the first information is used to indicate at least one of the following: the length of the SI window corresponding to the SI message; a first offset; the period of the SI message; the repetition pattern of the SI message; wherein the SI message is located in a time-division duplex (TDD) frame, and the SI message is sent within the SI window. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., step S2101, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to execute at least one of other steps (e.g., step S2102, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be elaborated here.
[0296] Figure 3B is a schematic diagram of the structure of a network device proposed in an embodiment of this disclosure. The network device 3200 is used to perform any of the above methods. In some embodiments, as shown in Figure 3B, the network device 3200 may include at least one of a transceiver module 3201, a processing module 3202, etc. In some embodiments, the transceiver module 3201 is used to send first information to a terminal, the first information being used to determine the location of the time-domain resource where the system information SI message is located; the first information is used to indicate at least one of the following: the length of the SI window corresponding to the SI message; a first offset; the period of the SI message; the repetition pattern of the SI message; wherein the SI message is located in a time-division duplex (TDD) frame, and the SI message is sent within the SI window. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., step S2101, but not limited thereto) performed by the network device 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the network device 102 in any of the above methods, which will not be elaborated here.
[0297] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0298] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0299] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.
[0300] Figure 4A is a schematic diagram of the structure of the communication device 4100 proposed in an embodiment of this disclosure. The communication device 4100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 4100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0301] As shown in Figure 4A, the communication device 4100 is used to execute any of the above methods. In some embodiments, the communication device 4100 includes one or more processors 4101. The processor 4101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 4100 is used to execute any of the above methods. Optionally, one or more processors 4101 are used to invoke instructions to cause the communication device 4100 to execute any of the above methods.
[0302] In some embodiments, the communication device 4100 further includes one or more transceivers 4102. When the communication device 4100 includes one or more transceivers 4102, the transceiver 4102 performs at least one of the communication steps (e.g., step S2101, but not limited thereto) in the above method, such as sending and / or receiving, and the processor 4101 performs at least one of other steps (e.g., step S2102, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0303] In some embodiments, the communication device 4100 further includes one or more memories 4103 for storing data and / or instructions. Optionally, one or more processors 4101 are used to invoke instructions stored in the memory 4103 to cause the communication device 4100 to perform any of the above methods. Optionally, all or part of the memory 4103 may also be located outside the communication device 4100. In an optional embodiment, the communication device 4100 may include one or more interface circuits 4104. Optionally, the interface circuit 4104 is connected to the memory 4102 and can be used to receive data and / or instructions from the memory 4102 or other devices, and can be used to send data and / or instructions to the memory 4102 or other devices. For example, the interface circuit 4104 can read data and / or instructions stored in the memory 4102 and send the data and / or instructions to the processor 4101.
[0304] The communication device 4100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 4100 described in this disclosure is not limited thereto, and the structure of the communication device 4100 may not be limited by FIG4A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0305] Figure 4B is a schematic diagram of the structure of chip 4200 according to an embodiment of this disclosure. For cases where the communication device 4100 can be a chip or a chip system, please refer to the schematic diagram of chip 4200 shown in Figure 4B, but it is not limited thereto.
[0306] Chip 4200 includes one or more processors 4201. Chip 4200 is used to perform any of the above methods.
[0307] In some embodiments, chip 4200 further includes one or more interface circuits 4202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 4200 further includes one or more memories 4203 for storing data and / or instructions. Optionally, all or part of the memories 4203 may be located outside of chip 4200. Optionally, the interface circuits 4202 are connected to the memories 4203, and the interface circuits 4202 can be used to receive data and / or instructions from the memories 4203 or other devices, and can be used to send data and / or instructions to the memories 4203 or other devices. For example, the interface circuits 4202 can read data and / or instructions stored in the memories 4203 and send the data and / or instructions to the processor 4201.
[0308] In some embodiments, the interface circuit 4202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., step S2101, but not limited thereto). The interface circuit 4202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 4202 performing data and / or instruction interaction between the processor 4201, the chip 4200, the memory 4203, or the transceiver device. In some embodiments, the processor 4201 performs at least one of other steps (e.g., step S2102, but not limited thereto).
[0309] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0310] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0311] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0312] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
Claims
1. A communication method characterized by comprising: The method is performed by a terminal, and the method comprises: receiving first information sent by a network device, the first information being used to determine a location of time domain resources where a system information SI message is located; the first information being used to indicate at least one of the following information: a length of an SI window corresponding to the SI message; a first offset; a periodicity of the SI message; a repetition pattern of the SI message; wherein the SI message is located in a time division duplex TDD frame, and the SI message is sent in the SI window.
2. The method of claim 1, wherein, The length of the SI window is an integer multiple of a periodicity corresponding to the TDD frame.
3. The method according to claim 1 or 2, characterized in that, The periodicity of the SI message is an integer multiple of a periodicity corresponding to the TDD frame.
4. The method of any one of claims 1-3, wherein: the SI message occupies at least one valid subframe in each of the SI windows; and a starting time domain location corresponding to the SI message is a first valid subframe in the SI window. wherein the valid subframe is a subframe in time domain resources occupied by a downlink channel corresponding to the terminal and not used for sending second information.
5. The method of claim 4, wherein, The second information comprises at least one of: a narrowband primary synchronization signal NPSS; a narrowband secondary synchronization signal NSSS; a narrowband physical broadcast channel NPBCH; a narrowband system information block 1 SIB1-NB.
6. The method according to any one of claims 1 to 5, characterized in that, The periodicity of the SI message is an integer multiple of the repetition pattern of the SI message.
7. The method according to any one of claims 1 to 6, characterized in that, The first offset is used to determine a starting position of the SI window in the periodicity of the SI message.
8. The method of any one of claims 1-7, wherein: a starting time domain location of a time domain resource pattern of a TDD frame corresponding to the terminal has an offset relative to a first subframe #0 in a first system frame SFN#0, and the offset is equal to the first offset.
9. The method of any one of claims 1-8, wherein: the terminal does not expect a transport block size TBS corresponding to the SI message to exceed 120; or the transport block size TBS corresponding to the SI message does not exceed 120.
10. A communication method characterized by comprising: The method is performed by a network device, and the method comprises: sending first information to a terminal, the first information being used to determine a location of time domain resources where a system information SI is located; the first information being used to indicate at least one of the following information: a periodicity of the SI message; a repetition pattern of the SI message; wherein the system information SI message is located in a time division duplex TDD frame, and the SI message is sent by the network device in the SI window. The length of the SI window is an integer multiple of a periodicity of the TDD frame. The periodicity of the SI message is an integer multiple of a periodic of the TDD frame.
11. The method of claim 10, wherein, 13. The method of any one of claims 10-13, wherein:
12. The method according to claim 10 or 11, characterized in that, the SI message occupies at least one valid subframe in each of the SI windows; a starting time domain location corresponding to the SI message is a first valid subframe in the SI windows. The effective subframe is a subframe in which time domain resources occupied by a downlink channel corresponding to the terminal are not used for transmitting second information.
14. The method of claim 13, wherein, The second information includes at least one of: a narrowband primary synchronization signal (NPSS); a narrowband secondary synchronization signal (NSSS); a narrowband physical broadcast channel (NPBCH); a narrowband system information block 1 (SIB1-NB).
15. The method according to any one of claims 10 to 14, characterized in that, The period of the SI message is an integer multiple of the repetition pattern of the SI message.
16. The method according to any one of claims 10-15, characterized in that, The first offset is used to determine a starting position of the SI window in the period of the SI message.
17. The method of any of claims 10-16, wherein: a starting time domain position of a time domain resource pattern of a TDD frame corresponding to the terminal has an offset relative to a first subframe #0 in a first system frame SFN#0, and the offset is equal to the first offset.
18. The method of any of claims 10-17, wherein: the terminal does not expect a transport block size (TBS) corresponding to the SI message to exceed 120; or the TBS corresponding to the SI message does not exceed 120.
19. A terminal, characterized by The terminal includes: a transceiver configured to receive first information transmitted by a network device, the first information being used to determine a position of time domain resources where a system information (SI) message is located; the first information is used to indicate at least one of: a length of an SI window corresponding to the SI message; a first offset; a period of the SI message; a repetition pattern of the SI message; The SI message is located in a time division duplex (TDD) frame, and the SI message is transmitted in the SI window.
20. A network device, comprising: The network device includes: a transceiver configured to transmit first information to a terminal, the first information being used to determine a position of time domain resources where a system information (S I) message is located; the first information is used to indicate at least one of: a length SI window corresponding to the SI message; a first offset; a period of the SI message; repetition pattern of the SI message; The SI message is located in a time division duplex (TDD ) frame, and the SI message is transmitted in the SI window.
21. A terminal, characterized by The terminal includes: one or more processors; The terminal is configured to perform the communication method of any of claims 1-9.
22. A network device, comprising: The network device includes: one or more processors; The first network device is configured to perform the communication method of any of claims 10-18.
23. A communications device, characterized by The communication device is configured to perform the communication method of any of claims 1-9, 10-18.
24. A communication system, characterized by The terminal and the network device are configured to implement the communication method of any of claims 1-9 and 10-18, respectively.
25. A storage medium, the storage medium storing instructions, wherein, The instructions, when executed on the communication device, cause the communication device to perform the communication method of any of claims 1-9, 10-18.
26. A program product comprising at least one of a program, instructions, characterized in that At least one of the program and the instructions, when executed on the communication device, implements the communication method of any of claims 1-9, 10-18.