Communication methods, terminal equipment, network equipment, media and products

Abstract

This disclosure provides a communication method applied to a terminal device, comprising: receiving at least two carrier bandwidths carried on an SIB1 from a network device, wherein the at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device; determining a target carrier bandwidth from the at least two carrier bandwidths that matches the carrier bandwidth supported by the terminal device; and using the SIB1 carrying the target carrier bandwidth for cell access. This disclosure also provides a terminal device, a network device, a computer-readable medium, and a computer program product.

Description

Technical Field

[0001] This disclosure relates to the field of mobile communication technology, and in particular to a communication method, terminal equipment, network equipment, computer-readable medium, and computer program product. Background Technology

[0002] With the development of mobile communication technology, network devices support increasingly higher bandwidths to meet the demands of high-speed data transmission. However, the hardware and software configurations of terminal devices (such as mobile phones and computers) at the time of manufacture determine the bandwidth they can support. In some scenarios, the bandwidth supported by the terminal device may differ from that supported by the network device, potentially leading to compatibility issues between the two. Summary of the Invention

[0003] This disclosure provides a communication method, a terminal device, a network device, a computer-readable medium, and a computer program product.

[0004] In a first aspect, embodiments of this disclosure provide a communication method applied to a terminal device, comprising: receiving at least two carrier bandwidths carried on an SIB1 from a network device, wherein the at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device; determining a target carrier bandwidth from the at least two carrier bandwidths that matches the carrier bandwidth supported by the terminal device; and using the SIB1 carrying the target carrier bandwidth for cell access.

[0005] Secondly, embodiments of this disclosure provide another communication method applied to a network device, comprising: determining at least two carrier bandwidths, wherein the at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device; sending at least two carrier bandwidths carried on SIB1 to the terminal device so that the terminal device uses SIB1 carrying a target carrier bandwidth for cell access, wherein the target carrier bandwidth is a carrier bandwidth among the at least two carrier bandwidths that matches the carrier bandwidth supported by the terminal device.

[0006] Thirdly, embodiments of this disclosure provide a terminal device, which includes a memory and a processor; the memory stores a computer program executable by the processor, and when the computer program is executed by the processor, it implements the first aspect and any possible embodiment of the first aspect.

[0007] Fourthly, embodiments of this disclosure provide a network device including a memory and a processor; the memory stores a computer program executable by the processor, and the computer program, when executed by the processor, implements the second aspect and any possible embodiments thereof.

[0008] Fifthly, embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the first aspect and any possible embodiments thereof, or the second aspect and any possible embodiments thereof.

[0009] In a sixth aspect, embodiments of this disclosure provide a computer program product, which includes a computer program that, when executed by a processor, implements the first aspect and any possible embodiments thereof, or the second aspect and any possible embodiments thereof.

[0010] In this embodiment, the network device provides at least two carrier bandwidths to the terminal device. These at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device. This ensures that the terminal device can determine a target carrier bandwidth that matches its supported carrier bandwidth from the carrier bandwidths configured by the network device, and thus use SIB1 carrying the target carrier bandwidth for cell access. This guarantees that the carrier bandwidth configured by the network device for the terminal device always includes a carrier bandwidth supported by the terminal device. Even if the bandwidths supported by the terminal device and the network device are inconsistent, the terminal device can still match a suitable carrier bandwidth for communication, thereby avoiding compatibility issues caused by inconsistencies in the bandwidths supported by the terminal device and the network device. Attached Figure Description

[0011] In the accompanying drawings of the embodiments disclosed herein:

[0012] Figure 1 A schematic diagram of the frequency ranges of N28A and N28B provided in this embodiment of the disclosure;

[0013] Figure 2 This is a schematic flowchart of a communication method provided in an embodiment of the present disclosure;

[0014] Figure 3 This is a schematic diagram of another communication method provided in an embodiment of the present disclosure;

[0015] Figure 4 This is a schematic diagram of an N28 band cell configuration provided in an embodiment of the present disclosure;

[0016] Figure 5 A flowchart of another communication method provided in this disclosure embodiment;

[0017] Figure 6 A flowchart of another communication method provided in this disclosure embodiment;

[0018] Figure 7 A flowchart of another communication method provided in this disclosure embodiment;

[0019] Figure 8 A flowchart of another communication method provided in this disclosure embodiment;

[0020] Figure 9 A flowchart of another communication method provided in this disclosure embodiment;

[0021] Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present disclosure;

[0022] Figure 11 This is a schematic diagram of the structure of a network device provided in an embodiment of this disclosure. Detailed Implementation

[0023] To enable those skilled in the art to better understand the technical solutions of this disclosure, the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0024] The present disclosure will be described more fully below with reference to the accompanying drawings; however, the embodiments shown may be embodied in different forms, and the present disclosure should not be construed as limited to the embodiments set forth below. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will enable those skilled in the art to fully understand the scope of the disclosure.

[0025] The accompanying drawings of the embodiments disclosed herein are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the detailed embodiments to explain this disclosure and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the description of the detailed embodiments with reference to the accompanying drawings.

[0026] Where there is no conflict, the various embodiments of this disclosure and the features thereof in the embodiments may be combined with each other.

