Communication methods, communication device, communication system, storage medium and program product
Patent Information
- Application Number
- PCT/CN2025/085512
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-27
- Publication Date
- 2026-10-01
Smart Images

Figure CN2025085512_01102026_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 communication methods, communication devices, communication systems, storage media, and program products. Background Technology
[0002] In a non-terrestrial network (NTN), a terminal can connect to a terrestrial base station via satellite. Summary of the Invention
[0003] How does a terminal determine valid random access information in NTN?
[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0005] In a first aspect, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:
[0006] Receive the Synchronization Signal Physical Broadcast Channel Block (SSB) sent by the network device;
[0007] Identify at least one first SSB for random access;
[0008] Within the time domain interval associated with the at least one first SSB, determine the random access information corresponding to the at least one first SSB, wherein the random access information includes a random access occupancy (RO) and / or a random access preamble.
[0009] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:
[0010] Send an SSB to the terminal, wherein the SSB is used by the terminal to determine at least one first SSB for random access, and the time domain interval associated with the at least one first SSB is used to determine the random access information corresponding to the at least one first SSB, wherein the random access information includes a random access timing (RO) and / or a random access preamble.
[0011] Thirdly, embodiments of this disclosure provide a communication device for performing the method described in the first or second aspect.
[0012] Fourthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,
[0013] The terminal is configured to implement the method as described in the first aspect;
[0014] The network device is configured to implement the method as described in the second aspect.
[0015] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...
[0016] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.
[0017] In a sixth aspect, an embodiment of this disclosure provides a program product comprising at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.
[0018] In this embodiment of the present disclosure, the terminal can select a suitable first SSB from the SSBs sent by the network device for random access. Based on the time domain interval associated with the first SSB, the random access information corresponding to the first SSB is determined within a certain time domain range, thereby ensuring the validity of the random access information and facilitating the network device to accurately receive the random access information, thus improving the success rate of random access. Attached Figure Description
[0019] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.
[0020] Figures 1A and 1B are exemplary schematic diagrams of the architecture of a communication system provided according to embodiments of the present disclosure;
[0021] Figure 1C is a schematic diagram illustrating beam-hopping transmission according to an embodiment of the present disclosure;
[0022] Figure 1D is a schematic diagram illustrating the SSB-RO mapping according to an embodiment of the present disclosure;
[0023] Figure 1E is a schematic diagram of an SSB configuration according to an embodiment of the present disclosure;
[0024] Figures 2A and 2B are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;
[0025] Figures 3A to 3D are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;
[0026] Figure 4A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure;
[0027] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure;
[0028] Figure 5A is a schematic diagram of a communication device according to an embodiment of the present disclosure;
[0029] Figure 5B is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation
[0030] This disclosure provides communication methods, communication devices, communication systems, storage media, and program products.
[0031] In a first aspect, embodiments of this disclosure propose a communication method executed by a terminal, the method comprising:
[0032] Receive synchronization signal block (SSB) sent by the network device;
[0033] Identify at least one first SSB for random access;
[0034] Within at least one time-domain interval associated with a first SSB, determine random access information corresponding to at least one first SSB, wherein the random access information includes random access timing (RO) and / or random access preamble.
[0035] In the above embodiments, the terminal can select a suitable first SSB from the SSBs sent by the network device for random access. Based on the time domain interval associated with the first SSB, the random access information corresponding to the first SSB is determined within a certain time domain range, thereby ensuring the validity of the random access information and facilitating the network device to accurately receive the random access information, thus improving the success rate of random access.
[0036] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:
[0037] Receive configuration information sent by network devices, including time domain range information.
[0038] In the above embodiments, the terminal can learn the time domain interval associated with the first SSB through the configuration information of the network device, and thus can use the configured time domain interval to determine valid random access information, thereby improving the success rate of random access.
[0039] In conjunction with the embodiments of the first aspect, in some embodiments, the information of the time domain interval includes at least one of the following:
[0040] The duration of the time window corresponding to the time domain interval;
[0041] The time domain interval corresponds to the period of the time window;
[0042] The time domain interval corresponds to the starting offset of the time window.
[0043] In the above embodiments, the terminal can determine the position of the time domain interval based on at least one of the duration, period and starting offset of the time window, which improves the configuration flexibility and the efficiency of determining valid random access information.
[0044] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:
[0045] The start time of the time domain interval is determined based on the time domain location of at least one first SSB burst.
[0046] In the above embodiments, the terminal can accurately determine the start time of the time domain interval based on the time domain location of the SSB burst where at least one first SSB is located. Combined with the duration of the time window, the time domain interval can be accurately determined, which is beneficial for saving configuration parameters.
[0047] In conjunction with the embodiments of the first aspect, in some embodiments, the start time is one of the following:
[0048] The starting time domain location of the SSB burst;
[0049] The domain location at the end of the SSB burst;
[0050] The time-domain unit where the SSB burst occurs.
[0051] In the above embodiments, any one of the starting time domain position, ending time domain position, and time domain unit of the SSB burst can be used as the start time of the time domain interval, thereby improving configuration flexibility and applicability to different scenarios.
[0052] In conjunction with the embodiments of the first aspect, in some embodiments, the start time of the time domain interval is determined based on the start offset and the set frame.
[0053] In the above embodiments, the start time of the time domain interval is determined based on the start offset and the set frame, thereby improving the accuracy of determining the position of the time domain interval.
[0054] In conjunction with the embodiments of the first aspect, in some embodiments,
[0055] The starting offset is the default value or 0.
[0056] The above embodiments can improve the applicability of determining the start time in different scenarios.
[0057] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:
[0058] The time domain interval is determined based on the configuration period and / or association period associated with at least one first SSB as defined in the protocol.
[0059] In the above embodiments, at least one configuration period and / or association period associated with a first SSB is defined. Based on this, the time domain interval position associated with the first SSB can be accurately determined, improving the accuracy of determining the time domain interval position, facilitating the determination of valid random access information, and improving the success rate of random access.
[0060] In conjunction with the embodiments of the first aspect, in some embodiments,
[0061] The maximum value of the configuration period is: the beam duration of at least one first SSB corresponding to the transmitted beam; and / or,
[0062] The maximum value of the association period is determined based on the beam duration and configuration period of at least one first SSB corresponding to the transmitted beam.
[0063] In the above embodiments, the maximum value of the configuration period and / or the maximum value of the associated period are related to the beam duration of the transmitted beam corresponding to at least one first SSB, thereby determining the time domain interval associated with at least one first SSB and improving the accuracy of determining the location of the time domain interval.
[0064] In conjunction with the embodiments of the first aspect, in some embodiments,
[0065] The maximum value of the association period is: floor(Tdwell / configuration period), where Tdwell represents the beam duration and floor represents the floor operation.
[0066] In the above embodiments, the maximum value of the association period is determined based on the beam duration, which facilitates the accurate determination of the time domain interval of at least one first SSB association.
[0067] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:
[0068] Send capability information to network devices. The capability information is used to indicate whether the terminal supports the ability to determine random access information in at least one time domain interval associated with a first SSB in a non-terrestrial network (NTN).
[0069] In the above embodiments, the terminal sends capability information to the network device to inform the network device of its relevant capabilities, which facilitates the network device to schedule or configure based on the terminal's capabilities, thereby improving the accuracy of scheduling or configuration.
[0070] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:
[0071] The device receives indication information sent by a network device, which is used to instruct the terminal to enable or activate the function of determining random access information within at least one time domain interval associated with a first SSB.
[0072] In the above embodiments, the terminal determines to enable or activate relevant functions based on the indication information from the network device. In this case, the network device can perform appropriate scheduling or configuration to improve the accuracy of scheduling or configuration.
[0073] In conjunction with the embodiments of the first aspect, in some embodiments,
[0074] The first period used to send an SSB includes multiple second periods, with at least one first SSB located within any of the second periods.
[0075] In the above embodiments, within different second periods, random access information within each second period can be accurately determined based on at least one time-domain interval associated with a first SSB, thereby improving the success rate of random access.
[0076] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:
[0077] Send an SSB to the terminal, wherein the SSB is used by the terminal to determine at least one first SSB for random access, and the time domain interval associated with the at least one first SSB is used to determine the random access information corresponding to the at least one first SSB, wherein the random access information includes random access timing (RO) and / or random access preamble.
[0078] In the above embodiments, the network device sends an SSB to the terminal, enabling the terminal to select a suitable first SSB for random access. Thus, the terminal can determine the random access information corresponding to the first SSB within a certain time domain range based on the time domain interval associated with the first SSB, thereby ensuring the validity of the random access information and facilitating the network device to accurately receive the random access information, thereby improving the success rate of random access.
[0079] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:
[0080] Send configuration information to the terminal, which includes information about the time domain range.
[0081] In conjunction with embodiments of the second aspect, in some embodiments, the information of the time domain interval includes at least one of the following:
[0082] The duration of the time window corresponding to the time domain interval;
[0083] The time domain interval corresponds to the period of the time window;
[0084] The time domain interval corresponds to the starting offset of the time window.
[0085] In conjunction with the embodiments of the second aspect, in some embodiments, the start time of the time domain interval is determined based on the time domain location of the SSB burst to which at least one first SSB is located.
[0086] In conjunction with the embodiments of the second aspect, in some embodiments, the start time is one of the following:
[0087] The starting time domain location of the SSB burst;
[0088] The domain location at the end of the SSB burst;
[0089] The time-domain unit where the SSB burst occurs.
[0090] In conjunction with the embodiments of the second aspect, in some embodiments, the start time of the time domain interval is determined based on the start offset and the set frame.
[0091] In conjunction with the embodiments of the second aspect, in some embodiments, the starting offset is a default value or 0.
[0092] In conjunction with the embodiments of the second aspect, in some embodiments, the time domain interval is determined according to the configuration period and / or association period associated with at least one first SSB as defined by the protocol.
[0093] In conjunction with the embodiments of the second aspect, in some embodiments, the maximum value of the configuration period is: the beam duration of at least one first SSB corresponding to the transmitted beam; and / or,
[0094] The maximum value of the association period is determined based on the beam duration and configuration period of at least one first SSB corresponding to the transmitted beam.
[0095] In conjunction with the embodiments of the second aspect, in some embodiments, the maximum value of the association period is: floor(Tdwell / configuration period), where Tdwell represents the beam duration and floor represents the floor operation.
[0096] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:
[0097] The terminal receives capability information sent by the terminal. The capability information is used to indicate whether the terminal supports the ability to determine random access information in at least one time domain interval associated with a first SSB in a non-terrestrial network (NTN).
[0098] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:
[0099] Send indication information to the terminal, the indication information being used to instruct the terminal to enable or activate the function of determining random access information within at least one time domain interval associated with a first SSB.
[0100] In conjunction with the embodiments of the second aspect, in some embodiments, the first period for transmitting the SSB includes a plurality of second periods, and at least one first SSB is located in any of the second periods.
[0101] Thirdly, embodiments of this disclosure provide a communication device for performing the method described in the first or second aspect.
[0102] Fourthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,
[0103] The terminal is configured to implement the method as described in the first aspect;
[0104] The network device is configured to implement the method as described in the second aspect.
[0105] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...
[0106] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.
[0107] In a sixth aspect, an embodiment of this disclosure provides a program product comprising at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.
[0108] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., 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.
[0109] This disclosure provides communication methods, communication devices, communication systems, storage media, and program products. In some embodiments, terms such as communication method and information processing method may be used interchangeably.
[0110] 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.
[0111] 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.
[0112] 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.
[0113] In the embodiments disclosed herein, "multiple" refers to two or more.
[0114] In some embodiments, the terms "at least one of A or B, at least one of A and B", "one or more", "a plurality of", "multiple" and the like can be used interchangeably.
[0115] 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.
[0116] 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.
[0117] 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.
[0118] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0119] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0120] 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.
[0121] 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”.
[0122] 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.
[0123] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0124] 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.
[0125] 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.
[0126] 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.
[0127] 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.
[0128] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0129] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0130] 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.
[0131] Figures 1A and 1B are schematic diagrams of the architecture of a communication system according to embodiments of the present disclosure.
[0132] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102.
[0133] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things 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, and wireless terminal device in smart home, but is not limited thereto.
[0134] In some embodiments, network device 102 may be a network device in a TN or NTN.
[0135] For example, as shown in Figure 1B, in the NTN communication system 100, network device 102 may include satellites and base stations, and terminal 101 can communicate with base stations via satellites. Here, satellites can also be called satellite stations or satellite base stations, and base stations refer to ground stations or ground base stations.
[0136] In some embodiments, network device 102 may include at least one of access network device and core network device. In an NTN, the access network device may correspond to a base station or terrestrial base station.
[0137] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.
[0138] 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.
[0139] 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.
[0140] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
[0141] 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.
[0142] The following embodiments of this disclosure can be applied to the communication system 100 or some of the main bodies shown in FIG1A or FIG1B, but are not limited thereto. The main bodies shown in FIG1A or FIG1B are illustrative. The communication system may include all or some of the main bodies in FIG1A or FIG1B, or may include other main bodies other than those in FIG1A or FIG1B. 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.
[0143] The embodiments disclosed herein can be applied to 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), IEEE 802.16 (WiMAX), and 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, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0144] In some implementations, in non-terrestrial network (NTN) scenarios, the satellite's equivalent isotropically radiated power (ERIP) is limited, preventing the satellite from simultaneously covering all beam areas. According to Radio Access Network (RAN) 1 agreements, the parameters for satellite beam coverage are shown in Tables 1-1 to 1-3:
[0145] Table 1-1
[0146] Wherein, *: The reference configuration ElRP limit is 61.24 dBm. **: Assumes 100% resource block (RB) utilization within the same beam at maximum power. The absolute number of simultaneously active beams is up to 212 (due to RF limitations). ***: For a 600km constellation design, a low elevation angle of 30° and a selected beam size (e.g., parameters in set1). Note 1: This beam size is at least included in this scenario; larger beam sizes can be based on evaluation and reporting.
[0147] Table 1-2
[0148] Wherein, *: The EIRP limit for the reference configuration is 53dBm. **: The absolute number of simultaneously active beams is up to 16 (due to RF limitations). Note 1: This scenario includes at least this beam size; larger beam sizes can be based on evaluation and reporting.
[0149] Table 1-3
[0150] Wherein, *: The reference configuration EIRP limit is 53.24dBm. **: The absolute number of simultaneously active beams is up to 212 (due to RF limitations). Note 1: This scenario includes at least this beam size; larger beam sizes can be based on evaluation and reporting.
[0151] In some implementations, satellites can improve beam coverage by beam hopping. To achieve full beam coverage without increasing the number of SSBs, beam hopping is used. As shown in Figure 1C, using the parameters in Table 1-2 as an example, assuming the default SSB period is extended to 80ms, the network device sends an SSB every 20ms. However, within 80ms, the beam (or physical beam, satellite beam) used to send the SSB is different every 20ms. For example, the beams in the first 20ms are beam#1-16, and the beams in the second 20ms are beam#17-32. The number of beams sending SSBs can be 4. One SSB index can correspond to 4 satellite beams. For SSB indexes SSB#1-4, 16 satellite beams can be sent within 20ms using Time Division Multiplexing (TDM). A total of 64 satellite beam points need to be covered within 80ms.
[0152] In some implementations, for the mapping between RO and SSB, according to existing protocols, network devices configure the time-frequency resources of RO for the terminal through RO parameters. The UE maps the RO and SSB beams according to the mapping parameters and specific rules (such as TS38.213). The RO parameters may include the Physical Random Access Channel (PRACH) configuration period, system frame number, subframe number, start symbol index, etc. The mapping parameters include msg1-frequency division multiplexing (FDM), the number of synchronization blocks for each random access channel timing, and the number of contention-based access preambles corresponding to each synchronization block (ssb-perRACH-OccasionAndCB-PreamblesPerSSB, abbreviated as ssb-perRO). msg1-FDM defines how many ROs are available on the same time resource but different frequency domain resources, and ssb-perRO defines how many SSBs correspond to one RO and how many preambles correspond to one SSB.
[0153] In some implementations, an association period, starting from frame 0, is used to map SSB (or SS / PBCH block) indexes to RO (or PRACH occasions). This association period can be determined by the smallest integer in the set of PRACH configuration periods defined in Tables 1-4, such that within this association period, Each SSB index is mapped to the RO at least once. The terminal can obtain the "ssb-PositionsInBurst" value from System Information Block (SIB) 1, Serving Cell Configuration Common Information (ServingCellConfigCommon), or SSB-Machine Type Communication (MTC)-Additional Physical Cell Identifier (PCI). If, within a single association cycle, after an integer number of mapping cycles from SSB indexes to ROs, there exists a set of ROs or PRACH preambles that have not been mapped... If an RO is not associated with an SSB index, then no SSB index will be mapped to this RO or PRACH preamble. An association pattern period contains one or more association periods, determined in such a way that the pattern between the RO and the SSB index repeats at most once every 160ms. After an integer number of association periods, if there are ROs not associated with an SSB index, these ROs will not be used for PRACH transmission.
[0154] The PRACH configuration cycle and the associated cycle have the mapping relationship shown in Table 1-4:
[0155] Table 1-4
[0156] In some implementations, the RO to SSB mapping mechanism has problems in NTN scenarios. Taking Tables 1-1 to 1-3 above as examples, in order to ensure that beams in different regions have available RO resources, according to the existing RO resource configuration method, RO resources are calculated starting from frame 0 and appear periodically, and are cyclically bound to the effective SSB beams. The protocol only limits the terminal to select the RO resource corresponding to the selected SSB beam for transmission. When there are multiple such RO resources, the protocol does not restrict the UE to select which RO resource to transmit.
[0157] For example, as shown in Figures 1C and 1D, suppose that physical beam #1 is associated with SSB #1 in the first 20ms (i.e., 10ms and 20ms), and physical beam #17 is associated with SSB #1 in the second 20ms (i.e., 30ms and 40ms). Both are associated with the same SSB index. Beam #1 can correspond to the ROs associated with or mapped by SSB #1, assuming the four ROs at time domain position t1. Beam #17 can correspond to the ROs associated with SSB #1, assuming the four ROs at time domain position t2. However, according to the existing protocol's RO-SSB mapping relationship, the protocol does not distinguish between physical beams with the same SSB index; that is, both physical beam 1 and physical beam 17 correspond to SSB #1. When the terminal maps ROs to the SSB #1 corresponding to beam #1 or beam #17, all eight ROs at time domain positions t1 and t2 can be selected for mapping. However, a user who selects SSB#1 corresponding to physical beam 1 might choose the RO resource bound to SSB#1 corresponding to physical beam 17 for preamble transmission, or vice versa. For example, when a terminal maps an RO to SSB#1 corresponding to beam#17, it might map to one of the four ROs at time domain position t1. At this time, if network devices such as satellites have switched their physical beams from beam#1 to beam#17, the network devices will not be able to receive the preamble signal transmitted by the terminal on the RO at time domain position t1. It is worth noting that the relevant period diagram in Figure 1D is only for illustrating the problem and does not limit the positions of each period.
[0158] In some implementations, an offset can be introduced to configure the position of the RO relative to the SSB, which can support the same beam footprint, and the period of the RO resource can be configured to be larger.
[0159] For example, ROs are mapped to SSBs, and the association period starts from frame 0. For a given RO, its time and frequency resources may overlap with ROs associated with SSBs transmitted in different beam coverage areas. Avoiding RO resource overlap across different beam coverage areas can be challenging without RO offset configuration. If the number of beam coverage areas with overlapping ROs is greater than the number of uplink receive active beams, network devices such as gNBs cannot detect PRACH from all beam coverage areas. Introducing RO offset can provide configuration flexibility to avoid overlap of ROs from different beam coverage areas. As shown in Figure 1E, with the introduction of random access timing offset (RO-offset), ROs can be configured starting from radio frames other than frame 0 within an SSB period. Furthermore, configuring the RO starting from radio frame 0 allows for better flexibility in RO offset configuration. For different beam coverage areas, when different SSBs need to be transmitted in TDM mode within an extended SSB period, the RO start may need to be closer to the corresponding SSB location within the beam coverage area. This provides better RO offset configuration flexibility to support the appropriate RO location configuration relative to the SSB. However, in this implementation, introducing an offset to configure the RO position relative to the SSB requires that RO resources be concentrated within a single frame; that is, available resources in each period are concentrated in one frame. This imposes constraints on base station configuration and limits the terminal's ability to determine RO resources.
[0160] Based on the description of the above implementation method, in the case of beam hopping in NTN, the terminal lacks a method to determine valid random access information, so as to solve the problem that the network device may not be able to receive the terminal preamble.
[0161] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, a communication method according to an embodiment of the present disclosure includes:
[0162] In step S2101, terminal 101 sends capability information to network device 102.
[0163] In some embodiments, network device 102 receives capability information sent by terminal 101.
[0164] In some embodiments, capability information is used to indicate whether terminal 101 supports the ability of NTN to determine random access information within a time domain interval associated with at least one first SSB. For ease of description, the ability of NTN to determine random access information within a time domain interval associated with at least one first SSB will be referred to as the first capability.
[0165] Optionally, if terminal 101 supports the first capability, the terminal can indicate that it supports the first capability through the capability information, such as indicating that terminal 101 supports the first capability by using a 1-bit value in the capability information as a first value; if terminal 101 does not support the first capability, the terminal can indicate that it does not support the first capability through the capability information, such as indicating that terminal 101 does not support the first capability by using a 1-bit value in the capability information as a second value. The first value can be 0 and the second value can be 1; or the first value can be 1 and the second value can be 0.
[0166] Optionally, the first SSB is used to represent the SSB used for random access. The random access information includes RO and / or random access preamble. The time domain interval associated with the first SSB is used to characterize the time domain interval in which the RO mapped by the first SSB is located. For a detailed explanation of how the terminal 101 determines the random access information in at least one time domain interval associated with the first SSB in the NTN, please refer to the following steps S2104-S2107, which will not be repeated here.
[0167] 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.
[0168] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.
[0169] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “time range,” “duration,” “segment,” “time window,” “window,” and “time.”
[0170] 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.
[0171] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0172] 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.
[0173] In step S2102, network device 102 sends instruction information to terminal 101.
[0174] In some embodiments, terminal 101 receives indication information sent by network device 102.
[0175] In some embodiments, the indication information is used to indicate the function of enabling or activating terminal 101 to determine random access information within at least one time domain interval associated with a first SSB, which may be referred to as a first function, a first feature, or a first characteristic, etc.
[0176] Optionally, the first function may also indicate the function of determining random access information within a time domain interval associated with at least one first SSB in a beam-hopping scenario.
[0177] In some embodiments, network device 102 may enable or activate a first function if terminal 101 supports a first capability. For example, if capability information indicates that terminal 101 supports a first capability, network device 102 may instruct the activation of the first function through indication information, thereby enabling terminal 101 to determine valid random access information in subsequent steps.
[0178] In some embodiments, network device 102 may assume that terminal 101 supports the first capability and enable or activate the first function by indicating information. In this case, step S2101 is optional or may be omitted.
[0179] In some embodiments, network device 102 may broadcast instruction information.
[0180] In some embodiments, the network device 102 enables or activates the first function by indicating information, as shown in the following examples:
[0181] In one example, the indication information includes a first parameter, through which network device 102 instructs terminal 101 whether to enable a first function. If network device 102 enables the first function (if [network] enabled), the terminal can determine random access information within the time domain interval associated with the first SSB based on the first function, as described in the following embodiment.
[0182] In one example, when network device 102 indicates that a first function is enabled, or indicates other relevant parameters, such as when the second parameter of the indication information indicates an NTN scenario or beam hopping, terminal 101 can determine random access information within the time domain interval associated with the first SSB based on the first function, as shown in steps S2103-S2107. In this example, network device 102 may assume that the terminal supports the first capability.
[0183] In one example, if the indication information indicates that the first function is enabled, or indicates other relevant parameters, such as if the indication information indicates an NTN scenario or beam hopping, the terminal 101 supporting the first capability can use the process shown in subsequent steps S2103-S2107 to determine valid random access information.
[0184] In some embodiments, this disclosure describes an example where, when terminal 101 supports the first capability, network device 102 also sends indication information to terminal 101. In another embodiment, if terminal 101 supports the first capability, network device 102 may enable or activate the first function by default after receiving the capability information. In this case, step S2102 is optional or can be omitted, that is, network device 102 may not send the indication information to terminal 101.
[0185] In step S2103, network device 102 sends configuration information to terminal 101.
[0186] In some embodiments, terminal 101 receives configuration information sent by network device 102.
[0187] In some embodiments, the configuration information includes information about the time domain interval.
[0188] Optionally, the time domain interval information is used to indicate the time domain interval associated with the SSB (such as the first SSB in the following embodiment) selected by terminal 101.
[0189] Optionally, referring to Figure 1C, when transmitting SSBs with the same index within different 20ms intervals, these SSBs with the same index can be associated with different time domain intervals, or in other words, beams transmitting within different 20ms intervals can be associated with different time domain intervals. For example, for SSB indexes #1-4, multiple beams transmitting SSB#1 within the first 20ms can be associated with time domain interval 1, beams transmitting SSB#1 within the second 20ms can be associated with time domain interval 2, beams transmitting SSB#1 within the third 20ms can be associated with time domain interval 3, and beams transmitting SSB#1 within the fourth 20ms can be associated with time domain interval 4.
[0190] In some embodiments, the information of the time domain interval includes at least one of the following:
[0191] The time domain interval corresponds to the duration of the time window; where the duration of the time window is the length of the time window (window duration).
[0192] The time domain interval corresponds to the period of the time window.
[0193] The time domain interval corresponds to the starting offset of the time window.
[0194] Optionally, the duration of the time window can be several frames, such as X frames, or ms.
[0195] Optionally, the duration of the time window can be less than or equal to 20ms. Alternatively, the duration of the time window can be less than or equal to the second period in the following embodiments.
[0196] Optionally, the starting offset is the default value or 0. The default value can be 1, 2, or other settings.
[0197] Alternatively, the time window can also be called a time-domain window.
[0198] Optionally, the information in different time domain intervals can be the same or different.
[0199] In some embodiments, the time domain interval may be aperiodic, in which case the configuration information may only configure the duration of the time window, or the configuration information may configure the duration and start offset of the time window. In some embodiments, the time domain interval may be periodic, in which case the configuration information may configure the duration and period of the time window, or the configuration information may configure the duration, start offset, and period of the time window.
[0200] In step S2104, network device 102 sends an SSB to terminal 101.
[0201] In some embodiments, terminal 101 receives SSB sent by network device 102.
[0202] Optionally, network device 102, such as a satellite, can transmit SSBs using a beam-hopping method. For example, network device 102 may transmit multiple SSBs, with the number of corresponding SSB indices being up to 4, such as SSB#1-4 (or denoted as SSB index#1-4).
[0203] In some embodiments, the period for sending SSB may include a first period and a second period.
[0204] Optionally, network device 102 sends an SSB to terminal 101 within the first period. The first period can be the default period or the default extended period for sending SSBs. For example, as shown in Figure 1C, the first period can be 80ms, 160ms, or other durations.
[0205] Optionally, the first period includes multiple second periods, and the network device 102 sends an SSB to the terminal 101 using a different beam in each second period. As shown in Figure 1C, the first period is 80ms and the second period is 20ms. Within the 80ms period, the network device 102 sends an SSB using a different beam every 20ms.
[0206] Optionally, the SSB index sent by network device 102 to terminal 101 can be the same in different second cycles within a first cycle. For example, in the example of Figure 1C, a first cycle includes four second cycles, and the SSBs sent in each second cycle are SSB#1-4.
[0207] In one example, network device 102 transmits SSBs with different beams in different second cycles within a first cycle. As shown in Figure 1C, the first cycle includes four second cycles. In the first second cycle or the first 20ms, the beams transmitting SSBs#1-4 are beams#1-16; in the second second cycle or the second 20ms, the beams transmitting SSBs#1-4 are beams#17-32; in the third second cycle or the third 20ms, the beams transmitting SSBs#1-4 are beams#33-48; and in the fourth second cycle or the fourth 20ms, the beams transmitting SSBs#1-4 are beams#49-64.
[0208] Optionally, one SSB index corresponds to at least one beam. For example, one SSB index can correspond to four first beams. The number of SSB beams transmitted by network device 102 at the same time can be four. If one SSB index corresponds to four beams, network device 102 can transmit 16 beams in TDM mode within each 20ms.
[0209] Alternatively, the beam can also be called a satellite beam or a physical beam.
[0210] In step S2105, terminal 101 determines at least one first SSB for random access.
[0211] In some embodiments, the first SSB represents the SSB selected by terminal 101 for random access.
[0212] In some embodiments, at least one first SSB for random access may be random access based on random access information such as RO (or RO resource) associated or mapped by at least one first SSB.
[0213] In some embodiments, terminal 101 determines one or more first SSBs based on the SSB sent by network device 102 in step S2103.
[0214] In some embodiments, terminal 101 may determine or select the first SSB based on a variety of methods.
[0215] In some embodiments, terminal 101 may randomly select at least one first SSB from the received SSBs. For example, upon receiving SSB index#1-4, at least one of SSB index#1-4 may be determined as the first SSB for random access, such as determining SSB index#1 as the first SSB for random access.
[0216] In some embodiments, terminal 101 can measure each received SSB, obtain a measurement result for each SSB, and determine the SSB whose measurement result is greater than a first threshold as the first SSB. Optionally, the measurement result can be the Reference Signal Receiving Power (RSRP) or other results representing the signal quality of the SSB. The first threshold can be the RSRP threshold.
[0217] Optionally, random access can be either contention-based random access (CBRA) or contention-free random access (CFRA).
[0218] In some embodiments, at least one first SSB is located within any second cycle. For example, a first cycle includes four second cycles, and at least one first SSB may be located within the first second cycle. Alternatively, at least one first SSB may represent an SSB selected by the terminal within a second cycle.
[0219] Step S2106, terminal 101 determines the time domain interval.
[0220] In some embodiments, the terminal 101 can obtain relevant time domain information of the time domain interval based on the configuration information, thereby determining the location of the time domain interval, such as determining the start time of the time domain interval.
[0221] In the first embodiment, the configuration information configures the duration of the time window, or configures both the duration and period of the time window. In this embodiment, the start offset of the time window may not be configured, or the start offset may be a default value or 0.
[0222] In this embodiment, terminal 101 determines the start time of the time domain interval based on the time domain location of at least one first SSB in the SSB burst.
[0223] In this embodiment, the start time of the time domain interval is the relative time with respect to the SSB burst location.
[0224] Optionally, the start time is one of the following:
[0225] The starting time domain location of the SSB burst;
[0226] The domain location at the end of the SSB burst;
[0227] The time-domain unit where the SSB burst occurs.
[0228] Optionally, the start time-domain location, end time-domain location, or time-domain cell of an SSB burst can be represented by a corresponding frame. For example, if the time-domain cell of an SSB burst containing a first SSB is flagship0, flagship0 can be determined as the start time of the time-domain interval.
[0229] Optionally, for non-periodic time windows, after determining the start time of the time domain interval, the terminal 101 can determine the position of the time domain interval based on the start time and the duration of the time window, thereby determining the RO associated with the first SSB in the time domain interval.
[0230] Optionally, for periodic time windows, after determining the start time of the time domain interval, terminal 101 can determine the position of the periodic time domain interval based on the start time, the duration of the time window, and the period of the time window. For example, the start time of the time domain interval is frame0, the period is window periodicity, and the start times of each periodic time domain interval are frame0, frame0 + window periodicity, frame0 + 2 * window periodicity, ... The timing of each time domain interval is [frame 0, frame 0 + window duration], [frame 0 + window periodicity, frame 0 + window periodicity + window duration], [frame 0 + 2 * window periodicity, frame 0 + 2 * window periodicity + window duration], ...
[0231] In the second embodiment, the configuration information configures the duration and start offset of the time window; or, the configuration information configures the duration, start offset, and period of the time window.
[0232] In this embodiment, terminal 101 determines the start time of the time domain interval based on the start offset and the set frame. The set frame is a frame defined by the protocol or agreed upon in advance; for example, the set frame can be frame0, frame1, or other frames.
[0233] In this embodiment, the start time of the determined time domain interval can be an absolute time, such as frame X.
[0234] Optionally, for a non-periodic time window, assuming the frame is set to frame0 and the starting offset is offset, the terminal can determine the start time of the time domain interval as frame0 + offset. After determining the start time of the time domain interval, the terminal 101 can determine the position of the time domain interval based on the start time and the duration of the time window, thereby determining the RO associated with the first SSB within that time domain interval.
[0235] Optionally, for periodic time windows, after determining the start time of the time domain interval based on the start offset and the set frame, the terminal 101 can determine the position of the periodic time domain interval based on the period of the time window. For example, if the set frame is frame0, the start offset is offset, and the period is window periodicity, then the start times of each periodic time domain interval are determined sequentially as frame0 + offset, frame0 + offset + window periodicity, frame0 + offset + 2 * window periodicity, ... The occurrence times of each time domain interval are sequentially [frame0 + offset, frame0 + offset + window duration], [frame0 + offset + window periodicity, frame0 + offset + window periodicity + window duration], [frame0 + offset + 2 * window periodicity, frame0 + offset + 2 * window periodicity + window duration], ...
[0236] In some embodiments, when the time window is periodic, the periodic configuration can achieve multiple windowing, thereby determining the corresponding time domain interval for SSBs of different beams, which facilitates the determination of effective random access information.
[0237] 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.
[0238] In step S2107, terminal 101 determines random access information corresponding to at least one first SSB within the time domain interval associated with at least one first SSB.
[0239] In some embodiments, random access information includes RO and / or random access preamble.
[0240] In some embodiments, terminal 101 determines random access information starting from the start time of at least one time domain interval associated with a first SSB, and within the duration of the corresponding time window of that time domain interval.
[0241] Optionally, taking the random access information as RO and the first SSB as SSB#1 as an example, as shown in Figure 1D, when terminal 101 determines the RO associated with SSB#1 corresponding to beam#1, it needs to determine the RO within the time domain interval associated with SSB#1. That is, only the RO within this time domain interval is usable. For example, if the time domain interval is 20ms, then the terminal needs to determine the RO within 20ms of the location of SSB#1. Therefore, during the process of mapping RO to SSB#1 corresponding to beam#1, terminal 101 can only map the RO corresponding to position t1, and will not map to the RO corresponding to position t2, thus ensuring that a valid RO is determined. Based on the preamble sent by this RO, network device 102 can receive it accurately.
[0242] In one example, different second periods within a first period can be considered as different beam coverage areas, and each second period or each beam coverage area can determine a corresponding time domain interval.
[0243] In another example, for different first periods, a corresponding second period can correspond to the same or related time domain intervals.
[0244] In some embodiments, in the NTN, the duration of the RO or RO resource is consistent with the duration of each beam's duration or dwell time. Referring to Figure 1C, the RO resources bound to the first SSB1-4 (beam#1-16) in Figure 1C are 10-20ms, the RO resources bound to the second SSB#1-4 (beam#17-32) are 30-40ms, and so on. Each physically transmitted beam has a corresponding RO resource.
[0245] In some embodiments, the terminal 101 determines the mapping relationship between the first SSB and RO based on a protocol definition. The difference in this embodiment lies in the limitation of the time domain interval, rather than the restriction on the mapping order or mapping relationship.
[0246] It should be noted that the above embodiment describes the determination of the time domain interval within a first cycle. In other embodiments, the time domain interval associated with the SSB of the same beam can be the same in different first cycles. For example, the time domain interval associated with the SSB of beam1 within 10-20ms in the first first cycle (0-80ms) is the same as the time domain interval associated with the SSB of beam1 within 90ms-100ms in the second first cycle (80ms-160ms). Therefore, the time domain interval associated with the SSB of the same beam can be applied cyclically based on the first cycle.
[0247] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2107. For example, steps S2104, S2105 and S2107 may be implemented as independent embodiments, and step S2107 may be implemented as an independent embodiment, but is not limited thereto.
[0248] In some embodiments, steps S2101, S2102, S2103, and S2106 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0249] In some embodiments, steps S2101 and S2102 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0250] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0251] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, a communication method according to an embodiment of the present disclosure includes:
[0252] In step S2201, terminal 101 sends capability information to network device 102.
[0253] In some embodiments, the implementation of step S2201 can be found in the implementation of step S2101 in FIG2A.
[0254] In step S2202, network device 102 sends instruction information to terminal 101.
[0255] In some embodiments, the implementation of step S2202 can be found in the implementation of step S2102 in FIG2A.
[0256] In step S2203, network device 102 sends an SSB to terminal 101.
[0257] In some embodiments, the implementation of step S2203 can be referred to the implementation of step S2104 in FIG2A.
[0258] In step S2204, terminal 101 determines at least one first SSB for random access.
[0259] In some embodiments, the implementation of step S2204 can be referred to the implementation of step S2105 in FIG2A.
[0260] In step S2205, terminal 101 determines the time domain interval according to the configuration period and / or association period associated with at least one first SSB defined in the protocol.
[0261] In some embodiments, a configuration period (or PRACH configuration period) and / or association period applicable to the NTN scenario are defined by the protocol, as shown in Table 2-1, for at least one first SSB association, thereby making the way the first SSB maps RO different from the associated way.
[0262] In some embodiments, as shown in Table 2-1, the maximum value of the configuration period is: the beam duration (or beam illumination duration) Tdwell of the transmit beam corresponding to at least one first SSB. Referring to Figure 1D, the configuration period associated with the first SSB corresponding to different beams can be 10ms, 20ms, 40ms, or Tdwell.
[0263] In some embodiments, the maximum value of the association period is determined based on the beam duration and configuration period of the transmit beam corresponding to at least one first SSB.
[0264] Optionally, the maximum value of the association period is: floor(Tdwell / configuration period), where Tdwell represents the beam duration and floor represents the floor operation.
[0265] For example, if the configuration period is 10ms and the maximum configuration period is Tdwell ms, then the maximum value of the associated period can be determined to be floor(Tdwell / 10). As another example, if the configuration period is 20ms and the maximum configuration period is Tdwell ms, then the maximum value of the associated period can be determined to be floor(Tdwell / 20). And as yet another example, if the configuration period is Tdwell ms and the maximum configuration period is Tdwell ms, then the maximum value of the associated period can be determined to be 1.
[0266] Optionally, Tdwell is a predefined duration, or Tdwell is a duration configured for network device 102.
[0267] Table 2-1
[0268] In some embodiments, based on the definitions of configuration period and / or association period in Table 2-1, terminal 101 can determine the associated time domain interval for the first SSB.
[0269] In step S2206, terminal 101 determines random access information corresponding to at least one first SSB within the time domain interval associated with at least one first SSB.
[0270] Optionally, still referring to the examples shown in Figures 1C and 1D, due to the adjustment of the maximum value of the configuration period and / or association period, the association period may become smaller, and the time domain range for the terminal to select RO resources will correspondingly become smaller. For example, the time domain interval associated with the first SSB (SSB#1) corresponding to beam#1 will be narrowed to within 20ms. If the terminal can only map the RO at time domain position t1, the RO resource at time domain position t2 is not available for mapping the SSB corresponding to beam#1. Thus, the terminal determines the RO of the first SSB corresponding to beam#1 within a certain time domain range of the first SSB. Correspondingly, for the first SSB corresponding to beam#17, the terminal 101 will also determine it within its associated time domain interval, thereby ensuring that the determined RO is valid, so that the network device 102 can receive the preamble sent on that RO.
[0271] In some embodiments, other implementations of step S2206 may also refer to the implementation of step S2107 in FIG2A.
[0272] In some embodiments, in the manner of the embodiment of FIG2B, the relevant information of the time window in FIG2A can also be configured, thereby configuring the period and / or associated period based on the relevant information of the time window, determining the time domain interval or time domain range, and mapping RO in the time domain interval or time domain range.
[0273] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2206. For example, steps S2203, S2204 and S2206 may be implemented as independent embodiments, and S2206 may be implemented as an independent embodiment, but are not limited thereto.
[0274] In some embodiments, steps S2201, S2202, and S2205 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0275] In some embodiments, steps S2201 and S2202 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0276] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0277] Figure 3A is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, a communication method according to an embodiment of the present disclosure includes:
[0278] In step S3101, network device 102 sends an SSB to terminal 101.
[0279] In some embodiments, the implementation of step S3101 can be referred to the implementation of step S2104 in FIG2A.
[0280] In step S3102, terminal 101 determines at least one first SSB for random access.
[0281] In some embodiments, the implementation of step S3102 can be referred to the implementation of step S2105 in FIG2A.
[0282] In step S3103, terminal 101 determines random access information corresponding to at least one first SSB within the time domain interval associated with at least one first SSB.
[0283] In some embodiments, the implementation of step S3103 can be found in the implementation of step S2107 in FIG2A or step S2206 in FIG2B.
[0284] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0285] Figure 3B is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, a communication method according to an embodiment of the present disclosure includes:
[0286] In step S3201, network device 102 sends an SSB to terminal 101.
[0287] In some embodiments, the implementation of step S3201 can be referred to the implementation of step S2104 in FIG2A.
[0288] In step S3202, terminal 101 determines at least one first SSB for random access.
[0289] In some embodiments, the implementation of step S3202 can be referred to the implementation of step S2105 in FIG2A.
[0290] In step S3203, terminal 101 determines at least one time domain interval associated with the first SSB.
[0291] In some embodiments, the implementation of step S3202 can refer to the implementation of step S2106 in FIG2A, or the implementation of step S2205 in FIG2B.
[0292] In step S3204, terminal 101 determines random access information corresponding to at least one first SSB within the time domain interval associated with at least one first SSB.
[0293] In some embodiments, the implementation of step S3204 can be found in the implementation of step S2107 in FIG2A or step S2206 in FIG2B.
[0294] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0295] Figure 3C is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3C, a communication method according to an embodiment of the present disclosure includes:
[0296] In step S3301, network device 102 sends configuration information to terminal 101.
[0297] In some embodiments, the implementation of step S3301 can be referred to the implementation of step S2103 in FIG2A.
[0298] In step S3302, network device 102 sends an SSB to terminal 101.
[0299] In some embodiments, the implementation of step S3302 can be referred to the implementation of step S2104 in FIG2A.
[0300] In step S3303, terminal 101 determines at least one first SSB for random access.
[0301] In some embodiments, the implementation of step S3303 can be referred to the implementation of step S2105 in FIG2A.
[0302] In step S3304, terminal 101 determines the time domain interval.
[0303] In some embodiments, the implementation of step S3304 can be referred to the implementation of step S2106 in FIG2A.
[0304] In step S3305, terminal 101 determines random access information corresponding to at least one first SSB within the time domain interval associated with at least one first SSB.
[0305] In some embodiments, the implementation of step S3305 can be referred to the implementation of step S2107 in FIG2A.
[0306] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0307] Figure 3D is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3D, a communication method according to an embodiment of the present disclosure includes:
[0308] In step S3401, network device 102 sends an SSB to terminal 101.
[0309] In some embodiments, the implementation of step S3301 can be referred to the implementation of step S2104 in FIG2A.
[0310] In step S3402, terminal 101 determines at least one first SSB for random access.
[0311] In some embodiments, the implementation of step S3302 can be referred to the implementation of step S2105 in FIG2A.
[0312] In step S3403, terminal 101 determines the time domain interval according to the configuration period and / or association period associated with at least one first SSB defined in the protocol.
[0313] In some embodiments, the implementation of step S3403 can be referred to the implementation of step S2205 in FIG2B.
[0314] In step S3404, terminal 101 determines random access information corresponding to at least one first SSB within the time domain interval associated with at least one first SSB.
[0315] In some embodiments, the implementation of step S3404 can be found in the implementation of step S2206 in FIG2B.
[0316] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0317] In the method provided in this disclosure, the terminal determines the random access information corresponding to the first SSB within a time domain interval associated with the first SSB used for random access. Determining the random access information within a suitable time domain interval can ensure the validity of the random access information, thereby improving the success rate of random access. To facilitate understanding of this disclosure, some embodiments are listed below:
[0318] Example 1: The UE determines the available RO resources based on the time-domain window.
[0319] Example 1-1: Define new RO time-domain resource configuration parameters, including the window length (x frame).
[0320] Optionally, the start time position of the window is determined by the relative time of the SSB burst where the SSB selected by the UE is located, such as the start time, end time, or time unit (frame) of the SSB burst where the selected SSB is located.
[0321] Optionally, the method by which the UE selects the SSB is not limited, such as whether it is selected randomly or based on the RSRP threshold.
[0322] Optionally, it is not limited whether RO resources are used for CBRA or CFRA.
[0323] In some embodiments, a time-domain window or window is equivalent to a time-domain interval or time window in the above embodiments, and the length of the window is equivalent to the duration of the time window in the above embodiments.
[0324] Example 1-2: Define new RO time-domain resource configuration parameters, including window length and window offset.
[0325] Optionally, RO resources are calculated starting from frame 0 + offset, with a duration equal to the window duration.
[0326] Optionally, the offset can be 0, in which case the window starts from frame0 and the duration is window duration.
[0327] Examples 1-3: Define new RO time-domain resource configuration parameters, including window length and window periodicity.
[0328] Optionally, this embodiment can implement multiple windows, with the starting time being a relative position (see Embodiment 1-1) and the duration being the window duration. Taking frame 0 as an example, the timing of occurrence is [frame 0, frame 0 + window duration], [frame 0 + window periodicity, frame 0 + window periodicity + window duration], [frame 0 + 2 * window periodicity, frame 0 + 2 * window periodicity + window duration]...
[0329] Examples 1-4: Define new RO time-domain resource configuration parameters, including window length, window offset, and window periodicity.
[0330] Optionally, this embodiment can implement multiple windowing, starting from frame 0 + offset (the start time is the absolute position, see embodiments 1-2), with a duration of window duration, and multiple windowings are added.
[0331] Example 2: Based on the parameters of the window and the configuration of RO resources in the existing protocol, only the RO resources within the window are available. The UE maps the available RO resources to the SSB beam according to the protocol rules.
[0332] Example 3: The SSB and RO mapping method of the updated UE is shown in Table 2-1. The maximum value of each association period is the Tdwell / PRACH configuration period, where Tdwell is a predefined time length or the time length configured by the base station.
[0333] Optionally, the mapping method shown in Embodiment 3 can be combined with the method shown in Embodiment 1 above.
[0334] Example 4: The implementation methods of Examples 1 to 3 above require that the terminal supports this capability and / or the network enables this feature before execution. Here, this capability and feature are equivalent to the first capability in the above examples.
[0335] Example 4-1: The network indicates whether the feature is enabled via parameters; if [network] enabled, ..., the base station broadcasts this.
[0336] Example 4-2: When the network indicates that the feature is enabled, or other relevant parameters, such as indicating an NTN scenario or beam hopping, the UE determines the valid RO according to the above method.
[0337] Example 4-3: When the network indicates that the feature is enabled, or other relevant parameters, such as indicating an NTN scenario or beam hopping, the UE with this capability determines the valid RO according to the above method.
[0338] 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.
[0339] 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 configuration files, 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.
[0340] 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).
[0341] Figure 4A is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. Terminal 4100 is used to execute any of the above methods. In some embodiments, as shown in Figure 4A, terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module 4101 is used to receive a synchronization signal block (SSB) sent by a network device; the processing module 4102 is used to determine at least one first SSB for random access; the processing module 4102 is further used to determine random access information corresponding to the at least one first SSB within a time domain interval associated with the at least one first SSB, wherein the random access information includes a random access timing (RO) and / or a random access preamble. Optionally, the transceiver module 4101 is used to execute at least one of the communication steps such as sending and / or receiving performed by terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module 4102 is used to execute at least one of the other steps performed by terminal 101 in any of the above methods, which will not be elaborated here.
[0342] Figure 4B is a schematic diagram of the structure of a network device proposed in an embodiment of this disclosure. The network device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to send an SSB to a terminal, wherein the SSB is used by the terminal to determine at least one first SSB for random access, and the time domain interval associated with the at least one first SSB is used to determine random access information corresponding to the at least one first SSB, wherein the random access information includes a random access timing (RO) and / or a random access preamble. Optionally, the transceiver module 4201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device 4200 in any of the above methods, which will not be elaborated here. Optionally, the processing module 4202 is used to perform at least one of the other steps performed by the network device 4200 in any of the above methods, which will not be elaborated here.
[0343] 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.
[0344] 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.
[0345] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.
[0346] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 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 5100 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.
[0347] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 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 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.
[0348] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0349] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.
[0350] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. 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 having 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.
[0351] Figure 5B is a schematic diagram of the structure of the chip 5200 proposed in an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, the schematic diagram of the chip 5200 shown in Figure 5B can be referred to, but is not limited thereto.
[0352] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.
[0353] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.
[0354] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.
[0355] 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.
[0356] 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.
[0357] 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.
[0358] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. Industrial applicability
[0359] The terminal can select a suitable first SSB from the SSBs sent by the network device for random access. Based on the time domain interval associated with the first SSB, the random access information corresponding to the first SSB can be determined within a certain time domain range, thereby ensuring the validity of the random access information, which in turn facilitates the network device to accurately receive the random access information and improves the success rate of random access.
Claims
1. A communication method, executed by a terminal, the method comprising: Receive synchronization signal block (SSB) sent by the network device; Identify at least one first SSB for random access; Within the time domain interval associated with the at least one first SSB, determine the random access information corresponding to the at least one first SSB, wherein the random access information includes random access timing (RO) and / or random access preamble.
2. The method as described in claim 1, wherein, The method further includes: The system receives configuration information sent by the network device, the configuration information including information about the time domain interval.
3. The method as described in claim 2, wherein, The information of the time domain interval includes at least one of the following: The duration of the time window corresponding to the time domain interval; The time domain interval corresponds to the period of the time window; The time domain interval corresponds to the starting offset of the time window.
4. The method of claim 3, wherein, The method further includes: The start time of the time domain interval is determined based on the time domain location of the at least one first SSB in the SSB burst.
5. The method of claim 4, wherein, The start time is one of the following: The starting time domain location of the SSB burst; The domain location at the end of the SSB burst; The time domain unit where the SSB burst is located.
6. The method of claim 3, wherein, The start time of the time domain interval is determined based on the start offset and the set frame.
7. The method as described in any one of claims 3 to 6, wherein, The starting offset is the default value or 0.
8. The method of claim 1, wherein, The method further includes: The time domain interval is determined according to the configuration period and / or association period associated with the at least one first SSB as defined in the protocol.
9. The method of claim 8, wherein, The maximum value of the configuration period is: the beam duration of the transmission beam corresponding to the at least one first SSB; And / or, The maximum value of the association period is determined based on the beam duration of the transmitted beam corresponding to the at least one first SSB and the configuration period.
10. The method of claim 9, wherein, The maximum value of the associated period is: floor(Tdwell / configuration period), where Tdwell represents the beam duration and floor represents the floor operation.
11. The method according to any one of claims 1 to 10, wherein, The method further includes: The network device sends capability information, which is used to indicate whether the terminal supports the ability to determine random access information within the time domain interval associated with at least one first SSB in a non-terrestrial network (NTN).
12. The method as claimed in any one of claims 1 to 11, wherein, The method further includes: The system receives indication information sent by the network device, the indication information being used to instruct the terminal to enable or activate the function of determining random access information within the time domain interval associated with at least one first SSB.
13. The method as claimed in any one of claims 1 to 12, wherein, The first period for transmitting the SSB includes multiple second periods, wherein the at least one first SSB is located within any of the second periods.
14. A communication method performed by a network device, the method comprising: Send an SSB to the terminal, wherein the SSB is used by the terminal to determine at least one first SSB for random access, and the time domain interval associated with the at least one first SSB is used to determine the random access information corresponding to the at least one first SSB, wherein the random access information includes a random access timing (RO) and / or a random access preamble.
15. The method of claim 14, wherein, The method further includes: The configuration information is sent to the terminal, and the configuration information includes information about the time domain interval.
16. The method of claim 15, wherein, The information of the time domain interval includes at least one of the following: The duration of the time window corresponding to the time domain interval; The time domain interval corresponds to the period of the time window; The time domain interval corresponds to the starting offset of the time window.
17. The method of claim 16, wherein, The start time of the time domain interval is determined based on the time domain location of the SSB burst where the at least one first SSB is located.
18. The method of claim 17, wherein, The start time is one of the following: The starting time domain location of the SSB burst; The domain location at the end of the SSB burst; The time domain unit where the SSB burst is located.
19. The method of claim 16, wherein, The start time of the time domain interval is determined based on the start offset and the set frame.
20. The method of any one of claims 16 to 19, wherein, The starting offset is the default value or 0.
21. The method of claim 14, wherein, The time domain interval is determined according to the configuration period and / or association period associated with the at least one first SSB as defined in the protocol.
22. The method of claim 21, wherein, The maximum value of the configuration period is: the beam duration of the transmission beam corresponding to the at least one first SSB; And / or, The maximum value of the association period is determined based on the beam duration of the transmission beam corresponding to the at least one first SSB and the configuration period.
23. The method of claim 22, wherein, The maximum value of the associated period is: floor(Tdwell / configuration period), where Tdwell represents the beam duration and floor represents the floor operation.
24. The method according to any one of claims 14 to 23, wherein, The method further includes: The terminal receives capability information sent by the terminal, the capability information being used to indicate whether the terminal supports the ability to determine random access information within the time domain interval associated with at least one first SSB in a non-terrestrial network (NTN).
25. The method as claimed in any one of claims 14 to 24, wherein, The method further includes: Send indication information to the terminal, the indication information being used to instruct the terminal to enable or activate the function of determining random access information within the time domain interval associated with at least one first SSB.
26. The method as claimed in any one of claims 14 to 25, wherein, The first period for transmitting the SSB includes multiple second periods, wherein the at least one first SSB is located within any of the second periods.
27. A communication device, wherein, The communication device is used to perform the method according to any one of claims 1 to 13 or any one of claims 14 to 26.
28. A communication system comprising a terminal and network equipment, wherein, The terminal is configured to implement the method as described in any one of claims 1 to 13; The network device is configured to implement the method as described in any one of claims 14 to 26.
29. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1 to 13 or any one of claims 14 to 26.
30. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by a communication device, it implements the method as described in any one of claims 1 to 13 or any one of claims 14 to 26.