[0027] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. The term "and / or" as used in this disclosure includes any and all combinations of one or more of the associated enumerated entries. The singular forms "a" and "the" as used in this disclosure are also intended to include the plural forms, unless the context clearly indicates otherwise. The terms "comprising," "made of," etc., as used in this disclosure specify the presence of the stated feature, integral, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0028] Unless otherwise specified, all terms used in this disclosure (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in this disclosure.

[0029] In some scenarios, the bandwidth supported by the terminal device differs from that supported by the network device, which may lead to compatibility issues between the two. For example, in fifth-generation mobile communication (5G)... th In 5G systems, the N28 band uses Frequency Division Duplex (FDD) technology, with an uplink (UL) frequency range of 703MHz to 748MHz and a downlink (DL) frequency range of 758MHz to 803MHz. For terminal devices supporting a 30MHz bandwidth on the N28 band, the 30MHz bandwidth cannot be arbitrarily selected. The protocol specifies two specific 30MHz frequency ranges: N28A and N28B. Specifically, N28A corresponds to an uplink frequency range of 703MHz to 733MHz and a downlink frequency range of 758MHz to 788MHz; N28B corresponds to an uplink frequency range of 718MHz to 748MHz and a downlink frequency range of 773MHz to 803MHz. (See attached diagram.) Figure 1 This diagram illustrates the N28A and N28B frequency ranges provided in this embodiment. For the N28 band, 3GPP protocol 38.101 specifies that with a 15kHz subcarrier spacing, the carrier bandwidth supported by the terminal device includes 5MHz, 10MHz, 15MHz, 20MHz, and 30MHz. 3GPP protocol 38.104 specifies that with a 15kHz subcarrier spacing, the carrier bandwidth supported by the network device includes 5MHz, 10MHz, 15MHz, 20MHz, 30MHz, and 40MHz. In this example, when the network device configures the downlink carrier bandwidth or uplink carrier bandwidth to 40MHz via the Master Information Block (SIB) 1, some terminal devices will perform strict verification according to the 3GPP protocol. Since the protocol specifies that the terminal device does not support a 40MHz carrier bandwidth with a 15kHz subcarrier spacing, this causes the terminal device to not initiate access, leading to compatibility issues between the terminal device and the network device.

[0030] In view of the above, embodiments of this disclosure provide a communication method, a terminal device, a network device, a computer-readable medium, and a computer program product, which will be described in detail below with reference to the accompanying drawings.

[0031] Firstly, refer to the appendix Figure 2 This is a schematic flowchart of a communication method provided in an embodiment of the present disclosure. The method is applied to a terminal device and includes:

[0032] S201: Receive at least two carrier bandwidths carried on SIB1 from a network device, wherein the at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device.

[0033] In the embodiments disclosed herein, the terminal device may also be referred to as a terminal, user equipment (UE), UE unit, UE device, mobile station, mobile station (MS), mobile terminal (MT), remote terminal, mobile device, etc., and refers to a device that provides voice and / or data connectivity to a user.

[0034] In this disclosure, network devices may also be referred to as base stations, radio access network (RAN) nodes (or devices), or access points, referring to devices that connect a UE to a wireless network. Examples include next-generation radio access network nodes (NG-RAN nodes), continuously evolving node Bs (gNBs), transmission reception points (TRPs), evolved node Bs (eNBs), radio network controllers (RNCs), and node Bs (NBs).

[0035] S202: Determine a target carrier bandwidth that matches the carrier bandwidth supported by the terminal device from at least two carrier bandwidths, and use SIB1 carrying the target carrier bandwidth for cell access.

[0036] In this embodiment of the disclosure, the target carrier bandwidth that matches the carrier bandwidth supported by the terminal device can be understood as the target carrier bandwidth that is the same as the carrier bandwidth supported by the terminal device.

[0037] In this embodiment of the disclosure, using SIB1 carrying the target carrier bandwidth for cell access can be understood as using the configuration information in SIB1 carrying the target carrier bandwidth for cell access.

[0038] In the embodiments of this disclosure, cell access can be interpreted differently for different application scenarios. For example, in the scenario of initial access of a terminal device, cell access refers to the first access to a cell or the initial access to a cell; in the scenario of re-establishing a connection of a terminal device, cell access refers to re-establishing the connection in a cell; in the scenario of a terminal device recovering from an inactive state to a connected state, cell access refers to restoring the connection state in a cell; and in the scenario of a terminal device performing cell handover, cell access refers to accessing a cell after the handover.

[0039] Using the above method, the network device can provide at least two carrier bandwidths to the terminal device via SIB1. These at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device. This ensures that the terminal device can determine a target carrier bandwidth that matches its supported carrier bandwidth from the carrier bandwidth configured by the network device, and thus use SIB1 carrying the target carrier bandwidth for cell access. This guarantees that the carrier bandwidth configured by the network device for the terminal device always includes a carrier bandwidth supported by the terminal device. Even if the bandwidths supported by the terminal device and the network device are inconsistent, the terminal device can still match a suitable carrier bandwidth for communication, thereby avoiding compatibility issues caused by inconsistencies in the bandwidths supported by the terminal device and the network device.

[0040] In some embodiments, at least two physical random access channel configuration indices (prach-ConfigurationIndex) carried on SIB1 are received from the network device, wherein the at least two physical random access channel configuration indices correspond one-to-one with at least two carrier bandwidths.

[0041] In some embodiments, there are multiple SIB1s, with each of at least two carrier bandwidths carrying a different SIB1, each of at least two physical random access channel configuration indices carrying a different SIB1, and each carrier bandwidth and its corresponding physical random access channel configuration index carrying the same SIB1. Different prach-ConfigurationIndexes indicate different random access times, and the prach-ConfigurationIndex is used to identify the SIB1 used by the UE when performing cell access. For example, a UE receives two SIB1s from the base station: a 40MHz SIB1 and a 30MHz SIB1. The 40MHz SIB1 carries a carrierBandwidth field of 40MHz and a physical random access channel configuration index (PRAMC) denoted as prach-ConfigurationIndex1. The 30MHz SIB1 carries a carrierBandwidth field of 30MHz and a PRAMC denoted as prach-ConfigurationIndex2. When the UE uses either the 40MHz or 30MHz SIB1 for cell access, the base station can identify the SIB1 used by the UE based on whether prach-ConfigurationIndex1 or prach-ConfigurationIndex2 is used. For instance, if the UE uses prach-ConfigurationIndex1, it can be determined that the UE is using the 40MHz SIB1; if the UE uses prach-ConfigurationIndex2, it can be determined that the UE is using the 30MHz SIB1. SIB1, that is, can identify whether the UE accesses the network through the configuration information in the 40MHz SIB1 or the configuration information in the 30MHz SIB1.

[0042] In some embodiments, different SIB1s are associated with different beams. Exemplarily, these different beams may all be wide beams and have the same coverage.

[0043] In some embodiments, the number of SIB1s is one, and at least two carrier bandwidths and at least two physical random access channel configuration indices are carried on the same SIB1.

[0044] In some embodiments, at least two Non-Cell Defined Synchronization Block (NCD-SSB) measurement information are received from a network device, each NCD-SSB measurement information being transmitted through an available frequency band of the target frequency band. Measurements are performed based on the at least two NCD-SSB measurement information to obtain measurement results, which are then sent to the network device to determine the target available frequency band supported by the terminal device within the available frequency band. Based on the target available frequency band, a target BWP is determined among multiple bandwidth portions (BWPs) associated with the target frequency band, and the target BWP is received from the network device. This allows existing incompatible terminal devices to be served in the N28 frequency band, improving the spectrum utilization of the N28 frequency band.

[0045] For example, the target frequency band can be any frequency band that supports the issuance of NCD-SSB, such as the N28 frequency band. When the target frequency band is the N28 frequency band, the available frequency bands of the corresponding target frequency band may include the N28A and N28B frequency bands.

[0046] Secondly, refer to the appendix. Figure 3 This is a schematic flowchart of another communication method provided in this disclosure embodiment. The method is applied to a network device and includes:

[0047] S301: Determine at least two carrier bandwidths, wherein the at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device.

[0048] S302: Send at least two carrier bandwidths carried on SIB1 to the terminal device so that the terminal device can use SIB1 carrying the target carrier bandwidth for cell access, wherein the target carrier bandwidth is the carrier bandwidth among the at least two carrier bandwidths that matches the carrier bandwidth supported by the terminal device.

[0049] Using the above method, the network device can provide at least two carrier bandwidths to the terminal device via SIB1. These at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device. This ensures that the terminal device can determine a target carrier bandwidth that matches its supported carrier bandwidth from the carrier bandwidth configured by the network device, and thus use SIB1 carrying the target carrier bandwidth for cell access. This guarantees that the carrier bandwidth configured by the network device for the terminal device always includes a carrier bandwidth supported by the terminal device. Even if the bandwidths supported by the terminal device and the network device are inconsistent, the terminal device can still match a suitable carrier bandwidth for communication, thereby avoiding compatibility issues caused by inconsistencies in the bandwidths supported by the terminal device and the network device.

[0050] It should be noted that the same concepts or steps involved in the second aspect as those in the first aspect can be found in the description of the first aspect, and will not be repeated in the second aspect.

[0051] In some embodiments, at least two physical random access channel configuration indices carried on SIB1 are sent to the terminal device, wherein the at least two physical random access channel configuration indices correspond one-to-one with at least two carrier bandwidths.

[0052] In some embodiments, there are multiple SIB1s, each of at least two carrier bandwidths is carried by a different SIB1, each of at least two physical random access channel configuration indices is carried by a different SIB1, and each carrier bandwidth and its corresponding physical random access channel configuration index are carried by the same SIB1.

[0053] In some embodiments, at least two NCD-SSB measurement information messages are sent to the terminal device, each NCD-SSB measurement information message being transmitted through an available frequency band of the target frequency band; measurement results obtained by performing measurements based on the at least two NCD-SSB measurement information messages are received from the terminal device, and a target available frequency band supported by the terminal device is determined in the available frequency band based on the measurement results; a target BWP is determined in multiple bandwidth parts (BWPs) associated with the target frequency band based on the target available frequency band supported by the terminal device, and the target BWP is sent to the terminal device.

[0054] In some embodiments, before determining the target BWP among multiple BWPs associated with the target frequency band, the method further includes: determining the SIB1 of the bearer target carrier bandwidth used by the terminal device for cell access based on the physical random access channel configuration index used by the terminal device; determining the target BWP among multiple BWPs associated with the target frequency band includes: determining the target BWP among multiple BWPs associated with the target frequency band based on the target available frequency band supported by the terminal device and the SIB1 of the bearer target carrier bandwidth used by the terminal device for cell access.

[0055] In some embodiments, determining a target BWP among a plurality of BWPs associated with a target frequency band includes: determining the target BWP among a plurality of BWPs associated with a target frequency band based on the channel bandwidth supported by the terminal device, the target available frequency band supported by the terminal device, and the SIB1 of the bearer target carrier bandwidth used by the terminal device for cell access.

[0056] To enable those skilled in the art to more clearly understand the technical solutions provided by the embodiments of this disclosure, the technical solutions provided by the embodiments of this disclosure are further described below through specific embodiments. In the following embodiments, the N28 frequency band in a 5G system is used as an example for illustration. Before describing the embodiments in detail, the cell configuration of the N28 frequency band is first described, referring to the appendix. Figure 4 This is a schematic diagram of an N28 band cell configuration provided in an embodiment of this disclosure. Figure 4 It can be seen that the cell configuration for the N28 frequency band is as follows:

[0057] 1) Customer-held frequency range: 40MHz (UL: 703MHz~743MHz; DL: 758MHz~798MHz);

[0058] 2) The cell transmits two NCD-SSBs, NCD-SSB1 and NCD-SSB2, in the frequency ranges unique to N28A and N28B, and transmits a Cell Defining SSB (CD-SSB) in the overlapping range of N28A and N28B. All BWPs contain CD-SSBs.

[0059] 3) BWP0 is the initial BWP with a frequency range of 10MHz (UL: 723MHz~733MHz; DL: 778MHz~788MHz), which is the BWP within the overlapping range of N28A and N28B;

[0060] 4) BWP1 is a dedicated BWP with a 10MHz bandwidth for the cell, and its frequency range is the same as the initial BWP;

[0061] 5) BWP2 is a dedicated BWP for the 30MHz bandwidth of the cell, with a frequency range of 30MHz (UL: 703MHz~733MHz; DL: 758MHz~788MHz), which is the same as the frequency range of N28A;

[0062] 6) BWP3 is a dedicated BWP for the 20MHz bandwidth of the cell, with a frequency range of 20MHz (UL: 723MHz~743MHz; DL: 778MHz~798MHz). It is a 20MHz bandwidth BWP within the frequency range of N28B.

[0063] 7) BWP4 is a dedicated BWP for 20MHz bandwidth in the cell, with a frequency range of 20MHz (UL: 713MHz~733MHz; DL: 768MHz~788MHz). It is a BWP with a 20MHz bandwidth within the N28 frequency range.

[0064] Example 1:

[0065] See attached document Figure 5 and attached Figure 6 This is a flowchart of another communication method provided by an embodiment of the present disclosure. In this embodiment, the terminal device is a UE, which includes UE1 (which does not support 40MHz carrier bandwidth), UE2 (which supports 40MHz carrier bandwidth), UE3 (which does not support 40MHz carrier bandwidth), and UE4 (which supports 40MHz carrier bandwidth). The network device is a gNB. There are two carrier bandwidths carried on SIB1, namely 40MHz and 30MHz. The 30MHz carrier bandwidth is supported by both the gNB and the UE, and the 40MHz carrier bandwidth is supported by the gNB but not by some UEs. There are two SIB1s, and the two carrier bandwidths are carried on different SIB1s. Two physical random access channel configuration indices corresponding one-to-one with the two carrier bandwidths are carried on different SIB1s. The SIB1 carrying the 40MHz carrier bandwidth is denoted as 40MHz SIB1, and the SIB1 carrying the 30MHz carrier bandwidth is denoted as 30MHz SIB1. The 40MHz carrier bandwidth and its corresponding physical random access channel configuration index are carried on 40MHz SIB1, and the 30MHz carrier bandwidth and its corresponding physical random access channel configuration index are carried on 30MHz SIB1. SIB1, 40MHz SIB1 associated beam 1 (Beam1), 30MHz SIB1 associated beam 2 (Beam2), beam 1 and beam 2 are different beams. In this embodiment, the target frequency band is the N28 band, and the available frequency bands of the target frequency band include the N28A and N28B bands. This embodiment is described in two processes; the first process can be found in the appendix. Figure 5 This is the process that triggers the UE to initiate cell access; the second process can be found in the appendix. Figure 6 This refers to the process by which the UE accesses the cell and the gNB selects the BWP. The two processes are described below.

[0066] See appendix Figure 5 This is the process that triggers the UE to initiate cell access. Figure 5 The process shown includes the following steps:

[0067] S501a: gNB broadcasts SSB1 on beam 1.

[0068] S501b: gNB broadcasts 40MHz SIB1 on beam 1.

[0069] S501a1: UE1 performs the first blind test.

[0070] In this embodiment, the first blind detection performed by UE1 includes: UE1 blindly detects SSB1, obtains the Master Information Block (MIB) from SSB1 and parses the MIB to obtain the location of receiving 40MHz SIB1.

[0071] S501b1: UE1 receives 40MHz SIB1, parses the carrier bandwidth field in 40MHz SIB1 to be 40MHz, performs verification, if verification fails, does not initiate cell access.

[0072] S501a2: UE2 performs the first blind test.

[0073] In this embodiment, the first blind detection performed by UE2 includes: UE2 blindly detecting SSB1, obtaining and parsing the MIB from SSB1, and obtaining the location of receiving 40MHz SIB1.

[0074] S501b2: UE2 receives 40MHz SIB1, parses the carrierBandwidth field in 40MHz SIB1 to be 40MHz, performs verification, and if the verification passes, initiates cell access using 40MHz SIB1.

[0075] S502a: gNB broadcasts SSB2 on beam 2.

[0076] S502b: gNB broadcasts 30MHz SIB1 on beam 2.

[0077] S502a1: UE1 performs a second blind check.

[0078] In this embodiment, the second blind detection performed by UE1 includes: UE1 blindly detects SSB2, obtains and parses the MIB from SSB2, and obtains the location of receiving 30MHz SIB1.

[0079] S502b1: UE1 receives 30MHz SIB1, parses the carrierBandwidth field in 30MHz SIB1 to be 30MHz, performs verification, and if the verification passes, initiates cell access using 30MHz SIB1.

[0080] S502a2: UE3 performs the first blind test.

[0081] In this embodiment, the first blind detection performed by UE3 includes: UE3 blindly detects SSB2, obtains and parses the MIB from SSB2, and obtains the position of receiving 30MHz SIB1.

[0082] S502b2: UE3 receives 30MHz SIB1, parses the carrierBandwidth field in 30MHz SIB1 to be 30MHz, performs verification, and if the verification passes, initiates cell access using 30MHz SIB1.

[0083] S502a3: UE4 performs the first blind test.

[0084] In this embodiment, the first blind detection performed by UE4 includes: UE4 blindly detecting SSB2, obtaining and parsing the MIB from SSB2, and obtaining the location of receiving 30MHz SIB1.

[0085] S502b3: UE4 receives 30MHz SIB1, parses the carrierBandwidth field in 30MHz SIB1 to be 30MHz, performs verification, and if the verification passes, initiates cell access using 30MHz SIB1.

[0086] See appendix Figure 6 This is the process by which the UE selects a BWP for access to the cell and gNB. Figure 6 The process shown includes the following steps:

[0087] S601: gNB broadcasts NCD-SSB1 within the N28A frequency band.

[0088] S602: gNB broadcasts NCD-SSB2 within the N28B frequency band.

[0089] S603: gNB broadcasts CD-SSB within the overlapping area of ​​N28A and N28B frequency bands.

[0090] For example, the gNB can periodically broadcast NCD-SSB1, NCD-SSB2 and CD-SSB.

[0091] S604: gNB broadcasts 40MHz SIB1 and 30MHz SIB1 on two beams respectively.

[0092] For details regarding S604, please refer to [link / reference]. Figure 5 The description of the first process.

[0093] S605a: The UE sends MSG1 to the gNB.

[0094] S605b: gNB determines the SIB1 used by the UE for cell access based on the physical random access channel configuration index used by the UE.

[0095] In this embodiment, since the physical random access channel configuration index corresponds one-to-one with the carrier bandwidth, and different physical random access channel configuration indices and carrier bandwidths are carried through different SIB1s, the gNB can determine the SIB1 used by the UE for cell access based on the physical random access channel configuration index used by the UE.

[0096] In this embodiment, a UE that supports a 40MHz carrier bandwidth can initiate cell access using either a 30MHz SIB1 or a 40MHz SIB1; a UE that does not support a 40MHz carrier bandwidth can only initiate cell access using a 30MHz SIB1.

[0097] S606: gNB sends MSG2 to UE.

[0098] S607: The UE sends an RRC connection establishment request message (RRCSetupRequest) to the gNB.

[0099] S608: gNB sends an RRC connection establishment response message (RRCSetup) to UE.

[0100] S609: The UE sends an RRC connection establishment complete message (RRCSetupComplete) to the gNB.

[0101] S610: gNB sends an initial UE message to AMF.

[0102] S611: The AMF sends an Initial Context Establishment Request message (INITIALCONTEXT SETUPREQUEST) to the gNB.

[0103] S612: gNB sends an RRC reconfiguration message (RRCReconfiguration) to the UE, carrying BWP1 in the RRCReconfiguration message.

[0104] In this embodiment, the gNB determines that the cell frequency band accessed by the UE is the N28 frequency band. Since the gNB cannot know which available frequency bands of the N28 frequency band the UE supports (i.e., it cannot determine whether the UE supports N28A, N28B, or both), in order to ensure that the UE can access the network normally, it can only configure a dedicated BWP1 for the overlapping area of ​​N28A and N28B for the UE.

[0105] S613: The UE sends an RRC reconfiguration complete message (RRCReconfigurationComplete) to the gNB.

[0106] S614: gNB sends an Initial Context Establishment Response Message (INITIALCONTEXT SETUPRESPONSE) to AMF.

[0107] S615: gNB sends RRCReconfiguration to UE, carrying NCD-SSB1 and NCD-SSB2 measurement information in RRCReconfiguration.

[0108] In this embodiment, the gNB transmits NCD-SSB1 and NCD-SSB2 measurement information within the frequency range unique to N28A and N28B.

[0109] S616: The UE sends RRCReconfigurationComplete to the gNB.

[0110] S617a: The UE sends a Measurement Report to the gNB, which carries the measurement results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information. For example, the measurement results may be the results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information within a preset time period.

[0111] S617b: The gNB determines the target available frequency bands supported by the UE in the available frequency bands of the N28 band based on the measurement results.

[0112] S617c: The gNB determines the target BWP from among multiple BWPs associated with the target frequency band based on the channel bandwidth supported by the UE, the target available frequency band supported by the UE, and the SIB1 used by the UE for cell access.

[0113] In this embodiment, after the gNB identifies the target BWP, it can also delete the NCD-SSB1 and NCD-SSB2 measurement information to stop the NCD-SSB1 and NCD-SSB2 measurements.

[0114] In this embodiment, S617c can be implemented in the following way:

[0115] S1: If the gNB determines that the UE uses 40MHz SIB1 to initiate cell access, then continue to execute S11. If the gNB determines that the UE uses 30MHz SIB1 to initiate cell access, then continue to execute S21.

[0116] S11: If the gNB determines that the UE only supports the N28A band, then continue to execute S111; if the gNB determines that the UE only supports the N28B band, then continue to execute S112; if the gNB determines that the UE supports both the N28A and N28B bands, then continue to execute S113.

[0117] S111: If the gNB determines that the UE supports a 30MHz carrier bandwidth, the gNB switches to BWP2 via a reconfiguration message; if the gNB determines that the UE supports a 20MHz carrier bandwidth, the gNB switches to BWP4 via a reconfiguration message; otherwise, it remains in BWP1.

[0118] S112: If the gNB determines that the UE supports a 20MHz carrier bandwidth, the gNB switches to BWP3 via a reconfiguration message; otherwise, it remains in BWP1.

[0119] S113: If the gNB determines that the UE supports a 30MHz carrier bandwidth, the gNB switches to BWP2 via a reconfiguration message; if the gNB determines that the UE supports a 20MHz carrier bandwidth, the gNB can determine the target BWP based on the load of BWP3 and BWP4, and switch to BWP3 or BWP4 via a reconfiguration message; otherwise, it remains in BWP1.

[0120] S21: If the gNB determines that the UE only supports the N28A band or supports both the N28A and N28B bands, then continue to execute S211; if the gNB determines that the UE only supports the N28B band, then continue to execute S212.

[0121] S211: If the gNB determines that the UE supports a 30MHz carrier bandwidth, the gNB switches to BWP2 via a reconfiguration message; if the gNB determines that the UE supports a 20MHz carrier bandwidth, the gNB switches to BWP4 via a reconfiguration message; otherwise, it remains in BWP1.

[0122] S212: If the gNB determines that the UE supports a 20MHz carrier bandwidth, the gNB switches to BWP3 via a reconfiguration message; otherwise, it remains in BWP1.

[0123] S618: gNB sends RRCReconfiguration to UE, carrying the target BWP in RRCReconfiguration.

[0124] S619: The UE sends RRCReconfigurationComplete to the gNB.

[0125] Example 2:

[0126] In this embodiment, the first process in Embodiment 1 can be modified as follows: Two carrier bandwidths are added to SIB1, one with a bandwidth of 30MHz and the other with a bandwidth of 40MHz. A new Physical Random Access Channel Configuration Index (PRANCI) is also added to SIB1. At this point, SIB1 carries two carrier bandwidths and two PRANCIs, with a one-to-one correspondence between the carrier bandwidths and the PRANCIs. When the UE initiates cell access using the 30MHz carrier bandwidth, the corresponding PRANCI is used; otherwise, when the UE initiates cell access using the 40MHz carrier bandwidth, the corresponding PRANCI is used. The remaining processes in this embodiment are the same as the second process in Embodiment 1, and will not be repeated here.

[0127] Example 3:

[0128] See attached document Figure 7 This is a flowchart of another communication method provided by this disclosure. In this embodiment, the relevant configuration is the same as in Embodiment 1, and will not be repeated here. The difference between this embodiment and Embodiment 1 is that this embodiment is applied to the scenario where the UE resumes from the inactive state to the connected state. This embodiment describes in detail the process of the UE accessing the cell and gNB selecting the BWP in the scenario where the UE resumes from the inactive state to the connected state. Figure 7 The process shown includes the following steps:

[0129] In this embodiment, S701 to S706 are the same as S601 to S606. Please refer to the relevant descriptions of S601 to S606, which will not be repeated here.

[0130] S707: A UE in the RRC inactive state (RRC_INACTIVE) sends an RRC recovery request message (RRCResumeRequest) to the currently serving gNB.

[0131] In this embodiment, for ease of description, the gNB currently being served will be referred to as gNB.

[0132] S708: The gNB sends a RETRIEVE UE CONTEXT REQUEST message to the last servicing gNB of the UE.

[0133] S709: Last Serving gNB sends a RETRIEVE UECONTEXT RESPONSE message to gNB.

[0134] S708 and S709 are optional execution steps, the purpose of which is to pass the UE's context from the last gNB served by the UE to the current gNB.

[0135] S710: gNB sends an RRC recovery message (RRCResume) to the UE, carrying BWP1 in the RRCesume.

[0136] In this embodiment, the gNB determines that the cell frequency band accessed by the UE is the N28 frequency band. Since the gNB cannot know which available frequency bands of the N28 frequency band the UE supports (i.e., it cannot determine whether the UE supports N28A, N28B, or both), in order to ensure that the UE can access the network normally, it can only configure a dedicated BWP1 for the overlapping area of ​​N28A and N28B for the UE.

[0137] S711: The UE sends an RRC recovery complete message (RRCResumeComplete) to the gNB.

[0138] S712: gNB sends RRCReconfiguration to UE, carrying NCD-SSB1 and NCD-SSB2 measurement information in RRCReconfiguration.

[0139] In this embodiment, the gNB transmits NCD-SSB1 and NCD-SSB2 measurement information within the frequency range unique to N28A and N28B.

[0140] S713: The UE sends RRCReconfigurationComplete to the gNB.

[0141] S714a: The UE sends a MeasurementReport to the gNB, which carries the measurement results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information. For example, the measurement results may be the results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information within a preset time period.

[0142] S714b: The gNB determines the target available frequency bands supported by the UE in the available frequency bands of the N28 band based on the measurement results.

[0143] S714c: The gNB determines the target BWP from among multiple BWPs associated with the target frequency band based on the channel bandwidth supported by the UE, the target available frequency band supported by the UE, and the SIB1 used by the UE for cell access.

[0144] In this embodiment, the specific implementation of S714c can be found in S617c of Embodiment 1, and will not be repeated here.

[0145] In this embodiment, after the gNB identifies the target BWP, it can also delete the NCD-SSB1 and NCD-SSB2 measurement information to stop the NCD-SSB1 and NCD-SSB2 measurements.

[0146] S715: gNB sends RRCReconfiguration to UE, which carries the target BWP and indication information for deleting NCD-SSB1 and NCD-SSB2 measurement information.

[0147] S716: The UE sends RRCReconfigurationComplete to the gNB.

[0148] Example 4:

[0149] See attached document Figure 8 This is a flowchart of another communication method provided by this disclosure. In this embodiment, the relevant configuration is the same as in Embodiment 1, and will not be repeated here. The difference between this embodiment and Embodiment 1 is that this embodiment is applied to the scenario of UE re-establishing connection. This embodiment describes in detail the process of UE accessing the cell (i.e., UE re-establishing in the cell or UE re-establishing into the cell) and gNB selecting BWP in the scenario of UE re-establishing connection. Figure 8 The process shown includes the following steps:

[0150] In this embodiment, S801 to S806 are the same as S601 to S606. Please refer to the relevant descriptions of S601 to S606, which will not be repeated here.

[0151] S807: The UE sends an RRC Reestablishment Request message to the currently serving gNB.

[0152] In this embodiment, for ease of description, the gNB currently served by the UE will be referred to as gNB.

[0153] S808: The gNB sends a RETRIEVE UECONTEXT REQUEST message to the Last Serving gNB.

[0154] S809: Last Serving gNB sends a RETRIEVE UECONTEXT RESPONSE message to gNB.

[0155] S808 and S809 are optional execution steps, the purpose of which is to pass the UE's context from the last gNB served by the UE to the current gNB.

[0156] S810: gNB sends an RRC Reestablishment message to UE.

[0157] S811: The UE sends an RRC Reestablishment Complete message to the gNB.

[0158] S812: gNB sends RRCReconfiguration to UE, carrying BWP1 in RRCReconfiguration.

[0159] In this embodiment, the gNB determines that the cell frequency band accessed by the UE is the N28 frequency band. Since the gNB cannot know which available frequency bands of the N28 frequency band the UE supports (i.e., it cannot determine whether the UE supports N28A, N28B, or both), in order to ensure that the UE can access the network normally, it can only configure a dedicated BWP1 for the overlapping area of ​​N28A and N28B for the UE.

[0160] S813: The UE sends RRCReconfigurationComplete to the gNB.

[0161] S814: The gNB sends a PATH SWITCH REQUEST message to the Last Serving gNB.

[0162] S815: Last Serving gNB sends a PATH SWITCHREQUEST ACKNOWLEDGE message to gNB.

[0163] S814 and S815 are optional execution steps.

[0164] S816: gNB sends RRCReconfiguration to UE, carrying NCD-SSB1 and NCD-SSB2 measurement information in RRCReconfiguration.

[0165] In this embodiment, the gNB transmits NCD-SSB1 and NCD-SSB2 measurement information within the frequency range unique to N28A and N28B.

[0166] S817: The UE sends RRCReconfigurationComplete to the gNB.

[0167] S818a: The UE sends a MeasurementReport to the gNB, which carries the measurement results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information. For example, the measurement results may be the results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information within a preset time period.

[0168] S818b: gNB determines the target available frequency bands supported by the UE in the available frequency bands of the N28 band based on the measurement results.

[0169] S818c: The gNB determines the target BWP from among multiple BWPs associated with the target frequency band based on the channel bandwidth supported by the UE, the target available frequency band supported by the UE, and the SIB1 used by the UE for cell access.

[0170] In this embodiment, the specific implementation of S818c can be found in S618c of Embodiment 1, and will not be repeated here.

[0171] In this embodiment, after the gNB identifies the target BWP, it can also delete the NCD-SSB1 and NCD-SSB2 measurement information to stop the NCD-SSB1 and NCD-SSB2 measurements.

[0172] S819: gNB sends RRCReconfiguration to UE, which carries the target BWP and indication information for deleting NCD-SSB1 and NCD-SSB2 measurement information.

[0173] S820: The UE sends RRCReconfigurationComplete to the gNB.

[0174] Example 5:

[0175] See attached document Figure 9 This is a flowchart of another communication method provided by this disclosure. In this embodiment, the relevant configuration is the same as in Embodiment 1, and will not be repeated here. The difference between this embodiment and Embodiment 1 is that this embodiment is applied to a scenario where the UE performs cell handover. This embodiment describes in detail the process of the UE handing over to the target cell and the gNB selecting the BWP in the cell handover scenario. Figure 9 The process shown includes the following steps:

[0176] S900: The target gNB stores the IMEISV of UEs that do not support 40MHz carrier bandwidth.

[0177] In this embodiment, the Target gNB can obtain the IMEISV of a UE that does not support a 40MHz carrier bandwidth from the network management configuration.

[0178] S901a: The UE sends a MeasurementReport to the source gNB.

[0179] S901b: The Source gNB determines the cell handover to be performed based on the MeasurementReport.

[0180] S902a: The Source gNB sends a Handover Request message to the Target gNB, which carries the UE's IMEISV.

[0181] S902b: Target gNB selects carrier bandwidth and BWP based on IMEISV.

[0182] In this embodiment, S902b may specifically include, after receiving the Handover Request, if the Target gNB determines that the Target gNB is a cell supporting the N28 frequency band, then it may output the downlink bandwidth (RRCReconfiguration->masterCellGroup->spCellConfig->reconfigurationWithSync->spCell ConfigCommon->downlinkConfigCommon->frequencyInfoDL->scs-SpecificCarrierList->carrierBandwidth) and uplink bandwidth (RRCReconfiguration->masterCellGroup->spCellConfig->reconfigurationWithSync->spCell ConfigCommon->uplinkConfigCommon->frequencyInfoUL->scs-SpecificCarrierList->carrierBandwidth) and BWP1 of the synchronization cell according to the IMEISV carried in the Handover Request.

[0183] For example, it can be determined whether the UE initiating cell handover supports a 40MHz carrier bandwidth by comparing the IMEISV carried in the Handover Request with the IMEISV stored in S900. If the IMEISV carried in the Handover Request matches the IMEISV stored in S900, it is considered that the UE initiating cell handover does not support a 40MHz carrier bandwidth, and the uplink and downlink bandwidth in the synchronization cell are configured to be 30MHz, with the number of RBs corresponding to a subcarrier spacing of 15KHz being 160; otherwise, the uplink and downlink bandwidth in the synchronization cell are configured to be 40MHz, with the number of RBs corresponding to 15KHz being 216.

[0184] In this embodiment, since the gNB cannot know which available frequency bands of the N28 band are supported by the UE (i.e., it cannot determine whether the UE supports N28A, N28B, or both), in order to ensure that the UE can access the network normally, it can only configure a dedicated BWP1 for the overlapping area of ​​N28A and N28B for the UE.

[0185] S903: The Target gNB sends a handover request confirmation message (HANDOVER REQUESTACKNOWLEDGE) to the Source gNB.

[0186] S904: The Source gNB sends RRCReconfiguration to the UE, carrying BWP1 in the RRCReconfiguration.

[0187] S905: The UE sends RRCReconfigurationComplete to the Target gNB.

[0188] In this embodiment, by executing S903 to S905, the uplink bandwidth and downlink bandwidth in the BWP1 and synchronization cell selected by the Target gNB can be sent to the UE via an RRC reconfiguration message.

[0189] S906: The Target gNB sends a PATH SWITCH REQUEST message to the AMF.

[0190] S907: The AMF sends a PATH SWITCH REQUESTACKNOWLEDGE message to the Target gNB.

[0191] S908: The Target gNB sends a UE context release message (UE CONTEXT RELEASE) to the Source gNB.

[0192] S909: The Target gNB sends RRCReconfiguration to the UE, carrying NCD-SSB1 and NCD-SSB2 measurement information in the RRCReconfiguration.

[0193] In this embodiment, the Target gNB transmits NCD-SSB1 and NCD-SSB2 measurement information within the frequency range unique to N28A and N28B.

[0194] S910: The UE sends RRCReconfigurationComplete to the Target gNB.

[0195] S911a: The UE sends a MeasurementReport to the Target gNB, which carries the measurement results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information. For example, the measurement results may be the results obtained by the UE performing measurements based on the NCD-SSB1 and NCD-SSB2 measurement information within a preset time period.

[0196] S911b: The Target gNB determines the target available frequency bands supported by the UE in the available frequency bands of the N28 band based on the measurement results.

[0197] S911c: The Target gNB determines the target BWP from among multiple BWPs associated with the target frequency band based on the channel bandwidth supported by the UE, the target available frequency band supported by the UE, and the uplink and downlink bandwidth configured for the UE.

[0198] In this embodiment, using 30MHz uplink and downlink bandwidth is equivalent to using 30MHz SIB1 in the access procedure, and using 40MHz uplink and downlink bandwidth is equivalent to using 40MHz SIB1 in the access procedure.

[0199] In this embodiment, the specific implementation of S911c can be found in S618c of Embodiment 1, and will not be repeated here.

[0200] In this embodiment, after S911c determines the target BWP, it can also delete the NCD-SSB1 and NCD-SSB2 measurement information to stop the NCD-SSB1 and NCD-SSB2 measurements.

[0201] S912: The Target gNB sends an RRCReconfiguration to the UE, which carries the target BWP and an indication to delete the NCD-SSB1 and NCD-SSB2 measurement information.

[0202] S913: The UE sends RRCReconfigurationComplete to the Target gNB.

[0203] Thirdly, refer to the appendix. Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present disclosure, comprising: at least one processor 1001, at least one memory 1002, and one or more I / O interfaces 1003. The one or more I / O interfaces 1003 are connected between the processor 1001 and the memory 1002. The memory 1002 stores one or more computer programs, which are executed by the at least one processor 1001 to enable the at least one processor 1001 to implement the first aspect described above and any possible embodiment thereof.

[0204] Among them, the processor is a device with data processing capabilities, including but not limited to the central processing unit (CPU); the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read-write interface) is connected between the processor and the memory, enabling information exchange between the memory and the processor, including but not limited to the data bus (Bus).

[0205] Fourthly, refer to the appendix. Figure 11 This is a schematic diagram of the structure of a network device provided in an embodiment of the present disclosure, comprising: at least one processor 1101, at least one memory 1102, and one or more I / O interfaces 1103. The one or more I / O interfaces 1103 are connected between the processor 1101 and the memory 1102. The memory 1102 stores one or more computer programs, which are executed by the at least one processor 1101 to enable the at least one processor 1101 to implement the first aspect described above and any possible embodiment thereof.

[0206] Among them, the processor is a device with data processing capabilities, including but not limited to the central processing unit (CPU); the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read-write interface) is connected between the processor and the memory, enabling information exchange between the memory and the processor, including but not limited to the data bus (Bus).

[0207] Fifthly, embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the first aspect and any possible embodiments thereof, or implements the second aspect and any possible embodiments thereof.

[0208] In a sixth aspect, embodiments of this disclosure provide a computer program product, which includes a computer program that, when executed by a processor, implements the first aspect and any possible embodiments thereof, or implements the second aspect and any possible embodiments thereof.

[0209] Those skilled in the art will understand that all or some of the steps, systems, and devices disclosed above, as functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0210] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be executed by several physical components working together.

[0211] Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit (CPU), digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technique for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH) or other disk storage; read-only optical disc (CD-ROM), digital versatile disc (DVD) or other optical disc storage; magnetic cartridges, magnetic tapes, disk storage or other magnetic storage; and any other media that can be used to store desired information and can be accessed by a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0212] This disclosure has disclosed exemplary embodiments, and although specific terminology has been used, it is for general illustrative purposes only and should not be construed as limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this disclosure as set forth by the appended claims.

Claims

1. A communication method applied to a terminal device, comprising: Receive at least two carrier bandwidths carried in system information block SIB1 from the network device, wherein the at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device; A target carrier bandwidth matching the carrier bandwidth supported by the terminal device is determined from the at least two carrier bandwidths, and cell access is performed using SIB1 carrying the target carrier bandwidth.

2. The method according to claim 1, wherein, The method further includes: The network device receives at least two physical random access channel configuration indices carried on the SIB1, wherein the at least two physical random access channel configuration indices correspond one-to-one with the at least two carrier bandwidths.

3. The method according to claim 2, wherein, The number of SIB1s is multiple, each of the at least two carrier bandwidths is carried by a different SIB1, each of the at least two physical random access channel configuration indices is carried by a different SIB1, and each carrier bandwidth and its corresponding physical random access channel configuration index are carried by the same SIB1.

4. The method according to claim 3, wherein, Different SIB1s are associated with different beams.

5. The method according to claim 2, wherein, The number of SIB1s is one, and the at least two carrier bandwidths and the at least two physical random access channel configuration indices are all carried on the same SIB1.

6. The method according to claim 1, wherein, The method further includes: The network device receives at least two non-cell defined synchronization signal block (NCD-SSB) measurement information, each of the NCD-SSB measurement information being transmitted through an available frequency band of the target frequency band. The measurement results are obtained by performing a measurement based on the at least two NCD-SSB measurement information, and the measurement results are sent to the network device to determine the target available frequency band supported by the terminal device in the available frequency band, and to determine the target BWP in the multiple bandwidth portions (BWPs) associated with the target frequency band based on the target available frequency band. Receive the target BWP from the network device.

7. A communication method applied to a network device, comprising: Determine at least two carrier bandwidths, wherein the at least two carrier bandwidths include at least one carrier bandwidth supported by both the network device and the terminal device; The terminal device is sent the at least two carrier bandwidths carried in the system information block SIB1 so that the terminal device can use the SIB1 carrying the target carrier bandwidth for cell access, wherein the target carrier bandwidth is the carrier bandwidth among the at least two carrier bandwidths that matches the carrier bandwidth supported by the terminal device.

8. The method according to claim 7, wherein, The method further includes: Send at least two physical random access channel configuration indices carried on the SIB1 to the terminal device, wherein the at least two physical random access channel configuration indices correspond one-to-one with the at least two carrier bandwidths.

9. The method according to claim 8, wherein, The number of SIB1s is multiple, each of the at least two carrier bandwidths is carried by a different SIB1, each of the at least two physical random access channel configuration indices is carried by a different SIB1, and each carrier bandwidth and its corresponding physical random access channel configuration index are carried by the same SIB1.

10. The method according to claim 8, wherein, The method further includes: At least two Non-Cell Defined Synchronization Block (NCD-SSB) measurement information are sent to the terminal device, and each NCD-SSB measurement information is transmitted through an available frequency band of the target frequency band. The terminal device receives measurement results obtained by performing measurements based on the at least two NCD-SSB measurement information, and determines the target available frequency band supported by the terminal device in the available frequency band based on the measurement results. Based on the target available frequency band supported by the terminal device, a target BWP is determined from multiple bandwidth portion BWPs associated with the target frequency band, and the target BWP is sent to the terminal device.

11. The method according to claim 10, wherein, Before determining the target BWP among the multiple bandwidth portions (BWPs) associated with the target frequency band, the method further includes: Based on the physical random access channel configuration index used by the terminal device, determine the SIB1 of the bearer target carrier bandwidth used by the terminal device for cell access; Determining the target BWP among multiple BWPs associated with the target frequency band includes: Based on the target available frequency band supported by the terminal device and the SIB1 of the target carrier bandwidth used by the terminal device for cell access, the target BWP is determined from the multiple BWPs associated with the target frequency band.

12. The method according to claim 11, wherein, Determining the target BWP among multiple BWPs associated with the target frequency band includes: Based on the channel bandwidth supported by the terminal device, the target available frequency band supported by the terminal device, and the SIB1 of the bearer target carrier bandwidth used by the terminal device for cell access, the target BWP is determined from the multiple BWPs associated with the target frequency band.

13. A terminal device comprising a memory and a processor; the memory storing a computer program executable by the processor, wherein the computer program, when executed by the processor, implements the method of any one of claims 1 to 6.

14. A network device comprising a memory and a processor; the memory storing a computer program executable by the processor, wherein the computer program, when executed by the processor, implements the method of any one of claims 7 to 12.

15. A computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method of any one of claims 1 to 12.

16. A computer program product comprising a computer program that, when executed by a processor, implements the method of any one of claims 1 to 12.

Images